-
Nas
- Enthusiast
- Posts: 56
- Liked: 6 times
- Joined: Oct 02, 2023 3:34 am
- Full Name: Nashville M.
- Contact:
Fast cloned backup capacity when moved to object storage
Hi,
From VBR console, my current Windows ReFS repository capacity shows:
100TB used
70TB free
90TB total capacity
From the Windows repository explorer, it shows E: drive capacity is 20TB used. So fast clone is saving lot of physical storage usage in my case.
If I were to enable SOBR, with my Windows repository as performance tier and Azure blob storage as capacity tier. What would be the expected usage (TB) on my capacity tier assuming I choose copy all backups?
I understand there is no block cloning on object storage, so am I anticipating my existing backups to rehydrate beyond 20TB or maybe reach 100TB capacity usage once they copied over to capacity tier?
From VBR console, my current Windows ReFS repository capacity shows:
100TB used
70TB free
90TB total capacity
From the Windows repository explorer, it shows E: drive capacity is 20TB used. So fast clone is saving lot of physical storage usage in my case.
If I were to enable SOBR, with my Windows repository as performance tier and Azure blob storage as capacity tier. What would be the expected usage (TB) on my capacity tier assuming I choose copy all backups?
I understand there is no block cloning on object storage, so am I anticipating my existing backups to rehydrate beyond 20TB or maybe reach 100TB capacity usage once they copied over to capacity tier?
-
HannesK
- Product Manager
- Posts: 15684
- Liked: 3470 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Fast cloned backup capacity when moved to object storage
Hello,
assuming that you are not using immutability, the storage consumption on object storage would be similar as on REFS / XFS.
With immutability the math is more complicated: see user guide. Then the space consumption formula is "retention period + immutability period + block generation period". Please note, that the storage consumption is massively reduced in V13 with "direct to object storage" (aka Backup Copy Job). The new formula is "retention period" + "block generation period".
http://calculator.veeam.com/ also should help to estimate.
Best regards
Hannes
assuming that you are not using immutability, the storage consumption on object storage would be similar as on REFS / XFS.
With immutability the math is more complicated: see user guide. Then the space consumption formula is "retention period + immutability period + block generation period". Please note, that the storage consumption is massively reduced in V13 with "direct to object storage" (aka Backup Copy Job). The new formula is "retention period" + "block generation period".
http://calculator.veeam.com/ also should help to estimate.
Best regards
Hannes
-
Nas
- Enthusiast
- Posts: 56
- Liked: 6 times
- Joined: Oct 02, 2023 3:34 am
- Full Name: Nashville M.
- Contact:
Re: Fast cloned backup capacity when moved to object storage
Hi Hannes,
Thanks for replying, the capacity tier is immutable.
Referring to formula "retention period + immutability period + block generation period", in my case I set;
retention policy to 30 days
immutability period 30 days
azure default block generation period 10 days
Am I correct to assume that retention policy and immutability period always overlap?
So effectively, I should be forecasting for 40 days storage consumption as minimum and not 30 + 30 + 10, correct?
Thanks for replying, the capacity tier is immutable.
Referring to formula "retention period + immutability period + block generation period", in my case I set;
retention policy to 30 days
immutability period 30 days
azure default block generation period 10 days
Am I correct to assume that retention policy and immutability period always overlap?
So effectively, I should be forecasting for 40 days storage consumption as minimum and not 30 + 30 + 10, correct?
-
vitalii.fesh
- Influencer
- Posts: 16
- Liked: 4 times
- Joined: May 29, 2024 2:47 pm
- Full Name: Vitalii Feshchenko
- Contact:
Re: Fast cloned backup capacity when moved to object storage
No, you have to sum up retention and immutability. Check this out: https://helpcenter.veeam.com/docs/backu ... ml?ver=120
-
HannesK
- Product Manager
- Posts: 15684
- Liked: 3470 times
- Joined: Sep 01, 2014 11:46 am
- Full Name: Hannes Kasparick
- Location: Austria
- Contact:
Re: Fast cloned backup capacity when moved to object storage
yes, your space consumption would be 70 days (30+30+10) with capacity tier.
from the link above
from the link above
user guide wrote:Actual retention = job retention policy + immutability period + Block Generation period
Who is online
Users browsing this forum: Amazon [Bot], Baidu [Spider] and 5 guests