Outlook.pst on network drive not locked? No files locked?

I have recently set up a freeNAS server (brilliant!) and put all my data on it, including outlook.pst.

In the past when outlook.pst was on my XP machine, I had to use a freebie program called "unlocker" to unlock outlook.pst before backing it up.

However, I have noticed that now it's on a network drive, it never seems to be locked, at least as reported by Unlocker.

In fact, any file on the freeNAS server opened by a Windows app never seems to be locked, according to Unlocker.

I have read somewhere that MS does not support outlook.pst on a network drive - is this the case? I have not had any problems (yet!).

Are there other locking-related things I need to be concerned about when using freeNAS? Why is no file ever found to be locked, even if it's in use by a Windows app?


johniathomeAsked:
Who is Participating?
 
gheistConnect With a Mentor Commented:
It is samba which is serving files to you, it is running on BSD, but that does not change much. By default it locks full files. But may be customized to lock positions
0
 
Jeff BrownGlobal Helpdesk SupervisorCommented:
in order to lock the files it needs control over the file system.  NAS's typically use some form of linux which has different locking mechanisms.  The pst should be fine on the network as long as the network link does not go down often.  YOU MAKE SURE nothing else is editing the pst while outlook has it open.  The drives file structure stays stable.

--wild
0
 
gheistCommented:
Unlocker does not support networked files at all.
Try to rename file from other session to see if it is locked.
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
johniathomeAuthor Commented:
gheist:

I dare not try your suggestion with outlook.pst - I have seen too many cases of corruption.

However, I did the following test using a spreadsheet on my freeNAS server:

Open the spreadsheet using Excel on one PC.
Try to open it with Excel on another PC, and it says its locked.

Open the spreadsheet using OpenOffice on one PC.
Try to open it with Excel on another PC, and it allows full edit access, with no mention of locking.

If this test is repeated using notepad and a txt file, there are no locking issues at all.

So, file locking appears to be handled entirely by the app, and not by the OS!
This is not very satisfactory, to put it mildly. Surely it is the OS's responsibility to control multiple consurrent accesses to a file, and make sure it's kept clean and safe?
0
 
gheistCommented:
Dsiable offline files in Windows and try again.
0
 
johniathomeAuthor Commented:
gheist:
Offline files have been disabled for some time - I have enabled Fast User Switching, which prohibits offline files, for some reason.

Isn't the problem more to do with freeNAS? I believe it is a stripped down version of BSD, about which I know nothing. freeNAS must be aware of when a file is open, and when another user is trying to access it?
0
 
johniathomeAuthor Commented:
gheist:

Thanks for your comments.

I have done some poking around in Samba, and find there is  something called "opportunistic locking" (oplocks). This is turned ON in my freeNAS version, in smb.conf, as it is by default in WIndows.

The problem with oplocks is that it allows the Windows client to cache it's writes locally(!) for a long time, to improve performance. But this leaves the door open to a Windows crash, with a loss of all the pending writes. This looks like a horror show to me, in relation to outlook.pst files, which are notoriously prone to corruption anyway. I don't mind this for "normal" Word and Excel files, but outlook.pst is more like a database.

By mucking around with Samba config and Windows reg entries, it is possible to force the Windows app to wait until Samba has committed each write before proceeding. This is total safety, but also totally rubbish performance.

I now know enough about Samba config files and the Windows registry to muck around with oplocks and other things, but I don't know nearly enough to stay out of trouble!

I think the solution for outlook.pst is to keep it on my local Windows PC for the time being to reduce the chances of corruption, and back it up to the NAS server when it's quiet.
0
 
johniathomeAuthor Commented:
gheist:

Thanks for the link. It comfirms my other researches.
0
 
gheistCommented:
Watch in what year it is issued ;) Actually problem is mostly forgotten since people do not use shared files databases, but database servers.
0
 
johniathomeAuthor Commented:
Thanks gheist, you pointed me in the right direction on this one.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.