Upon completion of this module, you should be able to:
Move an empty disk to a different disk group
Move a populated disk to a new disk group
Perform a snapshot backup
Move a disk group between systems
Assign and remove hot spares
Enable and disable hot relocation
Create a striped pro volume with a file system
Evacuating a Disk
If a disk begins to fail, its contents can be easily moved to another disk providing the following is true:
The new disk is in the same disk group
The new disk does not contain conflicting objects
The new disk has sufficient free space
Before starting the evacuation process, you should:
Find out what volume the failing plex is associated with and name of the disks that are associated with it
Find out the disk group associated with the failing disk drive
Determine if any other volumes are associated with the failing disk drive
Find a new disk with enough free space to perform the evacuation
Check for any volume conflicts associated with the new disk
If the disk you want to move contains an active volume and you do not care if the data is lost, you must:
1,Unmount a related file system and disable any related applications
2,Stop the volume
# vxvol stop volume_name
3,Delete the volume configuration
# vxedit -r rm volume_name
4,Remove the disk from the disk group
# vxdg rmdisk disk_name
5,Add the disk to a different disk group
# vgdg -g new_dg adddisk new02=c1t3d0
Hot Devices
Automatic replacement of failed disk drives by assigned spares can be assomplished using either:
An older hot spare daemon, vxsparecheck
A new hot relocation daemon, vxreload
Depending on how the /etc/rc2.d/S95vxvm-recover file is configured, either the older hot spare daemon, vxsparecheck ,will start at boot time or the newer hot relocation daemon, vxreload, will start
Hot-Relocatioin Failures
If relocation is not possible, the system administrator is notified and no further action is taken. Relocation is not possible if:
Subdisks do not belong to a mirrored or RAID-5 volume
Not enough space is available on spare disks or free space
The only available space for relocation is on a disk that contains any portion of the surviving mirror or RAID-5 volume
A mirrored volume has a dirty region logging log subdisk as part of its data plex, subdisks belonging to that plex cannot be relocated
The failure is a log plex, a new log plex is created so it is not actually relocated
Snapshot Backups
The SSVM snapshot feature automatically prepares a volume for backup by performing the following operations:
Attaching a new write-only mirror to the volume
Copying the data to the new mirror
Detaching the mirror
Creating a new volume from the new mirror
阅读(2403) | 评论(0) | 转发(0) |
