I wonder if anyone could point me in the right direction.
NetApp Release 8.1.4P1 7-Mode
Our environment consists of multiple SQL servers with datastores stored on VMDKs (mixture of NFS and FC). VSC is installed and along with SnapDrive and SnapManager for SQL we reqularly clone database snapshots from one SQL server to another, with good results.
We have a second environment which uses the same NetApp system but prestents to a separate vCenter with its own VSC install. The servers are in the same active directory. This environment is behind a firewall. We seem to be unable to mount a clone from a server within here to a server in the first environment. We have opened all of the ports we think are required between the source and destination servers. The clone fails with ....
Snapshot mount failed.
Remote clone operation failed: Error code: 0x80004005, Error Code: 0x80004005 Object reference not set to an instance of an object.
We suspect this is a firewall issue?
Questions that I am trying to find answers to are what in the flow of traffic in a clone mount operation to a remote server. Is all the communication SQL server to SQL server or does the server communicate with the VSC of the destination server? or even the vCenter server?
Thanks for responding and thinking about this. I have checked and we are using the same account for both Snapdrives which is in both local admin groups. I was wondering if it was at least possible i.e. one A VM in one VCentre to a VM in another VCentre. I have taken the support ticket route and logged a case with Netapp. They state that it is possible but I'm still waiting on a response to my last email requesting that, yes, help from a product specialist would be most welcome. I'll update this post if I find a solution.
here is a draft of what the Prerequisites for VMDK verification or cloning on SnapMirror destination volumes are, but please note that those steps are not fully tested and you should treat them as guideline and test them yourself before relying on them:
You can verify backup sets on SnapMirror destination volumes and you can clone databases from
SnapMirror destination volumes. If the databases that you want to verify or clone are hosted on
VMDKs, you must meet several prerequisites before you can perform either of those operations.
You can verify and clone from destination volumes when the database hosted on the VMDKs is
replicated to a site by SnapMirror and the configuration meets the following requirements:
The virtual machine is installed on the ESX server on the secondary site.
SQL Server, SnapDrive, and SnapManager are installed on the virtual machine.
The ESX server is managed by another vCenter Server and the VSC server on the secondary site.
SnapDrive is installed on the secondary virtual machine that is pointing to the VSC server on the
On the primary site, you have selected the SQL Server on the secondary site as the remote
On both the primary and secondary VSC servers, you have created a Windows share on the VSC
repository folder where the backup metadata file resides.
The SnapManager service account has read permission on the share at the primary site and write
and modify permissions at the share on the secondary site.
The primary VSC server has discovered the destination storage system.
For NFS datastores residing on clustered Data ONTAP, a datastore must exist on the SnapMirror
destination volume and the name of the destination datastore must be specified in the change list
On the primary virtual machine where the backup is initiated, the following registry settings and
values must be defined in HKEY_LOCAL_MACHINE\SOFTWARE\Network Appliance
\SnapManager for SQL Server\Server:
destination SMVI server name
\\source SMVI server name\SMVI repository share name\backups.xml
\\destination SMVI server name\SMVI repository share name
change list file name
Requirements for the change list file
The change list file is a text file that contains information about source and destination volumes. The
contents of the file must be in the following format with fields separated by a space and each