Category
产品版本
主题
副主题
Backup fails with error 2651 - cant write detail...The requested operation could not be completed due to a file system limitation (4040213)
Backup of large VM (10TB in particular case) fails with error: ... CIFS repository resides on NTFS partition ... A heavily fragmented file in an NTFS file system volume may not grow beyond a certain size caused by an implementation limit in structures that are used to describe the allocations.
Uknown failure for installation for the agent (4041088)
Unknown failure for installation for the agent. ... Server has a red x right next to it in the vRanger application. ... When vRanger tries to authenticate with the physical server, the credentials are not correct or just does not have the credentials in the server Go to services, right click on "Quest vRanger Physical Client Service", select the logon tab, change the account permission to "local system account"
When starting vRanger "Could not connect to the service" (4041116)
Could not connect to the service. ... Service cannot be started. ... System.ServiceModel.AddressAlreadyInUseException: HTTP could not register URL http://+:xxxx/XXXXXXX.svc/. ... This happens even after restarting the services on the vRanger server
Sweep to tape script for vRanger 7.2 (4038445)
When attempting to access sweep to tape script in user guide the link provided has an incorrect path attached.
vRanger Upgrade to 7.2 with external SQL database workaround (4036203)
vRanger v7.2 upgrade may experience a failure to use existing vRanger databse if database is located on a remote/external server due to external security settings on that other server. ... vRanger will create a new databse and add a unique UUID no next to database name EX: vRangerPro 1234-dhfd-4564-yre6-5798...
The VM had no disks (4032739)
When running a back up, it will fail with the error message "The VM had no disks" The possibility to get it working again would be to edit the job and then disable VSS application level quiescing and VSS log truncation, once those are disable the job could work with out any issues.
vSphere 4.1 with vRanger 7.2 not supported anymore (4041061)
Ever since vRanger 7.2, vSphere 4.1 environment, including ESXi 4.1 and vCenter 4.1 are no longer supported. ... In order to perform required tasks in vRanger 7.2, vSphere environment should be on at least version 5.
Backup fails with: "Error: 2983 - FATAL nfs_cant_read" (4040216)
Backup to NFS Repository fails with "Verifying repository content produced the following error(s): Error: 2983 - FATAL nfs_cant_read NFS can't read" Not enough free space in the Repository <p>Free up required additional space</p><p>Run the backup again</p>
Restore - error: 2250 vix connection error (4039311)
When trying to restore a virtual machine receive an error: 2250 vix connection error Anti-virus (AV) software was scanning the repository during restore. ... AV software was disabled and repository excluded from on-access scanning.
vRanger 7.2 (and up) can now do FLR from a GPT partition (4039333)
Symtom of a GPT partitioned disk when doing a File Level Recovery (FLR) is no mounted drive information is displayed under the disk volume. ... If your drive larger then 2.2 TB and is formatted as a single drive it may be a GPT
Error 2760 "One or more required subsystems failed to initialize" during machine-based backup (4041048)
Virtual Appliance-based backup works. ... This is a known VMware issue described below: ... http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2120818 ... As per VMware KB above, there is no resolution yet.
Error: user root could not be authenticated (4040193)
Doing a backup he will get the error user root could not be authenticated This would be because the host needs to authenticate, but there sometimes the authentication is not needed or already there.
Error: API call failed. Message: Invalid configuration for device 'x'. (4038498)
Device number may vary. ... After Performing upgrade to vRanger 7.2 issue is still observed ... There are new devices that are used for CD/DVD-Rom in a version 10 hardware virtual machine. ... These new devices were not in the code, therefore they are not recognized devices and will cause failure.
Backup job results in PSOD on ESXi 5.5 GA (4040146)
It is observed that a backup of a VM residing on ESXi 5.5 GA (release build 1331820) results in PSOD on the ESXi host. ... Upgrade the affected ESXi host to one of the versions that is not affected by this issue.
Location of VA (virtual appliance) OVA file for manual deployment (4040168)
You no longer need to download the OVA file to deploy vRanger virtual appliance as it is included in the install.
vRanger job fails with "Login50FromVmware failed" (4032754)
It is observed that jobs in vRanger fail with "Error: Login50FromVmware failed" as username used to credential vCenter in vRanger. ... <p>User that is credentialing vCenter in vRanger has SSO issues.</p><p>That can be confirmed by attempting to log in to the vSphere Client or the Web client with the same user, from the vRanger machine.
Error 2258: Can't create the directory (4040177)
NAS drive was replaced or removed ... As the NAS drive was replaced or removed, everything had to be configured again, the configuration could be wrong andthe DNS is not able to resolve the name.
Unable to add RDA Repository "Access denied" error message appears (4040197)
After upgrading the DR Unit Firmware version, it is not possible to add an RDA container. ... Firmware upgrade causes default username/password of "backup_user/Stor@ge!" to lose authentication privileges.
vRanger blue screens when Replication jobs are running (4040195)
It is observed that Replication jobs in vRanger cause the BSOD to appear. ... Known VMware limitation detailed in this VMware KB article ... Upgrade the ESXi host to one of the versions that is not affected by this issue
VA Deployment fails with: "PBM error occurred during PostProcessReconfigureSpec: pbm.fault.PBMFault" (4041090)
Virtual Appliance deployment fails with "API Call failed with message: A general system error occured: PBM error occured during PostProcessReconfigureSpec: pbm.fault.PBMFault" Failure is caused by the vCenter Inventory Database Service described in this <a href="http://kb.vmware.com/kb/2087990" style="color: rgb(0, 0, 170);font-family: Verdana, Geneva, sans-serif;" target="_blank">VMware KB article</a> Issue is resolved by restarting the vCenter server http://pubs.vmware.com/vsphere-60/index.jsp#com.vmware.vspsdk.apiref.doc/pbm.profile.ProfileManager.html
Error 2250 - VIX connection error (4039353)
On the vCenter computer, configure an exception in Symantec Endpoint Protection to exclude all the vRanger VAs
VA based backups running slowly after upgrading vRanger to version 7.8.1 (4042848)
Since upgrading to vRanger Backup & Replication 7.8.1, the backups are taking considerably longer to complete when using vRanger virtual appliances to a CIFS/SMB repository. ... This has been identified as a product defect.
Permissions required to add the Hyper-V server (4041060)
Permissions required to add the Hyper-V host, run backup and restore tasks in vRanger.
Upgrading to 7.2 database selection screen is grayed out (4038487)
When upgrading or reinstalling 7.2 the database screen is grayed out not allowing the selection of a specific or local database <p>previously used database is still in the registry and is being read by vRanger installation wizard</p><p>You must remove it from registry to reset vRanger to defaults</p><p></p> <p></p><p>You must first clean out the registry entry folder "Vizioncore, Inc" (see entry below) then run installer again</p><p>HKEY_LOCAL-MACHINE/SOFTWARE/Vizioncore,inc</p><p>.</p><div><div><br><div></div></div></div><p></p>
Restore of Hyper-V VM fails with error: No network card was found that met the specified criteria (4043696)
When restoring Hyper-V virtual machines, the virtual machine creation fails with the following message: ... Creating virtual machine 'Virtual Machine Name' failed: No network card that meets the specified criteria was found.
新产品关联性