Backup notification

Hello @Erwan RIGOLLOT ,

the mail subject is defined with

[%JobResult%] - %JobName% (%VmCount% VMs) %Issues%

So I think you have to delete the %JobName% and the JobName will not appaer in the mails.

Hello @JMeixner 

Thanks !

But I want the first job name : “Backup Copy Job 00-HyperV” and not “\Backup Job 00-HYPERV”

Ooops, yes… it would be better to read carefully and correctly the whole sentence…

The variable 5jobname% contains the name of the backup copy job AND the source job…

I don’t see a way to change the variable. My only idea for your problem is to cut the offending part from the string in your script. But I think this is not what you had on your mind...

Maybe not exactly what you want to hear but you could give VeemONE a chance or use the execelent power shell integration.

Another one is this:https://github.com/AsBuiltReport/AsBuiltReport.Veeam.VBR

Your other option here would be to use to use the API as part of B&R Enterprise Manager. This is what i do to create custom backup job reports on our multi tenant platform so yours would be even easier and you could pull out the information you want specifically/present it your way (even via email, or a dashboard)

Seen below is the dashboard for a test tenant on our portal, pulling data via the API (the slide out panel is when you click the little gear icon on the main table)

benyoung wrote:

Your other option here would be to use to use the API as part of B&R Enterprise Manager. This is what i do to create custom backup job reports on our multi tenant platform so yours would be even easier and you could pull out the information you want specifically/present it your way (even via email, or a dashboard)

Seen below is the dashboard for a test tenant on our portal, pulling data via the API (the slide out panel is when you click the little gear icon on the main table)

 

@benyoung can you tell me if is possible to get a log of jobs via (Rest)API? Would be great to get the log, visible in GUI: 

Last I check that granular log around each disk read rates was not available. I have looked in the past about sourcing this info directly from the database or scraping job log files but in the end that information for our use case wasnt overly useful for our customers as they really want to see 

Success/fail

Start/end times of the job and each individual VM 

Type of restore point (less so)

Thanks for checking!

Hey @vNote42 - Ive been playing with the BETA of V11, new API in there still very much under development but the good news is we can finally get this detail, here is an example from one off my lab jobs returning the session log.

{
    "totalRecords": 21,
    "records": [
        {
            "id": 21,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:47.3265379+13:00",
            "updateTime": "2020-12-03T00:08:47.3265379+13:00",
            "title": "Job finished at 3/12/2020 12:08:47 AM",
            "description": ""
        },
        {
            "id": 20,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:47.1859263+13:00",
            "updateTime": "2020-12-03T00:08:47.1859263+13:00",
            "title": "Primary bottleneck: Source",
            "description": ""
        },
        {
            "id": 19,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:47.1859263+13:00",
            "updateTime": "2020-12-03T00:08:47.1859263+13:00",
            "title": "Load: Source 99% > Proxy 0% > Network 5% > Target 0%",
            "description": ""
        },
        {
            "id": 18,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:30.1742557+13:00",
            "updateTime": "2020-12-03T00:08:30.1742557+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-21T152748_6957.vbk' per retention policy",
            "description": ""
        },
        {
            "id": 17,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:28.4661664+13:00",
            "updateTime": "2020-12-03T00:08:28.4661664+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-21T165615_46E6.vib' per retention policy",
            "description": ""
        },
        {
            "id": 16,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:27.4974192+13:00",
            "updateTime": "2020-12-03T00:08:27.4974192+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-22T000022_61CA.vib' per retention policy",
            "description": ""
        },
        {
            "id": 15,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:26.8411649+13:00",
            "updateTime": "2020-12-03T00:08:26.8411649+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-23T000037_5EF5.vib' per retention policy",
            "description": ""
        },
        {
            "id": 14,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:26.5442884+13:00",
            "updateTime": "2020-12-03T00:08:26.5442884+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-24T000022_A34D.vib' per retention policy",
            "description": ""
        },
        {
            "id": 13,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:25.8255375+13:00",
            "updateTime": "2020-12-03T00:08:25.8255375+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-25T000030_7490.vib' per retention policy",
            "description": ""
        },
        {
            "id": 12,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:24.3984194+13:00",
            "updateTime": "2020-12-03T00:08:24.3984194+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-26T000036_DF22.vib' per retention policy",
            "description": ""
        },
        {
            "id": 11,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:08:23.2265529+13:00",
            "updateTime": "2020-12-03T00:08:23.2265529+13:00",
            "title": "Removing 'E:\\Backup\\Lab Infrastructure\\Lab InfrastructureD2020-11-27T000020_5E76.vib' per retention policy",
            "description": ""
        },
        {
            "id": 9,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:03:12.6525487+13:00",
            "updateTime": "2020-12-03T00:07:53.494225+13:00",
            "title": "Processing POWERHAUS",
            "description": ""
        },
        {
            "id": 6,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:26.5787671+13:00",
            "updateTime": "2020-12-03T00:06:18.3601373+13:00",
            "title": "Processing AppServer",
            "description": ""
        },
        {
            "id": 8,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:47.476389+13:00",
            "updateTime": "2020-12-03T00:04:10.3095093+13:00",
            "title": "Processing DATAPROCESSOR",
            "description": ""
        },
        {
            "id": 10,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:04:04.2797952+13:00",
            "updateTime": "2020-12-03T00:04:04.3110458+13:00",
            "title": "All VMs have been queued for processing",
            "description": ""
        },
        {
            "id": 7,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:26.6412672+13:00",
            "updateTime": "2020-12-03T00:03:27.4679354+13:00",
            "title": "Processing FILESERVER01",
            "description": ""
        },
        {
            "id": 5,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:21.440211+13:00",
            "updateTime": "2020-12-03T00:00:56.1366797+13:00",
            "title": "Processing DOCKER1",
            "description": ""
        },
        {
            "id": 4,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:13.5662182+13:00",
            "updateTime": "2020-12-03T00:00:13.5662182+13:00",
            "title": "Changed block tracking is enabled",
            "description": ""
        },
        {
            "id": 3,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:13.5349575+13:00",
            "updateTime": "2020-12-03T00:00:13.5349575+13:00",
            "title": "VM size: 460 GB (373.5 GB used)",
            "description": ""
        },
        {
            "id": 2,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:07.6329099+13:00",
            "updateTime": "2020-12-03T00:00:10.3672921+13:00",
            "title": "Building list of machines to process",
            "description": ""
        },
        {
            "id": 1,
            "status": "ESucceeded",
            "startTime": "2020-12-03T00:00:07.3204062+13:00",
            "updateTime": "2020-12-03T00:00:07.3204062+13:00",
            "title": "Job started at 3/12/2020 12:00:04 AM",
            "description": ""
        }
    ]
}

Thank you @benyoung! It this new to v11?

I finally found a way to export the logs using PowerShell as well - @JMeixner  provided the missing link. I will post this later on.

Just posted the PowerShell-way to export this job logs.

• [PowerShell] Export VBR console job logs

Yep, this is coming to v11 @vNote42 - brand new API that is decoupled from Enterprise Manager - woohoo!

Not sure everyone fully understands how many possibilities this will open up!