View Source

{color:#000000}Before you set up Archive, you will need to have an FTP server or Amazon Glacier account already configured.{color}

h3. {color:#000000}How to set up an Amazon Web Services/Amazon Glacier account{color}

{color:#000000}The following links will re-direct you to Amazon Web Services for instructions on how to set up an account:{color}
* [How to set up an Amazon Web Services Account|https://aws.amazon.com/console/]
* [Getting Started with Amazon Glacier|https://aws.amazon.com/glacier/getting-started/]
* [Amazon Glacier Frequently Asked Questions|https://aws.amazon.com/glacier/faqs/]
* [Amazon Glacier URLs for data center regions|http://docs.aws.amazon.com/general/latest/gr/rande.html#glacier_region]

h3. {color:#000000}SBM disk space requirements{color}

{color:#000000}Note that  Archive requires additional disk space on the SBM volume on top of the standard volume sizing guidelines. Follow these guidelines for calculating the amount of formatted disk space required:{color}
* {color:#000000}3 times the live data of all protected machines in the volume.{color}
* {color:#000000}Additional disk space equal to 2x the amount of live data on the machine for each machine in the volume that has{color}{color:#000000} {color}{color:#000000}{_}Archive{_}{color}{color:#000000} {color}{color:#000000}enabled (to allow for the replica and future recovery).{color}

h4. {color:#000000}Sizing Examples{color}

{color:#000000}{*}Example 1{*}{color}{color:#000000}: A site with 3 protected machines that does not use Archive.{color}

{color:#000000}For this example, consider a site that has three protected machines (none of which have Archive enabled) with a per-machine breakdown of live data as follows:{color}
* {color:#000000}Machine 1: 200 GB of live data{color}
* {color:#000000}Machine 2: 100 GB of live data{color}
* {color:#000000}Machine 3: 100 GB of live data{color}

{color:#000000}{*}Total appliance disk space required{*}{color}{color:#000000} {color}{color:#000000}would be calculated as: 3x (200 GB\+ 100 GB \+100 GB)  = 1.2 TB{color}

{color:#000000} {color}

{color:#000000}{*}Example 2{*}{color}{color:#000000}: A site with three protected machines where Archive is enabled on two machines.{color}

{color:#000000}For this example, consider a site that has 3 protected machines with the same per-machine breakdown of live data as in the previous example, but with Archive enabled on two of the machines.{color}

{color:#000000}For each machine where Archive is enabled, additional disk space (equal to 2x the total size of live data on the machine) needs to be allotted to accommodate the disk safe replica that is created when you enable Archive in the policy, and to allow for a copy of the disk safe to be retrieved from the cloud storage location (FTP or Amazon Glacier) in the event of a disaster.{color}
* {color:#000000}Machine 1: 200 GB of live data{color}*# {color:#000000}Archive enabled = additional 400 GB of space required (200 GB for the replicated disk safe \+200 GB to accommodate a copy retrieved from the Archive in a DR scenario).{color}
* {color:#000000}Machine 2: 100 GB of live data{color}*# {color:#000000}Archive enabled = additional 200 GB of space required (100 GB for the replicated disk safe \+100 GB to accommodate a copy retrieved from the Archive in a DR scenario).{color}
* {color:#000000}Machine 3: 100 GB of live data{color}

{color:#000000}{*}Total SBM disk space required{*}{color}{color:#000000} {color}{color:#000000}would be calculated as: 3x (200 GB\+ 100 GB \+100 GB) \+600 GB (for the two machines with Archive enabled)  = 1.8 TB{color}

h3.