Native Exchange 2013 Journaling - Guidance over Storage Planning!

Hi,
We are currently exploring full envelope journaling service using Exchange 2013 with Sharepoint 2013 eDiscovery suite for ALL internal and external messages for a largish enterprise ~40K mailboxes and need to accurately plan storage for the dedicated Journal
servers; we have used the standard messagestats powershell script to get send / receive and average message size and have some valid metrics to utilize however there is next to no actual guidance on how to plan storage for journaling published?
My question concerns which metric to use - unique send and receive OR total send / receive figures; I have reached out to some of my default Microsoft contacts and dug into how FE Journaling works under the hood and my understanding is that it is total send
/ receive for every message would be more valid to plan against?
Any guidance would be great!

Hi,
Do you mean you want to plan storage for journaling in Exchange 2013?
The storage will keep increasing as long as the new conversation is recorded. Targeting only the specific recipients can minimizes storage which is based on your requirements.
Here is an article about journaling in Exchange 2013 for your reference.
http://technet.microsoft.com/en-GB/library/aa998649(v=exchg.150).aspx
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Similar Messages

Exchange 2013 Journaling Best practices

I am using native Exchange 2013 Journaling for journal all external messages for all users. The size of journal mailbox is very huge. I am looking for best practices for journaling
in terms of journal mailbox size? Journal database size? Do I need to create multiple journal mailboxes? Do I enable achieving for journal mailbox? If archiving enabled, then what is max size for archive mailbox? I do not want to export mails to PSTs.
Appreciate help from others

Hi,
Do you mean the size limit for .pst file?
By default, in Outlook 2010 and Outlook 2013, the overall size of .pst file has a preconfigured limit of 50GB. In Outlook 2003 and Outlook 2007, the default .pst file size limit is 20 GB. If the file size is greater than the default size limit, you will
be unable to open the .pst file. However, we can modify this value by making changes to the Windows registry.
Here is a related article for your reference.
The file size limits of .pst and .ost files are larger in Outlook 2010 and Outlook 2013
http://support.microsoft.com/kb/982577
About the user mailbox size limit, there are no inherent size limits, you can set the size limit to unlimited if you want. But you need to take many factors into consideration as mentioned above.
Best regards,
Belinda
Belinda Ma
TechNet Community Support

Exchange 2013 journaling and JBOD

Is anyone using JBOD on exchange journaling servers? If yes, how is that working out for you?

Hi mombu,
Microsoft does not support Exchange server deployed on JBOD storage architecture without DAG. JBOD have two main advantages: full space utilization and cost effective. However, if you lose a single disk in the JBOD then there is a high likelihood that you
will lose data, as the concept of a JBOD does not include not fault tolerance.
So it is important to point out at this stage that JBODs should not be considered if you do not plan to use DAG.
More details about Exchange 2013 storage configuration and
high availability, for your reference:
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
http://technet.microsoft.com/en-us/library/dn789066(v=exchg.150).aspx
Best Regards,
Allen Wang

Exchange 2013 Journalling help Required..

Hi All,
please help me to resolve these concerns for one of my customer..
(1) I am going to enable journalling for my all users. i will have retention period of one year and after one year i have to delete all mail items from journal mailbox. is there any cmdlet that can delete all mail items without login and configuring outlook
for journalling mailbox and deleting mail items manually?
(2) i don't want Delivery receipt and read receipt to deliver into my journalling mailbox. is there any way i can restrict such mails from delivering into journal mailbox? also i have noticed that if i Enable Database Level Journalling i receive a lot of
mails delivered to Health Mailbox..is there any way to restrict to deliver these Health/monitoring mails to journal mailbox??
(3) How can i search Mails TO/FROM a particular user via e-discovery of i have enabled Database level Journalling??
thanks,
Aanand Singh
Regards, Aanand Singh

Hello,
For your first issue, you can use search-mailbox cmdlet to do it. Here is an article for your reference.
http://technet.microsoft.com/en-us/library/dd298173(v=exchg.150).aspx
For your second issue, I recommend you use transport rule to do it.
For your third issue, if you want to check messages TO/FROM a particular user, I recommend you search these messages in jourmal mailbox.
If I have any misunderstanding, please free let me know.
Cara Chen
TechNet Community Support

DAG with Exchange 2010 & Exchange 2013

