--- title: "Zerto LTR - Configure long-term retention bucket" description: "Learn how to configure and manage an OVHcloud Object Storage bucket for long-term retention (LTR) with Zerto." url: https://docs.ovhcloud.com/it/guides/hosted-private-cloud/powered-by-vmware/zerto-ltr lang: it lastUpdated: 2026-06-11 --- # Zerto LTR - Configure long-term retention bucket ## Objective This guide explains the purpose of the **LTR (Long Term Retention)** feature in Zerto and how to configure it to retain your recovery points for an extended period. This feature allows you to: - Associate an OVHcloud Object Storage bucket with Zerto for long-term retention. - Define the data immutability policy. - Secure the configuration with proper connection information. - Easily recover the configuration in case of failure. ## Prerequisites - Have an active Managed VMware vSphere service with Zerto enabled. - Have an OVHcloud Object Storage bucket. - Have S31 credentials associated with this bucket (access key and secret key). :::info To configure LTR, navigate to the Zerto section of your datacenter in Managed VMware vSphere. ::: ## In practice ### Step 1: Understanding the requested information When adding or editing an LTR bucket, the following fields are used: - `repositoryName`: name of the repository displayed in Zerto. - `bucketName`: name of the OVHcloud Object Storage bucket. - `endPointUrl`: URL of the S3 endpoint for the target region. - `objectStorageAccessKey`: S3 access key. - `objectStorageSecretKey`: S3 secret key. - `repositoryType`: type of repository (`highPerformance` or `standard`). - `defaultRepository`: set this repository as the default repository. Field requirements: | Field | Status | Details | | :--------------------- | :---------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------- | | repositoryName | Required | Name of the repository displayed in Zerto. | | bucketName | Required | Name of the OVHcloud Object Storage bucket. | | endPointUrl | Required | S3 endpoint for the bucket region. | | objectStorageAccessKey | Required | S3 access key for the bucket. | | objectStorageSecretKey | Required | S3 secret key for the bucket. | | repositoryType | Required | `highPerformance` or `standard` (this parameter corresponds to the Object Storage bucket class and can also be managed from the Object Storage interface). | | enableImmutability | Optional | Enables immutability protection. | | immutabilityPolicy | Conditional | Required if `enableImmutability` is enabled. | | numberOfDays | Conditional | Required if `immutabilityPolicy = Period` (30 to 90 days). | | defaultRepository | Optional | Sets this repository as the default value. | ### Step 2: Configure immutability To configure immutability, enable the `enableImmutability` option, then choose a policy: - `Period`: you explicitly define a duration in days. - `perVPGRetentionPolicy`: the duration is driven by the Zerto retention policy. If you choose `Period`, set `numberOfDays` to a value between **30 and 90 days**. ### Step 3: Verify the Object Lock requirement **Object Lock** must be enabled on the OVHcloud Object Storage bucket. Without this configuration, long-term retention cannot function correctly. Message to display: ```text Object Lock must be enabled on your OVHcloud Object Storage bucket. Without this configuration, LTR will not work correctly. ``` :::warning If Object Lock is not enabled, LTR configuration may fail or not guarantee the expected immutability. ::: ### Step 4: Use up-to-date region endpoints Verify that the endpoint entered matches the OVHcloud region of your bucket. Region endpoints may change; always use the most recent values provided in the interface. ### Step 5: Manage configuration failures If a configuration attempt fails: - An explicit error message must indicate that the configuration did not succeed. - The add form must become available again to allow another attempt. ### Step 6: Understanding the state without a configured bucket When no bucket is associated, the page displays: - A message explaining that an OVHcloud Object Storage bucket is necessary to enable LTR. - A **Order an OVHcloud Bucket** button redirecting to OVHcloud Object Storage ordering. - If you have a Public Cloud project, the page opens the Object Storage section of the Manager. - Otherwise, it opens the Object Storage page on the OVHcloud website. - A secondary **Add Existing Bucket** button opens the add window. ### Step 7: Manage existing buckets For each configured bucket, the following actions are available: - `Edit`: modify the bucket configuration. - `Delete`: delete the bucket configuration. ## Go further - [Using Zerto between OVHcloud and a third-party platform](/it/guides/hosted-private-cloud/powered-by-vmware/zerto-virtual-replication-customer-to-ovh.md) - [Setting up Zerto Virtual Replication between two OVHcloud datacenters](/it/guides/hosted-private-cloud/powered-by-vmware/zerto-virtual-replication-vmware-vsphere-drp.md) Ask questions, give your feedback and interact directly with the team building our Hosted Private Cloud services on the dedicated [Discord](https://discord.gg/ovhcloud) channel. Join our [community of users](https://community.ovhcloud.com/). 1 : S3 is a trademark of Amazon Technologies, Inc. OVHcloud's service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.