Replace a Brick Storage Enclosure
You can replace existing Bricks with new Bricks within a storage domain. You
must migrate the volumes to the new Bricks because clones are not migrated
with the parent volumes when Bricks are replaced.
1 Delete the clones of existing volumes in the Bricks that must be replaced.
2 Create a minimum of one new Storage Domain.
3 Add the new Bricks to the Pillar Axiom 600 system.
4 Accept the newly added Bricks into the new Storage Domain.
5 Verify that the capacity from the new Bricks has been added successfully in
the Pillar Axiom 600 system.
6 If the Bricks that must be added are in the existing primary Storage Domain,
make sure you add a minimum of two Bricks of the same Storage Class to
a single new Storage Domain before you promote the new Storage Domain
to primary.
Important! Before making a Storage Domain primary or migrating data to a
new Storage Domain, add all the Bricks to the new Storage Domain. Failure
to do so may cause performance issues because the Pillar Axiom 600
system might not be able to stripe the data across the appropriate number
of Bricks for the Quality of Service (QoS) and Storage Class.
7 Make the new Storage Domain primary.
When the new Storage Domain is made primary, the persistence VLUN is
migrated from the old primary Storage Domain to the new primary Storage
Domain. The migration uses Bricks in the following order: serial ATA
(SATA), Fiber channel (FC), and solid state drive (SSD).
8 Migrate all the volumes on the old Bricks to the desired Storage Class in the
new Storage Domain.
Tip: For minimum impact to system performance, migrate one volume at a
time.
9 Use the storage allocation CLI
axiomcli storage_allocation
command to ensure that all volumes have been migrated from the old
Bricks that must be replaced.
Chapter 3 Install Components
Replace a Brick Storage Enclosure
80