after a real long testing period with surebackup i found a little potential for improvement. case #00930447
the actual veeam way of testing a dc is like that:
0. boot up timeout starts (im my case a realy big number of sec.)
1. the domain controller (dc) starts
2. the dc gets pingable
3. the vmware heartbeat comes up
4. veeam realize that the dc has started and stops the boot up timer.
5. now the application start timer starts (for example 300 sec.)
6. as the dc is a dc. the dc begins to restart!
7. the application start timer is expired.
8. veeam begins with the tests. (but the dc is still booting!!!)
9. test fails
(i know i have to set the application timeout higher..
)the way it should be:
0. boot up timeout tarts (im my case a realy big number of sec.)
1. the domain controller (dc) starts
2. the dc gets pingable
3. the vmware heartbeat comes up
4. veeam realize that the dc has started and waits for the reboot.
5. dc is rebooting
6. the dc gets pingable
7. the vmware heartbeat comes up
8. veeam realize that the dc has started and stops the boot up timer.
9. now the application start timer starts (for example 300 sec.)
10. the application start timer is expired.
11. veeam begins with the tests. (against the running and up dc)
12. tests ok!
perhaps i am not the only one with this and we will see this in one of the next updates.
markus