Windows 10 Junction on UNC path

black3dynamite

Already tried mklink /h?

JaredBusch

@black3dynamite said in Windows 10 Junction on UNC path:

Already tried mklink /h?

That results in: Local NTFS volumes are required to complete the operation.

Using UNC or mapped drive letter.

Found an old post on here, and I used /D in that example.

JaredBusch

When using /D, Windows works as expected, but Crashplan shows it as a 0 byte file.

JasGot

My hunch is that your symlinks are not fully enabled.

Run this on the both sides (your computer running crashplan, and also the server you want your backups to reside on)

fsutil behavior query SymlinkEvaluation

You will likely find this:
Local to local symbolic links are enabled.
Local to remote symbolic links are enabled.
Remote to local symbolic links are disabled.
Remote to remote symbolic links are disabled.

The "remote to" are your problem.

Run this to enable them:

fsutil behavior set SymlinkEvaluation R2R:1

The quick way through is to just run this on both, but you may wish to run it on your workstation and try the backup, and then run it on your server is it still doesn't work.

If this is a complete failure, I apologize

Edit: R2L at the other end....

black3dynamite

@JasGot said in Windows 10 Junction on UNC path:

My hunch is that your symlinks are not fully enabled.

Run this on the both sides (your computer running crashplan, and also the server you want your backups to reside on)
fsutil behavior query SymlinkEvaluation
You will likely find this:
Local to local symbolic links are enabled.
Local to remote symbolic links are enabled.
Remote to local symbolic links are disabled.
Remote to remote symbolic links are disabled.

The "remote to" are your problem.

Run this to enable them:
fsutil behavior set SymlinkEvaluation R2R:1
The quick way through is to just run this on both, but you may wish to run it on your workstation and try the backup, and then run it on your server is it still doesn't work.

If this is a complete failure, I apologize

Edit: R2L at the other end....

Why isn't "Remote to" not enabled by default? Security?

JaredBusch

@JasGot said in Windows 10 Junction on UNC path:

My hunch is that your symlinks are not fully enabled.

Run this on the both sides (your computer running crashplan, and also the server you want your backups to reside on)
fsutil behavior query SymlinkEvaluation
You will likely find this:
Local to local symbolic links are enabled.
Local to remote symbolic links are enabled.
Remote to local symbolic links are disabled.
Remote to remote symbolic links are disabled.

The "remote to" are your problem.

Run this to enable them:
fsutil behavior set SymlinkEvaluation R2R:1
The quick way through is to just run this on both, but you may wish to run it on your workstation and try the backup, and then run it on your server is it still doesn't work.

If this is a complete failure, I apologize

Edit: R2L at the other end....

No difference, but seriously good idea to check. Thanks.

JaredBusch

Yes, I can copy the files to the local machine and let the backup take it from there. But I never had to previously. It, the script to copy the files, would just be one more point of failure.

pirho99

@JaredBusch
You can use BareMetal VHD loader to mount a vhd/vhdx on a network drive at startup, and Crashplan will see that as a local drive. link

dafyre

Is Crashplan running as a particular user?

If it's running as "System", it won't see the junction, will it?

marcinozga

Ok, so junction points don't support mapping to network path, symlinks do, and hardlinks can only be created for files, not folders. Try creating symlink and then create junction to the symlink and see if Crashplan can be fooled that way. So mklink /D C:\fake-Backup \\server01\Share\Subfolder and mklink /J c:\backup c:\fake-backup .