We are loking to setup our Snapcentre 4.4 P1 servesr behind a load balancer. The load balancer provide s VIP/DNS Alias to access Snapcentre. From the SDCLI perspective, how to we specif this VIP? 

Is there any published feature set for Snapcenter i.e. do we know what might be released with Snapcenter 4.5 and when that might be released?

I am resetting all local NetApp cluster passwords to upgrade the hash from MD5 to SHA512 and I am down to my last one - the local service account used by SnapDrive for the Transport Protocol Settings. We only have SnapDrive running on Windows Failover Clusters, and only for LUN management (due to a SnapCenter bug I'm awaiting a fix on). We use SnapCenter on all systems, including the ones with SnapDrive, for backups.

Within this context, is there any risk to changing the password for the service account used in the Transport Protocol Settings dialog box, and then going one system at a time to update the new password in the dialog box? I don't want to get in a situation where (a) SnapDrive tries to connect and it affects LUN functionality, and/or (b) SnapDrive tries to connect from systems I haven't updated the password for yet, and it locks out the service account.

Any recommendations?

New to SnapCentre. Does use of SnapCentre negate the requirement for Snapdrive at the target server where storage is presented. 

Using Snapcentre for Oracle 3.4.1 P4 on Windows 2008 R2 (don't ask why! 🙂 ). Obviously SMO works by creating flex-clones in the underlying storage then presenting back to the OS as a new instance of oracle. It was indicated to me though that these clones of the DB could not be split out into a new standalone DB like you would when you split a flexclone off from it's parent.

Is that the case or can SMO clones be split? 

We've got some old systems that are still running SnapDrive and SnapManager for SQL.  There's VMware in my world and we're running Virtual Storage Console.  It's past time to upgrade to current software. 

- Are there any blogs, guides, etc. about how to do this upgrade?

- In general, is it possible to run the old and new environments in parallel, so I can move systems to the new world one at a time instead of having to do a big upgrade?

Pointers appreciated.

Thanks!

FIrst, some background: we are migrating from SnapDrive/SMSQL to SnapCenter, however SC has numerous bugs <related to failover clusters and mount points> that requires us to keep SnapDrive (but not SMSQL) on a few servers until the bugs are patched. We are running OnTAP 9.3 because SnapDrive isn't supported in OnTAP 9.4 and above. I am aware there are special bundled versions of SnapDrive with certain SnapManager products (such as Hyper-V) that are supported in OnTAP 9.4 and above, but SMSQL isn't one of them.

Now my question: what if I installed one of the special SnapManager/SnapDrive bundled products on the SQL Servers where I need SnapDrive, and just didn't use the SnapManager component? Would that be a legitimate way to get a supported version of SnapDrive on those servers so we can upgrade to OnTAP 9.5? It would be even simpler, of course, if installing the latest SnapDrive patch as a standalone would be compatible (see below), but everything I've seen so far indicates it is not.

Would love to hear anyone's insight! Thanks in advance.

SnapDrive 7.1.5P3

https://mysupport.netapp.com/site/products/all/details/snapdrive-windows/downloads-tab/download/30049/7.1.5P3

I heard recently that some older SnapManager products such as SnapManager for Hyper-V are now coming bundled with SnapDrive 7.1.5P2 which is supposedly supported through OnTAP 9.7. I say "supposedly" because the IMT is inconsistent on this point. When looking at SnapManager for Hyper-V it shows compatibility through 9.7, but when you choose SnapDrive it still shows compatibility only through 9.3.

Why do I ask? We are currently only on OnTAP 9.3 because we haven't fully deployed SnapCenter yet, and my understanding was that SnapDrive/SMSQL are only supported through 9.3 based on the IMT. Can anyone provide clarity on this point? It would be a game-changer for my planning purposes if SnapDrive 7.1.5P2 and SMSQL 7.2.3 were now supported through OnTAP 9.7. It would not be as big of a deal if we weren't continually running into limitations, issues, and bugs in SnapCenter as we deploy it.

Hello,

I am trying to create a LUN in a Windows Failover Cluster for the first time using SnapCenter after having used SnapDrive for years. I'm running across two very confusing elements and wondered if someone could provide insight. Specifically:

1. In the Disk Type screen I of course select Shared Disk, but then it requires that you type in the Windows Cluster Resource Group. In SnapDrive you just selected it from a drop-down list. I'm not sure if the name should be the full name as shown in Windows Failover Cluster ("SQL Server (APPNAME)") or just the app name (APPNAME). Any ideas?
2. When selecting the initiators, I choose each host in the cluster and select the initiator on each host as I did before in SnapDrive. However, on the Group Type screen that follows, you can only choose one iGroup! In SnapDrive, I select Automatic which attaches the LUN to two igroups, one for each node in the cluster. I can't do that here!

I did read in NetApp documentation (below) the line "You need only create the disk on one host in the failover cluster." Does that indicate I should only connect to one of the initiators in the Map LUN screen and select the matching initiator group in the Group Type screen? If so, does the wizard automatically add mapping to the additional nodes?

Any help will be appreciated!

http://docs.netapp.com/ocsc-41/index.jsp?topic=%2Fcom.netapp.doc.ocsc-ag%2FGUID-7A7D7B1D-EB19-4739-BC03-BE94730FA7F5.html

Hello,

      We have SME 6.0.0.706 for exchange 2007 which is running on Windows 2003 X64.  Exchange 2007 has 10 databases which are snapmirrored to the DR site. 

Since few days the backup fails with atleast 1 Database with the following error in the backup log.

[09:54:49.475] [SnapDrive Error]:VDS disk object for the LUN s/n '7Sms/+AYRODR' has not been found
(SnapDrive Error Code: 0xc004031c)
[09:54:49.490] SnapDrive failed to mount the snapshot.
[09:54:49.490] [SnapDrive Error]:VDS disk object for the LUN s/n '7Sms/+AYRODR' has not been found

[09:54:49.490] Unable to mount snapshot, abort verification.
[09:54:49.490] [SnapDrive Error]:VDS disk object for the LUN s/n '7Sms/+AYRODR' has not been found

[09:54:49.490] BackupVerification Job of JobID=21461 is finished with status Failed.

I need to know where is the Serial Number 7Sms/+AYRODR' . I am sure that this is the snapshot serial number becasue in my HEAD office the snapshot has a different serial number, it seems to be from the DR side.

Please Help

Hi,

Before the upgrade to ONTAP 9 my Hyper-V Cluster was running distributed application-consistent snapshots over SMB 3.

After the upgrade my SnapDrive and SnapManager had to be re-installed/downgraded after a bad SD version. Now the option to run Distributed backups is gone in the configuration wizard and I found an old document saying that it wasn't supported but that was on Windows 2012, ONTAP 8 and SnapManager 2.0.

If it still isn't supported how come I could run it for over a year before the upgrade of ONTAP?

Is there a way to activate Distributed backups by editing registry or config files? The benefit of Hyper-V cluster kind of loses its point if I can't run distributed backups.

Best regards

Joakim

HI there

I have built a Snapcenter POC environment to test out the solution before moving to production. It consists of an SC server (windows 2016 core), Netapp SIM (ontap 9.4), MS SQLServer and MS AD Server (both windows 2016 core). I can connect iscsi luns to the SQL and AD server using oncommand (via the sim) and Windows Admin Centre to manage the core servers. all works fine. windows volumes mount and are avialable for use etc Hapy Days.

When I try to do the same via snapcentre, i can build and register the iScsi path, igroup and register the hosts, but cannot create a lun or connect to an exisiting lun. I have removed all firewalls, ensured the credentials supplied are Admins or domain admins all with no joy.

on looking at the SCWDebug.log file I can see SDW is having 2 problems

1: When I try to create a LUN, it suceeds in creating, connecting  and intialising the lun in the specified volume, but fails when it tries to create a volume. error is  "Failed to Create windows file system at Snapdrive.NSF.Core.Host.PartitionManager.CreateWindowsFileSystem".

it then deletes the LUN and finishes. Note it does not remove the igroup so if re-run fails with a different error. which has to be corrected in ontap by removing the igroup. 

2: When I try to connect to existing LUN, it applies the requested igroup, it mounts the lun and then fails with an invalid WMI Query error is System.Management.ManagementException.ThrowWith ExtendedInfo(..... get.count()..... at SnapDrive.NSF.Core.Host.PartitionManager.<>c_DisplayClass13.<connectdisk>b__d(String Node). reported error is

"Task Creating Windows File system Status: Failed Message: No disk is found on all nodes".

Query is "Select * from MSFT_Partition Where DiskID = "{1}\\\\<servername>\\root/Microsoft/Storage/Providers_v2\\WSP_Disk.objectid="<Disk ID>

Scope \\<Server name>\root\Microsoft\windows\Storage.

Note the 4 \\\\ above are correct as reported in log file???? this is strange as the Disk ID reported 2 lines above only has 2\\.

This time it exits and leaves the lun mounted and ready to use from the windows server and looking good in ontap, but not registered in snapcentre, so unable to be used for backup operations. ;-(

There seems to be an issue with Snapdrive (Snapcentre for windows) creating or enumerating windows volumes on a Server core target, has anyone else experienced this or have do you have any futher pointers on things to try as I am now out of ideas.

Thanks in advance for your time and support

I am trying to setup SMSQL and snapvault intergration on CDOT 

When running a SMSQL backup job that also archives off to secondary storage - the job runs, and the snapshots do get sent to the SV destination as expected.

However - the snapvault datasets do not show up in the gui to be able to be restored.

Looking in the backup logs shows the following:

SMSQL7.2.2, Snapdrive 7.1.4 and DOT9.1

[14:36:15.861] [GH950] No database associated with an enabled data set archive backup was selected.
[14:36:15.877] [GH950] Starting to prepare the list of volumes (which has snapvault relationship) and corresponding storage details
[14:36:15.877] [GH950] Preparation of list of volumes (which has snapvault relationship) and corresponding storage details succeeded
[14:36:15.877] [GH950] Starting to transfer the snapshot on secondary
[14:36:16.298] [GH950] Starting to initiate SnapVault update ...
[14:36:18.654] [GH950] SnapVault update of snapshot from primary to secondary initiated successfully
[14:36:18.669] [GH950] Starting to write snapvault info SIF 
[14:36:18.669] [GH950] Prepare to save sanpvault info to SnapInfo file...

[14:36:18.669] [GH950] Updating snapvault info in SIF for databases sharing same drive letter - [#1]
[14:36:18.685] [GH950] Starting to find UUID for each primary snapshot to its corresponding secondaries....
[14:36:18.841] [GH950] Finding UUID for each primary snapshot to its corresponding secondaries – successful
[14:36:18.841] [GH950] Starting to find UUID for each primary snapshot to its corresponding secondaries....
[14:36:18.888] [GH950] Finding UUID for each primary snapshot to its corresponding secondaries – successful
[14:36:18.888] [GH950] Writing snapvault info SIF - completed successfully
[14:36:18.903] [GH950] Not to update SnapMirror after operation. Skip SMVI metadata transform also.
[14:36:19.668] [GH950] SDDatasetDFMProxy failed.
[14:36:19.668] [GH950] [SDAPI Error]: DFM is not configured.

106
[14:36:19.839] [GH950] Preparing LUN 'E:\', for SDAPI operation...
[14:36:20.354] [GH950] Preparing LUN 'F:\', for SDAPI operation...

[14:36:20.963] [GH950] Querying backup data sets for LUN: E...
[14:36:21.197] [GH950] Getting Snapmirror Destinations....
[14:36:24.535] [GH950] CSmSDSnapShot::GetAllSnapshotList -> Snapshot Listing failed.
[14:36:24.551] [GH950] [SDAPI Communication Exception]: Error 0xc0040457 occured. Description is not found.
[14:36:26.906] [GH950] CSmSDSnapShot::GetAllSnapshotList -> Snapshot Listing failed.
[14:36:26.922] [GH950] [SDAPI Communication Exception]: Error 0xc0040457 occured. Description is not found.

Anyone else encountered this?

Thanks

We have in the past had issues with our existing snapshots which are at a volume level (CSV data) on our filers - in that the data has been corrupted previously and was inconsistent.

What is the recommended process for snapshots of CSV data where our VMs are stored?

Should we be using SnapDrive for Hyper-V instead, if so what disadvantages would this have? i.e. if the SnapDrive service stops for any reason will the snapshots stop, etc.

Our source filers are running 8.3.2P2 (yes I know they need to be upgraded, it is arranged for a time in the future) with our destination filers running 9.1P14.

If anyone could off any advise that would be great.

Thanks,

Where I work, we have a troublesome Windows 2012 R2 server with SQL Server 2008 R2 on (no Snapmanager for SQL though) that we are required to upgrade SnapDrive on to version 7.1.5 in preparation for our OnTap upgrade that is happening later this week. We are currently on OnTap 8.2.3P1

We have not been able to install SnapDrive 7.1.5 or uninstall the existing version of SnapDrive 7.1.1 on this troublesome server.

The install fails (or uninstall) fails every time with a InstallShield DLL Custom Action error relating to not being able to find a .tmp file.  Please see the screen print uploaded for an example of this error.

Also since trying to uninstall the old version of snap drive, the GUI for SnapDrive will no longer open nor will the SnapDrive services start, although the iSCSI drives still connect automatically on start up.

What could be at fault here (i know the screenshot probably is not helpfull), we have not had an issue upgrading SnapDrive on other 2012 R2 servers we have.  Windows Host Utilities 7.1 also installed fine on the troublesome server as did the hotfixes for WHU.

So far I have tried to no avail:

• Installing in safeMode
• Installing as Local Admin
• Uninstalling AV Software
• Trying to unstall old version of SnapDrive first.

Regards: Elliott. 

Hi all;  where I work we have a  4 node Windows Server 2016 Hyper-V cluster, each with WHU 7.1, SnapDrive 7.1.5 and SnapManager for Hyper-v 2.1.3.  Currently running OnTap 8.2.3P1 what is very soon to be upgraded.

Cluster has three volumes connected with SnapDrive on each node:

• CSV volume for VM's
• CSV volume for SnapManager for Hyper-V (SnapInfo)
• Volume for Disk Witness in Quroum

Intermittently the distributed application consistent backups taken with SnapManager for Hyper-V will start failing and will continually then fail unless I reboot the nodes that appear to be missing from the VSS witters list on the node that owns the cluster where the backups are taken from.

I don't know if this normal or not in regards to not all the nodes appering on the VSS witters list on the node that owns the cluster resource group, but it's what i have recentley noticed.

For example, the below is missing from the "Cluster Shared Volume VSS Writer" section of the VSS Writers list on the Cluster resource owner where the SnapManager backups are taken from untill I reboot VM-Node2.

+ Component "Cluster Shared Volume VSS Writer:\F9894808-30A0-4730-99E8-1F224760E715<CSV>66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:50ccb3b7-9268-49da-994c-64b476c36bd5:VM-Node2</CSV>"
			- Name: F9894808-30A0-4730-99E8-1F224760E715<CSV>66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:50ccb3b7-9268-49da-994c-64b476c36bd5:VM-Node2</CSV>
			- Logical path: 
			- Full path: \F9894808-30A0-4730-99E8-1F224760E715<CSV>66841cd4-6ded-4f4b-8f17-fd23f8ddc3de:50ccb3b7-9268-49da-994c-64b476c36bd5:VM-Node2</CSV>
			- Caption: Offline\LAB-APP01
			- Type: VSS_CT_FILEGROUP [2]
			- Is selectable: TRUE
			- Is top level: TRUE
			- Notify on backup complete: FALSE
			- Paths affected by this component:
				- C:\ClusterStorage\VM_Storage_Cluster\lab-app01\Snapshots
				- C:\ClusterStorage\VM_Storage_Cluster\lab-app01\Snapshots\
				- C:\ClusterStorage\VM_Storage_Cluster\lab-app01\Snapshots\55E46C19-0D34-47C9-9CEB-3293AE0EB4E7
				- C:\ClusterStorage\VM_Storage_Cluster\lab-app01\Snapshots\BD9C2128-3A17-48E2-8B34-4A0FC8CD6C33
				- C:\ClusterStorage\VM_Storage_Cluster\lab-app01\Virtual Hard Disks
				- C:\ClusterStorage\VM_Storage_Cluster\lab-app01\Virtual Hard Disks\
				- C:\ClusterStorage\VM_Storage_Cluster\lab-app01\Virtual Machines\
			- Volumes affected by this component:
                               - \\?\Volume{57705205-5386-4040-a163-7fe707aade75}\ [C:\ClusterStorage\VM_Storage_Cluster\]
			- Component Dependencies:

VM-Node1 is normally the cluster resource owner and thus where the distributed application consistent backups with Snap Manager for Hyper-V are taken from. The above quoted text was a small section taken from VM-Node1 with the "diskshadow" and "list writers"  commands in command prompt.

I have since disabled the automatic balancing of virtual machines under the "Balancer" tab of the cluster proprieties in case that is responsible; I don't know if this option can be enabled or not?

Also no windows updates have yet been installed on any of the nodes of the Windows Server 2016 Hyper-V Cluster if that may also be responsible for the backup issues? In essence what is causing these VSS related backup issues and how can they be properly resolved?  

I have tried restarting the SnapManager for Hyper-V Web Service and the VSS Service of the nodes in the cluster to no avail; whilst rebooting nodes sequentially that are missing from the VSS writers on the owner node works, it is anything but an ideal solution nor should that even be required!

Regards: Elliott.