![background image](http://html1.mh-extra.com/html/ibm/totalstorage-ds300/totalstorage-ds300_best-practices-manual_3462750041.webp)
Chapter 2. iSCSI overview
23
2.4.4 Backup
Backup of data on the IP Storage is the same as for any direct attach storage;
that is, via any method that supports SCSI-attached volumes. A backup
application running on an external server, including the one hosting the iSCSI
initiator code, will control the backup of data that is physically stored on the iSCSI
appliance.
An NAS appliance, because it “hides” disk volumes from its clients, and often
includes specialized backup facilities, may be easier to install and manage.
2.4.5 Management
iSCSI is managed like any direct-attach SCSI device. iSCSI-connected disk
volumes are visible to attached processors. Compared to Fibre Channel SANs,
iSCSI benefits from using IP networks for which there are established network
management tools and people skills. Such tools enable network administrators to
coordinate provision of bandwidth among users and applications, traffic
management, and overall network operations. Training in new networking skills is
minimized.
2.5 iSCSI planning considerations
Since the iSCSI appliance attaches to the existing Ethernet network,
implementation is very similar to an NAS device. In this way, NAS and iSCSI are
very similar. However, when you make the comparisons between iSCSI, Fibre
Channel and NAS, it really comes down to Block I/O versus File I/O. Both iSCSI
and Fibre Channel use Block I/O to transport data, whereas NAS uses File I/O.
The determining factor might ultimately be what kind of application is to be used.
Will the application work better in a Block I/O environment, or File I/O
environment? Is the application database or file sharing oriented? How much
does performance play in this application?
All File I/Os result at a lower layer in Block I/Os. This means that iSCSI can also
support File I/O applications. However, if “visibility” and “sharing” of files are
needed, File I/O applications are better supported by NAS than by iSCSI devices.
Actual device sharing can only happen at the Block I/O level. This requires a
“share-aware” file system. Windows NTFS does not support this.
Summary of Contents for TotalStorage DS300
Page 2: ......
Page 20: ...2 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 28: ...10 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 226: ...208 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 228: ...210 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 240: ...222 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 450: ...432 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 581: ...Copyright IBM Corp 2006 All rights reserved 563 Part 4 Appendixes Part 4...
Page 582: ...564 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 638: ...620 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 640: ...622 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 648: ...630 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 664: ...646 IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 677: ...1 0 spine 0 875 1 498 460 788 pages IBM TotalStorage DS300 and DS400 Best Practices Guide...
Page 678: ......
Page 679: ......