Convert Netbackup Appliance 5250 to Flex Appliance 5250.
Hi everyone, I understand that the NetBackup Appliance 5250 is great, but it lacks WORM (Immutable). I would like to inquire if it's possible to convert the NetBackup Appliance 5250 to a Flex Appliance 5250. Thanks, Rick.1.1KViews0likes2CommentsSlow CIFS backups
WE have CIFS shares on a netapp device. Backup of these shares has gotten extremely slow. (From about 8-10 mb/sec to 200-400 kb/sec. I have noticed that when this happens, the snapshot fails also. Am I correct in thinking that If the snapshot (or snapvault) fails, then the backup is taken from the disk itself, and not from the snapshot. If there are others using the netapp (and there are many) this would cause a drastic decrease in the read time on the netapp ?1.1KViews0likes2CommentsBackups are failing with error code 84 after writing 16gb of data in desktop
Hi All , Backup for one of the Lab PC is getting faled with 84 after writing some data .Please help me on this . Dec15,201912:31:16PM-Infonbjm(pid=90913)startingbackupjob(jobid=5862919)forclient07r-malvern02,policyGOLD-FS-07R-LABPC-GRP1,scheduleWeekly Dec15,201912:31:16PM-Infonbjm(pid=90913)requestingSTANDARD_RESOURCEresourcesfromRBforbackupjob(jobid=5862919,requestid:{B27CAD80-1F60-11EA-9361-F55878484892}) Dec15,201912:31:16PM-requestingresourceMGW_FS_STG Dec15,201912:31:16PM-requestingresourceu0bpnbuma02.NBU_CLIENT.MAXJOBS.07r-malvern02 Dec15,201912:31:16PM-grantedresourceu0bpnbuma02.NBU_CLIENT.MAXJOBS.07r-malvern02 Dec15,201912:31:16PM-grantedresourceMediaID=@aaaas;DiskVolume=fs_lsu;DiskPool=mgw_fs_pool;Path=fs_lsu;StorageServer=s07dd002;MediaServer=w07pnbume02.myl.com Dec15,201912:31:16PM-grantedresourcew07pnbume07_MGW_FS_STU Dec15,201912:31:17PM-estimated33184826kbytesneeded Dec15,201912:31:17PM-Infonbjm(pid=90913)startedbackup(backupid=07r-malvern02_1576431077)jobforclient07r-malvern02,policyGOLD-FS-07R-LABPC-GRP1,scheduleWeeklyonstorageunitw07pnbume07_MGW_FS_STU Dec15,201912:31:18PM-startedprocessbpbrm(pid=3368) Dec15,201912:31:53PM-Infobpbrm(pid=3368)07r-malvern02isthehosttobackupdatafrom Dec15,201912:31:53PM-Infobpbrm(pid=3368)readingfilelistforclient Dec15,201912:32:01PM-connecting Dec15,201912:32:23PM-connected;connecttime:0:00:00 Dec15,201912:32:25PM-Infobpbrm(pid=3368)startingbpbkar32onclient Dec15,201912:32:57PM-Infobpbkar32(pid=6820)Backupstarted Dec15,201912:32:57PM-Infobpbkar32(pid=6820)changetimecomparison:<disabled> Dec15,201912:32:57PM-Infobpbkar32(pid=6820)archivebitprocessing:<enabled> Dec15,201912:32:57PM-Infobptm(pid=3108)start Dec15,201912:32:58PM-Infobptm(pid=3108)using262144databuffersize Dec15,201912:32:58PM-Infobptm(pid=3108)settingreceivenetworkbufferto1049600bytes Dec15,201912:32:58PM-Infobptm(pid=3108)using30databuffers Dec15,201912:33:00PM-beginwriting Dec15,201912:33:01PM-Infobptm(pid=3108)startbackup Dec15,201912:33:02PM-Infobptm(pid=3108)backupchildprocessispid8364.8424 Dec15,201912:33:02PM-Infobptm(pid=8364)start Dec15,201912:36:14PM-Infobpbkar32(pid=6820)notusingchangejournaldatafor<C:\>:notenabled Dec15,201910:10:19PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramFiles(x86)\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Bin\service.dat(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:19:05PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\BASH\ShdSettg.dat(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:19:06PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\BASH\ShdSettg.dat.log(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:19:08PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\BASH\SPSettg.dat(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:19:10PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\BASH\SPSettg.dat.log(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:22:05PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\CmnClnt\ccGEvt\Global\LM2.dat(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:22:07PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\CmnClnt\ccGLog\ccGenericLog.dat(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:22:09PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\CmnClnt\ccJobMgr\JobMgr.dat(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:22:10PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\CmnClnt\ccJobMgr\JobMgr.dat.log(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:22:12PM-Warningbpbrm(pid=3368)fromclient07r-malvern02:WRN-can'topenfile:C:\ProgramData\Symantec\SymantecEndpointProtection\12.1.5337.5000.105\Data\CmnClnt\ccSetMgr\44bb4a26-6c2a-48a8-a256-8ae3ee56f112.dat(WIN3232:Theprocesscannotaccessthefilebecauseitisbeingusedbyanotherprocess.) Dec15,201910:22:12PM-Infobpbrm(pid=3368)fromclient07r-malvern02:TRV-lastmessagebeingsuppressedafter10occurrences Dec16,201910:59:26AM-Criticalbptm(pid=3108)imagewritefailed:error2060046:pluginerror Dec16,201910:59:26AM-Criticalbptm(pid=3108)sts_get_image_propfailed:error2060046:pluginerror Dec16,201910:59:32AM-Errorbptm(pid=3108)cannotwriteimagetodisk,Invalidargument Dec16,201910:59:33AM-Infobptm(pid=3108)EXITINGwithstatus84<---------- Dec16,201911:00:03AM-endwriting;writetime:22:27:03 Dec16,201911:00:05AM-Infobpbkar32(pid=6820)done.status:84:mediawriteerror mediawriteerror (84)964Views0likes1Commentcan't connect to client
hello all i have the status 58 in our netbackup (job failed) and look this command when i was maked and how you can advice me to troubleshooting the issue >bptestbpcd.exe -client MPX-VM-NAVINT01 -verbose -debug 14:59:18.771 [12420.13224] <2> bptestbpcd: VERBOSE = 0 14:59:19.802 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:21.443 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:21.474 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:21.474 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2030] VN_REQUEST_SERVICE_SOCKET 6 0x6 14:59:21.474 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2044] service bpcd 14:59:21.599 [12420.13224] <2> logconnections: BPCD CONNECT FROM 10.0.100.20.62200 TO 10.0.112.250.13724 fd = 640 14:59:22.630 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:24.521 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:24.552 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:24.552 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2072] connect VNETD CONNECT FROM 10.0.100.20.62203 TO 10.0.112.250.13724 fd = 660 14:59:24.552 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:455] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 14:59:24.552 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:480] ipc_string 23279 14:59:24.599 [12420.13224] <2> ConnectToBPCD: bpcd_connect_and_verify(MPX-VM-NAVINT01, MPX-VM-NAVINT01) failed: 46 14:59:25.630 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:27.568 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:27.630 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:27.630 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2030] VN_REQUEST_SERVICE_SOCKET 6 0x6 14:59:27.630 [12420.13224] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2044] service bpcd 14:59:27.662 [12420.13224] <2> logconnections: BPCD CONNECT FROM 10.0.100.20.62207 TO 10.0.112.250.13724 fd = 640 14:59:28.693 [12420.13224] <8> async_connect: [vnet_connect.c:1709] getsockopt SO_ERROR returned 10061 0x274d 14:59:30.615 [12420.13224] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3508] VN_REQUEST_PBX_C_SUPPORTED 13 0xd 14:59:30.646 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2036] remote host supports PBX, but PBX is not running 0 0x0 14:59:30.646 [12420.13224] <8> do_vnetd_service: [vnet_connect.c:2072] connect VNETD CONNECT FROM 10.0.100.20.62211 TO 10.0.112.250.13724 fd = 660 14:59:30.646 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:455] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 14:59:30.646 [12420.13224] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:480] ipc_string 23291 14:59:30.693 [12420.13224] <2> local_bpcr_connect: got an exit status error message: <?xml version="1.0" encoding="utf-8"?><StatusMsgDoc><StatusMsg NBUStatus="46" Severity="2" VXULoid="137" VXULtid="114"><P pos="0">mpx-py-bkup02.snmvt.intra</P><P pos="1">10.0.100.20</P><P pos="2">MPX-VM-NAVINT01.snmvt.intra</P><P pos="3">10.0.112.250</P><MsgString>Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access.</MsgString><StatusMsg NBUStatus="46" Severity="0" VXULoid="137" VXULtid="115"><P pos="0">mpx-py-bkup02.snmvt.intra</P><P pos="1">10.0.100.20</P><P pos="2">mpx-vm-navint01.snmvt.intra</P><MsgString>Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra.</MsgString></StatusMsg></StatusMsg></StatusMsgDoc> 14:59:30.693 [12420.13224] <2> ConnectToBPCD: bpcd_connect_and_verify(MPX-VM-NAVINT01, MPX-VM-NAVINT01) failed: 46 <16>bptestbpcd main: Function ConnectToBPCD(MPX-VM-NAVINT01) failed: 46 14:59:30.709 [12420.13224] <16> bptestbpcd main: Function ConnectToBPCD(MPX-VM-NAVINT01) failed: 46 <16>bptestbpcd main: Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access. Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra. 14:59:30.740 [12420.13224] <16> bptestbpcd main: Request from host mpx-py-bkup02.snmvt.intra (10.0.100.20) to host MPX-VM-NAVINT01.snmvt.intra (10.0.112.250) is not allowed access. Host mpx-py-bkup02.snmvt.intra (10.0.100.20) is not an authorized server for host mpx-vm-navint01.snmvt.intra. <2>bptestbpcd: server not allowed access 14:59:30.771 [12420.13224] <2> bptestbpcd: server not allowed access <2>bptestbpcd: EXIT status = 46 14:59:30.771 [12420.13224] <2> bptestbpcd: EXIT status = 46 server not allowed access Iwassearchedmore in theVeritasweb can'tfixthis issue,please helpSolved4.5KViews0likes12Commentsclient process aborted (50)
Dear all 13 sept. 2019 19:23:35 - Info nbjm (pid=5140) starting backup job (jobid=121197) for client 10.0.100.212, policy Full_Backup, schedule Full 13 sept. 2019 19:23:35 - Info nbjm (pid=5140) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=121197, request id:{CAECE6C4-EE6C-4ABE-B894-25C8C9FEE25B}) 13 sept. 2019 19:23:35 - requesting resource sauv01py112-hcart-robot-tld-0 13 sept. 2019 19:23:35 - requesting resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.10.0.100.212 13 sept. 2019 19:23:35 - requesting resource sauv01py112.snmvt.intra.NBU_POLICY.MAXJOBS.Full_Backup 13 sept. 2019 19:23:35 - awaiting resource sauv01py112-hcart-robot-tld-0. No drives are available. client process aborted (50) please i need your answer about this troubleshooting is right or not ? * - This issue it can be caused by not enough time ( need to increase it ) * - I have one drive in our robot use for different VMs ,this later can causes the slow process of saving and to out of the board time. this result of client process aborted (need other drive to avoid of out of time range1.3KViews0likes2Commentsmedia manager - system error occurred (174)
1 sept. 2019 18:03:09 - Info nbjm (pid=5140) starting backup job (jobid=121048) for client 10.0.100.212, policy P_DB_SQL_NEW, schedule Full 11 sept. 2019 18:03:09 - Info nbjm (pid=5140) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=121048, request id:{6E79351E-7088-401E-BD20-5ADDC0E1A733}) 11 sept. 2019 18:03:09 - requesting resource sauv01py112-hcart-robot-tld-0 11 sept. 2019 18:03:09 - requesting resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.10.0.100.212 11 sept. 2019 18:03:09 - awaiting resource sauv01py112-hcart-robot-tld-0. No drives are available. 11 sept. 2019 18:04:43 - granted resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.10.0.100.212 11 sept. 2019 18:04:43 - granted resource 0009L4 11 sept. 2019 18:04:43 - granted resource IBM.ULT3580-TD4.001 11 sept. 2019 18:04:43 - granted resource sauv01py112-hcart-robot-tld-0 11 sept. 2019 18:04:44 - estimated 0 kbytes needed 11 sept. 2019 18:04:44 - Info nbjm (pid=5140) started backup (backupid=srv-nav2009.snmvt.intra_1568221483) job for client 10.0.100.212, policy P_DB_SQL_NEW, schedule Full on storage unit sauv01py112-hcart-robot-tld-0 11 sept. 2019 18:04:44 - started process bpbrm (pid=10608) 11 sept. 2019 18:04:46 - Info bpbrm (pid=10608) 10.0.100.212 is the host to backup data from 11 sept. 2019 18:04:46 - Info bpbrm (pid=10608) reading file list for client 11 sept. 2019 18:04:47 - connecting 11 sept. 2019 18:04:49 - Info bpbrm (pid=10608) listening for client connection 11 sept. 2019 18:04:56 - Info bpbrm (pid=10608) INF - Client read timeout = 3600 11 sept. 2019 18:04:56 - Info bpbrm (pid=10608) accepted connection from client 11 sept. 2019 18:04:56 - connected; connect time: 0:00:00 11 sept. 2019 18:04:57 - Info dbclient (pid=5160) Backup started 11 sept. 2019 18:04:57 - Info bptm (pid=7512) start 11 sept. 2019 18:04:57 - Info bptm (pid=7512) using 65536 data buffer size 11 sept. 2019 18:04:59 - Info bptm (pid=7512) setting receive network buffer to 263168 bytes 11 sept. 2019 18:04:59 - Info bptm (pid=7512) using 30 data buffers 11 sept. 2019 18:05:00 - Info bptm (pid=7512) start backup 11 sept. 2019 18:05:00 - Info bptm (pid=7512) backup child process is pid 11884.11268 11 sept. 2019 18:05:00 - Info bptm (pid=7512) Waiting for mount of media id 0009L4 (copy 1) on server sauv01py112.snmvt.intra. 11 sept. 2019 18:05:00 - Info bptm (pid=11884) start 11 sept. 2019 18:05:00 - mounting 0009L4 11 sept. 2019 18:05:49 - Info bptm (pid=7512) media id 0009L4 mounted on drive index 1, drivepath {3,0,0,0}, drivename IBM.ULT3580-TD4.001, copy 1 11 sept. 2019 18:05:49 - mounted 0009L4; mount time: 0:00:49 11 sept. 2019 18:05:50 - positioning 0009L4 to file 20 11 sept. 2019 18:06:41 - positioned 0009L4; position time: 0:00:51 11 sept. 2019 18:06:41 - begin writing 11 sept. 2019 18:06:42 - Info dbclient (pid=5160) dbclient(pid=5160) wrote first buffer(size=65536) 11 sept. 2019 18:20:37 - Info dbclient (pid=5160) done. status: 6 11 sept. 2019 18:20:42 - Critical bptm (pid=11884) attempted to write 7 gigabytes, 1971067252 bytes, it is not a multiple of 512 11 sept. 2019 18:20:42 - Info bptm (pid=7512) waited for full buffer 22703 times, delayed 47829 times 11 sept. 2019 18:21:50 - Info bptm (pid=7512) EXITING with status 174 <---------- 11 sept. 2019 18:21:54 - Info dbclient (pid=5160) done. status: 174: media manager - system error occurred 11 sept. 2019 18:21:54 - end writing; write time: 0:15:13 media manager - system error occurred (174) hello all so the troublesouting of this later is to change drive ?? are you agree?Solved1.6KViews0likes1Commentnetwork read failed (42)
10 sept. 2019 18:00:00 - Info nbjm (pid=5140) starting backup job (jobid=120962) for client MPX-VM-GLDINT01.snmvt.intra, policy P_SRVENTREPOT3, schedule Full 10 sept. 2019 18:00:00 - Info nbjm (pid=5140) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=120962, request id:{694EB4A6-9E45-45C8-967D-353C5C1490A4}) 10 sept. 2019 18:00:00 - requesting resource sauv01py112-hcart-robot-tld-0 10 sept. 2019 18:00:00 - requesting resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.MPX-VM-GLDINT01.snmvt.intra 10 sept. 2019 18:00:00 - requesting resource sauv01py112.snmvt.intra.NBU_POLICY.MAXJOBS.P_SRVENTREPOT3 10 sept. 2019 18:00:00 - awaiting resource sauv01py112-hcart-robot-tld-0. No drives are available. 11 sept. 2019 03:23:02 - granted resource sauv01py112.snmvt.intra.NBU_CLIENT.MAXJOBS.MPX-VM-GLDINT01.snmvt.intra 11 sept. 2019 03:23:02 - granted resource sauv01py112.snmvt.intra.NBU_POLICY.MAXJOBS.P_SRVENTREPOT3 11 sept. 2019 03:23:02 - granted resource 0028L4 11 sept. 2019 03:23:02 - granted resource IBM.ULT3580-TD4.001 11 sept. 2019 03:23:02 - granted resource sauv01py112-hcart-robot-tld-0 11 sept. 2019 03:23:02 - estimated 257627584 kbytes needed 11 sept. 2019 03:23:02 - begin Parent Job 11 sept. 2019 03:23:02 - begin Stream Discovery: Start Notify Script 11 sept. 2019 03:23:02 - Info RUNCMD (pid=10644) started 11 sept. 2019 03:23:03 - Info RUNCMD (pid=10644) exiting with status: 0 Operation Status: 0 11 sept. 2019 03:23:03 - end Stream Discovery: Start Notify Script; elapsed time 0:00:01 11 sept. 2019 03:23:03 - begin Stream Discovery: Stream Discovery 11 sept. 2019 03:23:04 - Info bpmount (pid=6140) started 11 sept. 2019 03:23:04 - Info bpmount (pid=6140) exiting with status: 0 Operation Status: 0 11 sept. 2019 03:23:05 - end Stream Discovery: Stream Discovery; elapsed time 0:00:02 11 sept. 2019 03:23:05 - begin Stream Discovery: Policy Execution Manager Preprocessed Operation Status: 42 11 sept. 2019 06:14:37 - end Stream Discovery: Policy Execution Manager Preprocessed; elapsed time 2:51:32 11 sept. 2019 06:14:37 - begin Stream Discovery: Stop On Error Operation Status: 0 11 sept. 2019 06:14:37 - end Stream Discovery: Stop On Error; elapsed time 0:00:00 11 sept. 2019 06:14:37 - begin Stream Discovery: End Notify Script 11 sept. 2019 06:14:37 - Info RUNCMD (pid=8280) started 11 sept. 2019 06:14:37 - Info RUNCMD (pid=8280) exiting with status: 0 Operation Status: 0 11 sept. 2019 06:14:37 - end Stream Discovery: End Notify Script; elapsed time 0:00:00 Operation Status: 42 11 sept. 2019 06:14:38 - end Parent Job; elapsed time 2:51:36 network read failed (42) is the missing connexion ? to troubleshoouting this problemSolved1.2KViews0likes1Commentthe backup failed to back up the requested files (6)
10 sept. 2019 18:02:32 - Info nbjm (pid=5140) starting backup job (jobid=120969) for client srv-recharge.snmvt.intra, policy P_DB_SQL_NEW, schedule Full 10 sept. 2019 18:02:32 - Info nbjm (pid=5140) requesting MEDIA_SERVER_ONLY resources from RB for backup job (jobid=120969, request id:{B7E95808-3460-449A-A532-EBF8F63D35FC}) 10 sept. 2019 18:02:32 - requesting resource sauv01py112-hcart-robot-tld-0 10 sept. 2019 18:02:32 - requesting resource sauv01py112.snmvt.intra.NBU_POLICY.MAXJOBS.P_DB_SQL_NEW 10 sept. 2019 18:02:32 - granted resource sauv01py112.snmvt.intra.NBU_POLICY.MAXJOBS.P_DB_SQL_NEW 10 sept. 2019 18:02:35 - estimated 0 kbytes needed 10 sept. 2019 18:02:35 - Info nbjm (pid=5140) started backup (backupid=srv-recharge.snmvt.intra_1568134955) job for client srv-recharge.snmvt.intra, policy P_DB_SQL_NEW, schedule Full on storage unit 10 sept. 2019 18:02:35 - started process bpbrm (pid=8652) 10 sept. 2019 18:02:37 - Info bpbrm (pid=8652) srv-recharge.snmvt.intra is the host to backup data from 10 sept. 2019 18:02:37 - Info bpbrm (pid=8652) reading file list for client 10 sept. 2019 18:02:39 - connecting 10 sept. 2019 18:02:42 - Info bpbrm (pid=8652) starting bphdb on client 10 sept. 2019 18:02:42 - connected; connect time: 0:00:00 10 sept. 2019 18:02:42 - Info bphdb (pid=1428) Backup started 10 sept. 2019 18:02:44 - Info dbclient (pid=612) INF - Intelligent policy initiated by server <sauv01py112.snmvt.intra> 10 sept. 2019 18:02:45 - Info dbclient (pid=612) INF - Intelligent policy <P_DB_SQL_NEW> is valid. The input file <C:\Program Files\Veritas\NetBackup\dbext\mssql\input.1428.0.0910119.180242> has been parsed successfully 10 sept. 2019 18:02:47 - Info dbclient (pid=612) INF - <RECHARGE> is a Failover Cluster Instance. Using virtual name <SRV-RECHARGE.snmvt.intra> 10 sept. 2019 18:02:47 - Info dbclient (pid=612) INF - Instance server name resolved to: <SRV-RECHARGE> 10 sept. 2019 18:02:49 - Info dbclient (pid=612) INF - Intelligent policy <P_DB_SQL_NEW> has resulted in <6> batch operation(s). 10 sept. 2019 18:02:50 - Info dbclient (pid=612) INF - Intelligent policy <P_DB_SQL_NEW>: <6> operation(s) will protect full databases. 10 sept. 2019 18:02:51 - Info dbclient (pid=612) INF - Intelligent policy preprocessing has finished, created temporary batch file <__18_02_48_408_00.bch>, and submitted it to the backend agent for processing 10 sept. 2019 18:02:54 - Info dbclient (pid=612) INF - BACKUP STARTED USING 10 sept. 2019 18:02:54 - Info dbclient (pid=612) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2789.0 (X64) 10 sept. 2019 18:02:54 - Info dbclient (pid=612) Sep 28 2011 17:10:21 10 sept. 2019 18:02:54 - Info dbclient (pid=612) Copyright (c) Microsoft Corporation 10 sept. 2019 18:02:54 - Info dbclient (pid=612) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 10 sept. 2019 18:02:54 - Info dbclient (pid=612) Batch = __18_02_48_408_00.bch, Op# = 1 10 sept. 2019 18:02:56 - Info dbclient (pid=612) INF - Using backup image SQL05PY100.MSSQL7.SRV-RECHARGE\RECHARGE.db.ProFidelity.~.7.001of001.20190910180253..C 10 sept. 2019 18:02:56 - Info dbclient (pid=612) INF - backup database "ProFidelity" to VIRTUAL_DEVICE='VNBU0-612-8960-1568134975' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 10 sept. 2019 18:02:58 - Info dbclient (pid=612) INF - Number of stripes: 1, Number of buffers per stripe 2. 10 sept. 2019 18:02:58 - Info dbclient (pid=612) INF - Setting backup catalog name to: srv-recharge.snmvt.intra 10 sept. 2019 18:03:02 - Info dbclient (pid=612) INF - Created VDI object for SQL Server instance <RECHARGE>. Connection timeout is <300> seconds. 10 sept. 2019 18:08:06 - Info dbclient (pid=612) ERR - Error in GetConfiguration: 0x80770003. 10 sept. 2019 18:08:07 - Info dbclient (pid=612) CONTINUATION: - The api was waiting and the timeout interval had elapsed. 10 sept. 2019 18:08:13 - Info dbclient (pid=612) INF - OPERATION #1 of batch __18_02_48_408_00.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 320(320) seconds. 10 sept. 2019 18:08:20 - Info dbclient (pid=612) INF - BACKUP STARTED USING 10 sept. 2019 18:08:20 - Info dbclient (pid=612) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2789.0 (X64) 10 sept. 2019 18:08:20 - Info dbclient (pid=612) Sep 28 2011 17:10:21 10 sept. 2019 18:08:20 - Info dbclient (pid=612) Copyright (c) Microsoft Corporation 10 sept. 2019 18:08:20 - Info dbclient (pid=612) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 10 sept. 2019 18:08:20 - Info dbclient (pid=612) Batch = __18_02_48_408_00.bch, Op# = 2 10 sept. 2019 18:08:21 - Info dbclient (pid=612) INF - Using backup image SQL05PY100.MSSQL7.SRV-RECHARGE\RECHARGE.db.TOP_UP_Test.~.7.001of001.20190910180818..C 10 sept. 2019 18:08:21 - Info dbclient (pid=612) INF - backup database "TOP_UP_Test" to VIRTUAL_DEVICE='VNBU0-612-2632-1568135300' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 10 sept. 2019 18:08:22 - Info dbclient (pid=612) INF - Number of stripes: 1, Number of buffers per stripe 2. 10 sept. 2019 18:08:22 - Info dbclient (pid=612) INF - Setting backup catalog name to: srv-recharge.snmvt.intra 10 sept. 2019 18:08:23 - Info dbclient (pid=612) INF - Created VDI object for SQL Server instance <RECHARGE>. Connection timeout is <300> seconds. 10 sept. 2019 18:13:24 - Info dbclient (pid=612) ERR - Error in GetConfiguration: 0x80770003. 10 sept. 2019 18:13:25 - Info dbclient (pid=612) CONTINUATION: - The api was waiting and the timeout interval had elapsed. 10 sept. 2019 18:13:31 - Info dbclient (pid=612) INF - OPERATION #2 of batch __18_02_48_408_00.bch FAILED with STATUS 1 (0 is normal). Elapsed time = 312(312) seconds. 10 sept. 2019 18:13:37 - Info dbclient (pid=612) INF - BACKUP STARTED USING 10 sept. 2019 18:13:37 - Info dbclient (pid=612) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2789.0 (X64) 10 sept. 2019 18:13:37 - Info dbclient (pid=612) Sep 28 2011 17:10:21 10 sept. 2019 18:13:37 - Info dbclient (pid=612) Copyright (c) Microsoft Corporation 10 sept. 2019 18:13:37 - Info dbclient (pid=612) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 10 sept. 2019 18:13:37 - Info dbclient (pid=612) Batch = __18_02_48_408_00.bch, Op# = 3 10 sept. 2019 18:13:38 - Info dbclient (pid=612) INF - Using backup image SQL05PY100.MSSQL7.SRV-RECHARGE\RECHARGE.db.master.~.7.001of001.20190910181335..C 10 sept. 2019 18:13:40 - Info dbclient (pid=612) INF - backup database "master" to VIRTUAL_DEVICE='VNBU0-612-4400-1568135618' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 10 sept. 2019 18:13:40 - Info dbclient (pid=612) INF - Setting backup catalog name to: srv-recharge.snmvt.intra 10 sept. 2019 18:13:40 - Info dbclient (pid=612) INF - Number of stripes: 1, Number of buffers per stripe 2. 10 sept. 2019 18:13:41 - Info dbclient (pid=612) INF - Created VDI object for SQL Server instance <RECHARGE>. Connection timeout is <300> seconds. 11 sept. 2019 02:30:28 - Info dbclient (pid=612) INF - Thread has been closed for stripe #0 11 sept. 2019 02:30:38 - Info dbclient (pid=612) INF - OPERATION #3 of batch __18_02_48_408_00.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 29822(1) seconds 11 sept. 2019 02:30:43 - Info dbclient (pid=612) INF - BACKUP STARTED USING 11 sept. 2019 02:30:43 - Info dbclient (pid=612) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2789.0 (X64) 11 sept. 2019 02:30:43 - Info dbclient (pid=612) Sep 28 2011 17:10:21 11 sept. 2019 02:30:43 - Info dbclient (pid=612) Copyright (c) Microsoft Corporation 11 sept. 2019 02:30:43 - Info dbclient (pid=612) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 11 sept. 2019 02:30:43 - Info dbclient (pid=612) Batch = __18_02_48_408_00.bch, Op# = 4 11 sept. 2019 02:30:44 - Info dbclient (pid=612) INF - Using backup image SQL05PY100.MSSQL7.SRV-RECHARGE\RECHARGE.db.model.~.7.001of001.20190911023042..C 11 sept. 2019 02:30:45 - Info dbclient (pid=612) INF - backup database "model" to VIRTUAL_DEVICE='VNBU0-612-1604-1568165444' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 11 sept. 2019 02:30:46 - Info dbclient (pid=612) INF - Number of stripes: 1, Number of buffers per stripe 2. 11 sept. 2019 02:30:46 - Info dbclient (pid=612) INF - Setting backup catalog name to: srv-recharge.snmvt.intra 11 sept. 2019 02:30:46 - Info dbclient (pid=612) INF - Created VDI object for SQL Server instance <RECHARGE>. Connection timeout is <300> seconds. 11 sept. 2019 02:43:39 - Info dbclient (pid=612) INF - Thread has been closed for stripe #0 11 sept. 2019 02:43:48 - Info dbclient (pid=612) INF - OPERATION #4 of batch __18_02_48_408_00.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 785(1) seconds 11 sept. 2019 02:43:54 - Info dbclient (pid=612) INF - BACKUP STARTED USING 11 sept. 2019 02:43:54 - Info dbclient (pid=612) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2789.0 (X64) 11 sept. 2019 02:43:54 - Info dbclient (pid=612) Sep 28 2011 17:10:21 11 sept. 2019 02:43:54 - Info dbclient (pid=612) Copyright (c) Microsoft Corporation 11 sept. 2019 02:43:54 - Info dbclient (pid=612) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 11 sept. 2019 02:43:54 - Info dbclient (pid=612) Batch = __18_02_48_408_00.bch, Op# = 5 11 sept. 2019 02:43:54 - Info dbclient (pid=612) INF - Using backup image SQL05PY100.MSSQL7.SRV-RECHARGE\RECHARGE.db.msdb.~.7.001of001.20190911024352..C 11 sept. 2019 02:43:55 - Info dbclient (pid=612) INF - backup database "msdb" to VIRTUAL_DEVICE='VNBU0-612-4200-1568166234' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 11 sept. 2019 02:43:56 - Info dbclient (pid=612) INF - Setting backup catalog name to: srv-recharge.snmvt.intra 11 sept. 2019 02:43:56 - Info dbclient (pid=612) INF - Number of stripes: 1, Number of buffers per stripe 2. 11 sept. 2019 02:43:57 - Info dbclient (pid=612) INF - Created VDI object for SQL Server instance <RECHARGE>. Connection timeout is <300> seconds. 11 sept. 2019 02:57:01 - Info dbclient (pid=612) INF - Thread has been closed for stripe #0 11 sept. 2019 02:57:12 - Info dbclient (pid=612) INF - OPERATION #5 of batch __18_02_48_408_00.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 799(2) seconds 11 sept. 2019 02:57:17 - Info dbclient (pid=612) INF - BACKUP STARTED USING 11 sept. 2019 02:57:17 - Info dbclient (pid=612) Microsoft SQL Server 2008 R2 (SP1) - 10.50.2789.0 (X64) 11 sept. 2019 02:57:17 - Info dbclient (pid=612) Sep 28 2011 17:10:21 11 sept. 2019 02:57:17 - Info dbclient (pid=612) Copyright (c) Microsoft Corporation 11 sept. 2019 02:57:17 - Info dbclient (pid=612) Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) 11 sept. 2019 02:57:17 - Info dbclient (pid=612) Batch = __18_02_48_408_00.bch, Op# = 6 11 sept. 2019 02:57:18 - Info dbclient (pid=612) INF - Using backup image SQL05PY100.MSSQL7.SRV-RECHARGE\RECHARGE.db.recharge.~.7.001of001.20190911025716..C 11 sept. 2019 02:57:19 - Info dbclient (pid=612) INF - backup database "recharge" to VIRTUAL_DEVICE='VNBU0-612-7308-1568167037' with stats = 10, blocksize = 65536, maxtransfersize = 4194304, buffercount = 2 11 sept. 2019 02:57:20 - Info dbclient (pid=612) INF - Setting backup catalog name to: srv-recharge.snmvt.intra 11 sept. 2019 02:57:20 - Info dbclient (pid=612) INF - Number of stripes: 1, Number of buffers per stripe 2. 11 sept. 2019 02:57:20 - Info dbclient (pid=612) INF - Created VDI object for SQL Server instance <RECHARGE>. Connection timeout is <300> seconds. 11 sept. 2019 03:10:21 - Info dbclient (pid=612) INF - Thread has been closed for stripe #0 11 sept. 2019 03:10:30 - Info dbclient (pid=612) INF - OPERATION #6 of batch __18_02_48_408_00.bch SUCCEEDED with STATUS 0 (0 is normal). Elapsed time = 794(2) seconds 11 sept. 2019 03:10:33 - Info dbclient (pid=612) INF - Results of executing <__18_02_48_408_00.bch>: 11 sept. 2019 03:10:33 - Info dbclient (pid=612) <4> operations succeeded. <2> operations failed. 11 sept. 2019 03:10:34 - Info dbclient (pid=612) INF - The following object(s) were not backed up successfully. 11 sept. 2019 03:10:34 - Info dbclient (pid=612) INF - ProFidelity 11 sept. 2019 03:10:35 - Info dbclient (pid=612) INF - TOP_UP_Test 11 sept. 2019 03:10:56 - Error bpbrm (pid=8652) from client srv-recharge.snmvt.intra: ERR - exit status: <1> 11 sept. 2019 03:10:56 - Error bpbrm (pid=8652) from client srv-recharge.snmvt.intra: ERR - bphdb exit status = 6: the backup failed to back up the requested files 11 sept. 2019 03:10:59 - Info bphdb (pid=1428) done. status: 6: the backup failed to back up the requested files 11 sept. 2019 03:10:59 - end writing the backup failed to back up the requested files (6)Solved1.9KViews0likes2Comments