Replay transaction logs to a new empty mailbox database

My Exchange 2010 mailbox database got corrupted and do not really have a good backup to recover from and it is not a DAG too.
Using eseutil log files are good but if I do soft recovery, it complains of a missing log file. Going through the log files it is just one file that is missing and even checking the creation date for this file at that time the server was offline because
we were relocating.
Soft recovery has not been successful.
I want to try hard recovery but do not know how much data will be lost. Or better still is there a way to replay log files of the corrupted database into the new database and continue from there?

Without having a good backup, you can not ensure about the security of data that would be recovered.
If you have an old backup of the database and all transaction log files since that backup then you can restore everything up to the last transaction log file.
If you want to do it in the RSG then you can copy all transaction log files from the production storage group to the log file directory of the RSG, then restore you last backup and let the backup program mount the database. Exchange will automatically replay
the log files in the RSG directory and the files on the tape. Please follow this Library : http://technet.microsoft.com/en-us/library/aa998370(EXCHG.65).aspx
If you still unable to recover the data manually, you may consider on this automated software (http://www.exchangeserverrecovery.com/) that might be helpful to recover the data without any losses and resolve
your purpose.

Similar Messages

Cannot Remove empty Mailbox Database

Hi All,
I got following error.
Microsoft Exchange Error
The mailbox database 'MDB3' cannot be deleted.
MDB3
Failed
Error:
This mailbox database is associated with one or more active MailboxExport requests. To get a list of all MailboxExport requests associated with this database, run Get-MailboxExportRequest | ?{ $_.RequestQueue -eq "<Database ID>" }. To remove
a MailboxExport request, run Remove-MailboxExportRequest <Recipient ID\Request Name>.
run Get-MailboxExportRequest | ?{ $_.RequestQueue -eq "<Database ID>" }
Name
Mailbox
Status
MailboxExport
InProgress
So how do i remove this?
AS

Hi,
There were couple of Export requests pending for this database. Get-MailboxExportRequest command was giving me "Cannot perform searches outside the scope" error.
Here are the commands I executed to resolve this issue.
1. Set-AdServerSettings -ViewEntireForest $True
2. Get-MailboxExportRequest -Database "Database Name" | Remove-MailboxExportRequet
3. Remove-MailboxDatabaseCopy -identity "Database Name"
Database was successfully removed after executing these commands.
or
Get-MailboxExportRequest | remove-mailboxexportrequest
Deepak Kotian.
MCP, MCTS, MCITP Exchange 2010 Ent. Administrator
Disclaimer:
Please take a moment to "Vote as Helpful" and/or "Mark as Answer", where applicable.
This helps the community, keeps the forums tidy, and recognizes useful contributions. Thanks
All the opinions expressed here is mine. This posting is provided "AS IS" with no warranties or guarantees and confers no right

Exchange 2010 Excessive Archive Transaction Logs

I've got an Exchange 2010 environment with about 225 users over 6 mailbox DB's with corresponding Archive DB's.
They're seeing log files for the archive DB's growing by about 25-30% of the total DB size daily. Those logs are generally about 8 x the logs generated by the corresponding primary mailbox database.
Something like
DB1 = 20GB daily average logs 2GB
DB1Archive = 90GB daily average logs ~28GB
I don't see any Retention policies that have duplicated Tags and the Default policy has no tags assigned.
The customer wants to continue with their existing backup process of weekly fulls and daily incremental/differentials, and missing two days is enough to max out their transaction log volumes. (which are as large as their combined database size).
The archive db's have been in place for at least 12 weeks now so it's not just initial population, which is obvious by the fact that the archive db's are much larger than the original db's and the total logs in a week exceed the DB volumes by 2-3 times.

Hi,
First, please make sure there is no corruption in the retention policies.
If there is no corruption, I recommend you create a new archive mailbox database and move archive mailbox to this new database to check result.
Besides, here is a similar thread for your reference.
http://social.technet.microsoft.com/Forums/en-US/77845ba9-96c4-4b94-8d55-b47c51ef8974/exchange-2010-archive-transaction-logs?forum=exchange2010
Hope this is helpful to you.
Best regards,
Belinda Ma
TechNet Community Support

Big transaction log file

Hi,
I found a sql server database with a transaction log file of 65 GB.
The database is configured with the recovery model option = full.
Also, I noticed than since the database exist, they only took database backup.
No transaction log backup were executed.
Now, the "65 GB transaction log file" use more than 70% of the disk space.
Which scenario do you recommend?
1- Backup the database, backup the transaction log to a new disk, shrink the transaction log file, schedule transaction log backup each hour.
2- Backup the database, put the recovery model option= simple, shrink the transaction log file, Backup the database.
Does the " 65 GB file shrink" operation would have impact on my database users ?
The sql server version is 2008 sp2 (10.0.4000)
regards
D

I've read the other posts and I'm at the position of: It really doesn't matter.
You've not needed point in time restore abilities inclusive of this date and time since inception. Since a full database backup contains all of the log needed to bring the database into a consistent state, doing a full backup and then log backup is redundant
and just taking up space.
For the fastest option I would personally do the following:
1. Take a full database backup
2. Set the database recovery model to Simple
3. Manually issue two checkpoints for good measure or check to make sure the current VLF(active) is near the beginning of the log file
4. Shrink the log using the truncate option to lop off the end of the log
5. Manually re-size the log based on usage needed
6. Set the recovery model to full
7. Take a differential database backup to bridge the log gap
The total time that will take is really just the full database backup and the expanding of the log file. The shrink should be close to instantaneous since you're just truncating the end and the differential backup should be fairly quick as well. If you don't
need the full recovery model, leave it in simple and reset the log size (through multiple grows if needed) and take a new full backup for safe keeping.
Sean Gallardy | Blog |
Twitter

Shared Disk solution for Transaction Logs and JMS?

          In a machine failure, two key resources for a clean recovery are the Transaction Logs
          and the JMS Store.
          The WebLogic Server Administration Guide discusses moving the Transaction Logs to
          a new machine before starting a failed WLS server on that machine in order to achieve
          a clean recovery.
          It suggests use of "a dual-ported disk available to both machines."
          I'm looking for such a solution.
          We currently use Veritas Cluster Server to manage our Database environment, but I
          am concerned it is too expensive or too comprehensive a solution for the size of
          the Transaction Logs and the complexity of the problem.
          Has anyone implemented a solution to achieve high availability of the Transaction
          Logs and JMS Store?
          Can you recommend solutions I should be looking into, in addition to Veritas?
          Thanks,
          Steve Tahmosh
          Sovereign Bank
          617 533-1258


Sully,
OK, I am just about as frustrated as I can get. I'm doing everything that you said, at least as far as I can tell, but all of my Windows machines (two XP, one Vista) are asking me for a username and password and then saying they can't connect.
Any help would be appreciated.
Mitch

Pb moving transaction log with DS5.2

Hi,
I don't manage to change the transaction log directory : my ldap server can't restart. I did the following tasks :
- i stopped the server
- i modified the dse.ldif by hands :
nsslapd-db-logdirectory: /data/slapd-siu/tlog
- i moved the transaction log file (log.0000000001) which was in the previous directory, in that directory
- i tried to start the server : it failed
Any ideas ?
Has someone succeded in moving the transaction log with DS 5.2 ?
Thank you

i have solved my pb : i copied the transaction log files under "root" and my server is running under "ldapuser" : with a chown ldapuser on the transaction log in the new directory i was able to start my server.

Recreate user account in Workgroup Manager, empty mailbox

We have OS X 10.3.8 Server version. Postfix mail server.
We have a user/account with email problems and a huge mailbox. He (user: gordon) had over 16000 emails in his mailbox (/var/spool/imap/user/gordon). All other mail users on this server work fine, including newly created user accounts.
Our solutions was to try and delete all mail from his mailbox via Terminal. This did not seem to decrease the size of his mailbox. Our next idea was to delete this user in Workgroup Manager and then re-created this user. Hoping to created an new mail setup and empty mailbox. This idea failed aswell.
How does one basically purge an old account/user in Workgroup Manager, and then, recreate that same user name and effectively recreate the user with a new account, including a new/empty mailbox?
Mac OS X (10.3.8)

cyradm is not part of 10.3.x
To use it you would have to install it first. See here:
http://www.afp548.com/article.php?story=20040814204411280&query=cyradm
And then follow the instructions given beforehand.
Having said that, your issue can be resolved differently. You deleted all mail manually in the file system (not a good idea, but what is done is done). So the mail is actually gone. What you are seing is Cyrus' index. Since you deleted manually the index didn't get updated. To get rid of the problem either reconstruct that users mailbox throgh Server Admin - > Mail or alternatively run:
sudo -u cyrus reconstruct -r user/gordon (assuming that's the user's name)
Alex

SQL Server Database - Transaction logs growing largely with Simple Recovery model

Hello,
There is SQL server database on client side in production environment with huge transaction logs.
Requirement :
1. Take database backup
2. Transaction log backup is not required. - so it is set to Simple recovery model.
I am aware that, Simple Recovery model also increases the transaction logs same as in Full Recovery model as given on below link.
http://realsqlguy.com/origins-no-simple-mode-doesnt-disable-the-transaction-log/
Last week, this transaction log became of 1TB size and blocked everything on the database server.
How to over come with this situation?
PS : There are huge bulk uploads to the database tables.
Current Configuration :
1. Simple Recovery model
2. Target Recovery time : 3 Sec
3. Recovery interval : 0
4. No SQL Agent job schedule to shrink database.
5. No other checkpoints created except automatic ones.
Can anyone please guide me to have correct configuration on SQL server for client's production environment?
Please let me know if any other details required from server.
Thank you,
Mittal.

@dave_gona,
Thank you for your response.
Can you please explain me this in more details --
What do you mean by one batch ?
1. Number of rows to be inserted at a time ?
2. or Size of data in one cell does matter here.
As in my case, I am clubbing together all the data in one xml (on c# side) and inserting it as one record. Data is large in size, but only 1 record is inserted.
Is it a good idea to shrink transaction log periodically, as it is not happening itself in simple recovery model.
HI Mittal,
Shrinking is bad activity yu should not shrink log files regularly, in rare case if you want to recovery space you may do it.
Have manual chekpoints in Bulk insert operation.
I cannot tell upfront what should be batch size but you can start with 1/4 th of what you are currently inserting.
Most important what does below query return for database
select log_reuse_wait_desc from sys.databases where name='db_name'
The value it returns is what stopping the log from getting cleared and reused.
What is version and editon of SQl server we are talking about. What is output of
select @@version
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Wiki Article
MVP

OAV-9016 - Audit Vault 12.1.1 error creating audit trail with TRANSACTION LOG

Hey guys,
I bumped into this problem when trying to start an audit trail with TRANSACTION LOG.
Oracle Audit Vault and Database Firewall 12.1.1.1
Oracle 11gR2 RAC two nodes, OEL x64.
Connection String:
jdbc:oracle:thin:@//192.168.1.139:1521/orcl
I have already ran the sql setup for a REDO_COLL user.
Any ideas?
I have created secure target for each node.
(host01)(oracle@orcl1):log> pwd
/u01/app/oracle/agent/av/log
(host01)(oracle@orcl1):log> cat av.collfwk-8311-0.log
[2013-12-12T17:16:49.855-02:00] [collfwk] [ERROR] [] [] [tid: 22] [ecid: 192.168.1.109:27132:1386867392018:0,0] OAV-9016: Target database global_name is not correct. global_name must include the domain for transaction log collection. Please configure the target database with the correct global_name.CollectionFactory : createCollection : Exception while creating collection. [[
Target database global_name is not correct. global_name must include the domain for transaction log collection. Please configure the target database with the correct global_name.
        at oracle.av.platform.agent.collfwk.impl.redo.RedoCollector.checkDBName(RedoCollector.java:1480)
        at oracle.av.platform.agent.collfwk.impl.redo.RedoCollector.verifySource(RedoCollector.java:1278)
        at oracle.av.platform.agent.collfwk.impl.redo.RedoCollector.startCollector(RedoCollector.java:215)
        at oracle.av.platform.agent.collfwk.impl.redo.RedoCollectorManager.startTrail(RedoCollectorManager.java:199)
        at oracle.av.platform.agent.collfwk.impl.factory.CollectionFactory.createCollection(CollectionFactory.java:504)
        at oracle.av.platform.agent.collfwk.impl.factory.CollectionFactory.createCollection(CollectionFactory.java:354)
        at oracle.av.platform.agent.StartTrailCommandHandler.processMessage(StartTrailCommandHandler.java:63)
        at oracle.av.platform.agent.AgentController.processMessage(AgentController.java:325)
        at oracle.av.platform.agent.AgentController$MessageListenerThread.run(AgentController.java:1859)
        at java.lang.Thread.run(Thread.java:722)
(host01)(grid@+ASM1):~> lsnrctl status
LSNRCTL for Linux: Version 11.2.0.3.0 - Production on 12-DEC-2013 17:27:34
Copyright (c) 1991, 2011, Oracle. All rights reserved.
Connecting to (DESCRIPTION=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER)))
STATUS of the LISTENER
Alias                     LISTENER
Version                   TNSLSNR for Linux: Version 11.2.0.3.0 - Production
Start Date                12-DEC-2013 16:58:03
Uptime                    0 days 0 hr. 29 min. 31 sec
Trace Level               off
Security                  ON: Local OS Authentication
SNMP                      OFF
Listener Parameter File   /u01/app/11.2.0/grid/network/admin/listener.ora
Listener Log File         /u01/app/grid/diag/tnslsnr/host01/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=ipc)(KEY=LISTENER)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.109)(PORT=1521)))
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=192.168.1.139)(PORT=1521)))
Services Summary...
Service "+ASM" has 1 instance(s).
Instance "+ASM1", status READY, has 1 handler(s) for this service...
Service "orcl" has 1 instance(s).
Instance "orcl1", status READY, has 1 handler(s) for this service...
Service "orclXDB" has 1 instance(s).
Instance "orcl1", status READY, has 1 handler(s) for this service...
The command completed successfully
(host01)(grid@+ASM1):~>
(host01)(grid@+ASM1):~> cat /u01/app/11.2.0/grid/network/admin/listener.ora
LISTENER=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER))))            # line added by Agent
LISTENER_SCAN3=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN3))))                # line added by Agent
LISTENER_SCAN2=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN2))))                # line added by Agent
LISTENER_SCAN1=(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=IPC)(KEY=LISTENER_SCAN1))))                # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN1=ON                # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN2=ON                # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER_SCAN3=ON                # line added by Agent
ENABLE_GLOBAL_DYNAMIC_ENDPOINT_LISTENER=ON              # line added by Agent
(host01)(grid@+ASM1):~>

