Backup Schedules
Configure backup schedules to define when and how often Microsoft 365 data is backed up. OpsPilot365 supports flexible scheduling with workload-specific configurations, maintenance windows, and priority settings for critical data.
Note: All scheduled backups are incremental by default, capturing only new and changed data since the last backup. This minimizes backup duration, reduces API calls to Microsoft 365, and optimizes storage consumption. Full backups are performed automatically during initial protection setup.
Schedule Overview
| Metric | Value |
|---|---|
| Active Schedules | 28 (across all tenants) |
| Next Run | 2:00 AM (in 4 hours) |
| Paused | 2 (temporarily disabled) |
| Running Now | 0 (active backup jobs) |
Schedule Presets
- Standard — Daily backup at 2:00 AM in tenant timezone
- Frequent — Every 4 hours for critical data protection
- Continuous — Hourly backups for maximum RPO protection
- Custom — Define your own schedule with advanced options
Configured Schedules
| Schedule Name | Tenants | Workloads | Frequency | Status |
|---|---|---|---|---|
| Default Daily | 12 tenants | All workloads | Daily at 2:00 AM | Active |
| Critical - 4 Hour | 3 tenants | Exchange, OneDrive | Every 4 hours | Active |
| Healthcare - Hourly | 1 tenant | Exchange | Every hour | Active |
| SharePoint Weekly | 5 tenants | SharePoint | Sunday 3:00 AM | Paused |
Frequency Options
- Hourly — Run every 1, 2, 4, 6, or 12 hours
- Daily — Run once per day at specified time
- Weekly — Run on specific days of the week
- Custom (Cron) — Advanced scheduling with cron expression
Time Settings
- Start Time — Select the time of day for the backup to begin
- Timezone — Tenant Local Time, UTC, US Eastern, US Pacific, or Europe/London
- Backup Window — No limit, 4-hour, 6-hour, or 8-hour window (jobs pause if not complete within window)
Workload-Specific Schedules
| Workload | Recommended | Minimum | Considerations |
|---|---|---|---|
| Exchange | Every 4 hours | Daily | High change rate, critical for business |
| OneDrive | Every 4-6 hours | Daily | User files, ransomware protection |
| SharePoint | Daily | Weekly | Large data volumes, moderate change rate |
| Teams | Daily | Daily | Conversations, channel data |
Maintenance Windows
Blackout Periods
Times when backups will not start (running jobs will continue):
- Business Hours — Mon-Fri 8:00 AM - 6:00 PM
- Maintenance Window — 1st Sunday 2:00 - 6:00 AM
Priority Settings
Control backup order when multiple jobs are scheduled simultaneously:
| Workload | Default Priority |
|---|---|
| Exchange mailboxes | High |
| OneDrive files | Normal |
| SharePoint sites | Normal |
| Teams data | Normal |
On-Demand Backup
Run immediate backup jobs outside of scheduled windows for specific tenants or workloads. On-demand backups run immediately regardless of blackout periods or scheduled maintenance.
Best Practices
- Run backups during off-peak hours to minimize impact
- Stagger large tenant backups to avoid API congestion
- Use higher frequency for critical workloads (Exchange, OneDrive)
- Consider tenant timezone for optimal timing
- Test restore procedures periodically
- Avoid concurrent backups of large tenants
- Monitor throttling from Microsoft APIs
- Use priority settings for critical data
API Reference
POST /api/backup/schedules— Create a new backup scheduleGET /api/backup/schedules— List all configured schedulesPUT /api/backup/schedules/:id— Update a scheduleDELETE /api/backup/schedules/:id— Delete a schedulePOST /api/backup/schedules/:id/run— Trigger on-demand backup