I did not intend to imply you can't restore the DB from the target server. What I meant is that you cannot restore client files from the target server. You have to get the source server up and running again.
It's really no different from any other DR situation. If you lose your primary TSM server, you have to go and get the tapes out of the vault and reload the DB before you can do client restores. With server-to-server, your vault is electronic, so you don't have to physically go and get the tapes, the data comes over the wire. But you STILL have to reload the DB of the source server. -----Original Message----- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]] Sent: Thursday, April 18, 2002 2:36 PM To: [EMAIL PROTECTED] Subject: Re: Offsite Mirror of TSM server That is what I guessed from the docs. I was hoping I was wrong ! So, of what value would a DB backup to a "target" server be ? I could never recover from it !!! Sounds like a partially implemented and of very limited use feature, to me !! Is anybody out there using a "target" server to perform backups of any kind ? If you do, the better question would be, why and how ? "Prather, Wanda" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 04/18/2002 01:03 PM Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject: Re: Offsite Mirror of TSM server My understanding is that when you use source/target server, you think of the "target" TSM server as just an electronic vault. It is NOT the same as having a backup TSM server. As you said, the objects in the target server's data base are archive objects. The metadata needed to restore the data is still in the DB of the SOURCE server. So you won't be able to do restores, until you build a repair/recovery source server and reload its DB. Now someone else might reasonably expect to reload the DB into a TSM server at the offsite location; but since you are planning for the target/source TSM's to be on different platforms, that won't be an option. You will need to rebuild the TSM server on your OS/390 recovery machine, wherever that is. -----Original Message----- From: Zoltan Forray/AC/VCU [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 17, 2002 1:46 PM To: [EMAIL PROTECTED] Subject: Offsite Mirror of TSM server Let me preface this with, I am not sure how to completely ask these questions since I don't have all of the details but hopefully someone can give me some idea of how TSM can/will handle this, if at all possible. Current configuration: TSM 4.1 on OS/390 using 3590B tape drives in a 3494 ATL Requirements as I understand them: Setup a off-location "hot site" backup TSM server that will have copies of everything the main server and/or other TSM server (we are working on splitting the TSM traffic/load onto another TSM server) has. The "hot site" server will probably be an AIX box with 3590E (possibly FC) drives. I have looked into the source/target server issue but am a little confused since the "target" server will only see things that come from the "source" server as archive objects. If the building with the "source" server burns down (and this same building also houses a majority of the clients that are backed up !), how would the "target" server be used to restore all of the client nodes ? How about the database backups that are sent to the "target" server ? What use are they if you have to have the "source" server to identify what is on the "target" server ? Should I/could I setup database mirror volumes on a remote (target ?) server over simple IP connections or is this only possible with DASD using XRC processes....especially since the current, main database is on OS390 ? If this was moved to an AIX box, how would this be handled ? NFS ??? As you can tell, any and all guidance is greatly appreciated !!! ---------------------------------------------------------------------------- ------------------------ Zoltan Forray Virginia Commonwealth University - University Computing Center e-mail: [EMAIL PROTECTED] - voice: 804-828-4807
