We are trying to use the SCCLI tool with Snapcentre to create some scripts to clone Oracle DBs. The guide does not indicate how to sign into Snapcentre silently but from testing it seems we canuse the -password option. Is this the only method available to us and if so why is it no documented? 

Hey all,

I don't know if here is the right place to ask, please be patient 🤗

We have On-prem environment based on VMWare vsphere (a few ESXi hosts and VMware VCenter). We also have Snap Center plugin for vmware VCetner installed on the VCenter itself, and a dedicated server for backups (snap center server on windows os, snap center version 4.0)

Since the plugin for VCenter is installed, we can to do a simple recovery actions from snapshots (restore a single vmdk file, de-attach and attach disks, restore entire vm, etc...). Those actions automatically creats a datastore (usually named snap-<some uid>) managed by the snap center vmware 'run as account'. I will call these 'snap center datastores'

However, a regular user still can create Virtual disks on these datastores - makig it difficult to manage. 

We thought create a storage policy that prevent a regular VM disks reside on Datastore generated by the snap center. For this to come out, we need to find a way to attach vmware tag to each datastore created by the snapcenter.

Is it possible to define some vmware storage tag added automatically to those datastores when they are created?

This is important for us since we have some "leftovers" - snap center datastores being kept for a long time for some research reasons.

Hope this message is clear enough 😊

Tankwell

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? 

Exploring the Shares possibilities in OnCommand we turned off cifs on an interface in order to force shares through a specific subnet, using CLI to our netapp host: options interface.blocked.cifs (interface name)

After doing this we had problems backing up an SQL database, the server lost connection to disks and started asking for a valid certificate. Enabling the cifs interface again with options interface.blocked.cifs “” brought back the disks, but a problem still remains. The SnapDrive and SnapDrive Manager services stopped working.

How can we activate the services again so we can start backing up our SQL Databases again. We have tried the registry change for prolonging the shut down time for services to start. Still no result. We have tried rebooting. Reinstalling is not an option.

Any help in this matter is greatly appreciated.

This is our products in relation to the error.

Snapmanager for sql server  6.0.1.1431

Sql version 2008 r2

Server OS 2008 r2

Snapdrive manegement version 7.0.3

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!

I have an error when using ndmpcopy,  somebody can helpme?

Log: Volume Visibility check failed for volume

system node run -node DSIPMXNAS01-01 -command ndmpcopy -sa ndmpuser -da ndmpuser 10.48.202.103:/SVM_NAS01_01_CIFS/vol_NX_Arranque/.snapshot/weekly1/IQTITRENDVIEW/ 
Ndmpcopy: Starting copy [ 136 ] ...
Ndmpcopy: 10.48.202.103: Notify: Connection established
Ndmpcopy: 10.48.202.103: Notify: Connection established
Ndmpcopy: 10.48.202.103: Connect: Authentication successful
Ndmpcopy: 10.48.202.103: Connect: Authentication successful
Ndmpcopy: 10.48.202.103: Log: Session identifier: 65735
Ndmpcopy: 10.48.202.103: Log: Session identifier: 65740
Ndmpcopy: 10.48.202.103: Log: Volume Visibility check failed for volume vol_vmwiso on vserver SVM_NAS01_02_NFS
Ndmpcopy: Connection setup for transfer failed
Ndmpcopy: Done

I installed the SMBR on a Windows 2012 R2 VM. But I'm unable to pass the license check unter About -> License Info

Tried the cluster management and node ip's unter "Storage appliancename or IP address" but I alway get the following error:

"Netapp storage appliance not found. Verify the specified storage appliance is accessible and try again"

It works with the older 7-Mode system. But because the 7-Mode system will go offline in a few month I installed now a new SMBR VM.

All the Webserver services are enabled on cluster and the vserver.

Regards
Carma

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.

We have to move to SnapCenter from SMO due to compatibility issues with our SMO/Oracle estate going forward. Do the products have feature parity? Is this documented anywhere? 

We are in the early stages of testing the SnapCenter Plug-In for SQL to replace SnapManager for SQL. We noticed today that tlog backups generate errors if any databases are in simple recovery mode. Since there are typically a mix of databases that are and aren't in SRM, is there any way to skip SRM databases during tlog backups?

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

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

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.