Exchange 2010 database won't mount

We had a power outage and I believe that the database has been corrupted. When I try to mount a restored copy of the database the day before the crash it gives me the following error.
Microsoft Exchange Error
Failed to mount database 'Mailbox Database 0517197706'.
Mailbox Database 0517197706
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database 0517197706; Error code: An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount
database. (hr=0x80004005, ec=-501)
. [Database: Mailbox Database 0517197706, Server:#########].
An Active Manager operation failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)
. [Database: Mailbox Database 0517197706, Server: ###########]
An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)
. [Server: ###########]
MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-501)

So it appears that what happened may be that the copy back process was terminated earlier, hence the smaller file size etc. So what I would do is
1. Rename
Mailbox Database 0517197706.edb to "OLD_Mailbox Database 0517197706.edb"
2. if the TMP file is in same location as the main file I would then just rename
TEMPDFRG7840.EDB to
Mailbox Database 0517197706.edb. If the TMP file is in alternate location I would rename and then copy back into place where Exchange expects the file to live.
3. Then attempt a mount and report back
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Similar Messages

Exchange 2007 database won't mount due to MapiExceptionCallFailed errors

A server is running Exchange Server 2007 SP2 on Windows Server 2008 64-bit. After a couple years of running smoothly, the Windows Application event log started filling up with several instances every minute of the following error:
MSExchangeIS (2644) First Storage Group: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 5, PgnoRoot: 10) of database H:\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb (165296 => 3185, 817790).
Messages sent to a specific mailbox on the server started getting returned as undeliverable with the message:
#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionCallFailed..."
I assumed that the event log messages and the delivery errors were related so I ran "eseutil /d" on the database but it exited with the message, "Operation terminated with error -1605 (JET_errKeyDuplicate, Illegal duplicate key) after 76.578 seconds. Running
eseutil /mh reports the database state as clean shutdown.
The Exchange database had been backed up nightly using Windows Server 2008 Backup. I restored the latest backup of the .edb file. Unfortunately, the corruption behind the bad page link error seemingly had propagated through the backups because the restored
.edb file had the same issues.
I then attempted to create a new clean database with the goal of then transferring mailbox data from the old to the new as described in the article "Simplifying the Dial Tone Database Recovery Process in Exchange 2007" (http://blogs.technet.com/b/dhardin/archive/2009/08/25/simplifying-the-dial-tone-database-recovery-process-in-exchange-2007.aspx).
I successfully created the new storage group and database with empty instances of all mailboxes but attempts to mount the old database yield this message:
Error: Exchange is unable to mount the database that you specified. Specified database: FASTMAIL\NewStorageGroup\Mailbox Database; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-344)
I then tried to return to the initial state of having a corrupted database but one that would at least function temporarily for all but the one broken mailbox. The idea would be to instruct individual users to run the Outlook archive command to back their
messages up locally into .pst files. Unfortunately, all attempts to mount the original .edb file yield the same MapiExceptionCallFailed error. I also tried to mount the database after deleting the transaction log files.
I searched the web for information on this error. There are some pages describing similar errors such as "hr=0x80004005, ec=2417" but I could not find any for "ec=-344". Some articles recommend running IsInteg.exe but this utility only works for databases
that are already mounted and I am unable to mount the database.
The Exchange server is running again using the empty database so that the users can at least send and receive mail. I get the sinking feeling that all hope is lost and the historical mail data that was stored on the server is gone for good. Before I face
the pitchforks of the angry mob, I figured that I would at least post an inquiry on an Exchange-related forum.
Are there any other steps I should take to try to recover the old data?

have you checked the health of the database using eseutil /mh "edbfilename.edb" ?
is the state: Clean Shutdown ?
If it is in clean shutdown state, then move the old logs, chk, .jrs files and select the option "This database can be overwritten by a restore" and mount the database.
In case if your database is not in clean shutdown state then you would need to work towards getting the database to clean shutdown using any of the following strategies based on the criteria that the database is affected with !
1. soft recovery
2. Hard Recovery
3. Hard repair
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
Information is provided is "AS IS" and confers NO Rights!!

