Table of Contents
Advertisement
Note -
created.
Hot spares are allocated as a percentage of total pool size and are independent of the profile
chosen (with the exception of striped, which doesn't support hot spares). Because hot spares are
allocated for each storage configuration step, it is much more efficient to configure storage as a
whole than it is to add storage in small increments.
In a cluster configuration, cache devices installed in controller slots are available only to the
node which has the storage pool imported. In a cluster, it is possible to configure cache devices
on both nodes to be part of the same pool. To do this, takeover the pool on the passive node, and
then add storage and select the cache devices. This has the effect of having half the global cache
devices configured at any one time. While the data on the cache devices will be lost on failover,
the new cache devices can be used on the new node.
Cache devices installed in disk shelf slots, when added to a pool, are automatically imported
during a cluster failback or takeover. No additional pool configuration is required.
Understanding the Appliance Status
The Status section provides a summary of appliance status and configuration options. Use the
following sections for conceptual and procedural information about appliance status views and
related service configuration:
"About the Oracle ZFS Storage Appliance" on page 19
■
"Dashboard Status" on page 114
■
"Summary of Memory Use" on page 119
■
"Disk Activity Dashboard" on page 120
■
"Dashboard CLI" on page 122
■
"Running the Dashboard Continuously" on page 123
■
"Status Dashboard Settings" on page 124
■
"Changing the Displayed Activity Statistics" on page 126
■
"Changing the Activity Thresholds" on page 126
■
"NDMP Status" on page 127
■
"NDMP States" on page 128
■
When different sized log devices are in different chassis, only striped log profiles can be
Understanding the Appliance Status
Configuring the Appliance
113
Advertisement
Table of Contents
