Problem in Pools Configuration?

Question

I have created a group and a pool. I have marked the group name in the pool properties. It worked fine for few months. But now without any change in configuration when I run scheduled backup of the same group it throws warning 'Waiting for a writable volume in pool Default'. I have rechecked the pool properties but there is group checked. What is the cause and remedy of the problem?

vsemaska · Answer

I've had something like that happen. In my case somehow the pool was no longer marked 'Enabled'. So check to make sure the pool in enabled.Vic

IKP1 · Answer

Hi,Have you checked there is free media in the pool your group is assigned to as NetWorker has a 'built-in' safety feature that will attempt to use media in the default pool if it unable to find available media in the assigned pool.HtHIKP

Yogendra4 · Answer

In my case the pool is enabled. I have rechecked it.

Yogendra4 · Answer

In the pool of the group media ia available but there is no media in default pool.

IKP1 · Answer

If you have free or available media in the pool linked to the group, and still NetWorker is trying to access the default pool, this suggest that you have a configuration issue. Have you checked that there are no groups associated with the default pool ?

From the GUI, select the default pool and check that non of the groups is selected.

IKP

Yogendra4 · Answer

I have cheched and there is no group assigned to default pool.

IKP1 · Answer

Hi,Can you run the save group from the command line with very very very verbose logging and post the output to here. However, before you start the group please ensure that there are no other backup groups running and therefore no outstanding mount requests.IKP

Yogendra4 · Answer

HiI have just restarted the NetWorker services and again run the scheduled backup. This time the data started to go in the right pool.Yogendra

Yogendra4 · Answer

Restart the services and the problem gets solved.

mfriedma · Answer

The message you have received is probably a result of a failure to probe the client for data to be backed up. In this case NW will just write the index, and I assume is the reason it is waiting for a tape in the Default group. Restarting the services on the client and the elimination of this issue is just a proof that the NW server could not contact the nsrexecd process on the client.

HTH

ble1 · Answer

Normally, if there are no device restrictions in case of remote storage nodes or dedicated pools, NW will writ into same pool and not Default. There used to be a buggy version on the other hand where failure to run probe first time would ask for Default pool tape (so not just index&bootstrap but data itself would get written into Default pool). Usually you could see that by looking at logs where first probe would fail, but next retry would work (using Default pool).

NetWorker

Problem in Pools Configuration?

Was this post helpful?