asggenesis.blogg.se - Veeam storage calculator

The average object size depends on the observed Data Reduction, but a good estimation is to use a 2:1 ratio.įinally, a count of objects can easily be deducted from the observed or simulated backup size in the performance tier (prior to any capacity tier offloads), and the object average size. Note: Local Target - extra large (8192KB blocks, see KB4215: Release Information for Veeam Backup & Replication 11a ) The "Job block size" (or “Storage optimization”) is defined in the user guide, but to summarize: The number of PUTs is directly related to the Veeam Job Storage Optimization settings (“job block size). You can plug these numbers into your public cloud calculator of choice for cost or ensure that your on-premises object store can optimally process the workloads locally. The following formulas propose a simple method to "guesstimate" the number of PUT operations and maximum number of objects for backup offloads.

Bucket maximum size for a given object size.

Data ingest rate (MB/s) and maximum object size.

Objects ingest rate (objects per second) and maximum object size.

The architecture specific limitations of the object storage vendor’s metadata service are typically expressed in one or a combination of the following metrics: Each implementation comes with its own limitations. Some vendors store object metadata in databases while others may store object metadata on disk using placement technique such as consistent hashing. Note: Object Storage Device metadata service implementations vary from vendor to vendor. If you are considering an "on-premises" Object Storage solution, be mindful of vendor-specific limitations in their ability to handle large amounts of object metadata (and therefore number of objects). With most public cloud providers, API operations are not free. Note: It is safe to assume that 99% of all objects created are backup Data bits, the rest is backup Meta-Data.

Veeam backup Meta-Data and Data bits become Objects stored onto the Capacity Tier via PUT operations. When offloading backups to the Capacity Tier, the “. Note: You can combine both offload operations.

The Capacity tier offers two types of offload operations: The Performance Tier holds the "operational restore window" parts of the backups on-premises, typically on block or file-based storage, while both the Capacity and Archive Tiers allow expansions to Object Storage. SOBR is a logical construct allowing a backup administrator to group storage extents together to form a multi-tier storage "pool" to ease the management of backups.