Host-based backup of VMs running on Red Hat Virtualization, Oracle Linux Virtualization Manager, Scale Computing Hypercore, XCP-ng, HPE VM Essentials.
Locked
cody.ault
Veeam Software
Posts: 54
Liked: 27 times
Joined: Nov 04, 2010 2:53 pm
Full Name: Cody Ault
Contact:

[BETA] [HPE VME] Veeam Plug-In for HPE VM Essentials Beta (December 01, 2025)

Post by cody.ault » 9 people like this post

Version history:

Public Beta (December 01, 2025) > build version 13.1.0.206 (VBR 13.0.1.180)

BUG REPORTS:
1. Open a new topic in this very forum (here).
2. Describe the issue in a detailed yet concise manner.
3. Be ready to gather and provide logs.

Download

Veeam beta site

Password: HPEVMEBeta
File names: (Windows)VeeamPluginHpeMorpheusVme_13.1.0.206.BETA.exe, (Linux VSA) veeam-platform-service-hpemorpheusvme-13.1.0.206-0.el9.x86_64.BETA.bndl

This download contains the plug-in installers for a dedicated beta test Windows or Linux Veeam Backup & Replication server running version 13.0.1.

License

The download includes a 90 day trial key to test up to 1000 instances.
You can also use your existing license file or contact your sales representative if the provided license isn't sufficient.

Beta Features
Overall, beta includes all the functionality planned for 1.0.
There could be some limitations, but all the available features should work:

Backup

- Incremental and full VM backup using CBT
- Ability to select individual VMs, VMs by Tags and Labels, all VMs on cluster or entire HPE
- Morpheus VM Essentials server as a job source
- Support for all backup repository types except Cloud connect repositories and external repositories
- Application-level quiescence for Windows VMs
- Skip dirty blocks on NTFS, skip swap file on NTFS
- Active full, synthetic full, daily retention (point-based retention is not supported)
- Email notifications
- Compression level and block size
- Health Check
- Backup Copy Jobs
- Backup to tape Jobs

Malware detection
posting.php?mode=edit&p=559091#
- ScanBackup
- SureBackup jobs. "Scan only" mode[/list]

Restore

- VM restore to HPE Morpheus VM Essentials cluster
- Disk export as VMDK/VHD/VHDX
- Disk publishing for Windows/Linux
- Guest OS File Restore (Without dedicated mount server appliance)
- Guest OS File Restore (With dedicated mount server appliance on VMware/Hyper-V/Nutanix AHV )
- Veeam Explorers (via heuristics)

System requirements

HPE Morpheus VM Essentials
Version: HPE Morpheus VM Essentials 8.0.11
User roles: System Admin

Windows-Based and Linux-Based backup servers

Follow Veeam Backup & Replication v13 userguide.
Automatic license updates must be enabled in the Veeam Backup & Replication configuration before adding your HPE Morpheus VM Essentials to the backup infrastructure.

Installation process

Do not use a production installation of Veeam Backup & Replication.
Use a separate instance for beta testing.

Download for Backup & Replication v13.0.1 can be found here.

The Veeam Plug-In for HPE Morpheus VM Essentials 1.0 beta will not be automatically included in Veeam Backup & Replication and must be downloaded and installed manually as described in the Veeam Plug-In for HPE Morpheus VM Essentials User Guide.

Limitations & known issues:

General

- Supported datastores where VM volumes reside: Directory Pool, NFS Pool, GFS2 Pool, HPE Alletra Block Storage HVM.

- At least one datastore of the Directory Pool, NFS Pool, GFS2 Pool type must be configured in HPE Morpheus VM Essentials Software since the HPE Alletra Block Storage HVM datastore type is not supported for storing VM snapshots which are created on VM backups.

- If the Veeam Backup & Replication server is registered in Enterprise Manager, it is not possible to add HPE Morpheus VM Essentials to the server. To work around this, temporarily remove the server from Enterprise Manager, add HPE Morpheus VM Essentials to the backup infrastructure, and then re-register the server in Enterprise Manager if necessary.

- Configuration backup with backup file encryption enabled does not work if HPE Morpheus VM Essentials is added to Veeam Backup and Replication server.

- Veeam HPE Morpheus VME Service is not properly managed for High Availability. It must be stopped and started manually when creating a Veeam Backup & Replication cluster and during switch and failover scenarios.

- Veeam Backup & Replication Web UI is not supported for Veeam Plug-In for HPE Morpheus VM Essentials.

Backup Infrastructure

