IDE Failures and backups

For 80% of people, running backups is a non-event. We simply don't consider doing them, not because we are lazy but it just never crosses our mind. Fortunately I had a happy event last week - I ran a full backup of my beloved D610 Dell Latitude's hard disk and not 2 days later the bastard failed on me. It was then I found out how much harder it is to get IDE hard disks for laptops. The 40GB HDD in it was adequate for my purposes and the smallest I could find was 120GB. Now I know how easy it is to fill 120GB of disk with music or movies or whatnot, but in context, I store very little of such things on this notebook. It's for work, and for online stuff such as Google's services and apps. At any rate, I use the wonderful TrueCrypt (www.truecrypt.org) to create encrypted partitions and then use the equally handy rsync (or in a pinch xcopy) to incrementally back that data up across the network to my servers. 

I thought perhaps I'd share how I do this, using xcopy in a batch file and with the potential of using either an external USB device or whatnot. You can get *very* fancy, but in all honesty, any backup is better than no backup so here is the script (abridged for privacy purposes) that I use:

xcopy "z:\My Documents\*" "m:\My documents\*" /C/D/E/H/Y

You can see that I'm just backing up My Documents from one location to another. The first one, on the Z:\ drive is the source and M:\ is the backup. Easy! 

The switches do the following:

/C: Continues copying even if an error occurs

/D: Copies files changed on or after the specified date. If no date is given, copies only those files whose source time is newer than the destination time.

/E: Copies directories and subdirectories, including empty ones.

/H: Copies hidden and system files also.

/Y: Suppresses prompting to confirm you want to overwrite an existing destination file.

Pretty straightforward really. I run it manually at the moment, but plan to put a schedule in place once I get some error correction built into it. For example, if the M:\ drive is not available I don't want it to panic and grind to a halt, much better for it to gracefully exit.

Feel free to adapt it for your purposes if any. As I noted, it's better to have *some* sort of backups than none at all. This particular one of mine doesn't catch emails or the like, fortunately for me I use Gmail so it's not really an issue - all my emails reside on the Google servers (bless them!). For everything else, there's xcopy!

Review: Windows Server 2008 Small Business Server

Recently I've had the requirement to install and configure Windows Server 2008 SBS. Previously I've deployed 2003 SBS in varying settings and found it to be quite a nice little product. In more recent times though, I've gone the more segmented path of Windows Server 2003 plus Exchange 2003 separately and found that to be quite effective. For a small operation, however, SBS provides many features that are very helpful to the operator who isn't necessarily skilled in IT, nor has a great deal of time to set things up and play with them. Being a Sys Admin with the inclination and the time to play with it, here are some of my thoughts regarding SBS2008.

The management system for accounts and the like is very nicely set up for the none technical user. An application with common tasks is easily available and allows for configuration of most casual system changes to be made. I refer primarily to user and group (both distribution and security) creation, file and folder shares and backup configuration/testing. SBS2008, like it's predecessor has some nice daily reports that can be emailed to the Administrator or to a designated person and contain excellent information to keep an eye on the system. For example, this includes disk usage, backup status and the like. Very nice.

SBS2008 likes to take control of the network - it offers to be the gateway, DNS, DHCP, mail and file server all in one. I had problems with this on my network - I already *have* a gateway, DNS, and DHCP servers and it didn't play nicely together at all. In fact, the installation failed and I had to restart it again from scratch. This time I was a bit smarter and had the server plugged into a dummy switch. Once the initial install was passed, I added a virtual interface to my gateway and set the SBS server to point at it. This time it was happy, but by gum it wasn't the first time around. It automatically assigned itself the .2 IP address on the network (i.e. 192.168.0.2) and off it went from there. It did talk successfully to the gateway and once I reconfigured squid and my firewall, network traffic flowed as one would expect it to.

