ADSM-L

Re: backup primary stgpool to different library

2002-11-07 08:11:08
Subject: Re: backup primary stgpool to different library
From: "Loon, E.J. van - SPLXM" <Eric-van.Loon AT KLM DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 7 Nov 2002 14:06:36 +0100
Hi Kurt!
It sure is! We do this too and we even use different libraries (a 3584 as
primary and a 3494 as copy library).
If you want, you can contact me directly, even in Dutch :-)
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines


-----Original Message-----
From: kurt.beyers AT pandora DOT be [mailto:kurt.beyers AT PANDORA DOT BE]
Sent: Thursday, November 07, 2002 13:54
To: ADSM-L AT VM.MARIST DOT EDU
Subject: backup primary stgpool to different library


Hi,

I would like to check the following. We will have two identical libraries
connected via SAN to the TSM server. The second library will be in a
different room than the TSM server and the first library.

I would like to have the primary storage pool on the first library and the
copy storage pools on the second library. Is it possible to have a backup of
a primary storage pool residing in library A to a copy storage pool residing
in library B?  I guess it has to be possible as the two libraries are
identical but I want to be sure.

Thanks,
Kurt


**********************************************************************
For information, services and offers, please visit our web site: 
http://www.klm.com. This e-mail and any attachment may contain confidential and 
privileged material intended for the addressee only. If you are not the 
addressee, you are notified that no part of the e-mail or any attachment may be 
disclosed, copied or distributed, and that any other action related to this 
e-mail or attachment is strictly prohibited, and may be unlawful. If you have 
received this e-mail by error, please notify the sender immediately by return 
e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), 
its subsidiaries and/or its employees shall not be liable for the incorrect or 
incomplete transmission of this e-mail or any attachments, nor responsible for 
any delay in receipt.
**********************************************************************

<Prev in Thread] Current Thread [Next in Thread>