Exchange
--
Questions
--
Followers
Top Experts
New-MailboxExportRequest cmdlet issues
Hello everyone,
I'm currently running Microsoft Exchange 2010 SP1 Update Rollup 3-v3. Has anyone had any real success in using the cmdlet New-MailboxExportRequest? I've been tasked to export specific people in AD to pst files on a monthly basis (which is what I used to to do in Exchange 2003). Basically they're important people and this is a "just in case" backup process.
So what I did was executed each member of 'Group1' to the New-MailboxExportRequest cmdlet to a file server \\FILESERVER1\share\month\
Then what I did was made a Powershell script to go one by one, execute the command, wait until it finished, then moved on. This started working pretty well until it hit some users. They get stuck in a 'Queued' state forever. During this time, memory utilization on FILESERVER1 gradually got higher and higher. Once I killed the process, it dropped back down.
Does anyone know why this happens? Why does the memory utilization in the destination server keep creeping upwards? What makes a user stuck in a Queued state forever? I know I'm asking a lot of questions, but anyone who has any insight on this will be much appreciated! I could not find anything on Google that helped me troubleshoot this.
I'm currently running Microsoft Exchange 2010 SP1 Update Rollup 3-v3. Has anyone had any real success in using the cmdlet New-MailboxExportRequest? I've been tasked to export specific people in AD to pst files on a monthly basis (which is what I used to to do in Exchange 2003). Basically they're important people and this is a "just in case" backup process.
So what I did was executed each member of 'Group1' to the New-MailboxExportRequest cmdlet to a file server \\FILESERVER1\share\month\
Then what I did was made a Powershell script to go one by one, execute the command, wait until it finished, then moved on. This started working pretty well until it hit some users. They get stuck in a 'Queued' state forever. During this time, memory utilization on FILESERVER1 gradually got higher and higher. Once I killed the process, it dropped back down.
Does anyone know why this happens? Why does the memory utilization in the destination server keep creeping upwards? What makes a user stuck in a Queued state forever? I know I'm asking a lot of questions, but anyone who has any insight on this will be much appreciated! I could not find anything on Google that helped me troubleshoot this.
Zero AI Policy
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
1. Exactly how long is 'forever'?
2. How large is the first mailbox that appears to be in 'queued' state?
2. How large is the first mailbox that appears to be in 'queued' state?
1. I stopped the process after 3 hours of it being in Queued.
2. At the time that mailbox was about 600 megs.
I'm running the script now, and FILESERVER1 is at 97% memory utilization. One user got successfully moved and it's in the middle of the second one.
2. At the time that mailbox was about 600 megs.
I'm running the script now, and FILESERVER1 is at 97% memory utilization. One user got successfully moved and it's in the middle of the second one.
Attached is a screenshot of Task Manager of FILESERVER1. The Available memory is down to 130 megs, and the server itself has a total of 4 gigs of RAM. Under normal use, 3.0-3.5 gigs of RAM is usually available.
The second user is currently being backed up and he has a mailbox size of 1.2 Gigs.
Capture.GIF
The second user is currently being backed up and he has a mailbox size of 1.2 Gigs.
Capture.GIF
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Can you look at the actual processes and sort on memory usage and determine which ones are the heavy hitters?
The interesting part is that the process doesn't show up in Task Manager. 3.5 Gigs of RAM is being used on FILESERVER1, but the top process with the highest memory usage is only 130 megs.
Capture.GIF
Capture.GIF
One quick thing... It looks like you are running Sophos antivirus... have you ensured that you have appropriate exceptions defined for the real time scanning (exclude Exchange database and logging directories)?
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
We made it a policy since Sophos was rolled out that all servers have Real-Time scanning turned off. It does nightly system scans.
I'd be interested in hearing how that policy came about... I believe we'd have PCI compliancy issues if that were in place here... we have multiple layers of AV in our Exchange environment... one at the system level (with RT scanning enabled), one specifically aimed at Exchange.... no impact to performance...
Anyhow...
Can you open up a powershell console and see if you can get any further process info:
get-process
Anyhow...
Can you open up a powershell console and see if you can get any further process info:
get-process
Here's the results of Get-Process on it. It's lists 64 processes, just like Windows Task Manager.
PS C:\> get-process
Handles NPM(K) PM(K) WS(K) VM(M) CPU(s) Id ProcessName
------- ------ ----- ----- ----- ------ -- -----------
225 12 4616 1004 97 0.48 1060 ALMon
9232 8 3196 2576 42 439.44 2444 ALsvc
217 13 6044 5576 52 2,125.58 1604 BBWin
39 3 2200 200 16 0.11 1616 bedbg
436 84 45668 9740 260 ...28.94 2908 beremote
62 53 1044 960 25 1.73 400 collector
732 11 1908 2016 69 729.70 516 csrss
170 7 2864 3668 48 1.86 4300 csrss
82 6 1396 2216 44 0.13 1784 ctfmon
59 4 828 1192 40 0.06 4420 ctfmon
173 15 7436 540 107 1.55 1744 DWRCS
350 17 11796 11260 124 1.78 2304 explorer
0 0 0 24 0 0 Idle
334 62 9144 1928 96 64.38 1900 inetinfo
94 6 3060 496 35 2.59 1312 iscsiexe
179 56 3416 1508 46 ...66.28 276 jqs
194 14 6500 2128 76 0.23 668 jucheck
204 14 5456 1536 74 0.20 2032 jusched
132 9 2512 1480 58 46.92 1940 LocalSch
20 3 1364 272 40 8.92 688 logon.scr
770 43 14124 7888 107 1,358.02 604 lsass
389 27 10236 6212 96 642.50 2408 ManagementAgentNT
153 11 2936 200 39 0.20 1504 msdtc
43 5 892 200 30 0.05 2212 NMSAccessU
132 12 5284 200 60 0.11 1976 pds
109 10 3684 1504 60 2,282.45 708 policy.client.invoker
232 12 47300 44200 548 1.77 4564 powershell
78 6 1976 1972 65 0.06 3216 rdpclip
163 204 5572 404 60 26.97 1680 residentAgent
311 26 8152 3364 81 41.06 2476 RouterNT
91 7 3224 328 44 0.11 4124 SAVAdminService
721 54 131516 77056 328 ...72.55 4492 SavService
482 22 7852 28528 332 7,096.73 592 services
24 1 292 200 5 0.58 468 smss
157 12 3236 956 54 82.69 2308 snmp
129 9 4828 2492 69 1,670.67 2328 softmon
189 15 7792 496 86 5.77 1472 spoolsv
433 24 95000 1584 1533 395.63 2104 sqlservr
178 11 4940 536 84 25.22 2516 sqlwriter
94 6 1944 712 31 5.95 800 svchost
363 36 3052 3016 41 450.23 872 svchost
155 13 6472 2288 69 15.95 1200 svchost
90 5 1696 792 28 4.61 1216 svchost
1307 92 24812 13196 419 2,415.00 1256 svchost
160 10 6740 1180 49 4.98 1700 svchost
117 8 3080 372 50 0.66 1724 svchost
69 4 1436 200 26 0.06 1800 svchost
45 4 1356 760 18 0.66 2236 svchost
70 5 2004 200 29 0.08 2888 svchost
239 12 4076 1960 80 132.38 3332 svchost
227 14 4172 232 50 0.53 3536 svchost
140 8 2036 1864 41 1.83 3864 swi_service
3191 0 44 129092 169 ...01.17 4 System
92 7 2652 2972 65 0.83 2016 taskmgr
179 111 9424 1036 92 78.75 2056 tmcsvc
69 6 1260 1528 56 0.03 4248 VCDDaemon
38 4 1712 200 26 0.09 772 vmacthlp
244 14 8288 3356 107 2,189.30 2748 vmtoolsd
98 6 2312 200 40 0.16 1448 VMUpgradeHelper
68 6 2752 2160 64 0.06 4272 VMwareTray
631 174 11308 5016 80 160.70 544 winlogon
283 17 5424 4040 93 0.75 4348 winlogon
166 7 4776 680 45 12.02 3252 wmiprvse
358 15 11172 6472 94 926.11 3836 wmiprvseEARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
ok.... so, last thing to try and see all of your processes
WMIC path win32_process get Caption,Processid,WorkingS
WMIC path win32_process get Caption,Processid,WorkingS
Unfortunately that also has a same number of processes. I'm starting to think this is a Microsoft bug since that cmdlet is brand new in SP1.
C:\>WMIC path win32_process get Caption,Processid,WorkingSetSize
Caption ProcessId WorkingSetSize
System Idle Process 0 24576
System 4 132190208
smss.exe 468 204800
csrss.exe 516 2068480
winlogon.exe 544 5152768
services.exe 592 29220864
lsass.exe 604 8122368
vmacthlp.exe 772 204800
svchost.exe 800 729088
svchost.exe 872 3137536
svchost.exe 1200 2318336
svchost.exe 1216 811008
svchost.exe 1256 16506880
iscsiexe.exe 1312 507904
spoolsv.exe 1472 507904
msdtc.exe 1504 204800
BBWin.exe 1604 5623808
bedbg.exe 1616 204800
residentAgent.exe 1680 356352
DWRCS.EXE 1744 552960
svchost.exe 1800 204800
inetinfo.exe 1900 1974272
LocalSch.EXE 1940 1515520
pds.exe 1976 204800
jqs.exe 276 1507328
collector.exe 400 987136
policy.client.invoker.exe 708 1540096
tmcsvc.exe 2056 1060864
sqlservr.exe 2104 1630208
NMSAccessU.exe 2212 204800
svchost.exe 2236 778240
snmp.exe 2308 987136
softmon.exe 2328 2584576
ManagementAgentNT.exe 2408 3088384
ALsvc.exe 2444 2768896
RouterNT.exe 2476 3923968
sqlwriter.exe 2516 548864
vmtoolsd.exe 2748 3436544
svchost.exe 2888 204800
beremote.exe 2908 9973760
VMUpgradeHelper.exe 1448 204800
svchost.exe 1700 1208320
svchost.exe 1724 380928
wmiprvse.exe 3252 696320
svchost.exe 3332 1986560
svchost.exe 3536 237568
logon.scr 688 278528
SavService.exe 4492 85528576
SAVAdminService.exe 4124 335872
swi_service.exe 3864 1908736
wmiprvse.exe 3836 6807552
csrss.exe 4300 3252224
winlogon.exe 4348 4128768
rdpclip.exe 3216 2105344
explorer.exe 2304 11943936
VMwareTray.exe 4272 2228224
ctfmon.exe 1784 2273280
ctfmon.exe 4420 1220608
VCDDaemon.exe 4248 1564672
ALMon.exe 1060 1617920
jusched.exe 2032 1576960
taskmgr.exe 2016 3145728
jucheck.exe 668 2179072
cmd.exe 4960 3100672
wmic.exe 3500 11993088
Upon further investigation. I think the memory utilization on FILESERVER1 is directly related to the PST size of the file. My script was in a middle of exporting a user with a 4 gig mailbox, and the file server had no ram available. I had to kill it so it won't crash. The moment I killed it, the amount of available RAM jumped back up to 3.5 Gigs. Very strange.
Get a FREE t-shirt when you ask your first question.
We believe in human intelligence. Our moderation policy strictly prohibits the use of LLM content in our Q&A threads.
If it helps you can always play around with
-MRSServer <nameofserver> with your export request.
On the server in question edit the file MSExchangeMailboxReplicati
This should make it do one move at a time and not throttle your servers.
-MRSServer <nameofserver> with your export request.
On the server in question edit the file MSExchangeMailboxReplicati
MaxActiveMovesPerSourceMDB = "1"
MaxActiveMovesPerTargetMDB = "1"
MaxActiveMovesPerSourceServer = "1"
MaxActiveMovesPerTargetServer = "1"
MaxTotalMovesPerMRS = "1"This should make it do one move at a time and not throttle your servers.
ASKER CERTIFIED SOLUTION
membership
Log in or create a free account to see answer.
Signing up is free and takes 30 seconds. No credit card required.
Decided to go another route.
ok
EARN REWARDS FOR ASKING, ANSWERING, AND MORE.
Earn free swag for participating on the platform.
Exchange
--
Questions
--
Followers
Top Experts
Exchange is the server side of a collaborative application product that is part of the Microsoft Server infrastructure. Exchange's major features include email, calendaring, contacts and tasks, support for mobile and web-based access to information, and support for data storage.