Test VRanger | Page 27

Quest vRanger Installation/Upgrade Guide 27   Excessive network packet loss could result in replication failure.Replication will work with links having average packet loss of less than 2%. Replication is not designed to work in replication environments where packet loss can exceed commercially accepted limits.  3.3.1.b A continuous connection between source and target sites is required when replication is taking place. Networks having 99% Uptime/Availability will generally provide for good Replication performance. HotAdd In order to perform backup/restore/replication tasks using HotAdd, vRanger must be installed on a virtual machine. Additionally:   HotAdd only works on SCSI disks. IDE disks and vRDMs are not supported.  Datastores for the target virtual machines must be accessible to the vRanger VM.  vRanger can only perform operations on VMs within the same datacenter.  HotAdd cannot be used if the VMFS block size of the datastore containing the virtual machine folder for the target virtual machine does not match the VMFS block size of the datastore containing the vRanger VM. For example, if you back up a virtual disk on a datastore with 1MB blocks, the proxy must also be on a datastore with 1MB blocks.  3.3.2 HotAdd requires VMware Enterprise or higher licensing. HotAdd is not supported with VMware Standard licenses. Backing up thick disk requires the maximum disk size to be available. When backing up a thick disk, the vRanger VM’s datastore must have at least as much space available as the maximum configured disk size for the virtual machine to be backed up. File-Level Recovery - Windows In order to perform a file-level recovery from a windows VM, the VM must meet the following requirements:   3.3.3 The VMs must be using basic disks, The VMs must use an MBR partition. GPT partitions are not supported. File-Level Recovery - Linux Please review the information below in order to understand the functions and limitations of vRanger’s Linux file-level recovery feature  The source VM properties needs to show the OS type as Linux. If this is not configured properly, vRanger will not identify the savepoint as a Linux VM.  3.4.1 vRanger requires you to recover the Linux files to an intermediate Windows machine. When you recover Linux files to a Windows machine, you will lose the file permissions.  3.4.0 Linux file-level recovery requires the vRanger virtual appliance.  See for a list of supported file systems. Configuration Req uirements Supported Disk Types vRanger operates with some basic restrictions on the type of disks and partitions used in the environment. The sections below describe the limitations as they apply to specific features and functions. 3.4.1.a File-Level Recovery Disk Requirements In order to perform a file-level recovery from a windows VM, the VM must meet the following requirements: