public:module:hyper-v:about_granular_restore
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
public:module:hyper-v:about_granular_restore [2019/09/20 15:05] ronnie.chan created |
public:module:hyper-v:about_granular_restore [2021/05/12 17:49] (current) ronnie.chan |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== About Granular Restore ====== | ====== About Granular Restore ====== | ||
| ---- | ---- | ||
| - | {{INLINETOC}} \\ | ||
| ===== Summary ===== | ===== Summary ===== | ||
| Line 29: | Line 28: | ||
| ^ Cons | **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. | **Slower Recovery** - As the entire guest VM has to be restored before you can access any of it’s file(s) or data, the restore time could be long if the guest VM size is large.\\ **Two Backup Sets and CloudBacko Pro Licenses 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 CloudBacko Pros licenses are required. | | ^ Cons | **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. | **Slower Recovery** - As the entire guest VM has to be restored before you can access any of it’s file(s) or data, the restore time could be long if the guest VM size is large.\\ **Two Backup Sets and CloudBacko Pro Licenses 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 CloudBacko Pros licenses are required. | | ||
| - | \\ | ||
| - | |||
| - | ===== Requirements ===== | ||
| - | ---- | ||
| - | <WRAP indent> | ||
| - | ==== Supported Backup Modules ==== | ||
| - | ---- | ||
| - | Granular Restore is supported on Hyper-V backup sets created and backed up using CloudBacko Pro installed on a Windows platform with the Granular Restore feature enabled on the backup set. | ||
| - | |||
| - | ==== License Requirements ==== | ||
| - | ---- | ||
| - | 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 ==== | ||
| - | ---- | ||
| - | 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 ==== | ||
| - | ---- | ||
| - | CloudBacko Pro must be installed on a 64 bit Windows machine as libraries for Granular only supports 64 bit Windows operating system. CloudBacko Pro must be installed on the following Windows Operating Systems: | ||
| - | | Windows 2012 | Windows 2012 R2 | Windows 2016 | | ||
| - | | Windows 8 | Windows 8.1 | Windows 10 | | ||
| - | |||
| - | ==== Temporary Directory Requirement ==== | ||
| - | ---- | ||
| - | For Hyper-V 2008 and 2012 in both Non-Cluster and Cluster environment, the temporary directory __must be__ set to a local drive. | ||
| - | |||
| - | For Hyper-V 2016 or above in a Non-Cluster environment, the temporary directory can be set to a local drive, network drive or a cluster storage. | ||
| - | |||
| - | For Hyper-V 2016 or above in a Cluster environment, the temporary directory must be set to a network drive or cluster storage accessible to all cluster members. | ||
| - | |||
| - | The temporary directory should have at least the same available size as the guest VM to be restored. | ||
| - | |||
| - | ==== Available Spare Drive Letter ==== | ||
| - | ---- | ||
| - | One spare drive letter must be available on the Windows machine for the Granular Restore process, as the VHD virtual disk is mounted on Windows as a logical drive. CloudBacko Pro will automatically take the next available drive letter in alphabetical order for the mounted virtual disk. | ||
| - | <WRAP info> | ||
| - | 1. The Windows drive letters A, B, and C are not used by Granular Restore. \\ | ||
| - | 2. The Granular Restore assigned drive letter(s) will be released once you exit from CloudBacko Pro UI. | ||
| - | </WRAP> | ||
| - | |||
| - | ==== Network Requirements ==== | ||
| - | ---- | ||
| - | Recommended minimum network speed is at least 100Mbps download speed. | ||
| - | |||
| - | The network bandwidth requirements will increase in proportion to the size of the guest VM and or the incremental delta chain length to ensure optimal performance. Working with limited network bandwidth may severely affect the Granular Restore performance. | ||
| - | |||
| - | You can use an online network speed test website (e.g. www.speedtest.net) to get an idea of the actual bandwidth of the machine. | ||
| - | |||
| - | ==== Other Dependencies ==== | ||
| - | ---- | ||
| - | The following dependencies are required for restore and therefore they are verified by CloudBacko Pro only when a Granular Restore is performed. Absence of these dependencies will not affect the backup job but would cause the Granular Restore to fail. | ||
| - | * Microsoft Visual C++ 2015 Redistributable (x86) / (x64) \\ [[https://www.microsoft.com/en-us/download/details.aspx?id=48145]] | ||
| - | * Update for Universal C Runtime in Windows \\ [[https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows]] | ||
| - | |||
| - | ==== Permissions ==== | ||
| - | ---- | ||
| - | The Windows login account used for installation and operation of the CloudBacko Pro client machine requires Administrator privileges. | ||
| - | |||
| - | <WRAP info> | ||
| - | **Recommendation** - It is recommended that a local destination is added to the backup set for faster Granular Restore. Since Granular Restore of large guest VM from cloud storage over the internet can be slow depending on network bandwidth and CBS server load. | ||
| - | </WRAP> | ||
| - | |||
| - | </WRAP> | ||
| - | |||
| - | \\ | ||
| - | |||
| - | ===== Limitations ===== | ||
| - | ---- | ||
| - | |||
| - | 1. Granular restore does not support the mounting of virtual disks, if the disk itself is encrypted, for example using Windows Bitlocker or other third party security features. | ||
| - | |||
| - | 2. If any folders or files on a virtual disk are encrypted these files/folder cannot be restored. For example, if the “Encrypt contents to secure data” is selected in Advanced attributes. | ||
| - | |||
| - | 3. The mounting of Linux/Unix file systems from virtual disk file is currently not available due to limitations of the file system drivers. | ||
| - | |||
| - | 4. Granular restore can only be performed on one guest VM at a time with no limitation on number of virtual disk than can be mounted on the guest VM, however, only files/ folders from one virtual disk can be retrieved at a time. | ||
| - | |||
| - | 5. Windows User Account Control (UAC) must be disabled to apply granular restore. | ||
public/module/hyper-v/about_granular_restore.1568963111.txt.gz · Last modified: 2019/09/20 15:05 by ronnie.chan
Page Tools
