05-31-2017
If you are cloning to a physical server in the same network, it is worth unplugging the network cable whilst you do it else the restored server will immediately cause IP conflicts. Correct the IP definitions before reconnecting the cable.
If you are cloning to an LPAR, de-configure the network card then after the restore completes add it back in (probably need a boot) and set up the network definitions then.
It causes a panic when strange things start happening in production whilst you are recovering your clone.
I hope that this helps,
Robin
9 More Discussions You Might Find Interesting
1. AIX
Hi,
Other than df -k, is there any command that will tell me all physical hard drives installed on the system as well as the size of each one?
I'm using AIX 5.1
Thanks, (3 Replies)
Discussion started by: quickfirststep
3 Replies
2. Shell Programming and Scripting
Hi Engg. ! :mad:
I have a harddisk on which SCO UNIX Open Server was installed. There was some data (in .dbf format) on it. Present condition of HDD is that it is not booting. Now I want to mount this HDD through other HDD on which SCO UNIX Open Server is installed by attaching... (0 Replies)
Discussion started by: Niraj Gopal Sha
0 Replies
3. Solaris
A sparc server has a new SCSI hard disk added and labeled by the engineer, but they need to be formatted identically to an existing disk (c4t0d0). You decide to script the process and run from the command line without interaction.
I know that the following command line must be achieve this.
#... (3 Replies)
Discussion started by: kingsan
3 Replies
4. SCO
Hi.
We tried cloning a SCO Unix hard disk using Norton Ghost.
However, the new cloned hard disk encounter booting problem.
What possibly go wrong? (1 Reply)
Discussion started by: Mizan
1 Replies
5. SCO
Continuing saga of working on making a retail store more robust by creating a backup clone of the main server, a 1995 era :eek: PC running SCO OpenServer 5.0.0b and a discontinued Point of Sales (POS) software system.
I have a PC of the same make and model. The CPU runs faster and it has a... (5 Replies)
Discussion started by: jgt10
5 Replies
6. Red Hat
in red hat 4, 5 any one know any commands or any scritps to monitor HP DL 380 G5/6 server and trigger alarm when hard disk failed.
thanks for all support
---------- Post updated at 02:45 PM ---------- Previous update was at 12:00 PM ----------
does HP ProLiant Support Pack support is... (4 Replies)
Discussion started by: maxlee24
4 Replies
7. Linux
Hi all,
I'm kind of new to programming in Linux & c/c++. I'm currently writing a FileManager using Ubuntu Linux(10.10) for Learning Purposes. I've got started on this project by creating a loopback device to be used as my virtual hard disk. After creating the loop back hard disk and mounting it... (23 Replies)
Discussion started by: shen747
23 Replies
8. AIX
hello folks,
I have a 300GB ROOTVG volume groups with one filesystem /backup having 200GB allocated space
Now, I cannot alt disk clone or mirrorvg this hdisk with another smaller disk. The disk size has to be 300GB; I tried alt disk clone and mirrorvg , it doesn't work. you cannot copy LVs as... (9 Replies)
Discussion started by: filosophizer
9 Replies
9. AIX
Hi all,
I have encountered the issue with the hard disk, the disk is failed and need to replace by the new one.
As my understanding, this is just to take out the failed disk and insert the new ones, and that's all.
But the third party hardware vendor said, there should be another procedure... (9 Replies)
Discussion started by: Phat
9 Replies
EPAIR(4) BSD Kernel Interfaces Manual EPAIR(4)
NAME
epair -- A pair of virtual back-to-back connected Ethernet interfaces.
SYNOPSIS
To compile this driver into the kernel, place the following line in your kernel configuration file:
device epair
Alternatively, to load the driver as a module at boot time, place the following line in loader.conf(5):
if_epair_load="YES"
DESCRIPTION
The epair is a pair of Ethernet-like software interfaces, which are connected back-to-back with a virtual cross-over cable.
Each epair interface pair is created at runtime using interface cloning. This is most easily done with the ifconfig(8) create command or
using the cloned_interfaces variable in rc.conf(5). While for cloning you only give either epair or epair<n> the epair pair will be named
like epair<n>[ab]. This means the names of the first epair interfaces will be epair0a and epair0b.
Like any other Ethernet interface, an epair needs to have a network address. Each epair will be assigned a locally administered address by
default, that is only guaranteed to be unique within one network stack. To change the default addresses one may use the SIOCSIFADDR ioctl(2)
or ifconfig(8) utility.
The basic intend is to provide connectivity between two virtual network stack instances. When connected to a if_bridge(4) one end of the
interface pair can also be part of another (virtual) LAN. As with any other Ethernet interface one can configure vlan(4) support on top of
it.
SEE ALSO
ioctl(2), altq(4), bpf(4), if_bridge(4), vlan(4), loader.conf(5,) rc.conf(5), ifconfig(8)
HISTORY
The epair interface first appeared in FreeBSD 8.0.
AUTHORS
The epair interface was written by Bjoern A. Zeeb, CK Software GmbH, under sponsorship from the FreeBSD Foundation.
BSD
July 26, 2009 BSD