Skip to content

Commit 8d6512f

Browse files
committed
Duplication
1 parent 777f2ca commit 8d6512f

File tree

13 files changed

+690
-26
lines changed

13 files changed

+690
-26
lines changed

pages/storage_and_backup/object_storage/s3_faq/guide.de-de.md

Lines changed: 53 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Object Storage - FAQ (EN)
33
excerpt: "Frequently Asked Questions on the Object Storage solution"
4-
updated: 2024-12-11
4+
updated: 2025-02-05
55
---
66

77
## General questions
@@ -56,7 +56,7 @@ Yes, Object Storage is largely compatible with S3 APIs and can be integrated wit
5656

5757
### How is the service billed?
5858

59-
Object Storage is billed according to the storage space used, with a granularity of 1GB. To ensure readability, the price is displayed per GB/month, but the billing granularity is per GB/hour. View pricing on [this page](/links/public-cloud/prices).
59+
Object Storage is billed according to the storage space used, with a granularity of 1GiB. To ensure readability, the price is displayed per GiB/month, but the billing granularity is per GiB/hour. View pricing on [this page](/links/public-cloud/prices).
6060

6161
### Billing example for Object Storage – 1-AZ
6262

@@ -227,6 +227,57 @@ The High Performance class is adapted to AI or analytics use cases, it is built
227227

228228
The maximum bandwidth is 1 Gbps per connection.
229229

230+
## Data Replication
231+
232+
### What is the Offsite Replication option in a 3-AZ deployment mode?
233+
234+
With Object Storage in a 3-AZ region, we have introduced a new option called **Offsite Replication**, which automatically replicates your data to a remote site for greater resiliency with a one-click action in the OVHcloud Control Panel. This feature is only available for primary Object Storage in a 3-AZ region and is based on an OVHcloud auto-generated and managed replication rule configuration:
235+
236+
- 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.
237+
- Objects stored in the replica bucket are billed differently. View pricing on [this page](/links/public-cloud/prices).
238+
- The replica bucket is exclusively dedicated to this action and users can only list objects and/or delete them if needed.
239+
240+
#### What are the differences between the asynchronous replication feature and the Offsite Replication feature available in 3-AZ regions?
241+
242+
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).
243+
244+
#### What if a replica bucket is deleted?
245+
246+
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.
247+
248+
#### What about the initial replication rule?
249+
250+
The intial rule will remain unchanged and active until you disable it.
251+
252+
#### What if a source bucket with offsite replication enabled is deleted? And what about the initial replication rule?
253+
254+
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.
255+
256+
#### Where will be stored the replicated data as the replication rule configuration is managed by OVHcloud?
257+
258+
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.
259+
260+
#### Can I modify the replication rule configuration?
261+
262+
We highly recommend that you do not modify the auto-generated replication rule configuration to ensure optimal operation. However, as it is a standard asyncronous replication rule configuration, you can decide to enrich/upgrade it for advanced protection. Please refer to [the asynchronous replication guide](/pages/storage_and_backup/object_storage/s3_asynchronous_replication) for details about configuration.
263+
264+
#### What is the name of the replica bucket?
265+
266+
The destination bucket name follows the pattern `backup-{src-region}-{dst-region}-{timestamp_in_ms}-{src-bucket}`.
267+
268+
#### How can I access my backed up data and which actions are possible with the replica bucket?
269+
270+
You can list/head/delete objects on this replica bucket. However it is not possible to put/post objects on it. The replica bucket is exclusively dedicated to the Offiste Replication option. Last but not least, getting objects is possible but rate-limited.
271+
In the event of a primary region unavailability/loss for your source bucket, the replica bucket will automatically switch to a read/write mode and becomes available for additional requests to get objects.
272+
273+
#### Which users/credentials can be used to access the destination bucket?
274+
275+
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.
276+
277+
#### How will my backup data be billed?
278+
279+
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.
280+
230281
## Go further
231282

232283
Join our [community of users](/links/community).

pages/storage_and_backup/object_storage/s3_faq/guide.en-asia.md

Lines changed: 53 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Object Storage - FAQ
33
excerpt: "Frequently Asked Questions on the Object Storage solution"
4-
updated: 2024-12-11
4+
updated: 2025-02-05
55
---
66

77
## General questions
@@ -56,7 +56,7 @@ Yes, Object Storage is largely compatible with S3 APIs and can be integrated wit
5656

5757
### How is the service billed?
5858

59-
Object Storage is billed according to the storage space used, with a granularity of 1GB. To ensure readability, the price is displayed per GB/month, but the billing granularity is per GB/hour. View pricing on [this page](/links/public-cloud/prices).
59+
Object Storage is billed according to the storage space used, with a granularity of 1GiB. To ensure readability, the price is displayed per GiB/month, but the billing granularity is per GiB/hour. View pricing on [this page](/links/public-cloud/prices).
6060

6161
### Billing example for Object Storage – 1-AZ
6262

@@ -227,6 +227,57 @@ The High Performance class is adapted to AI or analytics use cases, it is built
227227

228228
The maximum bandwidth is 1 Gbps per connection.
229229

