Docs
ufile
Common Tools
US3SYNC Migration Tool
Download and Environment Setup

Download and Environment Setup

US3SYNC provides two deployment options: General Deployment and UHOST Image Startup. Users can choose the appropriate method based on their existing resources. The following describes the general deployment process:

Runtime Environment

  • Linux:
  • CentOS 7.0 and above (check with cat /etc/redhat-release)
  • Ubuntu 16.04 and above (check with cat /etc/issue)

US3SYNC depends on the telnet, expect, and rsync commands. Ensure these commands are pre-installed. If you use the yum package manager, you can install them with the following command:

yum install -y telnet expect rsync

Download and Extract

wget -O US3SYNC.tgz "https://ufile-release.cn-bj.ufileos.com/US3SYNC/v1.10.5/US3SYNC.tgz"
tar xzf US3SYNC.tgz
cd ./US3SYNC

Start the Master Service

./console.sh start
# Set the cache service listening port:
Please set cache service listening port [9000]:
# Set the cache service password:
Please set cache service password [user-passwd]:
# For cloud hosts bound to EIP, use 0.0.0.0 as the IP address
Please set web service listening address [0.0.0.0:443]:
# Internal communication address should not be exposed to the public network. Use the machine's internal IP.
Please set internal communication listening address [x.x.x.x:8080]:
# Set the number of retries for errors:
Please set retry count for errors [10]:
# Set the username for web login:
Please set web login username [root]:
# Set the password for web login:
Please set web login password [passwd]:
US3SYNC start success!
# View the master service status:
./console.sh show
# Stop the master service:
./console.sh stop
# Verification:
# Check if the process is running correctly:
./console.sh show

Add Worker Nodes

  1. After the service starts, open a browser and navigate to: https://<web service listening IP>:<web service listening port>/ Note: When deploying on a cloud host, use the EIP instead of 0.0.0.0.

  2. Log in using the username and password set during the startup process.

  3. Add worker nodes. Refer to the Node Creation Interface Instructions. Each worker node must have a unique working path. If the path does not exist, the system will automatically create the corresponding directory. Note: It is recommended to use the internal IP address.

Tool IntroductionQuick Start