Jobs & scheduling
A job ties together what to back up (a FileSet), which machine (a Client), where it goes (a Storage + Pool) and when (a Schedule). NGBackup runs several job types: Backup, Restore, Verify, Copy, Migrate and Admin.
Backup levels
Section titled “Backup levels”| Level | What it copies |
|---|---|
| Full | Everything in the FileSet. |
| Differential | Everything changed since the last Full. |
| Incremental | Everything changed since the last backup of any level. |
A typical policy is a weekly Full + daily Incrementals; NGBackup automatically promotes an Incremental to Full when no prior Full exists.
Run a job
Section titled “Run a job”From the console:
/opt/backup/bin/backup-console* runPick the job, adjust level/storage if needed, and confirm. To run non-interactively:
* run job="BackupClient1" level=Full yesWatch it:
* status director* messagesSchedule it
Section titled “Schedule it”Jobs run automatically via a Schedule resource:
Schedule { Name = "WeeklyCycle" Run = Full sun at 23:05 Run = Incremental mon-sat at 23:05}Every scheduling directive is in the Schedule resource reference. Job behaviour (priority, concurrency, retention, retries…) is controlled by the Job resource directives.
Concurrency & priority
Section titled “Concurrency & priority”Run more jobs at once by raising Maximum Concurrent Jobs on the Director, Client and Storage, and order them with Priority. See the Job and Director references.