--- title: Standard Privatization Package description: Describe the base product capabilities and default delivery scope included in the standard privatization package. slug: private-package-standard lang: en category: Private Plans category_order: 1 order: 2 keywords: - Standard privatization - Enterprise Drive - private deployment --- # Standard privatization package The standard privatization package inherits the core capabilities of the public cloud Babel and runs in the customer's own environment. It is suitable for organizations that need to uniformly manage corporate files, protect data security, access internal systems, and maintain long-term maintainability. ## Standard capabilities - Corporate files, personal files, department folders, project folders and material libraries. - File upload, download, chunked transfer, breakpoint resume, incremental upload and download, and deduplication storage. - File preview, BabelViewer, annotations, comments, version management, version rollback and version comparison. - Department roles, project permissions, file access control, customized file permissions, sharing permissions and log auditing. - Windows, macOS, and Kirin clients, including synchronization, transfer management, and virtual mapping disk capabilities. - Enterprise console, manages organizational structure, members, roles, tags, watermarks, access logs, statistical analysis, etc. ## Privatized Delivery Instructions ## Private deployment The BabelBird public cloud network disk system needs to provide continuous and uninterrupted services to 600,000 users including free users at the same time, block various attacks on the public network, and continuously improve system efficiency to reduce the high cost of public cloud servers. As many as 10 years of experience in uninterrupted public cloud services have made the Babel system time-tested. The Babel private cloud system is developed on the basis of the Babel public cloud system. It inherits all the functions and features of the public cloud Babel, and is updated synchronously with the public cloud Babel, providing you with high stability and high availability that other private network disks cannot match. Deployment plan In response to the different IT system construction needs of different enterprises, the Babel privatization system supports a variety of flexible deployment methods and deployment requirements. Whether it is single server, multi-server, cluster, hyper-converged system, distributed system, third-party cloud platform or even Docker deployment, we support it. Our deployment team can work with you to develop a deployment plan based on your needs. At the same time, because private cloud only serves a single enterprise, we can provide optional customization settings that far exceed those of public cloud systems. From interface operations to processes to permissions, everything can be adjusted according to your needs. Recommended server configuration and performance requirements Server type and function: The hardware system required by BabelBird Enterprise Drive consists of two parts: business servers and storage servers. Business servers can be divided into 4 types. These 4 types of services can be deployed in one physical machine or virtual machine according to needs, or can be deployed dispersedly in four or more servers. Therefore, the minimum unit for deploying the Babel system is two physical servers or two virtual machines (one for business and one for storage) | Service name | Purpose | Operating system | | --- | --- | --- | | Main business server | web services, load balancing, main business function implementation | Linux | | Database Server | Database Service | Linux | | Search server | Provides file full-text search and advanced search functions | Linux | | Transcoding server | Transcode and add watermarks to files that require transcoding preview | windows 2012, Linux | | Storage server | Provides file storage | Linux | In extreme cases, if the hard disk mounted on the server is used as storage space, Babel also supports deploying all services and storage in a physical machine or virtual machine (all-in-one machine mode). However, considering performance and disaster recovery or future upgrade and expansion issues, such a deployment method is not recommended. The best deployment method we recommend is a small cluster deployment of 4 servers (virtual machines). The main business services and database services are placed on one server, the search server and transcoding server are independent, and then a storage server is added. If the storage space requirement is less than 10TB, a storage server is not required. You can directly mount a hard disk or NFS disk for storage. BabelBird also supports access to third-party storage. In theory, as long as the third-party storage system supports the NFS or S3 protocol, it can be connected to BabelBird as a storage service. Most storage systems support both protocols. Each server must ensure smooth communication between each other. If the intranet has higher security requirements, please refer to 9.1.2 Ports that need to be opened Minimum performance configuration: The lowest performance configuration of BabelBird can support normal use by about 100 users and manage less than 10TB of data. | cpu | memory | system disk | storage disk | network | operating system | | --- | --- | --- | --- | --- | --- | | 8-core CPU (reference benchmark E5-2609) | 32G ECC memory | 500G | Below 10TB | Gigabit | Linux | Recommended performance configuration examples: The recommended performance configuration of BabelBird can support normal use by 1000-2000 users and manage documents up to 1PB. Babel supports multiple deployment methods, and this instance is the standard deployment method. Use virtual machines to deploy business servers to connect to independent single or multiple object storage servers. Business servers and storage servers are managed separately. Business server: It is recommended that business servers be deployed using virtual machines | Number | Server type | Configuration requirements | Operating system | Server purpose | | --- | --- | --- | --- | --- | | 1 | Virtual machine | 8-core CPU 64G memory 500G SSD system disk | CentOS8 or openeuler22 | Main business server/database | | 2 | Virtual machine | 8-core CPU 32G memory 500G SSD system disk | CentOS8 or openeuler22 | Search server | | 3 | Virtual machine | 8-core CPU 16G memory 200G SSD system disk | windows 2012 R2 | transcoding server | *The performance of the 8-core CPU should be close to that of the Zhiqiang 4410 BabelBird Enterprise Drive is deployed using Docker. In theory, it can be deployed as long as it is a Linux operating system. CentOS or open Euler is recommended. If there are no ready-made virtual machine resources, you need to purchase a new business server. The business server hardware configuration requirements are as follows: | Number | Server type | Configuration requirements | Operating system | Server purpose | | --- | --- | --- | --- | --- | | 1 | Business server | Xeon Silver 4210*2 20-core CPU 64G memory 2TB SSD hard drive | Linux | Main business server | *It is best to purchase VM for business servers and use virtualization for management. Storage server (object storage): Babel supports building an object storage system on a general-purpose server. If the storage space is expected to be less than 100TB, it is recommended to use a single server to build the object storage system. A single object storage can use disks for data verification redundancy, and can be horizontally expanded by adding one storage server at a time. (The expansion operation can be done without stopping the server) It is recommended to use an independent physical machine for the object storage server, and the recommended configuration is as follows: | Server type | Configuration requirements | Operating system | Server purpose | Notes | | --- | --- | --- | --- | --- | |Storage server | If storage density and future expansion investment are considered, a 12T hard drive can be used. | Linux | Object Storage Server | It is recommended to add a server with the same disk capacity for future expansion. | If the required storage space is greater than 300TB, multiple servers are required to build a distributed object storage system. BabelBird also supports building distributed object storage systems for customers. To learn about distributed object storage, please refer to the "Self-Built Object Storage" chapter. Need to open the port For the security of the server system, we need to open only specific ports. The following are the ports that need to be opened: Ports open to the outside world (ports required for external network access): | Port number | Port purpose | Protocol | Open host | | --- | --- | --- | --- | | 80 | Network disk main business web external access port, not encrypted | http | main business server | | 443 | Network disk main business web external access port, encrypted | https | Main business server | | 3060 | Network disk main business node external access port, not encrypted | TCP | Main business server | | 3080 | Network disk main business node external access port, encryption | TCP | Main business server | Open ports are required between servers (open ports are required for internal server communication): Generally, during actual deployment, only external network ports (external) will be restricted, and internal ports between servers will not be restricted. However, some users who deploy across networks and computer rooms will also need to limit internal ports. | Host | Port number | Port purpose | Protocol | Target network segment | | --- | --- | --- | --- | --- | | Business server | 6379 | redis access port for windows transcoding and search server | TCP | transcoding server and search server | | Business server | 8080 | Used by windows transcoding server to access network disk business server | TCP | Transcoding server and search server | | Business server | 3306 | Database port, used by the search server to access the database | TCP | Transcoding server and search server | | Business server | 9000 | Docker cluster deployment, internal visual interface port | TCP | Transcoding server and search server | | Business server | 111 | portmap port | TCP+UDP | Transcoding server and search server | | Business server | 2049 | TCP+UDP | TCP+UDP | Transcoding server and search server | | Business server | 35000 | mountd port | TCP+UDP | Transcoding server and search server | | Business Server | 2376 | docker REST API port for TLS encryption | TCP | Native | | Business server | 2377 | TCP port used for communication related to docker cluster management | TCP+UDP | Native | | Business server | 7946 | TCP and UDP ports, used for communication between docker swarm nodes | TCP+UDP | Local machine | | Business server | 4789 | docker overlay network default port | TCP+UDP | Local machine | | Search server | 9200 | elastic port, used by the main business server | TCP | business server | | Search server | 5601 | Kibana port, internal visual elastic interface access port | TCP | Business server | | Search server | 9998 | tika port, extract document text server port | TCP | Business server | | Search server | 9000 | Docker cluster deployment, internal visual interface port | TCP | Transcoding server and search server | | Search Server | 2376 | docker REST API port for TLS encryption | TCP | Native | | Search server | 2377 | TCP port used for communication related to docker cluster management | TCP | Native | | Search server | 7946 | TCP and UDP ports, used for communication between docker swarm nodes | TCP+UDP | Local machine | | Search server | 4789 | docker overlay network default port | TCP+UDP | Native | | Transcoding server | Transcoding server | Can access the business server | Can access the business server | Can access the business server | Ports that need to be opened during deployment: | Port number | Port purpose | Open server | Destination IP address | | --- | --- | --- | --- | | 22 | SSH port number, used for SSH access | All servers | Springboard machine for deployment | | 443 | Obtain authorization | All servers | 47.96.234.200 | | 443 | Get installation source | All servers | 120.27.245.68 | | 443 | Docker installation source | All servers | 13.35.121.100 | POC deployment POC deployment is suitable for users to conduct POC testing in the production environment before selection. POC deployment requirements: