Safenix checks each server once per minute. The dashboard status identifies the condition that needs attention; the following checks show what to verify on the server.
Backup delayed
Backup delayed means that no backup completed within 90 minutes of the last successful backup. Files and databases are evaluated separately, and the worse status determines the server status.
- Check that the server is powered on and connected, and that the Safenix agent is running.
- Check the agent status with:
sudo systemctl status safenix-agentServer not responding
Server not responding means that the server has not contacted Safenix for 24 hours. This differs from a delayed backup: a server can remain healthy until the agent process stops, after which the only signal is silence.
- Check that the server is powered on and can reach the internet.
- Check the agent:
sudo systemctl status safenix-agent- If the agent is not running, start it:
sudo systemctl start safenix-agentNo complete database copy
No complete database copy means that changes are arriving, but the full copy required as the starting point for a restore is missing. This condition appears one hour after the server is registered, rather than one hour after the last upload, so a copy that keeps failing does not remain hidden.
This is normally caused by permissions or insufficient space in the database. Check the recent database dump messages:
sudo journalctl -u safenix-agent -n 50 | grep -i dumpRestart the agent to retry immediately:
sudo systemctl restart safenix-agentContinuous capture unavailable on the Critical plan
Continuous capture unavailable on Critical plan is not a fault and requires no action. The server is protected with periodic database copies because binary logging is not active. You can leave the condition as it is, move to the Business plan, or cancel the subscription.
The agent refused to start
The agent refused to start means that the local backup and storage do not correspond, usually after a reinstallation. No data was lost and nothing was written. The message on the server explains the two available options.
View the recent agent messages with:
sudo journalctl -u safenix-agent -n 80Email alerts
For each condition, Safenix sends one email when the condition opens and one email when it is resolved. Recipients are configured in the dashboard under Alerts. These alerts are not sent when an account is suspended or closed by Safenix.