Kategorie
Product Version
Topic
Subtopic
Does Quest Data Protection products have SOC 2 compliance, and/or ISO 27001 certifications? (4372548)
Some organizations require compliance certifications such as SOC 2 or ISO 27001 when evaluating vendor security and risk management. ... This article clarifies Quest Data Protection products' compliance with these standards.
How to open a case using the Quest Support Portal to request Technical Support (4225829)
How to open a case or submit a service request through the Quest Support Portal when experiencing an issue or have questions about Foglight. ... First, the user must registered with an account associated with a license number or asset number on the Quest Support Portal.
Restart the vRanger Services (4047854)
This can pertain to several issues in vRanger and is a simple thing to try first. ... Close the vRanger application and Shut down (Stop) the vRanger Services in any order. ... ***Note: Stopping the vRanger Services will kill any jobs running and might leave open snapshot on the VMs being backed up at the time.
How do I purchase additional licenses? (4044588)
I need to purchase additional licenses.
The remote server returned an error : (503) Server Unavailable. (4044935)
When you try to add the Virtual Center in the vRanger inventory the connection fails with the error "The remote server returned an error : (503) Server Unavailable". ... This usually happens if port 443 connection is blocked from vRanger to the virtual center.
Error: 2760 - FATAL vix_cant_open_detail VIX can't open [Datastore XXXX] Folder-XXXX/File-XXXXX.vmdk (The server refused connection) [at vddkd_open_internal:569] [at vix_open:412] (4048183)
After new deployed ESXi hosts, the backups are failing and cannot deploy VA's. New deployed ESXi host usually come with some firewall settings and advanced settings enabled that can block communication with the backup software.
Resolving "The Trust Relationship Between This Workstation and the Primary Domain Failed" After Restoring a VM (4376743)
This article addresses the error message "The trust relationship between this workstation and the primary domain failed" that may occur after restoring a virtual machine (VM). ... This issue typically arises because the VM's computer account in Active Directory (AD) is out of sync with the security channel established between the VM and the domain.
Upgrade Virtual Hardware and VMware Tools in Virtual Appliances (VAs) (4034057)
Our VMware vSphere environment has newer versions of Virtual Hardware and VMware Tools available and we want to keep all our VMs up to date. ... We do not support upgrading vRanger VAs' Virtual Hardware or VMware Tools.
Reposync: Retention policy not being enforced, Save-points not being removed from repository. (4037421)
Repository contains more save points than what is shown in view within vRanger My Repositories. ... Job may have been run manually therefore not allowing the retention policy to be implemented. ... Please download the attached PowerShell script that can be used to synchronize your repository.
Machine-SAN restore fails with message "One of the parameters supplied is invalid" (4044774)
When attempting to run a VMware SAN restore, it fails over to LAN transport with the following message: ... The Windows operating system has the SAN disks configured in Read-Only mode. ... Restores direct to SAN disk are not possible.
Restoring Physical Server to dissimilar hardware (4035785)
Can savepoints from physical backups be restored to dissimilar hardware? ... When restoring to a physical server, ensure that you are restoring to hardware supported by the operating system and drivers in the savepoint being restored.
VMDK Extractor manual restore (4044582)
Unable to perform a restore but we have the savepoint with VAR files accessible. ... The steps to perform a manual restore: 1. ... The drive(s) should be the same size as the original. ... The sizes can be found in the VMconfig.metadata file.
Restore of a Virtual Machine Connected to Cisco Nexus 1000V Virtual Switch does not have NIC (4046110)
After restoring a VM that was originally connected to a Cisco Nexus 1000V Virtual Switch, the VM has no NIC and no network settings. ... During the setup of the restore job the network selection drop-down list is unpopulated.
How to migrate vRanger configuration and license (4042855)
This article outlines the process of migrating vRanger configuration and licensing to a new server. ... If SQL has been installed using the vRanger embedded installer, the instance name is called <em>VRANGERPRO</em>.
What's new in vRanger 7.8.5? (4373057)
What's new in vRanger 7.8.5? Enhancements in this release: ... <ul><li>Support for vSphere 8.0 and 8.0.1 for vRanger.</li><li>Certified to support Windows Server 2022.</li><li>Support for EMC DD OS 7.10 for vRanger.</li></ul> VR-1482
Physical Agent backups fail after upgrading to vRanger 7.8.4 or 7.8.5. (4372679)
The vRanger Server and the Physical Agents were upgraded to versions 7.8.4 or 7.8.5.<br>In the Physical server, the VSS snapshot is not created when vRanger requests it.<br>New and Existing Backup Jobs are failing with any of the following behaviors:<br><br><strong>Error 1:</strong> <br>[DATE TIME]: An existing vRanger VSS snapshot was detected. The snapshot will now be removed.<br>[DATE TIME]: Creating snapshot failed.<br>[DATE TIME]: Error: Failed to remove a pre-existing vRanger VSS snapshot from the target machine.<br><br><strong>Error 2:</strong><br>[DATE TIME]: Creating snapshot failed.<br>[DATE TIME]: Error: Failed to create VSS snapshot on the target machine (CREATE_SNAP_SET_ERR).<br><br><strong>Error 3:</strong><br>The job just waits for 20 minutes and times out, at the 10 minute mark a retry is observed.<br> A Defect was identidied with the Physical Agents on version 7.8.4 and 7.8.5.<br>It has been identified with ID: VR-1478<br><br>This is currently being investigated by our Development team, this KB article will be updated in the future with an expected release date or version with the fix when available. <strong>Workaround:</strong><br>Downgrade the Physical Agent to version 7.8.3.
Manual VMware VM restore for vRanger 7.x (4033004)
Sometimes vRanger runs into a VMware VM restore issue and nothing can be done to resolve it at that time. ... If the VMware VM needs to be restored immediately and there is not enough time to troubleshoot the restore issue, you can manually restore the VMware VM.
vRanger VMware VM Encryption support (4036178)
This article outlines vRanger Backup & Replication support for VMware encrypted virtual machines. ... <p>Since VMware Sphere 6.5, virtual machine encryption has been released as a feature in order to protect sensitive data.
Cannot upgrade Virtual Appliances after upgrading to vRanger 7.8.4 or 7.8.5 (4371343)
After upgrading vRanger to version 7.8.4 or 7.8.5, in the Upgrade Virtual Appliance(s) wizard, an error message "Version not valid for upgrade, this VA will be skipped." if the version is 7.8.3.<br> In the installation directory, the default being "C:\Program Files\Quest\vRanger", it is observed that the OVA file is called "vRanger-Virtual-Appliance_783.ova".<br> vRanger versions 7.8.4 and 7.8.5 do not have a new Virtual Appliance version to be deployed, this error message is expected.<br>The latest version will continue to be 7.8.3 so no upgrade is available.<br>
vRanger 7.7.1 and VMware 6.7 Update 2 compatibility (4039193)
This document outlines the compatibility between vRanger 7.7.1 and the latest VMware 6.7 update 2 release. ... <p>The latest VMware 6.7 Update 2 patch introduces Virtual Hardware Version 15 which adds support for creating virtual machines with up to 256 virtual CPUs.
Can vRanger Restore a Physical Machine to a VM? (4033089)
Can vRanger Restore a Physical Machine to a virtual machine.
Backup fails with "Error: API Call failed with message: An error occurred while saving the snapshot" (4040289)
Backup of a VM located on an ESXi 5.5 host, failed when taking a Quiesced snapshot with the following error message in vCenter: "msg.snapshot.error-QUIESCINGERROR" ... vRanger task log reveals following error message: "Error: API Call failed with message: An error occurred while saving the snapshot"
Reports not working correctly (4041231)
vRanger reports are damaged and also new reports are instantly damaged after creating. ... Go to control panel\ programs and features\ uninstall programme</span></li><li style="margin-top: 0;margin-bottom: 0;vertical-align: middle;"><span style="font-family: Calibri;font-size: 11.0pt;"> Highlight vRanger Backup & Replication</span></li><li style="margin-top: 0;margin-bottom: 0;vertical-align: middle;"><span style="font-family: Calibri;font-size: 11.0pt;"> Right click and choose change</span></li><li style="margin-top: 0;margin-bottom: 0;vertical-align: middle;"><span style="font-family:
No backup. No error message. No failed task (4039484)
Scheduled backup job fails to run but received no warning or error message in failed tasks. ... Check in 'Recent Jobs' view verified job creation had failed as a result of the vCenter being unavailable/disconnected.
Confirm vss tools operation (4040335)
If log truncation is required during creation of a Quiesced snapshot. ... then VSS tools can be installed to provide application consistency to the snapshot. ... The steps below can be used to confirm the correct operation.
Neue Produktverknüpfung
- Self-Service-Tools
- Knowledge Base
- Benachrichtigungen und Warnmeldungen
- Produkt-Support
- Software-Downloads
- Technische Dokumentationen
- Benutzerforen
- Videoanleitungen
- RSS Feed
- Kontakt
- Technische Support
- Alle anzeigen