Scenario:

A Core has 2000 GB of storage allocated to the repository, but the Home tab of the UI only shows 1800 GB for the Total Size of the repository. 

Explanation:

The Core's repository is split into 2 sections. One is for storing the individual recovery points. The other stores the recovery point indexes and metadata information. The indexes and metadata use approximately 10% of the allocated space. The Home tab only reflects the amount of storage available for recovery point storage and excludes the storage required for the index and metadata information.

Just like your local core, your remote core is a Windows machine that we host for you. While you do not have access to the full machine – instead you only have access to the user interface – your remote core behaves just like your local core does in regards to space usage.

The core listed above shows 2.68 TB of space total on the repository, with 1.59 TB of that space in use. The machine that hosts the core, though, has a 3000 GB X drive, as seen below:

The space listed for Disk 1 that is unallocated is space available to extend your core, if you request it. Remember, you pay for the space that is allocated to your core’s X drive where the repository resides, whether you have data on the repository or not. You do not pay for the unallocated space.

When a new repository is created or new space is added to your repository, approximately 10% is reserved for the metadata. In newer version of Rapid Recovery, this space is allocated for the metadata with a slider and box to type in. We set this to 10%.

In older versions of Rapid Recovery, though, this percentage is calculated automatically by the software, and we have no control and no indication of exactly how much space is being used for the metadata. Even in older version, this is generally approximately 10% of the repository’s available space.

Example: 2000 GB * .10 = 200 GB. 2000 GB less this 200 GB = 1800 GB

There is also an additional 5-10 GB that is reserved for Windows File System operations that does not show in the allocated storage on the UI.