One thing I neglected to add..(important however) Once the restore is complete and you reboot, then you will attempt to have two servers on the network with same name and SID...not a good thing. You really need to convince the application/server owner to allow you to bring it offline temporarily by disconnecting the network cable at the recover server reboot time to avoid this. Then check the success of the recovery.
Again, stress the importance of testing... you don't want to trouble shoot.. and they will not want to wait if a real recovery needs to take place and you are working out the kinks... And trust me... there will be kinks. Matt -----Original Message----- From: Adams, Matt (US - Hermitage) Sent: Friday, February 08, 2002 7:44 AM To: 'ADSM: Dist Stor Manager' Subject: RE: Testing A WIN2k Server restore You could name your test(recovery) server to something different than your production server. Once it comes back up, you can go into the registry and find the "ComputerName" registry key located in: "HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\ComputerName\ActiveComputer Name" to the production server name. Don't reboot. This will fool TSM enough to do the restore. Now... all that being said, you are reducing the chance of a successful restore. I wouldn't recommend it for an actual recovery, but it will work to do a test restore. Best thing to do is to get the application owner on board with the testing and explain its importance of a successful recovery of his/her application. This might allow you to test recovery on the actual box. Or have a second box similar in function that is only a testing box that can be brought offline for the recovery testing. Just some thoughts.. Matt Adams Tivoli Storage Manager Team Hermitage Site Tech Deloitte & Touche USA LLP 615.882.6861 -----Original Message----- From: Amini, Mehdi [mailto:[EMAIL PROTECTED]] Sent: Friday, February 08, 2002 7:16 AM To: [EMAIL PROTECTED] Subject: Testing A WIN2k Server restore Hi All, I have finally found a server that I can do a test restore. According to the Redbook SG24-6141-00 I have to Name the computer the same as the one I am trying to recover. My problem is that the recovering Server is still in production and I would like to do a test recovery of this server. I have installed Minimum OS on this second machine, and it is in its own work Group. But when I try to name the Server the same as the recovering server, I get a message that a duplicate name found on the Network. How can I name the second server as the same as the first server and at the same time be able to see the TSM Server without connecting the our main Network? Any help would be greatly appreciated. Mehdi Amini LAN/WAN Engineer ValueOptions 3110 Fairview Park Drive Falls Church, VA 22042 Phone: 703-208-8754 Fax: 703-205-6879 ********************************************************************** This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the sender by email, delete and destroy this message and its attachments. ********************************************************************** - This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. - If you are not the intended recipient, you should delete this message and are hereby notified that any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited.
