Failover testing template


















Partner with Evolve IP and gain the combined experience of hundreds of technologists, all acting as an extension of your IT team. Helping you do more with less. Request Information 1. Request Information or Call 1. Skip to content. Disaster Recovery Plan Template. Hardware fails, hackers attack, and disasters happen.

Use this template to create your DR plan to prepare your organization from common IT-based business disruptions. Key questions answered by a comprehensive DR Plan include:. Are employees and service providers able to execute the plan? Are data backups accessible within the desired timeframes? Are contingencies in place to adapt to accommodate resources or employees that may not be able to participate in the recovery process due to the disaster itself?

Can the recovery time objective RTO practical or attainable? Can the systems be restored with an acceptable degree of data loss? Instructions for Using This Template. Content Key:. Disaster Recovery Plan Template Introduction. The Purpose of the DR Plan. Emergency Contact Form. External Contacts. Notification Network. Required Any changes, edits and updates made to the DR Plan will be recorded in here. Add rows as required as the DR Plan is amended. Disaster Recovery Lead.

Edit this list to reflect your organization Make the determination that the organization is declaring that a disaster has occurred and trigger the DR Plan and related processes. Initiate the DR Notification Network. Be the single point of contact for and oversee all of the DR Teams. Organize and chair regular meetings of the DR Team leads throughout the disaster. Present to the Management Team on the state of the disaster and the decisions that need to be made.

Contact Information. Management Team. Network Team. Required The Network Team will be responsible for assessing damage specific to any network infrastructure and for provisioning data and voice network connectivity including WAN, LAN, and any telephony connections internally within the organization as well as telephony and data connections with the outside world. If network services are provided by third parties, the team will communicate and co-ordinate with these third parties to ensure recovery of connectivity.

Server Team. Required The Server Team will be responsible for providing the physical server infrastructure required for the organization to run its IT operations and applications in the event of and during a disaster.

Applications Team. Required The Applications Team will be responsible for ensuring that all organization applications operate as required to meet business objectives in the event of and during a disaster. Data in Order of Criticality. Restoring IT Functionality.

Current System Architecture Required Insert a detailed system architecture diagram that identifies all of your systems and their locations. IT Systems. Network Equipment. Load Balancers. VPN Devices. Miscellaneous Network Appliances.

Severity One System. When determining the right Disaster Recovery services, there are three aspects to consider: Source of System — Whether your system is onsite, in the Evolve IP Cloud, or elsewhere. All policies run this procedure on all policies. Domain mark. Verify dual delegation in DNS before failover.

DFS failover preparation. Verify all DFS mounts have both referrals configured. Communicate to application teams and business units that use the cluster the failover outage impact. Scheduled maintenance window with application and business units.

Ensure to explain that data loss will occur if data is written passed the maintenance window start time. Steps on the failover Day.

For SMB protocol the 2. This inserts a deny read permission dynamically before failover starts and removes after failover completes.

NFS requires the protocol to be disable to guarantee no IO. Exports should be unmounted before disabling the the protocol on the cluster. Force run syncIQ policies 1 hour before planned failover. Run each syncIQ policy before so that the failover policy run will less data to sync. Execute failover. Monitor failover.

How to Monitor the Eyeglass Assisted Failover. If Required Data recovery guide. Failover Recovery Procedures. Ensure Active Directory admin is available.

After Failover. Test Data Access. Use post failover steps guided steps. Home Top. Record the make writable time difference log step to the beginning of the failover log time stamp Repeat one more time with 3 policies same amount of data in each directory Now average the 3 test run times to the make writeable step and use this value that is unique to your environment clusters, WAN, nodes in replication, etc.. Note: The reason to create as many shares under each policy as in production is to get the time for the rename step to complete for each share, this step is parallel operation but should be benchmarked on your clusters Note: failover logs include steps post failover to prepare for failback and complete audit of the clusters.

Calculate the average time per policy based on your production configuration Use this number to estimate the time to complete your production failover times Note: The reason to create as many shares under each policy as in production is to get the time for the rename step to complete for each share, this step is parallel operation but should be benchmarked on your clusters Note: failover logs include steps post failover to prepare for failback and complete audit of the clusters.

The test network should mimic your production network:. Although we recommended that you use a test network separate from your production network, if you do want to test a disaster recovery drill into your production network, note the following:.

To run a test failover for application testing, you need a copy of your production Active Directory environment in your test environment. Read test failover considerations for Active Directory to learn more. Follow the steps described here to troubleshoot any connectivity issues post failover. After you've completed a disaster recovery drill, learn more about other types of failover. Skip to main content. This browser is no longer supported.

Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Please rate your experience Yes No. Any additional feedback? Submit and view feedback for This product This page. View all page feedback. In this article.



0コメント

  • 1000 / 1000