Proxmox 8.2.4 - Veeam agent

[danielt]

Hi,
Did someone succeed to install the Veeam agent and backup as volume level the host?
I receiving the next errors:
8/7/2024 11:20:37 AM Succeeded Processing 192.168.3.14
8/7/2024 11:20:39 AM Succeeded 192.168.3.14 state updated
8/7/2024 11:20:46 AM Succeeded [192.168.3.14] Preparing Veeam Agent for Linux installation
8/7/2024 11:20:46 AM Succeeded [192.168.3.14] Package veeam_6.1.2.1781_amd64.deb has been uploaded
8/7/2024 11:20:46 AM Succeeded [192.168.3.14] Package veeam-libs_6.1.2.1781_amd64.deb has been uploaded
8/7/2024 11:20:46 AM Succeeded [192.168.3.14] Package blksnap_6.1.2.1781_all.deb has been uploaded
8/7/2024 11:20:46 AM Failed [192.168.3.14] Failed to install veeam_6.1.2.1781_amd64.deb, veeam-libs_6.1.2.1781_amd64.deb and blksnap_6.1.2.1781_all.deb packages: E: Unable to locate package linux-headers-6.8.4-2-pve E: Couldn't find any package by glob 'linux-headers-6.8.4-2-pve' E: Couldn't find any package by regex 'linux-headers-6.8.4-2-pve' Failed to invoke rpc command 0:00:13
8/7/2024 11:21:00 AM Failed [192.168.3.14] Failed to install Veeam Agent for Linux: E: Unable to locate package linux-headers-6.8.4-2-pve E: Couldn't find any package by glob 'linux-headers-6.8.4-2-pve' E: Couldn't find any package by regex 'linux-headers-6.8.4-2-pve' Failed to invoke rpc command
8/7/2024 11:21:09 AM Succeeded Backup agent is not installed
8/7/2024 11:21:10 AM Failed Processing finished with errors at 8/7/2024 11:21:10 AM

Thanks
Daniel

 

[Falk R.]

Hi,
As a rule, this is not a good idea. If you deviate from the default setup and do not use disk pools (LVM-Thin / ZFS) and provide your disks with a file system and the VMs as qcow, then it could work.
As soon as you have a standard installation, it won't work because Veeam can only handle file systems and no pooling mechanism.

 

[danielt]

Hi Falk,
I using LVM-thin.
there a way that veeam will work on the new proxmox version?

 

[VictorSTS]

E: Unable to locate package linux-headers-6.8.4-2-pve E: Couldn't find any package by glob 'linux-headers-6.8.4-2-pve' E: Couldn't find any package by regex 'linux-headers-6.8.4-2-pve'

apt install proxmox-default-headers should install you currently installed kernel's headers. No idea if it will work or not afterwards. I strongly suggest you try this in a testing server before trying it in your production ones.

 

[danielt]

If not veeam which better solution do I have? only the PBS?

 

[Falk R.]

Veeam 12.2 comes with Proxmox support, then you can back up your VMs. However, you will need a proxy VM as with vSphere Hot Add mode.

The best solution at the moment is the PBS, it is fully integrated, fast, efficient and offers live restore and file restore.

Application Aware must also be done with the agent in the first Veeam for Proxmox version, as this is not yet implemented.

 

[Magnus-mercer]

If not veeam which better solution do I have? only the PBS?

Maybe you can try Vinchin Backup & Recovery, it offers multiple backup strategies, instant recovery and file-level recovery. But it focuses on virtual machine backup and does not seem to be able to backup containers.

 

[Falk R.]

Maybe you can try Vinchin Backup & Recovery, it offers multiple backup strategies, instant recovery and file-level recovery. But it focuses on virtual machine backup and does not seem to be able to backup containers.

I have try Vinchin, but the PBS works better.

 

[danielt]

