Seagate ST34572WC Especificaciones Pagina 25

  • Descarga
  • Añadir a mis manuales
  • Imprimir
  • Pagina
    / 67
  • Tabla de contenidos
  • MARCADORES
  • Valorado. / 5. Basado en revisión del cliente
Vista de pagina 24
25
The vgchange command attaches all paths for all disks in the volume group, and automatically
resumes recovering any unattached failed disks in the volume group. Therefore, only run vgchange
after all work has been completed on all disks and paths in the volume group, and it is desirable to
attach them all.
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 as follows:
For an Integrity server, follow steps 5, 6, and 8 in Appendix D: Mirroring the Root Volume on
Integrity Servers.
For a PA-RISC server, follow steps 4, 5, and 7 in Appendix D: 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 the following 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 might 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, see the LVM
Online Disk Replacement (LVM OLR) white paper.
Disk Replacement Scenarios
The following scenarios show several LVM disk replacement examples.
Scenario 1: Best Case
For this example, you have followed all the guidelines in Section 1: Preparing for Disk Recovery: all
disks are hot-swappable, all logical volumes are mirrored, and LVM OLR functionality is available on
the system. In this case, you can detach the disk using the pvchange command, replace it, reattach
it, and let LVM mirroring synchronize the logical volumes, all while the system remains up.
For this example, you assume that 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. Enter 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
Root: lvol3 on: /dev/dsk/c0t5d0
Vista de pagina 24
1 2 ... 20 21 22 23 24 25 26 27 28 29 30 ... 66 67

Comentarios a estos manuales

Sin comentarios