SearchFAQMemberlist Log in
Reply to topic Page 1 of 1
Failed to create a VSS snapshot
Author Message
Post Failed to create a VSS snapshot 
Here hoping someone else has seen this error. This is only happening on Windows 2008 servers.

The System State fails with the following error:

“Description: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan.”

If I run the command vssadmin list writers, the writers are in a Failed state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it’s a Microsoft issue, we believe so as well. We will continue to escalate through Microsoft but I’m hoping someone else has experienced this.

The workaround is to reboot the servers and the writers are fine and backups are happy until they fail randomly. It’s not practical to keep rebooting these servers but that’s our workaround for now.

Any ideas?

Thanks!

Leslie

__._,_.___
Reply to sender ([email]LLopez < at > isd.lacounty.gov?subject=Re%3A%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (1)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4964/stime=1302909232/nc1=4507179/nc2=4025338/nc3=5758219[/img]
__,_._,___

Post Failed to create a VSS snapshot 
Any visible errors from VSS in your application/system event logs? On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez < at > isd.lacounty.gov[/email])> wrote:> Here hoping someone else has seen this error. This is only happening on Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a Failed state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We will continue to escalate through Microsoft but I'm hoping someone else has experienced this.

The workaround is to reboot the servers and the writers are fine and backups are happy until they fail randomly. It's not practical to keep rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie


__._,_.___
Reply to sender ([email]kaneda.san.sec < at > gmail.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (2)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4965/stime=1302909359/nc1=1/nc2=2/nc3=3[/img]
__,_._,___

Post Failed to create a VSS snapshot 
Oh yes, forgot to include that. At the time of the failure, the App log displays the following message. Another bit of information, these are all VM’s from the same image, sigh…..about 30 out there in production. Very random errors and we can’t pinpoint what triggers it. A theory that Microsoft had was that CommVault was not releasing the writer after the backup had completed. Eventually that would reach some threshold where it would cause the writers to fail. But CommVault stated clearly in the log that it is releasing the writers. “It’s not us, it’s them….” hehehehe

Log Name: Application
Source: VSS
Date: 4/14/2011 8:48:06 PM
Event ID: 12347
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. The Registry Writer failed to respond to a query from VSS. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.

Operation:
Gathering Writer Data
Executing Asynchronous Operation

Context:
Execution Context: Requestor
Current State: GatherWriterMetadata

From: commvault < at > yahoogroups.com [mailto:commvault < at > yahoogroups.com] On Behalf Of Luke
Sent: Friday, April 15, 2011 4:16 PM
To: commvault < at > yahoogroups.com
Subject: Re: [commvault] Failed to create a VSS snapshot




Any visible errors from VSS in your application/system event logs?
On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez < at > isd.lacounty.gov[/email])> wrote:
Here hoping someone else has seen this error. This is only happening on Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a Failed state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We will continue to escalate through Microsoft but I'm hoping someone else has experienced this.

The workaround is to reboot the servers and the writers are fine and backups are happy until they fail randomly. It's not practical to keep rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie







__._,_.___
Reply to sender ([email]LLopez < at > isd.lacounty.gov?subject=RE%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=RE%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (3)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4966/stime=1302909686/nc1=5191952/nc2=4507179/nc3=4025291[/img]
__,_._,___

Post Failed to create a VSS snapshot 
I also had this error on a new ms cluster and the fix was a miswritten path in the registry (wrong slash direction). Cv tech support did the fix so I can't be more specific.
-----Original Message-----
From: Leslie Lopez <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) <commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])>

Sent: 4/15/2011 4:21:00 PM
Subject: RE: [commvault] Failed to create a VSS snapshot

Oh yes, forgot to include that. At the time of the failure, the App log displays the following message. Another bit of information, these are all VM's from the same image, sigh.....about 30 out there in production. Very random errors and we can't pinpoint what triggers it. A theory that Microsoft had was that CommVault was not releasing the writer after the backup had completed. Eventually that would reach some threshold where it would cause the writers to fail. But CommVault stated clearly in the log that it is releasing the writers. "It's not us, it's them...." hehehehe

