Since I'm on a roll... I'll resurface other discussions as well.

[SOAPBOX] A loooooong time ago in a far away galaxy (circa Feb2015) it was mentined that there didn't seem to be any real logical reason to limit the SYNTHETIC FULL to only "# of Backups."  It was suggested to add that option to some, if not all, the other options available in the INCREMENTAL retention area.  Somebody from Macrium thought that was a great idea and would consider it in a future release.  This is just a "bubble to the top of one's memory" request for that function 

The other area suggested for change was the scheduling area for INCREMENTALS, primarily (although it probably could apply to both DIFFs and FULLs as well, although not as needed in those areas).  The request was for an HOURLY consideration in the scheduling area along with the Daily, Weekly and the others.

The main reason for this was after a healthy discussion with Macrium's marketing team, they were made to understand how this product, which now includes Rapid Data Restore, could easily offer itself in the typical "snapshot" environment.  Since that time, many previous users of both AX64 Time Machine (same principle as RDR) and Rollback RX (a snapshot "solution") have moved into the Macrium arena.  Why?  Because the reliability of Reflect vs both of the previous mentioned snapshot solutions is superior.  What is missing in the snapshot arena is that no one knows that Reflect can accomplish this capability now that it's armed with RDR.  The only thing missing is the marketing effort brought to bear in this area as well a finer resolution for the automatic incremental snapshot.  Reflect can easily do MANUAL snapshots with its current capability... all that's missing is a smaller time slot for the incrementals... VOILA!... hourly incrementals.  I think the snapshot capability of this tool was lost in the initial public presentation due to the breed of the product... an imaging/backup application.  With RDR it can not only do that but provide a snapshot capability along with its history of reliable imaging.

Macrium should "market" that snapshot capability with gusto... and in the meantime, add the hourly scheduling parameter to meet a lot of the existing snapshot needs in the marketplace. [/SOAPBOX]

Regarding your second item, it would seem to be a fairly straightforward user interface issue.  Reflect's current scheduling interface (1st image) makes no provision for hourly repetition.  However, the item that Reflect actually adds to the Windows Task Scheduler (2nd image - Advanced Settings) would allow hourly repetition despite its "Configure for: Windows XP" limitations.  (Something else that may be overdue for reconsideration.)  I haven't actually tried it, but I would assume that one could use that Windows Task Scheduler provision for hourly repetition even as it stands.  Perhaps Macrium will confirm (or deny) that capability in acknowledging your suggestions.  To be honest, I'm not sure that I like the "marketeering" advice much, but that's beside the point.






Regards, Richard V. ("Arvy")

Hi Arvy!  Yes, that "tweak" in the actual schedule works just fine (that's what some snapshot users have done), but as soon as you do it, the Reflect DEFINITION no longer sees that scheduled item and therefore cannot be edited/removed via the Reflect UI, it must be done at the scheduler level.

I'm not sure whether you've ever been a heavy snapshot user (quick return to previous time points <and time point return via regular imaging/restoration without some sort of RDR feature is not what I would call "quick"> ), but if so, as a snapshot user you would be generally thrilled with Reflect's new RDR feature.  Previous snapshot solutions of almost all kinds have been iffy due to unreliable time point return, in the case of imaging type applications, or just plain disk explosions in the case of non-imaging applications... neither of these scenarios is acceptable to a concerned user.

When v6 was "unofishuly" dropped on the Wilder's Security Imaging forum in January 2015 prior to its official release, many users began to play with the "non-Beta," both in the areas of imaging and as a possible snapshot tool (only due to RDR).  Excitement built rapidly especially amongst the snapshot app users.  Soon it was clear that this previous imaging app now had a real place amongst snapshot applications.

At the time, whilst in the middle of a pre-release issue with the application, I was contacted by the organization responsible for the primary marketing of this particular release of Reflect.  They thanked me for my "beta" effort and during the discussion the snapshot capability of the application came to the surface.  They said they weren't very familiar with that user community so we chatted for quite a while concerning that issue.  They thanked me for my input and stated they would look seriously on integrating that capability into their marketing approach for the new version of Reflect.

Since that time I have seen nothing in the marketing or literature concerning that capability of Reflect v6.  I just thought it would be nice to possibly bubble up that seeming interest of Macrium's in that capability.  The snapshot community is pretty large but at the moment there's no real way to draw their attention to Reflect other than through referrals... which has been large via the Wilders Security Forum and decent via word of mouth.  I just felt at the time (pre-release) that it would be good way to add to the re-positioning of the product about to be announced.

Possibly Macrium felt no need for this... of course that was their decision to make.

A very generous explanation, Froggie, and I thank you for it most sincerely.  Frankly, I did wonder just a little about those "marketeering" insights, but thought it might be impolite and not advisable to inquire too closely about it in an open forum milieu.  So I didn't, but it's good to understand the background none the less.

No, I've never been a big fan of semi-continuous snapshotting, but I can understand its appeal for others more inclined to be adventurous and 'playful' with their system setups and various applications than I am.  And I'm certainly not opposed to what you are suggesting so long as it doesn't detract from what I consider as primary backup and recovery functionality and, most importantly, doesn't involve any "distortions" of the operating environment that I'm trying to preserve and protect.  The latter consideration, BTW, is my main concern about the so-called "superfast change block" stuff.  RDR is okay, I guess.

Yes, I know I'm an "old geezer" stuck in his own preconceived notions and ways of doing things.  But "old geezer" support constitutes an important and ever-increasing part of market demographics too, I think.  

Regards, Richard V. ("Arvy")

I agree with you wholeheartedly... the main product should not be compromised or its function detracted from.  My suggestion for HOURLY scheduling clearly does not do that.

As far as marketing is concerned, it's just an attempt to open up the product to another class of users, not change the product in any way.... it already does what's needed today, it's just that potential users don't know that   Even the new users who love the "fast restore" that Reflect is offering them, many of them don't realize why that's even happening at all, especially since RDR is DEFAULTed to when doing recoveries.  I find this all the time when chatting with new Reflect users.

And, of course, "old geezer" marketing is very important and will become more so as us boomers down our omega-3 fats and antioxidants in great quantities... we're gonna be around for a long time 

...and Macrium almost called the new RAPID DATA RESTORE "RV"R rather than RDR in appreciation for one of its more prolific Forum members, but then they came to their senses 

Well, I guess we're both okay with it as proposed ... so long as they don't hire Satya Nadella and his team of "visionaries" to start bugging us about "Get Macrium X" ... OR ELSE!

Regards, Richard V. ("Arvy")

Once again... agreed.  That superfast change block stuff also scares me.  The two apps I'm most familiar with that use a so called "tracking" function both have significant shortcomings... both are seriously affected by EXTERNAL volume modifications (WinPE, Linux, etc) and don't reliably operate under any type of LITE virtualization... once again the tracking information is lost and must be re-established.

These are both tough nuts for Macrium to crack... but I do await the results.  As long as RDR remains an option to use, I will be a happy camper.

Hello,

Feature request(s) submitted for evaluation  

Kind Regards

Stephen

See our reviews on

Thank you for the consideration, Stephen... and I really did like "RV"R (Rapid Verification and Restore)