Data evacuation state workflow

CAUTION:
All IBM Cloud Object Storage Slicestor® devices that are included in the Storage Pool first must be upgraded to ClevOS 3.4 or higher.
Slicestor® Data Evacuation follows this simple workflow:
Figure 1. Slicestor Data Evacuation State Diagram
image
  1. Follow the steps that are outlined in Replace a Device in the Manager Administration Guide.
  2. When a Slicestor® device is replaced, data evacuation starts and enters the Evacuating state. It can be paused and resumed after it begins evacuation.
  3. When all data is copied to the Destination Slicestor® device, the evacuation enters the final Completed state.
Attention: Do not remove Slicestor® devices during an evacuation.

If the Source Slicestor® device is reimaged or removed from the System Manager before data evacuation is completed, all data slices that are not already evacuated are lost. The data slices must be rebuilt.

If the Destination Slicestor® device is reimaged for any reason during data evacuation, data slices that are already evacuated are not present and are lost. These data slices must be rebuilt.

Do not remove or reimage any Slicestor® device that is involved in data evacuation while it is in progress in a production environment.

For more information about the Rebuilder process, see the Rebuilder Agent guidelines.

Note: Lists and reads are disabled on the Destination Slicestor® device during evacuation. It prevents the Rebuilder process on other Slicestor® devices or clients from gathering incomplete data.