Surebackup/Restore Suse Linux Enterprise

[maygyver]

Hi,

I have serveral Suse Linux Enterpise Server, 10/11/12.

When I try to Surebackup them, their network is not starting. Is this a known bug, how do I solf it.

Sven

[PTide]

Hi,

What do you mean by "not starting"? The service is dead, the interface is down, it does not get IP address, or it is ping test that times out? Please elaborate.

Thank you

[jmmarton]

Any chance the MAC address of the NICs are changing when you do SureBackup?

Joe

[maygyver]

Hi,

problem is, when I do a surebackup the network card is not available, cause it is a new one.
How di I get Surebackup running with this systems.

Even surebackup with a linux vcenter 6.5 is not working.

may

[tdewin]

Quick googling makes me think that SUSE is also using udev rules. You might consider this:
vmware-vsphere-f24/rhel6-surebackup-t11681.html#p63750

Although it is RHEL

[jmmarton]

This article references using PlateSpin Migrate to clone SLES VMs, but the problem is very similar and as Timothy mentioned udev is a wait to try and resolve things.

https://www.suse.com/support/kb/doc/?id=7012911

Joe

[tsightler]

SUSE allows you to configure the udev rules via YaST. By default SUSE does bind by MAC address, which will indeed change any time a VM is cloned. However, using YaST you can change the network adapter to bind by PCI bus ID, which will not change when the VM is cloned, although it might possibly change during VM virtual hardware upgrades, so keep that in mind.

It's not super easy to find in YaST, but it is documented:

https://www.suse.com/documentation/sles ... ard_change

Scroll down to the section titled "Changing the Device Name and Udev Rules" and follow those instruction to switch from MAC address binding to Bus ID binding, and Surebackup should work fine.