Thanks for the comprehensive yet simple clarification on this. There has been on some occasions (not often), for me anyway, where that is happened and Macrium Reflect (which i don't use now), fortunately repaired the BCD upon a log review of event. HOWEVER this was only using Macrium Relect to fix a non-boot issue only. Not a failed restore or anything similar. Sort of an emergency BCD repair. BUT might have been a problem had the BCD mangle issue interfered with an actual restore (or not).
BTW, it's more than just passing appreciation. @n8chavez, @TheRollbackFrog, others, i've revisited Hasleo's Product Forum and combed over the progress of this Imaging Program as bug issues were passed to the DEVS, and really appreciate highly, each & every suggestion laid at the table for the DEVS which MOST they happily revised their product to improve quality and make it flawlessly feature-rich to this point. Looking forward to v5 which DEVS said they will set Delta Restore as default. Along with other in-house refining's, i'm not sure if there is much more in the feature set they might think of to add.
HBS running in the installed winre.wim on Windows 11 I just need to press Shift + restart Also Drive Snapshot, Explorer++, Q-Dir and of course IFW are there... Spoiler
Regarding Strelec, if he hasn't yet, or doesn't soon include it, that is a project on this end worth to tackle. It has for a very long time been one of the fastest loading PE's i ever found to be stable too.
Hasleo Backup Suite V4.9.1 Released! What's new in this version: 1. The backup pre and post commands do not work properly in some cases 2. Volumes in the backup image file cannot be listed in some cases 3. Network shared folders cannot be listed in some cases 4. Fixed some bugs to improve product quality
Turns out STRELEC uses as many "portable" files as possible, most being created by 7-Zip. At the moment, the only structure even close to being portable available from Hasleo is structured in contradiction to the way 7-Zip can make apps portable. I have asked Hasleo if their app can be restructured accordingly... or at least, if possible, make a test build available with the required structure change. If they make that change, I'm sure a request can be made of STRELEC to add it to his diagnostic build. At the moment there is a method to either configure it directly into the WIM (the program itself, not the WIM access structure) of any WinPE build (not STRELEC's solution) or have it standalone on a WinPE UFD build that can be executed manually. We'll see where all this goes...
There is a really interesting prospect with some potential should the DEVS go through with that. What just can't help to be noticed, is that it has to grab everyone's attention with the way that their Development Team fine tunes this, what some might already consider, a Hallmark new backup imaging program, (HASLEO BACKUP SUITE), In the limited time since it has been introduced the DEVS have really outperformed. It certainly stands to reason why it is rapidly caught the attention of many. By the way i am sure plenty others using HASLEO, as either their Primary source Imager or Secondary, Or just testing it are like me, Fishing hard for issues and also potential NEW Features which can improve on this program. There is still space on the HOME screen for MORE FEATURES.
@TheRollbackFrog - I might have lost track of this conversation on HASLEO's Retention Feature (auto scheduling process)-but i set mine for 5 daily incrementals, So what happens to them at the end of that final INC image. Are they auto-merged into a single INC? Or are those auto deleted? I assume the Incrementals are never auto merged into the full first image. I tried that manually with a disastrous result of having run out of space. I checked the HASLEO GUIDE on their site but didn't find anything matching the question about it.
You will always have 5-INCs with merging occuring into the oldest remaining Inc. As the Incs approach your DIFF, any INCs after the DIFF are standalone until there are 5-DIFFs after that INC. Until then, merges will continue into the oldest INC. Remember, nothing needs to be merged across the DIFF since that contains all your changes from the previous FULL. It'll look a little like this...
Is Always retain first backup a necessity. Or simply applied new on every new FULL for the duration of your selected preference of schedule,
No, there's no reason to retain the 1st backup unless you want the reference for some reason. The scheme you described previously is a basic GFS (Grandfather, Father, Son) approach. The FULLs remain at their time point until retention settings remove them.
I also noticed you only have 1 DIFF being kept in your retention schedule. With this setting, there will be no MERGE operation since the minute you make the 2nd DIFF, the 1st one (and its INCs) will disappear as well. If you want to use the MERGE, you'll need more DIFFs in your retention model. My model allows all the DIFFs between the FULLs to remain until the parent FULL is deleted by retention settings. This allows my 7-days of merged INCs to move forward in time across my retained DIFFs.
My GFS model has all images being executed at exactly the same time on the days scheduled (Sunday nights). I allow my DIFFs to remain (no retention setting) until the parent FULL is disposed of. With a 2-month (or 8-week if that's easier to understand), there will always be month #1 and month number #2 with its forwarding 7-days of merged INCs across its retained DIFFs. This happens once your retention scheme reaches its maximum number of FULLs.
Thanks Froggie- I now set it to 2 Differentials It's getting better becoming acquainted with EACH schedule HASLEO RETENTION SCREEN. I want 5 INCS then DIFF in that order.
Also please note... you have 5-Days of INCs in your retention. This can potentially give you more that 5-INCs in a 5-day period. If you use that task to do MANUAL INCs within your 5-day period (which I do a lot when testing), they will remain and be merged forward accordingly, but when doing this you may have more than 5-INCs in that existing chain. It doesn't hurt anything, it just may surprise you
...and also be aware, if you schedule your images at the same date and time, Hasleo handles the hierarchial nature of the requests... FULL before DIFF before INC, no issues at all.
Well looks like the INCS came through in a pinch. The 5th INC completed this morning and a Differential was then created as per HASLEO schedule. A few hours later i run across a wireless bluetooth speaker which was a gift from a friend. I was searching Windows Bluetooth Settings and danged if i didn't delete that speaker. I had totally forgotten the name and just assumed the device name was something else. When trying to rediscover that Bluetooth Wireless Speaker in Windows 11 the setting wasn't working for some reason. KEEP IN MIND WINDOWS 10 APPS & SETTINGS ARE STILL ON from my upgrade to Windows 11. Anyway the only way to get it back again was to run the soonest Incremental. That RESTORE went off without a hitch, and the Wireless Speaker Name was returned and works perfectly when paired. At least the confidence level from another HASLEO RESTORE is confirmed again. Great features and very efficient!
And i completely forgot to use Delta Restore which a HASLEO forum member on their site suggested making Default. Followed up by the Admin replying WILL BE ADDED IN v5.
My issue isn't with delta. HBS sees my disk as a different disk then the one from the image, which is not correct.
No it's not. You been active on their forums somewhat, Raise that issue up with them I notice in the box that has my 3 separate backup tasks on the HOME screen, after i selected to RESTORE an Incremental which belonged to the DISK i needed it on. THEN the little wheel started turning in a different Image panel than the one that i selected and alarmed me a little. Luckily it did restore correct. DEVS still have some bug fixes to address.
