Why do some machines with scheduling of doing incremental images start off completely with a new...


Why do some machines with scheduling of doing incremental images start...
Author
Message
max2
max2
Proficient Member
Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)
Group: Forum Members
Posts: 109, Visits: 243
It did not start off or leave off from the previous incremental image. Weird.

If I need to post a screenshot I will.



jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)
Group: Forum Members
Posts: 12K, Visits: 72K
If a scheduled backup creates a Full when you expected an Incremental, this will be noted in the job log, along with the reason for it.  What does your job log say?  Also, your thread title was apparently long enough to get truncated.  Might want to economize your titling a bit. Wink

max2
max2
Proficient Member
Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)
Group: Forum Members
Posts: 109, Visits: 243
jphughan - 13 June 2021 7:35 AM
If a scheduled backup creates a Full when you expected an Incremental, this will be noted in the job log, along with the reason for it.  What does your job log say?  Also, your thread title was apparently long enough to get truncated.  Might want to economize your titling a bit. Wink


Thanks I think it said no Incremental image to append to Sad 

Though there is.

How do I append it? lol
max2
max2
Proficient Member
Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)
Group: Forum Members
Posts: 109, Visits: 243
This is what it says why ?



jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)
Group: Forum Members
Posts: 12K, Visits: 72K
If Reflect could have appended to an existing backup set, it would have.  The fact that it made a Full means it didn't have a choice.  Typically this happens if any partitions on the source disk have been resized, which can happen during a Windows 10 feature release upgrade.  If you want to be sure, compare the disk layouts shown in one of your earlier backups and your new backup.  Check the total sizes of the partitions.  Are they different?

Edited 13 June 2021 8:15 AM by jphughan
max2
max2
Proficient Member
Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)
Group: Forum Members
Posts: 109, Visits: 243
jphughan - 13 June 2021 8:14 AM
If Reflect could have appended to an existing backup set, it would have.  The fact that it made a Full means it didn't have a choice.  Typically this happens if any partitions on the source disk have been resized, which can happen during a Windows 10 feature release upgrade.  If you want to be sure, compare the disk layouts shown in one of your earlier backups and your new backup.  Check the total sizes of the partitions.  Are they different?

Yes they are different Sad

Anyway to fix this please?

max2
max2
Proficient Member
Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)
Group: Forum Members
Posts: 109, Visits: 243
One is 58 GB one is 58.5 GB

jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)Macrium Evangelist (18K reputation)
Group: Forum Members
Posts: 12K, Visits: 72K
Probably not.  (Fyi posting screenshots is a really good idea when you ask questions like this....)  In order for a new image backup to be appended to an existing image backup set, the partitions must be an EXACT match, which means the new backup must contain the same partitions as those in the existing set, with no partitions added or removed, and all partitions must have the same size and "offset" (position on disk).  It's not at all clear from your posts which partition you're talking about that changed or which size is the previous size and which is the current size (again, screenshots!!), but you're talking about your Windows partition and it was originally 58.5 GB and is now 58 GB, and it's not because you did that yourself, then it probably happened because Windows shrank it to create space for a new/larger Windows Recovery partition after it.  In that case, THAT partition would be different now too.

You just have to let Reflect create a new Full based on the new partition layout, and from that point forward you'll be able to create new Incrementals as children of that new Full.  It's not a big deal.

Also be aware that by default, your retention policy will no longer act on those older backups since the default mode is to apply rules to "all matching backups", and those old backups will no longer be a match.  You can change that to "all backups in the destination folder" if you want, but if you do that, make sure your destination folder contains ONLY backups created by this job, otherwise that change could cause Job A to purge completely unrelated backups created by Job B.

Anyhow, it's currently 3:30 AM where I am.  I was up working on something else that took a lot longer than expected, but I'm going to sleep now.  If you need anything else, I'll check it later. Smile

max2
max2
Proficient Member
Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)Proficient Member (200 reputation)
Group: Forum Members
Posts: 109, Visits: 243

jphughan - 13 June 2021 8:32 AM
Probably not.  (Fyi posting screenshots is a really good idea when you ask questions like this....)  In order for a new image backup to be appended to an existing image backup set, the partitions must be an EXACT match, which means the new backup must contain the same partitions as those in the existing set, with no partitions added or removed, and all partitions must have the same size and "offset" (position on disk).  It's not at all clear from your posts which partition you're talking about that changed or which size is the previous size and which is the current size (again, screenshots!!), but you're talking about your Windows partition and it was originally 58.5 GB and is now 58 GB, and it's not because you did that yourself, then it probably happened because Windows shrank it to create space for a new/larger Windows Recovery partition after it.  In that case, THAT partition would be different now too.

You just have to let Reflect create a new Full based on the new partition layout, and from that point forward you'll be able to create new Incrementals as children of that new Full.  It's not a big deal.

Also be aware that by default, your retention policy will no longer act on those older backups since the default mode is to apply rules to "all matching backups", and those old backups will no longer be a match.  You can change that to "all backups in the destination folder" if you want, but if you do that, make sure your destination folder contains ONLY backups created by this job, otherwise that change could cause Job A to purge completely unrelated backups created by Job B.

Anyhow, it's currently 3:30 AM where I am.  I was up working on something else that took a lot longer than expected, but I'm going to sleep now.  If you need anything else, I'll check it later. Smile

Np thank you.

JK
JK
Master
Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)Master (1.8K reputation)
Group: Forum Members
Posts: 1.2K, Visits: 4.4K
This topic may be relevant reading for you.  It appears to be practically impossible to return the modified partitions to their original sizes, but there may be a way to prevent Windows from resizing your partitions with future updates.  This basically involves manually creating a Windows RE partition that is sufficiently large to accommodate future expansion of the WinRE.wim file.  If interested, you can jump to this post, in the topic linked above, which contains the key instructions provided by @jphughan

Disclaimer: I have not yet verified that this approach successfully prevents Windows from resizing the partitions, because there has been no new feature update since it last happened.  But it seems like it should work.

                                
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search