New repository and use old as copy location

[A.T.]

Hello,

We are planning to migrate Veeam B&R to a new server with a new repository. I'm aware of the option within B&R to move the existing job to a new repository, so don't think that'll be a problem.
But what I want to accomplish after that is to make the current repository a copy location of the backup.

The current storage is at a remote site, but we want a storage at the local site too, for better performance.
So let's say the current storage holds 30 days of retention and we copy the last chain (1 full and the incrementals) to the new repository, reconfigure the job to have a 7 day retention on the new repository and have a copy job with 30 day retention to the remote site.
Are we able to use the already present files, or do we need to clear the repository and build it from scratch?
The current storage can't hold all the data two times, so we can't leave them there and build the copy next to it until we reach the 30 days retention.

Thanks,
André.

[david.domask]

Hi André, welcome to the forums.

> Are we able to use the already present files, or do we need to clear the repository and build it from scratch?

You will need to create a seed from a Backup Copy Job in order to accomplish what you're looking for.

From our User Guide on the limitations for mapping:

You can map the backup copy job created in Veeam Backup & Replication 12 only to a backup created by a backup copy job. Legacy backup copy job can be mapped to backups created by both backup job and backup copy job.

So starting fresh is an option, or you can point the primary job to the new repository location, and either create a Backup Copy Seed to seed the "old" repository, or just start a Backup Copy fresh.

[A.T.]

Hello David,

Thank you for your response.
So it looks like I have to copy files from remote to local and then copy them back with a copy job.
That's a bit unfortunate.