Well, this iSCSI stuff has intrigued me for a long time now. and its starting to make more and more sense. I have started to see more advantages of using it, and better ways of implementing it on my network.
Take for example my PowerEdge server running as Exchange/Web/SQL box. this machine is on 24/7 and is pretty important to have live. but its limited in the amount of storage I can physically add to it. If I stick in a new GigE net card (it has one already) and leave it alone, I can remotely add extra storage by placing it in a larger server and let the PowerEdge take storage from that. If I want to migrate my SQL Server to a new box, just take the SQL server down on the PowerEdge, disconnect the iSCSI drive, reconnect it on the new box, and let SQL server do its magic. its now on a new machine, and that’s it.
Mind you, I do know there will be problems.
- even GigE network can be slow. it will max out at 125mb/s (if your lucky) and cached reads from hardware can be faster.
- More points of failure. now if the iSCSI drive does down, the network is screwed.
but there are more advantages.
- Single place for backups.
- Only one RAID array, on the storage box, is required.
Anyway, here are some links, which might be handy:
Byte and Switch has an article on How to build an iSCSI Disk Array.
Josh Maher has a post talking about Exchange 2007 on iSCSI storage. again handy.
EmBoot is a company with a couple of interesting products: winBoot/I and netBoot/I. These allow a machine to boot over iSCSI using just a standard network card.