-
- Novice
- Posts: 8
- Liked: never
- Joined: May 09, 2023 2:01 am
- Full Name: Felix
- Contact:
Feature Request: Bring back the Missing Column on the Backup Size of Restorepoint in VBAWS version 6
In VBAWS version 5, there is a column to show the backup size of each individual restorepoint.
In version 6, this column is no longer available.
We opened Veeam case (#06300169) and were informed by tech support that the VBAWS v6 was designed with purpose to let go of that column showing the size of every restore point under protected data.
They mentioned that we could raise feature request but this depended on how many clients ask for the feature to be back where the prod team would consider working it out.
The reason was due to the complexity and issues getting the accurate sizing when object storage was used making it difficult to calculate the correct sizes so to get better performance and improve the storage handling, this feature which showed the sizing of the restore point was removed.
Can we raise more attention from Veeam R&D to prioritize it based on the value/gain, not based on the number clients who'd like to actively ask?
This is because whenever we'd like to ask/urge the client to upgrade, the client would usually raise concern if certain features that were available in earlier version, were missing in the newer version.
The size of restorepoint is important to understand the storage consumption on the full vs incremental backup so that users can decide/plan whether they need to retain or reduce the retention policies when the cost of s3 storage is increasing on their side.
If there is impact on performance and storage handling, can it be put as option/setting to be enabled on certain protected instances only?
(e.g. provide a checkbox and button to trigger VBA to start scanning all restorepoints on certain particular instance to calculate the size when user'd like to zoom in certain storage consumption there?)
Thank you.
In version 6, this column is no longer available.
We opened Veeam case (#06300169) and were informed by tech support that the VBAWS v6 was designed with purpose to let go of that column showing the size of every restore point under protected data.
They mentioned that we could raise feature request but this depended on how many clients ask for the feature to be back where the prod team would consider working it out.
The reason was due to the complexity and issues getting the accurate sizing when object storage was used making it difficult to calculate the correct sizes so to get better performance and improve the storage handling, this feature which showed the sizing of the restore point was removed.
Can we raise more attention from Veeam R&D to prioritize it based on the value/gain, not based on the number clients who'd like to actively ask?
This is because whenever we'd like to ask/urge the client to upgrade, the client would usually raise concern if certain features that were available in earlier version, were missing in the newer version.
The size of restorepoint is important to understand the storage consumption on the full vs incremental backup so that users can decide/plan whether they need to retain or reduce the retention policies when the cost of s3 storage is increasing on their side.
If there is impact on performance and storage handling, can it be put as option/setting to be enabled on certain protected instances only?
(e.g. provide a checkbox and button to trigger VBA to start scanning all restorepoints on certain particular instance to calculate the size when user'd like to zoom in certain storage consumption there?)
Thank you.
-
- Product Manager
- Posts: 5838
- Liked: 1220 times
- Joined: Jul 15, 2013 11:09 am
- Full Name: Niels Engelen
- Contact:
Re: Feature Request: Bring back the Missing Column on the Backup Size of Restorepoint in VBAWS version 6
Hi Felix,
Sounds to me that you offer the solution as a service. Are you a service provider or am I wrong here?
We will look into enhancing this for the future but I cannot provide an ETA for when we may be able to return this.
Sounds to me that you offer the solution as a service. Are you a service provider or am I wrong here?
We will look into enhancing this for the future but I cannot provide an ETA for when we may be able to return this.
Personal blog: https://foonet.be
GitHub: https://github.com/nielsengelen
GitHub: https://github.com/nielsengelen
-
- Novice
- Posts: 8
- Liked: never
- Joined: May 09, 2023 2:01 am
- Full Name: Felix
- Contact:
Re: Feature Request: Bring back the Missing Column on the Backup Size of Restorepoint in VBAWS version 6
Hi Nielsen,
Thank you. Yes, my company is providing infra and managed services for cloud and on-prem
https://www1.asiapac.com.sg/solutions/i ... singapore/
Regards,
Felix
Thank you. Yes, my company is providing infra and managed services for cloud and on-prem
https://www1.asiapac.com.sg/solutions/i ... singapore/
Regards,
Felix
-
- VP, Product Management
- Posts: 27463
- Liked: 2825 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Feature Request: Bring back the Missing Column on the Backup Size of Restorepoint in VBAWS version 6
I guess you can achieve the same goal by just monitoring the growth of the entire backup chain, right? If the trend goes high and too quickly, then probably the corresponding storage limits should be increased as well.felixasiapac wrote:The size of restorepoint is important to understand the storage consumption on the full vs incremental backup so that users can decide/plan whether they need to retain or reduce the retention policies when the cost of s3 storage is increasing on their side.
Unfortunately, I wouldn't expect individual restore points size to come back, as technically, it returns wrong data in GFS (where blocks are reused).
-
- Novice
- Posts: 8
- Liked: never
- Joined: May 09, 2023 2:01 am
- Full Name: Felix
- Contact:
Re: Feature Request: Bring back the Missing Column on the Backup Size of Restorepoint in VBAWS version 6
Can you please advise how to do it? If there is no individual restorepoint size, how do we know the growth of the entire backup chain?
-
- Novice
- Posts: 8
- Liked: never
- Joined: May 09, 2023 2:01 am
- Full Name: Felix
- Contact:
Re: Feature Request: Bring back the Missing Column on the Backup Size of Restorepoint in VBAWS version 6
Also, when you mentioned "it returns wrong data in GFS (where blocks are reused)", how did you calculate it previously in VBAWS version 5 and earlier?
Who is online
Users browsing this forum: No registered users and 1 guest