What is eSurfing Cloud ZOS?

Zettabyte Object Storage (ZOS) is an elastic storage product provided by eSurfing Cloud featuring high reliability and cost effectiveness with a massive storage form for cloud computing, big data, and unstructured data.

It provides cloud storage services for unstructured data (images, audio and video, text and files in other formats) through the S3 protocol and standard service interfaces.

Can I try ZOS for free?

Yes, you can explore ZOS through trial options. However, the pay-as-you-go billing method does not support trial use. If you enable ZOS using pay-as-you-go, regular charges apply. To trial ZOS, you can order a resource package. During the valid trial period of the resource package, your ZOS usage is deducted from the allocated resources within the package. If your usage exceeds the resource package quota, services are not interrupted, but the excess usage is charged at the pay-as-you-go rate. If you do not intend to purchase the commercial use after the trial, proactively delete data and resources. Otherwise, you will be billed based on actual usage.

Self-service trial registration is not supported on the official eSurfing Cloud website. To apply for a trial, contact your customer manager.

What storage types does ZOS provide?

Zettabyte Object Storage (ZOS) provides three storage types that are suitable for diverse data storage needs from frequently accessed to archival, including Standard Storage,

Infrequent Access (IA) Storage, and Archive Storage.

Standard storage provides robust reliability, high availability, and exceptional performance. It is suitable for scenarios that demand frequent access (multiple times per month).

Examples of such scenarios include mobile applications, websites, audio/video content, social networking images, and big data analysis.

IA storage provides robust reliability and cost-effectiveness. It is suitable for scenarios that require infrequent access (approximately once per month), while still ensuring high real-time access speed when necessary. Examples of such scenarios include data backup and monitoring data storage.

Archive storage provides robust reliability at low costs. Data can be accessed after being unfrozen. It is suitable for scenarios where data is accessed very infrequently (approximately once per year). Examples of such scenarios include archival data, medical images, and long-term retention or backups.

What are the differences among Elastic Volume Service (EVS), ZOS, and Scalable File Service (SFS)?

eSurfing Cloud provides EVS, ZOS, and SFS. The following table describes the differences among these data storage services.

Scope	Scalable File Service	Zettabyte Object Storage	EVS
Concept	SFS provides highly scalable file storage, allowing multiple ECS instances to access the same file system concurrently. It features high availability, data persistence, and reliability.	ZOS provides robust features, including high scalability and data persistence. It stores extensive amounts of data of any type. ZOS automatically processes data redundancy, fault recovery, and data distribution.	EVS provides high-performance, low-latency scalable block storage. EVS disks can be mounted to VM instances or physical servers to store data persistently.
Storage Mode	SFS uses file storage. File storage is organized in a hierarchical directory and file architecture. You can access directories and files using the file paths and names.	In ZOS, data is stored as independent objects. Each object consists of both data and the associated metadata. Metadata includes attributes such as the file name, file type, and file size.	EVS uses block storage. In block storage, data is divided into blocks of fixed size (several KBs or MBs) and accessed through a unique block address.
Access Mode	SFS enables data access through network sharing. You can mount a file system to specific ECS instances or container instances and use standard file system interfaces sch as NFS and CIFS to access the file system.	To access data in ZOS, you can use specific bucket addresses through HTTP or HTTPS transmission protocols.	EVS disks are similar to disks in PCs, and they cannot be used independently. They are often mounted to ECS instances or physical servers to become visible in operating systems.
Scenario	Example scenarios include the storage of application configuration files and log files that need to be shared, as well as data sharing and synchronization between different container instances in containerized applications.	Example scenarios include large-scale data storage and analysis such as big data analysis, data lake, data backup and archive, as well as static website hosting storage.	Example scenarios include persistent data storage media for ECS instances or physical servers, and high-performance computing (HPC) for large-scale data processing and distributed computing.
Capacity	SFS provides dynamically scalable capacity, with the ability to scale up to 10 PB.	ZOS offers an unlimited system capacity within its architecture. The capacity often reaches EB or ZB level.	EVS allows on-demand capacity expansion, with a minimum expansion of 1 GB. Individual EVS disks can be expanded from an initial size of 10 GB up to an impressive 32 TB.
Whether data sharing is supported	Yes	Yes	Yes
Whether remote access is supported	Yes	Yes	No

