Kategorie
Product Version
Topic
Subtopic
Replication performance issues (4041154)
Replication via vRanger is having performance issues. ... How to troubleshoot and diagnose the issue? ... Network bandwidth between 2 sites are running on point to point VPN or slow performance issue for replication.
Trial licence cannot be added (4040291)
A new trial licence that has been supplied to allow for an extension of the trial period will not add to vRanger. ... vRanger will not accept a 2nd trial licence with the same resources as in previous version.
All replication jobs failing with "2535 - FATAL phys_cant_create_detail PHYS can't create 1:/scratch/sdb/" (4040295)
It is observed that all Replication jobs are failing with "2535 - FATAL phys_cant_create_detail PHYS can't create 1:/scratch/sdb/42008411-0e26-940b-40a7-55f99fe3e112/vzundo-script (Read-only file system)" <p>Target Virtual Appliance had it's filesystem in Read-only mode.</p><p>While logged in as Root, it was not possible to create a directory in the /scratch/sdb location.</p><p>Error message was (Read-only file system)</p> <p>Reboot the Virtual Appliance</p><p>Test creating a directory with "mkdir test" command in /scratch/sdb to confirm Read-Only mode is no longer in place.</p><p>After confirming, run the replication job again</p>
Backup fails with "Task could not complete due to unexpected system shutdown." (4039441)
It is observed that the vRanger application crashed and the backup fails with "Task could not complete due to unexpected system shutdown." ... Application: Vizioncore.vRanger.exe ... Framework Version: v4.0.30319
vRanger operating system compatibility requirements. (4041214)
What are the current supported operating systems for installation of vRanger 7.2? <div>Please review the current list of <a href="https://support.quest.com/technical-documents/vRanger/7.2.1/installation-and-upgrade-guide/system-requirements-and-compatibility/requirements-for-the-vranger-machine/supported-operating-systems-for-installation" target="_blank">supported operating systems</a> for vRanger 7.2</div><div></div><div>A complete list of system requirements and compatibility are posted in the vRanger <a href="https://support.quest.com/technical-documents/vRanger/7.2.1/installation-and-upgrade-guide" target="_blank">installation and upgrade guide</a><br>– please use this information to confirm vRanger is supported in your environment.</div>
All backups are failing after the upgrade to 7.2.1 (4038506)
After the upgrade from version 7 to 7.2.1, all backups are failing with 'Error: -1 Backup process had an unexpected failure'. ... Backup the vRanger DB and catalog first or do not remove the existing databases during the vRanger 7.2.1 uninstallation.
Restored VM will not boot up on ESXi 5.0 server (4038523)
Upon the successful Restore of a VM to ESXi 5.0 Express Patch 3 version, VM will not boot up. ... Upgrade the ESXi 5.0 host to the most recent version to resolve the issue.
Backups fail with Error: 2916 - CIFS cannot connect to share (4041125)
One or two backups run and then the next backup gets the error “Error:2916 – CIFS cannot connect to share” Server is rebooted, one or two backups work, and then same error occurs. ... vRanger Virtual Machine was running out of memory due to another program installed on the VM using half of the available memory.
HotAdd backups fail over with Backup failed: Error: 2760 - [vix_cant_open_detail] VIX can't open [Datastore] VMname/VMname.vmdk (You do not have access rights to this file) (4041131)
Windows Event log on the vRanger machine reports disk errors reading volumes during the backups. ... Automount needs to be disabled and old automount information needs to be purged. ... 1. Open a cmd prompt as Administrator.
error P_VSSUTIL_PROVIDER_VETO with Hyper-V or Physical backup. (4039386)
When job is running and creating the snapshot, the user will get an error "P_VSSUTIL_PROVIDER_VETO" on VM or physical server event viewer. ... <p>When the backup job starts, no snapshot is being created and you can see VSS errors in the event log.
SAN Restore fails with "2813 (You do not have access rights to this file)" (4041137)
It is observed that a SAN Restore failed with "2813 (You do not have access rights to this file)" <p>LUNs that are presented to vRanger in Disk Management do not have permissions set up correctly.</p><p></p> <p>vRanger requires Read&Write access to the LUNs in order to perform SAN Restores.</p><p>Follow the <a href="https://support.quest.com/technical-documents/DOC241436" target="_blank">Documentation</a> to set up the permissions correctly</p>
Unexpected Problem vRanger has encountered a problem and needs to be closed. When trying to access Virtual Appliance Configuration (4041142)
When trying to access Virtual Appliance Configuration get "Unexpected Problem vRanger has encountered a problem and needs to be closed. ... Parameter name: Value" Specific cause is not known at this time other than some corruption on the Virtual Appliance.
Issues sending email to office 365 (4038358)
Unable to get emails notifications from vRanger server using office 365. ... </p><p> </p> <p>Office 365 is not natively supported. ... Populate the SMTP Server field.</p><p>4. ... Leave the default (25) in the Port field.</p><p>5.
vRanger VA upgrade to 7.8.2 version will create a VM with an E1000 vNIC (4042031)
After upgrading vRanger to version 7.8.2, the vRanger virtual appliance is created with an E1000 virtual network interface. ... It is not possible to add a new VMXNET3 virtual network interface to the virtual machine.
vRanger task fails with API Call Failed: The parent virtual disk has been modified since the child was created (4044610)
When running a backup or replication task, it fails with the following message: ... Error: API Call failed with message: An error occurred while taking a snapshot: The parent virtual disk has been modified since the child was created.
System Event Log shows Event ID 157 "Disk # has been surprise removed" for Hyper-V guests (4041159)
When using vRanger to backup Hyper-V VM's, Event Viewer warning with the 157 ID is present in guest's system log. ... This Event occurs after a backup task completes and it refers to a disk that is currently not connected to the VM.
Repository becomes inaccessible during backups when attached to Windows workstation machine (4041169)
Repository connect to a Windows 7 or 8.1 workstation fails during backup with various errors, such as, "2034 - FATAL cifs_cant_use_detail CIFS cannot connect to share" or "Error 2258: FATAL cifs_cant_mkdir CIFS can't create the directory (Connection timed out)", or sometimes the backup does not run and there is no error.
API Call failed with message: A specified parameter was not correct: (4041301)
After upgrading ESXi and virtual center to 6.7 update 2 restore jobs and new replication jobs fail with error Error: API Call failed with message: A specified parameter was not correct: ... Replication jobs are running successfully if their Replica exists.
Restore fails with "The job Restore 'Name of the job' has completed with a status of Failed" (4040271)
It is observed that a Restore job fails immediately with "The job Restore 'Name of the job' has completed with a status of Failed" ... Following line is also present in Recent Jobs view in vRanger:
Cannot replicate virtual machins (VM) in Hyper-V (4041166)
There is no Replication option for Hyper-V VMs. Replication is not supported for Hyper-V <p>WORKAROUND </p><p>None</p><p>STATUS</p><p>An enhancement request FT-780 has been submitted to Development for consideration in a future release of vRanger</p> FT-780
Remove Catalog service from installation. (4038516)
Would like to remove the installed catalog service from version 7.x. ... To remove the catalog service from the current installation, I would recommend the following: ... Go to the control Panel ... Select 'vRanger backup & replication'
Hyper-V system Center VMM is not showing Hosts in inventory view. (4039405)
When looking at inventory in vRanger the hosts associated with the Hyper-V system center are not showing. ... Hosts can be added individually to the inventory. ... Hyper-V cluster is offline. ... Open Failover Cluster Manager.
Backup failure: Error: -1 - chown changing ownership... Read-only file system (4036313)
Read-only file system chown: changing ownership of '/root/vzva/201409250900/libvzvfr.so': Read-only file system chown: changing ownership of '/root/vzva/201409250900/ssh': Read-only file system chown: changing ownership of '/root/vzva/201409250900/iorofs.so': Read-only file system chown: changing ownership of '/root/vzva/201409250900/remotereplicate': Read-only file system chown: changing ownership of '/root/vzva/201409250900/lzo.so': Read-only file system
Reducing the retention policy in the current vRanger backup job (4039321)
In case of a need for reduced number of savepoints in the Repository location, by editing an existing vRanger backup job, Retention policy can be modified. ... In most cases, need to modify the Retention policy arises from spacing issues in the Repository location.
How to mount the disks to the Windows OS in order to allow LAN-free or SAN mode backups (4043981)
This document outlines the procedure to mount the datastores to the vRanger Windows OS in order to allow LAN-free or SAN backup transport methods. ... </strong></span></p><p><strong>Mounting the disks using iSCSI:</strong></p><p>You need to set up the parameter automount disabled in the DISKPART utility on your vRanger server.
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