Retrospect handling of NTFS Junctions?

[jhg]

It appears from my experimentation that Retrospect does not follow junction points and backup the files from the junction's target.

Is there a way to control this behavior (i.e. a "follow links" option)?

[mbennett]

Something jiggled my memory when I read this question. NTFS is mentioned 51 times in the user guide, but I think this is the important point.

Open File Backup Unlimited – Protects open files on NTFS-formatted volumes on Windows
servers, desktops, and laptops. This add-on makes it possible to protect line-of-business
applications—such as accounting, CRM, and proprietary database systems—while they’re
running, even those with data files spread across multiple volumes. Retrospect’s Open File
Backup Unlimited add-on extends to all Windows systems protected by your Retrospect host
server, including end-user desktops and laptops.

That said, it might be you need to work with the Selectors.  This problem may also be caused by Windows security settings for the NTFS share. There's also this mention:

Windows Volume Mount Points (NTFS Mounted Drives)
Windows allow you designate an empty folder as a volume mount point, a kind of gateway for
accessing a different drive. For an overview and configuration instructions, see the Windows help
index under “mounted drives overview” and “mounting volumes as NTFS folders.”

There are many other mentions, but I would say the answer is yes if you have the right license, you just need to open the Acrobat doc and Ctrl-F for NTFS. If that doesn't answer your question email support@retrospect.com

[Nigel Smith]

Does this apply to any and all junction points, or just some? (Remembering the fun people have with OneDrive FOD and similar...) Are the point/target on the same or different volumes? Are you logging any messages about these failures?