Regresar
-
Título
Determining the reason for “waiting for media” status -
Descripción
Determining the reason for “waiting for media” status -
Causa
When a job is in Waiting for Media state, it implies that the job is unable to initiate data transfer as the target driveor media item is unavailable. The Diagnose Job method allows you to determine the exact reason for this state.A job may be in the Waiting for Media state due to the following reasons:• The target media or device is in use by a different job.• The target device is offline.• The target media item is not loaded.• "Reuse Media" option is not selected for the job. So, the job is waiting for new media.• No blank or reusable media item is available for the job.• Media is unusable. -
Resolución
To determine the exact reason for the “Waiting for Media” status:1. In the Navigation pane, click Job Status.2. In the list of jobs, select the job and click the [🩺Diagnose Job] button.
3. On the Diagnose Media Request page, you can view the following information:- Media Request ID: Media request ID
- Request Type: Backup or restore.
- Status: Status of the media request.
- Priority: Media request priority.
- Client: NetVault Client on which the job is running.
- Storage Tier: Logical group of storage media.
- Media: Target media and group label (if specified).
- Reuse Media: The “Reuse Media” option is selected or not.
- Required Space: Amount of space required on the media to complete the current request.
- Ensure backup is the first on the target media: The “Ensure This Backup is First on the Media” option is selected or not.
- Auto-Label: The “Label Blank Media Automatically” option is selected or not.
- Mark Read-Only After: The “Mark Media Read-Only” option is selected or not.
- Media Format: Media format.
- Unload on Completion: Media to be unloaded after job completion or not.
- Drives: Drive on which the tape resides.
- Force Local: The “Local Drives Only” option is selected or not.
▪ Network Compression: The “Network Compression” option is selected or not.
4. The Drives list show the ones allowed to be used by the job. If none is listed, modify the job's Target Set, so the correct drives are selected.
5. The Reasons table lists the details why the specified device or media cannot be used for the job. Among the available reasons, here are the most common ones:- Not enough space: media lacks the estimated amount of storage space required for the backup job
- Currently unavailable: media cannot be currently assigned for the job
- Not target MID: the media label doesn't match the one specified for the job
- The 'force local drives' option is set: the device is considered network attached
Based on the reasons listed, among the actions that could be taken the following are include:
- If all drives are currently writing data, wait for one to become available. Changing the jobs schedule could minimize contention for the drives.
- Verify that the correct storage device was selected on job Target Set.
- Ensure that tape libraries content was properly updated by following the correct procedure.
- Reconfigure the job to reuse media.
- Rotate blank tapes into the library. Verify that job is configured to use blank media and can label them.
- Manually blanking older tapes which are no longer needed. Caution: data cannot be recovered or restored from a blanked media.
- Bring unavailable drives back online