Dear all,

I'm currently facing an issue while adding Shared Disks to one of our Microsoft Failover Clusters in our testing environment.

A few hours earlier, I was able to add LUNs to another Microsoft Failover Cluster that was setup using the exact same procedure. All of a sudden, I now recieve the following error:

Error: No storage connection is set for StorageSystem : svm03-mgmt.example.com

The only change that was made in between both the succesfull and failed tries is the SnapCenter server's Fully Qualified Domain Name.

Troubleshooting Steps I've taken so far:

• Verified the Storage Virtual Machine is correctly registered in DNS; both forward lookup (A Record) as well as reverse lookup (PTR Record).

> svm03-mgmt.example.com
Server:  dc01.example.com
Address:  10.0.0.1

Name:    svm03-mgmt.example.com
Address:  10.0.0.130

> 10.0.0.130
Server:  dc01.example.com
Address:  10.0.0.1

Name:    svm03-mgmt.example.com
Address:  10.0.0.130

• Verified the "Storage Systems" Page in SnapCenter contains the Storage Virtual Machine.

• Verified the credentials on the "Storage Systems" Page in SnapCenter.

• Reviewed the Job Log in SnapCenter.

Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Cannot retrieve storage connection setting from SMS server.
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Failed to provision disk
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Error: No storage connection is set for StorageSystem : svm03-mgmt.example.com at SnapDrive.Nsf.Core.DiskProvisioningHelper.PreProcessandValidateCreateRequest(SDProvisionCreateStorageRequest request, DiskOperationContext context, HostDetails& host) at SnapDrive.Nsf.Core.DiskProvisioningManager.SDProvisionCreateStorage(SDProvisionCreateStorageRequest request, DiskOperationContext context)
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3432389+02:00 Error SDW PID=[1608] TID=[2060] Error: No storage connection is set for StorageSystem : svm03-mgmt.example.com
Exchange02.example.com SCW_132.log	ERROR	2018-05-13T21:53:50.3119889+02:00 Error SDW PID=[1608] TID=[2060] ManagementException : Not supported

• Verified the SnapCenter server is correctly registered in DNS; both forward lookup (A Record) as well as reverse lookup (PTR Record).

> snapcenter.example.com
Server:  dc01.example.com
Address:  10.0.0.1

Name:    snapcenter.example.com
Address:  10.0.0.221

> 10.0.0.221
Server:  dc01.example.com
Address:  10.0.0.1

Name:    snapcenter.example.com
Address:  10.0.0.221

Please note I'm currently using SnapCenter Build 4.0.0.809 installed on Windows Server 2012 R2 with all available HotFixes applied.

Has anyone had a simmilar issue? Anyone an idea on how further investigate the root cause for this issue?

Thank you in advance!

Kind regards,

Pieter-Jan Rijmenants

HI

We have a number of virtual centers 6.5. We are running snap ceter 4.0 and we have a retention of 1. We have set it to vault to a different SVM.

how ever it doesn't seem to delete the old snapshots on the production volume. It always seems to leave the old snaps behind

Any suggestions 

Thanks

SnapManager for SQL Full backups are taken and then SnapVaulted : 3 separate vol/lun are designated.

1. data [mdf]
2. log [ldf]
3. snapinfo

Out of these three, only data volume is available, 2 & 3 is gone.

Problem: When trying to import mdf in sql management studio, its complaining ldf are missing.

Any idea = Why is it asking for LDF files when this was a full backup model. Does that mean, the dirty buffers [or midified data] were still in cache basically in the log file, when the DB was snapshotted ? But, should that have not comitted considering full backup model.

many thanks in advance.
-Ashwin

Did the ability to mount a restricted volume change in OnTap 9.3?  I ask this because I am trying to do an NDMP SMTape restore. This OnTap 9.3. I prepare my target by creating a DP volume and set the state to "restricted".  However, I cant mount the volume now because it is in restricted state.  Because I cant mount the volume, the NDMP client can't see it to verify the target volume exists.

For ONTap 9.3, What is the proper procedure to prepare a destination volume for an NDMP SMTape restore?

Thanks

Has anyone been able to script getting the snapgather.exe to run for when you need to troubleshoot some failed SnapManager for SQL backups?

