The following information covers both the requirements and prerequisites for Windows instant recovery (WIR).
The following topics cover the necessary requirements for different types of VFCs:
Requirement |
Description |
---|---|
Unitrends system resources |
VFC uses part of the Unitrends appliance’s processors, memory, and storage. This usage may impact the performance of regular system functions (such as backups, backup copies, deduplication, and purging). Monitor the appliance closely and make adjustments as necessary. |
On-system retention |
On-system retention is reduced because a portion of the appliance’s storage is reserved for the VFC. |
Use case for the VFC |
Use temporarily until you can get new hardware and run bare-metal recovery. |
UEFI-based assets |
Cannot recover UEFI-based assets. |
GPT-partitioned assets |
Cannot recover GPT-partitioned assets. |
Requirement |
Description |
|||||||||
---|---|---|---|---|---|---|---|---|---|---|
Hypervisor version |
|
|||||||||
Compute |
One VFC requires a minimum of 1024 MB of memory. This number must be a multiple of 4. |
|||||||||
VFC client changeability |
Once configured, do not change the VFC. Any alteration to the VFC (unless it is in Live mode) may lead the VFC to an inconsistent state. |
|||||||||
Storage |
Size of VFC is capped by what the hypervisor supports. If you configure the VFC with disks larger than 2 TB, the ESXi server must run version 5.5 or higher. |
|||||||||
Virtual hardware version |
The VFC is configured with the highest hardware version that the hypervisor supports. |
|||||||||
Virtual host asset |
The ESXi host must be added to the appliance as an asset. See Managing protected assets. |
Requirement |
Description |
||||||
---|---|---|---|---|---|---|---|
Hypervisor version |
|
||||||
Host agent version |
|
||||||
Compute |
One VFC requires a minimum of 1024 MB of memory (must be a multiple of 4). |
||||||
VFC client changeability |
Once configured, do not change the VFC. Any alteration to the VFC (unless it is in Live mode) may lead the VFC to an inconsistent state. |
||||||
Storage |
The size of the VFC is capped by what the hypervisor supports. The appliance creates a VFC with a disk of the same size as the disk on the original client. For Windows clients with disks larger than 2 TB, create the VFC on Hyper-V server version 2012 or higher. Create a VFC on Hyper-V server 2008 R2 with a VHD. Create a VFC on server version 2012/2012 R2 with a VHD(X). |
||||||
VFC virtual machine generation |
The client's firmware interface type determines the generation of the VFC VM. VFCs for BIOS-based clients are created as generation 1 VMs, and VFCs for UEFI-based clients are created as generation 2 VMs. A VFC for a UEFI-based client can run only on Hyper-V server version 2012 R2. |
||||||
Passthrough disks |
VFCs support pass-through disks. After booting the VFC in live mode and configuring the network settings, you must refresh and reconnect any existing iSCSI targets on the client. |
||||||
Virtual host asset |
The Hyper-V host must be added to the appliance as an asset. See Managing protected assets. |
Requirement |
Description |
---|---|
Registration |
A VFC can run on a server in a cluster configuration. You must first install Unitrends Windows agent version 8.0 or higher on each node and then add each node and the cluster to the appliance from which you will create the VFC. Every node in the cluster must have the same agent version installed. |
VFC location selection |
To create a clustered VFC, select the cluster when specifying the location for the VFC. You cannot specify an owner node. If you select an individual node in the cluster, the VFC will not be clustered. |
Network switch selection |
For a clustered VFC, select the network switch common to all nodes in the cluster. If you do not select this switch, a VFC in live mode that fails over to another cluster will lose network connectivity. |
2008 R2 clusters |
To run the VFC on 2008 R2 servers in a cluster configuration, enable DCOM and WMI Virtualization access for all nodes in the cluster. For instructions, see KB 1140. |
Live migration interoperability |
During live migration of a clustered VFC, the Unitrends appliance cannot restore to the VFC, verify or audit the VFC, or boot it in live mode. If a restore or verify attempt takes place during a live migration, the appliance waits several minutes and then attempts the operation again. If you try to boot the VFC in audit or live mode during a live migration, the appliance notifies you that it cannot run the operation because of the migration and prompts you to attempt the operation again later. |
The Windows server must meet the following requirements to use WIR:
Requirement |
Description |
|||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Client Operating Systems |
Notes:
|
|||||||||||||||||||||
Server Operating Systems |
Note: A VFC running Windows Server 2012 or higher cannot reside on Hyper-V server 2008 R2. |
|||||||||||||||||||||
Applications |
The following limitations apply:
|
|||||||||||||||||||||
Firmware interface type |
WIR supports BIOS- and UEFI-based clients. Meet the following requirements to create a VFC for a UEFI-based client:
|
|||||||||||||||||||||
Disk configuration |
WIR supports Windows machines configured with basic disks and dynamic disks, as long as the boot and system disks are not dynamic. The following types support dynamic volumes configured as data volumes:
Notes:
|
|||||||||||||||||||||
Disk partition type |
WIR protects Master Boot Record (MBR) partition types. GUID Partition Table (GPT) disks are supported with the following limitations:
|
|||||||||||||||||||||
Number of volumes |
A client protected by WIR can have a maximum of 20 volumes, including the System Reserved volume and other unmounted volumes. A VFC created for a client with more than 20 volumes may fail to boot. |
|||||||||||||||||||||
Separate boot and system partitions |
For protected assets with boot and system partitions located on different disks, the system partition must reside on the first disk (Disk 0). |
|||||||||||||||||||||
File System Configuration |
WIR supports the following file systems:
|
|||||||||||||||||||||
Active Directory |
WIR supports an Active Directory database (NTDS) on the boot volume. (If it is not on the boot volume, the configuration is not supported, and you see an error message when you add the VFC.) |
Depending on the identity of the appliance (backup system or replication target), you can allocate storage among backups/replication, vaulting, and instant recovery. You cannot use resources allocated for a VFC for other purposes, such as backups, archives, or deduplication.
Note: This procedure is only required for on-host instant recovery on the Recovery-Series appliance.
Before allocating storage, note the following:
• | The system load and use. |
• | The amount of storage on the asset. To determine the storage amount to allocate for instant recovery on the appliance, figure the sum of space in use on all the original clients (for which you want to create VFCs). To determine the amount of space in use on an asset, select the computer window, and view the disks. |
1 | On the Configure > Appliances page, select the Storage tab. |
2 | Select the Internal storage and click Edit. |
3 | Modify the percent of storage allocated for backups versus the percent of storage allocated for instant recovery, and click Save. |
Periodically back up clients and applications you want to protect with WIR. You do not have to create a special schedule for clients that WIR protects. If you implement WIR for a client that a backup schedule already protects, it does not produce a conflict. The existing schedule will continue to function.
Unitrends recommends you use an incremental forever schedule, but any schedule with periodic full and differential backups, or periodic full and incremental backups, will work. For more details, see Backups.
For a SQL server protected by WIR, the recommended strategy uses a combination of SQL Full and Transaction Log backups. For more details, see SQL backup requirements and considerations.
For Microsoft Exchange application backups, the recommended strategy comprises a combination of full and incremental backups. For more details, see Exchange backup requirements and considerations.
Once you have created the VFC, WIR restores completed backups to that VFC, so the VFC stays current.