Something I learned from SBS 2008 is that you cannot set up mail addresses etc from within Active Directory, as you can in Server 2003 (not SBS) with Exchange. Also, security and distribution groups all had to be set up from the SBS system application. Not realising this, I created groups and used the Exchange Systems Manager to set up the email accounts and groups. These did not appear in the SBS system application. Oops! I'll have to revisit it and see if it's found them or not. Something else I learned - the HP ML350 I installed SBS2008 on is a very nice machine, but the HP setup disks - which cater for nearly every *other* version of Server 2008 - do not cater for SBS 2008. Damn! All those drivers and tools had to be installed after the fact - SBS2008 just would not work with the HP boot CD. Disappointing, but the ML350 was released before SBS2008, so you can't have everything I guess. That being said, the ML350 is quite a nice bit of kit indeed and highly configurable and affordable too. This one had a simple RAID1 mirror and everything ran flawlessly - as you would definitely hope it to in this particular setting.

Overall, I was impressed with SBS2008 and if needed I would happily deploy it elsewhere. I imagine that as one becomes more familiar with it, the ease of installation and configuration would certainly increase - I felt a bit confused at times and had to rely on trusty Google to get me through. At the very least, the problems I encountered were well documented by others. I must say though, the initial problem I had with the installation of the server failing was one that had been noted on the Microsoft webpages but no solution had been offered. If your SBS 2008 install fails - make sure it is the only thing on the network when you do the install - no other servers should be present if you want it to go smoothly. By all means migrate your AD stuff later, or even better (given that it is for Small Businesses) create a fresh new directory and build it in a pristine state for roll out. Also to be noted - it requires a minimum of 60GB of hard disk space for the C drive and a minimum of 4GB of RAM (!). Lucky RAM is cheap :-)

Virtualisation in the server space

Recently I've had the chance to view VMWare (www.vmware.com) and HP's (www.hp.com.au) entries in the virtualisation market - through VMWare's ESXi server and HP's Blade servers and SAN systems. Prior to this presentation I'd only looked into virtualisation a little bit, concerns for server redundancy and the like preventing me from spending a lot of time looking into it, and also, the size and scope of the organisation I work for is insufficient for such things - or so I had thought.

I have about 10 servers under my direct control and of these, 6 could be virtualised. Thinking about it going forward, in 3 to 5 years when these servers are due for replacement, buying 2 servers and a small SAN will cost less than the 6 new servers and provide the same services. At the end of the day, I think that's what it is all about - same services (or better), with uptime being up in the 5 nines range and cost-effective hardware/software. I've been a fan of VMWare's virtualisation stuff for several years, solely through the VMWare desktop range. Running multiple operating systems and applications on a single development machine was lots of fun. Back in the day (5 odd years ago) RAM was pricey and so was disk space so the VM's were pretty little.

Now you can run whole server instances in a file and then slip that file between servers depending on load requirements and whatever other fancy things you want to do - such as bringing one physical server down for updates and maintaining all your VM's on another server. Absolutely amazing stuff - especially when you combine it with blade technology and have dozens of servers sharing one big SAN all in the same rackspace. Truly incredible. Pretty complicated too I think as well, remembering where everything is going.

The new Blade servers from HP look very impressive too - they've done a lot of work on cooling and on cabling and everything is redundant with backup from at least one module exactly the same. Of course, when I saw those big fancy Blade servers I thought to myself - why virtualise? You could have a netboot install of a server ready to rock at a moment's notice and be back up and running in a very short time, especially if you combine the server with Microsoft's ASR technology and tape backup. There is so much chance for overkill it's every enterprise geek's wet dream. There were quite a few geeks at the presentation that looked like they were in their happy place that's for sure.

The most important thing I took away from it all was that virtualisation in the server space has come a long way since I last looked into it and the offerings from both VMWare and HP are quite spectacular. Given my quite low funds though - I'm now looking into Linux's XEN virtualisation. If you're more interested in this (any virtualisation for that matter) there is a lot of stuff on the interwebs. Mind you don't clog up your tubes! :-)

Waiting for Windows 7

