Redbooks Paper
Alex Osuna
Chrisanthy Carlane
Resizing the Root Volume on IBM
System Storage N series
Overview
In this IBM® Redpaper we describe the default volume configurations for the IBM
System Storage™ N3700 and the attributes associated with them. We also
discuss alternatives for those customers with limited resources or smaller
businesses and that need to maximize storage capacity.
The following topics are covered:
򐂰 Default disk configurations of IBM Storage System N Series products
򐂰 Options to modifying the root volume
򐂰 Risks and considerations when changing the configuration of the root volume
Introduction
The N series storage systems root volume arrived preconfigured by default with
a RAID-DP configuration of three disks. The default root volume of the storage
system has the effective capacity of one disk while utilizing three disks for its
parity and double parity. In an environment where the number of disks is limited
or not readily available, maximizing volume capacity is very important. However,
© Copyright IBM Corp. 2006. All rights reserved.
ibm.com/redbooks
1
there are some considerations and risks that you must review when altering from
the default configuration.
N Series System Storage default configuration
By default, N series storage system products come with one root volume
configured with three disks in a RAID-DP array preconfigured. The usable space
is approximately equal to the capacity of one disks minus the root volume or
/vol/vol0 capacity. In other words, you will have the physical capacity of three
disks with usable capacity of less than one disk, though it offers the best
redundancy in return. See Example 1 on page 3 for disk allocations on the initial
root volume and Figure 1 on page 3 for a graphical illustration of the initial
aggregate.
This may not be the best configuration for your environment due one or several
of the following reasons:
򐂰 You have only one expansion unit or one N3700 storage system.
򐂰 You ordered a expansion unit or N3700 with less than 14 disks.
򐂰 Your data growth rate is faster than you hardware acquisition rate.
2
Resizing the Root Volume on IBM System Storage N series
Red2>vol status vol0 -r
Aggregate aggr0 (online, raid_dp) (block checksums)
Plex /aggr0/plex0 (online, normal, active)
RAID group /aggr0/plex0/rg0 (normal)
RAID Disk
--------dparity
parity
data
Device
-----0b.16
0b.35
0b.18
HA SHELF BAY
-----------0b
1
0
0b
2
3
0b
1
2
CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
---- ---- ---- ----- -------------- -------------FC:B FCAL 10000 68000/139264000 69536/142410400
FC:B FCAL 10000 68000/139264000 69536/142410400
FC:B FCAL 10000 68000/139264000 69536/142410400
Example 1 Root volume
Figure 1 Initial aggregate
Planning
Data ONTAP allows you to make changes on the root volume concurrently
without interruption, which means that it is not necessary for you to restore the
data after modifying the root volume. However, this procedure always creates
additional overhead and should not be done during peak production times. In
addition, IBM best practices recommend that you do a full storage system
backup before modifying anything on the root volume.
Changing the N series root volume size requires careful planning and should be
done by trained personnel.
Resizing the Root Volume on IBM System Storage N series
3
Optimizing the root volume
This paper discusses the following methods of optimizing the root volume:
򐂰 Utilizing Raid4
򐂰 Resizing FlexVol
򐂰 Adding more disks to the initial aggregate to maximize capacity and
performance
Utilizing RAID4
As previously discussed in “N Series System Storage default configuration” on
page 2, N series storage system comes with RAID-DP configuration, which will
utilize one disk for data, one disk for parity, and one disk for dual parity per node.
This means that you will have two spare disks only for one data disk. If you only
have one data disk, one parity should be enough. Then it will work just like
RAID1 or mirroring, which provides very good redundancy.
RAID 4 with one data disk and one parity disk is sufficient for disk redundancy,
as one would not likely to have two disks fail at the same time.
Example 2 on page 5 shows you how to change root volume RAID-DP to RAID4.
You will see that the default root volume is a flexible volume (FlexVol), not a
traditional volume, because it resides in aggr0, which is the default aggregate.
aggr0 contains three disks: 0b.16 (dparity), 0b.18 (data), and 0b.35 (parity).
In order to free up one disk, you have to modify aggr0 raidtype to raid4. Use the
aggr options [aggrname] raidtype raid4 command to modify RAID-DP to
RAID4 in aggr0.
4
Resizing the Root Volume on IBM System Storage N series
Red2> aggr status aggr0 -r
Aggregate aggr0 (online, raid_dp) (block checksums)
Plex /aggr0/plex0 (online, normal, active)
RAID group /aggr0/plex0/rg0 (normal)
RAID Disk
--------dparity
parity
data
Device
-----0b.16
0b.35
0b.18
HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
------------- ---- ---- ---- ----- -------------- -------------0b 1
0
FC:B
- FCAL 10000 68000/139264000 68552/140395088
0b 2
3
FC:B
- FCAL 10000 68000/139264000 68552/140395088
0b 1
2
FC:B
- FCAL 10000 68000/139264000 68552/140395088
Red2> aggr options aggr0 raidtype raid4
Fri Apr 14 17:53:26 GMT [Red2: raid.config.raidsize.change:notice]: Aggregate
aggr0: raidsize is adjusted from 16 to 8 after changing raidtype
Aggregate aggr0: raidsize is adjusted from 16 to 8 after changing raidtype.
Red2> aggr status aggr0 -r
Aggregate aggr0 (online, raid4) (block checksums)
Plex /aggr0/plex0 (online, normal, active)
RAID group /aggr0/plex0/rg0 (normal)
RAID Disk Device
--------- -----parity
0b.35
data
0b.18
HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
------------- ---- ---- ---- ----- -------------- -------------0b 2
3
FC:B
- FCAL 10000 68000/139264000 68552/140395088
0b 1
2
FC:B
- FCAL 10000 68000/139264000 68552/140395088
Example 2 Changing Root volume aggregate from RAID-DP to RAID4
In Example 2 you see that after running the aggr options aggr0 raidtype raid4
command, the members of aggr0 are now 0b.18 (data) and 0b.35 (parity), while
disk 0b.16 becomes a spare disk. See Figure 2 on page 6 for a graphical
illustration.
Resizing the Root Volume on IBM System Storage N series
5
Figure 2 Disk 0b.16 is now a spare disk
6
Resizing the Root Volume on IBM System Storage N series
Resizing root FlexVol
The default root volume for the N series storage system is a FlexVol (or flexible
volume). This means that you are able to resize the root volume to add capacity
to other volumes within aggr0. You can use FilerView or command-line interface
(CLI) to resize the volume. Follow the steps below to resize the FlexVol root
volume using FilerView:
1. At the FilerView, go to Volumes → Manage, and choose vol0. FilerView will
show you volume vol0 properties. Click Resize Storage. See Figure 3 for a
graphical illustration.
Figure 3 Volume Properties
Resizing the Root Volume on IBM System Storage N series
7
2. After clicking Resize Storage, a Volume Wizard window will open. Click the
Next button. See Figure 4 for a graphical illustration.
Figure 4 Volume Wizard
3. Input the new size of the root volume and make sure you choose volume for
space guarantee. Click the Next button. See Figure 5 for a graphical
illustration.
Figure 5 Input FlexVol parameters
8
Resizing the Root Volume on IBM System Storage N series
4. The wizard will show your configuration changes. Check the new
configuration and click the Commit button. See Figure 6 for a graphical
configuration.
Figure 6 Commit changes
5. You will get a confirmation that the change is successful. See Figure 7 for a
graphical illustration.
Figure 7 Volume Wizard Confirmation window
Resizing the Root Volume on IBM System Storage N series
9
Now the root volume size has changed to 16 GB with a total capacity of 20 GB,
as specified previously (see Figure 8).
Figure 8 New root volume size
You may also resize the root volume using the CLI. The command to resize
FlexVol is very simple:
vol size volname [[+|-]size]
This command sets or displays the given flexible volume's size as specified,
using space from the volume's containing aggregate. It can make the flexible
volume either larger or smaller. The size argument has the same form and obeys
the same rules as when it is used in the vol create command to create a flexible
volume. Be careful if the sum of the sizes of all flexible volumes in an aggregate
exceeds the size of the aggregate.
10
Resizing the Root Volume on IBM System Storage N series
If [+|-]size is used, then the flexible volume's size is changed (increased or
decreased) by that amount. Otherwise, the volume size is set to size (rounded up
to the nearest 4 KB). See Example 3 for an example of changing root volume
size using CLI.
Red2> vol
vol size:
Red2> vol
vol size:
Red2> vol
vol size:
size vol0
Flexible volume 'vol0' has size 48g.
size vol0 20g
Flexible volume 'vol0' size set to 20g.
size vol0
Flexible volume 'vol0' has size 20g.
Example 3 Modify root volume size using CLI
In Example 3, you see that the initial root volume size was 48 GB. Then we
modified it using the vol size vol0 20g command. As a result, the root volume
size is now 20 GB. You may also use the vol size vol0 -28g command, which
will have the same end result.
Data ONTAP prevents you from setting the root option on a FlexVol volume that
is smaller than the minimum root volume size for your storage system model,
and prevents you from resizing the root volume below the minimum allowed size.
See Table 1 for details.
Table 1 Minimum root volume size requirement
Storage system
Minimum root FlexVol volume size
IBM Storage System N3700
10 GB
IBM Storage System N5200
12 GB
IBM Storage System N5500
16 GB
Adding more disks to the initial aggregate
Another scenario of optimizing the root volume and the aggregate volume is to
join all of the disks into one aggregate and combine it with the root volume
resizing as explained in the previous section or “Resizing root FlexVol” on
page 7. Then you will have better performance, as you have more disks spindle
in your aggregate and bigger capacity for data.
Resizing the Root Volume on IBM System Storage N series
11
You may use FilerView or CLI to add disks to the aggregate. Follow the steps
below to add more disks to aggr0 using FilerView:
1. At the FilerView, go to Aggregates → Manage, and choose aggr0. FilerView
will show you Aggregate aggr0 Properties. Click Add Disks. See Figure 9 for
a graphical illustration.
Figure 9 Aggregate properties
12
Resizing the Root Volume on IBM System Storage N series
2. After clicking Add Disks, an Aggregate Wizard window will open. Click Next.
See Figure 10 for a graphical illustration.
Figure 10 Aggregate Wizard window
3. Choose the disk selection method. You may either choose Automatic to let
Data ONTAP assign the disks for you, or Manual. We recommend that you
choose the Automatic method, as disks are automatically selected to match
those in the aggregate's existing plex. Click Next to continue. See Figure 11
for a graphical illustration.
Figure 11 Make disk selection
Resizing the Root Volume on IBM System Storage N series
13
4. The next window will show you the disk size available on the storage system.
Choose the disk size you want to use for this aggregate. You may choose
Any Disk, to let Data ONTAP automatically choose the best disk size for you,
or Manual, to choose the disk size manually. Click Next to continue. See
Figure 12 for a graphical illustration.
Figure 12 Choose disk size
14
Resizing the Root Volume on IBM System Storage N series
5. Then the wizard will ask you the number of disks you will add to the
aggregate. In Figure 13 you can see that using FilerView, you may only add
up to three disks from four spares available. This is because Data ONTAP
always frees up one disk to be assigned as global hot spare. You will be able
to use all the spares when adding disks using CLI, which is explained later.
Figure 13 Select number of disks to add
Resizing the Root Volume on IBM System Storage N series
15
6. The wizard will then show your configuration changes. Check the new
configuration and click Commit to apply changes. See Figure 14 for a
graphical configuration.
Figure 14 Commit changes
16
Resizing the Root Volume on IBM System Storage N series
7. When the changes have been committed, you will get a confirmation that the
change is successful. Click Close to close wizard. See Figure 15 for a
graphical illustration.
Figure 15 Confirmation window
Resizing the Root Volume on IBM System Storage N series
17
Now the number of disks for aggr0 has changed from four to five disks, and total
capacity has increased to 170 GB. See Figure 16.
Figure 16 Updated aggr0 properties
You can also add more disks to aggregate using CLI using the aggr add
command. The syntax is aggr add <aggr-name> [-f] [-n] [-g <raid-group>]
<disk-list>, where <disk-list> is either <ndisks>[@<disk-size>] or -d
<disk-name1> <disk-name2> ... <disk-nameN>. See the storage system man
page for further details.
Note: ndisks is the number of disks in the aggregate, including the parity
disks. The disks in this newly created aggregate come from the pool of spare
disks. The smallest disks in this pool join the aggregate first, unless you
specify the @size argument. size is the disk size in GB, and disks that are
within 10% of the specified size will be selected for use in the aggregate.
18
Resizing the Root Volume on IBM System Storage N series
In Example 4 we run the aggr status aggr0 -r command to check the current
number and disk size in aggr0.
Red2> aggr status aggr0 -r
Aggregate aggr0 (online, raid_dp) (block checksums)
Plex /aggr0/plex0 (online, normal, active)
RAID group /aggr0/plex0/rg0 (normal)
RAID Disk
--------dparity
parity
data
data
data
Device
-----0b.36
0b.35
0b.18
0b.20
0b.23
HA SHELF BAY
------------0b
2
4
0b
2
3
0b
1
2
0b
1
4
0b
1
7
CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
---- ---- ---- ----- -------------- -------------FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
Example 4 aggr status aggr0 -r command
In Example 4 we see that currently aggr0 consists of five units of FCAL 10k rpm
disks with 66 GB each, configured with RAID-DP. Next, in Example 5 on page 20,
we check how many spare disks are left on the filer by using the aggr status -r
command.
Resizing the Root Volume on IBM System Storage N series
19
Red2> aggr status -s
Spare disks
RAID Disk Device HA SHELF BAY CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
--------- ------ ------------- ---- ---- ---- ----- ---------------------Spare disks for block or zoned checksum traditional volumes or aggregates
spare
0b.16 0b 1
0
FC:B - FCAL 10000 68000/139264000 68552/140395088
spare
0b.26 0b 1
10
FC:B - FCAL 10000 68000/139264000 68552/140395088
spare
0b.27 0b 1
11
FC:B - FCAL 10000 68000/139264000 68552/140395088
Example 5 aggr status -s command
In Example 5, we see that currently the filer has three spare disks of 66 GB each.
20
Resizing the Root Volume on IBM System Storage N series
Next, in Example 6, we will run the aggr add aggr0 3 command to add three
disks to aggregate aggr0. We will not define the raid group to add, as we will let
Data ONTAP automatically assign the disks to whichever raid group is available.
Note: By default, the storage system fills up one RAID group with disks before
starting another RAID group. Suppose an aggregate currently has one RAID
group of 12 disks and its RAID group size is 14. If you add five disks to this
aggregate, it will have one RAID group with 14 disks and another RAID group
with three disks. The storage system does not evenly distribute disks among
RAID groups.
Red2> aggr add aggr0 3
WARNING! Continuing with aggr add will result in having no spare disk available for
one or more RAID groups.
Are you sure you want to continue with aggr add? yes
2 disks have been added to the aggregate. 1 disk needs to be zeroed before
addition to the aggregate. The process has been initiated and you will be notified
via the system log as disks are added.
Red2> Mon Apr 17 04:46:03 GMT [Red2: raid.rg.spares.low.unowned:warning]:
/aggr0/plex0/rg0 Assign unowned disks.
Mon Apr 17 04:47:00 GMT [Red2: monitor.globalStatus.nonCritical:warning]: There are
not enough spare disks. Assign unowned disks.
Mon Apr 17 05:00:00 GMT [Red2: kern.uptime.filer:info]:
5:00am up 5 days, 3:42
0 NFS ops, 9967 CIFS ops, 57 HTTP ops, 0 DAFS ops, 20849 FCP ops, 0 iSCSI ops
Mon Apr 17 05:05:44 GMT [Red2: raid.disk.zero.done:notice]: Disk /0b.16 Shelf 1 Bay
0 [NETAPP
X272_S10K7073F10 NA00] S/N [3KT1VH9D00007551UFTM] : disk zeroing
complete
Mon Apr 17 05:05:44 GMT [Red2: raid.vol.disk.add.done:notice]: Addition of Disk
/aggr0/plex0/rg0/0b.27 Shelf 1 Bay 11 [NETAPP
X272_S10K7073F10 NA00] S/N
[3KT1VGD100007551UBX2] to aggregate aggr0 has completed successfully
Mon Apr 17 05:05:44 GMT [Red2: raid.vol.disk.add.done:notice]: Addition of Disk
/aggr0/plex0/rg0/0b.26 Shelf 1 Bay 10 [NETAPP
X272_S10K7073F10 NA00] S/N
[3KT1VHR700007551XXTG] to aggregate aggr0 has completed successfully
Mon Apr 17 05:05:44 GMT [Red2: raid.vol.disk.add.done:notice]: Addition of Disk
/aggr0/plex0/rg0/0b.16 Shelf 1 Bay 0 [NETAPP
X272_S10K7073F10 NA00] S/N
[3KT1VH9D00007551UFTM] to aggregate aggr0 has completed successfully
Example 6 aggr add command
Resizing the Root Volume on IBM System Storage N series
21
After three disks are added, the aggr status aggr0 -r command will show eight
disks in aggr0, as in Example 7.
RAID Disk
--------dparity
parity
data
data
data
data
data
data
Device
-----0b.36
0b.35
0b.18
0b.20
0b.23
0b.16
0b.26
0b.27
HA SHELF BAY
-----------0b
2
4
0b
2
3
0b
1
2
0b
1
4
0b
1
7
0b
1
0
0b
1
10
0b
1
11
CHAN Pool Type RPM Used (MB/blks) Phys (MB/blks)
---- ---- ---- ----- -------------- -------------FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
FC:B
- FCAL 10000 68000/139264000 68552/140395088
Example 7 New aggr status
The new aggregate size is now 320 GB, as in Figure 17.
Figure 17 New root volume aggregate capacity
22
Resizing the Root Volume on IBM System Storage N series
However, the storage system status will show a degraded mode, as we have
used all the spares. See Figure 18.
Figure 18 Storage system without spare disk
If no spare disks exist in a storage system, Data ONTAP can continue to function
in degraded mode. Data ONTAP supports degraded mode in the case of
single-disk failure for aggregates configured with RAID4 protection and in the
case of single or double disk failure in aggregates configured for RAID-DP
protection.
Note: IBM recommends keeping at least one hot spare disk for each disk size
and disk type installed in your storage system. This allows the storage system
to use a disk of the same size and type as a failed disk when reconstructing a
failed disk. If a disk fails and a hot spare disk of the same size is not available,
the storage system uses a spare disk of the next available size up.
Note: In addition to keeping one spare per disk size and disk type, you must at
a minimum keep one spare per aggregate.
Resizing the Root Volume on IBM System Storage N series
23
In the next section we discuss adding more disks to a raid group as part of an
aggregate.
Larger versus smaller RAID groups
You can specify the number of disks in a RAID group and the RAID level of
protection, or you can use the default for the specific appliance. Adding more
data disks to a RAID group increases the striping of data across those disks,
which typically improves I/O performance. However, with more disks, there is a
greater risk that one of the disks might fail.
Configuring an optimum RAID group size for an aggregate requires a trade-off of
factors. You must decide which factor (speed of recovery, assurance against
data loss, or maximizing data storage space) is most important for the aggregate
that you are configuring. Table 2 shows the minimum, maximum, and default raid
group size for N series (N3700, N5200, N5500).
Table 2 IBM Storage System N series raid group size
Raid type
Minimum group
size
Maximum group
size
Default group size
RAID-DP
3
28
16
RAID-DP (ATA
disk)
3
16
14
RAID4
2
14
8
Advantages of large RAID groups
Large RAID group configurations offer the following advantages:
򐂰 More data drives available. An aggregate configured into a few large RAID
groups requires fewer drives reserved for parity than that same aggregate
configured into many small RAID groups.
򐂰 Small improvement in system performance. Write operations are generally
faster with larger RAID groups than with smaller RAID groups.
Advantages of small RAID groups
Small RAID group configurations offer the following advantages:
򐂰 Shorter disk reconstruction times. In case of disk failure within a small RAID
group, data reconstruction time is usually shorter than it would be within a
large RAID group.
򐂰 Decreased risk of data loss due to multiple disk failures. The probability of
data loss through double-disk failure within a RAID4 group or through
24
Resizing the Root Volume on IBM System Storage N series
triple-disk failure within a RAID-DP group is lower within a small RAID group
than within a large RAID group.
For example, whether you have a RAID group with fourteen disks or two RAID
groups with seven disks, you still have the same number of disks available for
striping. However, with multiple smaller RAID groups, you minimize the risk of
the performance impact during reconstruction and you minimize the risk of
multiple disk failure within each RAID group.
Advantages of RAID-DP over RAID4
With RAID-DP, you can use larger RAID groups because they offer more
protection. A RAID-DP group is more reliable than a RAID4 group that is half its
size, even though a RAID-DP group has twice as many disks. Thus, the
RAID-DP group provides better reliability with the same parity overhead.
The disks in a plex are not permitted to span spare pools. This behavior can be
overridden with the -f option. The same option can also be used to force using
disks that do not have matching rotational speed. The -f option has effect only
when used with the -d option specifying disks to use.
Summary
It is common, in the case of limited disk capacity, to deviate from the default root
volume configuration. However, do not compromise the system reliability and
always do comparison between the implemented configuration with its risks and
consideration.
The team that wrote this Redpaper
This Redpaper was produced by a team of specialists from around the world
working at the International Technical Support Organization, Tucson, Arizona.
Alex Osuna is a Project Leader with the San Jose International Technical
Support Organization. He has over 27 years of experience in the IT industry and
22 years of experience in the hardware/software storage area dealing with
maintenance, development, early ship programs, education, publishing,
performance analysis, and technical sales support. He holds 10 certifications
from IBM, Microsoft®, and Red Hat.
Chrisanthy Carlane is an IT Specialist with IBM Information Technology
Services in Indonesia. She has five years of experience providing
enterprise-wide infrastructure implementations, migration, and support for IBM
Resizing the Root Volume on IBM System Storage N series
25
Tape and Storage System and xSeries® servers. She has certifications with
IBM, Cisco, Microsoft, Red Hat, and McDATA and holds Bachelor of Economics
- Accounting from Tarumanagara University, Jakarta, Indonesia.
Thanks to the following people for their contributions to this project:
Norman Bogard, Technical Sales Specialist, IBM Advanced Technical Support.
Thorsten Busch, IBM ATS Customer Solutions Mainz, IBM Deutschland GmbH
26
Resizing the Root Volume on IBM System Storage N series
Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult
your local IBM representative for information on the products and services currently available in your area.
Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product, program, or service that
does not infringe any IBM intellectual property right may be used instead. However, it is the user's
responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this document.
The furnishing of this document does not give you any license to these patents. You can send license
inquiries, in writing, to:
IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY 10504-1785 U.S.A.
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION
PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR
IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer
of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made
to the information herein; these changes will be incorporated in new editions of the publication. IBM may
make improvements and/or changes in the product(s) and/or the program(s) described in this publication at
any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any
manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the
materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Information concerning non-IBM products was obtained from the suppliers of those products, their published
announcements or other publicly available sources. IBM has not tested those products and cannot confirm
the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on
the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information contains examples of data and reports used in daily business operations. To illustrate them
as completely as possible, the examples include the names of individuals, companies, brands, and products.
All of these names are fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrates programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs in
any form without payment to IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating platform for which the
sample programs are written. These examples have not been thoroughly tested under all conditions. IBM,
therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy,
modify, and distribute these sample programs in any form without payment to IBM for the purposes of
developing, using, marketing, or distributing application programs conforming to IBM's application
programming interfaces.
© Copyright International Business Machines Corporation 2006. All rights reserved.
Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by
GSA ADP Schedule Contract with IBM Corp.
27
This document created or updated on July 7, 2006.
Send us your comments in one of the following ways:
򐂰 Use the online Contact us review redbook form found at:
ibm.com/redbooks
򐂰 Send your comments in an email to:
redbook@us.ibm.com
򐂰 Mail your comments to:
IBM Corporation, International Technical Support Organization
Dept. HYTD Mail Station P099, 2455 South Road
Poughkeepsie, NY 12601-5400 U.S.A.
®
Trademarks
The following terms are trademarks of the International Business Machines Corporation in the United States,
other countries, or both:
Eserver®
Eserver®
Redbooks (logo)
™
xSeries®
IBM®
Redbooks™
System Storage™
The following terms are trademarks of other companies:
Data ONTAP, FilerView, The Network Appliance logo, the bolt design,Camera-to-Viewer, Center-to-Edge,
ContentDirector, ContentFabric, NetApp Availability Assurance, NetApp ProTech Expert, NOW, NOW
NetApp on the Web, RoboCache, RoboFiler, SecureAdmin, Serving Data by Design, Smart SAN,The
evolution of storage, Virtual File Manager, and Web Filer are trademarks of Network Appliance, Inc. in the
U.S. and other countries. All other brands or products are trademarks or registered trademarks of their
respective holders and should be treated as such.
Microsoft, and the Windows logo are trademarks of Microsoft Corporation in the United States, other
countries, or both.
Other company, product, or service names may be trademarks or service marks of others.
28
Infrastructure Simplification with IBM System Storage N Series