The CloudM Migrate Service Manager is an essential application for managing and configuring the core migration service on a CloudM Migrate Self-Hosted server. It is installed by default on both 'Basic' and 'Advanced' installations of a Primary or Secondary Migration Service.
Admins use it to control service settings (for example, to scale out the migration infrastructure or optimize performance), start and stop the migration service, and view service logs.
Introduction and Access
The CloudM Migrate Service Manager is primarily intended for CloudM Migrate Self-Hosted users.
Note: If you are a CloudM Migrate Hosted user, you cannot access the CloudM Migrate Service Manager. While installed in these environments, access is restricted to CloudM Support and Development teams.
The Service Manager can be accessed locally via the Windows Start menu by navigating to Start > All Programs > CloudM > CloudM Migrate Service Manager.
Key Capabilities and Configuration
The Service Manager provides the following key functionalities:
-
Configuration Management: Adjust service settings on the machine where the application is installed.
-
Service Control: Start, Stop, and Restart the migration service.
-
Log and Event Viewing: View events generated by the Primary and/or Secondary Migration Services.
-
External Tool Access:
-
Open Services Management Console: Access the Windows built-in Service Management Console.
-
Open Event Viewer (Application View): Access the Windows built-in Event Viewer.
-
While most options can be left at default settings, the settings most frequently adjusted are Maximum User Migrations and Maximum Complete Migrations. These control the number of entity threads that can be migrated concurrently on each server and the number of overall concurrent migration batches.
Applying Configuration Changes
Configuration changes made within the Service Manager are only applied after clicking the Update Configuration button. A service restart is required for these changes to take effect.
The service can be restarted by clicking the drop-down arrow in the Stop button and selecting Restart.
Important: If you restart the service while a migration is in progress, the migration will stop ungracefully and will not produce a migration report. We highly recommend ensuring no migrations are running, by stopping them, before applying configuration updates that require a service restart.
Configuration Settings Reference
The following sections detail the configurable items within the Service Manager.
Service Settings
-
ServicesEndpoint: The endpoint name for the migration service. (Rarely requires modification.) -
Validate SSL Certificates: Determines whether the service validates SSL certificates of services it connects to. -
Run Primary Service: Controls whether the Primary Service is active. Only one Primary Service should run per migration network. -
Run Secondary Service: Controls whether the Secondary Service is active. Many Secondary Services can run within one migration network. Secondary and Primary can run on the same server.
Heartbeat and Retry Settings
-
Heartbeat: The interval at which Secondary Services provide state information to the Primary Service. -
Maximum Start Attempts: The maximum number of times the service will attempt to start. -
Start Attempt Delay (ms): The time (in milliseconds) to wait before retrying a service startup if the previous attempt failed. -
Primary Persist State Interval (min): The interval (in minutes) at which the migration service state is persisted by the Primary Service.
Data Storage and Migration Balancing
-
Redis Server Location: The address of the Redis server if it is not located at the same address as the SQL Server. Credentials can also be provided (e.g.,8.8.8.8or8.8.8.8, password=Password1). -
Migration Balancer-
Allocate Migration Items Based On Parent: Configures whether migration items are allocated based on configuration or only parent configuration. -
Allocate Migration Items Busy First: Determines whether migration items are allocated to secondary servers based on a busy-first algorithm.
-
Migration Limits
-
Maximum Complete Migrations: The maximum number of concurrent overall migrations or batches running concurrently. -
Maximum User Migrations: The maximum number of entity (users, groups, etc) migrations to run per Secondary Service simultaneously. -
Migration Queue Scan Interval: The interval at which the migration queue is scanned for migrations awaiting processing.
System Timeouts
-
Unresponsive Secondary Timeout (mins): The maximum time to wait for status updates from a Secondary Service before marking it as inactive and potentially removed from operation. -
Ignore Unresponsive Secondary (mins): The duration to ignore a Secondary Service that has previously failed. -
Migration Item Processing Timeout (mins): (Requires clarification and definition.) -
Available Secondary Wait Time (mins): The time to wait from the start of a migration before failing if no Secondary Service is available. -
Message time to live (seconds): The timeout applied to messages delivered when communicating between machines via NServiceBus. -
Primary Secondary Timeout (mins): The timeout applied to messages processed when communicating between the Primary and Secondary Services. -
Service Health Check Interval (mins): The interval at which the Windows service health status is checked. -
Primary Heartbeat (ms): The interval at which the Primary Service updates its alive status. -
Unresponsive Primary Timeout (ms): The maximum time until the Primary Service is considered dead, used to avoid multiple primary services running simultaneously.
Miscellaneous (Misc) Settings
-
Secondary Maximum Error Count: The maximum number of serious system errors a Secondary Service can encounter before it is taken out of operation. -
Failed Migration Retry Count: The maximum number of times a migration will be retried if it fails due to a system error.
CloudM Migrate Service Manager Use Cases
The following information applies exclusively to CloudM Migrate Self-Hosted for multi-server installations.
By default, the settings for migration limits are
Maximum Complete Migrations: 2
and
Maximum User Migrations: 20.
Use Case: Migrating 100 Users (1 Primary and 2 Secondary Servers)
Scenario 1: Single Batch Configuration
-
Setup: 1 batch of 100 users.
-
Execution: Each of the 2 Secondary servers will process 20 users concurrently, resulting in a total of 40 concurrent user threads. The single batch will utilize all 40 available threads immediately. As each user migration completes, a new user from the remaining queue will automatically start, maintaining 40 concurrent user threads until the entire batch is complete.
Scenario 2: Two Batch Configurations
-
Setup: 2 batches (Batch 1: 50 users, Batch 2: 50 users).
-
Execution: Batch 1 starts and utilizes all 40 available threads. As users from Batch 1 complete, their threads become free. Batch 2 will only begin when the total number of threads utilized by Batch 1 drops below 40. Once started, both batches will run concurrently, limited by the Maximum Complete Migrations setting (which is 2 by default), meaning you'll have 2 batches running at the same time.
Important Notes
- Increasing the number of Secondary servers will increase the available Maximum User Migrations concurrently, but it won't increase the number of concurrent batches (which is controlled by Maximum Complete Migrations).
-
As the number of Secondary servers increases, the specifications (CPU, RAM) of the Primary server may need to be reconsidered, as it acts as the "engine room" for the migration infrastructure.
-
The Primary server should typically remain dedicated to its primary service role. However, depending on the Primary server's specifications and if the total Secondary server count is low, it can be utilized as a Secondary service.
Managing Migrate Services via the CloudM Migrate Self-Hosted UI
The CloudM Migrate Self-Hosted UI includes a Migrate Services tab under Advanced. This provides a limited view and selection of controls from the Service Manager application.
From this tab, you can:
-
View all migration services (connected or disconnected).
-
See the number of tasks running on each service.
-
Connect to servers directly.
-
Download service logs or traces for investigation and troubleshooting.