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?
-
- Service Provider
- Posts: 1092
- Liked: 134 times
- Joined: May 14, 2013 8:35 pm
- Full Name: Frank Iversen
- Location: Norway
- Contact:
-
- Product Manager
- Posts: 10276
- Liked: 2746 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Fast block
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
Moving Backups
Best,
Fabian
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
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.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.
Moving Backups
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Service Provider
- Posts: 114
- Liked: 9 times
- Joined: Jul 01, 2017 8:02 pm
- Full Name: Dimitris Aslanidis
- Contact:
Re: Fast block
Sadly, this has not worked for me. I have in the past moved manually a lot of backups from ReFS disk to another ReFS disk on the same Veeam server and Fast Clone worked normally. When I did it with the Move function the last few times, again ReFS to ReFS on the same server, Fast Clone did not work and I have jobs taking TBs of space each week. This has caused us huge issues as an MSP.
-
- Product Manager
- Posts: 10276
- Liked: 2746 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Fast block
Hi Dimitris
Move Backup is a Fast Clone supported operation.
Best,
Fabian
Please open a case with our customer support if Move Backup didn't use FastClone.When I did it with the Move function the last few times, again ReFS to ReFS on the same server, Fast Clone did not work and I have jobs taking TBs of space each week. This has caused us huge issues as an MSP.
Move Backup is a Fast Clone supported operation.
Best,
Fabian
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Baidu [Spider] and 115 guests