The "best practice" for creating archive backups is "don't do it, create image backups instead".
Archive backups date back to Olden Tymes when folks used diskettes, CDs, DVDs, tape drives, zip drives and the like, sometimes FTP. Nowadays, dirt-cheap external hard drives and the cloud rule the offline backup world, with OS file move/copy commands and USB3 and HTTP used to move the files around.
The reason? Nobody should have to start an engine just to run a RESTORE DATABASE command to get your database back... just "start the engine" and have it do automatic recovery of the backup files (db and log).
Plus, all those other storage mediums were notorious for errors, and nobody ever ran verify because it doubles the backup time, meaning they might as well NOT BOTHER taking a backup.
Always run verify during the offline copy, and always run dbvalid on the end result... if dbvalid says your offline copy is OK then you know (by definition) the online database was OK.
answered 04 Jul '13, 11:21