Surebackup: OS did not boot in alloted time

[macnet]

Hi,
Trying to run surebackup (V6) on a vm.
When I run the job it times out after 10 minutes with:
Error: Results: OS did not boot in the allotted time

The VM has no specific role.
I have tried without heartbeat and ping enabled.
If I open the console it displays a blackscreen.
I have tried several VMs, with the same result.

I have used Restore and the VM works fine.
What have I missed?
Cheers
Mac

[Fizzer]

It turns out that, even with ping and heartbeat tests unchecked, surebackup does still try to confirm that the OS boots and will fail if it times out first. This cannot be bypassed: Feature Request - Advanced Surebackup Boot Order
It may just be that your VM is not booting within 10 minutes, some of mine didn't. I set up a scratch raid 0 array with 15k sas drives locally on the host to run the surebackup jobs, this improved boot time by approx 25% over just using nfs datastores on our filer(which is also running lots of other stuff). my quickest one with this setup is over 8 minutes.

As a test, try setting the timeout value to something very large (1200 for example) start the job and go put the kettle on.
You can also monitor the progress of the boot by opening a console of the VM that Veeam creates.

[macnet]

Hi Fizzer,
Thanks for the swift response.
Just trying a DC, 21 minutes so far..............
Will post any results.
Cheers
Mac

[Vitaliy S.]

Malcolm, where is your vPower NFS datastore located?

Btw, we have some existing topics discussing possible ways of improving vPower NFS datastore performance, please take a look: http://forums.veeam.com/search.php?st=p ... power+slow

[macnet]

Hi Vitaly,
Thanks for the response.
The proxy is a physical server which has a share to a SAN using iSCSI.
The VPower is running from an NFS store on LUN mounted as VMFS3.
Cheers
Mac

[rbrambley]

just trying a DC, 21 minutes so far..............

Is this DC looking for other DCs when booting (FSMO roles, DNS servers, etc?) Did you use the Advanced VSS option when you backed up this DC? If the DC is one of multiple DCs in your environment there is more to consider: Multiple Domain Controllers - How to Backup?

Can you try a another test VM (not a DC and with little dependencies on other servers) and see if you have the same problem? This would help you determine if your Surebackup infratsructure is an issue or not, or if it is just your DC VM.

[macnet]

Hi,
sorry for the slow response, managed to get a holiday.
I have tried several VMs of differening roles but all come back with the same result.
I have asked support for assistance and they are looking at the files.
Will keep you informed of a solution.
Cheers
Mac

[Fizzer]

Hi Macnet, how did you get on?

[macnet]

Hi Andy,
As it happens I had issues with the server so rebuilt it, reinstalled windows 2008 R2 sp1, patched up to the gills.
Installed B&R 6.1 (looks nice) as the local admin (everything runs through this account now).
Backs up fine, restores fine (file level as well), sureBackup still won't boot.....
Still waiting for a resolution from support... they cannot replicate the error in their labs (sent them the VM files).
Must be something that I am configuring incorrectly(?).
Thanks for your concern and will keep you updated.
Cheers

[macnet]

Hi folks,
Working fine now.
In the end it was the speed of the NFS port switch connection. It had auto-negotiated to run at 100Mb (problem with NIC, switch port...).
Managed to get it to 1000Mb.

Many thanks for the support and possible solutions
Cheers
Mac

[Fizzer]

thanks for the updates, useful info!

[tfloor]

Hello,

I've B&R 6.5 , and already have some experience with using virtual labs.
This time i have create an application group with 2 Linux SLES 11 servers.

I try to Start the job, with selecting only Webserver, because it has that role.
I get this error
"Powering on"
"Error: Results: OS dit not boot in the alloted time"

What i see is that the OS is booting find, then i can logon, and i saw that it takes some time before the os has his network adapter in the air.
So because of that i have set the Maximum allowed Boot time to "2500"
and the application initialization timeout to "300".

Also tried that in combination with several Boot verifications... but without luck, always the same error.

What am i doing wrong?
Most of the time i use windows machines for the virtual lab, so is there something difficult with Suse linux Enterprise 11?

Regards,

Tristan

[tfloor]

My Post is merged, but still ask for help.
Don't see any usefull information yet for my situation

[foggy]

Tristan, here is another topic with similar symptoms. Please check whether the suggested solutions work for you and don't hesitate to contact technical support for assistance in case they don't.

[tfloor]

That post is most of the time for windows machines.
I have a Suse linux enterprise server.

Is there a Telephone number to contact for this?

[foggy]

Is there a Telephone number to contact for this?

Sure. Get one by clicking Phone Support on the support portal.

[cstemaly]

I'm SO close to having this working.....

On my production network (the network guy tells me that all server traffic is untagged and is VLAN 1), I have a domain controller DC02 which has the following network config (for example):
IP Address: 10.100.114.2
Subnet Mask: 255.255.252.0
Default Gateway: 10.100.115.254

