June 11, 2008 at 11:00 pm
Hi,
I am facing the problem when i am taking the backup and verify it .It makes my server busy
Is there any option so that i can move my backup to another server and verify for the same
and howmuch it is fesiable.
Thanks in Advance
June 11, 2008 at 11:46 pm
wat is the size of ur database
June 12, 2008 at 12:00 am
There is no direct way of doing what you want.... You can take a backup without verifying and restore it in another server to check whether the backup is ok or not. But this will be more of a headache ...
I dont think that verifying a backup can cause a lot of server activity... check whether server activity is due to other reasons or not.
Check whether there are any corruptions in the db using DBCC CheckDB. Do this when your server and db usage is at the lowest point.
"Keep Trying"
June 12, 2008 at 1:19 pm
Yes, using another server to perform a RESTORE VERIFYONLY is valid as it's using the RESTORE command and not the BACKUP command (gitit?).
I have to agree w/the other replies though - the verifyonly operation shouldn't cause your server issues (unless it's at near capacity already)....
Your friendly High-Tech Janitor... 🙂
June 12, 2008 at 8:58 pm
Thanks for your reply but my backup is around 500 GB.
I know that by using restore verifyonly on another server shows the backup is valid but i am not
100 % sure that its completly fesiable .
June 12, 2008 at 9:22 pm
Verification happens by using a command other than BACKUP. That is what makes it feasible to be run on/with/from another server.
Since it's 2005, you can add the CHECKSUM option to your backup routines and it will add a checksum for the backup. The verification process will use this in addition to physically verifying the backup.
Reccomend that you see the RESTORE VERIFYONLY and BACKUP WITH CHEKSUM command in BOL. It's documented in detail there.
Your friendly High-Tech Janitor... 🙂
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply