Ah - A light dawns.

You have a TSM server, 'A', on host 'A' that has connections to a library, 
disk, and other such. You are now building a new copy of the TSM server 'A' on 
host 'B'. If host 'B' does not have physical contact with the library AND your 
new server 'A' does not have a server definition for the old 'A' you should be 
OK.

Like I say, we've never done server to server setups. But I do think it would 
be unusual to define a server to itself, which would be the only way I could 
see the new copy attaching to the old copy at the server level.

When I run my validation tests here I make sure that the normal TSM config for 
my test environment continues to point to the production server. Then I use a 
custom DSM.OPT pointing to a test server stanza in the DSM.SYS to access the 
test TSM server for both client and administrative command-line tools. I also 
partition my library (I have a 3584) and set up an absolute minimum library 
environment -- but only after I've played with expiration.

Does this help, or have I confused the issue?

Tom

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Zoltan Forray/AC/VCU
Sent: Friday, August 15, 2008 10:39 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Expiration on a Test server

This is one of the reasons I haven't brought it up after the reload, yet.

The test server isn't going to use/do anything but test things like EXPIRE
INVENTORY.  We will be erasing/reloading it numerous times.

So, how do I avoid these possible complication?  Disconnect the ethernet
cable and work from the console?  Remove/change the test servers
definition from the production server?




Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
08/15/2008 10:28 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: [ADSM-L] Expiration on a Test server






On Aug 15, 2008, at 10:10 AM, Zoltan Forray/AC/VCU wrote:

> Will doing this effect the actual, live data on the production server,
> since they see each other?  I was concerned it would try to release
> tapes
> and such.

By covertly sharing the real tape library inventory, you're playing
with fire, as the test TSM goes to use "expired" tapes for database
backups and any other server scheduled or triggered events.  That
server may also adjust the settings of tapes in the library, out of
sync with what the real server is doing.  Interesting situations may
result.

    Richard Sims
CONFIDENTIALITY NOTICE:  This email and any attachments are for the 
exclusive and confidential use of the intended recipient.  If you are not
the intended recipient, please do not read, distribute or take action in 
reliance upon this message. If you have received this in error, please 
notify us immediately by return email and promptly delete this message 
and its attachments from your computer system. We do not waive  
attorney-client or work product privilege by the transmission of this
message.