bizflycloud/bizfly-backup

BizFly Cloud backup service.

bizfly-backup's Issues

Authentication with Public API

Each backup-agent is provided access key and secret key. Use these keys with agent ID to authenticate with Public before perform any task.

List/Backup/Restore at machine side

Some cases, use want to perform action (backup and restore) in his machine instead of via API or dashboard. We should support this case.

Perform backup as schedule policy

The schedule policy is get from public api as issue #13 .

From these schedule policy, backup-agent will perform backup for each directory at pattern time.

For example:

• Directory /etc/mysql has cron pattern 0 * * * * (every hour at 0 minute)

Subscribe to MQTT Server then perform backup and restore

In some cases, user want to manual backup or restore through API/ Dashboard. Backup-Agent subscribe to a topic in MQTT Server then perform these actions.

Update machine information when start agent

When start backup-agent in a machine, we need to update the machine information such as (OS type, os version, backup agent version,...).

Add more environments to CI

Currently, bizfly-backup is only built/tested on Linux, we need to setup CI for other environment:

• Windows
• Mac OSX

Get configuration file from Public API

Backup agent get configuration file from Public API when

• start agent
• Reconnect after network disconnected

Only download the agent when the newer version available

When use the installation script, we need to check if the agent is installed or not. If the agent is already installed, we need to check the newer version is available and then upgrade the current installed agent.

Setup Gihub Action

Add Github Action to run CI.

Requirements

• vernemq image (See docker-compose.yml for details configuration)

Subscribe to MQTT Server and change configuration

An user can change config at centralized API, then the API publish a message to MQTT Server.
Backup agent subscribe to a topic in MQTT Server then change the local configuration file.