It would appear that Veeam does not play well with volume mount points. At a recent project, we migrated into a new Exchange 2010 environment using volume mount points attached to c:\volmtpt – Veeam would see the empty folder, but never the contents.
We were providing the the raw drive space with RDM. So we tried the same drive space, but mounted as a direct drive. Veeam could not see that either. Veeam support forums hinted that RDM may or may not work – apparently depending on the phase of the moon. There are some folks who claim to have it working – but not me.
In the end, we went with raw drive space vmdk. Now it works as expected. But what if you don’t want 24 drive letters? Or even more than 1? Windows Server Backup, in the same scenario had no issues with the mount point construction.
WASSUP WID DIS?
YMMV
No comments:
Post a Comment