Hi,

The TARGET server (where the DR data resides) sees the data as archive
objects.  When the SOURCE server (where the primary copy of the data
resides) copies the data to the DRPOOL, the objects become archive
objects on the TARGET server.

Most people who use this type of server-to-server implementation do so
for the express purpose of not having to remove the tapes from the
TARGET server (which assumably resides at a different geographical
location than the SOURCE.)

If you still want to remove the tapes, then I suggest that you do the
following:

On the TARGET server, create a storage pool just for the source server
data.  Then, update the Archive Copy Group in the default management
class of the policy domain the SOURCE server belongs to so that it
points to this new storage pool as the destination storage pool.

When volumes are created in that pool, you can check them out of the
library and update their access to OFFSITE.

Laura Buckley
STORServer, Inc.
ph: (719) 531-5133
cell: (719) 337-2436
fax: (719) 266-55576
buckley AT storserver DOT com


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Ubhaykar, Nitin
Sent: Saturday, January 18, 2003 12:39 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Managing Server-to-Server tapes taken offsite



Hi TSMers,

Our site has a TSM implementation which is as follows :

we have 2 TSMs, each backing up different clients into their local
TAPEPOOLs. We have set up remote DRPOOL (using Server-to-Server) across
each other, so that TAPEPOOL contents of each TSMserver get replicated
on DRPOOL of the other TSMserver.

We now intend to take the tapes from DRPOOLs out for off-site storage.
Is there any way that we can mark the tapes taken out as OFFSITE. (Pl.
note that these tapes are unknown to the local TSM and are managed by
the remote TSM).

Any help would be highly appreciated
Thanks in advance.

Regards,
 <<ole0.bmp>> Nitin Ubhayakar
* 3989111 x 69182
* nnu AT kockw DOT com