Communal storage for on-premises Eon Mode databases

If you create an Eon Mode database, you must plan for your use of communal storage to store your database's data. Communal storage is based on a shared storage, such as AWS S3 or Pure Storage FlashBlade servers.

Whatever communal storage platform you use, you must ensure that it is durable (protected against data loss). The data in your Eon Mode database is only as safe as the communal storage that contains it. Most cloud provider's object stores come with a guaranteed redundancy to prevent data loss. When you install an Eon Mode database on-premises, you may have to take additional steps to prevent data loss.

Planning communal storage capacity for on-premises databases

Most cloud providers do not limit the amount of data you can store in their object stores. The only real limit is your budget; storing more data costs more money.

When you create an Eon Mode database on-premises, your storage is limited to the size of your communal storage. Unlike the cloud, you must plan ahead for the amount of storage you will need. For example, if you have a Pure Admin FlashBlade installation with three 8TB blades, then in theory, your database can grow up to 24TB. In practice, you need to account other uses of your object store, as well as factors such as data compression, and space consumed by unreaped ROS containers (storage containers no longer used by Vertica but not yet deleted by the object store).

The following calculator helps you determine the size for your communal storage needs, based on your estimated data size and additional uses of your communal storage. The values with white backgrounds in the Value column are editable. Change them to reflect your environment.

	Description	Value	Unit	Notes
1	Expected size of uncompressed data	100	TB	The amount of data you expect to have after a year, or possibly the end of the amortization period
2	Expected compression of data	5	x	Compressed data will be 20% of its original size.
3	Expected compressed data size	20	TB
4	Number of projections	2	x	Projections are copies of the data sorted differently to support different queries.
5	Expected database size with projections	40	TB
6	Staging area for loading data	20	TB	The amount of space you will use to stage data to be loaded into Vertica.
7	Space for external tables	50	TB	The amount of space you will use in the object store to hold external Vertica tables.
8	Space for unreaped ROS files	5	TB	Space consumed by storage containers Vertica no longer needs but have not yet been deleted. This value is affected by the size and distribution of daily loads, which triggers the tuple mover to merge-out and combine files
9	Estimated total data size	115	TB
10	Headroom for spikes or unexpected situations	10	%	As a percent of the estimated total data size.
11	Safety margin	5	%	An additional safety margin to cover unforseen circumstances.
12	Recommended size for communal storage	132.25	TB

jExcel Spreadsheet