Feature Request Scale out Repository and GFS

Availability for the Always-On Enterprise

Feature Request Scale out Repository and GFS

Veeam Logoby Tim783 » Fri 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
Tim783
Influencer
 
Posts: 11
Liked: never
Joined: Fri Jul 20, 2012 2:05 pm

Re: Feature Request Scale out Repository and GFS

Veeam Logoby Shestakov » Sun Apr 09, 2017 7:40 pm

Hi Tim,
your request does make sense and will be taken into account. Thank you!
Shestakov
Veeam Software
 
Posts: 5123
Liked: 430 times
Joined: Wed May 21, 2014 11:03 am
Location: Saint Petersburg
Full Name: Nikita Shestakov

Re: Feature Request Scale out Repository and GFS

Veeam Logoby Tim783 » Mon Apr 10, 2017 4:17 pm

Thanks Shestakov :)
Tim783
Influencer
 
Posts: 11
Liked: never
Joined: Fri Jul 20, 2012 2:05 pm

Re: Feature Request Scale out Repository and GFS

Veeam Logoby foggy » Mon 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.
foggy
Veeam Software
 
Posts: 15266
Liked: 1131 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson


Return to Veeam Backup & Replication



Who is online

Users browsing this forum: No registered users and 9 guests