How to Backup Reolink Duo 2 PoE 4K 180° Panoramic Camera to IDrive e2

Ultra-wide dual-sensor 4608x1728 panoramic camera with single-stream FTP upload. Follow our step-by-step setup guide below to stream footage directly into AWS S3, Cloudflare R2, or Backblaze B2 via FTP/S with Rilavek as the pipe, zero on-prem NVR required.

Reolink Duo 2 PoE 4K 180° Panoramic Camera - Product View
Zero NVR Vulnerability

Your Reolink Duo 2 PoE uploads footage offsite in real time. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.

S3-Native Retention

Store Reolink Duo 2 PoE recordings on your own terms. Apply automated bucket lifecycle rules to roll over or archive clips after 30, 90, or 365 days.

Direct Streaming Bridge

Rilavek ingests native FTP/S streams from your Reolink Duo 2 PoE and writes them directly into multipart S3 PUTs with zero disk writes.

Reolink Duo 2 PoE 4K 180° Panoramic Camera
Reolink Duo 2 PoE 4K 180° Panoramic Camera
FTP/FTPS
Rilavek
Rilavek Bridge
S3 API
IDrive e2
IDrive e2

Step-by-Step Setup Guide for Reolink Duo 2 PoE 4K 180° Panoramic Camera

Follow these 8 steps to select your cloud provider, provision your object storage, configure Rilavek’s Data Store, Sender, and Ingestion Pipe, enter your camera firmware settings, verify ingestion, and establish automated S3 retention rules.

01

Select Your Cloud Storage Provider

Choose where you want to store your Reolink surveillance footage. Selecting a provider customizes the bucket setup steps, endpoint URLs, and API key instructions in Step 2.

02

Set Up Your IDrive e2 Bucket & Generate API Keys

Configure your target bucket and API credentials inside IDrive e2 so Rilavek can stream motion clips and continuous video directly into your storage.

1

Create an IDrive e2 Storage Bucket

In the IDrive e2 Dashboard, select Create Bucket . Pick your geographic region and keep file access private.

2

Generate an Access Key Pair

Navigate to Access Keys > Create Access Key . Assign Read/Write permissions restricted to your surveillance bucket.

3

Copy Endpoint URL and Credentials

Copy your Access Key ID, Secret Key, and regional S3 endpoint URL. IDrive e2 endpoints embed your assigned region automatically in the host name.

03

Add Your Data Store in Rilavek

In your Rilavek dashboard, navigate to Data Stores > New Data Store, select your provider, and enter your S3 credentials. Rilavek verifies the connection with an automated write-probe before saving.

Grant minimal S3 permissions only.Rilavek needs minimal, write-focused actions and nothing more.
Rilavek Dashboard · Data Stores > New S3 Data Store

Add New Data Store

S3 Compatible
Reolink Surveillance Storage
https://<account_id>.idrivee2-<region>.com
AKIAIOSFODNN7EXAMPLE
••••••••••••••••••••••••••••••••
How to create →
cctv-reolink-recordings
Automatically executes multipart write-probe test before saving.Save Data Store
Fig 1: Add New S3 Data Store configuration in the Rilavek console.
04

Create a Camera Sender in Rilavek

Go to Senders in the Rilavek sidebar and click New Sender. A Sender represents the hardware identity of your Reolink Duo 2 PoE 4K 180° Panoramic Camera and generates a dedicated device-level password.

Rilavek Dashboard · Senders > Create New Sender Modal

Create New Sender

Reolink Duo 2 PoE 4K 180° Panoramic Camera
cam_duo2poe

Must be at least 6 characters, lowercase, start with a letter/underscore, and contain only letters, numbers, hyphens, or underscores.

security@reolink-cctv.local

Secure credentials will be automatically generated for this sender.

CancelCreate Sender
Fig 2: Create New Sender modal assigning dedicated camera hardware identity.
Rilavek Dashboard · Senders > Generated Device Credentials

Sender Credentials

