Safe to start new backup while old increments are being removed?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Safe to start new backup while old increments are being removed?

Florian Hollerweger
Hi,

I recently ran an rdiff-backup while (much) older increments were still being removed via --remove-older-than from the same repository. Is this safe to do?

Although it seems that both processes were eventually completed successfully without throwing any warnings or error messages, I still wanted to make sure I can rely on the integrity of my backup.

The same question has been asked (but not unequivocally answered) at

  http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/rdiff-backup-23/safe-to-remove-old-increments-while-a-backup-runs-124402/

Best,
Florian


_______________________________________________
rdiff-backup-users mailing list at [hidden email]
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Safe to start new backup while old increments are being removed?

Marian 'VooDooMan' Meravy
Greetings,

first of all, I'm not a rdiff-backup guru.

On 2014-12-26 09:43, Florian Hollerweger wrote:
> Hi,
>
> I recently ran an rdiff-backup while (much) older increments were still being removed via --remove-older-than from the same repository. Is this safe to do?

IMO, it is safe.

My environment backs up two times a day, but before each backup it
performs --remove-older-than 4W (i.e. 4 weeks). This is done by on Linux
server by cron, and on Windows environment by task scheduler with cygwin
involved.

Recently, I needed to restore backup from like 4 days ago, and I went
very well...

IMO (but I might be wrong) rdiff-backup tracks in the meta-data files
(gzipped) which are still present to backup, and only removes those
which disappeared like (in my case) in 4 weeks. ALL IN THE LIST: correct
me if I'm wrong...

so IMO it should be fine.

so I recommend --remove-older-than like 1 week, and then immediately
backup today's backup.

E.g. If the frequency of "today's" backup is more than "remove" clause,
then you should be fine.

>
> Although it seems that both processes were eventually completed successfully without throwing any warnings or error messages, I still wanted to make sure I can rely on the integrity of my backup.

yes, there are no error/warning messages... try your own experiment for
like 1 hour and post your resume here.

best,
vdm
.

>
> The same question has been asked (but not unequivocally answered) at
>
>   http://www.backupcentral.com/phpBB2/two-way-mirrors-of-external-mailing-lists-3/rdiff-backup-23/safe-to-remove-old-increments-while-a-backup-runs-124402/
>
> Best,
> Florian
>
>
>
> _______________________________________________
> rdiff-backup-users mailing list at [hidden email]
> https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
> Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki
>

_______________________________________________
rdiff-backup-users mailing list at [hidden email]
https://lists.nongnu.org/mailman/listinfo/rdiff-backup-users
Wiki URL: http://rdiff-backup.solutionsfirst.com.au/index.php/RdiffBackupWiki

signature.asc (836 bytes) Download Attachment