Currently the PhyLock cache is implemented on the volume being imaged... can this be moved to a different volume for the imaging operation (an .INI function maybe)?
Thanks in advance for your help with this...
Edit: we're investigating a HOT "All Sector" imaging operation for those that may not have enough RAM to provide for a decent PhyLock cache.
PhyLock.swp... is its location configurable?
Re: PhyLock.swp... is its location configurable?
<Knock, knock, knock...> TeraByte Support... anybody home?
It's been 2-weeks and I was hoping for some guidance. All I need is a YES or NO or (hopefully) a MAYBE.
Any help with this, greatly appreciated...
It's been 2-weeks and I was hoping for some guidance. All I need is a YES or NO or (hopefully) a MAYBE.
Any help with this, greatly appreciated...
-
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: PhyLock.swp... is its location configurable?
It currently uses the drive with the most free space. It would have to be
on the same physical drive even when on another volume. Something could be
added if there is some special need.
"Froggie" wrote in message news:9667@public.image...
TeraByte Support... anybody home?
![:o]({SMILIES_PATH}/icon_e_surprised.gif)
It's been 2-weeks and I was hoping for some guidance. All I need is a YES
or NO or (hopefully) a MAYBE.
Any help with this, greatly appreciated...
on the same physical drive even when on another volume. Something could be
added if there is some special need.
"Froggie" wrote in message news:9667@public.image...
TeraByte Support... anybody home?
![:o]({SMILIES_PATH}/icon_e_surprised.gif)
It's been 2-weeks and I was hoping for some guidance. All I need is a YES
or NO or (hopefully) a MAYBE.
Any help with this, greatly appreciated...
Re: PhyLock.swp... is its location configurable?
Uhhhh... one more question (below)...
Last edited by Froggie on Wed May 13, 2015 3:05 pm, edited 1 time in total.
Re: PhyLock.swp... is its location configurable?
Assuming this operation will be an ALL SECTOR image ("Backup unused sectors")...
Based on that, may I safely assume that if another volume shares the disk with the volume being imaged, AND has more FREE SPACE than the one being imaged, PhyLock will then select that 2nd VOLUME for the location of its cache (PhyLock.swp)?
Thanks in advance!
TeraByte Support wrote:
> It currently uses the drive with the most free space. It would have to
> be
> on the same physical drive even when on another volume. Something could be
>
> added if there is some special need.
Based on that, may I safely assume that if another volume shares the disk with the volume being imaged, AND has more FREE SPACE than the one being imaged, PhyLock will then select that 2nd VOLUME for the location of its cache (PhyLock.swp)?
Thanks in advance!
TeraByte Support wrote:
> It currently uses the drive with the most free space. It would have to
> be
> on the same physical drive even when on another volume. Something could be
>
> added if there is some special need.
Re: PhyLock.swp... is its location configurable?
Well... without a definitive answer I went ahead and tried what was explained above... a single disk with 2-partitions (C: & D:). Partition D: had the most FREE space. Imaged ("All unused sectors") partition C: using the following options...
GENERAL
UnCHECKed: "Automatic PHYlock RAM mode select"
PHYlock/VSS
UnCKECKed: "Use VSS if available" (made sure "Use Disk Storage" was selected)
PHYlock.swp was created on the C: partition (least amount of FREE space)... not what I expected.
Did I miss something? Any further guidance or help...?
GENERAL
UnCHECKed: "Automatic PHYlock RAM mode select"
PHYlock/VSS
UnCKECKed: "Use VSS if available" (made sure "Use Disk Storage" was selected)
PHYlock.swp was created on the C: partition (least amount of FREE space)... not what I expected.
Did I miss something? Any further guidance or help...?
-
- Posts: 3629
- Joined: Thu May 05, 2011 10:37 pm
Re: PhyLock.swp... is its location configurable?
No, it currently only considers the volumes in the backup.
"Froggie" wrote in message news:9675@public.image...
Assuming this operation will be an ALL SECTOR image ("Backup unused
sectors")...
Based on that, may I safely assume that if another volume shares the disk
with the volume being imaged, AND has more FREE SPACE than the one being
imaged, PhyLock will then select that 2nd VOLUME for the location of its
cache (PhyLock.swp)?
Thanks in advance!
TeraByte Support wrote:
> It currently uses the drive with the most free space. It would have to
> be
> on the same physical drive even when on another volume. Something could
> be
>
> added if there is some special need.
"Froggie" wrote in message news:9675@public.image...
Assuming this operation will be an ALL SECTOR image ("Backup unused
sectors")...
Based on that, may I safely assume that if another volume shares the disk
with the volume being imaged, AND has more FREE SPACE than the one being
imaged, PhyLock will then select that 2nd VOLUME for the location of its
cache (PhyLock.swp)?
Thanks in advance!
TeraByte Support wrote:
> It currently uses the drive with the most free space. It would have to
> be
> on the same physical drive even when on another volume. Something could
> be
>
> added if there is some special need.
Re: PhyLock.swp... is its location configurable?
OK, that answers everything!
Thanks for your help with this...
TeraByte Support wrote:
> No, it currently only considers the volumes in the backup.
Thanks for your help with this...
TeraByte Support wrote:
> No, it currently only considers the volumes in the backup.
Re: PhyLock.swp... is its location configurable?
Froggie wrote:
>
> PHYlock.swp was created on the C: partition (least amount of FREE space)...
> not what I expected.
>
I tried a "Backup unused sectors" of the C: drive. PHYLock.swp wasn't created at all. But I had a tick in "Automatic PHYlock RAM mode select". I thought you were trying to avoid having PHYLock.swp. I'm confused.
Edit... I get it now.
>
> PHYlock.swp was created on the C: partition (least amount of FREE space)...
> not what I expected.
>
I tried a "Backup unused sectors" of the C: drive. PHYLock.swp wasn't created at all. But I had a tick in "Automatic PHYlock RAM mode select". I thought you were trying to avoid having PHYLock.swp. I'm confused.
Edit... I get it now.