Jump to: navigation, search
MithiWiki Home > ConnectXf Home > ConnectXf Administration > Configuration > Hw upgrade single server


HowTo Icon.png
How To
Product ConnectXf
Version All
Applies to Administrators
Level Advanced


Hardware upgrade: Moving MCS to a New Hardware

Situation

  1. A central site has a mail server which needs to be shifted onto new hardware

Prerequisites

  1. New hardware of same or better specifications
  2. Hardware installed and connected to the network
  3. Fresh IP assigned to the new server
  4. New Temporary IP available for the old server
  5. OS and MCS cds of the same version.

Installing OS and MCS on new hardware

Step Location Command
Install OS and MCS on new hardware as per requirement/hardware support New Server OS Installation
Note: Ensure that you install the same version as is present on the current live server New Server Connect XF Installation

One day before shifting

The downtime required will depend on the mailstore size. Minimum downtime will be an hour.

Step Location Command
Make a list of all the domains on the servers Old server
Start the maintainance mode Old Server
Take a backup of the domain-system data Old Server Taking a Backup
Make a note of the number of LDAP and database entries Old Server How do I count the number of entries in the LDAP server
Take a backup of the mailstore and mcsdata backup Old Server Taking a Backup
Inform customer about the possibility of duplicate mails Old Server IMPORTANT: Please click here to know about mail duplication when moving hardware/changing IP etc
Restore mcs backup New Server Restoring a Backup
Generate log report for data restore New Server
Check and confirm ldap entries are same on old and new server New Server How do I count the number of entries in the LDAP server
Test the login and mailing on local server New Server
By telnet New Server
By webmail New Server
Copy mail store New Server Copying the mailstore to another server using RSYNC
Audit the server New Server Audits

Switching to new Server

The downtime required will depend on the mailstore size. Minimum downtime will be an hour.

Step Location Command
Stop SMTP, POP and IMAP services Old Server SMTP, POP, IMAP
Alarm/Flush the mail queue Old Server Queue
Stop the remaining services Old Server Look up the Server Control section in Server Properties
Change IP to temporary IP Old server Assign temporary IP to the old server
Remove live IP Old Server Disconnect the live IP
Assign Live IP New Server If you are assigning new IP instead of Old server's IP make sure you will run "/mithi/mcs/bin/changenetworkip.sh " e.g Live/old server has IP 10.95.7.249 new server has IP 10.95.7.252 after run the command /mithi/mcs/bin/changenetworkip.sh 10.95.7.249 10.95.7.252
Restart the server New server reboot
Start SMTP, POP amd IMAP services New Server SMTP, POP, IMAP
Test services and local mailing New Server Administration:Testing
Test full mailing New Server Administration:Testing
Stop the maintenance mode New Server
Configure final rsync for mail store New Server Copying the mailstore to another server using RSYNC