Stream Hikvision ColorVu 4K DS-2CD2387G2-LU Turret to Backblaze B2

Commercial-grade 4K ColorVu 24/7 full-color turret with FTPS/FTP upload. Follow our step-by-step setup guide below to stream footage directly to Backblaze B2 via FTP/S with Rilavek as the pipe — zero on-prem NVR required.

Hikvision ColorVu 4K DS-2CD2387G2-LU Turret - Product View
Zero NVR Vulnerability

Your Hikvision DS-2CD2387G2-LU uploads footage offsite in real time directly to Backblaze B2. Intruders cannot steal or destroy evidence by seizing on-prem recorder hardware.

S3-Native Retention

Store Hikvision DS-2CD2387G2-LU recordings in Backblaze B2 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 Hikvision DS-2CD2387G2-LU and writes them directly to Backblaze B2 via multipart S3 PUTs with zero disk writes.

Hikvision ColorVu 4K DS-2CD2387G2-LU Turret
Hikvision ColorVu 4K DS-2CD2387G2-LU Turret
FTP/S
Rilavek
Rilavek Bridge
S3 API
Backblaze B2
Backblaze B2

How to Stream Hikvision ColorVu 4K DS-2CD2387G2-LU Turret to Backblaze B2

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

01

Set Up Your Backblaze B2Backblaze B2 Bucket & Generate API Keys

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

  1. Log into Backblaze B2 and navigate to Buckets > Create a Bucket (keep bucket Private).
  2. Navigate to Application Keys in the sidebar and click Add a New Application Key.
  3. Name the key rilavek-ds-2cd2387g2-lu, restrict access to your new bucket, and select Read and Write.
  4. Copy the generated keyID (Access Key ID) and applicationKey (Secret Access Key). Backblaze displays this secret only once.
  5. In bucket details, locate your S3 Endpoint (https://s3.<region>.backblazeb2.com).
02

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 first.Rilavek needs minimal, write-focused actions — nothing more.
Rilavek Dashboard · Data Stores > New S3 Data Store

Add New Data Store

S3 Compatible
Hikvision Surveillance Storage
https://s3.<region>.backblazeb2.com
AKIAIOSFODNN7EXAMPLE
••••••••••••••••••••••••••••••••
cctv-hikvision-recordings
Automatically executes multipart write-probe test before saving.Save Data Store
Fig 1: Add New S3 Data Store configuration in the Rilavek console.
03

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 Hikvision ColorVu 4K DS-2CD2387G2-LU Turret and generates a dedicated device-level password.

Rilavek Dashboard · Senders > Create New Sender Modal

Create New Sender

Hikvision ColorVu 4K DS-2CD2387G2-LU Turret
cam_ds2cd2387g2lu

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

security@hikvision-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_ds2cd2387g2lu
PasswordSave for Step 5
••••••••••••
Done
Fig 3: Generated device-level username and one-time password for camera authentication.
04

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_ds2cd2387g2lu@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 Hikvision ColorVu 4K DS-2CD2387G2-LU Turret) 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.

