Disaster recovery planning is a difficult process. During the planning phase, through which people naturally more tangible disasters such as fire, burglary concentrate, and natural disasters. Data are also known as disasters, but only as rare. This is a short-sighted attitude that should emphasize the comprehensive approach, unlike companies with their plans to take disaster. Thinking proactively can be better protected to solve this problem and keep your business. Here are someproactive suggestions for your disaster plan:

Documentation

A review of emergency procedures on a quarterly basis is a proactive approach to disaster recovery. Key personnel should be abreast of all technical articles on the primary business systems or messaging systems. A detailed documentation is in the server room area available, describes individual machine configurations and software settings. Administrative documentation should with any fullMachine.

Microsoft Exchange Server Redundancy

For example, in a company with Microsoft Exchange message server, there is a secondary server back in place to restore the Information Store during the failure of the server handle? All current versions of Exchange Server log files record to message transactions before they are committed to the information store database. While ‘Circular Logging’ is the storage capacity to support, during a data disaster, a complete set ofLog files are put in a restored information store service to date and get back the user to their data is crucial.Raid recovery

Archived data on tape media

Disaster recovery planning should have plans for off-site storage of backup tapes and other media. Tape backups bring additional validation check steps to the plan. It is advisable to check the backups at regular intervals. Tape rotation should be regular and consistent monitoring and life of the tapes is an important process toMedia to reduce failures.

RAID Systems

If it disasters with RAID storage systems, SAN systems, JBOD systems and NAS systems, disaster planning is, takes a different perspective. These storage systems are redundant architecture to prevent breakdowns and accidents. However, this may create a false sense of security.Raid recovery

For example, a customer had to distribute 40TB storage space last year, more than 20 servers. These systems were hardware RAID 1 +0Configurations. Problems started things on a server if a drive off-line would go for a moment. The controller card would go to copy the mirror as part of the redundancy process. Eventually, the first drive would be back online. The controller card would switch back to the original drive, and it would be contradictory data from a volume and file system perspective. After a system power down and restart the storage system hardware reset. The operating system is automatic volume controlRepair program started and began making repairs. This was the cause of additional problems, the integrity of the file system and critical data is no longer available. The data had to be immediately available and Remote Data Recovery was the best option for this client. READ MORE http://www.raidrecovery.pannipa.com/2009/09/10/disaster-recovery-planning-tips-for-a-proactive-approach/