230+
## Data Replication
231+
232+
### What is the Offsite Replication option in a 3-AZ deployment mode?
233+
234+
With Object Storage in a 3-AZ region, we have introduced a new option called **Offsite Replication**, which automatically replicates your data to a remote site for greater resiliency with a one-click action in the OVHcloud Control Panel. This feature is only available for primary Object Storage in a 3-AZ region and is based on an OVHcloud auto-generated and managed replication rule configuration:
235+
236+
- 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.
237+
- Objects stored in the replica bucket are billed differently. View pricing on [this page](/links/public-cloud/prices).
238+
- The replica bucket is exclusively dedicated to this action and users can only list objects and/or delete them if needed.
239+
240+
#### What are the differences between the asynchronous replication feature and the Offsite Replication feature available in 3-AZ regions?
241+
242+
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).
243+
244+
#### What if a replica bucket is deleted?
245+
246+
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.
247+
248+
#### What about the initial replication rule?
249+
250+
The intial rule will remain unchanged and active until you disable it.
251+
252+
#### What if a source bucket with offsite replication enabled is deleted? And what about the initial replication rule?
253+
254+
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.
255+
256+
#### Where will be stored the replicated data as the replication rule configuration is managed by OVHcloud?
257+
258+
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.
259+
260+
#### Can I modify the replication rule configuration?
261+
262+
We highly recommend that you do not modify the auto-generated replication rule configuration to ensure optimal operation. However, as it is a standard asyncronous replication rule configuration, you can decide to enrich/upgrade it for advanced protection. Please refer to [the asynchronous replication guide](/pages/storage_and_backup/object_storage/s3_asynchronous_replication) for details about configuration.
263+
264+
#### What is the name of the replica bucket?
265+
266+
The destination bucket name follows the pattern `backup-{src-region}-{dst-region}-{timestamp_in_ms}-{src-bucket}`.
267+
268+
#### How can I access my backed up data and which actions are possible with the replica bucket?
269+
270+
You can list/head/delete objects on this replica bucket. However it is not possible to put/post objects on it. The replica bucket is exclusively dedicated to the Offiste Replication option. Last but not least, getting objects is possible but rate-limited.
271+
In the event of a primary region unavailability/loss for your source bucket, the replica bucket will automatically switch to a read/write mode and becomes available for additional requests to get objects.
272+
273+
#### Which users/credentials can be used to access the destination bucket?
274+
275+
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.
276+
277+
#### How will my backup data be billed?
278+
279+
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.
280+
230281
## Go further
231282

232283
Join our [community of users](/links/community).

pages/storage_and_backup/object_storage/s3_faq/guide.en-au.md

Lines changed: 53 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Object Storage - FAQ
33
excerpt: "Frequently Asked Questions on the Object Storage solution"
4-
updated: 2024-12-11
4+
updated: 2025-02-05
55
---
66

77
## General questions
@@ -56,7 +56,7 @@ Yes, Object Storage is largely compatible with S3 APIs and can be integrated wit
5656

5757
### How is the service billed?
5858

59-
Object Storage is billed according to the storage space used, with a granularity of 1GB. To ensure readability, the price is displayed per GB/month, but the billing granularity is per GB/hour. View pricing on [this page](/links/public-cloud/prices).
59+
Object Storage is billed according to the storage space used, with a granularity of 1GiB. To ensure readability, the price is displayed per GiB/month, but the billing granularity is per GiB/hour. View pricing on [this page](/links/public-cloud/prices).
6060

6161
### Billing example for Object Storage – 1-AZ
6262

@@ -227,6 +227,57 @@ The High Performance class is adapted to AI or analytics use cases, it is built
227227

228228
The maximum bandwidth is 1 Gbps per connection.
229229

230+
## Data Replication
231+
232+
### What is the Offsite Replication option in a 3-AZ deployment mode?
233+
234+
With Object Storage in a 3-AZ region, we have introduced a new option called **Offsite Replication**, which automatically replicates your data to a remote site for greater resiliency with a one-click action in the OVHcloud Control Panel. This feature is only available for primary Object Storage in a 3-AZ region and is based on an OVHcloud auto-generated and managed replication rule configuration:
235+
236+
- 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.
237+
- Objects stored in the replica bucket are billed differently. View pricing on [this page](/links/public-cloud/prices).
238+
- The replica bucket is exclusively dedicated to this action and users can only list objects and/or delete them if needed.
239+
240+
#### What are the differences between the asynchronous replication feature and the Offsite Replication feature available in 3-AZ regions?
241+
242+
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).
243+
244+
#### What if a replica bucket is deleted?
245+
246+
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.
247+
248+
#### What about the initial replication rule?
249+
250+
The intial rule will remain unchanged and active until you disable it.
251+
252+
#### What if a source bucket with offsite replication enabled is deleted? And what about the initial replication rule?
253+
254+
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.
255+
256+
#### Where will be stored the replicated data as the replication rule configuration is managed by OVHcloud?
257+
258+
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.
259+
260+
#### Can I modify the replication rule configuration?
261+
262+
We highly recommend that you do not modify the auto-generated replication rule configuration to ensure optimal operation. However, as it is a standard asyncronous replication rule configuration, you can decide to enrich/upgrade it for advanced protection. Please refer to [the asynchronous replication guide](/pages/storage_and_backup/object_storage/s3_asynchronous_replication) for details about configuration.
263+
264+
#### What is the name of the replica bucket?
265+
266+
The destination bucket name follows the pattern `backup-{src-region}-{dst-region}-{timestamp_in_ms}-{src-bucket}`.
267+
268+
#### How can I access my backed up data and which actions are possible with the replica bucket?
269+
270+
You can list/head/delete objects on this replica bucket. However it is not possible to put/post objects on it. The replica bucket is exclusively dedicated to the Offiste Replication option. Last but not least, getting objects is possible but rate-limited.
271+
In the event of a primary region unavailability/loss for your source bucket, the replica bucket will automatically switch to a read/write mode and becomes available for additional requests to get objects.
272+
273+
#### Which users/credentials can be used to access the destination bucket?
274+
275+
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.
276+
277+
#### How will my backup data be billed?
278+
279+
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.
280+
230281
## Go further
231282

232283
Join our [community of users](/links/community).

0 commit comments

Comments
 (0)