You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/virtual-machines/workloads/mainframe-rehosting/ibm/deploy-ibm-db2-purescale-azure.md
+40-58Lines changed: 40 additions & 58 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -8,7 +8,7 @@ manager: mamccrea
8
8
ms.service: virtual-machines
9
9
ms.subservice: mainframe-rehosting
10
10
ms.topic: how-to
11
-
ms.date: 11/09/2018
11
+
ms.date: 04/19/2023
12
12
---
13
13
14
14
# Deploy IBM DB2 pureScale on Azure
@@ -30,35 +30,25 @@ The repository also has scripts for setting up a Grafana dashboard. You can use
30
30
31
31
The deploy.sh script creates and configures the Azure resources for this architecture. The script prompts you for the Azure subscription and virtual machines used in the target environment, and then performs the following operations:
32
32
33
-
- Sets up the resource group, virtual network, and subnets on Azure for the installation.
34
-
35
-
- Sets up the network security groups and SSH for the environment.
36
-
37
-
- Sets up multiple NICs on both the shared storage and the DB2 pureScale virtual machines.
38
-
39
-
- Creates the shared storage virtual machines. If you use Storage Spaces Direct or another storage solution, see [Storage Spaces Direct overview](/windows-server/storage/storage-spaces/storage-spaces-direct-overview).
40
-
41
-
- Creates the jumpbox virtual machine.
42
-
43
-
- Creates the DB2 pureScale virtual machines.
44
-
45
-
- Creates the witness virtual machine that DB2 pureScale pings. Skip this part of the deployment if your version of Db2 pureScale does not require a witness.
46
-
47
-
- Creates a Windows virtual machine to use for testing but doesn't install anything on it.
33
+
- Sets up the resource group, virtual network, and subnets on Azure for the installation.
34
+
- Sets up the network security groups and SSH for the environment.
35
+
- Sets up multiple NICs on both the shared storage and the DB2 pureScale virtual machines.
36
+
- Creates the shared storage virtual machines. If you use Storage Spaces Direct or another storage solution, see [Storage Spaces Direct overview](/windows-server/storage/storage-spaces/storage-spaces-direct-overview).
37
+
- Creates the jumpbox virtual machine.
38
+
- Creates the DB2 pureScale virtual machines.
39
+
- Creates the witness virtual machine that DB2 pureScale pings. Skip this part of the deployment if your version of Db2 pureScale does not require a witness.
40
+
- Creates a Windows virtual machine to use for testing but doesn't install anything on it.
48
41
49
42
Next, the deployment scripts set up an iSCSI virtual storage area network (vSAN) for shared storage on Azure. In this example, iSCSI connects to the shared storage cluster. In the original customer solution, GlusterFS was used. However, IBM no longer supports this approach. To maintain your support from IBM, you need to use a supported iSCSI-compatible file system. Microsoft offers Storage Spaces Direct (S2D) as an option.
50
43
51
44
This solution also gives you the option to install the iSCSI targets as a single Windows node. iSCSI provides a shared block storage interface over TCP/IP that allows the DB2 pureScale setup procedure to use a device interface to connect to shared storage.
52
45
53
46
The deployment scripts run these general steps:
54
47
55
-
1. Set up a shared storage cluster on Azure. This step involves at least two Linux nodes.
56
-
57
-
2. Set up an iSCSI Direct interface on target Linux servers for the shared storage cluster.
58
-
59
-
3. Set up the iSCSI initiator on the Linux virtual machines. The initiator will access the shared storage cluster by using an iSCSI target. For setup details, see [How To Configure An iSCSI Target And Initiator In Linux](https://www.rootusers.com/how-to-configure-an-iscsi-target-and-initiator-in-linux/) in the RootUsers documentation.
60
-
61
-
4. Install the shared storage layer for the iSCSI interface.
48
+
1. Set up a shared storage cluster on Azure. This step involves at least two Linux nodes.
49
+
2. Set up an iSCSI Direct interface on target Linux servers for the shared storage cluster.
50
+
3. Set up the iSCSI initiator on the Linux virtual machines. The initiator will access the shared storage cluster by using an iSCSI target. For setup details, see [How To Configure An iSCSI Target And Initiator In Linux](https://www.rootusers.com/how-to-configure-an-iscsi-target-and-initiator-in-linux/) in the RootUsers documentation.
51
+
4. Install the shared storage layer for the iSCSI interface.
62
52
63
53
After the scripts create the iSCSI device, the final step is to install DB2 pureScale. As part of the DB2 pureScale setup, [IBM Spectrum Scale](https://www.ibm.com/support/knowledgecenter/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/t0057167.html) (formerly known as GPFS) is compiled and installed on the GlusterFS cluster. This clustered file system enables DB2 pureScale to share data among the virtual machines that run the DB2 pureScale engine. For more information, see the [IBM Spectrum Scale](https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.0/ibmspectrumscale42_welcome.html) documentation on the IBM website.
64
54
@@ -73,30 +63,33 @@ The GitHub repository includes DB2server.rsp, a response (.rsp) file that enable
| Response File and Summary | first option | Install DB2 Server Edition with the IBM DB2 pureScale feature and save my settings in a response file |
92
-
|| Response file name | /root/DB2server.rsp |
82
+
|| Response file name |`/root/DB2server`.rsp |
93
83
94
84
### Notes about this deployment
95
85
96
86
- The values for /dev-dm0, /dev-dm1, /dev-dm2, and /dev-dm3 can change after a restart on the virtual machine where the setup takes place (d0 in the automated script). To find the right values, you can issue the following command before completing the response file on the server where the setup will run:
97
87
88
+
```bash
89
+
sudo ls -als /dev/mapper
98
90
```
99
-
[root\@d0 rhel]\# ls -als /dev/mapper
91
+
92
+
```output
100
93
total 0
101
94
0 drwxr-xr-x 2 root root 140 May 30 11:07 .
102
95
0 drwxr-xr-x 19 root root 4060 May 30 11:31 ..
@@ -108,37 +101,26 @@ The GitHub repository includes DB2server.rsp, a response (.rsp) file that enable
108
101
```
109
102
110
103
- The setup scripts use aliases for the iSCSI disks so that the actual names can be found easily.
111
-
112
-
- When the setup script is run on d0, the **/dev/dm-\*** values might be different on d1, cf0, and cf1. The difference in values doesn't affect the DB2 pureScale setup.
104
+
- When the setup script is run on d0, the `/dev/dm-\*` values might be different on d1, cf0, and cf1. The difference in values doesn't affect the DB2 pureScale setup.
113
105
114
106
## Troubleshooting and known issues
115
107
116
108
The GitHub repo includes a knowledge base that the authors maintain. It lists potential problems you might have and resolutions you can try. For example, known problems can happen when:
117
109
118
-
- You're trying to reach the gateway IP address.
119
-
120
-
- You're compiling General Public License (GPL).
121
-
122
-
- The security handshake between hosts fails.
123
-
124
-
- The DB2 installer detects an existing file system.
125
-
126
-
- You're manually installing IBM Spectrum Scale.
127
-
128
-
- You're installing DB2 pureScale when IBM Spectrum Scale is already created.
129
-
130
-
- You're removing DB2 pureScale and IBM Spectrum Scale.
110
+
- You're trying to reach the gateway IP address.
111
+
- You're compiling General Public License (GPL).
112
+
- The security handshake between hosts fails.
113
+
- The DB2 installer detects an existing file system.
114
+
- You're manually installing IBM Spectrum Scale.
115
+
- You're installing DB2 pureScale when IBM Spectrum Scale is already created.
116
+
- You're removing DB2 pureScale and IBM Spectrum Scale.
131
117
132
118
For more information about these and other known problems, see the kb.md file in the [DB2onAzure](https://aka.ms/DB2onAzure) repo.
133
119
134
120
## Next steps
135
121
136
-
-[Creating required users for a DB2 pureScale Feature installation](https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/t0055374.html?pos=2)
-[DB2 pureScale Clusters Data Solution](https://www.ibmbigdatahub.com/blog/db2-purescale-clustered-database-solution-part-1)
141
-
142
-
-[IBM Data Studio](https://www.ibm.com/developerworks/downloads/im/data/index.html/)
143
-
144
-
-[Azure Virtual Data Center Lift and Shift Guide](https://azure.microsoft.com/resources/azure-virtual-datacenter-lift-and-shift-guide/)
122
+
-[Creating required users for a DB2 pureScale Feature installation](https://www.ibm.com/support/knowledgecenter/en/SSEPGG_11.1.0/com.ibm.db2.luw.qb.server.doc/doc/t0055374.html?pos=2)
0 commit comments