Stopping Services and Releasing Resources [Switchover Destination Site]

Save Configuration Information

When restoration of the switchover source site is planned after a failback operation, save the following information in a location other than the switchover information storage folder on the switchover destination site specified in the DR definition file.

For the settings of the DR definition file, refer to "3.3 Manager Installation and Configuration".

Configuration Information of the Switchover Destination Site

Execute the rcxmgrexport command to save the configuration information of the switchover destination site.

Execution of the rcxrepdef command and the rcxstorage command are not necessary.
Example

[Windows Manager]
```
>Installation_folder\SVROR\Manager\bin\rcxmgrexport -dir C:\Users\Administrator\work\backup\Export <RETURN>
```
[Linux Manager]
```
# /opt/FJSVrcvmr/bin/rcxmgrexport -dir /root/work/backup/Export <RETURN>
```
For details on the rcxmgrexport command, refer to "B.1 rcxmgrexport".
For physical/virtual L-Server switchover (VM host/VM guest), the definition file containing the information of the VM management software on the switchover site which was created when performing "3.6 Creating Files Used for Switchover"
For virtual L-Server switchover (VM guest), the VM pool definition file containing the information of the VM host on the switchover site which was created when performing "3.6 Creating Files Used for Switchover"

The saved information is used during "4.5 Operation after Failback".

Release Resources

For Active-Active operation

Physical servers used for switchover need to be released from the operation of the switchover destination site using one of the following methods.

When manually releasing servers used for switchover from pools
1. Stop services operating on the physical servers used for switchover.
  
  When the physical OS is operating, shutdown the physical servers.
  
  However, do not shut down physical servers to be used as VM hosts during switchover.
  
  For L-Servers operating on the VM hosts, delete or migrate the servers to VM hosts other than those used for switchover.
  
  For details on deletion, refer to "8.3.16 Reconfiguration Page" in the "User's Guide for Tenant Administrators CE".
  
  For details on migration, refer to "17.7 Migration between VM Hosts" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
2. Release the physical servers which were stopped in step a from the physical L-Server. Or delete the physical L-Servers. However, physical servers to be used as VM hosts during switchover are not the target of this operation.
  
  For details on how to release the physical servers from the physical L-Servers, refer to "17.8 Allocating and Releasing Resources to L-Servers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
3. Unregister the physical servers stopped in step a or VM hosts from the resource pool.
4. When a physical server used for switchover is configured as a spare server, cancel the spare server setting.

When releasing servers used for switchover by deleting tenants

Identify the physical servers used for L-Platforms/L-Servers in the tenants to be deleted or VM hosts, using the GUI or the CLI.
When the physical OS is operating on the physical servers identified in step a, shutdown the physical servers. When being operated as VM hosts, do not shut them down.

Clean up the tenants to be deleted.

Execute the rcxadm config cleanup -tenant command to clean up the tenants to be deleted on the switchover destination site.

When executing the cleanup command (rcxadm config cleanup), add the -predr option and the -deluser option.

Table 4.3 Conditions for -predr Option Addition
Virtual L-Server Switchover (VM guest)	-predr Option
Switched over	Added
Not switched over	Not added

Table 4.4 Conditions for the -deluser Option (When Using Single Sign-On Authentication)
Directory Service Information	-deluser Option
Shared among sites	Not added
Not shared among sites	Added

Information

When the -predr option is added to the cleanup command (rcxadm config cleanup), it unregisters the virtual L-Server resources deleted from managers and VM guest information linked to the resources from the VM management software.

This operation is necessary for synchronization of information on VM management software and Resource Orchestrator, when using the VMware virtual L-Server switchover (VM guest) method.

When the -deluser option is added to the cleanup command (rcxadm config cleanup), it deletes the user resources deleted from managers and user information linked to the resources from directory services.

When directory services are shared between sites, deleting user information from directory services disables recovery of the deleted user information, so ensure users are not deleted.

Note

When tenants are deleted using the rcxadm config cleanup command, VMware cloning images used for L-Server deployment in the tenants will be unregistered from resource pools. To continue using the cloning images, register them to resource pools again.

Execute the following procedure, when using servers that have not been used as physical L-Servers in the switchover destination site as physical L-Servers for switchover.

Execute the rcxadm server list command.

[Windows Manager]
```
>Installation_folder\SVROR\Manager\bin\rcxadm server list <RETURN>
```
[Linux Manager]
```
# /opt/FJSVrcvmr/bin/rcxadm server list <RETURN>
```
For details on the rcxadm server list command, refer to "3.11 rcxadm server" in the "Reference Guide (Command/XML) CE".
Execute the following procedure for any servers for which a value is given in the SERVER item of the rcxadm server list execution results, within the servers used for physical L-Server switchover.
1. Delete the target server from the ROR console server tree.
2. Register the target server in the ROR console server tree.
  
  In this case, do not register the agent.