What are regions and availability zones (AZs)?

In cloud computing, regions and AZs are fundamental concepts that define the organizational structure and resource distribution within data centers.

Region: A region represents a geographical area where eSurfing Cloud operates one or more data centers.

Each region is an independent operational unit, with its own network infrastructure, power supplies, and security measures.

When choosing a region for deploying your applications or storing data, it is essential to consider several factors, including your geographical location, requirement for application performance, and regulatory compliance. Service availability, billing policies, and features can vary across different regions.

AZ: An AZ represents one or more separate physical data centers within a region. Each availability zone has independent power supplies, network connectivity, and fault isolation mechanisms, guaranteeing high availability and disaster recovery capabilities.

The availability zone settings are designed to provide data center-level redundancy and fault tolerance capabilities. Distributing applications and data across available zones mitigates the impact of natural disasters on service continuity.

What advantages does ZOS offer compared to SAN or NAS storage?

In SAN storage, LUN or volumes are allocated to applications. These LUNs or volumes represent specific portions of disk space. To access SAN, upper-layer applications use the Fibre

Channel (FC) or iSCSI protocol. SAN storage handles disk management tasks, while additional functionalities are implemented by upper-layer applications.

In NAS storage, a file system or file folder is allocated to upper-layer applications. To access NAS, the applications use the NFS or CIFS protocol. In a file system, maintaining a directory tree is essential.

ZOS is more suitable for web applications. It provides an extensive storage space that can be accessed through URLs. It can store files in various formats. ZOS employs a flat architecture, eliminating the need for intricate file directory maintenance. Without storage space limitations, ZOS offers an unlimited system capacity within its architecture. The capacity often reaches EB or ZB level.

What types of data can ZOS store?

ZOS can store unstructured data in various formats. Example:

Image files: ZOS can store image files, such as photos, paintings, and icons, in various formats including JPEG, PNG, and GIF.
Audio files: ZOS can store audio files, such as songs and audio records, in various formats including MP3, WAV, and FLAC.
Video files: ZOS can store video files, such as films, in various formats including MP4, AVI, and MKV.
Text files: ZOS can store text files, such as e-books, reports, and notes, in various formats including TXT, PDF, DOC, and PPT.
Log files: ZOS can store a large number of log files, such as system logs, application logs, and access logs.
Backup and archive data: ZOS offers secure and reliable storage media for backup and long-term archive data, including database backups and enterprise data archives.
Other file types: In addition to the common file types mentioned above, ZOS also stores other types of files, including compressed files and data set files.

Where does ZOS store data?

By default, ZOS stores data in a specific AZ within the specified region. However, if multi-AZ storage is enabled, ZOS employs a data redundancy storage mechanism to store data across multiple AZs within the same region for enhanced redundancy. In the event that one of the AZs becomes unavailable, data can still be accessed from the remaining AZs.

ZOS provides high availability and disaster recovery capabilities through multi-AZ storage. By storing data across multiple AZs, ZOS reduces the impact of a single faulty AZ, ensuring both data security and reliability.

How much data can ZOS store? Is there a limit to the amount of data ZOS can handle?

The total storage capacity of ZOS, including the capacity of individual buckets, is not limited.

This means that you can store as much data as you need within ZOS.

However, for the purpose of enhancing system stability and maintaining resource balance, each user is initially allocated a quota of 100 buckets within a single resource pool. To request an increase in this quota, submit a ticket. The maximum quota is 1000 buckets.

In addition, the size of individual files uploaded through the console is limited to less than 5 GB. If you intend to upload a file larger than 5 GB, consider using the SDK, API, ZOSBrowser, or S3Browser.

Is ZOS secure?

ZOS provides various measures to ensure data security:

Encrypted data transmission: ZOS employs secure data transmission protocols such as HTTPS to encrypt data during network transmission, preventing data from being eavesdropped or tampered with.
Server-end encrypted storage: ZOS encrypts data during storage, ensuring that data remains secure within storage media.
Access control by setting permissions:

