One of the fun things about the start of a new month is seeing what surprises lurk in the web server log analysis program. This morning, for example, was the first and only time that visitors to this server from Hungary outnumbered visitors from any other country.
What’s really fun is that second place went to Switzerland. The .net and .com addresses combined were a distant third. Of course, this just counts visitors that hit between midnight and 6am local time, so by tomorrow the server will be back to its old Americentric self.
Well, I’ve already lost the non-geeks out there, so I might as well continue in the same technical vein…
It’s the start of a new fiscal year at the office, so I figured it was as good a time as any to institute some changes to the server backup system. We’re using Retrospect to back up not only our server, but all of our workstations on the office network. Our previous backups have been going to the same catalog set for the past six years, and it’s gotten to the point where the most time consuming part of backups is where it matches files to the existing catalog to see what has changed.
Creating a new backup set is easy. Sure, it’ll use a couple of tapes right off to back everything up, but that’s quite all right. Unfortunately, I’ve run into an odd snag. The total back up runs fine on every machine we have, except for the Powerbook that I use. About halfway through the backup, it just quits. It doesn’t even report an error in the log…
The only thing I can think to try is to back it up without a disc in the DVD drive, and that’s just a hunch based on some odd behavior that it had been exhibiting a while ago. Other than that, I’m stumped. If it works, I’ll post here, just in case someone else out there is having a similar problem.