Hi Yash Khan Until you try restores, you really haven't proved anything. Especially with those 20 sec incrementals, test restoring them should be crucial
Nope. They're basically asking users to re-initiate their automatic scheduled items and make sure Reflect is updated to the latest version before they do. The main problem was that the original Scheduler API v1, used prior to the AU, was changed by MicroSloth at the AU and all the v1 API stuff started falling apart. MicroSloth never told anyone of the upcoming change. And apparently if you were on one of the "rings" that had it available, it didn't make it out on the ring before the AU. This is just one of many, many things that has kept me away from W10 (I test with it, nothing more)... not just the dumping of 2,500 support personnel and exchanging them for user feedback on the multi-ring System.
I mentioned to know what you experts think & may be you guys give it a test & see what all its doing. I may try restore & if I, will update here.
I recently had Macrium Reflect, installed with the help of support, and implemented a regular backup schedule, since the install. So far, I haven't tried to test if a restore would work or not. Also, I haven't got the AU update from Microsoft, as yet. So, I shouldn't be a affected by any of these problems that are happening, hopefully. Edit: see my earlier posts, on page #156 - https://www.wilderssecurity.com/threads/macrium-reflect.356309/page-156
I've done several hundreds of restores with Macrium. I probably do a restore every couple of days, or anytime I test something.
Pete. . . you sound like a Macrium restore expert. I've never done one and wondering just how you actually do a restore? -- the simplest way .
If you want to test your backup get a used or new second hard drive to restore to. If the backup failed your boot drive will be safe. Always do a restore to see if the image works. Later on when you need to restore, you will not end up with a damaged your boot drive. After a successful restore you will have a ready to boot C drive. If you are using a laptop, you have to remove the drive from the laptop. Put the restored drive in the laptop to see if it boots up.
The simplest way is add the boot menu to the system via the macrium gui. Then you just initiate a restore from with in the windows GUI. Macrium will reboot the system, boot in the recovery env. , automatically do the restore and then reboot into windows. Guys I can assure you if you ever actually have to do a restore, your gonna be under stress. The only way to reduce it is to actually restore(not substitute disks) and do it often enough so you can do it automatically. When you are under the stress of needing to do it. is not the time to wonder if it will work, or try and learn how to do it. I consider messing inside my computer to swap disks is more risky then just doing a restore. Before I will add an imaging program to the stable, I do on average two images a day and two restores. Do that for a trial period of 30 days and I am comfortable. Another thing I've done, with Shadowprotect, Macrium, Drive Snapshot, IFW, and even Aomei is stress test the restore. What I do is start the restore, let it run for two or 3 minutes, and then do a power reset. Basically that trashes the disk. Then restart the restore. It should restore fine, and the ones I've done that with passed just fine. Also I do at least daily images, and with Macrium on one system hourly. I test restore once a week. I want to know those images will work. First time is scary, but once you do it enough, it's old hat.
Pete - just a point that might be worth mentioning is that you use a single partition disk. Your method of interrupting a backup/restore might work differently on a multi partition system. Not sure how it would work.
Hi David When I image my win 10 set up I have it image the whole disk which includes the two partitions. So when I go from my single partition win 7 setup and restore my one win 10 image it restores both partitions. I see no reason why interrupting it would be any different. The key is to make sure when you image you image the disk not a partition. Pete
Hello I was wondering what is the best way to delete a backup off my usb stick. it is a bootable macrium usb stick. do I just delete the img files for the date backup I am trying to delete? thanks
TheRollbackFrog & Peter2150, Please help me here https://www.wilderssecurity.com/threads/easeus-todo.373507/
Yep, works fine! Make sure you delete the whole chain or, if not, the last <n> files (by number) that you no longer need.
To restore, all the incremental backup should be fine i.e any one incremental backup not good & restore would not work?
So I have to "verify" all the images before restore Or during backup, the product will warn/notify any prob & will not save the bad image?
Users process this in different ways. If you VERIFY when you create the image, you'll know immediately of a problem and can re-do the Incremental image if necessary. If you wait 'til you need the image and find out it's bad via VERIFICATION, you're toast as far as that image chain is concerned beyond that bad point in time. Some people worry about "bit rot" on old images (possible magnetic failures on the storage media)... if this were an issue, VERIFICATION immediately upon imaging would not help, it would be bad when you went to use it. Some users try and avoid this with multiple copies of their images (this is what I do). ...or, use only DIFFERENTIALS which don't rely on a chain of Incrementals but tend to use much more storage. And there's always the case where the baseline FULL image develops bit rot which will make the whole process bad (and moot). Immediate VERIFICATION and copies of the backups seem to be the safer method when it comes to the "bit rot" scare. The product cannot save the image once it's gone bad (no longer verifys correctly).
TheRollbackFrog, 1. Full Backup - Incremental Backup ------------- a. Pre-OS console - I try to restore to an IB...if I get an error on restore start then I can exit & boot normally, right? b. Pre-OS console - I try to restore to an IB...If I get an error during restore i.e mid-way then after exit, can I boot normally? 2. Full Backup - Incremental Backup ------------- occasional Differential Backup (once in a week) a. Pre-OS console - Suppose 1 IB is bad But FB & DB (DB later in the chain i.e after the bad IB, there are 3-4 IB & then this DB) are fine...I try to restore to the mentioned DB, no probs restoring (even if an IB is bad), right? 3. Fullback - Incremental Backup ---------------- Differential Backup (Bad) - Incremental Backup ----------------- Differential Backup a. Pre-OS console - Can I restore to the last DB? Is there any difference starting restore within OS & starting restore at the boot with Pre-OS console, like speed, quality, time taken, etc....?
In most cases, if the error occurs before any of the backup chain (and partition) data is written, a reBOOT will work just fine (the original partition hasn't been changed yet). If the error was during the restoration, a reBOOT will not be possible (if the partition being restored was the ACTIVE BOOTable partition). A DB is a child of only one parent, the FB. Any DB of that FB is available for restoration if IBs are broken. IBs are children of either other IBs, DBs or FBs, depending on where they are in the chain. The last DB is fine, its parent is the FB. The bad DB + its following IBs cannot be used. The within OS restore will restore, with script provided, with any Recovery Media BOOT mechanism. If it sees the pre-BOOT menu item, it'll use it automatically after it shuts down your system. If it doesn't, it'll ask you to BOOT with your Recovery Media to perform the very same operation. Only difference will be a little time in loading an external Recovery Media if that's all you have, both operations will use the Reflect script provided to do your restoration. Of course, you can load either manually (menu selection or external Recovery Media load) and do the exact same recovery MANUALLY while in the Recovery Media... there are no restrictions.
So I cannot boot into OS, right? And options are, with Pre-OS console, either try with full backup or check backup chain & try the last good backup before the bad one in the chain, right? And better options, keep multiple & external backup & try those, right?
