Been using MR for system imaging for years but only just started with file backups. Looks promising but I'm wondering whether losing one file in an incremental chain would invalidate the whole backup? At risk of losing this month's chain I could test this of course but hoping to avoid having to do that.
Been using MR for system imaging for years but only just started with file backups. Looks promising but I'm wondering whether losing one file in an incremental chain would invalidate the whole backup? At risk of losing this month's chain I could test this of course but hoping to avoid having to do that.
It makes no difference whether it's a system image backup or a files and folders backup. To restore an incremental set you need the full and every incremental since the full up to the incremental for the date you wish to restore to.
1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
Hard Drives
1TB Samsung EVO 870 SSD
Internet Speed
50 Mbps
Browser
Edge, Firefox
Antivirus
Defender
Other Info
fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Operating System
Windows 11 Pro
Computer type
Laptop
Manufacturer/Model
Dell Latitude E4310
CPU
Intel® Core™ i5-520M
Motherboard
0T6M8G
Memory
8GB
Graphics card(s)
(integrated graphics) Intel HD Graphics
Screen Resolution
1366x768
Hard Drives
500GB Crucial MX500 SSD
Browser
Firefox, Edge
Antivirus
Defender
Other Info
unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
If you had 6 incrementals and incremental 4 was deleted or corrupted, incrementals 1 to 3 would still work, but incrementals 5 and 6 would no longer be of use as they have become "detached".
The Full will contain complete copies of all the files and folders you have chosen to back up. There will be one copy of each file as it stood at the time you made the Full backup. Each Incremental will contain just the changes made to any of those files since the previous backup. The first incremental holds the changes since the full, the next any changes since the previous incremental, and so on.
1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
Hard Drives
1TB Samsung EVO 870 SSD
Internet Speed
50 Mbps
Browser
Edge, Firefox
Antivirus
Defender
Other Info
fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Operating System
Windows 11 Pro
Computer type
Laptop
Manufacturer/Model
Dell Latitude E4310
CPU
Intel® Core™ i5-520M
Motherboard
0T6M8G
Memory
8GB
Graphics card(s)
(integrated graphics) Intel HD Graphics
Screen Resolution
1366x768
Hard Drives
500GB Crucial MX500 SSD
Browser
Firefox, Edge
Antivirus
Defender
Other Info
unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Thanks guys, all makes perfect sense. I asked because I also use BT Cloud which keeps the last six versions of every file in each of the folders you have opted to include in its backups. While I've never considered it very sensible to use backup systems or email accounts provided by your ISP I'm going to make an exception of BT for that reason. Anyway, I just wanted to be certain my backup strategy of having two sets of file backups, one local, MR, and one cloud based, BT, were both actually doing exactly what I want. I also use WinRAR backup profiles on demand and have local monthly backups going back to 1996 - OTT or what?
In my experience you can never have enough backups. Besides my Macrium images I use two other independent backup methods for my critical user files. My oldest backup only goes back as far as 2014 though
1366x768 native resolution, up to 2560x1440 with Radeon Virtual Super Resolution
Hard Drives
1TB Samsung EVO 870 SSD
Internet Speed
50 Mbps
Browser
Edge, Firefox
Antivirus
Defender
Other Info
fully 'Windows 11 ready' laptop. Windows 10 C: partition migrated from my old unsupported 'main machine' then upgraded to 11. A test migration ran Insider builds for 2 months. When 11 was released on 5th October 2021 it was re-imaged back to 10 and was offered the upgrade in Windows Update on 20th October. Windows Update offered the 22H2 Feature Update on 20th September 2022. It got the 23H2 Feature Update on 4th November 2023 through Windows Update, and 24H2 on 3rd October 2024 through Windows Update by setting the Target Release Version for 24H2.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
Operating System
Windows 11 Pro
Computer type
Laptop
Manufacturer/Model
Dell Latitude E4310
CPU
Intel® Core™ i5-520M
Motherboard
0T6M8G
Memory
8GB
Graphics card(s)
(integrated graphics) Intel HD Graphics
Screen Resolution
1366x768
Hard Drives
500GB Crucial MX500 SSD
Browser
Firefox, Edge
Antivirus
Defender
Other Info
unsupported machine: Legacy bios, MBR, TPM 1.2, upgraded from W10 to W11 using W10/W11 hybrid install media workaround. In-place upgrade to 22H2 using ISO and a workaround. Feature Update to 23H2 by manually installing the Enablement Package. In-place upgrade to 24H2 using hybrid 23H2/24H2 install media. Also running Insider Beta, Dev, and Canary builds as a native boot .vhdx.
My SYSTEM THREE is a Dell Latitude 5410, i7-10610U, 32GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro (and all my Hyper-V VMs).
My SYSTEM FOUR is a 2-in-1 convertible Lenovo Yoga 11e 20DA, Celeron N2930, 8GB RAM, 256GB ssd. Unsupported device: currently running Win10 Pro, plus Win11 Pro RTM and Insider Dev, Beta, and RP 24H2 as native boot vhdx.
My SYSTEM FIVE is a Dell Latitude 3190 2-in-1, Pentium Silver N5030, 8GB RAM, 512GB NVMe ssd, supported device running Windows 11 Pro, plus the Insider Beta, Dev, Canary, and Release Preview builds as a native boot .vhdx.
I'm a retired LAN/WAN Network and Hardware Help Desk Manager. When we first started installing LAN's and (Novell) servers at our field offices we started server backups with a full backup on Monday night and incrementals Tuesday through Friday. That turned into a fiasco if a restore was needed and not done properly. Additionally a full backup restore took less time so we switched to only doing full backups each night.
I do Macrium full backups only and alternate between backup drives. I keep the current and previous backup on each drive. Whether that all is needed ???? I guess carryover from my network days.
