You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -146,6 +147,7 @@ The basic structure of a replication rule within the configuration JSON file is
146
147
| Destination | A container for information about the replication destination and its configurations. | Yes |
147
148
| DeleteMarkerReplication | Tells if delete operations should be replicated. | Yes |
148
149
| Bucket | The destination bucket (to replicate to multiple destinations, you must create multiple replication rules). | Yes |
150
+
| StorageClass | The destination storage class. By default, OVHcloud Object Storage uses the storage class of the source object to create the object replica.<br><br> Please note that **not all storage classes are available in all regions** i.e some storage classes are not supported in some regions such as EXPRESS_ONEZONE which is not supported in 3AZ regions. To learn more about the available storage classes in each region check [our documentation](/pages/storage_and_backup/object_storage/s3_location). | Yes |
149
151
| And | You can apply multiple selection criteria in the filter. | No |
With Object Storage in a 3-AZ region, we have introduced a new option called **Offsite Replication**, which simplifies the replication process and automatically replicates your data to a remote site forgreater resiliency with a one-click actionin the OVHcloud Control Panel.
446
+
This feature is only available forprimary Object Storagein a 3-AZ region (to know more about existing 1-AZ and 3-AZ regions, see [Endpoints and Object Storage geoavailability](/pages/storage_and_backup/object_storage/s3_location)) and is based on an OVHcloud auto-generated and managed replication rule configuration:
447
+
448
+
- Data is replicated on a remote 1-AZ region. The system will automatically determine the most suitable location among Strasbourg, Gravelines, and Roubaix, ensuring efficient and reliable offsite data protection.
449
+
- Objects stored in the replica bucket are stored in an **Infrequent Access** class and are billed differently. View pricing on [this page](/links/public-cloud/prices). This class is designed for less frequently accessed data and allow you to reduce your overall Object Storage bill together with Standard-class performance level. This said, if the destination bucket storage class doesn’t suit your needs, you can choose another approach and use the asynchronous replication feature and manage the replication rule configuration by yourself.
450
+
- The replica bucket and the replication rule configuration are then available for modification if needed.
451
+
452
+
#### How can I access the option in the OVHcloud Control Panel?
453
+
454
+
When creating a new bucket/container in a **3-AZ region**, you will be asked if you want to activave or not the Offsite Replication option. If enabled, and because it relies on the asynchronous replication feature, the versioning will be automatically enabled too.
#### What are the differences between the asynchronous replication feature and the Offsite Replication feature available in 3-AZ regions?
459
+
460
+
The Offsite Replication option offered in 3-AZ regions is based on the asynchronous replication feature. With this Offsite Replication option, OVHcloud automatically generates a replication rule configuration with pre-filled parameters, whereas the S3-compatible asynchronous replication functionality allows the user to take control of the entire function(configuration and deployment).
461
+
462
+
#### What if a replica bucket is deleted?
463
+
464
+
The source objects that are to be replicated will have a replication status `FAILED` when Object Storage tries to replicate them but you will not get any errors.
465
+
466
+
#### What about the initial replication rule?
467
+
468
+
The initial rule will remain unchanged and active until you modify or disable it.
469
+
470
+
#### What if a source bucket with offsite replication enabled is deleted? And what about the initial replication rule?
471
+
472
+
Your replica bucket still exists but no more objects are replicated to it from your original source bucket. The initial replication rule is set up on the source bucket and thus will also be deleted.
473
+
474
+
#### Where will be stored the replicated data as the replication rule configuration is managed by OVHcloud?
475
+
476
+
Your replicated data is stored as any other data and will be stored in a bucket automatically generated by OVHcloud in a region of our choosing. The system will automatically determine the most suitable location between Strasbourg, Gravelines, and Roubaix, ensuring efficient and reliable offsite data protection.
477
+
478
+
#### Can I modify the replication rule configuration?
479
+
480
+
We recommend that you do not modify the auto-generated replication rule configuration to ensure optimal operation. However, as it is a standard asynchronous replication rule configuration, you can decide to enrich/upgrade it foradvanced protection by following the steps highlightedin the sections above.
481
+
482
+
#### What is the name of the replica bucket?
483
+
484
+
The destination bucket name follows the pattern `backup-{src-region}-{dst-region}-{timestamp_in_ms}-{src-bucket}`.
485
+
486
+
#### How can I access my backed up data and which actions are possible with the replica bucket?
487
+
488
+
You can list/head/delete objects on this replica bucket. Data stored on the replica bucket are using the Infrequent Access storage class to help you optimizing your storage costs. As it is used for data protection reasons and supposed to be rarely accessed, this storage class is adapted and designed for such use cases. The replica bucket is exclusively dedicated to the Offiste Replication option. You can also read those objects, however a retrieval fee is applied for the Infrequent Access target storage class. View pricing on [this page](/links/public-cloud/prices).
489
+
490
+
#### Which users/credentials can be used to access the destination bucket?
491
+
492
+
When you activate the Offsite Replication during the source bucket creation, the same user that you associated with your source bucket will be associated with the replica bucket.
493
+
494
+
#### How will my backup data be billed?
495
+
496
+
You can access the details of the Offiste Replication pricing on the global Object Storage [pricing page](/links/public-cloud/prices). It is billed according to the storage space used, with a granularity of 1 GiB. To ensure readability, the price is displayed per GiB/month, but the billing granularity is per GiB/hour.
497
+
442
498
## Go further
443
499
444
500
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
@@ -146,6 +147,7 @@ The basic structure of a replication rule within the configuration JSON file is
146
147
| Destination | A container for information about the replication destination and its configurations. | Yes |
147
148
| DeleteMarkerReplication | Tells if delete operations should be replicated. | Yes |
148
149
| Bucket | The destination bucket (to replicate to multiple destinations, you must create multiple replication rules). | Yes |
150
+
| StorageClass | The destination storage class. By default, OVHcloud Object Storage uses the storage class of the source object to create the object replica.<br><br> Please note that **not all storage classes are available in all regions** i.e some storage classes are not supported in some regions such as EXPRESS_ONEZONE which is not supported in 3AZ regions. To learn more about the available storage classes in each region check [our documentation](/pages/storage_and_backup/object_storage/s3_location). | Yes |
149
151
| And | You can apply multiple selection criteria in the filter. | No |
With Object Storage in a 3-AZ region, we have introduced a new option called **Offsite Replication**, which simplifies the replication process and automatically replicates your data to a remote site forgreater resiliency with a one-click actionin the OVHcloud Control Panel.
446
+
This feature is only available forprimary Object Storagein a 3-AZ region (to know more about existing 1-AZ and 3-AZ regions, see [Endpoints and Object Storage geoavailability](/pages/storage_and_backup/object_storage/s3_location)) and is based on an OVHcloud auto-generated and managed replication rule configuration:
447
+
448
+
- Data is replicated on a remote 1-AZ region. The system will automatically determine the most suitable location among Strasbourg, Gravelines, and Roubaix, ensuring efficient and reliable offsite data protection.
449
+
- Objects stored in the replica bucket are stored in an **Infrequent Access** class and are billed differently. View pricing on [this page](/links/public-cloud/prices). This class is designed for less frequently accessed data and allow you to reduce your overall Object Storage bill together with Standard-class performance level. This said, if the destination bucket storage class doesn’t suit your needs, you can choose another approach and use the asynchronous replication feature and manage the replication rule configuration by yourself.
450
+
- The replica bucket and the replication rule configuration are then available for modification if needed.
451
+
452
+
#### How can I access the option in the OVHcloud Control Panel?
453
+
454
+
When creating a new bucket/container in a **3-AZ region**, you will be asked if you want to activave or not the Offsite Replication option. If enabled, and because it relies on the asynchronous replication feature, the versioning will be automatically enabled too.
#### What are the differences between the asynchronous replication feature and the Offsite Replication feature available in 3-AZ regions?
459
+
460
+
The Offsite Replication option offered in 3-AZ regions is based on the asynchronous replication feature. With this Offsite Replication option, OVHcloud automatically generates a replication rule configuration with pre-filled parameters, whereas the S3-compatible asynchronous replication functionality allows the user to take control of the entire function(configuration and deployment).
461
+
462
+
#### What if a replica bucket is deleted?
463
+
464
+
The source objects that are to be replicated will have a replication status `FAILED` when Object Storage tries to replicate them but you will not get any errors.
465
+
466
+
#### What about the initial replication rule?
467
+
468
+
The initial rule will remain unchanged and active until you modify or disable it.
469
+
470
+
#### What if a source bucket with offsite replication enabled is deleted? And what about the initial replication rule?
471
+
472
+
Your replica bucket still exists but no more objects are replicated to it from your original source bucket. The initial replication rule is set up on the source bucket and thus will also be deleted.
473
+
474
+
#### Where will be stored the replicated data as the replication rule configuration is managed by OVHcloud?
475
+
476
+
Your replicated data is stored as any other data and will be stored in a bucket automatically generated by OVHcloud in a region of our choosing. The system will automatically determine the most suitable location between Strasbourg, Gravelines, and Roubaix, ensuring efficient and reliable offsite data protection.
477
+
478
+
#### Can I modify the replication rule configuration?
479
+
480
+
We recommend that you do not modify the auto-generated replication rule configuration to ensure optimal operation. However, as it is a standard asynchronous replication rule configuration, you can decide to enrich/upgrade it foradvanced protection by following the steps highlightedin the sections above.
481
+
482
+
#### What is the name of the replica bucket?
483
+
484
+
The destination bucket name follows the pattern `backup-{src-region}-{dst-region}-{timestamp_in_ms}-{src-bucket}`.
485
+
486
+
#### How can I access my backed up data and which actions are possible with the replica bucket?
487
+
488
+
You can list/head/delete objects on this replica bucket. Data stored on the replica bucket are using the Infrequent Access storage class to help you optimizing your storage costs. As it is used for data protection reasons and supposed to be rarely accessed, this storage class is adapted and designed for such use cases. The replica bucket is exclusively dedicated to the Offiste Replication option. You can also read those objects, however a retrieval fee is applied for the Infrequent Access target storage class. View pricing on [this page](/links/public-cloud/prices).
489
+
490
+
#### Which users/credentials can be used to access the destination bucket?
491
+
492
+
When you activate the Offsite Replication during the source bucket creation, the same user that you associated with your source bucket will be associated with the replica bucket.
493
+
494
+
#### How will my backup data be billed?
495
+
496
+
You can access the details of the Offiste Replication pricing on the global Object Storage [pricing page](/links/public-cloud/prices). It is billed according to the storage space used, with a granularity of 1 GiB. To ensure readability, the price is displayed per GiB/month, but the billing granularity is per GiB/hour.
497
+
442
498
## Go further
443
499
444
500
If you need training or technical assistance to implement our solutions, contact your sales representative or click on [this link](/links/professional-services) to get a quote and ask our Professional Services experts for a custom analysis of your project.
0 commit comments