Dave,

Werth, Dave wrote:

Sid,

The reason your backups are asking for Default pool tapes rather than the
pools you set up is likely because you defined your pools too narrowly.
Probably in the backup levels you allow.

For instance, on our Win2K systems, an incremental backup will backup the
file systems at an incremental level but indexes are backed up at level 9
and the SYSTEM STATE & SYSTEM DB are backed up at level full even though
it's an incremental backup.

If your pool for this allows only incremental level backups then it will
fall back to the Default pool for the save sets mentioned above.

In general I've found you should keep the restrictions in a pool to a bare
minimum.

Dave

David Werth
Garmin AT, Inc
(formerly: UPS Aviation Technologies)
(formerly: II Morrow)
Salem, Oregon
dave.werth AT garmin DOT com

-----Original Message-----

From: Sid Martin [mailto:swmartin AT LINK DOT COM] Sent: Monday, February 21, 2005 2:03 PM

To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Scheduling

I want to seperate daily incremental, weekly fulls and monthly full into
different pools. Our existing BU scheduling allows fulls and incrementals
to occupy the same tapes making archiving and tape retention very messy and
requires too much guess work. I have a pool for each category daily
(incremental every day and skips every Sunday. Weekly does a full on every
Sunday except skips the third sunday each month and skips all other days.
Monthly doesa full on only the third Sunday skips every day and all other
Sundays. There is only one selection for schedule and that is on the client.

With your Help I have created 3 client definitions one for each
pool/schedule. The problem now is the ask for tapes from Default pool
instead of the tapes created for each of the seperate pools. Where is
Networker deciding to use the Default tapes???

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

------------------------- This e-mail and any attachments may contain confidential material for the sole use of the intended recipient. If you are not the intended recipient, please be aware that any disclosure, copying, distribution or use of this e-mail or any attachment is prohibited. If you have received this e-mail in error, please contact the sender and delete all copies. Thank you for your cooperation

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--

Ron Short                                       email: short AT sgi DOT com
Solutions Architect                             office: 651/683-5680

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=