1) well, this is why I set up a domain just for remote servers, they have no
backup copy group and their archive copy group has a default of never
expiring archives. (I'm big on covering my a$$)
2) IT is always nice to easily see just what in the heck is going on
utilization wise with a remote server, by sticking it into an isolated
storage pool, it is real easy to look at things.
additional question answer... to delete a filespace of a source server over
on the target server you can't get away with just
del file other_server_node
you are forced to use
del file other_server_node TYPE=SERVER
it is just a CYA in TSM... (which I like ! )
If that is part of a def that you still are having problems with...
I've found it is possible to clean up everything on either end no matter
what order things were deleted/removed
You just have to get the specific commands right with the specific
options...
more along the lines of having to specify "type=server" with a del file,
that sort of stuff
but I've had some pretty UGLY situations and I've been able to clear them
all up...
also remember there are "volumereusedelays" you might have to wait on once
you purge data from tapes & the such...
Oh, and I'm at TSM Srv 3.7 currently.
hope this helps
later,
Dwight
-----Original Message-----
From: Steve Bennett [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 03, 2001 1:22 PM
To: [EMAIL PROTECTED]
Subject: copypools using tsm server to server
Fellow *SMers,
I have two TSM 4.1.3 servers in different cities and would like to use
themn each for offsite storage for the other. Bandwidth considerations
aside I have some other questions based upon things I have read in the
server to server redbook.
This can get a bit convoluted so get ready to wade through my verbage.
1) The book indicates that the virtual vols on the target server are
only deleted at the request of the source server and at no time will the
archive retention of the target server management class cause the
virtual vol archive to be deleted. Have any of you verified this?
2) I would like to have server-1 backup it's primary stgpools to target
server-2 and vice versa. Given that all primary pools for server-1
reside on server-1 is there any reason I shouldn't let the copypool data
from source server-1 comingle with the data in the primary stgpools on
target server-2?
One additional question that might be related to #1 is that at one time
I had some server to server virtual vols defined for primary pool
migration. That has since been abandoned and some of the server to
server and node defs deleted. However there are some parts of the defs
that I cannot delete because it says there are still inventory
references, in particular the other server def. I suspect that because
part of the defs were already deleted there is no way for the source
server to tell the target server to delete the archives and when I try
to do it manually it slaps my hand. Is there any way to delete those
inventory references so I can delete the other server def?
TIA
--
Steve Bennett, (907) 465-5783
State of Alaska, Information Technology Group, Technical Services
Section
