User Tools

Site Tools


public:granular_restore

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:granular_restore [2019/08/21 15:16]
ronnie.chan [What is Granular Restore Technology]
public:granular_restore [2022/11/30 14:31] (current)
kirk.lim Last modified: 2019/08/21 15:18 by ronnie.chan
Line 1: Line 1:
 ====== Granular Restore for VMware / Hyper-V ===== ====== Granular Restore for VMware / Hyper-V =====
  
 +Last modified: 2019/08/21 (Note: Content written for AhsayCBS v7+v8, and still generally apply to latest product release)
  
-==== What is Granular Restore Technology ====+===== What is Granular Restore Technology ​=====
 AhsayOBM granular restore technology enables the recovery of individual files from a guest VM without booting up or restoring the whole guest VM first. AhsayOBM granular restore technology enables the recovery of individual files from a guest VM without booting up or restoring the whole guest VM first.
  
Line 13: Line 14:
 </​WRAP>​ </​WRAP>​
  
-==== How does Granular Restore work ====+===== How does Granular Restore work =====
  
 {{public:​ahsay_wiki_module_vmware_granular_restore.png?​800}} {{public:​ahsay_wiki_module_vmware_granular_restore.png?​800}}
  
-==== Benefits of using Granular Restore ====+====Granular ​vs Traditional ​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. 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.
Line 23: Line 24:
 <WRAP indent> <WRAP indent>
  
-=== Granular Restore ===+==== Granular Restore ​====
 ^ Pro                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            ^ Con                                                                                                                                                                                                                                       ^ ^ 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. ​ | | **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 ===+==== 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. 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.
  
Line 34: Line 35:
 </​WRAP>​ </​WRAP>​
  
-==== Requirements ====  ​+===== Requirements ​=====  ​
  
 <WRAP indent> <WRAP indent>
Line 43: Line 44:
 An OpenDirect / Granular restore add-on module license is required per backup set for this feature to work. Contact your backup service provider for more details. An OpenDirect / Granular restore add-on module license is required per backup set for this feature to work. Contact your backup service provider for more details.
  
-=== Backup Quota Storage ===+==== Backup Quota Storage ===
 As compression is not enabled for Granular backup sets, to optimize restore performance,​ the storage quota required will be higher than non-Granular backup sets. Contact your backup service provider for details. As compression is not enabled for Granular backup sets, to optimize restore performance,​ the storage quota required will be higher than non-Granular backup sets. Contact your backup service provider for details.
  
-=== Operating System === +==== Operating System ​==== 
-AhsayOBM must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system for VMware ESXi/​VCenter. AhsayOBM must be installed on the following Windows Operating Systems: +AhsayOBM must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system for VMware ESXi/​VCenter. AhsayOBM must be installed on the following
-| Windows 2008 R2 SP1 or above | Windows 2012 | Windows 2012 R2 +Windows Operating Systems ​^ 
-| Windows 2016 | Windows 7 SP1 or above | Windows 8 | +| Windows 2008 R2 SP1 (minimum) ​
-| Windows 8.1 | Windows 10 | |+| Windows 7 SP1 (minimum) ​|
  
-=== Temporary Directory Requirement ===+==== Temporary Directory Requirement ​====
 Temporary Directory Folder should have at least the same available size as the guest VM to be restored and should be located on a local drive to ensure optimal performance. Temporary Directory Folder should have at least the same available size as the guest VM to be restored and should be located on a local drive to ensure optimal performance.
  
-=== Available Spare Drive Letter ===+==== Available Spare Drive Letter ​====
 One spare drive letter must be available on the Windows machine for the granular restore process, as the VDDK virtual disk is mounted on Windows as a logical drive. AhsayOBM will automatically take the next available drive letter in alphabetical order for the mounted virtual disk. One spare drive letter must be available on the Windows machine for the granular restore process, as the VDDK virtual disk is mounted on Windows as a logical drive. AhsayOBM will automatically take the next available drive letter in alphabetical order for the mounted virtual disk.
  
-<​WRAP ​prewrap> +<​WRAP ​info>
-<​code>​ +
-NOTE+
 The Windows drive letters A, B, and C are not used by granular restore. The Windows drive letters A, B, and C are not used by granular restore.
 The granular restore assigned drive letter(s) will be released once you exit from AhsayOBM UI.  The granular restore assigned drive letter(s) will be released once you exit from AhsayOBM UI. 
-</​code>​ 
 </​WRAP>​ </​WRAP>​
  
-=== Network Requirements ===+==== Network Requirements ​====
 Recommended minimum network speed is at least 100Mbps download speed. ​ Recommended minimum network speed is at least 100Mbps download speed. ​
  
Line 72: Line 70:
 You can use an online network speed test website (e.g. [[http://​www.speedtest.net]]) to get an idea of the actual bandwidth of the machine. ​ You can use an online network speed test website (e.g. [[http://​www.speedtest.net]]) to get an idea of the actual bandwidth of the machine. ​
  
-=== Permissions ===+==== Permissions ​====
   * The Windows login account used for installation and operation of the AhsayOBM client machine requires Administrator privileges. ​   * The Windows login account used for installation and operation of the AhsayOBM client machine requires Administrator privileges. ​
   * For Granular Restore, Windows User Account Control (UAC) must be disabled.   * For Granular Restore, Windows User Account Control (UAC) must be disabled.
  
-=== Other Dependencies ===+==== Other Dependencies ​====
 The following dependencies are restore related and therefore they will be checked by AhsayOBM only when granular restore is performed. Absence of these elements will not affect the backup job but would cause the restore to fail.  The following dependencies are restore related and therefore they will be checked by AhsayOBM only when granular restore is performed. Absence of these elements will not affect the backup job but would cause the restore to fail. 
  
public/granular_restore.1566371761.txt.gz · Last modified: 2019/08/21 15:16 by ronnie.chan

Page Tools