Agent-based backup of Windows, Linux, Max, AIX and Solaris machines.
Post Reply
cosmik
Enthusiast
Posts: 79
Liked: 10 times
Joined: Jan 23, 2021 10:14 am
Full Name: Michael Pappas
Contact:

Upgrading a "managed by agent" installation (and other questions)

Post by cosmik »

Hello everybody, glad to be in the Veeam f0s again :)

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: Select all

General ------------------------------------------
Backup job name: backup job
Backup job description:
Created by -


Source -------------------------------------------
Backup mode: volume level backup
Included items:
	(A single disk which is mapped to an iSCSI volume)


Destination --------------------------------------
Veeam Agent for Microsoft Windows repository
	Backup server: xxx
	Backup repository: xxxxx-repo
Keep restore points for the last 14 days
Compression level: Optimal (recommended)
Storage optimization: Local target
Storage encryption: disabled
Perform backup files health check monthly on the last Friday of January, February, March, April, May, June, July, August, September, October, November, December
GFS: enabled


Backup cache -------------------------------------
Backup cache is disabled


Guest processing ---------------------------------
Application-aware processing: [enabled]
Process transaction logs with this job

Microsoft SQL transaction logs: [truncate logs]

Oracle transaction logs:
Do not delete archived logs

Microsoft SharePoint application:

Guest file system indexing: [disabled]

Script processing: [disabled]


Schedule -----------------------------------------
Schedule: server
On [Τρι, Τετ, Πεμ, Παρ, Σαβ] at [3:00 πμ]
Retry failed job 3 times
Wait before each retry attempt for: 10 minutes
Create synthetic backups full on Friday


Command line to start the job:
"C:\Program Files\Veeam\Endpoint Backup\Veeam.EndPoint.Manager.exe" xxxx
Mildur
Product Manager
Posts: 10355
Liked: 2773 times
Joined: May 13, 2017 4:51 pm
Full Name: Fabian K.
Location: Switzerland
Contact:

Re: Upgrading a "managed by agent" installation (and other questions)

Post by Mildur » 1 person likes this post

Hi Michael

Welcome back :)
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)
When you mention XML, I assume someone used "protection groups for pre-installed Veeam Agents." In this scenario, an installation package with a configuration XML file is created. Another option is manual installation using our agent configurator tool.
In both cases, you need to update the agent manually on your Windows server.

If "protection groups for pre-installed Veeam Agents" was used, please follow the procedure in our Helpcenter.
If the agent was deployed manually with the agent configuration tool, download the latest agent from our website and execute the update directly on the machine with the agent.
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".
Standalone Agent backup jobs targeting a Veeam backup repository do not have their own encryption settings. They use the encryption setting configured on your repository.

Best,
Fabian
Product Management Analyst @ Veeam Software
cosmik
Enthusiast
Posts: 79
Liked: 10 times
Joined: Jan 23, 2021 10:14 am
Full Name: Michael Pappas
Contact:

Re: Upgrading a "managed by agent" installation (and other questions)

Post by cosmik »

When you mention XML, I assume someone used "protection groups for pre-installed Veeam Agents." In this scenario, an installation package with a configuration XML file is created. Another option is manual installation using our agent configurator tool.
In both cases, you need to update the agent manually on your Windows server.

If "protection groups for pre-installed Veeam Agents" was used, please follow the procedure in our Helpcenter.
If the agent was deployed manually with the agent configuration tool, download the latest agent from our website and execute the update directly on the machine with the agent.
Hmm, I don't know how it was deployed... Are there tell-signs that can help me identify which case it was?
Standalone Agent backup jobs targeting a Veeam backup repository do not have their own encryption settings. They use the encryption setting configured on your repository.
Thanks for the info buddy!
Post Reply

Who is online

Users browsing this forum: No registered users and 14 guests