What does this error REALLY mean?

[rangerbob]

Tue 08:02:17 PM media waiting event: Waiting for 1 writable volumes to backup pool 'Default'tape(s) on blah.blah.com

There is indeed a pool called 'DEFAULT' It is factory installed, cannot be modified or deleted.

In the setup I have, I can find absolutely no location where 'DEFAULT' is called. That is probably because I don't know where to look, right?

I have one client currently, and two groups that I have enabled: Full and Not Full. I have also two customized pools, Full and NotFull, which are the only two pools associated with the server blah. So why is it trying to find something from the 'DEFAULT' group?

I will provide any information needed to try and trouble shoot this problem. Thanks in advance for the help.


Still confused,

RangeR BoB

 

[VicMcD]

Calling the save command without specifying the -b (pool) option causes Legato to use the default group. Using the Networker User icon to backup files from the client also calls for the Default pool. I cannot find a way to change it.
Also creating a new group and not associating it with any tape pool will cause it to use Default

 

[sendhilk]

what are the backup levels of the full and not full groups that u have created. check the pools that u have created and see if u have enabled them for that group. u will see all the groups listed under that pool and click on the group u want that pool to use. there is an option for leven of back up too.. 1 to 9 , full and incremental, based on what schedule u ahve given for ur client click that for that corresponding pool. it shud now pick up from the pool u have configured..

 

[rangerbob]

I have two custom pools, Full and NonFull. They are associated with groups Full and NonFull respectively. Neither is associated with Default.

It appears that Networker is trying to back up "bootstrap" information to the default group. Any way to make it NOT do this?

Of course this doesn't seem to be covered in any readable form in the book. Maybe I missed it.

Thanks so much for hte suggestions!

 

[jmdc]

What works for me is edit your pool. Under clients make sure this is empty. If all the clients you need to backup are already in the group you have choosen then you don't need to specifiy anything in the client section. This worked for me. Hope this helps

-Justin

 

[VicMcD]

The bootstrap is saved to various different pools.
See Extract
Check your daemon.log for these messages and hopefully this will identify the backup that is using the default pool


Extract from daemon.log

04/02/01 12:05:27 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/03/01 07:42:19 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0005)
04/03/01 12:07:13 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/04/01 06:27:14 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0140)
04/04/01 12:04:53 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/05/01 09:25:55 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0133)
04/05/01 12:06:00 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/06/01 08:06:23 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0149)

 

[VicMcD]

The bootstrap is saved to various different pools.
See Extract
Check your daemon.log for these messages and hopefully this will identify the backup that is using the default pool


Extract from daemon.log

04/02/01 12:05:27 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/03/01 07:42:19 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0005)
04/03/01 12:07:13 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/04/01 06:27:14 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0140)
04/04/01 12:04:53 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/05/01 09:25:55 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0133)
04/05/01 12:06:00 nsrd: sapprda:bootstrap saving to pool 'Long Term Archives' (AR0048)
04/06/01 08:06:23 nsrd: sapprda:bootstrap saving to pool 'Production' (PR0149)

 

[rangerbob]

04/06/01 04:01:48 AM nsrd: media event cleared: Waiting for 1 writable volumes to backup pool 'Default'tape(s) on altec.sps.
mot.com
04/06/01 04:01:48 AM nsrd: altec.sps.mot.com:index:altec.sps.mot.com saving to pool 'Default' (altec.sps.mot.com.003)
04/06/01 04:01:58 AM nsrd: altec.sps.mot.com:index:altec.sps.mot.com done saving to pool 'Default' (altec.sps.mot.com.003) 17 MB
04/06/01 04:01:58 AM nsrd: altec.sps.mot.com:bootstrap saving to pool 'Default' (altec.sps.mot.com.003)
04/06/01 04:01:58 AM nsrmmdbd: media db is saving its data. This may take a while.
04/06/01 04:01:59 AM nsrmmdbd: media db is open for business.
04/06/01 04:01:59 AM nsrd: altec.sps.mot.com:bootstrap done saving to pool 'Default' (altec.sps.mot.com.003) 48 KB
04/06/01 04:01:59 AM nsrd: savegroup notice: Full completed, 1 client(s) (All Succeeded)

 

