What I do on our test server is put dummy entries in the /etc/hosts file for my other tsm servers. The search order is set to check hosts file entries first, then dns.
For example, real server: tsm1 192.168.1.1 on server - in /etc/hosts: tsm2 99.99.99.99 Of course, this is assuming you have names in the tsm server definitions. Rick From: Zoltan Forray/AC/VCU <zfor...@vcu.edu> To: ADSM-L@VM.MARIST.EDU Date: 05/14/2012 09:54 AM Subject: Neutering a test server Sent by: "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> Recently, for migration/testing purposes, I did a full conversion of a 5.5 server to 6.2 on my test TSM server. I would like to continue using this server to test additional upgrades without having to wipe and rebuild. Unfortunately, since it is a copy of a real server, whenever I fire it up, it keeps trying to "reach out and touch" other TSM servers that it has definitions to (library manager, etc), thus producing constant error messages due to invalid passwords, etc. I am concerned if I play with it to do like things mass-deletes, etc, it will try to do things like purge/release tapes, etc. Besides adding to DSMSERV.OPT: DISABLESCHEDS YES NOMIGRRECL What else can I do to neuter it to avoid possible problems? In this same vein, is there a simple way to remove the current instance and install/configure another one? Zoltan Forray TSM Software & Hardware Administrator Virginia Commonwealth University UCC/Office of Technology Services zfor...@vcu.edu - 804-828-4807 Don't be a phishing victim - VCU and other reputable organizations will never use email to request that you reply with your password, social security number or confidential personal information. For more details visit http://infosecurity.vcu.edu/phishing.html ----------------------------------------- The information contained in this message is intended only for the personal and confidential use of the recipient(s) named above. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately, and delete the original message.