Thanks very much. Makes sense once I thought about it a moment. I never thought to define multiple servers to get multiple node names.
Just out of curiosity, how did you figure this out? Is there any manual I am missing where this type of example is shown? I tried searching some list archives and never even saw any discussion that hinted at this approach. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Joerg Pohlmann Sent: Thursday, June 30, 2005 3:26 PM To: [email protected] Subject: Re: [ADSM-L] Virtual volumes and multiple diskpools on target server Edward, set up multiple policy domains on your target server. Each Policy domain has a node (type=server) that is used for the virtual volumes by the source server. The default MC in each policy domain can then point to different hierarchies such that you have different physical tapes use for the virtual volumes of the multiple copy storage pools of the source server. On the source server, you will have multiple server definitions with the different nodes to be used for virtual volumes. Then you will have multiple device classes each using a different server defined on the source server. Hope this helps. Joerg Pohlmann 604-535-0452 "Pugliese, Edward" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[email protected]> 2005-06-30 15:13 Please respond to "ADSM: Dist Stor Manager" To [email protected] cc Subject Virtual volumes and multiple diskpools on target server Just to be sure I am not missing something obvious: With server-to-server configured, is it true that you can only have one diskpool or tapepool on the remote server as the destination for the virtual volumes? I have several diskpools on my source server that get backed up to local copypools and then migrated to appropriate tapepools. The local copypool tapes are then sent offsite. I wanted to create a remote copypool for each local diskpool and backup the diskpools to the appropriate remote copypool. The source server has the device class created with device type server. Even if there was more than one device class, they would still point to the same target server. The target server has the source node defined which belongs to a specific domain which has its archive copy group pointing to a specific diskpool or tapepool as its copy destination. Even if I had multiple diskpools or tapepools to select from on the target server, a node can only be defined in one domain and there is no way to specify a different management class to have unique copy destinations. Both TSM Servers are 5.2 running on AIX 5.2. Thanks, Ed "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."
