OSI/MHS Configuration and Management Manual

Planning Your OSI/MHS Subsystem
OSI/MHS Configuration and Management Manual—424827-003
3-16
MS Groups
•
What pattern of message flow do you expect? How do you want to set up your
store cleaner? (How often should it run?)
MS Groups
You can determine the number of message stores you need by the number of users
you anticipate. Each message store can support up to 1000 users.
Each MS group has its own PDU store database and SQL database. When you add
MS groups, you also add these databases.
When planning MS groups, consider the following:
•
How many MS groups do you need? You can increase the number of users by
adding MS groups.
•
How many individual MS mailboxes do you need? You will need one for each UA,
so you must consider the total number of UAs for each MTA.
RS Groups
When planning RS groups, consider the following:
•
How many RS groups do you need? Consider the type of network you have and
how many associations that network can supply.
•
How many remote UAs do you anticipate?
•
Do you have MS groups on your OSI/MHS subsystem? If so, you must have at
least one RS group.
How Can You Apply the NonStop
Fundamentals to Your OSI/MHS Subsystem?
The NonStop fundamentals include linear expandability, high performance, fault
tolerance, data integrity, and manageability. This section describes how you implement
these capabilities in your OSI/MHS subsystem.
Linear Expandability
As the number of users of your network grows or as message traffic increases, you
can expand your OSI/MHS subsystem by adding more GI, LO, MR, MS, and RS
groups.
Each MR group has the capacity to be a complete message transfer system, and you
can distribute MR groups across several processors. As you add processors to your
system, you can configure more groups across the CPUs to increase the processing
power available to your OSI/MHS subsystem.