My NW V is 8.2.4.0. The server I am backing up is Windows Server 2008 R2.
Yes I am backing it up automatically via a group. The Win server is configured as a NW client. NW does backup the other volumes successfully.
When I run nsrls on the client host name I get (Access is denied. (Win32 error 0x5)). I am using domain admin credentials to log into the networker server but our Networker is not AD integrated. Meanign I using a local admin account to log into Networker GUI.
According to the books, the NW installation should be a member of the local admins group.
By default NW has its own user rights system. If you use any other account you must add him to the NW Admin group (server properties). You can even allow everybody to gain access (*@*). However I do not recommend that for production environments.
"There are currently two workarounds, the first of which is documented in the Command Line Reference Guide:
1) Save command entry text:
path: File index could not be obtained due to . Contents of this directory may not be properly backed up. There was an error in retrieving an on-line file index record for the path with renamed directory support. Run nsrck (1m) and turn off the "Backup renamed directories" attribute in Client resource ( see nsr_client(5) ) to re-run the group if the problem persists.
2) The second workaround allows you to keep the backup renamed directories option on the client definition if this is important to you for your environment:
Amending the existing directive from
+skip: *.*
to
+skip: .
resolves the issue.
####
COMMANDS ON WINDOWS FAILING WITH 0x5 ####
From KA 456382 -- 82374:nsrck: Unable to acquire lock for RAP database retrieve: Access is denied -- URL: < https://support.emc.com/kb/456382 > notes,
"When running any NetWorker command from the Windows CMD prompt that requires administrator privileges, the "Run as administrator" was not selected."
Thank you David. I put the host to "full every day" instead of "Full Friday" and that seemed to resolve the issue. I change the host back to "Full Friday" and have not had an issue since.
But this is a great reference that I will use in the future.
bingo.1
2.4K Posts
0
March 22nd, 2018 05:00
May I remind you that you better provide some fundamental info about you environment like OS and NW version.
Not all issues are so generic that we understand exactly what you are doing.
You obviously backup a Windows 2xxx server.
How - manually (via 'save') or automatically (via 'savegrp') ?. From you other post I guess you are running NW 8.x
Is this server configured as NW client at all?
If so, does the backup of the other volumes fail as well?
What is the result if you run "nsrls ' on the NW server?
ChristianFC
11 Posts
0
March 26th, 2018 07:00
Thanks Bingo.
My NW V is 8.2.4.0. The server I am backing up is Windows Server 2008 R2.
Yes I am backing it up automatically via a group. The Win server is configured as a NW client. NW does backup the other volumes successfully.
When I run nsrls on the client host name I get (Access is denied. (Win32 error 0x5)). I am using domain admin credentials to log into the networker server but our Networker is not AD integrated. Meanign I using a local admin account to log into Networker GUI.
bingo.1
2.4K Posts
0
March 27th, 2018 02:00
According to the books, the NW installation should be a member of the local admins group.
By default NW has its own user rights system. If you use any other account you must add him to the NW Admin group (server properties). You can even allow everybody to gain access (*@*). However I do not recommend that for production environments.
muetzd
18 Posts
0
March 28th, 2018 10:00
A search of support.emc.com for
"File index could not be obtained due to" "Unable to get direntry"
I got a single result
"NetWorker Error reported "File index could not be obtained due to " for specific Windows drive/s after upgrade to NetWorker 8"
URL: < https://support.emc.com/kb/479456 >
"There are currently two workarounds, the first of which is documented in the Command Line Reference Guide:
1) Save command entry text:
path: File index could not be obtained due to . Contents of this directory may not be properly backed up. There was an error in retrieving an on-line file index record for the path with renamed directory support. Run nsrck (1m) and turn off the "Backup renamed directories" attribute in Client resource ( see nsr_client(5) ) to re-run the group if the problem persists.
2) The second workaround allows you to keep the backup renamed directories option on the client definition if this is important to you for your environment:
Amending the existing directive from
+skip: *.*
to
+skip: .
resolves the issue.
####
COMMANDS ON WINDOWS FAILING WITH 0x5
####
From KA 456382 -- 82374:nsrck: Unable to acquire lock for RAP database retrieve: Access is denied -- URL: < https://support.emc.com/kb/456382 > notes,
"When running any NetWorker command from the Windows CMD prompt that requires administrator privileges, the "Run as administrator" was not selected."
Additional information can be found in 420922 URL: < https://support.emc.com/kb/420922 >
ChristianFC
11 Posts
0
April 4th, 2018 06:00
Thank you David. I put the host to "full every day" instead of "Full Friday" and that seemed to resolve the issue. I change the host back to "Full Friday" and have not had an issue since.
But this is a great reference that I will use in the future.
Thanks David