Script for unmounting/deframenting exchange 2010 database

hi all,
i need a script to unmount exchange 2010 database, defrag it and mount it again.
thanks for any comment you may add...

Tried the above commands... works like a charm, but with the following modifications:
1. Delete trash and recoverable items from all mailboxes, run repeatedly
The command using is
Search-Mailbox -Identity "mailbox.name" -SearchDumpsterOnly -DeleteContent
1A. Determining Free Space in Mailbox Database
The command using is
Get-MailboxDatabase -Status | ft name,Availablenewmailboxspace,Databasesize
2.Calculate the disk space to perform the defrag, the formula is
(Databasesize-Availablenewmailboxspace)*1.1
3.Dismount the mailbox database
In EMS, go to the folder contain the database file then use the command
Dismount-Database <DatabaseName>
3A.Copy mailbox database (edb and all related log files) to another location
In EMS, go to the folder contain the database file then use the command
4.Defrag the edb file (eseutil will recreate a temp edb and rename to the new edb after successful complete it will delete the old edb file. If anything goes wrong, it will revert back to the old edb as in the /d)
eseutil /d <file.edb>
5.Mount again
Mount-Database <DatabaseName>
You are advised to purge (step 1) all mailboxes before eseutil or move mailbox, otherwise it will just carry all the sh!t over to the new mailbox anyway. I gave up trying to tally the total mailbox space used, the whitespace avail and the edb file size already.
For example, not sure why there is such a disparity where by I have 30 2GB mailboxe est. at 60GB used, whitespace after mailbox move/eseutil at 95GB, the edb size is 106GB. This is where my older exchange 2003 edb files wins hands down. Better budget more
storage for edb files! I am considering whether it's even worth migrating all to exchange 2010 altogether! The edb files are so damn space hungry even with 3 day retention and 6 day delete with 24/7 maintenance ticked. Exchange 2010 edb beast simply cannot
be tamed.
Personally I find in EMC to online move mailbox faster and more reliable overnight. Furthermore, you can simply create a new database, sort all mailboxes by database, select all of them, follow the wizard to move them all at once, the system simply queues
them to move and complete. Overnight moving is the best, all will be done the next day.

Replay only particular logs (before a certain date) to restored Exchange 2010 database?

Hello,
I'm doing Exchange 2010 database full backup using windows server backup (windows 2008 R2) every weekend. I have a Mac user which Mac Outlook 2011 which somehow managed to corrupt his mailbox. I.e. on Wednesday many messages and contacts disappeared (all
contact gone) after his Outlook told his something about "corrupted database". I'm not sure what Mac Outlook did, but fact is that his mailbox has zero contacts and many inbox message are gone. Hard deleted items don't contain lost messages.
So I have DB backup from weekend before and weekend after. No circular logging, so all logs in place.
Is there a way how I can restore his mailbox back to the point in time? I want to restore his mailbox how it was on Wednesday morning. For it looks obvious that since I have log files from Monday to Friday, it should be possible to replay logs until certain
time.
I tried to did thick trick by removing Friday and Thursday logs and doing soft recovery, but got Operation terminated with error -543 (JET_errRequiredLogFilesMissing, The required log files for recovery is missing.) They indeed missing:
dbtime: 2221857861 (0x846edc45)
State: Dirty Shutdown
Log Required: 2895446-2895464 (0x2c2e56-0x2c2e68)
Log Committed: 0-2895465 (0x0-0x2c2e69)
Log Recovering: 2838005 (0x2b4df5)
Log required are logs from they day of backup, so they are really missed in that case, but that's what I want - restore DB with less/older logs to get back in time, when mailbox was not corrupted.
Is that possible?
Thanks