Log Name: Application
Source: VSS
Date: 4/14/2011 8:48:06 PM
Event ID: 12347
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. The Registry Writer failed to respond to a query from VSS. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.

Operation:
Gathering Writer Data
Executing Asynchronous Operation

Context:
Execution Context: Requestor
Current State: GatherWriterMetadata

From: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])] On Behalf Of Luke
Sent: Friday, April 15, 2011 4:16 PM
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])
Subject: Re: [commvault] Failed to create a VSS snapshot

Any visible errors from VSS in your application/system event logs?
On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])<mailto:llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>> wrote:
Here hoping someone else has seen this error. This is only happening on Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a Failed state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We will continue to escalate through Microsoft but I'm hoping someone else has experienced this.

The workaround is to reboot the servers and the writers are fine and backups are happy until they fail randomly. It's not practical to keep rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie

The information in this electronic mail communication (e-mail) contains confidential information which is the property of the sender and may be protected by the attorney-client privilege and/or attorney work product doctrine. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized by the sender. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this e-mail transmission or the taking or omission of any action in reliance thereon or pursuant thereto, is prohibited, and may be unlawful. If you received this e-mail in error, please notify us immediately of your receipt of this message by e-mail and destroy this communication, any attachments, and all copies thereof.
Southwest Gas Corporation does not guarantee the privacy or security of information transmitted by facsimile or other unsecure electronic means. By choosing to send or receive confidential or personal identifying information via facsimile or unencrypted e-mail, you consent to accept any associated risk.
Thank you for your cooperation.


__._,_.___
Reply to sender ([email]Bill.Willis < at > swgas.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (4)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4967/stime=1302909942/nc1=1/nc2=2/nc3=3[/img]
__,_._,___

Post Failed to create a VSS snapshot 
Hm, this might be worth checking out...

From http://support.microsoft.com/kb/907574

This problem occurs because the Location registry entry in the following registry subkey is incorrect or missing:

HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlContentIndexCatalogs


This problem occurs when you uninstall a program that is listed in this registry subkey, but only the location information is removed from the registry subkey.

Do you have any other servers that are backing up fine that you might be able to compare this registry key to?

Luke


On 16 April 2011 09:21, Leslie Lopez <llopez < at > isd.lacounty.gov ([email]llopez < at > isd.lacounty.gov[/email])> wrote:
 

Oh yes, forgot to include that.  At the time of the failure, the App log displays the following message.  Another bit of information, these are all VM’s from the same image, sigh…..about 30 out there in production.  Very random errors and we can’t pinpoint what triggers it.  A theory that Microsoft had was that CommVault was not releasing the writer after the backup had completed.  Eventually that would reach some threshold where it would cause the writers to fail.  But CommVault stated clearly in the log that it is releasing the writers.  “It’s not us, it’s them….” hehehehe
 
Log Name:      Application
Source:        VSS
Date:          4/14/2011 8:48:06 PM
Event ID:      12347
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      SERVER
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers.  The Registry Writer failed to respond to a query  from VSS. Please check to see that the Event Service and Volume Shadow Copy Service  are operating properly, and please check the Application event log for any other events.
 
Operation:
   Gathering Writer Data
   Executing Asynchronous Operation
 
Context:
   Execution Context: Requestor
   Current State: GatherWriterMetadata
 
From: commvault < at > yahoogroups.com ([email]commvault < at > yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault < at > yahoogroups.com[/email])] On Behalf Of Luke
Sent: Friday, April 15, 2011 4:16 PM
To: commvault < at > yahoogroups.com ([email]commvault < at > yahoogroups.com[/email])
Subject: Re: [commvault] Failed to create a VSS snapshot



 
 
