When you are trying to recover a database in WSB, we select “Recovery type – Exchange” then “Select application to recover – Exchange”. I want to ask how would exchange know if you want to recover databases or log files? From what I described earlier, Exchange attempts to recover the databases. How can I recover the log files from a full backup?

Thanks.

Sounds like you’ve used database portability to recover the databases on a new server that has a different name. You can find a TechNet article on how to complete that process, or if you’re stuck and this is an outage for your users I recommend you open a support case with Microsoft so that they can give you the correct guidance.

I copied DBs folder and past it in an new virtual sever.
I Installed a new exchange in the new server (it’s ok, I mean it syncronized with my ADDS)

I used Win serv Backup to recover database files in the Mailbox folder.
the exchange management consol can see my recovered DBs.
I mounted in succesfuly.

The ISSUE is that I dont know how to link users to their mailboxes.

Help please.

God Says “my people is dying because of lake of knowledge” some hting like that…….

Hi Jason, this seems relevant to your question. I’m not 100% sure of the answer, because I don’t run any scenarios like yours.

https://technet.microsoft.com/en-us/library/dn798286(v=ws.11).aspx

I have a 2012 Host (not R2) that has a dedicated guest VM for Exchange 2013. The Windows Server Backup is on the host and runs fine but will not truncate the VM Exchange logs. I’ve changed the backup to exclude the System State and Bare Metal but nothing.

Is this possible from the Windows Server Backup, or should I do something different. I was thinking of backing up from within the VM to a n attached Virtual Disk just to truncate the logs.

Any suggestions please?

Jas

VM replication isn’t a backup, and won’t truncate logs. It’s also quite unsuitable for a range of data recovery scenarios. Aside from that VM replication is not supported for Exchange servers. Exchange has DAGs for DR purposes, and you should use that instead.

My boss think backup the active database may cause impact (such as system slow down , sort of…). So, insist only backup the passive one.

Is there any different (especially when need restore) between backup the active copy and the passive copy database?

What’s required, and supported, is to back up the active database copy. That will trigger log truncation, and that is what is supported for recovery.

The question is, which db copy is active at the time of the backup? In a neatly controlled environment you’ll expect that specific copies will be active. But what if there’s been a fault and the db activated on a different server? What if some copies on a volume are active and some are passive (note: multiple databases per volume is recommended, but complicates Windows Server Backup restores). To account for that you would backup every volume with every copy regardless of whether it’s active or passive.

The passive copies aren’t entirely useless. You can mount them in a recovery database if necessary. But you shouldn’t rely on them, you should still take backups of the active copy.