Added a screenshot of the reparse point setting, essentially whether to follow junction points etc and back up the contents on the destination, or just backup the points or whatever.. I don't feel like it should make any difference but maybe?
I guess I never noticed those settings - after checking, my two reparse settings are the default (recommended) ones. I noticed that your 2nd reparse point setting is not the recommended one (could it be that's the problem)?
I intentionally have that to not follow, works fine with delta indexes turned off at least. I'd rather have that setting set to Do not follow and delta indexes off than the other way around.
Thanks! One more question, synthetic Full if possible? Should I check this, want to use like AX64. Would this plan be similar? What are the drawbacks with synthetic Full if possible?
SYNTHETIC FULL actually will start moving your baseline (initial FULL image) forward in time as you reach your INCREMENTAL RETENTION Rule setting. If not set, only your actual INCREMENTALS will move forward in time.
Thanks, might have it. Still learning. What way is the most like AX64 time machine (without scheduled)? I used that program for along time.
AXTM runs either MANUALLY or AUTOMATIC. Its AUOTMATIC mode has some rudementary scheduling which changes over time. It cannot be duplicated in Macrium, but with Macrium's scheduling, you can come close. Macrium's MANUAL mode can reproduce AXTMs snapshot capability, but with Macrium, you cannot DELETE an INCREMENTAL in the middle of the chain like you can with AXTM... AXTM will do an automatic MERGE of relevant data in the deleted snapshot to the snapshot following it. When you delete a Macrium snapshot, it will delete itself and any follow-on snapshot that is dependent on the one being deleted... a very different process. You can set up Macrium to have a fixed baseline (like AXTM) and some number of manual snapshots, after which Macrium will merge those snapshots forward in time (delete the oldest when a new one is created).
Regarding my issues with Delta Indexes, I tried it again and this time using PE 5.0 to restore, same issue. Tried to verify the images with the "Verify.exe" tool Macrium has and they all verified fine, also tried to make a VM with the latest image using Macrium ViBoot and it worked just fine, which means the images are fine but the restore gets F'ed up but the program thinks it did a good job.. Btw, after trying to restore the delta index incrementals, the partitions show up as "Unformatted Active" and the first two partitions have 100% disk space used while the third has ~2/3rds used... Which is also weird and probably a result of the issue.. Anyway, hopefully the support will have an idea of what is going wrong, until then I'll keep Delta Indexes off.
Sanya, you might ask Macrium if your reparse settings could be the culprit because 879 with delta indexing is working very well here. I have since restored two incrementals, both of which completed quickly and accurately. Scott
If reparse points is the issue then the issue should probably manifest in the images themselves rather than just restores, since it affects what gets backed up and not (so ViBoot shouldn't work if that was the case) Anyway, I did mention it in the e-mail I sent them and they didn't bring it up in their response, we'll see what happens.
I didn't change anything, I just formatted my USB recovery stick & then used macrium to create the windows 10 pe. This time it booted fine although the monitor flashed some lines for a second or two before it loaded fully.
When initiating a restore to the C drive from within Windows, Reflect is no longer giving me the "your PC will now reboot" message. Instead it tells me to manually boot from the boot menu option or recovery disk. I did previously set up the boot menu option, it has a boot menu entry, and it works fine if booted to manually. Has anybody else encountered this?
Ah, nice that it worked the 2nd time. Unfortunately not for me. Guess I have to wait for another update.
Hopefully they will fix the issue you have quickly, they are pretty good at getting updates out. You can always use the win 8.1 till it's fixed
Hi Scott! I use the ADVACED OPTION in Reflect to place that stuff on a non-imaged disk... mainly so if I have to revert to an earlier image, I don't lose any PE work I've done/collected in the meantime. That said, I believe (a guess here) it's in ProgramData <hidden> under "Macrium" in a folder called "boot" When you put it elsewhere, it resides at the ROOT level of whatever volume you choose in the same "boot" folder.
Thanks Frog, that's what I want to do, however I'm unsure if doing that will actually MOVE the relevant PE boot files from wherever they are now located on C: to the volume specified, or if doing that will result in the PE boot files in two locations on my drive? Scott
There's no problem with deleting that "boot" folder. First, change your PE destination in your advanced options, then delete the existing "boot" folder. From that point on, Reflect will see that nothing exists and rebuild what's necessary, during MEdia creation, if you're asking for a BURN, ISO or Local Boot... it'll just put Humpty back together again. ...or, leave the original alone and reset your DEFAULT PE target. Any new builds will create what's necessary on the new target and leave the original alone... then you'll have 2-sets but Reflect will only use/build the TARGET sets.
