NAS backup failed silently for three nights before I realized I had set up all the alarms on my phone

That time my mom's house tripped, the backup tasks on my old DS220j were stuck for three nights straight, and I didn't feel anything at all. On weekends, I logged in to check the log, and the task list had three red lines lying down. The earliest was early Tuesday morning.
That weekend, I paired alerts for three machines (my N100 Feiniu, my mom's DS220J, and my cousin's four-seat Synology) one by one. This article laid out the events, channels, and scripts—just copy them.
First, think carefully about what kind of alarm you want it to call, then start setting up the passage
Many people set alerts in reverse: first figuring out which app to use to push messages, then not knowing which events to subscribe to, and finally their phone ringing eight times a day, all saying "system is running fine." First, list the events, rank them, then select the channel.
My rating is only in three tiers:
| Do you want to immediately know | thechannel I provided | |
|---|---|---|
| Backup task fails | , data pushes to | DingTalk | naked
| drive SMART abnormal, storage pool downgrade | , delayedsecondary damage | Synology automatic email + app push |
| transfer the UPS to the battery | , you need to prepare to shut down | . App push |
| disk level exceeds 85%, | just handle it the same day. | DingTalk pushes |
| Docker container update complete | , just glance | at the email |
| If the system has a new version | ,don't | rush to notify |
One-sentence rule: push your phone when you need to do it, go to your email if you just glance at it, and turn off what you don't need. All the following configurations revolve around this line.
Synology: One notification settings page, most of the process is completed
My mom's DS220j was the first to be built. In DSM, go to the Control Panel, find the "Notification Settings" tab and "Email." Service providers can directly choose QQ or choose custom SMTP to fill in: smtp.qq.com, port 465, SSL encryption.
Here's a pitfall I made on my first try: you can't enter QQ passwords in the password bar. First, go to the QQ Mail web version, go to Settings and Accounts, enable POP3/SMTP services, and send a text message for verification. It will give you a 16-digit authorization code. In DSM, the password field is filled with this authorization code. To save myself, I entered my QQ password, clicked 'Send test email,' and the authentication failed. It took me ten minutes to check back and forth before I realized what was happening.
Set up your email, and on the same page, there's a push service tab. Link your Synology account, install the DS Finder app on your phone, log in to the same account, and when you handle system-level events like hard drive health, storage pool downgrade, or UPS battery transfer, DSM will automatically push it to your phone. It's much faster than email—the lock screen pops up instantly. My cousin's four-disc Synology was remotely equipped with him. Same path, five minutes to finish.
Finally, back to the source of the incident: the mission plan. On each task's editing page, there's a 'Send Email Notification' option. Check the box below, then 'Send only when the task is terminated abnormally'—after a normal run, it's not bothersome, only reported if it crashes. This combination works perfectly. But remember the lesson the DS220j taught me: these checkboxes only mean "deciding to report." The channels in notification settings are actually "reporting with words." Without a mouthful of words, no matter how many decisions you make, you're still silent.
Feiniu: I couldn't find a systematic system at the system layer, so I put the alert on the script
sideMy N100 runs like a flying bull. To be honest, in this version, when I check notifications in the settings, there are only sporadic switches, and I don't have Synology's systematic notification center. Feiniu updates quickly; you might already have it by the time you see this article. Check it out yourself—I can't wait, the alert is done directly in Docker and the scripting layer.
Two cron scripts. The first is to check the disk water level, threshold 85%. This is the storage pool is full. The number of users who have taken a loss on a 4TB drive is exceeded. The second is to monitor hard drive health. Every Sunday morning, run smartctl-H, and if the output isn't PUSHED, it triggers an alarm. How do you read the specific SMART numbers Interpretation That article is very detailed, the script only recognizes the word PESSAID, rough but sufficient.
The two paths your phone can reach instantly: DingTalk Robot and Bark
Emails are slow, QQ Mail normally takes a few seconds to a few minutes, and DS finder only handles Synology. The ones that truly arrived instantly across all platforms, I got two of them.
DingTalk robots. Create a group with only your own (start a group chat and add anyone and then kick them out, or create a group face-to-face). Group settings, intelligent group assistant, add bots, and choose custom settings. In the security settings, select "Custom Keywords" and enter the word "NAS"—note this trap: from now on, all incoming messages must include this word; if not, it will be rejected. After obtaining the webhook address, a curl line can send :
curl -s "https://oapi.dingtalk.com/robot/send?access_token=your token" -H 'content-type: application/json' -d '{"msgtype":"text","text":{"content":"NAS disk water level alert: 87% used"}}'
After the first setup, I tested it and returned {"errcode":310000,"errmsg":"keywords not in content"}. At the time, I thought it was because the NAS couldn't get online, so I checked the firewall for a long time. Later, I realized it was because the message forgot to include the keyword "NAS." On Android phones, DingTalk is enough, and lock screen notifications pop up just as well.
If you're using an iPhone, add Bark. Install Bark in the App Store, open and copy your own Key, and at any time, a line of push: curl https://api.day.app/ your Key/NAS alert/disk level 87%, lock screen instantly arrives, it uses Apple's native push notification, and you don't even need to open the app. It can even build its own server, which is an advanced feature—using the official version is totally enough. I gave Bark the backup cable, DingTalk tube the hard drive and water level, separated the two wires, and when they sound, you know what kind of thing it is.
My current alarm checklist is just copying it directly
All three machines are fully equipped, and now the checklist looks like this:
| How to trigger | the machine | event | channel |
|---|---|---|---|
| My mom's DS220j | backup task failed at 03:40 | .Synology email | task schedule checkbox abnormally terminated |
| My mom's DS220j | Hard drive abnormalities, RAID downgrade | ,DS finder | ,DSM system event automatic |
| My Feiniu N100 | disklevel is 85%. | DingTalk | CRON runs scripts every morning |
| My Feiniu N100 | SMART non-BIASED | DingTalk | cron runs scripts every Sunday |
| My Feiniu N100 | container automatically updates | Watchtower environment variables | |
| Synology with UPS | switches power to battery when power is cut off | DS finder | system events are automatic |
The water level script only has a few lines; just modify the threshold and you can use it
#!/bin/bash
USE=$(df /vol01/1000 | awk 'NR==2{gsub("%",""); print $5}')
[ $USE -ge 85 ] && curl -s "https://oapi.dingtalk.com/robot/send?access_token=yourtoken" -H 'Content-Type: application/json' -d '{"msgtype":"text","text":{" content":"NAS disk water level alarm: '"$USE""%"}}'
Note that the script fixes the "NAS" prefix, which is reserved for the DingTalk keyword. Also, pick one day each month and temporarily set the threshold to 1% to run once a week. Check if your phone rings—the alert chain itself can be broken, SMTP authorization codes expire, DingTalk tokens reset, or CRON not running—all of which might make you think life is peaceful. Letting your phone ring is more reassuring than anything else.
Don't turn the alarm into a wolf
Themost common mistake with this kind of subscription is too many subscribers. There are two types of posts you absolutely must not open:
First, login failure notifications. The SSH post mentioned that during the half month I forwarded port 22, there were thousands of blowout logs. If every failed login had pushed my phone, I would have gone crazy. The correct way to fail login is to automatically block and regularly check reports, not to bomb in real time.
Second, system update reminders. The conclusion of the system update article is that important patches need to be upgraded, but the fact that "there's a new version" itself isn't worth interrupting you with. Just lie in your inbox and wait until you see it.
Here's another double insurance tip: don't have only one channel for critical events. My mom's DS220j uses dual channel for email and DS finder. When I replied that QQ email had SMTP issues, the app push notifications were still alive, but the phone was supposed to ring. Don't put all your eggs in one basket, especially in the field of reporting the police.
At the end, here's the order: first list the event lists and classify them, then configure channels (Synology has a settings page, Feiniu uses scripts), and check notifications for each task one by one, checking the link once a month. After installing this setup, the hard drive will fail, backups will fail, the switch will trip and power out—the phone will know before you do—those three nights of silent loss won't be endured again.
