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!

Migration NT4-Domain to AD: no matching devices

Status
Not open for further replies.

kdoe

Technical User
Feb 19, 2003
9
DE
Networker Server 7.3.2 W2K
After I have entered the full qualified domain name on the networker server, our networker has the following save errors:

* client2:SYSTEM DB:\ 1 retry attempted
* client2:SYSTEM DB:\ save: error, no matching devices for save of client `client2'; check storage nodes, devices or pools
* client2:SYSTEM DB:\ save: Cannot open save session with nwserver1.company.lan

After deleting the fqdn the networker will save normally.

Klaus
 
- Make sure that you have the short name as an Alias for that client

- Look up your device setup.
If you have SNs, then the devicenames might need to be changed.
- Look up your pools definition.
Especially when you assigned devices to pools, those might need to be adjusted.
 
Hello 605,
many thanks for your advice.

- alias had been set
- pool definition did not change after configuration change

but:
- we have a single server and the name of the storage node had to be set to the new long hostname
This was a little bit work: unload device, delete pool-device combination, delete library, delete device, delete (local) storage node, create new storage node with the long name (nwserver1.company.lan), scan for new devices, configure library, set device to pool, ready.

And now our networker is running like before

Klaus
 
Well, i did not say that you changed the pool setup. I just wanted to point out that the name change might have the impact on a remote device name which might have an impact on a pool.

Anyway, well done.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top