Surebackup Warning

[RPTan]

Hi,

I've got a minor question to ask:

I'm trying to run SureBackup with basic verification only (hearbeat + ping) since I don't have custom scripts for my app servers. So I set up a SureBackup job without an application group and don't specify any roles on verification options. When I check the realtime statistics and email reports, Heartbeat and Ping jobs are successful and the Script job is disabled -- but Status has a Warning.

The warning occurs in Application Initialization part of each job, and drilling down further on each job, these lines have warnings:
Application Initialization
No Test Script(s) defined
Summary: operation is skipped because of VM from linked backup job

Can anyone explain why I'm getting this warning?

Thanks,
Ryan

[foggy]

Ryan, according to some investigation by our devs, this message is displayed in informational purposes. In the case where application initialization operation cannot be performed (like your particular case with no scripts and no application group specified), it is skipped with the corresponding message. To avoid this message appearing, you can disable the application initialization stage setting the 'Application initialization timeout' parameter in 'Verification Options' window to 0. Maybe this message will be switched from warning to informational or be completely disabled in one of the future updates.

[Fiskepudding]

I have the exact same "problem". Since there is no selected script for Veeam to run i think a warning is misleading at best. Makes you take a second a look at every report just to see that that there is not another warning.

Changing to informational or just skipp the warning in a future update would be nice

I also find it strange that you only get this warning if the job is linked. If the same VM is in an application group and still no selected scripts, no warning is displayed.

Changing the application timeout to 0 is a nice workaround, thanx.

[CaptainFred]

I'm getting this but I don't have any backup jobs linked, only replication jobs and no backup jobs are running.

And I DO have scripts defined for the whole job. It seems to be doing them for some of the VMs in the same replication job but not all.

Any ideas why?

[Vitaliy S.]

Just to make sure we are on the same page - you would like to know why scripts are not triggered for all VMs or you're referring to the warning message about application initialization parameter?

[CaptainFred]

I'm getting the following. for some VMs that are linked as part of a replication job that do have scripts defined.

Code: Select all

02/05/2014 14:22:37          Publishing
02/05/2014 14:22:29          Replica point: created at 02/05/2014 05:38:39, type snapshot
02/05/2014 14:22:36          Virtual lab: Virtual Lab DR
02/05/2014 14:22:36          OS: Microsoft Windows Server 2003, Standard Edition (32-bit)
02/05/2014 14:22:36          Network adapter 1: MAC '00:50:56:B6:6E:EE', type 'vpx', network 'Web Services'
02/05/2014 14:22:36          Assigned roles: none
02/05/2014 14:22:36          Maximum boot time: 600 second(s)
02/05/2014 14:22:36          Application initialization: 120 sec
02/05/2014 14:22:36          Heartbeat test: enabled
02/05/2014 14:22:36          Ping test: enabled
02/05/2014 14:22:36          Script tests: disabled, 0 tests
02/05/2014 14:22:46          Reconfiguring
02/05/2014 14:22:46          Network 1: production 'Web Services', isolated 'Virtual Lab - Test', mapped
02/05/2014 14:22:46          Results: 1/1 network(s) mapped, 0 unmapped
02/05/2014 14:22:46          Summary: 100% total pass rate
02/05/2014 14:31:04          Powering on
02/05/2014 14:22:59          Waiting for OS to boot for up to 600 seconds (stable IP algorithm)...
02/05/2014 14:22:59          Note: Will proceed to the next step at 02/05/2014 14:32:59 or earlier
02/05/2014 14:31:04          Updating virtual lab parameters
02/05/2014 14:31:04          Summary: OS booted up successfully
02/05/2014 14:31:06          Heartbeat test
02/05/2014 14:31:06          Heartbeat status: green
02/05/2014 14:31:06          Results: heartbeat is 'green', passed
02/05/2014 14:31:06          Summary: 100% total pass rate
02/05/2014 14:31:22          Running ping test(s)
02/05/2014 14:31:07          Network adapter 1: name 'File and Print', usable
02/05/2014 14:31:22          Results: 1/1 test(s) passed, 0 failed, 0 skipped
02/05/2014 14:31:22          Summary: 100% total pass rate
02/05/2014 14:31:23          Application initialization
02/05/2014 14:31:22          No test script(s) defined
02/05/2014 14:31:23          Summary: operation is skipped because of VM from linked backup job
02/05/2014 14:31:26          Powering off
02/05/2014 14:31:30          Unpublishing

I've removed a couple of the lines for security reasons.

I know it says script tests disabled above, but I have added a test script to the whole linked replication job which this VM is a part of. It's running them for some but not others. It's really odd.

[foggy]

I know it says script tests disabled above, but I have added a test script to the whole linked replication job which this VM is a part of. It's running them for some but not others. It's really odd.

I would contact support with this to review the jobs configuration and debug logs, if required.