Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Quest vRanger backup and replication with vSAN datastores (70901)

Last Updated: 3/21/2024Categories: InformationalTotal Views: 4216Language:
Chinese (Simplified)JapaneseEnglish

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

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.

Solution

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:

vRanger server

Coordinates backup, restore, replication, and repository replication tasks

Enable file level restore for backups of virtual machines with windows guest operating system.

Controls job scheduling

Manages backup infrastructure

Manging and generating reports

Set configurations

Deploy and manage virtual appliances

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

vRanger UI client console: Client console gives access to the vRanger server.

vRanger powershell console: Enables automating vRanger server functionalities.

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/.

Related 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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSAN

Related Versions:

VMware vSAN 6.x

Take Our Survey

Support Assistant