Hello all.

We had to change the SnapCenter server's IP address, and now the vSphere web client SnapCenter plug-in fails to reach it.

All spinners keep running for a few seconds, then a box pops up with the following message :

Failed to load dashboard content.
Could not fetch dashboard data. Verify that SnapCenter Plugin for VMware vSphere service is running. If the service is down, start the service and try again.

I tried to update the vCenter and SnapCenter details with the arrow button on the hosts page in SnapCenter, to no avail.

Also tried to register the plugin again (https://<snapcenter_ip>:8144/register.html), same.

tcpdump on the vCenter show me that it's trying to reach the old address (ARP requests), but I have no idea where it gets it from.

Any clue on how to fix this ?

configuring DP Snapmirror with DataONTAP. I want to temporarily mount NFS on the DestinationVol side for ESXi DataStore.

In this case, should I do "Snapmirror break"? Or have to "Snapmirror delete"?

* SourceVol side has no problem sharing NFS.

*The basic settings such as junction path policy and data protocol are consistent with the source side.

I'm using VMDKs from multiple datastores/LUNs/Volumes to create a spanned Windows NTFS volume in a VMware VM.

So machine ServerA has two (2) disks connected - each hosted on separate data stores from different volumes

Disk1 [Datastore01\ServerA.vmdk] 100GB

Disk2 [Datastore02\ServerA.vmdk] 100GB

These disks are spanned to create a single "F:" drive of 200GB

Datastore01 is from the path /vol/Volume01/Lun01

Datastore02 is from the path /vol/Volume02/Lun01

I create a resource group in SnapCenter to backup the VM and include ALL spanned entities

The backup runs and I now have two snapshots.... one on each of the volumes

Volume01 - ServerA_test_12-13-2018_13.36.47.9187

Volume02 - ServerA_test_12-13-2018_13.36.47.9187

Judging by the identical snapshot names, it appears both volumes were quiesced for snapshots simultaneously to ensure a consistent snap - thus allowing for a supported method for restoring files from a spanned drive.

I haven't found specific wording in the SnapCenter or other documentation ...so I was hoping that one of my fellow community members could either confirm or refute this practice.

First, our scenario: we use SMSQL 7.2.3 and SnapDrive 7.1.5, and are about to use the Clone Wizard for the first time. Purpose is to move databases from one SQL Server to another.

Our plan: we will clone two LUNs on a production SQL Server (one containing databases and the other logs) to a second production SQL Server. We will configure clone life cycle management settings to keep the clones up-to-date. After a couple of days, we will schedule a cutover time. The DBAs will turn off databases on the source, we will run one last update of the clones, and then turn the cloned databases into the new production databases. We will then run the Clone Wizard and choose split-clone.

My question is: what is the best way to manually update the clones?  The Life Cycle settings are buried in the Clone Wizard, and I don't see an option to manually kick off an update. We could try to schedule the specific time, but we want flexibility in case we need to run it at a particular time. Any suggestions are appreciated!

Hi,

As "Snapshot backup of HANA 2.x MDC with multiple tenant" is not supported by SAP now, I'd like to know if

at least the "file-based backup of HANA MDC with multiple tenants" is possible with SnapCenter....

 in the past we need to restore some vm. restore was working without problems. after that i can remember fey days after restore my co worker found on netapp a clone. and then he unmount the clone and delete them.

 Today i found on snapcenter with smbackupjobs that a job is in database. i wanted to remove the snapshoots. but i get a error that snapshot is mounted so i cannot remove it.

i check all my volumes and found a snapshoot on one volume i delete it from netapp without any problems.

but when i want to remove snapshoot again from snapcenter i get the same error, that snapshoot is mounted. Also when i try a restore i see this snapshoots under primary snapsoots and mounted yes.

i also try
New-SmUnmountBackup -BackupName ower powershell i get a error cloen does not exist.

any ideaa how to remove the job from snapcenter db?

With Clustered DATA ONTAP, is it impossible to construct a reversed Snapmirror relationship (Restore processing) after deleting Snapmirror relation?

* I can not find a way to change Vol Type from RW to DP

* Reverse SM command can not be found in the beginning etc. etc ...

I guess that there are various obstacles and it is not feasible.

If you want to restore DestinationVol, is it necessary to create a new SM relationship after creating a new Vol on the Source side?

We've setup the monitoring and reporting setting to report every day for backups. We're getting reports of missed backups for databases no longer on the server? Do we have run through the configuration wizard again, or is there another way to fix this?

Here's a snippet of the report:

[09:55:00.033]  [SQL_QA] SnapManager for SQL Server completed the backup operations on the following number of databases on server: SQL_QA

[09:55:00.034]  [SQL_QA]    Succeeded: 5    Not run: 1      Total databases detected: 6

[09:55:00.034]  [SQL_QA] SnapManager for SQL Server completed the following backup operations:

[09:55:00.034]  [SQL_QA]    1: master - Succeeded: 1

        2: model - Succeeded: 1

        3: msdb - Succeeded: 1

        4: DB4 - Succeeded: 1

        5: DB5 - Succeeded: 0  <-- Removed from server weeks ago

        6: SSISDB - Succeeded: 1

Thanks,

Kevin

Hi,

Customer are planning to use vvol on VMware. They already have CI4N. 

I didn´t find any information that vvol is supported on CI4N.

Could you confirm that?

Is there a link for that documention?

Regards, Rafael.

Hi,

I have installed snapcenter 4.1.1 on Windows server 2016.  I have discovered Ontap 9.4 SVMs in snapcenter.  Also In snapcenter, I have configured snapcenter Windows host with plugins for Windows and SAP HANA.  I have successfully configured protection of snapcenter repository backup on an ISCSI LUN managed by snapcenter.  My main objective of this snapcenter setup is to take snapshot backup of HANA 2 multitenant backup, which is running on NFS shares on hana server.

My question is:

Can I setup snapshot backup of HANA 2 mutitenant using this single snapcenter server, which will also act as a Windows plugins host and HANA plugin host?

I will setup hdbuserstore to multiple HANA databases (both HANA 2 multitenant and HANA 1 single tenant) as Windows SYSTEM user on this server.  Any guidance on this is appreciated.

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.

I'm trying to setup Commvault to backup CIFS shares on a FAS cluster.

I have a File System iDA with a subclient pointing to \\NetApp\c$

If I add a domain account to the "Backup Operators" group on the NetApp and use that account in Commvault to "Connect As" on the subclient the backup doesn't work, I simply get "Access Denies" in the Commvault logs.

If I add the domain account to the "Administrators" group on the NetApp the backup works.

I understood that "Backup Operators" can bypass NTFS and  Share permissions to backup files.

Am I missing something in the NetApp implementation of this, or am I most likely doing something wrong with how I have the Commvault subclient configured?

Setting it to use the C$ share seems the simplest way to do this but I'm still new to NetApp and couldn't find much guidance on whether there's another recommended way.

Rich

How are you all managing snapshot policy after using snapmirror to move data?   

This is for Data OnTap 9.1p2

For example,  I have data on a netapp system in location A, where the RW volume has a snapshot policy taking a daily snap keep7 and a weekly snap keep 2.   

 i am closing that facility and need to transfer the data to location B.   I setup a DP volume in location B where I am unable to set a snapshot policy so the volume gets a snapshot policy of "none"  

Then I setup a snapmirror relationship between these 2 volumes to get the data to location B.   Once i am ready an Operations team member performs the snapmirror break and mounts the volume allowing the rest of the team access and they are able to test.   But unless the Operation team member modifiies the volume to have a snapshot policy it remains at "none" .   

Does anyone have a method to manage this or a way to make sure that the policy gets set correctly? 

Hi,
I've started with my next challenge:  snapcenter based snapshot backup and try to understand it's restore options.

In a test-environment (snapcenter 4.1.1 server, Oracle12 dbhost based on sles12) I've done some snapshot backups (including logs and controllfiles, no log bruning after backup)

Now, I've moved away all archivelogs from the archivelog location. (/oracle/PKW/oraarch/)
I expected to have them restored during the snap-restore task.

1st try:

• I chose the snapshot timestamp I'd like to restore and click on restore,
  • chose "All Datafiles"
  • chose "change database state if needed for restore and recovery"
  • chose "Force in place restore"
• select "Date and Time" and give a timestamp
• no pre ops, no post ops, no notification mail

and start

The result: Post restore error:

PL-SCO-25000: SCO_POSTRESTORE of database files failed with error: ORACLE-30036: Recovery of PKW failed due to the following error(s): [ORA-00308: cannot open archived log '/oracle/PKW/oraarch/PKWarch1_117_998124950.dbf', ORA-27037: unable to obtain file status, ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below, ORA-01195: online backup of file 1 needs more recovery to be consistent]

I suggested to have the archvelogs restord from snapshot, if logs are needed.

2nd try:

• I mounted the archvelog backup to an alternative location:
  /var/opt/snapcenter/sco/backup_mount/testvcorasap01_PKW_testvcorasap01_01-21-2019_13.23.43.8672_1/PKW/1
• • I chose the snapshot timestamp I'd like to restore,
    • chose "All Datafiles"
    • chose "change database state if needed for restore and recovery"
    • chose "Force in place restore"
  • select "Date and Time" and give a timestamp
  • specify external archive log files location
    • /var/opt/snapcenter/sco/backup_mount/testvcorasap01_PKW_testvcorasap01_01-21-2019_13.23.43.8672_1/PKW/1
  • no pre ops, no post ops, no notification mail

  and start

  The result: again Post restore error:

  PL-SCO-25000: SCO_POSTRESTORE of database files failed with error: ORACLE-30036: Recovery of PKW failed due to the following error(s): [ORA-00308: cannot open archived log '/oracle/PKW/oraarch/PKWarch1_117_998124950.dbf', ORA-27037: unable to obtain file status, ORA-01547: warning: RECOVER succeeded but OPEN RESETLOGS would get error below, ORA-01195: online backup of file 1 needs more recovery to be consistent]

in both cases archivelogs got expected at the original oraarch location.

Do I misunderstand the way to restore an oracle database from within SnapCenter?

I had the opinion that in a situation where datafiles have been corrupted AND archivelogs got manually deleted, a snapcenter based full restore should restore the required logs as well.

Hello,

TL;DR: Do we need to build an exact replica of our DB server if we're planning on using the secondary as a standby. We currently use SnapManager/SnapDrive as our SQL backup solution. This question also assumes the "main" DB server is dead or exploded in pieces.

Now for the gory details. Management would like to eliminate this single point of failure by having an exact up-to-the-minute backup of our Production DB server. They won't get that, as far as I know Windows Server 2008R2 and SQL Server 2008 don't support clustering per se, and to upgrade it to 2016 would require a lot of (wo)man hours converting and testing the code that has accumulated over years.

So, in the short term we were thinking of bringing up a much-less-powerful MSSQL Server and do log shipping. The backup would only be for the purposes of running a minimal business-needs SQL server until another could be spun up.

We run both SnapManager for SQL and SnapDrive on the DB server now, and we're not considering moving away from that solution. It does a good job. But, does that lock us into building an exact replica, meaning it would be set up with its famous insatiable requirements for CPU, RAM and storage. 

I did search The Google and The Forums, right here at cozy NetApp.) I've read several different sources that say not to mix SnapManager with 3rd party software, and I've seen slightly less articles saying it can be done. I couldn't really ask a NetApp support rep to offer advice on an unsupported kluge. Unless I deny recording the call......maybe.....