Any visible errors from VSS in your application/system event logs?
On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez < at > isd.lacounty.gov[/email])> wrote:
Here hoping someone else has seen this error. This is only happening on Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a Failed state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We will continue to escalate through Microsoft but I'm hoping someone else has experienced this.

The workaround is to reboot the servers and the writers are fine and backups are happy until they fail randomly. It's not practical to keep rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie

















__._,_.___
Reply to sender ([email]kaneda.san.sec < at > gmail.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (5)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4968/stime=1302909969/nc1=1/nc2=2/nc3=3[/img]
__,_._,___

Post Failed to create a VSS snapshot 
Hey Bill,

Do you still have the TR#?   Leslie could give it to cv, who can go chase the original tech down and see what the fix was.

Luke

On 16 April 2011 09:25, Bill Willis <bill.willis < at > swgas.com ([email]bill.willis < at > swgas.com[/email])> wrote:
 
I also had this error on a new ms cluster and the fix was a miswritten path in the registry (wrong slash direction). Cv tech support did the fix so I can't be more specific.

-----Original Message-----
From: Leslie Lopez <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) <commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])>

Sent: 4/15/2011 4:21:00 PM
Subject: RE: [commvault] Failed to create a VSS snapshot

Oh yes, forgot to include that. At the time of the failure, the App log displays the following message. Another bit of information, these are all VM's from the same image, sigh.....about 30 out there in production. Very random errors and we can't pinpoint what triggers it. A theory that Microsoft had was that CommVault was not releasing the writer after the backup had completed. Eventually that would reach some threshold where it would cause the writers to fail. But CommVault stated clearly in the log that it is releasing the writers. "It's not us, it's them...." hehehehe

Log Name: Application
Source: VSS
Date: 4/14/2011 8:48:06 PM
Event ID: 12347
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. The Registry Writer failed to respond to a query from VSS. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.

Operation:
Gathering Writer Data
Executing Asynchronous Operation

Context:
Execution Context: Requestor
Current State: GatherWriterMetadata

From: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])] On Behalf Of Luke
Sent: Friday, April 15, 2011 4:16 PM
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])
Subject: Re: [commvault] Failed to create a VSS snapshot

Any visible errors from VSS in your application/system event logs?



On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])<mailto:llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>> wrote:
Here hoping someone else has seen this error. This is only happening on Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a Failed state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We will continue to escalate through Microsoft but I'm hoping someone else has experienced this.

The workaround is to reboot the servers and the writers are fine and backups are happy until they fail randomly. It's not practical to keep rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie



The information in this electronic mail communication (e-mail) contains confidential information which is the property of the sender and may be protected by the attorney-client privilege and/or attorney work product doctrine. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized by the sender. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this e-mail transmission or the taking or omission of any action in reliance thereon or pursuant thereto, is prohibited, and may be unlawful. If you received this e-mail in error, please notify us immediately of your receipt of this message by e-mail and destroy this communication, any attachments, and all copies thereof.
Southwest Gas Corporation does not guarantee the privacy or security of information transmitted by facsimile or other unsecure electronic means. By choosing to send or receive confidential or personal identifying information via facsimile or unencrypted e-mail, you consent to accept any associated risk.
Thank you for your cooperation.










__._,_.___
Reply to sender ([email]kaneda.san.sec < at > gmail.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (6)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4969/stime=1302910058/nc1=1/nc2=2/nc3=3[/img]
__,_._,___

Post Failed to create a VSS snapshot 
I'm not at my terminal. This is what my windows admin forwarded me this afternoon

There was a registry entry that had a mis-configured path. The path was something like.... c:/pathpathdjfa; it should have been c:pathpathdjfa; so there was a forward slash after c: instead of a back slash.

-----Original Message-----
From: Luke <kaneda.san.sec < at > gmail.com ([email]kaneda.san.sec%40gmail.com[/email])>
Cc: Willis, Bill <Bill.Willis < at > swgas.com ([email]Bill.Willis%40swgas.com[/email])>
Cc: <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>
To: <commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])>

