It looks you haven't read my original message. My current configuration is exactly the same as you suggested - main TSM Server is mirrored by disk subsystem DS8100 (PPRC) and I can start it at DR without restoring database.
I am just trying now: - to avoid tape movement between Head Office and Disaster Site at all by direct copy to DR site; - to speed up recovery process using parallel recovery from FILE copy pool (better performance and no mount limit). Grigori G. Solonovitch Senior Technical Architect Information Technology Ahli United Bank Kuwait http://www.ahliunited.com.kw Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: grigori.solonovi...@ahliunited.com Please consider the environment before printing this Email -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Wednesday, September 15, 2010 4:40 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Using copy pool (device class FILE) Why do all the import export stuff. Just have an TSM instance on the disaster site, backup your db to the offsite Devclass as file, start tsm on the offsite with that db... Mark the primary vols unavailable and you're up! -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: Wednesday, September 15, 2010 7:58 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Using copy pool (device class FILE) I have: 1) defined target server AUBKDR on source server BKME by "def ser AUBKDR password=xxx hla=yyy lla=zzz" - for virtual volumes; 2) defined source server BKME on target AUBDR by "def ser BKME password=xxx hla=yyy lla=zzz" - for virtual volumes; 3) pinged servers by "ping server NAME" successfully; 4) exported policy from source server BKME to target server AUBDR by "exp pol AIX tos=AUBKDR"; 5) exported admins from source server BKME to target server AUBDR by "exp admin XXX tos=AUBKDR"; 6) exported all AIX nodes from source server BKME to target server AUBDR by "exp node XXX filedata=none tos=AUBKDR"; 7) create FILE device class on server AUBKDR by "define devclass DCP3_DR devtype=FILE mountlimit=32 maxcapacity=64G directory=/DCP3_DR shared=yes" - shared=y is OK or not? 8) created FILE copy pool on server AUBKDR by "define stgpool DCP3_DR DCP3_DR pooltype=copy maxscratch=0 reclaim=50"; 9) created volumes for stgpool DCP3_DR on server AUBKDR by "define volume DCP3_DR DCP3XXXX formatsize=65536"; 10) created device class on server BKME by "DEFINE DEVCLASS DCP3_DR DEVTYPE=Server SERVERNAME=AUBKDR MAXCAPACITY=64G PREFIX=DCP3"; 11) created stgpool on server BKME by "DEFINE STGPOOL DCP3_DR DCP3_DR POOLTYPE= Copy RECLAIM=50 RECLAIMPROCESS=1 RECLAMATIONTYPE=THRESHOLD COLLOCATE='No'. I do not know, what is the next step. Grigori G. Solonovitch Senior Technical Architect Information Technology Ahli United Bank Kuwait http://www.ahliunited.com.kw Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: grigori.solonovi...@ahliunited.com Please consider the environment before printing this Email -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Hart, Charles A Sent: Wednesday, September 15, 2010 3:09 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Using copy pool (device class FILE) I may be oversimplifying, but all you need to do is create a Copy pool using the Devclass file... Of course you have to have a FCIP connection or configure TSM to TSM server to server with virtual volumes. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Grigori Solonovitch Sent: Wednesday, September 15, 2010 3:02 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Using copy pool (device class FILE) Hello Everybody, I am trying to avoid tape movement between Head Office and Disaster Site by using additional copy pool (device class FILE) at Disaster Site: 1) main instance of TSM Server 5.5.4.1 is running at Head Office; 2) additional instance of TSM Server 5.5.4.1 is running at Disaster Site; 3) main and additional TSM servers are cross-defined; 4) policy and nodes are imported to disaster TSM Server; 5) main instance of TSM Server is mirrored online to Disaster Site by PPRC (files, database, logs) and can be activated in case of disaster to restore data from tape copy pool; 6) there is enough disk space to create additional copy pool (FILE) on TSM Server at Disaster Site. Is it possible to backup primary pools at Head Office directly to FILE copy pool at Disaster Site to be able to restore data from disk in case of disaster (avoid using tape copy pool)? If yes, I need help to configure remote FILE copy pool (any suggestions, documents, links, red books, etc). I will deeply appreciate your help. Kindest regards, Grigori G. Solonovitch Senior Technical Architect Information Technology Ahli United Bank Kuwait http://www.ahliunited.com.kw Phone: (+965) 2231-2274 Mobile: (+965) 99798073 E-Mail: grigori.solonovi...@ahliunited.com<mailto:grigori.solonovi...@ahliunited .com> Please consider the environment before printing this Email ________________________________ CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. Please consider the environment before printing this Email. This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ________________________________ CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software. This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. ________________________________ CONFIDENTIALITY AND WAIVER: The information contained in this electronic mail message and any attachments hereto may be legally privileged and confidential. The information is intended only for the recipient(s) named in this message. If you are not the intended recipient you are notified that any use, disclosure, copying or distribution is prohibited. If you have received this in error please contact the sender and delete this message and any attachments from your computer system. We do not guarantee that this message or any attachment to it is secure or free from errors, computer viruses or other conditions that may damage or interfere with data, hardware or software.
