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)