cancel
Showing results for 
Search instead for 
Did you mean: 

media write error (84)

Intore
Level 4

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 server and the policy is MS-Windows type.

The backup performed with "Accelerator forced rescan" fails with media write error (84).

I can show you the job details. Do you have more suggestions please?

Thank you

Dec 11, 2019 11:03:11 AM - Info nbjm (pid=8556) starting backup job (jobid=6629604) for client client_name, policy policy_name, schedule ManualWithRescan
Dec 11, 2019 11:03:11 AM - estimated 73956609 kbytes needed
Dec 11, 2019 11:03:11 AM - Info nbjm (pid=8556) started backup (backupid=clientname_1576058591) job for client client_name, policy policy_name, schedule ManualWithRescan on storage unit *****
Dec 11, 2019 11:03:12 AM - started process bpbrm (pid=9372)
Dec 11, 2019 11:03:21 AM - Info bpbrm (pid=9372) client is the host to backup data from
Dec 11, 2019 11:03:22 AM - Info bpbrm (pid=9372) reading file list for client client_name
Dec 11, 2019 11:03:23 AM - Info bpbrm (pid=9372) accelerator enabled
Dec 11, 2019 11:03:32 AM - Info bpbrm (pid=9372) Accelerator enabled backup with "Accelerator forced rescan", all data will be scanned and processed.Backup time will be longer than a normal Accelerator enabled backup.
Dec 11, 2019 11:03:32 AM - connecting
Dec 11, 2019 11:03:34 AM - Info bpbrm (pid=9372) starting bpbkar32 on client client_name
Dec 11, 2019 11:03:35 AM - connected; connect time: 0:00:00
Dec 11, 2019 11:03:36 AM - Info bpbkar32 (pid=11296) Backup started
Dec 11, 2019 11:03:41 AM - Info bpbkar32 (pid=11296) change time comparison:<enabled>
Dec 11, 2019 11:03:41 AM - Info bpbkar32 (pid=11296) accelerator enabled backup, archive bit processing:<disabled>
Dec 11, 2019 11:03:41 AM - Info bptm (pid=4280) start
Dec 11, 2019 11:03:41 AM - Info bptm (pid=4280) using 262144 data buffer size
Dec 11, 2019 11:03:41 AM - Info bptm (pid=4280) setting receive network buffer to 1049600 bytes
Dec 11, 2019 11:03:41 AM - Info bptm (pid=4280) using 30 data buffers
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) will attempt to use change journal data for <C:\>
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) will attempt to use change journal data for <F:\>
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) will attempt to use change journal data for <H:\>
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) will attempt to use change journal data for <I:\>
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) will attempt to use change journal data for <Q:\>
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) will attempt to use change journal data for <S:\>
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) not using change journal data for <System State:\>: not supported for non-local volumes / file systems
Dec 11, 2019 11:03:44 AM - Info bpbkar32 (pid=11296) not using change journal data for <_BACKUP_SPECIAL_OBJECTS AFTER System State > not supported for non-local volumes / file systems
Dec 11, 2019 11:03:49 AM - Info bptm (pid=4280) start backup
Dec 11, 2019 11:03:49 AM - Info bptm (pid=4280) backup child process is pid 3636.9952
Dec 11, 2019 11:03:49 AM - begin writing
Dec 11, 2019 11:03:49 AM - Info bptm (pid=3636) start
Dec 11, 2019 11:04:31 AM - Info bpbkar32 (pid=11296) not using change journal data for <C:\>: not supported with true image backups
Dec 11, 2019 11:05:01 AM - Critical bptm (pid=4280) A portion of data to be included from a previous backup (backupid = client_name_1575974485, offset = 582946304, length = 26624) has incorrect checksum (calculated checksum from backup image 5fd2802e4192e8ed65ec9eacec90bd0f1d737cb7, expected checksum 708f1501781af69885acea047c403e0fec5b90de)
Dec 11, 2019 11:05:02 AM - Critical bptm (pid=4280) image write failed: error -1: Not an OST error code
Dec 11, 2019 11:05:04 AM - Error bptm (pid=4280) cannot write image to disk, Invalid argument
Dec 11, 2019 11:05:04 AM - Info bptm (pid=4280) EXITING with status 84 <----------
Dec 11, 2019 11:05:06 AM - Error bpbrm (pid=9372) cannot send mail to ******
Dec 11, 2019 11:05:07 AM - Info bpbkar32 (pid=11296) done. status: 84: media write error
Dec 11, 2019 11:05:07 AM - end writing; write time: 0:01:18
media write error  (84)
Dec 11, 2019 11:05:10 AM - Info bpbrm (pid=12784) Starting delete snapshot processing
Dec 11, 2019 11:05:12 AM - Info bpfis (pid=1816) Backup started
Dec 11, 2019 11:05:12 AM - Warning bpbrm (pid=12784) from client: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.client_name_1576058591.1.0
Dec 11, 2019 11:05:12 AM - Info bpfis (pid=1816) done. status: 4207
Dec 11, 2019 11:05:12 AM - Info bpfis (pid=1816) done. status: 4207: Could not fetch snapshot metadata or state files

1 ACCEPTED SOLUTION

Accepted Solutions

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. 

View solution in original post

5 REPLIES 5

Marianne
Moderator
Moderator
Partner    VIP    Accredited Certified

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 

 

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

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
Moderator
Moderator
Partner    VIP    Accredited Certified

@Intore 

Please try @Hooray888 's suggestion.

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

Thank you, your solution has solved.