Hey,

I have just started evaluating SnapCenter and have already stumbled upon something I don't understand. However I think it's either a mis-use on my side or a "works as designed" that I don't understand rather than a bug.

So I have installed SnapCenter with a Dom Ad account for testing purposes, added a few hosts and an SQL Server. Setup was no problem, full- and log-backups are working fine. Now I went to take care of user management. What I did:

- Added an Active Directory Group to SnapCenterAdmin Role

- Users in Group can authenticate just fine but didn't see anyhting

- Of course, so under User Access - All I granted the permissions to every object for that group.

Now members of that group can see storage systems, hosts, policies and all that just fine.

However what does not show up are SQL databases (Resources - Databases). If I log in back as the DomAd I jused to set everything up, the databases are showing up just fine so I can do for example a restore.

However as one of the other AD users in the group, the databases do not show up. The instance appears and I can run a backup - but no restore, since for that I would require the database view.

What am I doing wrong?

Thanks guys

Regards,

Chris

Can anyone please help me with gettting snapvaults working with SnapManager for Exchange. No matter what I do the option to vault to secondary storage is greyed out or skipped over using the wizard. See attached image

I have run through the options listed in the following article https://kb.netapp.com/app/answers/answer_view/a_id/1071157 given to me by NetApp support who have been useless on this and I only get a single email a day on it from them at most, but that is for another day.

I have deleted and recreated the snapvault destination volumes along with the vault policy see attached. If I select the backup verification settings > verification on destination volumes I can see the snapvault volumes listed in there.

What am I missing? This hasn't work since migrating the servers from 7-mode to CDOT where the vaulting work perfectly.

I have an issue with Snap Creator Framework and Sybase agent and would like to share with you all in my workaround.

My environment has detail below.

Snapcreator Server:

• Microsoft Windows Server 2016 Standard Evaluation
• java version "1.8.0_161"
• Snap Creator Framework Version 4.3.1P3

Protection Server:

• SUSE Linux Enterprise Server for SAP Applications 12 SP2
• java version "1.6.0_24"

My Sybase's agent can start normally but failed in the quiescing database step.

# ./scAgent status
Checking Status of scAgent:
    Watchdog: Running
       Agent: Running

I got an error from Snapcreator GUI below.

########## Application Quiesce ##########
 INFO: Application Quiesce for plugin : sybase
 INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Starting
 INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: Entered
 INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: No database discovery (+ALL) specified, finishing
 INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Quiescing database model ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/nNjcrBXLoc.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/QfePbHD3wm.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/RQVQXmQSRM.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/mvkCLr4dk1.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/fXkjfT9s9D.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/KIk6ywsoH9.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/rAThV_WTCe.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/dz_B9HoFe2.sc"] failed with return code 255 and message  INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Quiescing database master ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/iwYKenXc1S.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/btFYCDCo8q.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/sQznOdT5Hk.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/WQ3CACm2Hq.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/wVVqbFECAS.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/FO2tYMHwJh.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/18AbTyWmPm.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/sG2WE58JoF.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] failed with return code 255 and message 
 ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00004] SYBASE:QUIESCE: Quiescing databases failed
 ERROR: [x.x.x.x:9090(4.3.0.0)] SCF-00038: Application quiesce for plug-in [sybase] failed with exit code [255], continuing with backup. INFO: Application quiesce result is empty  from plugin sybase. skipping config update operation
 INFO: Application Quiesce for plugin : sybase finished successfully

Looking more detail in debug logs:

########## Application Quiesce ##########
INFO: Application Quiesce for plugin : sybase
INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Starting
INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: Entered
INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:EXPAND_DB: No database discovery (+ALL) specified, finishing
INFO: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:QUIESCE: Quiescing database model
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Checking Database model state
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Executing SQL sequence:
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME)  SELECT CASE WHEN (status3 &   128) = 0 THEN 'Fq' ELSE 'Tq' END AS [(qui)]
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) 			from master.dbo.sysdatabases where name="model
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) go
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Executing command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"]
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"] finished with
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) exit code: [255]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stdout: [CT-LIBRARY error:
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) 	ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stderr: []ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/uQ5aCJoltU.sc"] failed with return code 255 and message DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Database model sql unable to execute :  SELECT CASE WHEN (status3 &   128) = 0 THEN 'Fq' ELSE 'Tq' END AS [(qui)]
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) 			from master.dbo.sysdatabases where name="model
-
--
-
-
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Executing SQL sequence:
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME)  SELECT CASE WHEN status = 1 THEN 'T1' ELSE 'F1' END AS [(mix1)] 
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) 				from master.dbo.sysdatabases where name="master
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) go
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Executing command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"]
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] finished with
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) exit code: [255]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stdout: [CT-LIBRARY error:
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) 	ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stderr: []ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00012] SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] failed with return code 255 and message DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:BACKUP_CHECK: Database master sql unable to execute :  SELECT CASE WHEN status = 1 THEN 'T1' ELSE 'F1' END AS [(mix1)] 
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) 				from master.dbo.sysdatabases where name="master
ERROR: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) [syb-00004] SYBASE:QUIESCE: Quiescing databases failed
ERROR: [x.x.x.x:9090(4.3.0.0)] SCF-00038: Application quiesce for plug-in [sybase] failed with exit code [255], continuing with backup.
INFO: Application quiesce result is empty  from plugin sybase. skipping config update operation
INFO: Application Quiesce for plugin : sybase finished successfully
########## Application Quiesce finished successfully ##########

