Upgrading on Protected Computer Side
You must perform the upgrade of Veeam Agent on the computers added to protection groups for pre-installed Veeam Agents on the protected computer side.
NOTE |
Upgrade of Veeam Agent on the protected computer side is the only option available for Veeam Agent for Mac. |
TIP |
During each synchronization session, Veeam Backup & Replication checks the version of Veeam Agents installed on the protected computers. If the Veeam Agent version does not coincide with the version of Veeam Backup & Replication, Veeam Agent computer will be moved to the Out of Date protection group. |
Before You Begin
Before you upgrade pre-installed Veeam Agent, do the following:
- Check that the latest update for Veeam Backup & Replication is installed on your backup server. To learn more, see the Upgrading to Veeam Backup & Replication 12.2 section in the Veeam Backup & Replication Guide.
- Make sure that Veeam Backup & Replication remote components, such as the distribution server, are updated.
- Make sure that a user account that you plan to use for installation on the Veeam Agent computer side has Local Administrator privileges.
Updating Protection Group Settings
To update pre-installed Veeam Agent, you must generate new Veeam Agent setup files on the Veeam Backup & Replication side. To do so, edit the protection group settings:
- Open the Inventory view.
- In the inventory pane, expand the Physical Infrastructure node.
- In the inventory pane, select the protection group for pre-installed Veeam Agents that you want to update and click Edit Group on the ribbon or right-click the protection group for pre-installed Veeam Agents that you want to update and select Properties.
- At the Package step, check that the export path and setup files for OSes that run on computers with Veeam Agents you want to update are specified correctly.
- Click Apply to generate setup files. Then click Finish to close the wizard.
Upgrading Veeam Agent on the Protected Computer Side
On the Veeam Agent computer side, the update procedure differs depending on the OS of the protected computer: