-
- Enthusiast
- Posts: 78
- Liked: 9 times
- Joined: Mar 04, 2013 2:41 pm
- Contact:
After upgrade to 12.1 outdated data mover Ubuntu
Hi,
we upgraded from VBR 12.0 to 12.1. Backup still works, but with our Ubuntu 22.04 we get a warning that the data mover is outdated after each backup.
Agents are newest ones.
Regards
Jens
we upgraded from VBR 12.0 to 12.1. Backup still works, but with our Ubuntu 22.04 we get a warning that the data mover is outdated after each backup.
Agents are newest ones.
Regards
Jens
-
- Product Manager
- Posts: 10278
- Liked: 2746 times
- Joined: May 13, 2017 4:51 pm
- Full Name: Fabian K.
- Location: Switzerland
- Contact:
Re: After upgrade to 12.1 outdated data mover Ubuntu
Hello Jens
Please make sure that you have updated all components of your VBR server:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
The agents are already updated as you have confirmed:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
If everything is up to date and you can still see this issue, a support case will be needed. Please open a case with our customer support team and provide them with a current log package of your VBR server and Agent.
Don't forget to share the case number with us.
Best,
Fabian
Please make sure that you have updated all components of your VBR server:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
The agents are already updated as you have confirmed:
https://helpcenter.veeam.com/docs/backu ... ml?ver=120
If everything is up to date and you can still see this issue, a support case will be needed. Please open a case with our customer support team and provide them with a current log package of your VBR server and Agent.
Don't forget to share the case number with us.
Best,
Fabian
Product Management Analyst @ Veeam Software
-
- Enthusiast
- Posts: 78
- Liked: 9 times
- Joined: Mar 04, 2013 2:41 pm
- Contact:
Re: After upgrade to 12.1 outdated data mover Ubuntu
Hi Fabian,
thanks, the manual upgrade fails with
"Failed to upgrade host components. Error: 'An established connection was aborted by the server.'"
I updated manually with
No luck, seems I have to open a ticket?
Regards,
Jens
thanks, the manual upgrade fails with
"Failed to upgrade host components. Error: 'An established connection was aborted by the server.'"
I updated manually with
Code: Select all
apt-get update
apt-get install veeam
Regards,
Jens
-
- Veeam Software
- Posts: 569
- Liked: 113 times
- Joined: Jul 03, 2023 12:44 pm
- Full Name: Rovshan Pashayev
- Location: Czechia
- Contact:
Re: After upgrade to 12.1 outdated data mover Ubuntu
Hello Jens,
Make sure that you have installed veeam-release package first, you can download it from this link.
And can reach Veeam's public repository.
Rovshan.
Make sure that you have installed veeam-release package first, you can download it from this link.
And can reach Veeam's public repository.
Rovshan.
Rovshan Pashayev
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
-
- Enthusiast
- Posts: 78
- Liked: 9 times
- Joined: Mar 04, 2013 2:41 pm
- Contact:
Re: After upgrade to 12.1 outdated data mover Ubuntu
Hi Rovshan,
thanks, but also no luck with this.
Regards
Jens
thanks, but also no luck with this.
Regards
Jens
-
- Veeam Software
- Posts: 569
- Liked: 113 times
- Joined: Jul 03, 2023 12:44 pm
- Full Name: Rovshan Pashayev
- Location: Czechia
- Contact:
Re: After upgrade to 12.1 outdated data mover Ubuntu
Hello,
Try following command, in order to see if you get list of versions:
And following command to upgrade veeam package:
You need also upgrade veeamsnap or blksnap, depending which module you were using.
If you still face problem, please open Support Case.
Rovshan
Try following command, in order to see if you get list of versions:
Code: Select all
apt list -a veeam
Code: Select all
apt upgrade veeam
If you still face problem, please open Support Case.
Rovshan
Rovshan Pashayev
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
Analyst
Veeam Agent for Linux, Mac, AIX & Solaris
-
- Product Manager
- Posts: 6576
- Liked: 772 times
- Joined: May 19, 2015 1:46 pm
- Contact:
Re: After upgrade to 12.1 outdated data mover Ubuntu
For further readers:
If your VBR manages agent machines (be it Windows or Linux), it is presumed that VBR will also handle all upgrades.
Although in some cases manually upgrading the agent on the target machine can help, that's not how the product is intended to work.
If you see that your VBR server fails to update its managed target agents, it is strongly recommended to file a support case regardless of whether manually updating agents using veeam repository has fixed things for you.
If your VBR manages agent machines (be it Windows or Linux), it is presumed that VBR will also handle all upgrades.
Although in some cases manually upgrading the agent on the target machine can help, that's not how the product is intended to work.
If you see that your VBR server fails to update its managed target agents, it is strongly recommended to file a support case regardless of whether manually updating agents using veeam repository has fixed things for you.
-
- Enthusiast
- Posts: 78
- Liked: 9 times
- Joined: Mar 04, 2013 2:41 pm
- Contact:
Re: After upgrade to 12.1 outdated data mover Ubuntu
Hi,
thanks for all suggestions!
I tried everything that's been recommended in this thread, that was last friday. No luck, I wanted to open a support ticket last monday. On monday, I saw that suddenly it worked. No idea, what happened here.
Seems to be, that there could be other caveats. We got a standalone SQL server (Windows Server 2019), Veeam told me that the agent was upgraded and a reboot is needed. I made a reboot, Veeam still insists that it needs another reboot. That was last weekend, then, out of nothing, the 'problem' wasn't anymore. I didn't reboot the server a second time, nethertheless the message was gone.
At upgrade, I told Veeam to automatically upgrade the other servers. Till now, no further problems.
Regards
thanks for all suggestions!
I tried everything that's been recommended in this thread, that was last friday. No luck, I wanted to open a support ticket last monday. On monday, I saw that suddenly it worked. No idea, what happened here.
Seems to be, that there could be other caveats. We got a standalone SQL server (Windows Server 2019), Veeam told me that the agent was upgraded and a reboot is needed. I made a reboot, Veeam still insists that it needs another reboot. That was last weekend, then, out of nothing, the 'problem' wasn't anymore. I didn't reboot the server a second time, nethertheless the message was gone.
At upgrade, I told Veeam to automatically upgrade the other servers. Till now, no further problems.
Regards
Who is online
Users browsing this forum: No registered users and 11 guests