my TS-212P keeps sending me the following error email:
Notification mail: The synchronization of RTRR job [TV-Ita–>TV-Ita-Backup] stopped with errors.
The synchronization of RTRR job [TV-Ita–>TV-Ita-Backup] stopped with errors. Error message: All folder pairs are invalid or inaccessible. Please check the logs for more detail. Folder Pairs : 1 Total File(s) : 1636 Total Folder(s) : 113 Skipped Files : 1636 Backed-up Files : 0 Total File Size : ------ Average Transmit Speed: 0.00 B/s
This is related to an old RTRR sync job that I had canceled (removed the job from the Hybrid Sync app) that somehow keeps running even though there’s no trace of it anywhere in the HBS app.
What can I do? The directories to be synced don’t even exist anymore (hence the error).
TS-212P has reached end-of-life (EOL). EOL means End-of-life, and EOL means no longer being maintained and supported (include QTS, all apps and all utilities). More info, please visit to https://www.qnap.com/en/product/status
Hybrid Backup Sync version is 2.1.190909 on TS-212P, released around October 31, 2019, is no longer maintained and supported.
It is correct that this model has officially reached its End of Life status.
Nevertheless, to assist you with your current issue, we will still have our support team help you look into the Crontab settings. Thank you for your patience and your continued support of our products!
I really appreciate, although after sending the HBS Diagnostic report as requested I have not heard back from the Support team anymore (and one week has passed)
1.) Stop Hybrid Backup Sync
2.) Reboot the NAS
3.) Restart Hybrid Backup Sync
See if this gets rid of your old sync job. It’s possible that there’s some old processes that are there which automatically restart themselves upon reboot of the NAS if HBS is running. They won’t if HBS is stopped.
Qnap Support wrote me a few days ago saying that the invalid job had been removed from the configuration file, services had been restarted and the problem should have been solved.
Today I didn’t receive the error email. I will never know whether it was thanks to NA9D’s suggestion or to the remote intervention of Qnap’s support, but what’s important is that the problem has been solved.
Thank you everyone for your help, with a special mention for SteveKo for having Qnap’s support look into my issue even though the NAS had reached it’s EOL long ago.