Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Friday, August 15, 2008 11:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Expiration on a Test server
We don't use DNS references. We use specific IP addresses to force
communic
s are from
192.168.y.z.
Tom
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Friday, August 15, 2008 11:06 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Expiration on a Test server
We don't use DNS references. We use specific
t Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Zoltan
Forray/AC/VCU
Sent: Friday, August 15, 2008 10:39 AM
To: ADSM-L@VM.MARIST.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
We don't use DNS references. We use specific IP addresses to force
communications onto a private connection/subnet between the servers.
Sounds like I need to go with the "unplug from the network" method before
I start the server up and run the expire.
Thanks for all the feedback. I am glad I ask
This is exactly what I do when testing a new TSM upgrade. I restore a DB
to our test server, but before
starting it I put bogus entries in the /etc/hosts file for each of our
production tsm instances and AIX servers, including
the library manager (we have dns aliases for each TSM instance). That
Zoltan -
I wouldn't touch this configuration with someone else's sharp stick.
For one thing, to run expiration in a realistic manner you'll be limited to one
run per day unless you change the date on the test server.
I'd break the testing into at least two stages -- one as a stand-alone, runnin
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 eraseing/reloading it numerous times.
So, how do I avoid these possible complication? Disconnect the ethernet
cable and work
When we did our upgrade testing we did not allow the test server to talk
to the production server by creating a false entry in the hosts file.
We also did not allow our test server to connect to the libraries. This
may be the paranoid approach, but we did not break anything.
Andy Huebner
-Ori
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
