Export data for updated OO on an other VM

Do you want to: Ask a how-to question
OO version production:
ONLYOFFICE Community Server 11.5.975
ONLYOFFICE Control Panel 3.0.385
ONLYOFFICE DocumentServer-EE 6.4.2
ONLYOFFICE XMPP Server 11.0.63
OS: Windows server 2019 1809 build 17763.7678
Browser version: Chrome 140.0.7339.208 (64bit)

OO version development:
ONLYOFFICE Community Server 12.7.1304
ONLYOFFICE Control Panel 3.5.434
ONLYOFFICE DocumentServer-EE 9.0.4
ONLYOFFICE XMPP Server 12.0.92
OS: Windows server 2022 21H2 build 20348.2932
Browser version: Chrome 140.0.7339.208 (64bit)
Type of installation of the Document Server (docker, deb/rpm, exe, please point us to the installation guide that you used as well): ONLYOFFICE_Workspace_Win-install.latest.exe (ver 24.12.840.0) and onlyoffice-documentserver-ee.exe (ver 9.0.4.50) Installing ONLYOFFICE Docs Enterprise Edition for Windows on a local server

Additional information:
Hello,
I have an outdated version of OnlyOffice in production. The company has just renewed the license, so I can now update it.

I cloned my production environment to check compatibility before updating, and I encountered several issues related to the fact that there are multiple versions installed on it. So I started with a freshly installed VM running Windows Server 2022 (see specifications in the description).

From my clone of the production VM, I ran a backup simulation to export the data to my new VM. It took about 2 hours and I ended up with a .tar.gz archive that is 111 GB. Is this normal, given that we don’t have any videos, 50 simultaneous connections and only text files? I also realized that I don’t have full access to the control panel until I add the license file. Is having two OO servers running likely to cause me any problems?

Before taking action, I wanted to know if there are any other preparatory tasks to be done? I have another question. I’m taking advantage of this update to upgrade to Windows Server 2022, but could I push it to Windows Server 2024?

I am available if you need more details.

Best regards,

Hello @Jules

Document Server is already a part of Workspace package. I recommend installing Workspace Enterprise directly, that way you won’t have 2 separate Document Server, which may cause issues indeed.

However, if you have options to clone machines, I’d rather suggest cloning old machine and trying to update it via Control Panel. There is huge leap in versions, database schemas are now a little different, which also may cause issues on most recent available version of Workspace and its components.