To setup an OpenEdge 10.2B SP5 (64 bit) Windows 2008 R2 clustering test environment under VMware follow the following steps:
- Install 3 Windows 2008 R2 enterprise virtual machines behind NAT (evaluation versions of Windows 2008 R2 can be download for free from the Microsoft website)
- install FreeNAS 7 on another virtual machine behind the same NAT as the 3 Windows 2008 R2 machines (for example version 0.7.2 revision 7903 from https://sourceforge.net/projects/freenas/files/FreeNAS-7-Stable/) or configure a Windows 2008 R2 machine as follow:
On the machine where the Windows 2008 R2 iSCSI storage will be located install the free Microsoft iSCSI Software Target program (the size of the executable iSCSITargetQFE4.exe is about 6.4MB) from http://www.microsoft.com/en-us/download/details.aspx?id=19867
When executing iSCSITargetQFE4.exe a destination folder will be prompted (value by default: C:\iSCSTarget) to unpack the installation files. An html page will open on C:\iSCSTarget\Index.htm, press on the link 'iSCSI Software Target (x64)' pointing to the installation file C:\iSCSTarget\x64\iscsitarget_public.msi and click 'Run', the standard installation directory will be C:\Program Files\Microsoft iSCSI Software Target\
Once the Microsoft iSCSI software target setup is finished go to Start -> Administrative Tools -> Microsoft iSCSI Software Target
Do a right click on 'Devices' and select 'Create Virtual Disk' -> Next -> C:\disks\firstdisk.vhd -> 2048 -> first disk -> Next -> Finish
Do a right click on 'iSCSI Targets' -> Create iSCSI Target -> Next -> firstdisk -> 'firstdisk' as iSCSI target name and Description -> firstdisk -> Next -> Finish
Under 'iSCSI Targets' do a right click on 'firstdisk' and select 'Add Existing Virtual Disk to iSCSI Target' and select the virtual disk with the description 'first disk' -> OK
Under 'iSCSI Targets' do a right click on 'firstdisk' and select 'Properties' and select the tab 'iSCSI Initiators' -> Add... -> Identifier Type 'IP' -> value 'IPhostnameNode1' -> OK -> Yes (warning about multiple initiators) -> Add... -> Identifier Type 'IP' -> value 'IPhostnameNode2' -> OK -> Yes (warning about multiple initiators)
then do the same for the second iSCSI disk:
Do a right click on 'Devices' and select 'Create Virtual Disk' -> Next -> C:\disks\seconddisk.vhd -> 2048 -> second disk -> Next -> Finish
Do a right click on 'iSCSI Targets' -> Create iSCSI Target -> Next -> seconddisk -> 'seconddisk' as iSCSI target name and Description -> seconddisk -> Next -> Finish
Under 'iSCSI Targets' do a right click on 'seconddisk' and select 'Add Existing Virtual Disk to iSCSI Target' and select the virtual disk with the description 'first disk' -> OK
Under 'iSCSI Targets' do a right click on 'seconddisk' and select 'Properties' and select the tab 'iSCSI Initiators' -> Add... -> Identifier Type 'IP' -> value 'IPhostnameNode1' -> OK -> Yes (warning about multiple initiators) -> Add... -> Identifier Type 'IP' -> value 'IPhostnameNode2' -> OK -> Yes (warning about multiple initiators)
A reboot of the machine running the iSCSI target might be necessary.
On the Windows cluster nodes go to Start -> Administrative tools -> iSCSI Initiator if the program is started for the first time on that Windows 200R2 installation a popup will apppear prompting for the authorisation to start the 'Microsoft iSCSI service automatically', confirm by pressing 'YES'
In the 'Target:' field of the 'Targets' tab fill in the host name or IP of the Windows machine running Microsoft iSCSI target and click 'Quick Connect...' under 'Discovered targets' the 2 disks should now be seen, first select the first disk an click on 'Connect' and then select the second disk and click on 'Connect' again and then click on 'Done'.
Go in the 'Volumes and Devices' tab and click on 'Auto Configure' and 'OK'
Then go to Start and do a right click on Computer and go to 'Manage' and in the left pane go to 'Storage' -> 'Disk management' a popup will appear about initializing the 2 disk, press OK.
Then do a right click on the new unallocated discs and select 'New Simple Volume...' -> Next -> Next -> Finish
Make sure the drives letters are the same on the 2 Windows cluster nodes and that the disks are put offline by doing a right click on the label containing a text similar to:
Disk 1
Basic
2,00 GB
Online
- With DCPROMO create a domain controller from one of the W2008 R2 machines and create 2 users clusterA and clusterB and make them part of the domain admins and of the Administrator groups.
- Follow the steps described here to configure the FreeNAS 7 machine as the ISCSI storage:
http://www.sysprobs.com/nas-vmware-workstation-iscsi-target
- On the 2 w2008 R2 cluster node machines install the features .Net Framework 3.5 and Failover Clustering as well as an installation of OpenEdge 10.2B SP5 64 bit (with exactly the same features, parameters and directories on both Windows machines). Installing the 32 bit version of OpenEdge 10.2B will make it impossible to use Microsoft clustering under Windows 2008 R2, to make sure the 64 bit version of OpenEdge is installed go to Start -> All Programs -> OpenEdge -> Config (or launch the command 'showcfg' in a proenv command prompt window), the 'Port Number:' value of the serials listed should indicate 33 (and not 31)
- Join the 2 machines that are not domain controller to the domain created previously on the new Windows domain controller.
- Follow the steps described here to configure the 2 Windows cluster node machines to connect to the ISCSI storage:
http://www.sysprobs.com/setup-windows-2008-cluster-vmware-workstation
If the 2 Windows cluster nodes are given a fixed IP adress then the virtual cluster node will have a fixed IP adress as well (an IP will need to be entered during the Windows cluster setup), if the 2 Windows cluster nodes are given IP adresses through DHCP then the virtual cluster node will have an IP adress automatically assigned by DHCP as well.
- log into the active Windows cluster node machine with the Windows domain user or users
- add the Windows domain account(s) used to login into the Windows cluster nodes in the 'Administrators' group of the 2 Windows cluster nodes
- add the registry key HKLM/Cluster/RessourceTypes/Progress to the active Windows cluster node machine if that key is not already present (the Windows cluster service needs to be running and it need to be done on the active Windows cluster node machine)
- in the proenv command line window opened as local Administrator enter: 'set PSC_CLUSTER_PATH=%DLC%'
- in that same Proenv command line window opened as local Administrator on the active Windows cluster node machine execute the command 'pscluster install' (some information is now added under the registry key 'HKLM/Cluster/RessourceTypes/Progress')
- Create a database with 'prodb testdb demo' on a virtual iSCSI disk
- create a testdb.pf file containing '-cluster protected -S 2345'
- the syntax of the command to enable clustering for an OpenEdge database is 'procluster db-name enable [-pf params-file] [AI][BI][APW=n][WDOG]'
For example, when the command 'procluster testdb enable -pf testdb.pf AI BI APW=2 WDOG' is executed the following message will show up: 'Failover Clusters registration has been successfully performed for database F:\directory\testdb. (12462)' and the following resources will be created under the 'OpenEdgeDatabase' Services and applications:
F:\directory\testdb.db
F:\directory\testdb.db_AIW
F:\directory\testdb.db_APW1
F:\directory\testdb.db_APW2
F:\directory\testdb.db_BIW
F:\directory\testdb.db_WDOG
- in a Windows powershell command window opened as local Administrator type the commands:
PS C:\Users\AAA2> import-module FailoverClusters
PS C:\Users\AAA2> Get-ClusterResource
A new group "OpenEdgeDatabase" should now be visible in the output of the Windows powershell
The "OpenEdgeDatabase" group should now also be added to the Failover Cluster Manager.
- it should now be possible to use the Failover Cluster Manager to manage the newly created Windows clustered database.
To add an additional secondary broker (for example a dedicated broker for SQL connections) as a resource in the Windows Failover Cluster Manager you need do the following:
First create a .pf file like F:\directory\databaseNameSecondaryBroker.pf for the database secondary broker.
Hereunder an example of content for databaseName.pf for the existing main broker (now) dedicated to 4GL connections:
-cluster protected -n 12 -Mn 4 -Ma 5 -Mpb 2 -N tcp -S 4200 -ServerType 4GL
and hereunder an example of content for secondaryBroker.pf for the new secondary broker dedicated to SQL connections:
-m3 -Ma 1 -Mpb 1 -N tcp -S 4205 -ServerType SQL
In the Windows failover Cluster Manager go into the left pane and go to 'Failover Cluster Manager -> CLUSTERNAME -> Services and applications -> right click on OpenEdgeDatabase -> Add a resource -> More resources... -> Add Progress Database'
In the central pane of the Windows failover Cluster Manager rename the newly created resource 'New Progress Datase' under 'Other Resources' to a more meaningful name like for example 'secondaryBrokerSQLdatabaseName', then do a right click on the resource 'secondaryBrokerSQLdatabaseName' and go to the 'Dependencies' tab and click on the field 'Click here to add a dependency' and select the database resource of your existing database main broker resource, by default a name similar to 'M:\directory\databaseName' and click 'Apply' then go to the 'Parameter' tab and fill in the fields with data like this:
'Database File Spec:' -> F:\directory\databaseName.db (same as in existing main broker database resource)
'Working Directory:' -> F:\wrk_directory (same as in the main broker database resource)
'Start Command:' -> C:\Progress\OPENED~1\bin\mprosrv(same as in existing main broker database resource)
'Start Options:' -> -pf F:\directory\databaseNameSecondaryBroker.pf
leave the fields 'Stop Command:' and 'Stop Options:' empty (these commands will be executed by the database main broker resource)
