storebackup - power outage, warnings

English Applications
1

Over a month ago, while mysystem was in the middleof running a backup,
the power went out at my house and my UPS wasn’t enough to hold the
computer on, so bang, my system went down.

I use the backup program called storebackup. I run it in crondaily every
morning.

Well, the time has passed and the backup date on which that power outage
happened should have been deleted by now, and to the best of my
knowledge, it has. See the components of the log file below (I added …
dots in between so that I don’t have to copy 400 lines of irrelevant log
entries here)


BEGIN     2013.05.07 06:30:02 10499 backing up directory
</mnt/newraid/backup> to </mnt/backcron/default>
VERSION   2013.05.07 06:30:02 10499 storeBackup.pl, 3.2, build 361
INFO      2013.05.07 06:30:02 10499 setting ARG_MAX to 63488 (Linux)
INFO      2013.05.07 06:30:02 10499 comprRule = $size > 1024 and not
$file =~
/\.zip\Z|\.bz2\Z|\.gz\Z|\.tgz\Z|\.jpg\Z|\.gif\Z|\.tiff\Z|\.tif\Z|\.mpeg\Z|\.mpg\Z|\.mp3\Z|\.ogg\Z|\.gpg\Z|\.png\Z/i
WARNING   2013.05.07 06:30:02 10499 backup
</mnt/backcron/default/2013.04.06_06.15.03> not finished
WARNING   2013.05.07 06:30:02 10499 backup
</mnt/backcron/default/2013.04.06_06.15.03> not finished
INFO      2013.05.07 06:30:02 10499 scanning directory </mnt/backcron>
for existing backups
....
INFO      2013.05.07 06:30:03 10499 analysis of old Backups in
</mnt/backcron/default>:
INFO      2013.05.07 06:30:03 10499    Tue 2013.04.16_06.15.02 (21d0h):
will be deleted (keepMaxNumber), keepWeekDays(30d)
INFO      2013.05.07 06:30:03 10499    Wed 2013.04.17_06.15.02 (20d0h):
keepWeekDays(30d)
INFO      2013.05.07 06:30:03 10499    Sat 2013.04.20_06.15.03 (17d0h):
keepWeekDays(30d)
INFO      2013.05.07 06:30:03 10499    Mon 2013.04.22_06.15.02 (15d0h):
keepWeekDays(30d)
INFO      2013.05.07 06:30:03 10499    Wed 2013.04.24_06.15.02 (13d0h):
keepWeekDays(30d)
INFO      2013.05.07 06:30:03 10499    Fri 2013.04.26_06.15.05 (11d0h):
keepWeekDays(30d)
INFO      2013.05.07 06:30:03 10499    Sat 2013.04.27_07.00.01 (9d23h):
keepMinNumber10, keepWeekDays(30d)
INFO      2013.05.07 06:30:03 10499    Mon 2013.04.29_07.30.04 (7d22h):
keepMinNumber9, keepWeekDays(30d)
....
STATISTIC 2013.05.07 06:35:24 10499                      CPU usage = 65.65%
INFO      2013.05.07 06:35:24 10499 removing lock file
</tmp/storeBackup.lock>
WARNING   2013.05.07 06:35:24 10499 -- 3 WARNINGS OCCURED DURING THE
BACKUP! --
INFO      2013.05.07 06:35:24 10499 syncing ...
END       2013.05.07 06:35:28 10499 backing up directory
</mnt/newraid/backup> to </mnt/backcron/default/2013.05.07_06.30.03>

Does anyone else use storebackup?

Youcan see from the dates that April 6 was the day of the power outage,
right in the middle of the backup procedure.

You can also see from the dates that the program just deleted the backup
from April 15, as I set it up to do. So the April 6 backup was already
deleted a long time ago.

However, I still continue to get the warnings every day in the log
program that the backup from April 6 was never finished (because of the
power outage).

What exactly is this signifying? It seems an irrelevant warning now,
since the backup from that day was deleted anyway. I would like to get
it to stop telling me that, unless I am missing something significant in
the warning about the condition of my backups today related all the way
back to that time when the April 6 backup never finished.

George

–
G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

2

Hi George,

yes, I do. :cool:

Without any additional options, storeBackup does not care about not-finished backups at all. You can delete them manually or do the following:

If you use the configuration files, set:
deleteNotFinishedDirs=yes

If you are using the command line interface, set:
–deleteNotFinishedDirs

then, storeBackup will delete not-finished backups automatically.

