Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Server object move

Status
Not open for further replies.

Juandaman81

IS-IT--Management
Joined
Jun 7, 2004
Messages
182
Location
GB

For the purposes of DR I plan to have some servers in the tree that can be moved should we have a complete failure of a production server.
The plan is:

Change DR server IP address and ship to remote site
When server has arrived give the DR server a r/w of that partition and then do the object move
Make DR server master of the partiton
delete exisiting security objects, eg PKI, SAS for the dead server
Delete dead server object
Rename DR server object
Change Internal IPX number of DR server
Re-create security objects

Will this suffice??
 
No, I don't think you should use that strategy.

What about all the files and trustee assignments, services running, volume objects, etc.

Recovering from a complete system failure is never easy. And you almost need to review each server individually to make sure you have covered all functionality of the server. And you have to make sure you have a way to recover and/or reestablish each service on the replacement server.

Plus if the replacement server is already in the tree, you can't just make it "assume" the identity of another server in the tree. It's a lot more complicated than that. If you do it the way you mention, you will end up with 2 down servers, not just one.




Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Furthermore...

Disaster recovery with Netware requires an intimate knowledge of Directory Services, and the NetWare file structure. Also wouldn't hurt to be very knowledgable of various Netware services, ie GroupWise, NDPS, ZenWorks, or whatever is applicable.

Even if you do have a step by step process in place, it will most likely not work correctly or exactly as you intended. You need to be able to adapt to circumstances or other problems that come up in the process.

One of the best things to do is have good documentation of all server configurations, information about all services running, a copy of all file trustee assignments (TRUSTBAR.NLM), information about Printers and IP addresses (if it's doing printing). Getting stuff back is much easier if you know what you had before the failure.

If you or your staff do not have the expertise to understand the stuff that I have mentioned, you should strongly consider finding someone that can help you with the process.

Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top