The DC fails to save the auto-backup configuration data on the DSLAM side.
1. Run the command on the DSLAM side to back up the configuration file. The operation succeeds.
2. Back up the DSLAM configuration file manually on the DC. The operation succeeds. But the saved data cannot be found in the corresponding directory. The problem may be traced to the process of data saving.
3. Check the DC configuration and it is found that the DC is configured to save six backup files at most. Hence, when the DC backs up the seventh file, the backup data automatically overwrites the data saved previously. But when the DC succeeds in backing up the seventh file, the backup data fails to overwrite the data saved previously. Check the system time and it is found that the system time on the server lags and is earlier than the date of the data saved previously. Hence, the overwriting operation fails. After the system time is reset, the data is backed up successfully and overwrites the data saved previously. The problem is solved.
The problem can be traced to the following causes:
1. The N2000 BMS is not connected to the DSLAM.
2. The fault occurs on the DSLAM side.
3. The server software is faulty.
During data saving of the DC, when the number of backup files exceeds the preset maximum value, the earliest file is automatically replaced. If the date of the new backup data is earlier than that of the earliest backup data, the operation fails. No new backup file is generated. In this way, the system prompts that the backup is successful, but the backup file fails to be found in the backup directory.