Forum Discussion

Intore's avatar
Intore
Level 4
5 years ago

media write error (84)

Hi, I already read the other disussions about the same issue but the proposed solutions have not solved my problem. Master server, media and client involved are NBU 8.1.2. The client is a physical...
8.1.2
windows server 2012
  • Hooray888's avatar
    Hooray888
    5 years ago

    Before I also ran into this media write error (84) message when performed the Accelerated Full Forced Rescan backup with one Windows client. 

    The fix is that go to the C:\Program Files\Veritas\NetBackup\track\ directory on this Windows client, and then delete the existing Accelerated folder associated with this windows client.  Then start over the Accelerated Full Forced Rescan backup, it would be ok this time.  Please have a try with this. 

Marianne's avatar
Marianne
Level 6
5 years ago

The problem is not with Accelerator (which sits on the client), but with a previous image on the media server. It seems that image id client_name_1575974485 is corrupt. 

I doubt that you will be able to restore from this image. 
Possibly best to expire this image and re-do a full backup.
The backup is only 2 days old - 1575974485 = Tuesday, 10-Dec-19 10:41:25 UTC 

 
  • Intore's avatar
    Intore
    Level 4
    5 years ago

    Hello Marianne, thank you for the reply.

    the backup-id (client_name_1575974485) mentioned in job details corresponds to a backup process that was finished with status code 1. These are the warnings:

    Dec 10, 2019 12:07:35 PM - Warning bpbrm (pid=13048) from client client_name: WRN - can't open file: C:\Users\username\NTUSER.DAT (WIN32 3: The system cannot find the path specified. )
    Dec 10, 2019 12:08:05 PM - Warning bpbrm (pid=13048) from client client_name: WRN - can't open file: C:\Users\username\AppData\Local\Microsoft\Windows\UsrClass.dat (WIN32 3: The system cannot find the path specified.)

    I just did expire that backup image and I re-started a full backup with Accelerator forced rescan option enabled. Unfortunatelly this job fails with error "media write error (84)" and the cause seems to be another corrupted image that is related to a backup job (differential backup) successfully completed on 11th December.

    Do I have to expire the image backwards? I don't really like this way!

    Intore

    • Hooray888's avatar
      Hooray888
      Level 3
      5 years ago

      Before I also ran into this media write error (84) message when performed the Accelerated Full Forced Rescan backup with one Windows client. 

      The fix is that go to the C:\Program Files\Veritas\NetBackup\track\ directory on this Windows client, and then delete the existing Accelerated folder associated with this windows client.  Then start over the Accelerated Full Forced Rescan backup, it would be ok this time.  Please have a try with this. 

      • Intore's avatar
        Intore
        Level 4
        5 years ago

        Thank you, your solution has solved.

         

    • Marianne's avatar
      Marianne
      Level 6
      5 years ago

      Intore 

      Please try Hooray888 's suggestion.

      If that does not work, please log a Support call with Veritas.