u/tlrman74

Now that Veeam Backup 13.1 has been released and is supposed to have Windows Application-Aware processing for Proxmox, has anyone been successful in getting it to work?

Using Proxmox 9.1 host.

I have a test SQL VM with the QEMU Guest Agent installed and VSS is working correctly, but when a backup job is run with application-aware configured for SQL the Qemu Guest Agent VSS and Volume Shadow services just crash.

Eventlog:

Faulting application name: qemu-ga.exe, version: 100.0.0.0, time stamp: 0x5c473543
Faulting module name: KERNELBASE.dll, version: 6.1.7601.24545, time stamp: 0x5e0eb6bd
Exception code: 0xc0000005
Fault offset: 0x000000000000c4d2

I've created the deployment kit and installed the persistent agent on the VM to see if that would resolve it, but the Proxmox job settings do not have the checkbox to use the persistent agent.

Un-checking the application-aware setting in the job results in successful backup job.

I kind of feel like this is still beta for Proxmox. Anyone been able to get a successful backup?

I'm looking at migrating from the Windows installed Veeam Backup and Replication v13 to the Software Appliance. One area I'm uncertain of is the current Windows Server where Veeam is installed has the dedup service installed to handle windows server file and folder restores on deduplicated disks.

If I migrate to the Veeam Appliance, can I designate a Windows Server that has dedup services enabled as a proxy for the restore job?

I've run into a weird issue with Odoo in Docker. I've stood up a new server and created a test Odoo instance. I log in as admin and change the company name from "My Company" and save the updated info. If I don't restart the Odoo instance the company name changes stay. But, if I restart the Odoo container the original company name is restored.

What is weird is it's not every field within the company info. The company address state is save but the not the street address. If I update the company logo it is not saved after a restart either but is stored in the filestore on the local server.

I've verified the docker compose has the required volumes and local folder paths configured. I can also see the values I enter are recorded in the database and the record history. I'm not sure what event is being triggered on restart of the container that would run an update to the company record.

Just looking for another place to check why this would occur.

I'm rethinking the entire implementation of my VEEAM Backup 13 infrastructure and have been looking at updating the service accounts used to backup vm's. Has anyone migrated to gMSA as the primary accounts to backup VMWare and Proxmox VM's?

For Linux VM's none of them a domain joined so I'll stick with the stored Linux accounts for now.

If you have moved away from standard domain accounts, have you had issues with gMSA accounts?

Current setup -

VEEAM Server 2019 - not-domain joined.

Proxmox 9.1 3 hosts.

NFS repo on Synology NAS with backup copy job to VEEAM Cloud Vault.