# What's new in this release

### Strategic Integration with Platform9

Platform9 is an enterprise private cloud provider whose flagship product, **Private Cloud Director**, delivers SaaS-managed OpenStack and Kubernetes infrastructure. Organizations running Platform9 get the operational simplicity of a managed control plane without sacrificing the architecture of a fully open platform.

Version 7.5 introduces native integration with Platform9, meaning workloads running on Platform9-managed OpenStack clusters can now be protected directly through Storware Backup and Recovery — with the same policy-driven backup scheduling, granular restore, and multi-destination support available for every other supported hypervisor.

This is a significant step for organizations that chose Platform9 precisely because it removes operational friction. Backup should work the same way.

### V2V Migration: Citrix Hypervisor and XCP-ng to OpenStack

Storware has supported [VM-to-VM (V2V) migration from VMware to OpenStack](https://storware.eu/solutions/v2v-migration/) for some time. Version 7.5 extends that capability to two additional source platforms: **Citrix Hypervisor** and **XCP-ng**.

For organizations currently running Citrix or XCP-ng environments that are planning — or mid-execution on — an OpenStack migration, this closes an important gap. The migration path is handled within the same backup workflow: VMs are backed up from the source hypervisor and can be cross-restored directly into an OpenStack environment, with no additional migration tooling required.

Operationally, this means:

* No vendor lock-in constraint when moving from Citrix or XCP-ng
* Migration progress can be staged — workloads move on your schedule, not the hypervisor vendor’s
* The same backup infrastructure that protects production workloads also drives the migration

VMware-to-OpenStack migration support remains available and continues to be the most-requested migration path in the platform.

### Nutanix: v4 API Support and a Redesigned VM Backup Workflow

Nutanix has been steadily moving its platform APIs from v3 to v4, and v4 brings a materially different approach to how VMs and storage are represented. The headline change relevant to backup: the shift to **volume groups** as the backing construct for VM disks in v4.

Storware 7.5 introduces full Nutanix v4 API support, including a redesigned VM backup workflow that leverages volume groups correctly. The practical benefits are improved performance at scale, better alignment with how Nutanix AHV actually manages storage under v4, and forward compatibility as Nutanix continues evolving the platform. Organizations running Nutanix at scale will find this particularly relevant — v4 support is the foundation for performance and reliability improvements that aren’t possible on the older API.

### Proxmox: Ceph v19 Support and Synthetic Backup via SSH

Two independent improvements for Proxmox environments landed in 7.5:

**Ceph v19 compatibility.** Proxmox deployments using Ceph as a storage backend can now upgrade to Ceph v19 without breaking backup support. This was a dependency constraint for a meaningful portion of Proxmox + Ceph users who were holding back on the Ceph upgrade to avoid disrupting their backup pipeline. That blocker is now removed.

**Synthetic backup via SSH transfer strategy.** Storware 7.5 adds support for using a synthetic backup destination with Proxmox environments using the SSH transfer strategy. Synthetic backups — sometimes called forever-incremental — maintain a virtual full backup by merging incrementals, which reduces backup windows, lowers storage load, and cuts network consumption significantly in environments with large or frequently-changing VMs. This is particularly effective for Proxmox deployments where backup windows were being stretched by full backup frequency.

### OpenStack: Inventory Sync, Partial Project Updates, Metadata Protection, and Multithreaded Reads

Several targeted improvements were made to the OpenStack integration in 7.5, each addressing specific pain points observed in production deployments:

* **Faster and more granular inventory synchronization.** Inventory sync now runs faster with optional domain scanning, so large multi-tenant OpenStack environments don’t pay a full-inventory cost when only a subset of projects needs to be refreshed.
* **API-driven partial project inventory synchronization.** Projects can now be updated independently via API, which is important for dynamic environments where new projects are provisioned frequently. Previously, a full sync was required to pick up new projects — now it’s targeted and on-demand.
* **Enhanced backup metadata protection.** Recovery consistency has been improved through better protection of backup metadata. In practice, this reduces the risk of partial or inconsistent restores in edge-case failure scenarios.
* **Multithreaded reads for OpenStack and OpenShift Virtualization.** Backup throughput for both OpenStack and OpenShift Virtualization workloads gets a significant boost from new multithreaded read support. For environments with large VMs or high-IOPS workloads, this is the most immediately impactful performance change in the release.

### OS Agent: Metadata Database Reliability and Purge Optimization

Two improvements to the OS Agent address operational correctness in large and multi-tenant environments:

**Metadata database reliability.** The OS Agent’s internal metadata database handling has been made more robust, reducing the risk of corruption or inconsistency under heavy load or unexpected process termination.

**Optimized object comparison in the purge process.** Purge operations — which clean up expired backup data — now perform object comparison faster. In large environments with many retained restore points, this was a source of operational delay. The optimization makes purge significantly more efficient, which matters in multi-tenant environments where purge operations compete with ongoing backup schedules.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.storware.eu/whatsnew.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
