1 / 12

Quest vRanger / Architecture

Quest vRanger / Architecture. Backup and Restore Types. Network backups for ESX – Direct to target Network backups for ESXi –vRanger as a Proxy LAN Free or Fiber/iSCSI backups for ESX and ESXi –vRanger proxy on Physical server attached to VMFS Datastores

tangia
Download Presentation

Quest vRanger / Architecture

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Quest vRanger / Architecture

  2. Backup and Restore Types • Network backups for ESX – Direct to target • Network backups for ESXi –vRanger as a Proxy • LAN Free or Fiber/iSCSI backups for ESX and ESXi –vRanger proxy on Physical server attached to VMFS Datastores • Hot Add backups – vRanger installed on a VM

  3. vRanger Pro 5.2 Architectural Options Hot Add SourceVM VM Source.vmdk

  4. ESX Network Backups

  5. ESX Network backups Benefits Considerations Service Console NIC can be limiter Consider using 2nd SC NIC to isolate backup traffic Multiple concurrent jobs can saturate moderate storage devices (sata disks, controllers, interfaces) – use resource manager to adjust # of tasks Performs better with a larger number of ESX servers that are less VM/data dense • Simplest way to deploy vRanger with ESX hosts • Uses “Direct to Target” • Works with vRanger as a VM or as a physical server • Generally works well in small environments and with dedup appliances for repository

  6. ESXi network backups • vStorage API running from vRanger server connects to ESXi host and requests a snapshot to be made • Data travels out from ESXi host to vRanger uncompressed, vRanger compresses, and sends it to the repository

  7. ESXi Network backups Benefits Considerations ESXi Mgmt NIC can be limiter Consider using 2nd Mgmt NIC to isolate backup traffic The entire VM must be copied each time to vRanger No “Direct to Target” • Simplest way to deploy vRanger with ESXi hosts • Works with vRanger as a VM or as a physical server • Backups are streamed to vRanger for white-space removal and compression, then sent to repository • Generally works well in small environments

  8. LAN Free (Fibre or iSCSI) backups • vStorage API running from • vRanger server connects to • ESX(i) host and requests a • snapshot to be made • vStorage API running from vRanger server reads VM disks and writes archives to repository. vRanger acts as proxy.

  9. LAN Free (Fibre or iSCSI) backups Benefits Considerations Do NOT initialize the VMFS datastores from your vRanger server! Scalability will also depend on # of cpu cores, amount of memory, and bandwidth to repositories. • Leverages investment and performance of your SAN • Isolates backup traffic to SAN • Performs very well • Can add additional HBAs or NICs to backup server to increase performance and scalability

  10. Hot Add backups • vRanger server connects to • ESX(i) host and requests a • snapshot to be made. SourceVM VM • vRanger server reads VM disks, removes whitespace, performs compression and/or encryption, and writes archives to repository. Source.vmdk

  11. Hot Add backups Benefits Considerations Disable auto mount on vRanger server Add 2nd SCSI controller to VM Scalability will also depend on # of cpu cores, amount of memory, and bandwidth to repositories. • Simple to deploy and configure • vRanger server must be a VM • Read speeds @ native VM performance

  12. Lets Choose What's right for you !!! Thank You

More Related