RHEL6 SureBackup

VMware specific discussions

RHEL6 SureBackup

Veeam Logoby DataAssure » Fri Apr 27, 2012 3:32 am

When running a SureBackup w/ RHEL6, we keep getting a "failed" and we knew for sure VMware Tools was installed fine. The SureBackup image could power up fine but Veeam B&R 6 flagged a "Powering On" error RED and we had already disabled heartbeat, ping & script test. TIA for ur help.
DataAssure
Influencer
 
Posts: 12
Liked: never
Joined: Wed Nov 10, 2010 3:19 pm
Full Name: Stephen Hui

Re: RHEL6 SureBackup

Veeam Logoby Gostev » Fri Apr 27, 2012 2:15 pm

Can you logon to the running SureBackup VM fine?
Gostev
Veeam Software
 
Posts: 21386
Liked: 2348 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: RHEL6 SureBackup

Veeam Logoby mlinders » Fri Apr 27, 2012 2:52 pm

Could be caused by the MAC address being defined in /etc/sysconfig/network-scripts/ifcfg-eth0
Put a # before HWADDR=xx:xx:xx:xx:xx:xx (e.g. # HWADDR=xx:xx:xx:xx:xx:xx )

Regards
mlinders
Veeam ProPartner
 
Posts: 26
Liked: 8 times
Joined: Sun Apr 22, 2012 10:42 pm
Location: the Netherlands
Full Name: Mark Linders

Re: RHEL6 SureBackup

Veeam Logoby DataAssure » Fri Apr 27, 2012 5:04 pm

Gostev: Yes, logon to the running SureBackup VM fine.
mlinders: OK - will give that a try but why? Using the same V-Lab1, our Windows server jobs are passing the SureBackup jobs w/ flying colors.
Tks gentlemen for the reply!
DataAssure
Influencer
 
Posts: 12
Liked: never
Joined: Wed Nov 10, 2010 3:19 pm
Full Name: Stephen Hui

Re: RHEL6 SureBackup

Veeam Logoby mlinders » Fri Apr 27, 2012 5:15 pm

Windows works differently then Linux does. When the generated MAC address from the surebackup job isnt the same as the specified HWADDR the interface stays down. Hence surebackup can't verify the server is up since it needs the interface to verify it's running.

By placing a # before the HWADDR you basically skip MAC address checking.
Let us know if it fixes your problem.

Regards,
mlinders
Veeam ProPartner
 
Posts: 26
Liked: 8 times
Joined: Sun Apr 22, 2012 10:42 pm
Location: the Netherlands
Full Name: Mark Linders

Re: RHEL6 SureBackup

Veeam Logoby dellock6 » Fri Apr 27, 2012 5:24 pm

Also, on RedHat/CentOS 6, ifcfg script is superseeded by udev rule "persistent-net-generator.rules".
On VMware, is sometimes better to delete this rule so it does not check mac address at every reboot (same problem when cloning VMs...)
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 5047
Liked: 1330 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: RHEL6 SureBackup

Veeam Logoby tdewin » Thu Oct 11, 2012 2:43 pm 5 people like this post

Don't know if this is still helpful but I'll just post it for other people out there

First remove the mac from the ifcfg scripts as stated above.

Then execute the following statement which basically copies the pci bus slot id in /etc/udev/rules.d/70-persistent-net.rules (makes the next step easier ;))
Code: Select all
echo -e "\n#"$(lspci | grep VMXNET3) >> /etc/udev/rules.d/70-persistent-net.rules


Now modify the udev rule so that it works on pci bus slot and not on the mac address. Your ID might differ but it should be added to the file by running the echo command.
Here is a list of the things I changed:
  • Changed the driver to vmxnet3
  • Removed the mac address ATTR
  • Added BUS=="PCI"
  • Added the ID based on the echo output ID=="0000:<pci id>"
Code: Select all
# cat /etc/udev/rules.d/70-persistent-net.rules
# This file was automatically generated by the /lib/udev/write_net_rules
# program, run by the persistent-net-generator.rules rules file.
#
# You can modify it, as long as you keep each rule on a single
# line, and change only the value of the NAME= key.
# PCI device 0x15ad:0x07b0 (vmxnet3)
SUBSYSTEM=="net", ACTION=="add", DRIVERS=="vmxnet3", ATTR{type}=="1", KERNEL=="eth*", NAME="eth0", BUS=="pci", ID=="0000:0b:00.0"

#0b:00.0 Ethernet controller: VMware VMXNET3 Ethernet Controller (rev 01)
tdewin
Veeam Software
 
Posts: 1043
Liked: 360 times
Joined: Fri Mar 02, 2012 1:40 pm
Full Name: Timothy Dewin

Re: RHEL6 SureBackup

Veeam Logoby bmcchesney-nv » Tue Nov 13, 2012 6:46 pm

Hello and thanks!

Using PCI bus slot ID instead of MAC address is probably the best fix I've seen so far, and perfectly good for VM templates.

Regards,
Bob
bmcchesney-nv
Novice
 
Posts: 5
Liked: 6 times
Joined: Wed Aug 08, 2012 9:32 am
Full Name: Bob McChesney

Re: RHEL6 SureBackup

Veeam Logoby andyleellgc » Wed Mar 06, 2013 10:57 am

Hello,
I'm also having this issue and the above fix has worked for a RHEL 6 VM with a single network adapter and one IP address.
My knowledge of RHEL 6 isn't that great and I was wandering how would i go about applying the same fix to a RHEL 6 VM with multiple network adapters and each with one IP address? Or a single network adapter with multiple IP addresses?

Regards

Andrew
andyleellgc
Lurker
 
Posts: 2
Liked: never
Joined: Wed Mar 06, 2013 10:28 am
Full Name: Andrew Jenkins


Return to VMware vSphere



Who is online

Users browsing this forum: Exabot [Bot], stehei and 28 guests