01-14-2013
You cannot really compare...
LVM mirroring (MirrorDisk/UX) is using permanently 2 disks, so if any of the two fail you have your system still running...
DRD, is a cloning utility letting you be ableto clone your root disk and modify the clone... you can boot from...
The diference is if your root disk fails, your system will crash... but yes you reboot on the clone after, but in mirror/UX there is no non planified downtime and if you are using hot swap disks, there is no downtime at all...
Now if you are testing updates you see the difference: in mirror/UX you cannot come to a previous situation since both disks are affected unless you brake the mirror...
This User Gave Thanks to vbe For This Post:
9 More Discussions You Might Find Interesting
1. Solaris
I've looked a little but haven't found a solid answer, assuming there is one.
What's better, hardware mirroring or ZFS mirroring? Common practice for us was to use the raid controllers on the Sun x86 servers. Now we've been using ZFS mirroring since U6. Any performance difference? Any other... (3 Replies)
Discussion started by: Lespaul20
3 Replies
2. Solaris
Hi all
Can someone explain to me the different syntax regarding how root / mirror disks are represented. I never truely understand the namely / device tress etc.
Let me give you an example. On one my my servers, the root and mirror drives are :-
A domain on a sunfire 6800 :- ... (6 Replies)
Discussion started by: sbk1972
6 Replies
3. Solaris
Hi all
I wish to mirror for the root disk, but last time i do, make the server cannot boot up. :p So this time, hope you guys can assist me on it. =)
At the last code, is the step i wish to do. Please help to check and correct me if got any wrong.
root@leo # format </dev/null
Searching for... (17 Replies)
Discussion started by: SmartAntz
17 Replies
4. Linux
Hi Guys,
I have a mirrored LVM volume, and wish to break the mirror leaving only copy1 (effectively removing copy 0).
Here's the config:
# lvs -a -o +devices
lvdata vg01 mwi-ao 2.19T lvdata_mlog 100.00 lvdata_mimage_0(0),lvdata_mimage_1(0)
vg01... (0 Replies)
Discussion started by: badoshi
0 Replies
5. UNIX for Advanced & Expert Users
I apologize is this isn't an appropriate post for the 'advanced' UNIX, so please let me know if I should post this under UNIX for dummies, but here's my problem in a nutshell: I having problems creating a mirrored logical volume.
I have created two new physical volumes
... (2 Replies)
Discussion started by: simonrodan
2 Replies
6. AIX
Hi,
I need to know who can I create an script in order to check server mirror in AIX. I got this script
!/usr/bin/ksh
#
# Check if a VG is mirrored.
#
# lsattr -El <lvname> -a strictness -a copies
# If copies=2 and scrictness=y, then VG is mirrored
#
# LVs are retrieved via 'lsvg -l... (5 Replies)
Discussion started by: fede_mont
5 Replies
7. HP-UX
Hi,
I have old server hp rp 3440 hp-ux 11.11. One mirrored disk is faulty. I need spesial patch PHKL_31216 and PHCO_30698, which give to correctly remove disk. Unfortunately I don't have access to hp support site. Please help me find it patch.
regards,Andre (0 Replies)
Discussion started by: andre9
0 Replies
8. Linux
Hello,
I am trying to convert a single-drive Centos 7.2 installation with LVM into a two-disk mdadm mirror with mrrored LVM. I was able to follow the excellent instructions at:
http://www.dgoradia.com/creating-a-raid1-mirrored-on-an-existing-centos-on-lvm/and did create a two-disk mirror... (1 Reply)
Discussion started by: Clovis_Sangrail
1 Replies
9. Solaris
Got a V490 with one existing root disk. Other disk slot was never populated.
Want to ensure we've got disk mirroring.
Currently vfstab mounts the physical disk - no mirroring set up.
Whats best way to achieve this without losing current disk? (1 Reply)
Discussion started by: psychocandy
1 Replies
LEARN ABOUT HPUX
vxbootsetup
vxbootsetup(1M) vxbootsetup(1M)
NAME
vxbootsetup - set up system boot information on a Veritas Volume Manager disk
SYNOPSIS
/etc/vx/bin/vxbootsetup [-g diskgroup] [medianame ... ]
DESCRIPTION
The vxbootsetup utility configures physical disks so that they can be used to boot the system. Before vxbootsetup is called to configure a
disk, the required volumes, standvol, rootvol and swapvol (and optionally, dumpvol) must be created on the disk. All of these volumes must
be contiguous with only one subdisk.
The -g option may be used to specify the boot disk group.
If no medianame arguments are specified, all disks that contain usable mirrors of the root, swap, /usr and /var volumes are configured to
be bootable.
If medianame arguments are given, only the disks that are associated with the specified disk names are configured to be bootable.
vxbootsetup requires that:
o The root volume must be named rootvol and must have a usage type of root.
o The swap volume must be named swapvol and must have a usage type of swap.
o The volumes containing /usr and /var (if any) must be named usr and var, respectively.
See the chapter "Recovery from Boot Disk Failure" in the Veritas Volume Manager Troubleshooting Guide for detailed information on how the
system boots and how VxVM impacts the system boot process. The vxmirror, vxrootmir, and vxresize utilities call vxbootsetup automatically.
If you use vxassist, or vxmake and vxplex to create mirrors of the root volume on a disk, you must run vxbootsetup explicitly to make the
disk bootable.
ARGUMENTS
medianame
Specifies the disk name (disk media name) of a VM disk that is to be configured as bootable.
SEE ALSO
disksetup(1M), edvtoc(1M), vxassist(1M), vxevac(1M), vxinstall(1M), vxintro(1M), vxmake(1M), vxmirror(1M), vxplex(1M), vxresize(1M),
vxrootmir(1M)
Veritas Volume Manager Troubleshooting Guide
VxVM 5.0.31.1 24 Mar 2008 vxbootsetup(1M)