What John says is interesting because I have seen it both ways.
Sometimes a backup reports it fails, because a single file is corrupt. However this same 'failed' backup works to restore everything BUT the corrupted file. So 99.99+% recovery.

Other times (using different BU method/software) a restore failed if even a just single file had an issue.

Like he said; make sure not only that the backup reported successful, but that restore process (using said backups) actually works.

False security is pretty much the worst security.
I know I'm repeating his point, but it's pretty important.
A backup that doesn't restore is not a backup. It's a waste of time.

As far as cloud backups, I think the time/bandwidth is worth it. It is off site and should be redundant (and backed up yet again) in the cloud.



Make your sound your own!
.. I do not work here, but the benefits are still awesome