new veeam server - backup agent

[kikanq]

Hi, I have an old Veeam server on which I make copies of another Windows Server via the Veeam agent - a task managed by the server. I already have a new Veeam server to which I want to transfer this task. Do I need to uninstall the agent for the server I am backing up on the old server? Or maybe I can simply add a server on the new Veeam server that wants to make a copy and configure the task (and turn off the old Veeam server).?

[Mildur]

Hello Kikanq

You can use configuration backup/restore to transfer the configuration from one Veeam Server to the other. Agent ownership/configuration will be transferred too.
https://helpcenter.veeam.com/docs/backu ... ml?ver=120

Best,
Fabian

[bstuiver]

Hi, I have a similar question, except this is a current Veeam server that is making copies of some Linux servers via Veeam agent version 6.0.2.1168, in addition to other backup jobs - the Linux agent backup job (one job to backup 3 Linux servers) is also managed by the server.

We have added a new Veeam server (v12.2) that will take over the Linux agent backup.
The other backup jobs will remain on the old Veeam server for now. Therefore, the configuration backup/restore method does not seem suitable to me here
So I need to add the 3 Linux servers to this new Veeam server and create a new backup job for this (don't worry about the old backups, we'll start with new ones)

I would like to know what the procedure for this would be:
Can I use the already installed agent version 6.0.2.1168 and just go ahead and add the Linux server?
Or do I need to remove the agent first and then install the current version? Or is this done automatically by Veeam (install/update to the latest agent version) when adding the server?

Do I also need to decommission something on the old Veeam server? Maybe remove the Linux servers here? Or can I just disable/delete the backup job here?

[Mildur]

Hi Bertus,

I recommend removing the Linux machine from the protection group first (Remove from configuration) on the original backup server. This will keep the agent installed on the machine. After that, you can add the machine to the second server. When you add the Linux machine to a protection group on the new server, the most recent version will automatically be deployed if necessary (v12.2 server --> 6.0.2 agent).
If you don’t remove the machine from the protection group, the first backup server will continue to attempt to contact the agent, which will result in rescan error messages.

We have added a new Veeam server (v12.2) that will take over the Linux agent backup.

I suggest considering starting with v12.3 for the new backup server. It’s important to note the solved security vulnerabilities in v12.3.

Best,
Fabian

[bstuiver]

Thank Fabian,

Clear and reassuring answer!


I noticed something else on the old Veeam server:
A protection group is configured for these 3 Linux servers, but in the scope of the corresponding agent backup job, this protection group is not used. Instead, the 3 servers are filled in here. Does this make a difference and is it better to configure the protection group in the job scope on the new Veeam server?

Finally: can the old Veeam v12 server also work with the agent version after it has been updated by the v12.2 (or 12.3) server ?
I ask this to ensure that we can temporarily fallback on the old server if something happens during this migration to the new server and we need more time to fix it. Or will the old Veeam server revert to the old agent version upon rescanning the protectgroup (after re-adding the server(s)) ?


BR
Bertus

[Mildur]

Hi BErtus

Does this make a difference and is it better to configure the protection group in the job scope on the new Veeam server?

Consider protection groups as groups/containers. If you add more machines to id, they are automatically protected by the same job/policy. I prefer to add protections groups when I can. But in the end it doesn't matter much.

Finally: can the old Veeam v12 server also work with the agent version after it has been updated by the v12.2 (or 12.3) server ?
I ask this to ensure that we can temporarily fallback on the old server if something happens during this migration to the new server and we need more time to fix it. Or will the old Veeam server revert to the old agent version upon rescanning the protectgroup (after re-adding the server(s)) ?

No, I don't expect agents 6.3 to work with v12.2 (disclaimer: I didn't tested myself). The backup server should always be updated first. In case you have to rollback, you can simply uninstall the agent (from the backup console before removing it from v12.3) and let the original backup server deploy the older agent again.

Best,
Fabian

[bstuiver]

Great

Thanks for your helpfull answers Fabian