Installation manual

Adding a Managed Volume
Selecting a VPU (optional)
CLI Storage-Management Guide 9-47
To mitigate this problem, you can assign the same namespace to both VPU domains.
This divides the namespace’s volumes between the domains. Each domain runs
independently; one can have a metadata failure without affecting the other. In the
example below, a metadata failure for volume 1 now only affects volume 3:
The volumes on domain 2, volume 5 and volume 7, are completely insulated from the
problem.
By default, a volume goes to the same VPU domain as any other volumes from the
same namespace. As with a direct volume, you can use the optional
domain clause in
the
vpu command to choose a domain for the current managed volume. For example,
the following command sequence assigns the current volume,
“medarcv~/test_results,” to VPU 2, domain 2:
bstnA6k(gbl)# namespace medarcv
bstnA6k(gbl-ns[medarcv])# volume /test_results
bstnA6k(gbl-ns-vol[medarcv~/test_results])# vpu 2 domain 2
bstnA6k(gbl-ns-vol[medarcv~/test_results])# ...
Reverting to Default-VPU Assignment
Before you enable the volume, you can remove the manual-VPU assignment. This
causes the namespace software to assign the volume according to the default rules
(refer back to “Default-VPU Assignment” on page 8-20). From gbl-ns-vol mode, use
the
no vpu command to revert to default-VPU assignment:
no vpu
single namespace
volume 3 volume 5volume 4
volume 6 volume 7volume 2volume 1
VPU 2VPU 1
D1 D2 D1 D2