Seagate ST34572WC Specifications Page 19

  • Download
  • Add to my manuals
  • Print
  • Page
    / 36
  • Table of contents
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 18
Step 5: Restoring Lost Data to the Disk
This final step can be a straightforward resynchronization for mirrored configurations, or a recovery of data from
backup media.
If a mirror of the root disk was replaced, initialize its boot information:
For an Integrity server, follow steps 5, 6, and 8 in
Appendix A: Mirroring the Root Volume on
Integrity Servers.
For a PA-RISC server, follow steps 4, 5, and 7 in
Appendix A: Mirroring the Root Volume on PA-RISC
Servers.
If all the data on the replaced disk was mirrored, you do not have to do anything; LVM automatically
synchronizes the data on the disk with the other mirror copies of the data.
If the disk contained any unmirrored logical volumes (or mirrored logical volumes that did not have a
current copy on the system), restore the data from backup, mount the file systems, and restart any
applications you halted in step 1.
Replacing a LVM Disk in an HP Serviceguard Cluster Volume Group
Replacing LVM disks in an HP Serviceguard cluster follows the same procedure described in steps 1-5, unless the
volume group is shared. If the volume group is shared, make these two changes:
When disabling LVM access to the disk, perform any online disk replacement steps individually on each
cluster node sharing the volume group. If you do not have LVM OLR, and you detach the disk, you will
probably need to make configuration changes that require you to deactivate the volume group on all
cluster nodes. However, if you have Shared LVM Single Node Online Volume Reconfiguration (SNOR)
installed, you can leave the volume group activated on one of the cluster nodes.
When re-enabling LVM access, activate the physical volume on each cluster node sharing the volume
group.
Special care is required when performing a Serviceguard rolling upgrade. For details, refer to the
LVM Online
Disk Replacement (LVM OLR) white paper.
Disk Replacement Scenarios
Following are several scenarios that illustrate LVM disk replacement.
Scenario 1: Best Case
For this example, you have followed all the guidelines in section 1—all disks are hot-swappable, all logical
volumes are mirrored, and LVM OLR patches are installed. In this case, you can detach the disk with pvchange,
replace it, reattach it, and let LVM mirroring synchronize the logical volumes—all while the system remains up.
For this example, you assume the bad disk is at hardware path 2/0/7.15.0 and has device special files named
/dev/rdsk/c2t15d0 and /dev/dsk/c2t15d0.
Check that the disk is not in the root volume group, and that all logical volumes on the bad disk are mirrored with
a current copy available. Run the following commands:
# lvlnboot –v
Boot Definitions for Volume Group /dev/vg00:
Physical Volumes belonging in Root Volume Group:
/dev/dsk/c0t5d0 (0/0/0/3/0.5.0) -- Boot Disk
Boot: lvol1 on: /dev/dsk/c0t5d0
19
Page view 18
1 2 ... 14 15 16 17 18 19 20 21 22 23 24 ... 35 36

Comments to this Manuals

No comments