Ag s3 archive

pages/index.md

@@ -771,6 +771,7 @@
                 + [Object Storage - Getting Started with Versioning](storage_and_backup/object_storage/s3_versioning)
                 + [Object Storage - How to connect Object Storage buckets with other resources in a vRack](storage_and_backup/object_storage/connect_other_ressources_in_vrack_private_network)
                 + [Object Storage - How to migrate from OVHcloud Swift Object Storage to OVHcloud S3-compatible Object Storage](storage_and_backup/object_storage/s3_migration_swift_to_s3)
+                + [Object Storage - Restoring an archived object from Cold Archive storage class](storage_and_backup/object_storage/s3_restoring_objects)
             + [Configure Object Storage with your solutions](public-cloud-storage-object-storage-configure-object-storage-with-your-solutions)
                 + [Object Storage - Third-party applications compatibility](storage_and_backup/object_storage/s3_ecosystem)
                 + [Object Storage - Use Object Storage with Rclone](storage_and_backup/object_storage/s3_rclone)

pages/storage_and_backup/object_storage/cold_archive_faq/guide.en-gb.md

@@ -1,9 +1,22 @@
 ---
 title: Cold Archive - FAQ
 excerpt: Frequently Asked Questions on the Cold Archive solution
-updated: 2023-09-12
+updated: 2025-11-18
 ---
 
+> [!warning]
+>
+> **This page is only for existing customers of the OVHcloud standalone bucket-granular Cold Archive introduced in 2023.**
+>
+> **You're looking for S3-compatible archiving solutions?** OVHcloud Object Storage now offers individual objects archiving feature rather than archiving the entire container thanks to the addition of the Cold Archive class in the Object Storage lifecycle. Indeed, the feature is now directly available in your Object Storage dashboard, from your existing Object Storage containers:
+>
+> - upload your objects in the Cold Archive class or,
+> - use lifecycle transitions to move data to Cold Archive class
+>
+> To learn more about this storage class, see [Choosing the right storage class for your needs](/pages/storage_and_backup/object_storage/s3_choosing_the_right_storage_class_for_your_needs).
+>
+> Moreover, the standalone bucket-granular Cold Archive won't be available from the Control Panel for new customers, with no impact to existing customers. APIs will continue to work and data will of course remain available and secure at any moment: we only modify the way users will access and manage objects. 
+
 ## General Information
 
 ### Which use cases are suitable for the Cold Archive storage service? 
@@ -245,4 +258,4 @@ Discover our dedicated Discord channel: <https://discord.gg/ovhcloud>. Ask quest
 
 Join our [community of users](/links/community).
 
-**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.
+**\***: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.

pages/storage_and_backup/object_storage/cold_archive_getting_started/guide.en-gb.md

@@ -1,9 +1,22 @@
 ---
 title: Cold Archive - Getting started with Cold Archive
 excerpt: This guide shows you how to manage your data with Cold Archive
-updated: 2025-08-18
+updated: 2025-11-18
 ---
 
+> [!warning]
+>
+> **This page is only for existing customers of the OVHcloud standalone bucket-granular Cold Archive introduced in 2023.**
+>
+> **You're looking for S3-compatible archiving solutions?** OVHcloud Object Storage now offers individual objects archiving feature rather than archiving the entire container thanks to the addition of the Cold Archive class in the Object Storage lifecycle. Indeed, the feature is now directly available in your Object Storage dashboard, from your existing Object Storage containers:
+>
+> - upload your objects in the Cold Archive class or,
+> - use lifecycle transitions to move data to Cold Archive class
+>
+> To learn more about this storage class, see [Choosing the right storage class for your needs](/pages/storage_and_backup/object_storage/s3_choosing_the_right_storage_class_for_your_needs).
+>
+> Moreover, the standalone bucket-granular Cold Archive won't be available from the Control Panel for new customers, with no impact to existing customers. APIs will continue to work and data will of course remain available and secure at any moment: we only modify the way users will access and manage objects. 
+
 ## Objective
 
 Cold Archive provides long-term data storage by archiving bucket objects onto physical tapes.
