Juju 2.4.3, controller running on Trusty.
When I try to create a backup of the controller model:
~$ juju create-backup -m controller
ERROR while creating backup archive: while dumping juju state database: error dumping databases: error executing "/usr/lib/juju/bin/mongodump": ERROR: unrecognised option '--sslAllowInvalidCertificates'; ; Export MongoDB data to BSON files.; ; options:; --help produce help message; -v [ --verbose ] be more verbose (include multiple times; for more verbosity e.g. -vvvvv); --version print the program's version and exit; -h [ --host ] arg mongo host to connect to ( <set ; name>/s1,s2 for sets); --port arg server port. Can also use --host ; hostname:port; --ipv6 enable IPv6 support (disabled by ; default); --ssl use SSL for all connections; -u [ --username ] arg username; -p [ --password ] arg password; --authenticationDatabase arg user source (defaults to dbname); --authenticationMechanism arg (=MONGODB-CR); authentication mechanism; --dbpath arg directly access mongod database files ; in the given path, instead of ; connecting to a mongod server - needs ; to lock the data directory, so cannot ; be used if a mongod is currently ; accessing the same path; --directoryperdb each db is in a separate directly ; (relevant only if dbpath specified); --journal enable journaling (relevant only if ; dbpath specified); -d [ --db ] arg database to use; -c [ --collection ] arg collection to use (some commands); -o [ --out ] arg (=dump) output directory or "-" for stdout; -q [ --query ] arg json query; --oplog Use oplog for point-in-time ; snapshotting; --repair try to recover a crashed database; --forceTableScan force a table scan (do not use ; $snapshot);
Hence, we have no backups of this (production) environment.
I'm pretty sure this will be additional flags for backup being passed to an older mongo (probably 2.4 in trusty).