A backup has already been performed.

Get-mailboxdatabase "Test1\DBTelus" -status | fl name,mounted,*Backup*

Name : DBTelus
Mounted : True
BackupInProgress : False
SnapshotLastFullBackup : True
...
...

Somehow, the "Test1\DBTelus" fails to mount.

Get-mailboxdatabase "Test1\DBTelus" -status | fl name,mounted

Name : DBTelus
Mounted : False

Dial Tone Recovery--allow the users to send and receive e-mail quickly but restoring old mail later

Get-StorageGroup "SGTelus" | fl name,*path

Name : SGTelus
LogFolderPath : C:\Telus\Logs
SystemFolderPath : C:\Telus\Systems
CopyLogFolderPath :
CopySystemFolderPath :

Get-MailboxDatabase "DBTelus" | fl Name,*path

Name : DBTelus
CopyEdbFilePath :
EdbFilePath : C:\Telus\Mailbox\DBTelus.edb

mv c:\telus\systems c:\backup\systems
mv c:\telus\logs c:\backup\logs
mv c:\telus\mailbox c:\backup\mailbox

#When you mount the DBTelus database, an empty database is created. The users who have mailboxes on DBTelus database can send and receive e-mail, except they cannot access the old e-mail, for now.

Mount-Database "DBTelus"

Restore the old e-mail

Database Recovery Management Tool

Complete the Wizard.

Run Restore software. I use the Symantec 12.5 with following options:

When I use the MS NTbackup utility, it can restore the backup directly to the Restore Storage Group.

Mount-Database "Test1\Recovery Storage Group\DBTelus"

Why do we swap? why don't we directly perform the merge or copy task?

For a large database, running the merge or copy wizard will take a long time. When the Recovery Storage Group and the original storage group are in the same logical drive, the swap is instantaneous--the actual content does not move.

Then, run the merge or copy wizard. This process will not take long because the newly-created-database is small.

Complete the wizard.