Manage storage groups by configuring the storage to make it attachable or non-attachable. You also have the option of marking a storage read-only so that App Volumes Manager can skip writing to that storage when updating a package or an AppStack.
The list of storage locations and their status is displayed on the Managed Storage Locations page.
When you configure a storage as not attachable, the App Volumes Manager ignores the storage while mounting volumes.
For example, if you have set up two vCenter Server instances. Each instance can have a local storage and shared storage capability. You can configure the slower-performing storage as Set Not Attachable. A storage thus configured as not attachable is ignored by the manager while mounting volumes and the storage can be used solely for replication of packages and AppStacks.
If the metadata of a package or an AppStack is updated and the package or AppStack is replicated from a read-only storage, App Volumes Manager skips writing the updates to the read-only storage, but the package or AppStack gets replicated. The replicated package or AppStack does not have the updated metadata. You have the option of removing the read-only marker on the storage.
- To see the list of storage locations that are visible to the App Volumes Manager, click .
- To see the details of a storage such as the current attachable and read-only statuses and other information, click the storage name that you desire to view.
- Select the storage whose status you want to change.
- Depending on the current attachable status of the storage, click Set Attachable or Set Not Attachable and confirm the operation.
- Depending on the current read-only status of the storage, click Mark Read-only or Unmark Read-only and confirm the operation.