"Petcher, Daniel" <[EMAIL PROTECTED]> wrote:
>
> Best Practices questions:
> -How do I add a backup job that I intend never to run again?
I don't know if I would call it a best practice, but I have a
handful of manual archiving jobs defined that all use the following
schedule resource:
Schedule {
Name = "Manual"
# Run = Level=Full Pool=Default sunday at 10:05
}
Don't know if the commented-out "Run..." line can be safely
removed or not, but I'm including it here since it was in
my running bacula-dir.conf file.
I also don't know if simply omitting the schedule definition line
from the job definition will have the same result, but I think
that it helps make my job configs more readable by saying that
it is a "Manual" schedule. (This will also work for jobs kicked
off via bconsole script input instead of the Bacula scheduler,
FWIW.)
> -How do I clean-up the database after this job is safely ensconsed on
> tape(s)?
You could set a one-day retention period for this job, but my
$0.02 is to leave it in the catalog and keep the bootstrap file
around just in case you need to restore from it. Also, since
Catalog is defined per-client in the config file, you could make
a second catalog for this job so that it doesn't pollute your
default one with archived entries.
Hope this helps.....
-Arthur
-------------------------------------------------------------------------
Arthur Emerson III Email: [EMAIL PROTECTED]
Network Administrator InterNIC: AE81
Mount Saint Mary College MaBell: (845) 561-0800 Ext. 3109
330 Powell Ave. Fax: (845) 562-6762
Newburgh, NY 12550 SneakerNet: Aquinas Hall Room 6
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
