-
Title
vRanger 7.1.1 Could not FLR after upgrade from version 5.5 to 7.1.1 -
Description
vRanger 5.4 upgraded to version 5.5 and upgraded to version 7.1.1, trying to do FLR is not possible Error: Mount Failed
vRanger is creating and deleting savepoints in the repository with no issues previous to the upgrade from version 5.5 to version 7.1.1. The account used to credential the Repository is not a Windows account but an account used exclusivly on the NAS device. Full restore is working , Repository is NAS EMC device.
When trying to do FLR from savepoint, the FLR does not work and it fails to mount the disk inside vRanger application with the error "Mount Failed"
When the FLR is attempted by using "FLR from manifest", and the same user is used as in repository properties (repository_admin) inside vRanger application, FLR fails.
When the FLR is attempted by using "FLR from physical manifest", and local admin credentials are used, the disk is not mounted and FLR do not works.
The user (repository_admin) you are accessing the repository with has full rights to the share on the NAS device. The "repository_admin" user is not a domain admin.
FATAL io_conn_inst_invalid invalid connection instance ID, must be 1 to 64. (192.168.X.x/backup/VRANGER) [at cifs_mount:72]The inventory item NGNHA0-SAV-01(ID:vm-10422) was not found for group NGNH_DOIM.The inventory item NGNHA0-FMO-01(ID:vm-33546) was not found for group NGNH_DOIM. -
Cause
The user (repository_admin) full the rights to the repo share but can't create a "%tmp%\FileLevelRestore\" directory structure on the vRanger server.
Note: When FLR is started (and the disk/s are mounted while FLR window is open) in the vRanger, a file structure is created, and it can be accesed by going to: Start>Run> Type: %temp% this will open windows explorer. Go to directory "FileLevelRestore\Date_Time\Disk (0)\... If you are logged in to vRanger server's windows session as a domain admin and the "repository_admin" is not a domain admin it has no rights to create a local %tmp% directory. When FLR is started (and the disk/s are mounted while FLR window is open in the vRanger application. The a file structure is created, and it can be accessed by going to Start>Run, Type: %temp% this will open windows explorer. Go to directory "FileLevelRestore\Date_Time\Disk (0)\...When you are logged in to vRanger server's windows session as a domain admin and the "repository_admin" is not a domain admin it has no rights to create a local %tmp% directory.
-
Resolution
Solution A:
Make a "repository_admin" a local administrator of the vRanger server.
Go to "services.msc" and one by one check the properties on all 3 vRanger services > Dell vRanger Service, Dell vRanger FLR and Dell vRanger API and vRangerPro DB > Edit. (Log On Tab) Enter credentials for "repository_admin"
Log off and log back in as a "repository_admin"
Solution B:
Make a "repository_admin" a domain admin or at vRanger Repository select the repository> remove the repository (all the jobs associated are going to be dissable) then add the repository back and use the repository_admin account or the local admin account used. Run and FLR and check if the SP's loads the Disks that is part of the Job
Solution C:
Edit the properties of the repository inside vRanger application and change "repository_admin" to the domain admin (Please test backup after change)
Solution D:
Don't change anything just use a Full Restore (navigate to your backup stored on NAS device from the GUI of vRanger) and use "domain admin" credentials to access the NAS share and restore files you need.