Hello,
I'd like to implement DAG in the system, but I was wondering if it is possible to use DAG in Exchange 2010 and 2013 environment?
Estimated amount of servers:
Exchange 2010 Standard
Exchange 2013 Enterprise
Exchange 2013 Enterprise
What I'm planning to do is moving all the mailboxes, public folders from Exchange 2010 Standard to Exchange 2013 Enterprise, then start using DAG and make Exchange 2010 as a member of DAG. Is it possible?
Thank you in advance.

Hello,
You cannot mix Exchange 2010 and 2013 versions in the same DAG. In your situation you need
to create Exchange 2013 DAG and migrate all resources (mailboxes, public folders, mailflow settings etc). When finished, you will be able to decommission old server.
Hope it helps,
Adam
CodeTwo: Software solutions for Exchange and Office 365
If this post helps resolve your issue, please click the "Mark as Answer" or "Helpful" button at the top of this message. By marking a post as Answered, or Helpful you help others find the answer faster.

#550 4.4.7 QUEUE.Expired; message expired ## With LastError "A storage transient failure has occurred during content conversion." In submission Queue. (Exchange 2013)

Greetings,
We seem to be having a problem with some users who are attempting to send e-mails from within the organisation to an external domain. Not all users are affected, and not all outgoing e-mails have this issue.
Some e-mails get stuck in the submission queue. This is the error message in Last Error : "A storage transient failure has occurred during content conversion."
Days later, the internal user who send the message gets a #550 4.4.7 QUEUE.Expired; message expired ## NDR.
We did have some initial configuration issues, but these were fixed more than a week ago :
- The external FQDN during EHLO was set to the wrong address, now pointing to the correct one.
- SPF record was updated with new IP adress.
Here is some additional information on the issue :
- Not on any blacklists - checked using dnsbl.info
- Telnet to remote servers works from exchange server, connections are accepted and can send mail.
- Outbound SMTP test ran using Microsoft Remote Connectivity Analyser : Passed with both External (Static) and Smarthost IP.
- This seems to happen only with emails that have an attachment and that are transfered, but only for the affected users.
- If content from these e-mails is manually copied over to a new email, email is sent to destination without problem.
Configuration information :
- Exchange 2013 running on Windows 2012 Datacenter with all latest updates.
- Outgoing e-mail is sent via smarthost. Only one outbound transport rule is active.
- Using internal DNS server.
- There is only one mailbox database.
Thank you for taking the time to read this!

On Wed, 16 Jan 2013 15:31:14 +0000, Ipigi wrote:
>Sorry, I often get some terms mixed up when I explain things as our users use the French version of outlook.
>
>E-mails are not transferred, but forwarded manually from their outlook. Message format in outlook is set to HTML and not Rich Text when they foward the e-mail.
Do they forward the message as an attachment?
>When forwarded internally, this is in the internet headers :
>
>Content-Type: application/ms-tnef; name="winmail.dat" Content-Transfer-Encoding: binary
Within your organization I'm prety sure that messages will use TNEF.
What does the message contain at the external recipient's side?
>It really seems to me that Exchange is not converting RTF to Plain Text. The first link you provided states in it's final paragraph that Exchange should be doing this conversion.
If you can, try creating a mail-enabed Contact for one of the external
recipients and set the message format on that.
>If I disabled TNEF as that link suggests, offending messages will get stuck in the submission queue again.
>
>I thank you for your help so far. This is not an issue I've had with any previous installations/migrations of Exchange that I have done.
>
>Please let me know if you need any additional information.
Have you tried UNsetting TNEF on the remote domain?
Set-RemoteDomain Default -TNEFEnabled $null
That should leave it up to the client to determine the format. It's
probably not what you're after, but see it makes a difference in the
format.
Rich Matheisen
MCSE+I, Exchange MVP
--- Rich Matheisen MCSE+I, Exchange MVP

MailboxInSiteFailoverException - OWA session error on database *over (Exchange 2013 SP1)

Hi all, I have noticed an issue with OWA when database(s) are failed over between DAG members. The environments in question (issue can be reproduced in separate implementations of 2013 SP1 all-role servers) are 2 or more DAG members within the same
AD site/subnet. These are also fresh implementations with SP1 and not upgraded. Exchange servers are load balanced via Netscaler.
So to the issue - OWA users experience the below "..MailboxInSiteFailoverException" message when the database copy is activated. Exchange does not immediately proxy the requests to the active database. You can wait several minutes and
the issue is resolved by refreshing the browser or if you recycle the MSExchangeOWAAppPool on both DAG members, the issue is resolved immediately (OWA session re-established on refresh).
Testing so far involved opening multiple OWA sessions and activating a database copy. At that point, upon refresh of the browser the below error is shown (in all test browsers/sessions below) where I would expect any DAG member to be able to proxy
the client request to the active database server immediately (and not after several minutes).
https://netscaler_LB/owa
https://ex2013server-1/owa
https://ex2013server-2/owa

