- Posts: 11
- Liked: never
- Joined: May 31, 2011 10:21 pm
- Full Name: Thomas Moy
For a separate on-site copy repository, we can usually keep 7 days of backups in less than 2TB. I haven't caught it in the act of merging/injecting, but by the time I check in the morning, it's less than 2TB.
So back to the cloud job: on the proxy I see the following files chronologically:
I'm curious if this is normal behavior for a Backup Copy job to a Cloud provider. If I want to have 2TB at rest capacity, do I need 3TB allocated for the cloud repository? 4TB?
Thanks in advance for any thoughts.
- SVP, Product Management
- Posts: 24940
- Liked: 3622 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
No, this is not a normal behavior.
The behavior should be exactly identical between your on-site Backup Copy, and the one going to your Cloud Connect provider (as in both cases, exactly the same code is used - so any deviations in behavior are simply impossible).
I recommend you troubleshoot this with support to see what has caused that large 900 MB increment to be created. Usually, it can only happen when some new VM is added to the Backup Copy job. But, there is always a chance that there is some bug as well.
- Veeam Software
- Posts: 5753
- Liked: 1644 times
- Joined: Jul 26, 2009 3:39 pm
- Full Name: Luca Dell'Oca
- Location: Varese, Italy
Principal EMEA Cloud Architect @ Veeam Software
vExpert 2011 -> 2019
Veeam VMCE #1
Users browsing this forum: Bing [Bot] and 34 guests