In any case, as it stands, I fear were headed toward the inevitable direction that we need to set up a near-mirror as a warm spare. To that end, I had several questions I asked NetApp support, and was admonished because it wasn't asking about a technical problem, so they don't handle that. Fair enough. I'll put it to the public.

1. Can we restore a snapmanager backup to a different server?
2. Can we simply detach the LUNs on the (presumably failed) primary and attach them to the backup server. I'm fairly certain you can't mount a LUN in two different places, we use RDM if that makes any difference.
3. What is the effect of full recovery mode in SnapManager 7.2.2? We backup with Simple Mode because SnapManager requred it. Or that's just how they set it up, I wasn't here back then. Can we convert those to full backup, or is that still off-limits?
4. If a LUN becomes inaccesible or corrupt, is the volume still available to mount to another LUN?

I have more, but this post is already long enough. Just want a starting point and we'll figure out how to proceed once we know the limitations or hidden implementations we didn't know about. Feel also to post if you have any general advice about a similar scenario, if it isn't directly related to ours. It's just good to know. I mean, it's not like we're working or anything, right?

TIA!

Steve

Hi,

Snapcenter reports can show you all backup jobs for specific resource groups and for a specific completion status if you want. What I miss here is report scheduling. 

Is it planned in future releases to be able to schedule reports (like a schedule for a daily report for all backup jobs for a specific resource group that will be sent using mail). A highly requested feature with our customers is the ability to send daily overviews of backup jobs to the responsible application owners.