Sent: 4/15/2011 4:27:30 PM
Subject: Re: [commvault] Failed to create a VSS snapshot

Hey Bill,

Do you still have the TR#? Leslie could give it to cv, who can go chase
the original tech down and see what the fix was.

Luke

On 16 April 2011 09:25, Bill Willis <bill.willis < at > swgas.com ([email]bill.willis%40swgas.com[/email])> wrote:



I also had this error on a new ms cluster and the fix was a miswritten path
in the registry (wrong slash direction). Cv tech support did the fix so I
can't be more specific.
-----Original Message-----
From: Leslie Lopez <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) <commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])>

Sent: 4/15/2011 4:21:00 PM
Subject: RE: [commvault] Failed to create a VSS snapshot

Oh yes, forgot to include that. At the time of the failure, the App log
displays the following message. Another bit of information, these are all
VM's from the same image, sigh.....about 30 out there in production. Very
random errors and we can't pinpoint what triggers it. A theory that
Microsoft had was that CommVault was not releasing the writer after the
backup had completed. Eventually that would reach some threshold where it
would cause the writers to fail. But CommVault stated clearly in the log
that it is releasing the writers. "It's not us, it's them...." hehehehe

Log Name: Application
Source: VSS
Date: 4/14/2011 8:48:06 PM
Event ID: 12347
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in
trying to contact shadow copy service writers. The Registry Writer failed to
respond to a query from VSS. Please check to see that the Event Service and
Volume Shadow Copy Service are operating properly, and please check the
Application event log for any other events.

Operation:
Gathering Writer Data
Executing Asynchronous Operation

Context:
Execution Context: Requestor
Current State: GatherWriterMetadata

From: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])] On
Behalf Of Luke
Sent: Friday, April 15, 2011 4:16 PM
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])
Subject: Re: [commvault] Failed to create a VSS snapshot

Any visible errors from VSS in your application/system event logs?
On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])<mailto:
llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>> wrote:
Here hoping someone else has seen this error. This is only happening on
Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in order
to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a Failed
state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We will
continue to escalate through Microsoft but I'm hoping someone else has
experienced this.

The workaround is to reboot the servers and the writers are fine and
backups are happy until they fail randomly. It's not practical to keep
rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie

The information in this electronic mail communication (e-mail) contains
confidential information which is the property of the sender and may be
protected by the attorney-client privilege and/or attorney work product
doctrine. It is intended solely for the addressee. Access to this e-mail by
anyone else is unauthorized by the sender. If you are not the intended
recipient, you are hereby notified that any disclosure, copying, or
distribution of the contents of this e-mail transmission or the taking or
omission of any action in reliance thereon or pursuant thereto, is
prohibited, and may be unlawful. If you received this e-mail in error,
please notify us immediately of your receipt of this message by e-mail and
destroy this communication, any attachments, and all copies thereof.
Southwest Gas Corporation does not guarantee the privacy or security of
information transmitted by facsimile or other unsecure electronic means. By
choosing to send or receive confidential or personal identifying information
via facsimile or unencrypted e-mail, you consent to accept any associated
risk.
Thank you for your cooperation.




The information in this electronic mail communication (e-mail) contains confidential information which is the property of the sender and may be protected by the attorney-client privilege and/or attorney work product doctrine. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized by the sender. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this e-mail transmission or the taking or omission of any action in reliance thereon or pursuant thereto, is prohibited, and may be unlawful. If you received this e-mail in error, please notify us immediately of your receipt of this message by e-mail and destroy this communication, any attachments, and all copies thereof.
Southwest Gas Corporation does not guarantee the privacy or security of information transmitted by facsimile or other unsecure electronic means. By choosing to send or receive confidential or personal identifying information via facsimile or unencrypted e-mail, you consent to accept any associated risk.
Thank you for your cooperation.


