This post is more than 5 years old
2 Intern
•
202 Posts
0
1535
Client index error?
Hi!
I have a customer who uses a quite old NW. (7.1.2)
(upgrade is another issue)
We have one Win2k3 file level backup client, which is working strange.
1. All backup is fine from C:\
2. M:\dir1 isnt working. Full backup size is 0kb, directory size is 10GB
M:\dir2 isnt working. Full backup size is 30kb, directory size is 5GB
Very strange, when i create a new dir in this dirs:
M:\dir1\dir3 backup is working
The quota and permissions are enabled on both dir. (M:\dir1, M:\dir2)
I run the agent on the client as a domain admin and the client definitions
contains the domain admin remote user.
The both directories has dirs with natinal chars, but for the new dirs it is working properly.
M:\dir1\dirb working well, if the dir contains national langugae chars.
(Unfortunately, i cannot specify the national chars save set in this Nw version.)
I tried several things, removed the /nsr/index/client index, but doesnt works.
I think maybe the index is corrupt, but i dont know surely.
How can is solve this problem?
What is the appropriate method for complete removing client index?
(i tried removing the /nsr/index/client dir)
Thx in advance,
Paul
saleesh1
128 Posts
0
September 15th, 2010 05:00
Are they DFS folders ?
DavidHampson-rY
294 Posts
1
September 15th, 2010 02:00
You haven't by any chance got some directives which cause those directories to skip?
Daniea3
123 Posts
1
September 15th, 2010 03:00
Hi Paul,
The M:\ drive which you mentioned. is this a shared drive or network drive which is mounted on one of the client? If so you need to specify the UNC path of the drive on the saveset.
Regards,
Arun
guenterH1
117 Posts
1
September 15th, 2010 04:00
Hi Pal,
Could it be the case that your host is an Exchange Server and this drive M:\ is part of the Exchange Installtion?
I mean the drive Exchange 2000 used to represent the plain file access to mail objects?
If so this drive should be skipped from backup at all.
Please let us know some more details of this drive.
On the other hand I would start with a manual backup of the directories in focus from the client side.
Something like
save -s -v M:\dir1
Probably adding debugging (-D 3) if verbosity doesn't show any hint.
That should show more detailed what NetWorker is doing within the backup run.
Regards,
Guenter
paulo3
2 Intern
2 Intern
•
202 Posts
0
September 15th, 2010 04:00
Is it a part of the network share.
It is a local drive on the server and shared for the clients.
I will try it.It is the unc path on the client?
\\servername\dirname
Do the networker accept it on save set spec?
BR: Paul
DavidHampson-rY
294 Posts
0
September 15th, 2010 05:00
When you say it is "a local drive on the server" is the server in question the backup client, or is the backup client the client this resource is shared to?
paulo3
2 Intern
2 Intern
•
202 Posts
0
September 16th, 2010 01:00
Hi!
I dont know if its part of the DFS or not.
It is a NW client, which has a local drice, called M: and N:
It is shared for a clients who uses this as a network share.
Thanks: Paul
paulo3
2 Intern
2 Intern
•
202 Posts
0
September 16th, 2010 04:00
Thanks.
It is a dfs dirs.
\\servername\dir1
\\servername\dir2
is working well! If you have any information about dfs file path
naming in Networker it is also helpful for me ...
thx: Paul
Daniea3
123 Posts
0
September 16th, 2010 05:00
Hi Paul,
What are the savesets for this Clent? Try using the UNC path as the saveset and make sure you have enough permissions on this path.
Regards,
Arun
paulo3
2 Intern
2 Intern
•
202 Posts
0
September 20th, 2010 05:00
Hi!
The original saveset is:
M:\Kozos
It doesnt works. If i add a remote user to the user name field it also doesnt works.
The unc path is:
\\servername\Kozos
is working, when i add the remote user to the remote user section of the client tab. otherwise
doesnt works.
Question:
Customer stated that he doesnt want to add the remote user to the remote user specifications.
How is the networker authenticate in this case?
If the Networker is installed on the client as a local admin he must save everything. Or is it not true in all cases?
BR: Paul
rovinabi
55 Posts
0
September 20th, 2010 16:00
Paul,
Since the saveset in question is a Network share you will have to specify the remote user name and password in the client configuration. To avoid this you might have to run the nsrexecd service with these credentials (on a windows server) by changing the lon on in the services mmc.
Rovin.
paulo3
2 Intern
2 Intern
•
202 Posts
0
October 1st, 2010 05:00
Hi!
Quite strange issue.
It is worked before with UNC path:
\\servername\dir1
and doesnt works:
M:\dir1
And something happened, and the unc path is failing to work:
\\servername\dir1 : could not stat invalid argument
It is not working on this way. Maybe the index is corrupted.
Do you have any ideas, how can i fix this?
Luis_Rogerio
116 Posts
0
October 1st, 2010 12:00
Hi Pal
If index is corrupted you can manually run a higher level check on the index - nsrck -L6 client_name
Regards,
Luis Rogerio