I.3.1 Setup in Single-User Mode

Execute the following procedure on all nodes of the copy destination.

Start the system in single-user mode.
Note
When using the GFS Shared File System in the copy source server, check that the following message has been output to the /var/adm/messages file before migrating the node to single-user mode.
WARNING: sfcfsrm:5001: Starting the sfcfrmd daemon was suspended because quorum does not exist
If this message is displayed, the node cannot be migrated to single-user mode with shutdown(1M) because the system startup is suspended. In this case, migrate the node to single-user mode after it is stopped forcibly in OBP mode.
Add or change the host name.
Refer to the system in the copy source to add or change the host name to /etc/inet/hosts according to the environment in the copy destination.
Change the primary management sever, secondary management server, httpip, and mip in the Web-Based Admin View.
1. Set the IP addresses of the primary management server (fuji4) and the secondary management server (fuji5).
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam primary-server 10.20.30.102
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam secondary-server 10.20.30.103
```
2. Set httpip.
  - fuji4
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam httpip 10.20.30.102
```
  - fuji5
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam httpip 10.20.30.103
```
3. Set mip.
  - fuji4
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam mip 10.20.30.102
```
  - fuji5
```
# /etc/opt/FJSVwvbs/etc/bin/wvSetparam mip 10.20.30.103
```
4. Change the connection target information of the Java application.
  Edit the [Target] parameter from properties of the shortcut and the desktop shortcut of the Java application to change the connection target information.
  Example when the home folder of a Windows login user is "C:\Users\[User name]\":
  - Shortcut for connecting to the primary management server
```
"C:\Users\[User name]\AppData\Local\Programs\PRIMECLUSTER Web-Based Admin View Startup\bin\javaw.exe"
-jar "WVStartup.jar" "10.20.30.102" "8081"
```
  - Shortcut for connecting to the secondary management server
```
"C:\Users\[User name]\AppData\Local\Programs\PRIMECLUSTER Web-Based Admin View Startup\bin\javaw.exe"
-jar "WVStartup.jar" "10.20.30.103" "8081"
```
Change the CF node name, CIP/SysNode name, cluster name, and device names of the interconnect.
Note
For the naming conventions (cluster name and CF node name), see "5.1.1 Setting Up CF and CIP".
1. Change the string of the CF node name within the CF node name and the CIP/SysNode name that are described in /etc/cip.cf.
  [Before change]
```
fuji2       fuji2RMS:netmask:255.255.255.0
fuji3       fuji3RMS:netmask:255.255.255.0
```
  [After change]
```
fuji4       fuji4RMS:netmask:255.255.255.0
fuji5       fuji5RMS:netmask:255.255.255.0
```
2. Refer to the system in the copy source to correct the string of the CF node name within the CIP/SysNode name that are described in /etc/inet/hosts according to the environment in the copy destination.
  [Copy source]
```
192.168.0.1     fuji2RMS
192.168.0.2     fuji3RMS
```
  [After change]
```
192.168.0.3     fuji4RMS
192.168.0.4     fuji5RMS
```
3. Change the CF node name, cluster name, and device names of the interconnect described in /etc/default/cluster.
  [Before change]
```
nodename fuji2
clustername PRIMECLUSTER1
device /dev/hme2
device /dev/hme3
```
  [After change]
```
nodename fuji4
clustername PRIMECLUSTER2
device /dev/vnet2
device /dev/vnet3
```
Restore the symbolic links to the device file.
For Solaris 11 or later, restore the symbolic links to the device file that was removed due to cloning.
```
# /opt/SMAW/SMAWcf/bin/cfrecoverdev
```
Cancel the SF settings.
Delete the /etc/opt/SMAW/SMAWsf/rcsd.cfg file.
```
# rm /etc/opt/SMAW/SMAWsf/rcsd.cfg
```
Delete the file of the Cluster Resource Management Facility.
If the /etc/opt/FJSVcluster/FJSVcldbm/config/shmno file exists, delete the file.
```
# rm /etc/opt/FJSVcluster/FJSVcldbm/config/shmno 
```
Change the node of the Cluster Resource Management Facility.
Note
This procedure is unnecessary when the Cluster Resource Management Facility.
Execute the following command to change the node name of the Cluster Resource Management Facility.
```
# /etc/opt/FJSVcluster/bin/clchgnodename
```
Delete the information in the management partition of GFS.
Note
This procedure is unnecessary when the GFS Shared File System is not being used.
Delete the information in the management partition of the GFS Shared File System. Execute the following command on all nodes.
```
# rm /var/opt/FJSVgfs/sfcfsrm.conf
```
Change the GDS settings.
Delete the local class and shared class definitions of GDS. Perform the following procedure on all nodes.
1. Delete the settings of class name in the "/etc/opt/FJSVsdx/sysdb.d/class.db" file.
```
...
Class1          <- Delete all the lines of cluster name
...
```
2. Delete all files named with the class name in the "/etc/opt/FJSVsdx/sysdb.d" directory.
```
# cd /etc/opt/FJSVsdx/sysdb.d
# rm Class1
```
3. Correct the sfdsk.conf file.
  When cloning a cluster system from other environment other than a Kernel Zone to the Kernel Zone, add the line: SDX_KZONE_SUPPORT=on to the /kernel/drv/sfdsk.conf file.
  When cloning a cluster system from the Kernel Zone to the environment other than the Kernel Zone, delete the line: SDX_KZONE_SUPPORT=on from the /kernel/drv/sfdsk.conf file.
4. Delete the devname.db file.
```
# cd /etc/opt/FJSVsdx/dev
# rm -f devname.db
```
Prepare for changing the GLS settings.
If you are using GLS, perform the following:
1. Refer to the system in the copy source to correct the /etc/inet/hosts file according to the environment in the copy destination.
  [Copy source]
```
10.34.214.185 takeoverIP # Virtual IP
10.34.214.181 primecl01  # primecl01 physical IP
10.34.214.182 primecl02  # primecl02 physical IP
10.34.214.188 swhub1     # primary HUB IP
10.34.214.189 swhub2     # secondary HUB IP
```
  [After change]
```
10.34.214.195 takeoverIP2 # Virtual IP
10.34.214.191 primecl03   # primecl03 physical IP
10.34.214.192 primecl04   # primecl04 physical IP
10.34.214.188 swhub1      # primary HUB IP
10.34.214.189 swhub2      # secondary HUB IP
```
2. Isolate the copy destination system so that there are no IP addresses in duplicate with the copy source system.
  Beforehand, make sure that the NIC cables are disconnected or the copy source is stopped, or connect from the copy source system to an isolated network, taking care that there are no IP addresses in duplicate with the copy source system.
Restriction of the automatic startup of RMS
Restrict the automatic startup of RMS
Check the settings of the current automatic startup of RMS and execute the following command according to the settings.
```
# hvsetenv HV_RCSTART
1    <- Check this value
```
- If "0" is set, the automatic startup of RMS has been restricted. Go to Step 13.
- If "1" is set, execute the following commands to restrict the automatic startup of RMS.
```
# hvsetenv HV_RCSTART 0
# hvsetenv HV_RCSTART
0    <- Check "0" is output
```
After completing above procedure on all nodes of the copy destination, start up all nodes in multi-user mode.