However, if we make a backup in a cluster where the rs0 was made from configsvr. And try to restore the backup to a new cluster where rs0 is shardsvr, we will get an error during restore. So restore started and fails.
It would be great to do a topology-compliant check before starting a restore. Even more useful with replset-remapping.
The same with the status, list, and oplog-replay commands
In addition we can check if we have all the members of the cluster up&running, and accordingly warn or stop backup/restore operations.
Medium
PBM match replset by name only during restore.
However, if we make a backup in a cluster where the rs0 was made from configsvr.
And try to restore the backup to a new cluster where rs0 is shardsvr, we will get an error during restore. So restore started and fails.
It would be great to do a topology-compliant check before starting a restore.
Even more useful with replset-remapping.
The same with the status, list, and oplog-replay commands
In addition we can check if we have all the members of the cluster up&running, and accordingly warn or stop backup/restore operations.