https://470-merge.resticprofile.pages.dev/tags/v0.29.0/index.htmlHugoen-gbhttps://470-merge.resticprofile.pages.dev/schedules/commands/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://470-merge.resticprofile.pages.dev/schedules/commands/index.htmlresticprofile accepts these commands: schedule unschedule status These commands operate on the profile or group selected by --name, or on all profiles when --all is passed. Warning Before version 0.29.0, the --name flag on a group selected all profiles in the group for scheduling, similar to running the schedule command on each profile individually. Version 0.29.0 introduced group scheduling: The group schedule works at the group level and runs all profiles one by one when triggered.https://470-merge.resticprofile.pages.dev/schedules/systemd/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://470-merge.resticprofile.pages.dev/schedules/systemd/index.htmlsystemd is a common service manager in use by many Linux distributions. resticprofile has the ability to create systemd timer and service files. systemd can be used in place of cron to schedule backups. User systemd units are created under the user’s systemd profile (~/.config/systemd/user). System units are created in /etc/systemd/system systemd calendars resticprofile uses systemd OnCalendar format to schedule events. Testing systemd calendars can be done with the systemd-analyze application. systemd-analyze will display when the next trigger will happen: