Migrate data from the old DOMINO server to the new server

Article Title: migrate data from old DOMINO servers to new servers. Linux is a technology channel of the IT lab in China. Includes basic categories such as desktop applications, Linux system management, kernel research, embedded systems, and open source.
The company's old LOTUS Server (Type: ibm pc Server, OS: Win2000 Server, Application: Lotus for NT R5.08, OA) wants to eliminate it and prepare a new Server. Now I want to export all the data in the old LOTUS server to the new server, but I don't want to change the configuration content of all the servers.
　　
What should I do? What else should we pay attention to during the migration process?
　　
★Method 1:
　　
The basic idea is: Install the same version of Domino server on the new machine, but do not configure it. Then, port the data directory And INI file from the old machine.
　　
1. First, obtain the installation media of the currently running Domino server. If the version of the original Domino server is earlier than the version of the installation medium of the existing Domino server, for example, the original running Domino server is R5.05, and the installation medium version of our Domino server is R5.07, then, we need to first upgrade the currently running Domino server from R5.05 to R5.07.
　　
Note: You should try to avoid moving the server before upgrading it, because only in this way can you identify whether the problem is caused by the upgrade in case of a problem.
　　
2. If the server is one of the many servers in the Notes network domain, you must first copy the Domino Directory (names. nsf) with other servers to ensure that the data is up-to-date.
　　
3. Copying and accessing the old server is prohibited. Replication and access from the Notes client can be stopped by disabling the Domino server.
　　
4. Make full backup for the old server.
　　
5. Install Domino on the new hardware server, but do not configure it.
　　
6. copy the data directory and notes. ini file from the old server to the new server to replace the data directory and notes. ini file generated when the new Domino is installed. (If third-party software is installed on the Domino server, you need to copy these dll files from the program directory separately, but the best way is to reinstall the third-party software .)
　　
7. if the path of the data directory on the new machine is different from the old one, you need to modify it in the notes. directory = row content in the ini file to define the location of the correct data directory on the new machine.
　　
8. Disconnect the old machine from the network.
　　
9. Modify DNS and set the IP address of the new server name (the name of the NT server does not need to be the same as that of the old server .)
　　
NOTE: If NetBIOS is used for name resolution, you need to clear the NetBIOS cache. Otherwise, other machines cannot find new machines.
　　
10. Start a new server and test whether the Notes and DNS work properly.
　　
11. Make full backup for the new server.
　　
12. If you need to reconnect to the old machine on the network, make sure that you have deprecated the Domino server installed earlier, so as not to conflict with the new server.
　　
13. Now, the Domino server can run normally on the new machine without affecting the original users.
　　
★Method 2:
　　
Dominant idea: create the same environment for the transplanted modules. This method is suitable for implementation after corresponding modules are developed. In the development process, you can use the user's environment without some settings and use them directly.
　　
1. backup the following file of the master server to be copied: cert. id, server. id, top5.dsk, and Cache. DSK, names. nsf and other required application databases (developed by developers); user is required for the imitation client. id and other required files.
　　
2. Install Domino. Do not prepare it for the moment. Copy the backup master server file to the data path of the newly installed domino and start configuring Domino:
　　
Step 1: select what the original server is;
Step 2: Select advanced;
Step 3: select the services of the original server. If the simulation requirements on the services of the original server are not high (unavailable), select http, imap, pop3, and smtp;
Step 4 (critical): Select "use existing validators", "Use existing Server identifiers", and "use existing administrator identifiers ", then, enter the required content, which must be the same as the corresponding settings of the master server. After you click Finish, you will be prompted to select a user id and enter the corresponding token secret. Run the following Domino. If no error message is displayed, the imitation server will be copied.
　　
3. Install the client (disable Domino during installation). Do not prepare it for the moment. Copy the backup file of the backup master client to the data directory of the newly installed domino. Start Domino and run the notes client configuration, which is exactly the same as the normal client configuration. (Do not forget to configure the hosts file if the connection fails ).