Forum Discussion

egoncharov's avatar
egoncharov
Level 4
15 years ago

error e0000602 during backup on tape

12.x and Earlier
Backup and Recovery
Backup Exec
  • Colin_Weaver's avatar
    Colin_Weaver
    15 years ago
    Assuming this is policy based with duplicates set to follow the backups.

    Are your media sets configured to make sure the original data is protected for long enough to be duplicated?
    Did anything fail on previous jobs in the sequence

    Be aware if a policy based duplicate is set to run immediately after the original backup, and the duplicate itself fails to complete the next time a duplicate runs it will be expecting to backup both previous backups not just the latest one.

    For example 
    1st Weekly Backup to disk runs - Duplicate job then starts but fails (for example no available media)
    2nd Weekly Backup to disk runs - Duplicate job starts and attempts to backup both 1st weekly data and 2nd weekly data

    If you take that example and only protect the media set used by the weekly backup to disk jobs for 6 days, then the 2nd Weekly job will overwrite the 1st weekly job - but the duplicate will still expect both sets of data so will fail.

    As you can see from above example to assist you we are likely to need details of when you run the backup to disk jobs, when you run the duplicate jobs, what your media sets are configured for and when previous jobs in the policy may have failed.

3 Replies

Sort By
  • egoncharov's avatar
    egoncharov
    Level 4
    15 years ago
    We have a job for full backup of servers on disk.  It works fine. The duplicate job on tape worked well week ago. Now there is an error e0000602 during duplicate backup.

    Error category    : Backup Media ErrorsError             : e0000602 - A query for media on which the data set being read is continued was unsuccessful. Ensure that all media in the family have been inventoried and cataloged.
    For additional information regarding this error refer to link V-79-57344-1538

    The links doesn't have any useful information. The jobs run on Backup Exec 12.5
  • Colin_Weaver's avatar
    Colin_Weaver
    Moderator
    15 years ago
    Assuming this is policy based with duplicates set to follow the backups.

    Are your media sets configured to make sure the original data is protected for long enough to be duplicated?
    Did anything fail on previous jobs in the sequence

    Be aware if a policy based duplicate is set to run immediately after the original backup, and the duplicate itself fails to complete the next time a duplicate runs it will be expecting to backup both previous backups not just the latest one.

    For example 
    1st Weekly Backup to disk runs - Duplicate job then starts but fails (for example no available media)
    2nd Weekly Backup to disk runs - Duplicate job starts and attempts to backup both 1st weekly data and 2nd weekly data

    If you take that example and only protect the media set used by the weekly backup to disk jobs for 6 days, then the 2nd Weekly job will overwrite the 1st weekly job - but the duplicate will still expect both sets of data so will fail.

    As you can see from above example to assist you we are likely to need details of when you run the backup to disk jobs, when you run the duplicate jobs, what your media sets are configured for and when previous jobs in the policy may have failed.
  • egoncharov's avatar
    egoncharov
    Level 4
    15 years ago
    Thanks for the answer. I've analyzed the jobs and find that problem jobs are in conflict with other jobs. I've change schedule and waiting for the next backup job.