Is there a guide for determining how many servers you should be running for respository servers? Right now I have 2 physical servers for proxy and 1 of them is the repository server. It currently has 2 large volumes provisioned on an IBM V3700 fibre subsystem. I am currently backing up around 200 VM's in my 10-hr backup window nightly. What I'm looking for is any documentation/FAQ/guide on how to determine the repository layout. How many servers? How many volumes/repositories per server? Concurrent tasks per repository or throughput? I'm seeing during the backup window where jobs are on hold waiting for resources. Would it help to put some repositories on the other proxy to split the load? I could then theoretically have twice the number of jobs running without waiting for resources. We were initially recommended to use only 1 for repository and the other would be in case the server went down and we needed to move the repsitories to the other server to continue processing.
Just looking for a little guidance.
TIA,
Bill Boyer
-
bjdboyer
- Service Provider
- Posts: 60
- Liked: 3 times
- Joined: Nov 16, 2015 5:52 pm
- Full Name: Bill Boyer
- Contact:
-
DaveWatkins
- Veteran
- Posts: 370
- Liked: 97 times
- Joined: Dec 13, 2015 11:33 pm
- Contact:
Re: Repository Configuration
"Waiting for resources" is a user configurable options. It's based on how many Concurrent Tasks you have set on the repository and on the proxies. If you think your storage can sustain more simultaneous jobs then just increase the number on the repository. At some point you're going to start going backwards as the increased latency of all the threads trying to write at once will offset any extra throughput, but against a fibre channel backed array, I would imagine you should be able to go pretty high before that becomes an issue
I tend to prefer simplicity where possible so unless the server hosting the repo runs out of power I think you're better off with just a single repo.
The other place that Waiting for resources comes into play is how many concurrent tasks you have the proxies set to do, given they are both physical boxes (and I assume both connected to the primary SAN with FC?) you probably have them set to be able to do more tasks that the storage so starting with bumping up the storage threads will likely help
I tend to prefer simplicity where possible so unless the server hosting the repo runs out of power I think you're better off with just a single repo.
The other place that Waiting for resources comes into play is how many concurrent tasks you have the proxies set to do, given they are both physical boxes (and I assume both connected to the primary SAN with FC?) you probably have them set to be able to do more tasks that the storage so starting with bumping up the storage threads will likely help
Who is online
Users browsing this forum: Bing [Bot] and 81 guests