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/16 16:40]
ronnie.chan [Table]
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 64: Line 66:
 The NFS datastore is dismounted. The NFS datastore is dismounted.
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​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. 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>​ </​WRAP>​
  
Line 148: Line 147:
 [[https://​kb.vmware.com/​s/​article/​2131180]] [[https://​kb.vmware.com/​s/​article/​2131180]]
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​code>​ +
-NOTE+
 Ports 443 and 902 are default ports for VMware. Ports 443 and 902 are default ports for VMware.
 If these have been changed from the default in your VMware environment,​ the firewall requirements will change accordingly. If these have been changed from the default in your VMware environment,​ the firewall requirements will change accordingly.
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
Line 165: Line 161:
 VMware Tools are used to quiesce VMs prior to backing them up. To create consistent backup for your VMs on Windows platforms, ensure that VMware Tools are installed, and up-to-date on all VMs to be backup. ​ VMware Tools are used to quiesce VMs prior to backing them up. To create consistent backup for your VMs on Windows platforms, ensure that VMware Tools are installed, and up-to-date on all VMs to be backup. ​
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​code>​ +
-NOTE+
 Quiescing is a process that ensures that the disk data is in a state suitable for backups to reduce the possibility of data corruption upon restore. This is especially important for transactional-based applications running on VMs like MS SQL Server.  ​ Quiescing is a process that ensures that the disk data is in a state suitable for backups to reduce the possibility of data corruption upon restore. This is especially important for transactional-based applications running on VMs like MS SQL Server.  ​
 There are different types of quiescing mechanisms, according to the guest operating systems (e.g. Crash-consistent,​ File-system-consistent and Application-consist quiescing). There are different types of quiescing mechanisms, according to the guest operating systems (e.g. Crash-consistent,​ File-system-consistent and Application-consist quiescing).
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
Line 206: Line 199:
   * To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to [[public:​8014_faq:​suggestion_on_antivirus_exclusions|this article]] for the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list.   * To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus software, refer to [[public:​8014_faq:​suggestion_on_antivirus_exclusions|this article]] for the list of processes and directory paths that should be added to all antivirus software white-list / exclusion list.
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​code>​ +
-NOTE+
 For AhsayOBM version 8.1 or above, the bJW.exe process is automatically added to Windows Defender exclusion list for Windows 10 and 2016, during installation / upgrade via installer or upgrade via AUA.  For AhsayOBM version 8.1 or above, the bJW.exe process is automatically added to Windows Defender exclusion list for Windows 10 and 2016, during installation / upgrade via installer or upgrade via AUA. 
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
Line 222: Line 212:
 [[https://​kb.vmware.com/​s/​article/​2131180]] [[https://​kb.vmware.com/​s/​article/​2131180]]
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​code>​ +
-NOTE+
 Ports 443 and 902 are default ports for VMware. Ports 443 and 902 are default ports for VMware.
 If these have been changed from the default in your VMware environment,​ the firewall requirements will change accordingly. If these have been changed from the default in your VMware environment,​ the firewall requirements will change accordingly.
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
Line 233: Line 220:
 For Backup Client Computer running on Linux operating system platform, Graphical User Interface (GUI) environment (e.g. GOME or KDE) must be installed. For Backup Client Computer running on Linux operating system platform, Graphical User Interface (GUI) environment (e.g. GOME or KDE) must be installed.
  
-<​WRAP ​prewrap> +<​WRAP ​important>
-<​code>​ +
-IMPORTANT+
 Run Direct restore, VDDK backup mode and Granular Restore is not supported for Backup Client Computer on Linux / Mac OS X platforms. Run Direct restore, VDDK backup mode and Granular Restore is not supported for Backup Client Computer on Linux / Mac OS X platforms.
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
Line 245: Line 229:
 **(Total File Size * Delta Ratio) * number of backup destinations = Maximum Free Space Required** **(Total File Size * Delta Ratio) * number of backup destinations = Maximum Free Space Required**
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​code>​ +
-NOTE+
 The calculation is based on the current guest VM size, and it does not take into account guest VM growth over time.  It is recommended for fast growing guest VM the maximum free space required should be reviewed on a regular basis to avoid potential backup problems. The calculation is based on the current guest VM size, and it does not take into account guest VM growth over time.  It is recommended for fast growing guest VM the maximum free space required should be reviewed on a regular basis to avoid potential backup problems.
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
Line 277: 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 290: 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 ==
Line 403: Line 379:
  
 ===== Granular Restore Technology ===== ===== Granular Restore Technology =====
 +AhsayOBM [[public:​granular_restore|granular restore technology]] enables the recovery of individual files from a guest VM without booting up or restoring the whole guest VM first. [[public:​granular_restore|Click here]] to read the details.
  
-==== What is Granular Restore Technology ==== +<​WRAP ​important>
-AhsayOBM granular restore technology enables the recovery of individual files from a guest VM without booting up or restoring the whole guest VM first. +
- +
-Granular restore is one of the available restore options for VMware ESXi/​vCenter backup sets from AhsayOBM v8.1.0.0 or above. AhsayOBM makes use of granular restore technology to enable a file level restore from a virtual disk file (VDDK) of guest VM backup possible. It is particularly useful if you only need to restore individual file(s) from a guest VM which would normally take a long time to restore and then startup before you can gain access to the files on the virtual disks. Granular restore gives you a fast and convenient way to recover individual files on a guest VM. +
- +
-During the granular restore process, the virtual disks of the guest VM can be mounted on the Windows machine as a local drive. This will allow the individual files on the virtual disks to be viewed via the file explorer within AhsayOBM or from the Windows File Explorer on the Windows machine you are performing the restore on, without having to restore the entire virtual machine. Granular restore can only mount virtual disks if the guest VM is running on a Windows Platform and it is supported for all backup destinations,​ i.e. AhsayCBS, Cloud storage, or Local/​Network drives. ​ The mounting of Linux/Unix file systems from virtual disk file is currently not available due to limitations of the file system drivers.  +
- +
-<​WRAP ​prewrap> +
-<​code>​ +
-IMPORTANT+
 Granular Restore requires an additional OpenDirect / Granular Restore add-on module license to work. Contact your backup service provider for further details. Granular Restore requires an additional OpenDirect / Granular Restore add-on module license to work. Contact your backup service provider for further details.
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
-==== How does Granular Restore work ==== 
- 
-{{public:​ahsay_wiki_module_vmware_granular_restore.png?​800}} 
- 
-==== Benefits of using Granular Restore ==== 
- 
-Granular restore allows you to quickly mount virtual disk(s) directly from the backup file of a guest VM, so that individual files from virtual disk(s) can be exposed via the file explorer on AhsayOBM, or to be copied from the file explorer on to a 64 bit Windows machine you are performing the restore. 
- 
-<WRAP indent> 
- 
-=== Granular Restore === 
-^ Pro                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            ^ Con                                                                                                                                                                                                                                       ^ 
-| **Restore of Entire Guest VM Not Required**\\ Compared to a traditional restore where you have to restore the entire guest VM first, before you can access any individual files/​folders,​ granular restore allows you to view and download individual files, without having to restore the entire guest VM first.\\ \\ **Ability to Restore Selected Files**\\ In some cases, you may only need to restore a few individual file(s) from the guest VM, therefore, granular restore gives you a fast, convenient, and flexible tool to restore selected file(s) from a guest VM quickly.\\ \\ **Only One Backup Set Required**\\ With traditional restore methods, if you wish to restore individual file(s) from a guest VM, you will have to create two different backup sets; a VMware guest VM backup set and a separate file backup set for the file(s) you wish to restore. You will require an additional AhsayOBM installation on the guest VM environment,​ with Granular Restore feature, only one backup set is required.\\ ​  * Fewer CAL (Client Access License) required - you will only need one AhsayOBM CAL to perform guest VM, Run Direct, and Granular restore. ​ \\   * Less storage space required - as you only need to provision storage for one backup set.\\ ​  * Less backup time required - As only one backup job needs to run. \\   * Less time spent on administration - As there are fewer backup sets to maintain. ​ | **No Encryption and Compression**\\ To ensure optimal restore performance,​ the backup of the guest VM will NOT be encrypted and compressed, therefore, you may have to take this factor in consideration when using this restore method. ​ | 
- 
-=== Traditional Restore === 
-The traditional restore method for guest VMs, restores the entire backup files to either the original VM location or another standby location. The files or data on the guest VM can only be accessed once the guest VM has been fully recovered and booted up. 
- 
-^ Pro                                                                                                                                                                                   ^ Con                                                                                                                                                                                                                                                                                                                                                                                                                                                  ^ 
-| **Backup with Compression and Encryption**\\ Guest VM is encrypted and compressed, therefore is in smaller file size, and encrypted before being uploaded to the backup destination. ​ | **Slower recovery**\\ As the entire guest VM has to be restored before you can access any of its file(s) or data, the restore time could be long if the guest VM size is large.\\ \\ **Two Backup Sets and CALs Required**\\ If you only wish to restore individual files from VM, two separate backup sets are required, one for the VM image and the other for the individual files, and therefore two CAL (client access licenses) are required. ​ | 
- 
- 
-</​WRAP>​ 
  
 ---- ----
public/vmware.1565944845.txt.gz · Last modified: 2019/08/16 16:40 by ronnie.chan

Page Tools