Skip to Content
Browse documentation

Configure a Reseller Backup Schedule

Set RAPP backup scope, format, time, daily weekly and monthly destinations, monthly dates and client upload settings for reseller or user schedules.

Choose Manage Backups → Backup Schedules, then add or edit the appropriate schedule type.

Fields

FieldMeaning and accepted values
Schedule nameRequired descriptive name, 3–50 characters.
Reseller / userYour own reseller for a reseller schedule, or an owned hosting account for a user schedule.
StatusOn or off. An inactive schedule cannot be started with Run backup.
Backup typeCompressed, archived or incremental. Choose the format appropriate to the destination and recovery plan.
Schedule time24-hour HH:MM, from 00:00 to 23:59. Confirm the server's scheduling timezone with the provider.
DailyEnable or disable the daily frequency.
Daily storage poolsAt least one selected destination when daily is enabled.
WeeklyEnable or disable the weekly frequency.
Weekly storage poolsAt least one selected destination when weekly is enabled.
Weekly daySunday through Saturday; required when weekly is enabled.
MonthlyEnable or disable the monthly frequency.
Monthly storage poolsAt least one selected destination when monthly is enabled.
Monthly dayThe supported choices are 1, 15 or 28; required when monthly is enabled.
Client uploadAllows this schedule to upload backups to storage pools configured by users or resellers. Review those destinations and the provider's policy before enabling it.

At least one of daily, weekly or monthly must be enabled. Each enabled frequency needs its own destination selection; selecting daily pools does not satisfy the weekly or monthly requirement.

Procedure

  1. Ensure an active storage pool exists.
  2. Choose the scope and account carefully.
  3. Enter the name, status, backup type and time.
  4. Enable the required frequencies and select their pools and days.
  5. Review client upload, then save.
  6. Reopen the schedule to confirm the saved policy and check actual backup records after execution.

A saved policy needs verification

The current user-schedule creation handler contains an undefined audit-name reference after invoking the save helper. If creation reports a server error, inspect the schedule list before retrying: the configuration may already have been written. Ask the provider to investigate rather than creating duplicate policies.

Do not assume a schedule also defines a retention count: these forms do not expose that field. Editing requires an existing matching schedule and an active pool; demo mode blocks saving.