|
You must be aware of
the following issues:
Security - EXMERGE
does not password-protect the .PST files
it creates. For security reasons, you’ll
want to create the .PST files on a
secure file system, such as NTFS.
Storage Space -
You need to consider how much space is
required to store the .PST files and
with what frequency you will have to
purge the archived .PST files. You might
want to add some archiving features to
your script, such as zipping all the
.PST files after exporting them.
Overwriting .PST
files - If there is no corresponding
.PST file for the mailbox in the export
folder, EXMERGE will create a new .PST
file for the mailbox. The .PST file
naming convention is <alias>.PST. If a
.PST file for the mailbox already exists
in the export folder, EXMERGE will
export only new message data from the
mailbox to the .PST file. Therefore, you
may want to purge the .PST files or move
them to another directory so that
EXMERGE will create new .PST files when
it runs next time.
Single Instance Architecture -
When EXMERGE exports mailbox data to a
.PST file, you lose the benefit of the
Single-Instance message storage
capability, so don’t be surprised if a
mailbox’s newly created .PST file is 10
to 50 percent larger than the mailbox
itself.
Restoring
the mailboxes
You have several
options when you need to restore mail
from a mailbox’s .PST file. You can run
EXMERGE in normal mode and select the
.PST data by a range of dates or other
criteria and restore them directly to
any production mailbox.
Or you can copy the
.PST file to the user’s local disk or
make it available on a network share.
Then, instruct the user to add Personal
Folders to their Outlook Profile and add
the .PST file when they do so. The user
can then browse through the .PST file’s
contents and retrieve the messages they
are looking for. |
