vRanger Pro [P2VDR module with 12 months Support/Maintenance (3.2 base license required)]

vRanger Pro now provides a new feature, P2V Disaster Recovery, which is a safe, reliable way to capture image-level backups of any physical Windows server. A backup job can be configured for a physical server with just a few clicks with no disruption to the source machine. Also included is a new VSS driver that utilises Microsoft’s Volume Shadow Copy Service to enable quiesing of supported databases to provide transactionally consistent backup images to minimize the risk of lost data or data corruption.

• Performs entire image or partial differential backup
• Integrates with VCB to offload backups from the host
• Offers full VMware VirtualCenter integration
• Is VMotion aware to follow virtual machines when moved to new hosts
• Includes VSS driver to provide “transactionally consistent” backup images
• Compresses files so they can be sent overLANs/WANs to remote locations
• P2V Disaster Recovery for image-level backups of physical machines
• Includes database repository to capturetrending metrics
• Easily restore a virtual machine or files from within a virtual machine
• Improved compression means faster backups
• Startup wizard for even easier implementation

Unlike agents, vRanger Pro runs outside the guest OS, and can be integrated with VMware VirtualCenter for efficient backup management. Backups can now be offloaded from the host leveraging integration with VMware VCB. vRanger Pro is also VMotion aware so it can follow virtual machines to perform regularly scheduled backups even after they have
moved.

“Out-of-Box" Administration

A policy-based rules engine allows administrators to set up the logic, interdependencies and frequency of backups for optimum results. A database repository gathers critical trending metrics to allow administrators to make informed adjustments to the backup process. Because vRanger Pro offers an easy-to-use Windows-based GUI and eliminates scripting, IT administrators do not require specialised knowledge to deploy a reliable backup strategy.

• Each physical CPU socket on ESX Host requires 1 CPU License (Quad CPU ESX Host requires 4 CPU Licenses.) Number of cores does not matter.

Support and Maintenance

• Each license requires support/maintenance - included in costs
• 1,2 and 3 year options avialable.
• Client is entititled to future upgrade and revisions of that SKU withi given support period.
• End User is required to renew support after period has expired or they incur fees on a case by case basis. Cost very minimal.