Make sure to copy your password now as you will not be able to see it again.
Username
cam_duo2poe
PasswordSave for Step 6
••••••••••••
Done
Fig 3: Generated device-level username and one-time password for camera authentication.
05

Create & Configure Your Ingestion Pipe in Rilavek

Go to Pipes in the sidebar and click Create Pipe. Configure the 4 core sections of your pipeline: General (Pipe ID), Inputs (FTP), Access Control (Sender permission), and Destinations (Data Store).

1General Settings (Pipe ID)

Every pipeline in Rilavek is assigned an immutable, globally unique Pipe ID (e.g. p_cctv9x). This ID acts as an isolated ingestion channel that segregates audit logs, real-time transfer metrics, and storage routing. It also forms the second half of your scoped camera FTP login username (username@p_cctv9x).

Rilavek Dashboard · Pipes > Pipeline Settings > General

Pipe ID

p_cctv9x

Use this ID to identify this pipe in logs. Combine it with the sender username for complete authentication details.

Fig 4: General settings displaying the unique Pipe ID used for authentication.

2Inputs (FTP / FTPS Ingress)

The Inputs configuration defines how camera files enter Rilavek. Enabling the FTP Ingress input provides a persistent, high-availability ingestion server (ftp.rilavek.com) compatible with active and passive FTP modes, explicit TLS negotiation, and standard CCTV firmware video push routines.

Rilavek Dashboard · Pipes > Pipeline Settings > Inputs

Inputs

Enable inputs to receive data.

1 input enabled
FTP
SFTP

FTP Ingress

Endpoint enabled. Connect using your Sender credentials.

Host
ftp.rilavek.com
Port
21
Username
<sender>@p_cctv9x

Example: cam_duo2poe@p_cctv9x

Password
••••••••••••

Use the password configured for the specific Sender.

Fig 5: Enabling the FTP Ingress endpoint for incoming surveillance video streams.

3Access Control (Sender Authorization)

Access Control prevents unauthorized uploads by enforcing a zero-trust boundary on the ingestion pipe. Only explicitly authorized Senders (such as Reolink Duo 2 PoE 4K 180° Panoramic Camera) can authenticate and stream video into this pipe. Any requests with unassigned credentials are rejected at the network edge.

Rilavek Dashboard · Pipes > Pipeline Settings > Access Control

Access Control

Restricts who can upload to this pipe.

1 sender allowed
1Individuals
Groups

Individual Senders

Grant or revoke pipe access for specific individual senders.

Reolink Duo 2 PoE 4K 180° Panoramic Camera
cam_duo2poe@p_cctv9x
Fig 6: Restricting pipeline ingress access to your authorized camera Sender.

4Destinations (Target Cloud Storage Routing)

The Destinations section routes video clips to your target cloud storage provider. Linking your configured Data Store routes all received footage directly to your IDrive e2 bucket (cctv-reolink-recordings). Video files are committed on-the-fly via parallel multipart S3 PUTs without intermediate disk caching.

Rilavek Dashboard · Pipes > Pipeline Settings > Destinations

Destinations

This is where we send your files to.

1 destination added
Reolink Storage (IDrive e2)
Primary
Target Bucketcctv-reolink-recordingsProviderIDrive e2StatusActive (Ready for camera ingress)
Fig 7: Routing incoming camera footage directly into your S3-compatible cloud bucket.
Camera Connection Parameters (Enter in Step 6):Reference Values
Server Hostftp.rilavek.com
Port21
Usernamecam_duo2poe@p_cctv9x
06

Configure FTP, Motion Detection & Linkage Method in Reolink Duo 2 PoE 4K 180° Panoramic Camera Firmware

Open your camera's web configuration page in your browser at its local LAN IP address and complete the steps below:

Step 6AConfigure FTP Streaming Credentials

Click Device Settings > Surveillance > FTP.

Turn on the FTP toggle switch, then click FTP Settings to expand the configuration card. Enter your Rilavek Ingestion Gateway server, port 21, scoped username, sender password, and remote directory. Enable 'Don't allow plain unencrypted FTP' for FTPS security.

