TeraByte Unlimited

Going to try and explain this as best as possible...

This is the backup command we are using:
/b /uy /um /pldisk /pldcs:2048 /max:50GiB /email:*****SERVERNAME /d:w4@0x1 /v /vb

According to the IFW Manual, found here http://www.terabyteunlimited.com/downlo ... manual.pdf...and maybe I am reading this wrong but it says:
"/pldisk | PHYLockUseDisk=1
Use this option to instruct Image for Windows to attempt to use disk-based storage for the PHYLock cache with a size specified by the /pldcs parameter.
Using a value of 0 will disable this option (e.g. /pldisk:0).
Default if omitted: This option will be enabled."

If in my backup command I use "/pldisk" I receive the following error:
[ 3/21/2012 12:01:47 am] PHYLock Error 0002h [ 3/21/2012 12:01:47 am] Deleting incomplete or failed backup.
If you research "0002h" error you receive this: (website here http://www.terabyteunlimited.com/kb/article.php?id=551)
"A larger RAM Cache is needed. Increase the size of the RAM Cache Size (KB) option. The default size is 8192KB (8MB). It's recommended to increase the size by 1024KB - 2048KB (1MB - 2MB) at a time to see if it resolves the problem. For example, try an increase from 8192 to 10240. Do not use a value below 2048 for this setting. Also, see the note below. Additionally, if you have a Norton product installed, see PHYLock Errors when Norton LiveUpdate Runs."
This would be incorrect, if I am using "/pldisk" I should receive a error related to disk cache size NOT ram cache size.

Interestingly,

If I run my command again with "/pldisk:0" I receive the following error:
[ 3/22/2012 8:38:49 am] PHYLock Error 0003h [ 3/22/2012 8:38:49 am] Deleting incomplete or failed backup.
This is the error I expect to see when using "/pldisk" as according to the manual it would not be disabled. The error code for "0003h" says this:
"PHYLock Error 0003h - A larger Disk Cache is needed. Increase the size of the Disk Cache Size (MB) option. The default size is 600MB. It's recommended to increase the size by 512MB at a time to see if it resolves the problem. For example, try an increase from 600 to 1112. Also, see the note below."
Now this is the error I would expect to receive: given the manual tells me that using ":0" will disable the option of disk cache but clearly if I do not add :0 to the end then I receive a RAM cache error which should only appear when using "/pldisk:0" according to the manual.


So basically, I am confused as to what is really going on here...We receive the error to "Please increase the cache size in settings" but since we are using a command line then how do we go about increasing the cache size. Not to mention which options do we really use to set DISK cache and not RAM cache? is it "/pldisk:0" or "/pldisk." Also which is recommended RAM or Disk?

Send the sections of the log in play as it has more information about what's
happening (including version of IFW/PHYLock/etc..). Also more about the
system, OS, normal HD, SSD, etc..

PHYLock 8 has changed a lot from the prior versions. Which version of
IFW/PHYLock are you using?


Anyway,

3 means out of areas to save data, which when disk cache is enabled would be
the disk cache, when ram enabled, RAM.

2 means when in disk cache mode, the RAM cache filled up, which is used to
handle requests needing to be saved to the cache (intermediary buffer).

run chkdsk /f on the partitions to ensure clean or that can cause issues of
caching items that don't need caching.



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

Going to try and explain this as best as possible...

This is the backup command we are using:
/b /uy /um /pldisk /pldcs:2048 /max:50GiB /email:*****SERVERNAME /d:w4@0x1
/v /vb

According to the IFW Manual, found here
[url:3fpy1krj]http://www.terabyteunlimited.com/downloads/ifw_en_manual.pdf[/url:3fpy1krj]...and
maybe I am reading this wrong but it says:[color=#FF0000:3fpy1krj]
"/pldisk | PHYLockUseDisk=1
Use this option to instruct Image for Windows to attempt to use disk-based
storage for the PHYLock cache with a size specified by the /pldcs parameter.
Using a value of 0 will disable this option (e.g. /pldisk:0).
Default if omitted: This option will be enabled."[/color:3fpy1krj]

If in my backup command I use "/pldisk" I receive the following error:
[color=#FF0000:3fpy1krj][ 3/21/2012 12:01:47 am] PHYLock Error 0002h [
3/21/2012 12:01:47 am] Deleting incomplete or failed
backup.[/color:3fpy1krj]
If you research "0002h" error you receive this: (website here

[
http://www.terabyteunlimited.com/kb/article.php?id=551
](http://www.terabyteunlimited.com/kb/article.php?id=551)

)
[color=#FF0000:3fpy1krj]"A larger RAM Cache is needed. Increase the size of
the RAM Cache Size (KB) option. The default size is 8192KB (8MB). It's
recommended to increase the size by 1024KB - 2048KB (1MB - 2MB) at a time to
see if it resolves the problem. For example, try an increase from 8192 to
10240. Do not use a value below 2048 for this setting. Also, see the note
below. Additionally, if you have a Norton product installed, see PHYLock
Errors when Norton LiveUpdate Runs."[/color:3fpy1krj]
This would be incorrect, if I am using "/pldisk" I should receive a error
related to disk cache size NOT ram cache size.

Interestingly,

If I run my command again with "/pldisk:0" I receive the following error:
[color=#FF0000:3fpy1krj][ 3/22/2012 8:38:49 am] PHYLock Error 0003h [
3/22/2012 8:38:49 am] Deleting incomplete or failed
backup.[/color:3fpy1krj]
This is the error I expect to see when using "/pldisk" as according to the
manual it would not be disabled. The error code for "0003h" says this:
[color=#FF0000:3fpy1krj]"PHYLock Error 0003h - A larger Disk Cache is
needed. Increase the size of the Disk Cache Size (MB) option. The default
size is 600MB. It's recommended to increase the size by 512MB at a time to
see if it resolves the problem. For example, try an increase from 600 to
1112. Also, see the note below."[/color:3fpy1krj]
Now this is the error I would expect to receive: given the manual tells me
that using ":0" will disable the option of disk cache but clearly if I do
not add :0 to the end then I receive a RAM cache error which should only
appear when using "/pldisk:0" according to the manual.


So basically, I am confused as to what is really going on here...We receive
the error to "Please increase the cache size in settings" but since we are
using a command line then how do we go about increasing the cache size. Not
to mention which options do we really use to set DISK cache and not RAM
cache? is it "/pldisk:0" or "/pldisk." Also which is recommended RAM or
Disk?

Thank you for your quick reply. As for the numbers you gave me 2 and 3 I assume you are referring to the error codes for PhyLock. if so can you please explain how that seems very different from your websites approach to these error codes? The website is located here: http://www.terabyteunlimited.com/kb/article.php?id=551 According to your site 2 deals with RAM cache and 3 deals with Disk Cache.

Also, please provide an explanation as to the proper usage of "pldisk" and its counterpart, "pldcs." I would like to know exactly how this works as the manual offered by TeraByte is incorrect.

As for the failing backup I have tried many different setups to try and resolve, previously it was working with the command I gave you in the earlier post. When it suddenly stopped is when I investigated further and found that the explanation for pldisk does not meet the error codes we are receiving.

Here is the log file you have requested:
Thanks again for the help!

Hello,

The manual is ocrrect. The KB article just needed to reflect that 3 refers
to the disk cache when disk cache active, RAM cache when RAM active. Error
2 only occurs when disk cache is active but runs out of the RAM cache (used
internally). So, you should first do "chkdsk /f", next you should update to
the latest 2.70 version, 2.51 is pretty old. You can probably knock down
the Disk Cache to more like 1024 or 2048 (larger disk cache also takes
larger RAM area).

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

Thank you for your quick reply. As for the numbers you gave me 2 and 3 I
assume you are referring to the error codes for PhyLock. if so can you
please explain how that seems very different from your websites approach to
these error codes? The website is located here:

[
http://www.terabyteunlimited.com/kb/article.php?id=551
](http://www.terabyteunlimited.com/kb/article.php?id=551)

According to your site 2 deals with RAM cache and 3 deals with Disk Cache.

Also, please provide an explanation as to the proper usage of "pldisk" and
its counterpart, "pldcs." I would like to know exactly how this works as
the manual offered by TeraByte is incorrect.

As for the failing backup I have tried many different setups to try and
resolve, previously it was working with the command I gave you in the
earlier post. When it suddenly stopped is when I investigated further and
found that the explanation for pldisk does not meet the error codes we are
receiving.

Here is the log file you have requested:

[code:3cdi11oy]--------------------------------------------------------------------------
[ 3/22/2012 9:59:43 am] /b /uy /um /pldisk /pldcs:2048/email:EMAIL
ADDRESS*SERVERNAME/base:\\SERVERNAME\mnt\images\IFW\SERVERNAME\NAME_2012-03-16-0000__FULL
/f:\\SERVERNAME\mnt\images\IFW\SERVERNAME\SERVERNAME_2012-03-16-0000_DIFF_$~YYYY$-$~MM$-$~DD$-$~HHMM$[
3/22/2012 9:59:43 am] Image for Windows 2.51 (GUI) [ 3/22/2012 9:59:43 am]
Starting ...
[ 3/22/2012 9:59:43 am] imagew /b
/base:"\\ids-te-02\mnt\images\IFW\SERVERNAME\SERVERNAME_2012-03-16-0000__FULL"[
3/22/2012 9:59:43 am] PHYLock is waiting for drive writing to stop ...
[ 3/22/2012 10:00:29 am] PHYLock Started [ 3/22/2012 10:00:29 am] PHYLock
Using RAM [ 3/22/2012 10:00:29 am] PHYLock version 5 [ 3/22/2012 10:00:29
am] Backup: Drive 4 (C:) System Partition (01) 96581 MiB HPFS/NTFS [
3/22/2012 10:00:29 am] To:
\\SERVERNAME\mnt\images\IFW\SERVERNAME3\SERVERNAME_2012-03-16-0000_DIFF_2012-03-22-0959.TBI
[ 3/22/2012 10:08:30 am] PHYLock Error 0003h [ 3/22/2012 10:08:30 am] INFO:
Total Sectors:197798368 Total
Allocated:128905072
[ 3/22/2012 10:08:30 am] PHYLock Error 0003h [ 3/22/2012 10:08:30 am]
Deleting incomplete or failed backup.
[ 3/22/2012 10:08:30 am] Operation Completed with Error Code 204 [ 3/22/2012
10:08:30 am] PHYLock failed to cache all changes. Please increase the cache
size in settings.
[ 3/22/2012 10:08:30 am] Stop
[/code:3cdi11oy]

Thanks again for the help!

Thank you for the reply. I am not sure I agree with you saying the manual is correct given that the errors read out different for each and using pldisk:0 does not actually disable it as the manual says. But to move on and be productive here, is PHYLock version 5 supported with Windows 2008? When I attempt to run a backup I will receive:

Unsupported PHYLock version 5

It does, look in the IFW.LOG .. it will say "Using RAM" instead of "Using
Disk".

Yes, but the version of IFW requires a newer version of PHYLock, when you
upgrade, ensure you choose to install/upgrade phylock at the same time
(check box), then when it asks to reboot at the end, ensure you reboot or
the old one is still being used.

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

Thank you for the reply. I am not sure I agree with you saying the manual
is correct given that the errors read out different for each and using
pldisk:0 does not actually disable it as the manual says. But to move on
and be productive here, is PHYLock version 5 supported with Windows 2008?
When I attempt to run a backup I will receive:

Unsupported PHYLock version 5

Thanks for the reply. After rebooting it was updated to Version 6. Increasing the size seems to have worked for some of our machines although we continue to get a few other errors which I have posted elsewhere on this forum.

The solution then is to simply reboot the machine and ensuring PHYlock version 6 is installed.

PHYLock is up to version 8 now.

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

Thanks for the reply. After rebooting it was updated to Version 6.
Increasing the size seems to have worked for some of our machines although
we continue to get a few other errors which I have posted elsewhere on this
forum.

The solution then is to simply reboot the machine and ensuring PHYlock
version 6 is installed.