I have checked with Sybase DBA, they confirmed database system is working well, no failure on Sybase.

My Workaround

1. Try the same command line on Linux.

Test execute the isql command line directly on Linux with simple SQL statement is working properly.

# cat /tmp/list.db.txt
use master
go
sp_helpdb
go

# /bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/list.db.txt"
 name                                                    
 db_size                                             
 owner                dbid                
 created                                         
 durability                                  
 lobcomplvl                              
 inrowlen                        
 status                                                                                                                                                                                                                                                                                       
 --------------------------------------------------------

This is can be confirmed that no failure on Sybase.

2. I got a lucky mistake.

I found the same error when I mistake with an incomplete command line in Linux.

# su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass"CT-LIBRARY error:
        ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.

3. found out a password issue.

Snapcreator:

DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) SYBASE:RUN_CMD: Command [/bin/su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass#2018 -SSID -w 1024 -i /tmp/zPo6c3tlDm.sc"] finished with
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) exit code: [255]DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) stdout: [CT-LIBRARY error:
DEBUG: [x.x.x.x:9090 (4.3.0.0)] (DATE/TIME) 	ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.]

compared to execute isql on Linux manual (my lucky mistake):

# su - sybSID -c "/sybase/SID/OCS-16_0/bin/isql -X -Usapsa -PPass"CT-LIBRARY error:
        ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.

I supposed that it seems The SnapCreator cannot handle this situation when "sapsa" password is content with "#".

because of it same as me execute with an incomplete command line.

This is just my assumption need to prove it.

4. Solution:

> Changing "sapsa" password to a simple password must without "#". 

5. Woo!! it's proved!!

Any suggestion welcome if you have an experience like this.

Hope this post is helpful for everyone

I've just setted up a maxdb protection based on a custum plugin at SnapCenter. Compare to what I had on SnapCreator before,
I have no solution for housekeeping the MAXDB archivelogs.

I wonder if someone already has a post snapshot script to delete maxdb archivelogs of a given SID older than "n" days.

It was so easy within snapcreator...

any idea?

I need to get an application consistant snapshot of an RDM volume, which I am during by running the following script to take a weekly backup of the D drive on a server. The only problem with this is I don't seem to be able to apply a snapmirror label to the snapshot. I can't seem to find an option to do this using the sdcli commands.

sdcli snap create -s sd_weekly.0 -D d -u
sdcli snapvault archive -force -a sd_weekly_%DATE:~6,4%%DATE:~3,2%%DATE:~0,2% -DS d sd_weekly.0
sdcli snap delete -D d -s sd_weekly.1
sdcli snap rename -d d -o sd_weekly.0 -n sd_weekly.1

So I have written the following powershell script to apply a snapmirror label to the snapshot, which works but when I run the last command to return the results it doesn't do so.

Import-ModuleDataONTAP

Connect-NcController-nameFiler1

$q=Get-NcSnapshot-Template

$q.Name ="sd_weekly.0"

$a=Get-NcSnapshot-Template

$a.SnapmirrorLabel ="Weekly"

Get-NcSnapshot-Volumeserver01_d-SnapNamesd_weekly.0|Update-NcSnapshot-Query$q-Attributes$a

Get-NcSnapshot-Volumeserver01_d-SnapNamesd_weekly.0|Select-ObjectVolume,SnapmirrorLabel

However if I run the following from putty on the filer1 it does show that it has updated the snapmirror label

 snapshot show -vserver SVM01 -volume server01_d -fields snapmirror-label

Does anyone have any idea's on how I can get this to update correctly in powershell??

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

Some of You may have noticed my previous posts regarding configuration issues, those are more likely gone. Now I've an issue regarding scheduled snapshots and theyre
Snapvaoult update.

In my SC4.0 environment I have already 4 HANA ressources (based on 4 different HANA Hosts) added and sceduled. As all these HANA Databases belong to the same customer, all HANA Volumes are located on a common "primary" svm and theyre snapvaults are on a common sv_svm as well.

All 4 setups are (I'm pretty sure...) totaly identical but one ressource causes -again- this fault during it's snapvault copy process:

SnapVault update failed for the relationship [PROD1VS001 : prod1vs001_qc5_data ==> PROD1VS003 : sv_prod1vs001_qc5_data]
with error: Snapshot copy 'prod1dhq04_hana_QC5_prod1dhq04_02-21-2018_20.05.03.2814' not found on the SnapVault
destination prod1VS003 : sv_prod1vs001_qc5_data

both, the snapshot and also the snapvault copy on NetApp side looks fine, so where's the problem or how could I get this in sync?

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.