Hello dears,
i have an issue but i actually dont know is it related to commvault or the mongo vendor or a cluster configuration issue .
we have a mongo cluster with a replica set configured.
we are performing backups successfully without any issues.
we are trying to restore the mongo db to a different cluster with same configuration as production,
so i have performed out of place restore multiple times with these configuration:
- picked the destination cluster and checked the automatic restore.
- picked the destination cluster and checked the automatic restore and changed the replicaset name to the destination cluster .
- restored files only
all above scenarios succeeded but with the below error
Data files have been successfully restored. But, all the mongodb servers could not be started with the restored data.
when we check the cluster after restore we see that the db is trying to connect to the prod servers not the destination servers.
is this the normal behaviour and the mongo admins should do some manual work to fix this ?
or there are some configuration i should apply during the restore?
Best answer by Damian Andre
View original