PITR Session: Continuous Failover
A Point-In-Time-Recovery session can be automatically started after VMs of a PITR-enabled domain have been recovered for continuous failover. Use this option if the entire protected site is compromised and all VMs should be failed over to the DR recovery site and then PITR used to roll back VMs to a certain point in time.
- Set up a PITR-enabled protected domain.
- Start Continuous Failover of the protected domain.
Start continuous failover of the PITR-enabled protected domain.
- On the final step to conclude the continuous failover process, specify a failover type and select the Run PITR after recovering VMs checkbox option.
Select the option to run PITR after recovery.
- Different dialog window messages can appear announcing information about continuous failover and the PITR session.
Message: PITR session.
Message: Continuous rehydration.
Message: Force failover.
- A PITR session will automatically start after continuous failover VMs have been recovered. In this case, PITR is considered to be an integral step of the failover process and the domain should be rolled back to a point in time before exiting the PITR session.
The PITR session initiates automatically after the VMs have been recovered.
Note: While a PITR session is active, protection of the domain is temporarily suspended. It will not be possible to failover, failback or restore to any periods of time during which a PITR session was active. Therefore, it is recommended to not leave PITR sessions active longer than necessary. Once the PITR session is exited, all DR protection resumes normally.
Important: PITR following continuous failover is considered an integral part of the failover process. It is expected the domain will be rolled back to a point in time within the PITR window during the session. If the session is exited without performing a PITR rollback, all PITR data will be reset and it will no longer be possible to roll back to points in time from the original PITR window.