Bug 1188147

Feature Overview:
This feature has arose due to recent engine database corruptions where users did not have any database backup. The goal here is to cause users to do backup and review their backup options and thus reduce engine downtime on engine corruptions cases. 

Raising awareness to the necessity of backups and providing simple options using existing tools or recommending using more advanced solutions. This is the most pressing matter at hand

Scope of this Specification:
In scope:
- Ensuring users follow best practice.
- Enhancing that best practice as necessary.
- Backup of engine database remote\local.
- Backup of essential configuration files.
Out of scope:
- Creating a VM backup solution.
- automatic backup options.

User Characteristics:
- Small scale deployments that don’t have a backup solution.
- Backup of simpler usage cases.
- User that don’t have external database management.

Assumptions:
- Engine-backup already provides part of the needed functionality.
- We need to support cases where remote DB is used.
- Raising awareness of user to backups will cause increase usage of backup.

Constraints:
- Engine must not have downtime for backup if possible.
- Sufficient disk storage can be provided by user.
- DWH\Reports also need to be optionally backed up and would require more disk space. 
- I\O and network performance best practices may be limited and cause issues.
- Detailed documentation is critical to allow users to make the right choices.
- We do not want to support complex backups since it is out of the oVirt scope.

Dependencies:
In order to allow external backup for other providers, we need to provide the backup tool as the start point of backup process.

Performance:
- The backup process should not cause failures in connections to hosts or storage and should not cause failure of tasks (even if performance is affected). Stress testing should be done to define minimal requirements to backup over the network and this should be added to best practices. 
- Backup process should have a low priority in the system (low nice).
- Lower footprint should be a priority over fast completion.
- Restore time should also be a priority in default backup formats and options. 

Capacity:
- The backup should not start if disk size is not sufficient for it’s completion. 
- Two backup instances may not run at the same time.