Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
networker scanner command 1
- Thread starter kristouf
- Start date
-
1
- #2
disldrautoldmc
Technical User
- Feb 13, 2003
- 32
Have you 6.0.1 version ?
Probably the clientID was modified or doubled:
mminfo command shows the same client with different client id's:
mminfo -av -r "client,clientid"
client clientid00001
client.long.name clientid00002
/nsr/index directory could show two different client file indexes for the same client:
/nsr/index/client
/nsr/index/client.long.name
Recover of "client.long.name" has no problems. Trying to recover data from "client" gives the unknown volume error
So this is the procedure to change it:
For this workaround, you are going to need to create a "dummy" hostname with fictious ip address on your host table.
A. If the hostname and the client id's are different:
1. From nwadmin, remove all instances for "client"
2. Shutdown the NetWorker daemons
3. Rename /nsr/index/client to /nsr/index/dummy
4. Clean /nsr/tmp folder
5. Restart the NetWorker daemons
6. From nwadmin, create the "dummy" client, and specify the same clientid for "client"
7. Edit "dummy" client, go to the Remote tab and add *@client.name.com in the Remote access field
8. Go to "client.long.name", and run a directed recover from "dummy" client.
B. If the hostname is the same and the client id's are different:
1. From nwadmin, create the "dummy" client, and specify the same clientid that are using the savesets you cannot recover.
2. Edit "dummy" client, go to the Remote tab and add *@client.name.com in the Remote access field.
3. Recover savesets from the dummy client doing a saveset recover.
Optional:
4. If you want to be able to run a directed recover and browse the dummy client, then you are going to need to rebuild the client file index using the scanner command or nsrck -L7. Check Primus ID 10329 if you want to learn more about recovering client file indexes.
5. Once the index is recovered, go to "client.long.name", and run a directed recover from "dummy" client.
Bye.
Probably the clientID was modified or doubled:
mminfo command shows the same client with different client id's:
mminfo -av -r "client,clientid"
client clientid00001
client.long.name clientid00002
/nsr/index directory could show two different client file indexes for the same client:
/nsr/index/client
/nsr/index/client.long.name
Recover of "client.long.name" has no problems. Trying to recover data from "client" gives the unknown volume error
So this is the procedure to change it:
For this workaround, you are going to need to create a "dummy" hostname with fictious ip address on your host table.
A. If the hostname and the client id's are different:
1. From nwadmin, remove all instances for "client"
2. Shutdown the NetWorker daemons
3. Rename /nsr/index/client to /nsr/index/dummy
4. Clean /nsr/tmp folder
5. Restart the NetWorker daemons
6. From nwadmin, create the "dummy" client, and specify the same clientid for "client"
7. Edit "dummy" client, go to the Remote tab and add *@client.name.com in the Remote access field
8. Go to "client.long.name", and run a directed recover from "dummy" client.
B. If the hostname is the same and the client id's are different:
1. From nwadmin, create the "dummy" client, and specify the same clientid that are using the savesets you cannot recover.
2. Edit "dummy" client, go to the Remote tab and add *@client.name.com in the Remote access field.
3. Recover savesets from the dummy client doing a saveset recover.
Optional:
4. If you want to be able to run a directed recover and browse the dummy client, then you are going to need to rebuild the client file index using the scanner command or nsrck -L7. Check Primus ID 10329 if you want to learn more about recovering client file indexes.
5. Once the index is recovered, go to "client.long.name", and run a directed recover from "dummy" client.
Bye.
This problem can occur with NetWorker 6 and 7. This is because clientid was introduced with NetWorker 6
After you upgraded from nt4 to w2k, did you notice that the NetWorker server's name changed from the short name lh3000-1 to the fully qualified domain name?
Check the client lh3000-1's setting. Specifically, look at the alias field, and make sure that both the short and FQDN are there.
This is definitely related to a clientid defined for both the short and FQDN. This can be verified by running:
mminfo -av -r client,clientid | sort | uniq >client.txt 2>&1
If your system doesn't have a sort or uniq program, then omit that, and then edit the output file and search for lh3000-1. Without the uniq program, you'll have to search through a lot of output lines.
What can be done about it? Reading disldrautoldmc's post gives the impression that it is complicated to fix, and I've found that there can be many solutions, depending on the particular circumstances.
The client-clientid cannot be removed from the media database once it is registered, but you can reassign the clientid to another "dummy" client.
It's really tricky, and my advise is to open a support call so that Legato can help you resolve this.
After you upgraded from nt4 to w2k, did you notice that the NetWorker server's name changed from the short name lh3000-1 to the fully qualified domain name?
Check the client lh3000-1's setting. Specifically, look at the alias field, and make sure that both the short and FQDN are there.
This is definitely related to a clientid defined for both the short and FQDN. This can be verified by running:
mminfo -av -r client,clientid | sort | uniq >client.txt 2>&1
If your system doesn't have a sort or uniq program, then omit that, and then edit the output file and search for lh3000-1. Without the uniq program, you'll have to search through a lot of output lines.
What can be done about it? Reading disldrautoldmc's post gives the impression that it is complicated to fix, and I've found that there can be many solutions, depending on the particular circumstances.
The client-clientid cannot be removed from the media database once it is registered, but you can reassign the clientid to another "dummy" client.
It's really tricky, and my advise is to open a support call so that Legato can help you resolve this.
- Status
Similar threads
- Question