Restore
Overview
Restore is the feature group used to recover a VM from an existing restore point. In Version 1.5, users work in the Restore tab and can choose one of these actions:
- Restore
- Restore Keep
- Instant Recovery
Prerequisites
- The tenant has Backup Instance by Veeam service activated.
- The user is logged in to the Unify Portal.
- The user has permissions to perform restore.
- The instance belongs to the current VPC and is within the user's allowed scope.
- The instance has at least one available restore point.
- The infrastructure has enough resources to perform the restore, especially for Restore Keep and Instant Recovery.
Restore screen
Purpose
Shows the instances that can be restored and provides restore actions for each eligible instance.
How to use
- Open the Restore tab on the Unify Portal.
- Find the instance to restore.
- Check the actions available for the instance.
- Choose the action that fits the recovery need.
- Pick a restore point and configure the options as instructed on the screen.
Notes
- Only instances with available restore points can be restored.
- If an instance does not meet the conditions, the restore action may be hidden or disabled.
- The Restore tab does not support filter or search in Version 1.5.
- Users can only pick a restore point that belongs to the specific instance being operated on.
- Restore is an operation that can affect data; review the restore point and options carefully before confirming.
Restore
Purpose
Restore over the current instance from one of its own restore points. Use this action when you want to roll the instance back to the backup state and accept overwriting the current state.
Steps
- Open the Restore tab.
- Find the instance to restore.
- Click the Restore action.
- The portal opens the Instance Restore popup.
- Verify Instance Name is shown as read-only.
- Pick a restore point from the Restore point list.
- Configure Advanced settings if needed:
- Quick rollback (restore changed blocks only)
- Power on instance after restoring
- Click Restore Instance.
- Read the warning about overwriting the current instance.
- Confirm the restore action.
Fields to select
| Field | Required | Notes |
|---|---|---|
| Instance Name | Yes | Shows the current instance, not editable |
| Restore point list | Yes | Pick an available restore point of the instance |
| Quick rollback | No | Restores only changed blocks when enabled |
| Power on instance after restoring | No | Powers on the instance after restore when enabled |
Result after restore
- The current instance is restored to the selected restore point's state.
- Current data or state of the instance may be overwritten.
- Existing restore points are not changed.
- If Power on instance after restoring is enabled, the system powers on the instance after restore per deployment design.
Notes
- Do not use this action if you need to keep the current instance for comparison or manual rollback.
- If you want to create a new VM from the restore point, use Restore Keep.
- If you need to launch a VM quickly to recover from an incident, use Instant Recovery.
Restore Keep
Purpose
Restore to a new VM from a restore point of the current instance, without overwriting or changing the source VM.
Steps
- Open the Restore tab.
- Find the source instance to restore.
- Click the Restore Keep action.
- The portal opens the Restore keep instance from point popup.
- Enter Name for the new VM.
- Pick a restore point from the Restore point list.
- Configure Advanced settings if needed:
- Power on instance after restoring
- Click Restore Instance.
- Read the warning or final confirmation.
- Confirm the restore action.
Fields to enter
| Field | Required | Notes |
|---|---|---|
| Name | Yes | Name of the new VM created from the restore point |
| Restore point list | Yes | Pick an available restore point of the source instance |
| Power on instance after restoring | No | Powers on the new VM after restore when enabled |
Result after restore
- A new VM is created from the selected restore point.
- The source VM is not overwritten or changed by Restore Keep.
- Existing restore points are not changed.
- If Power on instance after restoring is enabled, the system powers on the new VM after restore per deployment design.
Notes
- The new VM name must be valid and not conflict with system rules.
- Restore Keep requires enough infrastructure resources to create the new VM.
- Restore Keep does not support source VMs that have been deleted in Version 1.5.
- If infrastructure resources are insufficient, the action may be blocked beforehand or fail during restore.
Instant Recovery
Purpose
Quickly launch a new VM from a restore point to bring the system back online in the shortest time.
Steps
- Open the Restore tab.
- Find the instance to recover quickly.
- Click the Instant Recovery action.
- The portal opens the Restore instance by Instant Recovery popup.
- Pick an available restore point.
- Keep Restore Mode as Restore to the new instance.
- Enter or check New instance name.
- Choose Restore VM tags if needed.
- Click Restore Instance.
- Read the confirmation popup.
- Type the exact new instance name if the portal asks for confirmation.
- Click Restore New Instance.
- Track the session in the Instant Recovery tab.
Fields to enter
| Field | Required | Notes |
|---|---|---|
| Restore Point | Yes | Pick exactly one available restore point |
| Restore Mode | Yes | This version supports only Restore to the new instance |
| New instance name | Yes | Name of the new VM for instant recovery |
| Restore VM tags | No | Restores the VM tags from the restore point when enabled |
| Confirmation phrase | Yes when confirming | Type the exact new instance name to confirm |
Result after instant recovery
- A new VM is created from the restore point via the Instant Recovery mechanism.
- Users can access, check, or use the VM after instant recovery succeeds.
- The system creates an Instant Recovery session shown in the Instant Recovery tab.
- The restore point is not changed by the instant recovery action.
Actions after instant recovery
- Migrate To Production: convert the temporary session into a production VM for long-term use.
- Cancel: discard the session and remove the VM created by Instant Recovery if the session has not been migrated.
Notes
- Instant Recovery in Version 1.5 supports only Restore to the new instance.
- The VPC needs enough quota or resources to create a new instance.
- There must not be a conflicting active Instant Recovery session for the same instance.
- If you need to keep the instance after Instant Recovery, use Migrate To Production rather than Cancel.
Quick comparison of restore actions
| Action | When to use | Effect on current VM | Main outcome |
|---|---|---|---|
| Restore | You want to roll the current VM back to a restore point | Yes, overwrites current state | Current VM is restored |
| Restore Keep | You want a new VM and keep the current VM intact | No | A new VM is created from the restore point |
| Instant Recovery | You need to launch a VM quickly to handle an incident | Does not overwrite the current VM | A new VM is launched quickly from the restore point |
Common errors
| Situation | Resolution |
|---|---|
| Cannot see the instance in the Restore tab | Check the instance has an available restore point and belongs to the correct VPC |
| Restore action is disabled | Check restore permissions, instance status, and available restore points |
| Cannot click the restore confirm button | Check that a valid restore point is selected and all required fields are filled |
| Restore Keep fails | Check the new VM name and available resources |
| Instant Recovery conflict | Check the new VM name and any active Instant Recovery session |
| Restore takes too long to finish | Track the task status, or contact support if the task errors out or times out |