do a volhist after a full DB backup. If it is a dbbackup or copypool volume, take it. That is roughly what DRM will tell you to do.
I would do a 'quick' install of DRM if you are licensed, and generate a plan file. It will tell you what you need. Configuration is pretty intuitive. I also suggest you do a 'q license' and take that info with you as well as your CD with the license files. just to make life a little easier if you have more than the number of clients that the evaluation license allows. > -----Original Message----- > From: Braich, Raminder [SMTP:[EMAIL PROTECTED]] > Sent: Monday, January 06, 2003 1:15 PM > To: [EMAIL PROTECTED] > Subject: DR test - which volumes to take > > Hi, > TSM Server is 4.1.2 (to be upgraded shortly), clients are 4.1.2 and 4.2. > We would be doing our Disaster Recovery test shortly. DRM has not been > implemented. The plan calls for to request courier deliver the necessary > tapes back and we take these tapes to the recovery site. We run SAP R/3 > with > Oracle DB on WIN NT platform. All the systems are windows based. I have > identified the requirements to restore the TSM server as follows: > 1. Device Confiuration file. > 2. Server Options file. > 3. Volume history file. > 4. Output of q dbv f=d and q logv f=d. > 5. TSM Database backup volume. > The servers we are going to restore are going to be SAP R/3, Mail, File > Server and Oracle DB server(outside of SAP R/3). > We do not have collocation turned on. My question is how can I know which > tapes to request back from offsite to restore SAP R/3 which is backed up > via > TDP for R/3, Exchange(Mail) which is backed up via TDP for Exchange and > File > Server which is backed up incremental and Oracle DB server which is backed > up via TDP for Oracle. The requirement is to know all the tapes which are > going to be needed before hand. It has been implied that the courier is > not > going to deliver the tapes to the recovery site (which sounds silly to > me). > > What are other folks doing for this kind of situation? Are there any best > practices to follow. > > Thanks, > Raminder Braich.
