Enhancements and server role alignement

[ulvida]

Sister backuppc_server role has evolvedfor a better management of all BackupPC parameters, particularly the description of shares backed up and inclusion/exclusion options.

Morover, it seemed more logical to adopt a single uniform syntax for name variables in backuppc config.pl file.

Finally, an idea that emerged documenting v2.1.X version was developed:no more backuppc_scripts flag, scripts are used when paths to files are defined. (Changes quite some code in therole, however)

[andrespias]

Reading Readme.md...

Behaviour of scripts and db backups are different for mysql and pgsql. Particularly, for MySQL you must add yourself the scripts, por instance pre_dump.sh and post_dump.sh that do the job of dumping databases, while for PostgreSQL these scripts are built form templates (and they dump only a database).

Can't we make the role build these scripts from templates for Mysql?

[ulvida]

Reading Readme.md...

Behaviour of scripts and db backups are different for mysql and pgsql. Particularly, for MySQL you must add yourself the scripts, por instance pre_dump.sh and post_dump.sh that do the job of dumping databases, while for PostgreSQL these scripts are built form templates (and they dump only a database).

Can't we make the role build these scripts from templates for Mysql?

Certainly the present behaviour to automate databases backups, limited and different for mysql and pgsql, is not very satisfactory. But this was not in the scope of this refactor and enhancement, which was to complete backuppc config, and clearly separate server and client roles.
Maybe the best could be to let it to a further version, and to have a better design of the feature: one, several or all databases, create user for backup or given by playbook, optional template of scripts, ...