Description
Hey guys,
I’m trying to move my RocketChat install to a new server. But when I move the database over It just keeps going back to the setup wizard… What i’ve tried so far based on what i’ve read:
mongodump -o ~/backup
tar cvf backup.tar ~/backup
scp backup.tar to new server
on the new server:
tar xvf backup.tar
mongorestore --drop ~/backup
So far… can’t get it to accept the old install…
Help!
Server Setup Information
Version of Rocket.Chat Server: 3.1.0
Operating System: Ubuntu 18.04 LTS
Deployment Method:
Number of Running Instances: 1
DB Replicaset Oplog:
NodeJS Version: 4.0.18
MongoDB Version:
Proxy:
Firewalls involved: UFW
Any additional Information
2 Likes
Hi @cadillacrick
I’m having the same issue, could you figure out a solution?
1 Like
I am facing this issue. Anybody know how to handle this issue, please tell us.
I am looking forward the answer
yazon
September 13, 2021, 2:14am
4
Really sad that thread after thread dies, year after year, and we’re left helpless. Good luck lads
reetp
September 13, 2021, 9:26am
5
Hmmm. I think you will find that since Rocket built a new Community team earlier this year all recent questions have been answered.
But this forum is Community support so the Community should be helping itself, not just relying on Rocket staff to answer every question.
In any event, restoring from backups has been answered multiple times.
You were answered here:
Hi.
You CANNOT backup 1.3 and restore to 3.14
That’s why I am trying to my latest backup take from v1.3.0 and restore it 3.14
NO. You cannot do this.
There are too many changes in the database. It will break your RocketChat.
You need to CAREFULLY upgrade your RocketChat 1.3.0 to 3.14
First you must Backup your version 1.3.x and make sure you know where the data is.
Next you must upgrade your 1.3.x installation. I suggest you do it in steps like this with a separate backup between each s…
For anyone else reading, you MUST restore to the exact same version that you saved from.
If you are trying to backup/restore to/from snaps note that the DB name is different in snaps to all other install types.