Hi
Just run the script $AV_AGENT/av/plugins/com.oracle.av.plugin.oracle/config/oracle_user_setup.sql USER_NAME REDO_COLL
This will grant the user some privileges and roles like DBA and CREATE Database Link
I hope this answer your question
Thanks
Ahmed Moustafa

After move mailbox to another mailbox database the mailbox database has not free space

Hi,
If any one can help me about that question I appreciate:
- I have an Exchange Server 2010 mailbox database with 300 users.
- I moved the mailboxe to a new mailbox database.
- I have checked that the empty mailbox database did not release the free space from mailboxes moved
The question is: should I wait for the retention time be finished and the the maintence job be done?
Thanks a lot.
Luiz

Hi
Even when the retention time expires the edb file will not reduce in size automatically. You will need to run an offline defrag at that point ... which is actually not recommended.
It would be better to move all the mailboxes to a new database and delete the old one.
Steve

Transaction logs after large mailbox archive?

Hi all,
I've recently run a large mailbox archive on our mailbox database and I'm concerned about the transaction log files that will be produced.
Some info: We run a single Exchange server on Windows Server 2008, on a single hard disk. The system is run on VMWare with a full Exchange-aware backup run every night. Database file is currently 194GB with about 90GB whitespace.
I archived 20GB worth of email from a mailbox. My problem is that the hard disk with the database and log files on it only has 12GB of free space, so when the Recoverable Items folder is cleared 2 weeks later, is there going to be 20GB of transaction logs
with nowhere to go? Will I have to organise some additional storage to give the log files some room?
Appreciate any help.

