Preparations
Server data archiving requires the following preparatory work.
A Tencent Cloud Lighthouse server.
a same-region Tencent Cloud LighthouseCOS(LHCOS) bucket.
Feature Overview
Note:
The server data archiving feature relies on TAT (TencentCloud Automation Tools) to periodically run commands. It packages and compresses local server data before uploading it to Lighthouse COS via the tool. Data uploads may fail due to abnormal situations such as server environment changes, tool corruption, TAT unavailability, or virus infections. This feature does not guarantee successful data uploads via SLA. For scenarios like data backup, server intrusion prevention, or ransomware protection, we recommend using the snapshot feature. Users can one-click archive local directories of Lighthouse servers to buckets via the console. Two modes are supported: Immediate Archiving performs instant archiving of server local directories; Scheduled Archiving allows setting hourly, daily, or other intervals to regularly archive local directories to buckets.
Additionally, the server data archiving feature will first pack the local directory and then upload the compressed package to the bucket. By default, Linux systems use the tar.gz format for packing, while Windows systems support packing in zip or 7zip format.
Must-Knows
The server local directory size has limitations. The Linux system does not exceed 20GB; the Windows system supports up to 20GB in 7zip format and 1GB in zip format.
Files with absolute paths (exceeding 200 characters) in the server local directory may cause archive failure.
During archiving execution, reading or writing local files may cause archiving failure or data inconsistency. Therefore, this feature is suitable for archiving static files, not for frequently accessed files.
Supports querying archiving records from the last 30 days.
An account can create up to 1000 scheduled archiving tasks.
Usage Steps
Preparation: Service Role Authorization
1. Go to COS in the console, and select the specified bucket. Go to the bucket details page, and select Server Data Archiving. 2. Before using this feature, you need to authorize the service role COS_QCSLinkedRoleInLighthouseMounting to operate buckets and send TAT commands. If this service role is missing, you will be prompted to authorize it.
3. After the service role authorization is successful, return to the Server Data Archiving page to resume using the feature.
Instant Archiving
1. Go to COS in the console, and select the specified bucket. Go to the bucket details page, and choose Server Data Archiving > Instant Archiving. 2. Click Instant Archiving to immediately perform an archiving task. Enter the following parameters:
Select a server: Only servers in the same region are supported.
Server data directory: Enter the local directory on the server to be archived. For example, enter /home/lighthouse/lhtest for Linux servers; enter C:\\Users\\lhtest for Windows servers.
Bucket storage directory: Enter the bucket storage directory. Note that the path should start with /, for example /aaa.
Compression format: If the server runs Windows, you need to select a compression format. 7zip format is recommended, which supports archiving files up to 20GB, while zip format supports up to 1GB.
3. After an instant archiving task is generated, you can view the archiving records in the console. The records include the following fields:
Archiving Time: Archiving execution time.
Archiving Name: Automatically generated archiving task ID in the format of instant-<instance id>-<timestamp>.
Server Name /ID: Lighthouse instance ID.
Server data directory: Local directory on the server to be archived.
Bucket storage directory: To prevent archiving files from being overwritten, the actual directory automatically appends the archiving name path after the user-specified directory, in the format of <user input storage directory>/<archiving name>.
Compression format: Linux server is tar format, while Windows server is 7zip or zip format.
Command execution status: Task execution status, including Running, Completed, Exception.
Operation: Download files Download archived files to local. View files Navigate to the corresponding file in the bucket file list.
Scheduled Archiving
1. Go to the COS in the console page, and select the specified bucket. Go to the bucket details page, and choose Server Data Archiving > Scheduled Archiving. 2. Click Scheduled Archiving to add a scheduled archiving configuration. Enter the following parameters:
Archiving Name: Enter a custom name. The complete name format is: <custom name>-<instance id>
Select a server: Only servers in the same region are supported.
Bucket storage directory: Enter the bucket storage directory. Note that the path must start with a /, for example, /aaa. To prevent archived files from being overwritten, the actual directory will automatically append the archiving name path after the user-specified directory, in the format of <user-specified storage directory>/<archiving name>.
Server data directory: Enter the local directory on the server to be archived. For example, enter /home/lighthouse/lhtest for Linux servers; enter C:\\Users\\lhtest for Windows servers.
Compression format: If the server runs Windows, you need to select a compression format. 7zip format is recommended, which supports archiving files up to 20GB, while zip format supports up to 1GB.
Archiving Cycle: The following options are supported: 10 minutes, 30 minutes, hourly, every 2 hours, every 6 hours, daily.
Archiving Retention Period: Supports setting retention from 1 to 365 days. Archived files exceeding the retention period will be automatically deleted.
Note:
Once archived files are automatically deleted, the data cannot be recovered. Please proceed with caution.
3. Click OK to create a new scheduled archiving configuration.
4. View archiving records. You can view historical archiving records for the current scheduled archiving plan, with records queryable for up to the last 30 days.
5. Deleting a scheduled archiving configuration. After the configuration is deleted, server files will no longer be archived. However, archived files within the bucket will not be affected and will not be deleted.