How to Backup Dahua WizSense 4K Motorized Turret (5842T) to Cloudflare R2
4K AI-powered motorized vari-focal camera with perimeter protection and FTP sync. 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.
Your Dahua IPC-HDW5842T-ZE uploads footage offsite in real time. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.
Store Dahua IPC-HDW5842T-ZE recordings on your own terms. Apply automated bucket lifecycle rules to roll over or archive clips after 30, 90, or 365 days.
Rilavek ingests native FTP/S streams from your Dahua IPC-HDW5842T-ZE and writes them directly into multipart S3 PUTs with zero disk writes.
Step-by-Step Setup Guide for Dahua WizSense 4K Motorized Turret (5842T)
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.
Select Your Cloud Storage Provider
Choose where you want to store your Dahua surveillance footage. Selecting a provider customizes the bucket setup steps, endpoint URLs, and API key instructions in Step 2.
Set Up Your 
Cloudflare R2 Bucket & Generate API Keys
Configure your target bucket and API credentials inside Cloudflare R2 so Rilavek can stream motion clips and continuous video directly into your storage.
Cloudflare R2 provides an included monthly free tier of 10 GB storage, 1,000,000 Class A operations (uploads), 10,000,000 Class B operations (reads), and $0 egress bandwidth fees. Ensure you have completed the initial R2 subscription setup in your Cloudflare dashboard under Storage & databases > R2 before generating tokens.
Open R2 and Create Your Surveillance Bucket
In the Cloudflare Dashboard , navigate to Storage & databases > R2 > Overview. Click the blue Create bucket button and specify a name, such as cctv-dahua-recordings.
Leave location set to Automatic for the lowest-latency edge ingestion worldwide. If your organization requires strict data residency, select a specific Jurisdiction (European Union eu, United States us, or FedRAMP fedramp). Note that jurisdictional buckets require jurisdiction-specific S3 endpoints.
Copy Your 32-Character Cloudflare Account ID
On the right sidebar of the R2 Overview page under the Account Details section, locate and copy your 32-character hexadecimal Account ID. This is required to assemble your unique S3 API endpoint.
Create an Account API Token with Scoped Permissions
Under Account Details on the R2 overview page, select Manage next to API Tokens, then click Create API Token:
- Token Type: Choose Create Account API token (recommended for bridge infrastructure so credentials remain valid independently of individual user accounts; requires Super Administrator role).
- Permissions: Select Object Read & Write. This grants S3 API upload, download, and listing capabilities without exposing administrative privileges (like deleting buckets or altering account configs).
- Bucket Scoping: Select Apply to specific buckets only and pick your created bucket (
cctv-dahua-recordings). - TTL / Expiration: Leave blank for permanent 24/7 camera recording, or specify an expiration according to your organization's security rotation schedule.
Click Create Account API token to generate your credentials.
Copy Your Access Key ID and Secret Access Key
Record your Access Key ID (token ID) and Secret Access Key securely for Step 3.
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.
Add New Data Store
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 Dahua WizSense 4K Motorized Turret (5842T) and generates a dedicated device-level password.
Create New Sender
Must be at least 6 characters, lowercase, start with a letter/underscore, and contain only letters, numbers, hyphens, or underscores.
Secure credentials will be automatically generated for this sender.
Sender Credentials
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).
Pipe ID
Use this ID to identify this pipe in logs. Combine it with the sender username for complete authentication details.
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.
Inputs
Enable inputs to receive data.
FTP Ingress
Endpoint enabled. Connect using your Sender credentials.
Example: cam_ipchdw5842tze@p_cctv9x
Use the password configured for the specific Sender.
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 Dahua WizSense 4K Motorized Turret (5842T)) can authenticate and stream video into this pipe. Any requests with unassigned credentials are rejected at the network edge.
Access Control
Restricts who can upload to this pipe.
Individual Senders
Grant or revoke pipe access for specific individual senders.
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 Cloudflare R2 bucket (cctv-dahua-recordings). Video files are committed on-the-fly via parallel multipart S3 PUTs without intermediate disk caching.
Destinations
This is where we send your files to.
Configure FTP, Motion Detection & Linkage Method in Dahua WizSense 4K Motorized Turret (5842T) 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 Setting > Storage > Destination > FTP.
Enter your Rilavek Ingestion Pipe parameters as indicated by the red annotations below.
cam_ipchdw5842tze@p_cctv9x (SenderUsername@PipeID).Step 6BConfigure Upload Schedule (Snapshot & Record Schedule)
Click Setting > Storage > Schedule.
Select the Snapshot or Record tab, then ensure your schedule grid has Yellow (Motion) or Green (General) time blocks configured so the camera uploads footage during active periods.
Dahua IP cameras only upload files during times marked on the schedule matrix. Highlight periods in Yellow (Motion) for motion-triggered snapshot/clip upload to save S3 storage and ingress fees.
Step 6CEnable FTP Destination in Storage Path (Linkage Routing)
Click Setting > Storage > Destination > Path.
Check the "FTP" checkboxes under Scheduled and Motion Detection for Record and Snapshot. In Dahua firmware, FTP storage must be explicitly activated in this Path table for files to upload to Rilavek.
| Event Type | Scheduled | Motion Detection |
|---|---|---|
| FTP |
| Event Type | Scheduled | Motion Detection |
|---|---|---|
| FTP |
In Dahua IP camera firmware, you must check the "FTP" boxes under Scheduled and Motion Detection in this Path destination matrix. If these boxes remain unchecked, the camera will record events locally to SD card/NVR storage, but will never forward snapshots or video clips to your Rilavek FTP Ingestion Gateway even if the credentials under the FTP tab test 100% successfully.
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 Cloudflare R2.
| FILE | SENDER | SIZE | DATE | STATE |
|---|---|---|---|---|
dahua/ipc-hdw5842t-ze/2026-09-10/ch01_143000.mp4 | cam_ipchdw5842tze | 18.4 MB | Sep 10, 14:30 | Success |
dahua/ipc-hdw5842t-ze/2026-09-10/ch01_142500.mp4 | cam_ipchdw5842tze | 21.2 MB | Sep 10, 14:25 | Success |
dahua/ipc-hdw5842t-ze/2026-09-10/ch01_142000.mp4 | cam_ipchdw5842tze | 19.7 MB | Sep 10, 14:20 | Success |
Configure Cloudflare R2 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 Cloudflare R2 bucket. If you prefer to keep footage indefinitely or purge clips manually, feel free to skip this step.
Cloudflare R2 Retention Window
Select timeline to generate policyApplying lifecycle expiration is optional. If you want automated retention, apply this configuration to your Cloudflare R2 bucket to automatically purge or transition clips older than 30 days, preventing runaway storage bills.
{
"Rules": [
{
"ID": "dahua-ipc-hdw5842t-ze-cctv-retention-policy",
"Status": "Enabled",
"Filter": {
"Prefix": "wizsense-4k/"
},
"Expiration": {
"Days": 30
}
}
]
}aws s3api put-bucket-lifecycle-configuration \ --bucket my-cctv-surveillance-bucket \ --lifecycle-configuration file://cctv-lifecycle.json
Cloudflare R2 vs other cloud storage for Dahua WizSense 4K Motorized Turret (5842T)
How Cloudflare R2 compares with the other providers Rilavek can stream into.
| Provider | Billing model | Egress fees | Retention control |
|---|---|---|---|
| Cloudflare R2 | Usage-based (storage + operations) | Free egress | S3 Lifecycle expiration & transitions |
 Backblaze B2 | Usage-based (per GB stored) | Free up to 3x stored data/day, then metered | S3 Lifecycle expiration |
 Wasabi Hot Cloud | Flat-rate (no egress/API fees; minimum storage duration) | Free egress | S3 Lifecycle + 90-day minimum storage duration |
 IDrive e2 | Low usage-based (per GB stored) | Free egress | S3 Lifecycle expiration |
 DigitalOcean Spaces | Flat base (storage + egress allowance), then per-GB | Included allowance, then metered | S3 Lifecycle expiration |
 AWS S3 | Usage-based (storage + requests + egress) | Metered per GB | S3 Lifecycle expiration, transitions & Glacier archiving |
 Self-Hosted S3 | Self-hosted (your hardware/power) | Your own network | Depends on your S3 server's lifecycle support |
Frequently Asked Questions about Dahua IPC-HDW5842T-ZE Cloud Storage
Does the Dahua WizSense 4K Motorized Turret (5842T) require an on-site NVR to stream to cloud storage?
No. The Dahua WizSense 4K Motorized Turret (5842T) 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 IPC-HDW5842T-ZE?
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 Dahua WizSense 4K Motorized Turret (5842T) 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.