www.bobcloud.net
Ahsay Online Backup Manager v7
Microsoft Hyper-V Guest Virtual Machine
Backup & Restore Guide
Ahsay Systems Corporation Limited
19 November 2018
This is the original Ahsay manual
Depending on the service you have with us, some of the content won’t be applicable to you.
Note:
We don’t supply the following services, Open direct, Run Direct,or Run on Server on our
BOBcloud service. These are only provided on our System Provider service.
All accounts must be created on our reseller portal https://portal.data-stor.net
Any Ahsay professional services are provided by them and not us.
Definitions:
Our Desktop version is named ACB \ AhsayACB in this manual.
Our Server version is named OBM \ AhsayOBM in this manual.
The AhsayCBS Web Console is mapped to our own portal https://portal.data-stor.net
www.bobcloud.net
Copyright Notice
© 2018 Ahsay Systems Corporation Limited. All rights reserved.
The use and copying of this product is subject to a license agreement. Any other use is prohibited. No part of this publication
may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language in any form by any
means without prior written consent of Ahsay Systems Corporation Limited. Information in this manual is subject to change
without notice and does not represent a commitment on the part of the vendor, Ahsay Systems Corporation Limited does not
warrant that this document is error free. If you find any errors in this document, please report to Ahsay Systems Corporation
Limited in writing.
This product includes software developed by the Apache Software Foundation (http://www.apache.org/).
Trademarks
Ahsay, Ahsay Cloud Backup Suite, Ahsay Online Backup Suite, Ahsay Offsite Backup Server, Ahsay Online Backup Manager,
Ahsay A-Click Backup, Ahsay Replication Server, Ahsay BackupBox Firmware, Ahsay Universal Backup System, Ahsay NAS
Client Utility are trademarks of Ahsay Systems Corporation Limited.
Amazon S3 is registered trademark of Amazon Web Services, Inc. or its affiliates.
Apple and Mac OS X are registered trademarks of Apple Computer, Inc.
Dropbox is registered trademark of Dropbox Inc.
Google Cloud Storage and Google Drive are registered trademarks of Google Inc.
Lotus, Domino, Notes are registered trademark of IBM Corporation.
Microsoft, Windows, Microsoft Exchange Server, Microsoft SQL Server, Microsoft Hyper-V, Microsoft Azure, One Drive and
One Drive for Business are registered trademarks of Microsoft Corporation.
Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective
owners.
Oracle, Oracle 10g, Oracle 11g and MySQL are registered trademarks of Oracle Corporation.
Rackspace and OpenStack are registered trademarks of Rackspace US, Inc.
Red Hat, Red Hat Enterprise Linux, the Shadowman logo and JBoss are registered trademarks of Red Hat, Inc.
www.redhat.com in the U.S. and other countries. Linux is a registered trademark of Linus Torvalds.
ShadowProtect is registered trademark of StorageCraft Technology Corporation.
VMware, ESX, ESXi, vCenter are registered trademarks of VMware, Inc.
All other product names are registered trademarks of their respective owners.
Disclaimer
Ahsay Systems Corporation Limited will not have or accept any liability, obligation or responsibility whatsoever for any loss,
destruction or damage (including without limitation consequential loss, destruction or damage) however arising from or in
respect of any use or misuse of reliance on this document. By reading and following the instructions in this document, you
agree to accept unconditionally the terms of this Disclaimer and as they may be revised and/or amended from time to time by
Ahsay Systems Corporation Limited without prior notice to you.
www.bobcloud.net
Revision History
Date
Descriptions
Type of modification
31 May 2017
Added Ch. 4 Granular restore section, added
step in Create new backup set, added Granular
restore sub-section in the Restore section
New
20 Jun 2017
Updated Ch. 4, Ch. 9, Ch. 12, Updated all
granular screen shots
Modified
13 Jul 2017
Updated Ch. 4, Ch. 9, Ch. 12, Updated all
granular screen shots
Modified
6 October 2017
Updated Ch.2.4; Added CBT Requirement for
Ch.2.5; Added Windows Server 2016
Requirement for Ch.2.6; updated Limitations for
Ch.2.7; Updated Ch.4.1; Updated Ch.12; Added
note of restore using Windows File Explorer for
Ch.12; Added Ch.2.5 Hyper-V Backup Methods
New / Modified
7 Nov 2017
Modified Restore options for Ch.9; Modified
Requirements and Limitations for Ch.10.1;
Added Restore to Standby Hyper-V Host for
Ch.10.2; Modified sequence of restore option of
Non-Run Direct Restore for Ch.11
New / Modified
2 Feb 2018
Updated Ch. 2.7, Ch. 4, Ch. 6
Modified
9 May 2018
Updated Ch. 10, Ch. 11
Modified
8 June 2018
Updated Ch. 4, Ch. 6
Modified
19 July 2018
Added limitation 8 of disable replication for
Ch.2.8 Limitations
New
14 September 2018
Added requirement of Antivirus Exclusion for
Ch.2.3;
New
www.bobcloud.net
Table of Contents
1 Overview ..............................................................................................................1
What is this software?.......................................................................................................1
System Architecture..........................................................................................................1
2 Preparing for Backup and Restore....................................................................2
Hardware Requirement.....................................................................................................2
Software Requirement ......................................................................................................2
Antivirus Exclusion Requirement ......................................................................................2
AhsayOBM........................................................................................................................2
Hyper-V Server Requirement............................................................................................4
Hyper-V Backup Methods .................................................................................................9
VM Snapshot.........................................................................................................9
Saved State.........................................................................................................10
CBT Requirement ...........................................................................................................11
Windows Server 2016 Requirement ...............................................................................12
RCT Requirement ...............................................................................................12
Guest VM Dependencies Requirements.............................................................12
Limitations.......................................................................................................................13
3 Run Direct ..........................................................................................................14
4 Granular Restore Technology..........................................................................16
What is Granular Restore Technology?..........................................................................16
How does Granular Restore work?.................................................................................17
Benefits of using Granular Restore.................................................................................17
Requirements..................................................................................................................19
Supported Backup Modules ................................................................................19
License Requirements ........................................................................................19
Backup Quota Storage........................................................................................19
Operating System ...............................................................................................19
Temporary Directory Requirement......................................................................19
Available Spare Drive Letter ...............................................................................19
Network Requirements........................................................................................20
Other Dependencies ...........................................................................................20
Permissions.........................................................................................................20
5 Starting AhsayOBM ..........................................................................................21
Login to AhsayOBM ........................................................................................................21
6 Creating a Hyper-V Backup Set .......................................................................22
Non-Cluster Environment................................................................................................22
www.bobcloud.net
Run Direct Backup Set........................................................................................22
Non Run Direct Backup Set ................................................................................30
Cluster Environment .......................................................................................................37
Requirements......................................................................................................37
Run Direct Backup Set........................................................................................37
Non Run Direct Backup Set ................................................................................45
7 Overview on the Backup Process ...................................................................52
8 Running Backup Jobs ......................................................................................53
Login to AhsayOBM ........................................................................................................53
Start a Manual Backup....................................................................................................53
Configure Backup Schedule for Automated Backup.......................................................55
9 Restoring Hyper-V Guest Virtual Machines....................................................56
Restore Options ..............................................................................................................56
10 Run Direct Restore............................................................................................58
Requirements and Limitations ........................................................................................58
Original Hyper-V Host .....................................................................................................61
Start up a guest VM from Backup Destination without Auto Migration Enabled .61
Migrate Virtual Machine (Permanently Restore) .................................................65
Stop Run Direct Virtual Machines .......................................................................67
Start up a guest VM from Backup Destination with Auto Migration Enabled ......68
Different (Standby) Hyper-V Host ...................................................................................72
Start up a guest VM from Backup Destination without Auto Migration Enabled .72
Migrate Virtual Machine (Permanently Restore) .................................................76
Stop Run Direct Virtual Machines .......................................................................79
Start up a guest VM from Backup Destination with Auto Migration Enabled ......80
11 Non-Run Direct Restore ...................................................................................84
Original Hyper-V Host .....................................................................................................84
Restore of Guest VM to the Original Hyper-V Host (Original Location) ..............84
Restore of Guest VM to the Original Hyper-V Host (Alternate Location) ............88
Different (Standby) Hyper-V Host ...................................................................................91
Restore of a Guest VM to a Different (Standby) Hyper-V Host...........................91
Individual Virtual Disk Restore ........................................................................................96
Restore of an Individual Virtual Disk to Original/Different Guest VM ..................96
12 Granular Restore.............................................................................................101
Requirements and Limitations ......................................................................................101
Start Granular Restore..................................................................................................102
13 Contact Ahsay .................................................................................................110
www.bobcloud.net
Technical Assistance ....................................................................................................110
Documentation..............................................................................................................110
www.bobcloud.net 1
1 Overview
What is this software?
Ahsay brings you specialized client backup software, namely AhsayOBM, to provide a
comprehensive backup solution for your Hyper-V host machine backup. The Hyper-V module of
AhsayOBM provides you with a set of tools to protect Hyper-V host machine and guest VMs. This
includes a machine backup feature and instant recovery feature (with the use of Run Direct
technology), to ensure that mission critical machines are back up and running within minutes of a
disaster.
System Architecture
The following high level system architecture diagram illustrates the major elements involved in the
backup process of a Hyper-V host with AhsayOBM and AhsayCBS.
In this user guide, we will focus on the software installation, as well as the end-to-end backup and
restore process using the AhsayOBM as a client backup software.
www.bobcloud.net 2
2 Preparing for Backup and Restore
Hardware Requirement
Refer to the following article for the list of hardware requirements for AhsayOBM:
FAQ: Ahsay Hardware Requirement List (HRL) for version 7.3 or above
Software Requirement
Refer to the following article for the list of compatible operating systems and Hyper-V platforms:
FAQ: Ahsay Software Compatibility List (SCL) for version 7.3 or above
Antivirus Exclusion Requirement
To optimize performance of AhsayOBM on Windows, and to avoid conflict with your antivirus
software, refer to the following KB article the list of processes and directory paths that should be
added to all antivirus software white-list / exclusion list:
http://wiki.ahsay.com/doku.php?id=public:5352_suggestion_on_antivirus_exclusions
NOTE
For AhsayOBM version 7.17 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.
AhsayOBM
1. AhsayOBM is installed on the Hyper-V server. For Hyper-V Cluster environment
AhsayOBM is installed on all Cluster nodes.
2. The operating system account for setting up the Hyper-V / Hyper-V Cluster backup set
must have administrator permission (e.g. administrative to access the cluster storage).
3. For Granular Restore, Windows User Account Control (UAC) must be disabled.
4. AhsayOBM user account has sufficient Hyper-V add on modules or CPU sockets assigned.
Hyper-V Cluster backup sets will require one AhsayOBM license per node. (Please contact
your backup service provider for details)
5. AhsayOBM user account has sufficient quota assigned to accommodate the storage of the
guest virtual machines. (Please contact your backup service provider for details).
Hyper-V guest virtual machines contain three types of virtual disks:
Fixed Hard Disk.
Dynamic Hard Disk.
Differencing Hard Disk.
When AhsayOBM backs up a Hyper-V guest virtual machines for an initial or subsequent
full backup jobs:
Using fixed Hard Disks it will back up the provisioned size, e.g. for a 500GB fixed
virtual hard disk 500GB will be backed up to the storage designation.
www.bobcloud.net 3
Using Dynamic Hard Disk or Differencing Hard Disk it will back up the used size,
e.g. for a 500GB fixed virtual hard disk, 20GB will backed up to the storage
designation if only 20GB are used.
6. Since version 7.13, the default Java heap size setting on AhsayOBM is 2048MB, for Hyper-
V backups it is highly recommended to increase the Java heap size setting to improve
backup and restore performance. (The actual heap size is dependent on amount of free
memory available on your Hyper-V server).
Delta generation of large VHD files is a memory intensive process; therefore, it is
recommended that the Java heap size to be at least 2048MB - 4096MB. The actual
required Java heap size is subject to various factors including files size, delta mode,
backup frequency, etc.
Refer to the following KB article for details:
http://wiki.ahsay.com/doku.php?id=public:5003_how_to_modify_java_heap_of_ahsayobc
7. For stand-alone Hyper-V server, AhsayOBM uses the temporary folder for storing backup
set index files and any incremental or differential delta files generated during a backup job.
To ensure optimal backup / restore performance, it should be located on a local drive with
plenty of free disk space. It should not be on the Windows system C:\ drive.
Note: For Hyper-V server in Failover Cluster environment, the temporary folder must be set
to a network shared path accessible to all cluster nodes, or a Cluster Shared Volume.
8. AhsayOBM UI must be running when a guest virtual machine is started using Run Direct
Restore or when migration process is running.
9. For local, mapped drive, or removable drive storage destinations with Run Direct enabled,
the compression type will always be set to No Compression and data encryption is
disabled to ensure optimal backup and restore performance. The backup set compression
type and data encryption settings will only be applied to CBS, SFTP/FTP, or Cloud storage
destinations.
10. For ease of restore it is recommended to back up the whole guest machine (all the virtual
disks) rather than individual virtual disks.
11. Make sure NFS service has started for Run Direct to operate. If the backup destination is
located on network drive, the logon must have sufficient permission to access the network
resources.
www.bobcloud.net 4
Hyper-V Server Requirement
1. The Hyper-V management tools are installed on the server. For Hyper-V Cluster
environments Hyper-V management tools is installed on all Cluster nodes.
2. The Hyper-V services are started on the server. For Hyper-V Cluster environments the
Hyper-V services are started on all Cluster nodes.
www.bobcloud.net 5
Example: Windows 2008 R2 Hyper-V
3. The Microsoft Hyper-V VSS Writer is installed and running on the Hyper-V server and the
writer state is Stable. This can be verified by running the vssadmin list writers command.
Example:
C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative
command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {8de7ed2b-8d69-43dd-beec-5bfb79b9691c}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {1f668bf9-38d6-48e8-81c4-2df60a3fab57}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {01499d55-61da-45bc-9a1e-76161065630f}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {a51919e3-0256-4ecf-8530-2f600de6ea68}
www.bobcloud.net 6
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {7303813b-b22e-4967-87a3-4c6a42f861c4}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {d3199397-ec58-4e57-ad04-e0df345b5e68}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {25428453-2ded-4204-800f-e87204f2508a}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {78fa3f1e-d706-4982-a826-32523ec9a305}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {3efcf721-d590-4e50-9a37-845939ca51e0}
State: [1] Stable
Last error: No error
4. Integration Service
i. If Integration services is not installed / updated on a guest virtual machine or the
guest operating system is not supported by Integration Services, the
corresponding virtual machine will be paused or go into a saved stated during the
snapshot process for both backup and restore, and resume when the snapshot is
completed. Furthermore, the corresponding virtual machine uptime will also be
reset to 00:00:00 in the Hyper-V Manager.
ii. Installing or updating Integration Services guest virtual machine(s) may require a
restart of the guest virtual machine to complete the installation.
To install Integration Services
In Hyper-V Manager connect to the guest virtual machine and select Action >
Insert Integration Services disk
www.bobcloud.net 7
Example: Windows 7 Enterprise guest
If the guest operating system supports live virtual machine backup the Backup
(volume checkpoint) is enabled.
The related Integration Services are running on the guest virtual machine:
Example: Windows 7 Enterprise guest
Example: CentOS 6.4 Linux guest
www.bobcloud.net 8
To check if Linux Integration Services is running on the Linux guest:
# lsmod | grep hv
hv_netvsc 23667 0
hv_utils 7012 0
hv_storvsc 10022 2
hv_vmbus 91567 4
hv_netvsc,hv_utils,hid_hyperv,hv_storvsc
# ps -ef|grep hv
root 267 2 0 18:07 ? 00:00:00
[hv_vmbus_con/0]
root 268 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 269 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 270 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 271 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 272 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 273 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 274 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 275 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 276 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 277 2 0 18:07 ? 00:00:00
[hv_vmbus_ctl/0]
root 1174 1 0 18:07 ? 00:00:00
/usr/sbin/hv_kvp_daemon
root 1185 1 0 18:07 ? 00:00:00
/usr/sbin/hv_vss_daemon
root 1332 1316 0 18:11 pts/0 00:00:00 grep hv
Please refer to the following articles for further details on:
Considerations for backing up and restoring virtual machines
https://technet.microsoft.com/en-us/library/dn798286.aspx
Supported Windows Guest Operating Systems for Hyper-V in Windows
Server 2012
https://technet.microsoft.com/en-us/library/dn792028(v=ws.11).aspx
Supported Windows Guest Operating Systems for Hyper-V in Windows
Server 2012 R2
https://technet.microsoft.com/en-us/library/dn792027(v=ws.11).aspx
Supported Linux and FreeBSD virtual machines for Hyper
https://technet.microsoft.com/library/dn531030.aspx
Linux Integration Services Version 4.0 for Hyper-V
https://www.microsoft.com/en-us/download/details.aspx?id=46842
Managing Hyper-V Integration Services
https://msdn.microsoft.com/en-
us/virtualization/hyperv_on_windows/user_guide/managing_ics
www.bobcloud.net 9
5. For Hyper-V 2008 R2 server in order to use Run Direct restore feature the "Microsoft
Security Advisory 3033929" security update must be installed.
Please refer to the following KB article from Microsoft for further details:
https://support.microsoft.com/en-us/kb/3033929
6. For Run Direct Hyper-V Cluster backup sets the storage destination must be accessible by
all Hyper-V nodes.
7. For Hyper-V Cluster backup sets the guest virtual machines must be created and managed
by the Failover Cluster Manager.
Hyper-V Backup Methods
AhsayOBM v7 supports two methods for Hyper-V guest VM backup, VM Snapshot and Saved State.
VM Snapshot
The VM snapshot method is the preferred backup option, as it supports live guest VM backups.
This means guest VM will not be put into a saved state when a VSS snapshot is taken during a
backup job. So it will not affect the availability of any applications or services running on the guest
VM every time a backup job is performed.
VM Snapshot Method Requirements
1. The guest VM must be running.
2. Integration services must be enabled on the guest VM.
3. The Hyper-V Volume Shadow Copy Requestor service is running on the guest VM installed
with Windows operating system. Please refer to the following article for further details:
https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/reference/integration-
services#hyper-v-volume-shadow-copy-requestor
4. For guest VMs installed with Linux / FreeBSD operating systems, the VSS Snapshot
daemon is required for live backups, not all Linux / FreeBSD versions support live backup
on Hyper-V. For example, only FreeBSD 11.1 supports live backup while for Ubuntu,
version 14.04 LTS to 17.04 LTS supports live backups. Please refer to the following article
for further details: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-
v/supported-linux-and-freebsd-virtual-machines-for-hyper-v-on-windows
5. The guest VM volumes must use a file system which supports the use of VSS snapshots,
for example NTFS.
6. The guest VMs snapshot file location must be set to the same volume in the Hyper-V host
as the VHD file(s).
7. The guest VM volumes have to reside on basic disks. Dynamic disks cannot be used within
the guest VM.
www.bobcloud.net 10
Note
Some older Windows operating systems installed on guest VM's which do not support either Integration
Services or the Hyper-V Volume Shadow Copy Requestor Service, will not support VM snapshot method,
for example, Microsoft Windows 2000, Windows XP, or older Linux/FreeBSD versions.
Saved State
If any of the VM Snapshot method requirements cannot be fulfilled, AhsayOBM will automatically
use the Save State method. When the Saved State method is used, the guest VM is placed into a
saved state while the VSS snapshot is created (effectively shut down), and the duration is
dependent on the size of VM and performance of Huper-V host. The downside is it may affect the
availability of any applications or services running on the guest VM every time a backup job is
performed.
www.bobcloud.net 11
CBT Requirement
Since AhsayOBM version 7.9.0.0, a new service CBT Cluster Services (Ahsay Online Backup
Manager) is installed and enabled upon installation / upgrade to version AhsayOBM v7.9.0.0 or
above.
1. CBT (Changed Block Tracking) is used to optimize incremental backups of virtual
machines by keeping a log of the blocks of data that have changed since the previous
snapshot making incremental backups much faster. When AhsayOBM performs a backup,
CBT feature can request transmissions of only the blocks that changed since the last
backup, or the blocks in use.
Note
From version 7.15.0.0 onwards, CBT service is supported on all the backup destinations for
AhsayOBM instead of only RunDirect related local destination.
2. CBT cluster service is only installed on Windows x64 machine.
3. Check if CBTFilter is enabled.
Example:
i. This can be verified by running the net start CBTFilter command.
C:\Users\Administrator>net start CBTFilter
The requested service has already been started.
More help is available by typing NET HELPMSG 2182.
ii. Note: For Windows Server 2008 R2, if the following error is displayed
C:\Users\Administrator>net start CBTFilter
System error 577 has occurred.
Windows cannot verify the digital signature for this file. A
recent hardware or software change might have installed a
file that is signed incorrect or damaged, or that might be
malicious software from an unknown source.
The issue may be related to the availability of SHA-2 code signing support for
Windows Server 2008 R2 (https://technet.microsoft.com/en-
us/library/security/3033929).
www.bobcloud.net 12
To resolve the issue, install the following patch from Microsoft
https://www.microsoft.com/en-us/download/confirmation.aspx?id=46083
Restart the affected server afterward for AhsayOBM to operate properly.
4. CBT Cluster Service and CBTFilter will NOT be installed on Windows Server 2016 where a
built-in system called Resilient Change Tracking (RCT) will be used instead. For details of
RCT, please refer to Windows Server 2016 RCT Requirement.
Windows Server 2016 Requirement
RCT Requirement
1. From version 7.15.0.0 onwards AhsayOBM would not install CBT Cluster Services (Ahsay
Online Backup Manager) but use the native built-in RCT (Resilient Change Tracking)
feature of Windows server 2016 instead.
2. The guest virtual machine version in Hyper-V must be 8.0 or above.
Example:
i. This can be verified by using Windows PowerShell.
get–VM | format–table name, version
ii. If the version is not 8.0 or above, then need to upgrade the virtual machine
configuration version.
Update-VMversion <vmname>
Please refer to the following link of Microsoft for details about virtual machine version:
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/Upgrade-
virtual-machine-version-in-Hyper-V-on-Windows-or-Windows-Server
Guest VM Dependencies Requirements
To get full use of Hyper-V, install the appropriate linux-tools and linux-cloud-tools packages to
install tools and daemons, e.g. VSS Snapshot Daemon, for use with virtual machines. Please refer
to the following link for the details of requirements for Ubuntu relating to Hyper-V daemons:
https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/supported-linux-and-
freebsd-virtual-machines-for-hyper-v-on-windows
www.bobcloud.net 13
Limitations
1. Backup of guest machines located on a SMB 3.0 shares is not supported.
2. Backup of virtual machine with pass through disk (directly attached physical disk) is not
supported.
3. For backup of individual virtual disks, the restored virtual machine does not support the
reversion of previous snapshots, if the snapshot contains disks which are not previously
backed up by AhsayOBM.
4. A guest virtual machine can only be restored to the Hyper-V server with the same version,
e.g. backup of a guest on Hyper-V 2012 R2 server cannot be restored to Hyper-V 2008 R2
Server or vice versa.
5. The guest virtual machine will not start up if the virtual disk containing the guest operating
system is not restored.
6. Run Direct Restore of VM containing .VHDS shared virtual disk(s) is not supported.
7. Restore of individual virtual disks is only supported using the Restore raw file option for a
virtual disk with no snapshots.
NOTE
This will require modification of Hyper-V guest configuration files, and this only should be done if
you have in-depth knowledge and understanding of Hyper-V, otherwise the guest virtual
machine may not startup properly.
8. Replication must be disabled for the VM selected for backup, otherwise there may be
following error occurring during backup job:
For AhsayOBM pre-v7.15.6.55: Failed to backup virtual machine "guest_guid"., Reason
= "A parameter cannot be found that matches parameter name 'vmid'.
For AhsayOBM v7.15.6.55 or above: Failed to backup virtual machine "guest_guid".,
Reason = "Failed to take VM snapshot. Error = [CreateVirtualSystemSnapshotV2]
Error="The method call failed." (32775)".
Please refer to the following link for more details:
http://wiki.ahsay.com/doku.php?id=public:5349_failed_to_backup_hyperv_virtual_machine
_with_replication_enabled
www.bobcloud.net 14
3 Run Direct
Hyper-V Run Direct is a recovery feature introduced in AhsayOBM version 7.5.0.0, it helps to reduce
disruption and downtime of your production guest virtual machines.
Unlike normal recovery procedures where the guest virtual machine(s) are restored from the backup
destination and copied to production storage, which can take hours to complete. Restore with Run
Direct can instantly boot up a guest virtual machine by running it directly from the backup file in the
backup destination; this process can be completed in minutes.
The following steps are taken when a Run Direct restore is initiated:
Delete Guest Virtual Machine
AhsayOBM will delete the existing guest virtual machine on the original or alternate location
(if applicable).
Create Virtual Hard Disk Image Files
Empty virtual hard disk image files are created on the Hyper-V server (either on the original
location or alternate location).
Create VSS Snapshot
A VSS snapshot is created to make the backup data read only and track changes made
within the guest virtual machine environment.
Start Up Virtual Machine
The guest virtual machine is started up. To finalize recovery of the guest virtual machine,
you will still need to migrate it to from the backup destination to the designated permanent
location on the Hyper-V server.
Copy Data
Copy the data from the backup files in the backup destination to empty hard disk images on
the Hyper-V server.
Apply Changes
Apply any changes made within the guest virtual machine environment to the hard disk
image files on the Hyper-V server.
Delete VSS Snapshot
The VSS snapshot will be deleted after the Run Direct restoration is completed.
www.bobcloud.net 15
The restored virtual machine, at this stage (e.g. before the restore is finalized) is in a read-only state
to avoid unexpected changes. All changes made to the virtual disks (e.g. operation within the guest
virtual machine) are stored in a VSS snapshot created for the Run Direct restore. These changes
are discarded when Run Direct is stopped, where the restored guest virtual machine 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.
For more details on Run Direct restore options, refer to Restore Options.
www.bobcloud.net 16
4 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.
Granular restore is one of the available restore options for Hyper-V backup sets from AhsayOBM
v7.13.0.0 or above. AhsayOBM makes use of granular restore technology to enable a file level
restore from a virtual disk file (VHD) 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 the files on the virtual disks. Granular restore gives you
a fast and convenient way to recover individual files from 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, e.g. 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.
IMPORTANT
Granular restore requires an additional OpenDirect / Granular restore add-on module license to
work. Contact your backup service provider for further details.
www.bobcloud.net 17
How does Granular Restore work?
Benefits of using Granular Restore
Comparison between Granular Restore and Traditional Restore
Granular Restore
Introduction
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 32 bit or 64 bit Windows machine
you are performing the restore.
Pros
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.
www.bobcloud.net 18
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
Hyper-V guest VM backup set and a separate file backup set for the
file(s) you wish to restore. You will required 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.
Cons
No Encryption
and
Compression
To make 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
Introduction
The traditional restore method for guest VMs, restores the entire backup files to either to the
original VM location or another a 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.
Pros
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.
Cons
Slower
Recovery
As the entire guest VM has to be restored before you can access any it’s
file(s) or data, the restore time could be long if the guest VM size is large.
www.bobcloud.net 19
Requirements
Supported Backup Modules
Granular restore is supported on Hyper-V backup sets created and backed up using AhsayOBM
version 7.13.0.0 or above 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
AhsayOBM must be installed on a 64 bit Windows machine as libraries for Granular only supports
64 bit Windows operating system. AhsayOBM 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. AhsayOBM will automatically
take the next available drive letter in alphabetical order for the mounted virtual disk.
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.
www.bobcloud.net 20
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 AhsayOBM
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 AhsayOBM client machine
requires Administrator privileges
www.bobcloud.net 21
5 Starting AhsayOBM
Login to AhsayOBM
1. A shortcut icon of AhsayOBM should have been created on your Windows desktop after
installation. Double click the icon to launch the application.
2. Enter the login name and password of your AhsayOBM account provided by your backup
service provider, then click OK to login.
www.bobcloud.net 22
6 Creating a Hyper-V Backup Set
Non-Cluster Environment
Run Direct Backup Set
1. Click the Backup Sets icon on the main interface of AhsayOBM.
2. Create a new backup set by clicking the “+” icon or Add button to created new backup set.
3. Select the Backup set type and name your new backup set then click Next to proceed.
4. In the Backup Source menu, select the guest virtual machines you would like to backup.
Click Next to proceed.
www.bobcloud.net 23
5. In the Schedule menu, you can configure a backup schedule for backup job to run
automatically at your specified time interval.
Click Add to add a new schedule or double click on the existing schedule to change the
values. Click Next to proceed when you are done setting.
Note: The default backup schedule is daily backup at 22:00, the backup job will run until
completion and the retention policy job will be run immediately after the backup job.
www.bobcloud.net 24
6. Select the backup storage destination.
Note
1. For Hyper-V backup sets by the default the Run Direct feature is enabled.
2. For Run Direct enabled backup sets, the storage destination is restricted to Local,
Mapped Drive, or Removable Drive.
i. Click on Change to select the storage destination a Local, Mapped Drive, or
Removable Drive.
www.bobcloud.net 25
ii. After selecting the storage destination click on the Test button to verify if
AhsayOBM has permission to access the folder on the storage destination.
iii. Once the test is finished AhsayOBM will display “Test completed successfully
message. Click OK to proceed.
iv. To add extra storage destination click Add, otherwise Click Next to proceed.
www.bobcloud.net 26
7. If you wish to enable the granular restore feature, make sure you turn on the Granular
Restore switch in this menu. Click Next to proceed.
Notes
1. Once the Granular Restore feature is enabled and the backup set is saved, it is NOT
possible to disable it afterwards, and vice versa. If you wish to change the Granular
Restore settings, a new backup set will have to be created.
2. It is possible to enable both Granular Restore and Run Direct restore on the same
backup set. However, AhsayOBM will only allow either Granular Restore or Run Direct
restore to run, but not both to run concurrently.
3. Granular Restore requires an additional OpenDirect / Granular restore add-on module
license to work. Contact your backup service provider for further details.
8. IMPORTANT: If you have enabled the Granular restore or Run Direct restore feature, the
backup data will not be compressed and encrypted to optimize the restore performance,
therefore you can skip to step 10.
In the Encryption window, the default Encrypt Backup Data option is enabled with an
encryption key preset by the system which provides the most secure protection.
You can choose from one of the following three Encryption Type options:
Default – an encryption key with 44 alpha numeric characters will be randomly
generated by the system
User password – the encryption key will be the same as the login password of your
AhsayOBM at the time when this backup set is created. Please be reminded that if
you change the AhsayOBM login password later, the encryption keys of the backup
sets previously created with this encryption type will remain unchanged.
www.bobcloud.net 27
Custom – you can customize your encryption key, where you can set your own
algorithm, encryption key, method and key length.
Notes:
1. For best practice on managing your encryption key, refer to the following KB article.
http://wiki.ahsay.com/doku.php?id=public:5034_best_practices_for_managing_encryption_key
2. For local, mapped drive, or removable drive storage destinations with Run Direct enabled the
compression type will a be set No Compression and data encryption is disabled to ensure
optimal backup and restore performance. The backup set compression type and data
encryption settings will only be applied to CBS, SFTP/FTP, or Cloud storage destinations for
the backup set.
Click Next when you are done setting.
9. If you have enabled the Encryption Key feature in the previous step, the following pop-up
window shows, no matter which encryption type you have selected.
www.bobcloud.net 28
The pop-up window has the following three options to choose from:
Unmask encryption key – The encryption key is masked by default. Click this option
to show the encryption key.
Copy to clipboard – Click to copy the encryption key, then you can paste it in
another location of your choice.
Confirm – Click to exit this pop-up window and proceed to the next step.
10. Enter the Windows login credentials used by AhsayOBM to authenticate the scheduled or
continuous backup job.
Note
If the backup schedule is turned off for the backup set the Windows User
Authentication screen will be automatically skipped. The Windows User Authentication
login credentials can be added or updated post backup set creation.
11. Backup set created.
i. To start a manual backup job click on Backup now.
www.bobcloud.net 29
ii. To verify the backup set settings click on Close and then click on the Hyper-V
backup set to complete the setup.
www.bobcloud.net 30
Non Run Direct Backup Set
1. Click the Backup Sets icon on the main interface of AhsayOBM.
2. Create a new backup set by clicking the “+” icon next to Add new backup set.
3. Select the Backup set type and name your new backup set then click Next to proceed.
Note: AhsayOBM will automatically detect the Hyper-V version installed on the host.
4. In the Backup Source menu, select the guest virtual machines you would like to backup.
Click Next to proceed.
www.bobcloud.net 31
5. In the Schedule menu, you can configure a backup schedule for backup job to run
automatically at your specified time interval.
Click Add to add a new schedule or double click on the existing schedule to change the
values. Click Next to proceed when you are done setting.
Note: The default backup schedule is daily backup at 22:00 with the backup job will run
until completion and the retention policy job will be run immediately after the backup job.
6. Select the backup storage destination.
Note: For Hyper-V backup sets, the default setting is for Run Direct to be enabled and the
storage destination is either a Local, Mapped Drive, or Removable Drive.
www.bobcloud.net 32
To select a cloud, sftp/ftp, or CBS as a storage destination un-select Run Direct setting
and select your desired cloud, sftp/ftp, or CBS as a storage destination. Click OK to
proceed when you are done.
7. Click Add to an additional storage destination or click Next to proceed when you are done.
8. If you wish to enable the Granular restore feature, make sure you turn on the Granular
Restore switch in this menu. Click Next to proceed.
Notes
1. Once the Granular Restore feature is enabled and the backup set is saved, it is
NOT possible to disable it afterwards, and vice versa. If you wish to change the
Granular Restore settings, a new backup set will have to be created.
2. It is possible to enable both Granular Restore and Run Direct restore on the same
backup set. However, AhsayOBM will only allow either Granular Restore or Run
Direct restore to run, but not both to run concurrently.
3. Granular Restore requires an additional OpenDirect / Granular restore add-on
module license to work. Contact your backup service provider for further details.
www.bobcloud.net 33
9. IMPORTANT: If you have enabled the Granular restore or Run Direct restore feature,
backup data will not be compressed and encrypted to optimize the restore performance,
therefore you can skip to step 11.
In the Encryption window, the default Encrypt Backup Data option is enabled with an
encryption key preset by the system which provides the most secure protection.
You can choose from one of the following three Encryption Type options:
Default – an encryption key with 44 alpha numeric characters will be randomly
generated by the system
User password – the encryption key will be the same as the login password of your
AhsayOBM at the time when this backup set is created. Please be reminded that if
you change the AhsayOBM login password later, the encryption keys of the backup
sets previously created with this encryption type will remain unchanged.
Custom – you can customize your encryption key, where you can set your own
algorithm, encryption key, method and key length.
www.bobcloud.net 34
Notes:
i. For best practice on managing your encryption key, refer to the following KB
article.
http://wiki.ahsay.com/doku.php?id=public:5034_best_practices_for_managing_e
ncryption_key
ii. For local, mapped drive, or removable drive storage destinations with Run Direct
enabled the compression type will be set No Compression and data encryption
is disabled to ensure optimal backup and restore performance. The backup set
compression type and data encryption settings will only be applied to CBS,
SFTP/FTP, or Cloud storage destinations for the backup set.
Click Next when you are done setting.
10. If you have enabled the Encryption Key feature in the previous step, the following pop-up
window shows, no matter which encryption type you have selected.
The pop-up window has the following three options to choose from:
Unmask encryption key – The encryption key is masked by default. Click this option
to show the encryption key.
Copy to clipboard – Click to copy the encryption key, then you can paste it in
another location of your choice.
Confirm – Click to exit this pop-up window and proceed to the next step.
www.bobcloud.net 35
11. Enter the Windows login credentials used by AhsayOBM to authenticate the scheduled
backup job.
Note: If the backup schedule is turned off for the backup set the Windows User
Authentication screen will be automatically skipped. The Windows User Authentication
login credentials can be added or update post backup set creation.
12. Backup set created.
i. To start a manual backup job click on Backup now.
ii. To verify the backup set settings click on Close and then click on the Hyper-V
backup set to complete the setup.
www.bobcloud.net 36
www.bobcloud.net 37
Cluster Environment
Requirements
For Hyper-V Cluster backup sets:
1. The same version of AhsayOBM must be installed on all Hyper-V Cluster nodes.
2. The same backup user account must be used.
3. The backup schedule must be enabled on all Hyper-V Cluster nodes.
Run Direct Backup Set
1. Click the Backup Sets icon on the main interface of AhsayOBM
2. Create a new backup set by clicking the “+” icon or Add button to created new backup set.
3. Select the Backup set type MS Hyper-V Backup, Version Microsoft Hyper-V Server 2012
R2 (Failover Cluster), and name your new backup set then click Next to proceed.
4. In the Backup Source menu, select the guest virtual machines you would like to backup.
Click Next to proceed.
www.bobcloud.net 38
5. Click Add to add a new schedule or double click on the existing schedule to change the
values. Click Next to proceed when you are done setting.
Note: The default backup schedule is daily backup at 22:00 with the backup job will run
until completion and the retention policy job will be run immediately after the backup job.
6. Select the backup storage destination.
Note: For Hyper-V backup sets by the default the Run Direct feature is enabled.
i. Click on Change to select the storage destination a Local, Mapped Drive, or
Removable Drive.
www.bobcloud.net 39
ii. After selecting the storage destination click on the Test button to verify if
AhsayOBM has permission to access the folder on the storage destination.
iii. Once the test is finished AhsayOBM will display “Test completed successfully”
message. Click OK to proceed.
Note: For Hyper-V Cluster backup set with Run Direct enabled please ensure all
nodes have access to the Local, Mapped Drive, or Removable Drive destination
storage.
iv. To add extra storage destinations click Add, otherwise Click Next to proceed.
www.bobcloud.net 40
7. If you wish to enable the Granular Restore feature, make sure you turn on the Granular
Restore switch in this menu. Click Next to proceed.
Notes
1. Once the Granular Restore feature is enabled and the backup set is saved, it is
NOT possible to disable it afterwards, and vice versa. If you wish to change the
Granular Restore settings, a new backup set will have to be created.
2. It is possible to enable both Granular Restore and Run Direct restore on the same
backup set. However, AhsayOBM will only allow either Granular Restore or Run
Direct restore to run, but not both to run concurrently.
3. Granular Restore requires an additional OpenDirect / Granular restore add-on
module license to work. Contact your backup service provider for further details.
8. IMPORTANT: If you have enabled the Granular restore or Run Direct restore feature,
backup data will not be compressed and encrypted to optimize restore performance,
therefore you can skip to step 10.
In the Encryption window, the default Encrypt Backup Data option is enabled with an
encryption key preset by the system which provides the most secure protection.
You can choose from one of the following three Encryption Type options:
Default – an encryption key with 44 alpha numeric characters will be randomly
generated by the system
User password – the encryption key will be the same as the login password of your
AhsayOBM at the time when this backup set is created. Please be reminded that if
you change the AhsayOBM login password later, the encryption keys of the backup
sets previously created with this encryption type will remain unchanged.
www.bobcloud.net 41
Custom – you can customize your encryption key, where you can set your own
algorithm, encryption key, method and key length.
Notes:
i. For best practice on managing your encryption key, refer to the following KB
article.
http://wiki.ahsay.com/doku.php?id=public:5034_best_practices_for_managing_e
ncryption_key
ii. For local, mapped drive, or removable drive storage destinations with Run Direct
enabled the compression type will always be set No Compression and data
encryption is disabled to ensure optimal backup and restore performance. The
backup set compression type and data encryption settings will only be applied to
CBS, SFTP/FTP, or Cloud storage destinations for the backup set.
Click Next when you are done setting.
www.bobcloud.net 42
9. If you have enabled the Encryption Key feature in the previous step, the following pop-up
window shows, no matter which encryption type you have selected.
The pop-up window has the following three options to choose from:
Unmask encryption key – The encryption key is masked by default. Click this option
to show the encryption key.
Copy to clipboard – Click to copy the encryption key, then you can paste it in
another location of your choice.
Confirm – Click to exit this pop-up window and proceed to the next step.
10. Enter the Windows login credentials used by AhsayOBM to authenticate the scheduled or
continuous backup job.
www.bobcloud.net 43
Note: If the backup schedule is turned off for the backup set the Windows User
Authentication screen will be automatically skipped. The Windows User Authentication
login credentials can be added or update post backup set creation.
11. Configure a temporary directory for the backup set.
Refer to Chapter 4 of this document for details on the temporary directory requirement.
12. Backup set created.
i. To start a manual backup job click on Backup now.
ii. To verify the backup set settings click on Close and then click on the Hyper-V
backup set to complete the setup.
iii. Go to General and verify if the node has been added to the backup schedule.
www.bobcloud.net 44
iv. On the next Hyper-V node startup AhsayOBM and select the Hyper-V backup set.
13. Go to Backup schedule and enable the Run schedule backup for this backup set and
set the backup schedule time and click on Save when finished.
14. Go to General and verify if the node has been added to the backup schedule.
15. Repeat steps 11 to 12 for all Hyper-V Cluster nodes.
www.bobcloud.net 45
Non Run Direct Backup Set
1. Click the Backup Sets icon on the main interface of AhsayOBM
2. Create a new backup set by clicking the “+” icon or Add button to created new backup set.
3. Select the Backup set type MS Hyper-V Backup, Version Microsoft Hyper-V Server 2012
R2 (Failover Cluster), and name your new backup set then click Next to proceed.
4. In the Backup Source menu, select the guest virtual machines you would like to backup.
Click Next to proceed.
5. Click Add to add a new schedule or double click on the existing schedule to change the
values. Click Next to proceed when you are done setting.
www.bobcloud.net 46
Click Add to add a new schedule or double click on the existing schedule to change the
values. Click Next to proceed when you are done setting.
Note: The default backup schedule is daily backup at 22:00 with the backup job will run
until completion and the retention policy job will be run immediately after the backup job.
6. Select the backup storage destination. To select a cloud, SFTP/FTP, or CBS as a storage
destination un-select Run Direct setting and select your desired cloud, SFTP/FTP, or CBS
as a storage destination. Click OK to proceed when you are done.
7. Click Add to an additional storage destination or click Next to proceed when you are done.
www.bobcloud.net 47
8. If you wish to enable the Granular Restore feature, make sure you turn on the Granular
Restore switch in this menu. Click Next to proceed.
Notes
1. Once the Granular Restore feature is enabled and the backup set is saved, it is
NOT possible to disable it afterwards, and vice versa. If you wish to change the
Granular Restore settings, a new backup set will have to be created.
2. It is possible to enable both Granular Restore and Run Direct restore on the same
backup set. However, AhsayOBM will only allow either Granular Restore or Run
Direct restore to run, but not both to run concurrently.
3. Granular Restore requires an additional OpenDirect / Granular restore add-on
module license to work. Contact your backup service provider for further details.
9. IMPORTANT: If you have enabled the Granular Restore or Run Direct restore feature,
backup data will not be compressed and encrypted to optimize restore performance,
therefore you can skip to step 11.
In the Encryption window, the default Encrypt Backup Data option is enabled with an
encryption key preset by the system which provides the most secure protection.
You can choose from one of the following three Encryption Type options:
Default – an encryption key with 44 alpha numeric characters will be randomly
generated by the system
User password – the encryption key will be the same as the login password of your
AhsayOBM at the time when this backup set is created. Please be reminded that if
you change the AhsayOBM login password later, the encryption keys of the backup
sets previously created with this encryption type will remain unchanged.
www.bobcloud.net 48
Custom – you can customize your encryption key, where you can set your own
algorithm, encryption key, method and key length.
Notes:
i. For best practice on managing your encryption key, refer to the following KB
article.
http://wiki.ahsay.com/doku.php?id=public:5034_best_practices_for_managing_e
ncryption_key
ii. For local, mapped drive, or removable drive storage destinations with Run Direct
enabled the compression type will always be set No Compression and data
encryption is disabled to ensure optimal backup and restore performance. The
backup set compression type and data encryption settings will only be applied to
CBS, SFTP/FTP, or Cloud storage destinations for the backup set.
Click Next when you are done setting.
www.bobcloud.net 49
10. If you have enabled the Encryption Key feature in the previous step, the following pop-up
window shows, no matter which encryption type you have selected.
The pop-up window has the following three options to choose from:
Unmask encryption key – The encryption key is masked by default. Click this option
to show the encryption key.
Copy to clipboard – Click to copy the encryption key, then you can paste it in
another location of your choice.
Confirm – Click to exit this pop-up window and proceed to the next step.
www.bobcloud.net 50
11. Enter the Windows login credentials used by AhsayOBM to authenticate the scheduled
backup job.
Note: If the backup schedule is turned off for the backup set the Windows User
Authentication screen will be automatically skipped. The Windows User Authentication
login credentials can be added or update post backup set creation.
12. Backup set created.
i. To start a manual backup job click on Backup now.
ii. To verify the backup set settings click on Close and then click on the Hyper-V
backup set to complete the setup.
13. Go to General and verify if the node has been added to the backup schedule.
www.bobcloud.net 51
14. On the next Hyper-V node startup AhsayOBM and select the Hyper-V backup set.
15. Go to Backup schedule and enable the Run schedule backup for this backup set and
set the backup schedule time and click on Save when finished.
16. Go to General and verify if the node has been added to the backup schedule.
17. Repeat steps 13 to 15 for all Hyper-V Cluster nodes.
www.bobcloud.net 52
7 Overview on the Backup Process
www.bobcloud.net 53
8 Running Backup Jobs
Login to AhsayOBM
Login to the AhsayOBM application according to the instructions in Chapter 3.1
Start a Manual Backup
1. Click the Backup icon on the main interface of AhsayOBM.
2. Select the Hyper-V backup set which you would like to start a manual backup.
3. Click on Backup to start the backup job.
www.bobcloud.net 54
4. If you would like to modify the In-File Delta type, Destinations, or Run Retention Policy
Settings, click on Show advanced option.
5. Backup job is completed.
www.bobcloud.net 55
Configure Backup Schedule for Automated Backup
1. Click on the Backup Sets icon on the AhsayOBM main interface.
2. Select the backup set that you would like to create a backup schedule for.
3. Click Backup Schedule.
4. Then create a new backup schedule by clicking on the Run scheduled backup for this
backup set. Set this to On.
Click Add to add a new schedule or double click on the existing schedule to change the
existing values. Click Save to proceed when you are done setting.
Note: The default backup schedule is daily backup at 22:00 with the backup job will run
until completion and the retention policy job will be run immediately after the backup job.
www.bobcloud.net 56
9 Restoring Hyper-V Guest Virtual Machines
Restore Options
There are three major types of restore options, namely Run Direct Restore, Non Run Direct Restore
and Granular Restore.
www.bobcloud.net 57
www.bobcloud.net 58
10 Run Direct Restore
Requirements and Limitations
For Restore to the Original Hyper-V Host:
1. Run Direct restore can only be performed on one guest virtual machine at a time.
2. Restored guest virtual machines using Run Direct containing a saved state will not
automatically power on. The saved state must be manually deleted in Hyper-V Manager
and the guest must be powered on manually.
3. When a guest virtual machine is started in a Run Direct instance is stopped any changes
made within the guest environment will be lost, if the guest virtual is not migrated to the
Hyper-V Server using the “Auto migrate after Run Direct is running” option.
4. When a guest virtual machine is started using Run Direct Restore all backup jobs (manual,
scheduled, and continuous) for the related backup set will be skipped.
5. When a guest virtual machine is started using Run Direct Restore the following features are
not available for the backup set; Data Integrity Check, Space Freeing Up, and Delete
Backup Data.
For Restore to the Different (Standby) Hyper-V Host:
1. AhsayOBM must be installed on the Hyper-V Host where you wish to restore the guest
Virtual Machine.
2. The same AhsayOBM backup account must be used.
3. For restore to an alternate Hyper-V Host with a different CPU architecture, the AhsayOBM
client application must be version 7.15.6.0 or above.
4. The correct encryption key is required if the backup set was created with the encryption key
feature enabled.
5. A guest virtual machine can only be restored to another Hyper-V server with the same
version, e.g. backup of a guest on Hyper-V 2012 R2 server cannot be restored to Hyper-V
2008 R2 host or vice versa.
6. A guest virtual machine backed up from a standalone Hyper-V host can only be restored to
another standalone Hyper-V host. A guest virtual machine backed up from a Hyper-V
Cluster can only be restored to another Hyper-V Cluster.
7. Guest Virtual Machine backed up to local drive / mapped drive / removable drive on the
original Hyper-V host can be restored to another Hyper-V host only if the new machine has
access to the original drive(s).
8. The network configuration and structure of the standby Hyper-V host must be same with
the original Hyper-V host.
www.bobcloud.net 59
9. Since version 7.13, the default Java heap size setting on AhsayOBM is 2048MB. For
Hyper-V restore it is highly recommended to increase the Java heap size setting to improve
performance. Especially guest VM’s with many incremental delta files. (The actual heap
size is dependent on amount of free memory available on your Hyper-V host).
10. The temporary directory should be set to a local drive for best restore performance. Also,
the temporary directory must have sufficient free disk space for the guest VM restore, for
example, the restore of a 500GB guest VM with 30 incremental files of around 5GB each
(500GB + 150GB (30 x 5GB)), the temporary directory will require at least 650GB of free
space.
11. Restore guest Virtual Machine to “Original Location” is possible only if the disk setup on the
new Hyper-V host is the same as the original Hyper-V host, for example if the original guest
VM was backed up on G: drive. Then restore to “Original location” can be selected if G:
drive is setup on the new Hyper-V host. Otherwise, select “Alternate location”.
12. The Hyper-V management tools must be installed on the new Hyper-V host. For Hyper-V
Cluster environments Hyper-V management tools must be installed on all Cluster nodes.
13. The Hyper-V services must be started on the host. For Hyper-V Cluster environment, the
Hyper-V services must be started on all Cluster nodes.
14. The Microsoft Hyper-V VSS Writer must be installed and running on the new Hyper-V
host and the writer state must be Stable. This can be verified by running the vssadmin list
writers command.
Example:
C:\Users\Administrator>vssadmin list writers
vssadmin 1.1 - Volume Shadow Copy Service administrative
command-line tool
(C) Copyright 2001-2005 Microsoft Corp.
Writer name: 'Task Scheduler Writer'
Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124}
Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b}
State: [1] Stable
Last error: No error
Writer name: 'VSS Metadata Store Writer'
Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06}
Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93}
State: [1] Stable
Last error: No error
Writer name: 'Performance Counters Writer'
Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2}
Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381}
State: [1] Stable
Last error: No error
Writer name: 'System Writer'
www.bobcloud.net 60
Writer Id: {e8132975-6f93-4464-a53e-1050253ae220}
Writer Instance Id: {8de7ed2b-8d69-43dd-beec-5bfb79b9691c}
State: [1] Stable
Last error: No error
Writer name: 'SqlServerWriter'
Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a}
Writer Instance Id: {1f668bf9-38d6-48e8-81c4-2df60a3fab57}
State: [1] Stable
Last error: No error
Writer name: 'ASR Writer'
Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4}
Writer Instance Id: {01499d55-61da-45bc-9a1e-76161065630f}
State: [1] Stable
Last error: No error
Writer name: 'Microsoft Hyper-V VSS Writer'
Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}
Writer Instance Id: {a51919e3-0256-4ecf-8530-2f600de6ea68}
State: [1] Stable
Last error: No error
Writer name: 'COM+ REGDB Writer'
Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
Writer Instance Id: {7303813b-b22e-4967-87a3-4c6a42f861c4}
State: [1] Stable
Last error: No error
Writer name: 'Shadow Copy Optimization Writer'
Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f}
Writer Instance Id: {d3199397-ec58-4e57-ad04-e0df345b5e68}
State: [1] Stable
Last error: No error
Writer name: 'Registry Writer'
Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
Writer Instance Id: {25428453-2ded-4204-800f-e87204f2508a}
State: [1] Stable
Last error: No error
Writer name: 'BITS Writer'
Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
Writer Instance Id: {78fa3f1e-d706-4982-a826-32523ec9a305}
State: [1] Stable
Last error: No error
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {3efcf721-d590-4e50-9a37-845939ca51e0}
State: [1] Stable
Last error: No error
www.bobcloud.net 61
Original Hyper-V Host
Start up a guest VM from Backup Destination without Auto Migration
Enabled
Follow the steps below to start up the guest VM directly from the backup files.
1. In the AhsayOBM main interface, click the Restore icon.
2. Select the backup set that you would like to restore the guest VM from.
3. Select the local, mapped drive, or removable drive storage destination that contains Hyper-
V guest VM that you would like to restore.
www.bobcloud.net 62
4. Select Restore virtual machines as the restore mode.
5. Select to restore the Hyper-V guest VM from a specific backup job then select the files or
folders that you would like to restore. Click Next to proceed.
6. Select to restore the Hyper-V guest VM to the Original location, or to an Alternate
location. Then select Run Direct and click Next to proceed.
Original location – The Hyper-V guest VM will be restored to the same directory path
which stores the backup source on the original Hyper-V host.
www.bobcloud.net 63
Alternate location – The Hyper-V guest VM will be restored to the different directory
path on the original Hyper-V host.
Click Next to proceed and the following values are needed to update:
i. Virtual Machine Name
ii. Virtual Machines Directory Location (guest configuration files)
iii. Restore As (new location for the guest VHD files)
Example:
i. Rename the restored guest VM to “CentOS 6.4-1
ii. Store the configuration files in the new location “D:\Virtual
Machines\CentOS6.4\CentOS 6.4\
iii. Store the VHD files in the new location “D:\Virtual Machines\CentOS6.4\
When the values have been updated click on Next to proceed.
7. Confirm the temporary directory path is correct and then click Restore to proceed.
8. If the guest virtual machine selected to be restored already exists on the Hyper-V server,
AhsayOBM will prompt to confirm overwriting of the existing guest.
Yes - the exiting guest virtual machine will be deleted from the Hyper-V server before
the restore process starts.
www.bobcloud.net 64
No - the restore of the current guest virtual machine will be skipped.
9. After the Hyper-V guest virtual machine has been restored, you will see the following
screen.
10. Go to the Hyper-V server and open the Hyper-V Manager to verify the guest VM has been
restored and is powered on.
11. Connect to the guest virtual machine to verify if is running correctly.
Example: Linux guest
www.bobcloud.net 65
Migrate Virtual Machine (Permanently Restore)
To permanently restore the guest virtual machine after starting up using the Run Direct option,
you will still need to migrate it from the backup destination to the designated permanent location on
the Hyper-V server using the Migrate Virtual Machine option. This process can be performed
even when the guest machine is already running.
1. After starting up the guest machine from the backup destination. Click on Close.
2. Click on Manage Run Direct virtual machines.
3. Click on the guest virtual machine.
www.bobcloud.net 66
4. To permanently restore the guest virtual machine, click on Migrate Virtual Machine.
Note
AhsayOBM will begin migration of the guest VM from the backup destination to the Hyper-V
Server.
The guest virtual machine can be used during the migration process. Any changes made in the
guest virtual machine environment is saved in transaction logs and will be applied when the
migration process is completed.
When finalizing the restore, during the application of changes in transaction logs with the restored
guest VM, the guest VM will be put into saved state temporarily. Once the changes have been
applied the guest virtual machine resume.
www.bobcloud.net 67
Stop Run Direct Virtual Machines
To stop running guest virtual machines started up using Run Direct can be done by either:
Quitting AhsayOBM
-OR-
Click on the Stop Run Direct button at the left bottom corner.
Click on Stop all Run Direct virtual machines.
Note
When a guest virtual machine started in a Run Direct instance is stopped, any changes
made within the guest environment will be lost, if the guest virtual is not migrated to the
Hyper-V Server using the “Auto migrate after Run Direct is running” option.
www.bobcloud.net 68
Start up a guest VM from Backup Destination with Auto Migration
Enabled
Follow the steps below to start up the guest VM directly from the backup files.
1. In the AhsayOBM main interface, click the Restore icon.
2. Select the backup set that you would like to restore the guest virtual machine from.
3. Select the local, mapped drive, or removable drive storage destination that contains Hyper-
V guest virtual machine that you would like to restore.
4. Select Restore virtual machines as the restore mode.
www.bobcloud.net 69
5. Select to restore the Hyper-V guest from a specific backup job then select the files or
folders that you would like to restore. Click Next to proceed.
6. Select to restore the Hyper-V guest VM to the Original location, or to an Alternate
location. Then select Run Direct and Auto migrate after Run Direct is running and click
Next to proceed.
Original location – The Hyper-V guest VM will be restored to the same directory path
which stores the backup source on the original Hyper-V host.
Alternate location – The Hyper-V guest VM will be restored to the different directory
path on the original Hyper-V host.
Click Next to proceed and the following values are needed to be update:
i. Virtual Machine Name
ii. Virtual Machines Directory Location (guest configuration files)
iii. Restore As (new location for the guest VHD files)
Example:
i. Rename the restored guest VM to “CentOS 6.4-1
ii. Store the configuration files in the new location “D:\Virtual
Machines\CentOS6.4\CentOS 6.4\
iii. Store the VHD files in the new location “D:\Virtual Machines\CentOS6.4\
www.bobcloud.net 70
When the values have been updated click on Next to proceed.
7. Confirm the temporary directory path is correct and then click Restore to proceed.
8. If the guest virtual machine selected to be restore already exists on the Hyper-V server
AhsayOBM will prompt to confirm overwriting of the existing guest.
Yes - the exiting guest virtual machine will be deleted from the Hyper-V server before
the restore process starts.
No – the restore of the current guest virtual machine will be skipped.
www.bobcloud.net 71
9. After the Hyper-V guest virtual machine has been restored, you will see the following
screen.
10. Go to the Hyper-V server and open the Hyper-V Manager to verify the guest has been
restored and is powered on.
11. Connect to the guest virtual machine to verify if is running correctly.
Example: Linux guest
www.bobcloud.net 72
Different (Standby) Hyper-V Host
This restore option allows you to restore your backed up guest VM to another Hyper-V host, for
example if your original Hyper-V host is down and you need to restore your production guest VM’s to
a standby Hyper-V host.
Please refer to the Requirements and Limitations for the details about requirements and limitations
for restoring Hyper-V guest VM to another Hyper-V host.
Start up a guest VM from Backup Destination without Auto Migration
Enabled
Follow the steps below to start up the guest VM directly from the backup files.
1. On the machine you wish to restore Hyper-V guest VM, launch AhsayOBM and click the
Restore icon in the main interface.
2. Select the backup set that you would like to restore the guest virtual machine from.
3. Select the local, mapped drive, or removable drive storage destination that contains Hyper-
V guest VM that you would like to restore.
www.bobcloud.net 73
4. Select Restore virtual machines as the restore mode.
5. Select to restore the Hyper-V guest VM from a specific backup job then select the files or
folders that you would like to restore. Click Next to proceed.
6. Select to restore the Hyper-V guest VM to the Original location, or to an Alternate
location. Then select Run Direct and click Next to proceed.
Original location – The Hyper-V guest VM will be restored to the same directory path
which stores the backup source on the original Hyper-V host.
www.bobcloud.net 74
Alternate location - The Hyper-V guest VM will be restored to the different directory
path on the original Hyper-V host.
Note: For restore to an alternate Hyper-V Host with a different CPU architecture, the
AhsayOBM client application must be version 7.15.6.0 or above.
Click Next to proceed and the following values are needed to update:
i. Virtual Machine Name
ii. Virtual Machines Directory Location (guest configuration files)
iii. Restore As (new location for the guest VHD files)
Example:
i. Rename the restored guest VM to “CentOS 6.4-1
ii. Store the configuration files in the new location “D:\Virtual
Machines\CentOS6.4\CentOS 6.4\
iii. Store the VHD files in the new location “D:\Virtual Machines\CentOS6.4\
When the values have been updated click on Next to proceed.
7. Confirm the temporary directory path is correct and then click Restore to proceed.
8. If the guest virtual machine selected to be restored already exists on the Hyper-V server,
AhsayOBM will prompt to confirm overwriting of the existing guest.
www.bobcloud.net 75
Yes - the exiting guest virtual machine will be deleted from the Hyper-V server before
the restore process starts.
No – the restore of the current guest virtual machine will be skipped.
9. After the Hyper-V guest virtual machine has been restored, you will see the following
screen.
10. Go to the Hyper-V server and open the Hyper-V Manager to verify the guest VM has been
restored and is powered on.
11. Connect to the guest virtual machine to verify if is running correctly.
www.bobcloud.net 76
Example: Linux guest
Migrate Virtual Machine (Permanently Restore)
To permanently restore the guest virtual machine after starting up using the Run Direct option,
you will still need to migrate it to from the backup destination to the designated permanent location
on the Hyper-V server using the Migrate Virtual Machine option. This process can be performed
even when the guest machine is already running.
1. After starting up the guest machine from the backup destination. Click on Close.
www.bobcloud.net 77
2. Click on Manage Run Direct virtual machines.
3. Click on the guest virtual machine.
4. To permanently restore the guest virtual machine, click on Migrate Virtual Machine.
www.bobcloud.net 78
Note
AhsayOBM will begin migration of the guest virtual machine from the backup destination to the
Hyper-V Server.
The guest VM can be used during the migration process. Any changes made in the guest VM
environment is saved in transaction logs and will be applied when the migration process is
completed.
When finalizing the restore, during the application of changes in transaction logs with the restored
guest VM, the guest VM will be put into saved state temporarily. Once the changes have been
applied the guest virtual machine resume.
www.bobcloud.net 79
Stop Run Direct Virtual Machines
To stop running guest virtual machines started up using Run Direct can be done by either:
Quitting AhsayOBM
-OR-
Click on the Stop Run Direct button at the left bottom corner.
Click on Stop all Run Direct virtual machines.
Note
When a guest virtual machine started in a Run Direct instance is stopped, any changes
made within the guest environment will be lost, if the guest virtual is not migrated to the
Hyper-V Server using the “Auto migrate after Run Direct is running” option.
www.bobcloud.net 80
Start up a guest VM from Backup Destination with Auto Migration
Enabled
Follow the steps below to start up the guest VM directly from the backup files.
1. On the machine you wish to restore Hyper-V guest VM, launch AhsayOBM and click the
Restore icon in the main interface.
2. Select the backup set that you would like to restore the guest virtual machine from.
3. Select the local, mapped drive, or removable drive storage destination that contains Hyper-
V guest virtual machine that you would like to restore.
www.bobcloud.net 81
4. Select Restore virtual machines as the restore mode.
5. Select to restore the Hyper-V guest from a specific backup job then select the files or
folders that you would like to restore. Click Next to proceed.
6. Select to restore the Hyper-V guest VM to the Original location, or to an Alternate
location. Then select Run Direct and Auto migrate after Run Direct is running and click
Next to proceed.
Original location – The Hyper-V guest VM will be restored to the same directory path
which stores the backup source on the original Hyper-V host.
www.bobcloud.net 82
Alternate location – The Hyper-V guest VM will be restored to the different directory
path on the original Hyper-V host.
Click Next to proceed and the following values are needed to be update:
i. Virtual Machine Name
ii. Virtual Machines Directory Location (guest configuration files)
iii. Restore As (new location for the guest VHD files)
Example:
i. Rename the restored guest VM to “CentOS 6.4-1
ii. Store the configuration files in the new location “D:\Virtual
Machines\CentOS6.4\CentOS 6.4\
iii. Store the VHD files in the new location “D:\Virtual Machines\CentOS6.4\
When the values have been updated click on Next to proceed.
7. Confirm the temporary directory path is correct and then click Restore to proceed.
8. If the guest virtual machine selected to be restore already exists on the Hyper-V server
AhsayOBM will prompt to confirm overwriting of the existing guest.
Yes - the exiting guest virtual machine will be deleted from the Hyper-V server before
the restore process starts.
www.bobcloud.net 83
No – the restore of the current guest virtual machine will be skipped.
9. After the Hyper-V guest virtual machine has been restored, you will see the following
screen.
10. Go to the Hyper-V server and open the Hyper-V Manager to verify the guest has been
restored and is powered on.
11. Connect to the guest virtual machine to verify if is running correctly.
Example: Linux guest
www.bobcloud.net 84
11 Non-Run Direct Restore
Original Hyper-V Host
Restore of Guest VM to the Original Hyper-V Host (Original Location)
1. In the AhsayOBM main interface, click the Restore icon.
2. Select the backup set that you would like to restore the guest virtual machine from.
3. Select the CBS, cloud, SFTP/FTP or drive storage destination that contains Hyper-V guest
virtual machine that you would like to restore.
Example: Restore from D:\ drive
Example: Restore from AhsayCBS
4. If the backup set is created with Run Direct feature or Granular Restore feature enabled,
the following step will show. Select Restore virtual machines as the restore mode.
www.bobcloud.net 85
5. Select to restore the Hyper-V guest from a specific backup job then select the files or
folders that you would like to restore. Click Next to proceed.
6. Select to restore the Hyper-v guest VM to the Original location.
For backup set without Run Direct feature enabled:
For the backup set with Run Direct feature enabled, uncheck the box of Run Direct and
then click Next to proceed.
www.bobcloud.net 86
7. Confirm the temporary directory path is correct and then click Restore to proceed.
8. If the guest virtual machine selected to be restored already exists on the Hyper-V server
AhsayOBM will prompt to confirm overwriting of the existing guest.
Yes - the exiting guest virtual machine will be deleted from the Hyper-V server before
the restore process starts.
No – the restore of the current guest virtual machine will be skipped.
9. After the Hyper-V guest virtual machine has been restored.
10. Go to the Hyper-V server and open the Hyper-V Manager to verify the guest has been
restored and power on the guest virtual machine.
www.bobcloud.net 87
11. Connect to the guest virtual machine to verify if is running correctly.
Example: Linux guest
www.bobcloud.net 88
Restore of Guest VM to the Original Hyper-V Host (Alternate Location)
This feature will restore any guest VM to another location (a different disk or folder) on the same
Hyper-V host. The Restore to Alternate location can be used to restore only one guest virtual
machine at any one time.
1. In the AhsayOBM main interface, click the Restore icon.
2. Select the backup set that you would like to restore the guest virtual machine from.
3. Select the CBS, cloud, SFTP/FTP or drive storage destination that contains Hyper-V guest
virtual machine that you would like to restore.
Example: Restore from D:\ drive
Example: Restore from AhsayCBS
www.bobcloud.net 89
4. If the backup set is created with Run Direct feature or Granular Restore feature enabled,
the following step will show. Select Restore virtual machines as the restore mode.
5. Select to restore the Hyper-V guest from a specific backup job then select the files or
folders that you would like to restore.
6. Select to restore the Hyper-v guest VM to the Alternate location.
For backup set without Run Direct feature enabled:
For the backup set with Run Direct feature enabled, uncheck the box of Run Direct and
then click Next to proceed.
Click Next to proceed and the following values are needed to be update:
www.bobcloud.net 90
i. Virtual Machine Name
ii. Virtual Machines Directory Location (guest configuration files)
iii. Restore As (new location for the guest VHD files)
Example:
i. Rename the restored guest VM to “CentOS 6.4-1
ii. Store the configuration files in the new location “D:\Virtual
Machines\CentOS6.4\CentOS 6.4\
iii. Store the VHD files in the new location “D:\Virtual Machines\CentOS6.4\
When the values have been updated click on Next to proceed.
7. When the values have been updated click on Next to proceed. Confirm the temporary
directory path is correct and then click Restore to proceed.
8. After the Hyper-V guest virtual machine has been restored successfully
9. Open Windows File Explorer and verify the guest has been restored to the new location.
www.bobcloud.net 91
Different (Standby) Hyper-V Host
Restore of a Guest VM to a Different (Standby) Hyper-V Host
This restore option allows you to restore your backed up guest VM to another Hyper-V host, for
example if your original Hyper-V host is down and you need to restore your production guest VM’s
to a standby Hyper-V host.
Please refer to the Requirements and Limitations for the details about requirements and limitations
for restoring Hyper-V guest VM to another Hyper-V host.
1. On the machine where you wish to restore the VM, launch AhsayOBM and click the
Restore icon on the main interface.
2. Select the backup set that you would like to restore the guest virtual machine from.
3. If encryption key was set at the time when the backup set was created, enter the encryption
key when you see the following prompt.
4. Select the CBS, cloud, SFTP/FTP or drive storage destination that contains Hyper-V guest
virtual machine that you would like to restore.
www.bobcloud.net 92
Example: Restore from D:\ drive
Example: Restore from AhsayCBS
5. If the backup set is created with Run Direct feature or Granular Restore feature enabled,
the following step will show. Select Restore virtual machines as the restore mode.
www.bobcloud.net 93
6. Select to restore the Hyper-V guest from a specific backup job then select the files or
folders that you would like to restore.
7. Select to restore the Hyper-V guest VM to the Original location, or to an Alternate
location. Then click Next to proceed.
Original location – The Hyper-V guest VM will be restored to the same directory path
which stores the backup source on the original Hyper-V host.
For backup set without Run Direct feature enabled:
For the backup set with Run Direct feature enabled, uncheck the box of Run
Direct and then click Next to proceed.
Alternate location – The Hyper-V guest VM will be restored to the different directory
path on the original Hyper-V host.
Note: For restore to an alternate Hyper-V Host with a different CPU architecture, the
AhsayOBM client application must be version 7.15.6.0 or above
For backup set without Run Direct feature enabled:
www.bobcloud.net 94
For the backup set with Run Direct feature enabled, uncheck the box of Run
Direct and then click Next to proceed.
Click Next to proceed and the following values are needed to be update:
i. Virtual Machine Name
ii. Virtual Machines Directory Location (guest configuration files)
iii. Restore As (new location for the guest VHD files)
Example:
i. Rename the restored guest VM to “CentOS 6.4-1
ii. Store the configuration files in the new location “D:\Virtual
Machines\CentOS6.4\CentOS 6.4\
iii. Store the VHD files in the new location “D:\Virtual Machines\CentOS6.4\
When the values have been updated click on Next to proceed.
8. Confirm the temporary directory path is correct and then click Restore to proceed.
9. Click Restore to start the restore process.
www.bobcloud.net 95
10. The following screen shows when the restore is completed.
11. Go to the Hyper-V server and open the Hyper-V Manager to verify the guest has been
restored.
12. Connect to the guest virtual machine to verify if is running correctly.
Example: Linux guest
www.bobcloud.net 96
Individual Virtual Disk Restore
Restore of an Individual Virtual Disk to Original/Different Guest VM
The Restore raw file feature is used to the restore of an individual virtual disk to the original or a
different guest VM.
1. In the AhsayOBM main interface, click the Restore icon.
2. Select the backup set that you would like to restore the guest virtual machine from.
3. Select the CBS, cloud, SFTP/FTP or drive storage destination that contains Hyper-V guest
virtual machine that you would like to restore.
Example: Restore from D:\ drive
Example: Restore from AhsayCBS
www.bobcloud.net 97
4. If the backup set is created with Run Direct feature or Granular Restore feature enabled,
the following step will show. Select Restore virtual machines as the restore mode.
5. Select to restore the Hyper-V guest from a specific backup job then select the files or
folders that you would like to restore.
6. Then select the Restore raw file option and under the Virtual Hard Disks folder select the
virtual disk you would like to restore. Click Next to proceed.
www.bobcloud.net 98
7. Select to location on the Hyper-V server you want to restore the virtual disk to. Click Next
to proceed.
8. Confirm the temporary directory path is correct and then click Restore to proceed.
9. After the Hyper-V guest virtual machine has been restored.
www.bobcloud.net 99
10. In Hyper-V Manager, right click on the guest virtual machine you wish to add the virtual disk
to and select Settings.
11. Select Add to add virtual disk to the guest virtual machine.
www.bobcloud.net
100
12. Click on Browse to choose the according vhd file.
13. Select the folder where the restore virtual disk is located.
14. After the virtual disk is added. Start the guest virtual machine to confirm. Depending on
the guest operating system there may be other configuration settings to be completed
before the disk is available.
www.bobcloud.net
101
12 Granular Restore
IMPORTANT
Before you proceed with the Granular Restore, make sure the following dependencies are fulfilled
on the restore machine. Failure to do so may 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
Microsoft Security Advisory 3033929 (for Windows Server 2008 R2)
https://technet.microsoft.com/en-us/library/security/3033929.aspx
Requirements and 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.
www.bobcloud.net
102
Start Granular Restore
1. Click the Restore icon on the main interface of AhsayOBM.
2. Select the backup set that you would like to restore the individual files from.
3. Select the backup destination that contains the guest VM that you would like to restore.
www.bobcloud.net
103
4. Select to the Restore individual files in virtual machine (Granular Restore) option.
Note
The Mount virtual disks automatically option is selected by default. If the guest VM
contains a multiple virtual disks and you only require the restore of files from a single or
certain virtual disk(s), then unselect this option to speed up the virtual disk mounting.
Otherwise, granular restore will connect and mount all available virtual disks and this
process could take longer.
You may select the Read timeout limit by clicking Show advanced option.
This selection defines the duration when the granular restore session will be disconnected
if there is no response from the mounted virtual machine.
DefaultThis setting should be suitable for guest VMs located on a local, removable,
or network drive. The time out value is 15 seconds.
Unlimited – the connection will not be time out when this is selected. This selection is
recommended when:
Backup destination is a cloud stroage.
AhsayCBS over the Internet.
A large guest VM or guest VM with large incremental delta chain.
Note
If in doubt or unsure about the guest VM size or network stability, it is recommended
to use Unlimited.
Click Next to proceed when you are done with the selection.
www.bobcloud.net
104
5. Select the virtual machine that you would like to perform Granular Restore for, then click
Next to proceed.
6. Select a temporary directory for storing restore files, then click Restore to start the granular
restore.
7. The following screens show when you perform granular restore for a backup set on a
machine for the first time only. Make sure you click Yes to confirm mounting t of the virtual
disk on this machine. Clicking No will exit the restore process.
8. When the virtual disk(s) are in the process of being prepared for mounting on the
AhsayOBM machine, you will see the following screen.
Please wait as the process could take some time depending on the size of the virtual disk,
network bandwidth, and storage location.
www.bobcloud.net
105
9. If the Mount virtual disks automatically option is unselected then click on the disk icon to
mount the virtual disk you wish to restore files from.
Otherwise, the virtual disks will be automatically mounted.
There are two options to restore individual files from here.
Option 1: Restore Using AhsayOBM File Explorer
This method allows you to use the file explorer in AhsayOBM to browse through the files
from the mounted virtual disk and select files you wish to restore.
i. Click to browse the files in the mounted virtual disk. If there are multiple
volumes in the guest VM, you can only select one volume to restore individual
files at a time.
www.bobcloud.net
106
You will then see a file explorer menu as shown below. Select the file(s) you wish
to restore, then click Next to proceed.
Note
Some system folder(s) / file(s) generated (e.g. System Volume Information) are only shown
in the AhsayOBM File Explorer and will be not restored, therefore, those folder(s) / file(s)
will not be shown in the mapped drive shown in step iv below.
ii. Select a path where you wish the files to be restored to, then click Restore.
iii. The following screen shows when the selected files have been restored to the
defined destination.
www.bobcloud.net
107
iv. Open the defined restore path and you should be able to see the files being
restored there.
Option 2: Restore Using Windows File Explorer
This method allows you to browse through the files from the mounted virtual disk through
the file explorer on the machine where you have AhsayOBM installed on.
Note
Granular restore of Hyper-V backup sets performed using Windows File Explorer :
1. Will not show up on the [Restore Status] tab in Live Activities of the backup service provider
AhsayCBS.
2. Will not generate restore reports on backup service provider AhsayCBS.
3. Will not generate restore log on AshayOBM.
i. Click and then you will be prompted to select a driver letter where you wish
the mounted image to be mapped on your machine, click OK when you have
finished selection.
ii. The selected drive letter will be mapped and prompted in the Windows Files
Explorer with the files you wish to restore shown.
www.bobcloud.net
108
iii. You can now click on the files to view them directly from here, which will be in
read-only mode, or copy them to your local machine.
iv. The mounted drive letter cannot be ejected from the Windows File Explorer, it will
only be closed when you exit AhsayOBM.
10. When you have finished restoring the necessary files, you can go back to AhsayOBM and
click on Cancel.
www.bobcloud.net
109
11. Then click on Stop the granular restore and unmount the virtual disk(s).
Important
Due to the limitation of the virtual file system library, the mounted virtual disks will only be unmounted from your
machine when you exit AhsayOBM.
www.bobcloud.net
110
13 Contact Ahsay
Technical Assistance
To contact Ahsay support representatives for technical assistance, visit the following website:
https://www.ahsay.com/jsp/en/contact/kbQuestion.jsp
Also use the Ahsay Knowledge Base for resource such as Hardware Compatibility List, Software
Compatibility List, and other product information:
http://wiki.ahsay.com
Documentation
Documentations for all Ahsay products are available at:
https://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_downloads_documentation
_guides
You can send us suggestions for improvements or report on issues in the documentation, by
contacting us at:
https://www.ahsay.com/jsp/en/contact/kbQuestion.jsp
Please specify the specific document title as well as the change required/suggestion when
contacting us.