Default Schedule and Groups not scheduled to run but causing errors

Thanks for your reply, Carlos. All of the groups are associated with the “Default Clone” Clone pool. None of the individual clients are have anything under “Pool”

Is that what you are talking about?

Thanks, Tad

Hi there,

This looks like a misconfiguration of some group, meaning that, as there is no pool linked to that group, NetWorker attempts to use the Default pool, and that's why you get that warning.

Ensure all groups are correctly configured with the pool, in fact ensure that all groups are included in one pool.

Check the pool configuration and ensure that whatever is the group you run when you get that warning is checked in the "groups" area of the Pool configuration.

Thank you.

Carlos.

I think I would go by Carlos.

Additionally please share the daemon.raw from the backup server and client when the error actually comes up.

Tad,

The Default Clone pool is not a backup pool therefore I think this is why you are getting the message.

As Carlos explained earlier if NetWorker cannot work out which pool you have configured there is a catch-all situation which then attempts to use the Default pool. It is recommended Customers do not use this pool as it cannot be edited to allow volumes to be automatically given to other pools etc. Most Customers follow this advise as they get the prompt you are receiving if they add a group and forget to link to a new or existing pool.

Create a new pool or use on of the existing backup pools and once you have a labelled volume/tape in that pool your backups should start to write accordingly.

Hope this helps.

Regards,

Bill Mason

The pool parameter for individual clients may be empty but what Carlos means is different.

Check the Media tab > Media pools

Your group should be part of one of those media pools.

Thanks, I believe I found the suspect Group. I added it to the Weekly pool and hopefully it will behave itself now.

Thanks again