2.6.3 Moving resources in the case of 1:1 active/standby (with subsystems and partial cluster operation) configurations

Resources to be moved

In the case of a 1:1 active/standby configuration (with subsystems and partial cluster operation), transfer the following resources of the subsystems to be used in cluster operation to a shared disk. Do not transfer the resources of subsystems that will not be used in cluster operation.

For PRIMECLUSTER (for Solaris or Linux version)

Directory for calendar control information:
```
/var/opt/FJSVjmcal/post/sysn
```
n: Subsystem number
Jobscheduler database directory:
```
/var/opt/FJSVJOBSC/JOBDBn
```
n: Subsystem number
Job Execution Control spool directory:
```
/var/opt/FJSVMJS/var/spool/mjes/mjesn
```
n: Subsystem number
Directory for Job Execution Control operation information:
```
/etc/opt/FJSVMJS/etc/mjes/mjesn
```
n: Subsystem number
The database directory for Master Schedule Management (only if the Master Schedule Management function is enabled)
```
/var/opt/FJSVstem/stemDBn
```
n: Subsystem number

For MC/ServiceGuard

Directory for calendar control information:
```
/opt/FHPjmcal/post/sysn
```
n: Subsystem number
Jobscheduler database directory:
```
/opt/FHPJOBSCH/db/JOBDBn
```
n: Subsystem number
Job Execution Control spool directory:
```
/opt/FHPMJS/var/spool/mjes/mjesn
```
n: Subsystem number
Directory for Job Execution Control operation information:
```
/opt/FHPMJS/etc/mjes/mjesn
```
n: Subsystem number
The database directory for Master Schedule Management (only if the Master Schedule Management function is enabled)
```
/var/opt/FJSVstem/stemDBn
```
n: Subsystem number

For HACMP

Directory for calendar control information:
```
/opt/FAIXjmcal/post/sysn
```
n: Subsystem number
Jobscheduler database directory:
```
/opt/FAIXJOBSC/db/JOBDBn
```
n: Subsystem number
Job Execution Control spool directory:
```
/opt/FAIXMJS/var/spool/mjes/mjesn
```
n: Subsystem number
Directory for Job Execution Control operation information:
```
/opt/FAIXMJS/etc/mjes/mjesn
```
n: Subsystem number
The database directory for Master Schedule Management (only if the Master Schedule Management function is enabled)
```
/var/opt/FJSVstem/stemDBn
```
n: Subsystem number

Migration procedure

For PRIMECLUSTER (for Solaris or Linux version)

This section explains the migration procedure using an example where Subsystem 1 is used in cluster operation and "/disk1" is designated as the mount point of the shared disk. The command line provided here as a sample is for the Solaris version.

1) Stop the daemon.

Stop the Systemwalker Operation Manager daemon.

# /opt/systemwalker/bin/poperationmgr -s

If Systemwalker Operation Manager shares the environment with Systemwalker Centric Manager, always use the poperationmgr command with the -s option.

2) Mount the shared disk.

Mount the shared disk.
```
# mount /disk1 (*1)
```
*1
The command line for Linux version is as follows. (In this example, the device is "/dev/sdb1".)
```
# /bin/mount /dev/sdb1 /disk1
```

3) Move resources from the active node to the shared disk.

Move resources from the active node to the shared disk.

# mkdir -p /disk1/FJSVfwseo/JM1 (*1)
# chmod -R 755 /disk1/FJSVfwseo

# mkdir -p /disk1/FJSVjmcal/post
# chmod -R 755 /disk1/FJSVjmcal
# mv /var/opt/FJSVjmcal/post/sys1 /disk1/FJSVjmcal/post/sys1

# mkdir -p /disk1/FJSVJOBSC
# chmod -R 755 /disk1/FJSVJOBSC
# mv /var/opt/FJSVJOBSC/JOBDB1 /disk1/FJSVJOBSC/JOBDB1

# mkdir -p /disk1/FJSVMJS/var/spool
# chmod -R 755 /disk1/FJSVMJS
# mv /var/opt/FJSVMJS/var/spool/mjes/mjes1 /disk1/FJSVMJS/var/spool/mjes1

# mkdir -p /disk1/FJSVMJS/etc
# chmod -R 755 /disk1/FJSVMJS
# mv /etc/opt/FJSVMJS/etc/mjes/mjes1 /disk1/FJSVMJS/etc/mjes1

# mkdir -p /disk1/FJSVstem (*2)
# chmod -R 755 /disk1/FJSVstem (*2)
# mv /var/opt/FJSVstem/stemDB1 /disk1/FJSVstem/stemDB1 (*2)

*1: For security information, only create directories on the shared disk at this stage. Security information is applied in "2.7 Settings for Automatic Reflection".

*2: This operation is performed only when the Master Schedule Management function is enabled.

4) Delete resources from the standby node.

Delete resources from the standby node.

# rm -r /var/opt/FJSVjmcal/post/sys1

# rm -r /var/opt/FJSVJOBSC/JOBDB1

# rm -r /var/opt/FJSVMJS/var/spool/mjes/mjes1

# rm -r /etc/opt/FJSVMJS/etc/mjes/mjes1

# rm -r /var/opt/FJSVstem/stemDB1 (*1)

*1: This operation is performed only when the Master Schedule Management function is enabled and the target directory exists.

5) Create symbolic links to the relocated resources.

Create symbolic links on the active and standby nodes so that the resources transferred to the shared disk can be accessed from both active and standby nodes.

# ln -s /disk1/FJSVfwseo/JM1 /var/opt/FJSVfwseo/JM1

