Hitachi Global Link Manager Software Installation and Configuration Guide
Note: Do not execute two or more hcmds64dbclustersetup commands
concurrently. Do not execute the hcmds64dbclustersetup command and
the hcmds64getlogs command at the same time.
7. In Cluster Administrator, switch each group in which the Hitachi
Command Suite product service has been registered to the standby
system.
If Microsoft Failover Cluster is used (on OSs other than Windows Server
2012):
In Failover Cluster Management, right-click the resource group to
which the services used by Global Link Manager have been registered,
and then choose Move this service or application to another
node.
If Microsoft Failover Cluster is used (on Windows Server 2012):
In Failover Cluster Manager, right-click the role to which the services
used by Global Link Manager have been registered, choose Move, and
then Select Node.
8. On the secondary node, removing a Cluster Configuration.
Execute the following command:
Hitachi-Command-Suite-Common-Component-installation-folder\bin
\hcmds64dbclustersetup /removecluster /databasepath target-
folder-for-re-creating-the-database /exportpath target-folder-
for-storing-data /auto
Before executing the command, either delete target-folder-for-recreating-
the-database and target-folder-for-storing-data or make sure that the two
folders are empty.
On the local disk, deploy the target-folder-for-recreating-the-database
and target-folder-for-storing-data.
Specify an absolute path (maximum of 63 bytes) for target-folder-for-
recreating-the-database and target-folder-for-storing-data.
You can use the following characters for target-folder-for-re-creating-
thedatabase and target-folder-for-storing-data:
A to Z, a to z, 0 to 9, period (.), and underscore (_). You can also use a
backslash (\), colon (:), and forward slash (/) as the path delimiter.
When the /auto option is used, the system automatically stops Hitachi
Command Suite Common Component and starts HiRDB. After the
command is executed, both Hitachi Command Suite Common Component
and HiRDB are stopped. Depending on the machine performance, the
command is executed before HiRDB has completely started, and then the
KAPM06587-E message appears indicating that the export processing has
failed. In this case, manually start HiRDB, and then execute the
hcmds64dbclustersetup command without specifying the /auto option.
To start HiRDB, execute:
Hitachi-Command-Suite-Common-Component-installation-folder\bin
\hcmds64dbsrv /start
Installing Global Link Manager Clusters
4-27
Hitachi Global Link Manager Installation and Configuration Guide (Web Version)