@@ -279,4 +292,4 @@ If you need training or technical assistance to implement our solutions, contact
 
 Join our [community of users](/links/community).
 
-<sup>1</sup>: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.
+<sup>1</sup>: S3 is a trademark of Amazon Technologies, Inc. OVHcloud’s service is not sponsored by, endorsed by, or otherwise affiliated with Amazon Technologies, Inc.

pages/storage_and_backup/object_storage/cold_archive_overview/guide.en-gb.md

@@ -1,7 +1,7 @@
 ---
 title: Cold Archive - Overview
 excerpt: Discover the service, understand the capabilities and billing
-updated: 2025-10-20
+updated: 2025-11-18
 ---
 
 <style>
@@ -10,6 +10,20 @@ updated: 2025-10-20
 }
 </style>
 
+> [!warning]
+>
+> **This page is only for existing customers of the OVHcloud standalone bucket-granular Cold Archive introduced in 2023.**
+>
+> **You're looking for S3-compatible archiving solutions?** OVHcloud Object Storage now offers individual objects archiving feature rather than archiving the entire container thanks to the addition of the Cold Archive class in the Object Storage lifecycle. Indeed, the feature is now directly available in your Object Storage dashboard, from your existing Object Storage containers:
+>
+> - upload your objects in the Cold Archive class or,
+> - use lifecycle transitions to move data to Cold Archive class
+>
+> To learn more about this storage class, see [Choosing the right storage class for your needs](/pages/storage_and_backup/object_storage/s3_choosing_the_right_storage_class_for_your_needs).
+>
+> Moreover, the standalone bucket-granular Cold Archive won't be available from the Control Panel for new customers, with no impact to existing customers. APIs will continue to work and data will of course remain available and secure at any moment: we only modify the way users will access and manage objects. 
+
+
 ## Objective
 
 [OVHcloud Cold Archive](/links/public-cloud/cold-archive) is a class of storage designed for long-term storage of rarely accessed data.

pages/storage_and_backup/object_storage/s3_choosing_the_right_storage_class_for_your_needs/guide.en-gb.md

@@ -1,6 +1,6 @@
 ---
 title: Object Storage - Choosing the right storage class for your needs
-updated: 2025-09-18
+updated: 2025-11-18
 ---
 
 Object Storage is a family of storage solutions that offer high-performance, scalable and secure storage spaces.
@@ -31,16 +31,71 @@ The Infrequent Access storage class is designed for infrequently accessed data,
 
 This offer is suitable for the following use cases: long-term storage, backups, disaster recovery.
 
+### Object Storage - Cold Archive class (S3 compatible)
+
+The Cold Archive storage class is an archival storage class. Also existing on its own as [a dedicated product at OVHcloud](/pages/storage_and_backup/object_storage/cold_archive_getting_started), Cold Archive is also available as a class in a general-purpose object storage container. Cold Archive is designed for long-term data storage and data archiving with a very low cost per GiB-hour and per GiB restore fee. Indeed, data in the Cold Archive class are not available in real-time and need to be restored before being available.
+
+
 ### Comparison Table
 
