+x+x+xInteresting that VSS errors pertaining to a Q: drive are causing this backup to stumble even though you're not even trying to capture an image of that volume. As a potential quick fix, have you already tried the Other Tasks > Fix VSS Problems option within Reflect? Otherwise, is there some way of getting your Office installation to stop creating this virtual Q drive?
I have tried the Macrium Fix VSS option. No change.
I don't want to uninstall Office (obviously). The really frustrating thing is that the image file is right there as a tmp. It is a shame there is not a way to manually append an incremental to a set (just renaming it from tmp is no good, of course, as Reflect has no knowledge or record of it after the process fails.
Hi
VSS isn't the problem here. The error "Write operation failed - The process cannot access the file because it is being used by another process. " indicates that another process has exclusively locked the image file on the backup drive and prevented a write operation.
Are you runing any Anti-Virus software, if so please can you add 'ReflectBin.exe' and the backup target folder to any exclusions or whitelists.
The target folder is on another computer in the Homegroup. On the laptop (hosting Reflect in this case) I have a very light AV/A-malware using BitDefender Free. Being free it does not (appear) to offer any form of file exclusion, just a URL exclusion. (It would not be absolutely the end of the earth to uninstall that and see if it made any difference) On the computer hosting the location of the backup files I have put the folder hosting the backup files as an exclusion although not ReflectBin.exe as (of course) it is not on that machine.
One thing to mention (taking what you say fully on board) is when the backup DOES succeed (and up until now it usually has every 3-4-5th attempt---I haven't had any luck today, though) the VSS log does not feature any of these error messages for the Q drive. In fact no errors or warnings at all. Here is the VSS log for a successful backup. (follows). You say "not VSS" but wouldn't one expect those errors and warnings to still be present when the backup succeeds, if they were unrelated to the failure?
Thank you.
Mike
=============================
(Gathering writer metadata...)
(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
- Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
- Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
- Add component \PerformanceCounters
* Writer 'Registry Writer':
- Add component \Registry
* Writer 'COM+ REGDB Writer':
- Add component \COM+ REGDB
* Writer 'WMI Writer':
- Add component \WMI
Creating shadow set {0a1892d4-31d4-45f5-8067-275d61418e8a} ...
- Adding volume \\?\Volume{10b5181d-9400-11e1-9a76-806e6f6e6963}\ [C:\] to the shadow set...
- Adding volume \\?\Volume{ce5b7bc7-9b14-11e3-aad1-806e6f6e6963}\ [D:\] to the shadow set...
- Adding volume \\?\Volume{ce5b7bc8-9b14-11e3-aad1-806e6f6e6963}\ [E:\] to the shadow set...
Preparing for backup ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Shadow copy set succesfully created.
Saving the backup components document ...
List of created shadow copies:
Querying all shadow copies with the SnapshotSetID {0a1892d4-31d4-45f5-8067-275d61418e8a} ...
* SNAPSHOT ID = {85d0470f-6529-40ca-ab5e-194d5ca17b35} ...
- Shadow copy Set: {0a1892d4-31d4-45f5-8067-275d61418e8a}
- Original count of shadow copies = 3
- Original Volume name: \\?\Volume{10b5181d-9400-11e1-9a76-806e6f6e6963}\ [C:\]
- Creation Time: 1/3/2018 11:39:41 AM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy40
- Originating machine: PAVILIONG7
- Service machine: PAVILIONG7
- Not Exposed
- Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential
* SNAPSHOT ID = {fcfbf8f0-80b2-4dbc-b2b3-a75e038b1649} ...
- Shadow copy Set: {0a1892d4-31d4-45f5-8067-275d61418e8a}
- Original count of shadow copies = 3
- Original Volume name: \\?\Volume{ce5b7bc7-9b14-11e3-aad1-806e6f6e6963}\ [D:\]
- Creation Time: 1/3/2018 11:39:41 AM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy41
- Originating machine: PAVILIONG7
- Service machine: PAVILIONG7
- Not Exposed
- Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential
* SNAPSHOT ID = {1e09238b-9423-4382-9207-95d860c20ddd} ...
- Shadow copy Set: {0a1892d4-31d4-45f5-8067-275d61418e8a}
- Original count of shadow copies = 3
- Original Volume name: \\?\Volume{ce5b7bc8-9b14-11e3-aad1-806e6f6e6963}\ [E:\]
- Creation Time: 1/3/2018 11:39:41 AM
- Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy42
- Originating machine: PAVILIONG7
- Service machine: PAVILIONG7
- Not Exposed
- Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
- Attributes: Auto_Release Differential .