Disaster recovery planning is a challenging process. While we focus on the planning phase, people are naturally more tangible for disasters such as fire, theft and natural disasters. Disaster data are considered, but only as rare events. This is a shortsighted approach that companies should take a global conflict with their plans for disaster. Think proactive to help solve this problem and protect your business. Here are some activeTips for the emergency plan:
Documentation
Disaster Recovery Planning
A review of emergency procedures on a quarterly basis is a proactive approach to disaster recovery. Key personnel should be up to all the technical article on the main business systems and data messaging systems. Detailed documentation should be in the server room, description of individual machine configurations and software settings. Administrative documents must be complete with allMachine.
Microsoft Exchange Server Redundancy
For example, a company with Microsoft Exchange message server a secondary server is again in place to manage the retrieval of information during a server store? All current versions of Exchange Server log files to record transactions post before being transferred to the Information Store database. While "circular logging" can help to save storage space, during a data disaster on a completeLog files are essential to bring in a restored information store to date and get the user to their data.
The data stored on tape media
Disaster recovery planning should develop plans for the offsite storage of backup tapes and other media. Tape backup to provide additional validation testing phases of the plan. It 'good to test your backups regularly. Tape rotation regularly and consistently, and monitor the duration of the tapes is an important process to reduce theMedia failures.
RAID Systems
If disasters with RAID storage systems, SANs, NAS and JBOD systems, disaster planning takes a different perspective. These storage systems have redundant architecture to avoid failures and disasters. However, this can provide a false sense of security.
For example, a customer last year was 40 TB of disk space distributed more than 20 servers. These systems had hardware RAID 1 +0. The problems began to eventsa server, if it were a disc to go offline for a moment. The controller card would change the mirror as part of the process of redundancy. In the end, the first unit would be back online. The controller card would be returned to the original disk and inconsistent data from a file system volume and perspective. After a system power down and restart, the computer storage hardware reset. Start the operating system, the automatic volume repair program and began to produceRepairs. This was the cause of additional problems that the integrity of the file system and critical data was not available. The data should be readily available and Remote Data Recovery is the best option for this client.
This case history is interesting for the cascade of failures that occur in rapid succession. This client was processing large amounts of data from three shifts per day. To store the amount of variation in the data of each night was not possible. The customerwas convinced that the storage configuration "bullet proof" has mirrored.
These configurations can be successful against most units. In this case, but never the disk fails, you just went off-line. If the unit is back online, there are inconsistencies. Consequently, the data were not available when the automatic volume control has begun to make repairs repair tool. Engineers worked all night to the data. At the end ofDisaster recovery was 100% success.Data may one level, a disk drive fails or data is missing. Multi-tier data disasters are combinations of small disasters.
Disaster Recovery Planning - Tips for a proactive approach
ไม่มีความคิดเห็น:
แสดงความคิดเห็น