Hi,
I notice that there only 12 GB free disk in your mailbox server, it may be too small.
Exchange will not generate much more transaction log when delete Recoverable Items, however it also not delete previous transaction log. Meanwhile, Exchange will generate new log when mail flow and move message to archive database, the size of transaction log
only grow. Therefore, I recommend to add additional disk or full backup for your database on schedule to truncated some unrequired logs.
Here’s the article about Mailbox Server Storage Design, for your reference:
https://technet.microsoft.com/en-us/library/dd346703(v=exchg.141).aspx
Best Regards,
Allen Wang

Movemailbox issue: new empty calendar folder gets created after mailbox move

Hi,
when doing mailbox moves between Exchange 2010 and Exchange 2013 (CU3 and SP1) and also between two Exchange 2013 SP1 servers we experience the following issue:
sometimes a new empty default calendar folder is being created after the mailboxmove completes. Out of 230 moved mailboxes 6 mailboxes experienced this issue. For some reason the existing calendar folder is changed to a user created folder and a new
calendar folder gets being created. This causes some panic by the affected users, since they suddenly notice that their calendar is completely empty. The free/busy information other people see is also empty because they also see the empty calendar.
To correct the issue I have to manually move the items from the original calendar folder to the newly created calendar folder.
Any idea what might cause this? I don't have reproduction steps, it just happens at random during the mailbox move. The moverequest completes succesfully, no errors are reported and the movereport also doesn't contain any clues.
Frank.

