Re: [rdiff-backup-users] How will rdiff-backup behave if I rename files?

[dean gaudet]

rdiff-backup won't handle this cleanly.  it will treat all the newly named 
files as new and keep deltas deleting the old names... so yeah it'll 
double your space requirements until you age the old deltas.

the inode is used for hardlink detection only... not renaming 
unfortunately.

mind you i've never investigated what it would do if you hardlinked, did a 
backup, then deleted the original...

if your boxes are separated by a narrow pipe and you'd like to avoid 
retransferring everything you can delete the history (rdiff-backup-data 
subdir), and rename the mirror, and then use rdiff-backup --force to 
create a new history... or maybe use rsync's --fuzzy option once...

-dean

On Wed, 14 Jun 2006, Erik Forsberg wrote:

> Hi!
> 
> Currently, filenames on our NFS servers (backed up with rdiff-backup)
> are coded using iso-8859-1. We're thinking about switching to utf-8
> for filename encoding (and file content encoding as well, but that's
> less relevant here). 
> 
> Will rdiff-backup cope with this situation nicely, or will all renamed
> files be treated as delete old filename + new file, causing a need for
> more storage space on the backup server? 
> 
> I'm confused on whether the inode is used by rdiff-backup or not. I'm
> running rdiff-backup 1.1.5. 
> 
> Cheers,
> \EF
> -- 
> Erik Forsberg                OpenSource-based Thin Client Technology
> Systems Analyst/Developer    Phone: +46-13-21 46 00    
> Cendio AB                  Web: http://www.cendio.com
>                            
> 
> 
> 
> _______________________________________________
> 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
>