NDMP

18 Topics

NDMP media write error(84) while writting to Data Domain
Hello, Hardware/software info: Netbackup Server Linux Redhat using Netbackup version 7.7.3 (master as media) Client: os version "NetApp Release 8.2.4P6 7-Mode" DD6300 OS 6.0.1.10-561375 It is my first post so please forgive me mistakes. I have an issue with NDMP backup. The problem occures only with montlhy schedule wchich is using accelerator forced rescan option. It was working properly long time and a few days ago strated to fail with error code 84 media write error. It starts to write data and after some time fails. The backups goes directly to DD via DDboost. I do not have an access into client so I need to focuse on master server. anyone has faced similar issue? Job details: ... 01/09/2018 09:07:41 - Info ndmpagent (pid=17596) HOST1: DUMP: Tue Jan 9 09:04:10 2018 : We have written 688907814 KB. 01/09/2018 09:12:41 - Info ndmpagent (pid=17596) HOST1: DUMP: Tue Jan 9 09:09:10 2018 : We have written 692824322 KB. 01/09/2018 09:21:27 - Critical bptm (pid=17598) include image error, bytesw(53248) not equal to wlen(524288) 01/09/2018 09:21:27 - Critical bptm (pid=17598) image write failed: error 2060022: software error 01/09/2018 09:21:38 - Error bptm (pid=17598) cannot write image to disk, Invalid argument 01/09/2018 09:21:38 - Info ndmpagent (pid=17596) Received ABORT request from bptm 01/09/2018 09:21:38 - Error ndmpagent (pid=17596) NDMP backup failed, path = /vol/Vol_docs 01/09/2018 09:21:38 - Error ndmpagent (pid=17596) HOST1: DUMP: Write to socket failed 01/09/2018 09:21:38 - Error ndmpagent (pid=17596) HOST1: DUMP: DUMP IS ABORTED 01/09/2018 09:21:39 - Error ndmpagent (pid=17596) HOST1: DATA: Operation terminated (for /vol/Vol_docs). 01/09/2018 09:21:39 - Info bptm (pid=17598) EXITING with status 84 <---------- 01/09/2018 09:21:39 - Error bpbrm (pid=17590) could not send server status message 01/09/2018 09:21:39 - Info ndmpagent (pid=0) done. status: 84: media write error 01/09/2018 09:21:39 - end writing; write time: 19:34:29 media write error (84) BPTM logs: 09:21:27.548 [17598] <32> do_include_image: include image error, bytesw(53248) not equal to wlen(524288) 09:21:27.549 [17598] <32> write_data: image write failed: error 2060022: 09:21:27.560 [17598] <8> vnet_get_user_credential_path: [vnet_vxss.c:1474] status 35 0x23 09:21:27.560 [17598] <8> vnet_check_user_certificate: [vnet_vxss_helper.c:3728] vnet_get_user_credential_path failed 35 0x23 09:21:27.560 [17598] <2> ConnectionCache::connectAndCache: Acquiring new connection for host MASTER_SERVER_NBU, query type 161 09:21:27.561 [17598] <2> logconnections: BPDBM CONNECT FROM 172.16.57.1.57136 TO 172.16.57.1.13721 fd = 25 09:21:27.566 [17598] <2> db_end: Need to collect reply 09:21:38.459 [17598] <16> write_data: cannot write image to disk, Invalid argument 09:21:38.459 [17598] <4> write_backup: Calling close_all_ft_pipes 09:21:38.459 [17598] <2> NdmpAgentSession_abort_by_index[0]: aborting... 09:21:38.505 [17598] <2> NdmpAgentSession[0]: ndmp_xm_wait_for_abort_complete: Waiting for ABORT COMPLETE... 09:21:39.249 [17598] <2> bptm: EXITING with status 84 <---------- Connecting to host "HOST1" as user "ndmp"... Waiting for connect notification message... Opening session--attempting with NDMP protocol version 4... Opening session--successful with NDMP protocol version 4 host supports MD5 authentication Getting MD5 challenge from host... Logging in using MD5 method... Host info is: host name "HOST1" os type "NetApp" os version "NetApp Release 8.2.4P6 7-Mode" host id "0536982947" Login was successful Host supports LOCAL backup/restore Host supports 3-way backup/restore
Solved
MateuszK
7 years ago Place NetBackup
3.9KViews
0likes
6Comments
Unimplemented error code (114)
Last week, I have migrated master server to new hardware. After restored, everything works fine except my one of the NDMP host backup keep failing. Please see error logs below: Aug 22, 2017 8:33:28 PM - Info nbjm (pid=12373) starting backup job (jobid=2197) for client 10.105.33.14, policy NDMP_ston-mykul-p3n4, schedule Daily_backup Aug 22, 2017 8:33:28 PM - Info nbjm (pid=12373) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=2197, request id:{194631FA-8736-11E7-BDB8-408725342EC5}) Aug 22, 2017 8:33:28 PM - requesting resource MPX-TAPE_TLD3-HCART_HCART2 Aug 22, 2017 8:33:28 PM - requesting resource nbms-mykul-p3n1.NBU_CLIENT.MAXJOBS.10.105.33.14 Aug 22, 2017 8:33:28 PM - requesting resource nbms-mykul-p3n1.NBU_POLICY.MAXJOBS.NDMP_ston-mykul-p3n4 Aug 22, 2017 8:33:28 PM - awaiting resource MPX-TAPE_TLD3-HCART_HCART2. Waiting for resources. Reason: Drives are in use, Media server: mykulsnbmd001, Robot Type(Number): TLD(3), Media ID: N/A, Drive Name: N/A, Volume Pool: NDMP, Storage Unit: mykulsnbmd001-hcart-robot-tld-3-mpx, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Aug 22, 2017 8:33:28 PM - granted resource nbms-mykul-p3n1.NBU_CLIENT.MAXJOBS.10.105.33.14 Aug 22, 2017 8:33:28 PM - granted resource nbms-mykul-p3n1.NBU_POLICY.MAXJOBS.NDMP_ston-mykul-p3n4 Aug 22, 2017 8:33:28 PM - granted resource TB1116 Aug 22, 2017 8:33:28 PM - granted resource HP.ULTRIUM5-SCSI.004 Aug 22, 2017 8:33:28 PM - granted resource mykulsnbmd001-hcart-robot-tld-3-mpx Aug 22, 2017 8:33:28 PM - estimated 7986768 kbytes needed Aug 22, 2017 8:33:28 PM - Info nbjm (pid=12373) started backup (backupid=10.105.33.14_1503405208) job for client 10.105.33.14, policy NDMP_ston-mykul-p3n4, schedule Daily_backup on storage unit mykulsnbmd001-hcart-robot-tld-3-mpx Aug 22, 2017 8:33:29 PM - connecting Aug 22, 2017 8:33:29 PM - connected; connect time: 0:00:00 Aug 22, 2017 8:33:29 PM - begin writing Aug 22, 2017 8:42:35 PM - end writing; write time: 0:09:06 Aug 22, 2017 8:45:46 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: creating "/svm01-mykul-p1/DEPTSHARE_CIFS_OP_VOL001/../snapshot_for_backup.2340" snapshot. Aug 22, 2017 8:45:46 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: Using inowalk incremental dump for Full Volume Aug 22, 2017 8:45:48 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: Using snapshot_for_backup.2340 snapshot Aug 22, 2017 8:45:48 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: Date of this level 9 dump: Tue Aug 22 20:33:35 2017. Aug 22, 2017 8:45:48 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: Date of last level 8 dump: Tue Aug 15 20:03:08 2017. Aug 22, 2017 8:45:48 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: Dumping /svm01-mykul-p1/DEPTSHARE_CIFS_OP_VOL001/ to NDMP connection Aug 22, 2017 8:45:48 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: mapping (Pass I)[regular files] Aug 22, 2017 8:45:52 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: mapping (Pass II)[directories] Aug 22, 2017 8:46:12 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: No available buffers. Aug 22, 2017 8:46:12 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: DUMP IS ABORTED Aug 22, 2017 8:46:12 PM - Error ndmpagent (pid=26939) read from socket returned -1 104 (Connection reset by peer) Aug 22, 2017 8:46:12 PM - Error ndmpagent (pid=26939) MOVER_HALTED unexpected reason = 4 (NDMP_MOVER_HALT_CONNECT_ERROR) Aug 22, 2017 8:46:12 PM - Error ndmpagent (pid=26939) NDMP backup failed, path = /svm01-mykul-p1/DEPTSHARE_CIFS_OP_VOL001/ Aug 22, 2017 8:46:12 PM - Info ndmpagent (pid=26939) 10.105.33.14: DUMP: Deleting "/svm01-mykul-p1/DEPTSHARE_CIFS_OP_VOL001/../snapshot_for_backup.2340" snapshot. Aug 22, 2017 8:46:13 PM - Error ndmpagent (pid=26939) 10.105.33.14: DATA: Operation terminated (for /svm01-mykul-p1/DEPTSHARE_CIFS_OP_VOL001/). Aug 22, 2017 8:54:27 PM - Info bpbrm (pid=25638) sending message to media manager: STOP BACKUP 10.105.33.14_1503405208 Aug 22, 2017 8:54:36 PM - Info bpbrm (pid=25638) media manager for backup id 10.105.33.14_1503405208 exited with status 0: the requested operation was successfully completed unimplemented error code (114) NetBackup version: 8.0 NDMP:NetApp Release 8.2.1P1 Cluster-Mode Backup Method: MPX
Junz
7 years ago Place NetBackup
3.5KViews
0likes
3Comments
Unable to configure replaced tape drive | netbackup 6.5
Hi All, Recently a tape drive was replaced. This tape drive is connecetedn to filer through FC end to end connection. While configuring this tape drive we are unable to detect this tape drive at Netbackup level. Checkpoint infront of this tape library is disabled and it displays a message "tape drive attached to remote host". Any suggestions on how to get this corrected? Thanks in advance
Solved
Deepak_Irani1
8 years ago Place NetBackup
3.3KViews
0likes
7Comments
NDMP Restore failing
Having an issue with an NDMP restore. It's failing with a 2813 error. Here is what I get in the detailed status: 2/10/2017 4:39:17 PM - Critical bptm(pid=6212) sts_read_image failed: error 2060001 bytes Read = 18339597817245633366one or more invalid arguments 2/10/2017 4:39:17 PM - Error ndmpagent(pid=4960) connection 01231908 ndmp_message_process_one failed, status = 18 (NDMP_XDR_DECODE_ERR) 2/10/2017 4:39:17 PM - Error ndmpagent(pid=4960) NDMP restore failed from path /ifs/LonProdMedia/lonvidediting/PROJECTS 2/10/2017 4:39:22 PM - Error ndmpagent(pid=4960) LONVIDNAS01.ap.org: Failed to read data from daemon: No such file or directoryError reading file data (31009/-1): No such file or directoryWrite error: Invalid argument: ifs/LonProdMedia/lonvidediting/PROJECTS/ZARA WORK IN PROGRESS/zara.prproj 2/10/2017 4:39:22 PM - Error ndmpagent(pid=4960) LONVIDNAS01.ap.org: Could not skip data giving up 2/10/2017 4:39:22 PM - Error ndmpagent(pid=4960) LONVIDNAS01.ap.org: Failed to read archive during DAR for index 0 2/10/2017 4:39:22 PM - Warning ndmpagent(pid=4960) LONVIDNAS01.ap.org: Error extracting entry {ZARA WORK IN PROGRESS/zara.prproj, /ifs/LonProdMedia/lonvidediting/PROJECTS/ZARA WORK IN PROGRESS/zara.prproj} at index 0 of NLIST 2/10/2017 4:39:22 PM - Warning ndmpagent(pid=4960) LONVIDNAS01.ap.org: Operation halted by DMA 2/10/2017 4:39:22 PM - Error ndmpagent(pid=4960) send error status = 12 (NDMP_EOF_ERR) 2/10/2017 4:39:23 PM - Info ndmpagent(pid=4960) done 2/10/2017 4:39:23 PM - Info ndmpagent(pid=4960) done. status: 27: child process killed by signal 2/10/2017 4:39:23 PM - Error bpbrm(pid=4128) client restore EXIT STATUS 27: child process killed by signal 2/10/2017 4:39:23 PM - restored image lonvidnas01.ap.org_1486279880 - (child process killed by signal(27)); restore time 00:00:14 2/10/2017 4:39:23 PM - end Restore; elapsed time: 00:00:15 NDMP policy restore error(2813) I've looked into the solutions for the status code but can't see an issue. I would appreciate any help you could give.
smwoodcrafts
8 years ago Place NetBackup
3.3KViews
0likes
16Comments
NetBackup Hardware Tier Matrix
Hello all. I haven't been able to find the NDMP hardware tier Matrix for NBU. Any clue on where to find such a document? I've tried the NBU licensing guide sugested path in partnernet (Licensing > Pricelists > Additional Pricing Documents), VOX community search, PartnerNet search and even Google search; but so far I've just found a 2010 version for thisNDMP hardware tier Matrix document which iscompletely obsolete. Any help on this with be much appriciated.
Solved
CHACONR
7 years ago Place NetBackup
2.9KViews
0likes
2Comments
Manual Duplication is failing with 191 error code
NetBAckup Version: 8.1.1 OS Version: SLES 12 SP 1 My duplication job which is done by SLP fails with the following error after witing a couple of bytes. Apr9,201912:30:59PM-mounting0384L7 Apr9,201912:30:59PM-Infobptm(pid=18780)INF-Waitingformountofmediaid0384L7onserversivls105forwriting. Apr9,201912:31:32PM-Infobptm(pid=18780)mediaid0384L7mountedondriveindex21,drivepath/dev/alias/nst/C3EC3D2008,drivenameIBM.ULTRIUM-HH7.003,copy2 Apr9,201912:31:32PM-Infobptm(pid=18780)INF-Waitingforpositioningofmediaid0384L7onserversivls105forwriting. Apr9,201912:35:07PM-Errorbptm(pid=13610)cannotreadimagefromNDMPmediaid@aaaab,driveindex-1,errorcode20(NDMP_UNDEFINED_ERR) Apr9,201912:35:07PM-Errorbptm(pid=13610)NBEMMreturnedanextendederrorstatus:Invalidargument(4000002) Apr9,201912:35:07PM-Infobptm(pid=13610)EXITINGwithstatus85<---------- Apr9,201912:35:09PM-Errorbptm(pid=18780)mediamanagerterminatedbyparentprocess Apr9,201912:36:31PM-Errorbpduplicate(pid=18763)hostsivls106backupidmp2vmsd058_1524904249readfailed,mediareaderror(85). Apr9,201912:36:31PM-Errorbpduplicate(pid=18763)hostsivls105backupidmp2vmsd058_1524904249writefailed,mediamanagerkilledbysignal(82). Apr9,201912:36:31PM-Errorbpduplicate(pid=18763)Duplicateofbackupidmp2vmsd058_1524904249failed,mediamanagerkilledbysignal(82). Apr9,201912:36:31PM-Errorbpduplicate(pid=18763)Status=noimagesweresuccessfullyprocessed. Apr9,201912:36:31PM-endDuplicate;elapsedtime0:05:35 noimagesweresuccessfullyprocessed (191)
ngarart
6 years ago Place NetBackup
1.9KViews
0likes
4Comments
NDMP Restore to Different Location (NetApp C-mode)
HI Evnironment: MasterServer: Window Server 2012 R2 Netbackup Version : 7.6.0.1 NetApp Version :9 C-MODE Can anyone help me to restore NDMP to different location. When I restore file to different folder , it show "ERROR: restore not initial: the restore failed to recover the requested file (5)" 1. How to configuration restore NDMP to different folder? 2. If I want to restore files to different volume,how to do it. 3. What are log files to solve this issue
Pellnapook
8 years ago Place NetBackup
1.9KViews
0likes
1Comment
ndmp backup stops in middle of backup job
Hello people, Our ndmp filers can connect to the backup server but backupping the data is not going to complete. The others clients such as Windows file servers and linux machines backup state is perfect.The backup media master server is NB 8.1.2 on Windows Server 2016 fully patched. The backup server can connect to the NDMP host, runs for 10 - 20 minutes while writing data and then stops. Can someone give usefull information?
VeritasNB
5 years ago Place NetBackup
1.7KViews
0likes
6Comments
NDMP, Netapp cDOT 8.2, and parent policy to coordinate snapshot creation?
Hi, I'm trying to coordinate the creation of backup Snapshots when I backup two seperate, but related volumes of data. Because we're running NBU 7.7.3 on Solaris, and Netapp cDOT 8.2, we cannot do CAB (Cluster Aware Backups) until we upgrade to cDOT 8.3 sometime in the future. Which is a pain. I've got two volumes, Foo & Bar, which need to be snapshotted at the same time, but are on seperate nodes. Would using a parent policy with two sub-policies be the way to make this happen? We don't need the actual NDMP backups to be in parallel at all. I've been looking at the docs, and we've done bpstart_notify.<POLICY> scripts in the past, but I'm a bit stumped on how I should do it now? If we put both volumes into one policy, then it won't run properly because the policy is bound to a single Node on the Netapp. And of course we have the volumes spread across multiple nodes. Thanks, John
jstoffel-tosh
8 years ago Place NetBackup
1.7KViews
0likes
5Comments
Can I restart a failed NDMP Restore (NBU 8)
Hi, Performing lots of detailed restores. A couple have failed. I dont see an option to resume, is there anyway I can restart? They are very specific so re-creating the job each time is very long winded. I am using the B,A and R client within the NBU console. I also have OpsCenter analytics access but also do not see a restart option. Thanks!
Solved
bunsen82
7 years ago Place NetBackup
1.7KViews
0likes
3Comments