Sales Chat - Click Here

Knowledge Base

Search by either entering keywords/KB_ID or by selecting a category.

KB ID: 6259

Product: TS5010 Series | TS6000 Series | TS5020 Series | TS71210 Series | TS3010 Series | TS3020 Series | LS700 Series | TS-Essentials Series 2022 | TS Essentials Series 2025

Restore a VMware VM from a Veeam Backup on Buffalo NAS to Proxmox VE

Last Updated: 11/05/2026


Purpose

This KB describes how to restore an existing VMware VM backup stored on a Buffalo NAS to Proxmox VE using Veeam Backup & Replication.

Prerequisites

Before starting:

  • Verify the VMware VM backup is visible under Home > Backups > Disk.
  • Verify the Buffalo NAS backup repository is online.
  • Verify the target Proxmox host has sufficient storage.
  • Verify Veeam can communicate with the Proxmox host.
  • Make sure the installed Veeam Plug-in for Proxmox VE supports the installed Proxmox VE version.

Veeam Proxmox Plug-in version information:
https://www.veeam.com/kb4706

Veeam Proxmox system requirements:
https://helpcenter.veeam.com/docs/vbr/userguide/pve_system_requirements.html

1. Add Proxmox VE to Veeam

Go to:

Backup Infrastructure > Managed Servers > Add Server

Select Virtualization Platforms.

Select Proxmox VE.


 

Enter the Proxmox Server Address

Enter the DNS name or management IP address of the Proxmox standalone host or cluster node.

Use an address that can be reached by both the Veeam Backup Server and the Proxmox Worker.

Click Next.


Configure Credentials

Select or add a Proxmox account with root privileges.

Click Next.


Configure Snapshot Storage

Select the appropriate snapshot storage.

Click Apply.

Veeam should successfully register and refresh the Proxmox server.

2. Deploy a Proxmox Worker

Veeam requires at least one Proxmox Worker to process backup and restore operations.

When prompted to deploy a Worker, click Yes.

Configure the Worker VM

Example configuration:

  • Name: WorkerVM
  • Storage: local-zfs
  • Maximum concurrent tasks: 4
  • CPU: 6 vCPU
  • RAM: 6 GB

Click Next.


Configure the Worker Network

Click Add and select the appropriate Proxmox bridge.

Example:

  • Network: vmbr0
  • IP address: 192.168.11.95
  • Subnet mask: 255.255.255.0
  • Default gateway: 192.168.11.1
  • DNS server: 192.168.11.1

Important: The Worker IP must belong to the subnet used by the selected Proxmox bridge.

For example, if vmbr0 is on 192.168.11.0/24, the Worker must also use a 192.168.11.x address.


Test the Worker

On the Summary page, enable:

Test the worker configuration when I click Finish

Click Finish and verify that the Worker test completes successfully.

3. Start the VMware-to-Proxmox Restore

Go to:

Home > Backups > Disk

Locate the VMware VM backup.

Right-click the VM and select:

Restore entire VM to Proxmox VE

4. Select the VM and Restore Point

Verify the VM and restore point.

Use Point... if a different restore point is required.

Click Next.

5. Select Restore Mode

Select:

Restore to a new location, or with different settings

Click Next.

6. Select the Target Proxmox Host

Select the destination Proxmox node.

Click Next.

7. Select Target Storage and Disk Type

Select the desired Proxmox storage.

Example:
local-zfs

For ZFS storage, select:
RAW

 

Click Next.

8. Set the VM Name

Keep the original name or assign a temporary test name.

Click Next.

9. Leave the Network Disconnected

During the initial restore, leave the VM network adapters disconnected.

This prevents duplicate IP address or hostname conflicts while the original VMware VM is still running.

Click Next.

10. Review and Start the Restore

For the initial test, leave Power on target VM after restoring unchecked.

Click Finish.

11. Monitor the Restore

Veeam will start the Proxmox Worker and restore the VM from the Buffalo NAS backup repository.

Wait until the restore session completes successfully.

After the Restore

Once the restore shows Success, start the VM from the Proxmox console while keeping the production network disconnected.


Windows Boot Loop / Startup Repair

A restored Windows VM may continuously enter Automatic Repair or Startup Repair.

This can occur when the restored VM uses a VirtIO SCSI disk controller but Windows does not yet have the required VirtIO boot storage driver.

Fix:

  1. Shut down the restored VM.
  2. Go to Proxmox > VM > Hardware.
  3. Select the OS disk and choose Detach.
  4. Do not delete the disk.
  5. Select the resulting Unused Disk.
  6. Reattach the disk as SATA0.
  7. Go to Options > Boot Order.
  8. Make sure SATA0 is enabled and first in the boot order.
  9. Start the VM again.

Changing the restored Windows OS disk from VirtIO SCSI to SATA resolved the boot loop during testing.
 

Optional – Preserve SMBIOS UUID
Some software licensing or inventory systems may identify a VM by its SMBIOS System UUID. If required, record the System UUID from the original VMware VM and configure the same SMBIOS UUID on the restored Proxmox VM. This does not guarantee that Windows or other software will remain activated.

 

Final Checks

  • Confirm Windows and required applications start normally.
  • Install the QEMU Guest Agent if required.
  • Remove VMware Tools when no longer needed.
  • Check the static IP configuration because Windows may detect the Proxmox NIC as a new adapter.
  • Shut down the original VMware VM before connecting the restored Proxmox VM to the production network.

Do not run the original VMware VM and the restored Proxmox VM on the production network at the same time if they use the same hostname or IP address.

Related Articles

External References

X