Temporaly failure:

-Data still on disk

-Minimal or no data loss
Permanent Failure:
-Data on disk destroyed
- Redundant volumes: no data loss
-Non-redundant volumes:
Data loss
Data must restored from backup
AUTOMATIC DEVICE RECOVERY
1-Hardware problem resolved
2-OS recognizes disk array and disk
3-DMP recognizes disk array, enables paths to disks
Messages logged to system log file
RECOVERING FROM TEMPORARY DISK GRUPO FAILURES
-Automatic DMP recovery has ocurred
-Disk still contain provate regio
-Disk group configuration is still intact
1-Umount disable file system
2-Deport the disk group
3-Ensure DMP path are enable (from automatic recovery)
4-Import the disk group
5-If necessary , start the volumes
6-Perform file system checks
7-Mount the file systems
RECOVERING FROM PERMANENT DISK GRUPO FAILURES
-Automatic DMP recovery has ocurred
-Private region on disk destroyed
-No disk group configuration on disk
1-Umount disable file system
2-Deport the disk group
3-Restore disk group configuration
4-Recreate the file system
5-Restore data from backup
vxconfigbackupd -> make automatic backup dg config
DISK RECOVERY TASKS
1-Recovery the physical disk
Temporary: Fix the cable, replace HBA
Permanent: Replace failed disk with a new disk
2-Attach the VxVM disk
3-Recover the volumes
Start disable volumes
Resynchronize redundant volumes
RECOVERING THE PHYSICAL DISK
1-Connect the new disk or resolve the hardware problem
2-Ensure that OS recognizes the disk

3-Direct VxVM to recognize the disk:

Using original disk device:
vxdisk scandisks device=os_devicename
Using a new disk:
vxdisk scandisk new
4-Verify that VxVM recognizes the disk:
vxdisk -o alldgs list
ATTACHING THE VXVM DISK- PERMANENT FAILURES
vxdiskadm : Replace a failed or removed disk
vxdisksetup -i accessname (if new disk)
vxdg -k -g diskgroup adddisk dm_name=accessname
-k forces VxVM to reuse failed disk,s media name with new disk
vxdisksetup -i emc_dd2
vxdg -k -g appdg adddisk appdg02=emc0_d2
ATTACHING THE VXVM DISK - TEMPORARY FAILURES
If vxattachd is running:
Disk name automatically reattached
Redundancy volume recovery automatically started
If vxattachd is not running:
vxreattach [-br] [accessname]
-r:recover redundancy volumes using vxrecover
-b: background recovery
vxreattach emc0_dd2
RECOVERING A VOLUME
Redundant volumes:
vxrecover [-bs] [-g diskgroup] [volume_name | dm_name]
-b: background recovery
-s: start all startable volumes
vxrecover -bs -g appdg appvol
Non-redundant volumes:
vxvol [-g diskgroup] -f start volume_name
-f force start volumes
vxvol -g appdg -f start concatvol

INTERMITTENT DISK FAILURES

VxVM can mark a disk as failing if the disk is
experiencing I/O failures bur is still accesible
Failing disk are not used for any new volume space
When the problem is resolved, turn off the failing disk flag:
xvedit -d diskgroup set failing=off dm_name
HOT-RELOCATION PROCESS
1-vxrelocd detects disk failure
2-Subdisk for redundancy volumes are relocated to spare disk or free space
3-Volume recovery is attemped
Admin is notify by email each step
MANAGING SPARE DISK
vxdiskadm:

Turn off the spare flag on a disk

Exclude a disk from hot-relocation use
Make a disk available for hot-relocation use
To deasignate a disk as a spare:
vxedit -g diskgroup set spare=on|off dm_name
vxedit -g diskgroup set nohotuse=on|off dm_name
UNRELOCATING A DISK
vxdiskadm: Unrelocate subdisks back to a disk
vxunreloc [-f] -g diskgroup [-n dm_name] orig_dm_name
-f Force unrelocation
-n unrelocates to a disk other tan original
orig_dm_name Original disk before relocation