A Note on an Error When Moving a Backup to S3

Hi! In a previous post, we covered the Backup Move feature in VBR 12. It’s great.

However, I ran into a small error that prevented me from moving backups between repositories—in particular, from a local repository to an immutable S3 repository in Wasabi.

As the error shows, the issue was in the job configuration: it was set to run a Synthetic Full on Saturdays, which caused the problem.

We changed it to Active Full, ran a full backup, and then the repository move worked.

It’s a small detail to keep in mind when moving backups.
Keep an eye on available space. An Active Full takes up space, and depending on your resources, you could run into issues.

Another detail to keep in mind when creating jobs:
if you expect to move backups this way, it’s worth preparing for it in advance.

Regards.