Red Hat Summit Red Hat Summit지원콘솔개발자평가판 시작연락처

이 콘텐츠는 선택한 언어로 제공되지 않습니다.

Appendix B. Testing the Active-Passive Configuration

You must test your disaster recovery solution after configuring it. This section provides multiple options to test the active-passive disaster recovery configuration.

  1. Test failover while the primary site remains active and without interfering with virtual machines on the primary site’s storage domains. See Section B.1, “Discreet Failover Test”.
  2. Test failover and failback using specific storage domains attached to the the primary site, therefore allowing the primary site to remain active. See Section B.2, “Discreet Failover and Failback Test”.
  3. Test failover and failback for an impending disaster where you have a grace period to failover to the secondary site, or an unplanned shutdown of the primary site. See Section B.3, “Full Failover and Failback test”.
Important

Ensure that you completed all the steps to configure your active-passive configuration before running any of these tests.

B.1. Discreet Failover Test
링크 복사

This test simulates a failover while the primary site and all its storage domains remain active, allowing users to continue working in the primary site. For this to happen you will need to disable replication between the primary storage domains and the replicated (secondary) storage domains. During this test the primary site will be unaware of the failover activities on the secondary site.

This test will not allow you to test the failback functionality.

Important

Ensure that no production tasks are performed after the failover. For example, ensure that email systems are blocked from sending emails to real users, or redirect emails elsewhere. If systems are used to directly manage other systems, prohibit access to the systems or ensure that they access parallel systems in the secondary site.

Performing the discreet failover test:

  1. Disable storage replication between the primary and replicated storage domains, and ensure that all replicated storage domains are in read/write mode.

  2. Run the command to fail over to the secondary site: 

    # ansible-playbook playbook --tags "fail_over"
    Copy to Clipboard Toggle word wrap

    For more information, see Section 3.5, “Execute a Failback”.

  3. Verify that all relevant storage domains, virtual machines, and templates are registered and running successfully.

Restoring the environment to its active-passive state:

  1. Detach the storage domains from the secondary site.
  2. Enable storage replication between the primary and secondary storage domains.

B.2. Discreet Failover and Failback Test
링크 복사

For this test you must define testable storage domains that will be used specifically for testing the failover and failback. These storage domains must be replicated so that the replicated storage can be attached to the secondary site. This allows you to test the failover while users continue to work in the primary site.

Note

Red Hat recommends defining the testable storage domains on a separate storage server that can be offline without affecting the primary storage domains used for production in the primary site.

For more information about failing over the environment, cleaning the environment, and performing the failback, see Section 3.3, “Execute a Failover”, Section 3.4, “Clean the Primary Site”, and Section 3.5, “Execute a Failback”.

Performing the discreet failover test:

  1. Stop the test storage domains in the primary site. You can do this by, for example, shutting down the server host or blocking it with a firewall rule.
  2. Disable the storage replication between the testable storage domains and ensure that all replicated storage domains used for the test are in read/write mode.
  3. Place the test primary storage domains into read-only mode.

  4. Run the command to fail over to the secondary site: 

    # ansible-playbook playbook --tags "fail_over"
    Copy to Clipboard Toggle word wrap
  5. Verify that all relevant storage domains, virtual machines, and templates are registered and running successfully.

Performing the discreet failback test

  1. Run the command to clean the primary site and remove all inactive storage domains and related virtual machines and templates: 

    # ansible-playbook playbook --tags "clean_engine"
    Copy to Clipboard Toggle word wrap

  2. Run the failback command: 

    # ansible-playbook playbook --tags "fail_back"
    Copy to Clipboard Toggle word wrap
  3. Enable replication from the primary storage domains to the secondary storage domains.
  4. Verify that all relevant storage domains, virtual machines, and templates are registered and running successfully.

B.3. Full Failover and Failback test
링크 복사

This test performs a full failover and failback between the primary and secondary site. You can simulate the disaster by shutting down the primary site’s hosts or by adding iptables rules to block writing to the storage domains.

For more information about failing over the environment, cleaning the environment, and performing the failback, see Section 3.3, “Execute a Failover”, Section 3.4, “Clean the Primary Site”, and Section 3.5, “Execute a Failback”.

Performing the failover test:

  1. Disable storage replication between the primary and replicated storage domains and ensure that all replicated storage domains are in read/write mode.

  2. Run the command to fail over to the secondary site: 

    # ansible-playbook playbook --tags "fail_over"
    Copy to Clipboard Toggle word wrap
  3. Verify that all relevant storage domains, virtual machines, and templates are registered and running successfully.

Performing the failback test

  1. Synchronize replication between the secondary site’s storage domains and the primary site’s storage domains. The secondary site’s storage domains must be in read/write mode and the primary site’s storage domains must be in read-only mode.

  2. Run the command to clean the primary site and remove all inactive storage domains and related virtual machines and templates: 

    # ansible-playbook playbook --tags "clean_engine"
    Copy to Clipboard Toggle word wrap

  3. Run the failback command: 

    # ansible-playbook playbook --tags "fail_back"
    Copy to Clipboard Toggle word wrap
  4. Enable replication from the primary storage domains to the secondary storage domains.
  5. Verify that all relevant storage domains, virtual machines, and templates are registered and running successfully.
맨 위로 이동
Red Hat logoGithubredditYoutubeTwitter

자세한 정보

평가판, 구매 및 판매

커뮤니티

Red Hat 문서 정보

Red Hat을 사용하는 고객은 신뢰할 수 있는 콘텐츠가 포함된 제품과 서비스를 통해 혁신하고 목표를 달성할 수 있습니다. 최신 업데이트를 확인하세요.

보다 포괄적 수용을 위한 오픈 소스 용어 교체

Red Hat은 코드, 문서, 웹 속성에서 문제가 있는 언어를 교체하기 위해 최선을 다하고 있습니다. 자세한 내용은 다음을 참조하세요.Red Hat 블로그.

Red Hat 소개

Red Hat은 기업이 핵심 데이터 센터에서 네트워크 에지에 이르기까지 플랫폼과 환경 전반에서 더 쉽게 작업할 수 있도록 강화된 솔루션을 제공합니다.

Theme

© 2025 Red Hat