-| Storage Class | Use Cases | Performance (TTFB) | Supported Regions | Availability SLA | Minimum storage duration | Retrieval fee | Granularity |
-| --- | --- | --- | --- | --- | --- | --- | --- |
-| **High Performance** | AI & Analytics, Datalake, High power Computing Multimedia / Content Platform | milliseconds | 1-AZ | 1-AZ regions: 99,9% | No | No | Object-level, lifecycle management support |
-| **Standard** | Media/content storage, datalake, website, backup, logs, application metrics | milliseconds | 1-AZ and 3-AZ | 1-AZ regions: 99,9% - 3-AZ regions: 99,99% | No | No | Object-level, lifecycle management support |
-| **Infrequent Access** | Long-term storage, backups, disaster recovery. | milliseconds | 1-AZ and 3-AZ | 1-AZ regions: 99,9% - 3-AZ regions: 99,99% | 30 days | Yes | Object-level, lifecycle management support |
-| **Cold Archive** | Very long-term storage, backups, disaster recovery. | hours | 4 dedicated DCs | 99,9% | 180 days | Yes | Bucket-level, no lifeycle management support yet|
+<table>
+    <tr>
+        <td><strong>Storage Class<strong></td>
+        <td><strong>Use Cases<strong></td>
+        <td><strong>Performance (TTFB)<strong></td>
+        <td><strong>Supported Regions<strong></td>
+        <td><strong>Availability SLA<strong></td>
+        <td><strong>Minimum storage duration<strong></td>
+        <td><strong>Retrieval fee<strong></td>
+        <td><strong>Granularity<strong></td>
+    </tr>
+    <tr>
+        <td><strong>High Performance<strong></td>
+        <td>AI &amp; Analytics, Datalake, High power Computing Multimedia / Content Platform</td>
+        <td>milliseconds</td>
+        <td>1-AZ</td>
+        <td>1-AZ regions: 99,9%</td>
+        <td>No</td>
+        <td>No</td>
+        <td>Object-level, lifecycle management support</td>
+    </tr>
+    <tr>
+        <td><strong>Standard<strong></td>
+        <td>Media/content storage, datalake, website, backup, logs, application metrics</td>
+        <td>milliseconds</td>
+        <td>1-AZ and 3-AZ</td>
+        <td>1-AZ regions: 99,9% - 3-AZ regions: 99,99%</td>
+        <td>No</td>
+        <td>No</td>
+        <td>Object-level, lifecycle management support</td>
+    </tr>
+    <tr>
+        <td><strong>Infrequent Access<strong></td>
+        <td>Long-term storage, backups, disaster recovery.</td>
+        <td>milliseconds</td>
+        <td>1-AZ and 3-AZ</td>
+        <td>1-AZ regions: 99,9% - 3-AZ regions: 99,99%</td>
+        <td>30 days</td>
+        <td>Yes</td>
+        <td>Object-level, lifecycle management support</td>
+    </tr>
+    <tr>
+        <td><strong>Cold Archive*<strong></td>
+        <td>Very long-term storage, backups, disaster recovery.</td>
+        <td>hours</td>
+        <td>Paris, 3-AZ region</td>
+        <td>99,9%</td>
+        <td>180 days</td>
+        <td>Yes</td>
+        <td>Object-level, lifeycle management support</td>
+    </tr>
+   </table>
 
 More details about available regions [here](/pages/storage_and_backup/object_storage/s3_location).
+> [!primary]
+>
+> Before November 2025, Cold Archive only existed with a bucket-level granularity, as [a dedicated product at OVHcloud](/pages/storage_and_backup/object_storage/cold_archive_getting_started). The product has been updated to allow object-level granularity and Cold Archive is now considered as a class of Object Storage compatible with [**lifecycle management feature**](/pages/storage_and_backup/object_storage/s3_bucket_lifecycle).
+>
 
 ### Additional details
 
@@ -64,6 +119,12 @@ It refers to the ability to **automatically manage the storage lifecycle of your
 
 More details about lifecycle management [here](/pages/storage_and_backup/object_storage/s3_bucket_lifecycle).
 
