Hi Maxime,
Thanks for all that information.
- I’ll say that I would like to make a backup for the database from a remote server because I don’t have much space left on the server to store a local backup.
So, from a newer remote server running Mongo 5.x I run the following command
mongodump --host IP_server --db ping --out /home/mongos/mongo2x-`date +"%m-%d-%y"` --gzip
and I got this error:
Failed: can't create session: could not connect to server: server at 208.85.216.45:27017 reports wire version 0, but this version of the Go driver requires at least 2 (MongoDB 2.6)
I understand that I need to have Mongo 2.6 running to use the command, but I’m running 2.0.7 so I’m not sure what are my options to make a backup and store that on a remote server.
Here are my answers to your questions:
- The server is running Debian 6.0.5 so I’m not sure how to know if I’m running
mongod. Here is what I see when I try to check if the service is running.
Checking status of database: mongodb running.
- The DB is 47.93GB so far
- Is there a way I can check if it is a replica?
I went to the/etc/mongodb.conffile
and almost at the bottom I see
master = true
sourse = server2_hostname
Then I went to the config file of that other server and it has this:
slave = true
source = server1_hostname
Tho the replSet value is commented out so it does not have a name.
Does this mean that the replicaSet is active and the DBs are mirrored?
If the data is mirrored between the 2 servers, what would be the process to update ? should try to update the mongodb version on the second server (slave) to at least 2.6 to use mongodump ?
Thanks for your help with this.