Last week I wanted to move a backup job from one repository to another. When I tried I received an error that there wasn't enough disk space even though the disk was empty and larger than the disk where the job currently resides. If I do a properties of all the files on the disk the size well exceeds the capacity of the disk. I don't understand what is happening here.
I looked in the forum FAQ and there was a mention about ReFS block cloning to save disk space and the screenshots showed a simillar situation to mine. Is this my situation? If, so how can I move the files to another repository?
-
- Lurker
- Posts: 1
- Liked: never
- Joined: Aug 31, 2020 12:45 pm
- Full Name: Charlie Caldwell
- Contact:
-
- Product Manager
- Posts: 9948
- Liked: 2636 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: Disk Space used
If you move the files from a reFS Volume with FAST Clone backups to a new disk, all files will be rehydrated.
Meaning, you have now used 9TB physical disk space. If you have 6 Full Backups on this disk with the size of 7TB, you will need 6x 7TB disk space on the target. Windows Explorer cannot move the fullbackup files and keep the storage savings from Fast Clone/block Cloning API.
Only disk copy tools which operates on block level will keep the space savings from FAST Clone.
Meaning, you have now used 9TB physical disk space. If you have 6 Full Backups on this disk with the size of 7TB, you will need 6x 7TB disk space on the target. Windows Explorer cannot move the fullbackup files and keep the storage savings from Fast Clone/block Cloning API.
Only disk copy tools which operates on block level will keep the space savings from FAST Clone.
Product Management Analyst @ Veeam Software
Who is online
Users browsing this forum: Semrush [Bot] and 43 guests