Skip to content

Latest commit

 

History

History
61 lines (51 loc) · 2.66 KB

CHANGELOG.md

File metadata and controls

61 lines (51 loc) · 2.66 KB
Raw

Change Log

All notable changes to this project will be documented in this file. This project adheres to Semantic Versioning.

0.0.4 [unreleased]

Added

  • WIP: Out-of-region snapshot support
    • Prototype:
      • An additional region, in addition to the region an instance is located in, can be specified in the creator (hardcoded in the 'copy_region' (hardcoded variable). If left empty, no out of region copy is made.
      • Problem discovered: snapshot copies can be triggered before the original (source) has completed. This results in snapshots in an "error" state that are unusable. To prevent this, only completed snapshots should be copied.

Changed

  • During a job run, every individual snapshot that is triggered, is now displayed
  • The snapshot Description now includes the Name of the EC2 instance the volume was attached to at the time the snapshot was created
  • The snapshot Description now includes the device name (e.g. "/dev/sda1") on the EC2 instance the volume was attached to at the time the snapshot was created

Fixed

  • Nothing so far

0.0.3 - 2016-05-18

Added

  • Snapshots created by this tool (as opposed to manually) are now indicated by the automatic addition of and setting of the tag "Type" to "Automated" on each created snapshot.
  • Any previously created snapshot can be retained indefinitely by manually adding the tag "KeepForever" to the snapshot to any value.

Changed

  • Cleaned up some code formatting for key/values
  • The instance tag "Backup" must now be set explicitly to "Yes" (rather than just being present with any value)
  • The snapshot manager skips processing of any snapshots lacking the tag "Type" with a value of "Automated"
  • The instance Name (a standard AWS tag) is now displayed (in parentheses) after the InstanceID in log output in the snapshot creator

Fixed

  • Nothing so far

0.0.2 - 2016-05-18

Added

  • Second commit based on Ryan S. Brown code that adds support for expiration management
    • https://serverlesscode.com/post/lambda-schedule-ebs-snapshot-backups-2/
    • instances can be tagged with "Retention" tag so we can define how long to keep snapshots around
    • default Retention period, if none specified, is 7 days
    • snapshots are tagged with DeleteOn that contains the day the snapshot should be deleted. The date is formatted as YYYY-MM-DD (2015-11-05).
    • new snapshot manager function that handles deletion of old snapshots

0.0.1 - 2016-05-18

Added