Moving backup repository to "same" drive?

[Oletho]

A customer ran out of space on a backup repository, and did not have the possibility to extend.

Instead I mounted a bigger LUN on the same repository server, moved backup to the new disk, deleted the old one and gave the new same label and drive letter as previously.

Then rebooted repository server (Veeam server itself) and rescanned the repository. All was looking fine and freespace updated to new value.

First backup, which coincidently was a full, succeeded.

But the next incremental backup failed on all VMs, and at the end of the job status it says Error: Full storage not found.

Am I missing something?

[veremin]

Hi, Ole, I'm wondering what happens if you try to map the existing jobs to the corresponding backup data. Will you still get the said error after doing that? Thanks.

[Oletho]

Had to find a quick solution so we decided to delete all old backups and run a new full. The following incremental was fine.

[veremin]

Next time it might be worth trying mapping backup first, as it doesn't require restore point deletion. Thanks.

[Oletho]

I will. Thanks.