Introduction

A backup migration can bring the new repository online while protected servers still write backups to the old target. Jobs appear successful, but restore points land in the retired system, retention behaves inconsistently, or one protection group uses the new repository while another still depends on the previous backup environment because agents, policies, or repository mappings were not fully updated.

Treat this as a backup-destination problem instead of a generic restore or storage outage. Start by checking where an affected backup agent actually sends its job data, because migrations often stand up new backup infrastructure first while endpoints continue using their old repository assignment.

Symptoms

  • Backup jobs still write to the old repository after migration
  • New backup infrastructure is online, but fresh restore points do not appear there
  • One server or policy uses the new repository while another still targets the previous backup system
  • Retention, immutability, or offsite copy behavior differs after the cutover
  • Backups appear healthy until the old repository is decommissioned
  • The issue started after moving backup software, repositories, object storage, or protection policies

Common Causes

  • The backup agent or proxy still has the old repository, vault, or storage target assigned
  • A backup policy, protection group, or job template still maps workloads to the previous repository
  • One backup server or media proxy was migrated while another still manages jobs through the retired platform
  • Credentials, repository IDs, or object storage endpoints still resolve to the old backup target
  • Agents cached the previous server assignment and never re-registered with the new backup environment
  • Validation confirmed the new repository existed but did not verify where live backup jobs actually wrote data

Step-by-Step Fix

  1. Capture one affected backup job and record the exact repository, media server, or storage endpoint it uses, because the runtime destination matters more than the migration checklist.
  2. Compare that active target with the intended post-migration backup design, because one stale repository mapping can keep protected systems tied to the retired platform.
  3. Review backup policies, protection groups, repository assignments, proxy settings, and agent registration state for references to the old environment, because backup routing often spans several control layers.
  4. Check whether different job types such as full, incremental, archive, or replication backups use different targets, because migrations often move one path while another stays behind.
  5. Update the authoritative repository or policy mapping and re-register or restart affected agents if required, because job runners can keep using cached targets until they reload configuration.
  6. Trigger a controlled backup and confirm the new restore point appears in the intended repository, because a successful job status alone does not prove the backup landed in the right place.
  7. Verify the old repository no longer receives writes from migrated systems, because mixed backup destinations can stay hidden until retention or restore is needed.
  8. Review restore jobs, copy jobs, and retention policies if behavior still looks inconsistent, because secondary backup workflows often keep separate destination settings.
  9. Document who owns agent registration, repository mapping, and migration validation so future backup cutovers confirm the live write target before retiring the previous environment.