Open patricklarochelle opened 6 years ago
Hello @patricklarochelle,
This sounds related to issues people are seeing with non-replset-based Config Servers (SCCC mode) in 3.2 and older. There is an issue here to re-test the code with the old style config servers: https://github.com/Percona-Lab/mongodb_consistent_backup/issues/203 that I plan to action shortly.
Importantly, due to the nature of non-replset-based (SCCC mode) config servers not having any consistent changelog/oplog, the support for SCCC mode may be removed/deprecated in the future as we cannot guarantee a point of consistency without an oplog. Currently we "do our best" in SCCC mode but consistency is not guaranteed 100%. Seeing our tool is designed to create "consistent backups" this is of course confusing. See more about this here: https://github.com/Percona-Lab/mongodb_consistent_backup/issues/233.
As SCCC mode is supported as of today I will test and attempt to fix this problem, however I do suggest that you consider moving to 3.2+ with CSRS (replset-based) config servers as the support for SCCC may go away, plus there are tonnes of other benefits to using CSRS!
Stay tuned!
Tim
Running on : CentOS Linux release 7.3.1611
With MongoDB version: 3.0.11
With mongodb-consistent-backup version: mongodb-consistent-backup version: 1.2.0, git commit hash: unknown Python version: 2.7.5 Python modules: Fabric: 1.14.0 pymongo: 3.5.1 multiprocessing: 0.70a1 yaml: 3.12 boto: 2.48.0 filechunkio: 1.8
execution failing within first few connection steps:
YML file is attached.