Tag Archives: Exchange

Change SMTP Header Information

Every message that is sent (over the Internet) has header information. This header contains all kinds of information regarding the message, where it comes from, sent to, time, message identifier etc. All mail servers use this information to process the messages.

But when you take a closer look you’ll see information in the header of a message about your internal network. For example, I’ve sent a message from my Hub Transport Server, throught my Edge Transport Server to an external recipient and this is what I seen in the header information: Continue reading Change SMTP Header Information

LUN Design and Hardware VSS

This posting is written by Michel de Rooij, thanks for posting it here as well…

I had a question why you need to design seperate LUNs for Exchange database and log files when using a hardware based Volume Shadow Copy Service (VSS) backup solution, as mentioned in this TechNet article: Understanding Exchange 2010 LUN architecture

To deploy a LUN architecture that only uses a single LUN per database, you must have a database availability group (DAG) that has two or more copies, and not be using a hardware-based Volume Shadow Copy Service (VSS) solution.”

The reason for this requirement is that hardware VSS solutions operate at the hardware level, i.e. the complete LUN. Therefor, if you put the Exchange database and log files on a single LUN, it will always create a snapshot of the whole LUN. This restricts your recovery options, since you can by definition only restore that complete LUN, overwriting log files created after taking the snapshot. So, changes (log files) made after the snapshot are lost and you have no point-in-time recovery options.

For example, with the database and log files on a single LUN, suppose you create a full backup on Saturday 6:00. Then, disaster strikes on Monday. By definition, you can now only restore the database and log files as they were on Saturday 6:00; log files which were created after Saturday 6:00 are lost.

With the database and log files on separate LUNs, you can restore the database LUN, which leaves the LUN with the log files intact. Then, after restoring the database, you can start replaying log files.

So, keep this in mind when planning your Exchange LUNs in conjunction with the backup solution to be used. Note that the Mailbox Role Calculator supports this decision by letting you specify Hardware or Software VSS Backup/Restore as the Backup Methodology to be used.

If you’re interested in more background information on how VSS works, I suggest you check out this TechNet article: Volume Shadow Copy Service

Exchange Schema Versies

Every Exchange version comes with its own Active Directory Schema updates, even Cumulative Updates come with Schema updates these days. To determin the version of the Schema when it comes to Exchange you can verify the rangeUpper property of the ms-Exch-Schema-Version-Pt object in the Schema Partition as shown in the following figure (for Exchange 2013 CU8).

image

You can also use the following PowerShell commands to retrieve the Schema version:

$root = [ADSI]"LDAP://RootDSE"
$m = [ADSI]("LDAP://" + "CN=ms-Exch-Schema-Version-Pt," + $root.schemaNamingContext)
$m.rangeUpper

image

The following table lists all (or most) Schema versions of Exchange Server:

Exchange version Schema version
Exchange 2007 RTM 10637
Exchange 2007 SP1 1116
Exchange 2007 SP2 14622
Exchange 2007 SP3 14625
Exchange 2010 RTM 14622
Exchange 2010 SP1 14726
Exchange 2010 SP2 14732
Exchange 2010 SP3 14734
Exchange 2013 RTM 15137
Exchange 2013 CU1 15254
Exchange 2013 CU2 15281
Exchange 2013 CU3 15283
Exchange 2013 SP1 15292
Exchange 2013 CU5 15300
Exchange 2013 CU6 15303
Exchange 2013 CU7 15312
Exchange 2013 CU8 15312
Exchange 2013 CU9 15312

Page last modified: June 17, 2015