btw, you may want to upgrade to version 3.3.1 - there are some bug fixes regarding “blocked files”.
If it’s not in the repository, you can download a tar file from storeBackup.org and simply unpack it wherever you want. Additionally, you have to adjust your paths to that version storeBackup.

Does this help?

Regards, Heinz-Josef

3

On 05/07/2013 03:36 PM, hjclaes wrote:
> golson765;2554497 Wrote:
>> Does anyone else use storebackup?
>>
> Hi George,
>
> yes, I do. :cool:
>
> Without any additional options, storeBackup does not care about
> not-finished backups at all. You can delete them manually or do the
> following:
>
> If you use the configuration files, set:
> deleteNotFinishedDirs=yes
>
> If you are using the command line interface, set:
> --deleteNotFinishedDirs
>
> then, storeBackup will delete not-finished backups automatically.
>
> btw, you may want to upgrade to version 3.3.1 - there are some bug
> fixes regarding “blocked files”.
> If it’s not in the repository, you can download a tar file from
> ‘storeBackup.org’ (http://storebackup.org) and simply unpack it wherever
> you want. Additionally, you have to adjust your paths to that version
> storeBackup.
>
> Does this help?
>
> Regards, Heinz-Josef
>
>
Yes,thanks! Ok,I have changed the parameter in the configuration files.
I noticed, though, that the comment line is a bit counter-intuitive:


# delete old backups which where not finished
# this will not happen if doNotDelete is set
# Values are 'yes' and 'no'. Default is 'no' which means to delete.
;deleteNotFinishedDirs=

It says that the default is ‘no’ which means “to delete”. Shouldn’t that
mean “to not delete”?

I have set it for ‘yes’ and will see how it performs on the next backup.
Thanks for the help!

George

–
G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it

4

Thanks for the hint. This bug in the documentation must have been there for years - unbelievable it’s not reported up to now. :shame:

I changed the online documentation (which is for version 3.3.1) and documentations for the next version(s).

As I wrote, it’s a good idea to upgrade to 3.3.1. It can handle your old backups without any problems. See What’s new? for a short description of new features or ChangeLog file for a detailed description. Especially “replication” is of interest and gives you the possibility to replicate your backups to other disks (asynchronously), see replication of backups .

Do you use an old version of the openSUSE distribution or an actual one? Version 3.2 of storeBackup is 4 years old. (I’m not using SUSE at the moment so I’m not sure about which version of storeBackup is used in which version of the distribution.)

Regards, Heinz-Josef

5

On 05/09/2013 03:16 PM, hjclaes wrote:
> Thanks for the hint. This bug in the documentation must have been there
> for years - unbelievable it’s not reported up to now. :shame:
>
> I changed the online documentation (which is for version 3.3.1) and
> documentations for the next version(s).
>
> As I wrote, it’s a good idea to upgrade to 3.3.1. It can handle your
> old backups without any problems. See ‘What’s new?’
> (http://www.nongnu.org/storebackup/en/node7.html) for a short
> description of new features or ChangeLog file for a detailed
> description. Especially “replication” is of interest and gives you the
> possibility to replicate your backups to other disks (asynchronously),
> see ‘replication of backups’
> (http://www.nongnu.org/storebackup/en/node52.html) .
>
> Do you use an old version of the openSUSE distribution or an actual
> one? Version 3.2 of storeBackup is 4 years old. (I’m not using SUSE at
> the moment so I’m not sure about which version of storeBackup is used in
> which version of the distribution.)
>
> Regards, Heinz-Josef
>
>
I am using version 3.2 from the openSUSE repositories, so it must not
have been upgraded yet. I am not sure how to alert the openSUSE team
that it would be nice to upgrade what is available from the
repositories. It is a great program.

Thanks for the tip on the upgrade. I will take a look at upgrading
storeBackup in a couple of weeks - I am really busy and tied up right
now with work. When things slow down I will be able to schedule some
time to look at how to do the upgrade. My preference would be to just do
it from the repositories, but if I have time in a couple of weeks I
might be able to look at how to do it the manual way.

By the way, changing the setting on deleting incompleted backups worked
on the 2nd day after changing the settings, but the first day after
changing the settings, the warning was still there in the logs. Now the
warning is gone.

George

–
G.O.
Box #1: 12.3 | KDE 4.10 | AMD Phenom IIX4 | 64 | 16GB
Box #2: 12.2 | KDE 4.9.2 | AMD Athlon X3 | 64 | 4GB
Laptop: 12.3 | KDE 4.10 | Core i7-2620M | 64 | 8GB
learning openSUSE and loving it