Group: Forum Members
1st, some background: I have a number of clients that I've installed MR for that backs up to multiple external USB hard drives for the purpose of offsite rotation. I've developed a simple batch script (Windows) that allows me to identify the drive letter of the backup target then modify the MR XML config file (using FNR.EXE) then launch MR via command line. This way, regardless of which backup drive gets plugged in and whatever random drive letter it gets assigned to it, I can still find it and pass that along to MR. This also help if the user has one or more USB flash drives plugged in and/or network drives mapped that may hog preconfigured drive letters. It just lets MR work, period, regardless of drive letter. Also, MR automatically figures out what type of backup (Full, Incr, Diff) based on the files on the target drive (guid-xx-yy) that happens to be mounted. This has worked flawlessly for several years now, since v5.
Now a comment leading to my question: Reflect v7's new MIG feature is exactly what I've been waiting for. But in reading about MIG, it appears that MIG identifies the target drive\directory by examining the XML file then protecting the MRIMG files in said directory. Well, that won't work for me. In the XML, I specify a known sentinel (a dummy path that would never happen) that I search for using FNR.EXE and then replace that dummy path with the discovered drive and path for *this particular run* of MR. Again, works great.
Now my question: Q1: Am I understanding MIG correctly in that, does it indeed examine the XML to figure out where the MRIMG files are? I mean, that makes sense, but it'll break my code. Q2: Can MIG be somehow be configured via command line where to look for MRIMG files to protect? Q3: And can that protected location be changed on the fly? Q4: Finally, anyone else facing the problem wandering drive letters and how did you resolve them?