Hello @Divyanshu_Soni,
thanks for the update. mongodump is not the most efficient or scalable backup approach to use, as it requires all data to be read and dumped via the mongod process. A mongorestore has to recreate all data files and rebuild indexes, so will also take longer to restore than a backup approach such as filesystem snapshots.
If your data to be backed up is significantly larger than RAM, the backup and restore time will increase with the growth in your data set.
If you are backing up a sharded cluster, there are more moving parts to coordinate and mongodump is not a viable backup approach if you are also using sharded transactions in MongoDB 4.2+.
Concerning the concrete error I like to pass this to the DBAs around.
Cheers,
Michael