__._,_.___
Reply to sender ([email]Bill.Willis < at > swgas.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=Re%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (7)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4970/stime=1302910265/nc1=1/nc2=2/nc3=3[/img]
__,_._,___

Post Failed to create a VSS snapshot 
Thanks for the response Bill. If you can find the TR or the registry information that would be great!

Leslie

-----Original Message-----
From: Bill Willis [mailto:Bill.Willis < at > swgas.com ([email]Bill.Willis%40swgas.com[/email])]
Sent: Friday, April 15, 2011 4:31 PM
To: kaneda.san.sec < at > gmail.com ([email]kaneda.san.sec%40gmail.com[/email]); commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])
Cc: Leslie Lopez
Subject: Re: [commvault] Failed to create a VSS snapshot

I'm not at my terminal. This is what my windows admin forwarded me this afternoon

There was a registry entry that had a mis-configured path. The path was something like.... c:/pathpathdjfa; it should have been c:pathpathdjfa; so there was a forward slash after c: instead of a back slash.

-----Original Message-----
From: Luke <kaneda.san.sec < at > gmail.com ([email]kaneda.san.sec%40gmail.com[/email])>
Cc: Willis, Bill <Bill.Willis < at > swgas.com ([email]Bill.Willis%40swgas.com[/email])>
Cc: <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>
To: <commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])>

Sent: 4/15/2011 4:27:30 PM
Subject: Re: [commvault] Failed to create a VSS snapshot

Hey Bill,

Do you still have the TR#? Leslie could give it to cv, who can go chase
the original tech down and see what the fix was.

Luke

On 16 April 2011 09:25, Bill Willis <bill.willis < at > swgas.com ([email]bill.willis%40swgas.com[/email])> wrote:



I also had this error on a new ms cluster and the fix was a miswritten
path in the registry (wrong slash direction). Cv tech support did the
fix so I can't be more specific.
-----Original Message-----
From: Leslie Lopez <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) <commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])>

Sent: 4/15/2011 4:21:00 PM
Subject: RE: [commvault] Failed to create a VSS snapshot

Oh yes, forgot to include that. At the time of the failure, the App
log displays the following message. Another bit of information, these
are all VM's from the same image, sigh.....about 30 out there in
production. Very random errors and we can't pinpoint what triggers it.
A theory that Microsoft had was that CommVault was not releasing the
writer after the backup had completed. Eventually that would reach
some threshold where it would cause the writers to fail. But CommVault
stated clearly in the log that it is releasing the writers. "It's not
us, it's them...." hehehehe

Log Name: Application
Source: VSS
Date: 4/14/2011 8:48:06 PM
Event ID: 12347
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER
Description:
Volume Shadow Copy Service error: An internal inconsistency was
detected in trying to contact shadow copy service writers. The
Registry Writer failed to respond to a query from VSS. Please check to
see that the Event Service and Volume Shadow Copy Service are
operating properly, and please check the Application event log for any other events.

Operation:
Gathering Writer Data
Executing Asynchronous Operation

Context:
Execution Context: Requestor
Current State: GatherWriterMetadata

From: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])] On
Behalf Of Luke
Sent: Friday, April 15, 2011 4:16 PM
To: commvault < at > yahoogroups.com ([email]commvault%40yahoogroups.com[/email])
Subject: Re: [commvault] Failed to create a VSS snapshot

Any visible errors from VSS in your application/system event logs?
On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])<mailto:
llopez < at > isd.lacounty.gov ([email]llopez%40isd.lacounty.gov[/email])>> wrote:
Here hoping someone else has seen this error. This is only happening
on
Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in
order
to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a
Failed
state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We
will
continue to escalate through Microsoft but I'm hoping someone else has
experienced this.

The workaround is to reboot the servers and the writers are fine and
backups are happy until they fail randomly. It's not practical to keep
rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie

