Author |
Message |
kriemer Guest
|
Posted: Sun Apr 16, 2006 9:35 pm Post subject: Drive A:\ being accessed by VV ? |
|
|
Whenever VV backs-up or syncs, my "A:" drive is accessed. I find the buzzing irritating and as I do not have the "A:" drive as part of the VV profile I am confused by this behavour.
Any thoughts?
Thanks
k |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8761
|
|
Back to top |
|
|
K Riemer Guest
|
Posted: Mon Apr 17, 2006 3:13 am Post subject: |
|
|
I'm using VV2 Pro rel 2.0.10 |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8761
|
Posted: Mon Apr 17, 2006 8:40 am Post subject: |
|
|
should not happen... can you maybe try the program FileMon to see what file is accessed on the A drive ... you can download FileMon from http://www.sysinternals.com/Utilities/Filemon.html
Please first start ViceVersa. Then start FileMon (only after the ViceVersa main window is shown). Then click on "Compare", etc.
In FileMon you can filter to view activity only for the A: drive. If you can post the results of FileMon we can try to help. We only had one other customer before reporting this issue with the A: drive but we cannot reproduce this on our machines. thanks _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
kriemer Guest
|
Posted: Tue Apr 25, 2006 4:33 pm Post subject: I found the cause!! |
|
|
When VV is set to "Use Shadow Copy..." the "A:" drive is accessed. I'm not sure why this happens, but I am sure that the problem goes away when this feature is unpicked.
Any thoughts?
k |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8761
|
|
Back to top |
|
|
kriemer Guest
|
Posted: Sat Apr 29, 2006 2:17 am Post subject: A Drive |
|
|
Looking forward to hearing the results of your findings
Regards
k |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8761
|
Posted: Sun Apr 30, 2006 2:52 am Post subject: |
|
|
I tried on Win2003 and it does not happen. Are you using WinXP or Win2003?
Try this
From the command line (click Start->Run type cmd and press OK) type the following:
vssadmin list writers
This lists registered writers and their status. They should all be reported as stable. If some aren't listed as stable then there may be a problem with your Windows installation.
*** Please copy the list to this post ***
vssadmin list providers
There should be a list of at least one entry (MS Software Shadow Copy provider). If none are listed then there may be problem with your Windows installation.
*** Please copy the list to this post ***
thanks _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
kriemer Guest
|
Posted: Mon May 01, 2006 2:14 pm Post subject: Feedback |
|
|
I do not know if it matters but the "BOTH" ShadowCopy pulldown option was selected.
This is the results of the tests you asked for (results are the same when ShadowCopy is on or off):
======================
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\XYZ>vssadmin list writers
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Writer name: 'MSDEWriter'
Writer Id: {f8544ac1-0611-4fa5-b04b-f7ee00b03277}
Writer Instance Id: {4c7e9c4f-75c2-4abb-a85d-8ecb5c3b600c}
State: [1] Stable
Writer name: 'Microsoft Writer (Service State)'
Writer Id: {e38c2e3c-d4fb-4f4d-9550-fcafda8aae9a}
Writer Instance Id: {082c8a86-62a2-43b2-8754-e34671c2b806}
State: [1] Stable
Writer name: 'Microsoft Writer (Bootable State)'
Writer Id: {f2436e37-09f5-41af-9b2a-4ca2435dbfd5}
Writer Instance Id: {0bc23842-94cf-4d88-ad1d-1349b68c7f86}
State: [1] Stable
Writer name: 'WMI Writer'
Writer Id: {a6ad56c2-b509-4e6c-bb19-49d8f43532f0}
Writer Instance Id: {2b4b8d02-5ecd-4354-98e6-8c7a06f07bc7}
State: [1] Stable
C:\Documents and Settings\XYZ>vssadmin list providers
vssadmin 1.0 - Volume Shadow Copy Service administrative command-line tool
(C) Copyright 2001 Microsoft Corp.
Provider name: 'MS Software Shadow Copy provider 1.0'
Provider type: System
Provider Id: {b5946137-7b9f-4925-af80-51abd60b20d5}
Version: 1.0.0.7 |
|
Back to top |
|
|
TGRMN Software Site Admin
Joined: 10 Jan 2005 Posts: 8761
|
Posted: Thu May 04, 2006 2:06 am Post subject: |
|
|
We have further investigated this: it appears to be a known issue related to Microsoft's Volume Shadow Copy Service (VSS). VSS is the service that Viceversa PRO uses to backup open files, such as Outlook PST files.
As a test, if you run the command 'vssadmin list shadows', you will notice that also vssadmin accesses the A:\ drive as well in the same way was as ViceVersa software appears to do. This is a flaw in the VSS initialization code.
This behavior is annoying but does not cause any problems.
You can disable the use of VSS in ViceVersa, which will stop access to the a: drive, but you will not be able to backup open files. _________________ --
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com |
|
Back to top |
|
|
K Riemer Guest
|
Posted: Thu May 04, 2006 6:47 pm Post subject: Shadowcopy |
|
|
That's it.
My choice is to disable the ShadowCopy option. Others will make other decisions.
Thanks
k |
|
Back to top |
|
|
|