Copy data management requirements and considerations
Review the following requirements and considerations before proceeding to Copy data management procedures to create and run data copy access jobs.
Licensing requirements
Data copy access jobs are only enabled on Enterprise Plus licensed appliances. If you are interested in this feature, contact your sales representative or email sales@unitrends.com.
Note: Upon trial license expiration, data copy access UI objects no longer display.
Supported asset types
Data copy access jobs support image-level backups, host-level backups of VMware and Hyper-V VMs, as well as any replicas located on the host. Replicas located on the backup appliance are not supported. For more information on replicas, see VM replicas and Windows replicas.
Virtual host configuration
You must configure an isolated test network on your hypervisor prior to running tests and standing up instant labs. Failure to contain tests and instant labs within this VM network may allow them to interfere with your production VMs.
|
•
|
When creating a test network on a VMware host, do not assign a physical adapter to the standard switch. |
|
•
|
When creating a test network on a Hyper-V server, use the internal virtual switch type. |
VMware requirements and considerations
Review the following requirements and considerations before including VMware VMs in your data copy access jobs.
VMware basic requirements
All requirements for VM instant recovery as defined in Preparing for instant recovery must be met.
vSphere versions earlier than 5.5 are not supported.
The following must be installed or configured before taking the first backup intended for inclusion in data copy access jobs:
|
•
|
VMware Tools must be installed on the VM. |
|
•
|
Powershell version 3.0 or later must be installed on VMs that are running Windows as a guest OS. |
|
•
|
User Account Control must be disabled on VMs that are running Windows as a guest OS. |
|
•
|
.NET framework version 2.0 or later must be installed on VMs that are running Windows as a guest OS. |
|
•
|
Guest OS credentials must be configured for administrator-level privileges on the VM and added to the backup appliance. For further information on managing credentials, see Managing protected assets. |
|
•
|
For Active Directory domain controllers, guest OS credentials must be configured to use the local system administrator account. A user that is part of the domain administrator group is not sufficient. To run NTDS tests, the local system administrator account is required. |
VMware additional considerations
|
•
|
Failover jobs can only be committed on hosts that are managed by a vCenter. |
|
•
|
Re-IP functionality for Linux VMs requires ifconfig. ifconfig is not installed by default on minimal operating system versions. Be sure to install ifconfig to enable re-ip of these operating system versions by running this command: |
|
•
|
Additional requirements must be met to enable re-IP functionality for Windows 7 or Windows Server 2008 R2 VMs. See KB 5529 for further details. |
Hyper-V requirements and considerations
Review the following requirements and considerations before including Hyper-V VMs in your data copy access jobs.
Hyper-V basic requirements
All requirements for VM instant recovery as defined in Preparing for instant recovery must be met.
The following must be installed or configured before taking the first backup intended for inclusion in data copy access jobs:
|
•
|
Version 10.0.0-1 or later of the Unitrends Agent must be installed on the Hyper-V server. |
|
•
|
Hyper-V Integration Services must be installed and updated. |
|
•
|
Powershell version 3.0 or later must be installed on Windows VMs. |
|
•
|
User Account Control must be set to minimum on Windows VMs. |
|
•
|
.NET framework version 2.0 or later must be installed on Windows VMs. |
|
•
|
Guest OS credentials must be configured for administrator-level privileges on the VM and added to the backup appliance. For further information on managing credentials, see Managing protected assets. |
|
•
|
For Active Directory domain controllers, guest OS credentials must be configured to use the local system administrator account. A user that is part of the domain administrator group is not sufficient. To run NTDS tests, the local system administrator account is required. |
Hyper-V additional considerations
|
•
|
Re-IP and custom tests are not supported for Linux guests and Hyper-V/Windows Server versions earlier than 2012 R2. |
|
•
|
Re-IP functionality for Linux VMs requires ifconfig. ifconfig is not installed by default on minimal operating system versions. Be sure to install ifconfig to enable re-ip of these operating system versions by running this command: |
Image-level backup requirements and considerations
Review the following requirements and considerations before including image-level backups in your data copy access jobs:
Requirements and considerations for image-level backups on Hyper-V
|
•
|
Windows Server versions earlier than 2012 are not supported. |
|
•
|
Re-IP and custom tests are not supported for Hyper-V/Windows Server versions earlier than 2012 R2. |
|
•
|
If re-IP and custom test functionality is required, the data copy access Hyper-V agent must be installed on the asset before taking the first backup intended for inclusion in data copy access jobs. |
Replica requirements and considerations
Review the following requirements and considerations before including replicas in your data copy access jobs.
For further information on Windows replicas, see Windows replicas
For further information on VM replicas, see VM replicas
Requirements and considerations for Windows replicas on VMware
|
•
|
Windows Server versions earlier than 2008 are not supported. |
|
•
|
The host must be managed by a vCenter. |
|
•
|
Data copy access jobs that include Windows replicas and span two hosts require both hosts to be managed by the same vCenter. Windows replicas cannot be moved across hosts that are not managed by the same vCenter. |
|
•
|
If the Power On Timeout option is selected, it must be configured for longer than 20 minutes. |
Requirements and considerations for Windows replicas on Hyper-V
|
•
|
Powershell version 3.0 must be installed on Windows VMs. |
|
•
|
If the Power On Timeout option is selected, it must be configured for longer than 20 minutes. |
|
•
|
Hyper-V/Windows Server versions earlier than 2012 are not supported. |
|
•
|
If re-IP and custom test functionality is required, the data copy access Hyper-V agent must be installed on the Windows asset from which the replica is created. For instructions, see Installing the data copy access Hyper-V agent |
Note: Re-IP and custom tests are not supported for Windows replicas of Windows Server 2012 VMs hosted on Hyper-V/Windows Server 2012 R2 and later.
Installing the data copy access Hyper-V agent
To install the data copy access Hyper-V agent
|
2
|
Save the agent MSI file. |
|
3
|
Right click the installer file and select Run as administrator to start the setup wizard. |
|
4
|
From the first wizard screen, click Next. |
|
5
|
Click Finish when the installation completes. |
|
6
|
When successful setup is confirmed, click Close. |