migration veeam agent repository

[matteu]

Hello,

I need to migrate my veeam agent repository from Dxi to Hardened linux.
My customer would like to use USB disk on endpoint (veeam managed by AGENT job) to backup it and then copy the data on the linux repository (dxi would not be used) but I see this KB : https://www.veeam.com/kb2849

It's not possible to use USB disk and then copy the data on my linux repository to process this migration right ?

My only solution is to do a new full backup job over the WAN link ?

[Dima P.]

Hello matteu,

Customer can backup to a local usb drive without any issues but such backup wont be visible in the Veeam B&R console. You can tape the USB to your main site, import the backups to a Linux repository but then such backups will be treated as imported (so not retention will be performed). Thanks!

[matteu]

I can't use them as seeding right ?

[Dima P.]

Only for the current job - mapping will work within the same policy. Say you've configured agent policy to USB, then decided to change repo to a Linux Repository. When you change the current policy to a new repository (change the settings in the wizard), you can place backup files to this repo and automatic mapping will continue the backup chain. If that's a new policy or job that's not going to work.

[matteu]

If it's working on a new job it's perfect for me.

1) I create new backup job
2) I create backup with managed by agent and backup to USB disk
3) I copy the folder with job name from USB disk to linux hardened repository
4) I rescan the hardened repository
5) I update backup job policy from USB to veeam repository and select linux hardened and Veeam will map it automatically.

Am I right ?

I suppose I'm on scenario 1 from here : https://www.veeam.com/kb2321
but not sure it corresponds to what I wrote above.

[matteu]

OK, I did tests.

If I use local storage on the job, it's not working.
I need to declare the endpoint as veeam managed server and repository with USB drive path and use it as veeam backup repository for job destination.

It's what is written in the first KB I linked : https://www.veeam.com/kb2849