Single Mailbox Recovery license error with ONTAP

What to do if you have the following licensing problem with SMBR:

and your Storage Virtual Machine does not work as a “Storage appliance name” input on the “License Info” page?

I just had to enable http on the 9.1 cluster and it worked with the SVM name as “Storage appliance name”:

system services web node modify -node * -http-enabled true



Data protection made easy – SnapCenter 3.0

SnapCenter is a newly designed data protection solution made by NetApp. It provides a centralized, unified and easy made interface for protecting VMs, applications like SAP HANA, file systems and databases like SQL and Oracle.
SnapCenter manages SnapShots and SnapVault/SnapMirror relationships. Additionally it has RBAC (role based access control) and remote plugin installation features.

What’ new in SnapCenter 3.0?
Beside the already provided plugins for VMWare, SQL, Oracle, NAS and file systems there are the following new and/or improved plugins:

  • New SnapCenter Plug-in for SAP HANA Database
    • Consistend Backup for SAP HANA single container and MDC single tenant databases
    • Catalog management
    • Restore and recovery using SAP HANA Studio
  • SnapCenter Plug-in for VMware vSphere
    • Restore from SnapMirror or SnapVault destination volumes
    • VSC Backup and Restore feature parity
    • Single File Restore preparation with mounting a single VMDK
    • Migration path from VSC to SnapCenter Plugin
  • SnapCenter Plug-in for NAS File Services
    • Backup from ONTAP Primary to ONTAP Secondary without the need of AltaVault
    • Restore a file or directory to the same or an alternate path
  • SnapCenter Plug-in for Oracle Database
    • Restore backups from ONTAP secondary using SnapRestore for faster restores

Additional there is ONTAP 9.2 support as well as automatic migration from SQL Express/internal SQL Server to MySQL and many other enhancements.

Don’t forget the community plugins for DB2, MySQL and MongoDB (coming soon) or write your own little Plug-in.

Check the release notes for more information and the full list of enhancements:

What I really like about SnapCenter 3.0 is that most of the features from SnapCreator are now fully included in SnapCenter (SAP HANA, Oracle). Secondly and most important IMHO is that VSC for Backup can now finally be lifecycled with SnapCenter 3.0.

There is more coming in the future like Exchange Server or community based Plug-ins, so stay tuned!


VLDB not consistent after a forced MetroCluster switchover…

After a forced MCC switchover and a successful switchback I had the following error on a customer MCC in the event log:
6/21/2017 09:56:49 cluster01-01 ERROR vldb.aggrBladeID.missing: The volume ‘cluster02_svm1_root’ is located on the aggregate with UUID ‘3b61c6fd-b6d7-4d5f-9168-81b12632581c’ whose owning dblade UUID ‘cce2f293-3bd4-11e7-85ef-a1f0d21750d7’ does not exist in the Volume Location Database.

This is an open internal bug from NetApp and can rarely happen if the VLDB has been updated without the knowledge of the other cluster:

It can be solved by executing the following command on the cluster which hosts the affected SVM:
cluster02# metrocluster resync vserver -cluster cluster02 -vserver cluster02_svm1

Check the status with:
cluster02# metrocluster vserver show
cluster01# set diag; debug vreport show; set admin

Does anyone had the same problem recently? Thanks for commenting that.

NetApp HCI is here…

Normally I don’t do postings about Product Releases or New Features of a product but this one I really want to share with you because this is a huge change to the world of HCI (Hyper Converged Infrastructure).

On 5th June NetApp announced the new HCI product which integrates into the NetApp Data Fabric.

The NetApp HCI blocks ar based on VMWare vSphere Compute Nodes and SolidFire All-Flash Storage Nodes. Each block has a total of 4 Nodes.

But what does it make special and what’s the killer feature of this product?

  • You will get all the SolidFire advantages like guaranteed Performance, world-class QOS, vVOL integration, and so on…
  • You will get full Storage power with the All-Flash HCI…
  • You can change the identity of the different Nodes from Storage to Compute and vice versa…

  • Easy management via vCenter Server Web Interface…
  • Easy setup – The appliance is setup in about 30 minutes…
  • IMHO the real killer feature is the integration into the NetApp Data Fabric like SnapMirror and StorageGrid…

As I already mentioned each block has 4 Nodes. You can also unite multiple boxes with the 25GbE/10GbE links and get more Storage/Compute power. The Datastores are attached with iSCSI. If you want to have the familiar OnTap feeling, just deploy an OnTap Select instance and you will get the whole bunch of CIFS, iSCSI and NFS power for your environment.

What can we expect next?

  • We will hopefully get more and more Hypervisors
  • NetApp HCI SnapMirror integration with OnTap 9.3
  • Integration into SnapCenter 4.0

I’m really excited about my first use of this product and I’m #DataDriven…

Changing raid type RAID-DP to RAID4 and vice versa

I just needed to change the aggr raid type of the root Aggrs for an AFF MCC from RAID-DP to RAID4. This is an easy step:

storage aggregate show-status -aggregate AGGR0_NAME
storage aggregate modify –aggregate AGGR0_NAME -raidtype raid4

And verify:

storage aggregate show-status -aggregate AGGR0_NAME

The same can be done the other way:

storage aggregate modify –aggregate AGGR_NAME -raidtype raid_dp

or with RAID-TEC

storage aggregate modify –aggregate AGGR_NAME -raidtype raid_tec

SnapCreator throws an timeout error on listing volumes or snapshots

It is so easy to do an oracle restore with NetApp SnapCreator but what happens if the listing of the snapshots for the restore running in a timeout?

This is because there are too many volumes or snapshot and the listing takes longer than the expected 2 minutes.

Just change the option


in the file to 5 minutes for example (5 minutes = 300000ms) and restart the SnapCreator service. The default is 120000ms = 2 minutes.

Grow and shrink with NetApp volume autosize

You want to use volume autosize to grow and shrink a volume?
First to the grow part. This works as it should if you have modified the following options per volume:

-autosize-increment (has a default value)
-autosize-grow-threshold-percent (has a default value)
-autosize-mode (set to grow at least – should be default)
-autosize (set to on)
-max-autosize (has a default value – 120% of the volume)

The shrink part is a bit trickier and includes these options per volume:

-autosize-increment (has a default value)
-autosize-shrink-threshold-percent (has a default value – 50%)
-autosize-mode (set to grow-shrink)
-autosize (set to on)
-min-autosize (has a default value – the initial size)

If you want to shrink the volume with autosize beware of the following:
– Adjust the min-autosize if necessary
– Shrink the “files” parameter if the autosize has the following events in “event log show” and the volume does not shrink to the minimum specified

4/3/2017 10:02:20   node01 INFORMATIONAL wafl.vol.autoSize.done: Volume Autosize: Automatic shrink of volume ‘volume1@vserver:596d33d2-88d9-33e0-9092-90383kde9229’ by 295GB complete.
4/3/2017 10:02:20   node01 NOTICE        wafl.vol.autoSize.shrink.cap: Volume Autosize: Volume ‘volume1@vserver:596d33d2-88d9-33e0-9092-90383kde9229’ could not be auto shrunk below 44.9GB to recover space.

– The “files” parameter can be modified with

volume modify -vserver SVM1 -volume volume1 -files FILECOUNT

– Attention: The “files” parameter does grow but not shrink

More Info: