Pause and resume

Pausing in Backup is non-destructive – you keep all your existing backup files, your policy config, and your credentials. The schedule simply stops firing until you re-enable it.

There are two levels of pause.

Pause one policy attachment

Stops one specific schedule on one specific data source. Other policies attached to the same data source keep running.

1. Open the data source in app.norcube.com → Backup.
2. In Policies, find the row for the policy you want to pause.
3. Toggle Enabled off.

The change takes effect immediately. Any in-flight job for this attachment finishes; queued ones are canceled.

Pause everything on a data source

Stops every policy attached to one database. Useful when:

• You're decommissioning the database and want to stop accruing backup cost without deleting yet.
• The database is under maintenance and you want to skip backups for a few hours.

1. Open the data source.
2. Toggle the Active switch off (top of the page).

Re-enable when you're ready. The next scheduled time picks up automatically.

Behaviour and edge cases

• Retention still runs while paused. Old backups still age out per the policy's retention rule. If you want to freeze the current backup set as-is, detach the policy entirely instead.
• A paused schedule doesn't "catch up" on resume. If you pause for three days and resume, the missed runs are not run retroactively – the next scheduled time fires normally.
• Pausing isn't billed. No backup jobs, no compute. Storage continues to bill for any backups you've kept.

Related

• Browse backup history
• Data sources