Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations dencom on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Index save set

Status
Not open for further replies.

DaiHawkins

Technical User
May 24, 2007
49
US
NW 7.2.1 - Windows Server 2003
I have a goup called TEST set up which writes to the Test Pool.
When i run a full backup the job completes without problems, however when i run an Incremental job, i get the message, waiting for 1 writeable volume to backup pool 'Default' and this sits there until i stop the job.
 
Most likely you are using the 'level' selection criteria for your pool. The issue is that for incremental backups, the index is backed up with level 9 which you obviously not selected as well.

As the pool does not match, NW uses another pool trying to serve you the fastest way. Worst case it will use the pool Default. This is what you see.
 
Thanks for the reply. As you are aware i am a newbie to NW.
How woul di go about rectifying this problem; are you saying select level 9 and not incremental ?
 
Sure. A pool has 4 selection criteria to be followed top down:
groups
clients
save sets
levels

If the first three criteria match, then the level will become a differentiater. Consequently, if you want to use the pool for (fulls), incrementals and level 9 backups you must check the levels (full), incremental and level 9.

Or you do not specify the level at all and use the other criteria for selection.
 
Thanks, that worked, but then on another incrementall it was looking for a different pool to save the bootstrap to.

What i have set up is a pool for incremental backups - run daily
in the pool i have incr and level 9 set
and a pool for full backups - run weekly
in this pool i have full level set.

is this the right way to be going about things?
 
I would recommend pools per functionality:
- for the client backups
You may setup two pools (for fulls & incrementals) but i would not recommend it
- for the NW database backups (index & bootstraps)
This is better for the consolidated recovery of the NW databases

What ever policy you setup - it must comply to your rules which i do not know.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top