[Solved] Backup failure - Maybe false positive

Unimus support forum
Post Reply
Confab
Posts: 12
Joined: Thu Sep 14, 2017 7:08 pm

Mon Apr 30, 2018 7:50 pm

I think Unimus is generating false positive backup failure.
Each day I receive an alert informing some device failed during their backup.
Failed backup log is showing "ssh_backup_download_failed"
When I look in the "Backup" section i can see that the backup was correctly done...at least it tells me it is.

Any chance of false positive? I need to be sure.
User avatar
Tomas
Posts: 589
Joined: Sat Jun 25, 2016 12:33 pm

Mon Apr 30, 2018 7:56 pm

Hi,

If there is a backup failure, Unimus retires discovery, and if that succeeds, retires another backup.

You can always verify checking the job logs on the Dashboard:
- is there a failed backup job logged for that device (Latest failed job)?
- if so, are there any successful jobs with the same timestamp in the "Latest successful job" table?
Confab
Posts: 12
Joined: Thu Sep 14, 2017 7:08 pm

Thu May 03, 2018 12:47 pm

Here's an example:

https://imgur.com/a/g54jOLe
Here we see that 10.80.0.42 failed on Sunday April 29th

https://imgur.com/a/gmQxu44
Here we see that the device has done all its backup successfully since January 13th.

Does not make sense for me... Is there something I'm missing?

Thanks
User avatar
Tomas
Posts: 589
Joined: Sat Jun 25, 2016 12:33 pm

Thu May 03, 2018 1:06 pm

There were 2 failures on 29th of April:
1st a scheduled backup failed. This cause Unimus to do a re-discovery, which succeeded. After that, a re-backup failed again.
Meaning there was something wrong with the device at that time which prevented Unimus from backing it up (but discovery succeeded).

Unimus does a re-discovery and a re-backup after a failed scheduled backup to cover cases such as a device change, or credentials changes, etc. Basically it's an auto-adjustment mechanism which allows Unimus to adapt to changes in the network.
So the 2 backups failed at the same time is correct.

Now to why you see in the Backups a validity range that includes the failed dates.
Basically, if Unimus retrieves a backup, it compares it to a previous backup of that device in the system.
If the backups are the same, Unimus updates the "last seen" timestamp of the backup.

So even if there are failures during the "validity range" of a backup, if the backup was not change for the entirety of that date range (from the standpoint of Unimus), you will see that range include even failed scheduled backups.

Hope that makes sense.
Confab
Posts: 12
Joined: Thu Sep 14, 2017 7:08 pm

Thu May 03, 2018 1:17 pm

Ok!
But I have a lot of "ssh_backup_download_failed" lately. Never happened before.
I can't accept that much error, I must find how to correct it.
Any way to get more logs from these failure? Dashboard is only showing me "ssh_backup_download_failed".
User avatar
Tomas
Posts: 589
Joined: Sat Jun 25, 2016 12:33 pm

Thu May 03, 2018 1:22 pm

I would recommend trying the 1.7.0 Beta.

There were a bunch of improvements to both backup and discovery mechanisms.
Error logging for jobs was also improved, so now it will show you more details about a job failure, rather than just "backup failed".
Confab
Posts: 12
Joined: Thu Sep 14, 2017 7:08 pm

Thu May 03, 2018 1:27 pm

Will do! Thx
Post Reply