I only seems to be able to do it manually at the minute and it always prompts for the password of the account configured on SnapDrive?

Hi

Can anybody explain for a dummy what are Snapcenter 4.0 SQL backup types (Full and Logs, Full, Logs)?

When does log truncation happen?

Is it enough to make Full Backup to have restoreable SnapVault destination?

Correct me if I'm wrong:

1. Full and Logs

-Creates snapshots for data and log volumes. Rotates Snapshots.

-Copies Logs to Host Log Directory and creates a snapshot for Host Log Directory volume (aka snapinfo)

-Truncates logs (deletes logs in log volume)

-Deletes old Log files in HLD (according to retention)

2. Full

-Creates snapshots for data and log volumes. Rotates Snapshots

-Deletes old Log files in HLD (according ro retention)

-DOES NOT truncates logs

3. Log backup

-Copies Logs to Host Log Directory and creates a snapshot for Host Log Directory volume (aka snapinfo)

-Truncates logs (deletes logs in log volume)

-DOES NOT delete (rotate) snapshots

During restore Snapcenter uses recent Full or Full and Log backup, then looks at HLD to restore Up To Minute... it actually does not use Log volume for log roll?!

Thank you

Nick

Helloooo Community,

Have a situation where snap drive is not able to list the LUNs attached to our Hyper-V hosts. The LUNs are connected and accessible through Windows, it's just SnapDrive that can't seem to interact with them.

Hosts are all running Windows Server 2016 Datacenter Core. Other servers using same/similar hardware and software are able to enumerate LUNs through SnapDrive as normal. 

Only clues I've got are a ton of events like the following, but tracking down a solution has proven difficult:

The following information was included with the event:

\\?\mpio#disk&ven_netapp&prod_lun_c-mode&rev_0.3_#1&7f6ac24&0&54336130675d442f4d5a6138#{53f56307-b6bf-11d0-94f2-00a0c91efb8b}
/vol/DOCKERHOST_VOL/DOCKERHOST
(2,0,0,9)
c00402fa
A LUN with device path \\?\mpio#disk&ven_netapp&prod_lun_c-mode&rev_0.3_#1&7f6ac24&0&54336130675d442f4d5a6138#{53f56307-b6bf-11d0-94f2-00a0c91efb8b} and SCSI address (2, 0, 0, 9) is exposed through an unsupported initiator.

The handle is invalid

Any help is greatly appreciated.

Hi All,

 I wonder if I'm the only one who had been annoyed with the way SC(F) look up for relationships (vault,snapmirror  -- lists ALL that exists on controllers and then "finds" one that already specified in config file) ? As we all had been "blessed" with NetApp decision in ONTAP 9.3 to default to XDP engine over previous DP for snapmirror relationships it breaks mentioned products if the same source volume has snapvault to secondary relationship and snapmirror to DR as both now of type XDP and products seems to be completely ignorant about policy-type attribute and getting mad at users with error indicating multiple XDP destinations aren't supported ..does anyone knows how to "educate" SCF to differentiate relationships by snapmirror policy-type and not the type?

Hey folks,

we have some troubles with Snapshots of VM-Datastore via VSC in combination with SVM-DR relationship of the NFS-Datastore.

Snapshots cannot be deleted as configured in the vsc backup job because some snapshots have an record-owner entry. 

