Lucky me! Tonight I've assigned myself to try again to move our network user files from one server to another … one with a lot more disk space available. So, saying goodnight to everyone at 9:00 PM, I retreated to the Server Room to begin my night's work. Last time I tried it was some months ago. I thought it worked but the permissions were wrong and, basically, it was all "Read Only." That's fine for security but not so good for usability. So, as I write this, the first part of the transfer is taking place. Once the backup and restore to the new location is complete I'll change the login script to point users to the new file location. Ideally the only things users should notice is there is more space available for all of their crap and their crap is served and saved faster than it was. Ideally.
I did succeed in installing updated software to our email server while I was waiting for the big file copy operation. I dearly hope the vendor fixed a problem we've been seeing where Web messaging just quits –the ASP service crashes in the background– because that means most of our users lose their email service until the server machine is restarted. The operation was a success; only time will tell whether it helped the patient!
Update — 11:12 PM The Backup took 1 hour, 30 minutes, 40 seconds and verification took 3 minutes, 34 seconds. I've started the restoration process that unpacks the files to their new location that (this time) has access permissions that match their original home. It will take about 40 minutes for this process to complete. Then I get to test the thing by logging on using several different accounts and checking my file access. That will be at about Midnight. {Yawn!} Thank goodness I'm able to maintain Internet access during this vigil. Helpful in getting support information and in staying mentally active!
Update — 12:42 AM (Thursday) By Geroge I think I've got it! Restoring the files to their new home took 41 minutes, 9 seconds. The files didn't unpack the way I thought they would so I had to create a new shared directory, move the files and directories into it, and check permissions. Sure enough, they were set to "Read-Only." This time I removed the read-only attribute on everything except some restricted access files –Windows knew what they were– changed my login script and gave it a go with a low-level user account. Yea! I was able to access files I should be able to access, make changes, save those changes, and not get into files I've no business getting into! Yes, it looks good.
Of course the real test is when all those real users get logged in. What will they experience? Opening of business in a few hours will tell. Hopefully I'll come in well rested and not find a bunch of panicked librarians gnashing their teeth and pulling their hair out! For now, however, I'm goin' home.
PhotonStopper 
Saving crap quickly whilst preserving library workers hair is a true accomplishment! Hurrah and congratulations on you! I can't imagine being at work that late into the night (next morning.) Good not to have your job! ~S
It looks like everything went well. So far no gnashing or yanking of hair and we're well into the day! As to the definition of data as "crap" … It's crap when it's someone else's files that are of little importance to you. Your files, of course, are not crap. As to staying at work late… I once worked, worked for 24 hours straight: that's no naps, only routine breaks, 24 hours "on the clock." I was awake longer than that. That was an experience!