Comprehensive data protection for all workloads
Post Reply
christiankelly
Service Provider
Posts: 116
Liked: 7 times
Joined: May 06, 2012 6:22 pm
Full Name: Christian Kelly
Contact:

Balancing a scale-out file repository

Post by christiankelly » Aug 09, 2016 4:17 pm

I have a scale-out repository with 2 servers added. I want to add a third but I don’t anticipate adding many new jobs. But for IOPS and growth of current jobs I’d l want to spread data across all three. Is this possible?

Thanks,

Gostev
SVP, Product Management
Posts: 24612
Liked: 3458 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Balancing a scale-out file repository

Post by Gostev » Aug 09, 2016 4:29 pm

It will very quickly work out by itself, because the new extent will be given preference based on free disk space, while other extents will be quickly freeing up disk space according to your retention policy. Thus, all extents will quickly come to the same free space level, and thus will be used equally in terms of IOPS balancing.

christiankelly
Service Provider
Posts: 116
Liked: 7 times
Joined: May 06, 2012 6:22 pm
Full Name: Christian Kelly
Contact:

Re: Balancing a scale-out file repository

Post by christiankelly » Aug 09, 2016 4:44 pm

The use case I have is repositories with "data locality" and jobs with forever incremental 30 days. When would a current job every switch to a new extent?

Gostev
SVP, Product Management
Posts: 24612
Liked: 3458 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Balancing a scale-out file repository

Post by Gostev » Aug 09, 2016 6:39 pm

In this case never, actually (because you want data locality and there is no periodic fulls - so there is no opportunity for us to switch the extents).

dellock6
Veeam Software
Posts: 5703
Liked: 1606 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Balancing a scale-out file repository

Post by dellock6 » Aug 09, 2016 11:30 pm

One possibility is when you add new VMs, as the per vm chain of a new vm will be placed in the new extent
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2019
Veeam VMCE #1

christiankelly
Service Provider
Posts: 116
Liked: 7 times
Joined: May 06, 2012 6:22 pm
Full Name: Christian Kelly
Contact:

Re: Balancing a scale-out file repository

Post by christiankelly » Aug 09, 2016 11:54 pm

Is there any supported way to move some around manually and then rescan like we can with normal REPOs?

dellock6
Veeam Software
Posts: 5703
Liked: 1606 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Balancing a scale-out file repository

Post by dellock6 » Aug 10, 2016 7:31 am

Yes, you can manually move chains and let the periodic rescan task to synchronize the changes in the database.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2019
Veeam VMCE #1

christiankelly
Service Provider
Posts: 116
Liked: 7 times
Joined: May 06, 2012 6:22 pm
Full Name: Christian Kelly
Contact:

Re: Balancing a scale-out file repository

Post by christiankelly » Aug 10, 2016 4:38 pm

Thanks for the info. If I do an "Active Full" will it also pick a new extent?

Gostev
SVP, Product Management
Posts: 24612
Liked: 3458 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Balancing a scale-out file repository

Post by Gostev » Aug 10, 2016 4:41 pm

Certainly (assuming it has the most free space of all other extents).

ian0x0r
Veeam Vanguard
Posts: 221
Liked: 41 times
Joined: Nov 11, 2010 11:53 am
Full Name: Ian Sanderson
Location: UK
Contact:

Re: Balancing a scale-out file repository

Post by ian0x0r » Aug 15, 2016 6:45 am 1 person likes this post

Just to add to this, you can NOT move backup chains from a normal repo into one of the extents making up the SOBR without following the procedure below. The rescan operation will fail to find any new files. The procedure I received from support to make this work is as follows assuming that you have moved the backup chain already:

1. Remove extent from SOBR, it becomes simple repository
2. Rescan this repository: backup set is now under Backups - Disk (Imported) node
3. Re-add repository to SOBR, it becomes extent again
4. Backup set is still under Backups - Disk (Imported)
5. Map the job to backup set selecting Target repository - SOBR and then Map backup and click Finish
6. Backups disappear from Backups - Disk (Imported) and appear under Backups - Disk
7. Retry the job

I'm not sure if moving backups between extents that already make up the SOBR is different? Maybe one of the Veeam guys can answer that one.

Cheers,

Ian
https://www.snurf.co.uk

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

Re: Balancing a scale-out file repository

Post by foggy » Aug 15, 2016 3:43 pm

Ian, you can move backups between extents inside SOBR just fine. They will be recognized during rescan operation, as Luca has stated above.

Post Reply

Who is online

Users browsing this forum: No registered users and 24 guests