Bootstrap (and index?) wanting to go to pool default.

Question

I have been working on this for the best part of a day. All I want is to be able to backup the client to a single tape without needing to add anothr tape.

networker 7.6 sp3

The scenario is as basic as basic can be. One backup server (BS1) with one tape drive. One client (client1), (eventually there will be three more clients.)

client1 has two directories specified in its save set

/data1 and /data2

client1 is in the group client1_group and backups go to pool client1_pool.

I was told that under "save sets" in "client1_pool" I should put "All", "index" and "boostrap" on three separate lines.(but this had no effect)

When i do a test using savegrp -p client1_group

It shows the everything going into "client1_pool" including "Probe" and "index" (there is a line saying "nsrim run recently skipping"). There is no mention of "default", and looking at it you would not see a problem.

However when starting the backup from the console (using the start icon), It works as expected backing up the two directories, but just when you think it has reached 100% the status bar goes to 66% and asks for a tape in the default pool. Annoyingly it just says somethign along the lines of " I want a default tape", it does not say what for.

I have added a default tape, and the backup completed. I got this message in the logs after the default tape it loaded.

"Added 'BS1' to the group client1_group for bootstrap backup".

I then get a summary of the completed backup along the lines of

*****

client1:probe succeeded

client1:./data1 level=full 13 files

client1:/data2 level=full 12 files

BS1: index:client1 level=full 17 files

BS1: bootstrap level=full 129 files

*****

CarlosRojas · Accepted Answer

Hi John,

Sorry, I understood you wanted to have index and bootstrap in a separate pool.

I would say that you need to remove the "index" and "bootstrap" savesets from any pool, otherwise those savesets will be to the pool where you specified those savesets to go to.

By default you don't need to restrict any pool to use those savesets unless you want those 2 to go to that particular pool.

In other words, leave the pool configuration by default (index and bootstrap should not be included in any pool) and that should send the backup data, indexes and bootstrap to a single pool.

If there are tapes enough labeled for tat pool then all the data, including index and bootstrap should go to the same pool.

Thank you.

Carlos

CarlosRojas · Answer

Hi John,

As per documentation, this is the configuration you should set:

To send the NetWorker server’s bootstrap and client file indexes to the same media pool, create a media pool (in the Media Pool resource) with the values listed for the attributes in Table 27 on page 186.

Attribute Value

Name Index

Pool Type Backup

Save Sets Bootstrap

Index

When the group’s scheduled backup runs, the client save sets are written to a volume labeled for the appropriate save set media pools, while the NetWorker server’s bootstrap and index save sets are written to a separate volume labeled for the Index media pool.

Thank you.

Carlos.

deaddog · Answer

I'm afraid I still get the prompt 'waiting for 1 writable volume(s) to backup to pool 'default''. Can we approach this another way, can I stop the index and bootstrap fropm being backed up? Maybe its not a good idea, but all this messing around with 'index and bootstrap' tapes, is not practical for us.

deaddog · Answer

Thank you for your quick reply. 'When the group’s scheduled backup runs, the client save sets are written to a volume labeled for the appropriate save set media pools, while the NetWorker server’s bootstrap and index save sets are written to a separate volume labeled for the Index media pool.' but this is what I dont want to happen. I want to start the backup on a Friday evening, and come to work on Monday morning to see 'backup completed', not 'please insert a second tape'. I want the backup data, index and bootstrap  to go onto the same tape.

deaddog · Answer

Okay.

It looks like my error was in not putting the backup server under clients in the "selection criteria" tab in the relevant pool.

(I also created a new group just for the backupserver and put that group in "groups" in the relevant pool)

CarlosRojas · Answer

Hi John,

I would really NOT recommend not having index nor bootstrap backup, I would encourage you to troubleshoot this issue rather than avoid that backup.

What are the values you have for the Default pool and the client1_pool pool?

Please share the information of the 3 tabs, some screenshots would be great.

Thank you.

Carlos

deaddog · Answer

Turns out theat wasn;t the solution either. Soon as another client was brought online and we tried to do the same thing it complained along the lines of overlapping criteria. Anyway networker has beaten us. We have arranged for a refund from the suppliers (four days wasted on trying to get it to backup a client without wanting one tape for the data and one tape for the bootstrap). I recommend backup exec, for anyonewanting something "intuitive".

Networker looked a good product but "geeks only" I think. A quick google reveals it's known for its complexity (not surprising coming from Ever More Complicated)

By the way "notification to printer" -LOL. Would that be a dot matrix printer by any chance?

I'll leave you guys to your pools, clients, groups, schedules, directives and god knows what else.

NetWorker

Bootstrap (and index?) wanting to go to pool default.

Was this post helpful?