+#### Cold Archive (Object-level management) class considerations
+
+When using the Cold Archive class in an Object Storage general-purpose bucket, **archived objects are not available in real-time**. The user is asked to first restore the object through a "restore" request and then, after some time (from minutes up to multiple hours), the object is available to download for a duration set by the user when requesting it and is billed upfront at the Standard class rate. However its class will remain as Cold Archive but will be available for GET requests or other actions. In summary, for each object restored, a one time restoration fee per GiB of data plus the storage cost at the Standard rate of the object are billed. 
+
+For official prices, see [Object Storage pricing](https://www.ovhcloud.com/en-gb/public-cloud/prices/#storage).
+
 ## OpenStack SWIFT Object Storage tiers
 
 ### Standard object storage - SWIFT API

pages/storage_and_backup/object_storage/s3_location/guide.en-gb.md

@@ -28,61 +28,69 @@ OVHcloud Object Storage can be accessed through a unique endpoint: `https://s3.<
         <th>Storage tier supported</th>
     </tr>
     <tr>
-        <td rowspan=7><strong>Europe</strong></td>
+        <td rowspan=8><strong>Europe</strong></td>
         <td>Gravelines</td>
         <td>gra</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>Roubaix</td>
         <td>rbx</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>Strasbourg</td>
         <td>sbg</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>Paris</td>
         <td>eu-west-par</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>3-AZ region</td>
-        <td>Standard only</td>
+        <td>Standard, Infrequent Access and Cold Archive</td>
+    </tr>
+    <tr>
+        <td>Milan</td>
+        <td>eu-south-mil</td>
+        <td>HTTPS</td>
+        <td>4</td>
+        <td>3-AZ region</td>
+        <td>Standard, Infrequent Access</td>
     </tr>
     <tr>
         <td>Frankfurt</td>
         <td>de</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>London</td>
         <td>uk</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>Warsaw</td>
         <td>waw</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td rowspan=2><strong>North America<br>(excluding USA)</strong></td>
@@ -91,15 +99,15 @@ OVHcloud Object Storage can be accessed through a unique endpoint: `https://s3.<
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>Toronto</td>
         <td>ca-east-tor</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td rowspan=3><strong>Asia-Pacific</strong></td>
@@ -108,23 +116,23 @@ OVHcloud Object Storage can be accessed through a unique endpoint: `https://s3.<
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>Sydney</td>
         <td>ap-southeast-syd</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
     <tr>
         <td>Mumbai</td>
         <td>ap-south-mum</td>
         <td>HTTPS</td>
         <td>4</td>
         <td>1-AZ region</td>
-        <td>Standard & High Performance</td>
+        <td>High Performance, Standard and Infrequent Access</td>
     </tr>
 </table>
 
@@ -155,7 +163,7 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
     </tr>
     <tr>
         <td>STANDARD_IA</td>
-        <td rowspan=5>Standard Infrequent Access</td>
+        <td rowspan=4>Standard Infrequent Access</td>
     </tr>
     <tr>
         <td>ONEZONE_IA</td>
@@ -168,6 +176,7 @@ The mapping for **WRITE(PUT)** operations on the **io** endpoint is the followin
     </tr>
     <tr>
         <td>DEEP_ARCHIVE</td>
+        <td>Cold Archive</td>
     </tr>
 </table>
 
@@ -192,6 +201,10 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **io** endpoint is the
         <td>STANDARD_IA</td>
         <td>Standard Infrequent Access</td>
     </tr>
+    <tr>
+        <td>DEEP_ARCHIVE</td>
+        <td>Cold Archive</td>
+    </tr>
 </table>
 
 
@@ -234,13 +247,14 @@ The mapping for **WRITE(PUT)** operations on the **perf** endpoint is the follow
     </tr>
     <tr>
         <td>GLACIER_IR</td>
-        <td rowspan=3>Standard Infrequent Access</td>
+        <td rowspan=2>Standard Infrequent Access</td>
     </tr>
     <tr>
         <td>GLACIER</td>
     </tr>
     <tr>
         <td>DEEP_ARCHIVE</td>
+        <td>Cold Archive</td>
     </tr>
 </table>
 
@@ -265,6 +279,10 @@ The mapping for **READ(GET/LIST/HEAD)** operations on the **perf** endpoint is t
         <td>GLACIER_IR</td>
         <td>Standard Infrequent Access</td>
     </tr>
+    <tr>
+        <td>DEEP_ARCHIVE</td>
+        <td>Cold Archive</td>
+    </tr>
 </table>