the Archive destination 2 has been disabled for all ACR servers; the Archive destination 1 was configured for Slave ACR 880003 & 880004 during 2014/08/01 00:00:00 and 2015/01/01 00:00:00, the Archive destination 1 has been manually deleted from Master ACR but failed deleting from Slave ACR (because there’s already archive job performed for the two Slave ACR). That’s the reason that archive job still in running state in slave ACR.
For slave ACR 880004, the archive job has done for all recordings, therefore it has no archive job in jobqueue and has no more alarm for archive job;
For slave ACR 880003, there’re still 1700000+ archive job exists in jobqueue, therefore it still perform archive job. For any reason (e.g. recording file does not exists, archive file copy problem…etc), the job will stalled and show alarm in web portal.