Re: [rdiff-backup-users] Backup of changing files

[rdiff]

On Fri, 30 Mar 2007, Baldur Norddahl wrote:
> I want to use rdiff-backup with my Postgresql database. The problem is that 
> the tool refuses to backup files that are changing.

We simply pg_dumpall > /backup/sqldump.sql and then rdiff-backup the 
/backup directory.  Then you don't have to worry about changing files, and 
rdiff works /really/ well on text files :)

-Eric



> The database is live and modifying the database files during the backup. This 
> is fine, because I am using the PITR (point in time recovery) feature of 
> Postgresql.
>
> Using rsync works fine for this purpose. The database files will naturally be 
> damaged on the target, because they changed during the copy. However, the 
> database will create journal log files which can then be used to repair the 
> backup.
>
> All I need is a switch that tells rdiff-backup that it is ok that the target 
> files will not be consistent.
>
> I am aware of an earlier thread on this mail list, which proposes using LVM 
> for freezing the source while doing the backup. This will indeed work for my 
> purpose, but will require extensively reconfiguration of my setup and should 
> be unnecessary. Even using LVM, my backup will be in an invalid state (it 
> equals to a database crash). The LVM option adds a lot of complexity for 
> little gain.
>
> Thanks,
>
> Baldur
>
>
> _______________________________________________
> rdiff-backup-users mailing list at address@hidden
> http://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki