Deleting a HyperScale Storage Pool

You can delete a HyperScale storage pool.

Procedure

  1. Kill the jobs for the subclients that are associated with the storage policy that is associated with the Global Deduplication Storage Policy of the node.

    For instructions, see Killing a Job in the Job Controller.

  2. Disassociate all subclients that are associated with the storage policies that are dependent on the Global Deduplication Storage Policy that is associated with the storage pool.

    For instructions, see Updating Subclient Associations of a Storage Policy Copy.

  3. Delete the storage policies that are dependent on the Global Deduplication Storage Policy.

    For instructions, see Deleting a Storage Policy.

  4. Delete the storage pool associated with the MediaAgent from the Command Center.

    For instructions, see Deleting a Hyperscale Storage.

  5. Log on to one of the nodes in the HyperScale storage pool.

  6. Execute the following commands in the commandline:

    umount -l /ws/glus_<device_ID>
    gluster v stop <gluster_volume_name>
    gluster v delete <gluster_volume_name>
  7. Log on to all the nodes in the HyperScale storage pool, and then delete the following entry from the /etc/fstab file.

    /ws/glus_<device_ID>
  8. Log on to a node in the storage pool, and review the list of peers under the /var/lib/glusterd/peers.

  9. To detach the peers, execute the following command:

    gluster peer detach <peer_name>
  10. If a peer is not reachable, execute the following command in the current node that you logged on and other nodes.

    gluster peer detach <peer_name> force
  11. Log on to all the nodes in the HyperScale storage pool, and then delete the contents under /ws/disk* and /ws/ddb.

What to Do Next

Delete the MediaAgent nodes in the HyperScale storage pool. For instructions, see Deleting a MediaAgent.

Loading...