Data Backup Conundrum

I have no idea what you've done.

But here is a thread on the topic.

junction -s c:\ > output.txt # Store in a file for post-processing.

But the thing you have triggered, seems to be a unique second mechanism. Triggered by attempting to rename something in File Explorer, which might actually be under a Junction. While File Explorer seems to be able to deal with $FileName resources, it's unclear whether there is any intelligent handling of attempts to rename Junctions. Hardlinks should be OK, as they're implemented as multiple $FileName and should be edit-able.

In any case, parse the above thread and write us a summary of what worked and why it worked :-) What you've discovered, this would completely escape any utilities I have. I would not know one of those was present !

Paul

ISTR the localized name thing is more intended to allow the default folder names like "Desktop" to be rendered in international characters. Desktop.ini can also contain other links to apps needed for preview.

I expect it is more likely to be the backup program not understanding a junction or hardlink... I have also seen cases where software gets confused if you mount partitions into part of a existing directory hierarchy (i.e. *nix style). Things like failing to account for the storage requirements of the grafted partition when assessing size of the tree it is grafted into.

I once had a floppy disc with a faulty filing system. One directory contained a directory link to itself. This had very bad consequences when I tried a recursive directory listing.

John