Hi,

I have 2 diferent experiences with 2 identical laptops (latitude 3420 with win10 on nvme hard disk).

In one computer Hasleo Backup Suite works perfectly. But in the otherone no: when i try to restore the sistem backup and it startups on Hasleo boot envoirment, the destination hard disk don't apear.

I think that i find the nvme drivers, but now Hasleo Backup Suite doen't ask me for drivers!

Any suggestion?

If I try and manually execute an INC or DIFF when the backup chain is unavailable, HBS offers a msg concerning a non-existant backup image. When I do the same as a scheduled operation, there is no msg and the app automatically creates the needed PARENT image (a FULL to begin the chain) instead.

The result of the scheduled operation is excellent... what should be done in that case. I don't understand why the same thing isn't done for a manual operation... maybe with a msg informing the user of the anomaly and the result.

A few versions ago, when I created the emergency disk it allowed me to create it on a network share now it tells me "error system API".

Greetings!  I have a backup chain consisting of a V1 FULL and a V2-6 INCREMENTAL.  V5 INC is deleted or missing.  I ask Hasleo for a System restore of a System image and all goes well without notice of any kind.  Upon System reBOOT, without notice, what is the state of the System as far as the above described backup chain?

Without notice, how will I know the status of the restoration?  Based on what I think your INCs are doing, I would think that the entire chain had not been restored and that the status would be at v4 (since V5 is missing and V6 needs V5 to restore properly)... I still don't understand how I would know that.

Yes, it appears to be proprietary but my question concerns the ability to extract files from your images.  You offer a file extraction method completely indigenous to the Backup Suite itself.  Almost all other imaging applications offer the ability to actually mount their images/partitions under a standard Windows API.  At this point the partition is available under Windows with all its glory... without maybe the ability to write/modify that mounted image.  This allows the user access to most all his Windows apps and the DATA in that mounted partition... a very convenient user environment.

Has any thought been given to possibly offering similar capability with Hasleo images?  Just kinda looking down the roadmap a bit to see what might be on your horizon... thanx!

Greetings, Team!  Quick question about the thread SUBJECT item... when using the "USB drive plugged in" event AND you have the "Run only once a day" option set, does that mean the NEXT allowed image must be a minimum of 24-hours from the last allowed image, or are we talking CALENDAR DAY images... i.e., only one image in a calendar day (but any time distance apart... as in 11:59pm and 01:02am)?

I'm new to the Hasleo Backup. Creating and booting from the Emergency Disk worked like a charm.

Creating a Partition Backup from my Win10 bootdisk works for all partitions (e.g. RECOVERY) but not from the C:\ drive itself. It leads into an Error 0x0073007000000005 after a few seconds.

I did a chkdsk on the C: drive as well but still the same issue.

What kind of error is that and how to solve?

Greetings, team!  While testing your scheduling features, I chose DAILY and set the interval to start at 9am and end at 8pm... I expected 12 images to be generated on the hour but only got 11.  Turns out the finish time of the interval needed to be set to at least 8:01pm for the 12th image to be generated at 8pm... I don't think that should be the case.  If the ending time is at least the same time or earlier then the scheduled task, it should run successfully (just a l'il math anomaly )

The SUBJECT term is sometimes slightly misunderstood by users of software that use such a mode.  Sometimes that term refers to bringing up a WinPE-based separate Windows environment (like your Emergency Disk) to run the user's application, and other times the application is actually being run before bringing up the full LIVE Windows System in use (kinda like a partial reBOOT).

In the case of Backup Suite's automatic LIVE restoration of a locked partition (like the LIVE Windows environment), which of the above modes is being used for this function?  Thanks in advance!

Being a newbie here I figure this would be a great place for this discussion.

Item #1: A modern UEFI configuration these days includes at least one large disk which many times includes the FOUR necessary partitions for successful UEFI BOOTing (EFI, MSR, Recovery & OS) plus a separate DATA partition to be used as the user requires.  Your "System Backup" mode correctly includes those very same partitions and does not include the extra DATA partition.  This presents a significant problem during the restore operation.  Since the "System Backup" is not necessarily a Full disk backup, the System restore should not be one as well.  The System Restore should allow a user to select the partitions to restore (multiple, if necessary) without changing the geometry of the disk as far as resident DATA partitions are concerned.  Currently a System disk restore restores all the necessary BOOT partitions but blows away any partition on that disk that isn't included in the image... quite a big surprise when I first tested this feature.  I don't see a significant reason for having this type of restore do anything other that a non-destructive partition restoration... just like it does with the Partition restore mode.  When presented for restoration during a System disk recovery, all the included partitions should be selected for restoration, allowing the user to unSELECT anything he doesn't want to restore (like an OS-only restore).

Item #2: the Partition restore mode could do this as well but currently allows only a single partition to be restored non-destructively.  This makes a System configuration restoration require four separate partition restores to insure the non-backed up DATA partition remains untouched... a significant process and possibly very error prone.

Some initial observations... more to come.  Thanx for your consideration!