You can set permissions for buckets to control access to data within those buckets. You can configure buckets to be public or private, or you can implement more fine-grained access control as needed.
Hotlink protection: ZOS supports hotlink protection, which allows only requests from specific sources to access data in buckets. This prevents hotlinking and unauthorized access.
Cross-domain access: ZOS enables you to configure cross-domain resource sharing policies, allowing you to control the sources of cross-domain access requests and enhance data security.

ZOS is inherently secure.

Moreover, it offers a range of security features and access control mechanisms to safeguard your data during both transmission and storage. However, to ensure absolute data security, it is essential to configure security policies and permissions that align with your specific service requirements.

How to understand the concept of file folder or directory in ZOS?

File folders or directories are not directly used in ZOS. However, to align with user habits, ZOS simulates a traditional file management directory architecture, allowing file folders or directories to be displayed in the console. Actually, creating a directory involves creating an object with a key value of project/ and empty content.

Are file folders in ZOS the same as those in a file system?

No.

ZOS does not directly use the concept of files or file folders as found in a traditional file system.

However, to facilitate data management, ZOS provides a simulated file folder structure. In practice, ZOS adds a slash (/) to the name of an object to simulate a file folder display in the console.

Why does the access link to a publicly readable file become invalid?

If the link has a validity period set, it becomes invalid after the specified period. If you want others to access your file only within a certain time frame, you can share the link and set an expiration date.

When the file is publicly readable or writable, you can directly replicate the object URL to ensure continuous access. However, if the file is private and you want others to always have access, you need to first change the file permissions to publicly readable or writable before replicating the object URL.

Does ZOS support statistics?

Yes. ZOS supports statistics and provides data monitoring capabilities. You can query various statistics and trends in the console. For example, you can query information about storage capacity, file quantity, file fragments, the number of requests, and traffic for the entire system or for each bucket.

These statistics offer a comprehensive understanding of buckets and trends. By leveraging these statistics, you can perform capacity planning, optimize performance, and make informed decisions. In addition, the statistics assist in monitoring and managing buckets by detecting exceptions and tracking usage.

What are the naming rules of buckets?

A bucket name must be globally unique.

It cannot be replicated with any other bucket, even those created by other users, within any cluster.
The name of a bucket cannot be modified or renamed after its creation.
The name length must be between 3 and 63 characters, and it can include lower-case letters, digits, hyphens (-), and periods.
Two periods or one period and one hyphen cannot be adjacent in a bucket name. In addition, a name cannot start or end with a period or hyphen.
A bucket name cannot contain an IP address. If a name contains any period, security certificate verification may be required for accessing the bucket or objects within it.

How can I reduce storage costs?

eSurfing Cloud offers the following approaches to reduce your storage costs:

Flexible use of cold storage: Cold storage involves moving infrequently accessed data to lower-cost storage types, such as IA storage or Archive storage. Cold storage is generally accessed relatively slowly and is suitable for storing data that is infrequently read or written. You can move data infrequently accessed to IA storage or Archive storage to reduce storage costs.
Flexible use of lifecycle policies:

Lifecycle policies are employed for the automatic management of data stored in ZOS. By configuring lifecycle policies, you can define rules to automatically switch storage types or delete data. For example, you can define rules to automatically move data from Standard storage to lower-cost IA storage or Archive storage based on the data access frequency or delete data after the data expires. Appropriate lifecycle policies help optimize storage resource usage and reduce storage costs.

Other methods that can potentially reduce storage costs include compressing or deduplicating data to save storage space, assessing and optimizing bucket capacity, and periodically clearing or deleting unnecessary data.

How can I automatically optimize storage costs?

You can configure lifecycle policies that periodically delete unnecessary objects from buckets or switch storage types to optimize storage costs.

When configuring lifecycle policies, you perform the following actions:

Storage type switch: Specify the storage type to which you want to switch in the lifecycle rule. For example, you can switch the storage type for infrequently accessed data to IA storage or Archive storage.
Switch time and condition settings:

Specify the conditions that trigger this switch and define the time when the switch occurs.
Configure file deletion: Specify the conditions under which objects are automatically deleted.

The system automatically switches the storage type or deletes objects based on the specified lifecycle policies, resulting in cost savings. This reduces the need for manual intervention and ensures that storage costs are periodically optimized.

How can I stop ZOS or halt billing?

