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 way the test system is completely isolated with no chance of trying to contact a production server.
TEST BY TRYING TO PING the production servers/instances!!!!! We use AIX. One thing to watch our for is that the default lookup order is DNS first, hosts file second. (at that's how our systems were) I had to change the search order in the /etc/netsvc.conf file to do local search first, then DNS. Rick "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 08/15/2008 10:37:46 AM: > 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. > ----------------------------------------- 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.