OK, so we're starting to see some peeks at Windows 7. Check this out at ars technica: http://arstechnica.com/news.ars/post/20081028-first-look-at-windows-7.html The first screen shots of Windows 7. I'm not particularly interested in it at the moment, I'm more interested in the whole "What do I do with my 8 year old Windows XP now?"

There are several options and as a Sys Admin I get more than a few questions about what to do as Windows XP ages gracefully into oblivion. Obviously the wonderful Windows Vista is an option, as is the various distributions provided by the gifted GNU/Linux community. With Windows 7 slated for a late 2009 (probably 2010) release should users be holding out for it as their hardware ages and their PC's become due for renewal? And for businesses that have laboriously got themselves into a nice 3 year PC replacement cycle, what do they go for?

Honestly at this point I'd point them at Novell's Linux Enterprise Desktop 10. There is no way I'd suggest Windows Vista at this point. It is such a massive resource hog, plays poorly with legacy applications and just seems to be a slapped together and rushed out the door operating system. It should be noted I run Vista on several machines, and have a couple of machines out there with regular users running Vista and honestly, they give me no positive feedback on it. On the other hand, I've put Ubuntu and OpenSuSE on people's desktops and they have really liked them - especially on older machines where the processor is only a P4 with a 1GB of RAM.

So the question really is - wait for Windows 7 and hope for the best OR deploy Vista to the desktop? It's not a nice question at all. I'll admit to feeling burnt by Vista - sure it has some nice features but by crikey it can be frustrating to get it going in the right direction at times. I've rarely had issues with the various Linux dizzies I've installed and Windows XP, for all it's faults, has been a good OS from both a systems view and a users view. Obviously security is paramount with XP, but at least it works - and it works on a lower hardware spec than Vista. With the economy going spastic and the Australian dollar declining versus the US Dollar (and how does that happen when the greenback is in such turmoil with obvious poor management and leadership???) PCs are getting more expensive again. Boo hiss.

If Windows 7 requires even more grunt than Vista I see it being out of reach for a lot of users for at least a year past it's release date. As to Vista I'm going to try and pretend it never happened and keep it out of the workplaces I'm involved in. What are you going to do?

Review: Treo 750

Recently my JasJam decided (after it's 5th graceless crash to the ground) that it would only work under certain conditions. These include the 4th blue moon of the year, only on days starting with X and the like. You get the picture. Adios JasJam.

So being phoneless is no fun (although very quiet :-) ) Being a geek and needing email access and the like, but refusing to have a crackberry, I opted to have a bit of a look at the Treo 750. Compact, nice weight, nice screen and the keys feel good. Okey dokey. So being a high powered manager I demand and receive one immediately (ahh sweet sweet power). I've been using it for a couple of months now and here are my thoughts:

Windows Mobile 6 - much nicer than 5. Speedy and hangs up in a quick manner. I like that. Interface is nice, the green is very pretty and it has some useful functions. These things I like. Very easy to set up mail and stuff and I like the way it handles text messages using threading. Aye, that's pretty. I *still* don't like that you can't have an MP3 for the alarm tone. Come on! It's 2008 - catch up Microsoft!

Stylus - cunningly placed, nice weight, unlikely to get lost in the pocket and works well. I like it.

Keypad - I like the keypad too, although the buttons are small and I sometimes hit the wrong ones when I'm not paying enough attention they have a lovely tactile response to them.

Generally it's a good device. It hasn't crashed yet on me and it holds a good charge given I use it extensively throughout the workday. I can get probably 3 days of battery life out of it which is great. It's weight, shape and size are pleasing also. In general I feel this device to be a better one than the JasJam was. It has mini-SD memory (bit of a change from micro like everything else). I promptly put a 2GB card in there and it works great.

It lacks a front camera for video calls (but I never make video calls so who cares). Also, the camera that's built in has poor resolution and the like but again, that isn't why I got it. It does a reasonable job and that's really all I care about. Sound and voice quality are fine, dialling easy.

