What data for this category looks like
Data for this category is sourced from four core data sets: backup systems, database logs, object storage, and disaster recovery platforms. Regularly generated documents include four types: backup policies, recovery drill reports, disaster recovery switchover plans, and data verification records. Each document type contains fixed fields: backup task ID, recovery time objective (RTO), recovery point objective (RPO), verification result, and execution timestamp. The units for these fields are string, seconds, seconds, boolean, and timestamp, respectively. Data update frequencies fall into three categories: daily, monthly, and quarterly. These frequencies align with three business scenarios: daily inspection, monthly drill, and quarterly compliance verification.
Constraints imposed on scheduled tasks and automation
Since data comes from heterogeneous cross-system data sources, scheduled tasks must support cross-platform data pulling and format standardization. Without this, fields may be missing or formats may be inconsistent, making it impossible to generate summary reports that meet business requirements. Different update frequencies require task scheduling to support flexible cycle configuration. A single cycle cannot cover the three business scenarios of daily inspection, monthly drill, and quarterly compliance verification. The fixed fields of the four document types require summary logic to be categorized by document type. Without this, operation reports cannot meet the viewing needs of operation and maintenance teams, database administrators, and business continuity leaders. The most time-consuming steps—confirming recovery points, executing drill scripts, and verifying data consistency—require scheduled tasks to set reasonable timeout and retry mechanisms. This prevents tasks from blocking indefinitely and consuming system resources. Severe error outcomes require real-time alerts to trigger after task failure. This ensures business continuity leaders can intervene promptly, preventing issues such as data loss or recovery timeout from escalating.
How to configure settings
| Configuration Item | Recommended Setting | Rationale |
|---|---|---|
| Task scheduling cycle | Daily tasks set to 23:00, monthly tasks set to 02:00 on the 1st of each month, quarterly tasks set to 01:00 on the 1st of the first month of each quarter | Matches the business update frequencies of backup inspection, monthly drill, and quarterly compliance verification |
| Data source pull timeout | 300 seconds | Covers the average pull time across three data sources: backup systems, databases, and object storage |
| Failure retry count | 2 times | Filters occasional network anomalies, avoiding repeated execution that disrupts normal business operations |
| Operation report generation timing | Within 10 minutes after a disaster recovery drill completes | Ensures drill results are summarized promptly to meet the immediate viewing needs of operation and maintenance teams |
| Alert trigger threshold | 2 consecutive execution failures | Avoids invalid alerts triggered by single occasional anomalies |
| Verification result sync interval | 60 seconds | Balances data real-time performance and system resource usage |
Three Common Configuration Errors
- Symptom: After a disaster recovery drill report is generated, automatic copying or downloading fails, with the prompt "Unable to use browser auto-copy, please manually copy the content below". Cause: Cross-origin resource sharing rules are not configured in FastGPT v4.17.0, preventing the frontend from directly pulling report files generated by the backend.
- Symptom: Recovery drill report fields are empty after a scheduled task runs. Cause: Access permissions for the corresponding data source are not configured, making it impossible to pull core data from database logs and backup systems.
- Symptom: Disaster recovery drill summary tasks time out, with the error
ETIMEDOUT. Cause: The data source pull timeout setting is too short, failing to cover the maximum pull time across systems.
How to Confirm Configuration is Complete
- Manually trigger a daily scheduled task, and verify that pulled backup system data and database logs match the original data stored locally.
- Check task scheduling logs to confirm tasks execute at their preset cycles and times, with no delays or skips.
- Simulate a task failure scenario, and confirm that alert notifications trigger according to the configured threshold and are sent to relevant leaders.
- Review generated operation reports, and confirm that document categories and fields comply with the specifications for the four types of business documents: backup policies, recovery drill reports, and others.
The values provided here are common starting points, and should be evaluated against the reader's own samples.
Question material comes from public community discussions. Configuration values are common starting points and should be measured against your own samples. Verified on 2026-10-19.