It240 Disaster Plan

The 123 Textiles Corporation is at risk on multiple fronts. Its office location is in peril of natural disasters such as occasional earthquakes. Additionally, it is resides in a high-crime area that puts it in danger of human disasters such as breaking, entering, and theft. In fact, the worst came to fruition one day, when a thief broke into the building through a window and stole the company’s server. I intend to recommend a plan for the 123 Textiles Corporation to aid the recovery of its data in the event of a security breach or unforeseen failure, and how to protect network data from both physical and virtual adversaries.

Establishing a backup plan to ensure recovery of network data and system information can be accomplished through the maintenance of a log of issues and resolutions. A database of trending conflict and resolution consistencies can then be created to provide a readily available list of possible solutions should the same problems occur again. Furthermore, data should consistently undergo backups in relation to how the constant modification of files corresponds to the livelihood of the corporation to make certain that important files are stored in case of catastrophic failure.

An off-site server can provide a backup copy of each computer system and data contained on each computer on a duplicate server or tape drives and cassettes. A valid option of synchronization for 123 Textiles Corporation is a hot site, which is chiefly for fault-toleration executions and not disaster recovery. The organization would be able to relocate its data files with minimal losses to normal operations in real-time by using a hot site. However, a hot site is most applicable to systems that must be fully functional at all times, requiring constant use, and can be a greater expense to the company.

A better option would be to improve the 123 Textile Corporation’s network fault tolerance through adaptive load balancing (ALB), adaptive fault tolerance (AFT), or link...