Multiple full backup for NAS

Hi ​@ryan.drm ,

there is a function to move the backups from one Repository to another. But while moving veeam will disable the job and than reconfigure the job to go to the new repository. This would definitely help with the inactive chain.

https://helpcenter.veeam.com/docs/vbr/userguide/backup_moving.html?ver=13

There is also a possibility to copy to another Repository or folder. I´m not sure if veeam disables the job for this as well cause i never needed that feature till now.

https://helpcenter.veeam.com/docs/vbr/userguide/copy_backup.html?ver=13

Hope that helps

Regards

Chalid

Hi ​@ryan.drm - Welcome to the Community!

I’d for sure look at the Veeam Mover feature (as it was called in v12, tho no more I guess) Chalid shared about. That is probably the place to start with minimal impact, albeit your Job(s) disabled for a time. 

Your other option is if your current Repo’s are SOBR Repos and the option to move your backups to a different extent within your SOBR to accommodate the need for increased space. That’s a bit more complex though.

At the very least, I suggest to look at the Backup Move feature and certainly reach out to Veeam Support for confirmation and guidance on the best approach for your environment. 

Keep us posted if you could on how things go.

Best.

Hi Chalid, 

Thanks for your reply.

I already do copy backup from first repository to secondary repository, but it will be disable di backup job too. 

Is there another way do copy inactive backup chain? Maybe using manual copy (copy & paste), then import them manually from secondary repository?

Best ragerds,

Ryan

Hi Coolsport,

Thanks for your reply.

For SOBR, We haven't used it yet, because the repository we're currently using already contains backup data.

I'm curious what would happen if we manually copied and pasted the inactive backup chain, and then imported the copied file into repository 2. I already tested it on my lab and it works.

Thanks and regards,

Ryan

Hi ​@ryan.drm, 

It should be possible to copy the data and then re-scan the repository for existing backups. 

But from my understanding the “inactive” chain is not part of an active Job so it shouldn't be an issue if the inactive Job would be disabled for the time of the copy or move job.

Understood; and SOBR introduces a little bit of complexity IMO. It’s a decent feature...for specific use-cases, but for general Backups, stick with a regular (Immutable) Repo IMO.

You should be ok...especially if you tested the process already. I believe once you import it, it should show as “Orphaned” in the Home View > Backups section, and you could then use them to do a restore if needed. If you have any concerns, even though you tested the process already, you can always reach out to Veeam Support.