Note:For FanRuan projects deployed via FineOps, FineOps provides the Backup Management function, which supports one-click backup, automatic backup, and off-site backup.
The Backup & Restoration function introduced in this document is not suitable for FanRuan projects deployed via FineOps.
You are advised to back up and restore projects in FineOps.One-click backup, automatic backup, and off-site backup are supported.One-click restoration and downtime restoration are supported.
Overview
Version Description
| Version | Functional Change |
|---|---|
4.0.13 | Supported backup and restoration of scheduled tasks. |
Application Scenario
To ensure sound system upgrades and resource security, you need to back up the system resources.
During daily development, you may want scheduled backups of a single scheduled task or all scheduled tasks.
Function Description
You can back up and restore platform configurations, FineDataLink tasks, JAR packages, and plugins. You can also update and upgrade the server project online, as shown in the following figure.
Global Setting
Log in to the FineDataLink system as the super admin, choose System Management > Intelligent O&M > Backup & Restoration, and click the icon, as shown in the following figure.
Note:icon is only visible to the super admin.
The following table describes the setting items.
| Setting Item | Description |
|---|---|
Backup Path | The default path is .../backup. The backup file folder exists only in the webroot folder.If you remove the characters (../) when modifying the backup storage path, the backup file folder will be stored only in the WEB-INF folder. |
Backup Frequency | The default frequency is Every One Week Automatic Backup Once, with the auto backup time set to 2:00 AM. |
Maximum Records | The default maximum number of automatic backup records per module is five. If the maximum number is reached, the system will delete the earliest automatic backup to store the latest backup. |
Backup Capacity | By default, the maximum disk space occupied by automatic backup records per module is 1024 MB. If the disk capacity is full, the system will delete the earliest automatic backup to store the latest backup. |
Note:Content and Location of Backup Files
Backup files are stored in the /webapps/webroot/backup path of the FineDataLink project, and their specific locations are shown in the following table.
| Folder | Backup Content |
|---|---|
config | Platform configuration |
jar | JAR package |
plugins | Plugin |
dpworks | Scheduled task files Note:1. Scheduling configurations are excluded from the backup. If you want to back up and restore scheduled tasks, back up platform configurations at the same time. 2. After the restoration is complete, the existing scheduled tasks on the platform will be merged with the scheduled tasks in the backup, and the same tasks will be overwritten with the tasks in the backup. |
Take Platform Configuration as an example. The backup files are stored in the /webapps/webroot/backup/config path of the FineDataLink project. The folder name is consistent with the backup method, as shown in the following figure. (The manual folder stores manual-backup files while the auto folder stores auto-backup files.)
Platform configuration
Manual Backup
Click Manual Backup, customize the backup name in the pop-up dialog box, and click OK to start the manual backup, as shown in the following figure.
Auto Backup
Customize settings such as Backup Frequency, Maximum Records, and Backup Capacity in Global Setting. For details, see section "Global Setting."
Restoration
Select a backup file in Manual Backup or Auto Backup, click the icon, and click OK. A prompt saying “Restoration is successful. Restart the server for the restoration to take effect.” will be displayed. You can restart the FineDataLink server, as shown in the following figure.
Note:1. After restoration, the restored version disappears, and the current version is automatically backed up.
2. Ensure that the server is shut down normally before you restart the server. You cannot forcefully shut down the server, for example, by directly closing the running window in the Tomcat server.
Deleting Previous Backup
Select backups to be deleted, click Delete, and click OK to delete previous backups. Deletion operations for automatic backups and manual backups are the same, as shown in the following figure.
FDL Task
The steps to backup and restore tasks are the same as the steps to backup and restore platform configurations. For details, see section "Platform Configuration."
Backup
You can back up DP files of scheduled tasks.
Scheduled tasks are backed up as files in the dpworks folder created in the globally set backup folder (defaulted to the backup folder in the /webapps/webroot path).
Manual backup path: backup/dpworks/manual.
Auto backup path: backup/dpworks/auto.
Restoration
You can restore DP files of scheduled tasks.
The system can restore the selected backup task files from the backup directory to .../WEB-INF/dpworks.
After restoration and restart:
Tasks in the backup but not in the current project will be added to the current project.
Tasks in the backup will overwrite the same tasks in the current project.
Tasks in the current project but not in the backup will be retained in the project.
Note:1. Scheduling configurations are excluded from the backup of scheduled task files. If you want to back up and restore scheduled tasks, back up platform configurations at the same time.
2. After the restoration is complete, the existing scheduled tasks on the platform will be merged with the scheduled tasks in the backup, and the same tasks will be overwritten with the tasks in the backup.
JAR package
The steps to backup and restore JAR packages are the same as the steps to backup and restore platform configurations. For details, see section "Platform Configuration."
All the JAR packages in the /webapps/webroot/WEB-INF/lib path will be backed up.
Plugin
The steps to backup and restore plugins are the same as the steps to backup and restore platform configurations. For details, see section "Platform Configuration."
Plugin backup and restoration do not require a restart.
Update and Upgrade
Note:Setting the Message Push
Automatic Update Push is enabled by default, as shown in the following figure.
Update and Upgrade
1. Log in to the server after a new version is released, view and process the pushed messages, as shown in the following figure.
2. Click Update Now to update the platform, as shown in the following figure.
Restarting the FineDataLink Server
After the update is completed, restart the FineDataLink server.
Previous：Resource Migration
