Phylock Cache Size Issue

[TeraByte Support]

Unless it's disabled, a log file is always written.

Let Windows sit for a few/several hours to finish its indexing (if you want
indexing) then things will probably be the same as normal.

>Still no log file. Will try /logl:50 switch tomorrow

[Brian K]

Alan,

Can I make a suggestion? Create a batch file to image the 4 partitions individually. Make the Bootcamp partition first in the list. You know PHYLock uses Disk if Bootcamp is imaged individually.

[AlanD]

On 2013-03-22 4:06 PM, TeraByte Support wrote:
> Unless it's disabled, a log file is always written.
>
> Let Windows sit for a few/several hours to finish its indexing (if you want
> indexing) then things will probably be the same as normal.
>
>> Still no log file. Will try /logl:50 switch tomorrow
>
>
You are right. It is inside the folder from which my batch file runs,
whereas the other day, I just ran imagew.exe manually, and of course Log
file was in Terabyte Program folder. I was expecting it to always show
up in TB folder, now I know better.

Log file shows (in two efforts to use VSS) that VSS Snapshot Creation
Failed, so that was of no help presumably when latest effort for full
image succeeded.

Would there be any harm in increasing RAM another 2048 kB, or
conversely, what about increasing DISK CACHE size from the 600MB default??

AlanD

[AlanD]

On 2013-03-22 4:10 PM, Brian K wrote:
> Alan,
>
> Can I make a suggestion? Create a batch file to image the 4 partitions individually. Make the Bootcamp partition first in the list. You know PHYLock uses Disk if Bootcamp is imaged individually.
>
>
The three remaining are: EFI partition (200 MB), OSX Recovery partition
(600 MB), OSX partition (313 GB).

Due to the size of two of them, I'll image the three together.

VSS is not working, so I'll delete that option.

BTW, not that it matters, but I have been using Verify only on all
attempts, not BFB.

Starting now -it's using RAM cache again.

Something screwy here:

It completed, but something very wrong here:
the total compressed file is about 19 GB, finished in 9+ minutes with
verify. OS X partition alone is 313 GB

[AlanD]

On 2013-03-22 4:10 PM, Brian K wrote:
> Alan,
>
> Can I make a suggestion? Create a batch file to image the 4 partitions individually. Make the Bootcamp partition first in the list. You know PHYLock uses Disk if Bootcamp is imaged individually.
>
>
here is log file of last three events
1) successful creation whole drive 1hr:30min
2) 1st image three Part w/o bootcamp 9min:40sec
3) 2nd image same as above, same reults
--------------------------------------------------------------------------


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

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

