This regards the enterprise cluster product
What would you say would be the best practice doing a full restore on a existing cluster?
Why do you need to empty the cluster before you do a restore and what do you think is the best practice making that operation as quick as possible? Drop all databases then full restore, or is there a better way? Will github issue #9040 and/or #9148 fix this with the “live restore”?
What would you say would be the best practice doing a restore to a existing cluster where one or more replication siblings are broken in such a way that the AA service don’t have shards to copy from remaining servers? I don’t want to take down/erase the entire cluster before restoring just because x% is not working.
When restoring, files are copied to all data nodes. Would it be possible to just copy files to 1 of X replication siblings and then let the AA service spread files to the data nodes? It would speed up the restore process a lot(!).
When restoring, why is Kapacitor subscriptions not restored?