Differences

This shows you the differences between two versions of the page.

--- public:vmware [2019/08/16 14:33]
ronnie.chan
+++ public:vmware [2019/08/16 14:47]
ronnie.chan
@@ Line 22: / Line 22: @@
 When a Run Direct restore is performed, the backup destination is mounted as an NFS datastore from the VMware host, where the VM is run directly from the backup files.
-{{public:ahsay_wiki_module_vmware_system_architecture_2?640.png}}
+{{public:ahsay_wiki_module_vmware_system_architecture_2b.png?640}}
 The backup destination can either be the AhsayCBS server or a local drive that can connect with AhsayOBM. Initiating a Run Direct from the AhsayCBS (also known as agentless restore) will trigger a connection directly with the VMWare host (ESXi server and the direction shown in orange indicator below), while initiating the same action on the AhsayOBM requires the connection to route through the OBM (shown in green indication below).
 The restored virtual machine, at this stage (e.g. before the restore is finalized) is in a read-only state to preserve its integrity.  All changes made to the virtual disks (e.g. operation within the guest virtual machine) are stored separately in transaction logs stored on the NFS datastore or the original datastore, depending on the setting selected. These changes are discarded when Run Direct is stopped, where the restored VM will be removed and all changes will be discarded, or the changes will be consolidated with the original virtual machine data when the restore is finalized.
+The restored virtual machine, at this stage (e.g. before the restore is finalized) is in a read-only state to preserve its integrity.  All changes made to the virtual disks (e.g. operation within the guest virtual machine) are stored separately in transaction logs stored on the NFS datastore or the original datastore, depending on the setting selected. These changes are discarded when Run Direct is stopped, where the restored VM will be removed and all changes will be discarded, or the changes will be consolidated with the original virtual machine data when the restore is finalized.
+==== Settings Differences between Run Direct and Non-Run Direct Backup Set on VMware ====
+^      ^ Run Direct Backup Set       ^ Non-Run Direct Backup Set          ^
+| Encryption    | No     | Yes        |
+| Compression    | No     | Yes        |
+| VDDK (CBT)    | Yes     | Yes        |
+| AhsayCBS    | Yes     | Yes        |
+| Local Destination    | Yes     | Yes        |
+| Cloud Destination    | No     | Yes        |
+==== Finalizing a VM Recovery (Migrating VM to permanent location) ====
+To finalize recovery of a VM, you will still need to migrate it to a permanent location on the VMware host.  The following steps are taken when you finalize a Run Direct restore:
+=== 1). VMware Snapshot ===
+A VMware snapshot is created for the VM
+=== 2). Copying Files ===
+Backup files from the NFS datastore are copied to the production datastore on the VMware host.
+=== 3). Copying Changes ===
+Changes made to the VM after the snapshot creation are moved to the new location.
+=== 4). Data Consolidation ===
+The VM is temporarily suspended to consolidate the changes made after the snapshot creation.
+=== 5). Resume VM ===
+After all changes are consolidated, the VM is resumed.
+=== 6). Dismount NFS datastore ===
+The NFS datastore is dismounted.
+<WRAP prewrap>
+<code>
+NOTE
+For vCenter VM backup set, provided that the vMotion feature of the vCenter set is working properly, the VM will not be suspended during the data consolidation.
+</code>
+</WRAP>
+===== Backup Mode =====
+There are two backup modes available for VM backup:
+==== VDDK Backup Mode ====
+For VM on VMware host on Enterprise Standard, Enterprise and Enterprise Plus Edition, backup is performed in VDDK mode. Backup in VDDK mode produces a backup chain that consists of a full VDDK file and a set of VDDK incremental files.
+  * During the first backup, full files (*.F.vddk) are created in the backup destination.
+  * During subsequent backup, Changed Block Tracking (CBT) - a VMware [[https://kb.vmware.com/kb/1020128|native feature]] is employed, to identify disk sectors altered since the last backup.  Altered blocks are saved as incremental VDDK file (*.I.vddk) in the backup chain.
+During a subsequent backup in VDDK mode, AhsayOBM queries CBT through VADP (vSphere APIs for Data Protection) to request for transmission of all altered blocks since the last backup.
+As there is no need to stream the VM files to the Backup Client Computer for delta generation, backup in VDDK mode will greatly enhance the speed of subsequent backup.
+^ Pro      ^ Con       ^
+| Faster backup speed for subsequent backups compared to non-VDDK backup, as a result of backing up only the used size of your VM instead of the entire machine to enhance backup efficiency. This also helps with minimizing the storage size requirement and saving storage cost.    | Require paid license, i.e. VMware Essentials License for usage of vSphere API.     |
 ===== Documentation =====

User Tools

Site Tools

Differences

Page Tools