esxRanger™ is a point in time hot backup tool. esxRanger will create point in time backups of VMware® ESX Server guest operating systems. This is a very important step in your backup, change control and disaster recovery strategy. esxRanger has made it easy to backup online VMware ESX Server guest operating systems (.VMDK files).

esxRanger SE’s CLI is the command line interface.
esxRanger SE’s GUI is the graphical user interface.

Q: How do get a trial copy of esxRanger?
A: Download a trial copy of esxRanger from our downloads section. A trial version is good for 60 days and 10 CPUs.

Q: What is installed and where?
A: Install Location: esxRanger can be installed on local administrators workstation or a centrally accessible (via RDP) server or workstation with a gigabit network card (preferred). Recommended Location: Install esxRanger on your local PC for change control (point in time) backups and install esxRanger on a centralized server to schedule automated recurring backups. On the centralized server, use a gigabit network card if you will be using the server as a proxy (sending to a Windows destination).

Q: Is there an agent installed?
A: No. There are NO agents that need to be installed to the ESX Host Server.

Q: What privileges do I need for the installation of esxRanger?
A: Though local system administrator access is not required, it is highly recommended to at least have the domain administrator privileges during installation and also to manage the backups using esxRanger.

Q: What platforms are supported for the software to reside on?
A: esxRanger requires Windows® 2000 or greater and the .NET Framework 1.1 or greater. ESX Host Server Requirements: VMware ESX Server version 2.0 or greater. virtual machine Guest OS Requirements: None for standard operation Windows OS for advanced service control option within esxRanger CLI VMtools running in the guest to use the esxRanger -migrate option and -poweroff option.

Q: Does esxRanger require VirtualCenter?
A: esxRanger works without the need for VirtualCenter. When you set up esxRanger to perform recurring backups, use the -allregistered option so no matter where you VMotion™ a virtual machine esxRanger will be able to back it up. Do not hard code VMs for backup by specifying the virtual machine directly unless you do not plan on VMotioning the VM. An esxRanger version with direct VirtualCenter support is forthcoming. This future version will add enhanced virtual machine tracking and security functionality.

Q: Are the esxRanger backups compressed?
A: esxRanger will compress your disks .VMDK files before sending them to the destination server of your choice. This destination server can be the local ESX Server VMFS, a Linux server or a Windows server. NAS, SAN, Novell, UNC and mapped drives are also supported if accessible by the Windows host.

Q: Does esxRanger support Windows shares?
A: The destination server can be the local ESX Server VMFS, a locally mounted share or LUN on the ESX Server Console OS, another ESX Server or Linux server or a Windows server or PC. Novell, NAS, SAN, iSCSI, Fibre Channel are also supported if they are seen by the Windows host running esxRanger.

Q: How much time do I need for learning esxRanger?
A: esxRanger is easy to use and will install in minutes. To use esxRanger, you should have a base level knowledge of VMware and a general understanding of how backups work. Once you have esxRanger installed, the GUI is intuitive enough that you will not require any training to use it. For any additional questions on use, please visit the documentation and other FAQs within this web site.

Q: Do I need to know scripting?
A: No. esxRanger has both a GUI and Command Line Interface. esxRanger runs on a Windows host and can be scheduled to perform online hot backups recurring or as needed. With esxRanger there is no need for complex scripting. esxRanger can be scheduled to run using the standard Windows scheduler. There are NO agents needed on the ESX Server or the guest operating systems.

Q: Should I use the CLI or GUI?
A: Most administrators will run the esxRanger GUI for change control backups and generate the appropriate CLI command (from the GUI) as needed. Scheduling the esxRanger CLI command (sometimes with minor parameter changes) for recurring backup usually follows next. For recurring backups, esxRanger CLI currently uses the standard Windows scheduler. A central scheduler is forthcoming. Just use the esxRanger GUI to create the command line and then copy the command to your scheduler at this time.

Q: Does esxRanger replace guest operating system backup agents?
A: No. At times esxRanger can replace these agents. For instance, Domain Controllers, DNS, DHCP, WINS, WEB Servers, Application Servers, Print Servers, etc. may no long need an operating system backup agent. On VMs with fast changing user data ie. File Servers, SQL, Exchange or Domino servers, you will want to continue to running an operating system backup agent. However, in this case, you will still want to backup these VMs regularly with esxRanger for quick restores and then proceed to restore and changed data since the last esxRanger backup from your tape or disk backup.