Thanks 

Grtz,

Tom

Hi,

We have a requirement to protect an application with several VM’s spanning across several Datastores. There are 14 Datastores, each with one 1 Volume/FC LUN.

I know that some Plug-ins have an option to take snapshots in a Consistency Group to ensure the consistency of the snapshots across the volumes. However there are no Plug-ins for this application.

I am adding all the Datastores to the same Resource Group in the vSphere Plug-in, but I don't think this is guaranteeing that the snapshots will be taken as a consistent group.

Any ideas on how to achieve this?

Thanks

hello

my company is faced with the ultimate crash, du to a wrong action at network level we get physical corruption on all  datafiles of our DB.  our setup is :

JD edwards ERP 8.12

Oracle 10.2.0.4 Standard edition on AIX 6.1

IBM (netapp) N6240

SMO 3.2

I'm the DBA...I have 14 snapshot of the database take each night at 2.00 AM and two days of archivelogs online. The crash occure on  Friday (yesterday) at 14H56 , some of datafiles are in restore mode, cause I tried to recover them, but no success.

I tryied the restore with SMO with the following command :

smo backup restore -profile OWP_NIGHT_BCK -label 20190201020806_OWP_FULL -complete  -recover -until 2019-02-01:14:50:01 -force -verbose

but SMO check the status of the TARGET database and as it find files in recover mode it refused to restore ! :

