Surebackup Error:IP-address is not IPv4

[samon90]

Case ID: # 00550979

We are receiving the following error when we run a sure backup job on a Linux Machine:

Code: Select all

18/04/2014 2:32:35          Publishing
18/04/2014 2:32:20          Backup point: created at 17/04/2014 22:31:33, type increment
18/04/2014 2:32:34          Backup repository: Backup Repository (type windows server, server This server, mount server This server)
18/04/2014 2:32:34          Virtual resources: host 10.32.1.118, datastore VeeamBackup_TOKYO, VM ISTANBUL_d37cefd85d7d4d848bfade057d663dcb
18/04/2014 2:32:34          Virtual lab: Surebackup
18/04/2014 2:32:34          VM: ISTANBUL (verification, 3072 MB vRAM)
18/04/2014 2:32:35          OS: unknown
18/04/2014 2:32:35          Network adapter 1: MAC '00:50:56:9E:5E:FA', type 'vpx', network 'VM Network'
18/04/2014 2:32:35          Assigned roles: none
18/04/2014 2:32:35          Maximum boot time: 600 second(s)
18/04/2014 2:32:35          Application initialization: 120 sec
18/04/2014 2:32:35          Heartbeat test: enabled
18/04/2014 2:32:35          Ping test: enabled
18/04/2014 2:32:35          Script tests: disabled, 0 tests
18/04/2014 2:32:35          Backup file validation: disabled
18/04/2014 2:32:43          Reconfiguring
18/04/2014 2:32:43          Network 1: production 'VM Network', isolated 'Surebackup VM Network', mapped
18/04/2014 2:32:43          Results: 1/1 network(s) mapped, 0 unmapped
18/04/2014 2:32:43          Summary: 100% total pass rate
18/04/2014 2:32:50          Registering
18/04/2014 2:34:10 Error    Powering on
18/04/2014 2:32:55          Waiting for OS to boot for up to 600 seconds (stable IP algorithm)...
18/04/2014 2:32:55          Note: Will proceed to the next step at 18/04/2014 2:42:55 or earlier
[b]18/04/2014 2:34:10 Error    Error: IP-address is not IPv4[/b]
18/04/2014 2:34:12          Powering off
18/04/2014 2:34:13          Unregistering
18/04/2014 2:34:16          Cleaning up redo logs
18/04/2014 2:34:18          Unpublishing

When we run the sure backup job on a windows machines 2008 /2012 , it works.

How can we solved this issue?

[Vitaliy S.]

It might be a stupid question, but are you using IP v4 on this Linux VM?

[hatari]

Do you have VMWare Tools installed on this VM?

[Moebius]

I am getting a lot of these errors too lately.
The was running fine for months, then all of a sudden I started getting this error at different customers. I am suspecting some code change introduced by the last Veeam patch.

This is just one example:

Code: Select all

17/04/2014 11:33:10          Publishing
17/04/2014 11:32:54          Backup point: created at 17/04/2014 06:14:09, type full
17/04/2014 11:33:10          Backup repository: DS4700 (type windows server, server This server, mount server This server)
17/04/2014 11:33:10          Virtual resources: host regesx04.corp.xyz.com, datastore VeeamBackup_REGBCK01, VM REGDTB01_6be92c67be7349e8871db7c0ed9db653
17/04/2014 11:33:10          Virtual lab: RE-SBLab1
17/04/2014 11:33:10          VM: REGDTB01 (verification, 8192 MB vRAM)
17/04/2014 11:33:10          OS: Microsoft Windows Server 2008 (64-bit)
17/04/2014 11:33:10          Network adapter 1: MAC '00:50:56:95:00:38', type 'vpx', network 'server_10'
17/04/2014 11:33:10          Assigned roles: none
17/04/2014 11:33:10          Maximum boot time: 600 second(s)
17/04/2014 11:33:10          Application initialization: 120 sec
17/04/2014 11:33:10          Heartbeat test: enabled
17/04/2014 11:33:10          Ping test: enabled
17/04/2014 11:33:10          Script tests: disabled, 0 tests
17/04/2014 11:33:10          Backup file validation: disabled
17/04/2014 11:33:13          Reconfiguring
17/04/2014 11:33:13          Network 1: production 'server_10', isolated 'RE-VeeamSBnet_10', mapped
17/04/2014 11:33:13          Results: 1/1 network(s) mapped, 0 unmapped
17/04/2014 11:33:13          Summary: 100% total pass rate
17/04/2014 11:33:23          Registering
17/04/2014 11:41:33          Powering on
17/04/2014 11:33:29          Waiting for OS to boot for up to 600 seconds (stable IP algorithm)...
17/04/2014 11:33:29          Note: Will proceed to the next step at 17/04/2014 11:43:29 or earlier
17/04/2014 11:41:29          Results: IP address '10.1.1.241' is detected
17/04/2014 11:41:33          Updating virtual lab parameters
17/04/2014 11:41:33          Results: IP address '10.17.1.241', network '10.17.0.0', mask '255.255.0.0', gateway '10.1.1.113'
17/04/2014 11:41:33          Summary: OS booted up successfully
17/04/2014 11:41:35          Heartbeat test
17/04/2014 11:41:35          Heartbeat status: green
17/04/2014 11:41:35          Results: heartbeat is 'green', passed
17/04/2014 11:41:35          Summary: 100% total pass rate
17/04/2014 11:41:36 Warning    Running ping test(s)
17/04/2014 11:41:36 Warning    No network adapters with IPv4 addresses found
17/04/2014 11:41:36          Application initialization
17/04/2014 11:41:36          No test script(s) defined
17/04/2014 11:41:36          Summary: operation is skipped because of VM from linked backup job
17/04/2014 11:41:48          Powering off
17/04/2014 11:41:53          Unregistering
17/04/2014 11:41:56          Cleaning up redo logs
17/04/2014 11:41:58          Unpublishing