Hikvision ColorVu 4K DS-2CD2387G2-LU Turret
cam_ds2cd2387g2lu@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 Backblaze B2 bucket (cctv-hikvision-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
Hikvision Storage (Backblaze B2)
Primary
Target Bucketcctv-hikvision-recordingsProviderBackblaze B2StatusActive (Ready for camera ingress)
Fig 7: Routing incoming camera footage directly into your S3-compatible cloud bucket.
Camera Connection Parameters (Enter in Step 5):Reference Values
Server Hostftp.rilavek.com
Port21
Usernamecam_ds2cd2387g2lu@p_cctv9x
05

Configure FTP, Motion Detection & Linkage Method in Hikvision ColorVu 4K DS-2CD2387G2-LU Turret Firmware

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

Step 5AConfigure FTP Streaming Credentials

Click Configuration > Network > Advanced Settings > FTP.

Enter your Rilavek Ingestion Pipe parameters as indicated by the red annotations below.

HIKVISION®
FTP
Email
Platform Access
QoS
Integration Protocol
Network Service
ftp.rilavek.com
Rilavek Ingestion Gateway: Managed global endpoint routing streams to your Backblaze B2 bucket.
21
cam_ds2cd2387g2lu@p_cctv9x
Anonymous
Scoped Rilavek Login: Enter cam_ds2cd2387g2lu@p_cctv9x (SenderUsername@PipeID created in Step 3 & 4).
••••••••••••
Device Password: Enter the one-time generated password from your Rilavek Sender credentials in Step 3.
••••••••••••
Save in the parent directory
Custom
hikvision-colorvu
Target Cloud Storage Path: Root folder inside your Backblaze B2 bucket.
1
Day(s)
Recommendation: Create a new subfolder per day (1 Day). Otherwise, all files will be saved in 1 monolithic directory in your cloud storage.
Default
Upload Picture / Video Clips
Test
Ready for Backblaze B2
Save
Changes take effect immediately on next event trigger.

Step 5BConfigure Motion Detection (Area Settings)

Click Configuration > Event > Basic Event > Motion Detection.

To stream motion-triggered events instead of continuous 24/7 recording (saving cloud storage and bandwidth), configure your detection area and target filters as indicated by the red annotations below.

HIKVISION®
Motion Detection
Video Tampering
Exception
Enable Motion Detection
Required for Cloud Motion Trigger: Must be checked so the camera generates event clips to stream to your Rilavek pipeline.
Enable Dynamic Analysis for Motion
Area Settings
Arming Schedule
Linkage Method
Draw Detection Zone: Frame the surveillance area and configure smart AI target filtering below.
Motion Detection Area [1] ActiveAI Smart Event Filter: Human & Vehicle Detection
Human: 94%
07-21-2024 Sun 01:39:11
Camera 01
Video StreamSnapshot
Draw Area
Clear All
Human
Vehicle
Storage Cost Optimization: Filters out environmental false alarms (leaves, shadows, rain) to minimize S3 Class A PUT requests and overall cloud storage costs.
60
Save
Changes take effect immediately on next event trigger.

Step 5CConfigure Linkage Method (Upload to FTP)

Click Configuration > Event > Basic Event > Motion Detection > Linkage Method.

Check "Upload to FTP/Memory Card/..." so motion video clips stream to Rilavek as indicated by the red annotations below.

HIKVISION®
Motion Detection
Video Tampering
Exception
Enable Motion Detection
Required for Cloud Motion Trigger: Must be checked so the camera generates event clips to stream to your Rilavek pipeline.
Enable Dynamic Analysis for Motion
Area Settings
Arming Schedule
Linkage Method
Critical Rilavek Linkage: You must check "Upload to FTP/Memory Card/..." so detected motion clips stream directly into your Rilavek Ingestion Pipe!
Normal Linkage
Trigger Recording
Send Email
Notify Surveillance Center
Upload to FTP/Memory Card/...
Critical Upload Action: Checking this sends motion video clips to ftp.rilavek.com so they stream to Backblaze B2.
A1
Save
Changes take effect immediately on next event trigger.

Hikvision Firmware Notes & Best Practices

Model-specific nuances, recommended settings, and verified workarounds for the DS-2CD2387G2-LU

Error 553 Directory Path Syntaxcritical

Hikvision firmware fails test transfers with Error Code 553 if the directory path has leading or trailing double slashes.

Solution:Format the directory as a simple single subfolder, e.g., 'camera1' or leave blank for root.
Snapshot vs Video Upload Linkagewarning

By default, Hikvision only uploads JPEG snapshots on motion events unless video linkage is enabled under Event Actions.

Solution:Navigate to Event > Basic Event > Motion Detection > Linkage Method and check 'Upload to FTP/Memory Card/NAS'.
06

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 Backblaze B2.

Rilavek Dashboard · Pipes > Transfers
Overview
Transfers
Refresh
FILESENDERSIZEDATESTATE
hikvision/ds-2cd2387g2-lu/2026-09-10/ch01_143000.mp4
cam_ds2cd2387g2lu18.4 MBSep 10, 14:30
Success
hikvision/ds-2cd2387g2-lu/2026-09-10/ch01_142500.mp4
cam_ds2cd2387g2lu21.2 MBSep 10, 14:25
Success
hikvision/ds-2cd2387g2-lu/2026-09-10/ch01_142000.mp4
cam_ds2cd2387g2lu19.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 Backblaze B2 bucket with zero local buffering and no intermediate disk storage.

Common questions

Does the Hikvision ColorVu 4K DS-2CD2387G2-LU Turret require an on-site NVR to stream to Backblaze B2?

No. The Hikvision ColorVu 4K DS-2CD2387G2-LU Turret has built-in FTP client firmware. It connects directly to Rilavek's cloud bridge on port 21, streaming video chunks into your Backblaze B2 bucket without requiring a local NVR or PC.

How does retention work on Backblaze B2?

You define exact retention policies (e.g. 30, 90, or 365 days) directly in your Backblaze B2 bucket using standard S3 Lifecycle expiration rules. Footage is never auto-overwritten by proprietary cloud caps.

What happens if my internet connection drops?

If your DS-2CD2387G2-LU has a local MicroSD card installed, it records motion events locally and retries the FTP upload once connectivity is restored.

Stream Hikvision ColorVu 4K DS-2CD2387G2-LU Turret to Backblaze B2

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.