ok so the problem is you have the dreaded -1018 error and this is a very serious issue. -1018 is not a good deal at all, in short your DB has corruption within it
and it is usually caused by a hardware or firmware related issue. Most of the time these occur somewhere within the storage subsystem, i.e. firmware upgrade or lack of firmware upgrade, Controller issue, cabling, disk, disk arrays, etc, however they can
also be caused by memory upgrades or failures, Motherboard issues etc.   The -1018 tells you the DB is already damaged and if you see these its very bad and needs to be addressed ASAP else the DB's are sure to fail and the more stress you put on
them the faster the chance of failure, i.e. database backups, defrag;s and repairs etc are not recommended at all until you solve the hardware issue. So here is what I would recommend:
A: Lets try to ensure the box is stable and whatever caused the DB to get the -1018's is solved before we do anything else.
General Review: Whats changed recently? i.e. any hardware, memory, motherboard, any firmware updates on anything at all?
Event Log Review: Look at your Application Log, how long have these 1018's been occurring?   Look at your System event log for errors and pay close attention to any errors regarding disk, memory or MB and report back
Protect: I would dismount the database & copy it and any others off to a secure, safe drive that is NOT connected to this system
Action: Depending on what you find in your review there are really two options
     i: If you had a recent change that is easily identifiable you may be able to correct it and then we can look at finding a clean copy of the EDB and rolling up the logs OR we opt to repair the DB you have
     ii: if you cannot find the issue in short order then I would suggest that you build a new Exchange Server on new hardware and migrate your mailboxes immediately.
B: Once you have addressed the -1018 issue then;
1. We need to find a database from your backups that does NOT have the -1018 result code when attempting a rollup.
2. Once you have a non -1018 result you can then grab a fresh copy of the EDB along with all logs from that point forward and make a consistent DB via rollup up to the 18th as desired.
3. If you cannot find a good copy of the EDB then you are stuck with the latest data you have and should either move all mailboxes to a new EDB on that server but ONLY IF the source of the -1018 is found and resolved, else you will just be making thing s
worse. IF you CANNOT resolve the issue that causes the -1018 then build a brand new server and move all users over to it ASAP, else you are headed for a major failure on all users.
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003 -->
2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange 2010 database help after clean install of exchange 2010

Long story short. Had exchange 2010 issues. My exchange store would not open and I could not mount database. Copied v14 folder over to another folder. Removed exchange from AD, recreated my windows 2008 r2 virtual machine, Installed completely new exchange.
It came up with new mailbox offline, which i left that way. I copied my flat files into the newly created v14 folder. When I open exchange, I see an unmounted copy of my old database. However, I am unable to do anything with it. Esutil said it was a clean
shutdown. I am looking for the steps I need to take to get my old database back online as it has everyone's info. So exchange see's a copy of my old database, but nothing else. Any help would be appreciated. Thanks in advance.
John

Thanks for the response Willard,
Your correct, I have placed myself in a Jam. the .edb file is in a clean state. I copied the whole directory over to a mapped drive. I am currently working the problem 2 ways. I have created a recoveryDB, but when I try to perform a New-MailboxRestore request
it fails. When i do a get statistics I can see all email in the recoveryDB, but only a system file mailbox in the new database i created, none of my users. I have also tried the database portability. I can check and confirm the old database, but at the last
step I am supposed to Get Mailbox -Database "old database", it fails to find the old database. So I am unable to run Get-Mailbox -Database "old Database" | Set-Mailbox -Database "New Database". I have set the new database to be
overwritten. The problem arises when i try to get-mailbox -Database (old database)= it says it cannot find database. Since I performed a clean install the old database is not in Active directory. When I open the path to the new database it is pointing
at the .edb in the folder I created using the steps at www.exchangerecover.com/blog/2010/move-a-mailbox-database-using-database-portability.html
Now that I totally screwed it up, I can start from the beginning if necessary. I am just hoping I do not lose the data. I would appreciate a push in the right direction. I am currently trying to touch base with an exchange admin at the local university.
We have played phone tag so far. Microsoft support is my next option.
John

