Veeam B&R 10 - SureBackup Exchange 2016 - Services wont start on Sandbox VM

[WinstonWolf]

Hi ,
I found two Posts which was not solved .
Now we have the same behavior .
In our Application Group are both DCs which was also DNS Servers and GC.
They start before the Exchange Server 2016.
All Exchange Services are in Status "Automatic" but they are all not startet .
When i trty to start an Service manually then it works .
I can do an nslookup and Ping from the Exchange Server and i reach both DNS , AD Server.

I found an workaround to create an Script which starts after the Serverstart ever 5 minutes the Exchange Services , but this is not an solution for us .

Is there another solution for this Problem ?

Thanks
Michael

[Mildur]

Windows will not start services if they have a great timeout.
The timeout can happen if storage connection is very slow.
I see this most of the time at customers with SureBackup Jobs. In a SureBackup job on a very slow backupserver/backup storage, the services will timeout.

It‘s not a Veeam Problem. Most likely your storage solution for SureBackup is slow.

You can try to extend the timeout in the registry on the original server. If thats the same problem in your enviroment.

[Andreas Neufert]

If it is a DAG Server then you need
AD Server of the domain, a AD Server of forest root domain (GC role there), the witness server/share and a CAS server started in an Application Group. Otherwise it will not come up. Potentially as well you need another DAG member server running as well (the server not Exchange services) when you have an uneven count of DAG members. Basically Exchange DAG services will not start if they think they are in the minority to avoid split brain situations.

Instead of Witness disk/share sometimes a CAS server is used as automatic witness, check your confit for it.

[WinstonWolf]

Windows will not start services if they have a great timeout.
The timeout can happen if storage connection is very slow.
I see this most of the time at customers with SureBackup Jobs. In a SureBackup job on a very slow backupserver/backup storage, the services will timeout.

It‘s not a Veeam Problem. Most likely your storage solution for SureBackup is slow.

You can try to extend the timeout in the registry on the original server. If thats the same problem in your enviroment.

Our Backup Reposuitory are Harddisks on the Veeam Backup Server himself . All of the SQL Server dont make Problems .
I dont think that this is an Problem with Timeouts because an slow Storage .

[WinstonWolf]

If it is a DAG Server then you need
AD Server of the domain, a AD Server of forest root domain (GC role there), the witness server/share and a CAS server started in an Application Group. Otherwise it will not come up. Potentially as well you need another DAG member server running as well (the server not Exchange services) when you have an uneven count of DAG members. Basically Exchange DAG services will not start if they think they are in the minority to avoid split brain situations.

Instead of Witness disk/share sometimes a CAS server is used as automatic witness, check your confit for it.

We dont have an DAG Cluster . Its only one Exchange Server 2016 . Nothing more nothing less.
As i wrote our two DCs with the GC and CAS are started before this VM in SureBackup . Before the Exchange 2016 ist tested , 3 SQL Server was tested successfully .

[Andreas Neufert]

I think you should do the following:

Place the Exchange server as well at then end of the Application Group and disable all tests for the Exchange VM.
At the SB job, select that the Application Group should stay online.
Start the SB Job.

Let the Surebackup boot all servers including the Exchange server. Wait 20minutes and then log into the Exchange VM.
Check if the Exchange Services are up and running or not.
If they are running go to the Windows Event Log and check how long it took them to start. Adjust potentially the timing in the Surebackup Job.
If they are not running, check Windows Event log why they did not come up. I guess in this case SureBackup did exactly his job and warned you that in case of a restore there would be an issue.

[WinstonWolf]

Hi Andreas ,
Thanks for the Tipp . I think i found the reason .
The Connection Timeout of 30000ms was reached for the Service "NetTCPPortSharing".
All Exchange Services depends on this Service.
Event Log System , Event ID 7009 , Service Control Manager

The "MSExchangeADTopology" depends on this Service . If this Service dont start , all Exchange Services dont start .

[Andreas Neufert]

Looks like this Microsoft KB addresses it: https://docs.microsoft.com/en-us/previo ... dfrom=MSDN

[WinstonWolf]

Thanks Andreas , this is exactly what i search . Maybe we can help the other guys in this Post too ?
vmware-vsphere-f24/surebackup-exchange- ... 59937.html
veeam-backup-replication-f2/exchange-se ... 50745.html

Can we link this to this Posts ?

[Mildur]

That was I have told in my post.
Look at your service timeouts

[Andreas Neufert]

done

[WinstonWolf]

That was I have told in my post.
Look at your service timeouts

Perfect , Nice Job
So set the Entry in the Regedit on the running Exchange Server and try it again tomorrow , to see if it works