This post is more than 5 years old
10 Posts
0
1787
October 9th, 2012 11:00
Can't add .vmdk from replication destination to VM
I've got a replication destination and I want to mount the .vmdk to a VM as read-only. I have the datastore marked as read-only and the host can see it, but when I edit the settings for the VM to add it, it won't "see" it. What am I missing? Does vSphere make changes to the .vmdk when it is added to a VM?
No Events found!
tgraves1
22 Posts
0
December 27th, 2012 06:00
In order to use the replication destination for testing, you'll need to create a snapshot on the destination side and promote that snapshot. The promoted NFS snapshot will then be accessible by your ESX hosts and used as an additional datastore. Changes made to that writable snapshot will be stored in your Protection Reserve space for the original VMware Storage Resouce.
The ability to promote snaps for NAS-based Storage Resources is only available with Vmware NFS Datastores currently.
JoshRountree1
10 Posts
0
December 27th, 2012 05:00
It was an NFS datastore. I have since changed direction on this project. We were trying to use VNXe replication from Unisphere for Disaster Recovery and I'm not so sure that is how it was intended to be used. I was doing some DR testing and wanted to use the replicated datastore, but I couldn't mount it. I'm now using Veeam instead.