If the storage that’s represented by an extended storage component is not currently being used to store objects in any namespaces defined on the HCP system, you can safely delete that storage component.
If, however, the storage that’s represented by an extended storage component is currently being used to store object data, you cannot delete that component. Instead you need to either retire that component or abandon it.
When you retire an extended storage component, HCP migrates the data off that component and then deletes that component from the system. For information about retiring an extended storage component, see Retiring storage.
When you abandon an extended storage component, HCP deletes that component from the system without attempting to migrate any of the stored data off the extended storage component. This operation is not recommended because it may result in data loss. If the only existing copies of the data for a given object are stored on a single extended storage component, when you abandon that component, the object data becomes permanently inaccessible to HCP.
Retiring and deleting a component is a much safer alternative to abandoning that component, as retiring a component ensures that the data stored on that component remains protected at the applicable levels. You should consider abandoning an extended storage component only as a last resort and only after you’ve taken the necessary steps to ensure that the data stored on the component exists elsewhere in the HCP system.
© 2015, 2020 Hitachi Vantara LLC. All rights reserved.