As this is an OS limitation there is not a lot that BackuP Exec can do - once you have identified it has affected a restore, you can redirect the data to the correct place.

You could also reduce the frequency between the full backups so that it is less likely to happen.

It is possible that a Synthetic Backup or True Image Restore  backup (using The Advanced Disk Based Backup Option - chargeable extra) might handle the rename in a better way

Dear Colin,
that's what I guessed. Sigh. Indeed I did a redirection, but of cause only in that cases a user notified me. So a more frequent full backup is recommended :-( Maybe I can convince the OS to change that folder behaviour. Any Idea will be appreciated:-)
Kind regards.
fortitudo

You may use backup with modified time, as modified time does change on rename of files. So, that should take care of this behaviour.

Thanks

I don't think the modified time will work either as I believe changing the folder with a rename will leave the time stamps of the files alone - what he really needs is a method of changing either the archive bit or the modified time of the files in the folder when the folder is renamed so that the next differential will backup the complete folder again. As I don't think NTFS provides this functionality though there is little that Backup Exec can do - we will have still backed up and restored the data it is just that some of it will be recovered to the old folder name - and some of his files will have 2 versions, one in the old folder and one in the new folder - at least until the next full backup runs when the rename will be fixed for the next differentials

So my classical backup strategy "full Backup followed by several differential backups first to disk then to tape" cannot avoid this behaviour. Unfortunately I havn't neither the budget nor a backup window to do a daily full backup (approx. 2.5 tera byte). How do you guys avoid this?
Any hint would be appreciated:-)
Kind regards.
fortitudo