Approved: Fortect
Over the past few days, some users have reported that they have discovered an Exchange 2010 Online Serving Event ID.
Exchange has an online maintenance task that runs every night. The Exchange admin center (EMC) displays. Go to Organization Setup> Mailbox> Database Management. Right click> our database> properties> maintenance tab. Can we then see my complete maintenance schedule?
As you can see, Exchange 2010 has a new setting that is unfortunately enabled by default. This option is “Enable background database maintenance (ESE 24×7 scan)”. It might not be online defragmentation, but database checksums. More on this later …
Online maintenance performs various tasks such as online defragmentation (OLD). Microsoft explains to OLD: “Online defragmentation is free for the first few pages of the database by simply compressing criminal records to the smallest number of pages, making I / O critical. Database enginex ESE does this by simply using the database metadata, which is our own database information describing the workstations in the database, and for each cube call to each table page as an attempt to logically write records to move the page of records. â €
There is also a process called the operational maintenance database checksum. The checksum checks the ethics of the database by finding every page in the database since there was no service contract. OLD will successfully scan every page on the World Wide Web to ensure there is no damage. This process is completely consistent and does not cause problems with database performance. The problem with this method in Exchange 2008 RTM is that this process was running at the end of online maintenance, and this made the way it makes them suspend continuous replication temporarily fault tolerant. In Exchange 2007 Service Pack 1 (SP1), Microsoft provided the Critical Factors registry so you can runRemove checksums in the background.
In releases of Exchange prior to Exchange 2010, we can track the 70 event IDs available in the ALT Event Viewer log. Similarly, you can check the number of spaces used in the file. They are all created in the event ID 1221 database. The list of event IDs for Exchange solutions prior to Exchange 2010 is as follows:
- 700 Start
- 701 – Completed
- 702 – Continue
- 703 – Continue Pass Completed
- 704 – Discontinued and done
- 1221 – number of spaces
This has changed slightly in Exchange 2010. OLD2 must be a new version of Online Defragmentation and therefore no longer runs at the end of the Online Maintenance Plan. Instead, X becomes 24. run 7 in the database. It is simply limited so as not to affect performance. OLD2 cannot be changed – works like OLD in previous Exchange projects. OLD2 is not configurable. For this reason, it is no longer necessary to troll each of our event IDs listed above. Instead of looking for 70 event exchange IDs, this yearyou will only be notified when there is something wrong with the line service. This way, none of the 70x error codes will show up as spam. If you see your 70x in Exchange 2010 then there is a problem. Note, however, that this again has to do with mailbox databases. Queue databases are always 70x event IDs.
If you need to check for spaces, you can do so now through the new Exchange Management Shell (EMS). Note that this will only free up space available in the root directory of the B-Tree database. If you want to find free space to search for a database, you need to completely shut down the databases and use eseutil. If your database is named Database1, the following is required:
Note. Switching status is required if you need to contact the directory directly to reduce the following information:
- BackupInProgress
- Online
- OnlineMain maintenanceInProgress
- Available storage space at database root
As mentioned earlier, OLD2 is limited and does not negatively impactand performance. If you want to monitor OLD2 performance, you can do so using the perfmon kiosk below: MSExchange Database -> Defrag Tasks.
Approved: Fortect
Fortect is the world's most popular and effective PC repair tool. It is trusted by millions of people to keep their systems running fast, smooth, and error-free. With its simple user interface and powerful scanning engine, Fortect quickly finds and fixes a broad range of Windows problems - from system instability and security issues to memory management and performance bottlenecks.
In Exchange 2010, there are two ways to easily set up online database scans (checksums). The first is the default, which is usually shown in the first image of this article, a 24×5 process for an active database. You have the option to disable this option. This option then returns a scan of the online database so that it changes after all online maintenance tasks have been completed. Since most online maintenance tasks are completed within an hour, this process works well enough for searching small databases (less than 500 GB). Microsoft currently supports up to 2 TB of databases. If this is not the case for this tool, Exchange 2010 does not display the correct evening alert in the event logs.
Thanks to Matt Gosseige, Program For Storage Manager, for visiting Microsoft for many of these answers. You can watch Matt’s Gossage Level 350 webcast about Exchange 2010 storage here.
Speed up your computer's performance now with this simple download.
