Problem default pool legato

[mahalingam1]

Hi all,

I´m working with legato networker 7.0. I have the following problem with one client belonging to a one group.

When i start the backup of this group networker ask for one volume of default pool, but this client belong to another pool. I was checked the client and the group and don't have any properties belonging to the default pool.

If abort the backup and them restart networker in the client the problem persists.


I must restart networker on both sides, the client and the server In order that the problem is solved


This client belongs to another group. When this group is started this client is skipped, but networker don't ask for a volume of pool default.

Please anyone can help me???


Thanks in advance and regards

 

[605]

If not specified else in the pool's client list, a pool can accept data from any client. And this is true for "Default" as this is the emergency pool which you can not change.

The reason for your problem is that your settings for a certain pool are not matched by all your save sets. For NW to be able to continue, its only chance is to use another pool (if such exists) or "Default" in worst case. So the behavior is fully intended.

- Go and check with save set(s) is causing trouble
- Verify its criteria with the parameters of the pool you want the backup to go to
- Change the settings accordingly or
- Create a new pool with appropriate settings

One last thing:
Be careful if you use the three standard pools "Full", "Nonfull" and "Offsite". These are disabled by default!
However, you may label media for them.

 

[mahalingam1]

Hi 605!!!

I had checked all save sets belonging to this group and all have the same configuration.

Today the backup fails. I have restarted the nw on client and server but NW asked for a volume of pool default.

Then I mounted the volumen that the group needs and restart the backup and it was done without problem.


I checked the legato deamon.log and i found :

07/22/08 09:17:15 savegrp: command 'save -s teide -LL -m alamo -t 1216625551 -l incr -q -N /almacen /almacen ' for client alamo exited with return code 9.
* alamo:/almacen Connection refused


I dont understand why one time the connection is refused but in the second time the backup finish without problems.


maybe it's due reverse name resolution from the DNS???


Thanks and regards

 

[605]

Connection refused" is typically a response due to the fact that the server is not authorized to contact the client. This is usually due to the fact that the file /nsr/res/servers at the client does not contain the server's name or the server is de facto using another name (name resolution might be an issue).

To correct that, edit the file appropriately and restart the client daemon/service (nsrexecd).

For the pools, it might help if you let you know the pool configuration. However, i might think what the reason could be: If you run incremental backups, the index backups will have level 9. So if you have your pool setup for incrementals, these backups are not allowed to use the same pool.

 

[mahalingam1]

hi 605

I have checked the file /nsr/res/servers and the name of the server is OK. This server name is the same that on another client that works fine.

In the Levels field of the pool we don't mark anything for the allowed levels of the pool.

What puzzles me is why when i restart the NW on the server and client the connection is allowed, but if i launch or restart the backup without reboot of NW the connection is not allowed. If this issue was due to reverse name resolution off DNS the behavior of the backup will be the same, the connection is allowed or not but not will switch between this two states, connection allowed or not allowed


Thanks and regards

 

[605]

Let's put the pool problem aside for the moment. This is what you will find in the manpage about "Connection refused":

This means the client machine is up, but it is not accepting new network connections for nsrexecd (or rshd). This could mean the client was in the process of booting when the savegrp attempted to connect, or that the client had exceeded some resource limit, and was not accepting any new connections. You should attempt to log into the client and verify that it is accepting remote connections. If the client is a nonUNIX machine, you may need to start the NetWorker client on that machine. Refer to your ClientPak installation for
more information.

Unfortunately, we can not look at your system to do further investigations.

 

[mahalingam1]

Hi 605!!

The problem was due the machine had two different IP entries in /etc/hosts for the same name.

I corrected this issue and the backup was fine.

Thank you very much for your help.

Regards