Preview
Playback
Reolink

FTP Settings

FTP Settings

Server

ftp.rilavek.com
↳Rilavek Ingestion Gateway: Direct endpoint streaming into your IDrive e2 bucket.
21
cam_duo2poe@p_cctv9x
↳Scoped Rilavek User: cam_duo2poe@p_cctv9x (Sender@Pipe).
••••••••••••
↳Sender Secret: Enter device secret generated in Step 3.
Auto▼

To use encrypted data transfer, please configure FTPS on FTP server.

↳FTPS Enforcement: Ensures explicit TLS encryption on port 21 so camera streams travel securely to Rilavek.

Directory

reolink/duo-2-poe
↳Prefix Path: Reolink models require paths without leading or trailing slashes (e.g. reolink/duo-2-poe).
YYYY-MM-DD▼

Upload

Video & Image▼

Video

Clear▼
15Second(s)▼
No▼
100▼
↳S3 Chunk Optimization: 100MB chunk size ensures efficient multipart upload streaming without socket timeouts.

Image

Clear▼
1Minute(s)▼
No▼
Test
Save

Step 6BConfigure FTP Upload Schedule & Smart AI Detection

Click Device Settings > Surveillance > FTP > Schedule.

Under Schedule > Alarm, select your desired smart detection triggers (Person, Vehicle, Animal) to eliminate false alarms. Ensure the 24-hour weekly grid blocks are highlighted in blue for active monitoring.

Preview
Playback
Reolink

FTP Settings

FTP Settings

Schedule

Alarm
Timer
Any Motion
Person
Vehicle
Animal
↳Smart AI Edge Filtering: Check Person, Vehicle, and Animal to instruct the camera to only upload verified events, eliminating false triggers and saving cloud storage.
Sun
Mon
Tue
Wed
Thu
Fri
Sat
01234567891011121314151617181920212223
Enable
Disable
Save

Step 6CSave Configuration & Verify FTP Connection (Test & Ingestion Check)

Click Device Settings > Surveillance > FTP > Save & Test.

Click 'Save' (1) first to store your credentials and schedule in the camera memory, then click 'Test' (2) to verify live FTP communication with Rilavek. A green confirmation badge verifies end-to-end cloud bucket streaming.

Preview
Playback
Reolink

FTP Settings

FTP Settings > Action Verification
Target Gatewayftp.rilavek.com:21 (FTPS)
Ingestion Scoped Usercam_duo2poe@p_cctv9x
Destination Cloud BucketIDrive e2
Save
1
Test
2
FTP Test Succeeded226 Transfer complete. Live TLS handshake verified and write access confirmed to s3://idrive-e2.
↳Two-Step Sequence: In Reolink firmware, click [1] Save first to store credentials and schedule in flash memory, then click [2] Test to perform the live handshake with Rilavek.

Reolink Firmware Notes & Best Practices

Model-specific nuances, recommended settings, and verified workarounds for the Duo 2 PoE

Panoramic Aspect Ratio Encodingwarning

The 8MP image is stitched into a seamless 32:9 aspect ratio. The high resolution requires consistent bandwidth during continuous recording.

Solution:Allocate at least 10 Mbps upstream bandwidth per Duo 2 if running continuous 24/7 FTP uploads.
07

Verify Ingestion

Click Test in your camera's FTP settings or trigger a test recording transfer. In your Rilavek dashboard, navigate to Pipes > your pipeline > Transfers tab to inspect incoming files as video clips stream into IDrive e2.

