just got an email today that support has now raised a bug for this issue. It is very disappointing to see how unstable NetApps newest products are. We also have issues to get SnapManager for Exchange,SQL to update to initiate a Snapvault snapshot. Until now it's not even clear if this is supported under CDot. To me CDOT is an unfinished product as most of the things that used to work great under 7Dot are either no longer working or no longer supported. We strongly consider to move away from NetApp products.
I have VSC 5.0GA I believe. But there was a problem with NetApp NFS in 5.5U1. So I have skipped that. Luckily 5.5U1b fixes that problem. I will have my ESX updated and give it a try. I wonder why it doesn't work with the default labels? I will report if it works. Just struggling with another VMware <-> NetApp issue where SMVI puts VMs to "disk consolidation needed" state after a backup job has run.
Followed your howto but coudn't get it to work, even with the custom labels.
<< I had to add the destination Cluster hostname and management IP in the DNS so that VSC could resolve the destination system. Should probably work with entries in the host file of the VSC. >>
I guess this could be my problem. I have a DNS record for the destination system that can be resolved from the VSC host. Do you have any clue what ports need to be opened between the VSC host and the destination storage system?
Thanks for that. Would be good to know which ports are actually needed from VSC to the filer. VSC and VC are on the same subnet, so there are no blocking firewall rules, but the filer sits on a different subnet with a firewall in between. So far we had http, https and port 623 open. I ran wireshark on the VSC host to see if it tries to communicate with the destination filer as soon as I trigger an ondemand backup job from VSC but there is just nothing...
NetApp Support had a good idea. I had to add the Snapvault destination filer in VSC. Now it works with the custom labels as well as with the default ones. However OnCommand System Manager still shows that there are no valid snapmirror labels. And another bad thing is that the naming scheme on snapvault destination filer doesn't contain "_recent" for the latest transferred snapshot. This makes it impossible to backup to tape as we can only select one single snapshot with a constant name.
Is your snapvault destination in the same cluster as your source or is it a intercluster setup?