Skip to main content
Hitachi Vantara Knowledge

Working with extended storage pools

HCP uses extended storage pools to represent logical groups of storage components that can be used as storage tiers.

Each extended storage pool consists of one or more extended storage components that are used to access the same type of storage. A storage pool contains one or more extended storage component access points (mount points, buckets, or containers).

Each storage tier that is defined for a namespace by its service plan typically consists of only one storage pool; however, a tier can be configured to use multiple storage pools. To store objects on an extended storage tier, HCP uses all of the storage that is allocated to all of the extended storage component access points (mount points, buckets, or containers) that are contained in the storage pools that are configured for the storage tier. Therefore, the capacity of a given extended storage pool is the total amount of space that can be accessed using the extended storage component access points included in the pool. You can add access points to an extended storage pool at any time, thereby increasing the capacity of the pool.

Each extended storage component provides HCP with the information it needs to use one or more mount points, buckets, or containers to access and use the storage that’s represented by that extended storage component. However, HCP can actually use the storage that is represented by a given extended storage component only if at least one of its access points is contained in a storage pool that is included in at least one storage tier that is defined for a namespace by its service plan.

Creating an extended storage pool

Use the Create Pool wizard on the Storage page to create and configure an extended storage pool.

Each time you use the Storage page to access the Create Pool wizard, you are prompted to select the type of extended storage pool that you want to create. The System Management Console then dynamically builds the pages in the Create Pool wizard to present only the fields you need to use to configure HCP to access and use the specified type of extended storage pool.

Procedure

  1. On the left side of the Storage page, click the Pools tab.

  2. On the Pools panel, click Create Pool.

    The Get Started wizard opens.

  3. In the Get Started wizard, click the arrow to display a list of supported extended storage pools, and select the type of pool that you want to create.

    Note

    To create a ThinkOn cloud storage pool, select ThinkOn as the type of pool to configure. Then follow the same procedure as you do to configure other S3 compatible storage pools.

  4. Click Go.

    The Get Started wizard exits and the System Management Console opens the Create Pool wizard for the type of extended storage pool that you selected.

  5. Use the fields on each page of the Create Pool wizard to specify the extended storage component access points that you want to include in the pool:

    • To create an Amazon S3 storage pool, specify the configuration information that is described in Amazon S3 and S3 compatible storage pools. Then return to this procedure.
    • To create a Google Cloud storage pool, specify the configuration information that is described in Google Cloud storage pools. Then return to this procedure.
    • To create a Microsoft Azure storage pool, specify the configuration information that is described in Microsoft Azure storage pools. Then return to this procedure.
    • To create a S3 compatible storage pool, including a ThinkOn cloud storage pool, specify the configuration information that is described in S3 compatible storage pools. Then return to this procedure.
    • To create an NFS storage pool, specify the configuration information that is described in NFS storage pools. Then return to this procedure.
  6. Click Next to save the information you entered and advance to the last page of the wizard.

  7. On the Review page, take one of these actions:

    • If the extended storage pool configuration information that you entered is correct, click Finish at the bottom of the page.

    • If the extended storage pool configuration information is not correct, use the Previous and Next buttons at the bottom of each page to navigate through the pages in the wizard and change any settings that are not correct.

  8. When you are finished making changes to the storage pool configuration settings, navigate to the Review page and click Finish.

    The wizard closes. The System Management Console displays the Pools panel on the Storage page. This panel displays a list of all of the primary storage pools and extended storage pools that exist on the HCP system and provides information about the current status of each pool, including the one you just created.

Results

You created and configured the extended storage pool.

Each extended storage pool provides HCP with the information it needs to access and use the storage that is represented by that pool. However, HCP can use the storage that is represented by a given pool only if it is included in at least one storage tier that is defined for a namespace by its service plan.

Amazon S3 and S3 compatible storage pools

Each Amazon S3 or S3 compatible storage pool contains one or more buckets that are associated with specific Amazon S3 or S3 compatible storage components. Each storage pool includes all of the storage that is allocated to all of the buckets in the pool.

To enable HCP to access the storage that is represented by the storage pool, you specify the following information when you create the component:

  • The storage pool name.
  • Optionally, a description of the pool.
  • Whether you want HCP to compress object data that’s stored on the storage that’s allocated to the buckets in the storage pool.
  • Whether you want HCP to encrypt object data that’s stored on the storage that’s allocated to the buckets in the storage pool. If encryption is disabled for the system, this option is not visible.
  • For each bucket you want to include in the storage pool:
    • The name of the Amazon S3 or S3 compatible storage component that represents the endpoint that’s used to access the bucket
    • The account label used to identify the Amazon S3 Web Services user account that’s used to access the storage associated with the bucket
    • The name of the bucket
