Test VRanger | Page 23

Quest vRanger Installation/Upgrade Guide 3.1.1.a 23 vRanger - Physical Machine The hardware recommendations for the vRanger physical machine are described below. CPU Any combination equaling 4 cores of CPUs are recommended. Example 1 quad-core CPU; 2 dual-core CPUs. RAM  4GB RAM is required. Storage  At least 4 GB free hard disk space on the vRanger machine. HBA 3.1.1.b   For LAN-Free, it is recommended to use two HBAs - one for read operations and one for writing. vRanger - Virtual Machine The hardware recommendations for using vRanger in a virtual machine are described below. CPU Four (4) vCPUs. RAM  4 GB RAM is recommended. Storage 3.1.2   At least 4 GB free hard disk space on the vRanger machine. Supported Operating Systems For Installation The following operating systems are supported for installation of vRanger. Operating System Service Pack Level Bit Level Windows Vista Business SP 2 (x86 or x64) Windows 7 SP 1 (x86 or x64) Windows 8 (x86 or x64) Windows Server 2008 Windows Server 2008 R2 SP 2 a (x86 or x64) SP 1 (x64) Windows Server 2012b (x64) a.Windows Storage Server 2008 is not supported as an installation platform for vRanger. b.SQL Express 2005 is not supported on Windows Server 2012. 3.1.2.a Additional Required Software In addition to a supported version of Windows and a supported VMware infrastructure, you may need some additional software components, depending on your configuration.  Microsoft .Net Framework - vRanger requires the .Net Framework 3.5 SP1. The vRanger installer will install it if not detected.  SQL Server [optional]- vRanger utilizes two SQL databases for application functionality. vRanger can install a local version of SQL Express 2005 or you can chose to install the vRanger databases on your own SQL 2005 or 2008 instance.  vRanger Virtual Appliance - The vRanger virtual appliance is a small, pre-packaged Linux distribution that servers as a platform for vRanger operations away from the vRanger server. vRanger uses the virtual appliance for the functions below:  replication to and from ESXi hosts  file-level recove ry from Linux machines  optionally for backups and restores.