Paths that begin with \\?\GlobalRoot are internal to the ker

[DeanGTS]

10/07/2014 18:19:06 :: Task V:\DIR\DIR\My Documents\JR History\Old Desktop Files\Completed work\DIR\planning list 14.xlsx failed: Paths that begin with \\?\GlobalRoot are internal to the kernel and should not be opened by managed applications.

New issue I've never seen, just wondered if I was doing something wrong before creating a support case.
Anyone have any idea's, this is a File to Tape job from a Robocopy sync'd directory.
Thanks in advance

[veremin]

Hi, Dean,

The quick search suggest that you're the first one to come across this issue. Please, open a ticket with our support team and let them find the root cause of this behavior.

Thanks.

[DeanGTS]

Thinking VSS issue but how to resolve.. ?
Is VSS necessary for File to tape jobs?

I have other directories with veeam .vrb/.vbk in this same Tape job and if the offsite location is being updated, I'd guess the shadow copy is required..

[DeanGTS]

mmmkay no problem v.Eremin!

[veremin]

VVS allows backup of files locked by application and provides file-level quiescence, etc. If it's your major suspect, you can disable the option temporarily and see whether it makes any difference.

As to the support ticket, once it's opened, kindly, post its number here for the convenience of future readers.

Thanks.

[DeanGTS]

CaseID: 00600215

[brifin5]

Well, you can use Long Path Tool, it works.

[DeanGTS]

Disabling VSS on a newly created job for this specific DIR, processing the folder separately to my current File to Tape job.
Support suggested this should be resolved in future patches, Thank You!

p.s. brifin5, it's doubtful that that tool would be of any use to vss system paths during a Veeam backup.