How Can I Change the Storage Type for Files in Zettabyte Object Storage (ZOS)?

You can change the storage type for individual files in the console.

You can also configure lifecycle policies to automatically transition files in a specific bucket or with a certain prefix to a different storage type at a specified time. For example, you can set up policies to move files to Infrequent Access (IA) storage or Archive storage based on predefined criteria. For more information, see Lifecycle Management.

Is There a Limit to the Data Storage Capacity in ZOS?

Limit on the number of buckets: By default, each resource pool can contain up to 100 buckets. To request an increase in this quota, submit a ticket. The maximum quota is 1000 buckets.

Limit on the number of objects within a bucket: A bucket created after September 30, 2023 is allowed to contain up to 400 million objects. Upon reaching this limit, creating new objects may be restricted. For buckets created before September 30, 2023, we recommend maintaining a single-bucket quota of no more than 400 million objects. If you require an increase beyond this limit, please submit a ticket for technical support.

Limit on the size of objects uploaded: The maximum size for individual objects uploaded through the console is 5 GB, while objects uploaded in segments using the API can reach up to 48.8 TB.

Why Are Fragments Generated?

Fragments are generated when objects are uploaded in segments, as a result of upload failures. These fragments facilitate subsequent resumed uploads.

Upload segments: ZOS typically handles large files. However, uploading a large file all at once can encounter issues like network disruptions, connection timeouts, or slow speeds. To address these challenges and enhance user experience, ZOS enables you to break down large files into smaller segments for upload.

Resume uploads: When segment uploads are interrupted, you can resume uploads from the point where they are interrupted, rather than starting from the beginning. ZOS accomplishes this by marking the segments that have already been uploaded and recording relevant information.

Fragment generation: Fragment generation occurs during segment uploads. If any segment fails to upload or is canceled, it is marked as a fragment. These marked fragments contain metadata such as the segment number and upload status. They facilitate resumption of uploads from the point of interruption.

Therefore, fragment generation in ZOS facilitates segment uploads and resumption of interrupted uploads, offering a reliable and efficient method for uploading large files while ensuring data integrity and consistency.

Can I Access ZOS Using HTTPS?

Yes. You can simply enter https:domain name in the address bar of your browser to access ZOS.

HTTPS is an encrypted version of HTTP that relies on the transmission-layer security protocol (TLS/SSL). It utilizes encrypted channels to safeguard data security and integrity during transmission.

To access ZOS, you can enter https:domain name in the address bar of your browser to access ZOS, such as https://example.com.

HTTPS ensures that data is encrypted during transmission, protecting it from theft or tampering. This provides users better data security and privacy protection.

How Do I Obtain the Access URL After Uploading Objects?

If your file is set to Public Read and you want other users to always access it, simply copy the object URL from the console. However, if you only want users to access the file during a specific time period, use the sharing function to obtain a link and set a validity period for that link. If your file is set to Private and you want other users to access it, first change the file to Public Read before sharing the link.

What Can I Do If Accessing Objects Using a URL Fails?

Cause: The objects within a bucket inherit the read/write permissions of the bucket. If the bucket is set to Private, the objects cannot be accessed using a URL.

Solution: Change the read/write permissions of the objects to Public Read and then replicate the URL to access the objects.

Note that changing the read/write permissions of the objects to Public Read enables other users to access the objects using the URL in a browser. However, this operation may pose risks to data security. Exercise caution when performing this operation.

Why Does the Access Link to a File Become Invalid?

Access links with temporary signatures can become invalid due to various reasons:

• Expired signature: When generating a temporary signature link, you can set the validity period of the signature. Once the signature expires, the link becomes invalid.

• Canceled signature: If you wish to revoke access permissions for a signature link, you can cancel the signature. Once the signature is canceled, the link becomes invalid.

• Objects deleted or moved: If the objects are deleted or moved, the signature link to those objects becomes invalid.

If you want links to remain valid without being restricted by signatures, obtain links without signatures using alternative methods. ZOS allows direct URL replication. Replicated URLs are standard links without signatures and remain perpetually valid. Note that perpetually valid links to public objects may pose security risks. Make sure to configure appropriate permissions to prevent unauthorized access or data leakage.

Is Encrypted Uploading of Objects Supported by ZOS?

Yes, ZOS supports encrypted uploading of objects. When server-side encryption is enabled for a bucket, objects uploaded to that bucket are encrypted for storage. Specifically, the uploaded data is encrypted at the server end, and the encrypted data is stored in ZOS as ciphertext.

When you download encrypted objects, they are decrypted at the server end and displayed as plaintext. This process ensures data security during transmission and protects the data from being accessed by unauthorized users.

Exercise caution when handling encryption keys for ZOS objects to ensure data security and reliability.

Can I Upload Segments to ZOS?

Tool	Segment Upload Feature
Management Console	Yes
S3browser	Yes
API	Yes

Can I Resume Segment Uploads to ZOS?

Tool	Resumable Upload Feature
Management Console	No
S3browser	Yes
API	Yes

Can I Upload Files in Batches to ZOS?

Tool	Upload Files in Batches
Management Console	Yes
S3browser	Yes
API	Yes

Can I Download Files in Batches from ZOS?

Tool	Download Files in Batches
Management Console	No
S3browser	Yes
API	Yes

Can I Delete Files in Batches from ZOS?

Tool	Delete Files in Batches
Management Console	Yes
S3browser	Yes
API	Yes

Under What Conditions Do File Uploads Fail?

File uploads may fail under the following conditions:

Network issues: A disconnection to the ZOS server due to specific reasons, can lead to upload interruptions or failures. The reasons include network disconnectivity, firewall settings, and proxy limitations.

Manual intervention: Suspending file uploads manually or disabling the file uploading application can result in upload failures.