But outlook wasn't running, so outlook couldn't have created the new calendar folder. I did the mailbox move out of office hours. Right after the mailbox move completed I ran the 'get-mailboxfolderstatistics' cmdlet. When looking at the output I search
for 'user created' calendar folders called 'Calendar'. The mailboxes that were affected also had another 'Calendar' folder of the type 'Calendar'. This is the newly created folder. So the mailbox contains two folders called 'Calendar' after the move. Although
I can't reproduce it, I'm able to detect when it happened by looking at the output of the above cmd-let.

Restoring Mailbox data through Transaction logs

Hello all,
We're running Exhange server 2007 on a dedicated VM.
We're currently running Tri-Daily VM backups and Daily backups via tape in 1 set, and 4 weekly sets of tapes.
Our issue is that now the tape drive has broken and we're trying to source a replacement and or repair of the tape drive, we need to work out how we're going to restore lost data without having to purchase more hardware for VM backups for dailys.
We know that transaction logs can be used to roll forward to a point in time of when the last VM backup was taken, to the time the server went down. to restore as many lost emails as possible.
Our SLA to our users is currently 2-48 hours of lost data on the system, but we'd like to limit this as much as possible, and as it's tri-daily, we run the risk of over running that SLA.
So the main question is, how would we roll our database forward using the transaction logs?

