|
Personal tools |
|
|
/Documentation/iSCSI
From AnnvixiSCSI
What is it?iSCSI is a protocol designed to allow block devices to be treated as local devices through a TCP/IP connection. This means that systems, such as databases or mail servers, that need local storage can take advantage of pooled storage. Essentially there will be a server that makes storage available and clients that use the storage. The server side provides iSCSI targets, and the client connects to those targets using an iSCSI initiator, but this is all usually software, so you don't have to worry about buying anything. iSCSI is known to work well with Linux and Windows. It can work with BSD and AIX and others, but Your Mileage May Vary. WhyWho hasn't wanted to add a drive to a machine but either didn't have the hardware to expand or just didn't want to open up the box? iSCSI is a way to add "drives" over a TCP/IP network. NAS vs iSCSINAS, or Network Attached Storage typically is available as either NFS or CIFS (or SMB for older systems.) iSCSI differs from traditional network storage in the way the information is shared. iSCSI is block level storage, NAS is file level storage. iSCSI works well for things like databases and pst files. With iSCSI the operating system can just work with the portion of a file that it is changing rather than copying the entire file into temporary storage as is typical of NAS. For this reason it is possible to have entire operating systems installed in iSCSI. Potential DrawbacksThere is one very serious consideration that cannot be ignored when using iSCSI. Just as two machines cannot easily share a single hard drive, neither can two systems share a single iSCSI share. It is technically possible but extremely dangerous since any changes made by one might apply to both, without the second being aware of the changes. Using a single iSCSI target for two systems is likely to result in data corruption. If using read only access, it may be possible, but the documentation on this is sparse. Where possible it is recommended to provide a separate iSCSI target for each Operating System. (One iSCSI system can provide many iSCSI targets so this is rarely a significant concern.) Virtual Machines with iSCSIiSCSI is ideal with Virtual Machines such as those with Xen or VMWare. With a virtual machine stored in an iSCSI target the hosting operating system can make the target available to the virtual machine which allows for more efficient use of storage. An especially attractive option is then to run the virtual machine from a different host when the original is unavailable. iSCSI with LVMWhen using LVM to provide the partitions that become iSCSI targets, new options become available. It is possible to create multiple snapshots of a base system and then the common portions of the systems are shared, but every difference created by each individual system is still all that individual system sees. As a backup, snapshots also make it possible to completely undo recent changes. This means that you could potentially create a good server configuration and then take a snapshot and not have to worry about doing something risky (like running a global distribution upgrade) and be able to restore the original system exactly as it was. LVM itself provides this functionality but when combined with iSCSI it adds the convenience of centralized storage. Snapshots also make it possible to clone an active system. MultipathOne additional potential benefit is the ability to multipath iSCSI targets. If one network becomes unavailable, a second can be used to access the same iSCSI target without interruption of service. This is not supported by all implementations, but is supported by current Windows initators. iSCSI is cheapThe standard high performance SANs have used Fiber Channel for drive access. Fiber Channel access is indeed very fast, about the equivilent of 2Gb ethernet, but it is also very expensive. iSCSI uses usually free software and existing ethernet networking to provide the same type of storage. It is often completely free of cost to implement. Even implementing iSCSI with specifically purchased network hardware is usually less expensive than implementing fiber channel. iSCSI can be fastIt is possible to access iSCSI shares with minimal access speeds and preferable over NAS because the OS is able to copy only the changed and read blocks instead of files over the network. It is also possible to use very high speed networking to achieve even higher performance. With the proliferation of Gigabit ethernet and multi-pathing and bonding it is possible to approach and possibly exceed speeds offered by Fiber Channel. Multiple targets can be combined with different networks to then be combined in software RAID, making it possible to utilize two or more Gigabit ethernet connections at the same time. With 10 Gigabit ethernet now available, it is possible to exceed Fiber Channel data transmission speeds, although keeping the drive capability ahead of the capacity of the network to transfer data becomes a challenge at those rates. Creating an iSCSI Enterprise TargetAuthor's note: this is a one time install and configuration for me. Please let me know how your tests go and any changes that should be made to this document in the talk page.
PreparationMy testing was done an installation of 2.0 while it was still in beta. Your installation should always be current so start off by making sure it is:
Pre-Configuration
Installation
Post-Installation Configuration
UseConnecting
Preparing the drive for use
|
![]() |
|
|
| |||