I'd just run into this behaviour when I'd just created a new client
inside of vmware and wanted to "see" it work immediately. I wanted just
the new client and not the group that it was assigned to to be backed
up. So, kick off a manual backup on the client, yes? Well, no since I
don't use the default pool, nor do I have another for non-scheduled
backups. The answer is in the Admin Guide under manual backups. You
cannot depend on group association that is used by any "scheduled"
backups. You must use a tape pool where "manual" is selected since the
backup scheme is handled entirely differently from scheduled backups.
There is no group association for manually backups that are started by a
client.
I also use Stan's method of having specialty groups for both manual and
out of schedule backups. I have a specialty schedule that I adjust for
this run, usually a full backup. This provides the flexibility I
usually need and will put the backups in the right tape pool. Just
remember to "Preview" the group before kicking it off to catch any
unwanted clients that you forgot to uncheck from the group.
I use the Networker scheduler exclusively. It suits our needs just
fine. There are plenty of Networker features that we don't use that are
mighty important to other folks.
(Currently Solaris 9, Networker 7.2.1-1, soon to be RHEL...don't know if
we will jump to 7.3.1 <sigh>)
Patti Clark
Unix System Administrator - RHCT
Office of Scientific and Technical Information
-----Original Message-----
From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
On Behalf Of Sid Shapiro
Sent: Thursday, June 29, 2006 12:10 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: [Networker] Stopping use of the default pool
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...)
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?
Thanks!
oh - btw - Networker server 7.2.1 on Solaris, or HP-UX (got both - both
act the same way...) / Sid /
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
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
|
