While entering PITR recovery session, domain must be in a consistent state (Remaining Background Data is 0, current RPO is close to 0 seconds). If the user tries to start PITR session while the domain is not in a consistent state, it will wait for the domain to become consistent and entering the PITR session might take longer than usual.
When PITR recovery session only refers to a part of all VMs protected in the domain, user should exit PITR recovery session as soon as possible, as JetDR currently cannot maintain consistency status of the VMs not undergoing PITR.
If the domain is restarted the PITR window will be reset. This could lead to extra Object Cloud and metaspace usage for the domain.
PITR supports rollback of the data in vDisks. It doesn’t rollback the VM configuration changes that happen across the PITR window. VM config changes discarded because of PITR, should be replayed by the admin after PITR session completes. (Example: VM config changes that have to be replayed are disk add, remove, detach and disk grow.)
When PITR is in progress, the HV tab will show some of the protected disks as orphan disks. This is a transient state and the disks move to initialized state after PITR procedure is complete. The issue will be fixed in the following releases. (JSTOOLS-366)
We encourage customers to enable PiT mode on the domain before adding any VMs to that domain, or add a new VM to the domain after enabling PiT mode. If a domain is already fully configured when PiT mode is enabled, we recommend checking whether PiT was able to gather some data by validating that a recovery point exists after starting a PiT recovery for any VM in the domain - no actual recovery required, but the selected VM would be temporarily shut down. In case there are no valid recovery points back in time, the workaround is to restart DRVA after exiting PiT recovery. (DRBC-8047)
There is a rare chance that PiTR recovery task would fail with a message "An unexpected error occurred on the remote system" with a distinction of "Unsupported or unrecognized SSL message". This is a temporary failure, and it is OK retry the operation. (DRBC-5902)