timo-news AT tee-en DOT net ("Timo Neuvonen") writes:
> "Simon J Mudd" <sjmudd AT pobox DOT com> kirjoitti viestissä
> news:20091206082523.GA612 AT mad06.wl0 DOT org...
> > Hello,
> >
> > I've been using Bacula for some time for home use, and trying to get
> > a working "TimeMachine" type configuration working.
> >
> > That is I'd like to configure bacula to store to an external hard disk
> > using a number of fixed sizes files, occupying up to a certain amount
> > of disk space. In my case 100 x 2GB files. I'd like to auto label
> > new files and purge old ones automatically to make space if needed.
> >
> > This sounds like a simple recipe which is appropriate for a large number
> > of SOHO type situations. I know Bacula can do more, but to minimise
> > intervention this looks nice.
> >
> > However, I don't quite get this to work. I've had issues with getting
> > the auto-label to always work, and also the auto-expire. I wonder
> > if anyone can look at my configuration or offer an alternative to do
> > this?
> >
>
> I guess "Time Machine" is something Apple-like, and I don't know nothing
> about it but the name. But if what you told is the essential, that is the
> disk usage strategy, it shouldn't be a problem though minor differences
> might exist.
Yes, sorry. It's basically a very simple application which comes with the Mac
OS X.
You plug in an external disk and it will backup as much as possible filling up
the
disk. The implementation is quite different but for most people that's all
they want: to "designate a location/size for backups", and then to keep as many
backups as possible in that location. When the disk space fills up the oldest
"backups" are automatically thrown away.
> I didn't notice "Volume Retention" specified in your Pool config. I controls
> how soon after the last write the volumes can be recycled. Since you make
> full backup once a month, this should be set to the minimum of more than one
> month (eg. 40 days) to make sure you'll always have at least one (I'd
> seriously recommend more, at least two) full backup(s) available. After this
> period, if necessary, Bacula _can_ recycle the existing volumes. However,
> actual recycle won't happen until really needed to free the previously used
> volumes, but it can't happen before this time limit has expired.
Yes, but that's what I'm trying to avoid. I realise that I MUST have sufficient
space really for at least 2 full backups plus some extra for incrementals
but I don't want to worry about the details. Therefore I want to configure
the "pool" to auto purge if it fills up. New full or incremental backups
will create new volumes as needed, and the older ones will get purged.
Doing this means I don't get to the point where bacula stops and asks me
to provide new volumes, or runs out of space as older ones have not been
purged.
> Also remember that modifying the pool parameters in the conf does not
> automatically apply to the existing volumes, only to the new ones created
> thereafter. To make the existing volumes to obey the new values, you'll need
> to use the update pool / update volumes from pool commands from the bacula
> console.
Perhaps that is what I've been missing. I've adjusted parameters and haven't
noticed if things were working as expected.
As I say that's why I'm looking for a simple "recipe" to do this which
will help me but probably will be EASY to configure for a large group of
SOHO type users who don't want to worry about the more complex issues
of having separate pools for FULL or incremental backups etc.
Simon
------------------------------------------------------------------------------
Join us December 9, 2009 for the Red Hat Virtual Experience,
a free event focused on virtualization and cloud computing.
Attend in-depth sessions from your desk. Your couch. Anywhere.
http://p.sf.net/sfu/redhat-sfdev2dev
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
