Possible statuses for an active job include the following:
Table: Active job statuses
Item |
Description |
---|---|
Running |
The operation is underway. |
Queued |
The job has been initiated, but Backup Exec is actively looking for a suitable drive or media. |
Cancel Pending |
Backup Exec cannot process the Cancel request immediately. This status is displayed until the job is actually canceled. The job is then displayed in Job History with a status of Canceled. |
Loading Media |
The media is being loaded and positioned on the target device. |
Pre-processing |
This status can indicate any or all of the following:
|
Snapshot processing |
Backup Exec is processing a snapshot operation. |
Device Paused |
The device that the job was sent to is paused. |
Server Paused |
The media server is paused. |
Stalled |
The Backup Exec services have become unresponsive. |
Media Request |
You must insert media for the job to continue. |
Communication Stalled |
Communications between the managed media server and the central administration server have not occurred within the configured time threshold. See Setting communication thresholds and active job status updates for CASO . |
No Communication |
No communication about jobs is being received at the central administration server from the managed media server. The configured time threshold has been reached. See Setting communication thresholds and active job status updates for CASO . |
Consistency Check |
Backup Exec is running a consistency check of the databases before backup. |
Updating Catalogs |
Backup Exec is updating the catalog information. |
Schedule, CPS backup job running |
The Exchange logs are being continuously protected with Continuous Protection Server (CPS). The status appears if you check the option Continuously back up transaction logs with Backup Exec Continuous Protection Server on the backup job properties for Exchange backups. |
The server encountered an internal error or misconfiguration and was unable to complete your request.
Please contact the server administrator at webmaster@systemmanager.forsenergy.ru to inform them of the time this error occurred, and the actions you performed just before this error.
More information about this error may be available in the server error log.
Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request.