The information in this electronic mail communication (e-mail)
contains confidential information which is the property of the sender
and may be protected by the attorney-client privilege and/or attorney
work product doctrine. It is intended solely for the addressee. Access
to this e-mail by anyone else is unauthorized by the sender. If you
are not the intended recipient, you are hereby notified that any
disclosure, copying, or distribution of the contents of this e-mail
transmission or the taking or omission of any action in reliance
thereon or pursuant thereto, is prohibited, and may be unlawful. If
you received this e-mail in error, please notify us immediately of
your receipt of this message by e-mail and destroy this communication, any attachments, and all copies thereof.
Southwest Gas Corporation does not guarantee the privacy or security
of information transmitted by facsimile or other unsecure electronic
means. By choosing to send or receive confidential or personal
identifying information via facsimile or unencrypted e-mail, you
consent to accept any associated risk.
Thank you for your cooperation.




The information in this electronic mail communication (e-mail) contains confidential information which is the property of the sender and may be protected by the attorney-client privilege and/or attorney work product doctrine. It is intended solely for the addressee. Access to this e-mail by anyone else is unauthorized by the sender. If you are not the intended recipient, you are hereby notified that any disclosure, copying, or distribution of the contents of this e-mail transmission or the taking or omission of any action in reliance thereon or pursuant thereto, is prohibited, and may be unlawful. If you received this e-mail in error, please notify us immediately of your receipt of this message by e-mail and destroy this communication, any attachments, and all copies thereof.
Southwest Gas Corporation does not guarantee the privacy or security of information transmitted by facsimile or other unsecure electronic means. By choosing to send or receive confidential or personal identifying information via facsimile or unencrypted e-mail, you consent to accept any associated risk.
Thank you for your cooperation.


