How to Backup Hikvision 8-Channel 4K NVR (DS-7608NI) to Wasabi Hot Cloud

Network Video Recorder offsite disaster backup directly to S3/R2 object storage. Follow our step-by-step setup guide below to replicate NVR channel footage directly into AWS S3, Cloudflare R2, or Backblaze B2 via FTP/S with Rilavek as the pipe, securing your footage offsite against on-prem hardware theft or disk failure.

Hikvision 8-Channel 4K NVR (DS-7608NI) - Product View
Anti-Theft Offsite Backup

Your Hikvision DS-7608NI-I2/8P replicates channel footage offsite in real time. Even if the physical NVR unit or local hard drives are stolen, damaged, or seized, your video archive remains safe in the cloud.

Unlimited Multi-Channel Retention

Retain multi-channel NVR footage beyond local drive capacity. Apply automated S3 lifecycle rules to transition recordings to cold archive or expire clips after 30, 90, or 365 days.

Zero-Disk Replication Bridge

Rilavek ingests native FTP/S uploads from your Hikvision DS-7608NI-I2/8P and streams them straight into multipart S3 PUTs with zero intermediate server disk writes.

Hikvision 8-Channel 4K NVR (DS-7608NI)
Hikvision 8-Channel 4K NVR (DS-7608NI)
FTP/FTPS
Rilavek
Rilavek Bridge
S3 API
Wasabi Hot Cloud
Wasabi Hot Cloud

Step-by-Step Setup Guide for Hikvision 8-Channel 4K NVR (DS-7608NI)

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

01

Select Your Cloud Storage Provider

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

02

Set Up Your Wasabi Hot Cloud Bucket & Generate API Keys

Configure your target bucket and API credentials inside Wasabi Hot Cloud so Rilavek can replicate multi-channel NVR recordings directly into your storage.

1

Create a Wasabi Hot Cloud Storage Bucket

Log into the Wasabi Console and select Create Bucket . Choose your preferred datacenter region and assign a unique bucket name.

2

Generate an API Access Key

Go to Access Keys in the left sidebar and click Create New Access Key . Create a sub-user key or standalone key with permissions restricted to your surveillance bucket.

3

Save API Credentials & Endpoint URL

Download the credentials file or copy your API Key and Secret Key. Wasabi regional endpoints use https://s3.<region>.wasabisys.com (for example, https://s3.us-east-1.wasabisys.com).

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
Hikvision NVR Storage
https://s3.<region>.wasabisys.com
AKIAIOSFODNN7EXAMPLE
••••••••••••••••••••••••••••••••
How to create →
cctv-hikvision-recordings
us-east-1
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 an NVR Sender in Rilavek

Go to Senders in the Rilavek sidebar and click New Sender. A Sender represents the hardware identity of your Hikvision 8-Channel 4K NVR (DS-7608NI) and generates a dedicated device-level password.

Rilavek Dashboard · Senders > Create New Sender Modal

Create New Sender

Hikvision 8-Channel 4K NVR (DS-7608NI)
nvr_ds7608nii28p

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 NVR 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
nvr_ds7608nii28p
PasswordSave for Step 6
••••••••••••
Done
Fig 3: Generated device-level username and one-time password for NVR 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 NVR 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 NVR recordings 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 NVR multi-channel 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: nvr_ds7608nii28p@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 8-Channel 4K NVR (DS-7608NI)) 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 8-Channel 4K NVR (DS-7608NI)
nvr_ds7608nii28p@p_cctv9x
Fig 6: Restricting pipeline ingress access to your authorized NVR 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 Wasabi Hot Cloud 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 (Wasabi Hot Cloud)
Primary
Target Bucketcctv-hikvision-recordingsProviderWasabi Hot CloudStatusActive (Ready for NVR ingress)
Fig 7: Routing incoming NVR footage directly into your S3-compatible cloud bucket.
NVR Connection Parameters (Enter in Step 6):Reference Values
Server Hostftp.rilavek.com
Port21
Usernamenvr_ds7608nii28p@p_cctv9x
06

Configure NetHDD / FTP Offsite Replication in Hikvision 8-Channel 4K NVR (DS-7608NI) Firmware

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

Step 6AConfigure FTP Streaming Credentials

Click Configuration > Network > Advanced > NetHDD / 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 Wasabi Hot Cloud bucket.
21
nvr_ds7608nii28p@p_cctv9x
Anonymous
↳Scoped Rilavek Login: Enter nvr_ds7608nii28p@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▼
nvr-backup
↳Target Cloud Storage Path: Root folder inside your Wasabi Hot Cloud 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 Wasabi Hot Cloud
Save
Changes take effect immediately on next event trigger.

Step 6BConfigure 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 NVR 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 6CConfigure 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 NVR 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 Wasabi Hot Cloud.
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-7608NI-I2/8P

Multi-Channel Folder Separationcritical

When streaming from an NVR, all 8 channels stream to the same FTP pipe. Channels can overwrite files if not segregated.

Solution:Select 'Save in Subdirectories by Channel No.' in Hikvision NVR FTP settings.
07

Verify Ingestion

Click Test in your NVR'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 Wasabi Hot Cloud.

Rilavek Dashboard · Pipes > Transfers
Overview
Transfers
Refresh
FILESENDERSIZEDATESTATE
hikvision/ds-7608ni-i2/2026-09-10/ch01_143000.mp4
nvr_ds7608nii28p18.4 MBSep 10, 14:30
Success
hikvision/ds-7608ni-i2/2026-09-10/ch01_142500.mp4
nvr_ds7608nii28p21.2 MBSep 10, 14:25
Success
hikvision/ds-7608ni-i2/2026-09-10/ch01_142000.mp4
nvr_ds7608nii28p19.7 MBSep 10, 14:20
Success
Showing 3 of 3 transfers
Fig 8: Transfers log confirming incoming NVR recordings streaming directly into cloud storage.
Direct S3 Ingest VerifiedIncoming surveillance streams are committed on-the-fly directly to your Wasabi Hot Cloud bucket with zero local buffering and no intermediate disk storage.
08

Configure Wasabi Hot Cloud 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 Wasabi Hot Cloud bucket. If you prefer to keep footage indefinitely or purge clips manually, feel free to skip this step.

Wasabi Hot Cloud Retention Window

Select timeline to generate policy

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

cctv-lifecycle.json (30-day retention for /nvr-backup/)
{
  "Rules": [
    {
      "ID": "hikvision-ds-7608ni-i2-cctv-retention-policy",
      "Status": "Enabled",
      "Filter": {
        "Prefix": "nvr-backup/"
      },
      "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

Wasabi Hot Cloud vs other cloud storage for Hikvision 8-Channel 4K NVR (DS-7608NI)

How Wasabi Hot Cloud 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 Hikvision DS-7608NI-I2/8P Cloud Storage

How does the Hikvision 8-Channel 4K NVR (DS-7608NI) backup recordings to cloud storage?

The Hikvision 8-Channel 4K NVR (DS-7608NI) features native NetHDD / FTP upload capabilities in its firmware. It streams channel recordings directly to Rilavek's in-memory pipe on port 21, replicating video files into your private S3 bucket in real time for secure offsite disaster recovery without requiring proprietary cloud subscriptions.

Which cloud storage providers work with DS-7608NI-I2/8P?

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 Hikvision 8-Channel 4K NVR (DS-7608NI) 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.