Ubuntu 12.04 VM Replica and Backup have issues at boot

[talong99]

Hi,

When attempting a SureBackup and/or a FailOver to the replica of the same VM I get errors and eventually end up with a machine that has no network and is unable to run binary executables such as uname, date, mkdir, etc...

Running:
Veeam B&R 6.5
ESXi 5.1U1
VM is Ubuntu 12.04 LTS x64

Any assistance would be wonderful.

Thanks,
Todd

[Vitaliy S.]

Hello Todd,

Just to make sure I understand what's going on - you've backed up and replicated the Ubuntu VM and none of the backup copies work? Could you have problems with the source VM by any chance? What kind of network adapter you use? E1000? VMXnet3?

Thank you!

[talong99]

Hi Vitaliy,

That is correct. The source VM is fine... I thought maybe that was the case, but I restarted it last night and it came up fine. Using the E1000 adapter.

FWIW, I just took a manual snapshot and was able to boot it successfully.

Thanks!

[tsightler]

Not a lot of detail there, but the missing network is a pretty common issue since the replica of the VM will have a different MAC address which causes Ubuntu to think it's a different NIC and thus it's a different interface. It's pretty easy to override this default behavior:

http://serverfault.com/questions/425882 ... ator-rules

Of course, that doesn't explain the issues of not being able to run binaries. I have no idea what would cause that. Are you saying the system boots up and you can login but can't run any local commands? That's very odd.

[talong99]

Yeah, that's what is happening... I can login but can't run any local commands. I can only access the VM from the vSphere Console and the information from there is pretty limited due to not being able to scroll up and down. When I login I get the following errors:

-bash: /bin/uname: cannot execute binary file
-bash: [: =: unary operator expected
-bash: [: too many arguments
etc...

In dmesg I can see services failing to start. One line that jumped out was "init unable to connect to the system bus".

I've created a clean backup job and still get the same results. Very odd, indeed.

[tsightler]

Have you tried a full restore of the VM or is this only during Surebackup/Failover of the replica.

[talong99]

It's only during SureBackup/Failover.

[veremin]

And what about Instant VM Recovery? Does it also result in such an issue? Thanks.

[tsightler]

It would probably be best to take up this issue with support. I can't think of any reason you would see such an issue. I have multiple Ubuntu 12.04 systems in my testing environment, and have worked with many customers with such systems and I've never seen anything like this behavior.

[talong99]

Vladimir, same results with Instant VM Recovery...

[talong99]

How do you suppose Helman http://forums.veeam.com/viewtopic.php?f ... 106#p65745 deleted his repository? Did he just delete the jobs, the directories or the entire filesystem? There seems to be some similarities between his issues and what I'm seeing.

[veremin]

Probably, just deleted backup jobs, as well as, directory itself. However, as mentioned above, kindly open a ticket with our support, since the team behind this community can’t assist you with the investigation of complex technical issue, especially, when a deep log investigation seems to be required.

Thanks.

[talong99]

The issue was resolved by making a clone of the VM and using the clone in the production role.

Hope this helps someone in the future.

[foggy]

Thanks for the update, Todd.