NoteAt any given time, a bucket can be included in only one storage pool.

Each bucket you add to a new Amazon S3 or S3 compatible storage pool must be empty or have only HCP data in it.

A storage pool is compliant only if all of the buckets in the pool are associated with compliant Amazon S3 or S3 compatible storage components.

Google Cloud storage pools

Each Google Cloud storage pool contains one or more buckets that are associated with specific Google Cloud storage components. Each Google Cloud storage pool includes all of the storage that’s allocated to all of the buckets in the pool.

To enable HCP to access the storage that’s represented by a Google Cloud storage pool, when you create that component, you specify the following information:

  • The storage pool name.
  • Optionally, a description of the pool.
  • Whether you want HCP to compress object data that’s stored on the storage that’s allocated to the buckets in the storage pool.
  • Whether you want HCP to encrypt object data that’s stored on the storage that’s allocated to the buckets in the storage pool. If encryption is disabled for the system, this option is not visible.
  • For each bucket you want to include in the storage pool:
    • The name of the Google Cloud storage component that represents the Google Cloud Platform endpoint that’s used to access the bucket
    • The account label used to identify the Google Cloud Platform user account that’s used to access the storage associated with the bucket
    • The name of the bucket
NoteAt any given time, a bucket can be included in only one storage pool.

Each bucket you add to a new Google Cloud storage pool must be empty or have only HCP data in it

A storage pool is compliant only if all of the buckets in the pool are associated with compliant Google Cloud storage components.

Microsoft Azure storage pools

Each Microsoft Azure storage pool contains one or more containers that are associated with specific Microsoft Azure storage components. Each Microsoft Azure storage pool includes all of the storage that’s allocated to all of the containers in the pool

To enable HCP to access the storage that’s represented by a Microsoft Azure storage pool, when you create that component, you specify the following information:

  • The storage pool name.
  • Optionally, a description of the pool.
  • Whether you want HCP to compress object data that’s stored on the storage that’s allocated to the containers in the storage pool.
  • Whether you want HCP to encrypt object data that’s stored on the storage that’s allocated to the containers in the storage pool. If encryption is disabled for the system, this option is not visible.
  • For each container you want to include in the storage pool:
    • The name of the Microsoft Azure storage component that represents the Microsoft Azure endpoint that’s used to access the container
    • The account label used to identify the Microsoft Azure user account that’s used to access the storage associated with the container
    • The name of the container
NoteAt any given time, a container can be included in only one storage pool.

Each container you add to a new Microsoft Azure storage pool must be empty or have only HCP data in it.

A storage pool is compliant only if all of the containers in the pool are associated with compliant Microsoft Azure storage components.

NFS storage pools

Each NFS storage pool contains one or more mount points that are associated with specific NFS storage components. Each NFS storage pool includes all of the storage that’s accessed using the NFS mount points included in the pool.

To enable HCP to access the storage that’s represented by an NFS storage pool, when you create that component, you specify the following information:

  • The storage pool name.
  • Optionally, a description of the pool.
  • Whether you want HCP to compress object data that’s stored on the storage that’s accessed using the NFS mount points in the storage pool.
  • Whether you want HCP to encrypt object data that’s stored on the storage that’s accessed using the NFS mount points in the storage pool. If encryption is disabled for the system, this option is not visible.
  • For each NFS mount point you want to include in the storage pool:
    • The name of the NFS storage component that represents the physical storage device that’s accessed using the NFS mount point
    • The full path name of the directory that you want to access using the NFS mount point
NoteAt any given time, an NFS mount point can be included in only one storage pool.

An NFS storage pool is compliant only if all of the NFS mount points in the pool are associated with compliant NFS storage components.

When you add an NFS mount point to a new or existing NFS storage pool, HCP creates that mount point and mounts the applicable storage volume (called an NFS volume or an external storage volume) on a node in the HCP system. HCP then adds that NFS volume to the NFS storage pool.

HCP uses a round-robin algorithm to determine which node to associate with each new NFS volume that’s added to an NFS storage pool. This method of assigning NFS volumes to the nodes in the HCP system ensures that the volumes are distributed evenly among the nodes.

If the node with which an NFS storage volume is associated becomes unavailable, that volume also becomes unavailable. HCP does not reassign the volume to a different node. When the node returns to service, the volume becomes available again.

In the HCP System Management Console, you can use the Hardware and Storage Node pages to view information about the NFS storage volumes (called external storage volumes) that are associated with each node in the HCP system.

Considerations for using NFS volumes

