Exchange 2010 DAG backups don't seem to obey max_jobs
I was wondering if anyone could shed any light on what is happening with my Exchange DAG backups. We have two mailbox servers, mbx-1 and mbx-2, in our DAG, which is called staffmbx. Each database is backed up under it's own policy so that I can run ad-hoc backups on a per database basis when necessary.
I was getting a lot of 196 errors and noticed that only one backup was running at a time. I increased the maximum jobs per client for the DAG (./bpclient -client staffmbx -add -max_jobs 2). That certainly allowed two concurrent jobs but it seems to override the max_jobs for each mailbox server such that both jobs can run on one mailbox server whilst the other sits idle; that not what I had intended.
Is there a way to keep the DAG maximum concurrent jobs at 2 whilst limiting it to 1 on each mailbox server whilst keeping each database backup in it's own policy.
Thanks for any help offered.