What Can I Do When I Failed to Create a Bucket?

Common reasons for encountering issues while creating a bucket include:

Network connectivity: Check the status of the network connection between your local device and ZOS. Make sure that the network connectivity is normal.

Overdue payments or insufficient balance: Check whether your account has any overdue payments or insufficient balance. If there are overdue payments, top up your account to restore its availability.

Lack of permissions: Check whether your account has the necessary permissions for creating buckets. If not, reach out to the administrator or an eligible user to grant you the required permissions.

Cap on the bucket quantity: If you have already created 100 buckets, you are not able to create additional ones. Consider deleting unnecessary buckets to free up the quota.

If this issue persists, contact the technical support of eSurfing Cloud and provide a detailed description of the problem to receive assistance.

What Can I Do When I Failed to Delete a Bucket?

Common reasons for encountering issues while deleting a bucket include:

The bucket contains files. You cannot delete a bucket that is not empty. To delete a bucket, first remove all the files and objects within the bucket.

The bucket serves as the log storage for other buckets. You cannot directly delete it. To delete such a bucket, first cancel the log storage setting for all the buckets that use this bucket as their log storage.

Exercise caution when performing deletions and ensure that important data is backed up. This will help prevent inadvertent deletions that may lead to data loss.

If this issue persists, contact the technical support of eSurfing Cloud for assistance.

What Are the Relationship Between Bucket Storage Type and File Storage Type?

The bucket storage type applies to the entire bucket, indicating the default storage type for all files within the bucket. You can configure the bucket storage type based on factors such as the frequency of data access, data availability requirements, and associated costs, to tailor it to your specific service needs.

The file storage type applies to individual files, indicating the storage type for a specific file. Files within a bucket can inherit the storage type of the bucket or have independent storage types. You can configure the file storage type based on factors such as the file importance and access frequency.

Can I Change the Region Where a Bucket Resides?

No. Once created, the region where a bucket resides cannot be changed.

You can create a bucket in the desired region and then migrate data to the new bucket using data migration tools or cross-region replication functionality.

What Disaster Recovery Solutions Does ZOS Utilize?

ZOS often uses the following disaster recovery solutions:

Enable versioning: ZOS provides a versioning feature that retains and manages multiple versions of an object. When versioning is enabled, the system automatically creates a new version and retains the historical versions each time you modify or delete an object. This ensures data reliability and integrity, allowing you to restore data in case of inadvertent operations or data loss.

Cross-region replication: This feature enables automatic data replication between different regions. By configuring cross-region replication rules, you can replicate data to other regions or data centers, enhancing data redundancy and availability. In the event of faults, disasters, or network disconnections in a region, you can rely on the backup data to ensure service continuity.

Multi-AZ redundant storage: Data is stored across different AZs. Each AZ represents an area with independent power supply, networking, and hardware. By maintaining data copies in multiple AZs, you can access or restore data from unaffected zones in the event of a single AZ or server failure. This feature enhances disaster recovery capabilities and data availability.

ZOS leverages versioning, cross-region replication, and multi-AZ redundant storage to provide robust disaster recovery capabilities and data protection mechanisms. These features prevent data loss, mitigate the risks of service interruptions, and ensure data restoration and availability in the face of faults, disasters, and other unforeseen factors.

Can I Allow Other Users to Access Data in ZOS?

You have two approaches to grant other users permissions to access data in ZOS:

• Bucket-level access-control list (ACL): ACLs can be configured for a bucket to specify the users authorized to read or write data in the bucket. By configuring ACLs, you can grant access permissions to specific users for data within a bucket.

• Bucket policy: This is a fine-grained method of access control that grants access permissions for bucket data based on defined conditions and rules. By configuring bucket policies, you can grant access permissions to specific users for data within a bucket.

Note that it is essential to adhere to applicable security and privacy regulations. Ensure prudent control over the scope of data access to avoid unauthorized access and potential data leakage.

How Can I Configure Lifecycle Policies?

Prior to configuring lifecycle policies, ensure you are well-acquainted with your data across the following dimensions:

Access mode: Monitor the frequency of data access to determine the optimal juncture for transitioning storage to Infrequent Access (IA) or Archive.

Application scenario and performance requirements: Examine the access frequency, retrieval speed, and associated storage costs to determine the most suitable storage type.

You can manage object lifecycles by combining various operations. For example, objects that are accessed frequently during the initial 30 days are kept in Standard storage; post that period, if access becomes infrequent within 90 days, they transition to Infrequent Access (IA) storage based on predefined policies; and upon ceasing to be accessed, they are relocated to Archive storage in accordance with the specified policies.

How Soon Do Lifecycle Policies Become Effective Following Their Configuration?

Lifecycle policies takes effect at 0:00 Beijing Time (GMT+8) on the day subsequent to their configuration.

If you specify a date or a period post-update for objects to be transferred to IA or Archive storage or automatically deleted, the specified actions commence at 0:00 Beijing Time (GMT+8) on the following day.

