File synchronization windows 20033/1/2023 No compression incurs more network traffic but is faster high compression incurs less network traffic but is slower. (This trend is becoming more widespread with the advent of Outlook 2003’s cached working mode, which makes centralized, consolidated Exchange data centers with outlying remote clients all the more attractive and effective.) You can explicitly choose whether to use compression, and if you do, you can choose the compression level. This is useful in many consolidation scenarios because servers distributed over the wide area network (WAN) are often being consolidated to centralized locations. The whole mailbox synchronization process uses compressed data files (which is another advantage over the default Microsoft tools) so that the actual transmission on the wire is kept to a minimum. On the target server, the MTA accepts the data, decompresses it, and transfers it to the destination mailboxes. The TA will send the appropriate PRV file directly to the required target server. If there are multiple target servers to receive data, then there will be multiple PRV files. The MSA then transfers the aggregate PRV file to the TA, also installed on the Exchange 5.5 server, which transfers mailbox information to the target Exchange 2000/2003 server. Each mailbox is queried for changes since the last synchronization, the changes are written to locally stored PST files for each mailbox and then compressed in a single file, known as the PRV file. ![]() ![]() You need one MSA per Exchange 5.5 server. The MSA resides on the source Exchange 5.5 server, which monitors the synchronization status of mailboxes. Agent Architecture for Mailbox Synchronization
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |