Skip to main content

Is it possible to add GFS restore points to the sizing for Azure, AWS and GCP?  When I do a sizing for cloud workloads the only option is for daily restore points but I need to size for weekly and monthly as well.

 

Thanks!

Hi @TeeDee,

which calculator are you using?

I just checked on the Cloud calculator https://www.veeam.com/calculators/simple/cloud/azure but I also saw the daily policy only.

Within the policies in the actual agent you absolutely should be able to work with GFS, here the article for Azure appliance as example: https://helpcenter.veeam.com/docs/vbazure/guide/configuring_global_retention_settings.html?ver=70

 

Where do you store the backups? Do you really need the estimated storage consumption, e.g. in case of pay-as-you-use these values are often not required or could be accumulated.

 

Best regards!

Lukas


That’s the calculator I’m using: https://www.veeam.com/calculators/simple/cloud/azure . Many times customers need to see a 1 or 2 TCO/ROI before moving forward with Veeam.  Without the GFS points in the calculator it becomes very difficult to put that TCO/ROI together. 


Does the customer compare this to an on-prem solution? My point is that the definition of TCO and ROI with cloud scenarios is often different, e.g. die 5-year lifespan is not declared or not “needed” in the cloud. You don’t have to set a timeframe to cloud workloads that is why it is very difficult to calculate those in my opinion.

What do you (or does the customer) declare as TCO and ROI and which timespan are we talking about? I am facing similar “challenges”, maybe I can give some input. 😊


Hi @TeeDee regarding the GCP here is my findings for you set up a SOBR in Veeam that uses a GCP bucket as its capacity tier this will allow us Veeam to offload GFS restore points to GCP and configure the offload policy to move or copy backup data including GFS points to the capacity tier in GCP make sure that Veeam has the appropriate access to the GCP bucket with sufficient permissions for managing backup data.


Comment