[2013-03-22 12:24:25 PM] Image for Windows 2.80 (GUI)
[2013-03-22 12:24:25 PM] Starting ...
imagew.exe /b /d:w0 /f:"F:\Backup-w0-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /v /comp:14
[2013-03-22 12:24:25 PM] Attempting to Create VSS Snapshot...
[2013-03-22 12:24:27 PM] VSS Snapshot Creation Failed (80042308h)
[2013-03-22 12:24:27 PM] PHYLock is waiting for drive writing to stop ...
[2013-03-22 12:24:41 PM] PHYLock Started
[2013-03-22 12:24:41 PM] PHYLock Using RAM
[2013-03-22 12:24:41 PM] PHYLock version 10
[2013-03-22 12:24:49 PM] Backup: Drive 0 EFI Partition (01) 200 MiB EFI System
[2013-03-22 12:24:49 PM] To: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 12:24:50 PM] INFO: Total Sectors:409600 Total Allocated:37582
[2013-03-22 12:24:50 PM] INFO: 37582 Sector(s) backed up
[2013-03-22 12:24:50 PM] Backup: Drive 0 (E:) Untitled 1 Partition (02) 312805 MiB OS X
[2013-03-22 12:24:50 PM] To: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 12:36:39 PM] INFO: Total Sectors:640625024 Total Allocated:56187224
[2013-03-22 12:36:39 PM] INFO: 56187224 Sector(s) backed up
[2013-03-22 12:36:39 PM] Backup: Drive 0 Recovery HD Partition (03) 620 MiB OS X
[2013-03-22 12:36:39 PM] To: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 12:36:47 PM] INFO: Total Sectors:1269536 Total Allocated:998232
[2013-03-22 12:36:47 PM] INFO: 998232 Sector(s) backed up
[2013-03-22 12:36:47 PM] Backup: Drive 0 (C:) BOOTCAMP Partition (04) 401778 MiB HPFS/NTFS
[2013-03-22 12:36:47 PM] To: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 1:22:17 PM] INFO: Total Sectors:822841344 Total Allocated:393935496
[2013-03-22 1:22:17 PM] INFO: 385976512 Sector(s) backed up
[2013-03-22 1:22:21 PM] Validating: EFI Partition (01) 200 MiB EFI System
[2013-03-22 1:22:21 PM] From: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 1:22:21 PM] Validating: Untitled 1 Partition (02) 312805 MiB OS X
[2013-03-22 1:22:21 PM] From: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 1:26:04 PM] Validating: Recovery HD Partition (03) 620 MiB OS X
[2013-03-22 1:26:04 PM] From: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 1:26:10 PM] Validating: BOOTCAMP Partition (04) 401778 MiB HPFS/NTFS
[2013-03-22 1:26:10 PM] From: F:\Backup-w0-2013-03-22-1224.TBI
[2013-03-22 2:04:34 PM] Operation Completed with Error Code 0
[2013-03-22 2:04:34 PM] Stop
--------------------------------------------------------------------------
[2013-03-22 6:00:13 PM] Image for Windows 2.80 (GUI)
[2013-03-22 6:00:13 PM] Starting ...
imagew.exe /b /d:w0@0x1,0x2,0x3 /f:"P:\Backup-w0-0x1-0x2-0x3-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /v /comp:14
[2013-03-22 6:00:13 PM] PHYLock is waiting for drive writing to stop ...
[2013-03-22 6:00:24 PM] PHYLock Started
[2013-03-22 6:00:24 PM] PHYLock Using RAM
[2013-03-22 6:00:24 PM] PHYLock version 10
[2013-03-22 6:00:32 PM] Backup: Drive 0 EFI Partition (01) 200 MiB EFI System
[2013-03-22 6:00:32 PM] To: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1759.TBI
[2013-03-22 6:00:32 PM] INFO: Total Sectors:409600 Total Allocated:37582
[2013-03-22 6:00:32 PM] INFO: 37582 Sector(s) backed up
[2013-03-22 6:00:32 PM] Backup: Drive 0 (E:) Untitled 1 Partition (02) 312805 MiB OS X
[2013-03-22 6:00:32 PM] To: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1759.TBI
[2013-03-22 6:06:35 PM] INFO: Total Sectors:640625024 Total Allocated:56187224
[2013-03-22 6:06:35 PM] INFO: 56187224 Sector(s) backed up
[2013-03-22 6:06:35 PM] Backup: Drive 0 Recovery HD Partition (03) 620 MiB OS X
[2013-03-22 6:06:35 PM] To: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1759.TBI
[2013-03-22 6:06:40 PM] INFO: Total Sectors:1269536 Total Allocated:998232
[2013-03-22 6:06:40 PM] INFO: 998232 Sector(s) backed up
[2013-03-22 6:06:42 PM] Validating: EFI Partition (01) 200 MiB EFI System
[2013-03-22 6:06:42 PM] From: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1759.TBI
[2013-03-22 6:06:42 PM] Validating: Untitled 1 Partition (02) 312805 MiB OS X
[2013-03-22 6:06:42 PM] From: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1759.TBI
[2013-03-22 6:09:34 PM] Validating: Recovery HD Partition (03) 620 MiB OS X
[2013-03-22 6:09:34 PM] From: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1759.TBI
[2013-03-22 6:09:35 PM] Operation Completed with Error Code 0
[2013-03-22 6:09:35 PM] Stop
--------------------------------------------------------------------------
[2013-03-22 6:33:26 PM] Image for Windows 2.80 (GUI)
[2013-03-22 6:33:26 PM] Starting ...
imagew.exe /b /d:w0@0x1,0x2,0x3 /f:"P:\Backup-w0-0x1-0x2-0x3-$~YYYY$-$~MM$-$~DD$-$~HHMM$" /v /comp:14
[2013-03-22 6:33:26 PM] PHYLock is waiting for drive writing to stop ...
[2013-03-22 6:33:37 PM] PHYLock Started
[2013-03-22 6:33:37 PM] PHYLock Using RAM
[2013-03-22 6:33:37 PM] PHYLock version 10
[2013-03-22 6:33:44 PM] Backup: Drive 0 EFI Partition (01) 200 MiB EFI System
[2013-03-22 6:33:44 PM] To: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1833.TBI
[2013-03-22 6:33:45 PM] INFO: Total Sectors:409600 Total Allocated:37582
[2013-03-22 6:33:45 PM] INFO: 37582 Sector(s) backed up
[2013-03-22 6:33:45 PM] Backup: Drive 0 (E:) Untitled 1 Partition (02) 312805 MiB OS X
[2013-03-22 6:33:45 PM] To: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1833.TBI
[2013-03-22 6:39:54 PM] INFO: Total Sectors:640625024 Total Allocated:56187224
[2013-03-22 6:39:54 PM] INFO: 56187224 Sector(s) backed up
[2013-03-22 6:39:54 PM] Backup: Drive 0 Recovery HD Partition (03) 620 MiB OS X
[2013-03-22 6:39:54 PM] To: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1833.TBI
[2013-03-22 6:39:59 PM] INFO: Total Sectors:1269536 Total Allocated:998232
[2013-03-22 6:39:59 PM] INFO: 998232 Sector(s) backed up
[2013-03-22 6:40:01 PM] Validating: EFI Partition (01) 200 MiB EFI System
[2013-03-22 6:40:01 PM] From: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1833.TBI
[2013-03-22 6:40:02 PM] Validating: Untitled 1 Partition (02) 312805 MiB OS X
[2013-03-22 6:40:02 PM] From: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1833.TBI
[2013-03-22 6:43:03 PM] Validating: Recovery HD Partition (03) 620 MiB OS X
[2013-03-22 6:43:03 PM] From: P:\Backup-w0-0x1-0x2-0x3-2013-03-22-1833.TBI
[2013-03-22 6:43:07 PM] Operation Completed with Error Code 0
[2013-03-22 6:43:07 PM] Stop