Hi Simon, I have tested with no firewall on the exchange servers and on client machines within the same subnet as the servers. All with the same results.
I can see many ASP.NET 4.0.30319.0 Event ID 1309 logs similar to this and other threads (http://social.technet.microsoft.com/Forums/windowsserver/en-US/c938dda0-b3bc-4544-851e-f27b503cf4ed/exchange-2013-event-id-1309-source-aspnet-40303190).
IIS logs show similar monitoring mailbox issues but I am still currently looking through the logs. Thanks for your input.
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 0 0 13
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
2014-03-30 00:00:23 127.0.0.1 POST /owa/proxylogon.owa - 444 - 127.0.0.1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST) - 401 1 2148074254 0
2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_3ce57cd622aa4655a ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
- 302 0 0 47
2014-03-30 00:01:23 ::1 POST /owa/proxylogon.owa &ex=UE:Microsoft.Exchange.Data.Storage.IllegalCrossServerConnectionException 444 DOMAIN\SM_2891f9d41af2422e8 ::1 Mozilla/4.0+(compatible;+MSIE+9.0;+Windows+NT+6.1;+MSEXCHMON;+ACTIVEMONITORING;+OWADEEPTEST)
- 302 0 0 47

Support for TLS 1.2 over Exchange 2013?

How to enable TSL1.2 in Exchange 2013, any documentation leading me to configure it?
Is there any confirmation about TSL 1.2 Supporting or not?
Any help or insight would be greatly appreciated. Thanks!

Hi
Similar article, no info as yet:
http://social.technet.microsoft.com/Forums/en-US/8815dada-94b5-4d89-ad80-43f03705c551/support-for-tls-12-over-exchange-2013-on-server-2012

RPC over HTTP trouble Exchange 2013/2007 coexistence, 2013 RPCProxy cannot ping GC.

