best practice for big Windows Volumes

Discussions specific to VMware vSphere hypervisor

best practice for big Windows Volumes

Veeam Logoby readie » Thu Apr 23, 2015 2:46 pm

Hi, this is partly a Veeam and partly a VMware questions.
I am about to build a new Windows 2012 fileserver with a 4TB Volume. In the past we have gradually increased sizes (up to about 3TB) by adding 512GB VHDs, and using Windows Disk Manager to create the big volume. This works nicely with Veeam backup as it can process several of the VHDs in parallel.
If I create only one, or two 2TB VHDs, Veeam will be less efficient (or perhaps I will have to think about getting this backup job for a 4TB VHD machine working at the same time as other smaller jobs for all our other servers?).
At the moment I try to schedule my 5 backup jobs so that they don't overlap too much - or am I being stupid and not leaving Veeam to do this as efficiently as possible? Perhaps it would do it better than I can?
Any advice welcome, before I plunge in.
Bob Eadie
Computer Manager at Bedford School, UK (since 1999).
Veeam user since 2009.
Posts: 158
Liked: 30 times
Joined: Sun Dec 05, 2010 9:29 am
Full Name: Bob Eadie

Re: best practice for big Windows Volumes

Veeam Logoby foggy » Thu Apr 23, 2015 2:58 pm

Bob, job overlapping is ok as long as sufficient resources are available. Veeam B&R automatic resource scheduling ensures your resources are utilized in most effective manner, optimizing backup windows and eliminating time periods when no jobs are running. I believe you'd better rely on it (probably limiting the number of concurrent tasks per proxy and repository to avoid possible constraints) and see whether you're meeting your backup window.
Veeam Software
Posts: 16306
Liked: 1302 times
Joined: Mon Jul 11, 2011 10:22 am
Full Name: Alexander Fogelson

Return to VMware vSphere

Who is online

Users browsing this forum: Bing [Bot] and 17 guests