On 01/12/2010 01:49, Dan Langille wrote:
> On 11/30/2010 11:09 AM, Matthew Seaman wrote:
>>
>> Hi,
>>
>> We have a setup with two storage director machines at different
>> locations. Most of the clients are in one hosting center, and use the
>> local SD, while several are scattered at various loca
On 11/30/2010 11:09 AM, Matthew Seaman wrote:
>
> Hi,
>
> We have a setup with two storage director machines at different
> locations. Most of the clients are in one hosting center, and use the
> local SD, while several are scattered at various locations around the
> net and use the other SD. Ther
> Sorry -- I didn't explain myself clearly enough. Concurrent jobs work
> fine when everything is OK. It's if there is some sort of exception
> that blocks jobs from executing on one of the SDs that we see the
> effect: all backups held up across both SDs.
I have never witnessed the behavior you
On 30/11/2010 16:22, John Drescher wrote:
> 2010/11/30 Matthew Seaman :
>>
>> Hi,
>>
>> We have a setup with two storage director machines at different
>> locations. Most of the clients are in one hosting center, and use the
>> local SD, while several are scattered at various locations around the
2010/11/30 Matthew Seaman :
>
> Hi,
>
> We have a setup with two storage director machines at different
> locations. Most of the clients are in one hosting center, and use the
> local SD, while several are scattered at various locations around the
> net and use the other SD. There's a single direc
Hi,
We have a setup with two storage director machines at different
locations. Most of the clients are in one hosting center, and use the
local SD, while several are scattered at various locations around the
net and use the other SD. There's a single director driving all this,
and one catalogue
