| Author |
Message |
Barry
Guest
|
Posted:
Mon Sep 12, 2005 3:28 pm Post subject:
vss issue |
|
|
Hi,
I get the following error whenever vss attmepts to creat a shadow copy:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12305
Date: 12/09/2005
Time: 11:14:44
User: N/A
Computer: STEALTH
Description:
Volume Shadow Copy Service error: Volume/disk not connected or not found.
Error context:
DeviceIoControl(\\?\Volume{9d67c321-ca18-40a1-84a5-342be1d8c67a} -
00000184,0x0053c008,00037590,0,000399D8,4096,[0]).
according to moutnvol that volume guid is correct. I've disabled and
renabled vss and there is only one scheduled task. i've installed any update
that i can find for vss. The server is 2003 sp1.
It makes no sense. It works fine for a day after its been rebooted, but
then refuses to create and copies the day after.
we are running TSM client on this server for backups, which does
occasionally come up with the error
"The shadow copies of volume C: were aborted because volume E:, which
contains shadow copy storage for this shadow copy, was force dismounted." E:
being the volume relating to that GUID above. It seems like VSS Still thinks
that the volume isnt mounted, even though it is (I can access it fine).
Any ideas?
thanks
Barry |
|
| Back to top |
|
 |
John Toner [MVP]
Guest
|
Posted:
Tue Sep 13, 2005 11:00 pm Post subject:
Re: vss issue |
|
|
Have you applied the VSS rollup hotfix? See
http://support.microsoft.com/kb/833167 for details.
Regards,
John
"Barry" <spamiittyspam@spammy.spam> wrote in message
news:ubTr6S4tFHA.464@TK2MSFTNGP15.phx.gbl...
| Quote: | Hi,
I get the following error whenever vss attmepts to creat a shadow copy:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12305
Date: 12/09/2005
Time: 11:14:44
User: N/A
Computer: STEALTH
Description:
Volume Shadow Copy Service error: Volume/disk not connected or not found.
Error context:
DeviceIoControl(\\?\Volume{9d67c321-ca18-40a1-84a5-342be1d8c67a} -
00000184,0x0053c008,00037590,0,000399D8,4096,[0]).
according to moutnvol that volume guid is correct. I've disabled and
renabled vss and there is only one scheduled task. i've installed any
update
that i can find for vss. The server is 2003 sp1.
It makes no sense. It works fine for a day after its been rebooted, but
then refuses to create and copies the day after.
we are running TSM client on this server for backups, which does
occasionally come up with the error
"The shadow copies of volume C: were aborted because volume E:, which
contains shadow copy storage for this shadow copy, was force dismounted."
E:
being the volume relating to that GUID above. It seems like VSS Still
thinks
that the volume isnt mounted, even though it is (I can access it fine).
Any ideas?
thanks
Barry
|
|
|
| Back to top |
|
 |
Barry
Guest
|
Posted:
Wed Sep 14, 2005 3:12 pm Post subject:
Re: vss issue |
|
|
Hi,
I haven't, no. The problems I'm seeing don't seem to be in the list of
things that are fixed, and it involves a call to PSS.
I'm semi-convinced it's actually a problem with the TSM client doing
something crazy, or being mis-configured. I didn't have this problem on the
test system. Though that also had TSM on it (same version) *shrugs*
Guess I could call PSS and get the patch anyway.
"John Toner [MVP]" <jtoner@DIE.SPAM.DIE.mvps.org> wrote in message
news:uQvla0IuFHA.3864@TK2MSFTNGP12.phx.gbl...
| Quote: | Have you applied the VSS rollup hotfix? See
http://support.microsoft.com/kb/833167 for details.
Regards,
John
"Barry" <spamiittyspam@spammy.spam> wrote in message
news:ubTr6S4tFHA.464@TK2MSFTNGP15.phx.gbl...
Hi,
I get the following error whenever vss attmepts to creat a shadow copy:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12305
Date: 12/09/2005
Time: 11:14:44
User: N/A
Computer: STEALTH
Description:
Volume Shadow Copy Service error: Volume/disk not connected or not found.
Error context:
DeviceIoControl(\\?\Volume{9d67c321-ca18-40a1-84a5-342be1d8c67a} -
00000184,0x0053c008,00037590,0,000399D8,4096,[0]).
according to moutnvol that volume guid is correct. I've disabled and
renabled vss and there is only one scheduled task. i've installed any
update
that i can find for vss. The server is 2003 sp1.
It makes no sense. It works fine for a day after its been rebooted, but
then refuses to create and copies the day after.
we are running TSM client on this server for backups, which does
occasionally come up with the error
"The shadow copies of volume C: were aborted because volume E:, which
contains shadow copy storage for this shadow copy, was force dismounted."
E:
being the volume relating to that GUID above. It seems like VSS Still
thinks
that the volume isnt mounted, even though it is (I can access it fine).
Any ideas?
thanks
Barry
|
|
|
| Back to top |
|
 |
Barry
Guest
|
Posted:
Wed Oct 05, 2005 4:17 pm Post subject:
Re: vss issue |
|
|
"Barry" <spamiittyspam@spammy.spam> wrote in message
news:ubTr6S4tFHA.464@TK2MSFTNGP15.phx.gbl...
| Quote: | Hi,
I get the following error whenever vss attmepts to creat a shadow copy:
Event Type: Error
Event Source: VSS
Event Category: None
Event ID: 12305
Date: 12/09/2005
Time: 11:14:44
User: N/A
Computer: STEALTH
Description:
Volume Shadow Copy Service error: Volume/disk not connected or not found.
Error context:
DeviceIoControl(\\?\Volume{9d67c321-ca18-40a1-84a5-342be1d8c67a} -
00000184,0x0053c008,00037590,0,000399D8,4096,[0]).
according to moutnvol that volume guid is correct. I've disabled and
renabled vss and there is only one scheduled task. i've installed any
update that i can find for vss. The server is 2003 sp1.
It makes no sense. It works fine for a day after its been rebooted, but
then refuses to create and copies the day after.
we are running TSM client on this server for backups, which does
occasionally come up with the error
"The shadow copies of volume C: were aborted because volume E:, which
contains shadow copy storage for this shadow copy, was force dismounted."
E: being the volume relating to that GUID above. It seems like VSS Still
thinks that the volume isnt mounted, even though it is (I can access it
fine).
Any ideas?
thanks
Barry
|
Just as a follow up to my own post for anyone else having the issue.
Installed a newer version of the TSM client and all appears to be working ok
now. |
|
| Back to top |
|
 |
|
|
|
|