- 论坛徽章:
- 0
|
真诚请教:有关Mirror Disk的镜像操作。
特地找了一下HP的知识库,大家不妨参考一下:
(BTW,这里有谁上过LVM课程的,里面有很详细的解释)
----------------------------------------------------------------------
CHAPTER 4 : Replacing a boot disk WITH mirroring
----------------------------------------------------------------------
As with chapter 2, mirroring adds a new twist to the recovery of a boot
disk, and makes the recovery much simpler than without mirroring.
Example configuration:
Volume group /dev/vg00 contains the three disks, with the logical
volume configuration as shown:
|---------| |---------| |---------|
| lvol 1 | | lvol 1 | | lvol 4 |
| | | mirror | | |
|---------| |---------| |---------|
| lvol 2 | | lvol 2 | | lvol 5 |
| | | mirror | | |
|---------| |---------| | |
| lvol 3 | | lvol 3 | | |
| | | mirror | | |
|---------| |---------| |---------|
hardware address 52.6.0 52.5.0 52.4.0
device file (/dev/dsk/) c0t6d0 c0t5d0 c0t4d0
This scenario involves a head crash of the disk at hardware address
52.6.0.
[Step 4.1]
Shutdown the system, have the customer engineer replace the faulty
disk, and then boot the system in single-user mode from the alternate
boot disk. If you only have two disks in the root volume group, then
you will need to override quorum as you boot. Note that you don't have
to boot in single-user mode if all of the disk data is mirrored
elsewhere (but you may still have to override quorum).
Note: If the disk being replaced is Hot-Pluggable (or Hot-Swappable) a
reboot may not be necessary. Please inquire your customer engineer to
determine if a reboot is required. If a reboot is not required replace the
disk and go on to step 4.2.
For our example:
ISL>; hpux -is (52.5.0;0)/stand/vmunix
OR
ISL>; hpux -is -lq (52.5.0;0)/stand/vmunix
(if you need to override quorum.)
[Step 4.2]
Restore the LVM configuration/headers onto the replaced disk from
your backup of the LVM configuration, activate the volume group
with the knowledge of the replaced disk, use mkboot to add boot
information, and syncronize the BDRA with these commands:
# vgcfgrestore -n /dev/vg00 /dev/rdsk/c0t6d0
# vgchange -a y /dev/vg00
# mount /usr
# mkboot /dev/rdsk/c0t6d0
# mkboot -a "hpux (;0)/stand/vmunix" /dev/rdsk/c0t6d0
# lvlnboot -R
Note: If /usr doesn't reside in /dev/vg00 the volume group that does
contain /usr's logical volume will also have to be activated.
At this point it is a good idea to verify that the BDRA information is
accurate. This can be done with the lvlnboot comman using the -v
option. Here is an example of the output:
# lvlnboot -v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t6d0 (52.6.0) -- Boot Disk
/dev/dsk/c0t5d0 (52.5.0) -- Boot Disk
/dev/dsk/c0t4d0 (52.4.0)
Boot: lvol1 on: /dev/dsk/c0t6d0
/dev/dsk/c0t5d0
Root: lvol3 on: /dev/dsk/c0t6d0
/dev/dsk/c0t5d0
Swap: lvol2 on: /dev/dsk/c0t6d0
/dev/dsk/c0t5d0
Dump: lvol2 on: /dev/dsk/c0t6d0, 0
Note: You must have performed the command vgcfgbackup to save off
the headers prior to the disk failure (refer to Appendix A.).
[Step 4.3]
Now, synchronize mirrored logical volumes:
# vgsync /dev/vg00
[Step 4.4]
If you have any logical volumes that resided on the faulty disk that
were not mirrored, you will need to recreate them as per steps 1.4
and 1.5 from chapter 1.
[Step 4.5]
The final step in the recovery process is to reboot the system. When
the system restarts, the recovery process will be complete.
# cd /
# shutdown -r
At this stage, your system should be fully recovered. It is a good idea to
verify the system can be booted from the newly replaced drive.
By hpux:热插拔硬盘不用象文章所说启动到单用户LV M模式! |
|