Cloudboost Appliance Cache Sizing - EMC CloudBoost 100 Installation And Setup Manual

Installation and Setup Guide

CloudBoost appliance cache sizing

EMC CloudBoost 100 2.0 Installation and Setup Guide
26
-------
address
Network Routes:
prefix
------
default
0.0.0.0
DNS Configuration
DNS Servers:
Appliance status:
Domain name:
Results
After you have verified the system's basic networking settings, you can register the
appliance and then configure CloudBoost by using the EMC Cloud Portal.
Note
Other commands are also available from the command line. To get help, type
or .
?
If you intend to enable the site cache for a CloudBoost appliance, change the data disk
size before initial configuration of the CloudBoost appliance at the CLI.
Change the parameters in vCenter virtual machine configurations before you begin
initial CloudBoost configuration at the CLI. It is recommended that you change these
numbers to the appropriate levels based on the amount of data you plan to backup.
Consider the following:
The ingestion rate for a CloudBoost appliance without site cache enabled is
l
measured at up to 100 MB/s.
The site cache has a 50 MB/s ingestion rate for the 32 TB physical appliance.
l
The site cache has a 25 MB/s ingestion rate for all other appliances that can be
l
improved by de-duplication and compression, depending on the workload.
The underlying storage rate must be 25 MB/s for simultaneous reading and
l
writing.
An average chunk size of 256 KB equals a few hundred IOPS.
l
The total number of site cache disks must be a multiple of 2 up to 32 disks. For
l
example 1, 2, 4, 8, 16 or 32 disks.
To optimize performance, configure each site cache VMDK on a different data
l
store. For example, for a 2TB site cache 4x500GB VMDKs can be used.
The size of the cache cannot be increased or decreased by growing the existing
l
data disk size in vCenter.
The minimum size of the cache is 200 GB, and can be increased up to 6 TB on the
l
virtual appliance by adding disks that match the size of the existing site cache
disks.
The cache is firewall-friendly, so multiple ports do not need to be opened.
l
---- ----
eth0 static
netmask
-------
0.0.0.0
address
10.8.192.91
Not yet registered
domain name
-------
10.5.96.123
gateway
-------
10.5.96.1
*
help