If your DR plan is a 30-page document that has been written up by a sole individual and e-mailed to the IT department with the hope that everyone is going to read, understand, and be able to act on its contents, then you can pretty much guarantee that your DR plan will fail.
Writing the plan is the first step, but the plan needs to be continuously shared with other team members and when the plan is implemented, communications and updates must continue as stated in Chapter 1, Planning and Key Concepts – What Not to Forget, and Chapter 2, Creating, Testing, and Maintaining the DR Plan. Keys are the defined roles within your DR plan, with who is responsible for the backup and restoration of the technologies such as Windows Server, the SQL Server databases, and the communications to the organization.
Another important aspect of a DR plan is the practice of testing the recovery process which obviously confirms that the plan works.
When a recovery is first...