Netbackup and Vmware compatibility matrix
HI All, We recently upgraded to Vmware Esxi 6.5 for our hosts which host a bunch of VM's that I backup. Before that we were on Esxi 5.5. Prior to the upgrade the vm backup was running without any issues, however post upgrade none of them seem to be working and fail with the message "error opening snapshot disks using given transport mode status 23". I have tried using different transport modes but no luck. Updated the host file entries on my master server to point to the correct Esxi host, still no luck. What I wanted to check was before going any further is that ... Is Netbaclup version 7.6 compatible with backing up virtiual machines on host with the version of 6.5? I know this version of netbackup is really old and end of support life, but I wanted to know if there some kind of matrix from Veritas which says .. using this version of netbackup (7.6).. you wont be able to backup vm's on Esxi version 6.5... PS: Yes, i know we need to upgarde our NBU version! -ASolved10KViews0likes3CommentsCatalog Fail get status 2520
Hello, We have the problem of catalog, which at the beginning fails me with error 2520. At the moment I have not made any resolution. Job detail: 07/02/2017 14:10:04 - Info nbjm (pid=53420) starting backup job (jobid=1048379) for client g300603cl005, policy CSD_BR_NBU_CAT, schedule Diario_Full 07/02/2017 14:10:04 - Info nbjm (pid=53420) requesting CATALOG_BACKUP_RESOURCE resources from RB for backup job (jobid=1048379, request id:{CF79AD2E-2679-4DE9-9BC0-2F3BD95FEDB0}) 07/02/2017 14:10:04 - requesting resource g300603cl005.NBU_CATALOG.MAXJOBS 07/02/2017 14:10:05 - granted resource g300603cl005.NBU_CATALOG.MAXJOBS 07/02/2017 14:10:05 - estimated 0 kbytes needed 07/02/2017 14:10:05 - begin Parent Job 07/02/2017 14:10:05 - begin Catalog Backup: Start Notify Script 07/02/2017 14:10:05 - Info RUNCMD (pid=21672) started 07/02/2017 14:10:05 - Info RUNCMD (pid=21672) exiting with status: 0 Operation Status: 0 07/02/2017 14:10:05 - end Catalog Backup: Start Notify Script; elapsed time 0:00:00 07/02/2017 14:10:05 - begin Catalog Backup: Database Manager Query Operation Status: 2520 07/02/2017 14:10:06 - end Catalog Backup: Database Manager Query; elapsed time 0:00:01 07/02/2017 14:10:06 - begin Catalog Backup: Stop On Error Operation Status: 0 07/02/2017 14:10:06 - end Catalog Backup: Stop On Error; elapsed time 0:00:00 07/02/2017 14:10:06 - begin Catalog Backup: End Notify Script 07/02/2017 14:10:06 - Info RUNCMD (pid=14736) started 07/02/2017 14:10:06 - Info RUNCMD (pid=14736) exiting with status: 0 Operation Status: 0 07/02/2017 14:10:06 - end Catalog Backup: End Notify Script; elapsed time 0:00:00 Operation Status: 2520 07/02/2017 14:10:06 - end Parent Job; elapsed time 0:00:01 Failed to get status code information (2520) Can you helpme about solution? Enviroment: Windows 2008, NBU 7.6.1. Regards.Solved9.9KViews0likes26CommentsError E000E020 on Backup Exec 2014.
Hello all, I would like to make a question regarding error E000E020, the error message I've been having in a remote site is: "e000e020 - The duration that this job is allowed to remain scheduled has passed. It will be rescheduled. Verify that storage is available and check the job's schedule settings. Ensure that there is enough time for it to begin running before it is considered missed." I've already checked the following article, and I think I can discard options A and C, as I don't think the options for option A is on Backup Exec 2014 (or maybe I am not finding them properly) and C we didn't have a time change here (therefor, there was no time change). So checking option B and normally we run the jobs as the following: Backup to Disk and then Duplicate to Tape. The disk we use for backup has a lot of free space left, as for the tape I wouldn't be surprised if it is not being change daily as it is a remote site where we don't have a lot of control (but then the error would only be on the duplicate job, not on the 1st backup). However the issue happens on the Backup job, where though I will attach some screenshots to see if it helps, I find odd the Job is set to start 9:00:00 PM, so it sometimes starts at 9:00:07 and it has end date of 9:00:04 (!?).Solved6.9KViews0likes3CommentsFailed to delete disk pool dp_disk_xxxdd1
Hi All; My NBU: master is running on window 2008 R2 nbu 7.7.2, meia server is netbackup appliance 5230. I am going to decom that netbackup appliance. I removed all SLP & STU related to that appliance but I am not able to remove diskpool. I got error message " Failed to delete disk pool dp_disk_xxxdd1: unable to process request because the server resources are busy (134) . Diskpool cannot be deleted because it contains volumes referenced by an SLP replication target (xxx_to_xxx_DD1_60_days) (MM Status 134). I ran nbstlutil list -lifecycle xxx_to_xxx_DD1_60_days -U but it doesn't show anything D:\Program Files\Veritas\NetBackup\bin\admincmd>nbstlutil list -lifecycle xxx_to_xxx_60_days -U No images or lifecycles matching criteria found. Anyone knows how to fix that ? Thank you. TomSolved6.4KViews0likes2CommentsInvalid Physical Volume Library Media Identifier
Hello, I have W2008R2, BEX 2012 doing duplicate backup to tapes at the end of each month. I tried to do a restore from these backupsets (Dec, Nov, Oct, Sept) and got the "0xe0008105Invalid Physical Volume Library Media Identifier" error for the failed job. Aug works. All of these(Dec, Nov, Oct, Sept) duplicate backup jobs completed without error messages. For each of these sets I tried an inventory and catalog where they scan the first tape in the set, prompt for the second, and then also fail with the same error message. I went back to my Aug backup set of tapes and I am able to do a restore from that set. Also, I can restore from all the tape backup sets if the data exists on the first tape only. Please advise. ThanksSolved5.2KViews0likes4CommentsBackup failing with error code 23
Hi Team, One windows client backup is getting failed with error code 23 from today. Below is the bptestbpcd output from master. Tried adding master server hostname and IP on client machine and client hostname and IP on master server. E:\Veritas\NetBackup\bin>bptestbpcd -client mispw3206 -debug 07:33:44.377 [3424.18492] <2> bptestbpcd: VERBOSE = 0 07:33:44.393 [3424.18492] <2> read_client: dname=., offline=0, online_at=0 offli ne_at=0 offlineres=0 onlineres_at=0 offlineres_at=0 07:33:44.393 [3424.18492] <2> read_client: dname=.., offline=0, online_at=0 offl ine_at=0 offlineres=0 onlineres_at=0 offlineres_at=0 07:33:44.393 [3424.18492] <2> read_client: dname=COA_0, offline=0, online_at=0 o ffline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0 07:33:44.393 [3424.18492] <2> read_client: dname=CO_0, offline=0, online_at=0 of fline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0 07:33:44.393 [3424.18492] <2> read_client: dname=host_info, offline=0, online_at =0 offline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0 07:33:44.393 [3424.18492] <2> read_client: dname=OAA_0, offline=0, online_at=0 o ffline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0 07:33:44.393 [3424.18492] <2> read_client: dname=OA_0, offline=0, online_at=0 of fline_at=0 offlineres=0 onlineres_at=0 offlineres_at=0 07:33:44.393 [3424.18492] <2> check_vnetd_process_dup_permission: OpenProcessTok en() failed: 5 07:33:44.393 [3424.18492] <2> vnet_check_windows_privileges: enabled SeDebugPriv ilege privilege 07:33:44.424 [3424.18492] <2> vnet_pbxConnect_ex: pbxConnectExEx() failed: 10054 07:33:44.424 [3424.18492] <2> vnet_pbxConnect_ex: ../../libvlibs/vnet_pbx.c.691: pbxSetAddrEx/pbxConnectExEx return error 10054:An existing connection was forci bly closed by the remote host. 07:33:44.424 [3424.18492] <8> do_pbx_service: [vnet_connect.c:2491] vnet_pbxConn ect() failed, status=18, errno=0, use_vnetd=0, cr->vcr_service=bpcd 07:33:44.424 [3424.18492] <8> vnet_get_peer_sock_names: [vnet_nbrntd.c:829] gets ockname() failed 10038 0x2736 07:33:44.424 [3424.18492] <2> vnet_proxy_get_logs: vnet_get_peer_sock_names(628) returned 10 10038 07:33:44.424 [3424.18492] <8> async_connect: [vnet_connect.c:2058] do_service fa iled 18 0x12 07:33:44.486 [3424.18492] <8> vnet_vnetd_pbx_c_supported: [vnet_vnetd.c:3531] VN _REQUEST_PBX_C_SUPPORTED 13 0xd 07:33:44.970 [3424.18492] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2053] VN_ REQUEST_SERVICE_SOCKET 6 0x6 07:33:44.970 [3424.18492] <8> vnet_vnetd_service_socket: [vnet_vnetd.c:2067] ser vice bpcd 07:33:45.188 [3424.18492] <2> logconnections: BPCD CONNECT FROM 10.128.44.226.59 719 TO 10.128.74.45.13724 fd = 628 07:33:45.188 [3424.18492] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 00000000 027E1C70 07:33:45.204 [3424.18492] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded 07:33:45.298 [3424.18492] <8> do_pbx_service: [vnet_connect.c:2581] via PBX VNET D CONNECT FROM 10.128.44.226.59721 TO 10.128.74.45.1556 fd = 652 07:33:45.298 [3424.18492] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vne td.c:458] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 07:33:45.547 [3424.18492] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vne td.c:483] ipc_string 65216 07:33:45.984 [3424.18492] <2> get_short_base: (1) cannot read (byte 1) from netw ork: An existing connection was forcibly closed by the remote host. 07:33:45.984 [3424.18492] <2> bpcr_put_vnetd_forward_socket: get_short failed: 1 0054 07:33:45.984 [3424.18492] <2> local_bpcr_connect: bpcr_put_vnetd_forward_socket failed: 23 07:33:45.984 [3424.18492] <2> ConnectToBPCD: bpcd_connect_and_verify(mispw3206, mispw3206) failed: 23 07:33:45.984 [3424.18492] <16> bptestbpcd main: JSON proxy message = {"allow_lar ge_status": {"timestamp": 1530099225, "who": "vnet_tss_init", "line_number": 32, "comment": "allow vnet status > 255", "data": true}, "direct_connect": {"timest amp": 1530099225, "who": "connect_to_service", "line_number": 834, "comment": "c onnect parameters", "data": {"who": "vnet_connect_to_vnetd_bpcd", "host": "mispw 3206", "service": "vnetd", "override_required_interface": null, "extra_tries_on_ connect": 0, "getsock_disable_to": 0, "overide_connect_timeout": 0, "connect_opt ions": null}}, "proxy_request": {"timestamp": 1530099225, "who": "vnet_proxy_bui ld_request", "line_number": 3300, "comment": "request to local proxy", "data": { "bpcd_info": {"remote_client": "mispw3206", "remote_host": "mispw3206", "remote_ probably_dhcp": false, "proxy_flag": 32, "proxy_flag_hex": "0x00000020", "cmd_so ck": 628}, "i_am_daemon": false, "domain_constraints": {}, "service": "vnetd", " auth_only": false, "pid": 3424, "ssa": false, "local_user": "v565751@CORP", "hos t": "mispw3206", "peer_host": "mispw3206", "isTestConnection": true, "peer_clien t": "mispw3206", "local_client": "to1pw3243.corp.statestr.com", "local_dhcp_inte rval": 0, "peer_dhcp_info": null, "local_hostname": "to1pw3243.corp.statestr.com ", "secure_peer": false, "resilient": false, "nbrntd_peer_addr": null, "nbrntd_s ock_addr": null, "hand_back": false, "request_timeout": 1810}}, "proxy_response" : {"timestamp": 1530099225, "who": "vnet_proxy_parse_response", "line_number": 3 472, "comment": "response from local proxy", "data": {"status": 0, "local_proxy_ info": {}, "domain_constraints_set": {"process_hint": "882e988d-3244-48e9-bb12-8 b43b6f0dac7", "process_hint_reason": "there was no inherited hint, the connected peer was not a master server, so defaulted to primary master", "process_hint_se rver_name": "to1pw3243.corp.statestr.com"}, "statusmsgxml": "<?xml version=\"1.0 \" encoding=\"utf-8\"?><StatusMsgDoc><StatusMsg NBUStatus=\"0\" Severity=\"0\">< /StatusMsg></StatusMsgDoc>"}}, "status": {"timestamp": 1530099225, "who": "conne ct_to_service", "line_number": 981, "comment": "vnet status", "data": 0}} <16>bptestbpcd main: Function ConnectToBPCD(mispw3206) failed: 23 07:33:45.984 [3424.18492] <16> bptestbpcd main: Function ConnectToBPCD(mispw3206 ) failed: 23 <16>bptestbpcd main: socket read failed 07:33:46.000 [3424.18492] <16> bptestbpcd main: socket read failed <2>bptestbpcd: socket read failed 07:33:46.015 [3424.18492] <2> bptestbpcd: socket read failed <2>bptestbpcd: EXIT status = 23 07:33:46.015 [3424.18492] <2> bptestbpcd: EXIT status = 23 socket read failed4.8KViews0likes15CommentsError bpbrm (pid=1264) no worklist items returned from bpresolver on client
Dear Frnds I am having an issue with my exchange backup policy, Each time when the backup started it got failed. Logs are attached. Please help me as my veritas support is expired, therefore, I am unable to take support from them. Your help will be highly appreciated. Nebackup version: 8.1 Plateform: Windows Server 2008 Regards Zuhaib Siddiqui3.8KViews0likes14Commentsdedicated interfaces for duplication in netbackup
Hi experts, I want to configure a separate interfaces for duplication on media servers. My query is : is it possible to send duplication data over dedicated interfaces to Target media servers? If yes, how I can configure in netbackup console? Please suggest. Any thought or opinion will be highly appreciated. Thanks DpxSolved3.8KViews0likes11CommentsSystem error occured (130)
Hi guys, i am receiving 130 error in exchange backups. i have no clue ho eto trouble shoot this. Please help. i am posting detailed job status. i cheked vssadmin list writers in MBX04 client machine . all are stable. details status: Feb 22, 2018 12:50:27 AM - Info nbjm (pid=12744) starting backup job (jobid=666154) for client EVM-EMXMBX004, policy CEC_EVM-EMXMBX004, schedule Full Feb 22, 2018 12:50:27 AM - Info nbjm (pid=12744) requesting STANDARD_RESOURCE resources from RB for backup job (jobid=666154, request id:{0AD38C09-D750-4F7A-A7BB-6F38FF4CDD1F}) Feb 22, 2018 12:50:27 AM - requesting resource LTO5_Media_Manager Feb 22, 2018 12:50:27 AM - requesting resource edc-bkp01.NBU_CLIENT.MAXJOBS.EVM-EMXMBX004 Feb 22, 2018 12:50:27 AM - requesting resource edc-bkp01.NBU_POLICY.MAXJOBS.CEC_EVM-EMXMBX004 Feb 22, 2018 12:50:27 AM - granted resource edc-bkp01.NBU_CLIENT.MAXJOBS.EVM-EMXMBX004 Feb 22, 2018 12:50:27 AM - granted resource edc-bkp01.NBU_POLICY.MAXJOBS.CEC_EVM-EMXMBX004 Feb 22, 2018 12:50:27 AM - granted resource 000591 Feb 22, 2018 12:50:27 AM - granted resource HP.ULTRIUM5-SCSI.001 Feb 22, 2018 12:50:27 AM - granted resource edc-bkp01-hcart-robot-tld-0 Feb 22, 2018 12:50:27 AM - estimated 720458272 kbytes needed Feb 22, 2018 12:50:27 AM - begin Parent Job Operation Status: 0 Feb 22, 2018 12:50:27 AM - end Parent Job; elapsed time 0:00:00 Operation Status: 0 Feb 22, 2018 12:50:27 AM - started process bpbrm (pid=8800) Feb 22, 2018 12:50:34 AM - Info bpbrm (pid=8800) EVM-EMXMBX004 is the host to backup data from Feb 22, 2018 12:50:34 AM - Info bpbrm (pid=8800) reading file list for client Feb 22, 2018 12:50:35 AM - Info bpbrm (pid=8800) start bpfis on client Feb 22, 2018 12:50:35 AM - Info bpbrm (pid=8800) Starting create snapshot processing Feb 22, 2018 12:50:37 AM - Info bpfis (pid=15120) Backup started Feb 22, 2018 12:50:50 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:50 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:50 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:50 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:50 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:51 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:51 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:51 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:51 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:51 AM - Info bpbrm (pid=8800) DB_BACKUP_STATUS is 103 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Critical bpbrm (pid=8800) from client EVM-EMXMBX004: FTL - snapshot preparation failed - Error attempting to find volumes to snap., status 130 Feb 22, 2018 12:50:51 AM - Info bpfis (pid=15120) done. status: 130 Feb 22, 2018 12:50:51 AM - Info bpfis (pid=15120) done. status: 130: system error occurred Feb 22, 2018 12:50:51 AM - end writing Operation Status: 130 Operation Status: 0 Feb 22, 2018 12:50:51 AM - started process bpbrm (pid=6700) Feb 22, 2018 12:50:58 AM - Info bpbrm (pid=6700) Starting delete snapshot processing Feb 22, 2018 12:51:03 AM - Info bpfis (pid=32980) Backup started Feb 22, 2018 12:51:03 AM - Critical bpbrm (pid=6700) from client EVM-EMXMBX004: cannot open C:\Program Files\Veritas\NetBackup\online_util\fi_cntl\bpfis.fim.cecdag.cec.root.careered.com_1519282227.1.0 Feb 22, 2018 12:51:04 AM - Info bpfis (pid=32980) done. status: 4207 Feb 22, 2018 12:51:04 AM - Info bpfis (pid=32980) done. status: 4207: Could not fetch snapshot metadata or state files Feb 22, 2018 12:51:04 AM - end writing Operation Status: 4207 Operation Status: 130 system error occurred (130)3.4KViews0likes10CommentsNet Backup License
Need some help. I have a client who is keeping the NBU in his environment just for the restore purpose of long term retention. He has just 1 master server running on 7.6.0.4. Recently there are some vulnerabilities detected by security teamhttps://www.veritas.com/content/support/en_US/security/VTS17-003.html#Issue1. I checked and these are getting resolved in 7.7.2 /7.7.3 with EEB or in version 8. We don't have the contract withVeritas anymore as we are just keeping that server for restore purposes. Can Veritas help us to provide the upgrade package and we can use the same license ? Please help with your valuable inputs.Solved3.3KViews0likes7Comments