- If HPE Morpheus VM Essentials credentials were changed, you will not be able to open the Edit HPE Morpheus VM Essentials wizard. To change the credentials, open the Datacenter Credentials window in the Veeam Backup and Replication menu.

- The Restore entire VM > HPE Morpheus VM Essentials option in the context menu may become not available (greyed out). To work around the issue, switch to another node. You can also use the ribbon to open the restore wizard.

Backup

- When adding HPE Morpheus VM Essentials to the Veeam Backup & Replication server, a Veeam service user is created on each of the cluster nodes which is managed by that instance of HPE Morpheus VM Essentials. The account is used for SSH connection between worker and cluster node for backup when the VM and worker reside on different nodes.

- If new clusters or cluster nodes appear in HPE Morpheus VM Essentials, going through the Edit HPE Morpheus VM Essentials wizard is required for Veeam service accounts to be created on new clusters and cluster nodes.

- NBD server always starts on backup even if a backup is created in HotAdd mode. However, the SSH connection between the worker and cluster node is not established in this case.

- The Guest quiescence in backup job advanced settings requires the QEMU Guest Agent to be installed on the processed VMs beforehand.

- Tags and labels are united into one entity Tags and labels in the New Backup Job Wizard. It is not possible to select VMs under a tag or label granularly.

- If Veeam HPE Morpheus VME Service has been restarted or the backup server has been rebooted during a backup session, the session may get stuck in the Running state in Veeam Backup & Replication console. To resolve the issue, contact the Veeam SE who shared this beta with you.

- Veeam Plug-in for HPE Morpheus VM Essentials does not support backup of VMs migrated from VMware to HPE Morpheus VM Essentials using the native HPE VME migration mechanism.

- A backup job may fail for a VM with an active backing chain of disks. The issue may occur during HPE Morpheus VM Essentials native clone sessions (for example, VM cloning).

- The backup window for periodically scheduled backup jobs is not supported. For supported scheduling options, see Veeam Plug-In for HPE Morpheus VM Essentials User Guide.

Restore

- The original instance layout must be available in target HPE Morpheus VM Essentials to perform restore.

- The following limitations apply to the Restore to the original location mode:
  • Restore will fail if the original instance exists in the cluster in the Locked state
  • Restore will fail if no owner is configured in parent instance settings
  • Restore will not be possible if the original HPE Morpheus VM Essentials server was removed from the backup infrastructure.
  • Though the Restore to the original location option will be still available in the restore wizard, an error message will be displayed in an attempt to proceed.
The following limitations apply to the Restore to a different location mode:
  • The Require Environment Selection option must be disabled in HPE Morpheus VM Essentials (Administration > Settings > Provisioning > Require Environment Selection)
  • Advanced VM settings (such as automation, user group, domain, affinity group, nested virtualization flag settings) cannot be restored.
  • Virtual machine names must be unique across the whole HPE Morpheus VM Essentials. A VM name must contain only letters, numbers, hyphens “-” and dots “.”, and must not exceed 48 characters in length to proceed with restore
  • When restoring a VM from one cluster to another, a network or a datastore with the same numeric ID from another cluster may be preselected in the restore wizard
  • Horizontally scaled instance configurations are not fully supported. Scaled VMs can be backed up. However, restore to separate instances is available only in the Restore to a different location mode
  • To be able to restore VM volumes to a local datastore, the worker must reside on the same cluster node as the target VM since NBD mode is not supported for restore operations in the beta build
  • vTPM VM settings are not supported for restore to other platforms
Workers

- At least one worker must be deployed in each HPE Morpheus VME cluster – a VM cannot be backed up if no worker resides in the same cluster. For optimal performance, one worker per cluster node is recommended.

- With the default configuration, the worker can handle up to 4 concurrent backup and restore tasks. While deploying a new worker or editing settings of an existing one, the maximum number of concurrent tasks can be changed – the minimum value is 2, the maximum value is 18. 1 vCPU and 1 GB RAM for each additional task must be allocated to the worker VM.

- If the first test of a worker fails, the worker VM must be manually removed from the HPE VME cluster. Otherwise, the worker VM will always fail to be deployed since a VM with the same name will exist in the cluster.

- The Veeam Backup & Replication console can stop responding after a worker test has started using the Test Worker button on the ribbon. Restart the console to resolve the issue.

Sessions

- UUIDs may be shown for different entities instead of user-friendly names.

Log Location

- Windows-Based backup server
...\Veeam\Backup\Plugins\HPEMORPHEUSVME

- Linux-Based backup server
/var/log/VeeamBackup/Plugins/HPEMORPHEUSVME
Locked

Who is online

Users browsing this forum: No registered users and 3 guests