Jump to content

Recommended Posts

Posted

Hi

 

I've decided that I need to update my very basic IT Disaster Recovery Plan. Can anyone point me in the direction of a template/guidance that they've come across?

 

How indepth do you go? What info do you add?

 

Thanks :D

Posted

I'm working on the same thing at the moment! I'm using one I wrote at my previous school as a template, which basically lists all the systems, the admin credentials for them, the company who support them, and their phone number. I decided against trying to document how to do a DR on each system, instead just ensuring that a suitably technical person could get access and/or allow the right people to get access. It is written assuming it will be read by a technical person, either my technician/replacement or the support partners, it doesn't contain enough for the Computing teacher or Business Manager to recover things themselves. If you're a one-man-department and/or don't have support contracts on your systems, you may want to write in more detail.

 

When you're done, remember to print a copy and keep it in a sealed envelope in the school safe. The disaster you're recovering from might mean you can't access an electronic version.

  • Thanks 2
Posted
Hi

 

I've decided that I need to update my very basic IT Disaster Recovery Plan. Can anyone point me in the direction of a template/guidance that they've come across?

 

How indepth do you go? What info do you add?

 

Thanks :D

 

We created a simple BC plan template for some of our clients. It might give you a steer …… BC-plan-Rev4.pdf

  • Thanks 3
  • 1 month later...
Posted

In a previous non-school career, we had a DR Plan and used to test it every 2 years.

 

It is fundamental that the DR plan is tested otherwise there is no way to validate that it will ever work when you need it to.

 

Similarly, your change management processes much include checking that the DR Plan is kept up to date whenever you make a change to services or infrastructure.

Posted
We should all remember that any BCDR plan should be incorporated with the school’s critical incident plans. Making sure that it is not looked at in a silo is important. BCDR is also about managing impact, not just managing the tech.
Posted

Consider prevention techniques as well.

 

A friend owns a business of around 30 staff and during Easter the office burnt down. Most of his staff had left their laptops on the premises and they burnt with the building. If they had brought them home they would have had them ready to go and the distribution would be considerably less.

Posted
Consider prevention techniques as well.

 

A friend owns a business of around 30 staff and during Easter the office burnt down. Most of his staff had left their laptops on the premises and they burnt with the building. If they had brought them home they would have had them ready to go and the distribution would be considerably less.

 

You need to risk assess this. The gains you might have from a BCDR point of view could be issues from a data protection and security point of view. Devices can be replaced via insurance, data can be backed up. A lost or stolen laptop can be a bigger issue.

  • Thanks 1
Posted (edited)
You need to risk assess this. The gains you might have from a BCDR point of view could be issues from a data protection and security point of view. Devices can be replaced via insurance, data can be backed up. A lost or stolen laptop can be a bigger issue.

 

All devices regardless of physical location should be secured. Taking them off site should have no baring on how secure the data is.

 

Laptops can't be replaced easy. I have had 400 on order since February and don't expect to see them until August. That would threaten the existence of many organizations.

Edited by FN-GM

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...