Joni, Should be fine. Just make sure that your device class points to the manual library. You may want to test a small scale DR recovery by creating a DR primary and copy pool and putting a single node's data in it and then test recovery offsite with this subset of data.
If you have a library manager/client relationship defined, you will need up run "upd server forcesync=yes" on both the lib manager and client. If yo have both systems (production and DR) operating simultaneously, you may want to revise the port numbers on the DR system (and clients which attach to it) to prevent any accidents - i.e. if production is 1500 change DR to 2999. Just think, in a year or so, when TSM V6 uses DB2, you will have to re-engineer your replication environment to integrate TSM DB2 with SRDF. There is tons of cooperation between IBM and EMC so this should be a breeze. Have a nice day! Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, March 25, 2008 9:52 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] TSM for a Disaster Hi Neil, Our disk is entirely EMC and we use SRDF/A for our Mainframe and SAN disk and Celerra Replication for our NAS environment. I was just wondering if it would be ok to remove all of the libraries, paths, etc. and still have the software work ok? When I left it in, it couldn't initialize properly because it couldn't find our Virtual tape library, SUN SL8500, etc. Would anyone know if that is ok? Just let me know. Thanks! ******************************** Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ******************************** "Strand, Neil B." <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> 03/25/2008 09:42 AM Please respond to "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> To ADSM-L@VM.MARIST.EDU cc Subject Re: TSM for a Disaster Joni, That sounds great! What disk storage and replication are you using? Neil Strand Storage Engineer - Legg Mason Baltimore, MD. (410) 580-7491 Whatever you can do or believe you can, begin it. Boldness has genius, power and magic. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joni Moyer Sent: Tuesday, March 25, 2008 8:20 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] TSM for a Disaster Hello everyone! I have the TSM database, recovery log, volume history, device configuration and drm plan replicated to our disaster recovery site. The TSM server is an AIX 5.3 server with TSM at 5.3.5.2. At our test drill I tried to bring up TSM without restoring it from a database backup and it worked fine. The only caveat was that I had to remove the library and path definitions to our ACSLS external library and our CDL library information from the device configuration file so that it looked as follows (We use a manual library & manual drives since we only use TSM to restore 2 servers now at disaster recovery. By next year I hope to not need TSM at all.): /* Device Configuration */ DEFINE DEVCLASS DBB DEVTYPE=LTO FORMAT=ULTRIUM2C ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60 MOUNTRETENTION=1 PREFIX=ADSM LIBRARY=SL8500 WORM=NO DRIVEENCRYPTION=ALLOW DEFINE DEVCLASS DBBFILE DEVTYPE=FILE FORMAT=DRIVE MAXCAPACITY=66060288K MOUNTLIMIT=1 DIRECTORY=/tsmprod/db1backup SHARED=NO DEFINE DEVCLASS DR_LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60 MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=DRLIB WORM=NO DRIVEENCRYPTION=ALLOW DEFINE DEVCLASS LTO2 DEVTYPE=LTO FORMAT=ULTRIUM2C ESTCAPACITY=209715200K MOUNTLIMIT=24 MOUNTWAIT=60 MOUNTRETENTION=1 PREFIX=ADSM LIBRARY=SL8500 WORM=NO DRIVE ENCRYPTION=ALLOW DEFINE DEVCLASS LTO2_CDLA DEVTYPE=LTO FORMAT=ULTRIUM2C MOUNTLIMIT=DRIVES MOUNTWAIT=60 MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=CDLA_PROD WORM=NO DRIVEENCRYPTION=ALLOW DEFINE DEVCLASS LTO2_CDLB DEVTYPE=LTO FORMAT=ULTRIUM2C MOUNTLIMIT=DRIVES MOUNTWAIT=60 MOUNTRETENTION=5 PREFIX=ADSM LIBRARY=CDLB_PROD WORM=NO DRIVEENCRYPTION=ALLOW DEFINE DEVCLASS LTO2_OFFSITE DEVTYPE=LTO FORMAT=ULTRIUM2C ESTCAPACITY=209715200K MOUNTLIMIT=DRIVES MOUNTWAIT=60 MOUNTRETENTION=1 PREFIX=ADSM LIBRARY=DRLIB WORM=NO DRIVEENCRYPTION=ALLOW DEFINE SERVER TSMPROD COMMMETHOD=TCPIP HLADDRESS=157.154.47.18 LLADDRESS=1500 SERVERPASSWORD=********************************** SET SERVERNAME TSMPROD SET SERVERPASSWORD **************************************** DEFINE LIBRARY DRLIB LIBTYPE=MANUAL DEFINE DRIVE DRLIB LTO1 DEFINE PATH TSMPROD LTO1 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=DRLIB DEVICE=/dev/rmt0 I then followed the regular steps of the DRM plan Set DSMSERV_CONFIG Set DSMSERV_DIR Do not need to create, format and then initialize the database and log volumes Do not need to restore the server database from a database backup Start the server. Update the LTO2_OFFSITE device class so that it points to the drlib manual library. Define the remaining drives & paths. Register the licenses by running the LICENSE.REGISTRATION script created by the DRM plan. Update copy storage pool volumes so that they are ready for use by running the COPYSTGPOOL.VOLUMES.AVAILABLE script created by the DRM plan. Mark volumes destroyed in copy storage pools that didn't make it offsite to the vault by running COPYSTGPOOL.VOLUMES.DESTROYED script created by the DRM plan. Mark primary storage pool volumes as destroyed by running PRIMARY.VOLUMES.DESTROYED script created by the DRM plan. I'm just wondering if it's ok to do it this way and remove all of that information from the device configuration file such as the regular library definitions, drives, paths, etc. and still have this work? If anyone has any comments please let me know. Thanks! ******************************** Joni Moyer Highmark Storage Systems, Storage Mngt Analyst III Phone Number: (717)302-9966 Fax: (717) 302-9826 [EMAIL PROTECTED] ******************************** IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you. IMPORTANT: E-mail sent through the Internet is not secure. Legg Mason therefore recommends that you do not send any confidential or sensitive information to us via electronic mail, including social security numbers, account numbers, or personal identification numbers. Delivery, and or timely delivery of Internet mail is not guaranteed. Legg Mason therefore recommends that you do not send time sensitive or action-oriented messages to us via electronic mail. This message is intended for the addressee only and may contain privileged or confidential information. Unless you are the intended recipient, you may not use, copy or disclose to anyone any information contained in this message. If you have received this message in error, please notify the author by replying to this message and then kindly delete the message. Thank you.
