{"id":19469,"date":"2024-03-15T14:00:02","date_gmt":"2024-03-15T11:00:02","guid":{"rendered":"https:\/\/trueconf.com/blog\/?p=19469"},"modified":"2024-09-20T18:30:09","modified_gmt":"2024-09-20T15:30:09","slug":"how-to-transfer-trueconf-server-data-between-windows-and-linux","status":"publish","type":"post","link":"https:\/\/trueconf.com/blog\/knowledge-base\/how-to-transfer-trueconf-server-data-between-windows-and-linux","title":{"rendered":"How to migrate TrueConf Server from Windows to Linux"},"content":{"rendered":"

\"\"<\/a><\/p>\n

Our customers often decide to migrate from Windows to Linux due to a number of factors, including the ease of administration, malware attack mitigation and the need to reduce the cost of licensing. Besides, the software used in such cases should be backward compatible. At TrueConf, we value the time of our clients; so we made sure that it is easy to export data from one server to another.<\/p>\n

Important! Please take into account that chat history can be saved only if the public server name remains unchanged because the sender of messages is determined by the full TrueConf ID.<\/div>\n

<\/p>\n

Step 1. Server data export<\/h2>\n

To migrate successfully, you need to make sure that the new server installed on Linux and the current server on Windows are of the same version. Our Linux repository always includes only the latest version of the distro. We do not provide earlier versions of the server due to security reasons. So, we suggest updating TrueConf Server for Windows up to the latest version. Read this article<\/a> to learn how it can be done.<\/p>\n

Step 2. Server data export<\/h2>\n

To migrate TrueConf Server, you will need the registration key<\/a> of your TrueConf Server instance and the backup copies listed below.<\/p>\n

Please note that the migration of TrueConf Server from one machine to another will be impossible without these preliminary actions.<\/div>\n

Registration key<\/h3>\n

Due to security reasons, the registration key cannot be retrieved directly from the TrueConf Server control panel. The email with the key was sent to you when your TrueConf Server instance was registered. To find this email, you can use Server ID<\/a> (the ID will be displayed in the Summary \u2192 License info<\/strong> section).<\/p>\n

Main data<\/h3>\n

Registry<\/h4>\n

The registry stores the data about users, groups, aliases, conferences, streams, and server settings (LDAP, SIP\/H.323, WebRTC, federation parameters etc.).<\/p>\n

Open the terminal as the administrator and go to the following directory:<\/p>\n

cd \/d [backup]<\/pre>\n
where [backup]<\/code> is the directory to which TrueConf Server settings will be exported, for example:<\/p>\n
cd \/d D:\\backup<\/pre>\n
Next, run this command to export the registry:<\/p>\n
\"C:\\Program Files\\TrueConf Server\\tc_regkey.exe\" export \"\" registry.csv<\/pre>\n
Database<\/h4>\n
The database stores the information from the Reports<\/b> section<\/a> of TrueConf Server, including chat history.<\/p>\n
How to check the current port number<\/h5>\n
To make sure that the data is exported successfully, you need to specify the number of the port used for connecting to the database. The 5444<\/code> port is used by default.<\/p>\n
Since the port could be changed at some point in the past (e.g., the port could be set to 5432<\/code> after updating TrueConf Server from versions earlier than 5.2.9), run this command in the terminal to check the current port number:<\/p>\n
findstr port \"C:\\Program Files\\TrueConf Server\\database\\conf\\postgresql.conf\"<\/pre>\n
Export<\/h5>\n
Open the command line as the administrator and go to the following directory:<\/p>\n
cd \/d [backup]<\/pre>\n
where [backup]<\/code> is the directory to which the database will be exported, for example:<\/p>\n
Then, run this command to export data:<\/p>\n
\"C:\\Program Files\\TrueConf Server\\database\\bin\\pg_dumpall.exe\" -p 5444 -U postgres -c -f tcs.dump<\/pre>\n
Data export may take much time if a large number of chats is stored on the server.<\/div>\n
HTTPS settings<\/h4>\n
If you have configured HTTPS, the key and certificate files will be stored in the directory [installation_path]\\httpconf\\ssl<\/code> where [installation_path]<\/code> is the server installation path. Keep the backup copy of this directory in any location you find convenient, e.g., D:\\backup\\<\/code>.<\/p>\n
Additional data<\/h3>\n
Conference and call recordings<\/h4>\n
If conferences or calls are automatically recorded<\/a> on the server side, the files will be saved in the Recordings<\/code> folder by default (this folder can be found in the TrueConf Server working directory). To find the location of video files, check the Path<\/strong> field in the Recordings<\/strong> section of the TrueConf Server control panel.<\/p>\n
\"\"<\/a><\/p>\n
If you need to move them to a new server, just copy necessary recordings.<\/p>\n
Chat files<\/h4>\n
All chat files shared by the users of your server are saved in the files<\/code> folder in the TrueConf Server working directory by default. To find their exact location, check the Path<\/strong> field in the File Storage<\/strong> section of the TrueConf Server control panel. If you want to move the files to a new server, save a backup copy of this directory.<\/p>\n
\"\"<\/a><\/p>\n
Log files<\/h4>\n
If you submit a ticket to TrueConf technical support, you may need to attach log files (e.g., to analyze issues you had when using the previous instance of TrueConf Server).<\/p>\n
The log files are located in the TrueConf Server working directory. To export them, create a backup copy of all directories and files listed in the article about logs<\/a>.<\/p>\n
User avatars<\/h4>\n
Avatars of the users registered on your TrueConf Server instance are stored in the avatars<\/code> folder in the TrueConf Server working directory. Copy this directory to a convenient location on your server.<\/p>\n
Move all the files to the selected directory on the Linux machine, for example, in the directory \/home\/$USER\/backups\/<\/code>.<\/p>\n
Step 3. TrueConf Server installation<\/h2>\n
Check this article<\/a> to learn how TrueConf Server can be installed from a file and repository.<\/p>\n
Do not register TrueConf Server after installation.<\/div>\n
Step 4: Importing data to Linux<\/h2>\n
The data should be imported strictly in the order described below!<\/div>\n
Use the sudo<\/b> program to run the commands in administrator mode, Please make sure that the current user is added to the sudo<\/b> group (check the corresponding instructions for your OS on the Internet). You need to take into account that the sudo<\/b> may not be installed on your OS by default. To check, if this command is available, run sudo -V<\/code>.<\/div>\n
Database<\/h3>\n
How to check the current port number<\/h4>\n
To ensure successful data import, you will need to specify the port used for.connecting to the database. The 5444<\/code> port is used by default.<\/p>\n
Since the port could be changed at some point in the past (e.g., the port could be set to 5433<\/code> after updating TrueConf Server from versions earlier than 5.2.9), run this command in the terminal to check the current port number:<\/p>\n
grep port \/opt\/trueconf\/server\/etc\/database\/postgresql.conf<\/pre>\n
Import<\/h4>\n
Disable TrueConf services and restart the database service to close all active connections:<\/p>\n
sudo systemctl stop trueconf-web\r\nsudo systemctl stop trueconf-manager\r\nsudo systemctl stop trueconf-php\r\nsudo systemctl restart trueconf-db<\/pre>\n
Later, you will need to complete the following steps to import the database:<\/p>\n
    \n
  1. Open the terminal (if it was previously closed).<\/li>\n
  2. Copy the exported file to the directory with the database:\n
    sudo cp \/home\/$USER\/backups\/tcs.dump \/opt\/trueconf\/server\/bin\/database<\/pre>\n<\/li>\n
  3. Sign in as the postgres<\/b> user:\n
    sudo su postgres<\/pre>\n<\/li>\n
  4. Go to the database directory:\n
    cd \/opt\/trueconf\/server\/bin\/database<\/pre>\n<\/li>\n
  5. Run the import command and specify the current port<\/a>:\n
    .\/psql -p 5444 -f tcs.dump<\/pre>\n
    The data import may take much time, if a large number of chats is stored on the server.<\/div>\n<\/li>\n
  6. Sign out of the postgres<\/b> user account by running this command:\n
    exit<\/pre>\n<\/li>\n<\/ol>\n
    Registry<\/h3>\n
    To import the registry from a backup file, you will need to delete the lines that are not compatible with Linux. To do it, run the following commands in the terminal:<\/p>\n
    sed -i '\/install_version\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,Working Directory\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/ConfDefault,Working Directory\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,Executable Path\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,Recordings Path\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,Ffmpeg Path\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,Push Script\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,File Storage Path\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,version\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration,DB Connection String\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Configuration\\\\ConfDefault,Working Directory\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/WebManager,server_dir\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/WebManager,db_port\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/WebManager,group_security\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/WebManager,group_admin\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/WebManager,client_path\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/Transceivers\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/WebManager\\\\API\\\\AccessTokens\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i '\/WebManager\\\\API\\\\RefreshTokens\\\\\/d' \/home\/$USER\/backups\/registry.csv\r\nsed -i 's\/ffmpeg\\.exe\/\\\/opt\\\/trueconf\\\/server\\\/bin\\\/ffmpeg\\\/ffmpeg\\\/\/' \/home\/$USER\/backups\/registry.csv<\/pre>\n
    If your new server has a different IP address, run the following command in the terminal (this command uses blank spaces as delimiters):<\/p>\n
    sed -i \"s x.x.x.x y.y.y.y \" \/home\/$USER\/backups\/registry.csv<\/pre>\n
    where:
    \nx.x.x.x<\/code>\u00a0is the previous IP address with dots (.) escaped, for example, 192.168.0.1<\/code>.
    \ny.y.y.y<\/code> is the new IP address where dots are not escaped, for example: 192.168.1.1<\/code>.<\/p>\n
    Then import the registry settings with this command:<\/p>\n
    sudo \/opt\/trueconf\/server\/bin\/vcs\/tc_regkey import \"\" \/home\/$USER\/backups\/registry.csv<\/pre>\n
    When all the data is imported, restart the following TrueConf services by running these commands consecutively:<\/p>\n
    sudo systemctl restart trueconf-db\r\nsudo systemctl start trueconf-manager\r\nsudo systemctl start trueconf-web\r\nsudo systemctl start trueconf-php<\/pre>\n
    LDAP<\/h3>\n
    If integration with LDAP was previously configured, you will need to restore default settings because in Windows and Linux, different default values are used for LDAP parameters. To do it, you will need to open the TrueConf Server control panel, go to the LDAP\/Active Directory \u2192 LDAP settings \u2192 Advanced<\/strong> section, and click the Default<\/strong> and Apply<\/strong> buttons consecutively. If you specified some other parameters in the Advanced<\/strong> section, you will need to specify them again and save settings.<\/p>\n
    If you do not take these steps, there may be user authorization problems.<\/em><\/div>\n
    Files<\/h3>\n
    Move the files to the default directory \/opt\/trueconf\/server\/var\/lib\/files<\/code>.<\/p>\n
    Name length<\/h4>\n
    When moving files, one should keep in mind that some files may not be saved. This problem occurs due to different OS restrictions on file name length. The NTFS file system used in Windows supports file names with up to 256 characters encoded in UTF-16. The ext4 file system, which is usually used in Linux, supports at most 255 bytes in UTF-8 encoding. In other words, it can support names with up to 255 Latin characters or 127 characters of other alphabets (e.g., Cyrillic alphabet).<\/p>\n
    So, the file with a non-English name may not be saved due to the restrictions imposed by the Linux kernel.<\/p>\n
    Solution<\/b><\/p>\n
    To fix this issue, you may use a different file system for Linux or save at-risk files (the ones with long names) so that they could be later sent to users.<\/p>\n
    SCP use<\/h4>\n
    The following errors may occur when the files are moved with the help of SCP (Secure Copy Protocol):<\/p>\n