...

A quick cost analysis has restoration costing $30-35 dollars, this is as of 6/11/2018 with approximately 1 TB of data. Approximately 66% of the cost was due to inter-region transfer fees (moving data from US-WEST to US-EAST). The rest is standard LIST, GET, and related fees.

Kithe recovery

Kithe currently (March 2019) has a small set of data to be handled for recovery.

• A postgres database which contains user data and item metadata
• Original binary files
• Derivative Files

The first two are the ones that are needed the derivatives are merely backed up because the cost to back them up is low relative to the amount of time saved on a recpvery by having a copy ready.

The postgres database is backed up to S3 (currently unscheduled, fix this)
The binary files are replicated via S3 replication to a second location in US-WEST rather than US-EAST in case of outages. When we actually switch over, these will also be backed over to local on-site storage.
The derivative files will also be replicated via S3 replication to a US-WEST location.

Recovery levels:

When we look at recovery it will be useful to distinguish between full and partial recoveries. The following classifications may prove helpful

• Raw data only: In this case we only have access to the raw data, this is only a level in case of a massive outage that destroys all AWS.
• Partial public, no staff recovery: In this case the public has access to limited functionality but features like derived images may not be fully restored, staff can access public functions but not do additional work.
• Partial public, partial staff recovery:
• Full public, no staff recovery
• Full public, full staff recovery: