Automatic TotalRecall backups use the native Automations system in Total CMS 3. They do not run merely because a schedule is selected in TotalRecall.
REQUIREMENTS FOR AUTOMATIC BACKUPS
Total CMS Pro is required. Automations must be enabled, its cron job must be configured, and the cron job must run regularly. For larger tcms-data directories, the Total CMS command-line automation process is preferable when your hosting supports it.
SET UP THE SCHEDULE
Open Automations in Total CMS and confirm that its cron job is active.
Run or observe an Automation cycle and confirm that it completes.
Open TotalRecall and choose hourly, daily, or weekly backups.
Save the schedule.
Return after the next due time and confirm that a restore point was created.
If a scheduled time is missed, TotalRecall creates the overdue backup on the next successful Automation run. It does not need a separate cron job.
RETENTION
Limit backups by count, age, or total physical storage. The newest backup is always retained. Shared backup objects are removed only when no remaining restore point uses them.
TROUBLESHOOTING
If manual backups work but scheduled backups do not, check Total CMS Automations first. Confirm the cron URL or command, PHP version, permissions, and last successful run. Also verify that the backup repository is writable and has enough free disk space.
After changing the schedule, run a manual backup as a separate safety check. A manual backup proves storage access; a later scheduled restore point proves the Automations cron is working.