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 / DB Engine / SQL Server / March 2008

Tip: Looking for answers? Try searching our database.

database recovery testing - procedure

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
soonyu - 03 Mar 2008 08:28 GMT
how frequent you guy verify database backup from tape ?
What is the procedure? do you restore from tape and attach to database

Cheers,
Uri Dimant - 03 Mar 2008 09:01 GMT
Hi
Have not played long time with tapes, but you can simple restore the
database to verify a file, very good practice.

> how frequent you guy verify database backup from tape ?
> What is the procedure? do you restore from tape and attach to database
>
> Cheers,
Russell Fields - 03 Mar 2008 14:38 GMT
soonyu,

As Uri says, restore is the best (really the only) way to test if a backup
is good.  You can restore the backup to another database name, so the
restore will not overwrite your working database.

RESTORE DATABASE TestRestoreDB FROM  TAPE ...

RLF

> how frequent you guy verify database backup from tape ?
> What is the procedure? do you restore from tape and attach to database
>
> Cheers,
soonyu - 03 Mar 2008 21:16 GMT
how frequent you do restoration testing per year
and what do you document in your document ?

Cheers,
soonyu

> soonyu,
>
[quoted text clipped - 10 lines]
> >
> > Cheers,
Russell Fields - 04 Mar 2008 14:02 GMT
soonyu,

I do restores all the time as a part of the regular work, to make test
copies of the database, etc. so my backups are tested frequently because of
that.  Of course, you should monitor the backup jobs daily to ensure that
they are running successfully.

I have heard it recommended (and think it is a good idea) to restore some
databases every week.  Rotate through your databases and servers from week
to week.

As far as documentation, a spreadsheet is fine to tick off the last test and
success or failure. (It only gets interesting when there is a failure, of
course.)  I use a workflow system to track problems and resolutions.

RLF

> how frequent you do restoration testing per year
> and what do you document in your document ?
[quoted text clipped - 17 lines]
>> >
>> > Cheers,
 
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.