11-29-2021 09:12 AM
Received error code 84 on a backup to PureDisk MSDP
Master server is RedHat Linux running NetBackup 8.2
Media server is NetBackup appliance 5240 with version 3.2 maintenance release 2
Error messages included below
Nov 28, 2021 10:31:53 AM - Info bpbkar (pid=4352) 204376 entries sent to bpdbm
Nov 28, 2021 10:34:28 AM - Critical bptm (pid=252290) get frag failed, backup id (enyrsrfilenetp1_1636251000)
Nov 28, 2021 10:34:28 AM - Critical bptm (pid=252290) image write failed: error 227: Not an OST error code
Nov 28, 2021 10:34:30 AM - Error bptm (pid=252290) cannot write image to disk, Invalid argument
Nov 28, 2021 10:34:30 AM - Info bptm (pid=252290) EXITING with status 84 <----------
11-29-2021 09:18 AM
also get a status 71 in the same backup.
Nov 28, 2021 10:34:28 AM - Critical bptm (pid=252290) get frag failed, backup id (enyrsrfilenetp1_1636251000)
Nov 28, 2021 10:34:28 AM - Critical bptm (pid=252290) image write failed: error 227: Not an OST error code
Nov 28, 2021 10:34:30 AM - Error bptm (pid=252290) cannot write image to disk, Invalid argument
Nov 28, 2021 10:34:30 AM - Info bptm (pid=252290) EXITING with status 84 <----------
Nov 28, 2021 10:34:30 AM - Info enyalbnbu002 (pid=252290) StorageServer=PureDisk:enyalbnbu002; Report=PDDO Stats for (enyalbnbu002): scanned: 5780510741 KB, CR sent: 26521830 KB, CR sent over FC: 0 KB, dedup: 99.5%, cache disabled, where dedup space saving:87.5%, compression space saving:12.0%
Nov 28, 2021 10:34:32 AM - Info bpbkar (pid=4352) done. status: 84: media write error
Nov 28, 2021 10:34:32 AM - end writing; write time: 14:32:13
Nov 28, 2021 1:34:34 PM - Info bpbrm (pid=323373) Starting delete snapshot processing
Nov 28, 2021 1:34:36 PM - Info bpfis (pid=7964) Backup started
Nov 28, 2021 1:34:42 PM - Error bpbrm (pid=323373) from client enyrsrfilenetp1: Delete bpfis state from enyalbnbu001 failed. status = 71
note that it took about 3 hours to get from 'end writing time' to actually trying to delete the snapshot
11-29-2021 01:08 PM - edited 11-29-2021 01:14 PM
Hi @PaulStevens
This could be an issue with accelerator track logs (without other information relating to the circumstances of the backup and other details). Review this article and see if this helps.
https://www.veritas.com/support/en_US/article.100049585
The two suggestions are to either try an accelerator forced rescan job (probably requires a new schedule), or to delete the relevant track logs for this backup. Note: Under the track log directories, there will be a number of directories created that correspond to the master server name, storage server name, policy name, client name, and backup selections, therefore, only remove track logs related to the specific Accelerator backup needing attention.
Cheers
David
11-30-2021 10:18 AM
Thanks David. Due to the nature of the application running on this server, it takes down the application while backup is running. And it is quite large so we cannot take it down that long during the week.
I scheduled my Full with Accelerator Forced Rescan for Saturday night and we'll see how that goes.
--Paul