Scenario and solution | Usage notes |
If you have identified the cause of the error that occurs in an abnormal task and fixed the error, you can restart the abnormal task. For example, if a backup error is caused by the shutdown of the source instance, you can restart the backup task after you start the source instance. | If you perform full backup, evaluate the impact of full backup on the source database before you restart the abnormal backup task. We recommend that you restart the abnormal backup task during off-peak hours. If the error is fixed, the state of the abnormal task changes to Completed after you restart the task. In this case, if only one abnormal task exists in your backup schedule, the state of the backup schedule changes to Running. If the backup schedule is still abnormal, check whether other abnormal tasks exist in the backup schedule. If the error is not fixed, the state of the abnormal task changes to Running and then Error or the state of the abnormal task changes to Error after you restart the task. In this case, you must further troubleshoot the cause of the error.
|
If you have identified the cause of the error that occurs in an abnormal task and fixed the error, you can ignore the error. For example, if a backup error is caused by the shutdown of the source instance or service exceptions, and the source instance is started or services become normal, you can ignore the error. The backup will be performed in the next backup window. | If the error is fixed, the state of the abnormal task changes to Completed after you ignore the error. In this case, if only one abnormal task exists in your backup schedule, the state of the backup schedule changes to Running. If the backup schedule is still abnormal, check whether other abnormal tasks exist in the backup schedule. |
If you cannot determine the cause of the error that occurs in an abnormal task or the solution to the error, you can move the pointer over the exclamation point (!) icon to view the error information. Then, search for the error that you want to fix in the Common errors and troubleshooting topic. | If the error is not described in the "Common Errors and Troubleshooting" topic, or your issue persists after you refer to the solutions provided in the topic, join the DingTalk group whose ID is 35585947 and contact technical support. |