[VicMcD]

The two pools you are using come as defaults with Legato.
I tried a little test by associating the group testing234 with the pool Full. the pool has no tapes associated with it and has the settings Pool type Backup and Label template Full. When I started the group I got the following message:-

04/09/01 12:59:59 nsrd: savegroup info: starting testing234 (with 1 client(s))
04/09/01 13:00:09 nsrd: media info: Labeling a new writable volume for pool 'Default'
04/09/01 13:00:11 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool
'Default'tape(s) on sapprda

I then enabled the pool Full and started the group again.

I then got the following message :-

04/09/01 13:07:41 nsrd: savegroup info: starting testing234 (with 1 client(s))
04/09/01 13:07:50 nsrd: media info: Labeling a new writable volume for pool 'Full'
04/09/01 13:07:50 nsrd: media waiting event: Waiting for 1 writable volumes to backup pool
'Full'tape(s) on sapprda

Note the change to pool "Full"
Can you check that the pools Full and Non-full are enables ?

 

[rangerbob]

The pool "full" has these settings:

Name: Full
Enabled: Yes
Pool Type: Backup
Groups: Full
Clients _____
SaveSets All
Levels Full
Devices: ____
Store Index Entries: Yes
Auto Media Verify: No
Recycle to other pools: Yes
Recycle from other pools:No
Volume Type Preference: _____

Group:
name: Full
AutoStart: Enabled
Start Time: 3:33
Client Retries: 1
Clones: No
Clone Pool: Default Clone
Migration Clone: Migration CLone
Printer: ____

It ran all of the save groups this weekend, and here is the output for that:


NetWorker Savegroup: (notice) Full completed, 1 client(s) (All Succeeded)
Start time: Fri Apr 6 14:03:41 2001
End time: Fri Apr 6 19:01:20 2001

--- Successful Save Sets ---

altec.sps.mot.com: /opt level=full, 1026 MB 00:48:41 37062 files
altec.sps.mot.com: / level=full, 1092 MB 01:02:02 41298 files
altec.sps.mot.com: /usr level=full, 852 MB 00:45:20 48443 files
altec.sps.mot.com: /var level=full, 53 MB 00:03:20 4495 files
altec.sps.mot.com: /home level=full, 19 GB 04:56:49 389613 files
altec.sps.mot.com: index:altec.sps.mot.com level=full, 107 MB 00:00:43 21 files
altec.sps.mot.com: bootstrap level=full, 81 KB 00:00:01 6 files


The bootstrap part I believe is what goes in the default group, and it seems to be a hell of a waste of a 12 Gb tape to sace 81k of data to it.

So at least I am getting all of the data to various pools, now if I could get rid of the silly need for the default...

Thanks all for hte help.

Ideas?

 

[sendhilk]

please go thro this link.. u may find this useful

http://web1.legato.com/lefaq/html/pchart.htm

Sendhil

 

[rangerbob]

Thanks that's a great link!

 

[bozsoki]

HEllo,

Two possibilities.

1. Is the pool enabled? IF not enable it, if so...
2. You must select level 9 on one or both of the pools to avoid writting the bootstrap to the Default pool.

cheers

 

[falchion]

I'm having this exact prpoblem, following an upgrade from 5.1 to 6.1. Did you get any resolution? I know it can be fixed, just not how...

 

[keefb]

Looks like this is trying to use the default pool to write the index and bootstrap to, you can prevent this by directing all bootstrap and index backups to a pool of their own. To do this try the following, found this most useful on our system.

1) within nwadmin create a new label template called index

2) create a new pool called index

the pool type is backup
label template is the new one created in step 1
add the groups in the index pool
tick the drives that the index pool will be allowed to use
define the savesets for the index pool as below

bootstrap
index:*

everything else can be left as it is

3) label a volume into the index pool

4) run a test backup of a group and watch to make sure the indexes and the bootstrap are written to the new index pool and not the tape that the data has been written to