Does the program perform complete backups once every specified number of differential backups?
Does the program perform complete backups once every specified number of differential backups?
Hi,
I’m using the free version of Macrium Reflect for my backups. I perform complete backups on Mondays and differential backups every other day. Recently I realized that several weeks had passed without a full backup, and I’m wondering if there’s another backup solution that can automatically trigger a full backup based on the count of differential backups since the last full one. For instance, if it shows five differential backups after a certain point, it should do a full backup next time. Thanks.
The reason for the missed scheduled backups likely lies in one of the following areas: human error, procedural mistakes, hardware issues, or another factor. It is important to identify the root cause first before taking corrective action. The current backup procedures should be reviewed to understand what specifically led to the backups being skipped.
I have configured it to perform a complete backup on Monday. If the computer isn't powered on by Monday, it will automatically turn it on on Tuesday following the scheduled backup time, ensuring the Tuesday difference backup is executed and the Monday backup is completed without being missed.
I have it configured to activate if missed, yet it appears to skip the second scheduled backup, leaving only the latest one—like a diff instead of a full backup. This seems to stem from a small oversight on my end, as I don’t have my computer available during the set times. I’m seeking a fix that avoids requiring me to adjust my random computer usage.
Macrium can also be executed via a command line interface.
For reference, the knowledge base provides guidance: https://knowledgebase.macrium.com/displa...mmand+line
It’s possible to generate a quick icon that launches DOS Command Prompt or Powershell for running commands.
A straightforward single-line command can be formed using the relevant switches (refer to "Running a Backup" in the linked resource).
If a scheduled full backup was overlooked, use the shortcut to initiate it.
An alternative is leveraging Task Scheduler, which could automatically trigger the command line based on configured rules.
This method might become complex without specific flags to verify the last full backup date or time.
It could require interpreting Macrium logs to compare the completion date of the last backup with system time, adding another layer of difficulty.
I suggest starting with the shortcut approach and evaluating its effectiveness before making adjustments.
There seem to be several viable methods, and further suggestions may emerge as you consider them.