Generate detail report in netbackup 8.1 or using opscenter
Hi, I would like to generate a detail report ..for example data everyday we are backing up in yearly,monthly,daily along with the number of clients which actively backed up by netbackup Looked into the opscenter..but the information is confusing791Views0likes1CommentDuplications failed with code 191 - NetBackup 8.1
Dear contributors, Hoping that you are well, I write this post because I have a problem with Duplications, I am new to this NetBackup world, so maybe it is a simple mistake. Unfortunately all Duplications have begun to fail .. I need help. - NetBackup 5230 - Appliance ver. 3.1 - NetBackup ver. 8.1 LOG: _____________________________________________________________________ Jan 30, 2020 2:09:12 PM - requesting resource LCM_CLESCNBU20010-hcart-robot-tld-1 Jan 30, 2020 2:09:12 PM - Info nbrb (pid=281640) Limit has been reached for the logical resource LCM_CLESCNBU20010-hcart-robot-tld-1 Jan 30, 2020 2:58:55 PM - granted resource LCM_CLESCNBU20010-hcart-robot-tld-1 Jan 30, 2020 2:58:55 PM - started process RUNCMD (pid=304107) Jan 30, 2020 2:58:56 PM - begin Duplicate Jan 30, 2020 2:58:56 PM - requesting resource CLESCNBU20010-hcart-robot-tld-1 Jan 30, 2020 2:58:56 PM - requesting resource @aaaab Jan 30, 2020 2:58:56 PM - reserving resource @aaaab Jan 30, 2020 2:58:56 PM - awaiting resource CLESCNBU20010-hcart-robot-tld-1. No drives are available. Jan 30, 2020 2:58:56 PM - ended process 0 (pid=304107) Jan 30, 2020 2:59:25 PM - awaiting resource CLESCNBU20010-hcart-robot-tld-1. Waiting for resources. Reason: Drives are in use, Media server: CLESCNBU20010.dys.corp, Robot Type(Number): TLD(1), Media ID: N/A, Drive Name: N/A, Volume Pool: Pool_Semanal, Storage Unit: CLESCNBU20010-hcart-robot-tld-1, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Jan 30, 2020 2:59:26 PM - awaiting resource CLESCNBU20010-hcart-robot-tld-1. No drives are available. Jan 30, 2020 3:15:21 PM - awaiting resource CLESCNBU20010-hcart-robot-tld-1. Waiting for resources. Reason: Drives are in use, Media server: CLESCNBU20010.dys.corp, Robot Type(Number): TLD(1), Media ID: N/A, Drive Name: N/A, Volume Pool: Pool_Semanal, Storage Unit: CLESCNBU20010-hcart-robot-tld-1, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Jan 30, 2020 3:15:23 PM - awaiting resource CLESCNBU20010-hcart-robot-tld-1. No drives are available. Jan 30, 2020 3:15:39 PM - awaiting resource CLESCNBU20010-hcart-robot-tld-1. Waiting for resources. Reason: Drives are in use, Media server: CLESCNBU20010.dys.corp, Robot Type(Number): TLD(1), Media ID: N/A, Drive Name: N/A, Volume Pool: Pool_Semanal, Storage Unit: CLESCNBU20010-hcart-robot-tld-1, Drive Scan Host: N/A, Disk Pool: N/A, Disk Volume: N/A Jan 30, 2020 3:15:39 PM - awaiting resource CLESCNBU20010-hcart-robot-tld-1. No drives are available. Jan 30, 2020 3:26:28 PM - resource @aaaab reserved Jan 30, 2020 3:26:28 PM - granted resource WC0179 Jan 30, 2020 3:26:28 PM - granted resource HP.ULTRIUM7-SCSI.001 Jan 30, 2020 3:26:28 PM - granted resource CLESCNBU20010-hcart-robot-tld-1 Jan 30, 2020 3:26:28 PM - granted resource MediaID=@aaaab;DiskVolume=PureDiskVolume;DiskPool=dp_disk_CLESCNBU20010;Path=PureDiskVolume;StorageServer=CLESCNBU20010.dys.corp;MediaServer=CLESCNBU20010.dys.corp Jan 30, 2020 3:26:29 PM - Info bpduplicate (pid=304107) window close behavior: Suspend Jan 30, 2020 3:26:29 PM - Info bptm (pid=314191) start Jan 30, 2020 3:26:29 PM - started process bptm (pid=314191) Jan 30, 2020 3:26:30 PM - Info bptm (pid=314191) start backup Jan 30, 2020 3:26:30 PM - Info bpdm (pid=314250) started Jan 30, 2020 3:26:30 PM - started process bpdm (pid=314250) Jan 30, 2020 3:26:30 PM - Info bpdm (pid=314250) reading backup image Jan 30, 2020 3:26:30 PM - Info bpdm (pid=314250) using 30 data buffers Jan 30, 2020 3:26:30 PM - Info bpdm (pid=314250) requesting nbjm for media Jan 30, 2020 3:26:30 PM - Info bptm (pid=314191) media id WC0179 mounted on drive index 1, drivepath /dev/nst0, drivename HP.ULTRIUM7-SCSI.001, copy 2 Jan 30, 2020 3:26:30 PM - Info bptm (pid=314191) INF - Waiting for positioning of media id WC0179 on server CLESCNBU20010.dys.corp for writing. Jan 30, 2020 3:26:32 PM - begin reading Jan 30, 2020 3:38:11 PM - end reading; read time: 0:11:39 Jan 30, 2020 3:38:11 PM - begin reading Jan 30, 2020 3:49:03 PM - end reading; read time: 0:10:52 Jan 30, 2020 3:49:03 PM - begin reading Jan 30, 2020 3:59:49 PM - end reading; read time: 0:10:46 Jan 30, 2020 3:59:49 PM - begin reading Jan 30, 2020 4:11:49 PM - end reading; read time: 0:12:00 Jan 30, 2020 4:11:49 PM - begin reading Jan 30, 2020 4:22:58 PM - end reading; read time: 0:11:09 Jan 30, 2020 4:22:58 PM - begin reading Jan 30, 2020 4:36:42 PM - end reading; read time: 0:13:44 Jan 30, 2020 4:36:42 PM - begin reading Jan 30, 2020 4:46:01 PM - end reading; read time: 0:09:19 Jan 30, 2020 4:46:01 PM - begin reading Jan 30, 2020 4:56:42 PM - end reading; read time: 0:10:41 Jan 30, 2020 4:56:42 PM - begin reading Jan 30, 2020 5:06:46 PM - end reading; read time: 0:10:04 Jan 30, 2020 5:06:46 PM - begin reading Jan 30, 2020 5:06:46 PM - Critical bpdm (pid=314250) Storage Server Error: (Storage server: PureDisk:CLESCNBU20010.dys.corp) PdvfsRead: Failed to read from spoold (Connection reset by peer). Ensure storage server services are running and operational. V-454-19 Jan 30, 2020 5:06:46 PM - Critical bpdm (pid=314250) sts_read_image failed: error 2060019 error occurred on network socket Jan 30, 2020 5:06:46 PM - Critical bpdm (pid=314250) image read failed: error 2060019: error occurred on network socket Jan 30, 2020 5:06:46 PM - Error bpdm (pid=314250) cannot read image from disk, Invalid argument Jan 30, 2020 5:06:48 PM - Error bptm (pid=314191) media manager terminated by parent process Jan 30, 2020 5:06:51 PM - Info CLESCNBU20010.dys.corp (pid=314250) StorageServer=PureDisk:CLESCNBU20010.dys.corp; Report=PDDO Stats for (CLESCNBU20010.dys.corp): read: 460800078 KB, CR received: 342190618 KB, CR received over FC: 0 KB, dedup: 0.0% Jan 30, 2020 5:07:19 PM - Error bpduplicate (pid=304107) host CLESCNBU20010.dys.corp backup id dysf-ex10mbx1.dys.corp_1580004201 read failed, media read error (85). Jan 30, 2020 5:07:19 PM - Error bpduplicate (pid=304107) host CLESCNBU20010.dys.corp backupid dysf-ex10mbx1.dys.corp_1580004201 write failed, media manager killed by signal (82). Jan 30, 2020 5:07:20 PM - Error bpduplicate (pid=304107) Duplicate of backupid dysf-ex10mbx1.dys.corp_1580004201 failed, media manager killed by signal (82). Jan 30, 2020 5:07:20 PM - Error bpduplicate (pid=304107) Status = no images were successfully processed. Jan 30, 2020 5:07:20 PM - end Duplicate; elapsed time 2:08:24 no images were successfully processed (191) _____________________________________________________________________ Please indicate if you need any more details.1.2KViews0likes2CommentsNBU Licensing doubt
Hi there, The principal site administrator with NBU 8.1 send us tape drives periodically and I need to restore those backups in a remote office with a differente console. These backup contain snapshots of VMware, SQL and Oracle. What is the minimum licensing I need on this remote office? Due to a only restore proven scenario (no backups)... Its ok a Netbackup Server and Library Based Tape Drive license only? Do I need agents for restore? What other considerations do I need to know to make it work? Thanks a lot!1.4KViews0likes4CommentsStatus 47
*** Moved to new post from: https://vox.veritas.com/t5/NetBackup/Backups-failling-with-Error-Code-47/m-p/675211 *** We have Same issue. Please find the below Output for the command : Bptestbpcd -client 10.140.132.48 -verbose -debug ---------------------------------------- acslclbckp004p:/usr/openv/netbackup/bin # bptestbpcd -client 10.140.132.48 -verbose -debug 13:27:00.534 [317391] <2> bptestbpcd: VERBOSE = 1 13:27:00.538 [317391] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded 13:27:00.622 [317391] <2> logconnections: BPCD CONNECT FROM 10.140.4.15.40467 TO 10.140.132.48.1556 fd = 3 13:27:00.622 [317391] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 0x2694820 13:27:00.624 [317391] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded 13:27:00.632 [317391] <8> do_pbx_service: [vnet_connect.c:2579] via PBX VNETD CONNECT FROM 10.140.4.15.42784 TO 10.140.132.48.1556 fd = 4 13:27:00.633 [317391] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:458] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 13:27:00.666 [317391] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:483] ipc_string /usr/openv/var/tmp/vnet-00517533760020670328000002570-fkUmFA 13:27:00.747 [317391] <2> bpcr_get_version_rqst: bpcd version: 08000000 1 1 1 10.140.4.15:40467 -> 10.140.132.48:1556 10.140.4.15:42784 -> 10.140.132.48:1556 13:27:00.749 [317391] <2> bpcr_get_version_rqst: bpcd version: 08000000 13:27:00.749 [317391] <16> bpcr_get_domain_ctx_rqst: connected bpcd version 0x08000000 is less than required version 0x08100000 13:27:00.749 [317391] <2> bpcr_get_peername_rqst: Server peername length = 29 13:27:00.750 [317391] <2> bpcr_get_hostname_rqst: Server hostname length = 14 13:27:00.750 [317391] <2> bpcr_get_clientname_rqst: Server clientname length = 14 13:27:00.750 [317391] <2> bpcr_get_version_rqst: bpcd version: 08000000 13:27:00.751 [317391] <2> bpcr_get_platform_rqst: Server platform length = 17 13:27:00.751 [317391] <2> bpcr_get_version_rqst: bpcd version: 08000000 13:27:00.751 [317391] <2> bpcr_patch_version_rqst: theRest == > < 13:27:00.752 [317391] <2> bpcr_get_version_rqst: bpcd version: 08000000 13:27:00.792 [317391] <2> bpcr_patch_version_rqst: theRest == > < 13:27:00.792 [317391] <2> bpcr_get_version_rqst: bpcd version: 08000000 PEER_NAME = acslclbckp004p.ncnu.goaaa.com HOST_NAME = acslclorap001v CLIENT_NAME = acslclorap001v VERSION = 0x08000000 PLATFORM = linuxR_x86_2.6.18 PATCH_VERSION = 8.0.0.0 SERVER_PATCH_VERSION = -1.-1.-1.-1 MASTER_SERVER = ACSLCLBCKP003V.NCNU.GOAAA.COM EMM_SERVER = ACSLCLBCKP003V.NCNU.GOAAA.COM NB_MACHINE_TYPE = CLIENT SERVICE_TYPE = UNKNOWN PROCESS_HINT = 13:27:00.800 [317391] <2> vnet_connect_to_vnetd_bpcd: js_bpcd_info: 0x2694300 13:27:00.801 [317391] <2> vnet_pbxConnect_ex: pbxConnectExEx Succeeded 13:27:00.809 [317391] <8> do_pbx_service: [vnet_connect.c:2579] via PBX VNETD CONNECT FROM 10.140.4.15.38157 TO 10.140.132.48.1556 fd = 5 13:27:00.809 [317391] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:458] VN_REQUEST_CONNECT_FORWARD_SOCKET 10 0xa 13:27:00.843 [317391] <8> vnet_vnetd_connect_forward_socket_begin: [vnet_vnetd.c:483] ipc_string /usr/openv/var/tmp/vnet-00518533760020847412000002570-nMWF5A 10.140.4.15:38157 -> 10.140.132.48:1556 <2>bptestbpcd: EXIT status = 0 13:27:00.885 [317391] <2> bptestbpcd: EXIT status = 02.7KViews0likes1Commentonline/archive backup of DB2 backing up through netbackup failing after upgrade from 7.6.0.2 to 8.1
Hi All, I have a DB2 redhat linux 2.6 client running SAP on it whose online and archive backups were running fine on version 7.6.0.2 before upgrading to 8.1. There are 4 DB2 databases on this client and after upgrade, 2 are running fine and other 2 are failing with EC 130. Below is the error from job details: ----------------------------------------------- 27 juil. 2018 09:39:39 - Error bprd (pid=6411) Unable to write progress log on client ******. Policy=DB2_*****_ONLINE Sched=Default-Application-Backup 27 juil. 2018 09:39:39 - Error bprd (pid=6411) CLIENT ****** POLICY DB2_*****_ONLINE SCHED Default-Application-Backup EXIT STATUS 130 (system error occurred) ------------------------------------------------- Since 2 DBs on this client are writing fine, there is no issues with communication on master server (Also a Redhat Linux Machine 2.6 NB Version 8.1). The problem happened earlier as well when we tried upgrading the client to 7.7.3 but we then rolled back to 7.6.0.2. I have tried adding the progress log path to BPCD_WHITELIST_PATH under bp.conf of the client but still no luck. I would be happy to provide further logs.1.7KViews0likes7CommentsVADP and RDM Backup on same host
Hi All, I would like to know if it is possible to have both VADP and NBU AGENT based backup on same windows machine I have a windows 2016 server with SQL cluster i want to backup C drive, System State etc ---> Using VADP backup Data drive (RDM disks) (D, E, Q etc..) ---> Using NBU agent Backup Can this be achieved on the windows VM machine ? Thanks, Nayab2.2KViews0likes3Comments