Exchange uses swap as "backing store". I'm not going to explain that, look it up.
Swap on an Exchange Server needs to be configured to a MINIMUM of (memory + 15 MB) and a maximum of (memory * 1.5 + 15 MB). I recommend that, for performance reasons, you set that to be a fixed size. This should be part of your normal server build setup. From: [email protected] [mailto:[email protected]] On Behalf Of xyz Sent: Tuesday, January 7, 2014 6:53 PM To: [email protected] Subject: [Exchange] ID error 7000 Greetings, Exchange 2010 SP2 RU3 Two node DAG (each is HP G7 2x 6 core 48 GIG RAM) 1500 Mailboxes split into two DBs. DAG has been in place for 3.5 years, very stable, and major issues other than the ordinary "stuff happens" Serverdag1 replication failed showing in EMC MAILBOX COPY STATUS of ServiceDown (instead of MOUNTED) (I have never had this one before). Serverdag2 took over and MOUNTED both MD DBs - so we stayed up. We see event: Time: 1/6/2014 7:00:49 AM ID: 7000 Level: Error Source: Service Control Manager Machine: serverdag1 Message: The Microsoft Exchange Replication service failed to start due to the following error: The paging file is too small for this operation to complete. Restarting The Microsoft Exchange Replication service got the DB copies back in sync. Serverdag1 has 48 GIG RAM and a 8840 paging file. Both DAGS have 48 GIG physical, and my thought is that exchange will use whatever hardware RAM even if some more is added ( Resource Manager shows the RAM is just about all in use). MS is suggesting we focus on increasing the paging file - possibly to the match the RAM of 48 GIG. Again, this design has worked well for 3.5 years and so I am wondering if this may just be an anomaly. The only changes we make are the monthly ms updates. Thanks for any tips while I keep looking into this. Dana