This happens randomly, with random VMs. All have valid IP addresses (it also shows in the job log). All have the VM tools installed. Re-running the SB job the error does not duplicate.
Also, what does "operation is skipped because of VM from linked backup job" mean??
Not sure if I have to open a ticket about this.

[Vitaliy S.]

Hi Lucio,

Please see this topic for the answer > Surebackup Warning.

As to the OPs error message, then I would recommend opening a support case as well to investigate it further.

Thanks!

[Moebius]

Thanks Vitaliy, this answer my second question.
What about the "no network adapters with IPv4 addresses found" problem? Am I required to open a case or is it the same issue that the OP is experiencing?

[Vitaliy S.]

If your VMs does have IP v4 and VMware Tools are up and running, then I would suggest contacting support for further investigation. I have reviewed the OPs support case and cannot see any resolution yet.

[Moebius]

Case opened, ID#00570527.

[Moebius]

Case solved.
After working with support (and having my case escalated to a higher tier engineer) it turned out that the VMware Tools were not properly installed.
There was no other sign of malfunction or error message to indicate a bad VMware Tools upgrade, and the Tools were shown as running and current in vSphere. However, after completely uninstalling and reinstalling the Tools, the problem never happened again.

Just wanted to leave some feedback in case anybody else experiences the same.

[Deon]

I would also suggest to check which IP address are VMTools returning in Managed Object Browser for the VM started in SureBackup job.

[Vitaliy S.]

Yes, this is the usual reason for SureBackup job failure and the best way to verify that is to use VMware Managed Object Browser.

[Moebius]

Any discussion or KB explaining how to do?

[Vitaliy S.]

These are not direct instructions, but you should be able to figure out where to look at once you get to VMware Tools State page > VMware Tools Heartbeat Status

[LDA]

Hi Guys,

We have the same issues with SureBackup. After upgrading to VMware 5.5 SureBackup started returning IP-address is not IPv4 error. I don't recall having this error while on 5.1...

It happens randomly and if we restart SureBackup on the same restore point it can finish successfully.

Veeam support checked the logs and found out that SureBackup gets the IPv6 from the VMWare tools when this error occurs.

We realised that it happens on Windows 2008 R2 servers with VMXNET 3 network adapters so I assume that even if on the live servers we have IPv6 disabled, when the server it's powered on from the backup by SureBackup, it obtains a new NIC (explained here: http://www.veeam.com/kb1570) which has IPv6 enabled.

My question is: Has anyone applied the patch http://support.microsoft.com/kb/2550978 provided by Microsoft to prevent new NIC assignment?

Thanks.

[nichola.vandevoorde]

Hi LDA,

I solved the issue by installing the Windows Patch http://support.microsoft.com/kb/2550978. I first tried reinstalling VMtools, to no avail.

Customer environment:

- Veeam 7.0.0.871
- VMware ESXi 5.5.0 1892794

Kind regards,

Nichola

[seonet]

Hello,

I have problem with start sure backup job. After some minutes from start VM veeam return Error: IP-Adress is not valid IPv4

Any idea what can be wrong?

Thank you

Pavel

[veremin]

Hi, Pavel,

Check the suggestions provided above, such as whether or not machine has a valid IPv4 address, whether or not VMWare Tools are up-to-date, and what particular address is returned.

Thanks.

[seonet]

Hi, thanks. I read this before, but I need recover something specific from mysql. And this solutions are on new backups no? What can I do to run WinVM from backup files directly, but in isolation network? Surebackup is only one way?

[seonet]

Logged case 00813757

[foggy]

You can perform Instant Recovery of that VM, but do not power it on automatically, connect it to an isolated network instead.

[deduplicat3d]

I am getting the same error message (address is not ipv4). I installed the Microsoft hotfix and the latest vmware tools for 5.5. I don't get the error message when i run a surebackup from backup, only when the surebackup is from replica. I've been working with tier 2 for a long time. Case number 00865217

[dietoself86]

The above hotfix was the fix for me as well.