Skip to main content
Question

Veeam 12 Azure Blob Job Failure - REST API 409 Conflict (SnapshotsPresent) After Tier Change

  • Oct 22, 2026 1:30 PM UTC
  • 1 comment
  • 10 views
Forum|alt.badge.img+1

Additional Details: Issue Description: Our offsite Azure Blob backup job is failing with a REST API 409 Conflict: SnapshotsPresent error when Veeam attempts to delete or clear the metadata lock files located in the .../Metadata/Lock/create.checkpoint/ directory. Steps Performed Before Opening Case & Why: 1. Disabled Azure Blob Soft Delete (In Azure Portal): Disabled Blob and Container Soft Delete and permanent delete for soft deleted items to stop a 7-day duplicate billing loop caused by Azure trapping Veeam's deleted files at premium rates. 2. Enabled Cool Tier Option (In Veeam 12 Console): Edited our repository properties in the Veeam 12 app and checked the box "Use cool blob storage tier" to migrate our data footprint from the premium Hot tier to the cheaper Cool tier, aimed at lowering our permanent monthly storage bill. 3. Inspected Blobs via Azure Portal: Navigated directly to the target metadata folder (try, lock, and declare blobs) to check for active snapshots. The Azure UI reports "No snapshots found," but the underlying API continues to return a SnapshotsPresent conflict lock, preventing Veeam from clearing the folder and running the job.

1 comment

anco93
  • anco93
  • New Here
  • Nov 2, 2026 8:47 AM UTC

The SnapshotsPresent error makes sense with soft delete in the picture. While blob soft delete was on, every overwrite of a blob created a soft-deleted snapshot, and Veeam rewrites those lock/checkpoint blobs a lot. Soft-deleted snapshots don’t show in the portal unless you enable “Show deleted blobs”, which is why you see “No snapshots found”. Disabling soft delete doesn’t remove them either: they stay until the retention period that was in effect expires, and Azure won’t delete a blob that still has snapshots.

So first check those blobs with “Show deleted blobs” on. You mentioned a 7-day loop, so if that was your retention they should be gone by now and the job should run again. If not, I’d open a case rather than clean up the metadata folder by hand.

Also worth knowing: Veeam doesn’t support blob soft delete on Azure Blob repositories at all, so disabling it was the right call regardless.

Terms & ConditionsAccessibility statement