VSS timeout issues, restart not suitable solution
Hello I have had continual issues with vss writers time outs on one of our machines we are backing up. Running Windows Server 2008R2 SP1, using BE2010 R3 SP1 The vss writers continue to cause the backup to fail due to timeout. They restart fixes the error status on the writers, but they will time out almost each and every time i run the job. The tech's say i have the job setup correctly, with aofo selected, ms volume shadow copy service(windows 2003 and later) selected and System-use microsoft software shadow copy provider selected. And backup files following junction points. I have selected "Process logical volumes for backup one at a time" too see if this helps. Any suggestions on fixes, besides contanct MS? We don't have support with MS, and as we are suggested to use their system writers by symantec, i would hope that Symantec would provide better aid in fixing VSS issues. Thanks for the help vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001-2005 Microsoft Corp. Writer name: 'Task Scheduler Writer' Writer Id: {d61d61c8-d73a-4eee-8cdd-f6f9786b7124} Writer Instance Id: {1bddd48e-5052-49db-9b07-b96f96727e6b} State: [1] Stable Last error: No error Writer name: 'VSS Metadata Store Writer' Writer Id: {75dfb225-e2e4-4d39-9ac9-ffaff65ddf06} Writer Instance Id: {088e7a7d-09a8-4cc6-a609-ad90e75ddc93} State: [1] Stable Last error: No error Writer name: 'Performance Counters Writer' Writer Id: {0bada1de-01a9-4625-8278-69e735f39dd2} Writer Instance Id: {f0086dda-9efc-47c5-8eb6-a944c3d09381} State: [1] Stable Last error: No error Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {bcedc94e-0c21-4212-8bbf-b65083123138} State: [9] Failed Last error: Timed out Writer name: 'ASR Writer' Writer Id: {be000cbe-11fe-4426-9c58-531aa6355fc4} Writer Instance Id: {fe09e27a-4aef-4e90-bbd3-2308b5d8c6ae} State: [1] Stable Last error: No error Writer name: 'Shadow Copy Optimization Writer' Writer Id: {4dc3bdd4-ab48-4d07-adb0-3bee2926fd7f} Writer Instance Id: {e6368e5a-147a-4561-bf1e-d46989773b71} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {47a3c30f-0074-4427-9937-749e88f3e5b0} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {f054ffeb-46ea-4d21-b9b3-b4c040a31214} State: [1] Stable Last error: No error Writer name: 'BITS Writer' Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0} Writer Instance Id: {3e2f6dc9-6533-4fad-9658-ece31839d8bf} State: [1] Stable Last error: No error Writer name: 'IIS Config Writer' Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6} Writer Instance Id: {f28b57b4-4222-497d-b54f-e75269db970e} State: [9] Failed Last error: Timed out Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {d50d5687-717b-4535-b70f-bee3ecb3f177} State: [9] Failed Last error: Timed outSolved31KViews2likes9Comments
error ( Cannot Connect On Socket )
Hey Everybody, I was working on a Issue, The error ( Cannot Connect On Socket ) occurs while trying communicate a Client from Master server. Checked BPCD logs and test the connectivity b/w client and master, which is not happening. Found that "Windows Firewall" service is running on the server. Now by disabling the Firewal this issue could get resolved. But my concern is ( as Firewall is used to protect the server from virus or any harmful objects ). Why we have to Disable it ? Why NBU connection failed when server is Behind firewll ? Why can not we take backup along with Firewall Enabled ?Solved30KViews1like12Comments
BackupExec Agent for Mac OS X Server not working
I cannot seem to get the BackupExec agent for OS X Server working. I have an XServe running 10.6.4 and RALUS/RAMS 2896.9 (2010r2). I have gone through the installrams script and verified everything is correct. All ports between my server and the backup server are open while troubleshooting this problem. The admin for the backup server has verified everything is correct on his end. Whenever he goes to connect to my server, it is killing the remote agent on my server. I have restarted with the logfile option and can attach if needed. The only thing that stands out to me is that some of the dylib's are not being loaded even though I have added that directory (/opt/VRTSralus/bin) to my DYLD_LIBRARY_PATH variable. Everything else looks normal, at least to me, but the agent is killed when the backup admin tries to connect to it from the BackupExec Console.26KViews0likes6Comments
change the logon account service using command line netbackup
Hello all, in netbackup i want to change the logon account service using command line allthough i already know how to change the services manually but it is not helpful for my testing purpose. Manual procedure is mention below" To configure the log on account for the NetBackup Client Services Any one help me.......any kind of help is appreciated... Thanks Open the Windows Services application. Double-click on the NetBackup Client Service entry. Click on the Log On tab. If Local System account is not selected as the Log on as account, proceed with step 9. Provide the name of the user account that you created for the NetBackup Client Service. The account must include the domain name, followed by the user account, domain_name\account . For example, recovery\netbackup . Type the password. Click OK. Stop and start the NetBackup Client Service. Close the Services control panel application I want to done above mention procedure but using command.Solved23KViews0likes4Comments
ERROR: Error 1335.The cabinet file 'Data1.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package.
Hi all, through installation of netbackup software I got this message : ERROR: Error 1335.The cabinet file 'Data1.cab' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package. I believe it is windows issue.kindly provide me steps needs to follow for solvin this issue. I tried to disable and enable windows moduler but no result. Regards,Solved23KViews1like12Commentsunable to log into Netbackup GUI (Status 526)
Hi all i'm having trobule with a box running redhat 5 and netbackup 7.1, i cant connect to the GUI, i get unbale to log in, status 526 From the log, i get the below - Connecting to vnetd service over PBX port = 1556 ServerInterface:Logon:Exception encountered null ServerInterface:Logon - Initial host:null, Current host:valorum, PBX port:1556 Can not connect to the NB-Java authentication service on valorum on port 1556. Exception: vrts.common.server.CantConnectToAuthServViaVNETDException Any ideas what can cause this? ThanksSolved22KViews3likes7Comments
Error code 21-Socket open failed in NetBackup
Hi All, I was facing error code 21- Scoket open failed issue from long back. While trouble shooting, I have restarted NetBackup Client Service. Still am facing same issue. Can any one suggest on this and provide solution for this to fix it. OS: Windows NetBackup version: 6.5 Thanks in Advance, Sam.Solved21KViews1like8CommentsExit Status: 48 (client hostname could not be found)
Hi all, I have an environment consist of cluster master server windows 2008 and 5 media servers and 2 5020 appliances.I installed agent on the linux redhat client and and i added all server list to bp.conf and etc/hosts in the client and i added the client name in the master server host file.when i'm trying to ping from the client every thing working fine,but i couldnot do this from the master to client.then when i configured the policy the jobs failed with status Exit Status: 48 (client hostname could not be found) then I ran command bptestbpcd -client from master with -debug i got this result: C:\Program Files\Veritas\NetBackup\bin\admincmd>bptestbpcd -client BEC13-ENC2-2 -debug 16:09:32.930 [3444.5668] <2> bptestbpcd: VERBOSE = 0 16:09:32.946 [3444.5668] <2> copy_preferred_network_list: ../../libvlibs/nbconf. c.1610: pseudo PN for : bec12-encx-v37 16:09:32.946 [3444.5668] <2> copy_preferred_network_list: ../../libvlibs/nbconf. c.1610: pseudo PN for : bec12-encx-v37 16:09:32.961 [3444.5668] <2> copy_preferred_network_list: ../../libvlibs/nbconf. c.1610: pseudo PN for : bec12-encx-v37 16:10:02.963 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:10:14.964 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:10:14.964 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:10:45.965 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:10:57.966 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:10:57.966 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:11:08.982 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:11:38.984 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:11:53.984 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:11:57.985 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:12:05.001 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:12:35.002 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:12:43.002 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:12:46.003 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:13:07.004 [3444.5668] <8> async_connect: [vnet_connect.c:1653] getsockopt SO_ ERROR returned 10060 0x274c 16:13:07.004 [3444.5668] <16> connect_to_service: connect failed STATUS (18) CON NECT_FAILED status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed o ut.; FROM 172.20.124.11 TO BEC13-ENC2-2 172.20.165.4 bpcd VIA pbx status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed o ut.; FROM 172.20.124.11 TO BEC13-ENC2-2 172.20.165.4 bpcd VIA vnetd status: FAILED, (42) CONNECT_REFUSED; system: (10060) Connection timed o ut.; FROM 172.20.124.11 TO BEC13-ENC2-2 172.20.165.4 bpcd 16:13:07.004 [3444.5668] <8> vnet_connect_to_bpcd: [vnet_connect.c:279] connect_ to_service() failed 18 0x12 16:13:07.004 [3444.5668] <2> local_bpcr_connect: Can't connect to client BEC13-E NC2-2 16:13:07.004 [3444.5668] <2> ConnectToBPCD: bpcd_connect_and_verify(BEC13-ENC2-2 , BEC13-ENC2-2) failed: 25 <16>bptestbpcd main: Function ConnectToBPCD(BEC13-ENC2-2) failed: 25 16:13:07.004 [3444.5668] <16> bptestbpcd main: Function ConnectToBPCD(BEC13-ENC2 -2) failed: 25 <2>bptestbpcd: cannot connect on socket 16:13:07.004 [3444.5668] <2> bptestbpcd: cannot connect on socket <2>bptestbpcd: EXIT status = 25 16:13:07.004 [3444.5668] <2> bptestbpcd: EXIT status = 25 cannot connect on socket C:\Program Files\Veritas\NetBackup\bin\admincmd> please advice what is missed??? Regards,Solved20KViews1like16Comments
Difference between Differential Inc backup and Cumulative Inc backup.
All my backups are archive bit dependant. Please let me know what is the difference we are backing up in Differential Inc backup and Cumulative Inc backup, if below definitions are correct. Please find the attachement. Thanks and regards, Bharath AcharSolved20KViews1like5Comments
BackupExec Agent for Mac OS X Server not working
I cannot seem to get the BackupExec agent for OS X Server working. I have an XServe running 10.6.4 and RALUS/RAMS 2896.9 (2010r2). I have gone through the installrams script and verified everything is correct. All ports between my server and the backup server are open while troubleshooting this problem. The admin for the backup server has verified everything is correct on his end. Whenever he goes to connect to my server, it is killing the remote agent on my server. I have restarted with the logfile option and can attach if needed. The only thing that stands out to me is that some of the dylib's are not being loaded even though I have added that directory (/opt/VRTSralus/bin) to my DYLD_LIBRARY_PATH variable. Everything else looks normal, at least to me, but the agent is killed when the backup admin tries to connect to it from the BackupExec Console.