ADSM-L

Re: MSSQL single database restore

2005-01-27 08:42:43
Subject: Re: MSSQL single database restore
From: Robert Ouzen <rouzen AT UNIV.HAIFA.AC DOT IL>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 27 Jan 2005 15:47:35 +0200
Hi Del

If we do the same by the GUI interface (restore inactive full backup + log in 
one step) did we have to check the recovery option  ???????

Or we have first to restore the full (recovery=no) and after the log 
(recovery=yes)

Regards

Robert Ouzen
E-mail: rouzen AT univ.haifa.ac DOT il
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Del Hoobler
Sent: Wednesday, January 26, 2005 7:52 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: MSSQL single database restore

Kevin,

If you want to restore a specific inactive backup first you should query all 
the backups for the specific database, for example:

     tdpsqlc query tsm dbname /all

This will show you all active and inactive the backups for the specific 
database.

Then... you should perform the restore specifying the exact full backup object 
name that you want to restore using the /OBJECT parameter. For example:

     tdpsqlc restore dbname full /object=<backup-obj-name>

Note: If you also have "log" backups to restore, you should use the
      /RECOVERY=NO on the restore of the full and then restore
      additional log backup objects, specifying the /RECOVERY=YES
      on the restore of the last log backup. For example:

         tdpsqlc restore dbname log=* /object=<backup-obj-name> /recovery=yes

See exact details of command-line syntax and examples of restoring inactive 
backups in the User's Guide.

As far as chasing down the hang situation, you can place a call with IBM 
Support.

Thanks,

Del

----------------------------------------------------

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 01/26/2005
11:42:38 AM:

> Hello All,
> I am attempting to restore a single database on a fairly busy SQL 2k 
> server. I need to go back to a certain point in time because the data 
> is corrupt after this time. Whenever I use the GUI for TDP for MSSQL 
> and
try
> to look at the active/inactive, tdpsql freezes (I think it runs out of 
> memory). So I have tried my hand at the command line. However, I 
> cannot figure out how to go back and get the last full backup at this moment.
All
> I can determine is how to get logs back.
> Unfortunately, I am not a DBA and our DBA does not work with TSM so we
are
> at an impasse.
> If someone could give some assistance that would be great.
> Thanks,
> Kevin
> Kevin M. Lipscomb
> Dan River Inc.
> Systems Engineering
> kevin.lipscomb AT danriver DOT com
> 434-799-4823

<Prev in Thread] Current Thread [Next in Thread>