Getting a disaster plan ready
I would like to start a disaster recovery preparation on all my netware servers. Is there a tid or steps anyone knows that can assist me.
Thank you
Thank you
ShineOn
Specific to NetWare, or in general?
Welll, BC/DR is a *very* broad subject.
Broadly, the principles are the same as for any other OS environment. Have good offsite backups (that you test periodically). Document your environment. Test your BC/DR plans - Plan your Test and Test your Plan.
With eDirectory and Cluster Services, there are tricks you can pull (for example, if you have a DR site to which you have the necessary connectivity, you can put a server there and have it host Replicas of your eDirectory Tree), but that level of detail is specific to the environment.
Broadly, the principles are the same as for any other OS environment. Have good offsite backups (that you test periodically). Document your environment. Test your BC/DR plans - Plan your Test and Test your Plan.
With eDirectory and Cluster Services, there are tricks you can pull (for example, if you have a DR site to which you have the necessary connectivity, you can put a server there and have it host Replicas of your eDirectory Tree), but that level of detail is specific to the environment.
I used most of the info I found here for my DRP.
http://techrepublic.com.com/1200-10880-5734043.html
Cheers
http://techrepublic.com.com/1200-10880-5734043.html
Cheers
ASKER
The DR/BC plan is specific to Netware for now. I have to setup about 22 servers for DR and all of them are located away from my home office and do not have technical staff to assist me. All the servers run NW6.5 sp5 GW7.01
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Christophadilla
I have never read a DR TID. DR plan and DC plan are usually specific to the user environment. For example, if your building burns down, "What'cha gotten do?"
Do you have proper backup systems in place?
Do you have insurance on your equipment that would replace servers and network equipment if there was major issue?
Do you have proper technical support on the line if the entire thing went down?
Do you have another site available if this one became unusable?
As for restoring servers or data, those steps are usually in a different layer of planning then the DR. If you have got 22 servers without written procedures about how to restore a lost mail box or folder, I would start with that. Refer to those documents in your DR. But basically, a DR is about WHAT YOU ARE GOING TO DO? if there is a disaster. There is are no TID's for that.
Other ideas are, depending on your budget and scale of operation,
- having a hot site, that can be switched over to if there was problem?
- A backup generation could be part of a DR Plan.
- Having all of your backup data at a place like Iron Mountain
- Have a DR box with all of the important installation software and configuration information, keep one off site.
- A list of professional skills or people that could run the network if all your techs got hit by a bus
- Password lists needed to access the network data
A BC plan usually involves difference issues like, what to do on a snow day? What if there was toxic spill on your street and you couldn't get into the building? What if there was terrorist attack? (to be extreme)
In a group of 22 servers, losing a server could hardly be considered a disaster. How to restore a server is not usually part of DR, but rather a reference. Usually, the only mention of platform and applications are made on a list of software needed to restore the network.
I hope this helps.
I have never read a DR TID. DR plan and DC plan are usually specific to the user environment. For example, if your building burns down, "What'cha gotten do?"
Do you have proper backup systems in place?
Do you have insurance on your equipment that would replace servers and network equipment if there was major issue?
Do you have proper technical support on the line if the entire thing went down?
Do you have another site available if this one became unusable?
As for restoring servers or data, those steps are usually in a different layer of planning then the DR. If you have got 22 servers without written procedures about how to restore a lost mail box or folder, I would start with that. Refer to those documents in your DR. But basically, a DR is about WHAT YOU ARE GOING TO DO? if there is a disaster. There is are no TID's for that.
Other ideas are, depending on your budget and scale of operation,
- having a hot site, that can be switched over to if there was problem?
- A backup generation could be part of a DR Plan.
- Having all of your backup data at a place like Iron Mountain
- Have a DR box with all of the important installation software and configuration information, keep one off site.
- A list of professional skills or people that could run the network if all your techs got hit by a bus
- Password lists needed to access the network data
A BC plan usually involves difference issues like, what to do on a snow day? What if there was toxic spill on your street and you couldn't get into the building? What if there was terrorist attack? (to be extreme)
In a group of 22 servers, losing a server could hardly be considered a disaster. How to restore a server is not usually part of DR, but rather a reference. Usually, the only mention of platform and applications are made on a list of software needed to restore the network.
I hope this helps.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you all for your input.