You can migrate the CommServe in a Windows environment to Linux.
Scenario 1: Migrating Standalone Windows CS using CS Hardware Refresh
You can migrate a standalone Windows CommServe using the CommServe hardware refresh method with DR backup dumps.
For instructions, see Setting Up the CommServe Database in the New Hardware.
Scenario 2: Migrating Standalone Windows CommServe Using CommServe LiveSync
You can migrate a standalone Windows CommServe using the CommServe LiveSync feature.
-
Install CSLiveSync on Existing Windows CS. This will become the Active CS.
For instructions, see Installing the CommServe Failover Package on the Production CommServe Host.
-
Install Passive CS on a Linux machine.
For instructions, see Installing the Standby CommServe Host on Linux.
-
Create a plan for CSLiveSync using a non-dedup storage.
-
Enable CommServe LiveSync.
For instructions, see Enabling or Disabling CommServe LiveSync.
-
Monitor CSLiveSync SQL Backup replication cycle.
-
Optional. Verify disaster readiness by performing a test failover and a test failback on the linux passive CS node.
For instructions, see Verifying Disaster Readiness Using Test Failover.
-
Perform a production failover to passive CS (Linux machine).
For instructions, see Planned Failovers in Linux Environment.
-
Once Linux CS is active, CSLiveSync will continue replicating database transaction logs to Windows CS.
-
If you do not intend to use CommServe LiveSync, do the following:
-
Disable CSLiveSync.
For instructions, see Enabling or Disabling CommServe LiveSync.
-
From the Command Center, retire Instance002 client of Active CS (Linux node) and Instance002 client of Passive CS (Windows node).
-
Verify that all clients and MediaAgents are reachable to Linux CS.
-
Decommission the Windows machines.
-
Scenario 3: Migrating CommServe Server in a CS LiveSync Windows Environment to Linux
You can migrate the CommServe Server in a CS LiveSync Windows Environment to Linux.
-
Install 2 Linux Passive CS machines pointing to Active Windows CS. One machine will act as Active CS and the other as Passive CS after Windows machines are removed.
For instructions, see Installing the Standby CommServe Host on Linux.
-
Verify that the clients and replication schedule for the newly installed Passive CS nodes are configured properly.
For more information, see Verifying the Default Setup (Linux).
-
Optional. Verify disaster readiness by performing a test failover and a test failback to Linux passive CS node.
For instructions, see Verifying Disaster Readiness Using Test Failover.
-
Perform a production failover to Linux node.
For instructions, see Planned Failovers in Linux Environment.
-
Verify that the Commserve setup is working properly.
-
From the Command Center, retire Instance002 client of Windows CS and its associated entries.
-
Decommission the Windows CS machines.