Conversion compatibility requirements

Edit online

Not all vaults can be converted. Several compatibility requirements exist that could prevent a vault, or an access pool, from being compatible for conversion.

System-wide requirements.
  • A service vault must exist in the system.
Requirements for each vault.
  • At least one account must have readWrite or owner permissions assigned.
  • Name index must be enabled 1.
  • Vault proxy is not allowed.
  • Recovery Listing is not allowed 1.
  • Locked vault is not allowed 1.
  • Delete restrictions not allowed 1.
  • Versioning is not allowed 1.
  • Being one side of a mirror is not allowed.
Requirements for each vault's storage pool.
  • Must use advanced storage engines, such as Packed Storage or Zoned Storage.
Requirements for each access pool.
  • API type must be 'Cloud Object Storage' or 'OpenStack Object Storage'.
  • Mirrors cannot be deployed.
Requirements for each account with permission to a selected vault.
  • One or more access keys must be created.

If a system does not obey these requirements, several of them can be reconfigured in the Cloud Object Storage Manager. For instance, if a vault proxy is configured on a vault, "fixing" the vault for conversion requires the vault remove the proxy.

1 No simple fix for this requirement exists. In these cases, no way to convert the standard vault to a container vault exists, at least without first migrating data to a new vault by using the vault migration function.

Note: If a vault contains objects that are written with Simple Object (SOH), those objects cannot be read if the vault is converted to a container vault.