The primary reason I am writing these boring posts is the occasion of having a friend of mine, a professional photographer, recover from a catastrophic data failure. Whenever I would bring up terms like "network file server", she would put on that expression of "I am just a girl and I dont know what that means" that so many of us are so familiar with. The good news is that even my brilliant professional photographer friend can pick up these computer terms with very little effort.
This stuff is not hard to understand. What is hard to understand may be how things are implemented to work well, if indeed they do work well, but the basic concepts are straightforward.
The fact is that most professional users of computers, even those in their own home office or studio, will have a heterogeneous collection of files that look like they are all attached to the local computer even though they are not. Some OS's handle this better than others "out of the box" but they all accommodate it.
Most of the time you, the user, do not care if a file is local, or on your local network, or even further afield. But you very well might care if you are your own systems administrator or your studio architect and since most of us are our own administrator, you have to know this stuff.
So get over your computer anxiety and gender bias and get this done. Here is your Wikipedia (and one optional Dell white paper) reading list.
Now we can get on with the exciting yet boring design of our backup system.