Exchange 2010 Databases move alert via email

Hello Team,
We are in Exchange 2010 SP3 environment with 2 copy DAG and don't have any SCOM Server for monitoring purpose. Please help to get script which helps to alert us via email whenever any database moved from one server to another server or any database in failed
status.

Hi Jha
Thank you for your question.
You can refer to the following link and modify some code to type the correct email address by which someone was reminded, but it just reminded when your database fail .
http://ammarhasayen.com/2013/10/01/get-alert-email-when-exchange-database-is-failed-orand-not-mounted-on-the-preferred-server-activation-preference/
If this script cannot meet your requirement and you to get some alert when database moved, you can post your requirement on Exchange Development Forum by the following link:
https://social.technet.microsoft.com/Forums/en-US/home?forum=exchangesvrdevelopment&filter=alltypes&sort=lastpostdesc
If there are any questions, please let me know.
Best Regard,
Jim

Exchange 2010 database mailbox restore after restore server form disaster recovery

Hello ,
after my exchange server failed i am installed new server and recovered server
successfully, i have 4 database mailbox all this database dismount and users cannot
connect their mailbox , i have backup for all database(separate).
what should to do to restore database mailbox. so that users can connect their mailbox
thanks

Hi activenew
Thank you for your question.
After we recover the exchange successfully by using “Setup /m:RecoverServer” cmdlet, the exchange server database is in the dismount status, then we will restore the exchange database by your backup tool. After we restore database, the database
is mount, then our client can connect exchange server and send/receive email .
We can refer to the follow link:
http://exchangeserverpro.com/exchange-2010-mailbox-database-backup-restore-windows-server-backup/
We can also refer to recovering an exchange database：
http://technet.microsoft.com/en-us/library/bb124040(v=exchg.65).aspx
If there are any questions, please let me know.
Best Regard,
Jim

Exchange 2010 Databases' recovery point volume is too large.

I have DPM 2012 SP1 backing up exchange databases exclusively.
One protection group is for Exchange 2010 and the other is for exchange 2013. EseUtil.exe is only working for 2013.
The 2010 databases have gigantic recovery volumes (40 GB for a 95 GB database!) while it is less than 1 GB used for Exchange 2013 ones (55 GB replica)
The 2010 sync every one hour and the 2013 sync every 15 minutes. both have express backup at 8 PM and retention for 1 day.
is there any explanation for this behavior??
the capacity on the DPM server is limited.

Hi,
It could be page zeroing in Exchange 2010.
See this blog:
http://blogs.technet.com/b/timmcmic/archive/2013/05/20/exchange-2010-page-zeroing-and-vss-based-backups.aspx
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread. Regards, Mike J. [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.

Power outage Mailbox Database won't mount

Hello,
We have experienced a power outage, when we brought the server back the Mailbox Database wouldn't mount.
After that i ran Eseutil /mh and was on dirty shutdown, the i did /r and finally /p
Database is now on Clean shutdown state but still doesn't mount, error in event viewer:
failed. Error: The database action failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-344) ---> Microsoft.Exchange.Data.Storage.AmOperationFailedException: An Active Manager operation failed. Error: Operation failed with message: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-344) ---> Microsoft.Mapi.MapiExceptionCallFailed: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-344)
First time dealing with this problem, have i missed something?

