What Is H3C CAS & UIS?
H3C CAS (Cloud Automation System) is a proprietary virtualization and cloud management platform designed to replace VMware in data centers. It effectively integrates compute, storage, network, and security virtualization. Its core components include CVK (a KVM-based hypervisor), CVM (a web-based management layer), and CIC (for cluster monitoring and detailed performance telemetry).
H3C UIS (Unified Infrastructure System) is a hyper-converged counterpart running on standard x86 or ARM servers. It integrates three kernels: CAS for compute, ONEStor for software-defined distributed storage, and Sec for network security. ONEStor pools disks to support multiple storage services with robust data protection. UIS also includes essential P2V and V2V migration tools.
Why Do You Need to Back Up H3C CAS & UIS?
Even with ONEStor's built-in redundancy, disk-level protection is not the same as backup. Multi-replica and erasure coding protect against drive or node failure, but they do not defend against the most common data-loss events: accidental deletion, corrupted applications, ransomware, and human error. When a VM is deleted or encrypted by malware, the redundant copies are deleted or encrypted too.
A proper H3C CAS backup solution restores to a specific point in time, independent of the production storage. That means an administrator can roll a VM back to yesterday's clean state after a bad patch, recover a single deleted file without a full restore, or rebuild the environment at a second site after a disaster. Many organizations also need scheduled backups for regulatory retention — financial, healthcare, and government workloads must prove recoverability, not just redundancy.
Key Challenges of H3C CAS & UIS Backup
Four platform-specific traits make backing up CAS and UIS harder than it first appears.
No native changed-block tracking.
Unlike VMware's CBT or Hyper-V's RCT, H3C CAS has no built-in API to report which data blocks changed since the last backup. A naive backup tool must rescan the entire disk each cycle, which makes incremental backups slow and storage-hungry. This is the single most important gap to understand when choosing a solution.
Raw and high-speed disk limits.
In CAS, disks created as raw disks or high-speed disks do not support online backup, incremental backup, or differential backup through the native path. A tool that cannot handle these disk types will either skip critical VMs or force lengthy offline backups.
Distributed-storage complexity in UIS.
UIS VMs often live on ONEStor's distributed storage, where data is striped across nodes. Backup must read consistently from this fabric without disrupting production I/O, and restores must reconstruct the VM onto the target host correctly — including disk format, bus type, and MAC address.
Application-consistency requirement.
SQL Server and Oracle databases running inside CAS/UIS VMs need application-aware quiescing before a snapshot, so the backup is transactionally consistent and restorable. A tool that only takes crash-consistent snapshots risks restoring a database that fails integrity checks.
Three Common Methods to Protect H3C CAS & UIS
There are three ways to protect CAS and UIS workloads, each with a different risk profile.
Native Snapshots
CAS and UIS offer snapshot capabilities through the CVM/UIS console. Snapshots are fast and useful for short-term rollback before a patch or upgrade. However, they are not backups. Snapshots are stored on the same storage pool as the VM, so a storage failure destroys both. On some CAS versions, snapshot chains also degrade VM performance and consume the same capacity as the production data. Snapshots are a complement to backup, never a substitute.
Export VMs (OVA/OVF Export)
The CVM/UIS console can export a VM as a template or OVA file for offline copies. This works well for archiving a few critical VMs or for migration. The drawback is operational: export is manual, offline in most configurations, and cannot scale to dozens or hundreds of VMs. There is no incremental export, so each copy is a full image, and restores require manual import and re-registration. Export suits periodic golden-image archiving, not day-to-day protection.
Third-Party Backup Tool
A dedicated H3C CAS backup tool (or a multi-hypervisor platform that officially supports CAS/UIS) is the only method that delivers automation, incremental efficiency, granular restore, and DR in one place. The right tool is agentless — it backs up at the hypervisor level via native APIs and installs only a lightweight backup plugin on the CVK/UIS hosts. It adds changed-block tracking that CAS lacks and handles raw and high-speed disks correctly.
The table below summarizes the trade-offs.
| Method | Automation | Incremental | Granular Restore | DR / Offsite | Best For |
|---|
| Native Snapshots | Manual | No | No | No | Pre‑change rollback |
| VM Export (OVA/OVF) | Manual | No | No | Partial | Golden‑image archiving |
| Third‑Party Tool | Yes | Yes (with CBT) | Yes | Yes | Production backup & DR |
Common H3C CAS & UIS Backup Selection Mistakes
Most failed CAS/UIS backup projects trace back to one of four selection errors.
Treating snapshots as backups.
Teams rely on snapshots and only discover the gap after a storage failure or ransomware event, when both VM and snapshot are gone.
Assuming VMware compatibility carries over.
A product that backs up ESXi is not automatically safe for CVK/UIS-CAS. Without explicit CAS/UIS support, jobs fail or silently skip VMs.
Ignoring the CBT gap.
Choosing a tool with no changed-block tracking turns every backup into a full scan. Incremental jobs become slow, and backup windows grow until they collide with production hours.
Skipping raw/high-speed disk verification.
If the vendor cannot state clearly how it handles raw and high-speed disks, VMs on those disks will be left unprotected — often discovered only during a restore test.
A short pre-purchase checklist: does it support CAS/UIS natively, does it add CBT, does it handle raw/high-speed disks, and is it officially certified — eliminates all four risks before signing.
Core Requirements of H3C CAS & UIS Backup Software
When evaluating an H3C UIS backup solution or an H3C CAS backup product, require these six capabilities.
Official certification. Look for H3Cloud Ready certification, which verifies compatibility and performance against H3C CAS. It is the strongest signal that the tool was tested against the platform rather than claimed.
Agentless, plugin-based architecture. Backup should run at the hypervisor level with a lightweight plugin on CVK/UIS hosts, not agents inside every VM. This avoids per-VM install, maintenance, and reboot overhead.
Changed-block tracking (CBT). The tool must supply its own CBT because CAS has none. This is what makes incremental backups fast and small.
Raw and high-speed disk support. Confirm explicitly that raw disks and high-speed disks can be backed up, incrementally, without forcing offline jobs.
Instant and granular recovery. Instant VM recovery (mounting backup storage via NFS) restores a VM in seconds, while granular recovery lets you pull a single file or folder from any restore point.
Cross-platform migration. The ability to restore a CAS/UIS VM to VMware or another hypervisor (V2V) protects against platform lock-in and supports migration projects.
Defined RPO and RTO. The tool must be able to hit your recovery-point and recovery-time targets — typically achieved through frequent incremental jobs and instant restore — rather than leaving these as vague promises.
Scalable backup infrastructure. For large clusters, the solution should let you add backup nodes for distributed storage while keeping all of them under a single web console.
How Vinchin Addresses H3C CAS & UIS Backup Challenges
Vinchin Backup & Recovery is built to close each CAS/UIS-specific gap directly.
H3Cloud Ready certification. Vinchin has passed H3C's official compatibility test for H3C CAS 3.0 and above and holds H3Cloud Ready certification. That means the integration was validated by H3C, not assumed.
SpeedKit replaces the missing CBT. Because CAS has no native changed-block tracking, Vinchin's SpeedKit feature identifies changed blocks on snapshot technology, so only modified data is transferred in incremental jobs. This restores the efficiency that a VMware-only tool would take for granted.
Correct raw and high-speed disk handling. Vinchin supports the full disk-type matrix of CAS and UIS, including the raw and high-speed disks that native tools skip, so no VM is left outside the protection scope.
Agentless plugin on hosts. A lightweight backup plugin installs on the CVK/UIS hosts, while backup jobs are managed from a unified web console — no agents inside individual VMs.
Instant recovery and granular restore. Instant VM Recovery mounts backup storage to a host over NFS and resumes the VM in about 15 seconds. Granular restore browses any restore point and downloads individual files without a full VM restore.
Storage and DR depth. Deduplication, compression, and the BitDetector feature strip swap files, partition gaps, and unpartitioned space to shrink backup storage. Offsite copy and cloud archiving to AWS, Azure, Alibaba Cloud, or Tencent Cloud satisfy the 3-2-1 backup rule, and cross-platform restore converts CAS/UIS VMs to VMware or other platforms while optionally preserving the MAC address.
Vinchin supports the following H3C versions:
| Category | Supported H3C Versions |
|---|
| H3C CAS | E0506, E0526, E0530, E0535, E0706, E0709, E0710, E0718, E0730, v7.0 |
| H3C UIS | E0606, E0611, E0716, E0720, E0721, E0750, E0802P01, E0881, R0785P03, R0786P02, R0886 |
FAQ
Q1: Why does H3C CAS backup feel slower than VMware backup?
A1: CAS has no native changed-block tracking. A tool without a CBT alternative must rescan full disks. Choose a solution with SpeedKit or equivalent CBT to make incremental jobs fast.
Q2: Can Vinchin back up raw and high-speed disks in CAS?
A2: Yes. Unlike native CAS paths, Vinchin supports raw disks and high-speed disk, including online and incremental protection, so these VMs are not excluded.
Q3: Can I restore an H3C CAS VM to VMware?
A3: Yes. Vinchin performs cross-platform recovery (V2V), converting a CAS/UIS VM to VMware or other supported hypervisors, and can preserve the original MAC address.
Q4: What does H3Cloud Ready mean?
A4: H3Cloud Ready is H3C's certification confirming that a partner product is compatible and performs reliably with H3C cloud-computing products. Vinchin is H3Cloud Ready certified for H3C CAS 3.0 and above.
Q5: Can Vinchin back up databases inside H3C VMs?
A5: Yes. Beyond crash-consistent VM backup, Vinchin adds application-aware protection for Microsoft SQL Server and Oracle, quiescing the database before the snapshot so restores are transactionally consistent.
Conclusion
Choosing a reliable H3C CAS & UIS backup solution comes down to four checks: native platform support, a real changed-block-tracking alternative, correct raw/high-speed disk handling, and official H3Cloud Ready certification. Native snapshots and VM export each cover only part of the need, while a certified third-party tool closes CAS's CBT gap and delivers automation, granular restore, and DR together.
Vinchin Backup & Recovery meets all four criteria with SpeedKit, H3Cloud Ready certification, and documented version coverage — making it a dependable choice for protecting H3C CAS and UIS virtual machines.
