-
- Novice
- Posts: 3
- Liked: never
- Joined: Apr 05, 2024 5:37 am
- Full Name: Sebi Ebner
- Contact:
Feature Request Tags on Snapshots
We currently have a problem with the tags in Azure that we have exceeded the limit of the payload, so that if you have selected all subscriptions it can no longer load the tags. This is because the tags of snapshots are extremely long. it would make it a lot easier if the values of the tags were shorter, because I think we are certainly not the only company with this problem.
-
- Product Manager
- Posts: 5738
- Liked: 1208 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Feature Request Tags on Snapshots
Hi Sebi,
Are you talking about the Veeam added tags that contain metadata to ensure we can restore the VM with all required settings? And can you clarify what you mean by "it can no longer load the tags"? Are you talking about VB for Azure or somewhere in the Azure portal?
Are you talking about the Veeam added tags that contain metadata to ensure we can restore the VM with all required settings? And can you clarify what you mean by "it can no longer load the tags"? Are you talking about VB for Azure or somewhere in the Azure portal?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Novice
- Posts: 3
- Liked: never
- Joined: Apr 05, 2024 5:37 am
- Full Name: Sebi Ebner
- Contact:
Re: Feature Request Tags on Snapshots
Hello
Yes I mean those, specially those on the snapshots "veeam01, veaam02, ...). I am talking about the Tags view in the azure portal "https://portal.azure.com/#view/HubsExtension/TagsBlade" then you get this error:
All the selected subscriptions failed to return tags.
content: {"error":{"code":"BadRequest","message":"Please provide below info when asking for support: timestamp = 2024-04-08T05:39:49.7973775Z, correlationId = cdf97df5-b77f-4b84-bb26-c66d217e4a35.","details":[{"code":"ResponsePayloadTooLarge","message":"Response payload size is 23718059, and has exceeded the limit of 16777216. Please consider querying less data at a time and make paginated call if needed."}]}}
contentLength: 404
But also when you create new resources in the step to add tags it doesn't show the ones already used.
Yes I mean those, specially those on the snapshots "veeam01, veaam02, ...). I am talking about the Tags view in the azure portal "https://portal.azure.com/#view/HubsExtension/TagsBlade" then you get this error:
All the selected subscriptions failed to return tags.
content: {"error":{"code":"BadRequest","message":"Please provide below info when asking for support: timestamp = 2024-04-08T05:39:49.7973775Z, correlationId = cdf97df5-b77f-4b84-bb26-c66d217e4a35.","details":[{"code":"ResponsePayloadTooLarge","message":"Response payload size is 23718059, and has exceeded the limit of 16777216. Please consider querying less data at a time and make paginated call if needed."}]}}
contentLength: 404
But also when you create new resources in the step to add tags it doesn't show the ones already used.
-
- Product Manager
- Posts: 5738
- Liked: 1208 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Feature Request Tags on Snapshots
Hi,
This looks like an issue with the Azure portal especially since you also get this when creating new resources. Have you already contacted Microsoft for insight on this?
As mentioned, VB for Azure relies on those tags since it contains information to perform restores. We haven't seen any other customers yet face this issue related to tags and the Azure portal.
Do you have an idea on how many other tags are being added to the virtual machines besides the ones Veeam creates? And how many snapshots do you currently store?
This looks like an issue with the Azure portal especially since you also get this when creating new resources. Have you already contacted Microsoft for insight on this?
As mentioned, VB for Azure relies on those tags since it contains information to perform restores. We haven't seen any other customers yet face this issue related to tags and the Azure portal.
Do you have an idea on how many other tags are being added to the virtual machines besides the ones Veeam creates? And how many snapshots do you currently store?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Novice
- Posts: 3
- Liked: never
- Joined: Apr 05, 2024 5:37 am
- Full Name: Sebi Ebner
- Contact:
Re: Feature Request Tags on Snapshots
Hello
Yes we already did, but we are still waiting for response. I'am refering about the snapshots. We currently have 4473 Snapshots from Veeam. The other Tags on the Snapshots are very short like "Creator, Description, Creator" which are applied from the disk. So my request is that is may be possible to shorten those value, cause they have a length of 256 which is the limit. And the other thing is that we have Snapshots with 1 Tag from Veeam and other with x Tags, why does Veeam need more than 1 Tag.
Thanks for feedback.
Yes we already did, but we are still waiting for response. I'am refering about the snapshots. We currently have 4473 Snapshots from Veeam. The other Tags on the Snapshots are very short like "Creator, Description, Creator" which are applied from the disk. So my request is that is may be possible to shorten those value, cause they have a length of 256 which is the limit. And the other thing is that we have Snapshots with 1 Tag from Veeam and other with x Tags, why does Veeam need more than 1 Tag.
Thanks for feedback.
-
- Product Manager
- Posts: 5738
- Liked: 1208 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Feature Request Tags on Snapshots
As mentioned, those tags contain data to restore from them. These are already shortened to not impact having 10 or 20 Veeam snapshots but only a few hence why they use the 256 length which is supported by Microsoft Azure.
Have you considered from snapshot based backups to using Azure Blob to reduce the number of snapshots as this will also reduce the cost requirement to store data for a longer time?
Have you considered from snapshot based backups to using Azure Blob to reduce the number of snapshots as this will also reduce the cost requirement to store data for a longer time?
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
Who is online
Users browsing this forum: No registered users and 3 guests