It disaster-tolerant strategy under the rising of cloud and virtualization technology

Introduction: The Rise of server virtualization and cloud computing technology does not mean that we no longer need good it disaster planning, toigo that new technologies and budget cuts should not be a reason for IT managers to reduce their concern for disaster tolerance, and that disaster preparedness must receive priority attention.

The rise of server virtualization and cloud computing technology does not mean that we no longer need good it disaster planning and the tape technologies that might be used in these plans. Here are some of the disaster-recovery techniques that Jon Toigo mentioned in his keynote address at his storage decisions meeting.

As CEO and management partner of Toigo partner Analysys, Toigo believes that the reduction of new technologies and budgets should not be a reason for IT managers to reduce their concern for disaster tolerance, and that disaster preparedness must receive priority attention.

"One of the biggest noise disturbances comes from the server virtualization and hypervisor management providers," Toigo in his It disaster recovery planning speech, "These vendors are trying to make you feel like you can no longer need a disaster recovery system." Toigo also refutes the idea that tape is outdated technology, and that tape is an essential part of it disaster recovery planning. "The story of the demise of the tape is nonsense," Toigo said. He says the disk is prone to corruption or failure, and we still need tapes to hold the data.

Some of the advice given by Toigo can protect data effectively and put your disaster-recovery system on the right track. His first suggestion was to make a full backup first. ' You might be surprised to find that there are so many companies that don't have full and timely backups, mainly because of budget cuts and increased workloads, ' says Toigo.

"Let yourself at least do the most basic data protection," he said.

He also advises administrators to take more records of downtime as a lesson. "By looking at these disruptive events, you can learn how to run your storage architecture more efficiently and what you need to do later to avoid these risks," he added.

Documenting the event itself, its causes, and the resulting downtime and financial losses can also help you establish a factual disaster tolerance argument for management. Collecting statistics on your company's own downtime is more effective than using industry-standard statistics.

He also told listeners to be more serious about archiving data, separating infrequently used data from production devices, and dividing the data from the protection of day-to-day data, such as copying backups. Toigo also wants participants to believe that all data will be required when the application is restored.

Using Microsoft's Exchange as an example, he points out that you need not only mail data, but also device drivers, mailbox configurations, and Active Directory settings. "This application is not just a collection of data," Toigo explains. "These are all additional data." If you want to restore the whole environment, you must get all the data. ”

Toigo also advises its listeners to test their data mirroring to ensure that the mirroring operation works properly because disaster-tolerant personnel may rarely be able to understand when the volume files are moved or when they are migrated or increased. "Stop mirroring and check for consistency so you can see if you want the mirror to be mirrored correctly," he said, "and the worst thing is that you found out about the problem in the event of a disaster." ”

Other suggestions for disaster recovery include:

• Use storage virtualization to avoid being locked down by a storage vendor, as well as local and zone-wide interrupt protection at the storage tier.

• Three-phase inspection of the primary and replication sites because the delay of the metropolitan area network affects the transaction and the protection mode of the database data.

• 30 days of data backup between disks to quickly reply to a disaster caused by user actions, such as incorrect file deletion.

• Use your small disaster-recovery site for testing, and some techniques you may not have the funds to deploy at the production site, but can be deployed at the test site. Toigo also mentions technologies such as virtual desktops and IP telephony that can be deployed in this way.

(Responsible editor: admin)