Hello everybody, glad to be in the Veeam f0s again ![:)]( "Smile")
First, the setup. We had had a VBR 11 installation on our VMWare installation, that included mostly the backup of our VMs plus a single "managed by agent" job of a Windows Server system (also VM, but wanted to avoid selecting it as a "managed by backup server" since that would involve storing our AD admin credentials in the VBR server). Upgraded to 12 and just recently after some fuss created with an expired certificate of our vCenter which required tinkering with the VBR server itself we found out that the agent is outdated. Specifically, in the VBR console we get an informational message stating that "Backup agent xxx" requires upgrade. For the record, the installed version on the Windows server box seems to be 5.0.3.4708.
I really can't recall how I installed the agent on the system, I believe it involved the generation of an XML file at some point, but not sure. Anyways, now I have a number of question here:
1) How can I upgrade the agent running on our WS system? From the documentation I've seen plenty of references when the system is part of a protection group but this is not the case here. Do note that the about box of VAW on the WS box does not offer any update option (and if it did, it would not work in our specfic environment)
2) Related to the agent, I can see some inconsistencies: if I check the backup job (type: windows agent policy) from the VBR side it is listed as having encryption. However when checking from the VAW side, no compression is listed when editing the job and checking the summary page. Additionaly, when going to backup repository -> advanced -> storage tab there's a note that "local encryption is not supported for Veeam backup repository".
I'm also attaching the VAW job summary, in case it helps
First, the setup. We had had a VBR 11 installation on our VMWare installation, that included mostly the backup of our VMs plus a single "managed by agent" job of a Windows Server system (also VM, but wanted to avoid selecting it as a "managed by backup server" since that would involve storing our AD admin credentials in the VBR server). Upgraded to 12 and just recently after some fuss created with an expired certificate of our vCenter which required tinkering with the VBR server itself we found out that the agent is outdated. Specifically, in the VBR console we get an informational message stating that "Backup agent xxx" requires upgrade. For the record, the installed version on the Windows server box seems to be 5.0.3.4708.
I really can't recall how I installed the agent on the system, I believe it involved the generation of an XML file at some point, but not sure. Anyways, now I have a number of question here:
1) How can I upgrade the agent running on our WS system? From the documentation I've seen plenty of references when the system is part of a protection group but this is not the case here. Do note that the about box of VAW on the WS box does not offer any update option (and if it did, it would not work in our specfic environment)
2) Related to the agent, I can see some inconsistencies: if I check the backup job (type: windows agent policy) from the VBR side it is listed as having encryption. However when checking from the VAW side, no compression is listed when editing the job and checking the summary page. Additionaly, when going to backup repository -> advanced -> storage tab there's a note that "local encryption is not supported for Veeam backup repository".
I'm also attaching the VAW job summary, in case it helps
Code:
General ------------------------------------------Backup job name: backup jobBackup job description:Created by -Source -------------------------------------------Backup mode: volume level backupIncluded items:(A single disk which is mapped to an iSCSI volume)Destination --------------------------------------Veeam Agent for Microsoft Windows repositoryBackup server: xxxBackup repository: xxxxx-repoKeep restore points for the last 14 daysCompression level: Optimal (recommended)Storage optimization: Local targetStorage encryption: disabledPerform backup files health check monthly on the last Friday of January, February, March, April, May, June, July, August, September, October, November, DecemberGFS: enabledBackup cache -------------------------------------Backup cache is disabledGuest processing ---------------------------------Application-aware processing: [enabled]Process transaction logs with this jobMicrosoft SQL transaction logs: [truncate logs]Oracle transaction logs:Do not delete archived logsMicrosoft SharePoint application:Guest file system indexing: [disabled]Script processing: [disabled]Schedule -----------------------------------------Schedule: serverOn [Τρι, Τετ, Πεμ, Παρ, Σαβ] at [3:00 πμ]Retry failed job 3 timesWait before each retry attempt for: 10 minutesCreate synthetic backups full on FridayCommand line to start the job:"C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Manager.exe" xxxxStatistics: Posted by cosmik — May 08, 2025 6:54 am
