Oh yea... what BETA? This is the WILDER'S CORPORATION "Private Preview." I, too, can confirm Pete's problem with the RUN function on the DEFINITION Toolbar. Now... how do we go about getting this information back to the Macrium Dev Team... smoke signal?
An anomaly.. but definitely not a bug. Since Macrium doesn't update its LOG until after it completes it operation, when returning to a snapshot, there will be NO log entry for that snapshot... mainly 'cause they're currently managed on the same backed up volume.
I am starting to get a headache,,,,, but I guess I am glad you guys are pushing it so that when it comes time to set this baby up someone will be able to tell me what (and what not) to do. Now where is that bottle of Aspirin.
Hadron, I believe if you do the official upgrade (when it's available), it will install over the existing version... that's the only thing that makes sense. But don't take what I say as gospel... ask Macrium support when the time comes. We've been doing what Pete did just to keep things pretty clean during our testing phase. What I will do for you is try and install the TRIAL over an existing v5.3 system I have laying around... will let you know how it goes.
You can keep them when you uninstall 5.3, but frankly at this point I'd delete them and start over. Now it may turn out when they release, they may have an upgrade mechanism so you can update in place. But that is an unknown at this point. Pete
Barry It may sound complicated right now, but remember we are learning as we go with no documentation. And actually it isn't nearly as bad as it sounds. Pete
Hadron, I set up v5.3 to have a coupla DEFINITION files and two schedule entries, checked them out, then installed the Mv6 TRIAL right on top of the installed v5.3. When I brought up the v6 TRIAL, the DEF files were still available and in place and the schedule jobs were also in place. From this I would assume (remember, ask support anyway) that all the usual suspects in terms of settings will remain following an installation on a v5.3 system. The hassle will be with licensing as its rumored that the current license needs be validated and a new one will be issued for use with the upgrade to v6. Hope this helps!
Hmmmm... not bad. Just received this from Macrium support concerning Pete's DEAD BUTTON issue... (talk about speed) ***contents of private message removed** <Oooops!> Sorry about the above...
HI Barry WHen it is released and when you are ready, there are several users here who have been learning and will be glad to help you. Don't worry. Pete
Thanks Pete, I am not really worried as I know I can count on you folks to answer any questions I may have (I will try to do it on my own first as I agree with you, you don't really know how unless you understand enough to do on your own).
That's exactly what I did... no uninstall of v5.3 ahead of time. PS- not only did I have DEFINITION files & SCHEDULES set up, I had also changed most of the Macrium DEFAULT settings to something other than the defaults. All remained as set (as expected) when the TRIAL was installed on top of the currently installed v5.3.
Yes they are... and they appear to be watching this thread very closely. To report issues/anomalies/failures, we are asked to use the address below. And remember, this is not a SUPPORT portal (Macrium never offers priority support to TRIAL users, especially unRELEASED software) but it can be used to feedback issues associated with v6 (Please don't ask them how to do anything... that's what SUPPORT is for... when it becomes available). Address: Feedback {AT} Macrium {DOT} com
Turns out the above is NOT a bug at all. Suffice it to say, unless you know that the backup chains you're trying to share a folder with are definitely DIFFERENT in their specifications (volume<s>/file<s> being saved, etc.), you should probably use separate folders for each of multiple backup chains you may want to run with. Thanks to MACRIUM for the above information...
I too found that mixing backup sets in one folder led to inconsistent results. I assumed mixing backup sets might have been possible (or even advisable), due to the Definition Retention Rules section when setting up a backup. Does anybody know what "Apply retention rules to matching backup sets in the target folder" and its alternative are for? The second option seems to suggest that it's ok to keep similar backups in the same folder.
What I've done is use different folders, AND a different definition file for each. That way there doesn't seem to be an issue.
As I tried to explain above... in the above context, matching backup sets have different SOURCE information but not necessarily the same ImageName or come from a single XML directive. If you have two different XML directives with different names imaging the same thing (say, your SYSTEM partition only), then Macrium sees them all the same and when doing an incremental/differential, will do it against the most recent either incremental (if incremental) or baseline (if a differential), regardless of its name or what directive it came from. The "matching sets" mentioned above would be, for example... a set imaging your SYSTEM partition only, and maybe another set imaging your whole disk, another whole disk, or maybe 2-partitions on the same disk. These backup chains have different SOURCE specs and therefore are DIFFERENT (not just in name only, possibly). These types of chains can co-exist in a folder, and with that option checked, the retention rules will be applied to both sets (say "Keep 16 incrementals")... it will keep 16 for each set. If those backups all come from the same source (i.e. SYSTEM paritition only), then they are all treated the same (a single chain) even if they have different names or came as a result of two different XML directives. I know it can be confusing, that's why I suggested you do what Pete does... even if your backup sets are indeed different, it makes it easier to understand.