Discussion in 'backup, imaging & disk mgmt' started by TheKid7, Aug 19, 2011.
...something this gentleman can clearly do at times
LOL, all gentlemen and bad boys do at times. Gentlewomen and nice ladies don't because they don't use disk imaging software.
Froggie is teasing me as he is aware of some of my mis adventures.
This one does
Way to go Stapp.
Thanks guys - I follow this tread with interest, so that's why I asked but I think you are right. I am not as much into testing programs (in general) and backup programs in particular just for the fun of it. I am however always grateful for your efforts and explanations.
I have always used PhyLock opposed to VSS when doing backups with IFW but I am now trying to make an informed decision as to which is better or even preferred. Even though I have never had any issues using PhyLock, I stumbled across the same thing in the manual that @Peter2150 did as I was researching the new "/usemd" and/or "UseMetaData=1" option for restores.
I have been using the "/usemd" and/or "UseMetaData=1" when making hot images with IFW and have seen no issues with these options and PhyLock.
Quote from the manual concerning backup options (referring to "/usemd" and/or "UseMetaData=1"):
So, back to the original question: Which it the best or preferred method to use, PhyLock or VSS? From reading the manual, TeraByte seems to want you to use VSS in this case. Is there some issue or potential issue when using PhyLock particularly if you decide to use the "/usemd" and/or "UseMetaData=1" option when doing backups?
The manual for IFW stating "When creating backups in Windows using this option, it’s highly recommended to use VSS." makes me think that if I continue to use PhyLock instead of VSS that it very well could be a disaster waiting to happen.
Are many of the users here using PhyLock along with the new hash options to speed up backups and restores and have any seen any issues with this combination?
Should I change to using VSS with IFW?
I was a PHYLock user until a few days ago. TeraByte now say to use VSS with /usemd, so I am. There is an unanswered question in the TeraByte Forum regarding why VSS is now preferred over PHYLock if one is using /usemd.
Hello @Brian K,
Thanks for the reply.
I just hate to change from PhyLock since it has been so flawless for many years. I use Macrium as a secondary solution which of course already uses VSS and having IFW use a different method was an extra plus just in an extremely rare case that either TeraByte or Macrium might fail. It just bothers me that the "highly recommended to use VSS" is hidden away in the manual and no announcement or explanation has been given for this.
I am going to change to VSS also at least for the time being because I have now lost that "warm, fuzzy feeling" when it comes to PhyLock...
How do I do this?
1. Open the program
2. CLick on settings.
3. Go to the third tab Phylock/VSS
4. In the bottom half just check the use VSS When available
Note I didn't bother with the top section didn't seem necessary
I have to say this new version is AWESOME. Before in 306a the behavior of some of the options were errratic for me. Now everything is stable and fast. Restores are amazing. I have been beating on it. Even wiped the vm disk and then did a restore. No need for any pre processing like formatting. Just did a restore. Perfect.
Open IFW, Settings, PHYLock/VSS tab.
PHYLock Settings... put a tick in Disable Usage
VSS Settings... put a tick in Use VSS When Available
I also remove the 2 ticks in
Exclude Files to Not Backup and Exclude Files to Not Snapshot. This means those files will be backed up. As they are with PHYLock. But the wording sounds like a double negative.
I found the disable usage under Phylock settings doesn't seem to matter.
Pete, OK. I guess it just seems logical to disable it if it isn't required.
Some crazy wording there.
I even went a step further and uninstalled the PHYLock driver since I see no reason to keep it running if not being used. I can always install it again if I change back to using PHYLock.
I thought about that kent, but decided the minute I did that I'd want it for something, so left well enough alone.
I surely don't know Terabyte's answer concerning VSS vs PHYLOCK when using metadata to do "delta" Incrementals, but I do know the superior method for using any kind of metadata to determine "difference" imaging is clearly VSS. As we know, VSS, by design, provides for a consistent FileSystem (or as consistent as its active tasks will allow) prior to making the locked FileSystem available for the requester (in this case, IFW). We know this because VSS is designed to interact with any task who requires consistency in their DATA set prior to any backup operations... the VSS protocols are clearly defined in the use of this sub-system.
PHYLOCK, on the other hand, has never been able to provide this... there are no protocols involved with locking a FileSystem under PHYLOCK. All it provides is the lock on the System for the requester, and that lock is not consistent in any way. It provides for inconsistent file states (especially with important files) and inconsistent file structures themselves which may, or may not, provide problems later. PHYLOCK features were designed before the days of VSS... that's why no protocols were ever offered for use when using this System locking method. Many other imagers also developed their own proprietary locking Systems prior to VSS availability, but they have since embraced the VSS design just as IFW has done.
Now, all of a sudden, IFW is using metadata for the first time to do its difference imaging. It makes great sense, when doing this, to insure that the FileSystem is as consistent as possible prior to the imaging operations... this can only be done when using VSS, at this point in time providing the most consistent FileSystem when the lock is established.
PHYLOCK never failed me either, but I was never running any sophisticated applications managing LIVE cached databases or LIVE important data files... that makes a huge difference in the result of imaging/restoration of complete FileSystems. I think the above discussion might have a lot to do with IFW now recommending the use of VSS.
My only gripe would be why didn't they announce this in a more obvious way.
Thanks for the reply @TheRollbackFrog...
@Peter2150 I agree with you. I would have not noticed this except for researching the options for metadata and/or hashes (ie: "/usemd" and/or "UseMetaData=1") in the IFW manual. If not for that (or reading your post), I would still be blindly using PHYLock. For something that is "highly recommended", it sure is hidden well. I am sure that a lot of people do not go through the manual and probably will not know this preferred setup.
TeraByte Support's answer to the VSS/PHYLock question....
Edit.... this post below...
To be accurate, is this post you're referring to? http://www.terabyteunlimited.com/ucf/viewtopic.php?f=4&t=2564#p13847
Separate names with a comma.