Announcement

Collapse
No announcement yet.

HS3 upgrade broke my BLBackup Event

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • HS3 upgrade broke my BLBackup Event

    Not sure if this is already known but figured I'd share this to remind everyone to verify their backups. I just noticed my last backup was Aug 20th. Aug 20th is when I upgrade HS3. I looked at my BLbackup event and the path was blank. Updated the path and it's working again. Over 2 months of no backups and I had no idea. I also noticed I"m getting a part 1 and part 2 now. Maybe I updated BLBackup since 8/20 also?


    Any way to send a pushover alert if backups fail?

    -rw-r--r-- 1 root root 279289045 Aug 18 01:02 hs3_DAILY_2017-08-18_01-00-00_FULL.zip
    -rw-r--r-- 1 root root 279383992 Aug 19 01:02 hs3_DAILY_2017-08-19_01-00-00_FULL.zip
    -rw-r--r-- 1 root root 279451495 Aug 20 01:02 hs3_DAILY_2017-08-20_01-00-00_FULL.zip
    -rw-r--r-- 1 root root 145628640 Nov 1 00:01 hs3_DAILY_2017-11-01_00-00-19_FULL_PART01.zip
    -rw-r--r-- 1 root root 91939634 Nov 1 00:02 hs3_DAILY_2017-11-01_00-00-19_FULL_PART02.zip

  • #2

    Comment


    • #3
      The upgrade did not affect my BLBackup plugin?

      Comment


      • #4
        Thanks for sharing.
        With what arguments is this script called?
        I assume it is the device code for BLBckup, but what is the second argument?

        Comment


        • #5
          the first argument is from the blbackup return code, the second one is the name of the device to send the pushover message as configured in the pushover plugin

          Comment

          Working...
          X