Gordano Messaging Suite Load Sharing Utility
---------------------------

Introduction
------------
Most customers who wish to use SMTP load sharing will already have
Gordano Messaging Suite on a server which they wish to split among two or
more servers.

Any customer using this utility should be aware that it will delete
users and files from their system. They should take a full backup of
their server before performing the load sharing split. No recovery
options are provided. If all servers to be used in the array are
clean, i.e. do not have users existing under the Gordano Messaging Suite installation,
load sharing may be setup from the Load Sharing page of the GUI.

The conversion utility is part of the mail.exe program already shipped
with Gordano Messaging Suite. A new command argument -loadshare is provided.
It will take no additional options. The domain to be split will be
specified by the -domain option. The -verbose option will turn on
verbose mode. A minimum command line would be
	mail -domain domain.dom -loadshare
	
+ Only one domain may be split amongst servers. A separate licence is
  required for each server in the load sharing array.
+ Machines other than the original server are assumed to be blank but
  with a full Gordano Messaging Suite key. Thus a setup.txt can be loaded
  onto them using the existing mechanism.
+ Users in virtual domains based on the source domain will remain on
  the source machine.
+ Administrative users will not be moved.
+ All services must be stopped before running this conversion program.

If the primary server is not listed in the rules file then a default
rule with a "*" in it for the primary server will be added to the
start of all rules files.

The program will prompt for the following additional information:
+ The name of the rules file. This file should contain rules (in
  order) for all machines in the load sharing array including the
  source machine.
+ The name of the source machine as identified in the rules file.
+ Confirmation as to whether this is a dry run or the real conversion.
  The default will be to do a dry run only.
+ The program will give a big warning prompt before doing a real 
  conversion. The default will be not to continue.

The output of the program will be the following:
1. A full setup.txt for each destination machine. This setup.txt will 
   contain a zip file which must be restored. No keys will be dumped
   in the setup.txt so that the keys on the destination machine will
   always be preserved even if they are a demo key.
2. The zip file in the setup.txt for each destination machine will 
   contain all the files from the base directory of the source machine
   (i.e. global filters etc will be transferred). The contents of the
   MML directory will also be transferred. It will also contain all
   the files from the domain directory - all mailboxes, plans etc.
   will be transferred.
3. An SMPTServers.txt file will be produced for each machine. This
   will be contained in the zip file.
4. The source machine will be deemed the primary server and the
   postmaster account will be left on it. A postmaster account will be
   created on all target machines with administrator rights.
5. Any users being transferred to another machine will be deleted from 
   the destination machine.
6. A postmaster user will be created on each destination machine with 
   full access rights.
7. A report of any warning or errors encountered will be produced.
   This report will give the total number of users on each machine.
In a dry run situation step 5 will be ignored.

In addition to the above the following will need to be done on the
source machine:
1. Setup load sharing as the primary machine

In addition to the above the following will need to be done on the
destination machines:
1. Setup load sharing as a secondary machine
2. Add a postmaster account with administrator rights
3. Update user access list with postmaster

Step By Step Guide to Setting Up Load Sharing
---------------------------------------------
The following steps should be taken to perform a load sharing
conversion for the domain "domain.dom":

1.  Decide how the domains should be split. In this example we shall 
    split over three machines "main", "server1", "server2". 
2.  Decide which users will be on which on which machines e.g. initial 
    letter "a" to "j" on "main" etc.
3.  Install a fresh copy of Gordano Messaging Suite on "server1" and "server2" and
    apply keys - note all keys must be different.  If they have an
    installation on the machines already then it will be lost.
4.  On each machine make sure that the machines "main.domain.dom", 
    "server1.domain.dom" and "server2.domain.dom" can be resolved from
    Gordano Messaging Suite. You may need to reconfigure your DNS server or Hosts file
    to do this.
5.  On the source machine "main" create a file in the Gordano Messaging Suite base 
    directory called "ls.txt". Edit this file and add the following
    lines:

    [a-j]* main.domain.dom
    [0-9]* main.domain.dom
    [k-p]* server1.domain.dom
    [q-z]* server2.domain.dom

    The above rules should cover all eventualities, if not you may
    need to add more. See the on-line help for definitions of the
    wildcard matching rules.
6.  Start a DOS command prompt.
7.  Run the Gordano Messaging Suite "mail" program to create a setup.txt for your
    machine. This is needed in case anything goes wrong. The command
    should be "mail -yA".
8.  Run the Gordano Messaging Suite "mail" program to create the load sharing array.
    Run the command "mail -domain domain.dom -loadshare".
9.  You will be prompted for the name of the file containing the load
    sharing rules. This is "ls.txt".
10. You will be prompted for the name of the source server in these 
    rules. This is "main.domain.dom".
11. You will now see a warning screen. We will perform a dry run 
    initially to check all is well. Just hit Return.
12. The domain conversion program now takes place. Any errors or 
    warnings that will occur in the full conversion will be shown. You
    can either deal with these now or after the conversion. If a user
    with now matching rule is found then you should return to step 5
    and add additional rules.
13. You will now see the file ls.out in the base directory, this file
    contains the output of the mail program for later reference.
14. Now run the conversion program again. Follow steps 9 and 10 again.
    This time at the warning screen enter "YES".
15. Another warning screen is shown. Enter "YES" again.
16. The domain conversion will now take place for real. 
17. Two files will be created in the Gordano Messaging Suite base directory named
    server1.domain.dom.txt and server2.domain.dom.txt. Copy
    "server1.domain.dom.txt" to server1 and "server2.domain.dom.txt"
    to server2.
18. On server1 and server2 load these files using the mail.exe
    program. The command is "mail -yRZ<filename>".
19. Log onto each of main, server1 and server2 via a web browser. You
    may need to perform the following corrections:
    + Modify the local domain names to remove the "*.domain.dom"
      entry.
    + Modify the IP Address of domain.dom on server1 and server2 to
      use the correct value.
20. Ensure that the MX records for "domain.dom" point to
    "main.domain.dom", ", "server1.domain.dom" and
    "server2.domain.dom".
21. The domain conversion is now complete. You may wish to modify some
    of the settings in the "Load Sharing" tab. All users mail has been
    transferred.