__._,_.___
Reply to sender ([email]LLopez < at > isd.lacounty.gov?subject=RE%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=RE%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (Cool
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4973/stime=1303137513/nc1=1/nc2=2/nc3=3[/img]
__,_._,___

Post Failed to create a VSS snapshot 
Thanks Luke! I looked at the reg key for both 2008 servers and the Catalogs key does not exist. The KB article looks like it’s specific to windows xp. The key does exist on my Windows xp box. Thanks for looking.

Leslie

From: Luke [mailto:kaneda.san.sec < at > gmail.com]
Sent: Friday, April 15, 2011 4:26 PM
To: commvault < at > yahoogroups.com
Cc: Leslie Lopez
Subject: Re: [commvault] Failed to create a VSS snapshot

Hm, this might be worth checking out...

From http://support.microsoft.com/kb/907574
This problem occurs because the Location registry entry in the following registry subkey is incorrect or missing:
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlContentIndexCatalogs

This problem occurs when you uninstall a program that is listed in this registry subkey, but only the location information is removed from the registry subkey.

Do you have any other servers that are backing up fine that you might be able to compare this registry key to?

Luke


On 16 April 2011 09:21, Leslie Lopez <llopez < at > isd.lacounty.gov ([email]llopez < at > isd.lacounty.gov[/email])> wrote:

Oh yes, forgot to include that. At the time of the failure, the App log displays the following message. Another bit of information, these are all VM’s from the same image, sigh…..about 30 out there in production. Very random errors and we can’t pinpoint what triggers it. A theory that Microsoft had was that CommVault was not releasing the writer after the backup had completed. Eventually that would reach some threshold where it would cause the writers to fail. But CommVault stated clearly in the log that it is releasing the writers. “It’s not us, it’s them….” hehehehe

Log Name: Application
Source: VSS
Date: 4/14/2011 8:48:06 PM
Event ID: 12347
Task Category: None
Level: Error
Keywords: Classic
User: N/A
Computer: SERVER
Description:
Volume Shadow Copy Service error: An internal inconsistency was detected in trying to contact shadow copy service writers. The Registry Writer failed to respond to a query from VSS. Please check to see that the Event Service and Volume Shadow Copy Service are operating properly, and please check the Application event log for any other events.

Operation:
Gathering Writer Data
Executing Asynchronous Operation

Context:
Execution Context: Requestor
Current State: GatherWriterMetadata

From: commvault < at > yahoogroups.com ([email]commvault < at > yahoogroups.com[/email]) [mailto:commvault < at > yahoogroups.com ([email]commvault < at > yahoogroups.com[/email])] On Behalf Of Luke
Sent: Friday, April 15, 2011 4:16 PM
To: commvault < at > yahoogroups.com ([email]commvault < at > yahoogroups.com[/email])
Subject: Re: [commvault] Failed to create a VSS snapshot




Any visible errors from VSS in your application/system event logs?
On 16-Apr-2011 9:13 AM, "Leslie Lopez" <llopez < at > isd.lacounty.gov ([email]llopez < at > isd.lacounty.gov[/email])> wrote:
Here hoping someone else has seen this error. This is only happening on Windows 2008 servers.

The System State fails with the following error:

"Description: Failed to create a VSS snapshot and it is required in order to run a system state backup. Failing the scan."

If I run the command vssadmin list writers, the writers are in a Failed state. Here is an example:

Writer name: 'IIS Metabase Writer'
Writer Id: {59b1f0cf-90ef-465f-9609-6ca8b2938366}
Writer Instance Id: {b1e90fd2-b5d0-406b-961e-6c33ed289ea1}
State: [7] Failed
Last error: No error

Writer name: 'IIS Config Writer'
Writer Id: {2a40fd15-dfca-4aa8-a654-1f8c654603f6}
Writer Instance Id: {0935df8b-cfd9-4625-a168-ce7a42f344ce}
State: [1] Stable
Last error: No error

Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {1ab9a3e1-b522-4430-9104-9bf2a3803092}
State: [7] Failed
Last error: No error

CommVault states it's a Microsoft issue, we believe so as well. We will continue to escalate through Microsoft but I'm hoping someone else has experienced this.

The workaround is to reboot the servers and the writers are fine and backups are happy until they fail randomly. It's not practical to keep rebooting these servers but that's our workaround for now.

Any ideas?

Thanks!

Leslie
















__._,_.___
Reply to sender ([email]LLopez < at > isd.lacounty.gov?subject=RE%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply to group ([email]commvault < at > yahoogroups.com?subject=RE%3A%20%5Bcommvault%5D%20Failed%20to%20create%20a%20VSS%20snapshot[/email]) | Reply via web post | Start a New Topic
Messages in this topic (9)
Recent Activity: Visit Your Group

Commvault Documentation here:
http://documentation.commvault.com/
MARKETPLACE

[url=http://global.ard.yahoo.com/SIG=15ors4ucb/M=493064.14543977.14365476.10835568/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1303144891/L=f327a066-69c9-11e0-b2fb-67c17b6729ef/B=wtEYO0oGYm8-/J=1303137691010097/K=O5P7977.jtivNRcra6wJhQ/A=6260316/R=0/SIG=11bc8n8gt/*http://custom.yahoo.com/fibromyalgiazone/]Find useful articles and helpful tips on living with Fibromyalgia. Visit the Fibromyalgia Zone today![/url] if(window.yzq_d==null)window.yzq_d=new Object(); window.yzq_d['wtEYO0oGYm8-']='&U=13ctq4tu0%2fN%3dwtEYO0oGYm8-%2fC%3d493064.14543977.14365476.10835568%2fD%3dMKP1%2fB%3d6260316%2fV%3d1'; [img]http://us.bc.yahoo.com/b?P=f327a066-69c9-11e0-b2fb-67c17b6729ef&T=1cg6e2sit%2fX%3d1303137691%2fE%3d1707277520%2fR%3dgroups%2fK%3d5%2fV%3d2.1%2fW%3dH%2fY%3dYAHOO%2fF%3d135655118%2fH%3dY29udGVudD0iR287V2lkZ2V0cztQb2RjYXN0cztNb2JpbGU7RmxpY2tyO0dyb3VwcztBdWN0aW9ucztTbWFsbF9CdXNpbmVzcztCcmllZmNhc2U7RmluYW5jZTsiIGRpc2FibGVzaHVmZmxpbmc9IjEiIHNlcnZlSWQ9ImYzMjdhMDY2LTY5YzktMTFlMC1iMmZiLTY3YzE3YjY3MjllZiIgc2l0ZUlkPSI0NDUyNTUxIiB0U3RtcD0iMTMwMzEzNzY5MDk5MjA3MyIg%2fQ%3d-1%2fS%3d1%2fJ%3d27228962&U=13ctq4tu0%2fN%3dwtEYO0oGYm8-%2fC%3d493064.14543977.14365476.10835568%2fD%3dMKP1%2fB%3d6260316%2fV%3d1[/img]

[url=http://global.ard.yahoo.com/SIG=15od7f2hc/M=493064.14543979.14365478.13298430/D=groups/S=1707277520:MKP1/Y=YAHOO/EXP=1303144891/L=f327a066-69c9-11e0-b2fb-67c17b6729ef/B=wNEYO0oGYm8-/J=1303137691010097/K=O5P7977.jtivNRcra6wJhQ/A=6060255/R=0/SIG=1194m4keh/*http://us.toolbar.yahoo.com/?.cpdl=grpj]Stay on top of your group activity without leaving the page you're on - Get the Yahoo! Toolbar now.[/url] if(window.yzq_d==null)window.yzq_d=new Object(); window.yzq_d['wNEYO0oGYm8-']='&U=13cqmq0jj%2fN%3dwNEYO0oGYm8-%2fC%3d493064.14543979.14365478.13298430%2fD%3dMKP1%2fB%3d6060255%2fV%3d1'; [img]http://us.bc.yahoo.com/b?P=f327a066-69c9-11e0-b2fb-67c17b6729ef&T=1cg8nc5bf%2fX%3d1303137691%2fE%3d1707277520%2fR%3dgroups%2fK%3d5%2fV%3d2.1%2fW%3dH%2fY%3dYAHOO%2fF%3d659523838%2fH%3dY29udGVudD0iR287V2lkZ2V0cztQb2RjYXN0cztNb2JpbGU7RmxpY2tyO0dyb3VwcztBdWN0aW9ucztTbWFsbF9CdXNpbmVzcztCcmllZmNhc2U7RmluYW5jZTsiIGRpc2FibGVzaHVmZmxpbmc9IjEiIHNlcnZlSWQ9ImYzMjdhMDY2LTY5YzktMTFlMC1iMmZiLTY3YzE3YjY3MjllZiIgc2l0ZUlkPSI0NDUyNTUxIiB0U3RtcD0iMTMwMzEzNzY5MDk5MjA3MyIg%2fQ%3d-1%2fS%3d1%2fJ%3d27228962&U=13cqmq0jj%2fN%3dwNEYO0oGYm8-%2fC%3d493064.14543979.14365478.13298430%2fD%3dMKP1%2fB%3d6060255%2fV%3d1[/img]


Text-Only ([email]commvault-traditional < at > yahoogroups.com?subject=Change Delivery Format: Traditional[/email]), Daily Digest ([email]commvault-digest < at > yahoogroups.com?subject=Email Delivery: Digest[/email]) &bull; Unsubscribe ([email]commvault-unsubscribe < at > yahoogroups.com?subject=Unsubscribe[/email]) &bull; Terms of Use




.

[img]http://geo.yahoo.com/serv?s=97359714/grpId=7450851/grpspId=1707277520/msgId=4974/stime=1303137690/nc1=5191952/nc2=4025304/nc3=4507179[/img]
__,_._,___

Display posts from previous:
Reply to topic Page 1 of 1
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
  


Magic SEO URL for phpBB