Additional prerequisites for multiple runs

The service templates provided and preconfigured in Ops Center Automator allow only a single task to run at the same time and do not support running multiple tasks concurrently. However, the following service templates allow up to 25 tasks to run concurrently by satisfying the following additional prerequisites.

Create Online Migration Pair
Migrate Data for Online Migration Pair
Clean up Online Migration Pair

For multiple runs, the Create Online Migration Pairs for Multiple Hosts service template can be used to run multiple Create Online Migration Pair tasks at once.

Software requirements for multiple runs

Ops Center Administrator v10.7.0 or later (only required when you specify "Select Hosts" for the "Source Selection" property)

Setup requirements for multiple runs

The Ops Center Automator server and Ops Center API Configuration Manager server must be on different servers.
The migration source storage system must be the same storage system for all migration tasks to be run at the same time.
The migration target storage system must be the same storage system for all migration tasks to be run at the same time.

Additional Ops Center Automator server settings

The Ops Center Automator server must be set to “High performance mode”. For more information, refer to "Configuring the performance mode" in the Hitachi Ops Center Automator Installation and Configuration Guide.
You must change the following values in the config_user.properties file:
```
plugin.threadPoolSize: 100
logger.TA.MaxFileSize: 100240
```
See "Changing the system configuration" in the Hitachi Ops Center Automator Installation and Configuration Guide.

Additional Ops Center API Configuration Manager server settings

The communication mode must be “fcConnectionMode”. For details, see "Appendix A. Changing the communication mode of the REST API server" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
The setting for the number of storage systems to be managed must be “BalanceMode” or “HighPerformanceMode". For more information, refer to "Setting the number of storage systems to be managed by the REST API" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide.
You must change the following values in StartupV.properties
```
rest.java.heapMemory.size: 6144
```
Refer to "Setting the java heap memory size on the Ops Center API Configuration Manager server" in the Hitachi Ops Center Automator Installation and Configuration Guide for more information.
You must register a single Ops Center API Configuration Manager to be used in multiple runs as the notification destination of configuration changes in the migration source and target storage systems. See "Appendix D: Sending notifications about changes to storage system configurations" in the Hitachi Ops Center API Configuration Manager REST API Reference Guide for more information.

Requirements for the server where the Ops Center product is installed

Ops Center Automator must meet the system requirements described below in addition to the requirements described in the Hitachi Ops Center Automator Installation and Configuration Guide.

Table. Additional server requirements for Ops Center Automator
Item	Value
OS	Windows (x64)
CPU	8 Core or higher
Memory	16 GB or higher

The Ops Center API Configuration Manager must meet the system requirements described below in addition to the requirements described in "Hardware and disk space requirements" in the Hitachi Ops Center API Configuration Manager System Requirements.

Table. Additional server requirements for Ops Center API Configuration Manager
Item	Value
OS	Windows (x64)
CPU	4 Core or higher
Memory	8 GB or higher

Scale of resources to be migrated

The upper limit of resources to be migrated that can be specified when running multiple tasks is shown in below.

Table. Upper limit of resources to be migrated
Item	Upper limit value
Maximum number of hosts	Up to 25 hosts in total for multiple running tasks
Maximum number of volumes	Up to 500 volumes in total for multiple running tasks
Maximum number of volumes that can be selected in a single task	Up to 500 volumes
Maxiumum number of paths per volume	Up to 16 paths both before and after migration

You can specify up to 500 volumes for all running tasks, but the maximum number of initial copy pairs that can be run simulataneously in the storage system is 64 by default. The storage system will gradually perform initial copy as long as the maximum number of initial copies is not exceeded.

If you want to increase the number of initial copy pairs to be copied simultaneously, you must increase the maximum number of initial copies from the “Remote Replication Options” window in Storage Navigator. If the Diskless Quorum feature is not used, the maximum number of initial copies should not exceed 200, because the Quorum disk may not be able to handle it.

For details, refer to the Global-Active Device User Guide for each storage system.

Storage systems supporting multiple runs

You must use the following storage systems when you run multiple Online Migration with Configuration Manager tasks.

Storage systems with the Use Diskless Quorum option enabled:

VSP G1000, VSP G1500, and VSP F1500: 80-06-86-00/00 or later
VSP 5100, 5500, 5100H, 5500H: 90-06-21-00/00 or later
VSP 5200, 5600, 5200H, 5600H: 90-08-01-00/00 or later

Storage systems with the Use Diskless Quorum option disabled:

VSP G1000, VSP G1500, and VSP F1500: 80-06-82-00/00-04 or later
VSP 5100, 5500, 5100H, 5500H: 90-04-06-00/00-05 or later
VSP 5200, 5600, 5200H, 5600H: 90-08-01-00/00 or later

Note: Multiple runs only support the VSP G1000, VSP G1500, and VSP F1500 as migration source storage systems and VSP G1000, VSP G1500, VSP F1500, VSP 5100, 5500, 5100H, 5500H, and VSP 5200, 5600, 5200H, 5600H as migration target storage systems.