Skip to content

Flussonic Media Server migration

When migrating Flussonic Media Server from one server to another, you should copy the config and license files. It is also possible to transfer the archive.

Warning

Do not move executable files and installed libraries. Use the package manager to install Flussonic Media Server on the new server.

Migrating the config ang license

To migrate the configuration:

  1. Install Flussonic Media Server on the new server.

    curl -sSf https://flussonic.com/public/install.sh | sh

  2. Move the following files from the old server to the new one using one of the methods described later on this page:

    • /etc/flussonic/flussonic.conf — the main configuration file.
    • /etc/flussonic/license.txt — license.

  3. Stop Flussonic Media Server on the old server:

    service flussonic stop

  4. Start on the new server:

    service flussonic start

Ways to transfer files:

Transferring the configuration using web interface

Go to the Config -> Settings tab both on the new and the old server. To download the configuration file, click the Download Config button. To upload configuration file to the new server, click the Upload Config button.

flussonic ui

Your license key can be viewed in the client area on the License keys tab.

Transferring the configuration using SCP

SCP (Secure CoPy) is a program for transferring files over a network between hosts. It uses SSH for data transfer, including authentication and security protocols that are implemented in SSH.

To copy the configuration and license files from one remote server remote.host1 to another remote server remote.host2, execute the following command:

scp user@remote.host1:/etc/flussonic/flussonic.conf user@remote.host2:/etc/flussonic/
scp user@remote.host1:/etc/flussonic/license.txt user@remote.host2:/etc/flussonic/

Transferring configuration using USB media

If you want to transfer configuration files using any USB media, use the following instruction.

Mounting USB

First, create the mount point (directory):

mkdir -p /mnt/usb

Insert the USB flash drive into the USB port and find the name of the attached device:

fdisk -l

The result of this command will look like:

Disk /dev/sdb: 4008 MB, 4008706048 bytes
118 heads, 53 sectors/track, 1251 cylinders, total 7829504 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x74a37a4d

Device    Boot      Start         End      Blocks   Id  System
/dev/sdb1   *          63     7829503     3914720+   b  W95 FAT32

In this example the device name is /dev/sdb1.

Use it to mount the device:

mount /dev/sdb1 /mnt/usb

Copying the configuration

cp /etc/flussonic/flussonic.conf /mnt/usb/flussonic.conf
cp /etc/flussonic/license.txt /mnt/usb/license.txt

After copying, do not forget to unmount the drive:

sudo umount /dev/sdb1

Installing the configuration on a new server

Install Flussonic Media Server on the new server:

curl -sSf https://flussonic.com/public/install.sh | sh

Create a directory in which the USB-drive will be mounted:

mkdir -p /mnt/usb

Insert the media into the USB port and find the name of the device:

fdisk -l

Mount:

mount /dev/sdb1 /mnt/usb

Transfer the configuration files:

cp /mnt/usb/flussonic.conf /etc/flussonic/flussonic.conf
cp /mnt/usb/license.txt /etc/flussonic/license.txt

Launch Flussonic Media Server:

service flussonic start

Done!

Migrating archive

Use the replication mechanism to migrate the archive.

Archive migration is only possible in a normal operation mode, that is, when the old server continues to work simultaneously with the new one for some time. Note that you will need a license allowing at least one more server for that. For example, you cannot run multiple instances of Flussonic Media Server at the same time if your license key is valid for only one server.

If the migration occurs due to a malfunction of the old server, then the archive will not be transferred. Just start recording the archive again on the new server. To avoid losing the archive in the future, set up replication in advance.