Has anyone seen this issue before - it's only started since upgrading to 6.1. It on a windows 2003 SP1 server with KB891957. Within the specification window I have "unticked" VSS enabled. We do not use VSS at all so would liek to disable the service but Replistor is trying to use it for something? Any ideas/pointers?
VSS is Volume Shadow Service which enables you to protect system files; can you explain the symptoms you are seeing here. What is Replistor doing at time of starting the service and of stopping the service?
Replistor is running as normal all day and the VSS service is still stopping and starting thats the issue I haven't got a clue why. 6.1 must be doing with VSS as described in the admin guide. How do you disable this In general, the RepliStor/VSS sequence of events that occurs in the creation of a shadow copy on the target is the following: 1. On the source side, the RepliStor Requestor (initiated via the RepliStor GUI) requests a VSS shadow copy. 2. VSS then asks the Exchange VSS Writer to freeze and flush all its I/O. 3. When this is completed, VSS asks the System Provider to take a shadow copy. 4. The RepliStor kernel interfaces with the VSS System Provider to determine when the I/O is that of a VSS shadow copy. This is the consistent data that is denoted by a marker which is passed to the target RepliStor server. 5. When the kernel marker is received at the target side, this indicates that the replicated data on the target is at the same state as the source at the time the data was frozen. This data is the consistent data for Exchange. 6. The target RepliStor server then optionally uses the RepliStor VSS Requestor to initiate a shadow copy on the target. 7. Once the shadow copy is on the target, the shadow copy can be mounted (if configured) and a user-supplied script can be run (if configured).
6.1.1 lists LGTpa85020 (The event log fills rapidly with VSS messages) as addressed. If you have the same issue peraps it is a different than original one so you will probably need to fill new escalation with support.
This issue has actually been resolved and will be in the next release verion of RepliStor. The LGTpa85020 you mentioned is different from the one described here.
Keep an out out for the software as RepliStor does not have patches to release.
DavidHampson
2 Intern
•
1080 Posts
352
0
Posted February 24th, 2006 08:00