You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: source/adminguide/kvm_veeam.rst
+13-6Lines changed: 13 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -301,22 +301,29 @@ All restore-related operations are executed using the **service account configur
301
301
302
302
If the service account does not have access to the networks selected in the **Veeam restore wizard**, the restore operation may fail.
303
303
304
+
The plugin reconstructs the instance networking configuration using the metadata saved during backup. This ensures that the restored instance closely resembles the original instance configuration where possible.
305
+
304
306
Compute Offering Selection
305
307
~~~~~~~~~~~~~~~~~~~~~~~~~~
306
308
307
309
During restore, the CloudStack Veeam integration plugin determines an appropriate **compute offering** for the restored instance based on the compute characteristics stored in the backup metadata. This typically includes parameters such as CPU and memory.
308
310
309
311
The plugin attempts to match these characteristics with an available compute offering in the CloudStack environment. If an exact match is not found, the closest suitable compute offering may be selected.
310
312
311
-
Network and Volume Reconstruction
312
-
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
313
+
Network Reconstruction
314
+
~~~~~~~~~~~~~~~~~~~~~~
315
+
316
+
**Networks** are attached to the restored instance in the same order and configuration as recorded in the backup metadata.
317
+
318
+
If one or more original networks cannot be attached during restore (for example, due to permission or capacity constraints), the instance is created without those networks and the restore process continues. Administrators can manually attach the missing networks after restore. To better handle such scenarios, it is recommended to restore instances without powering them on immediately.
319
+
320
+
Volume Reconstruction
321
+
~~~~~~~~~~~~~~~~~~~~~
313
322
314
-
The plugin reconstructs the instance networking and storage configuration using the metadata saved during backup:
323
+
**Volumes** are created and restored from the backup data and then attached to the instance.
315
324
316
-
* **Networks** are attached to the restored instance in the same order and configuration as recorded in the backup metadata.
317
-
* **Volumes** are created and restored from the backup data and then attached to the instance.
325
+
Restored volumes are always assigned an available custom disk offering. If needed, administrators can manually change the disk offering after the restore operation completes.
318
326
319
-
This process ensures that the restored instance closely resembles the original instance configuration where possible.
0 commit comments