@ TheRollbackFrog I am using Hasleo for full backup only (I haven't tried yet its other capabilities). I built a rescue ISO file using “Emergency Disk” in the “Common Tools” (within Hasleo GUI) and got an ISO file. I added this ISO to a Ventoy USB drive where I have all ISO tools including recovery ones. When I tried to boot from this ISO file (for a recovery), I’ve got “Press any key to activate the CD or DVD…”. After few seconds I got again the USB drive menu. I used the Hasleo recovery file from the Strelec ISO I have on the same USB drive, and it worked. 1. From where to generated Hasleo rescue ISO disc? Was my above process wrong? 2. I saw in a previous thread in this subject where you explain about “OffLine WinPE image (OPE)”. I followed your instructions and downloaded a “Hasleo Win PE OPE” file. Can you please elaborate what is it for, and how to use it.
@samy - you've got a couple of things going on here. Your ISO creation is correct and your placement on the VENTOY device is also correct. The problem (and it's really not a problem, just a configuration issue with your System's BiOS) is that your BiOS thinks that it's trying to load a CD (purest ISO image) and it also sees that your internal disk is BOOTable. As a result, it'll ask you if you want to BOOT from the "CD" (your selected VENTOY ISO image). When it says "Press any key..." you need to quickly hit your ENTER key. This will tell the BiOS that YES you want to BOOT from the CD image it thinks it sees and it will BOOT into the Hasleo ISO properly. The problem is that Systems vary in their speed after the "Press any key..." as to when they make a decision... mine is very fast so my ENTER key hit must be very quick. With VENTOY, I use a different approach to eliminate that issue. VENTOY has a WIMboot PLUG-IN available that allows you to BOOT from WIM files as well as ISOs and other BOOTable types. I use this method for almost all my WIM-based ISOs (of which HASLEO is). You'll need to extract the boot.wim file from the ISO's source folder to do this. Windows Explorer, 7ZIP and WinRAR can all do this for you. Once the WIM file has been extracted, you can name it anything you want and put it on your VENTOY disk in the appropriate area for all the other images you have. After that, VENTOY should see that file before selection and have no choice BOOTing issues. As far as the OPE file is concerned, all this does is eliminate the need to download a large DataSet from Microsoft each time you have to build an Emergency Disk. The WIM base for Hasleo's recovery media doesn't change that often so why download from Microsoft every time you need their files... just download the OPE file once and use that instead for all your Emergency Disk builds. In order to use it you will have to eliminate whatever data you used previously to generate your Emergency Disk (or reInstall your current Hasleo version which will do that for you and you won't have to do the following in RED). This is best done by deleting the winpe.iso file located in C:\Program Files\Hasleo\Hasleo Backup Suite\bin folder and the winpe.wim file in your WADK\Windows Preinstallation Environment\amd64 subfolder. Rebuild your Emergency Disk once again by selecting Tools/Emergency Disk/Download WinPE components/Offline WinPE Package then use the dropdown to select the OPE you plane to use, then Next. The media building process will commence without having to download any additional media from Microsoft.com.
There have been a lot of questions concerning the SETUP and OPERATION of Hasleo's Backup Suite... and when looking at Hasleo's online documentation, some of the operations/procedures included tend to be a bit cryptic. At the same time I have been asked, privately, by a Forum user to see if I can produce a simple TUTORIAL which explains the basic operations of HBS's main functions (disk imaging/restoration and file imaging/restoration). Since I have had many verbose responses in this Forum thread, and wish to cut those responses back a bit ( my fingers hurt), I've decided to try and give that tutorial a shot. I'm not sure how long it will take (life happens ya know) but I will make something available for the Forum members. I will also ask the Mods if the eventual result can be made as a STICKY THREAD in either the Forum's stickies or the Hasleo thread itself (don't know whether that's possible). It will be in the form of an attached PDF file (updated when necessary) and if the sticky is allowed, the sticky post will be similar to the one I did (RollbackRX) that is currently available at the top of the Forum. Wish me luck, pls ... @samy
@TheRollbackFrog Thank you for your good will. This software may soon replace (in my opinion) many other older programs or at least serve as a second backup. Therefore, it is important to know how to install and use it without error.
@TheRollbackFrog That would be a valuable (generous) contribution, especially given your expertise, that I also think merits a Sticky listing.
Hi @ Wilders Deleting Backup Tasks I have a Full backup followed by a chain of three differentials i.e. FB1, Diff1, Diff2, Diff3 and I want to delete a differential backup, in this case Diff3. Questions 1) How do I delete Diff3 through the GUI and also is it possible to delete Diff3 by just deleting the image? I was not able to find any way of deleting the Diff3 image via GUI. 2) Is there anything else that needs to be done to ensure the modified chain isn't compromised? 3) If instead I wanted to delete Diff2, can it be done if so how? 4) Where does merging fit in? Thanks Terry
1. No can do at this stage of development, yes you can do it via Explorer. 2. No, as long as there are no INCs following your DIFF deletion. 3. DIFFs only require their parent FULL to work properly, chain will remain in tact. 4. Merging only affects INCs if present.
Hi @ The Rollback Frog Many, many thanks for that. I has cleared up so much. Thank you. A few more questions:- 1) If I have a Full1, Inc1, Inc2, Inc3 What happens if I delete Inc3 (presumably via explorer not GUI?) Do I need to do anything else? 2) If I have a Full1, Inc1, Inc2, Inc3 and delete Inc2 (presumably via explorer not GUI?) Do I need to do anything else? 3) I've never used merge but have seen tick boxes shown in the manual can you explain what happens if I tick Full1, Diff1 and Diff3 ie leaving out Diff2? All of what I am asking you appears not to be available in the Hasleo Manual except the section on merging and that is not absolutely clear. Thank you again for your help Terry
@TerryWood 1. Deleting the last INC in a chain will not affect the chain (other than losing that particular INC). An INC (child) is parented by the most recent INC, DIFF or FULL in that order, whichever is most recent. If you delete that last one, the next INC will be based on the new last one left in the chain after your deletion. 2. If you delete INC2, INC3 will become invalid (no more parent <the old INC2>). When you do this, it's best to delete any following INCs (up to the next DIFF or FULL) to eliminate the now broken chain. Recent testing has shown that if you do break the chain, any further INCs will be successful in completion but will be invalid upon restoration. The Dev team produced an ongoing test version just recently (see HERE) to eliminate this issue. With this test version, the broken chain is now detected upon image creation rather than attempted restoration (no more useless INCs ). 3. The MERGE window specifically says... "Please select multiple consecutive backup image versions that you want to merge." This means what it says ... if they aren't consecutive, the PROCEED button will not be available (active) for you to use. I don't use the manual MERGE function. For retention control, the MERGE function is automatic based on your retention settings. If you have your retention settings, INC for example, set to 7-whatevers, the application will always merge forward into the chain based on your selection. In my case I retain 2-FULL monthly Backups and 7-Days of INC backups. Hasleo merges those INCs forward during the 7-Day period up until the next DIFF or FULL. FULL retentions are capped at 2-images, all DIFFs remain (done weekly) until their parent FULL is deleted during retention mgmt, and INCs are always available for the past 7-Days... works well for my needs.
Hi @ TheRollbackFrog Many, many thanks again. I can venture forward with some measure of confidence. Can't wait for your personalised manual. Terry
