| REVIEW | Do not wait until disaster strikes enterprises consider resilience and recovery network. The use of six steps can build a network disaster recovery plan for your business needs. Network is a major infrastructure companies, thus building a network disaster recovery plan is essential, mission-critical services can return to work within a specified time. |
Disaster recovery plans already exist several decades of history. However, it must be carefully designed to change and adapt to the new architecture and business use cases. Modern disaster recovery plan including cloud computing, remote workforce, and software-defined network.
The following describes the six practical steps companies can follow to help companies build a successful disaster recovery plan for its network. These steps can be used to build the network for its recovery target type of a disaster recovery plan framework.
Construction of automatic redundancy and flexibility in the network is a costly, time-consuming and complicated process. In these parts of the network, you can justify the creation of additional cost and complexity of automatic failover. Typically in a data center, WAN connectivity and network access computing resources in the cloud to discover the true automatic recovery.
FIELD typically fully elastic layer does not include a wireless LAN and access of end user connections. For these less important segments, you can develop a recovery plan, in line with the use of a specified period of replacement hardware and software service level agreement (SLA) to reconnect to the network.
Once the enterprise network can specify which tasks key to building resilience, the next step is to design and build. Business segment being processed will determine which technology is the most effective elasticity.
Most data centers are using dynamic routing protocol and virtual overlay network technologies to provide real-time failover across hardware and links. The WAN resiliency usually handled by software-defined WAN technologies.
Finally, elastic cloud computing can be implemented in numerous ways, in which the rapid failover technology in some way dependent on enterprises to cooperate with public cloud service providers design and maintenance. In any case, before choosing the option for companies to understand all the options it is very important.
As networks continue to shift from infrastructure hardware-centric to software-centric infrastructure and correct network configuration management becomes more and more necessary. For traditional network, the maintenance of the configuration directory is usually include the use of remote login to the automatic backup application for each network component, and configure copy and paste it into a text file. Then, in the case of hardware or virtualization components are missing, you can organize, store, retrieve these profiles.
Or with updated network architecture configuration of the entire network from a central location. The center position can be locally or in the public cloud. Either way, it becomes easier from a central location to create and store the backup.
In the long run, create flexible disaster recovery plan will save a lot of time.
Hardware replacement in case of a disaster, there are two aspects of choice. The first is to purchase the same hardware components, and replaced in the event of a hardware failure. These components are known as cold spare parts, companies need to be replaced at minimal network downtime, the effect is very good, which is the cost of the most expensive option, because of the need to purchase additional hardware.
Another option is to replace the service level agreement (SLA) signed by the appropriate hardware needed with the manufacturer companies. In some cases, the hardware manufacturer provides a lifetime warranty. In other words, this option hardware replacement time may take several weeks.
Most organizations choose to buy cold standby hardware for the network points, and hardware service providers signed a contract to replace the hardware. Similarly, companies have chosen the correct option can be attributed to hardware components when an interrupt occurs and the importance of the business function is lost.
Once developed processing network disaster plans and processes, the next step is to record the expected recovery, responsibility and communication channels. Expected recovery time is usually around every part of the service network. Responsibilities under the role of individuals, departments, third-party entities, as well as responsible for the implementation of their responsibilities in detail.
Finally, it should create channels of communication documents detailing the best communication flow between the problems being addressed by network technicians and channels in order to better communicate progress to the rest of the organization.
If no steps to assess the situation occurs, the causes and how to network the next time disaster recovery better, then any network disaster recovery plan is not complete. At this point, the team's performance will be evaluated in detail to ensure that the correct processes are followed. In addition, if the evaluation determines that the current process is not satisfactory, you should analyze steps to better improve or change procedures using this root cause.
When building a network disaster recovery plan, final recommendation is to assume major technology and infrastructure changes will happen soon. Therefore, enterprises must develop in such a way processes and procedures, making it easy to modify and communicate with the necessary stakeholders, without having to start from scratch. In the long run, create flexible disaster recovery plan can save a lot of time.
Original from: http://netsecurity.51cto.com/art/201908/600958.htm
This article addresses: https://www.linuxprobe.com/network-disaster-recovery-scheme.html Editor: Ping Ruitao, Auditor: Bao Pang increase
Linux command Daquan: https://www.linuxcool.com/
Linux can view more information: https: //www.linuxprobe.com/