These considerations apply to using NFS volumes with HCP:

  • HCP can use multiple NFS shares from a single device that’s represented by an NFS storage component. Keep in mind, however, that the larger the number of shares HCP uses, the greater the I/O load on the device.
  • Typically, you specify export options for a share according to the standards for your site. However, if HCP is unable to mount the extended storage volume that you created as an NFS share, you may need to change the export options. After changing the export options, you need to export the NFS share again.
  • For each NFS mount point that’s associated with an NFS storage component, you can specify more mount options than the required ones. You might do this, for example, to set the network block size for read or write requests to the optimal size for the storage device that’s represented by the NFS storage component. However, if HCP is unable to mount the extended storage volume that you created as an NFS share, you may need to change the additional mount options that you specified.
  • If the share for an NFS volume becomes unavailable (for example, because the extended storage device that’s hosting the share is inaccessible), HCP tries periodically to remount the volume. If, after the share is available again, the remount fails, you can try to manually remount the NFS volume.

Manually remount the NFS volume

  1. On the left side of the Storage page, click Components.

  2. In the components list, click the name of the NFS storage component that’s associated with the NFS volume that you want to remount.

  3. At the top of the panel that opens, click the Mount Points tab.

  4. On the Mount Points panel, in the table row that contains the NFS mount point that corresponds to the NFS volume you want to remount, click the remount control (Remount Control icon).

    HCP attempts to remount the NFS volume. If the remount fails, contact your authorized HCP service provider for help.

    To see which node the NFS volume is associated with, hover over the status icon for the mount point on the Mount Points panel.

Considerations for using NFS volumes (cont)

  • You cannot move an NFS volume from one NFS storage pool to another.
  • You cannot control which NFS volume HCP writes data to within an NFS storage pool.
  • When HCP creates a mount point for a specific NFS volume, HCP stores a file named .__hcp_uuid__ in the shared directory on the device that’s represented by the NFS storage component associated with that mount point. This file uniquely associates the NFS shared directory with the NFS volume. As a result:
    • HCP creates only one NFS storage volume for any given exported share.
    • If you delete an NFS mount point from an NFS storage component, the associated exported share cannot be reused as is. This means that any data remaining in the NFS volume associated with the mount point becomes permanently inaccessible to HCP.
    • To reuse an exported share after the associated NFS mount point is deleted from HCP, you first need to delete any remaining files from the shared directory, including the .__hcp_uuid__ file.
    • If you inadvertently delete the .__hcp_uuid__ file from an NFS shared directory that contains other HCP data, HCP can no longer use the exported share. Contact your authorized HCP service provider for help in recreating the file.
    • When you back up an NFS shared directory that’s associated with an NFS volume, you need to ensure that the .__hcp_uuid__ file is included in the backup operation. This ensures that the file still exists in the directory after a restore operation.
Reusing the exported share

A situation can occur in which HCP can access an exported share but cannot mount the associated NFS volume. In this case, if the .__hcp_uuid__ file is the only file in the shared directory on the extended storage device on which the data in the NFS volume is stored, you can reuse the exported share.

Procedure

  1. Delete the mount point that’s associated with the NFS volume from the NFS storage component that represents the device on which the NFS volume is stored.

  2. Delete the .__hcp_uuid__ file from the shared directory.

  3. Create a new NFS mount point for the share on the same NFS storage component from which you deleted the mount point in step 1.

Manually remounting the NFS volume

If an NFS volume becomes inaccessible due to a disk failure on the extended storage device on which the data in the NFS volume is stored, you need to replace the disk, restore the data from backup, and then export the NFS share again.

In this case, the NFS volume needs to be remounted. If HCP doesn’t remount the volume automatically, you can try to manually remount the NFS volume.

Procedure

  1. On the left side of the Storage page, click Components.

  2. In the components list, click the name of the NFS storage component that’s associated with the NFS volume that you want to remount.

  3. At the top of the panel that opens, click the Mount Points tab.

  4. On the Mount Points panel, in the table row that contains the NFS mount point that corresponds to the NFS volume you want to remount, click the remount control (Remount Control icon).

    If the manual remount fails, try restarting the node with which the NFS volume is associated. To see which node the NFS volume is associated with, hover over the status icon for the mount point on the Mount Points panel.

Considerations for using NFS volumes (last part)

  • You can restore an NFS shared directory to a different location from where it was originally. If you do this, you need to modify the configuration of the associated NFS mount point to point to the new location.
  • If HCP cannot create, mount, or use an NFS volume and you’ve already determined that the permissions for the shared directory, the export options for the share, the mount point configuration on the associated NFS storage component in HCP, and the mount options for the mount point are all correct, the problem may exist on the extended storage device that’s represented by the NFS storage component on which you configured the mount point. To resolve such problems:
    • Ensure that the NFS share has been exported on the device.
    • Ensure that the NFS server is running on the device.
    • Ensure that any NFS security software on the device is not blocking access by any of the HCP nodes.
    • Check the system log file on the device for messages indicating device errors. Then correct those errors.

