Comprehensive data protection for all workloads
Post Reply
Tim783
Influencer
Posts: 13
Liked: never
Joined: Jul 20, 2012 2:05 pm
Contact:

Feature Request Scale out Repository and GFS

Post by Tim783 » Apr 07, 2017 3:02 pm

Hi,

At the moment when using the data locality Scale out policy along with Backup Copy Jobs with Full GFS restore points.
There is no way for the Backup Copy Job to start using a different extent when the extent is becoming full or to just balance them out a bit without first running a manual Active full.

It would be good if when creating the GFS files Veeam could then choose a new extent.

As right now 1 of my extents is getting low on space where as the others are fine. But to fix I need to run a active full which will mean copying all the data to our DR site again.

Thanks

Shestakov
Veeam Software
Posts: 6974
Liked: 714 times
Joined: May 21, 2014 11:03 am
Full Name: Nikita Shestakov
Location: Prague
Contact:

Re: Feature Request Scale out Repository and GFS

Post by Shestakov » Apr 09, 2017 7:40 pm

Hi Tim,
your request does make sense and will be taken into account. Thank you!

Tim783
Influencer
Posts: 13
Liked: never
Joined: Jul 20, 2012 2:05 pm
Contact:

Re: Feature Request Scale out Repository and GFS

Post by Tim783 » Apr 10, 2017 4:17 pm

Thanks Shestakov :)

foggy
Veeam Software
Posts: 18276
Liked: 1564 times
Joined: Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson
Contact:

Re: Feature Request Scale out Repository and GFS

Post by foggy » Apr 10, 2017 4:56 pm

Do you mean the ability to define such extent in advance, when creating the job? As currently backup copy job should start using another extent automatically, in case the current one runs out of space.

Post Reply

Who is online

Users browsing this forum: Bing [Bot], dabrigo, david.domask, oleg.feoktistov, perrylee and 55 guests