Troubleshooting
Problem
Simple steps to switch Replication Mode, when upgrading to 3.1, and maintain the replicated data that already exists on a HUB system
Symptom
Running ProtecTIER 3.x or Higher with new Replication Functionality
Cause
The user guide does have each of these steps but not in one simple flow called "converting" and since users coming from 2.5 or lower will not have experience with 3.1 terms, this technote is to introduce the new function in an existing environment.
Environment
Upgrade from 2.4 or 2.5 ProtecTIER to 3.x or higher, with Replication existing
Diagnosing The Problem
N/A
Resolving The Problem
The High Level Flow is:
1.) Modify the Application Group, and remove the repositories from the Many to One group
2.) Verify your Repositories are "Stand Alone"
3.) Create a new group, choosing Many 2 Many.
Detailed:
Existing Many to One (2 node group)

1.) Right Click one of the repositories and choose "Replication group management"

2.) IN the wizard:

Uncheck the repositories you want to move to a new group (these are spokes)

You should not be replicating during this change, but, it will abort them if you are, which is ok.
BUT, do not do this if the repository or system is 'DOWN' of off line. You need to make sure all your spokes and your hub are "reachable" (not Dark Grey)
then, you get this:

3.) Create a new GROUP.

Choose Many to Many:

Select your repositories

Name the group:

After you click finish, your repositories will work like Many 2 Many, AND, the replicated carts will remain intact, and not have to be re-replicated.
However, you WILL have to modify your policies, since many to many policies are different from Many to One.
This should be ok, as you can configure the previous policies the same, only instead, choose the repository that used to be the HUB.
Note, IF you plan to make lots of changes in your replication scheme, it may be a good idea to first migrate to this, state, then phase your changes and copies in, as you need them.
Was this topic helpful?
Document Information
Modified date:
16 February 2022
UID
ssg1S1003932