Quantcast
Channel: File Services and Storage forum
Viewing all articles
Browse latest Browse all 13565

Windows Server 2012 R2, running restore-dfsrpreservedfiles, getting path, file name or both are too long error

$
0
0

Trying to recover some deleted files that are located in the DFSRPrivate folder as Conflicted files due to an erroneous change made on the primary server in the replication group.   I am getting the error shown below when I try to recover those files (which are listed in the manifest file).   Is there any workaround/solution to getting these files back using this mechanism?  I am trying to do recovery to a different folder so I can copy from it, but running with RestoretoOrigin gives the same error.  

Alternatively, if there's a way to de-obfuscate the files in the DFSRPrivate directories, that might be a reasonable plan C.

Initially tried to do a disk based recovery from the primary server, but there are differences.   Server is Windows Server 2012 R2 64 bit.

Any suggestions would be gratefully received.


PS F:\recovery> Restore-dfsrpreservedfiles -Path ".\DFSRPrivate\ConflictAndDeletedManifest.xml" -RestoreToPath F:\rd
Restore-dfsrpreservedfiles : The specified path, file name, or both are too long. The fully qualified file name must
be less than 260 characters, and the directory name must be less than 248 characters.
At line:1 char:1
+ Restore-dfsrpreservedfiles -Path ".\DFSRPrivate\ConflictAndDeletedManifest.xml"  ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [Restore-DfsrPreservedFiles], PathTooLongException
    + FullyQualifiedErrorId : System.IO.PathTooLongException,Microsoft.DistributedFileSystemReplication.Commands.Resto
   reDfsrPreservedFilesCommand

Patrick W. Foster

Newton, MA



Viewing all articles
Browse latest Browse all 13565

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>