Surebackup Script for Exchange failed

[Revan]

Hello,

Case ID: 07755136

One of my Surebackup Jobs contains a Backup of our Exchange Server (Microsoft Exchange 2019).
The surebackup job runs daily right after the backup job and it worked since 07/01/25
The test script "Mail server" fails since 07/02/25 but i don't know why.

I installed CU15 for the Exchange on 06/26/25 and there was no change since then.

Application Timeout and maximum allowed boot time was already set to 2000 seconds

Does anybody have a clue what i could do?

[PetrM]

Hello and Welcome to Veeam R&D Forums!

It would be best to continue working with our support team. In the meantime, you may want to verify that the Exchange services are started on the machine restored in Virtual Lab. To do this, check the box "Keep the application group running after the job completes" on this wizard step.

Thanks!

[Revan]

The support team told me that i should contact my exchange admin. Not very helpful, as i am the only admin in our company.
The services start fine in the live VM, as well as in the Surebackup-VM, but in the Surebackup-VM not all services start completely. And it's not always the same services that don't start, it often differs. But mainly it is the Microsoft Exchange Transport service that does not start.

And i understand, that the Surebackup Script cannot be completed succesful when the Transport Service is not running. What i don't understand is, why the service runs fine in the Live VM, but not in the Surebackup VM and what to do to get it running

[PetrM]

Hello,

Please let me have some time to clarify the situation with the support team. I'm not sure that I understand the root cause.

Thanks!

[Andreas Neufert]

Usually if Exchange Servers do not start all services, you can go to Windows Event Logs and there is usually a good indication on why it is not started or delayed.

Typical cases are:
AD/DNS service not reachable in the lab. Did you start the AD service in a application group before you try to start the Exchange server in the jobs section?
Check that the DNS entry in the exchange server matches the IP addresses that you start in the virutal lab.
As well a common issue is, if you run a Availability Group memeber in the lab and a witness was not started in the application group (can be a CAS server or share depending on configuration).

Best action is:
Start DNS server in Application Group
Start the AD server in the Application Group
Start a CAS server in the application group
Start the witness share (if applicable) in the application Group.

Then use the SureBackup job with the application group to check on the other exchange roles like the database systems.

In the Application check of the SureBackup job and within the Application Group, be sure to select the right tests as it will change the timing of the testing. Basically give the systems enough time to start AD in recovery mode and Exchange in VSS recovery mode.

Another important step is that you need to ensure that the Public Firewall Profile of the Exchange server and the other server you use for testing (DNS/AD/CAS) has the same configuration as the Domain Firewall Profile. When you start a server in the virtual lab, the original router is not the same and so Windows detects that the system is started in a new network. Therefore applying the "public" firewall profile by default.

You can as well check if it make sense to add additional timeout time in the SureBackup entry for the Exchange server that you have. Maybe the service will just takes more time.

[Revan]

The DC with AD and DNS role starts first, then the Exchange second. Windows Firewall is completely deactivated on both servers. The Exchange is no member of an availability group as it is just for management tasks in our O365 Hybrid environment. There are no mailboxes on premise.

The network details of the surebackup-exchange show the IP-adresses of the live-dns-servers instead of the preloaded surebackup-DC

I see in the Eventlog that many services were ended unexpected but i cannot see any reason why

[Andreas Neufert]

I think then SureBackup is exactly doing its job and letting you know that in case of a disaster you would end up in a unreliable recovery situation despite that everything was backed up bit by bit correctly.

I would work with an Exchange expert on checking what is going on in the event log. Maybe another depending server is missing?

What kind of errors do you see?

[Revan]

What i don't get is why it is working in one moment and in the next no more, without any change.

The job was working a long time. Then, a few weeks ago, i made a Windows Update on the DC and the Exchange and the job failed for a few days.
Did open a case, Support told me the same as now, Exchange Transport Service not starting. No solution found with the support.

Out of sheer desperation, I simply restarted the DC and Exchange and suddenly the Surebackup job was running again after the next backup.

Unfortunately, the restart did not help this time.

DNS and DC are both reachable from the failing Surebackup-Exchange btw.

[Andreas Neufert]

What issues do you see in the Event Log when the transport service does not come up?

Did you googeled the updates that you have done if they cause issues with Exchange like this one? https://support.microsoft.com/en-us/top ... 019%20CU15.

[Revan]

I see just that the services ended unexpected and try to restart. No further information.
I tried the mentioned workaround about KB5050672 but it didn't help.
Another Windows Update today with also no change. Live-Exchange fine, Backup fine, Surebackup fails

[Andreas Neufert]

Maybe it is just a matter of the timing. Can you add additional time in the SureBackup job that waits for the service availability before it starts with the testing?

Anyway if you have issues with the service itself, Surebackup is exactly there to detect this and warn you. You need to work on why this is happening and fix your Exchange production.

Do you see any latency warnings in the event log?
What happened in other areas of the event log when the service stopped working?