Hi,

I need to change the path to my backup files. 

When I first started using Reflect I needed to do this.  I did it by creating the new path, moving all my *.mrimg files from the old location to the new one, and updating the Backup Definition File to refer to the new location. 

Afterwards Reflect seemed happy: it displayed the backups correctly in the Restore tab and the log files correctly in the Log tab.  However when the next backup ran instead of creating an Incremental backup (which it should have) it created a Full backup.  The log entry said that the Backup Type was "Full - Incremental specified but no image set to append to". 

That wasn't what I expected: thought it would create an Incremental backup based on the previous Full backup.  Is there some way to do this so that subsequent Incremental or Differential backups don't ignore the backups created with the old path? 

Thanks,
Mike

Reflect's backup task definitions identify drives and partitions "by the numbers", so to speak.  If things get moved to another location that has a different numeric drive or partition identifier, it makes the existing task definition invalid and causes confusion for subsequent operations based on that task definition.  Is that, perhaps, an explanation for what happened in your case?

Regards, Richard V. ("Arvy")

Hi Mike

Changing your backup destination and copying your existing image files to the new destination will be fine.  

The message "Full - Incremental specified but no image set to append to" indicates that your backup definition cannot find any image files in the backup destination folder that match the partitions specified in the backup definition. 

Please see here:

http://knowledgebase.macrium.com/pages/viewpage.action?pageId=2457715

Kind Regards

Nick

Macrium Support

See our reviews on

Nick & Arvy,

Actually, I had forgotten that I decided to change the drive letter for the backup folder from G: to M: (M stands for Macrium, which is easier to remember).  I'm pretty sure that I did that at the time this happened.  Is that the problem?  I didn't make any changes to what was being backed up. 

Arvy, you say that this "makes the existing task definition invalid and causes confusion for subsequent operations based on that task definition".  Does that mean that the backup images created before I made the change will no longer work? 

Thanks to both of you. 

Mike

Hi Mike

Arvy was referring to changing the source of the backup not the target. His response is not relevant to your situation. 

Please read the KB article for the reasons for the error "Full - Incremental specified but no image set to append to"

http://knowledgebase.macrium.com/pages/viewpage.action?pageId=2457715

The following KB article 'How Backup Sets created and maintained' may also be useful for your understanding:

http://knowledgebase.macrium.com/display/KNOW/How+backup+sets+are+created+and+maintained

Check the log(s) for the image(s) that you copied to your 'M:' drive and confirm that the partition(s) you have imaged are *exactly* the same as the partition(s) you are currently backing up. 

Kind Regards

Nick

Macrium Support

See our reviews on

No, not at all.  The validity and integrity of the backup image files isn't affected in any way by merely moving or copying them to another location.  Nor are the backup images themselves affected by assigning a different "drive letter" to the partition on which they reside.  It's only the backup task definition (Reflect's "operational plan" if that makes it any clearer) that can be affected by changes of that kind.  In this case, it appears that other changes in the backup task may also be involved causing Reflect to decide that a new full backup was required.


Regards, Richard V. ("Arvy")

Nick & Arvy,

Nick, I had already read the first article but not the second.  It was very helpful. 

I think I now understand backup sets pretty well.  After rereading the article on what triggers a full backup I still don't know why that happened previously.  That's not really a problem: what's important is that I'm now clear on what the effect will be when I do different things. 

So I'm going move all my *.mrimg files from the old location to the new one, update the Backup Definition File to refer to the new location, and tell Reflect to look for backup files in the new folder.  I believe that the next backup (which should be incremental) won't be forced to a full, and I believe that if I need to use the backups from before the change they'll work correctly.  Also, my understanding is that I can move around backup files however I want, and as long as none are missing or corrupted and I tell Reflect where they are then everything will work correctly. 

Thanks again for your help. 

Regards,
Mike

Hi, I don't know if this thread is still living but I have an almost similar problem:

I did a F&F folder backup of my <I:> drive some days a ago ( It was just an HDD data drive, no OS on it) but I had to re install my system yesterday and my ex <I:> source drive became a <D:> on the new installation. 
Do you think it will raise an error if I launch a differential backup of the F&F .mrbak file ? 


edit: I don't have any .xml associated to this backup