|
dev
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Backup troublesI need some help with a logic for a important document I need to create. Its regarding my Backup procedures that require me to test my database backups every 3 months. The problem occurs that I do not have another server to test out the database. So my solution was the following: * Backup DB * Restore DB redirected towards another DB Now the problem is that QA doesnt think that is enough. I noticed that SQL 2005 (starting since SQL 2000) has this option which alot of 3rd party Backup application use (my case backup exec 10d) "consistency check". I am wondering if I set a consistency check at Backup and then at restore with consistency check, could I absolutely prove that both databases are EXACTLY the same. Example using MD5 for comparing 2 files. "Consistency check is the MD5 for the DB" Thank you so much, George S. Hi
The restoration of the database will only prove that you can backup and restore that backup i.e. the backup was not corrupted. It does not mean to say that the restored database is the one that you backed up i.e. the backup was not subsequently overwritten with a different backup. Therefore the issue is one for protecting the backup and making sure it is not tampered with. A checksum of the backup file may help, but then it doesn't mean that someone has not tampered with where that is stored either!! If checking consistency is the same as a DBCC CHECKDB it is not a comparison of the two databases. HTH John Show quote "George Spiro" wrote: > Hi, > > I need some help with a logic for a important document I need to create. Its > regarding my Backup procedures that require me to test my database backups > every 3 months. The problem occurs that I do not have another server to test > out the database. So my solution was the following: > > * Backup DB > * Restore DB redirected towards another DB > > Now the problem is that QA doesnt think that is enough. I noticed that SQL > 2005 (starting since SQL 2000) has this option which alot of 3rd party > Backup application use (my case backup exec 10d) "consistency check". > > I am wondering if I set a consistency check at Backup and then at restore > with consistency check, could I absolutely prove that both databases are > EXACTLY the same. > > Example using MD5 for comparing 2 files. > "Consistency check is the MD5 for the DB" > > Thank you so much, > > George S. > > > So what exactly is the Check consistency option on SQL 2000 / 2005?
G. Show quote "John Bell" <jbellnewspo***@hotmail.com> wrote in message news:6D092594-641C-46D3-92ED-78F3D0E13678@microsoft.com... > Hi > > The restoration of the database will only prove that you can backup and > restore that backup i.e. the backup was not corrupted. It does not mean to > say that the restored database is the one that you backed up i.e. the > backup > was not subsequently overwritten with a different backup. Therefore the > issue > is one for protecting the backup and making sure it is not tampered with. > A > checksum of the backup file may help, but then it doesn't mean that > someone > has not tampered with where that is stored either!! If checking > consistency > is the same as a DBCC CHECKDB it is not a comparison of the two databases. > > HTH > > John > > "George Spiro" wrote: > >> Hi, >> >> I need some help with a logic for a important document I need to create. >> Its >> regarding my Backup procedures that require me to test my database >> backups >> every 3 months. The problem occurs that I do not have another server to >> test >> out the database. So my solution was the following: >> >> * Backup DB >> * Restore DB redirected towards another DB >> >> Now the problem is that QA doesnt think that is enough. I noticed that >> SQL >> 2005 (starting since SQL 2000) has this option which alot of 3rd party >> Backup application use (my case backup exec 10d) "consistency check". >> >> I am wondering if I set a consistency check at Backup and then at restore >> with consistency check, could I absolutely prove that both databases are >> EXACTLY the same. >> >> Example using MD5 for comparing 2 files. >> "Consistency check is the MD5 for the DB" >> >> Thank you so much, >> >> George S. >> >> >> Hi George
I don't use backup exec so I can not be sure, but the sales literature does talk about performing DBCC commands, I don't think that it is anything that will help you, although you may want to check with Symantic directly. John Show quote "George Spiro" wrote: > So what exactly is the Check consistency option on SQL 2000 / 2005? > > G. > > > "John Bell" <jbellnewspo***@hotmail.com> wrote in message > news:6D092594-641C-46D3-92ED-78F3D0E13678@microsoft.com... > > Hi > > > > The restoration of the database will only prove that you can backup and > > restore that backup i.e. the backup was not corrupted. It does not mean to > > say that the restored database is the one that you backed up i.e. the > > backup > > was not subsequently overwritten with a different backup. Therefore the > > issue > > is one for protecting the backup and making sure it is not tampered with. > > A > > checksum of the backup file may help, but then it doesn't mean that > > someone > > has not tampered with where that is stored either!! If checking > > consistency > > is the same as a DBCC CHECKDB it is not a comparison of the two databases. > > > > HTH > > > > John > > > > "George Spiro" wrote: > > > >> Hi, > >> > >> I need some help with a logic for a important document I need to create. > >> Its > >> regarding my Backup procedures that require me to test my database > >> backups > >> every 3 months. The problem occurs that I do not have another server to > >> test > >> out the database. So my solution was the following: > >> > >> * Backup DB > >> * Restore DB redirected towards another DB > >> > >> Now the problem is that QA doesnt think that is enough. I noticed that > >> SQL > >> 2005 (starting since SQL 2000) has this option which alot of 3rd party > >> Backup application use (my case backup exec 10d) "consistency check". > >> > >> I am wondering if I set a consistency check at Backup and then at restore > >> with consistency check, could I absolutely prove that both databases are > >> EXACTLY the same. > >> > >> Example using MD5 for comparing 2 files. > >> "Consistency check is the MD5 for the DB" > >> > >> Thank you so much, > >> > >> George S. > >> > >> > >> > > >  |
|||||||||||||||||||||||
Other interesting topics