Norman P. B. Joseph wrote:
> Is there a general/common methodology for such a migration? Is there any
> benefit (apart from service outage issues) to migrating them one-at-a-time
> verses all-at-once? Sync-site-first or sync-site-last?
The common methodology attempts to minimize service outages.
*Apart from service outages*, your best bet would be to migrate them all
at once. It sounds like your new servers won't be able to communicate
with your existing servers, if I understand your comments about not
being able to route between Ethernet and ATM. In which case, you don't
really have any choice.
Someone suggested adding new servers before updating client-side
CellServDBs. Alternatively, you can update the client-side CellServDBs
first. If can tolerate a service outage, the following scheme might
work for you. It's probably easier to understand.
(1) update client-side CellServDBs to include both old and new database
servers.
(2) reboot or run "fs newcell" on all the clients
(3) shutdown, move, and restart servers
(4) update client-side CellServDBs to remove references to old servers
(5) run "fs newcell" on the clients, or wait for them to be rebooted
eventually.
The outage is limited to #3. How long do you think that period will
last? Depends on how far your new location is from your old and how
certain you are that the machines will not fail when they're
power-cycled, that the network drops and power are functional in the new
location, etc.
