backup status wdiget - time period

[frankive]

Hi.
I REALLY need to come to work on monday and see the backup status for the last week and the current week for multiple customers.
I have 1 widget for each customers and show their status in our sharepoint siste.
It seems like we now have to create two widget for each customers, one with current week and one with past week to accomplish this.
Is this correct?

EDIT: Is is possible to create a widget which which doesn't need any credentials? is is a pain in the .. that we must type in this in our kiosk-screen at each reboots..

[Shestakov]

Hi Frank,
You can either create 2 widgets with current week and past week or create one widget with a month scope.

EDIT: Is is possible to create a widget which which doesn't need any credentials? is is a pain in the .. that we must type in this in our kiosk-screen at each reboots..

Basically you need to login just once when enter the reporter. You can also save the credentials in the dialog window.

[frankive]

Is it possible to give the username and password in the web-syntax? f.ex https://username:password@myveeamserverl.local to display it perfectly
The reasons is we have som unmanaged kioskview on a couple of screens.

[Vitaliy S.]

Currently it is not possible, but this is a good FR. Thanks!

[frankive]

Is it possible to suppress the backup job alarms in the widget like with email?
in the widget it will show if a backup job has failed, so we have to log in to the customer to take a look.
then it usually has retried the job and succedded, so we really didn't have to log in..
if we have a lot of customers this takes time..
Would be great to have a option in the widget to be ablt to just show green if the retries went through.

[Shestakov]

Hi, Frank!
Do you mean "Backup job state" alarm?
Am I right saying that you had suppressed it for a certain time and when the job failed, you didn`t receive the alarm, but the error was expressed in the corresponding widget?
Thanks!

[Vitaliy S.]

Actually, it should work as you've described. Retries should not be counted in the widget and shouldn't affect job state. If it works differently, then it must be a bug.