Scenario
We have a Traveler 8.5.3 Pilot Server running as a stand alone Server in the DMZ. (NAB not replicated for 4 years, User changes copy/pasted in).
We now want to replace this with a 9.0.1 production Server, but with the same identity.
The hope here is to keep the user/device disruption to a minimum if not to almost zero.
When moving domino to new hardware in the past we have :-
Built the new server and installed Domino with a temp id.
Replicated the mail files to the new server (not required for traveler)
copied the ID file and Certificates from old to new server
Shut down both servers
Edited Notes.ini on new server to be old server
Rename a few dbs (log, domlog etc)
Change Windows settings - name, IP etc
Restart new server and it comes up as old server.
The users don’t need to do any reconfiguring, they just have a slow mail system for an hour or so, while it works out what has happened.
Can this thinking also be applied to moving traveler between hardware and from 8.5.3 to 9.0.1.
An added complication - there are already other Traveler 9.0.1 servers in production for other departments (which we can not use), so we have to leave them intact as well.
The ultimate goal here is to have minimum disruption to the users, so just an hour or so while we switch the identity of the server and their device just picks up where it left off.
Has anyone had any experience of this and/or can offer advice if it is even possible ?
Thanks in advance for any help/ideas
Ian