DR plans likewise are much easier when you don’t have to consider how the actual workers are going to access these systems. If the main site is cratered, there has to be some way for your workers to actually get to the data itself. Again, it doesn’t matter that much if all of the servers are up and running if you have a thousand users sitting at home with no way of accessing anything and no location to go to.
This part of the plan will have to be closely coordinated with non-IT staff to properly accommodate what the other divisions plan to do with users in the event of loss of access to the main site. Do the business processes allow non-IT to work remotely from home? If so, are you legally allowed to let them access company data on their home computers?
If users need to work together, and conference rooms are rented at (for example) a hotel, will you be able to get the connectivity necessary to get those users functional? What end points will they work on in that location? What about voice communications? Are there soft phones to allow those users to get on the phone through their connection to the DR site? Will cell phones be distributed? What happens to the main dial-in number? Does it get forwarded somewhere else? Also, it would be important to work with management to determine if there is a subset of users who are strictly required for everything to function and if those users need to be functional first before the rest.
Check out our last post on disaster recovery, covering technical documentation, or skip around to read the rest of our series:
- What is a Disaster?
- How to Construct a Proper Disaster Recovery Plan
- Management Buy-In
- Care and Feeding