TeraByte Unlimited

Just installed IFW/IFL 3.0c.

On my first attempt to backup the boot disk partitions using "Image for Windows (x64) 3.00c" IFW selected PHYLock. The result was "Error - Image for Windows" - 'Byte-for-Byte Comparison failed" " on the C: partition.

On my second attempt to backup the boot disk partitions I went into Image for Windows - Settings - PhyLock/VSS - PHYLock Settings and checked "Disable Usage". "VSS Settings" had "Use VSS When Available" checked. IFW would not take the backup. "Attempting to creat VSS snapshot" "Windows is locking volumes" "Warning - Image for Windows" "Unable to obtain lock on C: ..." - Abort/Retry/Ignore.

I ran other tests:

I took a backup of the boot disk partitions with IFL 3.0c using "Validate Byte-for-Byte" and had no problem.

I took a backup of the boot disk partitions with IFW 2.99-00 using VSS and "Validate Byte-for-Byte" and had no problem.

Windows 10 Home version 1511 (10586.545), 32GB memory.

Any suggestion on resolving the IFW 3.0C "Validate Byte-for-Byte" Issue?

Thanks

You'd still follow: http://www.terabyteunlimited.com/kb/article.php?id=151
(including chksk /f your partitions after running memory tests).

If VSS won't start, then you'll want to continue to use phylock.


"bob66412" wrote in message news:[email protected]...

Just installed IFW/IFL 3.0c.

On my first attempt to backup the boot disk partitions using "Image for
Windows (x64) 3.00c" IFW selected PHYLock. The result was "Error - Image
for Windows" - 'Byte-for-Byte Comparison failed" " on the C: partition.

On my second attempt to backup the boot disk partitions I went into Image
for Windows - Settings - PhyLock/VSS - PHYLock Settings and checked "Disable
Usage". "VSS Settings" had "Use VSS When Available" checked. IFW would not
take the backup. "Attempting to creat VSS snapshot" "Windows is locking
volumes" "Warning - Image for Windows" "Unable to obtain lock on C:
..." - Abort/Retry/Ignore.

I ran other tests:

I took a backup of the boot disk partitions with IFL 3.0c using "Validate
Byte-for-Byte" and had no problem.

I took a backup of the boot disk partitions with IFW 2.99-00 using VSS and
"Validate Byte-for-Byte" and had no problem.

Windows 10 Home version 1511 (10586.545), 32GB memory.

Any suggestion on resolving the IFW 3.0C "Validate Byte-for-Byte" Issue?

Thanks

Thank you for your reply.

I am pursuing issues with memory errors with G.Skill, but since these errors are Hammer Test errors, I don't know if it is possible to get a satisfactory resolution of that problem. Any suggestions would be welcome. (Note: My motherboard will not support ECC memory.) Is there DDR3 memory that is guaranteed to pass Hammer Tests?

I still don't understand why IFW 3.00C will not use VSS when IFW 2.99-00 will. What has changed?

Thanks

Do you have it configured to use it? What does the ifw.log say?


"bob66412" wrote in message news:[email protected]...

I still don't understand why IFW 3.00C will not use VSS when IFW 2.99-00
will. What has changed?

Thanks

I went through the VSS/PHYLock options and found that if I disabled IFW 3.00c VSS "Use component mode" that VSS will work.

Partial ifw.log shows two backups - the first has VSS "Use component mode" checked, the second has VSS "Use component mode" unchecked:

--------------------------------------------------------------------------
[8/16/2016 1:53:10 PM] Image for Windows (x64) 3.00c
[8/16/2016 1:53:10 PM] Starting ...
imagew64.exe /b /d:w3 /f:"D:\zzWinBackups\Backup-w3-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /max:4GiB /vb
[8/16/2016 1:53:10 PM] Attempting to Create VSS Snapshot...
[8/16/2016 1:53:10 PM] Added \\?\Volume{cd4cd9ee-0000-0000-0000-100000000000} to snapshot.
[8/16/2016 1:53:11 PM] Added \\?\Volume{cd4cd9ee-0000-0000-0000-501f00000000} (C:) to snapshot.
[8/16/2016 1:53:11 PM] VSS Snapshot Creation Failed (800423F4h)
[8/16/2016 1:53:11 PM] 00000000 - Task Scheduler Writer - Stable
[8/16/2016 1:53:11 PM] 00000000 - VSS Metadata Store Writer - Stable
[8/16/2016 1:53:11 PM] 00000000 - Performance Counters Writer - Stable
[8/16/2016 1:53:11 PM] 00000000 - Shadow Copy Optimization Writer - Stable (N/A)
[8/16/2016 1:53:11 PM] 800423F4 - ASR Writer - Stable
[8/16/2016 1:53:11 PM] 00000000 - BITS Writer - Stable (N/A)
[8/16/2016 1:53:11 PM] 00000000 - Registry Writer - Stable
[8/16/2016 1:53:11 PM] 00000000 - MSSearch Service Writer - Stable (N/A)
[8/16/2016 1:53:11 PM] 00000000 - WMI Writer - Stable
[8/16/2016 1:53:11 PM] 00000000 - COM+ REGDB Writer - Stable
[8/16/2016 1:53:13 PM] PHYLock is waiting for drive writing to stop ...
[8/16/2016 1:53:16 PM] Are you sure you want to cancel?
[8/16/2016 1:53:17 PM] PHYLock Failed to Start
[8/16/2016 1:53:17 PM] Deleting incomplete or failed backup.
[8/16/2016 1:53:17 PM] Operation Completed with Error Code 1
[8/16/2016 1:53:17 PM] Stop
--------------------------------------------------------------------------
[8/16/2016 1:53:59 PM] Image for Windows (x64) 3.00c
[8/16/2016 1:53:59 PM] Starting ...
imagew64.exe /b /d:w3 /f:"D:\zzWinBackups\Backup-w3-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /max:4GiB /vb
[8/16/2016 1:53:59 PM] Attempting to Create VSS Snapshot...
[8/16/2016 1:54:00 PM] Added \\?\Volume{cd4cd9ee-0000-0000-0000-100000000000} to snapshot.
[8/16/2016 1:54:01 PM] Added \\?\Volume{cd4cd9ee-0000-0000-0000-501f00000000} (C:) to snapshot.
[8/16/2016 1:54:03 PM] VSS Snapshot Created Successfully.
[8/16/2016 1:54:03 PM] Warning: Data excluded from files based on list in Registry.
[SYSTEM\CurrentControlSet\Control\BackupRestore\FilesNotToBackup]

...

--------------------------------------------------------------------------

I must have checked VSS "Use component mode" at some point.