Skip to content

DVR in a Cloud

Storing archives in a cloud

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 chan1 {
  url fake://fake;
  dvr s3://minioadmin:minioadmin@minio:9001/test 10G;
}

To store a stream on Amazon S3 and enable access via HTTPS, configure it like this:


stream chan5 {
  url fake://fake;
  dvr s3s://minioadmin:minioadmin@minio:9001/test 10G;
}

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


stream chan2 {
  url copy://chan1;
  dvr swift://user=test:tester&password=testing@swift:8080/test 10G;
}

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


stream chan3 {
  url copy://chan1;
  dvr akamai://keyName:keyValue@akamaihd.net/cpCode/dvr 10G;
}

Copying video archives to the cloud

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 moves the data to the cloud.

Specify the copy option like this:


stream chan4 {
  url copy://chan1;
  dvr /storage copy=s3://minioadmin:minioadmin@minio:9001/test 10G;
}

Learn more

Recording to the network storage when a stream was migrated

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.

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

Caution

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

See also