I have my virtual lab set up as follows (Basic didn't work so I'm using advanced configuration):
Proxy IP Address: 10.100.114.23
Subnet Mask: 255.255.252.0
Default Gateway: 10.100.115.254

Isolated Network is VLAN 1
Proxy Appliance IP Address in the isolated network: 10.100.115.254
Subnet Mask 255.255.252.0
Masquerade address is 10.255.C.D
DHCP is off, thus no DNS servers either.

My Application Group contains DC02 (see above).

When I run a SureBackup Job, I can see DC02 power on. Veeam even opens a console window on my Veeam server, but the job fails and tells me that it couldn't detect that the OS powered on. The console screen showed me that the VM was in fact on and I watched it sit at the Ctrl+Alt+delete screen for a good five minutes.

So, I'm guessing that my Veeam server cannot communicate through the masquerading address.
Do I need to put this address (10.255.0.0 into a routing table somewhere? Should I use a different address? Where did I go wrong?

[Hickzinho]

Hi cstemaly,

Did you manage to resolve this? Having the exact same issue and am going slightly insane

Cheers

[Hickzinho]

RE support Case # 00252071

Hi all,

I'm having an issue with a SureBackup.

We have 5 virtual database servers which we have placed in a Veeam application group, and all on the same network.

When we run a SureBackup job, all servers backup correctly with the exception of 1. We can see it powering on in vSphere but Veeam doesn't pick up on the fact that it powers up, it just times out when powering on (this has been changed to 20mins + for testing). If all the database servers had the same issue I would say we had network issues, but for 1 not to work seems a bit strange.

Has anybody else had an issue of this sort? And how was it fixed?

Many thanks

LA

[foggy]

This could be VMware Tools issue (VMware Tools did not start up or are out of date, for example) preventing heartbeat from being detected. Please continue investigating with support as debug logs review is most likely required. Thanks!

[janpaulsmit]

Hello,

I've B&R 6.5 , and already have some experience with using virtual labs.
This time i have create an application group with 2 Linux SLES 11 servers.

I try to Start the job, with selecting only Webserver, because it has that role.
I get this error
"Powering on"
"Error: Results: OS dit not boot in the alloted time"

What i see is that the OS is booting find, then i can logon, and i saw that it takes some time before the os has his network adapter in the air.
So because of that i have set the Maximum allowed Boot time to "2500"
and the application initialization timeout to "300".

Also tried that in combination with several Boot verifications... but without luck, always the same error.

What am i doing wrong?
Most of the time i use windows machines for the virtual lab, so is there something difficult with Suse linux Enterprise 11?

Regards,

Tristan

Hi Tristan,

I have the same issue. Did you manage to get iT resolved?

Regards,

JP

[veremin]

Tristan didn’t provide a ticket number, so it’s impossible to follow his support case.

As mentioned above, this issue might be related to VMware Tools that didn’t start or just had an obsolete version; so, kindly check it first.

Anyway, the most effective way to address any technical problem is open a ticket with our support team and let them investigate it directly.

Thanks.

[Hickzinho]

Hey guys,
If anyone else has issues heres what I received from Veeam Support:

http://kb.vmware.com/selfservice/micros ... Id=1032790

Apparently a known issue... We are currently in the process of writing a script to place on all our Linux VMs so that they are recognised when powered up.

Basically remove the 70-persistent-rules.... on boot and re-write it with the eth* configurations that we need.

When we get it working as it should we'll give a hand to others as it's very frustrating!

[veremin]

I’ve previously written a script that finds any non-Windows VMs within a given vCenter; so, if you change it slightly, you will be able to use it as a start point of the script you’re after.

Code: Select all

Asnp VMware.VimAutomation.Core
Asnp VeeamPSSnapin
Connect-VIServer -Server "Name of your vCenter" -User "User name" -Password "Password"
$UbuntuVMs = Get-VM | where {(($_ |Get-View).summary.config.guestFullName) -match "Ubuntu"}

Hope this helps.
Thanks.

[RMullis]

I was plagued with this error and finally set out to fixed once and for all. I tried many setting changes for time such as my domain controllers I set to allow 3600 secs for boot (recommended by Tier 2 support) and 300 seconds for application and on my Exchange 1020 servers i set OS boot to 3600 but the application to 600 since it can take awhile for all services to start. This made it better but it was now intermittent. Still had issues with Ping so I made sure my GPO disabled the public interface since Sureback adds a new interface and windows default "public profile". This fixed the pings but still would get the "Error: Results: OS did not boot in the allotted time". Then I looked and found the vmware tools was 1 version behind and the Update Operator must have missed the domain controllers as there were over 127 Windows updates available. I updated both on my domain controllers and also checked my other servers in my Sureback jobs, now my Sureback Jobs do not fail.

I hopes this helps other getting things working.

Rick