Hi, I'm testing out vRangers physical server backups in our environment, and I've run into some problems. I'm hoping someone can provide some insight that isn't in the manuals or on this forum yet so far.
Firstly, installing the Physical Client Agent didn't go very well... the test server, a newer machine, showed up in the Inventory but with a red X, and wouldn't backup.
I went to manually start the Service on the client server, and it refused to run with the login I gave it (the login is our backup-user login, and has domain admin priviledges).
I was able to get the service started after I assigned it to the "Local System" user.
With the serivce now running properly, I was able to create a backup job with disks selected, and no issues.
However, when I run the job if invariably fails after 20 second claiming:
"
[2013-08-09 14:07:57.155]: An internal error occurred during execution, please contact Quest support if the error persists. Error Message: 2254 - Unable to read or write to the repository. Please ensure permissions are correct
[2013-08-09 14:07:57.155]: Task validation failed for Backup 'svr-dvr-02.crab.org'-svr-dvr-02.crab.org, reason: An internal error occurred during execution, please contact Quest support if the error persists. Error Message: 2254 - Unable to read or write to the repository. Please ensure permissions are correct
"
The repository in question is a newly created respository folder, but is in the same location as my other repositories, and has the same permissions as the other repositories.
Additionally, this new repository will successfully receive a VM backup, and I have run several jobs to it with no problem.
Incidentally, the VM backups are credentialed with my backup-user account, as are all my other backups.
I'm fairly sure that the issue is the "local system" account that is assigned to the Physical Client, since that is local to the server itself.
Yet neither of my domain admin accounts (backup-user, my own SU account) will get the Physical Client service to start, and is remains in a 'disabled' state.
The manuals and online error message resolutions are very vague when it comes to permissions, stating that a "service account" with the right permissions needs to be used.
Any insight on what this "service account" must be? Or what permissions it requires, if not having widespread domain admin access...
Many thanks in advance,
.
Neil