Platform9 just got enterprise-grade backup and recovery.

Storware Backup and Recovery 7.5 introduces native support for Platform9 Private Cloud Director. The same proven, agentless engine protecting your VMware, Proxmox, and OpenShift environments — now extended to OpenStack workloads running on Platform9.

Get your free 60-day trialA premium experience with extended access

Five reasons Platform9 teams choose Storware.

Platform9 Private Cloud Director is built on KVM and standard OpenStack APIs. That means the backup platform protecting it needs to understand Cinder snapshots, Nova inventory, Keystone domains, and Glance images — not just “virtual machines in general.” Storware has been built around exactly this stack since 2015.

Native OpenStack integration
Storware communicates via Nova, Cinder, Glance, and Neutron APIs — the exact stack Platform9 Private Cloud Director is built on. No translation layer, no custom agents on hypervisor hosts.
Any storage backend
NFS, iSCSI, Fibre Channel, or Ceph RBD — Storware has a backup strategy for each. The right method is selected at setup, not discovered during an incident.
One policy engine, all hypervisors
Backup schedules and retention rules defined for VMware or Proxmox apply directly to Platform9 VMs. Nova tag-based auto-assignment means new VMs are protected from first inventory sync.
No extra license required
Storware’s universal licensing covers all supported hypervisors under a single agreement. If Storware already protects your other environments, Platform9 is activated by configuration — not by procurement.
Restore to Platform9, not just from it
Storware’s backup format is hypervisor-agnostic. VMs backed up from VMware can be restored directly into Platform9 — so data protection doesn’t have to wait for the migration to complete.

Solution PDF Product Leaflet How to build BaaS using OpenStack and Storware

Get Your Free 60-Day Trial

First name *

Last name *

Company*

Business Email*

Phone Number*

State / Country*

I want to receive information and updates on Storware solutions, events and promotions, and other Storware communications.

I have read and agree to the below Privacy Policy information. Read privacy statement here*

To receive this amazing tech guide, please submit the form below.

First name *

Last name *

Phone *

Business Email *

Company *

Country *

Please opt-in to receive future marketing communication form Storware.
By clicking the button below, you acknowledge our Privacy Policy.

Built for the way
Platform9 environments actually work.

Storware integrates at the API layer — not at the hypervisor agent layer — which means it follows the same management model Platform9 is built on.

Cross-hypervisor V2V migration

Backed-up Platform9 VMs can be restored to other supported hypervisors. Supports workload portability without re-architecting your backup infrastructure.

Multi-domain OpenStack auth

Supports both unscoped (single credential, multiple domains) and scoped (per-domain credentials) authentication. Works with LDAP-integrated Platform9 environments and Keystone federation.

Policy-based automation

Assign backup schedules, retention policies, and storage targets by VM name or Nova tag. Policy inheritance means new VMs are protected from first boot without manual intervention.

Instant VM restore

Mount backup data directly as an NFS-backed Cinder volume — VMs become accessible in minutes. Production migration runs in the background while the restored VM is already operational.

Immutable backup destinations

Write-once storage targets protect backup data from ransomware modification. Works with local filesystems, S3-compatible object storage, and Storware Cloud tiers.

Unified RTO/RPO management

Set and monitor recovery time and recovery point objectives from a single control plane — covering Platform9 alongside every other hypervisor in the environment.

Three backup strategies.

Storage-backend-independent incremental backups using block-level checksum comparison. Preferred for most Platform9 environments where Ceph monitor access from the proxy VM is not available.

Crash-consistent snapshot via Cinder API
Volumes attached to Proxy VM one by one
Incremental via block-level checksum
Pre/post command hooks for app consistency
Full, incremental, and synthetic backups

For environments with Ceph RBD as the storage backend. Changed block information is fetched directly from Ceph monitors — reducing data transferred per incremental cycle.

Snapshot via Cinder API
CBT-like incremental from Ceph monitor
Ceph monitor access required from Proxy VM
Ports 3300/tcp, 6789/tcp
Full and incremental backups

Direct access to KVM hypervisors via SSH. Suitable for environments where hypervisor-level access is permitted. Supports QCOW2/RAW files and Ceph RBD as storage backends.

virsh snapshot, rbd snapshot for Ceph
Data exported via SSH (or netcat)
No Proxy VM required
SSH + netcat port range required
Full and incremental backups

Up and running in three steps.

Add Platform9 as an OpenStack Hypervisor Manager in Storware, pointing to the Keystone URL: https://KEYSTONE_HOST:5000/v3. Configure authentication domain credentials and choose backup strategy.

Storware discovers all VM instances, Cinder volumes, Nova tags, and flavors via OpenStack APIs. Proxy VM is provisioned in the relevant Availability Zone automatically.

Apply existing backup schedules by VM name or Nova tag. First full backup runs immediately. Subsequent incrementals reduce storage and transfer overhead.