Fast block

[frankive]

When we migrate to a new veeamserver the support says we will loose the fast block savings on our repository (which is a jbod drive connected to the old server and will be attached to the new server). This will create a new huge demand for disc space for us during the migration.

the question is:
is it possible somehow after we have copied the backup files to the new server/repository that it will be able to hydrate the files again (also old archive backups), or will they stay dehydrated since the hydration only occurs at the time backupfiles is being processed?

[Mildur]

Hello Frank

May I ask, are you planning to "copy the files manually" or just reattaching the same disk?
I see both statements in your question.

If you just connect the same hard disk to the new server, migrated backup files won't be using more space.
But the following backup sessions may not use Fast Clone without running an active full backup or compact operation.

https://helpcenter.veeam.com/docs/backu ... ml?ver=120

After you have enabled Fast Clone for existing repositories as described in the previous paragraph or have manually moved backup chains to backup repositories with Fast Clone support, you must create active full backups for backup chains stored in / moved to the repositories to activate Fast Clone. You can also schedule the backup file compact operation instead of performing active full backup.

If you want to be sure that FastClone works, you can use our new backup move feature in V12. It allows you to move backup files FastClone aware to another repository.
Moving Backups


Best,
Fabian