Restore Point not Shown

Upon a Restore operation of a VPG or VM, there may be cases in which a Restore Point is not displayed in the Restore Wizard.

A Restore Point will not be displayed in the list of available Restore Points for a VM or a VPG in the following cases:

Description Solution

The Restore Point has expired, based on the configured Retention Policy.

 

Select another Restore Point to Restore from, that best fits your needs.

Note: In this case, the Retention Set may still be present in the Repository, if other Retention sets are depending on it.

The Restore Point does not exist:

• In case a Retention process has failed, its Retention set will be missing.
• If a Retention Process completed as Partial, the Retention set is not considered as a valid Restore Point, and therefore it will not be displayed.
• In case a VM was added to the VPG post Restore point creation.
Select another Restore Point to Restore from, that best fits your needs.

When a Retention process is still running, the Restore points for that VPG will not be displayed.

Wait for the Retention process to complete before launching the Restore Wizard. Upon successful completion of the Retention process, the Restore Point will be available for selection.

There is an on-going re-attach process of an LTR Repository.

In case a non-empty Repository is connected to the ZVM, it will take some time for the valid (successfully completed) Retention Sets to be loaded into the ZVM, and become available for Restore.
• Track the re-attach process in “Setup tab”-> “Repositories”. The “Restore Points” column should imply on the process’ progress.
• Upon completion of the re-attach process, launch the Restore Wizard and select the desired Restore point to restore from.

Re-attach process for an LTR Repository seems to be completed but I still cannot select the Restore Point.

The re-attach process will update only valid Retention sets in a Repository.

Valid Retention sets are considered as the ones conducted from a successfully completed Retention processes. If a Retention set was not loaded into to the ZVM, it can be because:

• The Retention Process failed and therefore no Retention set exists.
• The Retention Process completed as partial . Partial Retention sets cannot be leveraged for Restore.
• A Retention process is still running, or completed successfully after the re-attach process has been completed.

A Retention process is still running, or completed successfully after the re-attach process has been completed.

If the Repository is attached to multiple ZVMs at the same time, it might be that:

• There is a running Retention process (in another site) that was not yet completed, hence the Retention Set is not yet available for Restore.
• A Retention Process successfully completed in another site, but ended post re-attach process completion.

To be able to support these cases, periodical synchronization of the Repository’s content should be enabled.

Please contact Zerto Support to enable this capability.