Under Windows, DAR doesn't restore symlinks. Instead, it creates regular files that only Cygwin understands.
I'm using the 2.4.6 build uploaded to SourceForge.
Symlinks do not exists under Windows XP, which is the only windows system I have access to. To have support for symlinks under windows Vista or 2008+ you need to install cygwin on your system with all the necessary packages in order to compile dar, then get dar source tarball and compile dar. You can use the script misc/batch_cygwin to obtain in one command a new binary of dar using the cygwin adaptation layer suited for your version of Windows.
That's all I can do, sorry :
If windows OSes were free, I could maybe afford having a virtual machine of each and provide dar binary accordingly. However, I will not spend money for that poor closed freedomless systems, while I develop dar freely on my free time without the need of a windows system of any kind.
Hope you'll understand.
What? That doesn't make any sense. Even if you only have access to XP, you should still be able to produce binaries that use functions from newer versions of the API.
And please spare me the propaganda.
"Today [symlinks] are supported by [...] Windows operating systems such as Windows Vista, Windows 7 and to some degree in Windows 2000 and Windows XP in the form of Shortcut files."
source : http://en.wikipedia.org/wiki/Symbolic_link.
shortcut files are not symlinks and XP does not know how to handle this type of filesystem object. In another hand, the binary built upon cygwin upon windows XP does not seem to be able to handle windows 7 symlinks... seen your report.
I rather suspect that cygwin installer selects specific binary according to the underlying windows version (here XP). Or, maybe cygwin on any windows plateform is never able to handle windows 7 symlinks? In any case I can't fix this problem : This is Cygwin internal.
Sorry for the propaganda, was not at you.