wting / flyback

Automatically exported from code.google.com/p/flyback
0 stars 0 forks source link

Backup not linking to previous fiels #37

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Running backup for teh first time
2. running it again

What is the expected output? What do you see instead?
I should see that the second backup directory has linked to files that are
unchanged but instead I cannot see these files unless I click on the forst
backup I made.

What version of the product are you using? On what operating system?
0.4 ubuntu gutsy gibbon

Please provide any additional information below.
In the output it sasy that it was unable to create a link

Original issue reported on code.google.com by Danyhadd...@gmail.com on 13 Jan 2008 at 11:23

GoogleCodeExporter commented 9 years ago
This can be achieved by using the --link-dest=DIR option to rsync. That option 
is not
currently used in backup_backend.py. I would assume that we would want DIR to 
be the
last backup, so you may need to look in the backup directory and find the most 
recent
(since the user may have deleted a version or what-not).

Although using multiple --link-dest=DIR is possible, I don't see any benefit 
over
just having the most recent backup.

Original comment by ejon...@gmail.com on 31 Jul 2008 at 1:30

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
The --link-dest option is not used, but there is a cp -al performed on the last
backup to initiate the new backup directory, which is basically the same 
thing...

The difference is that it creates hard links for all files, and then rsync 
overwrites
the modified ones. It would probably be better to use the rsync option to avoid
hard-linking the modified files.

Original comment by remi.rer...@gmail.com on 21 Aug 2008 at 10:13

GoogleCodeExporter commented 9 years ago
resolved in v0.5

Original comment by pub...@kered.org on 27 Oct 2009 at 5:06