https://319-merge.resticprofile.pages.dev/schedules/index.htmlRecent content in Schedules on resticprofileHugo -- gohugo.ioen-gbhttps://319-merge.resticprofile.pages.dev/schedules/configuration/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://319-merge.resticprofile.pages.dev/schedules/configuration/index.htmlThe schedule configuration consists of a few parameters which can be added on each profile: ​ toml yaml hcl json [profile.backup] schedule = "*:00,30" schedule-permission = "system" schedule-priority = "background" schedule-log = "profile-backup.log" schedule-lock-mode = "default" schedule-lock-wait = "15m30s" profile: backup: schedule: '*:00,30' schedule-permission: system schedule-priority: background schedule-log: profile-backup.log schedule-lock-mode: default schedule-lock-wait: 15m30s "profile" "backup" { "schedule" = "*:00,30" "schedule-permission" = "system" "schedule-priority" = "background" "schedule-log" = "profile-backup.log" "schedule-lock-mode" = "default" "schedule-lock-wait" = "15m30s" } { "profile": { "backup": { "schedule": "*:00,30", "schedule-permission": "system", "schedule-priority": "background", "schedule-log": "profile-backup.https://319-merge.resticprofile.pages.dev/schedules/commands/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://319-merge.resticprofile.pages.dev/schedules/commands/index.htmlresticprofile accepts these internal commands: schedule unschedule status All internal 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. 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://319-merge.resticprofile.pages.dev/schedules/examples/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://319-merge.resticprofile.pages.dev/schedules/examples/index.htmlExamples of scheduling commands under Windows Note If you create a task with user permission under Windows, you will need to enter your password to validate the task. It’s a requirement of the task scheduler. I’m inviting you to review the code to make sure I’m not emailing your password to myself. Seriously you shouldn’t trust anyone. Example of the schedule command under Windows (with git bash): $ resticprofile -c examples/windows.https://319-merge.resticprofile.pages.dev/schedules/systemd/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://319-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.https://319-merge.resticprofile.pages.dev/schedules/launchd/index.htmlMon, 16 May 2022 20:13:32 +0100https://319-merge.resticprofile.pages.dev/schedules/launchd/index.htmllaunchd is the service manager on macOS. resticprofile can schedule a profile via a user agent or a daemon in launchd. User agent A user agent is generated when you set schedule-permission to user. It consists of a plist file in the folder ~/Library/LaunchAgents: A user agent mostly runs with the privileges of the user. But if you backup some specific files, like your contacts or your calendar for example, you will need to give more permissions to resticprofile and restic.