V-79-32772-8980

[Inventino]

I have problem when backup with open file, the error as below:

I used Advance open file option : Microsoft Volume Shadow Copy Service,Snapshot provider(Automatic-Allow VSS to select the snapshot provider)

*********************************************************************************************************************

Backup- \\server1\Shadow?Copy?Components - VSS Writer File System
V-79-57344-34110 - AOFO: Initialization failure on: "\\server1\System?State". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS).
VSS Snapshot error. Activity on a volume is preventing all volumes from being snapped. Try selecting the option 'Process logical volumes for backup, one at a time' , and then run the job again.

Event log from windows:

Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12298
Date: 3/3/2009
Time: 9:13:46 PM
User: N/A
Computer:  Server1
Description:
Volume Shadow Copy Service error: The I/O writes cannot be held during the shadow copy creation period on volume \\?\Volume{d62ffc4c-57db-11dd-98d8-806e6f6e6963}\. The volume index in the shadow copy set is 0. Error details: Open[0x00000000], Flush[0x00000000], Release[0x80042314], OnRun[0x00000000].

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 2d 20 43 6f 64 65 3a 20 - Code: 
0008: 43 4f 52 4c 4f 56 4c 43 CORLOVLC
0010: 30 30 30 30 30 39 36 34 00000964
0018: 2d 20 43 61 6c 6c 3a 20 - Call: 
0020: 43 4f 52 4c 4f 56 4c 43 CORLOVLC
0028: 30 30 30 30 30 38 36 36 00000866
0030: 2d 20 50 49 44 3a 20 20 - PID:  
0038: 30 30 30 30 35 39 38 38 00005988
0040: 2d 20 54 49 44 3a 20 20 - TID:  
0048: 30 30 30 30 36 30 35 36 00006056
0050: 2d 20 43 4d 44 3a 20 20 - CMD:  
0058: 43 3a 5c 57 49 4e 44 4f C:\WINDO
0060: 57 53 5c 53 79 73 74 65 WS\Syste
0068: 6d 33 32 5c 76 73 73 76 m32\vssv
0070: 63 2e 65 78 65 20 20 20 c.exe  
0078: 2d 20 55 73 65 72 3a 20 - User: 
0080: 4e 54 20 41 55 54 48 4f NT AUTHO
0088: 52 49 54 59 5c 53 59 53 RITY\SYS
0090: 54 45 4d 20 20 20 20 20 TEM  
0098: 2d 20 53 69 64 3a 20 20 - Sid:  
00a0: 53 2d 31 2d 35 2d 31 38 S-1-5-18

*********************************************************************************************************************

This is daily backup job. Backup job will be failed for someday.

Please advice me,How to fix this problem?

For more information:

OS: Windows 2003 SP2R2 Std

Backup Exec: 12.0 sp2

[Mirror]

Hello, I have the same with BE 12.0 SP3.
This error is happening almost every day. 
I have this problem  for more than 8 months, I created a case at Symantec and Microsoft.  
Neither company could give me solution to my problem. You could solve this problem?

Best, regard.

[T35216]

Hi, I am also experiencing with version 11d SP3, it only recently surfaced, The affected server is a domain controller if this is of any relevance.  Can somebody from Symantec comment on this is it a known issue and are you trying to resolve this

[Matt34]

I am also getting this error randomly on a nightly job.  I am using version 12.5

[jlehrhoff]

Been trying to find a solution for this as well. Using the most current 12.5

Funny that V-79-32772-8980 doesn't bring up anything in Symantec's KB

Also funny that I don't even have AOFO enabled

Not "ha ha" funny either

[coolsuny]

Hi,

Let me try,


1)from cmd prompt check for the VSS writer status by VSSadmin list writers, all the writers should give the "state: Stable and Last error: No error"

if any writer status is different  than this then the the server of  which the backup is failing should be rebooted to fix the issue with the writers (in most cases)

