Windows 2012 R2 & Exchange 2013 SP1 CU3 - DB Corrupted

Problem:
Exchange 2013 mailbox store will not mount after Windows 2012 R2 Upgrade.

Environment:
Windows 2012 Server, upgraded to Windows 2012 R2 Server

NOTE: If your doing a new install make sure to install Windows 2012 R2 Server then exchange. Do not install Windows 2012 server, then install Exchange 2013. After testing you install R2 Update, this will break your exchange. 

Can not mount the database, get the following error:

Log Name:      Application
Source:        ESE
Date:          3/13/2014 1:17:09 PM
Event ID:      613
Task Category: Table/Column/Index Definition
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:     
Description:
Information Store - Mailbox Database 0710374762 (7916) Mailbox Database 0710374762: Database 'C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 0710374762\Mailbox Database 0710374762.edb': The primary index 'GlobalsPK' of table 'Globals' may be corrupt. If there is no later event showing the index being rebuilt, then please defragment the database to rebuild the index.


Resolution:

1. Run CMD or command line as Administrator
2. Stop the Microsoft Exchange Information Store Service
    run: net stop MSExchangeIS

3. Execute the database repair:
  c:\Program Files\Microsoft\Exchange Server\V15\Bin>eseutil /p "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 0710374762\Mailbox Database 0710374762.edb"

4. Execute database defragment:
c:\Program Files\Microsoft\Exchange Server\V15\Bin>eseutil /d "C:\Program Files\Microsoft\Exchange Server\V15\Mailbox\Mailbox Database 0710374762\Mailbox Database 0710374762.edb"

5. Start the Microsoft Exchange Information Store Service
    run: net start MSExchangeIS

If your store does not mount you might need to fix your logs.

Veeam backups fail - NFC storage connection is unavailable

If your backups are running fine and then stop all of a sudden with the following error message:

Processing 'VM-NAME' Error: Client error: NFC storage connection is unavailable. Storage: [stg:datastore-192,nfchost:host-188,conn:vSphere-Name.fqdn]. Storage display name: [DS03].
Failed to create NFC download stream. NFC path: [nfc://conn:vSphere-Name.fqdn,nfchost:host-188,stg:datastore-192@VM-NAME/VM-NAME-01.vmx].

You checked Veeam KB 1198 and it does not help, all your backup repertoires are there and accessible. Most likely it is a problem with the vCenter Server.

Solution:
Log into your VMware vShphere server and restart the "VMware VirtualCenter Server"
Run your backups now :)