Great link from Ed and regarding rolling logs there are a few things to keep in mind.
1. in order to use ESEutil to roll logs you MUST have a database that is in a dirty/inconsistent state, i.e. system stopped abruptly (was not shut down gracefully) or an Exchange aware backup was made and you are able to restore the DB to disk without rolling
up or mounting the DB.
2. You can only rollup/apply a set of logs to a dirty DB one time, i.e. lets say you have a backup of the DB that is still dirty and the backup was from 1/1/2014 and you have logs up through today 3/11/2014. So you could then make a copy of the logs
through say 1/31/2014 and use eseutil to roll them up and bring the db to a consistent/clean state.
3. However if you want to rollup data through say 2/15/2014 you cannot do so with the DB that was rolled up to 1/31/2014 in step 2 because that DB is now in a clean/consistent state and therefore it will not accept additional log rollup for the logs through
2/15/2014. To solve this you would need to do the following;
A: get a copy of the 1/1/2014 EDB that is dirty/inconsistent
B: copy the logs from 1/14 to 2/15 into a separate directory
C: Roll the logs into the DB using eseutil.
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

Best practice for default location of mailbox database(s) / logs

Hello,
I don't recall seeing any options during the Exchange 2013 install, to specify an alternate location for either the mailbox database or log files. I've reviewed the commands for moving the mailbox databases, but before reviewing the options for setting a
location for the log files, I thought it best to see whether it's still advised to separate log/mailbox databases away from the OS, with our Exchange server being a virtualised instance?
Also, I'm assuming that Exchange still requires the usual backup of transaction logs, for them to be cleared?
Many thanks.