I currently have an Exchange 2013/2007 coexistence scenario which gives me trouble with the RPC over HTTP part with users with a 2007 mailbox. the MS RCA website performs 2 tests with the MAPI address book endpoints, once against a 2007 mailbox server and
once a against a GC/DC, the last one fails. The logs are from our test domain, but the exact same happens in the production domain. running CU8 (recently upgraded, but problem was exactly the same with CU7)
Testing the MAPI Address Book endpoint on the Exchange server.
The address book endpoint was tested successfully.
Additional Details
Elapsed Time: 7872 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: exmb11.domain.test:6004.
The endpoint was pinged successfully.
Additional Details
The endpoint responded in 156 ms.
Elapsed Time: 4153 ms.
Testing the MAPI Address Book endpoint on the Exchange server.
An error occurred while testing the address book endpoint.
Additional Details
Elapsed Time: 3079 ms.
Test Steps
Attempting to ping the MAPI Address Book endpoint with identity: tdc01421.domain.test:6004.
The attempt to ping the endpoint failed.
<label for="testSelectWizard_ctl12_ctl06_ctl02_ctl09_ctl00_tmmArrow">Tell
me more about this issue and how to resolve it</label>
Additional Details
The RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime process.
Elapsed Time: 3079 ms.
texmb11 = ex2007 mailbox
texfr11 = ex2007 CAS
tdc01421 = DC/GC
texch31 = 2013 multirole
other symptoms :
Browser test
https://texch31.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503 (which is correct)
https://texch31.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 404.0 Not Found
RPCPing
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texch31.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Fails!
so the Ex2013 RPCProxy doesn't proxy to the DC/GC, but the RPCProxy to an ex2007 mailbox server works fine, so the authentication methods configured are correct i'd say..
the same tests using the ex2007CAS server as RPC proxy all succeed!:
MS RCA is all green
https://texfr11.domain.test/rpc/rpcproxy.dll?texmb11:6004
--> 503
https://texfr11.domain.test/rpc/rpcproxy.dll?tdc01421:6004
--> 503
rpcping -t ncacn_http -s texmb11 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success
rpcping -t ncacn_http -s tdc01421 -o RpcProxy=texfr11.domain.test -P "user,dom,*" -I "user,dom,*" -H 2 -u 9 -a connect -F 3 -v 3 -e 6004
Success!!
Logs
all tries against the 2013 CAS server generate '404' log entries in several logs int the Logging directory, the most explicit being the one in Program Files\Microsoft\Exchange Server\V15\Logging\HttpProxy\RpcHttp : HttpProxy_xxxxxx.LOG
2015-04-30T19:58:00.153Z,895cdf07-f2eb-4beb-b787-da02ba11b0c2,15,0,1076,0,,RpcHttp,webmail.domain.test,/rpc/rpcproxy.dll,,Basic,true,DOM\user,,,MSRPC,10.10.142.132,TEXCH31,404,,MailboxGuidWithDomainNotFound,RPC_IN_DATA,,,,,,,,,4,,,,1,,,0,,0,,0,0,,0,2,0,,,,,,,,,1,1,0,,1,,2,2,,?TDC01422.domain.test:6004,,BeginRequest=2015-04-30T19:58:00.153Z;CorrelationID=<empty>;ProxyState-Run=None;ProxyState-Complete=CalculateBackEnd;EndRequest=2015-04-30T19:58:00.153Z;,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
RPC server name passed in by client could not be resolved: TDC01422.domain.test at Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveToDefaultAnchorMailbox(String originalRpcServerName String reason) at
Microsoft.Exchange.HttpProxy.RpcHttpProxyRequestHandler.ResolveAnchorMailbox() at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalBeginCalculateTargetBackEnd(AnchorMailbox& anchorMailbox) at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<BeginCalculateTargetBackEnd>b__3b();
the error suggests the name could not be resolved. but nslookup works fine. i can ping the tdc01421 correctly form texch31, it returns me the ipv4 address. i can telnet to port 6004 from texch31 server to tdc01421 giving me the correct 'ncacn_http' answer..
i look at the 'ValidPorts' and ValidPorts_Autoconfig_Exchange reg keys and filled them with the same i have on the 2007cas servers (all ex servers, all dc/gc's, all of them with netbios & fqdn ports 6001,6002 & 6004..) but also no success.
im out of ideas by now..

Hello togehter,
if anyone is using the Interim Update (Hotfix) "Exchange2013-KB2997209_2997847-x64-en.msp" please be aware of the following bug in this hotfix:
NOTE: Another issue that we have seen only from some E2013 On-Premises customers who installed
fixes for any of the above E2013 CU6 related issues is that “Using OWA, users cannot create new messages or reply to existing messages” – These are mostly installer issues where OWA files are not copying correctly in the new version directory. Ideally the
content of these two folders, i.e. “V15\ClientAccess\Owa\prem\15.0.995.31” and “V15\ClientAccess\Owa\prem\15.0.995.29” should be identical, now if for any reason, they are not then it can break the OWA experience like described above. Take these steps if you
run into related issues:
-Backup the contents of “15.0.995.31” folder to a different folder/directory
-Copy the files and folders from “15.0.995.29” to “15.0.995.31” folder – this should fix the issue …
Best,
Martin

Exchange 2013 Health mailbox and Journaling

Hi All,
We have recently build green field Exchange 2013 environment with standard journaling. Now we are seen that as per journal capture process it captures health mailboxes emails as well.
As we all know we will use options ignore/disable health mailboxes emails
Method 1 : Dynamic DL
Method 2 : Use global override
http://support.microsoft.com/kb/2823959/en-us
My questions
if go for Method 2
1. What will be the challenge will face in environment
2. Is Microsoft recommendation is go with Method 2 ( I am still looking for clarification even though I mentioned in MS KB)
Thanks
Vishal Saxena

Hi Vishal,
1. As it says in KB some server monitoring applications may not correctly monitor transport server components if you have any. Basically you will lose the ability to detect any condition when server stop accepting mails automatically.
2. You can definitely go with method 2 considering you have another way to monitor transport components and this failure detection.
Blog |
Get Your Exchange Powershell Tip of the Day from here

Why I got this email if I didn't schedule any storage plan ? This is the email I got; On 10/07/2013 you are scheduled to be charged $20.00 for your 10 GB iCloud storage plan, but there is a problem with your payment information, Can someone help me

Why I got this email if I didn't schedule any storage plan ? This is the email I got;
On 10/07/2013 you are scheduled to be charged $20.00 for your 10 GB iCloud storage plan, but there is a problem with your payment information, Can someone help me ? I don't want to be charge for something I don't want to buy.

You may want to do couple things
1. cancel auto renewal for icloud - instructions here -under downgrade storage
http://support.apple.com/kb/HT4874
2. change your payment info in itunes, to either none or other payment method - instructions here
http://support.apple.com/kb/ht1918

How to to make Cluster between two server 2012 Datacenter with share storage and Hyper-V role then install Exchange 2013 on each server datacenter then make DAG between Exchange servers

Dears,
I have IBM Flex server with built in storage,
HOW to to make Cluster between two server 2012 Datacenter with share storage and Hyper-V role then install Exchange 2013 on each server datacenter then make DAG between Exchange servers?
If there any prerequisites of the Share storage types ?and any configuration guide to deploy Cluster between two Server 2012 datacenter ?

Microsoft Failover Clusters require shared storage. If you wish to create a failover cluster with local storage, you need to use third party software to mirror the disks and present it to the hosts (siog.com, datacore.com, starwind.com). If you
use third party software, you will need to follow their instructions for configuring the environment.
Questions on how to configure Exchange environments are better asked in an Exchange forum.
.:|:.:|:. tim

Planning a migration from Exchange 2010 to Exchange 2013

Hello,
I am planning a migration from Exchange 2010 to Exchange 2013 and I was wondering if there was a good guide on the UM migration. I haven't found one that isn't confusing as heck.

Hello,
Is there any update?
If
you have any feedback on our support, please click here
Cara Chen
TechNet Community Support

Journaling mailbox - Exchange 2013 Migrations from 2010

hi guys
i am about to start mailbox movement from Exchange 2010 to 2013. my setup is working fine. i have enabled journaling from Exchange 2010 and as ii found, automatically journaling rules will be reflected to exchange 2013. i had very big journaling mailbox
and then newly created New Exchange 2010 journaling mailbox. now new journaling mailbox is configured for journaling and that also still on 2010(both Old and new journaling mailbox ), new mailx is couple of weeks old (6-8 GB) and old one is 2.6 TB. So i will
move old one at the end .
my questions is if i move new journaling mailbox to 2013 before start normal Mailboxes, it will cause some issues for journaling. i use premium journaling . is it okay to move journaling mailbox at the begin ??
thank you
Indunil

Hi,
Based on my test, journal rules will be synchronized in Exchange 2013 after you create in Exchange 2010. If you create in Exchange 2013, then the rule will be synchronized in Exchange 2010.
And I did create a rule to send message to a Exchange 2013 jounal mailbox for Exchange 2010 users. It worked.
So you can migrate journal mailbox to Exchange 2013 firstly based on this test.
Best regards,
Belinda Ma
TechNet Community Support

Exchange 2013 Server DR Planning

Recently we migrated from exchange server 2010 to 2013(2Mb, 2CAS) .
Planning to do below steps in DR. Kindly suggest me good practices, if possible share good document for exchange 2013 DR.
1) Mailbox Server (One Node)
2) CAS Server(One Node).
3) Adding this DR mailbox server to DAG.
4) Enabling DAC for DAG.
Is there any steps i missed out...
Kindly suggest me good practices, if possible share good document for exchange 2013 DR with DAC.

