Comprehensive data protection for all workloads
Post Reply
Munavvar
Novice
Posts: 7
Liked: never
Joined: Jul 13, 2021 11:32 am
Full Name: Munavvar Patel
Contact:

Feature Request - Prioritize extents in a Scale-out repository

Post by Munavvar »

Dear Team,

In SOBR, right now there is no option to give priority to any one extent, Like first the backup should be fall into extent_A. If extent_A is full or offline than only backup shoulf fall into extent_B.

This is i guess very basic feature and most the backup solution are providing right now.

Therefore requesting Veeam team to enhance product with this feature.

Thank you.
Andreas Neufert
VP, Product Management
Posts: 6707
Liked: 1401 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: Feature Request - Prioritize extents in a Scale-out repository

Post by Andreas Neufert »

Thanks for sharing this. There are some ideas for one of the next versions to force the usage of the existing extends. You could use this for your requested situation.
Place the second extend in maintenance mode (or just add it later), then create backups on first extent and bring the second one online.
That way the backups would go in the first extent and only at space or downtime issues it would use this.

Second option, you can implement a failover cluster or use a redundant filer today.
We have lot´s of customers that are using this method. Usually capacity is shared here.

I wonder why you request this functionality. Why don´t you want to use the second storage as performance booster for the backup? In your scenatio it would just sit there doing nothing.
Munavvar
Novice
Posts: 7
Liked: never
Joined: Jul 13, 2021 11:32 am
Full Name: Munavvar Patel
Contact:

Re: Feature Request - Prioritize extents in a Scale-out repository

Post by Munavvar »

Dear Anreas

Thank you for the response & sorry for the delay in response.

''Place the second extend in maintenance mode (or just add it later), then create backups on first extent and bring the second one online.
That way the backups would go in the first extent and only at space or downtime issues it would use this.''

The above option i tried, but while next synthetic full run, backups are fallen into another repository only. Now this i cannot do manually every week, so better to have automatic feature i guess.

The reason behind i don't want to use second storage is because that repository performance is not good and we used it as only secondary option in case of primary full or primary failure.

Thank you.
Andreas Neufert
VP, Product Management
Posts: 6707
Liked: 1401 times
Joined: May 04, 2011 8:36 am
Full Name: Andreas Neufert
Location: Germany
Contact:

Re: Feature Request - Prioritize extents in a Scale-out repository

Post by Andreas Neufert »

Currently there is no way other then what I described.
Please check upcoming v11a or v12 beta, maybe this feature will be added there.
Munavvar
Novice
Posts: 7
Liked: never
Joined: Jul 13, 2021 11:32 am
Full Name: Munavvar Patel
Contact:

Re: Feature Request - Prioritize extents in a Scale-out repository

Post by Munavvar »

Dear Andreas

Thank you.
PetrM
Veeam Software
Posts: 3229
Liked: 520 times
Joined: Aug 28, 2013 8:23 am
Full Name: Petr Makarov
Location: Prague, Czech Republic
Contact:

Re: Feature Request - Prioritize extents in a Scale-out repository

Post by PetrM »

I'd also recommend to review this page on our help center to be aware of extent selection logic for backup file placement.

Thanks!
Post Reply

Who is online

Users browsing this forum: Google [Bot] and 232 guests