CLI: restore backup

As an operations engineer, I want to be able to easily back up my instance data and configuration. I need this to reduce the load on the cluster when restoring an instance in the event of its death. I want to be able to back up my work machine without having to shell the node running the Tarantool instance. It is also important for me that the tools used and require the minimum possible additional configuration of the system in which it works.

Acceptance Criteria:

1. The administrator can view the list of instances on a specific node (similar to CLI: get coredumps with request)

2. The administrator has the ability to deploy a backup of an instance on a specific node.

3. Before deploying an instance backup, the Tarantool version on the target node is checked. * Here we focus on the distribution version, not a separate component! *

   1. If the version on the target node is higher than on the original one from which the backup was made, then the administrator will receive a corresponding warning and ask for confirmation to continue.
   2. If the version on the target node is lower than on the source, then the administrator is notified and the backup is not deployed.
   • Limitation: we do not handle the situation when the same instance is on another node. We warn the admin to check it yourself. *

4. Before deploying a backup of an instance on the target node, a check is made for the presence of this instance. Verification is performed by name or UUID. If the instance already exists, the administrator is asked to confirm that this instance will be replaced with a new one from the backup

5. The administrator has the ability to specify: expand only data or configuration + data.

   1. By default, the configuration + data is unrolled
   2. It is possible to deploy only data only if such an instance is already running on the target node.

Start by comparing the requested instance listing with the linked “CLI: get coredumps with request” issue and locating the existing CLI entry points for node and instance operations. Done means backups can be deployed with the specified version, instance-existence, replacement, and data-versus-configuration checks, including the required warnings and confirmations.