We have a similar set-up with FAStT storage in two locations that are not mirrored. Although we use the IBM 3583 tape library. This is how we approached the problem of not extending the SAN to the DR location:
TSM in location A is created with library client and library manager instance. DR site is at location B. TSM in location B is created as library manager instance. Client data goes to disk pools on library client at location A. Disk pools are large enough to store each days incremental. We use server-to-server communication to backup disk pool to remote virtual volumes at location B. These go to local disk pool at location B and then migrated to 3583 library at location B. We then migrate the disk pools at location A to the local tape pools at location A. The data now exists in both locations. Each night a database backup is sent to the remote location along with a backup of the volhist (so we know what virtual volume contains the DBB). During a disaster we have scripted to recreate the library client instance that existed at location A to location B. We then restore the DBB and mark the primary storage pool destroyed. Now if we need to restore a client we point to the new instance of the library client and it will get the data from the virtual volumes stored on the library manager at location B. The longest part is the DB restore but it is currently a manageable time frame. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of John C Dury Sent: Tuesday, December 20, 2005 2:50 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Suggestions on best stategy for our site We have 1 TSM server that is SAN attached to two 3494 libraries, one local and one remote although the TSM server sees them both as local since all data goes through the SAN. All of our TSM clients backup to the local site and it's 3494 library and thyen during the day, that chunk of data from the previous nights backups gets sent to the remote 3494library via the BACKUP STORAGE POOL command. We are going to create a second TSM server which will live at the remote location along with the remote 3494 library. We want the second TSM server to be a hot standby in case of disaster at the primary location. Some details: The TSM server is running on AIX and is using a FastT for it's primary disk storage pool as well as where the TSM DB is stored. We do have another FastT at the remote location but do not have any sort mirror or PPRC option licensed for the 2 FastTs. The FastTs do not see each other and are setup in 2 different SANs as per IBM's recommendations. I'd like to have the second TSM server ready to restore all of our clients in the event of a disaster with the minimal amount of preparation steps as in all likelyhood, I won't be around in the event of a disaster. I'd appreciate and suggestions you all have as I'm sure many of you are in similar situations. Thanks much, John "This e-mail and any attachments may contain confidential and privileged information. Any dissemination or use of the information by a person other than the intended recipient is unauthorized and may be illegal. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this e-mail and destroy any copies. Although this e-mail and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by the Board of Trade of the City of New York, Inc. or the New York Clearing Corporation for any loss or damage arising in any way from its use. Thank you."
