#1 Global Leader in Data Resilience

Additional Information on “Cost Estimation” in Veeam Backup for AWS

KB ID: 3054
Product: Veeam Backup for AWS | 1.0 | 2.0 | 3.0 | 4.0 | 5.0 | 5a | 6.0 | 6a | 7.0 | 8
Published: 2019-12-02
Last Modified: 2024-07-23
mailbox
Get weekly article updates
By subscribing, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.

Cheers for trusting us with the spot in your mailbox!

Now you’re less likely to miss what’s been brewing in our knowledge base with this weekly digest

error icon

Oops! Something went wrong.

Please, try again later.

Related User Guide Page

Challenge

Cost Estimation provides the administrator feedback on estimates of AWS infrastructure costs for the backup operations of a policy. This shows granular information on how much cost running the policy will incur, with an option to export to CSV or XML. Included in the cost estimation is the following information:

  • Snapshot Costs – costs for EBS snapshots
  • Backup Costs – costs for S3 storage and worker operations
  • Traffic Costs – costs for network transfers. These typically represent out-of-region or out-of-AWS networking charges
  • Transaction Costs – S3 request and data retrievals charges
  • Total Costs

Solution

Based on the instances included in a policy, settings, and schedules, cost estimation provides infrastructure cost estimates for the policy's operation.

The calculations are based on:

  • Sizes of the instances.
  • The location of the destination of the policy:
    • Snapshots
    • Backups (region of S3 bucket for storing backups)
  • Built-in constants for:
    • Change rates daily (3% daily)
    • % of total Instance capacity that is in use (70% of the provisioned size)
  • Schedule for the instance.
  • Types of storage consumed by the instance snapshots and backups.
  • Calculations are done based on the policy running regularly and becoming ‘mature’ in that retention operations are being performed.


When optimizing costs, some things to understand:

  • Are there unexpected network traffic charges due to out-of-region or out-of-AWS data transfers?
    Adjusting policy settings for repository selection may help reduce these costs. For example, selecting a repository that is in the same region as the source Instances being backed up by the policy.
  • Are there high Snapshot charges?
    Adjusting the snapshot retention may help reduce these charges.
  • The overall frequency of backups?
    More frequent policy scheduling can raise infrastructure costs for the policy.
  • Cost estimation does not estimate restore costs.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.

Spelling error in text

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

Oops! Something went wrong.

Please, try again later.

You have selected too large block!

Please try select less.

KB Feedback/Suggestion

This form is only for KB Feedback/Suggestions, if you need help with the software open a support case

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Notice.
This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply except as noted in our Privacy Policy.
Verify your email to continue your product download
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend
Thank you!

Thank you!

Your feedback has been received and will be reviewed.

error icon

Oops! Something went wrong.

Please, try again later.