+- Hasleo Software Forums (https://www.easyuefi.com/forums)
+-- Forum: Hasleo Software (formerly called EasyUEFI Development Team) (https://www.easyuefi.com/forums/forumdisplay.php?fid=1)
+--- Forum: Hasleo Backup Suite (Free Windows Backup & Restore Software) (https://www.easyuefi.com/forums/forumdisplay.php?fid=10)
+--- Thread: Simultaneous Scheduling Priority (/showthread.php?tid=2552)
Simultaneous Scheduling Priority - Gork - 03-20-2025
I read in change for HBS at some point that a change was made so that all simultaneous scheduled image backups would not occur, but the notes said nothing about whether that means NO simultaneous backups would occur or which one would be chosen. My question is, what would happen with the following scheduled image backups:
FIRST SUN OF MONTH @1100 HRS: FULL
EVERY SUN OF MONTH @1100 HRS: DIFF
EVERY DAY @1100 HRS: INC
My expectation is that ONLY a full would occur on the first Sunday of the month. ONLY a differential would be created all the other Sundays of the month. ONLY an incremental would be created every day of the month that is not a Sunday.
In other words, FULL trumps DIFF and DIFF trumps INC.
Is this correct?
RE: Simultaneous Scheduling Priority - Froggie - 03-20-2025
That is correct.
RE: Simultaneous Scheduling Priority - al3x - 03-20-2025
I use a very similar setting for my PC:
- first Sat. of month @0900: Full backup
- every Sun. @0900: Diff. backup
- everyday @0900: Inc. backup
The diff. and full backups are taken in favor of the inc. ones here. So no problems for me since the first 5.0 beta in December.
I don’t know about your specific setting where a full should be taken in favor of a diff. one, but I’m pretty sure this works just the same.
RE: Simultaneous Scheduling Priority - Gork - 03-20-2025
I tried to edit my post but y'all were too fast for me. I pulled my edit out and will put it here, but first, thank you for your replies. I've now been pondering the following...
In the scenario I shared above, what would happen on the FIRST MON if no FULL occurred on the FIRST SUN? Would the prior month's "chain" (assuming one existed) just be tacked onto with an INC? And what if no other prior image backups existed? Would a FULL be created since there was no FULL for the INC to "chain" to?
EDIT:
Had to fix my INC vs DIFF entries on the FIRST MON - got confused.
RE: Simultaneous Scheduling Priority - Froggie - 03-20-2025
Unlike REFLECT, Hasleo doesn't allow for a "managed" method, within the UI, to modify your image chain and not break it. If you break the chain outside of Hasleo (via Explorer), things will happen with tasks using that chain... not sure what, but easy enough to test for (will stop back later with results).
As far as schedules/retention is concerned, I use FULL On the 1st of the month, DIFFs on Sunday and daily INCs all at the same time. Retention mgmt is 2-FULLS and 7-DAYS of INCs (I do lots of manual INCs for snapshot purposes... that's why DAYs rather than BACKUPs for INC retention). All work very smoothly...
RE: Simultaneous Scheduling Priority - Gork - 03-20-2025
I'm not actually talking about modifying the image chain within the UI. I just mean, for instance, if I have the following schedule, as posted above, in place:
FIRST SUN OF MONTH @1100 HRS: FULL
EVERY SUN OF MONTH @1100 HRS: DIFF
EVERY DAY @1100 HRS: INC
But on the first Sunday of the month something happened, let's say the power was out, and no image FULL (or any) backup occurred. What would happen on the first Monday of the month?
In the first scenario, let's say I had a full chain of backups for the prior month. Would the incremental on the first Monday of the current month set by the rule EVERY DAY @1100 HRS: INC just tag on to the last FULL/DIFF/INC of the prior month and continue the prior month's chain?
In the second scenario, let's say I had no other prior backups for this schedule. It's the first Sunday of the month but the power is out so the FULL didn't run. Next day, Monday, the ruleset indicates an INC should run, but there are no image backups to chain it to. Would HBS create a FULL or error out due to no FULL to tie the INC to?
RE: Simultaneous Scheduling Priority - Froggie - 03-21-2025
Scenario #1: in the absence of your mentioned FULL, the existing chain exists and an INC would be done against that chain, as expected. When this has happened to me in the past, I just run a manual FULL at my earliest convenience and all moves on as expected.
Scenario #2: no previous reference image available, a new chain would be started with a FULL.
RE: Simultaneous Scheduling Priority - Gork - 03-21-2025
I did perform a test on whether or not triggering an INC when no FULL exists causes an error or initiates a FULL. It errored: "No backup image was found" when I tried to manually start the backup by choosing INC from the drop down for the backup entry. I tried again, but this time let the schedule run the INC itself, again where no FULL existed, and a FULL was created.
This is expected behavior, at least to me. And this covers the answer to my "second scenario" posted above.
If there is any insight with regard to what the result in my "first scenario" would be, I'd appreciate the info.
EDIT:
Grammar
RE: Simultaneous Scheduling Priority - Gork - 03-21-2025
Ahh, cross post. Thank you @Froggie.
RE: Simultaneous Scheduling Priority - Froggie - 03-21-2025
(03-21-2025, 12:21 AM)Gork Wrote: If there is any insight with regard to what the result in my "first scenario" would be, I'd appreciate the info.
EDIT:
Grammar
My test shows with the absence of the required PARENT image (DIFF without the FULL), error is presented. In the case of INCs... any missing INC at the end of the existing chain (any one of <n> for example) or a missing required DIFF (if no INCs available), an error is presented.
Hope this helps...