Avamar: If a client is being replicated, backups for that same client remain in a Waiting-Queue state

If a replication job is running for a particular client, backups for that client cannot run simultaneously.

The backup job remains in a "Waiting-Queue" state until the replication job completes or is cancelled.

This issue occurs when the replication job was started using the "avrepl" command with the flag "--send-adhoc-request=false".

Example:

avrepl --operation=replicate --[replscript]dstaddr=<target-avamar> --[replscript]dstid=repluser --dstpassword=<target-repluser-password> --[replscript]fullcopy=true --send-adhoc-request=false --max-streams=2 --[replscript]timeout=0 --[replscript]dstencrypt=ssl --[avtar]incpartials=true...

This is commonly seen during a migration.

1. Cancel the running replication job.

2. Restart the replication job without the flag:

For example, based on the example above:

With the flag:

avrepl --operation=replicate --[replscript]dstaddr=<target-avamar> --[replscript]dstid=repluser --dstpassword=<target-repluser-password> --[replscript]fullcopy=true --send-adhoc-request=false --max-streams=2 --[replscript]timeout=0 --[replscript]dstencrypt=ssl --[avtar]incpartials=true...

Without the flag:

avrepl --operation=replicate --[replscript]dstaddr=<target-avamar> --[replscript]dstid=repluser --dstpassword=<target-repluser-password> --[replscript]fullcopy=true --max-streams=2 --[replscript]timeout=0 --[replscript]dstencrypt=ssl --[avtar]incpartials=true...

Backup and replication jobs for the same client should now run simultaneously.