CL1::*> snapshot show -volume ESXxx -fields owners,busy,record-owner,create-time
vserver volume      snapshot                         create-time              busy  owners record-owner
------- ----------- -------------------------------- ------------------------ ----- ------ ----------------------------------------------------------------------
NFS1 ESXxx smvi__ESXxx_20180124213000 Wed Jan 24 21:43:27 2018 false -      snapmirrorDP.7eb76d1189f2e6119fd100a098c68937_2149105432.nonSMDstOwned
NFS1 ESXxx smvi__ESXxx_20180201213000 Thu Feb 01 21:43:06 2018 false -      snapmirrorDP.7eb76d1189f2e6119fd100a098c68937_2149105432.nonSMDstOwned
NFS1 ESXxx smvi__ESXxx_20180214213000 Wed Feb 14 21:43:06 2018 false -      snapmirrorDP.7eb76d1189f2e6119fd100a098c68937_2149105432.nonSMDstOwned
NFS1 ESXxx smvi__ESXxx_20180301213001 Thu Mar 01 21:43:16 2018 false -      -
[...]
NFS1 ESXxx smvi__ESXxx_20180329213001 Thu Mar 29 21:41:46 2018 false -      -
NFS1 ESXxx smvi__ESXxx_20180330213000 Fri Mar 30 21:42:16 2018 false -      snapmirrorDP.7eb76d1189f2e6119fd100a098c68937_2149105432.nonSMDstOwned
NFS1 ESXxx smvi__ESXxx_20180402213000 Mon Apr 02 21:41:26 2018 false -      -
NFS1 ESXxx smvi__ESXxx_20180403213001 Tue Apr 03 21:42:16 2018 false -      -
NFS1 ESXxx smvi__ESXxx_20180404213000 Wed Apr 04 21:53:26 2018 false -      snapmirrorDP.7eb76d1189f2e6119fd100a098c68937_2149105432.nonSMDstOwned
NFS1 ESXxx smvi__ESXxx_20180405213000 Thu Apr 05 21:42:06 2018 false -      -
NFS1 ESXxx smvi__ESXxx_20180406213000 Fri Apr 06 21:42:06 2018 false -      -
NFS1 ESXxx smvi__ESXxx_recent         Mon Apr 09 21:42:54 2018 false -      -
NFS1 ESXxx vserverdr.0.116db77e-f289-11e6-9fd1-00a098c68937.2018-04-10_080500
                                                     Tue Apr 10 08:05:02 2018 false -      VserverDR,snapmirrorDP.7eb76d1189f2e6119fd100a098c68937_2149105432.base
32 entries were displayed.

CL1::*> snapshot show -volume ESXxx -snapshot smvi__ESXxx_20180124213000 -instance

                              Vserver: NFS1
                               Volume: ESXxx
                             Snapshot: smvi__ESXxx_20180124213000
                 Snapshot Data Set ID: 914828035119
          Snapshot Master Data Set ID: 916977139480
                        Creation Time: Wed Jan 24 21:43:27 2018
                        Snapshot Busy: false
                       List of Owners: -
                        Snapshot Size: 319.6GB
           Percentage of Total Blocks: 3%
            Percentage of Used Blocks: 5%
              Consistency Point Count: 3352386
                              Comment: -
                  File System Version: 9.0
             File System Block Format: 64-bit
                     Physical Snap ID: 213
                      Logical Snap ID: 213
                Database Record Owner: snapmirrorDP.7eb76d1189f2e6119fd100a098c68937_2149105432.nonSMDstOwned
                        Snapshot Tags: VOPL_owner_snapmirrorDP.
                                       7eb76d1189f2e6119fd100a098c68937_
                                       2149105432.nonSMDstOwned=snapmirror
                        Instance UUID: b3fea069-1938-4c7f-8ef2-670eb364894f
                         Version UUID: b3fea069-1938-4c7f-8ef2-670eb364894f
                      7-Mode Snapshot: false
      Label for SnapMirror Operations: -
                       Snapshot State: -
                 Constituent Snapshot: false
                                 Node: CL1_N1
               AFS Size from Snapshot: 4.86TB
    Compression Savings from Snapshot: 1.78TB
          Dedup Savings from Snapshot: 2.94TB
       VBN Zero Savings from Snapshot: 199.4GB
             Snapshot Inofile Version: 4
                          Expiry Time: -
                     Compression Type: adaptive
                 SnapLock Expiry Time: -

Due to this entry, we cannot delete the snapshot in VSC, SystemManager and CLI (*force should work, but the vsc will not know about the deletion).

We are looking for a way to delete the record-owner entry or to prevent the vm backup process (VSC+SVM-DR) to create snapshots with stuck Database record owner.

Is there anyone out there, who already had such an behaviour? And maybe an solution? 

Thanks for any hints,

regards,

Pat

Trying to backup oracle db in a redhat vm. Fails during the file system discovery phase... 

 Discovery failed for object /u02 with error Backup of root file system is not supported, '/dev/sdd1' is shared with root file system device '/dev/mapper/vg_root-lv_root'.

I wanted to share this process since it took me a while to navigate through documentation / support / etc to figure this out.  

