Indexes going to another Pool

[MiamiXC]

I have set up a new group, a new pool and new instance of an existing client. I have the data being backed-up to teh correct pool, but when NW gets to backing up the indexes, it wants to place them in the Default Pool. How do I tell NW to place the indexes in the same pool as the data itself?

Thanks

 

[spaixpert]

I think the Default Pool has "index:" defined in the save set field. Just remove it.

 

[MiamiXC]

The Default Pool did not have "index" defined in the save set, so that cannot be why the index is going to the default pool.

 

[spaixpert]

check this:

in your client resource, what did you put in the save set field? if it's "All". it should save the index in the same pool as where your data is stored.

check also if the group and pool that this client is a member does not have any save set defined in the "save set" field.

if these does not fix the problem, i'd advise u to go over the admin guide. this is just very simple problem. u may have just miss or click something.

by the way, what version of Networker and platform it is running?

 

[ulsj]

Hi

Check the pool restrictions. The index backup of not level full it goes as a leve 9 backup. If you have some leve restrictons this may be your problem

 

[gerudman]

Hi

I can't think of a reason for your problem, but might give you some ideas as to where it could be. I do not use any level settings in the pool and group configuration and use only schedules.

Thus, say in the Incr pool, I would only select the groups to use this pool as well as the specific drive where it should backup on (if required). Then, in the Incremental group I would only select a Incremental schedule, containing when to backup and when to skip. Basicly the group is then connected to the desired pool and schedule of when to do what level backup.

I'd suggest check all you settings again and re-think the whole process of how you set up your environment.

Hope your problem gets resolved!

George

 

[dkl2002]

On the pool that you are having a problem, did you manually check any of the levels other than full? If you did, anytime this pool is used, the index will go to the Default pool because it is always backed up full, never incremental or differential.

To remedy, either don't check any levels, or if you are trying to do a daily incremental/ weekly full thing, disable the weekly full pool when it's not in use. Pools can be disabled/enabled at the command line using nsradmin.

I have tried reserving specific drives for each pool as gerudman has suggested and it was a fiasco. Legato kept loading tapes labeled for one pool into a drive reserved for another pool. It would then spit it out and reload the same tape, over and over again.

This was some time ago, so that problem may be fixed by now. Test thouroughly...

 

[MiamiXC]

Thanks dkl2002 and uslj. The level of the backup in the Pools option was set. I unselected it and let it be nothing. It then backedup correctly. Thanks again.

Nick