Using S3-Compatible Storage as a Repository Type for Extended Journal Copy
Zerto now supports S3-compatible storage as a repository type for Extended Journal Copy.
| • | The S3-compatible storage repository can either be on-premise or in public clouds. |
| • | Zerto implements a subset of S3 API for supporting S3-compatible storage. |
| • | The API signature version utilized by Zerto is S3 SDK version 1.8.83 |
Important: Zerto does not test and validate all S3-compatible storage platforms that can be potentially utilized by end-users. Therefore, it is the end-user responsibility to validate the S3 API version and to ensure that it meets the required list of S3 API actions/calls utilized by Zerto.
| • | S3-compatible storage is not supported for primary volumes, recovery volumes, and journal volumes. |
| • | Zerto recommends that users perform functional tests such as Repository creation, backups and restores of VMs, and deletion of Repositories prior to selecting any S3-compatible storage. |
| • | It is also recommended that users test performance of the S3-compatible storage prior to selecting it for a Repository. |
If assistance is needed for testing, please contact your Zerto account representative to engage with Zerto professional services.
| • | S3 incompatibility or performance issues cannot be addressed by opening support tickets with Zerto. Instead, an idea request via the MyZerto portal should be created. Requests will be evaluated, but are not a guaranteed within any specified period. |