Resizing Guarded in-Place Data Transformation Devices

Devices configured for in-Place Data Transformation can be resized using the system-provided resizing utilities. If you are using a file system on the GuardPoint, you can mount the file system after resizing the device and then grow the file system to the new size using the appropriate utility such as xfs_growfs or resize2fs.

Do not shrink IDT GuardPoints. Due to relocation of user data from CTE private region, if you shrink the device, you may corrupt data on the device.

1. Stop applications from accessing the GuardPoint.

   • Unmount the file system if the device is mounted.

   • Disable GuardPoints: auto-guard if it is enabled on the CipherTrust Manager, or manual-guard if it is enabled on the protected host.

2. Use the native disk management tools to resize the device.

3. After resizing the device, check the size of the device. For Linux, you can use the fdisk –l command.

4. If the reported size does not match what you expect, you may need to rescan your storage devices using the command appropriate for the device's connection type.

5. Once the expected size is achieved, enable the GuardPoint and restart your applications.

Examples

The following example show the administrative steps to grow an XFS file system mounted on an ES GuardPoint. The example shows a device of size 41,347,072 sectors resized to 43,395,072 sectors.

In this example we resize the device on the storage array to 43395072 sectors. Notice that the voradmin command reports the old device size until the device is guarded.

The final step shown in below is to mount and resize the XFS file system to include the extended space into the file system.