[TeraByte Support]

For VSS: http://www.terabyteunlimited.com/kb/article.php?id=461

For RAM mode: Page 37 of the manual talking about the log file size which
can eat up a lot of space.

If you can run at /logl:50 then perhaps it may show something (it may not).
It's taking less than a minute for PHYLock to start so doesn't seem like a
lot of writing going on.

If you don't include your Windows partition (or any Windows accessible
drive) then it will use RAM mode. It would only use disk mode if it can
find a drive on the same physical drive (will attempt to use the drive with
the most space). But in those cases with no drives, it should be fine
because Windows isn't altering them anyway. What if you get rid of the E:
drive mapping?



"AlanD" wrote in message news:5033@public.image...

On 2013-03-22 4:06 PM, TeraByte Support wrote:
> Unless it's disabled, a log file is always written.
>
> Let Windows sit for a few/several hours to finish its indexing (if you
> want
> indexing) then things will probably be the same as normal.
>
>> Still no log file. Will try /logl:50 switch tomorrow
>
>
You are right. It is inside the folder from which my batch file runs,
whereas the other day, I just ran imagew.exe manually, and of course Log
file was in Terabyte Program folder. I was expecting it to always show
up in TB folder, now I know better.

Log file shows (in two efforts to use VSS) that VSS Snapshot Creation
Failed, so that was of no help presumably when latest effort for full
image succeeded.

Would there be any harm in increasing RAM another 2048 kB, or
conversely, what about increasing DISK CACHE size from the 600MB default??

AlanD

[AlanD]