I'm still unable to mount the Database, i've moved the logs out of the path and tried to mount with the same error.
the output of eseutil /mh
PS E:\Mailbox Database moved> eseutil /mh '.\Mailbox Database 1773415643.edb'
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 14.00
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: .\Mailbox Database 1773415643.edb
DATABASE HEADER:
Checksum Information:
Expected Checksum: 0x0122201a
Actual Checksum: 0x0122201a
Fields:
File Type: Database
Checksum: 0x122201a
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,17
Engine ulVersion: 0x620,17
Created ulVersion: 0x620,17
DB Signature: Create time:11/10/2012 19:14:18 Rand:1372720 Computer:
cbDbPage: 32768
dbtime: 279606 (0x44436)
State: Clean Shutdown
Log Required: 0-0 (0x0-0x0)
Log Committed: 0-0 (0x0-0x0)
Log Recovering: 0 (0x0)
GenMax Creation: 00/00/1900 00:00:00
Shadowed: Yes
Last Objid: 1
Scrub Dbtime: 0 (0x0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 2
Repair Date: 11/10/2012 19:14:18
Old Repair Count: 0
Last Consistent: (0x2,8,4D) 11/10/2012 20:51:35
Last Attach: (0x1,9,6C) 11/10/2012 20:51:35
Last Detach: (0x2,8,4D) 11/10/2012 20:51:35
Dbid: 1
Log Signature: Create time:11/10/2012 20:51:35 Rand:7225210 Computer:
OS Version: (6.0.6002 SP 2 NLS 500100.50100)
Previous Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Previous Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Previous Copy Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Previous Differential Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Shadow copy backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
cpgUpgrade55Format: 0
cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
ECC Fix Success Count: found (15)
Last ECC Fix Success Date: 11/10/2012 19:30:10
Old ECC Fix Success Count: found (11)
ECC Fix Error Count: none
Old ECC Fix Error Count: none
Bad Checksum Error Count: found (620)
Last Bad Checksum Error Date: 11/10/2012 19:32:24
Old bad Checksum Error Count: found (518)
Last checksum finish Date: 00/00/1900 00:00:00
Current checksum start Date: 00/00/1900 00:00:00
Current checksum page: 0
Operation completed successfully in 2.277 seconds.

Rename existing Exchange 2010 database in DAG

Hello,
I want to rename one existing database on our exchange 2010 server. This database is in DAG and hosting around 1000 users. So not possible to create a new mailbox database and move.
How can I rename the database?
After renaming it, what will happen to the Copy database on another server as it is in DAG.
Thanks,
Mihir

Appreciate your response, Andy.
To clear my doubt,
If I am ok to reseed the passive copy, then I can follow below steps, Correct?
--> Remove Passive copy
--> Remove Database files and Log files on this passive server manually
And
"1. Then will a New database with this new name be created?"
--> On Move database, I will mention same location, but just
rename .edb file. So a exact copy of new database with this new name will be created. Correct?
--> And then I can delete the old named .edb, Correct?
Thanks.

Exchange 2010 Database Corrupted Every Several Months,I/O Disk,Event 203

Hi
I am Running Exchange 2010 on Vm Machine,
Machine Profile:
16Gb Ram,4 Cpu,200 Gb Database,200 users.
Every Several months I Need To Migrate The Mailboxes To New Database,
The Old Database(After the mailboxes migration Process) always Get Error event 203,
Its Cyclic error That Occured every Serval Months To New Database.
I Am Backup Successfully The Database With Full Vss Every Day until the database get corrupted!,
The Biggest mailbox Is 10 Gb.
I Noticed That The Error Occured When The Store process Was On 17,000,000 kb/sec Persistent.
My Exchange Storage Is On Virtual San Hp Vsa.
The Strange Thing is I Have physical exchange 2010 servers in different company who serves 200 users as well,
has 200 gb database ,Less Ram Memory from my vm,
but The Big Difference is i didnt have any issues with the physical server like i have with the vm.
how can i be sure if my storage(virtual san,hp vsa) have poor issue when the exchange need to
work on high I/O ?
I Got The Event 203 When The Store Process Was On 17,000,000? is it normal?
Is My Storage Cause To My New Database Get Corrupted Because It Has Poor Performance?
thx
kobi

Thank You
How Can I Monitor/Test My Virtual San Environment To Ensure Its Function When Hosting Exchange 2010?
Can Jetstress 2010 Can Supply Me Answers To My Cyclic Problem?
Is there A Tool Or Configuration To Achieve Store Process On 17,000,000 b/Sec?

Exchange 2010 - Database issues

Good morning everyone!
I have an exchange database problem. It was first caught when implementing exchange backups with Acronis backup software.
(EXCHANGE 2010 v 14.01.0218.013)
So the backups fail one night and succeed the next. But each time it fails we get 4 errors (Consistency related). Also the database size is growing rapidly. Here are the errors:
Then a couple more:
EVENT ID 9782
Exchange VSS Writer (instance b1bfbf43-9594-4cee-980f-50d84b0ee4eb:76) has completed the backup of database 'xxxxxxxxx' with errors. The backup did not complete successfully, and no log files were truncated for this database.
Then finally:
EVENT ID 2007
Information Store (2136) Shadow copy instance 76 aborted.
For more information, click http://www.microsoft.com/contentredirect.asp.
EDIT:
SO my DB is not growing because the issue...I had forgotten that we enabled LEGAL HOLD. But my backups fail / succeed / fail / succeed.
Any ideas on this?
Kevin

Hi,
Please use Windows Server backup to backup the Exchange database to check result.
If Windows Server backup works well, I recommend you contact the third party support to confirm this issue.
If the issue persists, please check whether your database is dirty shutdown. If it's dirty, please bring to clean state and backup agian to check result.
Best regards,
Belinda Ma
TechNet Community Support

How to get Exchange 2010 database size c#

I'm trying to get smallest Exchange database in my Exchange 2010 server using remote session.
I successfully connect to my exchange server and get database with properties. Some of them with value, but Properties "DatabaseSize" with Null value for each of them.
Did some body be able to get database size value?
For me important to use URI to connect Exchange DAG.
Part of my code below:
static void Main(string[] args)
string exchangePowershellRPSURI = "http://my.domain/powershell?serializationLevel=Full";
PSCredential credentials = (PSCredential)null;
//Provides the connection information that is needed to connect to a remote runspace
// Prepare the connection
WSManConnectionInfo connInfo = new WSManConnectionInfo((new Uri(exchangePowershellRPSURI)),
"http://schemas.microsoft.com/powershell/Microsoft.Exchange", credentials);
connInfo.AuthenticationMechanism = AuthenticationMechanism.Kerberos;
connInfo.SkipCACheck = true;
connInfo.SkipCNCheck = true;
connInfo.SkipRevocationCheck = true;
// Create the runspace where the command will be executed
Runspace runspace = RunspaceFactory.CreateRunspace(connInfo);
// Add the command to the runspace's pipeline
runspace.Open();
//Represents the base functionality of a pipeline that can be used to invoke commands
Pipeline pipeline = runspace.CreatePipeline();
Command getMDB = new Command("Get-MailboxDatabase");
getMDB.Parameters.Add("Identity", "*");
getMDB.Parameters.Add("Status", null);
pipeline.Commands.Add(getMDB);
Collection<PSObject> select = pipeline.Invoke();
if (select.Count > 0)
foreach(PSObject obj in select)
var db = obj.Properties["DatabaseSize"].Value;
string name = obj.Properties["Name"].Value.ToString();
Console.WriteLine("Database Name: {0} Size: {1}", name, db);
else
Console.WriteLine("Failed to create email account");
runspace.Dispose();
Console.ReadLine();

I found solution of my problem by myself. I just changed in string
getMDB.Parameters.Add("Status", null);
"null" to "true" like this:
getMDB.Parameters.Add("Status", true);
Now everything work fine for me.

Restore Exchange 2010 Database into Restore Database in stages

I have a full backup and a number of incremental backed up using TSM.
I am trying to restore a database into a recovery DB so that I can mount an old version of a users mailbox.
To restore the full backup and all the subsequent incremental backups up to the point where the restore is required would take over 400GB, but we only have a 200GB drive to restore to.
It seems that it must be possible to:
Restore full backup + some incrementals
perform recovery to replay logs
Delete replayed logs
restore more logs
perform recovery to replay logs
Delete replayed logs
... repeat from step 4 until the database is at the right time
When I get to step 5 and try to replay the next set of logs, I seem to get various errors.
Is what I am trying to do actually possible? Apply logs in stages to a database file?
Kind Regards,
Shane

Hello Shane,
I don't think it is possible to replay the transaction logs manually once it is in Clean Shutdown state from a previous incremental backup recovery and replay. Log Required field of the database will be set to 0-0 once replay/recovery is completed and database
is set to clean shutdown state (you can verify with eseutil /mh dbpath) and then you won't be able replay the transaction logs anymore...
Probably you could just restore logs to a temp location on network attached drive and perform full restore (full + all incremental)...
For some reason you have to invoke the hard recovery manually you can use eseutil /cc "temp path of logs"
Blog |
Get Your Exchange Powershell Tip of the Day from here

I can't either mount for remove Exchange 2010 mailbox database file

Yesterday I proceeded with moving Exchange 2010 database file to a newly installed hard drive because my "C" drive was running out of space. After dismouting both the mailbox database and the public folder database, I used EMC's "move
data path" wizard to move both the mailbox database and public folder database to "mailbox" folder in "D" drive. The move was successful without an error, but when I opened "mailbox" folder in "D" drive, both
the database file and public folder database files weren't there. All the other files were moved, but the mailbox database file was gone.
Luckily I manually copied entire mailbox folder to another folder in "D" drive. So I manually copied mailbox database file (it is about 20GB) to "d:\mailbox". When I try to mount, I received the following error message.
Microsoft Exchange Error
Failed to mount database 'Mailbox Database 1658107303'.
Mailbox Database 1658107303
Failed
Error:
Couldn't mount the database that you specified. Specified database: Mailbox Database 1658107303; Error code: An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC
error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3..
An Active Manager operation failed. Error The Microsoft Exchange Replication service may not be running on server bigrock.BKSERVER.LOCAL. Specific RPC error message: Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3.
Error 0x6d9 (There are no more endpoints available from the endpoint mapper) from cli_MountDatabase3
When I try to move the database path back to the original path, I received the following error message.
Mailbox Database 1658107303
Failed
Error:
There are no source files under the path:d:\emailbox\Mailbox Database 1658107303. Use the command Move-DatabasePath -ConfigurationOnly in the Exchange Management Shell to set the new path in Active Directory only.
Exchange Management Shell command attempted:
move-DatabasePath -Identity 'Mailbox Database 1658107303' -EdbFilePath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox database 1658107303\Mailbox Database 1658107303.edb' -LogFolderPath 'c:\progam files\microsoft\exchange server\v14\mailbox\mailbox
database 1658107303'
EMC would not even delete the database file.
I need help. I need to mount my mailbox database file. Please help.

If the database was fine pre move I doubt it needs a repair, however if you want to validate do an eseutil /mh ReplaceWithYourDatabaseName.edb and post the results here
did you move the logs as well or are they still in same location
I have seen this before if everything is where its supposed to bea restart fixed it so I would recommend that you put the DB back into the NEW D path and do a restart to see if that resolves the issue
Search, Recover, & Extract Mailboxes, Folders, & Email Items from Offline Exchange Mailbox and Public Folder EDB's and Live Exchange Servers or Import/Migrate direct from Offline EDB to Any Production Exchange Server, even cross version i.e. 2003
--> 2007 --> 2010 --> 2013 with Lucid8's
DigiScope

Exchange 2010 database won't mount

Similar Messages

Maybe you are looking for