I succeed to install the veeam agent on proxmox, and also add sucsfully to Veeam backup & repliaction server.
If I backup the server as bare metal is working without any problem.
but when I trying to backup as volume gateway and enter the path for the vm`s disks, its failing because veeam not found the path.
What the excalty path on proxmox server lvm-thin for the disks?
I think the path are for example vm-102
/local-lvm/vm-102-disk-0
/local-lvm/vm-102-disk-1

Thanks

 

[Falk R.]

There is no Path. A LVM-Thin Pool is a Block Device (LVM Partitions) an no Filesystem. Veeam Agent can only work with Filesystems.

The only way to use Veeam Agent (VM Backups are only Crash consistent) is: Delete LVM Pool, create a Filesystem, add Filesystem as Directory to PVE, create VMs with qcow2 Disks on these Filesystem.
I don’t recommend this.

 

[danielt]

Can I install the PBS server like a virtual machine?
Thanks

 

[Falk R.]

Can I install the PBS server like a virtual machine?
Thanks

Yes, of course you can.
I still recommend passing dedicated disks natively to this VM and backing up the PBS as a VZDUMP backup to a NAS or USB device.

If the PVe dies, you can simply restore the PBS from the VZDUMP and if the disks are available in the new server, you can restore directly from the PBS.

 

[itret]

Maybe you can try Vinchin Backup & Recovery, it offers multiple backup strategies, instant recovery and file-level recovery. But it focuses on virtual machine backup and does not seem to be able to backup containers.

I'd like to share my experience with Vinchin, I hope you will find this info useful.

This backup software is nice and has a lot of features (eg. will let you migrate your VMs from Hyper-V to Proxmox) but in my case its agent was causing serious issues on my VMs running MS SQL server during database and transaction log backups .

Here's and example.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="SQLWRITER" />
  <EventID Qualifiers="0">24583</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2024-11-04T23:00:55.851197800Z" />
  <EventRecordID>80043</EventRecordID>
  <Channel>Application</Channel>
  <Computer>sql.domain.local</Computer>
  <Security />
  </System>
- <EventData>
  <Data>ICommandText::Execute</Data>
  <Data>0x80040e14</Data>
  <Data>SQLSTATE: 42000, Native Error: 3013 Error state: 1, Severity: 16 Source: Microsoft SQL Server Native Client 11.0 Error message: BACKUP DATABASE is terminating abnormally. SQLSTATE: 42000, Native Error: 3271 Error state: 1, Severity: 16 Source: Microsoft SQL Server Native Client 11.0 Error message: A nonrecoverable I/O error occurred on file "{47D69ED0-DD9F-4CE0-98EF-2275763372BC}3:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). SQLSTATE: 01000, Native Error: 4035 Error state: 1, Severity: 0 Source: Microsoft SQL Server Native Client 11.0 Error message: Processed 0 pages for database 'xxx', file 'xxx' on file 1.</Data>
  <Binary>53514C434F4E4E43313237320000000053514C434F4E4E433132333700000000</Binary>
  </EventData>
  </Event>

This has been tested with build: 8.0.0.47864 and Proxmox 8.2.4. I've sent details and logs to the developer so it may get fixed sooner or later.
For now I had to remove Vinchin agent and everything is working fine.

 

[Magnus-mercer]

I'd like to share my experience with Vinchin, I hope you will find this info useful.

This backup software is nice and has a lot of features (eg. will let you migrate your VMs from Hyper-V to Proxmox) but in my case its agent was causing serious issues on my VMs running MS SQL server during database and transaction log backups .

Here's and example.

- <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
- <System>
  <Provider Name="SQLWRITER" />
  <EventID Qualifiers="0">24583</EventID>
  <Level>2</Level>
  <Task>0</Task>
  <Keywords>0x80000000000000</Keywords>
  <TimeCreated SystemTime="2024-11-04T23:00:55.851197800Z" />
  <EventRecordID>80043</EventRecordID>
  <Channel>Application</Channel>
  <Computer>sql.domain.local</Computer>
  <Security />
  </System>
- <EventData>
  <Data>ICommandText::Execute</Data>
  <Data>0x80040e14</Data>
  <Data>SQLSTATE: 42000, Native Error: 3013 Error state: 1, Severity: 16 Source: Microsoft SQL Server Native Client 11.0 Error message: BACKUP DATABASE is terminating abnormally. SQLSTATE: 42000, Native Error: 3271 Error state: 1, Severity: 16 Source: Microsoft SQL Server Native Client 11.0 Error message: A nonrecoverable I/O error occurred on file "{47D69ED0-DD9F-4CE0-98EF-2275763372BC}3:" 995(The I/O operation has been aborted because of either a thread exit or an application request.). SQLSTATE: 01000, Native Error: 4035 Error state: 1, Severity: 0 Source: Microsoft SQL Server Native Client 11.0 Error message: Processed 0 pages for database 'xxx', file 'xxx' on file 1.</Data>
  <Binary>53514C434F4E4E43313237320000000053514C434F4E4E433132333700000000</Binary>
  </EventData>
  </Event>

This has been tested with build: 8.0.0.47864 and Proxmox 8.2.4. I've sent details and logs to the developer so it may get fixed sooner or later.
For now I had to remove Vinchin agent and everything is working fine.

Thanks for sharing your experience! It’s great that you’ve already sent the details and logs to the developer — hopefully, they’ll address the issue in future updates.