Versioning
Can I restore accidentally deleted data?
No. However, you can enable versioning for your bucket so that you can store multiple versions of an object in a bucket, and extract, delete, or restore a specific object version. Versioning allows you to restore data lost due to accidental deletion or application failures. For more information, see Setting Versioning. What is COS's solution to disaster recovery?
You can achieve disaster recovery in COS by:
3. Using the MAZ configuration, which provides IDC-level disaster recovery capabilities for your data. Note:
1. Currently, the MAZ configuration of COS is supported only in Guangzhou, Shanghai, and Beijing regions and will be available in other public cloud regions in the future.
How can I delete noncurrent object versions after I enable versioning for a bucket?
You can set a lifecycle rule and enable Managing historical versions to transition or delete noncurrent object versions. Can a newly uploaded object not overwrite the old one that has the same name?
No. By default, the old object with the same name will be overwritten by the new one. However, you can enable versioning for your bucket so that multiple object versions can be preserved. For more information, see Versioning Overview. How can I download a specific version of object?
If you download with APIs or SDKs, add the versionId request parameter. For the API calling directions, see GET Object. If you download via the console, set the historical versions to Display in the top navigation bar so that you can download the desired object version.
How can I delete noncurrent object versions in batches?
Cross-Region Replication
Does cross-region replication use a private or public network?
By default, cross-region replication uses a private network.
Note:
Note that cross-region replication incurs traffic fees, which cannot be redeemed with a resource pack yet. The fees incurred will be deducted from your account at 00:00 the next day.
Can I sync resources between two regions?
Yes. Resources under the same account can be synced between two regions. You can set cross-bucket replication to replicate objects incrementally. How to quickly migrate resources from one account to another account?
Does cross-bucket replication support replicating existing data?
If I enable cross-bucket replication and delete a file from the source bucket, will the file be deleted as well in the destination bucket?
In a source bucket with cross-bucket replication enabled, COS will replicate the following:
Any new objects uploaded to the source bucket after the cross-bucket replication rule is added.
Object attributes such as object metadata and version ID.
Object operations, such as adding an object of the same name (equivalent to adding a new object) and deleting an object.
Note:
If you specify an object version to delete in the source bucket by specifying a version ID, COS will not replicate this delete operation.
If you add a bucket-level configuration such as a lifecycle rule to the source bucket, COS will not replicate any resulting object operations.
Data Encryption
Does COS support data encryption?
A client-side/COS-managed/KMS key is used to encrypt the file content into ciphertext, which affects performance to some extent (mainly by increasing access delay). The delay does not significantly affect large object reads/writes, but has a certain impact on small object reads/writes.
How can I get an encrypted object?
To get an encrypted object, include an encryption header when reading it. The encryption header differs according to the encryption algorithm. For more information, see Common Request Headers. Content Security
Why are non-compliant files found in my COS bucket?
Your data is stored in COS, and the data access permission is public read. When you access and disseminate such data on the public network, you need to comply with applicable laws and regulations. If the content of such data violates regulations, the compliance team of Tencent Cloud will handle it accordingly, and handled files will be displayed in the Violation List in the COS console.
I have already enabled the content moderation feature, but why do I still receive violation notifications?
Possible reasons:
1. The content moderation feature is not configured correctly; for example:
Automatic freezing is not configured, or the identified non-compliant data is not processed in time (such as deleting files).
The configured data freezing score is too high, so some non-compliant files have low scores and are not frozen.
Some non-compliant images are historical data and have not been moderated. We recommend you conduct a full moderation of historical data to check the entire bucket.
2. If the moderation configuration is correct, but non-compliant data is determined to be normal, this is generally because the data is relatively obscure, and the existing moderation model doesn't correctly moderate it. We will regularly collect similar moderation error samples for continuous optimization. You can also submit a ticket for customized moderation services. Other
Are there backups for the STANDARD, STANDARD_IA, and ARCHIVE storage classes?
COS data is stored at the underlying layer using multiple replicas or erasure coding (both are imperceptible to users). The storage engines are distributed across multiple availability zones in a region, making the data reliability 99.999999999%.