Now that there's some removal of increments for old fulls, we can keep fulls for a longer time, for instance 1Y which becomes default

Conflicts:
	AUTHORS
	ChangeLog

Thanks to Ian Beckwith for the patch.

Thanks to Sergio Talens-Oliag <sto@debian.org> for the bug report and patch.

Conflicts:

	ChangeLog

older versions (lenny) of lvm2 have a bug in vgcfgbackup that makes it so when you specify multiple volume groups to backup, it gives an error, saying you must set the %s template for the name. We are doing that, it just cannot handle it properly.

This change routes around this issue, which has been fixed in later lvm2 releases, by passing only one argument to vgcfgbackup by taking all the volume groups that are found and running them through a for loop

Conflicts:

	ChangeLog

Jacob Anawalt authored 14 years ago and intrigeri committed 14 years ago

Removed an extra '.' in file names introduced by the pg_dump options
patch, resulting in names like db..sql or db..sql.gz instead of just
db.sql or db.sql.gz.

older versions (lenny) of lvm2 have a bug in vgcfgbackup that makes it so when you specify multiple volume groups to backup, it gives an error, saying you must set the %s template for the name. We are doing that, it just cannot handle it properly.

This change routes around this issue, which has been fixed in later lvm2 releases, by passing only one argument to vgcfgbackup by taking all the volume groups that are found and running them through a for loop

Closes Roundup bug #598.

This breaks support of Debian etch.

Jacob Anawalt authored 14 years ago and intrigeri committed 14 years ago

The format option of pg_dump enables tar and custom archive file formats in
addition to the default plain-text file containing SQL commands.

When either the tar or custom format are selected the behaviour of database=all is changed to no longer dump a single file via pg_dumpall. Instead pg_dumpall
is called once to export the "global" data (roles & tablespaces) and then
pg_dump is called once for each non-template table in the database.

To support the GZIP and GZIP_OPTS variables in backupninja and to give the
default --rsyncable gzip compression flag a chance at working on a PostgreSQL
backup, the custom output is forced to not use compression. Instead compression
is done via a pipe to gzip. Hopefully this benefits rsync and rdiff-backup
style backups for reduced backup and storage costs that outweigh the
restoration ones.