Chat+ backup and move

ISO someone to help move my Chat+ mongod database to another server.

I've got the second server setup with a new chat install and have backed up the room data.

The problem I'm having is restoring the data using "mongodump --out /data/backup/," errors like

 "don't know what to do with file "mot27/rocketchat_room.metadata.json", skipping..."

ManOfTeal.COM a Proud UNA site, six years running strong!
Quote · 24 Oct 2017

Look at this; anything here that may help?

https://github.com/RocketChat/Rocket.Chat/issues/7437

Geeks, making the world a better place
Quote · 25 Oct 2017

 

Look at this; anything here that may help?

 Not really, but thanks for looking.

I will pay someone.

I'm afraid I won't get help here or UNA site.

Off to search for someone.

ManOfTeal.COM a Proud UNA site, six years running strong!
Quote · 25 Oct 2017

We use the following commands to dump and restore our demo every half an hour:

- stop the server

- dump the database:

mkdir mongo_rocketchat_db_dump; mongodump -d rocketchat -o mongo_rocketchat_db_dump

- move mongo_rocketchat_db_dump folder to the new server

- restore from backup:

mongorestore ./mongo_rocketchat_db_dump
Rules → http://www.boonex.com/terms
Quote · 25 Oct 2017

 Thanks!!!!

- dump the database:

mkdir mongo_rocketchat_db_dump; mongodump -d rocketchat -o mongo_rocketchat_db_dump

 The "rocketchat" above; is that generalized or the actual name of the chat?

My chat is "mot27" so do I use that?

ManOfTeal.COM a Proud UNA site, six years running strong!
Quote · 25 Oct 2017

Yes, if you have different monodb database name, then you need to change it like you've highlighted.

Rules → http://www.boonex.com/terms
Quote · 30 Oct 2017

@AlexT solution will work, but you will end up with a folder that has lots of json files which you will need to archive all of them before you can transfer the dump file to another server and restore it..

The alternative is to backup your mongodb and archive the files on the fly:

Lets call source db:  HR_PROD
and target db:           HR_STAGE


>> Backup
Now, lets backup HR_PROD on server-A and restore it on server-B with a different name:
Server-A> mongodump -d HR_PROD --gzip --archive='HR_PROD_BACKUP.gz"


>> Restore backed db and rename it to something else:
Server-B> mongorestore -d --nsFrom "HR_PROD" --nsTo "HR_STAGE"  --drop --gzip --archive="HR_PROD_BACKUP.gz"

Note: I added the parameter --drop which means drop the target db if it already exists and then restore.

If you like my answer, share the love & give it a thumbs up :)

Cheers.

Quote · 1 Nov 2017
 
 
Below is the legacy version of the Boonex site, maintained for Dolphin.Pro 7.x support.
The new Dolphin solution is powered by UNA Community Management System.