Introduction
	Keeping a VPS healthy is a handful of routine habits: knowing which services are running, reading the logs, watching load, and — above all — backing up. This page covers each, for both FreeBSD 15 and Rocky Linux 10. Patching and the firewall live on the companion Securing Your VPS page.
	Services
	Most of what your server does is run by background services. Check, start, stop, and enable them: # FreeBSD # service apache24 status # is it running? # service apache24 restart # stop then start # sysrc apache24_enable=YES # start automatically at every boot # service -e # list everything enabled at boot # Rocky Linux # systemctl status httpd # status (with recent log lines) # systemctl restart httpd # systemctl enable --now httpd # enable and start in one step # systemctl list-unit-files --state=enabled To see what is listening on which port: sockstat -4 -6 -l on FreeBSD, or ss -tulpn on Rocky Linux.
	Logs
	When something misbehaves, the logs explain why. On FreeBSD, logs are plain text files under /var/log — read them with tail, less, and grep (tail -n 40 /var/log/messages is the catch-all). On Rocky Linux, the system journal collects most logs; query it with journalctl: $ journalctl -u httpd # everything Apache logged $ journalctl -xe # most recent entries, with explanations $ journalctl -f # follow new entries live Both systems rotate logs automatically so they don't fill the disk — newsyslog on FreeBSD, logrotate on Rocky Linux. Your site's web server logs have their own page.
	Monitoring Load
	top shows live CPU and memory use and the busiest processes — the first place to look when the server feels slow. ps aux takes a snapshot of every process; df -h shows free disk space and du -sh * shows what is using it. If a process runs away, end it with kill (or kill -9 as a last resort): $ top $ df -h $ du -sh ~/* # what's using space in your home directory $ kill 12345 # ask process 12345 to stop
	Backups
	The single most important habit. Back up files with tar and databases with a SQL dump, then copy the result off the VPS — a backup that lives only on the same server is no backup at all: # Files $ tar czf site-`date +%F`.tar.gz ~/public_html # Database (see the MariaDB / MySQL pages) $ mariadb-dump myapp > myapp-`date +%F`.sql # Copy somewhere else $ scp site-*.tar.gz backups@elsewhere.example:~/ Schedule all of this from cron. The platforms also offer snapshot tools — ZFS snapshots on FreeBSD (zfs snapshot ...) and LVM snapshots on Rocky Linux — useful for a quick restore point right before a risky change, though not a substitute for off-server copies. TIP: A backup you have never restored is only a hopeful guess. Periodically restore a backup into a scratch directory and confirm the files and a database dump are intact.
	Documentation
	The manual pages cover each tool: top(1), tar(1), service(8) / newsyslog(8) on FreeBSD, and systemctl(1) / journalctl(1) / logrotate(8) on Rocky Linux.