The ideal vss writers status should be as below for a successful backup.

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: {00450973-1f3a-4afd-84b6-b1257e42f2e0}
   State: [1] Stable
   Last error: No error

Writer name: 'Registry Writer'
   Writer Id: {afbab4a2-367d-4d15-a586-71dbb18f8485}
   Writer Instance Id: {d9a11119-af36-40fc-8f4f-cc0df2409bf6}
   State: [1] Stable
   Last error: No error

Writer name: 'Event Log Writer'
   Writer Id: {eee8c692-67ed-4250-8d86-390603070d00}
   Writer Instance Id: {d9d2d620-8ff1-438f-a87e-63301d7746bc}
   State: [1] Stable
   Last error: No error

Writer name: 'COM+ REGDB Writer'
   Writer Id: {542da469-d3e1-473c-9f4f-7847f01fc64f}
   Writer Instance Id: {f6be985c-8c1c-4e22-992f-b8c9d283679c}
   State: [1] Stable
   Last error: No error

Writer name: 'IIS Metabase Writer'
   Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
   Writer Instance Id: {9506aec4-e43c-4827-a4af-844e8209042c}
   State: [1] Stable
   Last error: No error

Writer name: 'WMI Writer'
   Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
   Writer Instance Id: {13702ed5-47c3-426f-94f9-db0a00c8a1b6}
   State: [1] Stable
   Last error: No error

Writer name: 'BITS Writer'
   Writer Id: {4969d978-be47-48b0-b100-f328f07ac1e0}
   Writer Instance Id: {6ed1de67-92a1-4e71-bf8c-d6c846354271}
   State: [1] Stable
   Last error: No error


2) make the VSS service startup type in services.msc to 'Manual'

[jlehrhoff]

Yeah, the vssadmin list writers command shows no errors... I already installed the VSS rollup version 3 package KB940349

There was also an article which mentioned uninstalling a Backup Exec hotfix (in another thread I am involved in) but that didn't work either... Really annoying because basically my backups are succesful but show as failed every other job or so because of this...

I wish Symantec would fix this or at least point to what exactly the MS VSS issue is...

[jlehrhoff]

Would be great if Backup Exec jobs could report as successful for like a whole month. I haven't had this experience in 10 years and have seen this software in quite a few different environments...
Like I said in an earlier post, already installed the hotfix... I think I have done this already but will see if re-registering all the VSS dlls will help

net stop vss

Register the following DLLs and services (be sure you're still in

the WINDOWS\system32 directory at your command prompt):

regsvr32 ole32.dll

regsvr32 vss_ps.dll

Vssvc /Register

regsvr32 /i swprv.dll

regsvr32 /i eventcls.dll

regsvr32 es.dll

regsvr32 stdprov.dll

regsvr32 vssui.dll

regsvr32 msxml.dll

regsvr32 msxml3.dll

regsvr32 msxml4.dll

Start the Volume Shadow Copy service by running "net start vss"

REALLY wish Symantec would step up to the plate and give some support here...

[SirNemesis]

Has anyone had any luck resolving this problem? I've had the same issue occuring on an SBS2003 server, which seems to work once after a server restart but then fail the next day(s).

Backup Exec 12.0 SP3. I'm running KB940349 and I've tried re-registering all DLL's as mentioned above without success.

[WhosYourSeanie]

I'm at the point where I'd just like to see symantec's crap work for a whole week!! It's been a L O N G time since that has happened. Is there a better solution out there than Symantec Backup Exec. This is a miserable piece of software and having to call or contact support all the time got old a long time ago. Currently I'm using support where we email back and forth, but it's like they email. I email back... wait a day.... wait another day... and another day... (I'm still waiting by the way) and they eventually email back to request some other log file or some other additional information. They've created this software to be such a piece of crap that even their support personnel don't know how to get it to run properly.

[WhosYourSeanie]

I just did the command line doohicky and everything reports back Stable - No Error. What other kind of "magic" should we be trying with this POS?