So, the key is having the VOLHIST file saved, somewhere else, so it can be
reloaded to the rebuilt source server so he can find his DB backup !
Also sounds like doing a RECONCILE on a regular basis, is a good idea !
How often do you run RECONCILE ?
Thanks for enlightening me................
For a while there, we though it was FM ;-) !
Thanks also to "Dwight E. Cook" for your feedback. These are currently test boxes we
are playing with
so I plan to "destroy" the source server and try a recovery !
"Hooft, Jeroen" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
07/19/2002 04:43 AM
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Server-to-Server DB backup and recovery
Zoltan
We have a setup as you describe.
Your devconfig will have the TARGET SERVER as a device-class:
DEFINE DEVCLASS DEFAULT_SERVER_DEV DEVTYPE=SERVER MAXC.......
DEFINE SERVER LAMPS_VBB44_S1 COMMMETHOD=TCPIP HLADDRESS=......
The volhist will show your Database-backup pointing to the right
server/devclass:
* Location for volume LAMPS_VBB44_S1.DBB.026972100 is: 'LAMPS_VBB44_S1'
2002/07/18 08:01:39 BACKUPFULL 2139 0 1 DEFAULT_SERVER_DEV
LAMPS_VBB44_S1.DBB.026972100
With this information you can restore your TSM-DB. Just a "dsmserv restore
db" will do the trick. I tested this once during a TSM course and it
worked
fine (as long as your target server is up). If you have DRM, you can also
send your prepare-plan to the TARGET SERVER. This prepare plan can then be
viewed by the html-interface on the TARGET SERVER.
About Reconcile Volume: That's a (little buggy) tool that corrects errors
in
the administration of the virtual volumes. If a "BA STG" using
server-to-server is interrupted, chances are high that the information on
the target server is inconsistent with the info on the source server.
Reconcile will make this info consistent.
Regards
Jeroen
-----Original Message-----
From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]]
Sent: Thursday, July 18, 2002 10:12 PM
To: [EMAIL PROTECTED]
Subject: Server-to-Server DB backup and recovery
We are working on setting up multiple TSM servers at offsite locations, to
DR type processing.
We plan to do server-to-server to handle both the DB backup and COPY
POOLS.
My question is (I have been digging through the manuals but haven't found
a clear answer....):
Lets say the SOURCE SERVER is destroyed and I now need to rebuild its DB
from the backup that was made to the TARGET SERVER. How do I do this ?
>From what I understand, everything the TARGET server receives looks like
an ARCHIVE file/object to it.
How do you recover the DB from this backup ?
I kinda figured that I would first rebuild the SOURCE SERVER, including
the definition to point to the TARGET SERVER. The books talk about doing
a RECONCILE but when the phrases "delete objects from the target server
that arent on the target server" appear, this did not sound like a good
thing.
Anyone tested this kind of scenario ?
----------------------------------------------------------------------------
------------------------
Zoltan Forray
Virginia Commonwealth University - University Computing Center
e-mail: [EMAIL PROTECTED] - voice: 804-828-4807