If HCP still cannot create, mount, or use the volume, contact your authorized HCP service provider for help.

Modifying an extended storage pool

You can use the Pools panel on the Storage page to view and modify the configuration of any extended storage pool. To display this panel, click the Pools tab on the left side of the Storage page.

You can use the Pools panel to modify the configuration of any extended storage pool in any of the following ways:

  • Change one or more of the configuration settings that are specified when the pool is first created:
    • Amazon S3 and S3 compatible storage pools configuration settings
    • Google Cloud storage pools configuration settings
    • Microsoft Azure storage pools configuration settings
    • Amazon S3 and S3 compatible storage pools configuration settings
    • NFS storage pools configuration settings
  • Add one or more storage component access points (mount points, buckets, or containers) to an extended storage pool.
  • Delete one or more storage component access points from an extended storage pool.

Modifying the configuration settings used for an extended storage pool

  1. On the left side of the Storage page, click the Pools tab.

  2. On the Pools panel, click the table row that contains the name of the pool that you want to modify.

  3. At the top of the panel that opens, click the Settings tab.

  4. On the panel that opens, use the fields to change any of the settings that are currently used for the pool.

  5. Click Update Settings.

Adding access points to an extended storage pool

You can add one or more access points (mount points, buckets, or containers) to an existing extended storage pool.

Procedure

  1. On the left side of the Storage page, click the Pools tab.

  2. On the Pools panel, click the table row that contains the name of the pool to which you want to add one or more access points.

  3. At the top of the panel that opens, click the tab that corresponds to the type of access point that’s contained in the pool (Mount Points, Buckets, or Containers).

    The AccessPointType panel opens, displaying a table that contains a list of existing access points (mount points, buckets, or containers) that can be included in the type of storage pool that you’re currently configuring. The access points that are currently included in the pool are selected.

  4. Select each existing access point that you want to add to the storage pool.

  5. Click Update Settings.

Deleting access points from an extended storage pool

You can delete one or more unused access points (mount points, buckets, or containers) from an existing extended storage pool.

Procedure

  1. On the left side of the Storage page, click the Pools tab.

  2. On the Pools panel, click the table row that contains the name of the pool from which you want to delete one or more access points.

  3. At the top of the panel that opens, click the tab that corresponds to the type of access point that’s contained in the pool (Mount Points, Buckets, or Containers).

    The AccessPointType panel opens, displaying a table that contains a list of existing access points (mount points, buckets, or containers) that can be included in the type of storage pool that you’re currently configuring. The access points that are currently included in the pool are selected.

  4. Deselect each existing access point that you want to delete from the storage pool.

    Note

    After you store data on an NFS volume, you cannot delete it from its NFS storage pool. Also, you cannot delete all of the access points in a storage pool if that pool is currently used for a storage tier that’s defined for a namespace by its service plan.

  5. Click Update Settings.

Remounting an NFS volume

If an NFS volume is experiencing problems, you can manually try to remount that NFS volume. Before doing that, however, you should ensure that the device hosting the NFS volume and the network connection to that device are functioning properly. You should also ensure that the exported share that corresponds to the NFS volume is configured correctly on the host device.

HCP can take up to a minute to respond to a remount request.

Procedure

  1. On the left side of the Storage page, click Components.

  2. In the components list, click the name of the NFS storage component that’s associated with the NFS volume that you want to remount.

  3. At the top of the panel that opens, click the Mount Points tab.

  4. On the Mount Points panel, in the table row that contains the NFS mount point that corresponds to the NFS volume you want to remount, click the remount control (GUID-38C7E2E8-7113-4F02-8EBA-AAE3ACC5868F-low.png ).

Next steps

If the manual remount fails, try restarting the node with which the NFS volume is associated. To see which node the NFS volume is associated with, hover over the status icon for the mount point on the Mount Points panel.

Deleting an extended storage pool

If the storage that’s represented by an extended storage pool is not currently being used to store objects in any namespaces defined on the HCP system, you can safely delete that storage pool.

If, however, the storage that’s represented by an extended storage pool is currently being used to store object data, you cannot delete that pool. Before you can delete a storage pool, you need to first remove the extended storage pool from all storage tiers that currently include that pool and then retire the storage pool by migrating all of the data off it.

When you retire an extended storage pool, HCP migrates the data off that pool and then deletes that pool from the system.

Procedure

  1. On the left side of the Storage page, click the Pools tab.

    The Pools pane opens, showing a list of storage pools that are currently defined on the HCP system. A delete control (Delete Control icon) appears in the row for each unused storage pool.
  2. Click the delete control for any unused extended storage pool to delete it from the HCP system.

 

  • Was this article helpful?