-----Original message-----
From: Steven Schlansker <steven AT likeness DOT com>
Sent: Wed 25-01-2012 11:51
Subject: Re: [Bacula-users] Ensuring files made during the backup run are archived (hot-backup PostgreSQL)
To: Martin Simmons <martin AT lispworks DOT com>;
CC: bacula-users AT lists.sourceforge DOT net;

On Jan 25, 2012, at 11:34 AM, Martin Simmons wrote:

>>>>>> On Wed, 25 Jan 2012 09:34:10 -0800, Steven Schlansker said:
>>
>> Looking through the documentation, there's no obvious way to guarantee order or backups within a FileSet.  Is there some particular
>> order that Bacula uses that I can rely on portably?  (I assume not, but would love if there is)  If not, would it be hard to add an
>> option that say ensures that backups recurse in e.g. alphabetical order?
>>
>> I know I could set up two FileSets and two Jobs, but that is both more complex and makes doing differential / incremental backups and restores much more complicated.  I'd prefer to have a single job that does it all.
>
> The problem is larger than just guaranteeing the order -- you also have to
> generate the list of WAL files after the main data files have been archived.
>
> You could make a fileset with two Include sections, one which starts at / but
> excludes the WAL files (with the Exclude = yes option) and other that includes
> only the WAL files.  The main data files would be archived by the first
> Include section.

So, Bacula will process the Include directives in order?  I couldn't find that in the manual, but if
if's true that is exactly what I need.  Thanks!

If you want to be certain that the include files are included in order, you can use a script instead of including the text file itself.

That said, it seems to me that you'd need two jobs anyway. The first job backs up Postgres, the second one backs up the WAL files.

What I would sometimes do in situations like this is define the backup as being as of the second the snapshot is taken, rather than as of when the backup is complete. Any updates (such as the WAL files) since then will be backed up by the next backup run, usually 24 hours later.

The other option I see is, if the database is managably small, to use a Run Before script to take the snapshot, copy the snapshot somewhere else, copy the WAL files, and then back up this copy rather than the original.

------------------------------------------------------------------------------
Try before you buy = See our experts in action!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-dev2

_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users