Group: Forum Members
Hi Richard, and thank you for contributing to this thread, I appreciate it.
I'm pretty new to Macrium products and currently evaluating Reflect to see if we can migrate over to it from another imaging software. So I guess that I just might see something obvious here...
All other imaging software that I have been using since 1980's have had a trivial way to distinguish between incremental, differential and full backup files. Most often this information is recorded directly within the filename.
I learned that Reflect creates a set of environment variables (MACRIUM_*) that should provide the information I need, so I created a VBS script from the backup XML definition and tried to use them. However I encountered some strange problems there, too.
For example, it seems that the variables are created only before the backup operation starts, so they reflect the situation before creating the new backup. Since they do not seem to be updated after the backup operation has finished, there seems to be no way to detect inside the VBScript file what was the type of the backup just created.
As we have a need to integrate the backup imaging product into a higher level backup/archival software we have used for years, we must find a robust way of detecting the backup method used to create any existing image file.
I only recently learned to know the existence of Macrium and Reflect, and I must say that I was very surprised in a positive way. I was actually surprised that I had never before even heard of Macrium. After version 7 will soon be out, I think that it may well be the only product in the market to fulfill all our needs out of the box if it only will keep its high reliability AND IF we can find a way to detect the backup method for the created images.
I have already learned to like MR so much during my feasibility study that I'll be really sad if I have to conclude that we cannot migrate over to using it due to this single piece of missing information...