OK - let me try ...

Normal backups do the following ..

Monday - files A, B and C are backed up in a full backup

Tuesday - file D is created and gets backed up by the incremental backup

Wednesday - file A is deleted - nothing new to backup

Thursday - File C gets moved to a different directory - gets backed up as considered a new file

Friday - server breaks - So you restore it all from full and incremental backups - when done you have restored file A, B and C from the full, D from the incr, C to a second location.

So you server doesnt really look like it did when it broke - you have a file back on it that was deleted plus one file in two locations.

So if you use TIR with Move detection you get the following:

Monday - files A, B and C are backed up and the TIR mapping taken

Tuesday - File D is backed up and a new TIR mapping taken

Wednesday - nothing to back up but new TIR mapping taken

Thursday - Nothing backed up as TIR realises that the file has just moved - new TIR mapping taken.

Friday - When you run the restore it looks at the latest TIR mapping so this time when you do the restores you get B, C only once in the latest location and D.

So now your server looks exactly like it did when it was last backed up

Does that make any sense?