Jump to content

Backup Exec not talking to VSS on Windows Server 2003 R2


Recommended Posts

Guest deca2499
Posted

Hello all,

I am not really sure where to put this thread so here goes.

 

I have come into a company where they are having a problem backing up

one of

the domain controllers. I am seeing an error message ID# 13, Source:

VSS. It

is showing a username in the registry that is no longer valid. When I

go to

the properties of VSS it is showing to use the System account. My

problem is

this: 2 DC's, one getting a successful backup and the other is not.

Both have

the same error message, and both are configured the same from what I

can see.

Can someone help me with this issue? This is getting to be very

confusing.

 

Thank you in advance for all of your help.

  • Replies 1
  • Created
  • Last Reply
Guest deca2499
Posted

Re: Backup Exec not talking to VSS on Windows Server 2003 R2

 

On Jun 17, 1:33 pm, deca2499 <deca2...@gmail.com> wrote:

> Hello all,

> I am not really sure where to put this thread so here goes.

>

> I have come into a company where they are having a problem backing up

> one of

> the domain controllers. I am seeing an error message ID# 13, Source:

> VSS. It

> is showing a username in the registry that is no longer valid. When I

> go to

> the properties of VSS it is showing to use the System account. My

> problem is

> this: 2 DC's, one getting a successful backup and the other is not.

> Both have

> the same error message, and both are configured the same from what I

> can see.

> Can someone help me with this issue?  This is getting to be very

> confusing.

>

> Thank you in advance for all of your help.

 

After calling Symantec for support, I was able to find out that some

of the Writer metadata was not working correctly. Some of the Writers

were not started. A reboot took care of this. You can check on these

by opening a command prompt and entering "vssadmin list writers". All

the states should be Stable. My guess is this key is only used if you

use a username and password to kick off the service instead of the

System account, but it still checks the username if one is provided.

 

My question to everyone is, If I delete the username from the registry

key and leave it blank, what, if any effect will it have on the Volume

Shadow Copy Service?

 

Thank you.

 

Scott


×
×
  • Create New...