I needed to set up my diskspace for the director to produce the
following backup files on disk:
/nfs-mounted-point/client-name/[week or mon-sat]/labeled-disk-space
where nfs-mounted-point is an NFS directory set up on a separate
server from where I run the Bacula director,
client-name is the server running the Bacula client software,
week/mon/tue/wed/thu/fri is just that, so in the schedule I send to
the write day of the week for the daily differential and the week is
for the full weekly backup,
the labeled-disk-space is using Bacula's label command to create the disk space.
Then, in the director config file, I set up a JobDef with the common
parameters, followed by a Job statement for each client. Each client
has its own schedule. In the Schedule directive/statement, one per
client, I force it to use a pool and storge so I can control where it
writes. An example for one client is as follows
Schedule {
Name = "NYWeeklyCycle"
Run = Level=Full Storage=NYFileWeek Pool=NYWeeklyPool Sat at 6:00pm
Run = Level=Differential Storage=NYFileMon Pool=NYMonPool Mon at 8:00pm
Run = Level=Differential Storage=NYFileTue Pool=NYTuePool Tue at 8:00pm
Run = Level=Differential Storage=NYFileWed Pool=NYWedPool Wed at 8:00pm
Run = Level=Differential Storage=NYFileThu Pool=NYThuPool Thu at 8:00pm
Run = Level=Differential Storage=NYFileFri Pool=NYFriPool Fri at 8:00pm
}
Then, each Storage directive points to the appropriate device in bacula-sd.conf.
I have been using Bacula since Monday so I suspect I am making some
gross mistakes here. does this approach for controlling the creation
of my diskspace make sense?
-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