On 2013-03-23 1:38 AM, TeraByte Support wrote:
> For VSS: http://www.terabyteunlimited.com/kb/article.php?id=461
>
> For RAM mode: Page 37 of the manual talking about the log file size which
> can eat up a lot of space.
>
> If you can run at /logl:50 then perhaps it may show something (it may not).
> It's taking less than a minute for PHYLock to start so doesn't seem like a
> lot of writing going on.
>
> If you don't include your Windows partition (or any Windows accessible
> drive) then it will use RAM mode. It would only use disk mode if it can
> find a drive on the same physical drive (will attempt to use the drive with
> the most space). But in those cases with no drives, it should be fine
> because Windows isn't altering them anyway. What if you get rid of the E:
> drive mapping?
>
>
>
> "AlanD" wrote in message news:5033@public.image...
>
> On 2013-03-22 4:06 PM, TeraByte Support wrote:
>> Unless it's disabled, a log file is always written.
>>
>> Let Windows sit for a few/several hours to finish its indexing (if you
>> want
>> indexing) then things will probably be the same as normal.
>>
>>> Still no log file. Will try /logl:50 switch tomorrow
>>
>>
> You are right. It is inside the folder from which my batch file runs,
> whereas the other day, I just ran imagew.exe manually, and of course Log
> file was in Terabyte Program folder. I was expecting it to always show
> up in TB folder, now I know better.
>
> Log file shows (in two efforts to use VSS) that VSS Snapshot Creation
> Failed, so that was of no help presumably when latest effort for full
> image succeeded.
>
> Would there be any harm in increasing RAM another 2048 kB, or
> conversely, what about increasing DISK CACHE size from the 600MB default??
>
> AlanD
>
>
"If you don't include your Windows partition (or any Windows accessible
drive) then it will use RAM mode. It would only use disk mode if it can
find a drive on the same physical drive (will attempt to use the drive
withthe most space). But in those cases with no drives, it should be
fine because Windows isn't altering them anyway. What if you get rid
of the E: drive mapping?"

Not following you in your last paragraph above.
1) If I don't include Windows partition? I always include windows
partition, and it sure isn't using disk mode.
2) The next three sentences of yours totally baffle me. I can't even ask
the right questions to reply to them. Sorry, too dense here.

[AlanD]

On 2013-03-23 1:38 AM, TeraByte Support wrote:
> For VSS: http://www.terabyteunlimited.com/kb/article.php?id=461
>
> For RAM mode: Page 37 of the manual talking about the log file size which
> can eat up a lot of space.
>
> If you can run at /logl:50 then perhaps it may show something (it may not).
> It's taking less than a minute for PHYLock to start so doesn't seem like a
> lot of writing going on.
>
> If you don't include your Windows partition (or any Windows accessible
> drive) then it will use RAM mode. It would only use disk mode if it can
> find a drive on the same physical drive (will attempt to use the drive with
> the most space). But in those cases with no drives, it should be fine
> because Windows isn't altering them anyway. What if you get rid of the E:
> drive mapping?
>
>
>
> "AlanD" wrote in message news:5033@public.image...
>
> On 2013-03-22 4:06 PM, TeraByte Support wrote:
>> Unless it's disabled, a log file is always written.
>>
>> Let Windows sit for a few/several hours to finish its indexing (if you
>> want
>> indexing) then things will probably be the same as normal.
>>
>>> Still no log file. Will try /logl:50 switch tomorrow
>>
>>
> You are right. It is inside the folder from which my batch file runs,
> whereas the other day, I just ran imagew.exe manually, and of course Log
> file was in Terabyte Program folder. I was expecting it to always show
> up in TB folder, now I know better.
>
> Log file shows (in two efforts to use VSS) that VSS Snapshot Creation
> Failed, so that was of no help presumably when latest effort for full
> image succeeded.
>
> Would there be any harm in increasing RAM another 2048 kB, or
> conversely, what about increasing DISK CACHE size from the 600MB default??
>
> AlanD
>
>
I just made a full image using IFL, and feel a whole lot more confident
about that image than the few that completed using IFW. Not only that,
the total time to complete was roughly 1/2 that using IFW (when it
completed). Indicative to me of the fact that I do NOT want to make an
image using RAM cache, even though it is a pain running IFL.