[ INFO] ORACLE-20000: Changing state for database instance OWP from STARTED to MOUNTED.

[ INFO] ORACLE-20009: Attempting to reconnect to instance OWP after shutdown/startup.

[ INFO] ORACLE-20011: Reconnect to instance OWP successful.

[ INFO] SMO-07200: Beginning restore of database "OWP".

[ERROR] SMO-07426: Cannot perform incomplete recovery with datafile(s) "[/sl1103/oracle/OWP/ora/data/pd812t02.dbf, /sl1103/oracle/OWP/ora/indx/PRODDTAI06.dbf, /sl1103/oracle/OWP/ora/indx/prodpsoi01.dbf, /sl1103/oracle/OWP/ora/indx/svm812i01.dbf, /sl1103/oracle/OWP/ora/data/svm812t01.dbf, /sl1103/oracle/OWP/ora/indx/PRODDTAI09.dbf]" in RECOVER state.

[ERROR] SMO-13032: Cannot perform operation: Backup Restore.  Root cause: SMO-07426: Cannot perform incomplete recovery with datafile(s) "[/sl1103/oracle/OWP/ora/data/pd812t02.dbf, /sl1103/oracle/OWP/ora/indx/PRODDTAI06.dbf, /sl1103/oracle/OWP/ora/indx/prodpsoi01.dbf, /sl1103/oracle/OWP/ora/indx/svm812i01.dbf, /sl1103/oracle/OWP/ora/data/svm812t01.dbf, /sl1103/oracle/OWP/ora/indx/PRODDTAI09.dbf]" in RECOVER state.

[ INFO] SMO-07131: Unlocked database for SnapManager operations - removed lock file "/sl1103/app/oracle/product/10.2.0/dbs/.sm_lock_OWP" on host sl1103.

[ INFO] SMO-07433: Returning the database to its initial state: OWP(SHUTDOWN).

I do not understand this behaviour as the target database will erased by the restore, we need all the datafiles to be restored.

So could someone help and give the right command, we backup only data and index and archivelogs, no controlfile, no redo.

Thank you

snapcenter4.1

i have a sql server with 3 instances, for each instance i have a seperatly resource group.

and my problem is that only by one resource group (sql instance) by sql default db, master,msdb,  in snapcenter under snapmirror, and vault are showing more snapshoots that in retention is define. 

so it should be 31 but i have more as 31 , but when i check the snapshoots on netapp the number is ok.at the end i have to remove id in metadata from db repository.

the command cleanupsecondary dont do nothing.

have someone a ideea what should i do?

thanxs