Edit vaults

Edit this Vault configuration.

General

Each Vault must be uniquely named [255 characters max; however, no more than approximately 50 are recommended for the user interface]. The name is used by the Manager for all references to this Vault. A free-form Description (4000 characters max) can also be entered.

Select one or more existing Tags with the search utility or enter new a Tag Name [maximum name length is 50 characters, including special characters].

Select an existing Organization from the menu.

General

Edit the Alerting Level (t) and the Write Threshold (T_W)

The “health" alert level determines when the Monitor application alarms if Slicestor devices are missing and the Vault is approaching the “write” threshold. The health alert level is typically set slightly larger than the write threshold. For example, you can set the alert level to be (write threshold + 2) and none if the difference between width and write threshold is less than 2.

If the number of properly functioning Slicestor devices is greater than the write threshold (T_W), but less than (or equal to) the alert level (t), the Vault icon is yellow () in the Monitor application. [In this case the Vault is still fully functional.] Nonetheless the Network connections and the Monitor Event Console should be checked immediately to restore the missing Slicestor devices.

If the number of Slicestor devices available is less than the write threshold (T_W), and more than or equal to T, then the Vault is in read-only and the icon is red () .

The relationships are shown in this figure.

Enter the Provisioning Code, which must be unique for each vault. This parameter defaults to the vault name, when entered. This parameter would typically be the S3 PUT Bucket Location Constraint or Region parameter.

Attention: The following are not user configurable at the Container vault level: Delete Restricted, Name Index, and Recovery Listing.

Container versioning

For container vaults, versioning can be allowed or disallowed at the container level.

Note: If currently allowed and then disallowed, this will only apply to containers going forward.

For all containers that have versioning disabled, versioning will not be allowed. If the container has versioning enabled or suspended, versioning will continue to be allowed.

Replication

If Replication is enabled for a given Storage Pool, Replication can be enabled/disabled for the Container Vaults stored within that Storage Pool.

See Enable Replication for configurable options.

When Replication is enabled for a Vault, users are allowed to configure replication policies using S3 API for buckets within that Vault and the system replicates objects asynchronously based on the configured replication policies.

If Replication is disabled, system disallows further replication policy configurations by the user and halts asynchronous replications. Any unprocessed replications queued prior to disablement are preserved and will be processed once feature is enabled again.

Protection

If Vault Protection is enabled on the system, a Protection section is displayed when editing a vault. If Retention wasn't enabled at vault creation, you can enable it now only if the vault is empty. Once enabled, Retention cannot be disabled. In Vault Mode, you can choose whether to permanently retain objects. Once enabled, permanent retention cannot be disabled for a vault.

Note: Any changes to the protection settings of the vault affect only new objects created after the update.

In Vault Mode, the Data Retention Durations section displays the protection settings for this vault:

Retention Duration: The default retention period (in days) for an object in this vault. Protected objects that are created without a specified retention period are given this value as a retention period.
- If the vault has a finite retention duration, you can update the value to a number of days between the Minimum Duration and Maximum Duration.
- If the vault has a permanent retention duration, you can choose to use a finite value instead.
Minimum Duration: The minimum retention period (in days) for an object in this vault. When a protected object is created, this is the minimum value that can be specified for its retention period.
Maximum Duration: The maximum retention period (in days) for an object in this vault. When a protected object is created, this is the maximum value that can be specified for its retention period.

Options

Various vault specific properties will be displayed along with their currently defined value.

If wanted, enable Object Lock on a vault in a storage pool that has Object Lock enabled.

You must enable Object Lock at the system level before enabling it on a vault. See Enabling Object Lock for a system.
Once enabled at system level, you must enable Object Lock at the storage pool level. See Enabling Object Lock on a storage pool.
You must be in container mode to configure Object Lock on a vault.
Versioning support is required when using Object Lock.
Once Object Lock is enabled on individual container vaults it cannot be disabled.

Select Enable Object Lock in the Options section.
Note: The Allow Versioning on Containers option must be selected to enable Object Lock.
Click Update.

Quotas

Quota settings are optional and can be left open.

If wanted, select a value for a Soft Quota. A notification is sent to the Event Console if the soft quota setting is exceeded, but no physical restrictions to usage exist. Setting the quota higher than the total space available in the storage pool that is associated with this vault has no effect.

If wanted, select a value for a Hard Quota. The Accesser device (or DSAF SDK client) does not allow the user to exceed the hard quota value for this vault. A notification is sent to the Event Console if the hard quota setting is exceeded. Setting the quota higher than the total space available in the storage pool that is associated with this vault has no effect.

Advanced Index Settings

Enable Name Index [default = enabled (except for one-wide vaults)]. The index information is used to provide prefix-based listings and sorted listing for named object vaults. Results are returned in lexicographical order.

Note: Updating the index does require an extra "write" and reduces performance. Disable if not wanted.

Enable Recovery Listing [default = disabled] to allow listing requests. Recovery Listing results are not returned in lexicographical order. Prefix and delimiter listing request parameters are not supported by this option.

Note: When creating a vault, Recovery Listing will not be available if Name Index is enabled. If editing a vault, both <em>Name Index</em> andRecovery Listing can be enabled but the Recovery Listing settings take precedence over Name Index settings when servicing list requests. If neither listing option is enabled, HTTP error response code 405 will be returned for all listing requests.

Attention: Name Index listing results might be inaccurate if the Name Index was not enabled during object creation or deletion.

Notification Service

Enable the Notification Service to generate a notification whenever an object is written, overwritten, or deleted using the S3 protocol. The Notification Service utilizes a Producer to publish a stream of notifications to a topic. Each notification represents a single object-modifying event. You can then use a Consumer to consume the object change records and take any necessary actions.

Select a Configuration and the Topic to which you want to send notifications.