https://408-merge.resticprofile.pages.dev/tags/v0.25.0/index.htmlHugoen-gbhttps://408-merge.resticprofile.pages.dev/schedules/commands/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://408-merge.resticprofile.pages.dev/schedules/commands/index.htmlresticprofile accepts these internal commands: schedule unschedule status These resticprofile commands either operate on the profile selected by --name, on the profiles selected by a group, or on all profiles when the flag --all is passed on the command line. Examples: resticprofile --name profile schedule resticprofile --name group schedule resticprofile schedule --all Please note, schedules are always independent of each other no matter whether they have been created with --all, by group or from a single profile.https://408-merge.resticprofile.pages.dev/schedules/systemd/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://408-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: