|
Re: [Networker] Stopping use of the default pool
2006-06-29 12:20:01
On Jun 29, 2006, at 12:09 PM — 6/29/06, Sid Shapiro wrote:
Hello,
( This will probably turn out to be a basic configuration question
- sorry
about that...)
All of our backups are initiated by scripts that are triggered by cron
(unix) or other job scheduling systems. We do not use the scheduler in
Networker. (by the way - does anyone actually use the scheduler? We
need
more precise control over our job streams and timings, which is why we
don't use the Networker scheduler...)
Yup. I use NetWorker's built-in scheduler heavily. The only backup
that I do outside the scheduler is a cron job
that triggers a "savegrp -O" to do index backups.
So in our calling scripts, which use (mostly) the savegrp command, we
specify directly the pool and level values.
Occasionally it would be nice to use the nwadmin GUI group control
to do
manual backups, but whenever we do this, we are always prompted to
load a
device from the default pool. I have tried everything I can think
of to
have it only use a device from the specific pool that I want to be
used,
but nothing works.
I know this is a general question, but without giving you the whole
set of
resources, I don't know what else to tell you. What would you need to
know? Or what specific things should I be looking at?
What I found found works well is to set up a savegroup called "test"
or something similar.
Go into your pools menu and associate that test group with a non-
default tape pool.
Then you can use this test group to run any one-up backups you need
and/or do
investigative work for failing backups.
In fact, I have four test groups (test1, test2, test3, test4) and we
use them all the time, but
none of them are scheduled.
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|
