Veeam Jobs All Disabled — Site Not Backing Up

Signal

• The last-success fields (veeamServerLocalLastSuccess, veeamWorkstationLocalLastSuccess, the cloud equivalents) stop moving on every job at a site.
• veeamInventory shows the jobs, but none has run recently.
• In the Veeam console, every job shows its schedule disabled.

This is the most dangerous failure on the list: the site is not backing up at all, and nothing fails loudly, because a disabled job doesn't run to fail.

Cause

The upgrade script pauses every job before an install, and restores them when it finishes. If a run is cut off before that restore — killed by the RMM, interrupted by a reboot, or stuck on a service that wouldn't stop — the jobs stay off.

On 2026-09-29, nine BDRs were found this way, with 30 jobs off between them. One had been unprotected for six days.

Fix

Before you start: make sure no upgrade is mid-install on the BDR. If the scheduled task DTC-VeeamUpgrade-1146283-Installer is running, or a Veeam.Silent.Install process exists, wait for it to finish. Re-enabling jobs under a live installer races it.

1. Run the NinjaOne script Repair-VeeamJobState with mode=report. It changes nothing. It prints a JOBSTATE| line per BDR with enabled-versus-total counts, and a JOB| line per job marked WOULD-ENABLE where it would act.
2. Run it again with mode=repair. It re-enables only jobs that ran in the last 30 days, using the correct enable command for each job type: backup, backup copy, or agent policy.
3. Jobs it leaves off had not run in 30 days, so they may have been switched off on purpose. Check with the client's history or the AM before turning those on by hand.

If the service itself won't answer — the script times out after 150 seconds rather than hanging — fix that first: see VeeamBackupSvc Stuck Stopping or Won't Start.

Manual, for one BDR

& pwsh -NoProfile -Command {
  Import-Module Veeam.Backup.PowerShell -DisableNameChecking -WarningAction SilentlyContinue
  Get-VBRJob -WarningAction SilentlyContinue | Select-Object Name, JobType, IsScheduleEnabled | Format-Table -AutoSize
}

Every job you expect to run should read IsScheduleEnabled : True. Re-enable with the command that matches the job type — Enable-VBRJob for backup jobs, Enable-VBRBackupCopyJob for copy jobs, Enable-VBRComputerBackupJob for agent policies. Use pwsh on 13.x; the module needs PowerShell 7.

Verify

• mode=report shows every expected job enabled.
• The next scheduled run of each job starts, and the last-success fields move on the next veeam-inventory run.

Related

• Veeam BDR Script Toolkit
• NinjaOne Veeam Alerts & Custom Fields — Where to Start