Deprecated: __autoload() is deprecated, use spl_autoload_register() instead in /home/pbuc/public_html/forum/mods/ext_phorummail/ezc/Base/src/ezc_bootstrap.php on line 36

Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; KeyCAPTCHA_CLASS has a deprecated constructor in /home/pbuc/public_html/forum/mods/keycaptcha/keycaptcha.php on line 108
Missed backup, ok to run again?
Welcome! » Log In » Create A New Profile

Missed backup, ok to run again?

Posted by Anonymous 
Missed backup, ok to run again?
November 07, 2014 09:40AM
Hi venerable rsnapshot experts!
I’ve got a pretty standard setup here with these options at their defaults:

#sync_first 0
#use_lazy_deletes 0

The backup runs every morning at 1AM

This morning the connection went down and all the backups apart from a couple returned 255 errors:

[07/Nov/2014] /usr/bin/rsnapshot daily: ERROR: /usr/bin/rsync returned 255 while processing xxxxxxxx

Am I ok just to run snapshot daily again to get it to take todays copy?

Thanks,
Chris.
--
[url=http://chrispyfur.net]chrispyfur.net[/url]
Missed backup, ok to run again?
November 07, 2014 10:47AM
Hallo, Chris,

Du meintest am 07.11.14:

[...]

[quote]The backup runs every morning at 1AM
[/quote]
[quote]This morning the connection went down and all the backups apart from
a couple returned 255 errors:
[/quote]
[quote][07/Nov/2014] /usr/bin/rsnapshot daily: ERROR:
/usr/bin/rsync returned 255 while processing xxxxxxxx
[/quote]
[quote]Am I ok just to run snapshot daily again to get it to take todays
copy?
[/quote]
Just try it. If this second run also produces the above error messages
then examine the backup disk ...

Viele Gruesse!
Helmut

------------------------------------------------------------------------------
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Missed backup, ok to run again?
November 07, 2014 11:00AM
Chris,

You might want to check first that daily.0 looks similar to daily.1,
for example about the same disk usage and for a few random files X/Y/Z
that daily.0/X/Y/Z and daily.1/X/Y/Z are hard-linked together - unless
rsnapshot successfully did a backup of X/Y/Z and it changed recently.

The risk is that if the backup failed without fully populating daily.0
with hard links (eg with cp -al) then some of the files on your next
backup might be treated as new files (rsynced across the network in
full, and using up extra disk space because the "new" files won't be
hard linked to your current daily.1 and older backups).

I think this scenario is unlikely unless you have "link_dest 1" in
your rsnapshot config (and perhaps some other things), but it might be
worth checking that daily.0 looks right before you do your next backup,
just in case.

I assume you don't particularly mind that doing an extra backup means
that another daily backup from 6-7 days ago will be deleted (so one
of your "weekly" backups will end up having only about 6 actual days
spacing between them).

If that does really concern you, then you can delete daily.0 (assuming
that is the failed backup) and move daily.1 to daily.0, move daily.2
to daily.1, daily.3 to daily.2, ... and daily.6 to daily.5.

Then you can just go ahead and run rsnapshot daily again.

On Fri, Nov 07, 2014 at 09:21:11AM +0000, Chris Tebb wrote:
[quote]Hi venerable rsnapshot experts!

I’ve got a pretty standard setup here with these options at their
defaults:

#sync_first 0
#use_lazy_deletes 0
The backup runs every morning at 1AM
This morning the connection went down and all the backups apart from a
couple returned 255 errors:
[07/Nov/2014] /usr/bin/rsnapshot daily: ERROR: /usr/bin/rsync
returned 255 while processing xxxxxxxx
Am I ok just to run snapshot daily again to get it to take todays copy?
Thanks,
Chris.
--
[1]chrispyfur.net

References

1. http://chrispyfur.net/
[/quote]
[quote]------------------------------------------------------------------------------
[/quote]
[quote]_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
[/quote]

--
___________________________________________________________________________
David Keegel <djk < at > cyber.com.au> Cyber IT Solutions Pty. Ltd.
http://www.cyber.com.au/~djk/ Linux & Unix Systems Administration

------------------------------------------------------------------------------
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Missed backup, ok to run again?
November 07, 2014 11:44AM
syncfirst will make this work much better, if the backup fails, you can
just run it again, because it spends most of its time in rsync, except
for the last second.

David Keegel <djk < at > cyber.com.au> wrote:

[quote]Chris,

You might want to check first that daily.0 looks similar to daily.1,
for example about the same disk usage and for a few random files X/Y/Z
that daily.0/X/Y/Z and daily.1/X/Y/Z are hard-linked together - unless
rsnapshot successfully did a backup of X/Y/Z and it changed recently.

The risk is that if the backup failed without fully populating daily.0
with hard links (eg with cp -al) then some of the files on your next
backup might be treated as new files (rsynced across the network in
full, and using up extra disk space because the "new" files won't be
hard linked to your current daily.1 and older backups).

I think this scenario is unlikely unless you have "link_dest 1" in
your rsnapshot config (and perhaps some other things), but it might be
worth checking that daily.0 looks right before you do your next backup,
just in case.

I assume you don't particularly mind that doing an extra backup means
that another daily backup from 6-7 days ago will be deleted (so one
of your "weekly" backups will end up having only about 6 actual days
spacing between them).

If that does really concern you, then you can delete daily.0 (assuming
that is the failed backup) and move daily.1 to daily.0, move daily.2
to daily.1, daily.3 to daily.2, ... and daily.6 to daily.5.

Then you can just go ahead and run rsnapshot daily again.

On Fri, Nov 07, 2014 at 09:21:11AM +0000, Chris Tebb wrote:
[quote]Hi venerable rsnapshot experts!

I’ve got a pretty standard setup here with these options at their
defaults:

#sync_first 0
#use_lazy_deletes 0
The backup runs every morning at 1AM
This morning the connection went down and all the backups apart from a
couple returned 255 errors:
[07/Nov/2014] /usr/bin/rsnapshot daily: ERROR: /usr/bin/rsync
returned 255 while processing xxxxxxxx
Am I ok just to run snapshot daily again to get it to take todays copy?
Thanks,
Chris.
--
[1]chrispyfur.net

References

1. http://chrispyfur.net/
[/quote]
[quote]------------------------------------------------------------------------------
[/quote]
[quote]_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
[/quote]

--
___________________________________________________________________________
David Keegel <djk < at > cyber.com.au> Cyber IT Solutions Pty. Ltd.
http://www.cyber.com.au/~djk/ Linux & Unix Systems Administration

------------------------------------------------------------------------------
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
[/quote]
--
Your life is like a penny. You're going to lose it. The question is:
How do
you spend it?

John Covici
covici < at > ccs.covici.com

------------------------------------------------------------------------------
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Missed backup, ok to run again?
November 07, 2014 12:13PM
On Friday, November 07, 2014 06:57 PM, David Keegel wrote:
[quote]Chris,

You might want to check first that daily.0 looks similar to daily.1,
for example about the same disk usage and for a few random files X/Y/Z
that daily.0/X/Y/Z and daily.1/X/Y/Z are hard-linked together - unless
rsnapshot successfully did a backup of X/Y/Z and it changed recently.

The risk is that if the backup failed without fully populating daily.0
with hard links (eg with cp -al) then some of the files on your next
backup might be treated as new files (rsynced across the network in
full, and using up extra disk space because the "new" files won't be
hard linked to your current daily.1 and older backups).

I think this scenario is unlikely unless you have "link_dest 1" in
your rsnapshot config (and perhaps some other things), but it might be
worth checking that daily.0 looks right before you do your next backup,
just in case.
[/quote]
I encountered this situation once with an empty daily.0 and it took a
long time in the next backup to copy over all the missing files. :-(

Can you explain more about the link_dest options? The man page of
rsnapshot says that "If your version of rsync supports --link-dest
(2.5.7 or newer), you can enable this to let rsync handle some things
that GNU cp or the built-in subroutines would otherwise do. Enabling
this makes rsnapshot take a slightly more complicated code branch, but
it's the best way to support special files on non-Linux systems." and I
had presumed that it's a safer setting even for linux systems. If that's
not the case, then there's no advantage of setting it to 1 on linux systems.

Is this understanding correct?

Regards,
ST
--

------------------------------------------------------------------------------
_______________________________________________
rsnapshot-discuss mailing list
rsnapshot-discuss < at > lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss
Missed backup, ok to run again?
November 07, 2014 04:08PM
I see what you mean.
It’s working fine now, it’s rotated another daily.0 around but that’s ok I think, most of the backups have succeeded and not pulled an unexpectedly large number of files.

Many thanks for all your help, I understand a little more than I did when I woke up this morning ;)

Chris.[quote]On 7 Nov 2014, at 11:26, covici < at > ccs.covici.com ([email]covici < at > ccs.covici.com[/email]) wrote:
syncfirst will make this work much better, if the backup fails, you canjust run it again, because it spends most of its time in rsync, exceptfor the last second.David Keegel <djk < at > cyber.com.au ([email]djk < at > cyber.com.au[/email])> wrote:[quote]Chris,You might want to check first that daily.0 looks similar to daily.1,for example about the same disk usage and for a few random files X/Y/Zthat daily.0/X/Y/Z and daily.1/X/Y/Z are hard-linked together - unlessrsnapshot successfully did a backup of X/Y/Z and it changed recently.The risk is that if the backup failed without fully populating daily.0with hard links (eg with cp -al) then some of the files on your next backup might be treated as new files (rsynced across the network infull, and using up extra disk space because the "new" files won't behard linked to your current daily.1 and older backups).I think this scenario is unlikely unless you have "link_dest 1" inyour rsnapshot config (and perhaps some other things), but it might beworth checking that daily.0 looks right before you do your next backup,just in case.I assume you don't particularly mind that doing an extra backup meansthat another daily backup from 6-7 days ago will be deleted (so oneof your "weekly" backups will end up having only about 6 actual days spacing between them).If that does really concern you, then you can delete daily.0 (assuming that is the failed backup) and move daily.1 to daily.0, move daily.2to daily.1, daily.3 to daily.2, ... and daily.6 to daily.5.Then you can just go ahead and run rsnapshot daily again.On Fri, Nov 07, 2014 at 09:21:11AM +0000, Chris Tebb wrote:[quote] Hi venerable rsnapshot experts! I’ve got a pretty standard setup here with these options at their defaults: #sync_first 0 #use_lazy_deletes 0 The backup runs every morning at 1AM This morning the connection went down and all the backups apart from a couple returned 255 errors: [07/Nov/2014] /usr/bin/rsnapshot daily: ERROR: /usr/bin/rsync returned 255 while processing xxxxxxxx Am I ok just to run snapshot daily again to get it to take todays copy? Thanks, Chris. -- [1]rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss[/quote]-- ___________________________________________________________________________ David Keegel <djk < at > cyber.com.au ([email]djk < at > cyber.com.au[/email])> Cyber IT Solutions Pty. Ltd. rsnapshot-discuss < at > lists.sourceforge.net ([email]rsnapshot-discuss < at > lists.sourceforge.net[/email])https://lists.sourceforge.net/lists/listinfo/rsnapshot-discuss[/quote]-- Your life is like a penny. You're going to lose it. The question is:How doyou spend it? John Covici covici < at > ccs.covici.com ([email]covici < at > ccs.covici.com[/email])
[/quote]
--
[url=http://chrispyfur.net]chrispyfur.net[/url]
Sorry, only registered users may post in this forum.

Click here to login