Microsoft System Center DPM 2012 R2 - Exchange Backup Error

When you try to backup Exchange Databases , the backup fail ,
with this error :

Data consistency verification check failed for LOGS of Exchange Mailbox Database $DBNAME on $EXCHANGESERVER. (ID 30146 Details: Unknown error (0xc0000135) (0xC0000135))

I immediatly thought something is not right with eseutil.exe that handle the verification,
so when I tried to run eseutile.exe , I got this error :

The program can't start because MSVCR110.dll is missing from your computer. Try reinstalling the program to fix this problem.

the best solution to fix this problem is to download and install

Visual C++ Redistributable for Visual Studio 2012 Update 4

http://www.microsoft.com/en-us/download/details.aspx?id=30679

QNAP does not work with SCVMM 2012 !

Today, I kept trying to add QNAP TS-879 Pro as a storage device using System Center Virtual Machine Manager (SCVMM 2012) but I failed every time, after doing lots of research I found that QNAP does not support SMI-S protocol which is needed to connect SCVMM to SAN devices.

SMI-S basically defines a method for the interoperable management of a heterogeneous Storage Area Network (SAN).


This is a bad news to to me, If I knew this is the case , I will not buy QNAP for our Hyper-V infrastructure.
so my advise is to look for another SAN that support SMI-S. Don't buy QNAP until they implement this feature and you can add your request/ vote for this feature :
http://forum.qnap.com/viewtopic.php?f=24&t=42395&p=238573#p238573

XenServer the nfs server version is unsupported .

after a power failure , one xenserver powered off and when it came back again, it couldnt connect to the pool storage , I tried to repair the storage but I kept getting this error:
 the nfs server version is unsupported 



I rebooted the pool master hoping that this will fix the issue , but it made it worse, the pool master also lost the connection to the storage, I rebooted the networking switch , this didn't fix the problem either, the last step I did , was to reboot the storage device and then the repair worked.

I hope this will help anyone who face this problem, I searched google and bing for a solution and i couldn't find few old articles that didn't help.