database recovery testing - procedure

how frequent you guy verify database backup from tape ?
What is the procedure? do you restore from tape and attach to database
Cheers,Hi
Have not played long time with tapes, but you can simple restore the
database to verify a file, very good practice.
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:78EAC7A2-D57F-4894-AE12-E1951E27CE76@.microsoft.com...
> how frequent you guy verify database backup from tape ?
> What is the procedure? do you restore from tape and attach to database
> Cheers,|||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
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:78EAC7A2-D57F-4894-AE12-E1951E27CE76@.microsoft.com...
> how frequent you guy verify database backup from tape ?
> What is the procedure? do you restore from tape and attach to database
> Cheers,|||how frequent you do restoration testing per year
and what do you document in your document ?
Cheers,
soonyu
"Russell Fields" wrote:
> 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
> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
> news:78EAC7A2-D57F-4894-AE12-E1951E27CE76@.microsoft.com...
> > how frequent you guy verify database backup from tape ?
> > What is the procedure? do you restore from tape and attach to database
> >
> > Cheers,
>
>|||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
"soonyu" <soonyu@.discussions.microsoft.com> wrote in message
news:46C15702-8FEA-4221-9778-48634D3F1769@.microsoft.com...
> how frequent you do restoration testing per year
> and what do you document in your document ?
> Cheers,
> soonyu
> "Russell Fields" wrote:
>> 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
>> "soonyu" <soonyu@.discussions.microsoft.com> wrote in message
>> news:78EAC7A2-D57F-4894-AE12-E1951E27CE76@.microsoft.com...
>> > how frequent you guy verify database backup from tape ?
>> > What is the procedure? do you restore from tape and attach to database
>> >
>> > Cheers,
>>