Back Up Named Platforms. Replicate Between Them.
Platform-aware protection for VMware, Nutanix AHV, CloudStack, OSSEA and Azure, with an agent-based path for supported physical Windows servers.
Sendense joins backup, live replication, platform conversion and recovery into one operating model, so protection does not fracture when workloads move.
Named
Backup Sources
Policy
RPO Control
Hot
Failover Mode
P2V
Physical Restore
Native Backup Coverage
Protect The Platforms Already In Your Estate.
Each named virtual platform uses its qualified data path. Supported physical Windows servers use the enrolled Windows agent without implying support for their underlying hypervisor.
VMware vSphere
ProductionNative API Integration
Protect VMware workloads through the platform path, then recover or move them into Nutanix AHV, CloudStack, OSSEA or Azure.
CloudStack / OSSEA
ProductionDeep Storage Integration
Use qualified native or host-assisted changed-block paths where available and CloudStack-aware full-source-read paths elsewhere, with EBA repository governance.
Microsoft Azure
ProductionAzure APIs
Protect cloud workloads and use Azure as a recovery target for DR, migration and repatriation workflows.
Nutanix AHV
ProductionDirect Prism Element
Protect Nutanix AHV workloads and use AHV as a source or target with VMware, CloudStack, OSSEA and Azure. Sendense does not use or require Prism Central, and the same EBA and recovery proof benefits apply.
Protect Physical Windows Servers Without A Second Toolset.
The Sendense Windows agent protects supported physical Windows servers and their configured NTFS volumes through the same governed backup service.
Windows recovery points use the same EBA repository and validation workflow, with a code-backed P2V path into CloudStack. The host platform itself is not presented as supported.
Covered Workloads
Windows: VSS + App-Aware
VSS snapshots and NTFS change tracking for supported physical Windows servers.
Windows Agent Path
The enrolled Windows agent exposes configured NTFS volumes through the site's SNA.
Path-Aware Capture
Named virtual platforms retain their qualified native, host-assisted or full-source-read path.
P2V Built In
Recover a supported physical Windows backup as a VM on CloudStack.
Backup, Replication, Recovery
One Recovery Model, Not A Stack Of Point Tools.
The same platform path handles source capture, repository storage, live replication, file recovery, application recovery and platform conversion.
Replication Becomes A Recovery Workflow
Keep controller VMs ready at the DR site so failover is activation, not a full restore project.
One Protection Model Across Platforms
Native backup paths and source-aware capture feed the same repository, validation and restore operating model.
Recovery Starts Before Full Restore
Mount backups, browse files, recover application items and start VMs without rebuilding everything first.
Live Replication
Replicate Across Platforms. Restore Across Platforms.
This is not just backup copy. Nutanix AHV can be the source or target with VMware, CloudStack, OSSEA and Azure, while Sendense keeps recovery targets ready and lets operators restore to the selected supported platform.
Replication Paths
Hot Standby Targets Stay Ready.
CloudStack / OSSEA
Automatic Driver Injection
Azure
Native
VMware / CloudStack / OSSEA / Azure
Supported Cross-Platform Path
Nutanix AHV
Supported Cross-Platform Path
CloudStack
Native
Azure
Native
CloudStack
Automatic Driver Injection
CloudStack
P2V Conversion
Restore Paths
Recovery Does Not Have To Land Where It Started.
CloudStack / OSSEA
Auto Driver Injection
Azure
Native
VMware / CloudStack / OSSEA / Azure
Supported Cross-Platform Path
Nutanix AHV
Supported Cross-Platform Path
VMware
Auto Driver Injection
Azure
Native
CloudStack
Auto Driver Injection
CloudStack
P2V Conversion
File-Level Recovery
Mount any backup, browse files and recover what users need without running a full VM restore.
Application-Aware Recovery
Recover SQL Server and Active Directory from application-consistent backups, with file recovery for the surrounding workload.
Instant VM Recovery
Boot VMs directly from backup storage for immediate access while full restore completes.
From Capture To Recovery Evidence.
Each protected workload enters the same operating loop: capture the right data, track changes, store efficiently, replicate, convert and recover.
Capture
Use the best source path: native API, storage-level integration or source-aware capture.
Track
Native change maps are used when the source exposes them; other paths scan and read the source safely.
Store
Recovery points land in the Sendense repository path with EBA efficiency and governance.
Replicate
Hot standby targets stay close enough for operational failover targets.
Convert
Drivers and boot behavior are prepared when the target platform differs.
Recover
Operators restore files, applications, VMs or whole services from the same evidence-backed path.
EBA
Data Reduction
Repository efficiency
Hot
Failover Mode
Prepared activation
Policy
RPO Control
Scheduled synchronization
Named
Platforms
Backup and restore
Backup Replication FAQs
FAQs for Backup and Replication.
Short answers about platform support, cross-platform replication, physical server backup and recovery workflows.
01What Platforms Can Sendense Back Up?
Sendense protects VMware, Nutanix AHV, CloudStack, OSSEA, Azure and supported physical Windows servers. Nutanix AHV is a full production platform with direct Prism Element integration and the same EBA and recovery proof benefits as VMware and CloudStack.
02Can Sendense Replicate Between Different Platforms?
Yes. Nutanix AHV can be the source or target for replication and recovery to and from VMware, CloudStack, OSSEA and Azure. Physical Windows recovery uses its separate agent-based backup and CloudStack P2V path.
03Does Nutanix AHV Support Require Prism Central?
No. Sendense integrates directly with Prism Element by design and does not use or require Prism Central. Nutanix AHV receives the same full backup, bidirectional replication, EBA repository and recovery proof benefits as VMware and CloudStack.
04How Does Sendense Support Hot Standby Failover?
Sendense keeps selected destinations synchronized and supports planned, test and emergency activation workflows. Achievable RPO and failover time depend on policy, connectivity, workload behavior and target readiness.
05Does Sendense Support Physical Server Backup?
Yes. Sendense supports physical Windows servers through an enrolled Windows agent, with VSS-aware backup and P2V recovery to CloudStack.
06Can Sendense Restore Individual Files Or Applications?
Yes. Sendense supports file-level recovery, application-aware recovery and instant VM recovery so operators do not always need to run a full restore first.
Stop Juggling Backup Tools Across Your Supported Platforms.
Review your backup, replication and restore paths with a Sendense architecture session built around your actual workload mix.