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
-----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 9:10 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] Expiration on a Test server

We have purchased a new, even beefier server then our last one.

To make sure it is configured optimally, we want to test how long an
expire inventory runs.  Our biggest server is up to 190G DB and expires
run 40-48hours.

I installed and configured the new server, connecting it to the main,
tape
library owning server, which happens to be the one with the big DB.

I have taken the 190G DB and restored it to this new server.

Never having done this, I may be asking stupid question, but want to be
sure I don't do anything irreversible that may effect the production
server.

I want to run an EXPIRE INVENTORY against the restored database, perhaps
numerous times.

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.


This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.
Thank you.