Bare Metal Restore

Calculate Your Return On Investment

Desktop / Laptop
Number of computers  
Average amount of data per computers GB
Common data across all computers %
Changed data since last backup %
Full generations retained  
Incremental generations retained  
Application / File servers
Total amount of data GB
Changed data since last backup %
Full generations retained  
Incremental generations retained  
£Price per Gigabyte  

Legacy Systems vs AIMstor comparison

Total data stored in legacy system   TB
Total data stored in AIMstor   TB
AIMstor Capacity Saving   %
£Cost saving    

General Capacity Principals to Consider

A good rule of thumb is to consider the total capacity you are using for files, applications and OS's that you want to protect, and add 50% to 100% more for your capacity requirements within the AIMstor Repository.

The number of snapshot views, retention, file versions, and application data (MS SQL, Oracle, etc.) will influence the total capacity you use for Repositories. For example, consider these 2 scenarios:

Example One: 2TB File System "real, live data" (File Servers, Laptops, apps plus OS, etc.) and a daily 2% change rate:

24 Fulls Retained, 90 Incrementals Retained = 2.4TB Capacity Repository requirement

Example Two: 2TB Application "real, live data" (SQL, Oracle, etc.) and a daily 2% change rate:

24 Fulls Retained, 90 Incrementals Retained = 3.1TB Capacity Repository requirement

Site by Froot Websites