Archiving mailbox information has a greater impact on system performance than archiving prompts or applications.
This impact depends on
the server platform (amount of available memory)
the number of mailboxes and their usage of resources, including
number and lengths of stored voice messages
number and lengths of recorded personal greetings and the personal verification
number and lengths of personal distribution lists (PDLs)
whether the archive destination is a local tape drive or a remote disk drive because archiving to a remote drive is also impacted by server performance and network traffic
System performance is slow during high traffic periods. Suspending scheduled user archives returns the system to normal performance levels.
It is not possible to run a complete user archive during an available period of light system traffic.
There are several solutions to this problem.
Define a set of user archives and run them separately. This is a good solution if
running a user archive is the only negative impact on system performance
you can predict several periods of light traffic
during the day
For information, refer to
Reduce resource usage by mailbox owners.
For information, refer to
Re-allocate channels to services
For information, refer to
If archiving your mailbox information impacts system performance, run a test to determine how many mailboxes you can archive during times of light system traffic.
The object of the test is to determine how many mailboxes you can archive during predictable periods of light system traffic.
If the following example is not typical of your system, adjust the test to make it meaningful in helping you decide how to schedule your user archives. For information about your system, refer to
|
Platform: |
1002 rp with 512MBytes of memory under a load test |
|
Number of mailboxes: |
1000, where each has
|
|
Remote computer: |
Pentium III 450 Hz and 128 MBytes of memory running winnt 2.0 |
|
Network link: |
100mbit |
In this example
Archiving to a local tape takes 30 minutes.
Archiving to the remote hard drive takes 35 minutes.
This duration may vary greatly depending on the remote
PC's performance level and the network traffic.