Hi JH,
here is a link to storage options and requirements for the Mailbox server :
http://technet.microsoft.com/en-us/library/ee832792(v=exchg.150).aspx
By default when installing New Exchange server With mailbox role,it will create default database and log path.
Recomended is to have Database and Log files on seperate disks.You will have to attache those disk first,then you can create New database using ECP.
Please look at my Gallery With full guide on how to setup New Exchange server.
http://gallery.technet.microsoft.com/Install-Exchange-server-b5cce9e4
Also for future use you might need to clean up log files to free up Space on Your Exchange server:
http://gallery.technet.microsoft.com/Task-Scheduler-to-cleanup-25047622
Hope this helps
Please mark as helpful if you find my contribution useful or as an answer if it does answer your question. That will encourage me - and others - to take time out to help you. Thank you! Off2work

Moving Exchange 2010 Transaction Log

Hi. Running a single instance of SBS2011 with Exchange 2010. We only have one mailbox.
Earlier today I moved our main exchange database (.edb) file to a different hard drive. Used EMC, went through smoothly, no issues.
I then started moving the transaction logs. Same process:
Exchange Management Console > Organization Configuration > Mailbox > Move
Database Paths
This appeared to be going fine but after 40 mins came up with an error along the lines of "WinRM cannot process the request in the time specified"
Now I cant access any mailboxes. OWA giving the error - Your mailbox appears to be unavailable. Try to access it again in 10 seconds. If you see this
error again, contact your helpdesk
I have checked in EMC and the mailbox is successfully mounted. I have restarted all exchange services.
I also now have 8.5GB of log files in the "new" location. Not if these are just copies or exchange is actually using this drive.

Hi:
I think you may be over complicating this. SBS includes a wizard in the SBS Console to move most/all of the user impacted data stores, including Exchange, SharePoint, WSUS and Redirected folders. The transaction logs are limited in size if you
use either the SBS backup or a third party backup that is "Exchange Aware" to backup the server or the Exchange subsystem, so there is really no need to move the logs, assuming you are making good backups.
Larry Struckmeyer[MVP] If your question is answered please mark the response as the answer so that others can benefit.

Replay transaction logs to a new empty mailbox database

Similar Messages

Maybe you are looking for