Quest vRanger backup and replication with vSAN datastores

Products

• VMware vSAN

Issue/Introduction

This article provides information about vRanger Backup & Replication 7.7.1.

Disclaimer: The partner solution referenced in this article is a solution developed and supported by a partner. Use of this product is also governed by the end user license agreement of the partner. You must obtain the application, support, and licensing for using this product from the partner. For more information, see https://support.quest.com/vranger/7.7.1.

Environment

VMware vSAN 6.x

Resolution

Use Cases

• To backup virtual machines with disks residing on a VMware vSAN datastore.
• To restore backed up virtual machines with the same VMware vSAN storage policy if available.
• To enable disaster recovery by replicating a production virtual machine and failing back on a virtual machine replica residing on a VMware vSAN datastore.

Solution Architecture

Quest vRanger Backup & Replication is a simple and easy to use desktop-based solution that can be used to protect entire VMware environments. You can install it either on a supported Windows based virtual or a physical machine. Post installation steps involve configuring the VMware infrastructure, repositories and optional virtual appliances. The virtual appliances provide scalability and decrease the overall workload on the vRanger server.


Quest vRanger Backup and Replication has the following components:

1. vRanger server
   1. Coordinates backup, restore, replication, and repository replication tasks
   2. Enable file level restore for backups of virtual machines with windows guest operating system.
   3. Controls job scheduling
   4. Manages backup infrastructure  
   5. Manging and generating reports
   6. Set configurations
   7. Deploy and manage virtual appliances

Optionally it can also be used to handle i/o data and data storage.

2.  vRanger UI client console: Client console gives access to the vRanger server.
3. vRanger powershell console: Enables automating vRanger server functionalities.
4. vRanger virtual appliance: Is a Linux proxy which can be auto deployed on all ESXi hosts, or on a per cluster basis in the VMware infrastructure to deliver the backup and replication traffic. It retrieves virtual machine data from the virtual disk residing on the datastore and writes it to a backup repository in case of backup and the target datastore in case of replication.

A Backup repository is a storage location where the backup files and metadata files are stored.


For more information on the installation and upgrading, see
https://support.quest.com/technical-documents/vranger/7.7.1/installationupgrade-guide.
For more information on components and usage, see
https://support.quest.com/technical-documents/vranger/7.7.1/user-guide/

Solution Components

• List solution components: Quest vRanger Backup & Replication 7.7.1.
• Provide detailed information about the solution: Quest vRanger Backup & Replication processes VMware vSAN datastores to obtain the virtual machine data efficiently for backup and replication. It also understands the VMware vSAN storage policy applied and retains it during backup.
• Include the version of the VMware product: VMware vSphere 6.0 or greater.
• Link to official product interoperability matrix or VMware Compatibility Guide (vCG) with VMware products: https://marketplace.cloud.vmware.com/services/details/quest-vranger/?slug=true.
• Provide steps to download and install the product on VMware products: For more information on downloading, installing and purchasing Quest vRanger Backup & Replication, see https://www.quest.com/products/vranger/.

Additional Information

• vRanger Backup & Replication 7.7.1 is currently in limited support as of 4/17/2023 and end of support as of 4/17/2024 https://support.quest.com/vranger/7.7.1
• Support Information - https://marketplace.cloud.vmware.com/services/details/quest-vranger/?slug=true
• Troubleshooting (logs, procedures and techniques): https://support.quest.com/vranger/kb
• Indicate whether the solution supports vMotion, HA, and FT:
  • vRanger does support vMotion in that it can track if a VM has moved prior to backup or replication and perform the backup or replication. vRanger does not currently support HA or FT.
• Link to product documentation, and specific reference points in those documents (Example Page Numbers of content referenced): https://support.quest.com/vranger/7.7.1/technical-documents
• Link to downloads site: https://support.quest.com/vranger/7.7.1/download-new-releases
• Link to steps to collect partner SVM logs:
  • https://support.quest.com/vranger/kb/179254/how-to-collect-the-vranger-log-
  • https://support.quest.com/kb/76995/how-to-enable-and-collect-vranger-debug-logs-video-
• Support Process:
  • Customer can open a severity 1 case by calling into our support admins. Severity 2 and 3 cases can be opened via the support portal after logging into their user account. All cases regardless of severity initial contact is made by phone. If voice mail is reached a message is left and a follow up email is sent to case contact via ticketing system.
• SLA:
  • Severity 1: customer to be contacted by phone within 1 hour of case opening unless transferred directly to engineer via support admin.
  • Sev 2: customer to be contacted by phone within 2 hours of case opening.
  • Sev 3: customer to be contacted by phone within 3 hours of case opening.
• Escalation Process:

You can raise the severity of a Service Request, through the online Service Request tool, or call us and request to speak with a Support Manager.  
Upon your request, the Support Manager will evaluate the service request and create an action plan. If you are not satisfied with the plan or with the progress of the case after the plan has been implemented, you may contact the Director of Technical Support, who will review the service request with the Support Manager and determine if different or additional actions are required. 
More information regarding our support process, SLA, and escalation process can be found here:
https://support.quest.com/essentials/support-guide

• Contact information

Sample problematic scenarios and how to address them:
https://support.quest.com/vranger/kb/229564/upgrade-to-vranger-7-6-from-7-x-version-of-vranger
https://support.quest.com/vranger/kb/215586/after-upgrade-to-vranger-7-x-gui-cannot-connect-to-service
https://support.quest.com/vranger/kb/254506/trying-to-install-vranger-agent-fails-with-the-network-name-cannot-be-found-

• Best practices

https://support.quest.com/vranger/kb?r=Topic%3ABest%20Practices