TeraByte Unlimited

Phylock consistently waits for 10 minutes then seems to continue normally. Why the consistent wait since 1709 installation. Is phylock really working after the 10 minute delay?

Log:

[2017-11-21 12:10:07 AM] E:\Program Files (x86)\TeraByte Drive Image Backup and Restore Suite\TeraByte OSD Tool Suite Pro\win\IMAGEW64.EXE /ue /b /base:1@0x2:\2017-11-20-0009-Win10(SSD64)-(I)-.TBI /f:1@0x2:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-
[2017-11-21 12:10:08 AM] Image for Windows (x64) 3.13
[2017-11-21 12:10:08 AM] Starting ...
IMAGEW64.EXE /b /uy /u /sch:"I:\" /base:"I:\2017-11-20-0009-Win10(SSD64)-(I)-" /f:"I:\$~YYYY$-$~MM$-$~DD$-$~HHMM$-Win10(SSD64)-(I)-" /max:4GiB /v /comp:11 /hash
[2017-11-21 12:10:08 AM] PHYLock is waiting for drive writing to stop ...
[2017-11-21 12:20:13 AM] PHYLock using drive C:
[2017-11-21 12:20:13 AM] PHYLock Started
[2017-11-21 12:20:13 AM] PHYLock Using Disk
[2017-11-21 12:20:13 AM] PHYLock version 14
[2017-11-21 12:20:13 AM] Backup: Drive 3 (C:) Win10(SSD64) Partition (04) 59546 MiB NTFS
[2017-11-21 12:20:13 AM] To: I:\2017-11-21-0010-Win10(SSD64)-(I)-.TBI
[2017-11-21 12:22:53 AM] INFO: Total Sectors:121950208 Total Allocated:87835224
[2017-11-21 12:22:53 AM] INFO: 2065097 Sector(s) backed up
[2017-11-21 12:22:53 AM] Validating: Win10(SSD64) Partition (04) 59546 MiB NTFS
[2017-11-21 12:22:53 AM] From: I:\2017-11-21-0010-Win10(SSD64)-(I)-.TBI
[2017-11-21 12:22:58 AM] Time Elapsed: 0:00:12:50
[2017-11-21 12:22:58 AM] Operation Completed with Error Code 0
[2017-11-21 12:22:58 AM] Stop

Ten minutes is the default max wait time. PHYLock is still working after the delay. It just didn't find the "quiet" time it was looking for to start.

Is something running that is always accessing the partition? Has anything else changed (any programs, settings, etc.) since 1709 was installed? Have you tried reinstalling IFW (or just PHYLock) in case the upgrade affected it?

(Paul and I were replying at the same time).

As I understand it, It tries to wait until there is nothing writing to the disk/partition(s) being backed up. After a time out (10 minutes default), it performs its locking function even though writing is still taking place. I don't fully understand the implications of this but I try to avoid it.

I strongly suspect that something is writing to the disk during the entire 10 minutes. I don't know if there is a straightforward way to find out what.

I've had these symptoms twice. The first time, I started deleting installed applications and retrying the backup after deleting one or a few things. By this process of elimination, I determined that the wait would always time out if Secunia PSI was active so I stopped it being active and the problem went away.

More recently, I discovered that the symptoms seem to be present if the Chrome browser is active.

I also sometimes have this happen if I happen to create a backup when Windows Update is downloading an update, but that's probably not what's happening if the behavior is consistent.

My system auto backs up nightly whether attended or not. After the 1709 install was installed, I did a backup. That backup and all after started the phylock delay. I did uninstall and reinstall Phylock, and separately IFW. No changes. I noticed that 1709 activated hibernation and quick start, and put pagefile back on my SSD. Corrected all, but Phylock timeout still exists.

As long as Phylock is operational and data is being backed up correctly, I guess that I can live with the delay. While there is no delay with VSS, it appears that some files may not be synchronized correctly.

Thanks for the comments.

tas3086,

Run Procmon.exe from Sysinternals. It might show which process is blocking IFW from getting an early lock.

Correct, it's writes (changes) that it's waiting for to stop for the
configured time (default about 4 seconds if I recall correctly).


"Bob Coleman" wrote in message news:14409@public.image...

(Paul and I were replying at the same time).

As I understand it, It tries to wait until there is nothing writing to the
disk/partition(s) being backed up. After a time out (10 minutes default),
it performs its locking function even though writing is still taking place.
I don't fully understand the implications of this but I try to avoid it.

I strongly suspect that something is writing to the disk during the entire
10 minutes. I don't know if there is a straightforward way to find out
what.

I've had these symptoms twice. The first time, I started deleting installed
applications and retrying the backup after deleting one or a few things. By
this process of elimination, I determined that the wait would always time
out if Secunia PSI was active so I stopped it being active and the problem
went away.

More recently, I discovered that the symptoms seem to be present if the
Chrome browser is active.

I also sometimes have this happen if I happen to create a backup when
Windows Update is downloading an update, but that's probably not what's
happening if the behavior is consistent.