SPX backup causing computer to lose connection to network

I am running ShadowControl with an SPX policy. I have pushed the install to 41 HP workstations successfully, and have working backups for over a month. I have 2 HP workstations that were pushed the same package and they will not make a full backup. The backup starts runs for a while and then the workstation will lose connection to the network causing an I/O Error, Broken Pipe, or General Error. I have tried everything I can think of to get this working and nothing has worked. I opened a support ticket with StorageCraft and after waiting for two weeks I get an email with a few suggestions that did not help and they closed the ticket. I emailed the person that closed the ticket and after another week, I still have no response. I have done all repair suggestions that I have found duing my searches for similar problems, but if anyone has any ideas please let me know.

Here is the log for one of the workstations:

2017-05-18 08:26:06 I [5340] backuprun (50): 2017-05-18 08:26:06 I [5340] backuprun (51): ----- backup start -----2017-05-18 08:26:06 D [5340] stcapi (143): stc_create_session2017-05-18 08:26:06 I [5340] backuprun (85): BackupJob(name=u'MCI Workstations', uuid=u'cb1a065d1f96465ab25a5e40aff7cce2')2017-05-18 08:26:06 I [5340] backuprun (145): initial backup type: <BackupType.incremental: 2>2017-05-18 08:26:06 D [5340] backuprun (173): confirmed access to Destination(name=u'Workstation Backup', path=u'\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5')2017-05-18 08:26:06 D [5340] stcapi (311): stc_is_licensed<{"handle": 5522320}2017-05-18 08:26:06 I [5340] valid (279): incremental -> full_reset<{"volume": "\\\\?\\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}", "why": "no base"}2017-05-18 08:26:06 I [5340] stcapi (764): Added volume '\\?\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}' for full_reset2017-05-18 08:26:06 I [5340] backuprun (262): backup volumes<{"ready": "[(JobVolume(device=u'\\\\\\\\?\\\\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}', vol_id=u'2426a9c4a3c311e2b383806e6f6e6963'), <BackupType.full_reset: 1>)]", "unready": "[]"}2017-05-18 08:26:06 I [5340] backuprun (222): creating snapshot<{"vss_exclusions": []}2017-05-18 08:26:06 I [5340] stcapi (764): Snapshot attempt VSS API by STC provider of 1 warm volume2017-05-18 08:26:06 I [5340] stcapi (764): Requested backup type for volume '\\?\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}': full_reset2017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'System Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'Shadow Copy Optimization Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'ASR Writer' state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT hresult 0x800423f02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'MSSearch Service Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'MSMQ Writer (MSMQ)' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'IIS Config Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'Registry Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'COM+ REGDB Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): VSS phase 1 writer 'WMI Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:27:20 I [5340] stcapi (764): Snapshot attempt completed in 74.117s2017-05-18 08:27:20 I [5340] stcapi (764): Snapshot '\\?\STC_SnapShot_Volume_21_0' time 1313958764062920962017-05-18 08:27:21 I [5340] stcapi (764): Progress baseline: 61641519104 dirty bytes (est), 423069024256 free bytes, 946700280 dirty sectors, 946700280 total sectors, 512 sector size2017-05-18 08:27:21 I [5340] backuprun (232): created snapshot, type: <SnapshotType.vss_stc: 2>2017-05-18 08:27:21 I [5340] stcapi (764): Getting image filename2017-05-18 08:27:23 I [5340] backuprun (353): image filename: C_VOL-b001.spf2017-05-18 08:27:23 I [5340] stcapi (764): Backup starting2017-05-18 08:27:23 D [5340] stcapi (764): sbrun 112 86 ["6.3.4.5"]2017-05-18 08:27:23 I [5340] stcapi (764): sbrun 195 -1 ["6.3.4.5","6.3.4.5"]2017-05-18 08:27:23 I [6484] stcapi (764): sbrun 109 39 []2017-05-18 08:27:23 I [6484] stcapi (764): sbrun 107 7 [0]2017-05-18 08:27:23 D [6484] stcapi (764): sbrun 117 8 [946700280,946700280,100]2017-05-18 08:27:23 I [6484] stcapi (764): sbrun 101 2 ["\\\\?\\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}"]2017-05-18 08:27:23 I [6484] stcapi (764): sbrun 107 5 [0]2017-05-18 08:27:23 D [6484] stcapi (764): sbrun 112 82 ["\\\\?\\STC_SnapShot_Volume_21_0\\pagefile.sys"]2017-05-18 08:27:23 D [6484] stcapi (764): sbrun 112 82 ["\\\\?\\STC_SnapShot_Volume_21_0\\hiberfil.sys"]2017-05-18 08:27:23 I [6484] stcapi (764): Progress adjustment: 0 (+0) done, 58240299008 (-3401220096) total2017-05-18 08:27:23 I [7000] stcapi (764): sbrun 109 29 []2017-05-18 08:27:23 I [5636] stcapi (764): sbrun 620 -1 ["\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5\\C_VOL-b001.spf"]2017-05-18 08:27:23 I [5636] stcapi (764): sbrun 621 -1 ["\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5\\C_VOL-b001.spf"]2017-05-18 08:27:23 I [6484] stcapi (764): sbrun 107 6 [1]2017-05-18 08:27:23 I [6484] stcapi (764): sbrun 107 4 [63]2017-05-18 08:27:23 I [6484] stcapi (764): sbrun 109 -1 ["SBMSG_CHS_PARTNO<[60801,255,63,2] "]2017-05-18 08:27:23 I [7000] stcapi (764): sbrun 107 11 [5]2017-05-18 08:27:23 I [7000] stcapi (764): sbrun 107 12 [4]2017-05-18 08:27:23 I [7000] stcapi (764): sbrun 600 203 []2017-05-18 08:27:24 I [5636] stcapi (764): sbrun 101 3 ["smb://\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5\\C_VOL-b001.spf"]2017-05-18 08:31:17 I [6484] stcapi (764): Progress \\?\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963} 8% of 55542MB; 8% of 55542MB 7MB/s2017-05-18 08:31:59 I [5636] stcapi (764): sbrun 108 259 [General error: An unexpected network error occurred. (-31:1:59 c:1194)]2017-05-18 08:32:07 I [5636] stcapi (764): sbrun 107 260 [20]2017-05-18 08:32:07 C [5636] stcapi (764): sbrun 503 -1 ["smb://\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5\\C_VOL-b001.spf",2663798272,1,General error: An unexpected network error occurred. (-31:1:59 c:1194)]2017-05-18 08:32:07 I [5636] stcapi (764): sbrun 109 37 []2017-05-18 08:32:07 I [7000] stcapi (764): sbrun 109 30 []2017-05-18 08:32:07 I [6484] stcapi (764): sbrun 109 30 []2017-05-18 08:33:19 I [5636] stcapi (764): sbrun 109 30 []2017-05-18 08:33:19 E [5340] stcapi (764): SbRun failed: Broken pipe (-109:0:0 c:451)2017-05-18 08:33:19 E [5340] stcapi (764): Backup of volume '\\?\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}' failed: I/O error: An unexpected network error occurred. (-23:1:59 c:1194)2017-05-18 08:33:19 I [5340] stcapi (764): All backup threads joined2017-05-18 08:33:19 I [5340] stcapi (764): Unsnapping after unsuccessful backup2017-05-18 08:33:21 I [5340] stcapi (764): VSS phase 2 writer 'ASR Writer' state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT hresult 0x800423f02017-05-18 08:33:21 E [5340] backuprun (97): backup errorTraceback (most recent call last):  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\spx_service\backup\backuprun.py", line 90, in run  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\spx_service\backup\backuprun.py", line 215, in _run_core  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\spx_service\backup\backuprun.py", line 239, in _run_backup_session  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\stc_misc\native\stcapi.py", line 634, in do_backup  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\stc_misc\native\library.py", line 88, in _os_status_errcheckBackupError: stcapi.error.io2017-05-18 08:33:21 I [5340] backuprun (311): job event created: 2017-05-18 08:26:06.138000 (435 s.) "MCI Workstations" failure2017-05-18 08:33:21 I [5340] backuprun (111): ----- backup stop -----2017-05-18 08:33:21 D [5340] stcapi (186): stc_destroy_session<{"handle": 5522320}2017-05-18 08:45:00 I [8040] backuprun (50): 2017-05-18 08:45:00 I [8040] backuprun (51): ----- backup start -----2017-05-18 08:45:00 D [8040] stcapi (143): stc_create_session2017-05-18 08:45:00 I [8040] backuprun (85): BackupJob(name=u'MCI Workstations', uuid=u'cb1a065d1f96465ab25a5e40aff7cce2')2017-05-18 08:45:00 I [8040] backuprun (145): initial backup type: <BackupType.incremental: 2>2017-05-18 08:45:00 D [8040] backuprun (173): confirmed access to Destination(name=u'Workstation Backup', path=u'\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5')2017-05-18 08:45:00 D [8040] stcapi (311): stc_is_licensed<{"handle": 6281088}2017-05-18 08:45:00 I [8040] valid (279): incremental -> full_reset<{"volume": "\\\\?\\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}", "why": "no base"}2017-05-18 08:45:00 I [8040] stcapi (764): Added volume '\\?\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}' for full_reset2017-05-18 08:45:00 I [8040] backuprun (262): backup volumes<{"ready": "[(JobVolume(device=u'\\\\\\\\?\\\\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}', vol_id=u'2426a9c4a3c311e2b383806e6f6e6963'), <BackupType.full_reset: 1>)]", "unready": "[]"}2017-05-18 08:45:00 I [8040] backuprun (222): creating snapshot<{"vss_exclusions": []}2017-05-18 08:45:00 I [8040] stcapi (764): Snapshot attempt VSS API by STC provider of 1 warm volume2017-05-18 08:45:00 I [8040] stcapi (764): Requested backup type for volume '\\?\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}': full_reset2017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'System Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'Shadow Copy Optimization Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'IIS Config Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'MSMQ Writer (MSMQ)' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'WMI Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'COM+ REGDB Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'ASR Writer' state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT hresult 0x800423f02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'Registry Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): VSS phase 1 writer 'MSSearch Service Writer' state VSS_WS_WAITING_FOR_BACKUP_COMPLETE hresult 0x02017-05-18 08:46:06 I [8040] stcapi (764): Snapshot attempt completed in 65.446s2017-05-18 08:46:06 I [8040] stcapi (764): Snapshot '\\?\STC_SnapShot_Volume_21_0' time 1313958876605589152017-05-18 08:46:06 I [8040] stcapi (764): Progress baseline: 60466225152 dirty bytes (est), 424244318208 free bytes, 946700280 dirty sectors, 946700280 total sectors, 512 sector size2017-05-18 08:46:06 I [8040] backuprun (232): created snapshot, type: <SnapshotType.vss_stc: 2>2017-05-18 08:46:06 I [8040] stcapi (764): Getting image filename2017-05-18 08:46:07 I [8040] backuprun (353): image filename: C_VOL-b001.spf2017-05-18 08:46:07 I [8040] stcapi (764): Backup starting2017-05-18 08:46:07 D [8040] stcapi (764): sbrun 112 86 ["6.3.4.5"]2017-05-18 08:46:07 I [8040] stcapi (764): sbrun 195 -1 ["6.3.4.5","6.3.4.5"]2017-05-18 08:46:07 I [596] stcapi (764): sbrun 109 39 []2017-05-18 08:46:07 I [596] stcapi (764): sbrun 107 7 [0]2017-05-18 08:46:07 D [596] stcapi (764): sbrun 117 8 [946700280,946700280,100]2017-05-18 08:46:07 I [596] stcapi (764): sbrun 101 2 ["\\\\?\\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}"]2017-05-18 08:46:07 I [596] stcapi (764): sbrun 107 5 [0]2017-05-18 08:46:07 D [596] stcapi (764): sbrun 112 82 ["\\\\?\\STC_SnapShot_Volume_21_0\\pagefile.sys"]2017-05-18 08:46:07 D [596] stcapi (764): sbrun 112 82 ["\\\\?\\STC_SnapShot_Volume_21_0\\hiberfil.sys"]2017-05-18 08:46:07 I [596] stcapi (764): Progress adjustment: 0 (+0) done, 57065005056 (-3401220096) total2017-05-18 08:46:07 I [1636] stcapi (764): sbrun 109 29 []2017-05-18 08:46:07 I [7596] stcapi (764): sbrun 620 -1 ["\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5\\C_VOL-b001.spf"]2017-05-18 08:46:07 I [7596] stcapi (764): sbrun 621 -1 ["\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5\\C_VOL-b001.spf"]2017-05-18 08:46:07 I [596] stcapi (764): sbrun 107 6 [1]2017-05-18 08:46:07 I [596] stcapi (764): sbrun 107 4 [63]2017-05-18 08:46:07 I [596] stcapi (764): sbrun 109 -1 ["SBMSG_CHS_PARTNO<[60801,255,63,2] "]2017-05-18 08:46:07 I [1636] stcapi (764): sbrun 107 11 [5]2017-05-18 08:46:07 I [1636] stcapi (764): sbrun 107 12 [4]2017-05-18 08:46:07 I [1636] stcapi (764): sbrun 600 203 []2017-05-18 08:47:07 I [7596] stcapi (764): sbrun 108 265 [Sharing violation: The process cannot access the file because it is being used by another process. (-32:1:32 c:926)]2017-05-18 08:47:07 E [7596] stcapi (764): sbrun 404 -1 ["\\\\MCICLOUD2\\Workstation Backup\\MARISSA2-HP_1aedd58d45084e6b89a2ca2d8b250bb5\\C_VOL-b001.spf",Sharing violation: The process cannot access the file because it is being used by another process. (-32:1:32 c:926)]2017-05-18 08:47:07 I [7596] stcapi (764): sbrun 109 30 []2017-05-18 08:47:07 I [1636] stcapi (764): sbrun 109 30 []2017-05-18 08:47:07 I [596] stcapi (764): sbrun 109 30 []2017-05-18 08:47:07 E [8040] stcapi (764): SbRun failed: Broken pipe (-109:0:0 c:451)2017-05-18 08:47:07 E [8040] stcapi (764): Backup of volume '\\?\Volume{2426a9c4-a3c3-11e2-b383-806e6f6e6963}' failed: Sharing violation: The process cannot access the file because it is being used by another process. (-32:1:32 c:926)2017-05-18 08:47:07 I [8040] stcapi (764): All backup threads joined2017-05-18 08:47:07 I [8040] stcapi (764): Unsnapping after unsuccessful backup2017-05-18 08:47:09 I [8040] stcapi (764): VSS phase 2 writer 'ASR Writer' state VSS_WS_FAILED_AT_PREPARE_SNAPSHOT hresult 0x800423f02017-05-18 08:47:09 E [8040] backuprun (97): backup errorTraceback (most recent call last):  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\spx_service\backup\backuprun.py", line 90, in run  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\spx_service\backup\backuprun.py", line 215, in _run_core  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\spx_service\backup\backuprun.py", line 239, in _run_backup_session  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\stc_misc\native\stcapi.py", line 634, in do_backup  File "D:\bamboo-home\xml-data\build-dir\SPX-CXSPX85-JOB1\stc_misc\native\library.py", line 88, in _os_status_errcheckBackupError: stcapi.error.os_error2017-05-18 08:47:09 I [8040] backuprun (311): job event created: 2017-05-18 08:45:00.020000 (130 s.) "MCI Workstations" failure2017-05-18 08:47:09 I [8040] backuprun (111): ----- backup stop -----2017-05-18 08:47:09 D [8040] stcapi (186): stc_destroy_session<{"handle": 6281088}