SnapCenter 4.0 RDM LUN provisioning is currenlty only accomplished with the PowerShell Commands.  

This assumes you already have SnapCenter 4.0 Deployed

You already have added the Host to SnapCenter and Installed the Windows Plug-In

To Start:

You need to log into the VM you want to provision the RDM LUNs.

I used PowerShell ISE where I could view the powershell commands for the SnapCenter Module as well as the SnapDrive Module (not really snapdrive, but that's what it is called).

reference:  https://library.netapp.com/ecm/ecm_download_file/ECMLP2840881

Here is an example of what I would consider a simple and common RDM LUN Provisioning Operation:

new-sdstorage -storagesystem svm ip or hostname-path driveletter or ntfs mount point -LunPath /vol/volumename/lunname -size #andunit i.e.200G -igroup igroupname -Thin -RawDeviceMapping -Datastore RDM-Mapping Datastore Name in VMware -FileSystemLabel filesystemlablename -PartitionStyle MBR or GPT

Look through the other SDStorage commands for similar SnapDrive for Windows operations.

Hi, everyone

In my evironment, I installed VSC 6.2.1 in vCenter and created Backup Job on a per data store basis and run.
But,Backup Job was Suddenly failed,and displayed popup

At least one datastore must be backed up. Either explicitly or implicitly through backing up a virtual machine

I confirmed 'server.log'.It was outputted below.

Virtual machine 'ServerName' is currently migrating and will not be backed up

I read the sentence described in the URL below and confirmed that the virtual server whose status is
migrating will be skipped by VSC.

https://kb.netapp.com/app/answers/answer_view/a_id/1002291

There was only one virtual machine in this data store. As a result, if one is going to be skipped while migrating,
it seems that there was no server in the data store and an error occurred.

But, this server was not in migrating during backup.

And Similar symptoms (migrating and will not be backed up) also occurred in virtual machines
in other data stores.
The virtual machine was shutting down that did not perform any migration operation.

As a remedy for this problem, we confirm that if we do the operation below, we will make improvements.
１．Perform inventory removal and re-registration of virtual machines from vCenter
２．Retrieve one backup from the VSC only on the server where the problem occurred

If anyone knows, please let me know
１．Why did this problem occur?
２．Is there any other way than the remedial measure I wrote?

The environment is as follows.
・ONTAP 9.1
・vSphere 6.5 update 1
・VSC 6.2.1P1D5

Thanks
Nornir

Hi,

up to now I use SnapCenter for snapping SAP-DB2, I'd like to migrate SAP-DB2 Snapshot to SnapCenter 4.0. Is there somewhere a custom plugin available?

Regards

Space

I tried to create a new SMO profile on a RAC Database with OS Oracle Linux 7.4

smo profile create -profile backup_xxx-rac_xxx -profile-password yyyy -repository -dbname rmandb -host host1 -port 1521 -login -username snapmanager -database -dbname datenbankname -host node1 -sid instanz1 -login -username snapmanager -password zzzz -port 1521 -rman -login -username rman -password zzzz -tnsname rmandb -osaccount oracle -osgroup oinstall -retain -monthly -count 4 -comment "Backup xxx-rac DB xxx" -verbose

But the creation fails with SMO-05075

[ERROR] SMO-05075: Profile create failed: ORACLE-00300: Error executing srvctl command srvctl status database -d xxxxxx.  The command returned: [Instanz instanz1 wird auf Knoten node1 ausgef?hrt, Instanz instanz2 wird auf Knotennode2 ausgef?hrt]
[ INFO] SMO-20022: Deleted credentials and repository mapping for profile "backup_xxx-rac_xxx" in user credentials for "oracle".
Operation Id [8a4d014962fbdb840162fbdb87bb000a] failed. Error: java.lang.NullPointerException

error log /var/log/smp/server.log:

[ INFO] SMO-13046: Operation GUID 8a4d014962fbdb840162fbdb87bb000a starting on Profile backup_xxx-rac_xxx
[ INFO] SMO-13505: SnapDrive environment verification passed.
[ INFO] SMO-13507: JDBC verification for "snapmanager@node1:1521/instanz1" passed.
[ INFO] SMO-13506: SQLPlus verification for database SID "instanz1" passed.  Environment: [ORACLE_HOME=/oracle_base/product/12102/db]
Exception in thread "Thread-2" com.netapp.dlm.process.operation.OperationException: java.sql.SQLException: Festschreiben mit aktiviertem Auto-Commit nicht möglich
        at com.netapp.dlm.process.common.OperationCycleHeartbeatThread.run(OperationCycleHeartbeatThread.java:84)
Caused by: java.sql.SQLException: Festschreiben mit aktiviertem Auto-Commit nicht möglich
        at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:2356)
        at oracle.jdbc.driver.PhysicalConnection.commit(PhysicalConnection.java:2403)
        at com.netapp.dlm.process.common.OperationCycleHeartbeatThread.run(OperationCycleHeartbeatThread.java:74)