For Active-Standby operation

In either of the following cases, execute the following procedure from steps 1 to 3.

When performing site switchover
When performing tenant switchover for the first time

Stop all operations of the switchover destination site.

When performing site switchover and either of the following conditions are satisfied, it is not necessary to perform steps 2 and 3.
- There are no physical L-Servers that are switchover targets on the switchover source site
- None of the physical servers that are switchover targets are already used as physical L-Servers on the switchover destination site
Execute the following command to clean up the configuration information of the entire switchover destination site.

When executing the cleanup command (rcxadm config cleanup), add the -predr option and the -deluser option on the same conditions as in "When releasing servers used for switchover by deleting tenants".

When using internal authentication, do not add the -deluser option.
Example
- When performing physical/virtual L-Server switchover (VM host/VM guest), and the directory service information is not shared among sites
  
  [Windows Manager]
  >Installation_folder\SVROR\Manager\bin\rcxadm config cleanup -deluser <RETURN>
  [Linux Manager]
  # /opt/FJSVrcvmr/bin/rcxadm config cleanup -deluser <RETURN>
- When performing virtual L-Server switchover (VM guest), and the directory service information is shared between sites using Active Directory
  
  [Windows Manager]
  >Installation_folder\SVROR\Manager\bin\rcxadm config cleanup -predr <RETURN>
  [Linux Manager]
  # /opt/FJSVrcvmr/bin/rcxadm config cleanup -predr <RETURN>
Point
- When the cleanup target L-Servers are in Unknown status, only the management information of managers is cleaned up. As the entities of the VM guest inventory are not deleted, manually delete the VM guest inventory from the VM management software, after the managed servers are recovered.
- When the automatic collection of switchover information is enabled, performing cleanup disables the setting.
  
  Refer to "4.2.16 Exporting Configuration Information and Resuming Automatic Collection of Switchover Information [Switchover Destination Site]" to enable the setting when necessary.
Execute the following procedure when using servers that have not been used as physical L-Servers in the switchover destination site as physical L-Servers for switchover.
1. Execute the rcxadm server list command.
  
  [Windows Manager]
```
>Installation_folder\SVROR\Manager\bin\rcxadm server list <RETURN>
```
  [Linux Manager]
```
# /opt/FJSVrcvmr/bin/rcxadm server list <RETURN>
```
  For details on the rcxadm server list command, refer to "3.11 rcxadm server" in the "Reference Guide (Command/XML) CE".
2. Execute the following procedure for any servers for which a value is given in the SERVER item of the rcxadm server list execution results, within the servers used for physical L-Server switchover.
  1. Delete the target server from the ROR console server tree.
  2. Register the target server in the ROR console server tree.
  In this case, do not register the agent.

Information

Executing the rcxadm config cleanup command either deletes the following resources or unregisters them from the resource pool.

When the -tenant option is specified

Table 4.5 List of Resources to Be Cleaned Up (with the -tenant Option Specified)
	Resources Belonging to the Specified Tenant	Global Resources Used by the Specified Tenant	Other Resources
User	-	-	-
User Group	-	-	-
L-Servers	Yes	-	-
L-Server Templates	-	-	-
Image	Yes	Yes	-
AddressSet	Yes	Yes (*)	-
Network	Yes	Yes (*)	-
Pool	Yes	Yes (*)	-
Folder	-	-	-
VMHost	No	No (*)	-
Server	No	No (*)	-
Virtual_Storage	No	No (*)	-
Disk	No	No (*)	-
Network_device	No	No (*)	-
Customized role	-	-	-

Yes: Deletion of resources

No: Unregistration from the resource pool

-: Not applicable

* Note: When the user who executed the command is the last user of the specified tenant, the resources will be processed.

When the -tenant option is not specified (when cleaning up an entire site)

Table 4.6 List of Resources to Be Cleaned Up (without the -tenant Option Specified)
	Resources Belonging to Tenants	Global Resources Used by Tenants	Other Resources
User	-	-	Yes (*1)
User Group	-	-	Yes (*2)
L-Servers	Yes	-	Yes
L-Server Templates	-	-	Yes
Image	Yes	Yes	Yes
AddressSet	Yes	Yes	Yes
Network	Yes	Yes	Yes
Pool	Yes	Yes	Yes
Folder	-	-	Yes
VMHost	No	No	No
Server	No	No	No
Virtual_Storage	No	No	No
Disk	No	No	No
Network_device	No	No	No
Customized role	-	-	Yes

Yes: Deletion of resources

No: Unregistration from the resource pool

-: Not applicable

*1: Infrastructure administrators and dual-role administrators whose access scope is "all" are excluded.

*2: The user groups with "supervisor" users are excluded.

For details on the rcxadm config cleanup command, refer to "B.3 rcxadm config".

4.2.1 Stopping Services and Releasing Resources [Switchover Destination Site]