Feature Request - Date of Last Successful Backup in Alert

[yasuda]

Feature Requset: Show the date of the last successful backup in the email alerts sent by the VAW agent.

This could be merged with "Last Successful Completion Date with B&R" topic, although that feature request was for B&R reporting.

We have VAW (well, mostly VEB right now) agents installed on laptops, desktops and servers that DO NOT back up to VBR repositories. Mostly they are backing up to NAS shares. A lot of times backups fail because a machine was rebooted for updates, or a laptop was taken off site. It would be very helpful to see when the last successful backup was, so we can ignore single night failures, but pay close attention to multi day failures.

[Dima P.]

Hi Peter,

Good request, thanks. As a possible workaround, you can configure local email reporting to single email address and just sort emails in the mailbox by subject (sorting rule migh help too). %ComputerName% %JobResult% and %CompletionTime% variables for email notification subject should help.

fail because a machine was rebooted for updates, or a laptop was taken off site

Have you heard about new backup cache feature in VAW 2.0? It allows to save backup to local cache when connection to remote repository is lost and sync incremental restore point later.

[yasuda]

Hi Dima,

Good idea; thanks. Sorting the emails works, but we have a help desk monitoring alerts from many clients, and it's an extra step that will really slow them down.

I have read about the backup cache, but have not tested it. Will it help with the merge? That's the slow part for us. The incrementals tend to be small and complete quickly.

[Dima P.]

and it's an extra step that will really slow them down

You can setup a custom subject for every client like this

Client A - %JobResult% - %ComputerName%
Client B - %JobResult% - %ComputerName%
Client C - %JobResult% - %ComputerName%

I have read about the backup cache, but have not tested it. Will it help with the merge?

Not really. It allows to create incremental restore point locally when remote target is offline. When the connection is up, special process starts to upload the cached incremental backup to the remote repository.

Merge might be slow if you have long backup chains. In such case, periodic active full backups may help