[ INFO] SMO-13509: RMAN verification using catalog "rmancat" passed.
[ INFO] SMO-07431: Saving starting state of the database: instanz1(OPEN).
[ERROR] SMO-05075: Profile create failed: ORACLE-00300: Error executing srvctl command srvctl status database -d databasename  The command returned: [Instanz instanz1 wird auf Knoten node1 ausgeführt, Instanz instanz2 wird auf Knotennode2 ausgeführt]
[ERROR] SMO-13032: Cannot perform operation: Profile Create.  Root cause: ORACLE-00300: Error executing srvctl command srvctl status database -d databasename.  The command returned: [Instanz instanz1 wird auf Knotennode1 ausgeführt, Instanz instanz2 wird auf Knotennode2 ausgeführt]
[ERROR] SMO-09003: Failed committing changes to the repository. Batch update row count wrong: 0.
REMOTE-00004: RemoteObjectFactory shutdown gracefully.

I think it's a problem with the language. The srvctl command returns in german. I have set the language Param in /etc/locale.conf to "en_US.utf8

What's wrong? Any idea?

Regards Engelbert

Is there any information with regards to when the cmdlet help and cmdlet reference documentation is going to be updates to actually contain some useful details.

Currently the documentation doesn't have anything other than cmdlet name and list of parameters for many of the cmdlets, and doesn't have any useful descriptions or examples, the same goes for the cmdlets themselves. get-help on the cmdlets isn't very helpful at all.

Hi. I am new to NetApp, so please excuse the probably simple question. When I log into our SVM and run the following: 

snapshot show volNameHere

I get the list of the snapshots. This is a very inactive volume, so snapshots are very low in size (about 1MB). However when I run the following command to delete the snapshot:

snapshot delete -volume volumeNameHere -snapshot snapshotNameHere

It removes the snapshot, however it makes the snapshot before it grow to almost its same size. 

My question is how are these snapshots linked so when I delete say the one from Friday, the snapshot from Thursday takes its size? Thanks in advance!

In the past, with SMSQL and Snapdrive, the recovery of SQL was pretty simple.  During failover testing we would shutdown prod SQL VM, take volumes offline, clone the snapmirror of the SQL ISCSI volumes, and power on clone of SQL.  We'd run the command line snapdrive commands to mount the clones on the host in the same mountpoints as before and reboot

Voila...SQL all recovered....

However, with Snapcenter, I know there are some commands for snapcenter agent on the SQL server, but its a terrible mess of commands that I haven't worked out yet.

The only thing I can think of is that to do this I would need to recover the clone of snapcenter, recover the clone of SQL server (with no disks) and then manually use snapcenter to delete and re-add the ISCIS volumes on DR to the VM....

Thats horribly inefficient when time is of the essence.

Is there a better way that I am just not thinking about?

Hi

Sometimes, pretty frequently, backups of SQL DBs take around 10-20 minutes to complete with time spent in "Registering Backup and Applying Retention".

Because of 15min log backup schedule, jobs are beeing queued.

Can anybody tell what happens in that "Registering Backup and Applying Retention" phase and what can be the reason for long processing???

SnapCenter CPU utlization (4 cores, virtual machine) is around 40-50% taken by IIS worker mostly.

Thank you

Nick.

SnapCenter 4.0P1

Attempt to perform the first NAS backup but do not do the activity. where I can see more detailed the error or if he knows someone who could be. I am integrating a fas8200 with snapcenter and altavault. Please help me.