Upgraded to v7. Is it possible to run a script when a backup job is completed (instead of sending an email)? I'm asking because I would like to get a push notification on my iPhone when the job is finished. The service I might use for that does support email, but allows more options if I could make a REST call using curl (in a script?).
Right-click the definition file and select “Generate script” for the script language you want. The wizard allows you specify a pre- and/or post-backup program to run if that’s all you need, but you can also directly edit the script later however you want. You’ll find that script under the corresponding scripts tab within Reflect. So you don’t have Reflect run a script. You use a script to run Reflect and also do whatever else you want. Make sure you then associate your schedules with the script rather than the definition file if you use scheduling.
Purchased V7. Haven't installed yet. Anything I need to know about or worry about as far as the upgrade from V6-V7?
You may want to back up your definition files if you haven't already, since 7.2 adds some new XML tags for its new warning job outcome, and V6 therefore might not accept your definition files after they've been updated by 7.2 if you decide to roll back later. Making a Rescue Media ISO from your current installation wouldn't be a bad idea just to be extra careful. If you need SMB1 support on your Rescue Media and are currently using WinPE 10, you'll need to either drop to PE 5 or deal with a few workarounds for now, although it seems Macrium may be addressing that. Other than that, if you're already on V6, I haven't seen any widely reported issues. If you were on V5 it would be another story since you'd have to check your definition files after moving to the completely new retention policy setup introduced in V6, but that's unchanged for V7.
Same. FWIW I just went ahead without precautions and updated, with no problems - including scheduled tasks, even incremental. Haven't created new Rescue Media yet, waiting for Win 10 1809 which hasn't arrived for me via WU yet.
I purchased the v7 upgrade offer soon after it was released when I was on v6, but I tried it for a few days on one computer and went back to v6, and it is still going flawlessly. I can't remember the exact issues that I had with it, but it was in its infancy at the time, so maybe it works fine now. But, even still, it I didn't see any compelling features to require the upgrade. I just haven't bothered upgrading all my computers to v7 when v6 is working flawlessly. I just don't see the point. They made v6 so good, it never lets me down, so why change? So, I may even wait until v8.
True, most likely won't use any new features but the upgrade with BF 40% discount just made it a no-brainer really. I figured unsupported v6 may just run into problems Win 10 v1809 and beyond.
What does BF mean? I Googled it, and it came up with boyfriend, and I am sure your boyfriend didn't pay for 40%.
That's good if you bought upgrade to v7. Those that haven't might not be eligeble to upgrade directly from v.6 to v.8 when it comes out.
Hm, first incremental backup of less than 1 GB (from SATA HDD to SATA HDD, both internal) took 40 minutes, while it usually took v6 less than 15 minutes...
I haven't seen any indication that WinPE 10 1809 has any changes that are relevant to Rescue Media. The initial 1809 release that Microsoft later pulled actually introduced a problem that prevented Reflect from loading certain drivers automatically at startup even though they could be manually loaded afterward, but the "1809 re-release" solved that. But if you'll be using WinRE as your Rescue Media build choice, there's no real reason to wait until you update Windows because the Rescue Media Builder will just update when you do, and you won't have a large cache of files lying around somewhere else because WinRE just builds from the contents of your Recovery partition. And if you'll instead be using WinPE 10 as your build choice, then you'll be using WinPE 10 1709 no matter what. You're welcome! If you decide to use PowerShell and need any help, let me know. Biggest features from V6 to V7 are CBT, Image Guardian, and viBoot. Of those, I like Image Guardian even though I keep an offline disk because I don't update the offline disk as often as I should, and viBoot can be handy in a variety of situations. But there are also some smaller features I wrote up in this post if you're curious. And now that 7.2 is here, the new Rescue Media Builder that doesn't force large downloads from Microsoft and supports Wi-Fi can be nice, and I really like the new "warning" job outcome. The previous behavior where certain problem conditions (incomplete backup sets, consolidation failures) still resulted in the job being treated as a total success can and did cause some pretty significant risks or actual incidents for people, so I was glad to see that addressed.
Sorry for my ignorance, but how do I back up my definition files? Thanks to everyone else for responding. Most helpful.
Hello @Alexhousek, By default, the definition (*.xml) files are located at "C:\Users\*****\Documents\Reflect". Just copy the contents of that folder to a safe location. I hope this helps...
Yes, please. I created a "reflect" webhook in IFTTT and let it generate a push notification when triggered. I used this DOS command to test: Code: curl -X "PUT" -H "Content-Type: application/json" -d "{\"value1\":\"Image of SSD is finished\"}" https://maker.ifttt.com/trigger/reflect/with/key/<mykey> And that works fine (I get a push notification on my iOS devices). Now I tried to put this in the "success block" of the PowerShell script: Code: function OnBackupSuccess() { Write-Host " * Backup succeeded ($strXmlFilePath)."; curl -X "PUT" -H "Content-Type: application/json" -d "{\"value1\":\" Image of SSD is finished \"}" https://maker.ifttt.com/trigger/reflect/with/key/<mykey> } (note: the weird formatting is by the forum software) An image is made when I run the script, but no notification is generated. How can I debug/improve this?
The Reflect folder with the .xml file can be permanently transferred to another disk partition, and in the MR settings, specify a new path to the .xml file.
Sure, but that doesn't create a backup of the existing definition files before the 7.2 update might modify them. Additionally, definition files should be stored in a fairly locked down location. The default permissions for other partitions allows regular users to modify data on the partition, and that can be a security risk for definition files, because malicious users can leverage the ability to modify definition files to have Reflect help them steal data or even execute a malicious retention policy, even from a non-admin user account. By comparison, if the definition file is stored in its default location of your user profile's Documents folder, then other non-admin users can't even read the file, never mind modify it. Macrium wrote a KB article about definition file storage here, and these risks and others are why I wrote a Wish List thread requesting that Image Guardian protection be extended to XML files registered within Reflect here.
This is a great request, thanks! Until then, my .xml are located on D and are backed up in two more locations, including a mobile USB3.0 HDD.
Yes, you can, which I also do, but if you change drives, you have to edit the drive ID, from memory. Someone posted how to do that on here, but I am too busy right now to look for it.
