Proposal for improving the backup system

[javierav]

If we want to improve the backup system, we need to address the following issues:

• Set object key name for S3 backup #17
• Support for multiple backup schedules per service #30

Additionally:

• Run a new plugin trigger every time a scheduled backup runs. This will allow you to notify external systems of success or failure, for example.

The new commands would be as follows:

mysql:backup-auth

Using this command we can configure authentication BY BUCKET.

arguments

• <service>
• <bucket-name>
• <aws-access-key-id>
• <aws-secret-access-key>
• <aws-default-region>

Optional:

• <aws-signature-version>
• <endpoint-url>

mysql:backup-schedule

Using this command we can schedule the execution of a backup using a cronjob, assigning it a unique name.

arguments

• <service>
• <schedule-name>
• <schedule>
• <bucket-name>

Optional:

• [--use-iam]

mysql:backup-schedule-cat

This command cat the contents of the configured backup cronfile for the service.

arguments

• <service>
• <schedule-name>

mysql:backup-unschedule

This command deletes a scheduled execution.

arguments

• <service>
• <schedule-name>

mysql:backup-deauth

This command removes the authentication configuration from a bucket.

arguments

• <service>
• <bucket-name>

The commands for setting up encryption remain the same, as they must be global to the service and affect all backups generated.

@josegonzalez If you agree with the proposal, I can start the implementation for the MySQL plugin, which is what I am personally interested in.