V1.5.5
V1.12.0
Enhanced pre-backup disk space check requirements to avoid disk space exhaustion caused by backups.
Adjusted O&M projects' backup and restoration requirements, and allowed restoring from backups made within 24 hours.
V1.16.0
Supported the backup management of FineDataLink applications.
V2.7.0
Simplified the backup content by cancelling backing up the following folders to avoid taking too much time:
1. Cancelled the backup of standalone FineReport templates of previous versions: /assets/vcs.
2. Cancelled the backup of standalone FineDataLink snapshots of previous versions: /dpworks/records.
3. Cancelled the backup of the cluster's Excel source files: /assets/temp_attach.
4. Cancelled the backup of FineDataLink cluster's snapshots of previous versions: /dpworks/records.
Stopped backing up the data storage component content for FineBI 6.1 projects. Backed up only the configuration of the data storage component.
1. Added a Project Backup Anomaly alert to support automatic alert reminder upon backup failure.
2. Added backup integrity check logic to prevent invalid backup files.
1. Added a Minimum Unit Backup solution that regularly and forcibly backed up necessary content as a final safeguard for data security.
2. Supported backup of configuration files for self-provided configuration databases, further improving data security.
FineReport, FineBI, and FineDataLink applications have built-in backup and restoration functions, but limitations exist:
1. Application backup files can only be stored in the project directory and do not support off-site backups. If the project is accidentally deleted, the backup may also be deleted.
2. As the number of templates and data within the application increases, the backup speed decreases.
3. During application backups, JAR packages, templates, and configurations are backed up separately, but these contents need to be backed up uniformly according to time points in most cases.
When backing up containerized projects, the self-prepared components will not be backed up and cannot be restored.
You are advised to manually back up these self-provided components when backing up the project, and restore them simultaneously during restoration.
FineOps provides a Backup Management function.
You can choose one-click backup or automatic backup.
You can back up projects to the FineOps server for off-site backup.
You can manage backups and view backup failure records and other information on the page.
When backing up FineOps-deployed projects, you may need to back up relevant images. Therefore, you must ensure the platform is properly connected to the image repository.
If the platform is not configured with an image repository, the backup function cannot be used, and a prompt will appear: "Use this function after configuring the image repository."
Since backups consume server memory, you need to limit the number of backups and the disk space they consume.
Log in to FineOps as the admin, set the limits under Setting > Backup Setting, and click Save.
These settings apply to all projects within FineOps.
Setting Content
Description
Backup Limit
You can limit the maximum number of backups for each O&M project.
When the number of manual or automatic backup files for a project reaches the upper limit, the earliest backup file will be automatically deleted. You can keep three manual and three automatic backups by default.
Disk Limit
You can limit the remaining available disk space for the backup storage directory in FineOps.
The backups are normally stored in /ops/resources/backup of FineOps's mounting directory.
If no backups exist, the first backup will not proceed if the remaining available space in the backup storage directory is less than (2 * Set value).
If backups already exist, the new backup will not proceed if the remaining available space in the backup storage directory is less than (2 * Latest backup size + Set value).
The default value is 5 GB.
FineOps-Deployed Project
1. Backup Scope
The coverage of project backup depends on the component source:
V2.34.0 and later: The configuration files in the project configuration database are backed up. Other content is not backed up.
V2.33.0 and earlier: The following content is not backed up at all.
2. Backup Content
bi-web/bi6/fr/fdl (Project application)
bi6/fr/fdl (Project application;
Files related to dashboards in FineBI of old versions
(If the directory does not exist, it is not backed up.)
Configuration files related to FineDataLink tasks
Non-FineOps-Deployed Project
Only project-related files are backed up. External configuration databases, log storage components, and other components are not backed up.
You are advised to manually back up these necessary components when backing up the project, and restore them at the same time during restoration.
bi/fr/fdl (Application node)
Two backup methods:
Manual backup: You (the admin) can manually trigger project backups.
Automatic backup: You can set the automatic backup time. FineOps will automatically back up the project at specified time points.
Log in to FineOps as the admin, click a project, and choose Maintenance > Backup Management.
1. Select the backup content.
Project Type
Selection
Backup Content
FineOps-deployed Projects
Image Backup unticked
All content listed in the "FineOps-Deployed Project" section is backed up.
Image Backup ticked
1. The image files of the current versions of project components are backed up.2. All content listed in the "FineOps-Deployed Project" section is backed up.
Non-FineOps-Deployed Projects
JAR Package Backup unticked
All content listed in the "Non-FineOps-Deployed Project" section is backed up.
JAR Package Backup ticked
1. The JAR package files of the current version used by the project are backed up.2. All content listed in the "Non-FineOps-Deployed Project" section is backed up.
2. Start the backup.
Click Start Backup, name the backup file, and click OK.
After starting the backup, you can switch to other pages, as the backup process can run in the background.
1. If the number of manual backups exceeds the upper limit, a prompt will appear: "There are already X manual backups of this project. This backup will overwrite the earliest manual backup. Do you want to continue?"
2. If the remaining available space in the backup storage directory is less than the limit set in section "Setting Backup Limits", the backup will fail.
3. Backup file names must be unique.
Non-FineOps Deployed Projects
Enable Automatic Backup and set Backup Frequency. FineOps will automatically back up the project at the specified time.
The name of the automatically generated backup will be the backup time.
2. If the remaining available space in the backup storage directory is less than the limit set in the "Setting Backup Limits" section, no automatic backup will be executed.
The Minimum Unit Backup solution has been introduced since FineOps V2.34.0 for projects as a final safeguard for data security.
Solution description: If Automatic Backup is enabled, Minimum Unit Backup is disabled. If Automatic Backup is disabled, Minimum Unit Backup is enabled by default and forcibly executed, and it cannot be disabled on the frontend page.
Backup content: It includes configuration files of the project's external configuration database. (This scope applies to both FineOps-deployed and non-FineOps-deployed projects, and both FineOps-deployed and self-provided external configuration databases.)
Backup frequency: The backup is performed once a day. The default execution time is 2:00 a.m.
Backup file: Backups are generated on the FineOps server. The number of retained backups is the same as the value set in the "Setting Backup Limits" section. After a new minimum unit backup is generated, the previous minimum unit backup is automatically deleted.
Backup limit: A size limit applies to the minimum unit backup. If the limit is exceeded, the backup cannot be completed. The configuration files of the project's external configuration database are limited to 4 GB.
Restoration: The minimum unit backup does not support restoration on the frontend page. It is stored only as a final safeguard. To use a minimum unit backup for restoration, contact O&M personnel.
On the backup list page, a green backup icon indicates that minimum unit backup is running normally.
The backup file generated by automatic or manual backup is stored in FineOps's mounting directory/ops/resources/backup. You cannot modify the backup location.
You can use different servers for FineOps and projects to realize off-site backup.
1. The storage location of project backups cannot be modified or customized.
2. For details about locating the mounting directory, see Exporting FineOps Deployment Information.
3. Integrity checks are performed on backup content during backup storage, routine inspection, and restoration. Therefore, do not manually modify backup content. Otherwise, the backup may become invalid.
Details of each backup are displayed in a detail table in Full Backup. The remaining available space in the backup storage directory is displayed in the upper right corner.
Item
Backup Name
Name of the backup file
Backup Type
Backup type (Values include Manual Backup and Automatic Backup.)
Start Time
Time when the backup started (accurate to the second)
End Time
Time when the backup ended (accurate to the second)
Backup Size
Backup file size
Select a backup and click the Delete button to delete it, as shown in the following figure:
Click the icon next to a backup, rename the backup, and click OK to apply the new name.
Click Record of Backup Failure and Restoration to view the detail table of failed backup and restoration records. See the following figure:
A Project Backup Anomaly alert has been added since V2.29.0 to support automatic alert reminder upon backup failure.
For projects deployed in a non-containerized mode, manually generated backups in the backup storage directory of FineOps are named by backup ID, which makes it difficult to correlate backups with the names displayed on the frontend page and makes restoration inconvenient.
For projects deployed in a non-containerized mode, you can hover over a backup to view the directory name and click the icon to copy the name.
滑鼠選中內容，快速回饋問題
滑鼠選中存在疑惑的內容，即可快速回饋問題，我們將會跟進處理。
不再提示
10s後關閉
Submitted successfully
Network busy