It's end-of-life, insofar as it's running Server 2003, out of warranty, and developed a persistent RAID error that has defied diagnosis and cure over about two days and four tech support calls of attempts.

Not exponentially, at least in terms of staff. I don't expect us to top 20 bodies at any time during the useful life of this hardware. But I do expect more and more courts to go the way of the federal system with PACER/ECF. In fact, one of our local jurisdictions is already e-Filing. And we are increasingly able to get, say, squad car video in digital formats. So I do expect our data volume to increase at a rapid clip. We're at ~100 GB now; I don't want anything less than 2 TB of storage room.

We've played with Amicus, which is server based, but not been thrilled. We do a lot of contingent work, so the hourly billing features aren't so important. We also do a lot of travel, so the ability to check the office calendar on a smart phone, or copy a client's file onto a USB stick, is indispensable.

Otherwise, we're too small for Sharepoint and one person handles our books with a local install of QuickBooks.

Call us cousins up here in tornado alley, and on the floodplain of a major river. I am very, very interested in using cloud-based services for offsite backup - the further from our next federal disaster declaration, the better.

That said, I'd rather get a dropbox or carbonite style service but work off of local copies for our hour-to-hour needs. We're on a DSL connection and I have not been delighted by any cloud-based word processor I've tried.

This!

We have fifteen years worth of investment in carefully styled MS Word documents. Format matters, not just for courts, but for clients who expect a certain level of professionalism and consistency. Telling a client, "Yeah it looks all funny because we decided to start using iGoogleBook's TweetDocs and haven't got it all figured out yet," does not inspire confidence. Also, our best typists are 80 wpm and/or using keyboard shortcuts as a matter of spinal reflex. Cloud document services just aren't there yet.

It'd be fair to say we're underusing ADS. We have it, and we use it for our basic login credentials, but we don't really have any need to segregate our internal users into groups.

We have a very binary approach to data access. Everyone in our small office needs to be able to see all of the client files. No one outside of our office needs to see a blinking thing. So by one-size-fits-all, I mean that our receptionist has access to the same file set that our senior partner does - she has to, if she's going to be able to tell a client when his next court date is.

At this point, I've flushed about two days of what would otherwise be billable hours in trying to nurse our old server back to health, and now I'm here on Sunday trying to figure out where to go next. You're right that the process would have been worse if I hadn't been able to look up and quickly decipher a few key error messages online, but I regard a certain amount of time as the price of doing business.

With Windows, I'd call myself a power user, but I'm no full fledged network admin. I'm not intimidated by a CLI and a bit of a learning curve, but I don't have commands memorized, either. With *nix, I'm only slightly more skilled than a monkey banging on the keyboard at random.

We do have an Active Directory domain. We aren't using it for anything but one-size-fits-all login credentials.

Stipulated. You get what you pay for

:)

I'll readily concede that I cannot root-proof a NAS device on my own, or anything else for that matter. I'm pretty limited in my ability to troubleshoot a mis-configured firewall, too. But we have to have something, and I'm mainly wondering if a NAS device is inherently more vulnerable or more buggy than a full-on file server.

Clients emphatically do not have access to our file server. Quite a few of them are facing very serious criminal charges, and a certain number might even be guilty. Frequently a client will want to send us files; we accept those by e-mail or physical media. Occasionally a client will ask for a copy of his file; we're pleased to burn that to CD-ROM.

At present, we do not have an FTP server. We'd had a fairly hefty network (for a business of our size, at least) set up back in 2008, but I'm not married to anything so long as we can get access to our files at off hours and on the road.

Agreed that RAID is a must, as is independent backup. At present, we have a tape drive. Sometimes the secretary remembers to run it, sometimes she doesn't. But even when she does, she keeps the tapes on site and close by "so we don't lose them". One small fire, one small flood, one pissant vandal, and *shudder*. I know the cloud backup providers will surrender to subpoena power without a fight. But I also know how to get a protective order on attorney-client privileged files after the subpoena is issued. As I see it, there's no way to keep any kind of record, ever, without risking an outsider discovering it. But if cloud-based backups (especially automated, encrypted cloud-based backups) let us mitigate our disaster risk and cut out the oops-forgot-to-change-the-tape factor, they're the lesser of two evils.

Right now, we're a two attorney firm (me and my boss, who's very game but a little green when it comes to tech), looking to hire a third. We also have a pool of about five support staffers. We all have to be able to access one another's files - I'll write a memo to file, which Boss will review, the he'll dictate a letter for Paralegal A, who asks Paralegal B to help her find the recipient addresses and print off the enclosures, and then back to Paralegal A who scans and files the outgoing letter to our correspondence. The paralegals are high turnover, and prone to downloading scamware. I do what I can viz education and virus removal, but there are limits. We also travel cross-country with a specialty arbitration practice we have, and need to be able to access client files from the road.

As to what our server doesn't do, we POP into our e-mail, use Google Calendar for our scheduling, and have our simple little WordPress website hosted offsite. No real reason to change this at this point.

I'm not OK with former co-workers making backups and carrying them off; no attorney is. But I'm even less OK with trying to parcel out file access on a case-by-case and employee-by-employee basis

California already does defy federal law by allowing medical marijuana by prescription. Technically, all the producers and consumers could be busted on federal charges, state legal or no. But as a practical matter, the Feds rarely if ever prosecute "legal" users.

* IAN Your Lawyer. Do not take legal advice from strangers on the Internet.

Condolences, and best wishes for your project.

I lost a parent as a young teenager. My siblings were tweens. We have lots of peek-a-boo and Saturday morning couch fort memories, and don't get me wrong, we cherish them. But what I really miss now, as a grown woman, was getting to know my father as an adult. He was a great father for us as children, but we were too young and/or too sheltered for really open conversations on those thorny adult issues that most parents dread. The man I've gotten to know second-hand through his peers was a thoughtful, interesting, complicated guy. I wish I could have known him as a peer, too.

Whatever medium you and your wife use (and you should participate too, no parent is an island), don't neglect the shades of gray, and the things you'd only say to someone you trust after a couple of beers.