Stopping ZOS or halting billing manually is not possible once ZOS is activated.

However, you can empty buckets by deleting all data, including file fragments that haven not completed uploading and historical version objects. Once buckets are emptied, no further

charges are incurred. You do not need to deregister the account.

How is the number of API requests calculated?

Any operation in ZOS performed using the console, tools, API, SDK, or other methods calls the ZOS API, and each such call is considered as a request.

Requests are categorized into read operations, write operations, and object deletions. For example, downloading, uploading, and listing objects contribute to the total number of requests.

Does the performance of ZOS buckets get affected by the activities of other users?

No. The performance of ZOS buckets is not affected by the activities of other users. ZOS offers a user-level resource isolation mechanism that effectively segregates resources between different accounts. As a result, performance remains unaffected and unimpeded across accounts.

How can I obtain the endpoint for accessing ZOS?

Each resource pool in ZOS has a unique endpoint. To obtain the endpoint, log in to the ZOS console, click the bucket name to go to the bucket overview page. In the basic information section, you can see the endpoint for accessing the bucket from the intranet or over the Internet.

How can I obtain the Access Key (AK) and Secret Access Key (SK) for accessing ZOS?

If you choose to access ZOS using a client or SDK, you must first obtain the AK and SK for authentication.

To obtain the AK and SK, log in to the ZOS console, click "Access Key Management" in the upper-right corner, and then click "View AK/SK".

What are the application scenarios of ZOS?

Video surveillance storage: ZOS meets the storage needs of both individuals and enterprises, particularly for managing extensive video surveillance files. Use cases include scenarios like city traffic surveillance and home monitoring.

Data backup: ZOS meets the backup and archival requirements for application software, local databases, RDS, and unstructured data. In addition, it offers backup storage capabilities for cloud servers and Elastic Volume Service instances.

Data migration: eSurfing Cloud enables you to migrate data within ZOS across buckets in different regions or migrate data from storage systems of other vendors into ZOS.

Static website hosting: ZOS is well-suited for hosting various types of websites, such as portal websites, video websites, office automation (OA) systems, and Software as a Service (SaaS) applications. To use ZOS for website hosting, upload webpage files and related resources to ZOS buckets.

How can I start using ZOS?

To use ZOS, ensure that you have

registered an account on the official website of eSurfing Cloud and

completed the real name authentication process.
You can activate ZOS by choosing Home

Products > Storage > Object Storage > Object Storage >Open Now. Note that you need to top up your account with at least RMB 100 before activating ZOS.
Then, you can start using ZOS in the console.

Does ZOS support static website hosting? Where can I configure this feature? What are the procedures?

Yes. However, this feature is not publicly available due to regulatory compliance requirements from the Ministry of Industry and Information Technology (MIIT) of China. To use this feature, submit a ticket to apply for permissions.

The procedures of using static website hosting are as follows:

Store static website files: Upload static website files to ZOS. You can complete this task using the web management page, API, or CLI tools. File types include HTML pages, CSS style sheets, JavaScript code, and other resource files.
Create buckets: Create buckets in ZOS.

The buckets serve as containers organizing and managing files. In general, each website is hosted in a unique bucket.
Set access policies and permissions: You must configure access policies and permissions to allow users to access the files over the Internet. In general, ZOS offers the Public Read option, allowing users to download files through a web browser.
Allocate custom domain names: To facilitate user access to websites, you can associate a custom domain name with a ZOS bucket. This is achieved by mapping domain names to ZOS addresses. For example, you can configure a CNAME record to point to the bucket URL.
Configure static website hosting: ZOS provides an option for static website hosting. You can specify a default file (such as index.html), and define error page and redirection rules.
Website access: After completing the preceding procedures, you can use one of the custom domain names to access the corresponding static website. When the access request is sent to the bucket, ZOS resolves it and returns the corresponding file as the website content for the browser to display.

What should I do when I see a message during ZOSBrowser installation saying that the system cannot continue due to a missing mfc140u.dll, and it suggests reinstallation as a solution?

You Window system is missing the mfc140u dynamic library required for ZOSBrowser to run. Click the following link to download and install it. https://cloud.189.cn/web/share?code=yuENBzUB3Ify (access code: 7ltg)