Forum Discussion

anthonym's avatar
anthonym
Level 3
13 years ago

Duplicate Dedupe Job fails half way through

We are running a daily/weekly/monthly policy to a dedicated dedupe folder (B2D) and it works just fine. I have setup a duplicate job (inside policy) to an offsite B2D dedupe folder (again dedicated using and CASO/MMS setup) for both the daily and weekly jobs and it gets about 2 hours into the job and fails with the following error:

The requested media was mounted, but it has been erased and does not contain any backup sets

I also get the following errors on the logs only on some servers, not all.

 

A selection on device \\IDSFILESERVER\D: was skipped because of previous errors with the job.
A selection on device \\IDSFILESERVER\E: was skipped because of previous errors with the job.
A selection on device \\IDSFILESERVER\System?State was skipped because of previous errors with the job.
A selection on device \\MATTHEWSDB2.matthews.com.au\C: was skipped because of previous errors with the job.
A selection on device \\MATTHEWSDB2.matthews.com.au\D: was skipped because of previous errors with the job.
A selection on device MATTHEWSDB2.matthews.com.au was skipped because of previous errors with the job.
A selection on device MATTHEWSDB2.matthews.com.au\SQLEXPRESS2008 was skipped because of previous errors with the job.
A selection on device \\MATTHEWSDB2.matthews.com.au\Shadow?Copy?Components was skipped because of previous errors with the job.
A selection on device \\MATTHEWSDB2.matthews.com.au\System?State was skipped because of previous errors with the job.
A selection on device \\MATTHEWSFS3.matthews.com.au\C: was skipped because of previous errors with the job.
A selection on device \\MATTHEWSFS3.matthews.com.au\D: was skipped because of previous errors with the job.
 
Strange thing is I do not get errors on the original backup for these 3 servers and we are backing up 6 servers in total and the other 3 duplicate just fine.
 
Any ideas?
2010
Backing Up
Backup and Recovery
Backup Exec
Error messages
  • mwalker's avatar
    mwalker
    13 years ago

    After installing SP2 and waiting for 10 Days, this Problem did not occured again.

    So SP2 seems to resolve this issue.

    If you can confirm that for your environment you should mark this as Solution.

    thx

15 Replies

Sort By
  • pkh's avatar
    pkh
    Moderator
    13 years ago

    It could be due to some failure of the duplicate jobs, resulting in errors in the history.

    Since you are generating your backup and duplicate jobs from a policy, delete the existing jobs and then re-create them.  This will reset the job history.

  • anthonym's avatar
    anthonym
    Level 3
    13 years ago

    Thanks for that. I did do this as I recreated the dedupe folder on the MMS server and the first duplicate job failed. Do I need to recreate the original and duplicate jobs all over again? Also, I got these error messages that may refer to the previous messages (sorry just saw them!!). These appear on all the previously mentioned servers.

     

    V-79-8192-4881 - The count of Files and Directories processed is not available for this operation. The File and Directory count might be displayed as zero.
  • pkh's avatar
    pkh
    Moderator
    13 years ago

    I think you should re-create all the jobs that have errors.

  • anthonym's avatar
    anthonym
    Level 3
    13 years ago

    OK I have copied the policy, renamed it, renamed the jobs in the policy and created new jobs from the new policy and put the old jobs on hold. I have also excluded a couple of files that were causing the backup to complete with exception so we should get a clean daily tonight and hopefully a clean deplicate as well...fingers crossed

  • pkh's avatar
    pkh
    Moderator
    13 years ago

    Instead of copying policies, you could have copied your selection lists, give them new names and generate new jobs from these copied selection lists.  Actually, there is no need to keep the old jobs.  You could have deleted them.

  • anthonym's avatar
    anthonym
    Level 3
    13 years ago

    Followed your advise and recreated the policy and created brand new jobs. First daily differential and subsiquent duplicate to offsite DR went through no problems. The next day differential failed with the same error below:

     

    V-79-57344-1541 - The requested media was mounted, but it has been erased and does not contain any backup sets.
     
    Then this message on all servers in the backup selection list:
     
    A selection on device \\server\D: was skipped because of previous errors with the job.
     
    There doesn't seem to be any reason why it works ok one day then fails the next. I have changed the media set from Daily Media Set to Keep for 4 weeks and am trying it again. The only thing else I can think of is reissuing the agent to each of the servers being backed up as I have moved the CASO to a new server.
     
    Any thoughts on this?
  • pkh's avatar
    pkh
    Moderator
    13 years ago

    Go to Tools ---> Options ---> Media Management and check that the Overwrite Protection Level is set to Partial or Full.

  • anthonym's avatar
    anthonym
    Level 3
    13 years ago

    Tried this and no good. I also tried recreating the selection list, policy and all the jobs. Strange thing is I get a backup one night that goes through (barring skipping 1 exception) and a successful duplicate job to my offsite DR MMS using CASO, then  the next night it fails. I have attached the logs from the backup last night that failed and the logs from the full backup on Sat that was successful. I have since changed the backup set to keep indefinately and changed to alway overwrite on each template in the policy. I am at a loss at the moment. (one thing i read was restore will still work from a failed backup which is conforting)

    note: 114 was successful and 119 failed

  • anthonym's avatar
    anthonym
    Level 3
    13 years ago

    checked and restore jobs fail as well...need some help if there is anyone there who can