Windows Management Disaster Recovery plan

It can be proven that the two most important factors in testing the IT disaster recovery plan are keeping the scheduled updates and testing whether the plan is valid at a critical juncture.

Ideally, each year you will lead the disaster recovery team to rebuild and restore the original product system without error in the offline environment with backup tapes and new hardware. Sounds good, doesn't it? Unfortunately, most companies do not have the ability to fully test their disaster recovery plans every year. Even companies with the ability to do so need to invest more on this basis.

So my question is: how do you avoid calling your boss at 2:00, ask him/her to forgive you, because you forgot to authenticate users who placed important files in a Distributed File System (DFS) share.

There are 4 main parts of the test disaster recovery plan. One of the two steps is to identify the source file and orally schedule the plan. The other two steps, using existing scenarios and learning from errors, are described in detail in Part two.

Identify source files

Source file identification is the basic concept of a disaster recovery plan, but many people do not recognize it correctly. Do you know how to get a copy of all the software after a disaster recovery, and how to rebuild a personal application? The overly assertive side might say, "It's okay, it's back up." "But my first reaction to it was:" Do you promise? Can I get a copy?

You may think that most of them are backed up, but if you review the backup carefully, you'll find that something is missing, such as database schemas, stored programs, firewall rule sets, and DFS shares. is the directory where the user placed the source files correct for DFS shares? You've also overlooked the basics---do you have a copy of Microsoft Windows Server 2003?

You never know when your backup will fail so that you need a copy to start from scratch.

Don't forget to ask your team members if they use tools for offline backups, such as custom LDAP search scripts for Windows Server 2008 and Exchange 2007, VB scripts, and PowerShell scripts.

Oral Pre-Arrange

It costs 50 dollars to buy a pizza for a team member, but if you can find the problem in time, the benefits are priceless.

You'll be amazed at how much you spend half an hour eating lunch with your team members. Open discussion is good for getting your company's ability to cope with disaster. To make this activity a success, you must take some time to plan the agenda beforehand.

The agenda for assessing disaster recovery preparedness is as follows:

Overview (meeting goals)

Windows Server Group

The leader made DRP statement

Hypothesis Analysis

Measures to be taken on the basis of analytical results

Active Directory Group

The leader made DRP statement

Hypothesis Analysis

Measures to be taken on the basis of analytical results

Microsoft SQL Server Group

The leader made DRP statement

Hypothesis Analysis

Measures to be taken on the basis of analytical results

Exchange/messaging Group

The leader made DRP statement

Hypothesis Analysis

Measures to be taken on the basis of analytical results

Action Item (summary)

A hypothetical analysis ("What if") refers to a hypothetical question that everyone in the group asks to other team members to see how they respond to various possible failures.

The final step is to determine the time of the next meeting and to ensure that each group will put forward the proposed measures into practice. Each group leader is responsible for the corresponding measures respectively. This activity can be held quarterly to ensure that everyone is paying enough attention to disaster recovery.