User Tools

Site Tools


public:vmware

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
public:vmware [2019/08/21 15:35]
ronnie.chan [Backup Client Computer Requirements]
public:vmware [2022/11/28 11:11] (current)
kirk.lim Last modified: 2019/08/26 12:03 by ronnie.chan
Line 1: Line 1:
 ====== VMware Backup Set ====== ====== VMware Backup Set ======
 +
 +Last modified: 2019/08/26 (Note: Content written for AhsayCBS v7+v8, and may generally apply to latest product release)
  
 AhsayOBM allows you to back up individual Guest virtual machines (VMs) on your VMware hosts with our VMware Backup Set. VMware Guest VM backup module of AhsayOBM provides you with a set of tools to perform hot backup of your running VMs in VMware environment. ​ AhsayOBM allows you to back up individual Guest virtual machines (VMs) on your VMware hosts with our VMware Backup Set. VMware Guest VM backup module of AhsayOBM provides you with a set of tools to perform hot backup of your running VMs in VMware environment. ​
Line 26: Line 28:
 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. ​ 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_2b.png?640}}+{{public:ahsay_wiki_module_vmware_system_architecture_2.png?800}}
  
 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 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). ​
Line 256: Line 258:
 The VMware vSphere Storage APIs, which are essential for VDDK backup mode, are included with the VMware vSphere Enterprise Standard, Enterprise and Enterprise Plus Edition. Ensure that the license requirement is met. The VMware vSphere Storage APIs, which are essential for VDDK backup mode, are included with the VMware vSphere Enterprise Standard, Enterprise and Enterprise Plus Edition. Ensure that the license requirement is met.
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​code>​ +
-NOTE+
 For VM on free version of ESXi without a Run Direct backup destination,​ backup will be performed in non-VDDK mode.  For VM on free version of ESXi without a Run Direct backup destination,​ backup will be performed in non-VDDK mode. 
 For VM on free version of ESXi with a Run Direct backup destination,​ the following error message would be returned during a backup: For VM on free version of ESXi with a Run Direct backup destination,​ the following error message would be returned during a backup:
 ”Skip backing up Virtual Machine “name"​. Reason = "Run Direct is only support to VDDK backup mode"​”. ”Skip backing up Virtual Machine “name"​. Reason = "Run Direct is only support to VDDK backup mode"​”.
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
Line 269: Line 268:
   * The VM must be hardware version 7 or later.   * The VM must be hardware version 7 or later.
   * The VM must have zero (0) snapshots when CBT is enabled.   * The VM must have zero (0) snapshots when CBT is enabled.
-  * The virtual disk must be located on a VMFS volume backed by SAN, iSCSI, local disk, or a NFS volume. \\ <​WRAP ​prewrap>​ +  * The virtual disk must be located on a VMFS volume backed by SAN, iSCSI, local disk, or a NFS volume. \\ <​WRAP ​info> NOTE 
-<code> NOTE +For virtual disk on VMFS, the initial backup (e.g. full file backup) will be of size similar to used size; while for virtual disk on NFS, the initial backup will be of the provisioned size.
-For virtual disk on VMFS, the initial backup (e.g. full file backup) will be of size similar to used size; while for virtual disk on NFS, the initial backup will be of the provisioned size. </​code>​+
 </​WRAP>​ </​WRAP>​
   * RDM (Raw Device Mapping) in physical compatibility mode is not supported.   * RDM (Raw Device Mapping) in physical compatibility mode is not supported.
-  * The virtual disk must not be in Independent Mode (Persistent or Nonpersistent). \\ <​WRAP ​prewrap> +  * The virtual disk must not be in Independent Mode (Persistent or Nonpersistent). \\ <​WRAP ​info
-<​code>​ NOTE +Once the backup job executed on a VM with change block tracking option enabled by the VDDK, please do not turn off this option in the VM for consequent backup jobs. If you need to disable this option, you are suggested to create a new backup set with this option disabled. </​WRAP>​
-Once the backup job executed on a VM with change block tracking option enabled by the VDDK, please do not turn off this option in the VM for consequent backup jobs. If you need to disable this option, you are suggested to create a new backup set with this option disabled. ​</​code>​</​WRAP>​+
  
 == VMware Snapshot == == VMware Snapshot ==
public/vmware.1566372932.txt.gz · Last modified: 2019/08/21 15:35 by ronnie.chan

Page Tools