Enhancements and bug fixes for eybackup/ey_cloud_server.
Improves functionality and alerting for logical backups (eybackup). Corrects issue where mysql backups were recording database name in the backup Adds server identity to mysql backups to make them useful for replication-based restores Prevents and warns about overlapping backup runs; provides an override option off by default. cli improves backup errors when params specified incorrectly (leaving off db arg) listing backups with all now properly indexes multiple databases in environment OKAY messages only sent on first success after backup failure Error messages are printed to /var/log/engineyard/eybackup/#{dbname}.alert Backup Size and datestamps are printed to /var/log/engineyard/eybackup/#{dbname}.sizes which is capped at 100 lines new_backup option now backs up a specific db if listed, otherwise will back up all databases postgres restores perform analyze after load; adds a skip_analyze option adds multi-part upload and uploads up to 4.9TB as a single file adds Server Side Encryption (S3 managed keys) for all new S3 uploads Improves functionality and wording for eyrestore tool eyrestore displays bucket name hint when unable to access other environment eyrestore no longer requires both the database specified in both the –databases and –index args eyrestore with gpg backups should say download when restoring with gpz extension Updates fog-aws module from 0.3.0 to 1.2.1 Deprecates and removes unused aws-s3 gem
Medium
Logical backups are a critical path component of the Engine Yard stack, these changes have been carefully reviewed prior to preparing this release.
$ git diff next-release –name-only manifest/Gemfile manifest/Gemfile.lock
Repeat the backup and restore tests above for Postgres and MySQL on Solo and Cluster configurations.
# Description of your patch
Enhancements and bug fixes for eybackup/ey_cloud_server.
# Recommended Release Notes
Improves functionality and alerting for logical backups (eybackup). Corrects issue where mysql backups were recording database name in the backup Adds server identity to mysql backups to make them useful for replication-based restores Prevents and warns about overlapping backup runs; provides an override option off by default. cli improves backup errors when params specified incorrectly (leaving off db arg) listing backups with all now properly indexes multiple databases in environment OKAY messages only sent on first success after backup failure Error messages are printed to /var/log/engineyard/eybackup/#{dbname}.alert Backup Size and datestamps are printed to /var/log/engineyard/eybackup/#{dbname}.sizes which is capped at 100 lines new_backup option now backs up a specific db if listed, otherwise will back up all databases postgres restores perform analyze after load; adds a skip_analyze option adds multi-part upload and uploads up to 4.9TB as a single file adds Server Side Encryption (S3 managed keys) for all new S3 uploads Improves functionality and wording for eyrestore tool eyrestore displays bucket name hint when unable to access other environment eyrestore no longer requires both the database specified in both the --databases and --index args eyrestore with gpg backups should say download when restoring with gpz extension Updates fog-aws module from 0.3.0 to 1.2.1 Deprecates and removes unused aws-s3 gem
# Estimated risk
Medium
Logical backups are a critical path component of the Engine Yard stack, these changes have been carefully reviewed prior to preparing this release.
# Components involved
$ git diff next-release --name-only manifest/Gemfile manifest/Gemfile.lock
# Description of testing done
- Under the tpol-12.11 stack for Postgres and MySQL clusters
- Updated to the required stack
- Ran a backup
- Ran a restore
- Ran a GPG encrypted backup
- Ran a restore of an encrypted backup and confirmed the restore operation was blocked
- Ran a download of an encrypted backup and confirmed I was able to decrypt and restore
- Listed available backups
# QA Instructions
Repeat the backup and restore tests above for Postgres and MySQL on Solo and Cluster configurations.