Export (0) Print
Expand All
2 out of 3 rated this helpful - Rate this topic

Perform a Dial Tone Recovery

Exchange 2010
 

Applies to: Exchange Server 2010 SP3, Exchange Server 2010 SP2

Topic Last Modified: 2011-03-19

Using dial tone portability, users can have a temporary mailbox for sending and receiving e-mail while their original mailbox is being restored or repaired. The temporary mailbox can be on the same Exchange 2010 Mailbox server or on any other Exchange 2010 Mailbox server in your organization. The process for using dial tone portability is called a dial tone recovery, which involves creating an empty database on a Mailbox server to replace a failed database. To learn more, see Dial Tone Portability.

You must have fewer than the maximum number of databases deployed to create a dial tone database. Exchange 2010 Standard Edition supports a maximum of 5 databases per server. Exchange 2010 Enterprise Edition supports a maximum of 100 databases per server.

You need to be assigned permissions before you can perform this procedure. To see what permissions you need, see the "Mailbox recovery" entry in the Mailbox Permissions topic.

noteNote:
You can't use the EMC to perform a dial tone recovery on a single server.
  1. Make sure that any existing files for the database being recovered are preserved in case they're needed later for further recovery operations.
  2. Use the New-MailboxDatabase cmdlet to create a dial tone database, as shown in this example.
    New-MailboxDatabase -Name DTDB1 -EdbFilePath D:\DialTone\DTDB1.EDB
    
  3. Use the Set-Mailbox cmdlet to rehome the user mailboxes hosted on the database being recovered, as shown in this example.
    Get-Mailbox -Database DB1 | Set-Mailbox -Database DTDB1
    
  4. Use the Mount-Database cmdlet to mount the database so client computers can access the database and send and receive messages, as shown in this example.
    Mount-Database -Identity DTDB1
    
  5. Create a recovery database (RDB) and restore or copy the database and log files containing the data you want to recover into the RDB. For detailed steps, see Create a Recovery Database.
  6. After the data is copied to the RDB, but before mounting the restored database, copy any log files from the failed database to the recovery database log folder so they can be played against the restored database.
  7. Mount the RDB, and then use the Dismount-Database cmdlet to dismount it, as shown in this example.
    Mount-Database -Identity RDB1
    Dismount-Database -Identity RDB1
    
  8. After the RDB is dismounted, move the current database and log files within the RDB folder to a safe location. This is done in preparation for swapping the recovered database with the dial tone database.
  9. Dismount the dial tone database, as shown in this example. Note that your end users will experience an interruption in service when you dismount this database.
    Dismount-Database -Identity DTDB1
    
  10. Move the database and log files from the dial tone database folder into the RDB folder.
  11. Move the database and log files from the safe location containing the recovered database into the dial tone database folder, and then mount the database, as shown in this example.
    Mount-Database -Identity DTDB1
    
    This ends the service interruption for your end users. They will be able to access their original production database and send and receive messages.
  12. Mount the RDB, as shown in this example.
    Mount-Database -Identity RDB1
    
  13. Use the Get-Mailbox and Restore-Mailbox cmdlets to export the data from the RDB and import it into the recovered database, as shown in this example. This will import all the messages sent and received using the dial tone database into the production database.
    Get-Mailbox -Database DTDB1 | Restore-Mailbox -RecoveryDatabase RDB1
    
  14. After the restore operation is complete, you can dismount and remove the RDB, as shown in this example.
    Dismount-Database -Identity RDB1
    Remove-MailboxDatabase -Identity RDB1
    

For detailed syntax and parameter information, see the following topics:

 © 2010 Microsoft Corporation. All rights reserved.
Did you find this helpful?
(1500 characters remaining)
Thank you for your feedback

Community Additions

ADD
Show:
© 2014 Microsoft. All rights reserved.