Restore not possible

Hello dear team
I have a problem restoring the backup. I have backed up a running Onlyoffice and am now trying to restore this backup in a new Onlyoffice on a different machine. This also starts the restore, goes up to 100% and then nothing is restored?

i solved the problem, restore was working, but now i cant login anymore, i copied the machinekey from the old to the new server and restartet it, but still not working. what did i wrong?

Hello @mediabw

i copied the machinekey from the old to the new server and restartet it, but still not working.

Please try it again, but change machinekey value before the restoring. Will the situation change? Additionally, please make sure that both portals are using the same component versions (Community server, Control Panel, etc.)

Hi Alexandre, thanks for your help

I tried this, copying the machine key before restoring, but it doesnt work. Same problem with the passwords.

What i saw, that in the original machine docker looks like this:

                                  NAMES

d29998df1ef7 onlyoffice/communityserver:latest “/app/run-community-…” 2 months ago Up 3 weeks 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 3306/tcp, 5280/tcp, 9865-9866/tcp, 9871/tcp, 9882/tcp, 0.0.0.0:5222->5222/tcp, :::5222->5222/tcp, 9888/tcp onlyoffice-community-server
31bed6c63673 onlyoffice/documentserver:latest “/app/ds/run-documen…” 2 months ago Up 3 weeks 80/tcp, 443/tcp onlyoffice-document-server
032617b2b96e onlyoffice/elasticsearch:7.16.3 “/bin/tini – /usr/l…” 2 months ago Up 3 weeks 9200/tcp, 9300/tcp onlyoffice-elasticsearch
2d5174ff9e6e onlyoffice/controlpanel “/var/www/onlyoffice…” 11 months ago Up 3 weeks 80/tcp, 443/tcp onlyoffice-control-panel
36a74a6bd656 mysql:5.7.21 “docker-entrypoint.s…” 5 years ago Up 3 weeks 3306/tcp onlyoffice-mysql-server
91f6a1c93f66 onlyoffice/mailserver “/bin/sh -c 'export …” 5 years ago Up 3 weeks 0.0.0.0:25->25/tcp, :::25->25/tcp, 0.0.0.0:143->143/tcp, :::143->143/tcp, 3306/tcp, 0.0.0.0:587->587/tcp, :::587->587/tcp, 8081/tcp onlyoffice-mail-server

The new one

2a4c709b1ec8 onlyoffice/communityserver:12.5.2.1848 “/app/run-community-…” 2 weeks ago Up 23 minutes 0.0.0.0:80->80/tcp, :::80->80/tcp, 0.0.0.0:443->443/tcp, :::443->443/tcp, 3306/tcp, 5280/tcp, 9865-9866/tcp, 9871/tcp, 9882/tcp, 0.0.0.0:5222->5222/tcp, :::5222->5222/tcp, 9888/tcp onlyoffice-community-server
6c1d7fde03ec onlyoffice/controlpanel:3.5.0.516 “/var/www/onlyoffice…” 2 weeks ago Up 23 minutes 80/tcp, 443/tcp onlyoffice-control-panel
e287a936a82d onlyoffice/documentserver:7.4.1.1 “/app/ds/run-documen…” 2 weeks ago Up 23 minutes 80/tcp, 443/tcp onlyoffice-document-server
4d4ad7eec017 onlyoffice/elasticsearch:7.16.3 “/bin/tini – /usr/l…” 2 weeks ago Up 23 minutes 9200/tcp, 9300/tcp onlyoffice-elasticsearch
dc0bf3270e46 mysql:8.0.29 “docker-entrypoint.s…” 2 weeks ago Up 23 minutes 3306/tcp, 33060/tcp onlyoffice-mysql-server

The Problem is, if i don’t have any informations about the old versions, i can not recover the backup, is that true?

Best regards

Michael

Hello @mediabw
Do you have access to your ‘old’ portal? You can check out versions of installed components in the Control Panel of the portal (Update tab).
As I mentioned before, both portals should have the same component versions for successful backup restore process.

If the ‘old’ portal’ has older versions than new one, there’re two possible ways to resolve the situation:
A. Update ‘old’ portal to the latest versions. This way portal components will match to the new portal.

B. Install on the new server outdated components. We store old docker images on the DockerHub, so this option is possible too. Previously we discussed this option in this thread, please check out step-by-step guide: Old version Enterpris with DocServer 6.0 for Docker, installation - #4 by Alexandre
The guide was provided for Enterprise version of Workspace, so you have to make a few changes in case of Community version:

NB! We always recommend preparing whole server backup before any server-side actions.