sharded mongodb 3.6 replicaset members cannot start after restore

[Steve Yoon]

I am attempting to restore file system backup into new sharded mongodb 3.6.

I copied all necessary data files into each member.

It looks like they are failing to start because shardIdentity is pointing at older configsvr replicaset.

I think recoverShardingState paramter used to be used to get around this problem but it has been removed apparently. (Document still refers to it)

https://docs.mongodb.com/manual/tutorial/restore-sharded-cluster/#clear-per-shard-sharding-recovery-information

What would be the best course of action at this point?

* update shardIdentity document manually with correct configsvr replicaset -> failed to initialize shard

* remove shardIdentity document -> throws error: "Cannot accept sharding commands if sharding state has not been initialized with a shardIdentity document"

[Abhijit Jadhav]

Quickest and easiest way to restore sharded cluster would be to use mongodump and mongorestore from/to mongos rather mongod. Or use Ops manger to restore cluster.

If you have no other options I mentioned above then I will send you unsupported method to get it done manually.

Regards,

Abhi

--
You received this message because you are subscribed to the Google Groups "mongodb-user"
group.
 
For other MongoDB technical support options, see: https://docs.mongodb.com/manual/support/
---
You received this message because you are subscribed to the Google Groups "mongodb-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to mongodb-user...@googlegroups.com.
To post to this group, send email to mongod...@googlegroups.com.
Visit this group at https://groups.google.com/group/mongodb-user.
To view this discussion on the web visit https://groups.google.com/d/msgid/mongodb-user/23506bac-d50d-46d6-b525-4199960ca65b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Regards,
Abhijit

[Steve Yoon]

Thanks Abhijit,

I already have file snapshot backup files so mongorestore or ops manager are not valid options.

I think I managed to get around it by updating shardIdentity manually.

Could you send me unsupported method to restore file snapshot backup for sharded cluster?