Agree with Andy dynamic Quorum is enabled by default.
In an odd number of servers File share witness is being ignored it uses "Node majority"
In Windows 2008 if you have 3 members in a DAG and 2 of them fails automatically the 3rd one will be offline because no quorum. But in windows2012 if 2 members fails 3rd one will be still online.
Please refer these as it will answer your question I guess.
https://social.technet.microsoft.com/Forums/office/en-US/e4a46b94-e510-42bd-927b-8fa0a912f2e0/dag-file-share-witness-quorum-best-practice?forum=exchangesvravailabilityandisasterrecovery
http://www.msexchange.org/articles-tutorials/exchange-server-2013/high-availability-recovery/exchange-2013-dag-dynamic-quorum-part2.html
Below command will prevent automatic failover to DR site. Refer below URL
Set-MailboxServer -Identity EXDR02 -DatabaseCopyAutoActivationPolicy IntrasiteOnly
http://www.msexchange.org/kbase/ExchangeServerTips/ExchangeServer2010/HighAvailability/PreventDatabaseCopiesfromAutomaticallyMountinginotherSites.html
Thanks, MAS
Please mark as helpful if you find my comment helpful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you.
"But in windows2012 if 2 members fails 3rd one will be still online."
That depends on the failure. If the 2 that fail are in the same datacenter, and the datacenter fails, the
3rd will not be online. Dynamic quorum does not protect against the sudden loss of majority.
Twitter!:
Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Native Exchange 2013 Journaling - Guidance over Storage Planning!

Similar Messages

Maybe you are looking for