December 1, 2009 at 9:45 am
I have a 300 GB 2005 SQL db, and backup run around 5hours.
How much extra time is requird, if I check the verify backup integrity sql server
December 1, 2009 at 10:04 am
It will probably take a while to verify. That's a fair chunk of data.
On the other hand, the last thing you want is to go to restore the database, and find that your backup is junk. You definitely need to validate them.
Usually, with larger databases like that, you wouldn't use the standard maintenance wizard backups. You'd back up based on files, and a more complex but more efficient backup scheme.
One thing that can often help with backup and restore speed is data compression. I/O is usually the largest bottleneck for backups, and compression can reduce that by a large margin. Since you're using SQL 2005 (2008 Enterprise can do compressed backups on its own), I'd look into a third party backup tool. RedGate (link at the top of the page) has one that works quite well, and can speed up backups by a huge margin.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
December 1, 2009 at 10:08 am
Just bear in mind that unless you did the backup with the CheckSum option, a successful RESTORE VERIFYONLY does not guarantee that the backup is restorable. As far as I'm aware, it checks the header and not very much more. If you want to ensure that the backup is restorable, restore it somewhere else
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply