Hi,
can you please clarify meaning of following note? The filesystem backup with "Use Shadow Copy" ticked, "Allow fallback" unticked, "Lock files during backup" unticked.
[Normal] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 15:48:09
STARTING Disk Agent for my.file.server:/Q "Q: [Network2]".
[Normal] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 15:48:11
VSS option was specified. Attempting to create snapshot.
[Normal] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 15:48:11
Entering snapshot definition phase.
[Normal] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 15:48:11
Volume 'Q:\' successfully added to snapshot set. The volume is now locked.
[Normal] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 15:48:11
Exiting snapshot definition phase.
[Normal] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 15:48:33
Creation of snapshot volume for Q:\ succeeded. Proceeding with backup.
[Normal] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 15:48:33
Clearing archive flags is not applicable with Volume Shadow Copy backup.
...
[Minor] From: VBDA@my.file.server "Q: [Network2]" Time: 9.9.2014 21:18:30
[81:93] GLOBALROOT\Device\HarddiskVolumeShadowCopy1085\some\folder\with\files\some.dll.deploy
File is shorter than it was when it was opened.
(was 142848 bytes, now 131072 bytes)
I have read the explanation in Trouble.txt but I did not expected this to happen when Volume Shadow Copy is used. With Volume Shadow Copy VBDA should read files out of the snapshot so nay modifications happening later should not matter. Also, as suggested by the Troubles.txt, using "Lock files during backup" will defeat purpose of Volume shadow Copy as it will interfere with users suing that file. BTW, does it lokc the file when backup starts or when the file is being backed up and lock is release immediately?
Kind regards, Jan