So I'm quite happy with it. It's not quite as good as my e61 though on calls and the like, but is smaller and easier to deal with than the e61. So in conclusion - not a bad bit of kit at all.

Windows Mobile 6 Review

I've just updated my i-Mate JasJam to Windows Mobile 6. Although I was initially skeptical about this, I had to do it, basically. My JasJam checks my email continuously throughout the day, and when I'm on a call, the data check drops the sound for the call which is a major inconvenience. So I looked into some updates - via the Telstra JasJam site and found that Windows Mobile 6 was a free upgrade.

Being an early adopter of technology I decided to give it a whirl (even though it's been out for a while). During the update things went slowly. At one point I thought I'd fried my JasJam, a moment that made me decidedly uneasy. It came back to life however, and things progressed from there. I've been using it for about 14 days now and here are my impressions:

• wireless connectivity (802.11) is much better and setting up connections is easy and relatively fool proof.
• bluetooth seems more reliable
• no more sound drop outs during calls and while phone is checking email (yay!)
• I like the look of the new interface - pretty!
• Speed of dialling is faster. Previously the onscreen keys took a moment to register a press - now it's very quick.
• hanging up happens immediately. Previously, I had to press the "End" or red phone key several times until the phone would drop the call. Annoying if you say things after a call you don't want the caller to hear (oops!)
• Email interaction with the server is smoother and runs without any errors.

Overall, I'm quite happy with the improved interface. I note that it has it's own "Windows Update" built in. It also has updated versions of the various mobile office applications - Outlook, Word, Excel for example.

Most importantly it still has the block breaker game - my usual boredom killer.

OK, so here are my gripes:

• the alarm tone still has to be a wav file - large, unwieldy files that rarely seem to work
• the phone has hung a couple of times
• battery life seems to have decreased

All in all, not a bad update and fairly straightforward to implement. Works well with both Vista and XP. I should also note that the use of the phone as a modem is much improved. Well worth the time and effort to do.

Review: Nokia e61i

Recently my phone contract expired and I decided to go for something a little different this time. I liked the look of the Palm Treo and also the Nokia e61i. I checked them out on eBay and didn't really find one I liked the price of, so I decided to get one through my phone provider.

I've been pleasantly suprised. My current work phone (an iMate JasJam) is a great piece of kit. I venture to say that the e61i is at least as good - if not better. The 802.11 wireless is far better - it works with WPA2 and connects without problems. I have noticed that with a Netgear router it does have occasional problems - but then again, most PCs around the place have problems with that particular router.

As a phone it is more than adequate - I like the keypad very much. It has a nice tactile feel to it and I can type reasonably quickly on it. The location of various non-alpha keys confuses me sometimes, but that's to be expected when jumping between different keypads. It has a nice ear piece and I haven't had any problems with calls at all. It's a better phone than the JasJam.

As a PDA I find that it works very well too. But, I prefer the Windows Mobile approach to the Nokia Symbian approach (personal preference naturally). This is not to say it lacks functionality - it's just the aesthetics that I prefer. I've been happy with it's performance for note taking, task making, calendering etc so no complaints.

Battery life is good - I get about a week out of a charge - and this is with it checking my email hourly via wireless and various calls.

I was also pleasantly suprised by the music player bit of the phone. I find that creating playlists and the like is very easy and the sound quality out of the phone's speaker is quite decent.

OK, those were all good things. Here are a few tips on what *not* to do with this phone. Don't set it up with IMAP and gmail. I was completely locked out of my messages - SMS, MMS and emails. The fix? Reload the software. Ouch. Bye bye to all my phone numbers etc. I cried a bit but I got over it. That's probably my only complaint so far. It is a very wide phone too - which makes it hard to find a good case and occasionally makes me cranky when I'm lugging it about. Apart from this I have no further complaints at this time.

I haven't used the camera much and to be honest, don't expect anything special from *any* phone camera.

All in all, I'm very happy with it. It's a lovely compliment to my JasJam and fulfils my geeky requirements :-)