If you are carrying out the repair using --check-destination-dir then I
don't think it will need access to the source directory. All it does is
to roll back the repository to the previous (presumably consistent)
backup point and discard the more recent (inconsistent) data.
If however the repair is proceeding automatically because you are
running a backup session and rdiff-backup has found a previously-failed
backup, then I think you could (if you must) work on the source data
while the repair process is under way. But once the repair is complete
rdiff-backup will immediately proceed to make a new backup from the
source directory - and from this point until completion it would be
better if the source is static.
For the source directory snapshots using LVM (Linux) or VSS (Windows)
can be your friends here.
Dominic
--
*TimeDicer* <http://www.timedicer.co.uk>: Free File Recovery from Whenever
On 08/10/2013 09:09, Jose Heitor wrote:
Hi All,
Can I work with the source-directory files while a repair of a failed
incremental backup is in progress? Or must these remain static during
the entire repair process?
Jose Heitor
Tel: 082 460 9858
Fax: 086 657 1054
j...@heitorprojects.com
Heitor Projects <http://www.heitorprojects.com/>
_______________________________________________
rdiff-backup-users mailing list at rdiff-backup-users@nongnu.org
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
