ContributionsMost RecentMost LikesSolutionsRe: could not write KEEPALIVE to COMM_SOCK Rizwan, Thanks for reply but DLL files for VSSare registered already. Re: could not write KEEPALIVE to COMM_SOCK Marianne, below is the required output. And there is an activity going on step by step to upgrade all master, media server and client as well and this is also in the schedule. Yesits specified VSS for WOFB backup of client. E:\VERITAS\NetBackup\bin\admincmd>bpclient -client client01-L Client Name: client01 Current Host: Hostname: client01 IP Address: 0.0.0.0 Connect on non-reserved port: no No call-back connections: no Dynamic Address: no Free Browse: Allow List Restore: Not Specified Max Jobs This Client: Not Specified WOFB Enabled: yes WOFB FIM: VSS WOFB Usage: Individual Drive Snapshot WOFB Error Control: Abort on Error Thanks, Re: could not write KEEPALIVE to COMM_SOCK Rizwan, attached is the log file. Re: could not write KEEPALIVE to COMM_SOCK Netbackup client version :- WINDOWS 2003 HARDWARE Windows x86 VERSION NetBackup 5.1MP4S01 BUILDNUMBER 0178 RELEASEDATE Fri Mar 3 11:59:42 CST 2006 Netbackup Master Server Version :- WINDOWS 2003 HARDWARE Windows x86 VERSION NetBackup 5.1MP4S01 BUILDNUMBER 0178 RELEASEDATE Fri Mar 3 11:59:42 CST 2006 C:\VERITAS\NetBackup\bin>vssadmin list writers vssadmin 1.1 - Volume Shadow Copy Service administrative command-line tool (C) Copyright 2001 Microsoft Corp. Writer name: 'System Writer' Writer Id: {e8132975-6f93-4464-a53e-1050253ae220} Writer Instance Id: {40ba7fe3-a219-417b-9e6b-08f7c0bee758} State: [5] Waiting for completion Last error: No error Writer name: 'SqlServerWriter' Writer Id: {a65faa63-5ea8-4ebc-9dbd-a0c4db26912a} Writer Instance Id: {3b51be22-243f-4dce-966e-13a21ab3abaf} State: [5] Waiting for completion Last error: No error Writer name: 'MSDEWriter' Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277} Writer Instance Id: {2cae7d84-e8d0-43ad-bb01-f186cf8053da} State: [1] Stable Last error: No error Writer name: 'Registry Writer' Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485} Writer Instance Id: {8d84dea3-7275-4ef0-a049-2d5cc9ae5d98} State: [1] Stable Last error: No error Writer name: 'Event Log Writer' Writer Id: {eee8c692-67ed-4250-8d86-390603070d00} Writer Instance Id: {8bac6a6f-7db4-48f9-aeaa-0774ac48e9cc} State: [1] Stable Last error: No error Writer name: 'COM+ REGDB Writer' Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f} Writer Instance Id: {a85840a2-28a9-4061-a1ef-990ec4ac0c29} State: [1] Stable Last error: No error Writer name: 'WMI Writer' Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0} Writer Instance Id: {e2835648-678f-4f76-88cf-45ae7f8186d9} State: [5] Waiting for completion Last error: No error Writer name: 'IIS Metabase Writer' Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366} Writer Instance Id: {04f4fce5-9879-4aae-b979-110ef981f53e} State: [5] Waiting for completion Last error: No error Thanks in advance ! could not write KEEPALIVE to COMM_SOCK Hi All I'm facing an issue with widows 2003client backup. Its getting failed with error 71 (none of the files in the file list exist) only for "Shadow Copy Components:\" HOTFIX is updated and updated version of service pack is installed on the client. VSS services are in running state. 4/25/2011 4:38:52 PM - mounting 1117L3 4/25/2011 4:38:52 PM - started process bpbrm (568) 4/25/2011 4:38:52 PM - connecting 4/25/2011 4:39:22 PM - connected; connect time: 00:00:30 4/25/2011 4:39:35 PM - mounted; mount time: 00:00:43 4/25/2011 4:39:38 PM - positioning 1117L3 to file 1971 4/25/2011 4:40:22 PM - Error bpbrm(pid=4852) could not write KEEPALIVE to COMM_SOCK 4/25/2011 4:41:25 PM - positioned 1117L3; position time: 00:01:47 4/25/2011 4:41:25 PM - begin writing 4/25/2011 4:41:31 PM - end writing; write time: 00:00:06 none of the files in the file list exist(71) 4/25/2011 4:41:38 PM - Error bpsched(pid=4644) backup of client psgusguepes04 exited with status 71 (none of the files in the file list exist) Please assist how can we get out of this issue. Re: Backup failed with error 13 (file read failed) Hi All, Thankyou very much to all for your valuable suggestion and assistance to deal with the issue. Now issue has been resolved and what I found is that there were issue with VSS at the server end. I have re-register the VSS DLL files and by running following in cmd. Now vss is working fine and backup getting successfully completed. cd %windir%/system32 net stop vss regsvr32 /s ole32.dll regsvr32 /s vss_ps.dll vssvc /Register regsvr32 /s /i swprv.dll regsvr32 /s /i eventcls.dll regsvr32 /s es.dll regsvr32 /s stdprov.dll regsvr32 /s vssui.dll regsvr32 /s msxml.dll regsvr32 /s msxml3.dll regsvr32 /s msxml4.dll Thanks once again, nice to share the issue with all of you. R.S. Re: Backup failed with error 13 (file read failed) Zahid, Attached is the screen shot, and below are the detailed status of Partially successfully backup. Issue is still there. Mar 27, 2011 10:10:44 AM - requesting resource _ _LTO3_LTO4 Mar 27, 2011 10:10:44 AM - requesting resource .NBU_CLIENT.MAXJOBS. Mar 27, 2011 10:10:44 AM - requesting resource .NBU_POLICY.MAXJOBS.NTVALIDATED-VERITAS-SCHED Mar 27, 2011 10:10:44 AM - granted resource .NBU_CLIENT.MAXJOBS. Mar 27, 2011 10:10:44 AM - granted resource .NBU_POLICY.MAXJOBS.NTVALIDATED-VERITAS-SCHED Mar 27, 2011 10:10:44 AM - granted resource 002450 Mar 27, 2011 10:10:44 AM - granted resource LTO3_SHARED_9 Mar 27, 2011 10:10:44 AM - granted resource _ADIC_I2K_LTO3 Mar 27, 2011 10:10:45 AM - estimated 2223636692 kbytes needed Mar 27, 2011 10:10:54 AM - connecting Mar 27, 2011 10:10:57 AM - connected; connect time: 0:00:00 Mar 27, 2011 10:10:57 AM - begin writing Mar 27, 2011 10:23:27 AM - Warning bpbrm (pid=28042) from client : WRN - Content Indexing Server: unable to pause catalog: Web (some files may not get backed up) Mar 27, 2011 10:23:37 AM - Warning bpbrm (pid=28042) from client : WRN - Content Indexing Server: unable to pause catalog: Web (some files may not get backed up) Mar 27, 2011 10:23:47 AM - Warning bpbrm (pid=28042) from client : WRN - Content Indexing Server: unable to pause catalog: Web (some files may not get backed up) Mar 27, 2011 10:23:57 AM - Warning bpbrm (pid=28042) from client : WRN - Content Indexing Server: unable to pause catalog: Web (some files may not get backed up) Mar 27, 2011 10:24:07 AM - Warning bpbrm (pid=28042) from client : WRN - Content Indexing Server: unable to pause catalog: Web (some files may not get backed up) Mar 27, 2011 10:24:17 AM - Warning bpbrm (pid=28042) from client : WRN - Content Indexing Server: unable to pause catalog: Web (some files may not get backed up) Mar 27, 2011 10:36:38 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\SCOM\Health Service State\Health Service Store\edb.log (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 10:36:40 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\SCOM\Health Service State\Health Service Store\edbtmp.log (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 10:36:40 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\SCOM\Health Service State\Health Service Store\HealthServiceStore.edb (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 10:36:45 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\SCOM\Health Service State\Health Service Store\tmp.edb (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 10:37:11 AM - Warning bpbrm (pid=28042) from client : WRN - Content Indexing Server: unable to pause catalog: System (some files may not get backed up) Mar 27, 2011 10:37:31 AM - Error bpbrm (pid=28042) from client : ERR - failure reading file: C:\VERITAS\NetBackup\logs\bpbkar\032711.LOG (WIN32 13: The data is invalid. ) Mar 27, 2011 10:43:13 AM - current media 002450 complete, requesting next media Any Mar 27, 2011 10:43:14 AM - granted resource 008844 Mar 27, 2011 10:43:14 AM - granted resource _30 Mar 27, 2011 10:43:14 AM - granted resource _ADIC_I2K_LTO3 Mar 27, 2011 10:43:15 AM - mounting 008844 Mar 27, 2011 10:43:54 AM - mounted 008844; mount time: 0:00:39 Mar 27, 2011 10:43:54 AM - positioning 008844 to file 1 Mar 27, 2011 10:43:56 AM - positioned 008844; position time: 0:00:02 Mar 27, 2011 10:43:56 AM - begin writing Mar 27, 2011 11:18:10 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\master.mdf (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 11:18:11 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\mastlog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 11:18:11 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\model.mdf (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 11:18:12 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\modellog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 11:18:13 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\msdbdata.mdf (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 11:18:13 AM - Warning bpbrm (pid=28042) from client : WRN - can't open file: C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\Data\msdblog.ldf (WIN32 32: The process cannot access the file because it is being used by another process. ) Mar 27, 2011 11:45:48 AM - Error bpbrm (pid=28042) from client : ERR - failure reading file: C:\WINDOWS\system32\LogFiles\W3SVC1\ex110327.log (WIN32 13: The data is invalid. ) Mar 27, 2011 6:39:13 PM - current media 008844 complete, requesting next media Any Mar 27, 2011 6:39:14 PM - Waiting for scan drive stop LTO3_SHARED_14, Media server: .backup.ncsus.jnj.com Mar 27, 2011 6:39:14 PM - granted resource 002433 Mar 27, 2011 6:39:14 PM - granted resource LTO3_SHARED_14 Mar 27, 2011 6:39:14 PM - granted resource _ADIC_I2K_LTO3 Mar 27, 2011 6:39:15 PM - mounting 002433 Mar 27, 2011 6:39:52 PM - mounted 002433; mount time: 0:00:37 Mar 27, 2011 6:39:52 PM - positioning 002433 to file 1 Mar 27, 2011 6:39:55 PM - positioned 002433; position time: 0:00:03 Mar 27, 2011 6:39:55 PM - begin writing Mar 28, 2011 5:04:08 AM - current media 002433 complete, requesting next media Any Mar 28, 2011 5:04:09 AM - granted resource 006823 Mar 28, 2011 5:04:09 AM - granted resource _30 Mar 28, 2011 5:04:09 AM - granted resource _ADIC_I2K_LTO3 Mar 28, 2011 5:04:10 AM - mounting 006823 Mar 28, 2011 5:04:50 AM - mounted 006823; mount time: 0:00:40 Mar 28, 2011 5:04:50 AM - positioning 006823 to file 1 Mar 28, 2011 5:04:54 AM - positioned 006823; position time: 0:00:04 Mar 28, 2011 5:04:54 AM - begin writing Mar 28, 2011 3:30:54 PM - current media 006823 complete, requesting next media Any Mar 28, 2011 3:30:55 PM - granted resource 001126 Mar 28, 2011 3:30:55 PM - granted resource _25 Mar 28, 2011 3:30:55 PM - granted resource _ADIC_I2K_LTO3 Mar 28, 2011 3:30:56 PM - mounting 001126 Mar 28, 2011 3:31:32 PM - mounted 001126; mount time: 0:00:36 Mar 28, 2011 3:31:32 PM - positioning 001126 to file 1 Mar 28, 2011 3:31:35 PM - positioned 001126; position time: 0:00:03 Mar 28, 2011 3:31:35 PM - begin writing Mar 28, 2011 8:20:25 PM - current media 001126 complete, requesting next media Any Mar 28, 2011 8:20:25 PM - granted resource 002942 Mar 28, 2011 8:20:25 PM - granted resource _29 Mar 28, 2011 8:20:25 PM - granted resource _ADIC_I2K_LTO3 Mar 28, 2011 8:20:27 PM - mounting 002942 Mar 28, 2011 8:21:25 PM - mounted 002942; mount time: 0:00:58 Mar 28, 2011 8:21:26 PM - positioning 002942 to file 1 Mar 28, 2011 8:21:29 PM - positioned 002942; position time: 0:00:03 Mar 28, 2011 8:21:29 PM - begin writing Mar 29, 2011 5:25:34 AM - current media 002942 complete, requesting next media Any Mar 29, 2011 5:25:35 AM - granted resource 005942 Mar 29, 2011 5:25:35 AM - granted resource _31 Mar 29, 2011 5:25:35 AM - granted resource _ADIC_I2K_LTO3 Mar 29, 2011 5:25:36 AM - mounting 005942 Mar 29, 2011 5:26:38 AM - mounted 005942; mount time: 0:01:02 Mar 29, 2011 5:26:38 AM - positioning 005942 to file 1 Mar 29, 2011 5:26:41 AM - positioned 005942; position time: 0:00:03 Mar 29, 2011 5:26:41 AM - begin writing Mar 29, 2011 12:42:13 PM - current media 005942 complete, requesting next media Any Mar 29, 2011 12:42:14 PM - granted resource 007900 Mar 29, 2011 12:42:14 PM - granted resource _32 Mar 29, 2011 12:42:14 PM - granted resource _ADIC_I2K_LTO3 Mar 29, 2011 12:42:16 PM - mounting 007900 Mar 29, 2011 12:42:53 PM - mounted 007900; mount time: 0:00:37 Mar 29, 2011 12:42:53 PM - positioning 007900 to file 1 Mar 29, 2011 12:42:59 PM - positioned 007900; position time: 0:00:06 Mar 29, 2011 12:42:59 PM - begin writing Mar 29, 2011 4:36:44 PM - Warning bpbrm (pid=28042) from client : WRN - can't open object: Shadow Copy Components:\User Data\SMS Writer\N10Backup\SiteServer\N10Backup\SiteServer\SMSbkSiteRegNAL.dat (BEDS 0xFFFFFE07: ) Mar 29, 2011 4:36:44 PM - Warning bpbrm (pid=28042) from client : WRN - can't open object: Shadow Copy Components:\User Data\SMS Writer\N10Backup\SiteServer\SMSServer\inboxes\N10Backup\SiteServer\SMSServer\inboxes (BEDS 0xFFFFFE07: ) Mar 29, 2011 4:36:45 PM - Warning bpbrm (pid=28042) from client : WRN - can't open object: Shadow Copy Components:\User Data\SMS Writer\N10Backup\SiteServer\SMSServer\Logs\N10Backup\SiteServer\SMSServer\Logs (BEDS 0xFFFFFE07: ) Mar 29, 2011 4:36:45 PM - Warning bpbrm (pid=28042) from client : WRN - can't open object: Shadow Copy Components:\User Data\SMS Writer\N10Backup\SiteServer\SMSServer\data\N10Backup\SiteServer\SMSServer\data (BEDS 0xFFFFFE07: ) Mar 29, 2011 4:36:46 PM - Warning bpbrm (pid=28042) from client : WRN - can't open object: Shadow Copy Components:\User Data\SMS Writer\N10Backup\SiteServer\SMSServer\srvacct\N10Backup\SiteServer\SMSServer\srvacct (BEDS 0xFFFFFE07: ) Mar 29, 2011 4:36:52 PM - end writing; write time: 3:53:53 the requested operation was partially successful (1) Re: Backup failed with error 13 (file read failed) Marianne, WOFB is disabled, Version is 5.1 MP6 Job tracket is disabled, bpfis is terminates. I have created a bpbkar_path_tr file in Netbackup, and will check if any updated info. will be there in the bpbkarlogs. #bpclient -client <client_name> -L Free Browse: Allow List Restore: Not Specified Max Jobs This Client: Not Specified WOFB Enabled: no WOFB FIM: VSP WOFB Usage: Individual Drive Snapshot WOFB Error Control: Abort on Error Connect options: 2 2 3 Version.txt fileof client. HARDWARE Windows x64 VERSION NetBackup 5.1MP6A BUILDNUMBER 0240 RELEASEDATE Mon Nov 6 09:25:40 CST 2006 I have one query as, when the client is rebooted the very next schedule backup after reboot is getting complete but partially. So whats the thing which is getting correct after an reboot and get to the same situation after a completion of backup. Re: Disk Stagging is not getting successful Thanks Rajesh, yup its nice to resolve issue with you guys. There were issue with the Water Mark, as when the issue occurs, it was set to 100% High and 80 Low, due to which disk is getting full without cleanup. And after make this change as 30% low and 80% high then cleaning of images successful. Re: Backup failed with error 13 (file read failed) Zahid, there is no error or warning exist in the event viewer.