Re: [Clonezilla-live] Restored Disk Image: eth issue

[RSCL M. <rsc...@gm...>]

On Fri, Apr 9, 2010 at 9:20 PM, Les Mikesell <les...@gm...> wrote:

> On 4/9/2010 10:20 AM, RSCL Mumbai wrote:
>
> > My concern is not directly related to Clonezilla, but generic to
> > theconcept of cloning.
> >
> > I have a server with CentOS 5.3 and Samba.
> > As a back up measure against HDD and other peripheral failure, I have
> > purchased an identical PC and I plan to clone the main server and then
> > run rsync on daily basis.
> > Everything seems fine in this schematic and I am fine with this backup
> > approach.
> >
> > My concern is:
> > Both the server's have identical specs sans the ethernet.
> > When I will restore the image on the 2nd PC, and boot, it will alert for
> > a *new ethernet device found* and by default it will create a new
> > interface ETH1
> >
> > Is there any way to avoid creating the new ethernet device ETH1 and be
> > able to use the the original ETH0.
> >
> > One thought which crossed my mind, but I have not tried is, after
> > cloning, I can boot the server using a live distro (may be knopix),
> > mount the cloned HDD and make changes to the ETH configuration, namely
> > MAC address or whatever else. Not sure what should I change, and then
> > boot the closed HDD.
> >
> > Does this make sense ? Will it help.
> > Can someone throw light on how to prevent the creation of ETH1.
>
> This isn't really a clonezilla issue - it has to do with the way that
> Linux 2.6.x detects hardware in a more or less random order so even with
> what you think is identical hardware, the NICs and possibly even disk
> controllers may be given different names at boot/detection time.  Centos
> compensates for this by putting the ethernet hardware address in the
> /etc/sysconfig/ifcfg-eth? files and renaming the devices to match in
> some later step.  I have sometimes been successful with a script that
> pre-creates these files with the new mac addresses and sometimes they
> just get renamed and ignored.  My servers tend to have 4 to 6 NICs so
> there is the additional problem of knowing ahead of time which wire will
> be plugged into which NIC and I'd love to find a general solution.  For
> the moment the best approach might be to use a DHCP server that you can
> configure to give the old IP to the new NIC, or at least have a few
> spare IPs to give out so you can connect after the new server boots and
> repair the damage.
>
> --
>   Les Mikesell
>    les...@gm...
>
>
Thx Les,

Then I think I should stop looking around and just go ahead and manually set
up the required IP address on eth1 and move on.
Just that I will have to change the firewall script, but its a one time job.
So I should not really bother.

Thx & Cheers