9.5/ReFS/Server 2016 Memory Consumption

Availability for the Always-On Enterprise

Re: 9.5/ReFS/Server 2016 Memory Consumption

Veeam Logoby dellock6 » Mon Feb 06, 2017 8:31 pm

rgarvelink wrote:As stated in this thread, 4Gb of memory per core is the recommendation wouldn't OP need 64 Gb just for the Veeam operations assuming he's at 16 threads and is hitting the recommendation of 1 core for every thread? We know that ReFS prioritizes data availability over everything else and it appears to do so via memory consumption. We might just need to take that into consideration when sizing repositories.

I just wanted to highlight this part, as you are spot on and some people often overlook this part. 4GB per job (sorry my bad as I wrote core following the reply, thanks Anton) is the requested sizing for Veeam repository services, not the entire system. If you have additional services, like the ReFS components, you need to add these additional requirements into the sum of the needed memory. For 16 cores, thus handling usually 16 concurrent jobs, you need at least 64GB for just Veeam, plus the OS and its services.

Thanks for remiding this!

Luca
Luca Dell'Oca
EMEA Cloud Architect @ Veeam Software

@dellock6
http://www.virtualtothecore.com
vExpert 2011-2012-2013-2014-2015-2016
Veeam VMCE #1
dellock6
Veeam Software
 
Posts: 4787
Liked: 1247 times
Joined: Sun Jul 26, 2009 3:39 pm
Location: Varese, Italy
Full Name: Luca Dell'Oca

Re: 9.5/ReFS/Server 2016 Memory Consumption

Veeam Logoby Gostev » Mon Feb 06, 2017 8:57 pm

Guys, you probably meant 4GB per concurrent job (not per core) for the repository. One core = one task (if you follow our recommendation), however a single job usually uses many tasks.
Gostev
VP, Product Management
 
Posts: 20960
Liked: 2239 times
Joined: Sun Jan 01, 2006 1:01 am
Full Name: Anton Gostev

Re: 9.5/ReFS/Server 2016 Memory Consumption

Veeam Logoby suprnova » Wed Feb 08, 2017 2:55 pm

I added a new 64k repository and we had this issue again. The VM was reset and appears to be responsive, when before it would freeze after 30 seconds.

Here's the error message from the job that was running:

Synthetic full backup creation failed Error: Agent: Failed to process method {Transform.CompileFIB}: A file system block being referenced has already reached the maximum reference count and can't be referenced any further. Failed to duplicate extent
suprnova
Service Provider
 
Posts: 8
Liked: never
Joined: Fri Apr 08, 2016 5:15 pm

Re: 9.5/ReFS/Server 2016 Memory Consumption

Veeam Logoby Gostev » Thu Feb 09, 2017 3:00 pm

The error is quite strange as it would require having around 8000 of backup files in the chain to trigger. Perhaps it happens due to system instability, rather than running into the actual BlockClone API limitation. Please let me know the support case ID for this issue, as our devs would like to collect more information from debug logs. Thanks!
Gostev
VP, Product Management
 
Posts: 20960
Liked: 2239 times
Joined: Sun Jan 01, 2006 1:01 am
Full Name: Anton Gostev

Re: 9.5/ReFS/Server 2016 Memory Consumption

Veeam Logoby matteo.tosino » Tue Mar 21, 2017 10:09 am

hi, i have the same error (the maximum reference, from the last reply of suprnova) while Copy job merge, after 2 months of backup chain (7 Days, 4 Weeks, 3 Months, of 5 vms in one backup job).
This is the second time: the first time i open a case but with no solution
The support try to:
1. remove configuration of the copy job, and import again creaeting a new backup repository in a new location, impossible in my case (i have only one volume; i have try within the same volume, the error remain)
2. a volume defrag, but the defrag activity hung after few minutes with no disk or CPU activity).
3. refer to windows error code 0xC000048C STATUS_BLOCK_TOO_MANY_REFERENCES, but there is no documentation
I have closed the ticket because i read (don't remember where, sorry) to use ReFS with Storage Space as backup repository for Veeam. I try it for some days, but it's too slow respect of an hardware (hp smart array) management of my backup storage (JBOD).

Now i have again the same problem, what do you suggest?
I'm sure is a ReFS related problem, because it's born with this change in my infrastructure. Before to come back to NTFS, do you know some trick to solve this problem?
matteo.tosino
Lurker
 
Posts: 1
Liked: never
Joined: Tue Mar 21, 2017 9:52 am
Full Name: Matteo Tosino

Re: 9.5/ReFS/Server 2016 Memory Consumption

Veeam Logoby kubimike » Tue Mar 21, 2017 2:14 pm

@matteo.tosino can I chime in and ask if you've tried doing an active-full on the job to see if it goes away ?
kubimike
Enthusiast
 
Posts: 93
Liked: 14 times
Joined: Fri Feb 03, 2017 2:34 pm
Full Name: MikeO

Previous

Return to Veeam Backup & Replication



Who is online

Users browsing this forum: Bing [Bot], Majestic-12 [Bot], Yahoo [Bot] and 8 guests