DataKeeper Volume Resize

DataKeeper allows users to extend and shrink their DataKeeper volumes dynamically while retaining mirror settings. Once the resize is complete, a partial resync will be performed.

Note: This resize procedure should be performed on only one volume at a time.

!WARNING Do NOT attempt to perform the resize in releases prior to DataKeeper for Windows v7.4.

Restrictions

• DataKeeper does not support changing the disk type of the physical disk where a mirrored volume is located (for example, Basic Disk to Dynamic Disk — mirror must be deleted prior to creating your dynamic disk).

• DataKeeper does not support third-party partition resizing products.

• DataKeeper does not support volume resizing on shared volumes configured on Dynamic Disks. Windows cannot reliably use a shared Dynamic Disk.

Non-Shared Volume Procedure

Example configurations for using this procedure include the following:

Disk-to-Disk
One-to-One
One-to-Many ‘Multiple Targets’
Many-to-One

To resize your DataKeeper volume in a non-shared volume configuration, perform the following steps.

1. Pause all mirrors and unlock all target volumes via the Pause and Unlock mirror option in the DataKeeper UI.

Note: A mirror must be in a “mirroring” state in order to Pause or Unlock it.

2. Using the Windows Disk Management utility, increase (or decrease if allowed by the Operating System) the volume size on the source system by selecting “Extend Volume” or “Shrink Volume” in the Resizing Wizard. Once that resize is complete and verified, resize the target system(s). Make sure that the raw volume size of each target is greater than or equal to the size of the source volume.

Note: The Windows Disk Management utility will take longer to start on the target node based on the number of drives. Because the Windows operating system has error condition retries built in when a volume is locked, the speed with which it starts on the “locked” target node is affected.

Note: After the resizes on the source and target you will need to run a Rescan in Disk Management. Then, you will need to run the following on each system in the cluster so that DataKeeper sees the new volume size:

• Go to a command prompt (run as administrator)

• cd %extmirrbase%

• emcmd . updatevolumeinfo <enter-volume-letter>

3. Continue and Lock the mirrors after volumes have been resized. The mirroring process should resume and a partial resync should occur.

Shared Volume Procedure – Basic Disk

This resizing procedure will work on shared volumes if the shared volume is configured on a Basic Disk. Example configurations for using this procedure include the following:

*Shared Volume – More than one system has access to the same physical storage. This shared volume can be either on the source side of the mirror or on the target side.

N-Shared-Disk Replicated to One
N-Shared-Disk Replicated to N-Shared-Disk
N-Shared-Disk Replicated to Multiple N-Shared-Disk Targets

If there is free space on the disk, the volume can be extended to use the additional space.

1. Pause all mirrors and unlock all target volumes via the Pause and Unlock mirror option in the DataKeeper UI.

2. Shut down (power off) all shared source and/or shared target systems. (Note: Current source and current target systems should not be shut down.)

3. Change the volume sizes as noted above in the Non-Shared Volume procedure.

4. Continue and Lock the mirrors after resizing has completed.

5. Power on all shared systems. The new volume configuration will automatically be recognized.

Error Handling:

1. After performing the Continue and Lock, if the GUI abnormally maintains the “Paused” mirror state, check the system logs on both source and target nodes.

2. DataKeeper will prevent a mirror resync from starting if the target volume is smaller than the source volume. If the system logs show such an error, the target volume must be unlocked manually via the UNLOCKVOLUME command, and the volume must again be resized making sure that the volume size of the target is greater than or equal to the size of the source volume. Then proceed with the Continue and Lock step above.

3. DataKeeper, upon continuing the mirror, will reallocate the bitmap file and in-memory bitmap buffer using the new volume size. In the event DataKeeper is unsuccessful in reallocating the bitmap buffer – due to insufficient memory resources on the source or target – the mirror will be placed into a ‘Broken’ state which will require a FULL resync.

4. Once resizing a volume has begun, there is no way to back out of the resizing feature and the associated error handling as DataKeeper will have to reallocate the bitmap file and in-memory bitmap buffer. Any failure of this reallocation procedure will break the mirror and force a FULL resync.