Skip to main content

How to: Migrating Druva Phoenix Backup Store (PBS) from VMWARE to Nutanix AHV environment

How to: Migrating Druva Phoenix Backup Store (PBS) from VMWARE to Nutanix AHV environment

Overview

Standard "lift-and-shift" migration via Nutanix Move is not supported for the Druva Phoenix Backup Store (PBS). Because the PBS is a purpose-built appliance with deep kernel-level dependencies for storage (ZFS) and networking (NFS), moving the existing VM image can lead to driver conflicts and data corruption. To ensure a stable and supported environment on Nutanix AHV, the appliance must be redeployed as a fresh instance and re-registered to the Druva Cloud.

Problem Statement

Standard migration utilities inject new VirtIO drivers and modify guest tools to facilitate the move to AHV. For a specialized appliance like the Druva PBS, these modifications often lead to:

  • Storage Incompatibility: Failure to mount or import ZFS pools.

  • Service Instability: Conflicts between Nutanix Guest Tools and Druva’s hardened OS configurations.

  • Performance Issues: Degraded RMAN backup speeds or network timeouts.

Solution: New Deployment Strategy

To transition to Nutanix AHV, you must deploy a fresh instance of the PBS and register it to your existing Druva Cloud environment.

1. System & Hardware Requirements

Before provisioning the new VM on Nutanix AHV, ensure the environment meets the minimum compute, memory, and storage specifications.

Hardware Specifications: For detailed hardware requirements for the Phoenix Backup Store, refer to the official documentation: System requirements for Oracle PBS

2. Installation & Registration

The migration involves installing the Druva PBS Debian package onto a clean Ubuntu 22.04 instance. Do not attempt to copy the virtual disk (VMDK) from the old VMware instance.

Official Procedure: Follow the step-by-step instructions in the Druva Documentation: Deploy and register Phoenix Backup Store

Maintenance Guidelines

  • Dedicated Instance: To maintain appliance integrity, the server should remain a dedicated instance. Installing third-party software or using it as a general NFS server may interfere with Druva-managed mounts.

  • Maintenance Windows: Only apply OS patches or reboots when there are no active RMAN backup or restore jobs to prevent data corruption.

Did this answer your question?