Rilavek Dashboard · Pipes > Transfers
Overview
Transfers
Refresh
FILESENDERSIZEDATESTATE
reolink/duo-2-poe/2026-09-10/ch01_143000.mp4
cam_duo2poe18.4 MBSep 10, 14:30
Success
reolink/duo-2-poe/2026-09-10/ch01_142500.mp4
cam_duo2poe21.2 MBSep 10, 14:25
Success
reolink/duo-2-poe/2026-09-10/ch01_142000.mp4
cam_duo2poe19.7 MBSep 10, 14:20
Success
Showing 3 of 3 transfers
Fig 8: Transfers log confirming incoming camera recordings streaming directly into cloud storage.
Direct S3 Ingest VerifiedIncoming surveillance streams are committed on-the-fly directly to your IDrive e2 bucket with zero local buffering and no intermediate disk storage.
08

Configure IDrive e2 Bucket Lifecycle & Retention Rules (Optional)

Optional: Prevent runaway storage costs by configuring automated bucket expiration rules. Select your retention window below and apply the generated JSON lifecycle policy or CLI command to your IDrive e2 bucket. If you prefer to keep footage indefinitely or purge clips manually, feel free to skip this step.

IDrive e2 Retention Window

Select timeline to generate policy

Applying lifecycle expiration is optional. If you want automated retention, apply this configuration to your IDrive e2 bucket to automatically purge or transition clips older than 30 days, preventing runaway storage bills.

cctv-lifecycle.json (30-day retention for reolink/duo-2-poe)
{
  "Rules": [
    {
      "ID": "reolink-duo-2-poe-cctv-retention-policy",
      "Status": "Enabled",
      "Filter": {
        "Prefix": "reolink/duo-2-poe"
      },
      "Expiration": {
        "Days": 30
      }
    }
  ]
}
Apply via AWS / S3 CLI
aws s3api put-bucket-lifecycle-configuration \
  --bucket my-cctv-surveillance-bucket \
  --lifecycle-configuration file://cctv-lifecycle.json

IDrive e2 vs other cloud storage for Reolink Duo 2 PoE 4K 180° Panoramic Camera

How IDrive e2 compares with the other providers Rilavek can stream into.

ProviderBilling modelEgress feesRetention control
Cloudflare R2
Usage-based (storage + operations)Free egressS3 Lifecycle expiration & transitions
Backblaze B2
Usage-based (per GB stored)Free up to 3x stored data/day, then meteredS3 Lifecycle expiration
Wasabi Hot Cloud
Flat-rate (no egress/API fees; minimum storage duration)Free egressS3 Lifecycle + 90-day minimum storage duration
IDrive e2
Low usage-based (per GB stored)Free egressS3 Lifecycle expiration
DigitalOcean Spaces
Flat base (storage + egress allowance), then per-GBIncluded allowance, then meteredS3 Lifecycle expiration
AWS S3
Usage-based (storage + requests + egress)Metered per GBS3 Lifecycle expiration, transitions & Glacier archiving
Self-Hosted S3
Self-hosted (your hardware/power)Your own networkDepends on your S3 server's lifecycle support

Frequently Asked Questions about Reolink Duo 2 PoE Cloud Storage

Does the Reolink Duo 2 PoE 4K 180° Panoramic Camera require an on-site NVR to stream to cloud storage?

No. The Reolink Duo 2 PoE 4K 180° Panoramic Camera has built-in FTP client firmware. It connects directly to Rilavek's cloud bridge on port 21, streaming video chunks into your S3 bucket without requiring an on-prem NVR or dedicated PC.

Which cloud storage providers work with Duo 2 PoE?

Rilavek supports any provider with an S3-compatible API, including Cloudflare R2, Backblaze B2, AWS S3, Wasabi, IDrive e2, and self-hosted MinIO or RustFS instances.

How does video retention work?

You define retention policies (such as 30, 60, or 90 days) directly on your S3 bucket using lifecycle expiration rules. Your recordings are under your 100% control with zero vendor lock-in.

How to Backup Reolink Duo 2 PoE 4K 180° Panoramic Camera to Cloud Storage

Create your free Rilavek ingestion pipe in seconds. No NVR hardware, no proprietary camera cloud subscriptions, and 100% data ownership in your private storage bucket.

Free plan includes 10GB of transfer. No credit card required.