We have been running a replicated database for several years now, and have
outgrown the server.
Our current setup has several remote laptops syncing to the hub database
on
server Server A via the internet. Repman on Server A does direct hourly
syncs of "hub" to a managed replica "replica2" on Server B. It also does
a
nightly direct sync to the Design Master (which happens to sit on Server
A).
Our goal is to add a new server (Server A1) and remove Server A from
service.
Our plan is to do the following:
1) Shut down network access (to prevent laptops from syncing during the
transition)
2) On ServerA, use Repman to unmanage Hub.
3) On Server A, do a direct sync between Hub and Replica2 (on Server B).
This provides a backup.
4) On Server A, do a Move Replica to move Hub to the new server (Server
A1).
5) Take Server offline
6) Change Server A1 will have the same computer name and IP address and
the
old server.
7) On Server A1, use Repman to manage the moved Hub.
8) On Server A1, create a new DM from Hub.
9) On Server A1, force a direct sync with Replica2 on Server B
10) Open the network back up.
Any problems with this procedure?
Thanks in advance,
Don
|
