Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / November 2006

Tip: Looking for answers? Try searching our database.

Backup troubles

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
George Spiro - 21 Nov 2006 21:01 GMT
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.
John Bell - 22 Nov 2006 08:03 GMT
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

> Hi,
>
[quoted text clipped - 20 lines]
>
> George S.
George Spiro - 22 Nov 2006 14:31 GMT
So what exactly is the Check consistency option on SQL 2000 / 2005?

G.

> Hi
>
[quoted text clipped - 44 lines]
>>
>> George S.
John Bell - 22 Nov 2006 15:25 GMT
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

> So what exactly is the Check consistency option on SQL 2000 / 2005?
>
[quoted text clipped - 48 lines]
> >>
> >> George S.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.