Follow the steps below to configure a Highly Available production server environment:
-
On the primary production server and recovery server, varyonvg all volume group(s) associated with the Assure MIMIX for AIX configuration.
-
On the primary production server, use PowerHA C-SPOC to create file systems /usr/scrt/run/c<Primary Context ID> and /usr/scrt/run/c<FailOver Context ID> with inline logs on one of the shared enhanced concurrent mode volume groups that contains the production server logical volumes you want protected. The filesystem must be at least 128 MB in size.
-
On the primary production server, mount the file systems associated with the Assure MIMIX for AIX configuration.
-
mount /usr/scrt/run/c<Primary Context ID> -
mount /usr/scrt/run/c<Failover ContextID>
-
-
Use the Replication Group wizard to configure the Primary Context.
Refer to the section Chapter 6, Configuring Replication Groups.
After the creation of the Assure MIMIX for AIX Replication Group Configuration perform the following steps.
Note: You must manually copy and load the Assure MIMIX for AIX configuration onto the failover production server. -
On the primary production server, create a file with the Primary Context ID configuration.
-
odmget -q ContextID=<Primary Context ID> SCCuObj SCCuAttr SCCuRel >/tmp/C<Primary Context ID>.cfg -
Copy this configuration file to /tmp on the Failover Production Server.
-
-
On the primary production server, create a file with the Failover Context ID configuration.
-
odmget -q ContextID=<Failover Context ID> SCCuObj SCCuAttr SCCuRel >/tmp/C<Failover Context ID>.cfg
-
Copy this configuration file to /tmp on the Failover Production Server.
-
-
On the failover production server use rthostid to obtain its “HostId”.
/usr/scrt/bin/rthostid -
On the failover production server edit the production HostId stanza in the /tmp/C<Primary Context ID>.cfg file. Replace the contents of the “ObjectAttributeValue” field with the output from the "rthostid" command.
SCCuAttr: ObjectName = "production" ConfigObjectSerial = 15 ObjectType = "SCRT/info/host" ObjectAttributeName = "HostId" ObjectAttributeValue = "6CABA7DF" ObjectAttributeType = "ulong" SerialNumber = 15006 ObjectNlsIndex = 0 SC_reserved = 0 ContextID = 1 -
On the failover production server edit the backup HostId stanza in the /tmp/C<Failover Context ID>.cfg file replacing the content of the “ObjectAttributeValue” field with the output from the “rthostid” command.
SCCuAttr: ObjectName = "backup" ConfigObjectSerial = 4 ObjectType = "SCRT/info/host" ObjectAttributeName = "HostId" ObjectAttributeValue = "5FBBC3EF" ObjectAttributeType = "ulong" SerialNumber = 4006 ObjectNlsIndex = 0 SC_reserved = 0 ContextID = 11 -
On the failover production server, use sccfgd_putcfg to load the configurations onto the node.
-
/usr/scrt/bin/sccfgd_putcfg <Primary Context ID> /tmp/C<Primary Context ID>.cfg -
/usr/scrt/bin/sccfgd_putcfg<Failover Context ID> /tmp/C<Failover Context ID>.cfg
-
-
On the primary production server, use
/usr/sbin/lvlstmajorto obtain a list of unused device major numbers:lvlstmajor
46,50,54,57,64,67,70,73..75,82..93,95...
-
On the failover production server, use /
usr/sbin/lvlstmajorto obtain a list of unused device major numbers:lvlstmajor
51,54,57,61,65,69,82...
-
On the primary production server, use es_ha_config to configure a device major number for the Primary Context ID. Choose a device major number that is the same on both production servers.
es_ha_config <Primary ContextID> [NewMajorNumber]For example, when you execute:
es_ha_config 1 82The Primary Context ID is 1, and the new device major number 82, is available on both production servers.
-
On the failover production server, use es_ha_config to configure a device major number for the Primary Context ID. Choose a device major number that is the same on both production servers.
es_ha_config<Primary ContextID>[NewMajorNumber]For example, when you execute
es_ha_config 1 82The Primary Context ID is 1, and the new device major number 82, is available on both production servers.
-
On the primary production server, unmount the file systems associated with the Assure MIMIX for AIX configuration.
-
unmount /usr/scrt/run/c<Primary Context ID> -
unmount /usr/scrt/run/c<Failover Context ID>
-
-
On the primary production server, varyoff all volume group(s) associated with the Assure MIMIX for AIX configuration.
-
On both production servers, the file systems protected by Assure MIMIX for AIX should not be automatically mounted at system restart. Change the auto-mount attribute to “no”.
-
On the secondary production server, add the replication group port numbers to /etc/services.
The port numbers to add can be found in the /etc/services file on the primary production server.
For example, these port numbers are for primary context id 1 and failover context id 17:
sc1aba_dchannel 5779/tcp sc1aba_dchannel 5783/tcp sc1lca_channel 5780/tcp sc1lca_dchannel 5784/tcp sc1aa_channel 5778/tcp sc1aa_achannel 5782/tcp sc1ra_channel 5785/tcp sc1ca_channel 5781/tcp sc17aba_channel 5787/tcp sc17aba_dchannel 5791/tcp sc17lca_channel 5788/tcp sc17lca_dchannel 5792/tcp sc17aa_channel 5786/tcp sc17aa_achannel 5790/tcp sc17ra_channel 5793/tcp sc17ca_channel 5789/tcp -
Before starting Assure MIMIX for AIX on the production server, you must stop your application and unmount the protected file systems.