Usage Scenarios For Native Disk Shelves With Gateways - IBM System Storage N Series Implementation Manual

Usage scenarios for native disk shelves with gateways

Expanding storage
after reaching
storage array limits
Simplifying
installation
Improving core file
availability
Using SnapLock
Compliance
functionality
6
This section describes a few ways that customers use native disk shelves with
gateways.
As an alternative to expanding your storage array, you can add disks shelves to
the gateway when you need additional storage. For example, assume you have
added disks to your Hitachi Tier 1 storage array. As a result, you have reached the
limit for the maximum number of disks that the current configuration can
support. Options for expanding storage are as follows:
◆
Add native disk shelves to the gateway
◆
Purchase more controller cards on the Hitachi storage array
◆
Add another storage array—for example, a Tier 2 storage array
When a gateway is ordered with disk shelves, initial setup of the system is easier
because the factory performs some installation tasks that must be performed at
the customer site for systems without native disk shelves. Tasks performed by the
factory include installing the root volume, the Data ONTAP software, and the
gateway license.
When a native disk shelf is installed on a gateway and the root volume is installed
on a disk, core dumps are likely to be more available than if the root volume is
installed on an array LUN. See
volume" on page 24 for more details.
If you need SnapLock Compliance functionality, you can add native disk shelves
to your gateway and create SnapLock Compliance aggregates on those disks.
SnapLock Compliance is not supported with all versions of Data ONTAP. See the
gateway Interoperability Matrix to determine if it is supported with your release
of Data ONTAP.
Note
Data ONTAP SnapLock Compliance aggregates with array LUNs is not
supported.
"Considerations when planning for the root
Usage scenarios for native disk shelves with gateways