Yuck..... Yes this would be possible if your DB and your
environment is small.

        With your scenario, between steps 3 and 5, no clients can
connect to the TSM server (as their data would disappear when step #5
were executed). Where we have Databases push transaction/redo logs to
the TSM servers almost constantly, this would not be possible as their
data would be lost.

        We would have to restore the previous TSM DB to second server
instance to recover that data.

Ben

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Prather, Wanda
Sent: Wednesday, March 17, 2004 1:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Recovery of deleted filespaces


Well, the good news - you get to test your DR plan!
Bad news - it's quite a bit of work.

1) STOP any reclamation processes ASAP.

2) BACKUP your TSM DB as it is now.

3) RESTORE your TSM DB to a point BEFORE your deleted the filespace.

4) EXPORT the client's filespace to a tape.    (Will work unless a
RECLAIM
managed to write over the data after you deleted the filespace).

5) RESTORE your TSM DB from the backup in 2) above

6) IMPORT the filespace you exported.

Good luck!


-----Original Message-----
From: Chet Osborn [mailto:osborn AT RPI DOT EDU]
Sent: Wednesday, March 17, 2004 3:28 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Recovery of deleted filespaces


Hi,

In attempting to help a user clean up his backups, mistakenly assumed
that he had copies of the subset of folders that he wanted to back up on
his disk drive. I deleted the TSM filespace, only to discover that my
assumption was incorrect.

If I can figure out which tapes the backups are on, is there any way of
restoring them?

Chet Osborn
Rensselaer Polytechnic Institute