How Can I Migrate Data from Third-party Cloud Vendors to ZOS?

The procedures for migrating data from third-party cloud vendors to ZOS are as follows:

Log in to the ZOS console. Choose 对象存储迁移 in the left-side navigation pane.
Click 创建迁移任务 and follow the prompts to configure the necessary parameters.
View the progress and the time required for completion after the migration task is created.
Click the task name to view task details.

For more information, see Migrate Data from Third-party Cloud Vendors to ZOS.

What Are the Billing Considerations When Migrating Data from Other Cloud Vendors to ZOS?

When migrating data from other cloud vendors to ZOS, consider the following billing items:

• Source-end storage traffic fees: When migrating data from other cloud vendors to ZOS, outbound traffic fees are incurred at the source. These fees are determined by the pricing policies of the source storage vendors and are calculated based on the volume of data transferred.

• Storage capacity fees: After data is migrated to ZOS, storage capacity fees apply. These fees are calculated based on the used storage capacity and the selected storage type.

• Request fees: Accessing or operating data within ZOS, including reading, writing, replication, or deletion, incurs fees. These fees are calculated based on the type and quantity of requests.

What Causes Traffic in My Bucket Even When It Contains No Objects?

Possible cause 1: Inbound traffic is accounted for in real-time during file uploads. It is possible that users have uploaded files to the bucket and subsequently deleted them. As a result, while no objects are currently visible in the bucket, inbound traffic would have been recorded.

Possible cause 2: Interruptions during file uploads, due to unknown factors, may result in only partial file segments being uploaded without forming a complete object. Nevertheless, traffic is recorded during the upload of these segments.

What Is the Relationship Between Bucket Name and Endpoint?

The bucket name in ZOS is designated at the creation of the bucket, while the endpoint reflects the regional location of the bucket. They together form the access domain name of the bucket.

The access domain name is in the format of BucketName.Endpoint. BucketName indicates the name of the bucket while Endpoint indicates the regional location of the bucket.

How Can I Determine Whether My Bucket Is Private, Public, or Public Read/Write?

On the ZOS overview page, click the name of your bucket to access its details. Then choose 权限管理 > 读写权限 to view the privacy settings.

You can also click 读写设置 in the infrastructure section at the bottom of the overview page to view the privacy settings.

Can I Create Two Buckets with the Same Name?

No, you cannot create two buckets with the same name.

In ZOS, a bucket name must be globally unique. It cannot be replicated with any other bucket, even those created by other users, within any cluster. When creating a bucket in the console, a verification process is in place. If the chosen bucket name already exist—either under your account or the account of another user—the creation process will not proceed. To resolve this, select a unique bucket name to create your bucket.

In Which Scenarios Should I Use the Lifecycle Management Feature?

The lifecycle management feature applies to the following scenarios:

• Files have a predetermined retention period, such as a week or a month. By setting up lifecycle rules, these files can be automatically deleted after the specified duration, eliminating the need for manual intervention.

• Some files are frequently accessed in a certain period of time, but they are not allowed to be accessed after this period. By setting up lifecycle rules, these files can be automatically relocated to more economical cold storage once that period concludes.

Can I Change the Name of My Bucket?

No. The name of a bucket cannot be changed once created.

You can create a bucket and replicate objects or migrate data to the new bucket.

How Can I Prevent Bucket Data from Being Deleted?

ZOS allows you to set regulatory compliance policies for buckets. Once these policies are in place, data within the buckets cannot be permanently removed by any user until the specified retention period has lapsed. Only after this period can the data be deleted. This protects data that necessitates long-term preservation and should remain unaltered.

Can I Change the Storage Type of an Existing Bucket?

No. Once a bucket is created, its storage type is fixed. However, you can change the storage type of the objects contained within it.

If a different storage type is required, consider creating a new bucket and then replicate the objects or migrate the data to this newly created bucket.

What Can I Do When I Failed to Create a Bucket?

What Can I Do When I Failed to Delete a Bucket?

What Are the Relationship Between Bucket Storage Type and File Storage Type?

Can I Change the Region Where a Bucket Resides?

What Disaster Recovery Solutions Does ZOS Utilize?

Can I Allow Other Users to Access Data in ZOS?

How Can I Configure Lifecycle Policies?

How Soon Do Lifecycle Policies Become Effective Following Their Configuration?

How Can I Migrate Data from Third-party Cloud Vendors to ZOS?

What Are the Billing Considerations When Migrating Data from Other Cloud Vendors to ZOS?

What Causes Traffic in My Bucket Even When It Contains No Objects?

What Is the Relationship Between Bucket Name and Endpoint?

How Can I Determine Whether My Bucket Is Private, Public, or Public Read/Write?

Can I Create Two Buckets with the Same Name?

In Which Scenarios Should I Use the Lifecycle Management Feature?

Can I Change the Name of My Bucket?

How Can I Prevent Bucket Data from Being Deleted?

Can I Change the Storage Type of an Existing Bucket?

Zettabyte Object Storage

Storage Bucket FAQ