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 from the console? Remove/change the test servers
definition from the production server?
Richard Sims <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
08/15/2008 10:28 AM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU>
To
ADSM-L@VM.MARIST.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
