there was an issue with the backup last night, tape drive had an error.

so I am now running backup exec on my two exchange 2013 servers that are in DAG group since missed backup last night

we had issues earlier this week with replication, so I am running get-mailboxdatabsecopystatus *, checking on the health of the database and queues, and noticed that the CopyQueue length was growing, went from 5, then 35, then 145, but now back to 0.

is this a byproduct of the backup process.?  I would think so.  since the backups are done at night, I am usually not logging in and checking the mailbox copy status while the backup is running.

just would feel better if I knew this was the case.

there was an issue with the backup last night, tape drive had an error.

so I am now running backup exec on my two exchange 2013 servers that are in DAG group since missed backup last night

we had issues earlier this week with replication, so I am running get-mailboxdatabsecopystatus *, checking on the health of the database and queues, and noticed that the CopyQueue length was growing, went from 5, then 35, then 145, but now back to 0.

is this a byproduct of the backup process.?  I would think so.  since the backups are done at night, I am usually not logging in and checking the mailbox copy status while the backup is running.

just would feel better if I knew this was the case.

Yea, or just a user who just uploaded a bunch of messages or received some etc... 145 is not high and spikes are normal.

Hi,

Is this queue increase continuously?

If so, we need to reseed this Failed Database Copy. Please refer to below steps:
1. Run  Get-MailboxDatabaseCopyStatus * to list the health status for mailbox database.
2. Then Suspend, Update, Resume MailboxDatabaseCopy with SourceServer, DatabaseOnly or CatalogOnly paramenter as your want.
More details about it, for your reference: https://technet.microsoft.com/en-us/library/ff359982(v=exchg.140).aspx

Hope it help!