C.9 Use of WSFC
- Organization of this subsection
(1) Accounts used in the cluster configuration
For WSFC, you can use a Local System account for services even in the cluster configuration. The account of each service is not changed in this configuration. The following table lists and describes accounts used in the JP1/DH - Server system.
No. |
Account |
Description |
---|---|---|
1 |
Local System (or System) |
Used as an account to run the JP1/DH - Server application and reverse proxy processes. This account must have full control permissions for the installation folder and shared disk. |
2 |
User account used to create a cluster |
Used when a WSFC cluster is set up. This account must belong to the Domain Admins group. |
3 |
Cluster account |
Computer account for the cluster itself. |
4 |
Computer account for clustered services or applications |
Computer account used for clustered services or applications. |
5 |
postgres |
Used as an account to run the database. This account must have read or write permission for the shared disk. |
(2) Registry key used in the cluster configuration
In the default JP1/DH - Server configuration, the startup option D of the database is stored in the registry key. You must change the value of the following registry key from the installation drive to the shared disk:
\HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\JP1_DH_DATABASE_SVR\ImagePath
An example is shown as follows:
- From
C:/Program Files/Hitachi/jp1dh/server/PostgreSQL/9.4/bin/pg_ctl.exe runservice -N "JP1_DH_DATABASE_SVR" -D " C:/Program Files/Hitachi/jp1dh/server/PostgreSQL/9.4/data" -w
- To
C:/Program Files/Hitachi/jp1dh/server/PostgreSQL/9.4/bin/pg_ctl.exe runservice -N "JP1_DH_DATABASE_SVR" -D "I:/PostgreSQL/9.4/data" -w
(3) Settings for each generic service
All JP1/DH - Server applications are installed as Windows services. The following tables list and describe the settings for each service.
No. |
Category |
Item |
Value |
---|---|---|---|
1 |
General |
Resource Name |
JP1_DH_DATABASE_SVR |
2 |
Resource type |
Generic Service |
|
3 |
Service name |
JP1_DH_DATABASE_SVR |
|
4 |
Startup parameters |
"JP1/DH-Server-installation-folder\PostgreSQL\9.4\bin\pg_ctl.exe" runservice -N "JP1_DH_DATABASE_SVR" -D "I:\PostgreSQL\9.4\data" -w |
|
5 |
Use Network Name for computer name |
Selected |
|
6 |
Dependencies |
Service name and conditions |
Cluster disk name AND cluster network name |
7 |
Policies |
Response to resource failure |
If resource fails, attempt restart on current node |
8 |
Period for restarts (mm:ss) |
15:00 (default) |
|
9 |
Maximum restarts in the specified period |
1 (default) |
|
10 |
If restart is unsuccessful, fail over all resources in this service or application |
Selected (default) |
|
11 |
If all the restart attempts fail, begin restarting again after the specified period (hh:mm) |
01:00 (default) |
|
12 |
Pending timeout (mm:ss) |
03:00 (default) |
|
13 |
Advanced Policies |
Possible Owners |
Node 001 Node 002 |
14 |
Basic resource health check interval |
Use standard time period for the resource type |
|
15 |
Thorough resource health check interval |
Use standard time period for the resource type |
|
16 |
Run this resource in a separate Resource Monitor |
Not selected |
|
17 |
Registry Replication |
Not specified |
No. |
Category |
Item |
Value |
---|---|---|---|
1 |
General |
Resource Name |
JP1_DH_WEB CONTAINER |
2 |
Resource type |
Generic Service |
|
3 |
Service name |
JP1_DH_WEBCON |
|
4 |
Startup parameters |
"JP1/DH-Server-installation-folder\sbin\jp1dhwebcon.exe" -start |
|
5 |
Use Network Name for computer name |
Not selected |
|
6 |
Dependencies |
Service name and conditions |
JP1_DH_DATABASE_SVR |
7 |
Policies |
Response to resource failure |
If resource fails, attempt restart on current node |
8 |
Period for restarts (mm:ss) |
15:00 (default) |
|
9 |
Maximum restarts in the specified period |
1 (default) |
|
10 |
If restart is unsuccessful, fail over all resources in this service or application |
Selected (default) |
|
11 |
If all the restart attempts fail, begin restarting again after the specified period (hh:mm) |
01:00 (default) |
|
12 |
Pending timeout (mm:ss) |
03:00 (default) |
|
13 |
Advanced Policies |
Possible Owners |
Node 001 Node 002 |
14 |
Basic resource health check interval |
Use standard time period for the resource type |
|
15 |
Thorough resource health check interval |
Use standard time period for the resource type |
|
16 |
Run this resource in a separate Resource Monitor |
Not selected |
|
17 |
Registry Replication |
Not specified |
No. |
Category |
Item |
Value |
---|---|---|---|
1 |
General |
Resource Name |
JP1_DH_WEB SVR |
2 |
Resource type |
Generic Service |
|
3 |
Service name |
JP1_DH_WEBSVR |
|
4 |
Startup parameters |
Not specified |
|
5 |
Use Network Name for computer name |
Not selected |
|
6 |
Dependencies |
Service name and conditions |
JP1_DH_WEB CONTAINER |
7 |
Policies |
Response to resource failure |
If resource fails, attempt restart on current node |
8 |
Period for restarts (mm:ss) |
15:00 (default) |
|
9 |
Maximum restarts in the specified period |
1 (default) |
|
10 |
If restart is unsuccessful, fail over all resources in this service or application |
Selected (default) |
|
11 |
If all the restart attempts fail, begin restarting again after the specified period (hh:mm) |
01:00 (default) |
|
12 |
Pending timeout (mm:ss) |
03:00 (default) |
|
13 |
Advanced Policies |
Possible Owners |
Node 001 Node 002 |
14 |
Basic resource health check interval |
Use standard time period for the resource type |
|
15 |
Thorough resource health check interval |
Use standard time period for the resource type |
|
16 |
Run this resource in a separate Resource Monitor |
Not selected |
|
17 |
Registry Replication |
Not specified |
(4) Notes on the cluster configuration
-
A cluster configuration managed by WSFC requires Active Directory.
-
If your JP1/DH - Server applications run on Windows Server 2012, Windows Server 2012 R2 or Windows Server 2016, a domain controller must be running on a separate machine.
-
When you restart a clustered system, do not restart multiple machines at the same time. They must be restarted one by one.
(5) Setup
This subsection describes how to set up a WSFC cluster configuration.
For this configuration, every node must be running the same version of Windows Server and be a member of the same Active Directory domain.
-
Prepare a set of hardware components used to configure the cluster. The necessary set of components is as follows:
-
More than one machine
-
Shared disk (SCSI-connected)
-
Switch
-
Network interface card (NIC)
Except for the shared disk, prepare as many hardware devices as the number of the machines. In addition, one machine requires two or more network interface cards.
-
-
Determine the Active Directory domain that your cluster belongs to.
Consider joining the existing Active Directory domain if you have one. If the existing domain cannot be used, or if one does not exist, create a new Active Directory domain for your cluster configuration.
-
If you create a new Active Directory domain, determine where Active Directory will be installed.
Prepare a dedicated machine for Active Directory and then install Active Directory.
- Important
-
Although running Active Directory on a different node from the JP1/DH - Server node in the cluster configuration is possible, we do not recommend this.
-
Install the Failover Clustering feature in all nodes so that they can join the cluster configuration.
For details about the Failover Clustering feature, see the Windows Help.