Volume Shadow Copy service stops on its own

[Guest randy]

On my file server, I repeatedly get information events in the event log

saying that the VSS service has entered a stopped state. Then a little while

later, says it entered a running state.

 

If the service is set to automatic, why does the service not continuously

run? Is it designed to only start when needed?

[Guest Iain]

RE: Volume Shadow Copy service stops on its own

 

Have you checked to see if the stop state and start time coincide with any

backup schedules ... it is common for this to happen at such a time.

--

Iain Marshall

MCSE MCSA MCPs MCP

 

 

"randy" wrote:

> On my file server, I repeatedly get information events in the event log

> saying that the VSS service has entered a stopped state. Then a little while

> later, says it entered a running state.

>

> If the service is set to automatic, why does the service not continuously

> run? Is it designed to only start when needed?

[Guest randy]

RE: Volume Shadow Copy service stops on its own

 

It does not coincide with backup schedules. This seems to happen at all times

of the day/night. Our network backups occur for a 2 hour window at night.

 

Could this happen when it does the snapshot of the drive?

 

"Iain" wrote:

> Have you checked to see if the stop state and start time coincide with any

> backup schedules ... it is common for this to happen at such a time.

> --

> Iain Marshall

> MCSE MCSA MCPs MCP

>

>

> "randy" wrote:

>

> > On my file server, I repeatedly get information events in the event log

> > saying that the VSS service has entered a stopped state. Then a little while

> > later, says it entered a running state.

> >

> > If the service is set to automatic, why does the service not continuously

> > run? Is it designed to only start when needed?

[Guest Iain]

RE: Volume Shadow Copy service stops on its own

 

Are you using Windows SBS, with no event ID showing error the Volume Shadow

Copy will start only when the volume shadow copy program is running. For

example, if you scheduled the backup tasks by

using the SBS backup wizard (the backup snap-in in the Server Management

console), you may see that the VSS service is running at the beginning of

the backup.

 

So, let's check the issue first:

 

Step 1. Check the Shadow Copies Schedule

========================

1. Click Start, right-click My Computer, and then click Manage.

2. Right-click Shared Folders, point to All Tasks, and then click Configure

Shadow Copies.

3. Click Settings->Schedule

4. Check the settings and select OK

 

You are loking for any shadow copied enable tasks .. does this resolve your

problem?

 

--

Iain Marshall

MCSE MCSA MCPs MCP

 

 

"randy" wrote:

> It does not coincide with backup schedules. This seems to happen at all times

> of the day/night. Our network backups occur for a 2 hour window at night.

>

> Could this happen when it does the snapshot of the drive?

>

> "Iain" wrote:

>

> > Have you checked to see if the stop state and start time coincide with any

> > backup schedules ... it is common for this to happen at such a time.

> > --

> > Iain Marshall

> > MCSE MCSA MCPs MCP

> >

> >

> > "randy" wrote:

> >

> > > On my file server, I repeatedly get information events in the event log

> > > saying that the VSS service has entered a stopped state. Then a little while

> > > later, says it entered a running state.

> > >

> > > If the service is set to automatic, why does the service not continuously

> > > run? Is it designed to only start when needed?

[Guest randy]

RE: Volume Shadow Copy service stops on its own

 

Just so we're all clear.

 

This is a Windows Server 2003 Stnd.

 

Backup Exec is the network backup program and it backs up this server every

day at 12am. The backup job typically runs about 30 minutes.

 

Volume Shadow copy service is scheduled to make backups of the volumes at

7am, 12pm and 3pm daily.

 

The events in the event viewer that tell me that the service have entered a

stop state (remember, this is only an information messages not a warning or

an error. This is why my believe is that Windows is stopping the service when

it has no work to do, the nature of this post was to either confirm or deny

that belief) will happen at ALL hours of the day.

 

I recieve the message at 5am, at 10am, at 11am at 1pm at 6pm at 7pm at 8pm

at 9pm at 10:29:30pm. (These are just examples not actual times) The event

does not in any way correspond with a Volume Shadow copy backup or a network

backup. Has it happened around those times, maybe. But it happens probably

8-15 times daily and there are only 4 backup time periods so it could not be

related to that.

 

"Iain" wrote:

> Are you using Windows SBS, with no event ID showing error the Volume Shadow

> Copy will start only when the volume shadow copy program is running. For

> example, if you scheduled the backup tasks by

> using the SBS backup wizard (the backup snap-in in the Server Management

> console), you may see that the VSS service is running at the beginning of

> the backup.

>

> So, let's check the issue first:

>

> Step 1. Check the Shadow Copies Schedule

> ========================

> 1. Click Start, right-click My Computer, and then click Manage.

> 2. Right-click Shared Folders, point to All Tasks, and then click Configure

> Shadow Copies.

> 3. Click Settings->Schedule

> 4. Check the settings and select OK

>

> You are loking for any shadow copied enable tasks .. does this resolve your

> problem?

>

> --

> Iain Marshall

> MCSE MCSA MCPs MCP

>

>

> "randy" wrote:

>

> > It does not coincide with backup schedules. This seems to happen at all times

> > of the day/night. Our network backups occur for a 2 hour window at night.

> >

> > Could this happen when it does the snapshot of the drive?

> >

> > "Iain" wrote:

> >

> > > Have you checked to see if the stop state and start time coincide with any

> > > backup schedules ... it is common for this to happen at such a time.

> > > --

> > > Iain Marshall

> > > MCSE MCSA MCPs MCP

> > >

> > >

> > > "randy" wrote:

> > >

> > > > On my file server, I repeatedly get information events in the event log

> > > > saying that the VSS service has entered a stopped state. Then a little while

> > > > later, says it entered a running state.

> > > >

> > > > If the service is set to automatic, why does the service not continuously

> > > > run? Is it designed to only start when needed?