Repair volume(s)
volume repair (--suspend [time=time ]) | --resume volume repair name --resume volume repair name [--force | (--suspend [time=time])] volume repair [name] --status [--batch] vol repair --all [--force]
Name of the volume to repair or retrieve status for.
Suspend volume repair operation(s); for a maximum of 1 week
Resume volume repair operation(s)
(optional) Number of minutes to suspend the volume repair operation(s). If not specified, volume repair operation(s) are suspended for 60 minutes.
Start repairing the volume right away.
Display volume repair operation status.
Display volume repair operation status in UDL format
Initiate backgound volume repair (alias for 'vol check')
volume repair /system:MYSQL5.boot
repair global catalog class volume
volume repair my-app:data --force
start repair of app user volume right away
volume repair my-app:DBASE.boot
repair app singleton class volume
volume repair my-app/local:DBASE.boot
repair app catalog class volume
volume repair --suspend time=30
Suspend automatic volume repair for 30 minutes
volume repair --resume
Resume automatic volume repair
volume repair my-app:data --suspend time=30
Suspend repair of an app user volume for 30 minutes
volume repair my-app:data --resume
Resume repair of an app user volume
volume repair --status
Retrieve the current repair status for all volumes
volume repair my-app:data --status
Retrieve the current repair status of an app user volume
vol repair --all --force
Resume any suspended volume repairs and initiate check for volumes that need repair.
Note: Adhere to the naming conventions for CA 3Tera AppLogic entities.
All volume repair operations are performed in the background (one per server). To retrieve the current status of a volume repair operation, execute one of the following:
vol repair --status - retrieve repair status for all volumes
vol repair name --status - retrieve repair status for a single volume.
The automated volume repair in CA 3Tera AppLogic retrieves the list of degraded volumes that need to be repaired once every 6 hours. The user can force CA 3Tera AppLogic to retrieve the list of degraded volumes by executing vol check; this can be used to verify that the current list of degraded volumes are scheduled for repair.
When initiating the repair of a volume - vol repair name - the repair of the volume will start immediately if there are enough available servers to execute the repair. If there are not available servers, the repair will start when the servers become available.
When initiating a repair of a volume with --force, the repair operation is started immediately and may result in the suspension of the repair of a different volume currently being repaired. Use this command if the repair of a particular volume needs to be initiated right away.
When initiating the repair of all volumes with --force, all volumes will be repaired including suspended volumes, whether they were suspended by the user or CA AppLogic itself.
When the repair of a volume is suspended, the repair operation on the volume is stopped and restarted as soon as servers are available following the specified time period.
When resuming the repair of a volume with --resume, the volume will be repaired as soon as enough servers become available.
When the repair of a volume fails, the volume will be rescheduled for repair. If the volume fails to be repaired three times within a 24 hour period, the volume repair will not be attempted again until 24 hours later. If there is a volume on the grid that continuously fails repair, contact your service provider immediately.
The following is a description of the various volume statuses that are reported when vol repair is executed with the --status option:
- error: The volume is in 'error' state meaning that the volume does not have any good streams (that is, mirrors)
- failed: One or more repair operations over the volume failed
- repairing: The volume is currently being repaired
- queued: The volume is queued for repair. Once servers become available, the repair for the volume will be initiated.
- suspended: The repair of the volume has been suspended or the volume has failed to be repaired and will be re-scheduled for repair.
- complete : The repair operation of the volume was successfully completed.
A specification of the repair status output can be found here.
|
Copyright © 2011 CA.
All rights reserved.
|
|