{kb-symptom}
I have two policies per Agent. One Policy is used to backup 'system' volumes, and the other one is used to backup 'data' volumes. If the Server tries to execute both policies at the same time, instead of queuing the second policy, it displays an error stating:
{code}
Request was rejected by the agent. It is busy with another operation.
{code}
{kb-cause}
CDP 3.0 does not support running more than one backup at a time. There is an embedded queue mechanism that is activated when two policies attempt to save Recovery Points to the same Disk Safe (called the "Disk Safe Write Lock"). The problem here is that the Agent has two different policies with two different Disk Safes, and thus the lock is not triggered.
{kb-resolution}
You need to spread out your backup operations. Create a separate Policy for each Disk Safe.
_Or:_
Try scheduling the Policies so they do not run simultaneously or overlap.
{kb-related-articles}
I have two policies per Agent. One Policy is used to backup 'system' volumes, and the other one is used to backup 'data' volumes. If the Server tries to execute both policies at the same time, instead of queuing the second policy, it displays an error stating:
{code}
Request was rejected by the agent. It is busy with another operation.
{code}
{kb-cause}
CDP 3.0 does not support running more than one backup at a time. There is an embedded queue mechanism that is activated when two policies attempt to save Recovery Points to the same Disk Safe (called the "Disk Safe Write Lock"). The problem here is that the Agent has two different policies with two different Disk Safes, and thus the lock is not triggered.
{kb-resolution}
You need to spread out your backup operations. Create a separate Policy for each Disk Safe.
_Or:_
Try scheduling the Policies so they do not run simultaneously or overlap.
{kb-related-articles}