Device faults: Device faults, such as disk failures, PC breakdowns, or power supply shortages during uploads, can lead to upload failures.

Other conditions: Unforeseen conditions, such as sudden power cuts or natural disasters, can lead to upload failures and may also damage devices and data.

To prevent upload failures, consider the following measures:

Ensure that the network connectivity is stable and network speed is fast.

When uploading large files, consider implementing resumable segment uploads. This mechanism allows you to resume uploads after any interruptions.

Back up data periodically to prevent data loss due to device faults or other unforeseen conditions.

If you encounter upload failures, verify network connectivity, device status, and operational correctness. Address any issues based on specific conditions. You can also contact technical support of eSurfing Cloud for assistance.

Can I Configure a Trustlist to Grant File Access Using Browser Links?

Yes, you can configure hotlink policies that allow empty referrers. When this setting is enabled, users authorized in the trustlist can access files using links in their browsers.

Hotlink protection restricts file access to specific sources--domain names or IP addresses listed in the trustlist. By default, browsers do not send referer information when opening links. Therefore, after enabling hotlink protection, you cannot directly access files using browser links.

However, if you choose to allow empty referer, browsers can access files even without referer information. With the empty referer option, you can access files using browser links without providing referer information.

to Prevent Hotlinking of Files in ZOS?

You can configure hotlink protection by setting up a trustlist or blocklist to prevent hotlinking of files in ZOS.

Hotlink protection is implemented based on the referer field of HTTP request header. This field indicates the source address of requests. Requests from specific sources can be allowed or denied access to files. Those from sources listed on the blocklist are denied. While those from sources listed on the trustlist are allowed. You can configure hotlink protection rules using the console, API, or SDK. These rules allow or deny requests from certain addresses. After configuring hotlink protection rules, you can verify that only requests from authorized addresses can access the files.

Can Files Be Restored After Being Deleted or Overwritten?

If the versioning feature is not enabled for a bucket, files within the bucket cannot be restored after they are deleted or overwritten. In this case, exercise caution when you delete or overwrite files, and back up important data to prevent accidental data loss.

The versioning feature helps you manage accidental data deletion and other data-related issues. When you enable the versioning feature for a bucket, data within the bucket can be easily restored. This feature allows you to maintain multiple versions of an object and retrieve or restore data as needed. In this case, when a file is deleted or overwritten, it becomes a historical version rather than being permanently deleted. You can restore the file as needed. For more information, see Restore Files.

Does Deleted Data Leave any Residual Traces in ZOS?

When you choose to delete data from ZOS, the system completely erases the data without leaving any residual traces. This eliminates the risk of data leakage.

Can I Share File Folders within a Bucket?

No, but you can share files within a file folder. To share files with other users, follow these steps: click the share button, select the URL validity period (ranging from 1 minute to 12 hours), and then replicate the URL for sharing. When the validity period expires, the URL become invalid. You need to obtain a new URL for sharing.

What Causes Data Loss in ZOS?

First, check whether you have set lifecycle policies that delete data at specific times. If such policies exist, data may be removed as scheduled. Second, check whether you have granted other users write permissions for the bucket. If so, they might have deleted the data. If you have enabled the log storage feature, you can query the logs to identify the user responsible for the deletion.

Can I Control Permissions for Created File Folders?

Currently, you can only completely delete file folders. Permission configuration is not supported at the folder level. However, you can click on the file folder name to enter the folder page and configure permissions for individual files within it.

What Are the Differences Between PUT Uploads and POST Uploads?

In a PUT request, parameter information is placed in the request header for transfer. In a POST request, parameter information is included in the message body as form data.

In a PUT request, the file name must be specified in the URL, whereas in a POST request, the URL corresponds to the bucket domain name, and you do not need to specify the file name.

How Can I Handle Fragments?

Fragments occupy storage space in ZOS and result in unnecessary charges. To manage fragments, follow these steps: click the bucket name to access the bucket details, select the desired fragments, and then delete them individually, in batches, or all at once. Alternatively, you can search for a specific fragment by name and delete it.

What Are Restrictions for Creating Directories (File Folders) in a Bucket?

When creating directories in a bucket, note the following restrictions:

• Do not use emoticons. Use eligible UTF-8 characters instead.

• When creating directories under the current directory, avoid starting or ending with a slash (/) or using consecutive slashes.

• Do not use a backslash ().

• Do not create sub-directories named "..".

• The length ranges from 1 to 254 characters.

• You can create multi-level directories by dividing them with a slash (/). Instead of using emoticons, use eligible UTF-8 characters.

Can I Query Files of a Specific Type in ZOS?

No, you can only query files based on the file name prefix within the bucket or file folder.

To query files based on the file name prefix, follow these steps: navigate to the file management page of the ZOS console, and enter the entire file folder path and file prefix to search for eligible files. For more information, see Search for Files.

Can I Upload Individual Files Exceeding 5 GB? What are the procedures?

Using the console, you can upload up to 100 files, each with a capacity limit of 5 GB, all at once.

If you need to upload a file exceeding 5 GB, consider using the SDK or ZOSBrowser. For more information, see Segmented Uploading of Large Files.

Why Is an Expired URL Still Accessible?

Typically, an expired URL is not accessible.

However, if the URL is already open in the local browser, it remains accessible during the cache validity period. If you no longer need access, consider clearing the browser cache.

What Causes the File Name to Change When I Download a File with a Name Exceeding 255 Characters from ZOS to My Local PC?

In Windows, the maximum length of a file name is 255 characters, including the extension name. Consequently, when the file name you download exceeds this limit, the system automatically truncates it to 255 characters for storage.

Zettabyte Object Storage

Object (File) Frequently Asked Questions