-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Henning Holtschneider wrote:
> Rowdy wrote:
> 
>> I do similar to what Ger indicated (I have 2 hard drives alternating in
>> an external USB enclosure connected to a box running Bacula under
>> FreeBSD), but set the status to Used rather than Full.
> 
> That sounds good. The volume status update can be automated as a Run 
> Before Job script, i.e. check which volumes are available and mark all 
> other volumes as Used (or Full).
> 
> But what do I set the status to when I want to re-use the volumes marked 
> as Used or Full before? Will volstatus=Purged result in the database 
> records being purged as soon as the volume is actually being written to 
> or will I be left with a huge pile of orphaned database records after a 
> while? I already experienced that it's no good idea to set 
> volstatus=Append because this will cause Bacula to append to the volume 
> beyond the "Maximum Volume Bytes" setting, which will in turn cause a 
> serious deadlock of Bacula once the USB disk runs out of free space :-/ 
> Or will the volume be purged automatically once the volume retention 
> period has been exceeded?

Greetings,

In my situation I have about 6 servers being backuped to the hard
drives, and each server has an auto-labeled file on the drives
consisting of the server name and date.  Each file is created at 1am on
a Saturday morning for the full backups, and appended to each morning
thereafter for the differentials.

Each Friday morning I run a script to set the volume stati to Full,
physically swap drives, and remove files from 2 weeks ago from the new
drive (each drive holds 2 weeks of backups for all servers).

When Bacula starts the full backups the next day, Saturday, it will
automatically create and label a new volume (and file on the hard drive)
for each server.

Yes, there are a few manual steps in there, but the biggest of those is
the physical swapping of the hard drives, so the few extra seconds to
run a script to update volume stati is insignificant.

Eventually Bacula expires the very old volumes and deletes them from the
catalog, but you could either do that manually or set the
VolumeUseDuration or the MaxVolumeJobs options, as Ryan suggested, to
cater for that automatically.  I have not setup anything automatic at
the moment as we are in the process of decommissioning some old servers
and commissioning some new servers, and I am hoping to streamline
backups and maybe squeeze a few more files onto the hard drives.

Rowdy
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFE1dRAk3YP87Xv5cYRAlv6AJ9EKxQQaF3hgqDJCx7SR5OG/pNu7gCdEwIy
XJsIMtZMzNdYO8+vUNtJfHQ=
=tSo3
-----END PGP SIGNATURE-----

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys -- and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to