SERVICE PROVIDER
Moving a hosted organization that has a unique IP address varies somewhat from moving a hosted organization that has a shared IP address.
Moving a hosted organization that has a unique IP address
To move a hosted organization that has a unique IP address, complete these procedures:
1. Re-create the hosted organization infrastructure on the destination server.
2. Open the registration policy settings document for the hosted organization that you are moving and change the original mail server name to the name of the destination server -- that is, the new mail server.
3. Use the Domino Administrator to move databases and move users that have mail files from the source server to the destination server.
4. Prohibit access to the source server.
5. Move non-database files from the source to the destination server.
6. Enable access to the destination server.
7. From the source server, remove the infrastructure for the relocated hosted organization.
Moving a hosted organization that has a shared IP address
To move a hosted organization that shares an IP address with other hosted organizations, you must change the IP address of the hosted organization that you are moving. In addition, you must modify the server information in the documents, as well as the DNS entries for the hosted organization you are moving. DNS entries are often cached and may require a substantial amount of time to process a change.
Complete these procedures:
1. Prohibit access to the source server.
2. Enter the destination server name in the "Domino servers that host this site" field in all of the Site documents for the hosted organization.
3. Create a hosted organization infrastructure on the destination server.
4. Open the registration policy settings document and change the original mail server name to the name of the destination server -- that is, the new mail server.
5. For users who have mail files, use the Domino Administrator to move the users from the source server to the destination server.
6. Move nondatabase files from the source server to the destination server.
7. Enable access to the destination server.
8. Remove the infrastructure from the source server.
To create the hosted organization's infrastructure on the destination server
1. On the destination server, do one of these:
3. Copy the hosted organization's ACL file from the source server's data directory to the destination server's data directory.
4. If any Web application requires a "per hosted organization infrastructure," create that infrastructure.
To edit the hosted organization's registration policy settings document
1. From the IBM® Lotus® Domino™ Administrator, open the Domino Directory.
2. Choose Policies - Settings.
3. Select the registration policy settings document you want to edit.
4. Click Edit Settings.
5. On the Mail tab, choose the name of the destination mail server from the list displayed in the "Choose the mail server" field.
6. Click Save and Close.
To move the mail file and other databases
Caution During this procedure, do not approve the mail file deletion in the Administration Requests database (ADMIN4.NSF) If you approve the deletion too soon, the user will not have access to the mail file on the source server. Approve the mail file deletion later, when doing so will not impact user access to the mail file.
1. Make sure that you and the source server have Create Replica access to the destination server.
2. From the Domino Administrator, click People & Groups.
3. Select the person whose mail file you are moving.
4. From the Tools panel, click People - Move.
5. Enter the destination mail server name in the Destination field. Include the hosted organization subdirectory.
6. Select the server and paths on which you want to create mail files. Replicas will be created at the location you select.
7. Click OK.
For more information on moving user mail files, see the topic Moving a user's mail file and roaming files.
To enable access to the destination server
1. Associate the hosted organization's IP address with the destination server according to your particular setup. You may need to update host files, DNS server settings, and the IP address assigned to the TCP/IP stack.
2. You may need to stop and restart the server depending on your TCP/IP stack. Whether or not you can modify the IP addresses that are served without restarting the server depends on your individual configuration.
To prevent access to the source server
Complete this procedure after you have successfully initiated as many "Move mail file" actions as necessary. This procedure applies only to moving a hosted organization that has a unique IP address.
1. Shut down the Domino server on the source server.
2. Disassociate the hosted organization's IP address from the source server. You may need to modify host files or DNS server settings, as well as the IP address assigned to the TCP/IP stack.
To move non-database files from the source server to the destination server
1. Copy all database files from the source server to the destination server.
2. From the source server, recursively delete the non-database files that you copied to the destination server.
3. Copy all non-database files in directories that are not within the hosted organization's data directory. Copy the files from the source server to the destination server.
4. Determine whether any Web application requires per-hosted-organization data that has not already been copied. Copy that data to the destination server, and then delete it from the source server.
5. (Optional) Replicate the data from the source server to the destination server to ensure that all changes made to the source server appear on the destination server.
6. Change the IP addresses hosted by the destination server to include the new addresses -- that is, those formerly hosted by the source server. Modify all Internet Site documents as necessary.
7. Restart the Domino server on the destination server.
For more information on the Site documents, see the topics Creating an Internet Site document and Hosting Web sites.
To remove the infrastructure from the source server
1. Open the Administration Requests database (ADMIN4.NSF) and approve the requests to delete the source databases. When all requests have been successfully processed -- that is, when the databases have been deleted -- proceed to the Step 2.
2. Delete the hosted organization's subdirectory from the source server.
3. Delete any directories that are specific to the hosted organization and that reside outside of the hosted organization's data directory.
4. Delete the hosted organization's ACL file from the data directory on the source server.
For more information on approving administration requests, see the topic Approving an administration process request.
2. Disassociate the hosted organization's DNS names from the source server's IP address. Associate those DNS names with the destination server's IP address.
3. If SSL was used for encryption, do not copy the old key ring file to the destination server. Use the destination server's key ring file.
4. Open each Internet Site document to modify the IP address for the hosted organization on the destination server. Make sure that Web site names are correct.
See also