Flussonic Media Server documentation

DVR in a cloud

Storing archives in a cloud Anchor Anchor x2

Flussonic can record streams' archives to remote HTTP storages — Amazon S3 and OpenStack Storage (Swift).

By default, Flussonic writes a stream to the storage segment by segment, and this may be expensive. To make it more affordable, use the copy option that Flussonic offers (read later on this page).

To store a stream on Amazon S3, configure it like this:

stream chan0 {
  dvr s3://AWS_ACCESS_ID:AWS_SECRET_KEY@s3.amazonaws.com/mybucket 10G;
}

To store a stream in OpenStack Storage (Swift), configure it like this:

stream chan0 {
  dvr swift://user=video:streamer&password=SECRETPASS&@swift-storage.local/movies 10G;
}

To store a stream in Akamai Storage, configure it like this:

stream chan0 {
  dvr akamai://keyName:keyValue@akamaihd.net/cpCode/dvr 10G;
}

Copying video archives to the cloud Anchor Anchor x2

The copy option helps significantly reduce the number of times that Flussonic accesses the disk on a cloud.

Flussonic first accumulates recorded video data on a local disk (in the specified directory). Then, once an hour, it copies the data to the cloud.

Specify the copy option like this:

stream chan0 {
  dvr /storage copy=s3://AWS_ACCESS_ID:AWS_SECRET_KEY@s3.amazonaws.com/mybucket 10G;
}

Recording to the network storage when a stream was migrated Anchor Anchor x2

The group of Flussonic servers can work with the same storage, keeping all records in one directory. When a stream migrates from one server to another, the new server will catch the recording made by the old server.

The easiest way to migrate a stream is by using the SQL API:

mysql> update streams set server='srv03.cdn.local' where name='bunny2';
Query OK, 1 row affected (0.02 sec)

Flussonic completely transfers the configuration of the stream to the new server, and the archive will continue to work automatically. More about SQL API.

Important! Multiple servers must not record the same stream at the same time.