Re: [Veritas-bu] NBU 7.1.0.2
Hi Yes, it improves the speed of duplication from de-dup pool to tape, that's what we need.. Thanks, Leo On Fri, Sep 16, 2011 at 1:22 AM, Justin Piszcz jpis...@lucidpixels.comwrote: Hi, Has anyone installed this in production yet? Justin. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VMWARE bug in NB 7.1/7.0.1
David, In the meantime, I'd say we'll certainly want to make sure to disable the Exclude unused and deleted blocks option on all of our VMware backups ASAP. You can contact support referring the TECH160324 and ask them for engineering binary to protect you. The issue doesn't affect NBU 7.0/7.0.1 GA. It does affect 7.1 GA but binaries are available to resolve this. Which Netbackup version you are using on vmware backup host and have you deployed any EEBs on it. --- Thanks regards, Praveen Gupta -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of David McMullin Sent: Friday, September 16, 2011 1:21 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] VMWARE bug in NB 7.1/7.0.1 My co-worker Nate found this today: You can find more details at the link below, but the summary is this: If you've expanded an NTFS volume and the $BITMAP part of the MFT becomes fragmented in the process, and you take a FlashBackup with the Exclude unused and deleted blocks option Enabled in the snapshot options (which we do, at least on the VMWARE.adhoc.TEST policy), then it will discard fragments of the $BITMAP, thereby trashing the filesystem and, by extension, the backup. This can be fixed by disabling the option Exclude unused and deleted blocks in the snapshot options for the policy, but, based on my experience with the VMWare server, restores will take about 2.5 times as long. In the meantime, I'd say we'll certainly want to make sure to disable the Exclude unused and deleted blocks option on all of our VMware backups ASAP. Symantec says that this bug is patched in NetBackup for VMware 7.1.0.1. This issue affects the following versions of NetBackup for VMware: *NetBackup 7.1 *NetBackup 7.0/7.0.1 when certain Emergency Engineering Binaries have been applied See here for more details: http://www.symantec.com/business/support/index?page=contentid=TECH160324 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] strange socket write failed error during restore
Bart, You aren't hitting a read timeout on the backup image, are you (long seek time to the data etc)? Tar log on the client, and bpbrm log on the master server... That line: 9/14/2011 8:23:15 AM - Info bpbrm(pid=17433) media manager for backup id client_1315796976 exited with status 150 In your detailed log generally indicates that bpbrm chose to terminate the session - and a couple of lines above that entry in the bpbrm log should be a pointer as to why it was terminated... Cheers, Nic -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WALLEBROEK Bart Sent: 14 September 2011 08:18 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] strange socket write failed error during restore Hi Guys, We have since a while status 25 (socket write failed errors). We have a P1 case open with Symantec but they are as clueless as we are. Environment: 1 Solaris Master, 2 Solaris Media Servers (10Gbit connected), Data is backed up to DSSU, restores are coming from both tape and disk (same issue). We noticed that if we restore some data, we get this status code from time to time. When resuming the job (a couple of times) it eventually succeeds. So we believed it would be a network issue. BUT... When we try a restore towards the Media Server itself (having the tape drive connected directly to it, so network involved in the restore) then we get the same error. It even gets worse. Sometimes we get the status 24 even before there was a tape mounted (see log below). Anyone seen this before and knows a resolution ? Activity log: 9/14/2011 8:18:56 AM - begin Restore 9/14/2011 8:19:31 AM - 6 images required 9/14/2011 8:19:31 AM - media 010174 required 9/14/2011 8:19:31 AM - media 200424 required 9/14/2011 8:20:08 AM - restoring image client_1315796717 9/14/2011 8:20:10 AM - Info bpbrm(pid=17661) telling media manager to start restore on client 9/14/2011 8:20:11 AM - Info bpbrm(pid=17661) spawning a brm child process 9/14/2011 8:20:11 AM - Info bpbrm(pid=17661) child pid: 17668 9/14/2011 8:20:11 AM - connecting 9/14/2011 8:20:12 AM - Info bpbrm(pid=17668) start tar on client 9/14/2011 8:20:12 AM - restoring image client_1315796976 9/14/2011 8:20:12 AM - Info tar(pid=17452) Restore started. 9/14/2011 8:20:12 AM - connected; connect time: 00:00:01 9/14/2011 8:20:12 AM - requesting resource 010174 9/14/2011 8:20:12 AM - awaiting resource 010174 Reason: Drives are in use, Media Server: media_server_1, Robot Number: 1, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A 9/14/2011 8:20:14 AM - Info bpbrm(pid=17433) telling media manager to start restore on client 9/14/2011 8:20:14 AM - Info bpbrm(pid=17433) spawning a brm child process 9/14/2011 8:20:14 AM - Info bpbrm(pid=17433) child pid: 17457 9/14/2011 8:20:14 AM - connecting 9/14/2011 8:20:15 AM - Info bpbrm(pid=17457) start tar on client 9/14/2011 8:20:15 AM - Info tar(pid=17470) Restore started. 9/14/2011 8:20:15 AM - connected; connect time: 00:00:01 9/14/2011 8:20:15 AM - requesting resource 200424 9/14/2011 8:20:15 AM - awaiting resource 200424 Reason: Drives are in use, Media Server: media_server_2, Robot Number: 1, Robot Type: TLD, Media ID: N/A, Drive Name: N/A, Volume Pool: N/A, Storage Unit: N/A, Drive Scan Host: N/A 9/14/2011 8:23:11 AM - Info bpbrm(pid=17661) killing bpbrm child 17668. 9/14/2011 8:23:11 AM - Info bpbrm(pid=17661) sending media manager msg: STOP RESTORE client_1315796717 9/14/2011 8:23:11 AM - Info bpbrm(pid=17433) killing bpbrm child 17457. 9/14/2011 8:23:11 AM - Info bpbrm(pid=17433) sending media manager msg: STOP RESTORE beotcd02_1315796976 9/14/2011 8:23:11 AM - Warning bprd(pid=15388) Restore must be resumed prior to first image expiration on Wed Dec 14 03:04:14 2011 9/14/2011 8:23:12 AM - end Restore; elapsed time: 00:04:16 socket write failed(24) 9/14/2011 8:23:14 AM - Error bptm(pid=17667) The following files/folders were not restored: 9/14/2011 8:23:14 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:14 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:14 AM - Error bptm(pid=17667) UTF -[removed] / 9/14/2011 8:23:15 AM - Info bpbrm(pid=17433) media manager for backup id client_1315796976 exited with status 150: termination requested by administrator 9/14/2011 8:23:15 AM - Info bpbrm(pid=17433) sending media manager msg: TERMINATE 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error bptm(pid=17667) UTF - [removed] 9/14/2011 8:23:15 AM - Error
[Veritas-bu] bpcd 13782 - drops connection from master server
The issue - when master server initiates a session to client on port 13782, it drops immediately. Thus, bkps are not running. We are migrating clients off an old NetBackup server to this new server. Tests done: 1-client can telnet to master server on ports 13782 (and maintains connection) 2-master server can still connect to port 13782 on other clients (80+ clients are working without issue) 3-master server can telnet to other NetBackup service port 13724 on client (and maintains connection) 4-old NetBackup master server can telnet to ports 13724, 13782 on client (and maintains connection) Steps taken: 1-restarted NetBackup services on client 2-no firewalls or ACLs exist between client and master server. 3-reinstalled the NetBackup client 4-verified routes, bp.conf, services started Has anyone ever deal with something like this before? Looking for any ideas. Network team, server groups and Symantec not sure of issue. Thanks, Brett +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
Which NBU version? Since 6.0 server/client connection use vnetd (13724) only. M. Sent from my BlackBerry Bold - Original Message - From: brettkan [mailto:nbu-fo...@backupcentral.com] Sent: Friday, September 16, 2011 06:41 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server The issue - when master server initiates a session to client on port 13782, it drops immediately. Thus, bkps are not running. We are migrating clients off an old NetBackup server to this new server. Tests done: 1-client can telnet to master server on ports 13782 (and maintains connection) 2-master server can still connect to port 13782 on other clients (80+ clients are working without issue) 3-master server can telnet to other NetBackup service port 13724 on client (and maintains connection) 4-old NetBackup master server can telnet to ports 13724, 13782 on client (and maintains connection) Steps taken: 1-restarted NetBackup services on client 2-no firewalls or ACLs exist between client and master server. 3-reinstalled the NetBackup client 4-verified routes, bp.conf, services started Has anyone ever deal with something like this before? Looking for any ideas. Network team, server groups and Symantec not sure of issue. Thanks, Brett +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
Are you removing the old master from bp.conf on the clients and putting in the new master? Are you upgrading NBU on the clients to match version on the new master? Are any of these clients media servers? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Marianne Van Den Berg Sent: Friday, September 16, 2011 1:08 PM To: 'veritas-bu@mailman.eng.auburn.edu' Subject: Re: [Veritas-bu] bpcd 13782 - drops connection from master server Which NBU version? Since 6.0 server/client connection use vnetd (13724) only. M. Sent from my BlackBerry Bold - Original Message - From: brettkan [mailto:nbu-fo...@backupcentral.com] Sent: Friday, September 16, 2011 06:41 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server The issue - when master server initiates a session to client on port 13782, it drops immediately. Thus, bkps are not running. We are migrating clients off an old NetBackup server to this new server. Tests done: 1-client can telnet to master server on ports 13782 (and maintains connection) 2-master server can still connect to port 13782 on other clients (80+ clients are working without issue) 3-master server can telnet to other NetBackup service port 13724 on client (and maintains connection) 4-old NetBackup master server can telnet to ports 13724, 13782 on client (and maintains connection) Steps taken: 1-restarted NetBackup services on client 2-no firewalls or ACLs exist between client and master server. 3-reinstalled the NetBackup client 4-verified routes, bp.conf, services started Has anyone ever deal with something like this before? Looking for any ideas. Network team, server groups and Symantec not sure of issue. Thanks, Brett +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] bpcd 13782 - drops connection from master server
Here are the answers to your questions Hi Marianne - Which NBU version? - client 7.0; master 7.1 Hi Jeff - Are you removing the old master from bp.conf on the clients and putting in the new master? Adding the new master server / leaving old master for future restores. Are you upgrading NBU on the clients to match version on the new master? Yes Are any of these clients media servers? No +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
What do the bpcd vnetd logs on the clients show, if anything? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of brettkan Sent: 16 September 2011 18:41 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server The issue - when master server initiates a session to client on port 13782, it drops immediately. Thus, bkps are not running. We are migrating clients off an old NetBackup server to this new server. Tests done: 1-client can telnet to master server on ports 13782 (and maintains connection) 2-master server can still connect to port 13782 on other clients (80+ clients are working without issue) 3-master server can telnet to other NetBackup service port 13724 on client (and maintains connection) 4-old NetBackup master server can telnet to ports 13724, 13782 on client (and maintains connection) Steps taken: 1-restarted NetBackup services on client 2-no firewalls or ACLs exist between client and master server. 3-reinstalled the NetBackup client 4-verified routes, bp.conf, services started Has anyone ever deal with something like this before? Looking for any ideas. Network team, server groups and Symantec not sure of issue. Thanks, Brett +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] bpcd 13782 - drops connection from master server
neither bpcd or vnetd are logging anything when I kick off the bkps. Nothing is registering there. +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
As Patrick said, I I'd be looking at bpcd logs. Also, seeing as this appears to be some new fun you're having with version 7, my wild stab would be the new host cache feature. Run bpclntcmd -clearhostcache or something like that on the client, and see if that sorts it out... Cheers, Nic - Reply message - From: Patrick netbac...@whelan-consulting.co.uk Date: Fri, Sep 16, 2011 18:46 Subject: [Veritas-bu] bpcd 13782 - drops connection from master server To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU VERITAS-BU@MAILMAN.ENG.AUBURN.EDU What do the bpcd vnetd logs on the clients show, if anything? Regards, Patrick Whelan VERITAS Certified NetBackup Support Engineer for UNIX. VERITAS Certified NetBackup Support Engineer for Windows. netbac...@whelan-consulting.co.uk -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of brettkan Sent: 16 September 2011 18:41 To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server The issue - when master server initiates a session to client on port 13782, it drops immediately. Thus, bkps are not running. We are migrating clients off an old NetBackup server to this new server. Tests done: 1-client can telnet to master server on ports 13782 (and maintains connection) 2-master server can still connect to port 13782 on other clients (80+ clients are working without issue) 3-master server can telnet to other NetBackup service port 13724 on client (and maintains connection) 4-old NetBackup master server can telnet to ports 13724, 13782 on client (and maintains connection) Steps taken: 1-restarted NetBackup services on client 2-no firewalls or ACLs exist between client and master server. 3-reinstalled the NetBackup client 4-verified routes, bp.conf, services started Has anyone ever deal with something like this before? Looking for any ideas. Network team, server groups and Symantec not sure of issue. Thanks, Brett +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu The information contained in this e-mail and its attachments is confidential. It is intended only for the named address(es) and may not be disclosed to anyone else without Attenda's consent. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
If the resolutions are correct and you can ping the server then either bpcd port 13782 is not listening or there is something such as client firewall or a TCP wrapper blocking access to the port if you are not getting a bpcd log generated. Try this- telnet localhost 13782 Does that generate a bpcd log entry? If not then try from install pathnetbackup/bin/type in bpcd. Does that generate a log? This link may help- STATUS CODE 58: Can't connect to client. Troubleshooting procedures for status 58 errors http://www.symantec.com/docs/TECH68832 Dan O -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of brettkan Sent: Friday, September 16, 2011 1:06 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server neither bpcd or vnetd are logging anything when I kick off the bkps. Nothing is registering there. +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
Try the 1556 port. NBU client tries to use 1556 by default since 7.0.1 IIRC Also bpcd could drop connection if it cannot resolve the new master's hostname (forward or reverse). This can be catched with bptestbpcd. WBR, Mikhail On Fri, Sep 16, 2011 at 9:33 PM, brettkan nbu-fo...@backupcentral.comwrote: Here are the answers to your questions Hi Marianne - Which NBU version? - client 7.0; master 7.1 Hi Jeff - Are you removing the old master from bp.conf on the clients and putting in the new master? Adding the new master server / leaving old master for future restores. Are you upgrading NBU on the clients to match version on the new master? Yes Are any of these clients media servers? No +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] bpcd 13782 - drops connection from master server
Did generate a log when I typed : /usr/openv/netbackup/logs/bpcd /usr/openv/netbackup/logs/bpcd [352]root: cat log.091611 14:41:24.082 [15390] 2 setup_debug_log: switched debug log file for bpcd 14:41:24.083 [15390] 2 bpcd main: VERBOSE = 0 14:41:24.083 [15390] 2 logparams: bpcd 14:41:24.089 [15390] 2 process_requests: offset to GMT 21600 14:41:24.091 [15390] 2 logconnections: getsockname(0) failed 14:41:24.091 [15390] 2 process_requests: setup_sockopts complete 14:41:24.091 [15390] 16 bpcd peer_hostname: getpeername: Socket operation on non-socket 14:41:24.091 [15390] 16 process_requests: Couldn't get peer hostname +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
Clients can only have one server listed as Master Server. The 'old' server can be left as Server entry. Please do the following test (one client at a time): Ensure bpcd log folder exists on client. Run this command on master: bptestbpcd -client client-name -verbose -debug. (You should see 7.1 master trying to connect to PBX (1556) first, then fail back to vnetd (13724). Please send output produced by above command as well as client's bpcd log. Regards M. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of brettkan Sent: 16 September 2011 07:34 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server Here are the answers to your questions Hi Marianne - Which NBU version? - client 7.0; master 7.1 Hi Jeff - Are you removing the old master from bp.conf on the clients and putting in the new master? Adding the new master server / leaving old master for future restores. Are you upgrading NBU on the clients to match version on the new master? Yes Are any of these clients media servers? No +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
That is what you should get and proves the binary is executable. Did you get a log from the telnet localhost 13782?? Is this a Solaris 10 server?? Try starting bpcd in standlone mode- e.g. /usr/openv/netbackup/logs/bpcd -standalone Then can you connect?? See if these TN helps- Assuming it is Solaris- NetBackup bpcd service stuck in maintenance mode on Solaris 10 client http://www.symantec.com/docs/TECH58167 -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of brettkan Sent: Friday, September 16, 2011 2:43 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server Did generate a log when I typed : /usr/openv/netbackup/logs/bpcd /usr/openv/netbackup/logs/bpcd [352]root: cat log.091611 14:41:24.082 [15390] 2 setup_debug_log: switched debug log file for bpcd 14:41:24.083 [15390] 2 bpcd main: VERBOSE = 0 14:41:24.083 [15390] 2 logparams: bpcd 14:41:24.089 [15390] 2 process_requests: offset to GMT 21600 14:41:24.091 [15390] 2 logconnections: getsockname(0) failed 14:41:24.091 [15390] 2 process_requests: setup_sockopts complete 14:41:24.091 [15390] 16 bpcd peer_hostname: getpeername: Socket operation on non-socket 14:41:24.091 [15390] 16 process_requests: Couldn't get peer hostname +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpcd 13782 - drops connection from master server
Is client part of a Windows cluster? You might check this: http://www.symantec.com/business/support/index?page=contentid=TECH150081 -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of brettkan Sent: Friday, September 16, 2011 9:41 AM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] bpcd 13782 - drops connection from master server The issue - when master server initiates a session to client on port 13782, it drops immediately. Thus, bkps are not running. We are migrating clients off an old NetBackup server to this new server. Tests done: 1-client can telnet to master server on ports 13782 (and maintains connection) 2-master server can still connect to port 13782 on other clients (80+ clients are working without issue) 3-master server can telnet to other NetBackup service port 13724 on client (and maintains connection) 4-old NetBackup master server can telnet to ports 13724, 13782 on client (and maintains connection) Steps taken: 1-restarted NetBackup services on client 2-no firewalls or ACLs exist between client and master server. 3-reinstalled the NetBackup client 4-verified routes, bp.conf, services started Has anyone ever deal with something like this before? Looking for any ideas. Network team, server groups and Symantec not sure of issue. Thanks, Brett +-- |This was sent by brett.t.kand...@fisglobal.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
