The service did not respond to the start or control request in a timely fashion

[Gustav]

If your server starts and runs, but leaves a dozen Veeam services as stopped, it may be caused by a:

• too slow boot disk or boot controller

• degraded RAID system

Probably, the SQL Server neither has started.

Searching the Event Log will reveal a bunch of pairs of 7009 and 7000 errors like this:

EventID: 7009
A timeout was reached (30000 milliseconds) while waiting for the VeeamDeploySvc service to connect.

EventID: 7000
The VeeamDeploySvc service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Solution: Replace the boot disk with a faster model, or repair the RAID system.

Example of a too slow disk: Hitachi HTS545016B9A300, 160 GB, 5400 rpm, 2½" SATA 3.0 Gb/s

[HannesK]

Hello,
thanks for sharing the solution. I moved the post to the Backup & Replication forum as I assume it's about VBR (as the post mentions "dozen Veeam services").

Yes, that sounds like old (laptop) hardware... the software is built for "standard" hardware.

Best regards,
Hannes

[Gustav]

.. the software is built for "standard" hardware.

Sure.
We ran a test for a bare metal recovery, and that disk just happened to be on top of the stack of old disks.

As for the RAID system, it was rebuilt and then ran at expected speed - for us and Veeam B&R.