-
- Influencer
- Posts: 19
- Liked: never
- Joined: Apr 12, 2023 7:26 pm
- Contact:
Veeam Update Warning
I have Veeam for AWS backup 7.0.0.615 available to update but I have this warning:
This update is available for backup appliances that are managed by Veeam Backup & Replication only. Open the backup console UI and initiate the upgrade procedure from there. If you are not running Veeam Backup & Replication, download it from Veeam website and integrate this appliance with a backup server.
For more information, see the User Guide.
So I looked in the User's Guide and from what I can understand, I need another Veeam Backup & Replication server to upgrade my Veeam for AWS? Is this what I have read? If so why can't the update just run in place on the Linux server I already have? Please correct me if I am wrong. Thank you.
This update is available for backup appliances that are managed by Veeam Backup & Replication only. Open the backup console UI and initiate the upgrade procedure from there. If you are not running Veeam Backup & Replication, download it from Veeam website and integrate this appliance with a backup server.
For more information, see the User Guide.
So I looked in the User's Guide and from what I can understand, I need another Veeam Backup & Replication server to upgrade my Veeam for AWS? Is this what I have read? If so why can't the update just run in place on the Linux server I already have? Please correct me if I am wrong. Thank you.
-
- Product Manager
- Posts: 5838
- Liked: 1220 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Veeam Update Warning
Hi,
As VB for AWS is part of the Veeam Platform, VBR is required to benefit from the latest version and features. This will also allow you to benefit from VBR specific features such as backup copies. You can connect to your existing VBR installation, there is no need for a dedicated VBR instance.
As VB for AWS is part of the Veeam Platform, VBR is required to benefit from the latest version and features. This will also allow you to benefit from VBR specific features such as backup copies. You can connect to your existing VBR installation, there is no need for a dedicated VBR instance.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Influencer
- Posts: 19
- Liked: 2 times
- Joined: Nov 30, 2011 8:06 pm
- Contact:
Re: Veeam Update Warning
Hello Niels Engelen,
I'm confused by your above comment. Are you saying that the latest version of Veeam Backup for AWS is no longer available as a standalone product, and customers must now use Veeam Backup & Replication to use the latest VBAWS version?
-Taylorbox
I'm confused by your above comment. Are you saying that the latest version of Veeam Backup for AWS is no longer available as a standalone product, and customers must now use Veeam Backup & Replication to use the latest VBAWS version?
-Taylorbox
-
- Product Manager
- Posts: 5838
- Liked: 1220 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Veeam Update Warning
To benefit from the latest features such as DynamoDB support, the integration will be required. Other existing features are not affected by this change.
As we move forward with the platform, VBR will be the central management tool for the appliances (not just AWS) and it will allow us to benefit from additional features that are now only available in VBR.
As we move forward with the platform, VBR will be the central management tool for the appliances (not just AWS) and it will allow us to benefit from additional features that are now only available in VBR.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Influencer
- Posts: 19
- Liked: 2 times
- Joined: Nov 30, 2011 8:06 pm
- Contact:
Re: Veeam Update Warning
Niels,
Okay, interesting. So, I take this to mean that for customers like myself that use Veeam Backup for AWS only, not VBR, VBAWS standalone is now a deprecated product.
Is there any official, public announcement from Veeam on this matter?
-Taylorbox
Okay, interesting. So, I take this to mean that for customers like myself that use Veeam Backup for AWS only, not VBR, VBAWS standalone is now a deprecated product.
Is there any official, public announcement from Veeam on this matter?
-Taylorbox
-
- Product Manager
- Posts: 5838
- Liked: 1220 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Veeam Update Warning
It is actually not being deprecated, just becoming part of our data platform. The standalone version is still available and supported.
We are actively developing the next version as we speak covering requests from our users. However, to cover some of these requests, it was decided to make this change and over time this “split” will also fade out and the AWS data protection part will shift as part of VBR.
We are actively developing the next version as we speak covering requests from our users. However, to cover some of these requests, it was decided to make this change and over time this “split” will also fade out and the AWS data protection part will shift as part of VBR.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Influencer
- Posts: 19
- Liked: 2 times
- Joined: Nov 30, 2011 8:06 pm
- Contact:
Re: Veeam Update Warning
Niels,
Okay. Just to clarify please what you mean by "the whole AWS data protection split will shift as part of VBR"...
Does this mean that VBAWS will eventually be discontinued as a standalone product, or will VBAWS continue as a standalone product (indefinitely)?
-Taylorbox
Okay. Just to clarify please what you mean by "the whole AWS data protection split will shift as part of VBR"...
Does this mean that VBAWS will eventually be discontinued as a standalone product, or will VBAWS continue as a standalone product (indefinitely)?
-Taylorbox
-
- Product Manager
- Posts: 5838
- Liked: 1220 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Veeam Update Warning
The standalone product (as it is now) will remain the same, but to get new features and upgrades you would need to integrate it with Veeam B&R.
For now, you will be required to deploy a VBR to upgrade to v7 however, v6 is still supported and you are free to continue using this version if it fulfills your requirements in terms of protection. The built-in updater will allow you to install security updates.
For now, you will be required to deploy a VBR to upgrade to v7 however, v6 is still supported and you are free to continue using this version if it fulfills your requirements in terms of protection. The built-in updater will allow you to install security updates.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Influencer
- Posts: 19
- Liked: 2 times
- Joined: Nov 30, 2011 8:06 pm
- Contact:
Re: Veeam Update Warning
Is VBAWS v7 supported on the Veeam B&R Community Edition?
-Taylorbox
-Taylorbox
-
- VP, Product Management
- Posts: 27463
- Liked: 2825 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam Update Warning
Yes, Veeam B&R CE (latest release - 12.1) supports managing cloud backup appliances, but the license is limited to 10 instances.
-
- Influencer
- Posts: 19
- Liked: never
- Joined: Apr 12, 2023 7:26 pm
- Contact:
Re: Veeam Update Warning
So from readying this thread, I was correct that Veeam B&R is needed moving forward for upgrades and SOME features. Ok. The Veeam B&R CE supports up to 10 instances, I have only one Veeam For AWS EC2 machine, so I could run a Veeam B&R CE and keep it free and use it to keep updating major releases of my Veeam For AWS instance correct? Thank you.
-
- VP, Product Management
- Posts: 27463
- Liked: 2825 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam Update Warning
Yes, Veeam B&R is required to use new features/back up new workloads. Can you please clarify how many workloads/instances you're protecting and what the main driver is for you to do the upgrade?
-
- Influencer
- Posts: 19
- Liked: never
- Joined: Apr 12, 2023 7:26 pm
- Contact:
Re: Veeam Update Warning
I have 11 EC2 instnaces that Veeam for AWS is backing up now. Why upgrade? Well I saw it come up and figured it would be a good time to upgrade. I don't want to sit on an old version too long. How long with version 6.x be supported? Thanks.
-
- VP, Product Management
- Posts: 27463
- Liked: 2825 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam Update Warning
I see; please be aware that once you switch to the Community Edition, 1 EC2 workload will have to be excluded, as CE supports 10 instances/workloads maximum.sandmanfvr wrote:I have 11 EC2 instances that Veeam for AWS is backing up now.
You can find this information over here > https://www.veeam.com/product-lifecycle.htmlsandmanfvr wrote:Why upgrade? Well I saw it come up and figured it would be a good time to upgrade. I don't want to sit on an old version too long. How long with version 6.x be supported? Thanks.
Thanks!
-
- Lurker
- Posts: 2
- Liked: never
- Joined: Nov 15, 2023 9:39 pm
- Full Name: Sean Sliwinski
- Contact:
Re: Veeam Update Warning
So if VBR is not something already deployed, to go to 7 I need VBR, which I will now have to license since I use it for more than 10 instances, just to get 7....
I need none of the other features, that only are in VBR and going this route will do nothing but increase my TCO.
Sean
I need none of the other features, that only are in VBR and going this route will do nothing but increase my TCO.
Sean
-
- VP, Product Management
- Posts: 27463
- Liked: 2825 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam Update Warning
If you're using the VUL key to license VB for AWS, then you can install the same key to VBR and go from there. If you need new workload support, then yes, VBR integration will be required.
If new workload support is not something you're looking for, then you can continue using the standalone version; no need to migrate to VBR. Down the road, we will think about how to optimize TCO by offering a tighter integration between VBs (AWS, Azure and Google) and VBR.
If new workload support is not something you're looking for, then you can continue using the standalone version; no need to migrate to VBR. Down the road, we will think about how to optimize TCO by offering a tighter integration between VBs (AWS, Azure and Google) and VBR.
-
- Novice
- Posts: 3
- Liked: never
- Joined: Jun 01, 2021 10:18 am
- Contact:
Re: Veeam Update Warning
Hello,
We are currently running Veeam for AWS v7 standalone. We are considering upgrading to v8, but honestly, we don't need the new features. Setting up Veeam Backup & Replication (VB&R) in AWS just for Veeam for AWS v8 doesn't make sense for us.
What is the recommendation in this case? Should we just stay on version 7?
Additionally, there is no information on how long Veeam for AWS v7 will be supported, as it is now part of the VB&R lifecycle matrix. Veeam Product Lifecycle
We are currently running Veeam for AWS v7 standalone. We are considering upgrading to v8, but honestly, we don't need the new features. Setting up Veeam Backup & Replication (VB&R) in AWS just for Veeam for AWS v8 doesn't make sense for us.
What is the recommendation in this case? Should we just stay on version 7?
Additionally, there is no information on how long Veeam for AWS v7 will be supported, as it is now part of the VB&R lifecycle matrix. Veeam Product Lifecycle
-
- VP, Product Management
- Posts: 27463
- Liked: 2825 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Veeam Update Warning
Hello,
Yes, the recommendation would be to stay on the previous version if you don't want to upgrade. Usually, the components (VB for AWS is now a component of Veeam B&R) are supported based on N-1 release logic. So, in your case, the v7 will be out of support when v9 comes out.
Hope it helps!
Yes, the recommendation would be to stay on the previous version if you don't want to upgrade. Usually, the components (VB for AWS is now a component of Veeam B&R) are supported based on N-1 release logic. So, in your case, the v7 will be out of support when v9 comes out.
Hope it helps!
Who is online
Users browsing this forum: No registered users and 3 guests