Download EdgeWare OS User Manual - Cutting Edge Networked Storage

EDITING THE RESOURCE CONFIGURATION IN A RUNNING CLUSTER
Limited changes can be made to the configuration of a failover cluster without breaking it or
swapping Primary roles. These are essentially those found in the Create/Modify Resource page
except for the top two lines, plus the contents of Advanced Configuration. See Figure 120.
1. Go to Clustering > IP Failover > Create/Modify Resource on the Primary’s UI. The
Resource Status should be Up (green).
2. Make changes to Advanced Configuration if desired, and hit Save.
3. Make changes in the Create/Modify Resource page, except for the top two lines. See
Step IV of the previous subhead.
4. Select Save. This returns you to the module main page.
5. Select Apply Changes.
BREAKING A FAILOVER CLUSTER
Note: This is an emergency operation. This procedure involves races, and therefore Cutting Edge
cannot guarantee the results of performing it. Nevertheless we include it here because of its
potential utility to customers. In particular, it is very useful during the setup phase of an
installation, when failover has just been enabled and significant user data has not accumulated, if
it is desired to back out and try again with a somewhat changed resource configuration.
The result of breaking a failover cluster is to place both Storage Servers back in the state they
were in at the end of step II of the previous subhead, “IP Failover (Heartbeat Monitoring)”. Thus,
their HARs are set up on the Primary, ready to be activated in a non-failover setting, but none of
the Heartbeat configuration is there. After reaching this point, changes can be made to the HARs
and failover rebuilt from step III on, if desired.
1. Disconnect all NAS clients and iSCSI initiators, if any, that are using the failover cluster as
storage. This may involve first closing down some user applications. In iSCSI, then delete
the partition (compare “Formatting the iSCSI Virtual Drive in Microsoft Windows” above
in this manual), then enter Initator and log off the Target and remove all traces of the
volume (compare “How to Connect with a Microsoft iSCSI Initiator” part C).
2. If applicable, perform a Configuration Backup (see Maintenance > Integrity above in this
manual).
3. Stop all high-availability resources (HARs) that are running on the failover cluster,
whether NAS, iSCSI, or rsync. For example, to stop CIFS, go to the Networking > CIFS
module main page on the Primary and select Stop Samba Servers. Keep a list of all of
these.
4. Make sure a UI window is open for both the Primary and the Secondary. Go to the
Clustering > IP Failover page on both UIs.
Page 160