Nothing so far!Vitaliy S. wrote:Since there are no replies, it seems like this is not widely seen among our existing customers, might be something specific to this deployment. What does our support team say on this issue?
I avoided to contact them, since I am very busy with configuring two other VBR servers running under Windows Server 2012R2 and working like a charm. The real difference is only the OS.
I just found one thread here in the forum talking about some Visual C++ Runtime, that needs to be installed additionally and which does not come with VBR iirc, when you use Windows 2008R2.
Restores are generally possible, the Veeam Explorer for MS Exchange is the only problem with the upper mentioned error.
First I suspected, that it might be a memory problem, as this W2K8R2 server only has 8GB of ram, but as the related Exchange database is very very small, I neglected that, specially since all hardware requirements are fullfilled.
Regards,
Didi7