Migrate / Move a B&R w/Repo

[hbilke]

Howdy fellas,

my tasks is the following:
B&R Console w/tape lib (LTO6) and repo should move to a new host with more storage and bigger tape lib (LTO8).
My plan:
Install Veeam on the new device w/o license
Import config on new device
Move license to new device


And there is the Q.: is it possible to use the old repo (no license attached there) on the new device (for keep the backups running and then move/migrate the data to the new repo) and for copying the LTO6 to the LTO8 tapes?

hRy

[Mildur]

Hi hRy

is it possible to use the old repo (no license attached there) on the new device (for keep the backups running and then move/migrate the data to the new repo)

You can use the old host as a backup repository for the new VBR server. It won't cost you an additional license.
In case you want move the backup files to the new host, you can use this KB article: https://www.veeam.com/kb1729
What file system does the old host use? XFS or reFS? If you migrate that data to the new host, you will loose FastClone space savings. I suggest to wait for our next release V12, which will allow you to migrate that data without loosing FastClone space savings. Or you can just leave the old data on the old host and age them out. Start with new Active Fulls on the new host.

for copying the LTO6 to the LTO8 tapes?

Yes, you can use our tape copy feature for that:
https://helpcenter.veeam.com/docs/backu ... ml?ver=110

Thanks
Fabian

[hbilke]

Thanx Fabian,

when is V12 due?
ReFS to ReFS will loose FastClone? Is there a way to check for the needed space on target?

Harry

[Mildur]

when is V12 due?

Our current estimation is end of december for RTM and in 2023 GA release.

ReFS to ReFS will loose FastClone? Is there a way to check for the needed space on target?

Yes, in current versions, it will loose the space savings.
You can go to the repository folder where the Veeam backups are stored and open the properties of that folder. Do not use the disk properties. It has to be the folder properties. There you will see the space required to copy the backups.

As a short example. If you have 12 full backups which have a size of 5 TB each, they will require 12*5TB space if you decide to copy it now.
That would make 5TB before, 60 TB after you have copied the files. And you have to count in also the incremental files.
You could use a disk cloning tool, that could work as a workaround.

Thanks
Fabian

[hbilke]

Hi Fabian,

a last Q.: "age them out" - you mean start the backupchain anew and keep the old repo until my retention req.s are met? Should the repo sty connected / accessable or just keep the data?

Harry

[Mildur]

Yes. That‘s what I meant.
You can connect the old host as a repo todo restores from the old backups if needed.

If that‘s an option for you, you won‘t have todo the migration of the backup data.

[hbilke]

Thanx