Hi All.
I've been doing some research on sizing recently using the best practices guide and Timothy Dewin's "Sizing the Beast" webinar. Both mention that you should size for 1 proxy slot (1 core/vCPU and 2GB RAM) for every 30 VMs to be backed up in an 8 hour window. This seems to be based on an average size of 100GB per VM.
If this is so, would it be fair to say that the guidelines are ultimately based on each slot being able to process about 3TB (30 x 100GB) of data in an 8 hour window?
Thanks,
Neil.
-
- Enthusiast
- Posts: 94
- Liked: 16 times
- Joined: Nov 25, 2010 4:26 pm
- Full Name: Neil Murphy
- Contact:
-
- VP, Product Management
- Posts: 6749
- Liked: 1408 times
- Joined: May 04, 2011 8:36 am
- Full Name: Andreas Neufert
- Location: Germany
- Contact:
Re: Number of proxy tasks / slots
There are many ways to calculate proxy and repository ressources... by throughput, time and others. The 30-40VMs per Core and 8h backup window came from observation of existing customers and it worked way more reliable then any other method. Storage Systems are so different when it comes to random read and write.
The calculation is done that way that it is unlike that the proxy or repository role is the bottleneck at incremental forever runs.
The calculation is done that way that it is unlike that the proxy or repository role is the bottleneck at incremental forever runs.
-
- Enthusiast
- Posts: 94
- Liked: 16 times
- Joined: Nov 25, 2010 4:26 pm
- Full Name: Neil Murphy
- Contact:
Re: Number of proxy tasks / slots
Thanks Andreas.
Who is online
Users browsing this forum: No registered users and 58 guests