Forums:

Comments

STC-JoshS

Try rebooting the system. It

Try rebooting the system. It looks like something else is accessing the snapshot while we are. If that doesn't work I would recommend opening a ticket with support and having them give you a hand with this.

lesterlilley

I have already opened a

I have already opened a ticket, they took two weeks and then closed the ticket with a few suggestions. I replied to the technicians direct email address and did not receive a response.

JamesDyke

Auto closing

I too have faced this problem. they assume the resolutions they give you will fix the problem then automatically close the case.

NOT the way to do things :(

__________________

www.DittoIT.co.uk
Backup & Disaster Recovery in the UK.

lumacor

Other software?

Is any other backup software in use on the endpoint? E.g. Veeam Endpoint Backup.

If not, is there any other backup software that is dormant or no longer configured and yet to be uninstalled?

__________________

StorageCraft Certified Master Engineer

Veeam Technical Sales Professional (v9)

lesterlilley

Other Software

No, there are two HP Desktop computers out of 45 that have the problem. One of them was brand new, and one about a year old. There is no other backup software installed. I actually have around 45 HP Desktops that are configured the same and just these two have the problem. I have narrowed it down to the C: partition, when I ran a backup on the recovery partition it worked normally, but when I run the backup on the C: partition it runs normally for a while and then the computer looses connection to the network for a few seconds and then re-connects, and the backup fails with an I/O Error. My only option that I see is to get a new hard drive and new copy of Windows, but I have not done it yet.

Thanks,

dbowen

The logs show that there is

The logs show that there is an issue with the VSS snapshotting, and there is a Microsoft error code present. 

Error code 0x800423F0

Are all volumes on the machines being backed up? Also, look to see that Shadow copies aren't causing conflicts. Definitely sounds like the issue is isolated to some software configured in certain ways on those two machines. How does vssadmin list writers look?

 

lesterlilley

Sorry for late response I was

Sorry for late response I was out on vacation. No all volumes are not backed up, we are only backing up the C: volume, but it has never had a successful backup. I tried backing up the other partition which is an HP restore partition and it backed up with no problems. The vssadmin writers are all good until the problem occurs and then there is an error on the ASR writer, but clears up. I am almost positive that the problem is with the C: partition on both machines, but I have ran all the chkdsk, etc.. that I can do to the drives and they have not fixed the issue. I think my only option is to format the drives and re-install windows but I have not made the move yet. Thanks for replying...

Terms and Conditions of Use - Privacy Policy - Cookies