Q: Upon Macrium menu bar File > Exit. My ext drive pwr lite goes out while the "Safely Remove Hardware" Icon remains in SysTray. Does pwr lite off indicate safe-to-remove even while safe-to-remove Icon remains in system tray...? I can either pull usb with pwr lite off or click Icon which cycles ext drive pwr on again. Allowing safely remove sequence. Don't know if pwr lite off means safe-to-remove or I need to cycle safely remove hardware sequence ...? Thanks
Every ext drive is different. I would use SAFELY REMOVE just to be sure all data has been cached out storage.
Okay, "use SAFELY REMOVE just to be sure". Thanks! Just tried Safely Remove while Macrium window still open. That way pwr lite slowly goes off without sudden off (with Exit) then on with Safely Remove cycle. Pwr lite behaves noticeably different (sudden off vs slow off) so, maybe all data will not be cached out with File > Exit. Thanks!
If you're doing transfers to slower devices (USB2 for sure), the DATA is never cached out when you exit the application unless the data moving process has been quiet for some time. The "caching" is going on in the OS, not in the app... it's the OS that needs to empty those DATA buffers. That's why SAFELY REMOVE is always a good habit to get into. I've used it exclusively since it became available in Windows.
Okay, I've been opting Macrium Exit (first) and observe sudden pwr lite off....then, since Safely Remove Icon remains in system tray. I felt the need to opt Safely Remove cycle. Safely Remove Icon click turns pwr lite back on. Don't know damage by sudden pwr lite off with Exit ...then... pwr lite on with Safely Remove cycle. I've created new full Image and opted Safely Remove cycle first. Wait (pwr lite slow off). Then, Macrium Exit. That'll work. Thanks again!.
Hi Peter. Thanks! I finally upgraded to Reflect Home version 6.1.1225 from version 5.3.7310 (Pro); (long time overdue, I know...). No problems with license key. Using as you said PE 5.0. Boot menu "updated". Recovery disk (CD) made with PE 5.0. Is the option to make a Linux recovery disk removed in version 6 ? I could not find it. I was used to make one too, just in case, although I never needed it. I still have to test things to see whether they work on my PC. And to make adjustments to my liking. Thanks! Jan
The thing I really like about Reflect is that "It just works". That's important to me with a backup application.
GFS Backup Query: Just looked at the Scheduled Backup within the Gui and notice that my setup (full : first Wed every month Diff: every Wed of every week Incr: every day) shows up with last results Full: successful Diff: conflict Incr: successful I suppose the conflict is due to last Wednesday being the first Wednesday of the month and a wednesday, so the conflict was being running a full or differential. Am I right in assuming this is as it should be ? Stating it as a conflict makes me a bit nervous. Looking at the images in explorer I can see a full image was created. Is it advisable to change the diff from Wed to Thursday to avoid this situation?
I had understood MR to resolve this provided the two backups were at the same time, but someone more clued up than me will need to confirm. I have full scheduled at 3:30 am first Monday of every month, diff scheduled every Monday at same time with no apparent issues.
Beethoven, if your above schedules are all included in the same DEFINITION file and have the same time of operation, there should be no conflict of any sort. Reflect, when it finds identical schedules and different image types using the same DEFINITION, will choose the most relevant (Full over Diff over Inc) and dispense with the others for that particular time point. Many of us use those schemes without issue (paulderdash above). Can you tell us where you saw the "conflicted" msg? Better yet, give us a screen capture to look at?
Guys, I never noticed this before but then again, GFS is running nicely in the background, so I seldom look at it. Screenshot attached
Well, it looks like your schedules are whacky as to when they're supposed to run next. Did you have the right date when they were set up to begin with?
RBF, not sure what you mean as to being whacky and the right date? To me next runs look perfectly allright with the next full on Wed 1 June, the next Diff on Wed 11 May and the next Incr tonight. My original schedule is as attached - not sure how a date could be right or wrong but if I need to change the setup to prevent Full and Diff to fall on the same day, I will certainly do so.
B, that's my bad. I was reading your scheduled DATE in US Format (MM/DD/YYYY which is what I see) rather than WORLD Format (DD/MM/YYYY) which is apparently what your UI displays... sorry. Anyway, where was that "conflict" msg you referred to above... I'd like to see it if possible.
RBF - the error message is in the first screenshot in the column "Last Result" - you will see the full and incrementals shown as Success but the diff as Conflict. As mentioned before, maybe this is as it should be as only the full was running this being the first Wed of the month and thus no need for the Diff.
Turns out I had that exact same situation this morning (scheduled FULL & DIFF at the same time <every 4-weeks>). I looked at the "Last Result" column and saw exactly what you saw... "conflict." I really had never noticed it before because that column was always sized too small to see the whole msg, I usually just check my LOGs using the "Logs" TAB and never saw an issue. This appears to be normal when 2 or more schedules referencing the same DEFINITION conflict in time... Reflect just performs as expected doing only the relevant image requested and marking any other in "conflict." Both of us should be good to go...
PS- one thing I would not do is activate the option "Run the purge before the backup." I may have storage issues but the last thing I would want to do is purge a perfectly good backup before I even know that the one I'm about to take might fail. The current backup has to succeed before the oldest is purged. If it fails with that backup option set, then I've lost a perfectly good (and maybe important) backup before I ever get another good one. This is especially relevant if the user is using a Full retention of only 1-image. You're schedule, at worst, will have at least 2-images at retention time so the worst that could happen is you could be down to 1-image before a new one is attempted. To be a little safer, you might wanna change you Full retention to "# of backups" instead of "weeks" and the number to 3... that way you'll always have at least 2 Full images available if your image fails when your disk gets full.
just used a rescue disk to boot and went chose explore image to check if the image "looked" allright. While the tree and files are all there, trying to open any file (jpg. / mov./ tif / xls) just gets me "cannot open the file" - no associated program found. I am fairly sure I have done that before but maybe not from the recovery disk. Is that an issue I should be concerned about or will this feature not work in the recovery mode.
Remember, B, all the helper files that are needed to view that selection (Office, Windows Media Player, Picture Viewer) are most likely not installed in the Recovery Media. Try the same thing under LIVE Windows and you shouldn't have any problems. I'm sure the image is just fine but WinPE is not a very robust Windows build so you probably can't see most of the stuff you reference.
Thanks Froggie, you are right of course. I tend to get confused as to the prime purpose of the rescue disk - it's booting (doh), for checking the image I should do that in the live environment.