# ln -s /disk1/FJSVjmcal/post/sys1 /var/opt/FJSVjmcal/post/sys1

# ln -s /disk1/FJSVJOBSC/JOBDB1 /var/opt/FJSVJOBSC/JOBDB1

# ln -s /disk1/FJSVMJS/var/spool/mjes1 /var/spool/mjes/mjes1

# ln -s /disk1/FJSVMJS/etc/mjes1 /etc/mjes/mjes1

# ln -s /disk1/FJSVstem/stemDB1 /var/opt/FJSVstem/stemDB1 (*1)

*1: This operation is performed only when the Master Schedule Management function is enabled.

6) Configure settings for SELinux.

This must be done only in Linux environments where SELinux is enabled. Otherwise, it is not necessary.

Execute the following commands in order to set the SELinux security policies on the relocated resources. They must be executed on each node with the shared disk mounted.

# /usr/sbin/semanage fcontext -a -t var_t '/disk1/FJSVfwseo/JM1(/.*)?'
# /usr/sbin/semanage fcontext -a -t var_t '/disk1/FJSVjmcal(/.*)?'
# /usr/sbin/semanage fcontext -a -t var_t '/disk1/FJSVJOBSC(/.*)?'
# /usr/sbin/semanage fcontext -a -t var_t '/disk1/FJSVstem(/.*)?' (*1)
# /usr/sbin/semanage fcontext -a -t sw_fjsvmjs_spool_t '/disk1/FJSVMJS/var/spool(/.*)?'
# /usr/sbin/semanage fcontext -a -t etc_t '/disk1/FJSVMJS/etc(/.*)?'
# /sbin/restorecon -R /disk1

*1:: This operation is performed only when the Master Schedule Management function is enabled.

7) Unmount the shared disk.

Unmount the shared disk.
```
# umount /disk1(*1)
```
*1
The command line for Linux version is as follows:
```
# /bin/umount /disk1
```

For MC/ServiceGuard

In the examples that explain the migration procedure shown below, Subsystem 1 runs as a cluster system, the shared disk device is "/dev/vg01/lvol1", and the mount point to the shared disk is "/disk1".

1) Stop the daemon

Stop the Systemwalker Operation daemon.

# /opt/systemwalker/bin/poperationmgr -s

In the case of mixed environments with Systemwalker Centric Manager, the -s option must be specified for the poperationmgr command.

2) Mount the shared disk

Mount the shared disk.

# vgchange -c y /dev/vg01
# vgchange -a e /dev/vg01
# mount /dev/vg01/lvol1 /disk1

3) Migrate the active node resources to the shared disk

Migrate the active node resources to the shared disk.

# mkdir -p /disk1/FJSVfwseo/JM1 (*1)
# chmod -R 755 /disk1/FJSVfwseo

# mkdir -p /disk1/FHPjmcal/post
# chmod -R 755 /disk1/FHPjmcal
# mv /opt/FHPjmcal/post/sys1 /disk1/FHPjmcal/post/sys1

# mkdir -p /disk1/FHPJOBSCH
# chmod -R 755 /disk1/FHPJOBSCH
# mv /opt/FHPJOBSCH/db/JOBDB1 /disk1/FHPJOBSCH/JOBDB1

# mkdir -p /disk1/FHPMJS/spool
# chmod -R 755 /disk1/FHPMJS
# mv /opt/FHPMJS/var/spool/mjes/mjes1 /disk1/FHPMJS/spool/mjes1

# mkdir -p /disk1/FHPMJS/etc
# chmod -R 755 /disk1/FHPMJS
# mv /opt/FHPMJS/etc/mjes/mjes1 /disk1/FHPMJS/etc/mjes1

# mkdir -p /disk1/FJSVstem (*2)
# chmod -R 755 /disk1/FJSVstem (*2)
# mv /var/opt/FJSVstem/stemDB1 /disk1/FJSVstem/stemDB1 (*2)

*1: For security information, only create directories on the shared disk at this stage. Security information is applied in "2.7 Settings for Automatic Reflection".

*2: This operation is performed only when the Master Schedule Management function is enabled.

4) Delete the standby node resources

Delete the standby node resources.

# rm -r /opt/FHPjmcal/post/sys1

# rm -r /opt/FHPJOBSCH/db/JOBDB1

# rm -r /opt/FHPMJS/var/spool/mjes/mjes1

# rm -r /opt/FHPMJS/etc/mjes/mjes1

# rm -r /var/opt/FJSVstem/stemDB1 (*1)

*1: This operation is performed only when the Master Schedule Management function is enabled and the target directory exists.

5) Create the symbolic links to the resources that were migrated

So that the resources that were migrated to the shared disk can be used on both the active and the standby nodes, create the symbolic links on each node.

# ln -s /disk1/FJSVfwseo/JM1 /var/opt/FJSVfwseo/JM1

# ln -s /disk1/FHPjmcal/post/sys1 /opt/FHPjmcal/post/sys1

# ln -s /disk1/FHPJOBSCH/JOBDB1 /opt/FHPJOBSCH/db/JOBDB1

# ln -s /disk1/FHPMJS/spool/mjes1 /var/spool/mjes/mjes1

# ln -s /disk1/FHPMJS/etc/mjes1 /etc/mjes/mjes1

# ln -s /disk1/FJSVstem/stemDB1 /var/opt/FJSVstem/stemDB1 (*1)

*1: This operation is performed only when the Master Schedule Management function is enabled.

6) Unmount the shared disk

Unmount the shared disk.

# umount /disk1
# vgchange -a n /dev/vg01