Jump to content
  • 0

Trouble with File History


matser

Question

I'm having some trouble with File History on Windows 8.1. If I add folder x (tried several others as well) from my DrivePool to the Documents Library, I get a message in File History saying "File History has found files that are encrypted with Encrypting File System, on a network location, or on a drive that doesn't use the NTFS file system. These files won't be backed up."

 

It's not the most specific error message and I can't understand why I get it. I've tried copying the exact same folder from DrivePool and placed it in the Documents folder instead. When I do, the files are backed up and no error messages are shown.

 

Somebody got an idea?

 

Best regards

Mats

Link to comment
Share on other sites

15 answers to this question

Recommended Posts

  • 0

I don't have any encrypted files. Also made a test where I created a folder on the pool with one simple text document in it. File History wouldn't pick it up and referred to the same error message. If I move the folder outside the pool everything works as expected. So, File History and DrivePool is a no go then? Is this new to Windows 8.1 by the way?

Link to comment
Share on other sites

  • 0

I've flagged the logs for Alex (the develop), so he'll take a look at them soon.

 

 

Also, to make sure are you using encryption at all here? BitLocker, or per file (by using something like this http://www.howtogeek.com/178912/how-to-encrypt-files-and-folders-in-windows-8.1-using-efs/)?

Edited by Christopher (Drashna)
https://stablebit.com/Admin/IssueAnalysis/16693
Link to comment
Share on other sites

  • 0

Thank you!

 

No, I'm not using any encryption. I've tried moving the same folder and files around a bit and it's only when it's placed within the pool that it doesn't work. If it's on the system drive or another drive out of the pool everything works as expected and both folder and files are backed up by File History with no error message.

Link to comment
Share on other sites

  • 0

From what Alex has said, it looks like the feature uses USN Journaling (a low level file system feature), and that is why it's not working here.

 

A work around is to "move" the user folder(s) to a network share. This should prevent it from causing the issue (you could move it to "\\localhost\c$\users\{username}\{foldername}", and that should work).

Link to comment
Share on other sites

  • 0

Thanks Christopher. I've tried getting my head around the workaround but I don't think I understand. As far as I understand things, File History works for folders included in a library. What I've done is to include folder x (which is within the pool) in the Documents library to enable File History for folder x (this doesn't work as we've already concluded). Which folder should I "move" to a network share? I can move the user folder called "Documents" but how will that help me?

Link to comment
Share on other sites

  • 0

The workaround is to put the files on the share. This removes/disables the USN Journaling requirement (which is what is causing the error). 

 

the "\\localhost\c$\users" folder, is the local systems' C:\Users folder, actually (x$ are the drive letters in the system, where "x" is the actual letter). 

Link to comment
Share on other sites

  • 0

I'm sorry but I'm not getting it... I have "F:\SomeFolder" where "F:" is my DrivePool and "SomeFolder" the folder I want to enable File History for. I have of course "c:\Users" but what have that folder to do with anything? Maybe I'm slow ;-) but could you try to walk me though exactly what I need to do?

 

"C:\Users\" - Local system users folder. Not sure how this comes into play.

"F:\SomeFolder" - DrivePool folder that I want to enable File History for. To do so I've included it in the default Windows "Documents" library but that doesn't work as we already concluded.

"G:\" - Shouldn't matter but this is the disk that I've pointed File History to. Where it saves the backup.

 

Thanks,

Mats

Link to comment
Share on other sites

  • 0

Ok, tried it but ran into problems with indexing... :-( "F:\SomeFolder\" is indexed but when I try to add it to the library using "\\localhost\f$\SomeFolder" I'm getting an error that the folder isn't indexed. Tried several hacks to get it indexed but without luck. I guess it's a no go then. To bad because I could really see it useful together with DrivePool. Any plans on adding support for it? If it's at all possible?

 

Thanks for all your help!

Link to comment
Share on other sites

  • 0

For the shares, does it allow you to add it? If so, then you can ignore the "folder isn't indexed" error.

 

And as for the issue that's preventing it from working, the "USN Journaling" feature... we would like to add it, definitely. But the question is how complex will it be to do so.  So, I can't really give you an ETA on that. Sorry.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...