SnapCenter Software 3.0.1 Installation and Setup

SnapCenter® Software 3.0.1
Installation and Setup Guide
November 2017 | 215-12681_A0
doccomments@netapp.com
Table of Contents | 3
Contents
Deciding whether to read this information ................................................ 8
SnapCenter overview ................................................................................... 9
SnapCenter features ..................................................................................................... 9
SnapCenter components .............................................................................................. 9
SnapCenter security features ..................................................................................... 13
How resources, resource groups, and policies are used in data protection ............... 14
Installation workflow for new users ......................................................... 16
Installation workflow for SnapManager users ........................................ 18
Preparing for the installation .................................................................... 21
Storage types supported by SnapCenter Plug-ins for Microsoft Windows and for
Microsoft SQL Server ......................................................................................... 21
Storage types supported by SnapCenter Plug-in for Oracle Database ...................... 23
Host requirements ..................................................................................................... 23
Domain requirements ....................................................................................
Space and sizing requirements ......................................................................
SAN host requirements .................................................................................
Supported storage systems and applications .............................................................
Supported browsers ...................................................................................................
Connection and port requirements ............................................................................
Licensing requirements .............................................................................................
SnapCenter repository identification .........................................................................
Network Load Balancing and Application Request Routing options for high
availability ...........................................................................................................
Application Request Routing requirements ..................................................
High Availability for the SnapCenter MySQL Repository ...........................
23
24
26
26
27
27
29
29
30
30
31
Installing SnapCenter and the plug-in packages ..................................... 33
SnapCenter installation worksheet ............................................................................
Installing the SnapCenter Server ...............................................................................
Logging in to SnapCenter .........................................................................................
Modifying the SnapCenter default GUI session timeout ..........................................
34
35
37
39
Configuring role-based access control for SnapCenter users .................................... 39
Types of role-based access control in SnapCenter ........................................ 39
Role-based access control permissions and roles .......................................... 40
Pre-defined SnapCenter roles and permissions ............................................. 42
Adding a user to a role .................................................................................. 45
Assigning users access to assets .................................................................... 45
Adding SnapCenter capacity licenses ....................................................................... 46
Types of SnapCenter licenses ........................................................................ 46
How SnapCenter calculates capacity usage .................................................. 47
Adding SnapCenter capacity licenses ........................................................... 47
Setting up storage system connections ...................................................................... 49
4 | SnapCenter Software Installation and Setup Guide
Setting up Run As credentials ................................................................................... 52
Authentication methods for your Run As credentials ................................... 52
Setting up your Run As credentials ............................................................... 53
Installing plug-in packages ........................................................................................ 55
Prerequisites to adding hosts and installing plug-in packages ...................... 55
SnapCenter plug-in deployment checklist ..................................................... 57
Adding hosts and installing plug-in packages on remote hosts .................... 61
Installing plug-ins on multiple remote hosts using cmdlets .......................... 68
Monitoring SnapCenter plug-in package installation status ......................... 69
Configuring the host log directory and verification server for SQL
Server ....................................................................................................... 69
Identifying available resources ...................................................................... 71
Adding resources to SnapCenter Custom Plug-ins ....................................... 72
Adding databases to SnapCenter Plug-in for SAP HANA Database ............ 74
Installing and setting up SnapCenter Plug-in for VMware vSphere ..... 77
Overview of SnapCenter Plug-in for VMware vSphere ............................................ 77
When to use the SnapCenter GUI and the vCenter GUI ........................................... 78
Installation workflow for VMware vSphere users .................................................... 79
Preparing for the installation ..................................................................................... 79
Supported storage systems ............................................................................ 80
Installation requirements for the Plug-in for VMware vSphere .................... 80
Using SnapCenter Plug-in for VMware vSphere with vCenter Servers in
Linked Mode ........................................................................................... 82
Configuring RBAC for SnapCenter Plug-in for VMware vSphere users ...... 83
Setting up SVMs and Run As credentials ..................................................... 86
Authentication and user management with vCenter RBAC and ONTAP RBAC ...... 87
Components of vCenter Server permissions ................................................. 88
Predefined roles packaged with SnapCenter Plug-in for VMware
vSphere .................................................................................................... 89
Product-level privilege required by SnapCenter Plug-in for VMware
vSphere .................................................................................................... 89
ONTAP RBAC features in SnapCenter Plug-in for VMware vSphere ......... 90
How to configure ONTAP RBAC for SnapCenter Plug-in for VMware
vSphere .................................................................................................... 91
Installing SnapCenter Plug-in for VMware vSphere ................................................ 91
Types of installation configurations .............................................................. 92
Methods for installing the SnapCenter Plug-in for VMware vSphere .......... 92
Installing the Plug-in for VMware vSphere from the SnapCenter GUI ........ 93
Installing the Plug-in for VMware vCenter from the SnapCenter Server
host by using PowerShell cmdlets ........................................................... 95
Installing the Plug-in for VMware vSphere from a local host by using
the installer GUI for the SnapCenter Plug-ins Package for Windows ..... 96
Installing the Plug-in for VMware vSphere from a local host silently
from the command line ............................................................................ 97
Updating SnapCenter and vCenter settings ............................................................... 99
Table of Contents | 5
Updating hypervisor configuration settings ................................................ 100
Updating vCenter or SnapCenter information in the SnapCenter Plug-in
for VMware vSphere ............................................................................. 100
Upgrading SnapCenter Plug-in for VMware vSphere ............................................ 100
Migrating VSC hosts ............................................................................................... 103
Prerequisites for migrating VSC hosts ........................................................ 103
Migrating a VSC host using the SnapCenter GUI ...................................... 104
Migrating a VSC host using the vCenter GUI ............................................ 106
Post-migration tasks after migrating a VSC host ........................................ 109
Restarting the vSphere web client service ................................................... 110
Preparing storage systems for SnapMirror and SnapVault
replication ............................................................................................. 113
Understanding the differences between SnapMirror and SnapVault ....................... 113
Preparing storage systems for SnapMirror replication ............................................ 114
Preparing storage systems for SnapVault replication .............................................. 115
Provisioning storage on Windows hosts ................................................. 118
Configuring LUN storage ........................................................................................ 118
Establishing an iSCSI session ..................................................................... 118
Disconnecting an iSCSI session .................................................................. 119
Creating and managing igroups ................................................................... 119
Creating and managing disks ...................................................................... 121
Creating and managing SMB shares ....................................................................... 127
Creating an SMB share ............................................................................... 127
Deleting an SMB share ............................................................................... 128
Reclaiming space on the storage system ................................................................. 128
Using the SnapCenter Plug-in for Microsoft Windows in VMware environments . 129
Supported VMware guest OS platforms ..................................................... 129
Using FC RDM LUNs in a Microsoft cluster ............................................. 130
Troubleshooting RDM LUN creation ......................................................... 132
SnapCenter Plug-in for Microsoft Windows cmdlets ............................................. 132
Upgrading SnapCenter and SnapCenter plug-in packages ................. 134
Configuring SnapCenter to check for available updates ......................................... 134
Supported MySQL upgrade scenarios ..................................................................... 135
SnapCenter upgrade limitations .............................................................................. 135
Upgrading the SnapCenter Server ........................................................................... 136
Upgrading your plug-in packages ........................................................................... 138
Uninstalling SnapCenter plug-ins and plug-in packages ...................... 140
Uninstalling plug-ins from a host using the SnapCenter GUI ................................ 140
Uninstalling Windows plug-ins using the command-line interface on the
SnapCenter Server host ..................................................................................... 141
Uninstalling plug-ins locally on a host .................................................................... 142
Uninstalling SnapCenter Plug-ins Package for Linux using the command-line
interface ............................................................................................................. 142
Removing a host from SnapCenter Server .............................................................. 143
Prerequisites to remove a host ..................................................................... 143
6 | SnapCenter Software Installation and Setup Guide
Removing a host .......................................................................................... 143
Uninstalling SnapCenter ......................................................................................... 144
Installing plug-ins independently ............................................................ 146
Installing the SnapCenter Plug-in for Microsoft Windows independently ............. 146
Preparation to install the SnapCenter Plug-in for Microsoft Windows ....... 146
Installing the SnapCenter Plug-in for Microsoft Windows silently from
the command line .................................................................................. 146
Installing SnapCenter Plug-in for Microsoft SQL Server independently ............... 148
Preparation to install the SnapCenter Plug-in for Microsoft SQL Server ... 148
Installing the SnapCenter Plug-in for Microsoft SQL Server silently
from the command line .......................................................................... 149
Installing SnapCenter Plug-in for Oracle Database independently ......................... 150
Preparation to install the SnapCenter Plug-in for Oracle Database ............ 150
Installing the SnapCenter Plug-in for Oracle Database interactively .......... 150
Installing the SnapCenter Plug-in for Oracle Database using commandline interface .......................................................................................... 151
Installing SnapCenter Plug-in for SAP HANA Database independently on the
Linux host .......................................................................................................... 151
Preparation for installing the SnapCenter Plug-in for SAP HANA
Database on the Linux host ................................................................... 152
Installing the SnapCenter Plug-in for SAP HANA Database on the
Linux host using the command-line interface ....................................... 152
Troubleshooting ........................................................................................ 153
SnapCenter installation fails to create DB with the error Invalid username/
password, please try again ................................................................................. 153
Enabling AutoSupport email notifications .............................................................. 153
Unable to create SSL or TLS secure channel .......................................................... 154
SnapCenter Plug-in Package for Microsoft Windows or SnapCenter Plug-in for
Microsoft SQL Server upgrade might fail on hosts with SQL databases on
VMDK ............................................................................................................... 154
HTTP error 503. The service is unavailable. ........................................................... 154
Unable to display SnapCenter web login page on local host .................................. 155
SnapCenter Plug-ins Package for Linux installation fails due to an incorrect
Java version ....................................................................................................... 155
SnapCenter Plug-ins Package for Linux installation fails due to improper
uninstallation .....................................................................................................
SnapCenter Plug-ins Package for Linux installation fails .......................................
Reinstalling SnapCenter Plug-ins for Linux does not update spl.properties file
with new values .................................................................................................
SnapCenter Server is unable to communicate with the host ...................................
SnapCenter plug-in loader fails with an error .........................................................
SnapCenter plug-in loader does not start automatically when the host is
restarted .............................................................................................................
Registering vCenter details task displays a warning ...............................................
Unable to access cluster IP address from outside network .....................................
155
156
157
157
157
158
159
159
Table of Contents | 7
Unable to upgrade to SnapCenter 3.0 because communication with MySQL
Server fails ......................................................................................................... 160
Unable to add storage systems after upgrading SnapCenter Server ........................ 160
Failed to uninstall SnapCenter Server ..................................................................... 161
Uninstall does not remove plug-in from vCenter .................................................... 161
Appendixes ................................................................................................ 162
Adding an ONTAP RBAC role using security login commands ............................ 162
Minimum recommended RBAC roles for SnapCenter Plug-in for VMware
vSphere .............................................................................................................. 163
Minimum ONTAP privileges required .................................................................... 164
ONTAP CLI commands for creating SVM roles .................................................... 168
Features enabled on your Windows host during installation ................................... 172
Copyright information ............................................................................. 174
Trademark information ........................................................................... 175
How to send comments about documentation and receive update
notifications .......................................................................................... 176
Index ........................................................................................................... 177
8
Deciding whether to read this information
This information describes how to install SnapCenter Server, and how to upgrade your existing
SnapCenter software, configure your SnapCenter environment, install plug-ins (except Plug-in for
NAS File Services), provision storage on Windows hosts, and prepare storage for SnapMirror and
SnapVault replication.
Before you start the installation, you should read the SnapCenter Software Release Notes.
If you are using SnapCenter as part of the Data Fabric Solution for Cloud Backup deployment, you
should look at the Data Fabric Solution for Cloud Backup information first.
Protecting NAS file services data using Data Fabric Solution for Cloud Backup and SnapCenter
If this information is not suitable for your situation, you can find more information about different
features and release-specific information for SnapCenter in the documentation available on the
SnapCenter Software Resources page on the NetApp Support Site.
NetApp SnapCenter Software Resources
9
SnapCenter overview
SnapCenter is a unified, scalable platform for application-consistent data protection. SnapCenter
provides centralized control and oversight, while delegating the ability for users to manage
application-specific backup, restore, and clone jobs. With SnapCenter, database and storage
administrators learn a single tool to manage backup, restore, and cloning operations for a variety of
applications and databases.
SnapCenter manages data across endpoints in the NetApp Data Fabric. You can use SnapCenter to
replicate data between on-premise environments, between on-premise environments and the cloud,
and between private, hybrid, or public clouds.
SnapCenter features
SnapCenter enables you to create application-consistent Snapshot copies and to complete data
protection operations, including Snapshot copy-based backup, clone, restore, and backup verification
operations. SnapCenter provides a centralized management environment, while using role-based
access control (RBAC) to delegate data protection and management capabilities to individual
application users across your SnapCenter Server and Windows or Linux hosts.
SnapCenter includes the following key features:
•
A unified and scalable platform across applications and database environments, and virtual and
nonvirtual storage, powered by SnapCenter Server
•
Role-based access control (RBAC) for security and centralized role delegation
•
Application-consistent Snapshot copy management, restore, clone, and backup verification
support from both primary and secondary destinations (SnapMirror and SnapVault)
•
Remote package installation from the SnapCenter graphical user interface
•
Nondisruptive, remote upgrades
•
A dedicated SnapCenter repository that provides fast data retrieval
•
Load balancing implemented using Microsoft Windows Network Load Balancing (NLB) and
Application Request Routing (ARR), with support for horizontal scaling
•
Centralized scheduling and policy management to support backup and clone operations
•
Centralized reporting, monitoring, and Dashboard views
SnapCenter components
SnapCenter consists of the SnapCenter Server, the SnapCenter Plug-ins Package for Windows, and
the SnapCenter Plug-ins Package for Linux. Each package contains plug-ins to SnapCenter. You can
install only the plug-ins that are appropriate for the data you want to protect.
SnapCenter includes the following components.
10 | SnapCenter Software Installation and Setup Guide
SnapCenter Server
The SnapCenter Server or Servers includes a web server, a centralized HTML5-based user interface,
PowerShell cmdlets, APIs, and the SnapCenter repository. SnapCenter enables load balancing, high
availability, and horizontal scaling across multiple SnapCenter Servers within a single user interface.
You can accomplish high availability by using Network Load Balancing (NLB) and Application
Request Routing (ARR) with SnapCenter. For larger environments with thousands of hosts, adding
multiple SnapCenter Servers can help balance the load.
The SnapCenter platform is based on a multitiered architecture that includes a centralized
management server (SnapCenter Server) and a SnapCenter host agent (SMCore):
•
If you are using the SnapCenter Plug-ins Package for Windows, the SMCore agent runs on the
SnapCenter Server and Windows plug-in host.
The SnapCenter Server communicates with the Windows plug-ins through the SMCore agent.
•
If you are using the SnapCenter Plug-ins Package for Linux:
◦
For SnapCenter Plug-in for Oracle Database, the SMCore agent running on the SnapCenter
Server host communicates with the SnapCenter Plug-in Loader (SPL) running on the Linux
host to perform different data protection operations.
◦
For SnapCenter Plug-in for SAP HANA Database and SnapCenter Custom Plug-ins, the
server communicates with these plug-ins through the SCCore agent running on the host.
SnapCenter overview | 11
The SnapCenter Server and plug-ins communicate with the SMCore agent using HTTPS.
SnapCenter enables centralized application resource management and easy data protection job
execution through the use of resource groups and policy management (including scheduling and
retention settings). SnapCenter provides unified reporting through the use of a dashboard, multiple
reporting options, job monitoring, and log and event viewers.
Information about SnapCenter operations is stored in the SnapCenter repository.
SnapCenter Plug-ins Package for Windows
This installation package includes the following plug-ins:
SnapCenter Plug-in for Microsoft SQL Server
The Plug-in for SQL Server is a host-side component of the NetApp storage solution
offering application-aware backup management of Microsoft SQL Server databases. With
the plug-in installed on your SQL Server host, SnapCenter automates Microsoft SQL
Server database backup, restore, and clone operations.
The Plug-in for Windows is a required component of the Plug-in for SQL Server
workflows.
If you want to perform data protection operations on virtualized SQL Servers that are
using VMDKs or RDMs, SnapCenter also requires the use of SnapCenter Plug-in for
VMware vSphere.
Support is provided for provisioning SMB shares only. You cannot use SnapCenter to
back up SQL Server databases on SMB shares.
SnapCenter Plug-in for Microsoft Windows
The Plug-in for Windows is a host-side component of the NetApp storage solution that
enables application-aware data protection for other plug-ins. The Plug-in for Windows
enables storage provisioning, Snapshot copy consistency, and space reclamation for
Windows hosts. It also enables application-aware data protection of Microsoft file
systems. With the plug-in installed on your Windows host, you can use SnapCenter to
create and resize disks, initiate iSCSI sessions, manage igroups, manage SMB shares, and
perform backup, restore, and clone operations on Windows file systems; for example, on
NetApp LUNs that are mounted on a Windows host.
Support is provided for provisioning SMB shares and Windows file systems on physical
and RDM LUNs. You cannot use SnapCenter to back up Windows file systems on SMB
shares.
SnapCenter Plug-in for VMware vSphere
SnapCenter Plug-in for VMware vSphere is a host-side component of the NetApp storage
solution offering support for virtualized databases and Windows file systems in addition to
support for VMs and datastores.
For details about SnapCenter in virtualized environments, see the information about
SnapCenter Plug-in for VMware vSphere.
SnapCenter Plug-in for SAP HANA Database
The SnapCenter Plug-in for SAP HANA Database is a host-side component of the
NetApp SnapCenter software that enables application-aware data protection management
of SAP HANA databases. The Plug-in for SAP HANA Database automates the backup,
restore, and cloning of SAP HANA databases in your SnapCenter environment.
The Plug-in for SAP HANA Database is installed on the HDBSQL client host, and this
host can be on either a Windows system or a Linux system.
SnapCenter Plug-ins Package for Linux
This installation package includes the following plug-ins:
12 | SnapCenter Software Installation and Setup Guide
SnapCenter Plug-in for Oracle Database
The Plug-in for Oracle Database is a host-side component of the NetApp integrated
storage solution offering application-aware backup management of Oracle databases. With
the Plug-in for Oracle Database installed on your Oracle host, SnapCenter automates
backup, restore, recovery, verify, mount, unmount, and clone operations.
Note: You can use the Plug-in for Oracle Database to manage Oracle databases for SAP
as well. However, SAP BR*Tools integration is not provided.
SnapCenter Plug-in for UNIX
The Plug-in for UNIX handles the underlying host storage stack and enables you to
perform data protection operations on Oracle databases that are running on a Linux host
by working in conjunction with the Plug-in for Oracle Database. The Plug-in for UNIX
supports the Network File System (NFS) and storage area network (SAN) protocols on a
storage system that is running ONTAP. Oracle databases are supported on VMDK and
RDM LUN when you also use SnapCenter Plug-in for VMware vSphere.
SnapCenter Plug-in for SAP HANA Database
The SnapCenter Plug-in for SAP HANA Database is a host-side component of the
NetApp SnapCenter software that enables application-aware data protection management
of SAP HANA databases. The Plug-in for SAP HANA Database automates the backup,
restore, and cloning of SAP HANA databases in your SnapCenter environment.
The Plug-in for SAP HANA Database is installed on the HDBSQL client host, and this
host can be on either a Windows system or a Linux system.
SnapCenter Plug-in for NAS File Services
The Plug-in for NAS File Services enables backing up of local NAS file services data from ONTAP
to secondary or cloud and restore it using the SnapCenter GUI. You can also back up NAS file
services data from ONTAP to cloud using ONTAP CLI commands.
•
Install SnapCenter Plug-in for NAS File Services and then back up local NAS file services data
from ONTAP to secondary storage and restore it using the SnapCenter graphical user interface
(GUI).
Protecting NAS file services data with SnapCenter
•
Back up NAS file services data from primary storage to the cloud using the Data Fabric Solution
for Cloud Backup, which includes ONTAP, AltaVault, and SnapCenter.
Protecting NAS file services data using Data Fabric Solution for Cloud Backup and SnapCenter
•
Back up NAS file services data from ONTAP to the cloud with ONTAP CLI commands instead of
the SnapCenter interface.
Protecting NAS file services data using Data Fabric Solution for Cloud Backup and ONTAP CLI
SnapCenter Custom Plug-ins
You can create custom plug-ins and use the SnapCenter Custom Plug-ins feature to manage
applications of your choice.
Custom plug-ins are created by any SnapCenter user to support applications or databases that might
not be supported by SnapCenter. They are not provided as part of the SnapCenter installation.
When custom plug-ins are installed, you can use SnapCenter to create mirror copies of backup sets
on another volume and to perform disk-to-disk backup replication. The Custom Plug-ins can be used
in both Windows and Linux environments. In Windows environments, custom applications via
custom plug-ins can optionally utilize SnapCenter Plug-in for Microsoft Windows to take file system
consistent backups.
NetApp supports the capability to create and use custom plug-ins; however, custom plug-ins you
create are not supported by NetApp.
SnapCenter overview | 13
NetApp provides MySQL, DB2, and MongoDB custom plug-in samples with SnapCenter Software.
These plug-ins can be downloaded from the NetApp Tool Chest.
Note: MySQL and DB2 custom plug-ins are supported via the NetApp communities only.
You can create your own custom plug-ins by referring to the developer’s guide for creating custom
plug-ins.
Related concepts
Preparing for the installation on page 21
Installing and setting up SnapCenter Plug-in for VMware vSphere on page 77
Related references
Host requirements on page 23
Related information
SnapCenter Software 3.0 Developer's Guide for Creating Custom Plug-ins
Protecting custom applications with SnapCenter
Protecting NAS file services data using Data Fabric Solution for Cloud Backup and SnapCenter
SnapCenter security features
SnapCenter employs strict security and authentication features to enable you to keep your data
secure.
SnapCenter includes the following security features:
•
All communication to SnapCenter uses HTTP over SSL (HTTPS).
•
All credentials in SnapCenter are protected using Advanced Encryption Standard (AES)
encryption.
•
SnapCenter uses security algorithms that are compliant with the Federal Information Processing
Standard (FIPS).
•
SnapCenter supports Transport Layer Security (TLS) 1.2 communication with ONTAP. You can
also use TLS 1.2 communication between clients and servers.
•
SnapCenter is installed inside your company's firewall to enable access to the SnapCenter Server
and to enable communication between the SnapCenter Server and the plug-ins.
•
SnapCenter API and operation access uses tokens, which expire after 24 hours.
Tokens are also encrypted with AES encryption.
•
SnapCenter integrates with Windows Active Directory for login and role-based access control
(RBAC) that govern access permissions.
•
SnapCenter PowerShell cmdlets are session secured.
•
After a default period of 15 minutes of inactivity, SnapCenter warns you that you will be logged
out in 5 minutes. After 20 minutes of inactivity, SnapCenter logs you out, and you must log in
again.
See information about changing the default log out period.
•
Login is temporarily disabled after 5 or more incorrect login attempts.
14 | SnapCenter Software Installation and Setup Guide
Related tasks
Modifying the SnapCenter default GUI session timeout on page 39
You can modify the SnapCenter GUI session timeout period to make it less than or greater than
the default timeout period of 20 minutes.
How resources, resource groups, and policies are used in
data protection
Before you use SnapCenter, it is helpful to understand basic concepts related to the backup, clone,
and restore operations you want to perform. You interact with resources, resource groups, and
policies for different operations.
•
Resources are typically databases, Windows file systems, VMs, or file shares that you back up or
clone with SnapCenter.
However, depending on your environment, resources might be database instances, Microsoft SQL
Server availability groups, Oracle databases, Oracle RAC databases, Windows file systems, a
group of custom applications, VMs, or datastores.
•
A SnapCenter resource group, is a collection of resources on a host or cluster.
When you perform an operation on a resource group, you perform that operation on the resources
defined in the resource group according to the schedule you specify for the resource group.
You can back up on demand a single resource or a resource group. You also can perform
scheduled backups for single resources and resource groups. You should use a database plug-in to
back up databases, the Plug-in for Windows to back up Windows file systems, and the Plug-in for
VMware vSphere to back up VMs and datastores.
Note: The Plug-in for VMware vSphere web client in vCenter can only back up a single VM or
datastore if it is in a resource group.
In NetApp software, resource groups were formerly known as datasets. VMware vCenter backup
jobs are called resource groups in SnapCenter.
•
The policies specify the backup frequency, copy retention, replication, scripts, and other
characteristics of data protection operations.
When you create a resource group, you select one or more policies for that group. You can also
select a policy when you perform a backup on demand for a single resource.
Think of a resource group as defining what you want to protect and when you want to protect it in
terms of day and time. Think of a policy as defining how you want to protect it. If you are backing up
all databases or backing up all file systems of a host, for example, you might create a resource group
that includes all the databases or all the file systems in the host. You could then attach two policies to
the resource group: a daily policy and an hourly policy. When you create the resource group and
attach the policies, you might configure the resource group to perform a full backup daily and
another schedule that performs log backups hourly.
The following image illustrates the relationship between resources, resource groups, and policies for
databases:
SnapCenter overview | 15
The following image illustrates the relationship between resources, resource groups, and policies for
Windows files systems:
16
Installation workflow for new users
If you are new to SnapCenter and you are not using a NetApp SnapManager product, you need to
install and configure the server and packages, provision storage, and set up replication relationships
before you can create backups.
If you are using SnapCenter as part of the NAS file services deployment, you should look at NetApp
Data Fabric Solution for Cloud Backup Resources.
Some features are available only with specific operating systems. See host requirements information.
Related references
Host requirements on page 23
Installation workflow for new users | 17
Related information
Protecting Microsoft SQL Server databases with SnapCenter
Protecting Oracle databases with SnapCenter
Protecting custom applications with SnapCenter
18
Installation workflow for SnapManager users
If you are coming to SnapCenter from a NetApp SnapManager product, you have already set up
storage layouts, defined replication relationships, and configured backups. After you install and
configure SnapCenter, you can use the SnapCenter import feature to move from your SnapManager
environment to SnapCenter.
Uninstallation of SnapManager and SnapDrive products are not required. Your SnapManager and
SnapDrive products must be present to enable you to import your data to SnapCenter.
Note: SnapCenter does not support ONTAP running in 7-Mode. You can use the 7-Mode
Transition Tool to migrate data and configurations stored on a system running in 7-Mode to a
clustered Data ONTAP system. For details, see NetApp Documentation: 7-Mode Transition Tool.
Installation workflow for SnapManager users | 19
Some features are available only with specific operating systems. See host requirements information.
Related references
Host requirements on page 23
Related information
Protecting Microsoft SQL Server databases with SnapCenter
Importing SnapManager data into SnapCenter
Protecting Oracle databases with SnapCenter
20 | SnapCenter Software Installation and Setup Guide
NetApp Documentation: 7-Mode Transition Tool
21
Preparing for the installation
You should be aware of several requirements and prerequisites before installing SnapCenter.
•
Supported storage types
•
Host requirements
•
Supported storage systems and applications
•
Supported browsers
•
Supported plug-ins for virtualized applications and virtual machines
•
Connection and port requirements
•
SnapCenter licensing
•
Use of Microsoft Network Load Balancing and Application Request Routing features
You might benefit from using a SnapCenter installation worksheet.
For the latest information on requirements, see the NetApp Interoperability Matrix.
NetApp Interoperability Matrix Tool
Related concepts
SnapCenter repository identification on page 29
Network Load Balancing and Application Request Routing options for high availability on page
30
Minimum vCenter privileges required for SnapCenter RDM operations on page 130
Related references
Host requirements on page 23
Supported storage systems and applications on page 26
Connection and port requirements on page 27
Licensing requirements on page 29
SnapCenter installation worksheet on page 34
As you prepare to install SnapCenter, you can simplify the installation process by collecting the
required information in advance.
Storage types supported by SnapCenter Plug-ins for
Microsoft Windows and for Microsoft SQL Server
SnapCenter supports a wide range of storage types on both physical machines and virtual machines.
You must verify whether support is available for your storage type before installing the package for
your host.
SnapCenter provisioning and data protection support is available on Windows Server. For the latest
information about supported versions, see the NetApp Interoperability Matrix.
NetApp Interoperability Matrix Tool
22 | SnapCenter Software Installation and Setup Guide
Machine
Storage type
Provision using
Physical server
FC-connected LUNs
SnapCenter graphical
user interface (GUI)
or PowerShell cmdlets
iSCSI-connected
LUNs
SnapCenter GUI or
PowerShell cmdlets
SMB3 (CIFS) shares
residing on a Storage
Virtual Machine
(SVM)
SnapCenter GUI or
PowerShell cmdlets
RDM LUNs
connected by an FC
or iSCSI HBA
PowerShell cmdlets
iSCSI LUNs
connected directly to
the guest system by
the iSCSI initiator
SnapCenter GUI or
PowerShell cmdlets
Virtual Machine File
Sytems (VMFS) on
VMFS or NFS
datastores
VMware vSphere or
VSC cloning utility
A guest system
connected to SMB3
shares residing on an
SVM
SnapCenter GUI or
PowerShell cmdlets
Support for provisioning
only. You cannot use
SnapCenter to back up any
data or shares using the SMB
protocol.
Virtual FC (vFC)
LUNs connected by a
virtual Fibre Channel
Switch
SnapCenter GUI or
PowerShell cmdlets
You must use Hyper-V
Manager to provision Virtual
FC (vFC) LUNs connected
by a virtual Fibre Channel
Switch.
iSCSI LUNs
connected directly to
the guest system by
the iSCSI initiator
SnapCenter GUI or
PowerShell cmdlets
A guest system
connected to SMB3
shares residing on an
SVM
SnapCenter GUI or
PowerShell cmdlets
VMware VM
Hyper-V VM
Support notes
Support for provisioning
only. You cannot use
SnapCenter to back up any
data or shares using the SMB
protocol.
Support for provisioning
only. You cannot use
SnapCenter to back up any
data or shares using the SMB
protocol.
Note: Hyper-V pass through disks and backing up databases on VHD(x) that
are provisioned on NetApp storage are not supported.
Preparing for the installation | 23
Storage types supported by SnapCenter Plug-in for Oracle
Database
SnapCenter supports a wide range of storage types on both physical and virtual machines. You must
verify the support for your storage type before installing the SnapCenter Plug-ins Package for Linux.
Storage provisioning using SnapCenter is not supported for SnapCenter Plug-ins Package for Linux.
Machine
Storage type
Physical server
FC-connected LUNs
Support notes
iSCSI-connected LUNs
NFS-connected volumes
VMware ESX
RDM LUNs connected by an
FC or iSCSI HBA
iSCSI LUNs connected
directly to the guest system by
the iSCSI initiator
VMDKs on VMFS or NFS
datastores
NFS volumes connected
directly to the guest system
The storage configurations not supported by SnapCenter Plug-in for Oracle Database are:
•
ASM on VMDK
•
ASM on RDM LUN
•
RAC on VMDK
•
RAC on RDM LUN
Host requirements
Before you begin the SnapCenter installation, you should be familiar with the host requirements,
domain requirements, sizing requirements, and operating system requirements.
Domain requirements
The SnapCenter Server must be installed on a server in the same domain as the plug-in hosts or on
servers in trusted domains.
Note: Data protection using SnapCenter requires a two-way trust relationship between the
SnapCenter Server domain and the plug-in domain. The SnapCenter Server domain and the plug-in
domain must have a trust relationship between the two domains using the Microsoft Active
Directory Domains and Trusts snap-in. While domain trusts, multidomain forests, and crossdomain trusts are supported, cross-forest domains are not.
Note: After the SnapCenter Server is installed, you must not change the domain in which the
SnapCenter host is located. If you remove SnapCenter Server from the domain it was in when
24 | SnapCenter Software Installation and Setup Guide
SnapCenter Server was installed and then try to uninstall SnapCenter Server, the uninstall
operation fails.
See Microsoft documentation about Active Directory Domains and Trusts at https://
technet.microsoft.com/en-us/library/cc770299.aspx.
For installation, you must have domain user rights with local administrator credentials.
Space and sizing requirements
Before you begin the SnapCenter installation, you should be familiar with some basic host system
space requirements and sizing requirements.
Note: Before installing SnapCenter Server and the plug-ins, it is recommended that you apply
available system and security updates.
SnapCenter Server requirements
Item
Requirements
Operating Systems
Microsoft Windows
For the latest information about supported
versions, see the NetApp Interoperability
Matrix.
NetApp Interoperability Matrix Tool
Minimum CPU count
4 cores
Minimum RAM
8 GB
Minimum hard drive space for SnapCenter
Server software and logs
10 GB
Minimum hard drive space for SnapCenter
repository
20 GB
Required Software Packages
•
Microsoft .NET Framework 4.5.2 or later
•
Windows Management Framework (WMF)
4.0
•
PowerShell 4.0
•
Java 1.8 (64-bit)
•
7-Zip 16.04 or later (64-bit)
For the latest information about supported
versions, see the NetApp Interoperability
Matrix.
NetApp Interoperability Matrix Tool
Preparing for the installation | 25
SnapCenter Plug-ins Package for Windows requirements
Item
Requirements
Operating Systems
Microsoft Windows
Note: You must enable the Cluster Shared
Volumes (CSV) feature in Windows Server
2008 R2 SP1 if you want to create CSV type
disks.
For the latest information about supported
versions, see the NetApp Interoperability
Matrix.
NetApp Interoperability Matrix Tool
Minimum RAM
1 GB
Minimum Install space
2 GB
Required Software Packages
•
Microsoft .NET Framework 4.5.2 or later
•
Windows Management Framework (WMF)
4.0
•
PowerShell 4.0
For the latest information about supported
versions, see the NetApp Interoperability
Matrix.
NetApp Interoperability Matrix Tool
SnapCenter Plug-ins Package for Linux requirements
Item
Requirements
Operating Systems
•
Red Hat Enterprise Linux
•
Oracle Linux
Note: If you are using Oracle database on
LVM in Oracle Linux or RHEL 6.6 or 7.0
operating systems, you must install the
latest version of Logical Volume
Management (LVM).
•
SUSE Linux Enterprise Server (SLES)
For the latest information about supported
versions, see the NetApp Interoperability
Matrix.
NetApp Interoperability Matrix Tool
Minimum RAM
1 GB
Minimum Install space
2 GB
26 | SnapCenter Software Installation and Setup Guide
Item
Requirements
Required Software Packages
Java 1.7 (64-bit)
For the latest information about supported
versions, see the NetApp Interoperability
Matrix.
NetApp Interoperability Matrix Tool
SAN host requirements
If your SnapCenter host is part of a FC/iSCSI environment, you might need to install additional
software on the system to enable access to ONTAP storage.
If your SnapCenter host is part of a SAN environment, you might need to install the following
software:
•
Host Utilities
The Host Utilities support FC and iSCSI, and allow you to use MPIO on your Windows Servers.
•
ONTAP DSM for Windows MPIO
This software works with Windows MPIO drivers to manage multiple paths between NetApp and
Windows host computers.
For more information, see the Host Utilities and ONTAP DSM for Windows MPIO product
documentation and the Interoperability Matrix Tool on the NetApp Support Site.
NetApp Documentation
NetApp Interoperability Matrix Tool
Supported storage systems and applications
Before you begin your installation, it is helpful to understand the basic storage system and
application.
ONTAP
SnapCenter requires different versions on ONTAP depending on the data you need to protect.
Data protection needs
ONTAP version required
For Data Fabric Solution for Cloud Backup (with the
SnapCenter Plug-in for NAS File Services and AltaVault cloud
protection)
ONTAP 9.1
For NAS file services protection to secondary storage without
AltaVault
ONTAP 8.3
For other SnapCenter plug-ins
ONTAP 8.2.2 and later
SnapCenter Server repository
While installing SnapCenter 3.0 or later, MySQL Server 5.7.13 is installed on the SnapCenter Server
host. From SnapCenter 3.0, other Microsoft SQL Server or MySQL Server versions are not supported
for new installation.
Note: If you were using MySQL Server 5.7.13 with earlier version of SnapCenter but have to
upgrade the MySQL version, you can upgrade to any version later than 5.7.13 but less than 5.8.
Preparing for the installation | 27
If you have been using Microsoft SQL Server database with earlier version of SnapCenter, while
upgrading to SnapCenter 3.0 or later, Microsoft SQL Server is upgraded to MySQL Server and all
the repository data is migrated to the MySQL repository database.
Note: The time taken to migrate all the repository data depends on the repository size.
Plug-in applications and databases
For the latest information on requirements, see the NetApp Interoperability Matrix.
NetApp Interoperability Matrix Tool
Related information
NetApp Interoperability Matrix Tool
NetApp Documentation: Virtual Storage Console for VMware vSphere
Supported browsers
SnapCenter Software can be used on multiple browsers.
•
Chrome
•
Internet Explorer
•
◦
Only default-level security is supported.
Making changes to Internet Explorer security settings results in significant browser display
issues.
◦
Internet Explorer compatibility view must be disabled.
Microsoft Edge
SnapCenter Plug-in for VMware vSphere supports the same browsers that VMware vSphere vCenter
supports.
For the latest information about supported versions, see the NetApp Interoperability Matrix.
NetApp Interoperability Matrix Tool
Connection and port requirements
Connections and ports must meet minimum requirements before you can install SnapCenter.
•
Applications cannot share a port
All ports must be dedicated to the appropriate application.
•
Customizable ports
For customizable ports, you can select a custom port when you install if you do not want to use
the default port.
You cannot modify a customizable port number after you install SnapCenter. To change a port
number after installation, you must uninstall SnapCenter, and then install again.
•
Fixed ports
For fixed ports, you must accept the default port number.
•
Firewalls
◦
Firewalls, proxies, or other network devices should not interfere with connections.
28 | SnapCenter Software Installation and Setup Guide
◦
If you specify a custom port when you install SnapCenter, you must add a firewall rule on the
plug-in host for that port for the SnapCenter plug-in loader (SPL).
Note: This rule does not apply to SnapCenter Plug-in for VMware vSphere. A firewall rule
is added on SnapCenter Plug-in for VMware vSphere hosts when the plug-in is installed.
SnapCenter uses the following default ports:
Type of port
Default port
SnapCenter port
8146 (HTTPS), bidirectional, fixed, as in the URL https://server:8146
Used for communication between the SnapCenter client (the SnapCenter user)
and SnapCenter Server. Also used for communication from plug-in hosts to
SnapCenter Server.
SnapCenter SMCore
communication port
8145 (HTTPS), bidirectional, customizable
Used for communication between SnapCenter Server and hosts where
SnapCenter plug-ins are installed.
MySQL port
3306 (HTTPS), bidirectional
Used for communication between SnapCenter and MySQL repository database.
Windows plug-in hosts
135 and 445 (TCP). If 135 and 445 are unavailable, SnapCenter searches ports
1024 through 1034 for open ports.
These ports are used for communication between the SnapCenter Server and the
host where the plug-in is being installed. The ports are used by the Windows
Management Instrumentation (WMI) service to push plug-in package binaries
to plug-in hosts. The ports must be open only on the plug-in host and can be
closed after installation.
Linux plug-in hosts
21 and 22 (SSH)
These ports are used for communication between the SnapCenter Server and the
host where the plug-in is being installed. The ports are used by SnapCenter to
copy plug-in package binaries to Linux plug-in hosts and should be open or
excluded from the firewall or iptables.
SnapCenter Plug-ins Package for
Windows
8145 (HTTPS), bidirectional, customizable
Used for communication between SMCore and hosts where the SnapCenter
plug-ins are installed.
The communication path needs to be open between the SVM management LIF,
the plug-in host, and the SnapCenter Server
SnapCenter Plug-ins Package for
Linux
8145 (HTTPS), bidirectional, customizable
Used for communication between SMCore and hosts where the SnapCenter
plug-ins are installed.
The communication path needs to be open between the SVM management LIF
and the SnapCenter Server.
Custom plug-ins for SnapCenter
9090 (HTTPS), fixed
This is an internal port used only on the custom plug-in host; no firewall
exception is required.
Communication between SnapCenter Server and custom plug-ins is routed
through port 8145.
Preparing for the installation | 29
Type of port
Default port
SnapCenter Plug-in for VMware
vSphere port
8144 (HTTPS), bidirectional, customizable
Used for communications from the vCenter vSphere web client and from the
SnapCenter Server.
Note: You can specify a different port only when you install the plug-in. You
cannot modify the port after installation.
VMware vSphere vCenter Server
port
443 (HTTPS), bidirectional
Used for communication between the host for the SnapCenter Plug-in for
VMware vSphere and vCenter.
SnapCenter Plug-in for SAP
HANA Database ports
3instance_number13 or 3instance_number15, HTTP or HTTPS,
bidirectional, and customizable
For a multitenant database container (MDC) single tenant, the port number ends
with 13; for non MDC, the port number ends with 15.
For example, 32013 is the port number for instance 20 and 31015 is the port
number for instance 10.
Related information
Protecting NAS file services data using Data Fabric Solution for Cloud Backup and SnapCenter
Licensing requirements
Several licenses are required for data protection operations. The Release Notes contain details about
the licenses required for your environment.
SnapCenter Software 3.0.1 Release Notes
SnapCenter repository identification
The SnapCenter repository, sometimes referred to as the NSM database, stores information and
metadata for every aspect of SnapCenter.
When you install SnapCenter 3.0, MySQL Server is installed on the SnapCenter Server host as the
repository database.
Note: If there is an existing application that relies on a specific version of MySQL Server, that
should be resolved before installing SnapCenter.
If you have been using Microsoft SQL Server database with earlier version of SnapCenter, while
upgrading to SnapCenter 3.0, Microsoft SQL Server is upgraded to MySQL Server and all the
repository data is migrated to the MySQL repository database.
Note: The time taken to migrate all the repository data depends on the repository size.
The SnapCenter repository stores information and metadata about the following:
•
Backup, clone, restore, and verification metadata
•
Reporting, job, and event information
•
Host and plug-in information
•
Role, user, and permission details
•
Storage system connection information
30 | SnapCenter Software Installation and Setup Guide
SnapCenter can back up its own repository using its repository management features.
Network Load Balancing and Application Request Routing
options for high availability
Network Load Balancing (NLB) and Application Request Routing (ARR) are Microsoft features that
together provide a unified high-availability and load-balancing configuration. When you install
SnapCenter, you have the option to configure NLB and ARR. To use NLB and ARR in SnapCenter,
you must choose the option during installation; you cannot configure this later manually.
If you are using SnapCenter in a production environment and plan to deploy the user interface over
multiple SnapCenter Server hosts, you should configure SnapCenter with both ARR and NLB.
SnapCenter does not support other types of load balancing.
To better understand the NLB high-availability capabilities, see the following Microsoft
documentation:
•
Network Load Balancing
To better understand ARR, see the following Microsoft documentation:
•
Application Request Routing Version 2 Overview
•
Application Request Routing download
•
Deployment Recommendations for Application Request Routing
The MySQL NSM repository database is installed automatically on the SnapCenter host. In a NLB
setup, while installing SnapCenter on the second node, you join the NLB of the first node and a copy
of the NSM database is created on the second node.
When you implement NLB in a SnapCenter environment, your network adapter and NLB cluster
must have the same IP setting and Dynamic Host Configuration Protocol (DHCP) must be disabled
on the network adapter. To configure NLB, you must have a dedicated IP address (virtual IP) that will
be exposed from all NLB nodes. For example, if you select IPv4 virtual IP, all adapters on all nodes
designated for NLB must support IPv4 format. The same applies for IPv6: all adapters and cluster IP
must have IPv6 support. Additionally, when you add an SVM to an NLB configuration, each node in
the NLB configuration must resolve to the same name or FQDN.
When SnapCenter is installed on an cluster that uses the Microsoft Distributed Transaction
Coordinator (MS DTC) service, you must add a firewall exception for the service. If a firewall
exception for MS DTC is not added on NLB cluster nodes, resource group creation and host removal
operations fail.
For details about viewing NLB and ARR status in SnapCenter, see SnapCenter administration
documentation.
Related information
Performing administrative tasks with SnapCenter
Application Request Routing requirements
Application Request Routing (ARR) requires specific IIS features and configuration. It is a best
practice to install ARR and its required modules before you install SnapCenter, and then allow
SnapCenter to configure ARR during installation.
If you are using SnapCenter with ARR, each plug-in host must be able to communicate with
SnapCenter using the Network Load Balancing (NLB) IP address.
Preparing for the installation | 31
If you do not see the SnapCenter UI when you browse to https://NLB IP Address:8146 in
Internet Explorer (IE), you must add the NLB IP address as a trusted site in IE on each plug-in host,
or you must disable IE Enhanced Security on each plug-in host.
NetApp KB Article 2025082: SnapCenter in an HA configuration with Application Request Routing
enabled.
ARR requires the following additional IIS features:
•
URL Rewrite
•
External Cache module
Additionally, ARR requires the following:
•
Both .NET 3.5 and .NET 4.5.2
•
Wildcard-based, self-signed certificate created and used across all servers
•
A rule configured in the Web Server to avoid request-forward looping
You can ignore the message “Ready for load balancing” on servers. This message has a value of Yes
only when applications are provisioned in IIS using the Web Farm Network.
The following is the complete list of components required by ARR, listed in the order that they must
be installed. These components are also required by the SnapCenter installer to properly set up the
web farm and to add the appropriate routing rules:
1. IIS
2. Web Platform Installer 3.0
3. Web Platform Installer 5 (upgrade from 3.0)
4. Web Deploy 2.0
5. Web Deploy 3.5 (upgrade from 2.0)
6. Web Farm Framework 2.0 (requires IIS and Web Platform Installer 3.0)
7. Application Request Routing 3.0
8. URL Rewrite Module 2.0 (installed by ARR 3.0)
It is recommended that you check the Windows Add/Remove Programs list to verify that this
module is listed.
9. External Disk Cache (installed by ARR 3.0)
It is recommended that you check the Windows Add/Remove Programs list to verify that this
module is listed.
For more information about ARR, see the following Microsoft documentation:
•
Application Request Routing Version 2 Overview
•
Application Request Routing download
•
Deployment Recommendations for Application Request Routing
High Availability for the SnapCenter MySQL Repository
MySQL replication is a feature of MySQL Server that enables you to replicate data from one MySQL
database server (“master”) to another MySQL database server (“slave”). SnapCenter supports
32 | SnapCenter Software Installation and Setup Guide
MySQL replication for high availability only on two Network Load Balancing-enabled (NLBenabled) nodes.
SnapCenter performs read or write operations on the master repository and routes its connection to
the slave repository when there is a failure on the master repository. The slave repository then
becomes the master repository. SnapCenter also supports reverse replication, which is enabled only
during failover.
If you want to use the MySQL high availability (HA) feature, you must enable Application Request
Routing (ARR) while installing SnapCenter and configure Network Load Balancing (NLB) on the
first node. The MySQL repository is installed on this node as part of the installation. While installing
SnapCenter on the second node, you must join to the NLB of the first node and create a copy of the
MySQL repository on the second node.
SnapCenter provides the Get-SmRepositoryConfig and Set-SmRepositoryConfig PowerShell
cmdlets to manage MySQL replication.
You must be aware of the limitations related to the MySQL HA feature:
•
NLB and MySQL HA are not supported beyond two nodes.
•
Switching from a SnapCenter standalone installation to an NLB installation or vice versa and
switching from a MySQL standalone setup to MySQL HA are not supported.
•
Automatic failover is not supported if the slave repository data is not synchronized with the
master repository data.
You can initiate a forced failover by using the Set-SmRepositoryConfig cmdlet.
•
When failover is initiated, jobs that are running might fail.
If failover happens because MySQL Server or SnapCenter Server is down, then any jobs that are
running might fail. After failing over to the second node, all subsequent jobs run successfully.
Related information
SnapCenter Software 3.0.1 Windows Cmdlet Reference Guide
33
Installing SnapCenter and the plug-in packages
You must follow this order when installing SnapCenter and the plug-in packages: install SnapCenter,
log in, perform configuration tasks, and then add the hosts and deploy plug-in packages.
You can optionally perform several installation and configuration procedures by using PowerShell
cmdlets. For details, use the SnapCenter cmdlet help or see the cmdlet reference information.
Steps
1. SnapCenter installation worksheet on page 34
As you prepare to install SnapCenter, you can simplify the installation process by collecting the
required information in advance.
2. Installing the SnapCenter Server on page 35
You can use the InstallShield wizard to install the SnapCenter Server.
3. Logging in to SnapCenter on page 37
Through SnapCenter role-based access control, users or groups are assigned roles and resources.
When you log in to the SnapCenter graphical user interface, you log in with an Active Directory
account.
4. Modifying the SnapCenter default GUI session timeout on page 39
You can modify the SnapCenter GUI session timeout period to make it less than or greater than
the default timeout period of 20 minutes.
5. Configuring role-based access control for SnapCenter users on page 39
SnapCenter role-based access control enables you to delegate control of SnapCenter resources to
different users or groups of users. You can create and modify roles, and add resource access to
users at any time, but when you are setting up SnapCenter for the first time, you should at least
add Active Directory users or group to roles, and then add resource access to those users or
groups.
6. Adding SnapCenter capacity licenses on page 46
Before you add a storage system to SnapCenter, you must install one or more SnapCenter
licenses.
7. Setting up storage system connections on page 49
To perform data protection and provisioning operations with SnapCenter, first you must set up the
storage system connections that give SnapCenter access to ONTAP storage. Setting up these
connections also involves configuring AutoSupport and Event Management System (EMS)
features.
8. Setting up Run As credentials on page 52
To execute jobs on a specific database instance, you must set up Run As credentials with the
correct authentication method. Run As account credentials authenticate users so they can perform
SnapCenter operations, including Windows scheduling and Linux account access.
9. Installing plug-in packages on page 55
You must register hosts with SnapCenter and install the plug-in packages on the managed host by
using the SnapCenter graphical user interface (GUI) or PowerShell cmdlet.
Related concepts
Installing SnapCenter Plug-in for VMware vSphere on page 91
Related information
SnapCenter Software 3.0.1 Windows Cmdlet Reference Guide
SnapCenter Software 3.0 Linux Command Reference Guide
34 | SnapCenter Software Installation and Setup Guide
SnapCenter installation worksheet
As you prepare to install SnapCenter, you can simplify the installation process by collecting the
required information in advance.
Required information
Your value
Application Request Routing
(ARR)
You must decide whether you want to enable ARR for high
availability. ARR must be installed and configured before you
install SnapCenter.
Network Load Balancing
(NLB)
If you want to enable NLB, you must know whether you want to
create an NLB cluster or join an existing cluster.
If you want to create an NLB cluster, you must obtain the
following information:
•
NLB Cluster name:
•
NLB Cluster primary IP:
•
Interface name:
If you want to join an existing NLB cluster, you must obtain the
following information:
•
First NLB node IP:
•
Interface name:
You can configure NLB before installing SnapCenter or
configure during installation.
Credentials
Installation location
You must know the credentials that you want to use to log in to
SnapCenter as the administrator. You need a domain user with
local administrator permissions:
•
Account (Domain\User):
•
Password:
You can browse and provide the path where you want to install
SnapCenter Server and SnapCenter repository.
•
Location of SnapCenter Server web component and
SnapCenter SMCore Service:
•
Location of SnapCenter repository:
Installing SnapCenter and the plug-in packages | 35
Required information
Your value
SnapCenter port configuration
Make sure you specify the correct port numbers. To change a
port number, you must reinstall SnapCenter.
If you specify a custom port when you install SnapCenter, you
must add a firewall rule on the plug-in host for that port for the
SnapCenter plug-in loader (SPL).
•
SnapCenter port: 8146 fixed
•
SnapCenter SMCore communication port:
•
MySQL port:
•
Plug-in ports:
For additional details, see connection and port requirements.
MySQL Database connection
If you are using MySQL as the SnapCenter database repository,
you must specify the password.
Note: The password cannot contain the following characters:
[ ], ", ', `, ^, %, &, <, >, (, ), |, /, \, ;, =, #, comma, space, Newline, and Tab.
Related references
Connection and port requirements on page 27
Installing the SnapCenter Server
You can use the InstallShield wizard to install the SnapCenter Server.
Before you begin
•
Your SnapCenter host system must be up to date with Windows updates with no pending system
restarts.
•
You must have enabled Windows installer debugging.
See the Microsoft web site for information about enabling Windows Installer logging.
https://support.microsoft.com/en-us/kb/223300
•
The SnapCenter Server must be installed on a server that is part of a domain.
Note: SnapCenter Server cannot be installed on a domain controller.
•
A two-way trust relationship between the SnapCenter Server domain and the plug-in domain
using the Microsoft Active Directory Domains and Trusts snap-in must have been established.
While domain trusts, multi-domain forests, and cross-domain trusts are supported, cross-forest
domains are not supported.
See Microsoft documentation about Active Directory Domains and Trusts.
https://technet.microsoft.com/en-us/library/cc770299.aspx
•
If you plan to use Microsoft Application Request Routing (ARR) to perform load balancing
across multiple SnapCenter Servers with a single UI, you must install ARR and Microsoft Web
Farm Framework (WFF) before installing SnapCenter.
NetApp Knowledgebase.
36 | SnapCenter Software Installation and Setup Guide
Steps
1. Download the SnapCenter Server installation package from the NetApp Support Site at
mysupport.netapp.com.
2. Install the SnapCenter Server by performing one of the following:
•
Double-click the downloaded .exe file to launch the SnapCenter Server installer.
•
From a Windows command prompt on the local host, change to the directory where you
downloaded the installer and run the .exe file.
You can install in debug mode by running:
SnapCenterversion.exe/debuglog dir_path\log_name.log
3. In the Prerequisites Validation screen, the host is validated to see if it meets the requirements to
install the SnapCenter Server.
The Microsoft .NET version and RAM are validated against the minimum requirements. If the
minimum requirements are not met appropriate error or warning messages are displayed.
If the restart of the host is pending, a warning message is displayed.
Note: If you get an error stating minimum requirements are not met even though the host meets
all the requirements, you should skip prerequisite validation. From the command prompt, you
should install by running:
SnapCenterversion.exe ALLOW_PREREQ_NEXT=true
4. In the Network Load Balancing screen, if you want to enable and configure NLB select Enable
and configure NLB on the host.
a. Select Create new NLB cluster and enter the details for first node.
b. After creating the NLB cluster on the first node, when you run the installer on a second node,
select Join existing NLB cluster and enter the details.
When you install SnapCenter on two nodes in an NLB cluster, you must register the NLB
cluster name and IP address with your DNS server before you run the SnapCenter Installer on
the second node in the cluster.
Note: The NLB and ARR enabled configuration supports load balancing but the NLB
cluster node fail over is not supported by SnapCenter Plug-in for NAS File Services.
Note: You must run the SnapCenter Server installation package on the second node of the NLB
setup only after successfully installing the SnapCenter Server on the first node. You must never
try installing SnapCenter on both the nodes simultaneously.
5. In the Application Request Routing screen, select Configure ARR farm for SnapCenter to
configure ARR.
This screen is displayed only if ARR is correctly installed.
6. In the Credentials screen, enter the credentials that you want to use to log in to SnapCenter as the
administrator.
You need a domain user with local Windows administrator permissions.
Note: After installing SnapCenter you must log into SnapCenter to setup RBAC and configure
access for other users or groups.
7. In the Installation Folder screen, browse and provide the path where you want to install
SnapCenter Server and SnapCenter repository.
Installing SnapCenter and the plug-in packages | 37
•
•
The SnapCenter Server web component and SnapCenter SMCore Service are installed in the
corresponding folders at the default location C:\Program Files\NetApp.
The repository component is installed at the default location C:\ProgramData\NetApp
\SnapCenter.
Note: In a NLB setup for the second node, the installation path used for installing on first node
is auto populated and is non configurable.
8. In the SnapCenter Ports Configuration screen, enter the port details.
The default ports are auto populated but you can specify a custom port. In a NLB setup for the
second node, the SnapCenter ports used while installing on the first node are auto populated and
is non configurable.
9. In the MySQL Database Connection screen, enter the MySQL database password.
Note: The MySQL database password cannot contain the following characters: [ ], ", ', `, ^, %,
&, <, >, (, ), |, /, \, ;, =, #, comma, space, New-line, and Tab.
While installing SnapCenter on the first node, MySQL NSM database is installed. While
installing SnapCenter on the second node, you must join the NLB of the first node and a copy of
the NSM database is created on the second node. Thus, MySQL replication for high availability is
configured.
Note: MySQL NSM database is not uninstalled if you do not uninstall SnapCenter from the
last NLB node. Therefore, when you re-install SnapCenter, you must enter the same port
specified during the earlier installation.
10. In the Ready to Install screen, click Install.
Log files are listed (oldest first) in the %temp% folder.
Related references
SnapCenter installation worksheet on page 34
As you prepare to install SnapCenter, you can simplify the installation process by collecting the
required information in advance.
Related information
Protecting NAS file services data using Data Fabric Solution for Cloud Backup and SnapCenter
Logging in to SnapCenter
Through SnapCenter role-based access control, users or groups are assigned roles and resources.
When you log in to the SnapCenter graphical user interface, you log in with an Active Directory
account.
About this task
During the installation, the SnapCenter Server Installation wizard creates a shortcut and places it on
the desktop where SnapCenter is installed. Additionally, at the end of the installation, the Install
wizard displays the SnapCenter URL based on information you supplied during the installation,
which you can copy if you want to log in from a remote system.
Attention: Closing just the SnapCenter browser tab does not log you off of SnapCenter if you have
multiple tabs open in your web browser. To end your connection with SnapCenter, you must log
off of SnapCenter either by clicking the Sign out button or shutting down the entire web browser.
38 | SnapCenter Software Installation and Setup Guide
Attention: For security reasons, it is recommended not to allow your browser to save your
SnapCenter password.
The default GUI URL is a secure connection to the default port 8146 on the server where the
SnapCenter Server is installed (https://server:8146). If you provided a different server port during
the SnapCenter installation, that port is used instead.
For Network Load Balance (NLB) deployment, you must access SnapCenter using the NLB cluster
IP (https://NLB_Cluster_IP:8146). If you do not see the SnapCenter UI when you navigate to
https://NLB_Cluster_IP:8146 in Internet Explorer (IE), you must add the NLB IP address as a
trusted site in IE on each plug-in host, or you must disable IE Enhanced Security on each plug-in
host.
NetApp KB Article 2025082: SnapCenter in an HA configuration with Application Request Routing
enabled.
In addition to using the SnapCenter GUI, you can use the following interfaces:
•
PowerShell cmdlets on Windows hosts
You can use PowerShell cmdlets on SQL databases to script configuration, backup, restore,
verification, and clone operations. You can use PowerShell cmdlets to script data protection
operations on Windows file systems and NAS file services data.
•
SnapCenter command-line interface (CLI), sccli for Linux hosts.
You can use the CLI to script data protection operations.
Note: Some cmdlets have changed in SnapCenter 3.0. If you use cmdlets in older versions of
SnapCenter scripts, you might need to update your scripts.
For details, see the SnapCenter cmdlet or SnapCenter CLI documentation.
Steps
1. Launch SnapCenter from the shortcut located on your local host desktop, from the URL provided
at the end of the installation, or from the URL provided to you by your SnapCenter administrator.
2. Enter your user credentials:
Domain\UserName
Note: If you are logging into SnapCenter for the first time, you must log in using the
credentials that you provided during the install process.
3. If you are assigned more than one role, from the Role box, select the role you want to use for this
login session.
Your current user and associated role are shown in the upper right of SnapCenter once you are
logged in.
Result
If you are using SnapCenter for the first time, the Storage Systems page displays, and the Get Started
pane is expanded.
Related information
SnapCenter Software 3.0.1 Windows Cmdlet Reference Guide
SnapCenter Software 3.0 Linux Command Reference Guide
Installing SnapCenter and the plug-in packages | 39
Modifying the SnapCenter default GUI session timeout
You can modify the SnapCenter GUI session timeout period to make it less than or greater than the
default timeout period of 20 minutes.
About this task
As a security feature, after a default period of 15 minutes of inactivity, SnapCenter warns you that
you will be logged out of the web UI in 5 minutes. SnapCenter logs you out of the web UI after 20
minutes of inactivity, and you must log in again.
Steps
1. In the left navigation pane, click Settings > Global Settings.
2. In the Global Settings page, click Configuration Settings.
3. In the Session Timeout field, enter the new session timeout in minutes, and then click Save.
Configuring role-based access control for SnapCenter users
SnapCenter role-based access control enables you to delegate control of SnapCenter resources to
different users or groups of users. You can create and modify roles, and add resource access to users
at any time, but when you are setting up SnapCenter for the first time, you should at least add Active
Directory users or group to roles, and then add resource access to those users or groups.
Note that user or group accounts are not created using SnapCenter, but are created in Active
Directory in the operating system or database.
Types of role-based access control in SnapCenter
SnapCenter role-based access control (RBAC), ONTAP permissions, and SnapCenter Plug-in for
VMware vSphere RBAC enable SnapCenter administrators to create roles and set access
permissions. This centrally managed access empowers application administrators to work securely
within delegated environments.
SnapCenter uses the following types of role-based access control:
•
SnapCenter RBAC
•
SnapCenter plug-in RBAC (for some plug-ins)
•
Application-level RBAC
•
ONTAP permissions
SnapCenter RBAC
Roles and permissions
SnapCenter ships with predefined roles with permissions already assigned. You can assign
users or groups of users to these roles. You can also create new roles and manage
permissions and users.
•
Assigning permissions to users or groups
You can assign permissions to users or groups to access SnapCenter objects such as
hosts, storage connections, and resource groups. You cannot change the permissions of
the SnapCenterAdmin role.
40 | SnapCenter Software Installation and Setup Guide
You can assign RBAC permissions to users and groups within the same forest and to
users belonging to different forests. You cannot assign RBAC permissions to users
belonging to nested groups across forests.
•
Assigning users or groups to roles
You can assign users or groups to roles.
Note: If you create a custom role, it must contain all of the permissions of the
SnapCenter Admin role. If you only copy some of the permissions, for example, Host
add or Host remove, you cannot perform those operations.
Authentication
Users are required to provide authentication during login, through the graphical user
interface (GUI) or using PowerShell cmdlets. If users are members of more than one role,
after entering login credentials, they are prompted to specify the role they want to use.
Users are also required to provide authentication to run the APIs.
SnapCenter Plug-in for VMware vSphere RBAC
For details about SnapCenter in virtualized environments, see the information about SnapCenter
Plug-in for VMware vSphere.
Application-level RBAC
SnapCenter uses Run As credentials to verify that authorized SnapCenter users also have applicationlevel permissions.
For example, if you want to perform Snapshot copy and data protection operations in a SQL Server
environment, you must set Run As credentials with the proper Windows or SQL credentials. The
SnapCenter Server authenticates the credentials set using either method. If you want to perform
Snapshot copy and data protection operations in a Windows file system environment on ONTAP
storage, the SnapCenter admin role must have admin privileges on the Windows host.
Similarly, if you want to perform data protection operations on an Oracle database and if the
operating system (OS) authentication is disabled in the database host, you must set Run As
credentials with the Oracle database or Oracle ASM credentials. The SnapCenter Server
authenticates the credentials set using one of these methods depending on the operation.
ONTAP permissions
You must have vsadmin account permissions to access the storage system.
Related concepts
Minimum ONTAP privileges required on page 164
Related tasks
Adding an ONTAP RBAC role using security login commands on page 162
Related references
Minimum recommended RBAC roles for SnapCenter Plug-in for VMware vSphere on page 163
ONTAP CLI commands for creating SVM roles on page 168
Role-based access control permissions and roles
SnapCenter role-based access control (RBAC) enables you to create roles and add permissions to
those roles, and then assign users or groups of users to the roles. This enables SnapCenter
Installing SnapCenter and the plug-in packages | 41
administrators to create a centrally managed environment, while application administrators can
manage data protection jobs. SnapCenter ships with some predefined roles and permissions.
SnapCenter roles
SnapCenter ships with the following predefined roles. You can either assign users and groups to these
roles or create new roles.
When you assign a role to a user, only jobs that are relevant to that user are visible in the Jobs page
unless you assigned the SnapCenter Admin role.
•
•
•
•
App Backup and Clone Admin
Backup and Clone Viewer
Infrastructure Admin
SnapCenterAdmin
SnapCenter Plug-in for VMware vSphere roles
For details about SnapCenter in virtualized environments, see the information about SnapCenter
Plug-in for VMware vSphere.
SnapCenter permissions
SnapCenter provides the following permissions:
•
•
•
•
•
•
•
•
•
•
•
•
Resource Group
Policy
Backup
Host
Storage Connection
Clone
Provision (only for Microsoft SQL database)
Dashboard
Reports
Restore
◦ Full Volume Restore (only for Custom Plug-ins)
Resource
Plug-in privileges are required from the administrator for non-administrators to perform resource
discovery operation.
Plug-in Install\Uninstall
Note: When you enable Plug-in Installation permissions, you must also modify the Host
permission to enable reads and updates.
•
•
•
•
Migration
Mount (only for Oracle database)
Unmount (only for Oracle database)
Catalog (only for NAS File Services)
Related references
Minimum recommended RBAC roles for SnapCenter Plug-in for VMware vSphere on page 163
Pre-defined roles and permissions for the Plug-in for VMware vSphere on page 84
42 | SnapCenter Software Installation and Setup Guide
Pre-defined SnapCenter roles and permissions
SnapCenter ships with pre-defined roles, each with a set of permissions already enabled. When
setting up and administering role-based access control (RBAC), you can either use these pre-defined
roles or create new ones.
SnapCenter includes the following pre-defined roles:
•
SnapCenter Admin role
•
Backup and Clone Viewer role
•
App Backup and Clone Admin role
•
Infrastructure Admin role
For information about pre-defined roles and permissions for SnapCenter Plug-in for VMware
vSphere users, see the information about SnapCenter Plug-in for VMware vSphere.
When you add a user to a role, you must assign either the StorageConnection permission to enable
Storage Virtual Machine (SVM) communication, or assign an SVM to the user to enable permission
to use the SVM. The Storage Connection permission enables users to create SVM connections.
For example, a user with the SnapCenter Admin role can create SVM connections and assign them to
a user with the App Backup and Clone Admin role, which by default does not have permission to
create or edit SVM connections. Without an SVM connection, users cannot complete any backup,
clone, or restore operations.
SnapCenter Admin role
The SnapCenter Admin role has all permissions enabled. You cannot modify the permissions for this
role. You can add users and groups to the role or remove them.
App Backup and Clone Admin role
The App Backup and Clone Admin role has the permissions required to perform administrative
actions for application backups and clone-related tasks. This role does not have permissions for host
management, provisioning, storage connection management, or remote installation.
Permissions
Enabled
Create
Read
Update
Delete
Resource Group
Not
applicable
Yes
Yes
Yes
Yes
Policy
Not
applicable
Yes
Yes
Yes
Yes
Backup
Not
applicable
Yes
Yes
Yes
Yes
Host
Not
applicable
Yes
Yes
Yes
Yes
Storage Connection
Not
applicable
No
Yes
No
No
Clone
Not
applicable
Yes
Yes
Yes
Yes
Provision
Not
applicable
No
Yes
No
No
Installing SnapCenter and the plug-in packages | 43
Permissions
Enabled
Create
Read
Update
Delete
Dashboard
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Reports
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Restore
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Resource
Yes
Yes
Yes
Yes
Yes
Plug-in Install/Uninstall
No
Not
applicable
Not
applicable
Not
applicable
Migration
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Mount
Yes
Yes
Not
applicable
Not
applicable
Not
applicable
Unmount
Yes
Yes
Not
applicable
Not
applicable
Not
applicable
Full Volume Restore
No
No
Not
applicable
Not
applicable
Not
applicable
Backup and Clone Viewer role
The Backup and Clone Viewer role has read-only view of all permissions. This role also has
permissions enabled for discovery, reporting, and access to the Dashboard.
Permissions
Enabled
Create
Read
Update
Delete
Resource Group
Not
applicable
No
Yes
No
No
Policy
Not
applicable
No
Yes
No
No
Backup
Not
applicable
No
Yes
No
No
Host
Not
applicable
No
Yes
No
No
Storage Connection
Not
applicable
No
Yes
No
No
Clone
Not
applicable
No
Yes
No
No
Provision
Not
applicable
No
Yes
No
No
Dashboard
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Reports
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Restore
No
No
Not
applicable
Not
applicable
Not
applicable
44 | SnapCenter Software Installation and Setup Guide
Permissions
Enabled
Create
Read
Update
Delete
Resource
No
No
Yes
Yes
No
Plug-in Install/Uninstall
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Migration
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Mount
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Unmount
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Full Volume Restore
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Infrastructure Admin role
The Infrastructure Admin role has permissions enabled for host management, storage management,
provisioning, resource groups, remote installation reports, and access to the Dashboard. This role also
enables resource group, backup, restore, and catalog permissions for NAS File Services management.
Permissions
Enabled
Create
Read
Update
Delete
Resource Group
Not
applicable
Yes
Yes
Yes
Yes
Policy
Not
applicable
No
Yes
Yes
Yes
Backup
Not
applicable
Yes
Yes
Yes
Yes
Host
Not
applicable
Yes
Yes
Yes
Yes
Storage Connection
Not
applicable
Yes
Yes
Yes
Yes
Clone
Not
applicable
No
Yes
No
No
Provision
Not
applicable
Yes
Yes
Yes
Yes
Dashboard
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Reports
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Restore
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Resource
Yes
Yes
Yes
Yes
Yes
Plug-in Install/Uninstall
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Migration
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Installing SnapCenter and the plug-in packages | 45
Permissions
Enabled
Create
Read
Update
Delete
Mount
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Unmount
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Full Volume Restore
No
No
Not
applicable
Not
applicable
Not
applicable
Adding a user to a role
To configure role-based access control for SnapCenter users, you can add users or groups to a role.
The role determines the options that SnapCenter users can access.
Before you begin
You must have logged in as the SnapCenterAdmin role.
About this task
SnapCenter includes several predefined roles. You can either add users to these roles or create new
roles.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Roles.
3. In the Roles page, select the role to which you want to add the user.
4. Click Modify.
5. Click Next until you reach the Users/Groups page of the wizard.
6. In the Users/Groups page, specify the domain to which the user belongs.
7. In the user or group name field, enter a user or group name and click Add.
Repeat to add additional users or groups to the selected role.
8. Click Next to view the summary, and then click Finish.
Related tasks
Adding an ONTAP RBAC role using security login commands on page 162
Assigning users access to assets
Setting up role-based access control (RBAC) for users is a two-step process. After you add a user or
group to a role that contains the appropriate permissions, you must assign the user access to
SnapCenter assets, such as hosts and storage connections. This enables users to perform the actions
for which they have permissions on the assets that are assigned to them.
About this task
You can assign access to users even if the user is not part of a role. This helps you add users;
however, you must add the user to a role at some point to take advantage of RBAC efficiencies.
You can also assign Run As credential maintenance to a user.
46 | SnapCenter Software Installation and Setup Guide
If you are planning to replicate Snapshot copies, you must assign the storage connection for both the
source and destination volume to the user performing the operation. You should add assets before
assigning access to the users.
You must use the Admin role to assign permissions to Plug-in for VMware vSphere. For details about
SnapCenter in virtualized environments, see the information about SnapCenter Plug-in for VMware
vSphere.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click User Access.
3. In the User Access page, select the type of asset from the Asset drop-down list.
4. In the Asset table, select the asset and click Assign.
5. Provide the domain name to which the user or group belongs.
6. Choose whether you want to assign access to a user or a group.
7. Enter the user or group name and click Add.
If you are not sure about the name, use a more advanced search by clicking the Search users or
group heading, typing a partial name, and clicking Search.
8. Repeat this procedure until each user or group has access to all the required assets.
9. Click OK to save your changes.
Related tasks
Adding resources to SnapCenter Custom Plug-ins on page 72
Adding SnapCenter capacity licenses
Before you add a storage system to SnapCenter, you must install one or more SnapCenter licenses.
Types of SnapCenter licenses
You should understand the types of SnapCenter licenses and the purpose of each so you can
determine which licenses you require for your environment.
The type of SnapCenter licenses you install depends on your storage environment and the features
that you want to use.
SnapCenter Standard Capacity or Standard controller licenses
A SnapCenter Standard Capacity or Standard controller license enables you to add an SVM to a
SnapCenter instance to support backup and recovery of ONTAP storage, Clone Life Cycle
management, basic reporting, task automation, host file systems (Windows, Linux, UNIX), support
for custom applications or databases, update of Snapshot copies to SnapMirror and SnapVault
secondary destinations, virtualization with VMware, and support for enterprise applications
(Microsoft SQL Server, Oracle).
You must have either a Standard Capacity license installed on the SnapCenter Server or a controller
license installed on your ONTAP storage system.
The type of standard license you install depends on your storage platform:
Installing SnapCenter and the plug-in packages | 47
•
FAS and All Flash FAS
The license is included in the Premium Bundle and is installed on the primary storage system
using OnCommand System Manager or the storage system command line. The license provides
unlimited storage usage.
•
ONTAP Select and ONTAP Cloud
The license is available as an a la carte license and is installed on the SnapCenter Server. The
license is charged on the used storage capacity that is managed by SnapCenter.
The SnapCenter Standard Capacity license is available as a 90-day trial license with 100 TB capacity
entitlement.
NAS File Services license
A NAS File Services license provides license support for NAS shares backup to the cloud using
AltaVault, file catalog, and service level objective (SLO) data protection.
A NAS File Services license is required when you use the Data Fabric Solution for Cloud Backup
features in SnapCenter and the Plug-in for NAS File Services.
FAS, All Flash FAS, ONTAP Select, ONTAP Cloud: A la carte license, charged on the used storage
capacity that is managed by SnapCenter
The NAS File Services license is available as a 90-day trial license with 100 TB capacity entitlement.
How SnapCenter calculates capacity usage
SnapCenter automatically calculates capacity usage once a day at midnight on the storage it manages.
You should be aware of how SnapCenter calculates capacity.
If you are using ONTAP Cloud or ONTAP Select as your storage platform, you must have a
SnapCenter Standard Capacity license installed to enable SnapCenter features such backup and
restore. When you are using a Standard Capacity license, SnapCenter calculates the unused capacity
by deducting the used capacity on all volumes from the total licensed capacity. If used capacity
exceeds the licensed capacity, an overuse warning is displayed on the SnapCenter Dashboard. If you
configured capacity thresholds and notifications in SnapCenter, an email is sent when the used
capacity reaches the threshold you specify.
If you are using FAS or All Flash FAS as your storage platform, you must have a SnapCenter
controller license to enable SnapCenter features such as backup and restore. If you are using a
controller-based license, the capacity used by SnapCenter features such as backup and restore is not
calculated by SnapCenter.
If you want to use the Data Fabric Solution for Cloud Backup features in SnapCenter or the Plug-in
for NAS File Services, the NAS File Services license is required.
Adding SnapCenter capacity licenses
Depending on your requirements and the features that you want to use, you must purchase and install
one or more SnapCenter licenses.
Before you begin
•
You must log in as the SnapCenter Admin user.
•
If you want to log in to the NetApp Support Site using SnapCenter to obtain your licenses, you
must have the license serial numbers.
•
If you are using a license file to add your license, you must know the location of the license file.
48 | SnapCenter Software Installation and Setup Guide
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Software.
3. In the License section of the Software page, click Add (
) to add a license.
4. In the Add SnapCenter License wizard, select one of the following methods to obtain the license
you want to add:
For this field...
Do this...
NetApp Support Site
(NSS)
a. Enter your NSS user name and password.
b. Enter your SnapCenter license serial number.
Note: This is not your storage controller serial number.
NetApp License File
a. Browse to the location of the license file, and then select it.
b. Click Open.
5. In the Notifications page, enter the capacity threshold at which SnapCenter sends email, EMS,
and AutoSupport notifications.
The default threshold is 90 percent.
6. To configure the SMTP server for email notifications, click Settings > Global Settings >
Notification Server Settings, and then enter the following details:
For this field...
Do this...
Email preference
Choose either Always or Never.
Provide email settings
If you select Always, specify the following:
•
Sender email address
•
Receiver email address
•
Optional: Edit the default Subject line
The default subject reads as follows: “SnapCenter License
Capacity Notification”
7. If you want to have Event Management System (EMS) messages sent to the storage system
syslog or have AutoSupport messages sent to the storage system for failed operations, select the
appropriate check boxes.
Enabling AutoSupport is recommended to help troubleshoot issues you might experience.
8. Click Next.
9. Review the summary, and then click Finish.
Installing SnapCenter and the plug-in packages | 49
Setting up storage system connections
To perform data protection and provisioning operations with SnapCenter, first you must set up the
storage system connections that give SnapCenter access to ONTAP storage. Setting up these
connections also involves configuring AutoSupport and Event Management System (EMS) features.
Before you begin
•
You must have permissions in the Infrastructure Admin role to create storage connections.
•
You must not have host plug-in installations in progress while adding a storage system connection
because the host cache might not be updated, and databases might indicate “Not available for
back” or “Not on NetApp storage” in SnapCenter.
•
Storage system names must be unique
SnapCenter does not support multiple storage systems with the same name on different clusters.
Each storage system supported by SnapCenter must have a unique name.
About this task
•
AutoSupport and EMS
When you configure storage systems, you can also set up AutoSupport and EMS features. The
AutoSupport tool collects data about the health of your system and automatically sends the data
to NetApp technical support, enabling them to troubleshoot your system. If you enable these
features, SnapCenter sends AutoSupport information to the storage system and EMS messages to
the storage system syslog when a resource is protected, a restore operation completes
successfully, or an operation fails. These two features are available only if you choose ONTAP
Cluster or ONTAP SVM as the storage type.
•
SnapMirror or SnapVault destinations
If you are planning to replicate Snapshot copies to a SnapMirror or SnapVault destination, you
must set up storage system connections for the destination SVM as well as the source SVM.
Steps
1. In the left navigation pane, click Storage Systems.
2. In the Storage Systems page, click New.
50 | SnapCenter Software Installation and Setup Guide
The New Storage Connection wizard begins.
3. In the New Storage Connection wizard, provide the following information:
For this field…
Do this…
Storage Type
Select ONTAP SVM.
Note: If you add a new ONTAP SVM connection and you have
already added an ONTAP Cluster for the Data Fabric Solution
for Cloud Backup, after you add the SVM, you must run the
Modify Storage Connection wizard on the ONTAP Cluster
that you already added so that the following updates are made:
•
The SVM is in the NSM database.
•
CIFS server discovery is enabled on the SVM.
•
The SnapCenter cache is updated with information about the
new SVM.
Installing SnapCenter and the plug-in packages | 51
For this field…
Do this…
Platform
Select either FAS or All Flash FAS, or ONTAP Cloud or ONTAP
Select.
If you select Secondary, SnapCenter does not perform a license
check immediately.
Storage System
Enter the storage system name or IP address.
Note: Storage system names, not including the domain name,
must be 15 characters or fewer. To create storage system
connections with names with more than 15 characters, you can
use the Add-SmStorageConnection PowerShell cmdlet.
SnapCenter does not support multiple SVMs with the same name
on different clusters. Each SVM supported by SnapCenter must
have a unique name.
User name/Password
ONTAP: Enter the credentials used (usually vsadmin) to access
the storage system. Use vsadmin when adding an SVM. Use
admin when adding a cluster.
Protocol
Select the protocol used for connection to the SVM that was
configured during SVM setup, typically HTTPS.
Port
Enter the port that the storage system accepts.
The defaults typically work.
Timeout
Enter the time in seconds that should elapse before communication
attempts are halted. The default value is 60 seconds.
Preferred IP
If the SVM has multiple management interfaces, select the
Preferred IP check box, and then enter the preferred IP address
for SVM connections.
Event Management
System (EMS) &
AutoSupport Settings
Applicable only if you choose ONTAP Cluster or ONTAP SVM as
the storage type.
If you want to have Event Management System (EMS) messages
sent to the storage system syslog or have AutoSupport messages
sent to the storage system for applied protection, completed
restore operations, or failed operations, select the appropriate
check box.
When you select the Send AutoSupport Notification for failed
operations to storage system check box, the Log SnapCenter
Server events to syslog check box is also selected because EMS
messaging is required to enable AutoSupport notifications.
If you have questions about these values, consult your storage administrator.
4. Click OK.
52 | SnapCenter Software Installation and Setup Guide
Setting up Run As credentials
To execute jobs on a specific database instance, you must set up Run As credentials with the correct
authentication method. Run As account credentials authenticate users so they can perform
SnapCenter operations, including Windows scheduling and Linux account access.
Authentication methods for your Run As credentials
Run As credentials use different authentication methods depending upon the application or
environment. Run As credentials authenticate users so they can perform SnapCenter operations. You
should create one set of Run As credentials for installing plug-ins and another set for data protection
operations.
Windows authentication
The Windows authentication method authenticates against Active Directory. For Windows
authentication, Active Directory is set up outside of SnapCenter. SnapCenter authenticates with no
additional configuration. You need a Windows Run As credential to perform tasks such as adding
hosts, installing plug-in packages, and scheduling jobs.
VMware vSphere
The RunAs credential user should be a domain administrator or a regular domain user with local
administrator privileges on the system on which the SnapCenter Plug-in for VMware vSphere is to be
installed.
SQL Server authentication
The SQL authentication method authenticates against a SQL Server instance. This means that a SQL
Server instance must be discovered in SnapCenter. Therefore, before adding a SQL Run As
credential, you must add a host, install plug-in packages, and refresh resources. You need SQL Server
authentication for performing operations such as scheduling on SQL Server or discovering resources.
Linux authentication
The Linux authentication method authenticates against a Linux host. You need Linux authentication
during the initial step of adding the Linux host and installing the SnapCenter Plug-ins Package for
Linux remotely from the SnapCenter GUI.
Oracle database authentication
The Oracle database authentication method authenticates against an Oracle database. You need an
Oracle database authentication to perform operations on the Oracle database if the operating system
(OS) authentication is disabled on the database host. Therefore, before adding a Oracle database Run
As credential, you must create an Oracle user in the Oracle database with sysdba privileges.
Oracle ASM authentication
The Oracle ASM authentication method authenticates against an Oracle Automatic Storage
Management (ASM) instance. If you are required to access the Oracle ASM instance and if the
operating system (OS) authentication is disabled on the database host, you need an Oracle ASM
authentication. Therefore, before adding an Oracle ASM Run As credential, you must create an
Oracle user in the ASM instance.
Installing SnapCenter and the plug-in packages | 53
RMAN catalog authentication
The RMAN catalog authentication method authenticates against the Oracle Recovery Manager
(RMAN) catalog database. If you have configured an external catalog mechanism and registered your
database to catalog database, you need to add RMAN catalog authentication.
Related tasks
Setting up your Run As credentials on page 53
Setting up your Run As credentials
SnapCenter uses Run As credentials to authenticate users for SnapCenter operations. You should
create Run As credentials for installing SnapCenter plug-ins and additional Run As credentials for
performing data protection operations on databases or Windows file systems.
About this task
•
Linux hosts
You must set up Run As credentials for installing plug-ins on Linux hosts.
Although you are allowed to create Run As credentials for Linux after deploying hosts and
installing plug-ins, the best practice is to create Run As credentials after you add SVMs, before
you deploy hosts and install plug-ins. You must set up the Run As credentials for the root user or
a non root user who has sudo privileges to install and start the plug-in process.
•
Windows hosts
You must set up Windows Run As credentials before installing plug-ins.
Set up the Run As credentials with administrator privileges, including administrator rights on the
remote host.
•
SQL authentication on Windows hosts
You must set up SQL Run As credentials after installing plug-ins.
If you are deploying SnapCenter Plug-in for Microsoft SQL Server, you must set up SQL Run As
credentials after installing plug-ins. Set up a Run As credential for a user with SQL Server
sysadmin permissions.
The SQL authentication method authenticates against a SQL Server instance. This means that a
SQL Server instance must be discovered in SnapCenter. Therefore, before adding a SQL Run As
credential, you must add a host, install plug-in packages, and refresh resources. You need SQL
Server authentication for performing operations such as scheduling or discovering resources.
•
Custom Plug-ins applications
The plug-in uses the Run As credentials selected or created when adding a resource. If a resource
does not require a Run As credentials during data protection operations, you can set the Run As
credentials as None.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Run As Credentials.
3. Click New.
54 | SnapCenter Software Installation and Setup Guide
4. In the Run As Credentials page, do the following:
For this field…
Do this…
Run As name
Enter a name for the Run As credentials.
User name/Password
Enter the user name and password used for authentication.
You must add the domain name as the prefix to the username.
Authentication Mode
Select the authentication mode that you want to use.
If you select the SQL authentication mode, you must also specify
the SQL server instance and the host where the SQL instance is
located.
Use sudo privileges
Applicable to Linux users only. Select the Use sudo privileges
check box if you are creating run as credentials for a non-root user.
5. Click OK.
After you finish
After you finish setting up Run As credentials, you might want to assign Run As credential
maintenance to a user or group of users on the My SnapCenter Assets page.
Related concepts
Authentication methods for your Run As credentials on page 52
Installing SnapCenter and the plug-in packages | 55
Related tasks
Configuring sudo privileges for non-root users to install Plug-in for Oracle Database on page 57
Installing plug-in packages
You must register hosts with SnapCenter and install the plug-in packages on the managed host by
using the SnapCenter graphical user interface (GUI) or PowerShell cmdlet.
Related concepts
Installing SnapCenter Plug-in for VMware vSphere on page 91
Prerequisites to adding hosts and installing plug-in packages
Before you add a host and install the plug-ins packages, you must complete all the requirements.
General
If you are using iSCSI, the iSCSI service must be running.
Windows hosts
•
You must have a domain user with local administrator privileges with local login permissions on
the remote host.
•
If you manage cluster nodes in SnapCenter, you must have a user with administrative privileges to
all the nodes in the cluster.
•
If you are installing SnapCenter Plug-in for Microsoft SQL Server, you must have a user with
sysadmin permissions on the SQL Server.
SnapCenter Plug-in for Microsoft SQL Server uses Microsoft VDI Framework, which requires
sysadmin access.
Microsoft Support Article 2926557: SQL Server VDI backup and restore operations require
Sysadmin privileges
•
If SnapManager for Microsoft SQL Server is installed, you must have stopped or disabled the
service and schedules.
If you plan to import backup or clone jobs into SnapCenter, do not uninstall SnapManager for
Microsoft SQL Server.
•
Data protection using SnapCenter requires a two-way trust relationship between the SnapCenter
Server domain and the plug-in domain using the Microsoft Active Directory Domains and Trusts
snap-in.
Although domain trusts, multidomain forests, and cross-domain trusts are supported, cross-forest
domains are not.
https://technet.microsoft.com/en-us/library/cc770299.aspx
•
If you are installing SnapCenter Plug-in for VMware vSphere from the SnapCenter GUI, the host
must have Microsoft Net 4.5.2 or later installed. You can install the Plug-in for VMware vSphere
on either the SnapCenter Server host or on a dedicated Windows host. For the latest information
on requirements, see the NetApp Interoperability Matrix.
NetApp Interoperability Matrix Tool
Linux hosts
•
You must have enabled the password-based SSH connection for the root or non-root user.
56 | SnapCenter Software Installation and Setup Guide
From SnapCenter 2.0, SnapCenter Plug-in for Oracle Database can be installed by a non-root
user. However, you must configure the sudo privileges for the non-root user to install and start the
plug-in process.
•
You must have installed Java 1.7 or 1.8, 64-bit, on your Linux host.
If you are using Windows 2016 for the SnapCenter Server host, you must install Java 1.8, 64-bit.
For the latest information on requirements, see the NetApp Interoperability Matrix.
Java Downloads for All Operating Systems
NetApp Interoperability Matrix Tool
•
For Oracle databases that are running on a Linux host, you must install both SnapCenter Plug-in
for Oracle Database and SnapCenter Plug-in for UNIX.
Note: You can use the Plug-in for Oracle Database to manage Oracle databases for SAP as
well. However, SAP BR*Tools integration is not supported.
•
If you are using Oracle database 11.2.0.3 or later, you must install the 13366202 Oracle patch.
vSphere hosts
•
Virtualized databases and virtualized Windows file systems
When you add a vSphere host, SnapCenter Plug-in for VMware vSphere is automatically
installed. This plug-in facilitates data protection operations for virtualized databases and
virtualized Windows file systems that reside on virtual machine disk files (VMDKs) or raw
device mapping (RDM) configurations.
•
VMs and datastores on VMware vSphere
If you used VSC with SnapCenter 2.0 to protect VMs and datastores, then you must migrate each
VSC host to SnapCenter Plug-in for VMware vSphere. During the migration, SnapCenter Plug-in
for VMware vSphere is installed and a SnapCenter Plug-in for VMware vSphere web client is
added to vCenter. You can also manually install SnapCenter Plug-in for VMware vSphere on a
host to protect VMs and datastores using the web client on vCenter.
◦
You must be a user with SnapCenter Admin privileges.
◦
When you register SnapCenter Plug-in for VMware vSphere on vCenter, you must specify a
vCenter administrator as the vCenter user.
Custom Plug-ins
•
You must have created the custom plug-in for your application by referring to the Custom Plugins Developer’s Guide.
•
If you want to manage MySQL or DB2 applications, you must download the MySQL and DB2
Custom Plug-ins that are provided by NetApp.
•
You must have installed Java 1.7 or 1.8, 64-bit, on your Linux or Windows host.
•
The Custom Plug-ins must be available on the client host from where the add host operation is
performed.
SnapCenter Plug-in for SAP HANA Database
•
You must have installed Java 1.7 or Java 1.8 64-bit, on your Linux or Windows host.
•
You must have installed SAP HANA database interactive terminal (HSBSQL client) on the host.
For Windows, the HDBSQL client must be running using the “SYSTEM” Windows user.
•
For Windows, plug-in Creator Service should be running using the “LocalSystem” windows user,
which is the default behavior when Plug-in for SAP HANA is installed as domain administrator.
Installing SnapCenter and the plug-in packages | 57
•
For Windows, user store keys should be created as SYSTEM user. For example, hdbuserstore -u
SYSTEM -i set
•
For Linux host, user store keys are accessed as OS database user.
•
SnapCenter Server should have access to the 8145 or custom port of Plug-in for SAP HANA host.
Related tasks
Configuring sudo privileges for non-root users to install Plug-in for Oracle Database on page 57
Configuring sudo privileges for non-root users to install Plug-in for Oracle Database
SnapCenter 2.0 and later enables a non-root user to install the Plug-in for Oracle Database and to
start the plug-in process. You must configure sudo privileges for the non-root user to provide access
to several paths.
About this task
You must configure sudo privileges for the non-root user to provide access to the following paths:
•
/tmp/sc-plugin-installer/snapcenter_linux_host_plugin.bin
•
/custom_location/NetApp/snapcenter/spl/installation/plugins/uninstall
•
/custom_location/NetApp/snapcenter/spl/bin/spl
Steps
1. Log in to the Linux host on which you want to install the Plug-in for Oracle Database.
2. Add the following lines to the /etc/sudoers file by using the visudo Linux utility.
Example
Cmnd_Alias SCCMD = sha224:checksum_value== /tmp/sc-plugin
-installer/snapcenter_linux_host_plugin.bin, /opt/NetApp/snapcenter/spl/installation/
plugins/uninstall, /opt/NetApp/snapcenter/spl/bin/spl
Cmnd_Alias PRECHECKCMD = sha224:checksum_value== /tmp/netapp/Linux_Prechecks.sh
non_root_user ALL=(ALL) NOPASSWD:SETENV: SCCMD, PRECHECKCMD
Defaults:non_root_user !visiblepw
Defaults:non_root_user !requiretty
Important: The example should be used only as a reference for creating your own data.
non_root_user is the name of the non-root user that you created. For information about the
latest checksum values, see the Release Notes.
SnapCenter Software 3.0.1 Release Notes
SnapCenter plug-in deployment checklist
Several steps are required to deploy and configure the SnapCenter plug-ins packages. While the
procedures for performing these tasks include more detail, you might find it helpful to use the
abbreviated checklists.
•
Actions you should complete before adding a host on page 58
•
Actions you should complete while adding a host on page 58
•
Actions you should complete to configure a backup for a newly added host on page 60
If one person is deploying the plug-in packages and performing all tasks, that person should be
assigned to the SnapCenter Admin role to perform all these actions. However, if you want others to
58 | SnapCenter Software Installation and Setup Guide
perform various tasks, you must assign roles to other users. When you are setting up SnapCenter for
the first time, you must at least add users to roles, and then add resource access to those users.
For details, see information about configuring role-based access control (RBAC).
Actions you should complete before adding a host
Actions
Steps
Notes
Add Storage Virtual
Machines
1. Select Storage Systems.
Add a connection for each SVM
that backs storage for the host.
2. Click New to add an SVM.
Add Run As credentials
1. Select Settings > Run As
Credentials.
2. Click New to add a Run As
credential.
If you are planning to use SQL
authentication, instead of
completing this step now,
complete this step later, after you
add a host and discover resources.
If you are deploying Plug-in for
SQL Server, and you are installing
using Windows authentication, the
user must have sysadmin
permissions on the SQL Server.
Actions you should complete while adding a host
Before you complete actions in this checklist, you must complete the actions required before adding
hosts.
Installing SnapCenter and the plug-in packages | 59
Actions
Add host and deploy
plug-in packages
Steps
1. Select Hosts > Managed
Hosts > Add.
2. Complete the wizard to initiate
plug-in package deployment.
Monitor plug-in
package installation
status
1. Select Monitor > Jobs.
2. Wait until the plug-in package
installation job finishes, which
might take several minutes.
Notes
You add a host, or a cluster that
has many nodes, and deploy the
plug-in package one host at a time.
To deploy multiple hosts using a
PowerShell cmdlet, see
information about installing
multiple hosts.
•
Adding a cluster
If you add a cluster (Windows
Server Failover Clustering
(WSFC), Oracle real
application clusters (RAC)), or
SQL Always On Availability
Groups, SnapCenter performs
a remote installation on all
cluster nodes.
•
Adding a host with virtualized
databases or file systems
To protect virtualized
resources (SQL Server, Oracle,
and Windows file systems),
you must add a vSphere type
host, which causes SnapCenter
to install Plug-in for VMware
vSphere.
•
Adding a vCenter host
To protect VMs and datastores,
you must add a vSphere host
type and provide vCenter
information, which causes
SnapCenter to install Plug-in
for VMware vSphere and
register it as a web client on
VMware vSphere vCenter.
If you do not want Plug-in for
VMware vSphere installed on
the same host as the vCenter
host, then provide the
SnapCenter host information
on the "Host" page of the
wizard, and the vCenter host
information on the "Plug-ins to
install" page of the wizard.
After this process finishes, the
plug-in package is installed on the
remote host.
60 | SnapCenter Software Installation and Setup Guide
Actions
Steps
Notes
Add resources (only if
you are using Custom
Plug-ins)
1. Select Resources > Add
Resources.
After this process finishes,
resources will be available for data
protection operations.
2. Complete the wizard to add
resources to Custom Plug-ins.
Configure the plug-in
1. Select Hosts > Managed
log directory and
Hosts.
verification server (only
if you are using Plug-in 2. Select the host and click
for SQL Server)
Configure Plug-in.
Note: If you are protecting
VMs, you must add resources
from the SnapCenter Plug-in for
VMware vSphere GUI in
vCenter.
The log directory shows only
NetApp LUNs.
3. Complete the wizard.
Actions you should complete to configure a backup for a newly added host
To configure backups for VMs and datastores, you must use the SnapCenter Plug-in for VMware
vSphere GUI in vCenter.
Actions
Create a backup policy
Steps
1. Click Settings > Policies.
2. Select a plug-in, then click
New, and then complete the
wizard.
Create a backup
resource group
1. Click Resources.
2. Select a plug-in, then click
New Resource Group.
3. Complete the wizard, selecting
resources from the newly
added host.
Backup now
1. Click Resources, then select a
plug-in, and then click View
and select Resource Group
from the list.
2. Select the newly added
resource group and click
Backup Now.
3. Select a policy from the dropdown list and click Backup.
Notes
You can copy an existing policy.
Installing SnapCenter and the plug-in packages | 61
Actions
Steps
Monitor backup
progress
1. Select Monitor > Jobs.
Notes
2. Monitor the backup job for
completion.
Related tasks
Installing plug-ins on multiple remote hosts using cmdlets on page 68
Adding hosts and installing plug-in packages on remote hosts
You must use the SnapCenter Add Host wizard to add hosts and then install the plug-ins packages.
The plug-ins are automatically installed on the remote hosts. You can add a host and install plug-in
packages either for an individual host or a cluster.
Before you begin
You must be a user that is assigned to a role that has the plug-in install and uninstall permissions,
such as the SnapCenter Admin.
About this task
•
•
Installing plug-ins on a cluster:
◦
If you install plug-ins on a cluster (WSFC, Oracle RAC, or SQL Always On Availability
Groups), they are installed on all of the nodes of the cluster.
◦
You cannot install SnapCenter Plug-in for VMware vSphere on a cluster.
Installing SnapCenter Plug-in for VMware vSphere:
◦
When you add a type “vSphere” host, SnapCenter installs SnapCenter Plug-in for VMware
vSphere and installs a VMware vSphere web client in vCenter.
Separate sections in this guide contain details for installing this plug-in.
Steps
1. In the left navigation pane, click Hosts.
2. Verify that Managed Hosts is selected at the top.
3. Click Add.
4. On the Hosts page, do the following:
62 | SnapCenter Software Installation and Setup Guide
For this field…
Do this…
Host OS
Select the type of host:
Host name
•
Windows
SnapCenter Server adds the host and then installs the Plug-in
for Windows if it is not already installed on the host.
If you also select the Microsoft SQL Server option on the
Plug-ins page, SnapCenter Server also installs the Plug-in for
SQL Server.
•
Linux
SnapCenter Server adds the host and then installs on the host
the Plug-in for Oracle Database and the Plug-in for UNIX if
they are not already installed.
•
vSphere
You must specify a host that is using the Windows operating
system. SnapCenter Server adds the host and then installs
SnapCenter Plug-in for VMware vSphere, if it is not already
installed on the host, to facilitate data protection operations for
virtualized applications and VMs. The SnapCenter Server
establishes communication with vCenter, using the vCenter
information provided on the Plug-ins page.
Enter the fully qualified domain name (FQDN) or the IP address
of the host.
SnapCenter depends on the proper configuration of the DNS.
Therefore, the best practice is to enter the fully qualified domain
name (FQDN).
You can enter IP addresses or FQDN of one of the following:
•
Stand-alone host
•
Windows Server Failover Clustering (WSFC)
•
Any node in the Oracle Real Application Clusters (RAC)
environment
Node VIP or scan IP is not supported.
•
SQL Availability Groups
If you are adding a host using SnapCenter and it is part of a
subdomain, you must provide the FQDN.
For SnapCenter Plug-in for SAP HANA Database, enter the
communication host name. You must configure HDBSQL client
and HDBUserStore on this host.
For SnapCenter Plug-in for VMware vSphere, the host name
default is the SnapCenter Server host. However, if you are
installing the Plug-in for VMware vSphere on a dedicated host,
then enter the FQDN or the IP address of that host.
Installing SnapCenter and the plug-in packages | 63
For this field…
Do this…
Run As name
Select the Run As name that you created or create the new Run As
credentials.
The credential must have administrative rights on the remote host.
For details, see information about creating a Run As credential.
Details about Run As credentials, including the user name,
domain, and host type, are displayed by placing your cursor over
the Run As credential name you provided.
Note: Run As credentials authentication mode is determined by
the host type that you specify in the Add Host wizard.
Port
Either retain the default port number or enter the port number.
The default port number is 8145.
Note: If you manually installed the plug-ins with a custom port,
you must specify the same port or else the operation fails.
Add all hosts in the
cluster
Select this to add all of the cluster nodes in an Oracle RAC, a
WSFC, or a SQL Availability Group.
Skip prechecks
Select this check box if you already installed the plug-ins
manually and do not want to validate whether the host meets the
requirements to install the plug-in.
5. On the Installed plug-ins page, review the plug-in packages installed on the host.
For new deployments, no plug-in packages are listed.
6. On the Plug-ins to install page, do the following:
For plug-in packages...
Do this…
SnapCenter Plug-ins
Package for Windows
On the Plug-ins page, select the plug-in package and enter the
plug-in ports and installation path.
•
Microsoft Windows
•
•
Microsoft SQL Server
•
SAP HANA
SnapCenter Plug-ins Package for Windows
For SnapCenter Plug-ins Package for Windows, the default
path is C:\Program Files\NetApp\SnapCenter.
However, if you want, you can customize the default path.
•
SnapCenter Plug-ins Package for Linux
For SnapCenter Plug-ins Package for Linux, the default path
is /opt/NetApp/snapcenter. However, if you want, you
can customize the default path.
SnapCenter Plug-ins
Package for Linux
•
Oracle
•
SAP HANA
64 | SnapCenter Software Installation and Setup Guide
For plug-in packages...
Do this…
SnapCenter Custom Pluga. In the Custom Plug-ins section, click Browse, and then select
ins
the zipped custom plug-in folder.
The zipped folder contains the custom plug-in code and the
descriptor .xml file.
b. Click Upload.
The descriptor .xml file in the zipped custom plug-in folder is
validated before uploading the package.
If you want to manage MySQL or DB2 applications, you can
use the MySQL and DB2 custom plug-ins that are provided by
NetApp. The MySQL and DB2 custom plug-ins are available
at NetApp Tool Chest.
7. Click Next.
If you have not selected the Skip prechecks check box, the host is validated to see whether it
meets the requirements to install the plug-in. The disk space, RAM, PowerShell version, .NET
version, location (for Windows plug-ins), and Java version (for Linux plug-ins) are validated
against the minimum requirements. If the minimum requirements are not met, appropriate error or
warning messages are displayed.
If the error is related to disk space or RAM, you can either update the web.config located at C:
\Program Files\NetApp\SnapCenter WebApp or PowerShell config files located at C:
\Windows\System32\WindowsPowerShell\v1.0\Modules\SnapCenter\ to modify the
default values. If the error is related to remaining parameters, you must fix the issue.
Note: In an NLB setup, if you are updating web.config, you must update it on both of the
nodes.
8. After fixing any validation errors, click Validate.
9. Review the summary, and then click Finish.
10. Monitor the installation progress.
Refresh the Hosts page after a few minutes to see the newly added host.
After you finish
If you are installing SnapCenter Plug-ins Package for Linux, installation specific log files are
available at /custom_location/snapcenter/logs.
Note: If the firewall is enabled on the Linux host, the SnapCenter Plug-ins Package for Linux is
installed successfully but on the Managed Hosts page, the host status is displayed as down and the
overall status is displayed as stopped.
Related concepts
Configuring role-based access control for SnapCenter users on page 39
SnapCenter role-based access control enables you to delegate control of SnapCenter resources
to different users or groups of users. You can create and modify roles, and add resource access
to users at any time, but when you are setting up SnapCenter for the first time, you should at
least add Active Directory users or group to roles, and then add resource access to those users
or groups.
When to use the SnapCenter GUI and the vCenter GUI on page 78
Installing SnapCenter Plug-in for VMware vSphere on page 91
Installing SnapCenter and the plug-in packages | 65
Related tasks
Setting up your Run As credentials on page 53
Related references
Licensing requirements on page 29
Registering vCenter details task displays a warning on page 159
Modifying plug-in ports
After installing a plug-in, you can modify the plug-in port if required. You can modify only the plugin port and not the SnapCenter Server port.
About this task
You can modify a plug-in port only after the plug-in is installed. If you are using earlier versions of
SnapCenter Server and SnapCenter plug-ins, you must upgrade both SnapCenter Server and
SnapCenter plug-ins to version 3.0 to be able to modify the plug-in port. You cannot modify the plugin port while upgrade operations are in progress.
While modifying a plug-in port, you must be aware of the following port rollback scenarios:
•
In a standalone setup, if SnapCenter fails to change the port of one of the components, the
operation fails and the old port is retained for all of the components.
If the port was changed for all of the components but one of the components fails to start with the
new port, then the old port is retained for all of the components. For example, if you want to
change the port for two plug-ins on the stand-alone host and SnapCenter fails to apply the new
port to one of the plug-ins, the operation fails (with an appropriate error message) and the old port
is retained for both the plug-ins.
•
In a clustered setup, if SnapCenter fails to change the port of the plug-in that is installed on one of
the nodes, the operation fails and the old port is retained for all of the nodes.
For example, if the plug-in is installed on four nodes in a clustered setup, and if the port is not
changed for one of the nodes, the old port is retained for all of the nodes.
Note: The following limitations apply to vSphere hosts only:
•
SnapCenter port modifications
You can only modify the SnapCenter port if the SnapCenter Plug-in for VMware vSphere was
installed using the SnapCenter GUI Add Host wizard.
The SnapCenter port default is 8144 and is used by the plug-in to communicate with the
vCenter Server and with the SnapCenter Server.
•
vCenter port modifications not supported
You cannot modify the plug-in port for the vSphere host.
The default VMware vSphere vCenter port is 443. This port is for communication between the
SnapCenter Plug-in for VMware vSphere web client GUI and vCenter.
Steps
1. In the left navigation pane, click Hosts.
2. Verify that Managed Hosts is selected at the top.
3. Select the host for which you want to modify the plug-in port and then click Modify.
4. In the Modify page, select Modify plug-ins port, and then enter the new port number.
5. Review the summary, and then click Finish.
66 | SnapCenter Software Installation and Setup Guide
Increasing the remote plug-in installation process timeout
You can increase the remote plug-in installation timeout from the default of 10 minutes by using the
Set-SmConfigSettings cmdlet. You might want to do this if your plug-in package installation,
upgrade, or uninstallation is failing with the message “Process timed out and was killed on server:
hostname.”
Steps
1. Launch PowerShell.
2. From the SnapCenter Server command prompt, enter the following command and enter your
credentials:
Open-SMConnection
3. Display the current remote installation process timeout by entering the following command:
Get-SmConfigSettings -Server -Key WindowsRemoteInstallProcessTimeout
4. Increase the remote installation process timeout by entering the Set-SmConfigSettings
command:
Set-SmConfigSettings -Server -configSettings
@{"WindowsRemoteInstallProcessTimeout"="900"}
The remote installation process timeout is increased to 15 minutes.
Managing the SnapCenter Plug-in Loader service for Linux
The SnapCenter Plug-in Loader (SPL) service loads the plug-in package for Linux to interact with
the SnapCenter Server. The SPL service is installed when you install the the SnapCenter Plug-ins
Package for Linux.
About this task
After installing the SnapCenter Plug-ins Package for Linux, the SnapCenter Plug-in Loader service is
started automatically. However, you can also manually start, stop, and find the status of the services.
When you restart the Linux host, the SPL service is started automatically.
The spl.properties located at /custom_location/NetApp/snapcenter/spl/etc/ contains
the following parameters and the default values are assigned to these parameters.
Parameter name
Description
LOG_LEVEL
Displays the log levels supported.
The possible values are INFO, DEBUG,
TRACE, ERROR, FATAL, and WARN.
SPL_PROTOCOL
Displays the protocol supported by SPL.
Only https protocol is supported. You can add
the value if the default value is missing.
SNAPCENTER_SERVER_PROTOCOL
Displays the protocol supported by SnapCenter
Server.
Only https protocol is supported. You can add
the value if the default value is missing.
SPL_KEYSTORE_PASS
Displays the password of the keystore file.
You can change this value only if you change
the password or create a new keystore file.
Installing SnapCenter and the plug-in packages | 67
Parameter name
Description
SPL_PORT
Displays the port number on which SnapCenter
Plug-in Loader (SPL) service is running.
You can add the value if the default value is
missing.
Note: You should not change value after
installing the plug-ins for Linux.
SNAPCENTER_SERVER_HOST
Displays IP address or host name of the
SnapCenter Server.
SPL_KEYSTORE_PATH
Displays the absolute path of the keystore file.
SNAPCENTER_SERVER_PORT
Displays the port number on which SnapCenter
Server is running.
SPL_LOGS_MAX_COUNT
Displays the number of SPL log files that are
retained in the /custom_location/
snapcenter/spl/logs folder.
The default value is set to 5000. If the count is
more than specified value, then the last
modified 5000 files will be retained. The check
for the number of files is done automatically
every 24 hours from when SPL is started.
Note: If you have manually deleted the
spl.properties file then the number of
files to be retained is 9999.
If any of these parameters are not assigned the default value and you want to assign the value or you
want to change the value, you can modify the spl.properties file. You can also verify the
spl.properties file and edit it to troubleshoot any issues related to the values assigned to the
parameters. After you modify the spl.properties file, you must restart the SPL service.
Step
1. Do one of the following:
•
Start the SPL service by entering the following command:
/custom_location/NetApp/snapcenter/spl/bin/spl start
You must always start the service as a root user.
•
Stop the SPL service by entering the following command:
/custom_location/NetApp/snapcenter/spl/bin/spl stop
Note: You can use -force option with the stop command to terminate the SPL service.
Stopping the SPL forcefully should be used with caution as forcefully stopping the service
also terminates the existing operations.
•
Find the status of the SPL service by entering the following command:
/custom_location/NetApp/snapcenter/spl/bin/spl status
68 | SnapCenter Software Installation and Setup Guide
Installing plug-ins on multiple remote hosts using cmdlets
If you want to install SnapCenter plug-in packages on multiple hosts at one time, you can do so by
using the Install-SmHostPackage PowerShell cmdlet.
Before you begin
You must have logged in to SnapCenter as a domain user with local administrator rights on each host
on which you want to install plug-ins.
Steps
1. Launch PowerShell.
2. From the SnapCenter Server command prompt, enter the following and enter your credentials:
Open-SMConnection
3. From the command prompt, enter the following:
Install-SmHostPackage -skipprecheck
Example
Alternatively, you can enter the Install-SmHostPackage command and options. For example:
Install-SmHostPackage -HostNames @("10.231.72.165","10.231.72.99")
-ApplicationCode SCO -FilesystemCode SCU -RunAsName SmoPlugin Skipprecheck
You use the -skipprecheck option when you have already installed the plug-ins manually and
do not want to validate whether the host meets the requirements to install the plug-in.
The following prompts are displayed:
hostnames
Specifies the list of hosts on which you want to install the available plug-ins. If
possible, use the fully qualified domain name (FQDN) because SnapCenter relies
on the proper DNS configuration. You must separate host names with a comma.
Using quotations is recommended.
ApplicationCode
Specifies the code for one or more plug-ins in the packages that you want to install.
The following values are valid:
•
SCSQL
•
SCO
•
SCV
•
HANA
•
Name of the custom plug-in, for example: HRPlug-in
FilesystemCode
Specifies the code for one or more plug-in packages that you want to install. The
following values are valid:
•
SCW
•
SCU
Installing SnapCenter and the plug-in packages | 69
4. Enter your Run As credentials for remote installation.
Monitoring SnapCenter plug-in package installation status
You can monitor the progress of SnapCenter plug-in package installation by using the Jobs page. You
might want to check the progress of installation to determine when it is complete or if there is an
issue.
About this task
The following icons appear on the Jobs page and indicate the state of the operation:
•
In progress
•
Completed successfully
•
Failed
•
Completed with warnings or could not start due to warnings
•
Queued
Steps
1. In the left navigation pane, click Monitor.
2. In the Monitor page, click Jobs.
3. On the Jobs page, to filter the list so that only plug-in installation operations are listed, do the
following:
a. Click Filter.
b. Optional: Specify the start and end date.
c. From the Type drop-down menu, select Plug-in installation.
d. From the Status drop-down menu, select the installation status.
e. Click Apply.
4. Select the installation job and click Details to view the job details.
5. In the Job Details page, click View logs.
Configuring the host log directory and verification server for SQL Server
After you install SnapCenter plug-in packages, you should configure the host log directory before
you perform your first backup or clone job. The host log directory is the location that you specify to
store the transaction log backup files (.trb files) that enable you to perform up-to-the-minute restore
operations.
Before you begin
•
You can use the Configure Plug-in wizard to specify the location of the host log directory and a
verification server. SnapCenter detects NetApp volumes that can host the log directory.
•
You can set up one log directory per host. You cannot set up a log directory per instance.
•
If your environment includes a Windows cluster, you must configure a host log for each host. For
an SQL cluster, you must set a host log for the Failover Cluster Instance (FCI).
70 | SnapCenter Software Installation and Setup Guide
•
If you are using a remote verification server, an iSCSI or FC connection must already exist for
that host.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Managed Hosts.
3. From the Managed Hosts page, select an SQL host, and click Configure Plug-in to open the
Configure Plug-in wizard.
4. On the Configure host log directory page, click Browse and complete the following steps:
Only NetApp LUNs (drives) are listed for selection. SnapCenter backs up and replicates the host
log directory as part of the backup operation.
a. Select the drive letter or mount point on the host where the host log will be stored.
b. Choose a subdirectory, if required.
c. Click Next.
Installing SnapCenter and the plug-in packages | 71
5. If you want to configure a verification server, on the Verification Server page, select the Setup a
SQL Server instance check box, and complete the following steps:
a. Select the SQL host and instance that you want to use for verification.
b. Select the appropriate Run As credential to perform the operation.
c. Choose the maximum job count and mount point options. The maximum job count you can
specify is 5.
d. Click Apply, and then click Next.
6. Review your settings, and click Finish.
Related tasks
Identifying available resources on page 71
Identifying available resources
Resources are the databases and similar components that are maintained by the plug-ins you have
installed. You can add those resources to resource groups to perform data protection jobs, but first
you must identify available resources. Identifying resources also verifies that the installation of plugin packages is completed successfully.
About this task
SnapCenter Custom Plug-ins does not allow you to refresh resources.
Steps
1. In the left navigation pane, click Resources, and then select the appropriate plug-in from the list.
2. From the drop-down list, select the application (Oracle Database or SQL Server or Windows File
System) that you want to manage.
3. To filter the resources, select the host from the Host drop-down menu.
72 | SnapCenter Software Installation and Setup Guide
If you have installed SnapCenter Plug-ins Package for Windows, you can also filter the resources
based on the resource types such as database, instance, and availability group.
4. Click Refresh Resources.
The new resources added to the SnapCenter inventory are displayed.
Adding resources to SnapCenter Custom Plug-ins
You must add resources that you want to backup or clone. Depending on your environment, resources
might be database instances or collections that you want to back up or clone.
Before you begin
•
You must have completed tasks such as installing the SnapCenter Server, adding hosts, creating
storage system connections, and adding “Run As” credentials.
•
You must have created a custom plug-in. For details, see the Developer Guide for Creating
Custom Plug-ins .
•
You must have uploaded the plug-ins to SnapCenter Server.
About this task
You can also add resources for MySQL and DB2 applications. These plug-ins can be downloaded
from the NetApp Tool Chest.
Steps
1. In the left navigation pane, click Resources, and then select the appropriate plug-in from the list.
2. In the Resources page, click Add Resource.
3. In the Provide Resource Details page, perform the following actions:
For this field...
Do this...
Name
Enter the name of the resource.
Host name
Select the host.
Type
Select the type. Type is user defined as per the plug-in description
file. For example, database, instance.
In case the type selected has a parent, enter the parent details. For
example: If the type is Database and the parent is Instance, enter the
Instance details.
Run As name
(Optional) Select Run as or create a new Run As account.
Mount Points
Enter the mount paths where the resource is mounted.
This is applicable only for Windows host.
Installing SnapCenter and the plug-in packages | 73
4. In the Provide Storage Footprint page, select a storage system and choose one or more volumes,
LUNs and Qtrees and click Save.
(Optional) Click
, to add more volumes, LUNs, and Qtrees from other storage systems.
Note: SnapCenter Custom Plug-ins does not support auto discovery of the resources and the
storage details for physical and virtual environment. You must provide the storage information
for physical and virtual environments while creating the resources.
5. In the Resource Settings page, provide custom key-value pairs for the resource.
Use the custom key-value pairs if you want to pass resource specific information. For example,
when you are using MySQL plug-in, you can specify a master-slave configuration as
MASTER_SLAVE = “YES” or “NO” (name is MASTER_SLAVE and value is “YES” or “NO”).
74 | SnapCenter Software Installation and Setup Guide
6. Review the summary and click Finish.
Result
The resources are displayed along with information such as type, host or cluster name, associated
resource groups and policies, and overall status.
After you finish
If you want to provide access to the assets to other users, SnapCenter administrator must assign
assets to those users. This enables users to perform the actions for which they have permissions on
the assets that are assigned to them.
Related tasks
Installing the SnapCenter Server on page 35
You can use the InstallShield wizard to install the SnapCenter Server.
Setting up your Run As credentials on page 53
Assigning users access to assets on page 45
Adding databases to SnapCenter Plug-in for SAP HANA Database
You must add databases that you want to back up or clone.
Before you begin
You must have completed tasks such as installing the SnapCenter Server, adding hosts, creating
storage system connections, and adding “Run As” credentials.
Steps
1. In the left navigation pane, select the appropriate plug-in from the drop-down list, and then click
Resources.
2. In the Resources page, click Add SAP HANA Database.
3. In the Provide Resource Details page, perform the following actions:
For this field...
Do this...
Resource Type
Enter the resource type.
Resource types are Single Container and Multitenant Database
Containers (MDC) – Single Tenant.
SAP HANA System
Name
Enter the descriptive SAP HANA system name.
Installing SnapCenter and the plug-in packages | 75
For this field...
Do this...
SID
Enter the system ID (SID).
The installed SAP HANA system is identified by a single SID.
Tenant Database
Enter the name of the tenant database for SAP HANA databases.
This option is available only if you selected the Multitenant Database
Containers (MDC) – Single Tenant resource type.
HDBSQL Client Host
Select the communication host.
HDB Secure User
Store Keys
Enter the key to connect to the SAP HANA system.
The key contains the login information to connect to the database.
HDBSQL OS User
Enter the user name for whom the HDB Secure User Store Key is
configured.
For Windows, it is mandatory for the HDBSQL OS User to be the
SYSTEM user. Therefore, you must configure the HDB Secure User
Store Key for the SYSTEM user.
4. In the Provide Storage Footprint page, select a storage system and choose one or more volumes,
LUNs, and qtrees, and then click Save.
Optional: You can click
systems.
to add more volumes, LUNs, and qtrees from other storage
Note: SnapCenter Plug-in for SAP HANA Database does not support automatic discovery of
the resources and storage details for physical and virtual environments. You must provide the
storage information for physical and virtual environments while adding the databases.
5. In the Resource Settings page, perform the following actions:
For this field...
Do this...
Prefix
Enter the prefix of the File-Based backup name.
If the prefix is not provided, the default value is used.
76 | SnapCenter Software Installation and Setup Guide
For this field...
Do this...
Location
Enter the path on the SAP HANA node to save the File-Based
backup.
If the path is not provided, SAP HANA uses the default path
configured on the system, for example, <HANA shared path>/
<SID>/HDB<INSTANCE_ID>/backup/data.
6. Review the summary, and then click Finish.
The databases are displayed along with information such as the SID, Tenant Database for MDC,
communication host, associated resource groups and policies, and overall status.
After you finish
If you want to provide users access to resources, you must assign the resources to the users. This
enables users to perform the actions for which they have permissions on the assets that are assigned
to them.
Related tasks
Assigning users access to assets on page 45
77
Installing and setting up SnapCenter Plug-in for
VMware vSphere
If your database or Windows file system is stored on virtual machines (VMs), or if you want to
protect VMs and datastores, you must install and set up SnapCenter Plug-in for VMware vSphere.
Overview of SnapCenter Plug-in for VMware vSphere
The Plug-in for VMware vSphere is a host-side component of the NetApp storage solution offering
support for virtualized data, VMs and datastores. This plug-in is a component in the SnapCenter
Plug-ins Package for Windows.
The Plug-in for VMware vSphere provides native backup, recovery, and cloning of virtualized
applications (virtualized SQL and Oracle databases and Windows file systems). As a vSphere web
client on VMware vCenter, Plug-in for VMware vSphere provides backup and restore of virtual
machines in VMware vSphere environments using NetApp storage systems.
•
Support for virtualized databases and Windows file systems
The Plug-in for VMware vSphere provides support when you use the SnapCenter GUI to perform
backup, recovery, and cloning operations for virtualized applications. SnapCenter reduces the
complexity of protecting virtualized applications by natively leveraging the Plug-in for VMware
vSphere for all SQL, Oracle, and Windows file system data protection operations on virtual
machine disks (VMDKs), raw device mappings (RDMs), and NFS datastores.
After the Plug-in for VMware vSphere is installed, you do not need to take any further action; the
plug-in handles all interaction with vCenter.
The Plug-in for VMware vSphere supports all virtualized applications that are supported by
SnapCenter.
Note: You do not need to install the Plug-in for VMware vSphere in the following scenarios:
•
◦
Your SQL Server environment uses an in-guest iSCSI initiator
◦
Your Oracle environment uses NFS or an in-guest iSCSI initiator
Support for VMs and datastores
The Plug-in for VMware vSphere also provides a vSphere web client in vCenter. The Plug-in for
VMware vSphere GUI in vCenter allows you to perform backup and restore operations of VMs
that are registered with SnapCenter, backups of datastores, guest file restore operations, and
single file restore operations. You can also migrate to the Plug-in for VMware vSphere any VM
backups that were performed using VSC, if the backups were performed when VSC was
registered with SnapCenter.
The restore workflow utilizes the VMware Storage Vmotion feature. Storage Vmotion is a part of
the vSphere Standard License but is not available with the vSphere Essentials or Essentials Plus
licenses.
Although the Plug-in for VMware vSphere must be installed on a Windows host, it supports both
Windows-based vCenters and Linux-based vCenter appliances. SnapCenter natively uses this plug-in
to communicate with your vCenter for data protection operations of Windows and Linux virtualized
applications without user intervention, which reduces the complexity of protecting virtualized
applications.
Related concepts
Installation workflow for VMware vSphere users on page 79
Preparing for the installation on page 79
78 | SnapCenter Software Installation and Setup Guide
When to use the SnapCenter GUI and the vCenter GUI on page 78
When to use the SnapCenter GUI and the vCenter GUI
You use the SnapCenter GUI to perform data protection operations for all application-based plug-ins,
including data protection on virtualized databases and Windows file systems. You use the Plug-in for
VMware vSphere GUI in vCenter to perform data protection operations on VMs and datastores.
Use this GUI...
To perform these
operations...
Plug-in for VMware vSphere
GUI in vCenter
SnapCenter GUI
VM and datastore backup
VMDK attach and detach
VM restore
Single file restore
Backup and restore of
virtualized databases and
applications, including
protecting Microsoft SQL
databases and Oracle
databases.
And to access these
backups...
Backups performed by the
Plug-in for VMware vSphere
GUI in vCenter.
Backups performed by the
SnapCenter GUI.
Examples of when to use each GUI:
•
Example for protecting a VM
For example, to back up a VM in which Oracle is running (to perform a host-level backup, not an
application-consistent backup), you use the Plug-in for VMware vSphere GUI in vCenter to start
the backup. SnapCenter uses the Plug-in for VMware vSphere to perform the operation. You also
use the Plug-in for VMware vSphere GUI in vCenter to access or restore the backup.
•
Example for protecting a database
For example, to back up an Oracle database that is running on VMs (to perform an applicationconsistent backup), you use the SnapCenter GUI to start a backup of the database. SnapCenter
uses the SnapCenter Plug-in for Oracle Database and the SnapCenter Plug-in for UNIX to
perform the operation, and uses the Plug-in for VMware vSphere to communicate with vCenter.
You also use the SnapCenter GUI to access or restore the backup.
Both vCenter and SnapCenter job monitors display all SnapCenter jobs, regardless of which GUI was
used to start the job.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 79
Installation workflow for VMware vSphere users
If you are new to SnapCenter you need to install and configure the server and plug-ins and then
create backups.
Preparing for the installation
You should be aware of several requirements and prerequisites before installing SnapCenter Plug-in
for VMware vSphere.
For infomation about...
See the...
Supported storage types
Support information in this section.
Host requirements
SnapCenter requirements information.
Supported browsers
SnapCenter browser information.
Connection and port requirements
SnapCenter port and connection information.
SnapCenter licensing
SnapCenter licensing information.
For the latest information on requirements, see the NetApp Interoperability Matrix.
80 | SnapCenter Software Installation and Setup Guide
NetApp Interoperability Matrix Tool
Related references
Supported storage systems on page 80
Host requirements on page 23
Supported browsers on page 27
Connection and port requirements on page 27
Licensing requirements on page 29
Supported storage systems
SnapCenter Plug-in for VMware vSphere supports VMware virtual machines and datastores. You
must verify whether support is available for your storage type before installing the package for your
host.
Machine type
Storage type
Provision using
VMware VM
RDM LUNs connected by an FC or
iSCSI HBA
SnapCenter PowerShell cmdlets
iSCSI LUNs connected directly to the
guest system by the iSCSI initiator
SnapCenter GUI or PowerShell
cmdlets
Virtual Machine File Sytems (VMFS)
on VMFS or NFS datastores
VMware vSphere or VSC
provisioning
For the latest information about supported versions, see the NetApp Interoperability Matrix.
NetApp Interoperability Matrix Tool
Related references
Supported storage systems and applications on page 26
Installation requirements for the Plug-in for VMware vSphere
You should be aware of certain installation requirements before you install the SnapCenter Plug-in
for VMware vSphere. The requirements for the Plug-in for VMware vSphere are the same as for the
SnapCenter Plug-ins Package for Windows.
Host and privilege requirements
•
You must have SnapCenter admin privileges to install and manage the SnapCenter GUI.
•
You must install the Plug-in for VMware vSphere on a Windows host (virtual host or physical
host).
The Plug-in for VMware vSphere must be installed on a Windows host regardless of whether you
use the plug-in to protect data on Windows systems or Linux systems. You can install the Plug-in
for VMware vSphere or either the SnapCenter Server host or on a dedicated Windows host.
•
Do not install the Plug-in for VMware vSphere on the vCenter Server appliance.
You must not install the Plug-in for VMware vSphere on the vCenter Server appliance, which is a
Linux host. You can only install the Plug-in for VMware vSphere on Windows hosts.
•
You must not install other plug-ins on the host on which the Plug-in for VMware vSphere is
installed.
•
The Plug-in for VMware vSphere does not support IPv6.
•
You do not have to install the Plug-in for VMware vSphere in the following scenarios:
Installing and setting up SnapCenter Plug-in for VMware vSphere | 81
◦
Your SQL Server environment uses an in-guest iSCSI initiator.
◦
Your Oracle environment uses NFS or an in-guest iSCSI initiator.
•
You must have installed PowerShell 4.0 or later.
If the host from which you are installing is running Windows 2008 R2, then you must
independently install Windows Management Framework (WMF) for PowerShell 4.0. For
machines running Windows 2012 and later, Power 4.0 is installed by default.
•
You must have installed Microsoft Net 4.5.2 or later.
•
You must have turned on Windows message queuing.
Host space and sizing requirements
The following space and sizing requirements apply to all configurations of the Plug-in for VMware
vSphere: installed on the SnapCenter Server host, on a vCenter Windows host, or on a dedicated
Windows host.
Item
Requirements
Operating Systems
Microsoft Windows
Note: You must enable the Cluster Shared Volumes (CSV) feature in
Windows Server 2008 R2 SP1 if you want to create CSV type disks.
For the latest information about supported versions, see the NetApp
Interoperability Matrix.
NetApp Interoperability Matrix Tool
Minimum Install
space
2 GB
Required Software
Packages
•
Microsoft .NET Framework 4.5.2 or later
•
Windows Management Framework (WMF) 4.0
•
PowerShell 4.0
For the latest information about supported versions, see the NetApp
Interoperability Matrix.
NetApp Interoperability Matrix Tool
RAM and CPU requirements depend upon where the Plug-in for VMware vSphere is installed.
If the plug-in is installed
on...
Requirements
SnapCenter Server host
Requirements for the SnapCenter Server are:
•
RAM: Minimum 8 GB; recommended 32 GB
•
CPUs: 4
No additional resources are needed for the Plug-in for VMware
vSphere.
Dedicated host
Requirements are the same as for all other plug-ins.
•
RAM: Minimum 4 GB; recommended 8 GB
•
CPUs: Minimum 1; recommended 2
82 | SnapCenter Software Installation and Setup Guide
Related references
Prerequisites to adding hosts and installing plug-in packages on page 55
Using SnapCenter Plug-in for VMware vSphere with vCenter Servers in
Linked Mode
If you are using SnapCenter Plug-in for VMware vSphere in an environment where multiple vCenter
Servers are joined using vCenter Linked Mode or Enhanced Linked Mode, you need to register one
instance of the Plug-in for VMware vSphere with each vCenter Server so that there is a 1:1 pairing
between the Plug-in for VMware vSphere and the vCenter Server.
When you do this, you can perform backup and restore operations on all of the servers running
vCenter 6.0 update 3 or later from a single Plug-in for VMware vSphere web client in Linked Mode.
Attention: When you register the Plug-in for VMware vSphere with each vCenter Server in
Linked Mode, you must use the same ID type for all the linked hosts. In other words, you might
use the Plug-in for VMware vSphere host ID in all the linked vCenter Servers or you might use the
hostname. When the Plug-in for VMware vSphere is not registered the same in all the linked
vCenter Servers, the Plug-in for VMware vSphere displays duplicate entries for storage systems.
Note: If you have additional vCenter Servers that are not in Linked Mode, you need to register an
instance of the Plug-in for VMware vSphere with each vCenter Server.
In the diagram, you can log on to either vCenter A or vCenter B and because they are in Linked
Mode, you can perform backup and restore operations on VMs in both vCenters from the single
Plug-in for VMware vSphere web client. However, neither vCenter A or vCenter B can perform
backup and restore operations on vCenter C because it is not in Linked Mode.
Using the Plug-in for VMware vSphere web client to perform backup and restore tasks across Link
Mode vCenter Servers in Linked Mode requires the following:
•
You must have installed an instance of the Plug-in for VMware vSphere for each vCenter Server.
•
After installing the Plug-in for VMware vSphere, you must create users and assign them to
appropriate RBAC roles. The RBAC roles for the plug-in are different from the vCenter RBAC
roles and are reconciled in a Linked Mode configuration.
When you are performing an operation that requires you to specify a vCenter Server, select the
vCenter Server from the drop-down list. The default vCenter Server is always the first server in the
drop-down list.
For the latest information about supported versions, see the NetApp Interoperability Matrix.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 83
NetApp Interoperability Matrix Tool
Related concepts
Predefined roles packaged with SnapCenter Plug-in for VMware vSphere on page 89
Configuring RBAC for SnapCenter Plug-in for VMware vSphere users
Role-based access control for SnapCenter, the Plug-in for VMware vSphere, and vCenter combine to
enable you to delegate control of SnapCenter and vCenter resources to different users or groups of
users.
The Plug-in for VMware vSphere ships with predefined vCenter roles. You must add these roles to
vCenter Active Directory users to perform SnapCenter operations on the vCenter GUI. You cannot
change the permissions of the SnapCenterAdmin role.
You can create and modify roles, and add resource access to users at any time. However, when you
are setting up SnapCenter and the Plug-in for VMware vSphere for the first time, you should at least
add Active Directory users or groups to roles, and then add resource access to those users or groups.
Note that user or group accounts are not created using SnapCenter, but are created in the Active
Directory in the operating system or database.
Related concepts
Configuring role-based access control for SnapCenter users on page 39
SnapCenter role-based access control enables you to delegate control of SnapCenter resources
to different users or groups of users. You can create and modify roles, and add resource access
to users at any time, but when you are setting up SnapCenter for the first time, you should at
least add Active Directory users or group to roles, and then add resource access to those users
or groups.
Types of RBAC for SnapCenter Plug-in for VMware vSphere users
Role-based access control (RBAC) enables SnapCenter and vCenter administrators to create roles
and set access permissions. This centrally managed access empowers application administrators to
work securely within delegated environments. Configuring RBAC is a simple process, but it is
important to understand the RBAC components and configure them correctly to ensure that all
selected users are able to access SnapCenter, the Plug-in for VMware vSphere, and vCenter.
The Plug-in for VMware vSphere uses the following types of role-based access control:
•
vCenter Server RBAC
•
SnapCenter RBAC
•
Application-level RBAC
•
ONTAP permissions
See also the types of role-based access control for information on SnapCenter and application-level
RBAC, and ONTAP permissions.
Related concepts
Types of role-based access control in SnapCenter on page 39
84 | SnapCenter Software Installation and Setup Guide
Pre-defined roles and permissions for the Plug-in for VMware vSphere
SnapCenter Plug-in for VMware vSphere ships with pre-defined SCV roles, each with a set of
permissions already enabled. Before adding users to these pre-defined roles, it is helpful to
understand which permissions are enabled and which permissions are not enabled.
SnapCenter Plug-in for VMware vSphere includes the following pre-defined roles:
•
•
•
•
SCV Administrator
SCV Backup
SCV Restore
SCV View
vCenter privileges
vCenter Privileges
Predefined Roles for the
Plug-in for VMware vSphere
SCV
Administrator
SCV
Backup
SCV
Restore
Datastore:
Allocate space
x
x
Browse datastore
x
x
Low level file operations
x
Move datastore
x
x
Remove datastore
x
x
Rename datastore
x
x
Advanced settings
x
x
Change settings
x
x
Storage partition configuration
x
x
System resources
x
x
Create virtual machine
x
x
Delete virtual machine
x
x
Reconfigure virtual machine
x
x
x
x
Apply recommendation
x
x
Assign virtual machine to resource pool
x
x
Migrate powered off virtual machine
x
x
Query vMotion
x
x
Host:Configuration:
Host:Local operations:
Network:
Assign network
Resource:
SCV
View
Installing and setting up SnapCenter Plug-in for VMware vSphere | 85
vCenter Privileges
Predefined Roles for the
Plug-in for VMware vSphere
SCV
Administrator
SCV
Backup
SCV
Restore
Create task
x
x
x
Update task
x
x
x
SCV
View
Tasks:
Virtual machine:Configuration:
Add existing disk
x
x
Add new disk
x
x
Advanced
x
x
Change resource
x
x
Reload from path
x
x
Remove disk
x
x
Power off
x
x
Power on
x
x
Create from existing
x
x
Create new
x
x
Move
x
x
Register
x
x
Remove
x
x
Unregister
x
x
Virtual machine:Interaction:
Virtual machine:Inventory:
Virtual machine:Snapshot management:
Create snapshot
x
x
x
Remove snapshot
x
x
x
Revert to snapshot
x
x
x
SnapCenter Plug-in for VMware vSphere privileges
SnapCenter Plug-in for VMware vSphere
Privileges
Predefined Roles for the
Plug-in for VMware vSphere
SCV
Administrator
SCV
Backup
x
x
privilege.netappSCV.label:
privilege.netappSCV.Backup.label
SCV
Restore
SCV
View
86 | SnapCenter Software Installation and Setup Guide
SnapCenter Plug-in for VMware vSphere
Privileges
Predefined Roles for the
Plug-in for VMware vSphere
SCV
Administrator
SCV
Backup
privilege.netappSCV.Backup.BackupNow.label
x
x
privilege.netappSCV.Backup.BackupScheduled.labe
l
x
x
privilege.netappSCV.Backup.DeleteBackupJob.label
x
x
privilege.netappSCV.Configure.label
x
privilege.netappSCV.Configure.ConfigureSnapCente x
rServer.label
SCV
Restore
x
x
x
x
privilege.netappSCV.Configure.ConfigureStorageSy
stems.label
x
privilege.netappSCV.Configure.ConfigureStorageSy
stems.AddUpdate.label
x
privilege.netappSCV.Configure.ConfigureStorageSy
stems.Delete.label
x
privilege.netappSCV.Recovery.label
x
x
privilege.netappSCV.Recovery.MountUnMount.labe
l
x
x
privilege.netappSCV.Recovery.RecoverVM.label
x
x
privilege.netappSCV.View.label
x
x
x
SCV
View
x
Related tasks
Adding a user to a role on page 45
Assigning users access to assets on page 45
Related references
Role-based access control permissions and roles on page 40
Pre-defined SnapCenter roles and permissions on page 42
Setting up SVMs and Run As credentials
Before you can perform data protection operations in virtualized environments with SnapCenter, you
must set up the Storage Virtual Machine (SVM) connections and add Run As credentials that
SnapCenter Plug-in for VMware vSphere will use.
•
SVM connections
SVM connections give SnapCenter and the Plug-in for VMware vSphere access to ONTAP
storage. Setting up these connections also involves configuring AutoSupport and Event
Management System (EMS) features.
SVMs that are added using the SnapCenter GUI are also listed in the Plug-in for VMware
vSphere GUI in vCenter. SVMs that are added using the Plug-in for VMware vSphere GUI in
vCenter are also listed in the SnapCenter GUI.
•
Run As credentials
Installing and setting up SnapCenter Plug-in for VMware vSphere | 87
The RunAs credential user should be a domain administrator or a regular domain user with local
administrator privileges on the system on which the Plug-in for VMware vSphere is to be
installed.
•
SnapMirror or SnapVault destinations
If you are planning to replicate Snapshot copies to a SnapMirror or SnapVault destination, make
sure to set up storage system connections for the destination SVM as well as the source SVM.
Related concepts
Authentication methods for your Run As credentials on page 52
Related tasks
Setting up storage system connections on page 49
To perform data protection and provisioning operations with SnapCenter, first you must set up
the storage system connections that give SnapCenter access to ONTAP storage. Setting up these
connections also involves configuring AutoSupport and Event Management System (EMS)
features.
Setting up your Run As credentials on page 53
Authentication and user management with vCenter RBAC
and ONTAP RBAC
If you are using SnapCenter Plug-in for VMware vSphere, the vCenter Server provides an additional
level of RBAC. SnapCenter Plug-in for VMware vSphere supports both vCenter Server RBAC and
Data ONTAP RBAC.
•
vCenter Server RBAC
This security mechanism restricts the ability of vSphere users to perform SnapCenter Plug-in for
VMware vSphere tasks on vSphere objects, such as virtual machines (VMs) and datastores. The
Plug-in for VMware vSphere installation creates four roles for SnapCenter operations on vCenter:
SCV Administrator, SCV Backup, SCV Restore, and SCV View.
The vSphere administrator sets up vCenter Server RBAC by doing the following:
◦
Setting the vCenter Server permissions on the root object (also known as the root folder). You
can then refine the security by restricting child entities that do not need those permissions.
◦
Assigning the SCV roles to Active Directory users.
Note: At a minimum, all users must be able to view vCenter objects. Without this privilege,
users cannot access the Plug-in for VMware vSphere GUI.
•
ONTAP RBAC
This security mechanism restricts the ability of SnapCenter to perform specific storage
operations, such as backing up storage for datastores, on a specific storage system.
ONTAP and SnapCenter RBAC is set up in the following workflow:
1. The storage administrator creates a role on the SVM with the necessary privileges.
2. Then the storage administrator assigns the role to a storage user.
3. The SnapCenter administrator adds the SVM to the SnapCenter Server, using that storage user
name.
4. Then the SnapCenter administrator assigns roles to SnapCenter users.
The following diagram provides an overview of the Plug-in for VMware vSphere validation
workflow for RBAC privileges (both vCenter and ONTAP):
88 | SnapCenter Software Installation and Setup Guide
Components of vCenter Server permissions
The vCenter Server recognizes permissions, not privileges. Each vCenter Server permission consists
of three components: a role that defines which privileges can be performed; a user or group that
defines who can perform a task, and a vSphere object that is the target for the task.
Whether a SnapCenter task succeeds can depend on where you assigned a permission or what actions
a user took after a permission was modified. The permission on a child entity always overrides the
permission inherited from the parent entity.
vSphere objects
Permissions are associated with vSphere objects, such as the vCenter Server, ESXi hosts, virtual
machines, and datastores. You can assign permissions to any vSphere object. Based on the
permission that is assigned to a vSphere object, the vCenter Server administrator determines who can
perform which tasks on that object.
To access the SnapCenter Plug-in for VMware vSphere web client GUI on vCenter, you must have
the product-level, SnapCenter-specific View privilege assigned at the correct vSphere object level. If
you log in without this privilege, the Plug-in for VMware vSphere displays an error message and
prevents you from accessing the Plug-in for VMware vSphere GUI.
The assignment level determines which portions of the UI you can see. Assigning the View privilege
at the root object (folder) enables you to enter Plug-in for VMware vSphere by clicking the NetApp
icon. You can assign the View privilege to another vSphere object level; however, doing that limits
the Plug-in for VMware vSphere menus that you can see and use.
The root object is the recommended place to assign any permission containing the View privilege.
Users and groups
You can assign roles to Active Directory (or the local vCenter Server machine) users and groups of
users. You can assign only one role to a user or group.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 89
Predefined roles packaged with SnapCenter Plug-in for VMware vSphere
To simplify working with vCenter Server RBAC, SnapCenter Plug-in for VMware vSphere provides
a set of predefined SnapCenter roles that enable users to perform SnapCenter tasks. There is also a
read-only role that allows users to view SnapCenter information, but not perform any tasks.
The predefined SnapCenter Plug-in for VMware vSphere roles have both the required SnapCenterspecific privileges and the native vCenter Server privileges to ensure that tasks complete correctly. In
addition, the roles are set up to have the necessary privileges across all supported versions of vCenter
Server.
As an administrator, you can assign these roles to the appropriate users.
Note: SnapCenter Plug-in for VMware vSphere returns these roles to their default values (initial
set of privileges) each time you restart the vCenter web client service or modify your installation.
If you upgrade SnapCenter Plug-in for VMware vSphere, the predefined roles are automatically
upgraded to work with that version of the plug-in.
You can see the SnapCenter Plug-in for VMware vSphere predefined roles in the vCenter GUI by
clicking
> Administration > Roles.
Role
Description
SCV Administrator Provides all native vCenter Server and SnapCenter-specific privileges
necessary to perform all SnapCenter Plug-in for VMware vSphere tasks.
SCV View
Provides read-only access to all of SnapCenter Plug-in for VMware vSphere.
SCV Backup
Provides all native vCenter Server and SnapCenter-specific privileges
necessary to back up vSphere objects (virtual machines and datastores).
The user also has access to the configure privilege.
The user cannot restore from backups.
SCV Restore
Provides all native vCenter Server and SnapCenter-specific privileges
necessary to restore vSphere objects that have been backed up using
SnapCenter Plug-in for VMware vSphere.
The user also has access to the configure privilege.
The user cannot back up vSphere objects.
Product-level privilege required by SnapCenter Plug-in for VMware vSphere
To access the Plug-in for VMware vSphere GUI on vCenter, you must have the product-level,
SnapCenter-specific View privilege assigned at the correct vSphere object level. If you log in without
this privilege, the Plug-in for VMware vSphere displays an error message when you click the NetApp
icon and prevents you from accessing the Plug-in for VMware vSphere GUI.
The following information describes the Plug-in for VMware vSphere product-level View privilege:
90 | SnapCenter Software Installation and Setup Guide
Privilege
Description
Assignment level
View
You can access the Plug-in for
VMware vSphere GUI.
This privilege does not enable you to
perform tasks within SnapCenter. To
perform any Plug-in for VMware
vSphere tasks, you must have the
correct SCV-specific and native
vCenter Server privileges for those
tasks.
The assignment level
determines which portions of
the UI you can see.
Assigning the View privilege
at the root object (folder)
enables you to enter the Plugin for VMware vSphere by
clicking the NetApp icon.
You can assign the View
privilege to another vSphere
object level; however, doing
that limits the the Plug-in for
VMware vSphere menus that
you can see and use.
The root object is the
recommended place to assign
any permission containing the
View privilege.
ONTAP RBAC features in SnapCenter Plug-in for VMware vSphere
Data ONTAP role-based access control (RBAC) enables you to control access to specific storage
systems and the actions a user can perform on those storage systems. SnapCenter Plug-in for
VMware vSphere works with vCenter Server RBAC, SnapCenter RBAC, and ONTAP RBAC to
determine which SnapCenter tasks a specific user can perform on objects on a specific storage
system.
SnapCenter uses the credentials that you set up (user name and password) to authenticate each
storage system and determine which operations can be performed on that storage system. The Plug-in
for VMware vSphere uses one set of credentials for each storage system. These credentials determine
all tasks that can be performed on that storage system; in other words, the credentials are for
SnapCenter, not an individual SnapCenter user.
ONTAP RBAC applies only to accessing storage systems and performing SnapCenter tasks related to
storage, such as backing up VMs. If you do not have the appropriate ONTAP RBAC privileges for a
specific storage system, you cannot perform any tasks on a vSphere object hosted on that storage
system.
Each storage system has one set of ONTAP privileges associated with it.
Using both ONTAP RBAC and vCenter Server RBAC provides the following benefits:
•
Security
The administrator can control which users can perform which tasks on both a fine-grained
vCenter Server object level and a storage system level.
•
Audit information
In many cases, SnapCenter provides an audit trail on the storage system that lets you track events
back to the vCenter user who performed the storage modifications.
•
Usability
You can maintain controller credentials in one place.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 91
How to configure ONTAP RBAC for SnapCenter Plug-in for VMware vSphere
You must configure ONTAP RBAC on the storage system if you want to use it with SnapCenter
Plug-in for VMware vSphere.
From within ONTAP, you must perform the following tasks:
•
Create a single role.
For information on creating RBAC roles, see the ONTAP Administration Guide.
ONTAP 9 Administrator Authentication and RBAC Power Guide
•
Create a user name and password (the storage system credentials) in ONTAP for the role.
This storage system credential is needed to allow you to configure the storage systems for the
Plug-in for VMware vSphere. You do this by entering the credentials in the Plug-in for VMware
vSphere. Each time you log in to a storage system using these credentials, you are presented with
the set of SnapCenter functions that you set up in ONTAP when you created the credentials.
You can use the administrator or root login to access all the SnapCenter tasks; however, it is a good
practice to use the RBAC feature provided by ONTAP to create one or more custom accounts with
limited access privileges.
Installing SnapCenter Plug-in for VMware vSphere
To protect data on VMware vSphere virtual machines, you must register VMware vSphere hosts with
SnapCenter and install the Plug-in for VMware vSphere on a managed host.
Related concepts
Using SnapCenter Plug-in for VMware vSphere with vCenter Servers in Linked Mode on page 82
Types of role-based access control in SnapCenter on page 39
Authentication and user management with vCenter RBAC and ONTAP RBAC on page 87
Updating SnapCenter and vCenter settings on page 99
Related tasks
Installing the Plug-in for VMware vSphere from the SnapCenter GUI on page 93
Installing the Plug-in for VMware vCenter from the SnapCenter Server host by using PowerShell
cmdlets on page 95
Installing the Plug-in for VMware vSphere from a local host by using the installer GUI for the
SnapCenter Plug-ins Package for Windows on page 96
Installing the Plug-in for VMware vSphere from a local host silently from the command line on
page 97
Related references
Installation requirements for the Plug-in for VMware vSphere on page 80
Supported storage systems on page 80
Pre-defined roles and permissions for the Plug-in for VMware vSphere on page 84
Installation requirements for the Plug-in for VMware vSphere on page 80
Types of installation configurations on page 92
Methods for installing the SnapCenter Plug-in for VMware vSphere on page 92
92 | SnapCenter Software Installation and Setup Guide
Types of installation configurations
You can choose where to install the SnapCenter Plug-in for VMware vSphere, unlike other plug-ins
that support specific applications and must be installed on the same host as the application.
You can install the Plug-in for VMware vSphere on the following hosts:
•
SnapCenter Server host
Note: When the Plug-in for VMware vSphere is installed on the SnapCenter Server host, the
SnapCenter Plug-in for Microsoft Windows is also installed automatically. However,
SnapCenter Plug-in for Microsoft Windows is used only to manage the SnapCenter repository;
you cannot use the plug-in's provisioning features on that host.
•
Dedicated Windows host
Do not install other plug-ins on the same host as the Plug-in for VMware vSphere.
Methods for installing the SnapCenter Plug-in for VMware vSphere
You can install the Plug-in for VMware vSphere in four ways.
•
From the SnapCenter GUI by using the Add Host wizard.
This is the preferred method and is the easiest method for installing the Plug-in for VMware
vSphere on the local SnapCenter Server host or on a remote host.
The Add Host wizard installs the plug-in on the specified host and registers the Plug-in for
VMware vSphere with the specified vCenter. You can view the newly added vSphere host in the
SnapCenter GUI and in the SnapCenter Plug-in for VMware vSphere GUI in vCenter.
•
From the SnapCenter Server host by using PowerShell cmdlets.
If you do not want to use the SnapCenter GUI, this is the preferred method for installing the Plugin for VMware vSphere on the SnapCenter Server host or on a remote host.
•
From a local host by using the installer GUI for the SnapCenter Plug-ins Package for Windows.
If you want to install the Plug-in for VMware vSphere independently on a dedicated local host,
then this is the preferred method.
This method installs the plug-in on the local host and opens a link for registering the plug-in with
vCenter.
Note: This method is supported only for the Plug-in for VMware vSphere and only for
installing on a dedicated host, not for installing on the SnapCenter Server host. You cannot
install other plug-ins by using this method.
•
From a local host silently from the command line.
This is the method used to perform independent installations of other plug-ins.
Although you can install the Plug-in for VMware vSphere by using this method, it is more
complex because you must manually register the plug-in with vCenter after the installation is
completed.
Related tasks
Installing the Plug-in for VMware vSphere from the SnapCenter GUI on page 93
Installing the Plug-in for VMware vCenter from the SnapCenter Server host by using PowerShell
cmdlets on page 95
Installing the Plug-in for VMware vSphere from a local host by using the installer GUI for the
SnapCenter Plug-ins Package for Windows on page 96
Installing the Plug-in for VMware vSphere from a local host silently from the command line on
page 97
Installing and setting up SnapCenter Plug-in for VMware vSphere | 93
Installing the Plug-in for VMware vSphere from the SnapCenter GUI
To install the SnapCenter Plug-in for VMware vSphere from the SnapCenter GUI, you use the Add
Host wizard to add a vSphere host. The Plug-in for VMware vSphere is automatically installed on the
specified remote host (which must be a Windows host) and is registered in the specified vCenter
Server.
Before you begin
You must be a user that is assigned to a role that has the plug-in install and uninstall permissions,
such as the SnapCenter Admin role and the vsadmin role for vCenter.
You must have reviewed the installation requirements and types of supported configurations before
installing the Plug-in for VMware vSphere.
Steps
1. In the left navigation pane, click Hosts.
2. Verify that Managed Hosts is selected at the top.
3. Click Add.
4. On the Hosts page, specify the host on which you want to install the Plug-in for VMware
vSphere:
For this field…
Do this…
Host OS
Select vsphere as the type of host.
You must specify a virtual machine host that is using the Windows
operating system.
SnapCenter Server adds the host, and then installs the Plug-in for
VMware vSphere, if the plug-in is not already installed on the host
and add the Plug-in for VMware vSphere web client to vCenter.
The SnapCenter Server establishes communication with the
vCenter Server, using the vCenter information that is provided on
the Plug-ins to install page.
Host name
Type the fully qualified domain name (FQDN) or the IP address of
the host.
For the Plug-in for VMware vSphere, the host name default is the
SnapCenter Server host. However, if you are installing the Plug-in
for VMware vSphere on a dedicated host, then enter the FQDN or
the IP address of that host.
SnapCenter depends on the proper configuration of the DNS.
Therefore, the best practice is to specify the FQDN.
You can specify one of the following:
•
IP address or FQDN of the stand-alone host
•
IP address or FQDN of the Windows Server Failover
Clustering (WSFC)
If the host is part of a sub-domain, you must provide the FQDN.
94 | SnapCenter Software Installation and Setup Guide
For this field…
Do this…
Run As name
Select the Run As name that you created, or create new Run As
credentials.
The Run As credentials must have administrative rights on the
remote host. For details, see information about creating Run As
credentials.
You can view details about the Run As credentials, including the
user name, domain, and host type, by positioning your cursor over
the Run As credential name that you specified.
Note: Run As credentials authentication mode is determined by
the host type that you specify in the Add Host wizard.
Port
Either retain the default port number or type a different port
number.
The default port number is 8144.
Note: If you previously installed the Plug-in for VMware
vSphere manually with a custom port, you must specify the
same port or else the operation fails.
Skip prechecks
Select this check box if you have already installed the Plug-in for
VMware vSphere manually and do not want to validate whether
the host meets the requirements for installing the plug-in.
5. On the Plug-ins to install page, specify the vCenter information.
a. Specify the host on which vCenter is installed.
For the Plug-in for VMware vSphere, the default path is C:\Program Files\NetApp
\SnapCenter. You can customize the default path if required.
b. Specify the vCenter information.
You should specify the requested vCenter information to enable the Plug-in for VMware
vSphere to complete VMDK discovery.
6. Click Next.
If the Skip prechecks option was not selected, the host is validated to verify whether the host
meets the requirements for installing the plug-in. The disk space, RAM, PowerShell
version, .NET version, and location are validated against the minimum requirements. If the
minimum requirements are not met, appropriate error messages or warning messages are
displayed.
After fixing the issue, you should click Validate to re-validate the requirements.
If the error is related to disk space or RAM, you can either update the web.config file located at
C:\Program Files\NetApp\SnapCenter WebApp or the PowerShell config files located at
C:\Windows\System32\WindowsPowerShell\v1.0\Modules\SnapCenter\ to modify the
default values. If the error is related to the other parameters, you should fix the issue, and then
validate the requirements again.
Note: In an NLB setup, if you are updating the web.config file, you must update the file on
both the nodes.
7. Review the summary, and then click Finish.
You should monitor the installation progress. Refresh the Hosts page after a few minutes to see
the newly added host.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 95
After a vSphere host is successfully installed, SnapCenter automatically registers the Plug-in for
VMware vSphere with vCenter Server and installs the Plug-in for VMware vSphere web client on
the vCenter Server.
Note: The installation procedure does not validate the vCenter information that you provided
before adding the host. If the vCenter information is not correct, the add host operation
finishes, and a warning is displayed for the “Registering vCenter details with SnapCenter Plugin for VMware vSphere” task. You can update the vCenter information for that host from the
Hosts page.
Related concepts
Updating SnapCenter and vCenter settings on page 99
Related tasks
Setting up your Run As credentials on page 53
Related references
Installation requirements for the Plug-in for VMware vSphere on page 80
Installing the Plug-in for VMware vCenter from the SnapCenter Server host
by using PowerShell cmdlets
You should install the Plug-in for VMware vSphere from the SnapCenter GUI. If you do not want to
use the GUI, you can use PowerShell cmdlets on the SnapCenter Server host to install the plug-in on
the SnapCenter Server or on a remote host.
Before you begin
•
You must be a local administrator on the host.
•
You must have reviewed the installation requirements and types of supported configurations
before installing the Plug-in for VMware vSphere.
Steps
1. On the SnapCenter Server host, open the SM connection by using the Open-SmConnection
command.
2. Add a host by using the Add-SmHost command.
This command adds the host where you want the Plug-in for VMware vSphere to be installed.
The host can be the SnapCenter Server host or a dedicated host.
3. Install the Plug-in for VMware vSphere by using the Install-SmHostPackage command.
This command installs the Plug-in for VMware vSphere on the specified host, and then registers
the plug-in on the specified vCenter. The host must be a Windows host.
Related concepts
Updating SnapCenter and vCenter settings on page 99
Related tasks
Setting up your Run As credentials on page 53
Related references
Installation requirements for the Plug-in for VMware vSphere on page 80
96 | SnapCenter Software Installation and Setup Guide
Installing the Plug-in for VMware vSphere from a local host by using the
installer GUI for the SnapCenter Plug-ins Package for Windows
You should install the SnapCenter Plug-in for VMware vSphere from the SnapCenter GUI. If you
cannot do so for some reason, you can install the Plug-in for VMware vSphere from a local dedicated
host by using the installer GUI for the SnapCenter Plug-ins Package for Windows. This is the
preferred standalone installment method because it installs the plug-in on the local Windows host and
opens a link to register the plug-in with the specified vCenter.
Before you begin
•
You must be a local administrator on the host.
•
You must have reviewed the installation requirements and types of supported configurations
before installing the Plug-in for VMware vSphere.
Note: This method is supported only for the Plug-in for VMware vSphere and only for installing
on a dedicated host, not for installing on the SnapCenter Server host. You cannot install other plugins by using this method.
Steps
1. On the SnapCenter Server host, navigate to C:\ProgramData\NetApp\SnapCenter\Package
Repository, copy the snapcenter_windows_host_plugin file, and then paste the file on
the local host where you want the Plug-in for VMware vSphere to be installed.
The SnapCenter Plug-ins Package for Windows includes the Plug-in for VMware vSphere.
2. On the local host, double-click the .exe file to start the installer wizard for the Plug-in for
VMware vSphere.
After successful installation, the installer opens a page to register the Plug-in for VMware
vSphere with vCenter. The installer uses the link https://<SCV IP>:8144/scbr/
register.html to access the registration page. <SCV IP> is the IP address of the Plug-in for
VMware vSphere.
3. Specify the vCenter Server information that is required on the page to register the Plug-in for
VMware vSphere with vCenter:
For this field…
Do this…
Host name or IP Address
Specify the IP address of the vCenter Server that the Plug-in for
VMware vSphere should communicate with.
Port
443
User name
Type the vCenter administrator name that SnapCenter Server uses
to log in to vCenter.
Password
Type the vCenter administrator login password.
4. Click Register.
5. Log on to vCenter to configure the Plug-in for VMware vSphere for the SnapCenter Server.
6. In the VMware vSphere web client in vCenter for the Plug-in for VMware vSphere, in the left
navigation pane, click Settings > Configure SnapCenter Server , and then specify the
information that is required on the Configure SnapCenter Server page:
Installing and setting up SnapCenter Plug-in for VMware vSphere | 97
For this field…
Do this…
Server
Type the IP address of the SnapCenter Server.
Note: If the SnapCenter Server is on a host that is configured
for Microsoft Windows Network Load Balancing (NLB), then
you must enter the NLB cluster IP address.
Port
Type the SnapCenter Server HTTPS port that is used to
communicate with vCenter.
The default port is 8146.
Domain/Username
Type the SnapCenter administrator name that the vCenter Server
uses to log on to SnapCenter.
Password
Type the SnapCenter logon password.
7. Click Confirm.
You can monitor the job status in the SnapCenter GUI by clicking Monitor in the left navigation
pane.
You can check the overall status of the host in the SnapCenter GUI by clicking Hosts in the left
navigation pane.
Related concepts
Updating SnapCenter and vCenter settings on page 99
Related tasks
Setting up your Run As credentials on page 53
Related references
Installation requirements for the Plug-in for VMware vSphere on page 80
Installing the Plug-in for VMware vSphere from a local host silently from the
command line
You should install the Plug-in for VMware vSphere from the SnapCenter GUI. If you cannot do so,
you can use the command line on a local host to install the Plug-in for VMware vSphere.
Before you begin
•
You must be a local administrator on the host.
•
You must have reviewed the installation requirements and types of supported configurations
before installing the Plug-in for VMware vSphere.
About this task
This method is also used to perform independent, standalone installations of other plug-ins. Although
you can install the Plug-in for VMware vSphere by using this method, it is more difficult because
you must manually open the link to register the Plug-in for VMware vSphere with vCenter after the
installation is completed.
98 | SnapCenter Software Installation and Setup Guide
Steps
1. On the SnapCenter Server host, navigate to C:\ProgramData\NetApp\SnapCenter\Package
Repository, copy the snapcenter_windows_host_plugin file , and then paste the file on
the local host where you want the Plug-in for VMware vSphere to be installed.
The SnapCenter Plug-ins Package for Windows includes the Plug-in for VMware vSphere.
2. From a Windows command prompt on the local host, navigate to the directory where you pasted
the snapcenter_windows_host_plugin file.
3. Start the installation .exe file:
“snapcenter_windows_host_plugin.exe"/silent /debuglog"DirPath
\DebugLogFileName" /log"DirPath\InstallLogFileName"
SUITE_INSTALLDIR="InstallDirectory" BI_SCV_PORT=8144
ISFeatureInstall=SCV
Enter the following for each variable:
Variable
Description
DirPath
\DebugLogFileName
The location and name of the plug-in prerequisite check log
DirPath
\InstallLogFileName
The location and name of the installation log
InstallDirectory
The directory where you want to install the plug-in
Example
“snapcenter_windows_host_plugin.exe"/silent
/debuglog"c:\VSC\Add_Plugin_SCV.log"
/log"c:\VSC" SUITE_INSTALLDIR="C:\Program Files\NetApp\SnapCenter"
BI_SCV_PORT=8144 ISFeatureInstall=SCV
4. After successful installation, register the Plug-in for VMware vSphere with vCenter by opening
the https://<SCV IP>:8144/scbr/register.html link to access the registration page.
<SCV IP> is the IP address of the Plug-in for VMware vSphere.
5. Specify the vCenter Server information that is required on the page to register the Plug-in for
VMware vSphere with vCenter Server:
For this field…
Do this…
Host name or IP Address
Specify the IP address of the vCenter that the Plug-in for VMware
vSphere should communicate with.
Port
443
User name
Type the vCenter administrator name that SnapCenter Server uses
to log in to vCenter.
Password
Type the vCenter administrator login password.
6. Click Register.
7. Log on to vCenter to configure the Plug-in for VMware vSphere for the SnapCenter Server.
8. In the VMware vSphere web client in vCenter for the Plug-in for VMware vSphere, in the left
navigation pane, click Settings > Configure SnapCenter Server , and then specify the
information that is required on the Configure SnapCenter Server page:
Installing and setting up SnapCenter Plug-in for VMware vSphere | 99
For this field…
Do this…
Server
Type the IP address of the SnapCenter Server.
Note: If the SnapCenter Server is on a host that is configured
for Microsoft Windows Network Load Balancing (NLB), then
you must enter the NLB cluster IP address.
Port
Type the SnapCenter Server HTTPS port that is used to
communicate with vCenter.
The default port is 8146.
Domain/Username
Type the SnapCenter administrator name that the vCenter Server
uses to log on to SnapCenter.
Password
Type the SnapCenter logon password.
9. Click Confirm.
You can monitor the job status in the SnapCenter GUI by clicking Monitor in the left navigation
pane.
You can check the overall status of the host in the SnapCenter GUI by clicking Hosts in the left
navigation pane.
Related concepts
Updating SnapCenter and vCenter settings on page 99
Related tasks
Setting up your Run As credentials on page 53
Related references
Installation requirements for the Plug-in for VMware vSphere on page 80
Related information
SnapCenter Software 3.0.1 Windows Cmdlet Reference Guide
Updating SnapCenter and vCenter settings
After you install SnapCenter, you might need to update the vCenter or SnapCenter configuration
information for the SnapCenter Plug-in for VMware vSphere.
Related tasks
Updating hypervisor configuration settings on page 100
Updating vCenter or SnapCenter information in the SnapCenter Plug-in for VMware vSphere on
page 100
100 | SnapCenter Software Installation and Setup Guide
Updating hypervisor configuration settings
You can update your hypervisor configuration settings so that SnapCenter no longer displays a
"configure hypervisor" message in the host status area.
Before you begin
•
If you are using SnapCenter Plug-in for Microsoft SQL Server, your SQL Server environment
must be using NFS or an iSCSI initiator.
•
If you are using SnapCenter Plug-in for Oracle Database, your Oracle environment must be using
NFS or an iSCSI initiator.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Global Settings.
3. In the Hypervisor settings area, select VMs have iSCSI direct attached disks or NFS for all
the hosts and then click Update.
The host status for the VM changes from “configure hypervisor” to “Running.”
Updating vCenter or SnapCenter information in the SnapCenter Plug-in for
VMware vSphere
You might need to update the vCenter or SnapCenter host information that the SnapCenter Plug-in
for VMware vSphere uses when communicating with vCenter. For example, an update might be
necessary if the vCenter password for a host was changed.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, select the vSphere-type host.
3. Click the Add/Update vCenter details button.
4. In the dialog box, select the type of information you want to update:
Add/Update vCenter Details
Add/Update SnapCenter Details
5. In the dialog box, enter only the information that needs to be updated.
Blank fields are not changed.
6. Click OK.
Upgrading SnapCenter Plug-in for VMware vSphere
Each release of SnapCenter contains an updated SnapCenter Server and plug-in package updates. The
updates for SnapCenter Plug-ins Package for Windows include an update for SnapCenter Plug-in for
VMware vSphere that is distributed with the SnapCenter installer.
Before you begin
You must upgrade the SnapCenter Server before you can upgrade the Plug-in for VMware vSphere
hosts.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 101
About this task
The following upgrade paths are supported for the Plug-in for VMware vSphere:
From version...
You can upgrade to version...
2.0
3.0, 3.0.1
3.0
3.0.1
•
You can only upgrade one host at a time.
•
vSphere hosts are not put in maintenance mode during the upgrade operation.
•
Upgrade each virtualized database and application host
If you are using SnapCenter to protect virtualized databases and applications, then the Plug-in for
VMware vSphere is also installed on those hosts. In addition to upgrading your database or file
system plug-ins, you must also upgrade the Plug-in for VMware vSphere on each host that
contains virtualized data.
•
Migrating VSC hosts
If you are using VSC to back up and restore VMs and datastores, you cannot use VSC in
SnapCenter 3.0 and later. Instead, you must migrate each VSC host to SnapCenter Plug-in for
VMware vSphere. The migration operation automatically installs the Plug-in for VMware
vSphere on your VSC hosts, installs a SnapCenter Plug-in for VMware vSphere web client in
vCenter, and migrates your VSC backups, policies, and resource groups.
Note: The upgrade operation only migrates VSC backups that were performed using
SnapCenter.
SnapCenter 3.0 and later does not support VSC 6.2x. If you have VSC 6.2x installed and
registered after upgrading to SnapCenter, then all vSphere hosts in the SnapCenter GUI are listed
with the status "Plug-in incompatible" until you migrate the VSC host to the Plug-in for VMware
vSphere.
After you migrate a VSC host to the Plug-in for VMware vSphere, if you want to use VSC to
perform VM management tasks other than backup and restore then you must upgrade to VSC 7.0
virtual appliance. See the VSC documentation for details.
Steps
1. In the left navigation pane, click Hosts.
2. Verify that Managed Hosts is selected at the top.
3. Select the host for which you want to upgrade the plug-in package.
4. Click Modify in the toolbar.
5. In the Modify page, select Upgrade plug-ins.
Note: All the plug-ins in the package gets selected but only the plug-ins that were installed
with the earlier version of SnapCenter are upgraded and the remaining plug-ins are not
installed. You must use the Add plug-ins option to install any new plug-in.
Note: If you have the Windows plug-ins 1.1 package installed on the SnapCenter 1.1 host
(Windows host), while upgrading the plug-ins to 3.0, the Add plug-ins option is selected by
default and the Upgrade plug-ins option is disabled. You can successfully upgrade the plug-ins
by selecting the Add plug-ins option.
The Modify Port option is not active for the Plug-in for VMware vSphere.
6. Select Skip preinstall checks if you do not want to validate whether the host meets the
requirements to upgrade the plug-in.
102 | SnapCenter Software Installation and Setup Guide
If you installed SnapCenter Plug-in for VMware vSphere with a custom install path, then you
must check the Skip preinstall checks check box, otherwise the upgrade will fail.
7. Select the SnapCenter Plug-ins Package for Windows and then click OK.
8. Click Next.
If you have not selected the Skip preinstall checks check box, the host is validated to see if it
meets the requirements to install the plug-in. The disk space, RAM, PowerShell version, .NET
version, and location are validated against the minimum requirements. If the minimum
requirements are not met, appropriate error or warning messages are displayed. After fixing the
issue, click Validate to re-validate the requirements.
Note: If the error is related to disk space or RAM, you can either update the web.config
located at C:\Program Files\NetApp\SnapCenter WebApp or PowerShell config files
located at C:\Windows\System32\WindowsPowerShell\v1.0\Modules\SnapCenter\
to modify the default values. If the error is related to remaining parameters you must fix the
issue and then validate the requirements again.
9. Review the summary, and then click Finish.
The upgrade operation also registers the Plug-in for VMware vSphere with vCenter and adds a
vSphere web client in vCenter.
After you finish
•
•
After a successful upgrade of the Plug-in for VMware vSphere on a host, do the following:
◦
Check the new web client in vCenter
Log onto vCenter to verify that SnapCenter Plug-in for VMware vSphere is added as a web
client. If the plug-in is not displayed in vCenter, then you need to restart the vCenter web
client service.
◦
Migrate the VSC host
If you used VSC in conjunction with earlier versions of SnapCenter, you must migrate the
VSC host to SnapCenter Plug-in for VMware vSphere before you can use the new web client
in vCenter to perform backup and restore operations on VMs and datastores.
If you upgraded the Plug-in for VMware vSphere on a host in an NLB/ARR configuration, do the
following to update the cluster IP and configure SnapCenter with the correct IP:
1. In the left navigation pane in the SnapCenter GUI, click Hosts.
2. Select the vsphere host and then click Add/update vCenter Details in the plug-in
information table on the right.
3. Check the box Update SnapCenter Details.
Related concepts
Upgrading SnapCenter and SnapCenter plug-in packages on page 134
Migrating VSC hosts on page 103
Related tasks
Configuring SnapCenter to check for available updates on page 134
Upgrading the SnapCenter Server on page 136
Upgrading your plug-in packages on page 138
Restarting the vSphere web client service on page 110
Installing and setting up SnapCenter Plug-in for VMware vSphere | 103
Migrating VSC hosts
If you used Virtual Storage Console for VMware vSphere (VSC) with SnapCenter 2.x, then when
you upgrade to SnapCenter 3.0.x, you must migrate your VSC hosts to SnapCenter Plug-in for
VMware vSphere for performing backup and restore operations on VMs and datastores.
There are two ways you can migrate your VM policies, resource groups, and backups from VSC:
•
Migrate using the SnapCenter GUI
This is the typical choice for SnapCenter admins who seldom use vCenter.
•
Migrate using the SnapCenter Plug-in for VMware vSphere GUI in vCenter
This is the typical choice for vCenter admins who seldom use the SnapCenter GUI.
You can only migrate one host at a time although you can run several migration jobs concurrently. If
your vCenter is in Linked Mode or Enhanced Linked Mode, you must migrate each host separately.
Attention: You must migrate all the hosts in Linked Mode or Enhanced Linked Mode before
beginning SnapCenter data protection operations. With linked hosts, you cannot run a mix of the
Plug-in for VMware vSphere and VSC.
The migration procedure installs the Plug-in for VMware vSphere and migrates VSC backup
policies, backups, and backup jobs (called resource groups in SnapCenter) so they are available for
use in the Plug-in for VMware vSphere GUI in vCenter.
Note: The migrate operation only migrates VSC backups that were performed using SnapCenter.
Prerequisites for migrating VSC hosts
Before you migrate your VSC hosts (which includes migrating backups, policies, and resource
groups) to SnapCenter Plug-in for VMware vSphere, you must meet the migration requirements.
The migration requirements must be performed in the following order:
1. VSC must be registered with SnapCenter 2.0.
If you are using VSC that was not registered with SnapCenter before the upgrade, then you
cannot migrate your VSC hosts to the SnapCenter plug-in after the upgrade.
2. The VM backups you want to migrate must have been performed using VSC when SnapCenter
was registered with VSC.
Note: You cannot migrate a standalone VSC host.
3. You must have upgraded your SnapCenter host and be running the following software versions:
104 | SnapCenter Software Installation and Setup Guide
•
SnapCenter 3.0 or later
•
Virtual Storage Console for VMware vSphere 6.2.1 or later
Note: You must not upgrade to VSC 7.0 until after you migrate your VSC hosts to
SnapCenter Plug-in for VMware vSphere.
•
VMware vCenter Server 6.0 update 3 or later
If you are migrating using the vCenter GUI, you must be using the vCenter that was registered with
the VSC host.
Migrating a VSC host using the SnapCenter GUI
After you upgrade to SnapCenter 3.0.x, you must migrate the VSC backups that you created in
vCenter to SnapCenter Plug-in for VMware vSphere. If you are a SnapCenter admin who seldom
uses vCenter, you might want to perform the VSC host migration from the SnapCenter GUI.
Before you begin
You must have read the migration prerequisites.
About this task
•
You can migrate only one VSC host at a time
If your environment has one SnapCenter Server that is registered with two or more VSC hosts,
you must migrate each VSC host separately. If your vCenter is in Linked Mode or Enhanced
Linked Mode, you must migrate each host separately.
•
Migrating VSC hosts after upgrading
After you upgrade SnapCenter Server to 3.0.x, all vSphere hosts in the SnapCenter GUI are listed
with the status "Plug-in incompatible" until you migrate each VSC host to SnapCenter Plug-in for
VMware vSphere.
After the migration, you can perform your VM and datastore backup and restore operations using
the SnapCenter Plug-in for VMware vSphere GUI on vCenter, which allows you access to
SnapCenter features.
Attention: Unlike install and upgrade operations, not all validation checks for prerequisites are
performed during migration operations. Therefore, if a migration fails, check the information that
you provided in the migration wizard for the SnapCenter Server, VSC host, and vCenter.
Most of the fields on the migrate wizard pages are self-explanatory. The following information
describes some of the fields for which you might require guidance.
Steps
1. Log on to SnapCenter with the same username that is registered for VSC in SnapCenter.
2. In the left navigation pane, click Hosts.
After the SnapCenter Server host is upgraded to 3.0.x, but before you migrate VSC, all vSphere
hosts are listed as "Plug-in incompatible."
3. Select a vSphere host and then click Migrate in the toolbar.
4. In the Host page of the wizard, perform the following:
For this field…
Do this…
VSC host
This field is entered automatically with the vSphere host you
selected.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 105
For this field…
Do this…
Install VMware Plugin on VSC host
and
VMware Plug-in host
Specifies the host where you want Plug-in for VMware vSphere
installed.
•
Install VMware Plug-in on VSC host
To migrate to the same host, check the box. The VSC host name
is automatically entered.
•
VMware Plug-in host
To migrate to a different host, do not check the box, then enter the
name of the host you want to migrate to. You must specify a
Windows host.
Type
This field is entered automatically.
Run As name
Specifies a vCenter administrator. The current Run As name is
entered automatically. To change the Run As credentials, perform
one of the following:
Port
•
Select a different Run As name from the drop-down list.
•
Click
and enter the new Run As account information in the
dialog box.
This field is entered automatically.
5. In the Discover plug-ins page, SnapCenter lists the plug-ins that are running on the host named
in the Host page.
6. In the Plug-ins page, specify the information for the Plug-in for VMware vSphere host.
The vCenter must be the same vCenter that VSC is using.
7. In the Plug-ins page, the Plug-in for VMware vSphere configuration fields are automatically
entered, based on the information you entered in the Host page.
You can modify the information in any field.
8. Review the summary, and then click Finish.
•
The following migration operations are performed:
a. vCenter credentials and IP address are validated.
b. RBAC credentials are validated for the vCenter user.
c. VSC is unregistered from vCenter and removed from the vCenter GUI.
Note: VSC is not uninstalled from the host.
Note: If SnapCenter Plug-in for VMware vSphere is installed on the same host as the
VSC host, the VSC service startup type is set to manual to prevent VSC from reregistering with vCenter on the restart.
d. Plug-in for VMware vSphere is installed.
•
After a successful migration from VSC to Plug-in for VMware vSphere, VSC policies,
backups, and backup jobs (called resource groups in SnapCenter) are recognized and
operational in the Plug-in for VMware vSphere GUI in vCenter.
•
If the migration is not successful, all operations are undone. After you fix the problem
indicated in the error message, you can start the migration again from the beginning.
106 | SnapCenter Software Installation and Setup Guide
9. Optional: Monitor the operation progress by clicking Monitor > Jobs.
10. Optional: When the migration completes, log on to vCenter and verify that SnapCenter Plug-in
for VMware vSphere is listed in the left Navigator pane and in the
menu.
If you do not see SnapCenter Plug-in for VMware vSphere in the vCenter GUI, then you must
restart the vCenter web client service.
The VSC host still has both VSC and SnapCenter Plug-in for VMware vSphere installed but VSC
is no longer registered with SnapCenter.
The SnapCenter GUI displays the VSC host as "vSphere."
After you finish
Important: You must complete the post-migration tasks and then restart the vCenter web client
service before you can perform data protection operations.
After you migrate a VSC host to SnapCenter Plug-in for VMware vSphere, if you want to perform
VM management tasks other than backup and restore then you must upgrade to VSC 7.0. See the
VSC documentation for details.
Related tasks
Post-migration tasks after migrating a VSC host on page 109
Restarting the vSphere web client service on page 110
Related references
Prerequisites for migrating VSC hosts on page 103
Migrating a VSC host using the vCenter GUI
After you upgrade to SnapCenter 3.0.x, you must migrate the VSC backups that you created in
vCenter to SnapCenter Plug-in for VMware vSphere. If you are a vCenter admin who seldom uses
the SnapCenter GUI, you might want to perform the VSC host migration from the vCenter GUI.
Before you begin
You must have read the migration prerequisites.
About this task
•
You can migrate only one VSC host at a time
If your environment has one SnapCenter Server that is registered with two or more VSC hosts,
you must migrate each VSC host separately. If your vCenter is in Linked Mode or Enhanced
Linked Mode, you must migrate each host separately.
•
Migrating VSC hosts after upgrading
After you upgrade SnapCenter Server to 3.0.x, all vSphere hosts in the SnapCenter GUI are listed
with the status "Plug-in incompatible" until you migrate each VSC host to SnapCenter Plug-in for
VMware vSphere.
After the migration, you can perform your VM and datastore backup and restore operations using
the SnapCenter Plug-in for VMware vSphere GUI on vCenter, which allows you access to
SnapCenter features.
Attention: Unlike install and upgrade operations, not all validation checks for prerequisites are
performed during migration operations. Therefore, if a migration fails, check the information that
you provided in the migration wizard for the SnapCenter Server, VSC host, and vCenter.
Installing and setting up SnapCenter Plug-in for VMware vSphere | 107
Steps
1. On the SnapCenter host, locate the SnapCenter Windows host plug-in package (filename
snapcenter_windows_host_plugin), copy it, and then paste the copy onto the VSC host
where you want SnapCenter Plug-in for VMware vSphere installed.
You can install the Plug-in for VMware vSphere on the same host as the VSC host. It must be a
Windows host.
2. Log on to the host with the same username that is registered for VSC in SnapCenter.
3. On the host, run the .exe file in the Windows host plug-in package.
The program installs the Plug-in for VMware vSphere on the host.
At this point, the VSC host has both VSC and the Plug-in for VMware vSphere installed. The
SnapCenter GUI continues to display the VSC host as "Plug-in incompatible."
When the install completes, it opens a window for you to register the Plug-in for VMware
vSphere with vCenter.
4. Fill in the fields to manually register the Plug-in for VMware vSphere with vCenter, click
Register, and then close the window.
5. Log on to vCenter.
vCenter displays both VSC and SnapCenter Plug-in for VMware vSphere web clients.
6. In the VMware vSphere web client GUI, click
Plug-in for VMware from the drop-down list.
in the toolbar, and then select SnapCenter
7. In the left navigation pane, click Settings and then click the Configure SnapCenter Server tab.
108 | SnapCenter Software Installation and Setup Guide
8. Enter the SnapCenter Server information and then click Migrate.
The SnapCenter Server information must be the same as that used by VSC.
•
During the migration, the following operations are performed:
a. SnapCenter credentials and IP address are validated.
b. Validates that the VSC host is registered with SnapCenter. If it is registered, then the
migration continues. If it is not registered, then the Plug-in for VMware vSphere is
installed and registered with SnapCenter; there is nothing to migrate.
c. RBAC credentials are validated for the vCenter user.
d. VSC is unregistered from vCenter and removed from the vCenter GUI.
Attention: VSC is not uninstalled from the host.
Note: If the Plug-in for VMware vSphere is installed on the same host as the VSC host,
the VSC service startup type is set to manual to prevent VSC from re-registering with
vCenter on the restart.
•
After a successful migration from VSC to the Plug-in for VMware vSphere, VSC policies and
backup jobs (called resource groups in SnapCenter) are recognized and operational in the
Plug-in for VMware vSphere GUI.
•
If the migration is not successful, all operations are undone. After you fix the problem
indicated in the error message, you can start the migration again from the beginning.
9. Optional: After the migration completes, verify that the Plug-in for VMware vSphere is listed in
the left Navigator pane and in the vCenter
menu.
If you do not see SnapCenter Plug-in for VMware vSphere in vCenter, then you must restart the
vCenter web client service.
The VSC host still has both VSC and SnapCenter Plug-in for VMware vSphere installed but VSC
is no longer registered with SnapCenter.
The SnapCenter GUI displays the VSC host as "vSphere."
After you finish
Important: You must complete the post-migration tasks and then restart the vCenter web client
service before you can perform data protection operations.
After you migrate a VSC host to the Plug-in for VMware vSphere, if you want to perform VM
management tasks other than backup and restore then you must upgrade to VSC 7.0. See the VSC
documentation for details.
Related tasks
Post-migration tasks after migrating a VSC host on page 109
Restarting the vSphere web client service on page 110
Related references
Prerequisites for migrating VSC hosts on page 103
Installing and setting up SnapCenter Plug-in for VMware vSphere | 109
Post-migration tasks after migrating a VSC host
After you migrate a VSC host to SnapCenter Plug-in for VMware vSphere, you must complete the
post-migration cleanup and uninstallation tasks.
About this task
Attention: If you are using vCenter servers in Linked Mode or Enhanced Linked Mode, you must
perform the following steps on each vCenter server.
Steps
1. Assign new SCV roles to Active Directory users.
The installation of SnapCenter Plug-in for VMware vSphere creates four new roles in vCenter:
SCV Administrator, SCV View, SCV Backup, and SCV Restore.
a. Log on to vCenter as the domain administrator.
For example, log on as administrator@vsphere.local.
b. In the left Navigator pane of the vCenter GUI, select vCenter Inventory Lists (or Global
Inventory Lists in vCenter 6.5).
c. In the left Navigator pane, select Resources > vCenter Servers.
d. Right-click the vCenter server and select Add Permission from the drop-down menu.
e. Assign the new SCV roles to users.
2. Uninstall VSC from the host.
If you no longer plan to use other VSC features, you must uninstall VSC after a successful
migration of a VSC host.
If you want to use VSC to perform VM management tasks other than backup and restore, then
you must upgrade VSC to VSC 7.0 virtual appliance. See the VSC documentation for details.
a. On the VSC host, locate the program to be uninstalled.
Example
The program to be installed might have a file path similar to the following: Control Panel
\Programs\Programs and Features\NetApp Virtual Storage Console 6.2.1P1
for VMware vSphere
b. Uninstall the VSC program by using the Windows Uninstall utility.
3. Remove VSC roles from vCenter.
You must delete the VSC roles because they cannot be used when SnapCenter Plug-in for
VMware vSphere is installed.
a. Log on to vCenter as the vSphere.local administrator.
For example, log on as administrator@vsphere.local.
(Home) and select Administrator (or Administration in vCenter 6.5), and then
b. Click
click Roles.
c. Delete all the VSC roles.
110 | SnapCenter Software Installation and Setup Guide
After you finish
Next, you must restart the vCenter web client service.
To clean up secondary VSC backups that are listed in the SnapCenter Plug-in for VMware vSphere
GUI in vCenter, run the following PowerShell cmdlets on the SnapCenter host: Remove-SmBackup
and CleanupSecondaryBackups.
Virtual Storage Console, VASA Provider, and Storage Replication Adapter for VMware vSphere
Administration Guide for 7.0 release
SnapCenter Software 3.0.1 Windows Cmdlet Reference Guide
Related tasks
Restarting the vSphere web client service in Windows on page 110
Restarting the vSphere web client service in Linux on page 111
Restarting the vSphere web client service
You must restart the VMware vSphere web client service in vCenter after migrating Virtual Storage
Console for VMware vSphere (VSC) hosts to SnapCenter Plug-in for VMware vSphere.
About this task
You might also need to restart the web client service if you see the following after a fresh install or a
vCenter upgrade or an upgrade on a host where Virtual Storage Console for VMware vSphere (VSC)
was previously installed:
•
Right-click menus that are documented for mount, unmount, attach, and detach operations do not
appear.
•
The SnapCenter Plug-in for VMware vSphere GUI in vCenter does not match the documentation.
•
VMware privilege labels are not correct after a vCenter upgrade.
Note: The steps for restarting the vSphere web client service are different depending upon the
following:
•
Platform: Windows or Linux
•
vCenter version: 6.0 update 3 or later
Restarting the vSphere web client service in Windows
If your vCenter is on a Windows host, then you must use Windows commands to restart the VMware
vSphere web client service.
Steps
1. If you are running vCenter 6.5 or later, perform the following:
a. Stop the web client service by using the following command:
C:\Program Files\VMware\vCenter Server\vmon>.\vmon-cli --stop vsphereclient
Wait for the message Completed Stop service request.
b. Delete all stale packages on vCenter by performing the following:
Installing and setting up SnapCenter Plug-in for VMware vSphere | 111
i. Navigate to the vCenter packages folder at %PROGRAMDATA%/VMware/
vCenterServer/cfg/vsphere-client/vc-packages/vsphere-clientserenity
ii. Delete all plug-in folders with the following name: com.netapp.scvm.webclient<version_number>.
c. Restart the web client service by using the following command:
C:\Program Files\VMware\vCenter Server\vmon>.\vmon-cli --start
vsphere-client
Wait for the message Completed Start service request..
2. If you are running vCenter 6.0 update 3 or later, perform the following:
a. Open Server Manager on the Windows system on which vCenter Server is running.
b. Click Configuration > Services.
c. Select VMware vSphere Web Client and click Stop.
d. Delete all stale packages on vCenter by performing the following:
i. Navigate to the vCenter packages folder at %PROGRAMDATA%/VMware/
vCenterServer/cfg/vsphere-client/vc-packages/vsphere-clientserenity
ii. Delete all plug-in folders with the following name: com.netapp.scvm.webclient<version_number>.
e. Select VMware vSphere Web Client and click Start.
Restarting the vSphere web client service in Linux
If your vCenter is on a Linux appliance, then you must use Linux commands to restart the VMware
vSphere web client service.
Steps
1. If you are running vCenter 6.5 or later, perform the following:
a. Use SSH to log in to the vCenter Server Appliance as root.
b. Access the Appliance Shell or BASH Shell by using the following command:
shell
c. Stop the web client service by using the following command:
service-control --stop vsphere-client
d. Delete all stale packages on vCenter by using the following command:
/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
e. Start the web client service by using the following command:
service-control --start vsphere-client
2. If you are running vCenter 6.0 update 3 or later, perform the following:
a. Use SSH to log in to the vCenter Server Appliance as root.
b. Access the Appliance Shell or BASH Shell by using the following command:
shell
112 | SnapCenter Software Installation and Setup Guide
c. Navigate to the directory by using the following command:
cd /bin
d. Stop the web client service by using the following command:
service-control --stop vsphere-client
e. Delete all stale packages on vCenter by using the following command:
/etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity/
f. Start the web client service by using the following command:
service-control --start vsphere-client
113
Preparing storage systems for SnapMirror and
SnapVault replication
You can use a SnapCenter plug-in with ONTAP SnapMirror technology to create mirror copies of
backup sets on another volume, and with ONTAP SnapVault technology to perform disk-to-disk
backup replication for standards compliance and other governance-related purposes. Before you
perform these tasks, you must configure a data-protection relationship between the source and
destination volumes and initialize the relationship.
Note: If you are coming to SnapCenter from a NetApp SnapManager product and are satisfied
with the data protection relationships you have configured, you can skip this section.
A data protection relationship replicates data on primary storage (the source volume) to secondary
storage (the destination volume). When you initialize the relationship, ONTAP transfers the data
blocks referenced on the source volume to the destination volume.
Note: SnapCenter does not support cascade relationships between SnapMirror and SnapVault
volumes (Primary > Mirror > Vault). Use fanout relationships only (Primary > Mirror,
Primary > Vault).
SnapCenter supports the management of version-flexible SnapMirror relationships. For details about
version-flexible SnapMirror relationships and how to set them up, see the ONTAP documentation.
ONTAP 9 Data Protection Guide Using SnapMirror and SnapVault Technology
Understanding the differences between SnapMirror and
SnapVault
SnapMirror is disaster recovery technology, designed for failover from primary storage to secondary
storage at a geographically remote site. SnapVault is disk-to-disk backup replication technology,
designed for standards compliance and other governance-related purposes.
These objectives account for the different balance each technology strikes between the goals of
backup currency and backup retention:
•
SnapMirror stores only the Snapshot copies that reside in primary storage, because, in the event
of a disaster, you need to be able to fail over to the most recent version of primary data you know
to be good.
Your organization, for example, might mirror hourly copies of production data over a ten-day
span. As the failover use case implies, the equipment on the secondary system must be equivalent
or nearly equivalent to the equipment on the primary system to serve data efficiently from
mirrored storage.
•
SnapVault, in contrast, stores Snapshot copies whether or not they currently reside in primary
storage, because, in the event of an audit, access to historical data is likely to be as important as
access to current data.
You might want to keep monthly Snapshot copies of your data over a 20-year span, for example,
to comply with government accounting regulations for your business. Because there is no
requirement to serve data from secondary storage, you can use slower, less expensive disks on the
vault system.
The different weights that SnapMirror and SnapVault give to backup currency and backup retention
ultimately derive from the limit of 255 Snapshot copies for each volume. While SnapMirror retains
the most recent copies, SnapVault retains the copies made over the longest period of time.
114 | SnapCenter Software Installation and Setup Guide
Preparing storage systems for SnapMirror replication
Before you can use a SnapCenter plug-in to mirror Snapshot copies, you need to configure a dataprotection relationship between the source and destination volumes, then initialize the relationship.
Upon initialization, SnapMirror makes a Snapshot copy of the source volume, then transfers the copy
and all the data blocks that it references to the destination volume. It also transfers any other, less
recent Snapshot copies on the source volume to the destination volume.
Before you begin
•
•
•
You must have created the source and destination volumes in peered clusters with peered Storage
Virtual Machines (SVMs).
ONTAP 9 Cluster Peering Express Guide
You must be a cluster administrator.
For Snapshot copy verification on the destination volume, the source and destination Storage
Virtual Machines (SVMs) must have a management LIF as well as a data LIF.
The management LIF must have the same DNS name as the SVM. Set the management LIF role
to data, the protocol to none, and the firewall policy to mgmt.
About this task
You can use the ONTAP command-line interface (CLI) or OnCommand System Manager to create a
SnapMirror relationship. The following procedure documents CLI usage.
Important: If you are storing database files and transaction logs on different volumes, you must
create relationships between the source and destination volumes for the database files and between
the source and destination volumes for the transaction logs.
The following illustration shows the procedure for initializing a SnapMirror relationship:
Steps
1. Identify the destination cluster.
2. On the destination cluster, use the volume create command with the -type DP option to create
a SnapMirror destination volume that is either the same or greater in size than the source volume.
Preparing storage systems for SnapMirror and SnapVault replication | 115
Important: The language setting of the destination volume must match the language setting of
the source volume.
Example
The following command creates a 2 GB destination volume named dstvolB in SVM2 on the
aggregate node01_aggr:
cluster2::> volume create -vserver SVM2 -volume dstvolB -aggregate node01_aggr -type DP
-size 2GB
3. On the destination SVM, use the snapmirror create command with the -type DP parameter
to create a SnapMirror relationship.
The DP type defines the relationship as a SnapMirror relationship.
Example
The following command creates a SnapMirror relationship between the source volume srcvolA on
SVM1 and the destination volume dstvolB on SVM2, and assigns the default SnapMirror policy
DPDefault:
SVM2::> snapmirror create -source-path SVM1:srcvolA -destination-path SVM2:dstvolB
-type DP
Note: Do not define a mirror schedule for the SnapMirror relationship. The SnapCenter plug-in
does that for you when you create a backup schedule.
If you do not want to use the default SnapMirror policy, you can invoke the snapmirror
policy create command to define a SnapMirror policy.
4. Use the snapmirror initialize command to initialize the relationship.
The initialization process performs a baseline transfer to the destination volume. SnapMirror
makes a Snapshot copy of the source volume, then transfers the copy and all the data blocks it
references to the destination volume. It also transfers any other Snapshot copies on the source
volume to the destination volume.
Example
The following command initializes the relationship between the source volume srcvolA on SVM1
and the destination volume dstvolB on SVM2:
SVM2::> snapmirror initialize -destination-path SVM2:dstvolB
Preparing storage systems for SnapVault replication
Before you can use a SnapCenter plug-in to perform disk-to-disk backup replication, you need to
configure a data-protection relationship between the source and destination volumes, then initialize
the relationship. On initialization, SnapVault makes a Snapshot copy of the source volume, then
transfers the copy and all the data blocks it references to the destination volume.
Before you begin
•
•
You must have created the source and destination volumes in peered clusters with peered Storage
Virtual Machines (SVMs).
ONTAP 9 Cluster Peering Express Guide
You must be a cluster administrator.
116 | SnapCenter Software Installation and Setup Guide
About this task
You can use the ONTAP command-line interface (CLI) or OnCommand System Manager to create
SnapVault relationships. The following procedure documents CLI usage.
Important: If you are storing database files and transaction logs on different volumes, you must
create relationships between the source and destination volumes for the database files and between
the source and destination volumes for the transaction logs.
The following illustration shows the procedure for initializing a SnapVault relationship:
Steps
1. Identify the destination cluster.
2. On the destination cluster, use the volume create command with the -type DP option to create
a SnapVault destination volume that is the same size as or larger than the source volume.
Important: The language setting of the destination volume must match the language setting of
the source volume.
Example
The following command creates a 2 GB destination volume named dstvolB in SVM2 on the
aggregate node01_aggr:
cluster2::> volume create -vserver SVM2 -volume dstvolB -aggregate node01_aggr -type DP
-size 2GB
3. On the destination SVM, use the snapmirror policy create command to create a SnapVault
policy.
Example
The following command creates the SVM-wide policy SVM1-vault:
SVM2::> snapmirror policy create -vserver SVM2 -policy SVM1-vault
Preparing storage systems for SnapMirror and SnapVault replication | 117
Note: Do not define a cron schedule or Snapshot copy policy for the SnapVault relationship.
The SnapCenter plug-in does that for you when you create a backup schedule.
4. Use the snapmirror policy add-rule command to add rules to the policy that define the
following Snapshot copy labels and the retention policy for each label:
•
•
•
•
•
One Time
Hourly
Daily
Weekly
Monthly
Important: The labels are case-sensitive.
These are fixed labels for options displayed when you perform a backup. You select one of these
options when you archive the backup. You must execute this command once for each of the rules
you are adding.
Example
The following command adds a rule to the SVM1-vault policy that defines the “Daily” label and
specifies that 30 Snapshot copies matching the label should be kept in the vault:
SVM2::> snapmirror policy add-rule -vserver SVM2 -policy SVM1-vault
-snapmirror-label Daily -keep 30
5. Use the snapmirror create command with the -type XDP parameter and the -policy
parameter to create a SnapVault relationship and assign a vault policy.
The XDP type defines the relationship as a SnapVault relationship.
Example
The following command creates a SnapVault relationship between the source volume srcvolA on
SVM1 and the destination volume dstvolB on SVM2, and assigns the policy SVM1-vault:
SVM2::> snapmirror create -source-path SVM1:srcvolA -destination-path SVM2:dstvolB
-type XDP -policy SVM1-vault
6. Use the snapmirror initialize command to initialize the relationship.
The initialization process performs a baseline transfer to the destination volume. SnapMirror
makes a Snapshot copy of the source volume, then transfers the copy and all the data blocks it
references to the destination volume.
Example
The following command initializes the relationship between the source volume srcvolA on SVM1
and the destination volume dstvolB on SVM2:
SVM2::> snapmirror initialize -destination-path SVM2:dstvolB
118
Provisioning storage on Windows hosts
You can use SnapCenter to assign NetApp storage to supported Windows Server hosts. Provisioning
Windows hosts with ensureSnapCenters that the backups you create are application consistent. You
must have installed and configured the SnapCenter Plug-ins Package for Windows.
If you are coming to SnapCenter from a NetApp SnapManager product and are satisfied with how
your hosts are provisioned, you can skip this provisioning information
For the latest information about supported versions, see the NetApp Interoperability Matrix.
NetApp Interoperability Matrix Tool
Configuring LUN storage
You can use SnapCenter to configure an FC-connected or iSCSI-connected LUN. You can also use
SnapCenter to connect an existing LUN to a Windows host.
LUNs are the basic unit of storage in a SAN configuration. The Windows host sees LUNs on your
system as virtual disks. For more information, see the ONTAP 9 SAN Configuration Guide.
Establishing an iSCSI session
If you are using iSCSI to connect to a LUN, you must establish an iSCSI session before you create
the LUN to enable communication.
Before you begin
•
•
You must have defined the storage system node as an iSCSI target.
You must have started the iSCSI service on the storage system.
ONTAP 9 SAN Administration Guide
About this task
You can establish an iSCSI session only between the same IP versions: either IPv6 to IPv6 or IPv4 to
IPv4.
You can use a link-local IPv6 address for iSCSI session management and for communication
between a host and a target only when both are in the same subnet.
If you change the name of an iSCSI initiator, access to iSCSI targets is affected. After changing the
name, you might require to reconfigure the targets accessed by the initiator so that they can recognize
the new name. You must ensure to restart the host after changing the name of an iSCSI initiator.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click iSCSI Session.
3. From the Storage Virtual Machine drop-down list, select the Storage Virtual Machine (SVM)
for the iSCSI target.
4. From the Host drop-down list, select the host for the session.
5. Click Establish Session.
The Establish Session wizard is displayed.
Provisioning storage on Windows hosts | 119
6. In the Establish Session wizard, identify the target:
In this field...
Enter...
Target node name
The node name of the iSCSI target
If there is an existing target node name, the name is displayed in readonly format.
Target portal address
The IP address of the target network portal
Target portal port
The TCP port of the target network portal
Initiator portal address
The IP address of the initiator network portal
7. When you are satisfied with your entries, click Connect.
SnapCenter establishes the iSCSI session.
8. Repeat this procedure to establish a session for each target.
Disconnecting an iSCSI session
Occasionally, you might require to disconnect an iSCSI session from a target with which you have
multiple sessions.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click iSCSI Session.
3. From the Storage Virtual Machine drop-down list, select the Storage Virtual Machine (SVM)
for the iSCSI target.
4. From the Host drop-down list, select the host for the session.
5. From the list of iSCSI sessions, select the session that you want to disconnect and click
Disconnect Session.
6. In the Disconnect Session dialog box, click OK.
SnapCenter disconnects the iSCSI session.
Creating and managing igroups
You create initiator groups (igroups) to specify which hosts can access a given LUN on the storage
system. You can use SnapCenter to create, rename, modify, or delete an igroup on a Windows host.
Creating an igroup
You can use SnapCenter to create an igroup on a Windows host. The igroup will be available in the
Create Disk or Connect Disk wizard when you map the igroup to a LUN.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Igroup.
3. In the Initiator Groups page, click New.
4. In the Create Igroup dialog box, define the igroup:
120 | SnapCenter Software Installation and Setup Guide
In this field...
Do this...
Storage System
Select the SVM for the LUN you will map to the igroup.
Host
Select the host on which you want to create the igroup.
Igroup Name
Enter the name of the igroup.
Initiators
Select the initiator.
Type
Select the initiator type, iSCSI, FCP, or mixed (FCP and iSCSI).
5. When you are satisfied with your entries, click OK.
SnapCenter creates the igroup on the storage system.
Renaming an igroup
You can use SnapCenter to rename an existing igroup.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Igroup.
3. In the Initiator Groups page, click in the Storage Virtual Machine field to display a list of
available SVMs, and then select the SVM for the igroup you want to rename.
4. In the list of igroups for the SVM, select the igroup you want to rename and click Rename.
5. In the Rename igroup dialog box, enter the new name for the igroup and click Rename.
Modifying an igroup
You can use SnapCenter to add igroup initiators to an existing igroup. While creating an igroup you
can add only one host. If you want to create an igroup for a cluster, you can modify the igroup to add
other nodes to that igroup.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Igroup.
3. In the Initiator Groups page, click in the Storage Virtual Machine field to display a drop-down
list of available SVMs, then select the SVM for the igroup you want to modify.
4. In the list of igroups, select an igroup and click Add Initiator to igroup.
5. Select a host.
6. Select the initiators and click OK.
Deleting an igroup
You can use SnapCenter to delete an igroup when you no longer need it.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Igroup.
Provisioning storage on Windows hosts | 121
3. In the Initiator Groups page, click in the Storage Virtual Machine field to display a drop-down
list of available SVMs, then select the SVM for the igroup you want to delete.
4. In the list of igroups for the SVM, select the igroup you want to delete and click Delete.
5. In the Delete igroup dialog box, click OK.
SnapCenter deletes the igroup.
Creating and managing disks
The Windows host sees LUNs on your storage system as virtual disks. You can use SnapCenter to
create and configure an FC-connected or iSCSI-connected LUN.
About this task
Using SnapCenter, you can perform the following disk-related tasks:
•
View the lists of disks on a host.
•
Create a disk.
•
Resize a disk.
•
Connect to a disk.
•
Disconnect from a disk.
•
Delete a disk.
Note: SnapCenter does not support renaming a disk. If a disk that is managed by SnapCenter is
renamed, SnapCenter operations will not succeed.
Viewing the disks on a host
You can view the disks on each Windows host you manage with SnapCenter.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Disks.
3. Select the host from the Host drop-down list.
The disks are listed.
Creating FC-connected or iSCSI-connected LUNs or disks
The Windows host sees LUNs on your storage system as virtual disks. You can use SnapCenter to
create and configure an FC-connected or iSCSI-connected LUN.
Before you begin
•
You must have created a volume for the LUN on your storage system.
The volume should hold LUNs only, and only LUNs created with SnapCenter.
ONTAP 9 Logical Storage Management Guide
Note: You cannot create a LUN on a SnapCenter-created clone volume unless the clone has
already been split.
•
You must have started the FC or iSCSI service on the storage system.
•
ONTAP 9 SAN Administration Guide
If you are using iSCSI, you must have established an iSCSI session with the storage system.
122 | SnapCenter Software Installation and Setup Guide
Starting an iSCSI session on page 118
About this task
•
•
•
You cannot connect a LUN to more than one host unless the LUN is shared by hosts in a
Windows Server failover cluster.
If a LUN is shared by hosts in a Windows Server failover cluster that uses CSV (Cluster Shared
Volumes), you must create the disk on the host that owns the cluster group.
The SnapCenter Plug-ins Package for Windows must be installed only on the host on which you
are creating the disk.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Disks.
3. Select the host from the Host drop-down list.
4. Click New.
The Create Disk wizard opens.
5. On the LUN Name page, identify the LUN:
In this field...
Do this...
Storage System
Select the SVM for the LUN.
LUN path
Click Browse to select the full path of the folder containing the LUN.
LUN name
Enter the name of the LUN.
Cluster size
Select the LUN block allocation size for the cluster. Cluster size depends
upon the operating system and applications.
LUN label
Optionally, enter descriptive text for the LUN.
6. On the Disk Type page, select the disk type:
Select...
If...
Dedicated disk
The LUN can be accessed by only one host. Ignore the Resource Group
field.
Shared disk
The LUN is shared by hosts in a Windows Server failover cluster. Enter
the name of the cluster resource group in the Resource Group field.
You need only create the disk on one host in the failover cluster.
Cluster Shared Volume
(CSV)
The LUN is shared by hosts in a Windows Server failover cluster that
uses CSV. Enter the name of the cluster resource group in the Resource
Group field.
Make sure that the host on which you are creating the disk is the owner of
the cluster group.
7. On the Drive Properties page, specify the drive properties:
Property
Description
Auto assign mount point
SnapCenter automatically assigns a volume mount point based on the
system drive. For example, if your system drive is C:, auto assign creates
a volume mount point under your C: drive (C:\scmnpt\).
Auto assign is not supported for shared disks.
Provisioning storage on Windows hosts | 123
Property
Description
Assign drive letter
Mount the disk to the drive you select in the adjoining drop-down list.
Use volume mount point
Mount the disk to the drive path you specify in the adjoining field.
The root of the volume mount point must be owned by the host on which
you are creating the disk.
Do not assign drive letter or
volume mount point
Choose this option if you prefer to mount the disk manually in Windows.
LUN size
Specify the LUN size; 150 MB minimum. Select MB, GB, or TB in the
adjoining drop-down list.
Use thin provisioning for the
volume hosting this LUN
Thin provision the LUN. Thin provisioning allocates only as much
storage space as is needed at one time, allowing the LUN to grow
efficiently to the maximum available capacity.
Make sure there is enough space available on the volume to
accommodate all the LUN storage you think you will need.
Choose partition type
Select GPT partition for a GUID Partition Table, or MBR partition for a
Master Boot Record.
MBR partitions might cause misalignment issues in Windows Server
failover clusters.
8. On the Map LUN page, select the iSCSI or FC initiator on the host:
In this field...
Do this...
Host
Double-click the cluster group name to display a drop-down list that
shows the hosts that belong to the cluster and then select the host for the
initiator.
This field is displayed only if the LUN is shared by hosts in a Windows
Server failover cluster.
Choose host initiator
Select Fibre Channel or iSCSI and then select the initiator on the host.
You can select multiple FC initiators if you are using FC with multipath
I/O (MPIO).
9. On the Group Type page, specify whether you want to map an existing igroup to the LUN, or
create a new igroup:
Select...
If...
Create new igroup for
selected initiators
You want to create a new igroup for the selected initiators.
Choose an existing igroup or
specify a new igroup for
selected initiators
You want to specify an existing igroup for the selected initiators, or
create a new igroup with the name you specify. Type the igroup name in
the igroup name field. Type the first few letters of the existing igroup
name to autocomplete the field.
10. On the Summary page, review your selections and click Finish.
SnapCenter creates the LUN and connects it to the specified drive or drive path on the host.
Related tasks
Viewing the disks on a host on page 121
124 | SnapCenter Software Installation and Setup Guide
Resizing a disk
You can increase or decrease the size of a disk as your storage system needs change.
About this task
•
•
•
•
You cannot expand a LUN by more than 10 times its original size, or shrink a LUN by more than
half.
LUNs with MBR-style partitions have a size limit of 2 TB.
LUNs with GPT-style partitions have a storage system size limit of 16 TB.
It is a good idea to make a Snapshot copy before resizing a LUN.
If you need to restore a LUN from a Snapshot copy made before the LUN was resized,
SnapCenter automatically resizes the LUN to the size of the Snapshot copy.
After the restore operation, data added to the LUN after it was resized must be restored from a
Snapshot copy made after it was resized.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Disks.
3. Select the host from the Host drop-down list.
The disks are listed.
4. Select the disk you want to resize and then click Resize.
5. In the Resize Disk dialog box, use the slider tool to specify the new size of the disk, or enter the
new size in the Size field.
Note: If you enter the size manually, you need to click outside the Size field before the Shrink
or Expand button is enabled appropriately. Also, you must click MB, GB, or TB to specify the
unit of measurement.
6. When you are satisfied with your entries, click Shrink or Expand, as appropriate.
SnapCenter resizes the disk.
Related tasks
Viewing the disks on a host on page 121
Connecting a disk
You can use the Connect Disk wizard to connect an existing LUN to a host, or to reconnect a LUN
that has been disconnected.
Before you begin
•
•
You must have started the FC or iSCSI service on the storage system.
If you are using iSCSI, you must have established an iSCSI session with the storage system.
About this task
•
•
You cannot connect a LUN to more than one host unless the LUN is shared by hosts in a
Windows Server failover cluster.
If the LUN is shared by hosts in a Windows Server failover cluster that uses CSV (Cluster Shared
Volumes), you must connect the disk on the host that owns the cluster group.
Provisioning storage on Windows hosts | 125
•
The Plug-in for Windows needs to be installed only on the host on which you are connecting the
disk.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Disks.
3. Select the host from the Host drop-down list.
4. Click Connect.
The Connect Disk wizard opens.
5. On the LUN Name page, identify the LUN to connect to:
In this field...
Do this...
Storage System
Select the SVM for the LUN.
LUN path
Click Browse to select the full path of the volume containing the LUN.
LUN name
Enter the name of the LUN.
Cluster size
If the LUN is shared by hosts in a Windows cluster, select the size of the
cluster.
LUN label
Optionally, enter descriptive text for the LUN.
6. On the Disk Type page, select the disk type:
Select...
If...
Dedicated disk
The LUN can be accessed by only one host.
Shared disk
The LUN is shared by hosts in a Windows Server failover cluster.
You need only connect the disk to one host in the failover cluster.
Cluster Shared Volume
(CSV)
The LUN is shared by hosts in a Windows Server failover cluster that
uses CSV.
Make sure that the host on which you are connecting to the disk is the
owner of the cluster group.
7. On the Drive Properties page, specify the drive properties:
Property
Description
Auto assign
Let SnapCenter automatically assign a volume mount point based on the
system drive. For example, if your system drive is C:, the auto assign
property creates a volume mount point under your C: drive (C:
\scmnpt\).
The auto assign property is not supported for shared disks.
Assign drive letter
Mount the disk to the drive you select in the adjoining drop-down list.
Use volume mount point
Mount the disk to the drive path you specify in the adjoining field.
The root of the volume mount point must be owned by the host on which
you are creating the disk.
Do not assign drive letter or
volume mount point
Choose this option if you prefer to mount the disk manually in Windows.
8. On the Map LUN page, select the iSCSI or FC initiator on the host:
126 | SnapCenter Software Installation and Setup Guide
In this field...
Do this...
Host
Double-click the cluster group name to display a drop-down list that
shows the hosts that belong to the cluster, then select the host for the
initiator.
This field is displayed only if the LUN is shared by hosts in a Windows
Server failover cluster.
Choose host initiator
Select Fibre Channel or iSCSI, and then select the initiator on the host.
You can select multiple FC initiators if you are using FC with MPIO.
9. On the Group Type page, specify whether you want to map an existing igroup to the LUN or
create a new igroup:
Select...
If...
Create new igroup for
selected initiators
You want to create a new igroup for the selected initiators.
Choose an existing igroup or
specify a new igroup for
selected initiators
You want to specify an existing igroup for the selected initiators, or
create a new igroup with the name you specify. Type the igroup name in
the igroup name field. Type the first few letters of the existing igroup
name to automatically complete the field.
10. On the Summary page, review your selections and click Finish.
SnapCenter connects the LUN to the specified drive or drive path on the host.
Related tasks
Viewing the disks on a host on page 121
Disconnecting a disk
You can disconnect a LUN from a host without affecting the contents of the LUN, with one
exception: If you disconnect a clone before it has been split off, you lose the contents of the clone.
Before you begin
•
•
•
Make sure that the LUN is not in use by any application.
Make sure that the LUN is not being monitored with monitoring software.
If the LUN is shared, make sure to remove the cluster resource dependencies from the LUN and
verify that all nodes in the cluster are powered on, functioning properly, and available to
SnapCenter.
About this task
If you disconnect a LUN in a FlexClone volume that SnapCenter has created and no other LUNs on
the volume are connected, SnapCenter deletes the volume. Before disconnecting the LUN,
SnapCenter displays a message warning you that the FlexClone volume might be deleted.
To avoid automatic deletion of the FlexClone volume, you should rename the volume before
disconnecting the last LUN. When you rename the volume, make sure that you change multiple
characters than just the last character in the name.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Disks.
3. Select the host from the Host drop-down list.
Provisioning storage on Windows hosts | 127
The disks are listed.
4. Select the disk you want to disconnect, and then click Disconnect.
5. In the Disconnect Disk dialog box, click OK.
SnapCenter disconnects the disk.
Related tasks
Viewing the disks on a host on page 121
Deleting a disk
You can delete a disk when you no longer need it. After you delete a disk, you cannot undelete it.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Disks.
3. Select the host from the Host drop-down list.
The disks are listed.
4. Select the disk you want to delete, and then click Delete.
5. In the Delete Disk dialog box, click OK.
SnapCenter deletes the disk.
Related tasks
Viewing the disks on a host on page 121
Creating and managing SMB shares
To configure an SMB3 share on a Storage Virtual Machine (SVM), you can use either the
SnapCenter user interface or PowerShell cmdlets. Using the cmdlets is recommended because it
enables you to take advantage of templates provided with SnapCenter to automate share
configuration.
The templates encapsulate best practices for volume and share configuration. You can find the
templates in the Templates folder in the installation folder for the SnapCenter Plug-ins Package for
Windows.
Tip: If you feel comfortable doing so, you can create your own templates following the models
provided. You should review the parameters in the cmdlet documentation before creating a custom
template.
Creating an SMB share
You can use the SnapCenter Shares page to create an SMB3 share on a Storage Virtual Machine
(SVM).
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Shares.
128 | SnapCenter Software Installation and Setup Guide
3. Select the SVM from the Storage Virtual Machine drop-down list.
4. Click New.
The New Share dialog opens.
5. In the New Share dialog, define the share:
In this field...
Do this...
Description
Enter descriptive text for the share.
Share name
Enter the share name, for example, test_share. The name you enter
for the share will also be used as the volume name.
The share name:
Share path
•
•
Must be a UTF-8 string.
Must not include the following characters: control characters from
0x00 to 0x1F (both inclusive), 0x22 (double quotes), and the special
characters \ / [ ] : | < > + = ; , ?
•
•
Click in the field to enter a new file system path, for example, /.
Double-click in the field to select from a list of existing file system
paths.
6. When you are satisfied with your entries, click OK.
SnapCenter creates the SMB share on the SVM.
Deleting an SMB share
You can delete an SMB share when you no longer need it.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Shares.
3. In the Shares page, click in the Storage Virtual Machine field to display a drop-down with a list
of available Storage Virtual Machines (SVMs), then select the SVM for the share you want to
delete.
4. From the list of shares on the SVM, select the share you want to delete and click Delete.
5. In the Delete Share dialog box, click OK.
SnapCenter deletes the SMB share from the SVM.
Reclaiming space on the storage system
Although NTFS tracks the available space on a LUN when files are deleted or modified, it does not
report the new information to the storage system. You can run the space reclamation PowerShell
cmdlet on the Plug-in for Windows host to ensure that newly freed blocks are marked as available in
storage.
Before you begin
If you are running the cmdlet on a remote plug-in host, you must have run the SnapCenter OpenSMConnection cmdlet to open a connection to the SnapCenter Server.
Provisioning storage on Windows hosts | 129
About this task
•
•
•
•
•
•
You must ensure that the space reclamation process has completed before performing a restore
operation.
If the LUN is shared by hosts in a Windows Server failover cluster, you must perform space
reclamation on the host that owns the cluster group.
For optimum storage performance, you should perform space reclamation as often as possible.
You should ensure that the entire NTFS file system has been scanned.
Space reclamation is time-consuming and CPU-intensive, so it is usually best to run the operation
when storage system and Windows host usage is low.
Space reclamation reclaims nearly all available space, but not 100 percent.
You should not run disk defragmentation at the same time as you are performing space
reclamation.
Doing so can slow the reclamation process.
Step
1. From the application server PowerShell command prompt, enter the following command:
Invoke-SdHostVolumeSpaceReclaim -Path drive_path
drive_path is the drive path mapped to the LUN.
Related information
SnapCenter Software 3.0.1 Windows Cmdlet Reference Guide
Using the SnapCenter Plug-in for Microsoft Windows in
VMware environments
You can use the SnapCenter Plug-in for Microsoft Windows in VMware environments to create and
manage LUNs and manage Snapshot backup copies.
Note: For more information on support for VMware storage, see supported storage types and the
Data Protection Guide for VMs using the SnapCenter Plug-in for VMware vSphere.
Related references
Storage types supported by SnapCenter Plug-ins for Microsoft Windows and for Microsoft SQL
Server on page 21
Supported VMware guest OS platforms
You can use the Plug-in for Windows for LUN provisioning and Snapshot copy management support
on x64 guest operating systems running on supported versions of VMware ESXi.
The Plug-in for Windows supports the following VMware guest OS configurations:
•
Supported versions of Windows Server
•
Microsoft cluster configurations
Support for up to a maximum of 16 nodes supported on VMware when using the Microsoft iSCSI
Software Initiator, or up to two nodes using FC
•
RDM LUNs
Support for a maximum of 56 RDM LUNs with four LSI Logic SCSI controllers for normal
RDMS, or 42 RDM LUNs with three LSI Logic SCSI controllers on a VMware VM MSCS boxto-box Plug-in for Windows configuration
For the latest information about supported versions, see the NetApp Interoperability Matrix.
130 | SnapCenter Software Installation and Setup Guide
NetApp Interoperability Matrix Tool
VMware ESX server-related limitations
The SnapCenter Plug-in for Microsoft Windows is supported on VMware Windows guest. Before
you use the Plug-in for Windows to perform provisioning and Snapshot copy management
operations, you should be aware of some limitations.
•
Installing the Plug-in for Windows on a Microsoft cluster on virtual machines using ESX
credentials is not supported.
You should use your vCenter credentials when installing the Plug-in for Windows on clustered
virtual machines.
•
All clustered nodes must use the same target ID (on the virtual SCSI adapter) for the same
clustered disk.
•
When you create an RDM LUN outside of the Plug-in for Windows, you must restart the plug-in
service to enable it to recognize the newly created disk.
•
You cannot use iSCSI and FC initiators at the same time on a VMware guest OS.
Minimum vCenter privileges required for SnapCenter RDM operations
To perform RDM operations in a guest OS, you must have minimum vCenter privileges.
You must have the following minimum privileges set on the host:
•
Datastore: Remove File
•
Host: Configuration > Storage Partition Configuration
•
Virtual Machine: Configuration
You must assign these privileges to a role at the Virtual Center Server level. The role to which you
assign these privileges cannot be assigned to any user without root privileges.
After you assign these privileges, you can install the Plug-in for Windows on the guest OS.
Using FC RDM LUNs in a Microsoft cluster
You can use the Plug-in for Windows to manage a Microsoft cluster using FC RDM LUNs, but you
must first create the shared RDM quorum and shared storage outside the plug-in, and then add the
disks to the virtual machines in the cluster.
Starting with ESXi 5.5, you can also use ESX iSCSI and FCoE hardware to manage a Microsoft
cluster. The Plug-in for Windows includes out-of-box support for Microsoft clusters.
Requirements for using FC RDM LUNs in a Microsoft cluster
The Plug-in for Windows provides support for Microsoft clusters using FC RDM LUNs on two
different virtual machines that belong to two different ESX servers, also known as cluster access
boxes, when you meet specific configuration requirements.
The following configuration requirements must be met to use FC RDM LUNs on virtual machines in
a Microsoft cluster:
•
The VMs must be running the same Windows Server version.
•
ESX server versions must be the same for each VMware parent host.
•
Each parent host must have at least two network adapters.
•
There must be at least one VMFS datastore shared between the two ESX servers.
Provisioning storage on Windows hosts | 131
•
VMware recommends that the shared datastore be created on an FC SAN.
If necessary, the shared datastore can also be created over iSCSI.
•
The shared RDM LUN must be in physical compatibility mode.
•
The shared RDM LUN must be created manually outside of the Plug-in for Windows.
You cannot use virtual disks for shared storage.
•
A SCSI controller must be configured on each virtual machine in the cluster in physical
compatibility mode:
Windows Server 2008 R2 requires you to configure the LSI Logic SAS SCSI controller on each
virtual machine.
Shared LUNs cannot use the existing LSI Logic SAS controller if only one of its type exists and it
is already attached to the C: drive.
SCSI controllers of type paravirtual are not supported on VMware Microsoft clusters.
Note: When you add a SCSI controller to a shared LUN on a virtual machine in physical
compatibility mode, you must select the Raw Device Mappings option and not the Create a
new disk option in the VMware Infrastructure Client.
•
Microsoft virtual machine clusters cannot be part of a VMware cluster.
•
You must use vCenter credentials and not ESX credentials when you install the Plug-in for
Windows on virtual machines that will belong to a Microsoft cluster.
•
The Plug-in for Windows cannot create a single igroup with initiators from multiple hosts.
The igroup containing the initiators from all ESXi hosts must be created on the storage controller
prior to creating the RDM LUNs that will be used as shared cluster disks.
•
You can create an RDM LUN on ESXi 5.0 using an FC initiator.
When you create an RDM LUN, an initiator group is created with ALUA.
Microsoft cluster support limitations when using FC RDM LUNs
The Plug-in for Windows supports Microsoft clusters using FC RDM LUNs on different virtual
machines belonging to different ESX servers.
Note: This feature is not supported in releases before ESX 5.5i.
•
The Plug-in for Windows does not support clusters on ESX iSCSI and NFS datastores.
•
The Plug-in for Windows does not support mixed initiators in a cluster environment.
Initiators must be either FC or Microsoft iSCSI, but not both.
•
ESX iSCSI initiators and HBAs are not supported on shared disks in a Microsoft cluster.
•
The Plug-in for Windows does not support virtual machine migration with vMotion if the virtual
machine is part of a Microsoft cluster.
•
The Plug-in for Windows does not support MPIO on virtual machines in a Microsoft cluster.
Creating a shared FC RDM LUN
Before you can use FC RDM LUNs to share storage between nodes in a Microsoft cluster, you must
first create the shared quorum disk and shared storage disk, and then add them to both virtual
machines in the cluster.
About this task
The shared disk is not created using the Plug-in for Windows.
132 | SnapCenter Software Installation and Setup Guide
Step
1. Create and then add the shared LUN to each virtual machine in the cluster using the procedure in
the VMware Setup for Failover Clustering and Microsoft Cluster Service documentation.
See the section that describes how to cluster virtual machines across physical hosts.
Troubleshooting RDM LUN creation
If you experience errors creating RDM LUNs, you should be aware of some of the common errors
and workarounds.
Error message
Failed to create disk in virtual machine, Failed to Map virtual disk: File
[datastore] path_name was not found.
Problem
You might encounter this error when you attempt to create an RDM LUN with ESX Software
Initiator on a VM with a name with more than 33 characters.
You have several options to work around this issue.
Workaround 1
Manually create the same directory inside the datastore.
Workaround 2
Rather than selecting your datastore with the Store with Virtual machine option, select the
datastore in which you intend to create the RDM LUN. When you create the RDM LUN, use the
same datastore you just selected.
Workaround 3
Configure the Plug-in for Windows VirtualCenter or ESX Server login settings with the VirtualCenter
credentials.
SnapCenter Plug-in for Microsoft Windows cmdlets
The SnapCenter Plug-in for Microsoft Windows provides PowerShell cmdlets to support host
provisioning and space reclamation jobs. You can use cmdlets directly or add them to scripts.
If you are running the cmdlets on a remote plug-in host, you must run the SnapCenter OpenSMConnection cmdlet to open a connection to the SnapCenter Server:
Open-SmConnection –SMSbaseUrl https://SNAPCENTER_SERVER_NAME.DOMAIN_NAME:
8146 -RoleName “ROLE_NAME”
Where:
•
SNAPCENTER_SERVER_NAME is the server name or IP address of the machine where SnapCenter
is installed.
•
DOMAIN_NAME is the domain (for example, nextgen).
•
8146 is the default SnapCenter HTTPS port.
You can configure this port during the SnapCenter installation process. If you want to modify the
port, you must reinstall SnapCenter and specify a new port number during the new installation.
Provisioning storage on Windows hosts | 133
•
“ROLE_NAME” is the role name for the user assigned with the Admin role (for example, “Snap
Admin”). Role name is required only if the user is a member of multiple roles. Typically, you do
not need to specify this.
Provide the credentials you used to log in to the SnapCenter GUI.
Note: If you are a domain user with local administrator rights, you must run the GrantClusterAccess PowerShell cmdlet before you can run the Plug-in for Windows cmdlets in a
Windows failover cluster.
For detailed information about the Plug-in for Windows cmdlets, including syntax and examples, see
the SnapCenter Software Cmdlet Reference.
SnapCenter Software 3.0.1 Windows Cmdlet Reference Guide
134
Upgrading SnapCenter and SnapCenter plug-in
packages
Each release of SnapCenter contains an updated SnapCenter Server and plug-in package updates.
Plug-in package updates are distributed with the SnapCenter installer. You can configure SnapCenter
to check for available updates. Then, you must install them.
You can upgrade SnapCenter from version 2.0 to version 3.0.
Related concepts
Preparing for the installation on page 21
Configuring SnapCenter to check for available updates
SnapCenter periodically communicates with the NetApp Support Site to notify you of available
software updates. You can also create a schedule to specify the interval in which you want to receive
information about available updates.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Software.
The Available Software page displays the available plug-in packages, versions available, and their
installation status.
3. Click Check for updates to see if any newer versions of plug-in packages are available.
4. Click Schedule Updates to create a schedule to specify the interval in which you want to receive
information about available updates:
a. Select the interval in Check for updates.
b. Select the Windows Run as credential and click OK.
Upgrading SnapCenter and SnapCenter plug-in packages | 135
Supported MySQL upgrade scenarios
SnapCenter 3.0 supports only MySQL Server as the repository (NSM) database. If you are using
Microsoft SQL Server as the repository database with an earlier version of SnapCenter, while
upgrading to SnapCenter 3.0, the repository database is upgraded to MySQL Server.
Before upgrading to SnapCenter 3.0, you must be aware of the supported MySQL upgrade scenarios.
Supported upgrade scenarios
•
SnapCenter 1.1 standalone installation to SnapCenter 3.0 standalone installation with or without
NAS file protection.
•
SnapCenter 1.1 NLB installation to SnapCenter 3.0 NLB installation with or without NAS file
protection.
•
SnapCenter 2.0 standalone installation to SnapCenter 3.0 installation with or without NAS file
protection.
•
SnapCenter 2.0 standalone installation with NAS file protection to SnapCenter 3.0 NLB
installation with NAS file protection.
The SnapCenter 3.0 NLB installation supports MySQL high-availability.
•
SnapCenter 2.0 NLB installation to SnapCenter 3.0 NLB installation with or without NAS file
protection.
•
SnapCenter 2.0 NLB installation with NAS file protection to SnapCenter 3.0 NLB installation
with NAS file protection.
Related information
Performing administrative tasks with SnapCenter
SnapCenter upgrade limitations
Before upgrading to SnapCenter 3.0, you must be aware of certain limitations.
•
Upgrading from SnapCenter 1.0 to SnapCenter 3.0 is not supported.
You must upgrade from SnapCenter 1.0 to SnapCenter 1.1, and then upgrade to SnapCenter 3.0.
•
Upgrading the repository database from Microsoft SQL Server to MySQL Server can be
performed only while upgrading SnapCenter Server to version 3.0.
•
After successfully upgrading the repository database, reverting to Microsoft SQL Server is not
supported.
•
After successfully upgrading the repository database, protection of the repository database is
disabled, and all of the schedules that are related to repository operations are deleted.
You must run the Protect-SmRepository command to protect the repository database and to
create new schedules. You do not have to rerun the protection of repository database for the
following upgrade paths:
◦
SnapCenter 2.0 with MySQL Server and without NAS file protection to SnapCenter 3.0
without NAS file protection
◦
SnapCenter 2.0 with MySQL Server and with NAS file protection to SnapCenter 3.0 with
NAS file protection
136 | SnapCenter Software Installation and Setup Guide
Upgrading the SnapCenter Server
To upgrade the SnapCenter Server host, you must have the SnapCenter Server installation package on
the server where SnapCenter is installed. You can download the installation package directly from the
NetApp Support Site. If the server where SnapCenter is installed is in a secure environment, you can
download the installation package in a non-secure environment, then copy it to the server in the
secure environment.
Before you begin
•
If you are not using Network Load Balancing (NLB), you should place resource groups or the
hosts or both in maintenance mode prior to the upgrade so that scheduled backups do not occur
and you avoid creating failed backups.
If you are using NLB, you do not need to place resource groups or the host in maintenance mode.
If you are using NLB, you should have the same version of SnapCenter on all NLB nodes.
•
You must have backed up the SnapCenter repository (also called the NSM database).
The SnapCenter Software Administration Guide contains details.
•
If you are upgrading from SnapCenter 1.1 to a later version of SnapCenter, you must have
installed .NET 4.5.2 or later on all Windows hosts.
•
The disk where the SnapCenter repository (NSM) database resides must have sufficient space.
Steps
1. Download the SnapCenter upgrade package from the NetApp Support Site at
mysupport.netapp.com.
2. Place all hosts with plug-ins in maintenance mode:
a. In the left navigation pane, select Hosts, and in the Managed Hosts list, select the host that
you want to upgrade.
b. In the Information pane, select the host and its plug-in, and then click Suspend Schedule.
c. Repeat the substeps for each host.
Attention: You must place each host in maintenance mode before continuing this task.
3. Run the downloaded .exe file to launch the SnapCenter upgrade wizard.
In the Prerequisites Validation screen, the host is validated to see if it meets the requirements to
install the SnapCenter Server.
The Microsoft .NET version and RAM are validated against the minimum requirements. If the
minimum requirements are not met, appropriate error or warning messages are displayed. If the
restart of the host is pending, a warning message is displayed.
4. Enable and configure Network Load Balancing (NLB) on the host by either creating a new NLB
cluster or joining an existing NLB cluster.
Note: Upgrading from a SnapCenter stand-alone installation to SnapCenter NLB installation is
not supported.
You must run the SnapCenter Server upgrade package on the second node of the NLB setup only
after successfully upgrading the SnapCenter Server on the first node. You must never try
upgrading SnapCenter on both of the nodes simultaneously.
Note: While upgrading the first node, you cannot access the SnapCenter UI from the second
node. If the upgrade fails on the first node, you still cannot access the SnapCenter UI from the
Upgrading SnapCenter and SnapCenter plug-in packages | 137
second node. After you fix the upgrade issue and finish upgrading SnapCenter on both of the
nodes, you can start accessing the SnapCenter UI.
5. Manually install and enable Application Request Routing (ARR) for SnapCenter.
6. Enter the credentials that you want to use to log in to SnapCenter as the administrator.
7. Enter the MySQL database password.
If you specified a custom port during SnapCenter 3.0 installation, during upgrade the custom port
is changed to the default port.
From SnapCenter 3.0.1, the MySQL database password cannot contain the following characters:
[ ], ", ', `, ^, %, &, <, >, (, ), |, /, \, ;, =, #, comma, space, New-line, and Tab. If you are upgrading
to SnapCenter 3.0.1 and the password contains any of the restricted characters, you should
provide a new password.
8. Click Upgrade.
9. After the upgrade is successful, log in to SnapCenter and then, on the left navigation pane, click
Hosts > Activate Schedule to bring the host out of maintenance mode so that operations can
resume.
After you finish
•
You must perform a fresh discovery of resources on the hosts.
•
If you have upgraded from SnapCenter 1.1, you will see a difference in the number of clones that
are displayed on the Dashboard.
The difference in the number of clones is because each 1.1 clone dataset associated with one or
more policies are converted as individual clone jobs. For example, if in 1.1 you had one clone
dataset associated with two policies, after upgrading it will be converted to two clone jobs.
•
If you have upgraded from SnapCenter 1.1, the clones on the secondary (mirror or vault) are not
displayed under Mirror copies or Vault copies in the Topology page.
All of the clones created using SnapCenter 1.1 are displayed under the Local copies in
SnapCenter 3.0.
•
After successfully upgrading and migrating the repository database to MySQL Server, you can
manually delete the older database if you are running out of space.
After migrating the data, the older database is not deleted automatically. If the older repository
database was on the SnapCenter host, you might see the disk space issue as both the older and the
upgraded repository exists on the SnapCenter host.
•
If the upgrade fails, you can restore the NSM database to it's previous state and you can continue
using the earlier version of SnapCenter without losing any data.
•
After upgrading the SnapCenter Server host, you must also upgrade the plug-ins before adding
any storage system.
Related concepts
Network Load Balancing and Application Request Routing options for high availability on page 30
Related references
Supported MySQL upgrade scenarios on page 135
Related information
Performing administrative tasks with SnapCenter
138 | SnapCenter Software Installation and Setup Guide
Upgrading your plug-in packages
The plug-in packages are distributed as part of the SnapCenter upgrade.
Before you begin
You must be running SnapCenter Server 3.0 before you can upgrade plug-in hosts.
About this task
•
You can only upgrade one host at a time.
Note: If your hosts are in a Microsoft cluster, you can upgrade the SQL and Windows plug-ins
on all the hosts in the cluster at one time.
•
Maintenance mode
The upgrade procedure places your Windows or Linux host in maintenance mode, which prevents
the host from running any scheduled jobs.
For details about upgrading SnapCenter Plug-in for VMware vSphere, see the information about
SnapCenter Plug-in for VMware vSphere.
Steps
1. In the left navigation pane, click Hosts.
2. Verify that Managed Hosts is selected at the top.
3. Select the host for which you want to upgrade the plug-in package.
4. In the Information section, click Suspend Schedule to place the host for this plug-in in
maintenance mode.
5. Click Modify in the toolbar.
6. In the Modify page, select Upgrade plug-ins.
Note: All the plug-ins in the package gets selected but only the plug-ins that were installed
with the earlier version of SnapCenter are upgraded and the remaining plug-ins are not
installed. You must use the Add plug-ins option to install any new plug-in.
Note: If you have the Windows plug-ins 1.1 package installed on the SnapCenter 1.1 host
(Windows host), while upgrading the plug-ins to 3.0, the Add plug-ins option is selected by
default and the Upgrade plug-ins option is disabled. You can successfully upgrade the plug-ins
by selecting the Add plug-ins option.
You cannot select a custom location if you are upgrading the SnapCenter Plug-in for Oracle
Database from an earlier version to 3.0.
7. Select Skip prechecks if you do not want to validate whether the host meets the requirements to
upgrade the plug-in.
8. Select the plug-in package you want to upgrade to and then click OK.
Note: After upgrading SnapCenter Plug-in for Microsoft SQL Server, you must refresh the
resources to view the Availability Group type and you must also provide new values for Repeat
every option for monthly schedules because the values of Repeat every option are not
retained.
9. Click Next.
Upgrading SnapCenter and SnapCenter plug-in packages | 139
If you have not selected the Skip prechecks check box, the host is validated to see if it meets the
requirements to install the plug-in. The disk space, RAM, PowerShell version, .NET version,
location (for Windows plug-ins), and Java version (for Linux plug-ins) are validated against the
minimum requirements. If the minimum requirements are not met, appropriate error or warning
messages are displayed. After fixing the issue, click Validate to re-validate the requirements.
Note: If the error is related to disk space or RAM, you can either update the web.config
located at C:\Program Files\NetApp\SnapCenter WebApp or PowerShell config files
located at C:\Windows\System32\WindowsPowerShell\v1.0\Modules\SnapCenter\
to modify the default values. If the error is related to remaining parameters you must fix the
issue and then validate the requirements again.
10. Review the summary, and then click Finish.
After you finish
After the plug-in package is upgraded, bring the host out of maintenance mode by clicking Activate
Schedule.
Related tasks
Upgrading SnapCenter Plug-in for VMware vSphere on page 100
140
Uninstalling SnapCenter plug-ins and plug-in
packages
You can remove hosts and uninstall individual plug-ins or plug-in packages using the SnapCenter
GUI. You can also uninstall individual plug-ins or plug-in packages on remote hosts using the
command-line interface (CLI) on your SnapCenter Server host or using the Windows Uninstall a
program option locally on any host.
Uninstalling plug-ins from a host using the SnapCenter GUI
When you decide that you no longer require an individual plug-in or a plug-in package, you can
uninstall it using the SnapCenter interface.
Before you begin
•
You must have removed the resource groups for the plug-in package that you are uninstalling.
•
You must have detached the policies associated with the resource groups for the plug-in package
that you are uninstalling.
About this task
You can uninstall an individual plug-in. For example, you might need to uninstall the SnapCenter
Plug-in for VMware vSphere because a host is running out of resources and you want to move that
plug-in to a more powerful host. You can also uninstall an entire plug-in package. For example, you
might need to uninstall the SnapCenter Plug-ins Package for Linux, which includes SnapCenter Plugin for Oracle Database and SnapCenter Plug-in for UNIX.
•
Removing a host includes uninstalling all plug-ins
When you remove a host from SnapCenter, SnapCenter uninstalls all the plug-in packages on the
host before removing the host.
•
SnapCenter GUI removes plug-ins from one host at a time
When you use the SnapCenter GUI, you can uninstall plug-ins on only one host at a time.
However, you can have several uninstall operations running at the same time.
You can also uninstall a plug-in from multiple hosts by using the command-line interface (CLI).
•
When you uninstall SnapCenter Plug-in for VMware vSphere, the plug-in is also unregistered
with vCenter.
Attention: Uninstalling the SnapCenter Plug-ins Package for Windows from a host on which the
SnapCenter Server is installed will damage the SnapCenter Server installation. Do not uninstall the
SnapCenter Plug-ins Package for Windows unless you are certain that you no longer require the
SnapCenter Server.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Managed Hosts.
3. In the Managed Hosts page, select the host from which you want to uninstall the plug-in or plugin package.
4. Click Modify.
Uninstalling SnapCenter plug-ins and plug-in packages | 141
5. In the Modify Host page, select Remove plug-ins.
6. In the Plug-ins page, do the following:
•
If you are uninstalling a single plug-in, do not make any selection on this page.
•
If you are uninstalling a plug-in package, select the package you want to uninstall.
7. In the Summary page, review your selections and then click Finish.
After you finish
After you uninstall a plug-in, you must wait for 5 minutes before you reinstall the plug-in on that
host. This time period is sufficient for the SnapCenter GUI to refresh the status of the managed host.
The installation fails if you immediately reinstall the plug-in.
If you are uninstalling SnapCenter Plug-ins Package for Linux, uninstallation-specific log files are
available at: /custom_location/snapcenter/logs.
Uninstalling Windows plug-ins using the command-line
interface on the SnapCenter Server host
You can uninstall individual plug-ins or uninstall plug-ins packages from one or more hosts by using
the Uninstall-SmHostPackage cmdlet on the SnapCenter Server host command-line interface.
Before you begin
You must have logged in to SnapCenter as a domain user with local administrator rights on each host
on which you want to uninstall the plug-ins.
Steps
1. Launch the PowerShell application.
2. From the SnapCenter Server command prompt, enter:
Open-SMConnection -SMSbaseUrl https://SNAPCENTER_SERVER_NAME/DOMAIN_NAME
3. From the command prompt, enter:
Uninstall-SmHostPackage -HostNames hostname1[,hostname2...] ApplicationCode plugincode
•
You can specify one or more host names, separated by commas.
•
If you do not specify a host name, a prompt is displayed for you to list the host names.
•
If you do not specify an application (plug-in) code, SnapCenter uninstalls all SnapCenter
plug-ins on the host by default. Valid ApplicationCode values are as follows:
SCSQL
SnapCenter Plug-ins Package for Windows
SCO
SnapCenter Plug-ins Package for Linux
SCV
SnapCenter Plug-in for VMware vSphere
Name of the custom plug-in
SnapCenter Custom Plug-ins
Example
The following command uninstalls SnapCenter Plug-in for VMware vSphere from the specified
host.
142 | SnapCenter Software Installation and Setup Guide
Uninstall-SmHostPackage -HostNames lab-esx90.test1.com
-ApplicationCode SCV
Example
The following command uninstalls SnapCenter Custom Plug-ins from the specified host.
Uninstall-SmHostPackage -HostNames lab-esx90.test1.com
-ApplicationCode HRPlug-in
Where, HRPlug-in is the name of the custom plug-in.
Uninstalling plug-ins locally on a host
You can uninstall SnapCenter plug-ins locally on a host if you cannot reach the host from the
SnapCenter Server.
About this task
The best practice for uninstalling individual plug-ins or plug-in packages is to either use the
SnapCenter GUI or use the Uninstall-SmHostPackage cmdlet on the SnapCenter Server host
command-line interface. These procedures help the SnapCenter Server to stay up to date with any
changes. However, you might have a rare need to uninstall plug-ins locally. For example, you might
have run an uninstall job from the SnapCenter Server but the job failed, or you uninstalled your
SnapCenter Server and orphan plug-ins remain on a host.
Attention: Uninstalling a plug-in package locally on a host does not delete data associated with the
host; for example scheduled jobs and backup metadata.
Steps
1. On the host system, navigate to the Control Panel and click Uninstall a program.
2. In the list of programs, select the SnapCenter plug-in or plug-in package you want to uninstall
and click Uninstall.
Windows uninstalls all plug-ins in the selected package.
Uninstalling SnapCenter Plug-ins Package for Linux using
the command-line interface
You should uninstall SnapCenter Plug-ins Package for Linux by using the SnapCenter user interface.
However, if you cannot uninstall it for some reason, you can uninstall SnapCenter Plug-ins Package
for Linux using the command-line interface.
Before you begin
You must have deleted the scheduled jobs and running jobs must have been completed.
Step
1. Enter the following command:
/custom_location/NetApp/snapcenter/spl/installation/plugins/uninstall
Uninstalling SnapCenter plug-ins and plug-in packages | 143
Removing a host from SnapCenter Server
You can remove a host if you no longer want to use SnapCenter to manage its data protection jobs.
For example, you might want to remove a host if it no longer has data that needs to be protected.
Prerequisites to remove a host
Before you remove a host from SnapCenter Server, the administrator must perform the prerequisite
tasks.
•
If you are using SnapCenter Custom Plug-ins, you must have deleted all clones associated with
the host from SnapCenter.
•
You must ensure that the discovery jobs are not running on the host.
Prerequisites to remove a host using role-based access control
•
You must have created an RBAC role with read, delete host, installation, uninstallation of plug-in,
and delete objects permission.
Objects can be clone, backup, resource group, storage system, and so on.
•
You must have added the RBAC user to the RBAC role.
•
You must have assigned the RBAC user to the host, plug-in, Run As, resource groups, and storage
system (for clones) that you want to delete.
•
You must have logged in SnapCenter as an RBAC user.
Prerequisites to remove a host with clones created from clone lifecycle operation
•
You must have created clone jobs using clone lifecycle management for SQL databases.
•
You must have created an RBAC role with clone read and delete, resource read and delete,
resource group read and delete, storage read and delete, provision read and delete, mount,
unmount, plug-in installation and uninstallation, host read and delete permissions.
•
You must have assigned the RBAC user to the RBAC role.
•
You must have assigned the RBAC user to the host, SnapCenter Plug-in for Microsoft SQL
Server, run as, clone lifecycle resource group, and storage system.
•
You must have logged in SnapCenter as an RBAC user.
Removing a host
When the SnapCenter Server removes a host, it first removes the backup, clones, clones jobs,
resource groups, and resources listed for that host in the SnapCenter Resources page and then the
plug-in packages installed on the host are uninstalled.
About this task
•
If you have the permission to delete a host and you delete the host, the backups, clones, and
resource groups associated with the host are also deleted.
•
When you remove the resource groups, all the associated schedules are also removed.
•
If the host has a resource group that is shared with another host and you delete the host, then the
resource group is also deleted.
144 | SnapCenter Software Installation and Setup Guide
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Managed Hosts.
3. Select the host you want to remove, and then click Remove.
4. For Oracle RAC clusters, to remove SnapCenter software from all the hosts in the cluster, select
Include all the hosts of cluster.
5. In the Remove host page, perform the following actions:
a. Select Delete the backups and/or clones for the resources associated with this host if you
want to remove the host that is associated with backups or clones.
b. Select Include deletion of cloned resources that are cloned/mounted to alternate host to
delete all resources cloned to an alternate host.
6. Click OK to continue.
Uninstalling SnapCenter
If you no longer wish to use SnapCenter to manage data protection jobs, you can uninstall
SnapCenter using the Programs and Features Control Panel on your SnapCenter Server host system.
Uninstalling SnapCenter removes the Network Load Balancing (NLB) cluster, the Application
Request Routing server farm, and, if appropriate, the SnapCenter database.
About this task
The domain in which the SnapCenter host is located must remain unchanged. If you remove
SnapCenter Server from the domain it was in when SnapCenter Server was installed and then try to
uninstall SnapCenter Server, the uninstall operation fails.
Steps
1. On your SnapCenter host system, navigate to the Control Panel.
2. Make sure you are in the Category view.
3. Under Programs, click Uninstall a program.
Programs and Features opens.
4. Select NetApp SnapCenter Server and click Uninstall.
5. Select to remove the NLB node from the NLB cluster and the Application Request Routing server
farm.
6. If you do not want to use this SnapCenter repository with a newly installed SnapCenter Server,
select to remove the SnapCenter repository. In NLB configurations, you can only delete the
repository from the last NLB node.
After you finish
•
Removing the NLB node from an NLB cluster requires that you restart your SnapCenter Server
host system. If you do not restart the host system, you might experience a failure if you attempt to
reinstall SnapCenter Server.
Uninstalling SnapCenter plug-ins and plug-in packages | 145
•
Some non-NetApp components installed by SnapCenter are not removed during uninstallation,
including SnapCenter repository server and .NET Framework. If you want to remove these
components, you must uninstall them manually.
If you want to uninstall SQL Server Express (if you are uninstalling an earlier version of
SnapCenter), first delete the SnapCenter repository, then uninstall SQL Express by selecting
Microsoft SQL Server 2012 (64-bit).
146
Installing plug-ins independently
It is a best practice to install the plug-ins remotely from the SnapCenter user interface. If for some
reason you cannot install a plug-in remotely, you can use the independent plug-in installation
package to install the plug-in locally.
The independent plug-in installation packages are available for the following plug-ins:
•
SnapCenter Plug-in for Microsoft Windows
•
SnapCenter Plug-in for Microsoft SQL Server
•
SnapCenter Plug-in for Oracle Database
•
SnapCenter Plug-in for VMware vSphere
•
SnapCenter Plug-in for SAP HANA Databaseon the Linux host
Note: The independent installation of SnapCenter Custom Plug-ins is not supported.
Installing the SnapCenter Plug-in for Microsoft Windows
independently
You can install the SnapCenter Plug-in for Microsoft Windows locally on a Windows host if you are
unable to install the plug-in remotely from the SnapCenter user interface.
Preparation to install the SnapCenter Plug-in for Microsoft Windows
The Windows host on which you install the SnapCenter Plug-in for Microsoft Windows must meet
the specified software, browser, and operating system requirements.
Before you begin
•
•
•
•
•
If installed, you must have stopped the Windows Host utilities and provisioning and protection
capabilities of the OnCommand Unified Manager Core Package.
You must have installed Microsoft .Net 4.5.2 or later.
You must have installed PowerShell 4.0 or later.
You must have turned on Windows message queuing.
You must be a local administrator on the host.
About this task
Installing the plug-in remotely using the SnapCenter user interface is the preferred method. You
should install the plug-in locally only if you are unable to install it remotely from SnapCenter.
Installing the SnapCenter Plug-in for Microsoft Windows silently from the
command line
You can install the SnapCenter Plug-in for Microsoft Windows locally on a Windows host if you are
unable to install the plug-in remotely from SnapCenter. You can run the SnapCenter Plug-in for
Installing plug-ins independently | 147
Microsoft Windows installation program unattended, in silent mode, from the Windows command
line.
Steps
1. Download the SnapCenter Plug-in for Microsoft Windows from your install location. For
example, the default install path is C:\ProgramData\NetApp\SnapCenter\Package
Repository.
This path is accessible from the host where the SnapCenter Server is installed.
2. Copy the installation file to the host on which you want to install the plug-in.
3. From the command prompt, navigate to the directory where you downloaded the installation file.
4. Enter the following command, replacing variables with your data:
"SnapCenter Plug-in for Microsoft Windows.exe" /silent /debuglog
"DirPath\LogFileName" ISFeatureInstall="SCW"
BI_SDW_NG_DEST="InstallDirectory" BI_SERVICEACCOUNT=Domain\UserName
BI_SERVICEPWD=Password BI_WEBSERVICE_PORT=808
PREFERRED_STORAGE_SYSTEM_NAME=PreferredSystemName LICENSE_TYPE_SERVER=1
LPSM_SERIALNUMBER="LicenseKey"
Enter the following for each variable:
Variable
Description
DirPath\LogFileName
The location and name of the installation log file
InstallDirectory
The directory where you want to install the plug-in
Domain\UserName
The user account that Windows uses to run the plug-in
This account must have the domain user with local administrator
permissions on the Windows host.
Password
The password for the specified account
PreferredSystemName
The storage system name that the plug-in should use for management
traffic
LicenseKey
The per-server license key
Leave this field blank if you are using per-storage system licensing.
Example
"C:\ProgramData\NetApp\SnapCenter\Package Repository
\snapcenter_windows_host_plugin.exe"
/silent
/debuglog"C:\HPPW_SCSQL_Install.log"
/log"C:\"
BI_SNAPCENTER_PORT=8145
SUITE_INSTALLDIR="C:\Program Files\NetApp\SnapCenter WebApp"
BI_SERVICEACCOUNT=domain\administrator
BI_SERVICEPWD=password
ISFeatureInstall=SCW
The debuglog parameter includes the path of the log file for SnapCenter. Writing to this log file
is the preferred method of obtaining troubleshooting information, because the file contains the
results of checks that the installation performs for plug-in prerequisites.
148 | SnapCenter Software Installation and Setup Guide
If necessary, you can find additional troubleshooting information in the log file for the
SnapCenter for Windows package. Log files for the package are listed (oldest first) in the %Temp%
folder, for example, C:\temp\.
Installing SnapCenter Plug-in for Microsoft SQL Server
independently
You can install the SnapCenter Plug-in for Microsoft SQL Server locally if you are unable to install
the plug-in from the SnapCenter user interface.
Preparation to install the SnapCenter Plug-in for Microsoft SQL Server
The SnapCenter Plug-in for Microsoft SQL Server installer consists of third-party and NetApp
packages. You can also upgrade, repair, or remove the packages using the installer.
Third-party packages
Following are the third-party packages:
•
Microsoft Visual C++ 2012 Redistributable Package (x86)
This installs runtime components that are required to run C++ applications built with Visual
Studio 2012.
•
Microsoft SQL Server 2016 CLR Types (x64)
This is part of the Microsoft SQL Server Feature Pack but also is a stand-alone software that can
be installed separately. The SQL Server System CLR Types package contains the components
implementing the new geometry, geography, and hierarchy ID types in SQL Server 2016. You can
install this component separately from the server to allow client applications to use these types
outside of the server.
•
Microsoft SQL Server 2016 Management Objects (x64)
This is a collection of objects that are designed for programming all aspects of managing
Microsoft SQL Server. This object model works with SQL Server 2005, SQL Server 2008, SQL
Server 2008 R2, SQL Server 2012, SQL Server 2014, and SQL Server 2016. It is included in all
SQL Server editions, including the Express Edition and requires Microsoft SQL Server System
CLR Types.
•
Microsoft SQL Server 2016 CLR types (x64)
The SnapCenter Plug-in for Microsoft SQL Server requires all these packages to perform backup,
restore, and recovery operations for SQL databases running on NetApp storage systems.
Prerequisites
The following must have already been installed:
•
SnapCenter Plug-in for Microsoft Windows on the same host where SnapCenter Plug-in for
Microsoft SQL Server is installed
SnapCenter Server must be installed on a separate host.
•
Windows PowerShell v4.0 for Windows Server 2008 R2 SP1
•
Microsoft .Net Framework v4.5.2 or later
•
Microsoft Hotfixes
Installing plug-ins independently | 149
Installing the SnapCenter Plug-in for Microsoft SQL Server silently from the
command line
You should install SnapCenter Plug-in for Microsoft SQL Server from within the SnapCenter user
interface. However, if you cannot for some reason, you can run the SnapCenter Plug-in for Microsoft
SQL Server installation program unattended in silent mode from the Windows command line.
Before you begin
•
You must have backed up your SQL databases.
•
SnapCenter plug-in packages must be installed.
Steps
1. Download the SnapCenter Plug-in for Microsoft Windows from C:\ProgramData\NetApp
\SnapCenter\Package Repository.
This path is accessible from the host where the SnapCenter Server is installed.
2. Copy the installation file to the host on which you want to install the plug-in.
3. From a Windows command prompt on the local host, navigate to the directory to which you saved
the plug-in installation files.
4. Enter the following command to install replacing the variables with your data:
"snapcenter_windows_host_plugin.exe"/silent /
debuglog"<Debug_Log_Path>" /log"<Log_Path>" BI_SNAPCENTER_PORT=<Num>
SUITE_INSTALLDIR="<Install_Directory_Path>" BI_SERVICEACCOUNT=<domain
\administrator> BI_SERVICEPWD=<password> ISFeatureInstall=SCW,SCSQL
For example,
"C:\ProgramData\NetApp\SnapCenter\Package Repository
\snapcenter_windows_host_plugin.exe"/silent /debuglog"C:
\HPPW_SCSQL_Install.log" /log"C:\" BI_SNAPCENTER_PORT=8145
SUITE_INSTALLDIR="C: \Program Files\NetApp\SnapCenter"
BI_SERVICEACCOUNT=domain\administrator BI_SERVICEPWD=password
ISFeatureInstall=SCW,SCSQL
Enter the following values for the variables:
Variable
Value
/
debuglog"<Debug_Log_
Path>
Specify the name and location of the suite installer log file, as in the
following example: Setup.exe /debuglog"C:\PathToLog
\setupexe.log".
BI_SNAPCENTER_PORT
Specify the port on which SnapCenter communicates with SMCore.
SUITE_INSTALLDIR
Specify host plug-in package installation directory.
BI_SERVICEACCOUNT
Specify SnapCenter Plug-in for Microsoft Windows web service account.
BI_SERVICEPWD
Specify the password for SnapCenter Plug-in for Microsoft Windows
web service account.
ISFeatureInstall
Specify the solution to be deployed by SnapCenter on remote host.
150 | SnapCenter Software Installation and Setup Guide
Installing SnapCenter Plug-in for Oracle Database
independently
You can install the SnapCenter Plug-in for Oracle Database locally on the Linux host if you are
unable to install the plug-in from the SnapCenter user interface. You can use an interactive wizard or
the command-line interface to install the plug-in.
The Plug-in for Oracle Database must be installed on each Linux host where the Oracle database
resides.
Preparation to install the SnapCenter Plug-in for Oracle Database
The Linux host on which you are installing the SnapCenter Plug-in for Oracle Database must meet
the specified software, browser, database, and operating system requirements.
For latest information about the supported configurations, see the Interoperability Matrix Tool.
Before you install SnapCenter Plug-ins Package for Linux, you must have already installed
SnapCenter 2.0 on a Windows host and copied the SnapCenter Plug-ins Package for Linux to the
target host.
Related information
NetApp Interoperability Matrix Tool
Installing the SnapCenter Plug-in for Oracle Database interactively
You should install SnapCenter Plug-in for Oracle Database from within the SnapCenter user
interface. However, if you cannot for some reason, you can use the installation wizard to install
SnapCenter Plug-in for Oracle Database interactively on a Linux host.
Before you begin
•
You must have reviewed the prerequisites for installing Plug-in for Oracle Database.
•
You must set the DISPLAY environment variable to specify the IP address and port number of the
Linux host where you want to launch the wizard.
Steps
1. Download the Plug-in for Oracle Database installer from your install location. For example, the
default install path is C:\ProgramData\NetApp\SnapCenter\Package Repository.
This path is accessible from the host where the SnapCenter Server is installed.
2. Copy the installation file to the host on which you want to install the plug-in.
3. From the command prompt, navigate to the directory where you downloaded the installation file.
4. Enter the following command to run the executable file:
./SnapCenter_linux_host_plugin.bin –i swing
5. Follow the on-screen prompts in the wizard to install the SnapCenter Plug-in for Oracle Database.
6. Click Finish to complete the installation.
Installing plug-ins independently | 151
Installing the SnapCenter Plug-in for Oracle Database using command-line
interface
You should install SnapCenter Plug-in for Oracle Database from within the SnapCenter user
interface. However, if you cannot for some reason, you can install the SnapCenter Plug-in for Oracle
Database either in console mode or in silent mode using command-line interface.
Before you begin
•
You must have reviewed the prerequisites for installing Plug-in for Oracle Database.
•
You must ensure that the DISPLAY environment variable is not set.
About this task
The console mode installation requires you to provide the required installation information while
installing Plug-in for Oracle Database.
The silent mode installation does not require you to provide installation information while installing
Plug-in for Oracle Database.
Steps
1. Download the Plug-in for Oracle Database from C:\ProgramData\NetApp\SnapCenter
\Package Repository.
This path is accessible from the host where the SnapCenter Server is installed.
2. From the command prompt, navigate to the directory where you downloaded the installation file.
3. Perform the following steps to install Plug-in for Oracle Database in console mode:
a. Enter the following command to run the executable file:
./SnapCenter_linux_host_plugin.bin –i console
b. Follow the on-screen prompts to complete the installation.
4. Enter the following command to install in silent mode:
./SnapCenter_linux_host_plugin.bin -i silent -DPORT -DSERVER_IP DSERVER_PORT -DUSER_INSTALL_DIR=/opt/custom_path
Installing SnapCenter Plug-in for SAP HANA Database
independently on the Linux host
You can install the SnapCenter Plug-in for SAP HANA Database directly on the Linux host if your
environment does not allow remote installation of the plug-in from the SnapCenter Server. You can
use an interactive wizard or the command-line interface to install the plug-in.
The Plug-in for SAP HANA Database must be installed on each of the Linux host where the
HDBSQL client resides.
152 | SnapCenter Software Installation and Setup Guide
Preparation for installing the SnapCenter Plug-in for SAP HANA Database
on the Linux host
The Linux host on which you are installing the SnapCenter Plug-in for SAP HANA Database must
meet the dependent software, database, and operating system requirements.
The Interoperability Matrix Tool (IMT) contains the latest information about the supported
configurations.
The SnapCenter Plug-in for SAP HANA Database is part of SnapCenter Plug-ins Package for Linux.
Before you install SnapCenter Plug-ins Package for Linux, you must have already installed
SnapCenter 3.0.1 on a Windows host.
Related information
NetApp Interoperability Matrix Tool
Installing the SnapCenter Plug-in for SAP HANA Database on the Linux
host using the command-line interface
You should install SnapCenter Plug-in for SAP HANA Database from within the SnapCenter user
interface. However, if your environment does not allow remote installation of the plug-in from the
SnapCenter Server, you can install the Plug-in for SAP HANA Database either in console mode or in
silent mode using the command-line interface.
Steps
1. Copy the SnapCenter Plug-ins Package for Linux installation file
snapcenter_linux_host_plugin.bin from C:\ProgramData\NetApp\SnapCenter
\Package Repository to the host where the Plug-in for SAP HANA Database will be
installed.
You can access this path from the host where the SnapCenter Server is installed.
2. From the command prompt, navigate to the directory where you copied the installation file.
3. Install the plug-in:
path_to_installation_bin_file/snapcenter_linux_host_plugin.bin -i silent
-DPORT=port_number_for_host -DSERVER_IP=server_name_or_ip_address DSERVER_HTTPS_PORT=port_number_for_server
•
-DPORT specifies the SMCore HTTPS communication port.
•
-DSERVER_IP specifies the SnapCenter Server IP address.
•
-DSERVER_HTTPS_PORT specifies the SnapCenter Server HTTPS port.
•
-DUSER_INSTALL_DIR specifies the directory where you want to install the SnapCenter
Plug-ins Package for Linux.
•
DINSTALL_LOG_NAME specifies the name of the log file.
Example
tmp/sc-plugin-installer/snapcenter_linux_host_plugin.bin -i silent DPORT=8145 -DSERVER_IP=scserver.domain.com -DSERVER_HTTPS_PORT=8146 DUSER_INSTALL_DIR=/opt DINSTALL_LOG_NAME=SnapCenter_Linux_Host_Plugin_Install_2.log DCHOSEN_FEATURE_LIST=CUSTOM
153
Troubleshooting
If you encounter unexpected behavior or failure while installing SnapCenter Server, you can use the
installation log files to identify the cause and resolve the issue.
SnapCenter installation fails to create DB with the error
Invalid username/password, please try again
Description
After uninstalling SnapCenter and initiating a fresh installation, the installation fails because a hidden
MySQL folder exists.
Error message
The SnapCenter installer displays the following message: Invalid username/password,
please try again, and the installation log displays the message
CreateDB: Invalid username/password, please try again
CreateDB: ERROR exception: Access denied for user
Corrective action
1. Find and remove the MySQL folder from C:\ProgramData.
2. Run the SnapCenter installer again.
Enabling AutoSupport email notifications
You can enable AutoSupport email notifications on your storage system so that AutoSupport
messages are sent to a specified storage system user. AutoSupport messages can alert you to issues
such as failed backups.
About this task
Only a cluster administrator can perform AutoSupport management. The Storage Virtual Machine
(SVM) administrator has no access to AutoSupport.
To have email notifications sent from all storage systems to which SnapCenter has access, a cluster
administrator must enable AutoSupport on each storage system node.
Step
1. Enable AutoSupport email notifications from the storage system command line:
autosupport trigger modify -node nodename -autosupport-message
client.app.info enable -noteto enable
154 | SnapCenter Software Installation and Setup Guide
Unable to create SSL or TLS secure channel
Description
If you are using Windows 2016 for the SnapCenter Server host and a version of Java that is earlier
than version 1.8 on the plug-in host, you cannot install plug-ins from the SnapCenter GUI. Even if
you install the plug-ins manually while adding the host using the GUI, the installed plug-ins are not
discovered. This issue occurs because a Secure Sockets Layer (SSL) secure channel or Transport
Layer Security (TLS) secure channel could not be created.
Error message
The request was aborted: Could not create SSL or TLS secure channel.
Corrective action
You must install Java 1.8, 64-bit.
SnapCenter Plug-in Package for Microsoft Windows or
SnapCenter Plug-in for Microsoft SQL Server upgrade might
fail on hosts with SQL databases on VMDK
Description
When upgrading SnapCenter Plug-in for Microsoft Windows or SnapCenter Plug-in for Microsoft
SQL Server on hosts with SQL databases on VMDK, the upgrade might fail.
Error message
The installation log displays the error Engine: error 80070002 while running parcel
operations .
Workaround
Delete the following directories on the plug-in host:
•
C:\Windows\SnapCenter plugin"
•
All files and directories in C:\Users\Administrator.domain_name\AppData\Local
\Downloaded Installations
If the upgrade does not succeed after you delete the specified files and directories, you might need to
reboot the SQL server host, and then delete the files and directories.
HTTP error 503. The service is unavailable.
Description
Launching SnapCenter from a browser or opening a connection from the CLI might fail after
installation if Windows Process Activation Service (WAS) is not enabled.
Troubleshooting | 155
Corrective action
Verify in Windows Server Manager that Windows Process Activation Service is enabled.
Unable to display SnapCenter web login page on local host
Description
When using Internet Explorer with Protected Mode enabled, the SnapCenter login page does not
display when logging in to the local SnapCenter host as a user from another trusted domain.
Corrective action
Disable Protected Mode in Internet Explorer.
SnapCenter Plug-ins Package for Linux installation fails due
to an incorrect Java version
Description
SnapCenter Plug-ins Package for Linux installation might fail if the Java Virtual Machine (JVM) is
not found or if the JVM version required for the installation of SnapCenter Plug-ins Package for
Linux is not available.
Corrective action
1. Add the Java executable path to the PATH environmental variable.
2. Add the environment variable JAVA_HOME to the .bashrc file for the root user.
For example, JAVA_HOME=/usr/java/jre1.8.0_60
3. Verify the Java version by running the following command:
#ssh root@host_name java -version
SnapCenter Plug-ins Package for Linux installation fails due
to improper uninstallation
Description
The SnapCenter Plug-ins Package for Linux installation might fail if the uninstallation was not
performed properly.
Error message
An instance of SnapCenter plug-in for Oracle is already installed
Corrective action
1. List the RPM packages:
rpm -qa | grep netapp-snapcenter-plugin
2. Delete the RPM packages:
156 | SnapCenter Software Installation and Setup Guide
rpm -e netapp-snapcenter-plugin-loader netapp-snapcenter-plugin-oracle
netapp-snapcenter-plugin-unix
3. Remove the /var/.com.zerog.registry.xml file manually.
4. Verify if the SPL service is running by entering the following command:
Ps -ef | grep spl
5. If SPL service is still running, kill the process by running the following command:
Kill -9 process_id
SnapCenter Plug-ins Package for Linux installation fails
Description
After installing SnapCenter and adding hosts, installing the SnapCenter Plug-ins Package for Linux
fails and the plug-in discovery operation cannot be performed. This issue occurs because of
disconnection between SnapCenter and the host during plug-in installation.
Corrective action
You must perform the following steps:
1. Find the status of the SPL service by running the following command:
/custom_location/NetApp/snapcenter/spl/bin/spl status
2. Manually uninstall the plug-in by running the following command:
/custom_location/NetApp/snapcenter/spl/installation/plugins uninstall
3. Verify if the SPL service is running by entering the following command:
Ps -ef | grep spl
4. If SPL service is still running, kill the process by running the following command:
Kill -9 process_id
If manual uninstallation fails, you must perform the following steps:
1. List the RPM packages:
rpm -qa | grep netapp-snapcenter-plugin
2. Delete the RPM packages:
rpm -e netapp-snapcenter-plugin-loader netapp-snapcenter-plugin-oracle
netapp-snapcenter-plugin-unix
3. Remove the /var/.com.zerog.registry.xml file manually.
4. Verify if the SPL service is running by entering the following command:
Ps -ef | grep spl
5. If SPL service is still running, kill the process by running the following command:
Kill -9 process_id
After successfully uninstalling the plug-in, remove the host and then try again.
Troubleshooting | 157
Reinstalling SnapCenter Plug-ins for Linux does not update
spl.properties file with new values
Description
After uninstalling the SnapCenter Plug-ins for Linux from the Linux host using Remove Host, while
reinstalling the plug-ins using Add Host if you change any value, the spl.properties file does
not get updated with the new values. Thus, even after successful installation, Linux host could not be
connected.
Error message
Unable to connect to the remote server.
Corrective action
After uninstalling the plug-ins, you must manually run rm -f /var/opt/
snapcenter/spl/etc/* before reinstalling the plug-ins.
SnapCenter Server is unable to communicate with the host
Description
After installing the plug-in remotely, SnapCenter Server is unable to communicate with the host.
Corrective action
1. Verify whether the SnapCenter plug-in loader is started on the correct port with proper host name.
2. Configure the FQDN of the host if the SnapCenter plug-in loader has been started with localhost:
8145.
3. Run the hostname -f command to find the FQDN of the host.
4. Restart the SnapCenter plug-in loader service after changing the host name.
SnapCenter plug-in loader fails with an error
Description
SnapCenter plug-in loader fails with an error.
Error message
Error retrieving current directory.
Corrective action
•
You must ensure that you have not deleted any directory where the plug-in is operating on.
•
You must increase the memory space allotted to the Java Virtual Machine.
158 | SnapCenter Software Installation and Setup Guide
SnapCenter plug-in loader does not start automatically
when the host is restarted
Description
When the host is restarted, the SnapCenter plug-in loader (SPL) does not start automatically if there
is no symbolic link in /user/bin/Java, or if Java is mounted from an external entity.
Error message
ERROR: JAVA_HOME is set to an invalid directory.
Failed to start SnapCenter Plugin Loader.
Corrective action
If the host is running on...
Then...
init.d
1. Create the spl configuration file at /etc/
default/.
2. Add export
JAVA_HOME=path_where_java_is_moun
ted to the spl configuration file.
3. Add [-f /etc/default/spl ]
&& . /etc/default/spl to the
beginning of the SPL init script located
at /etc/init.d/.
system.d
1. Create the spl.conf configuration file
at /etc/systemd/system/
spl.service.d/.
2. Add the following lines to the spl.conf
configuration file:
•
Environment=JAVA_HOME=path_whe
re_java_is_mounted
•
RestartSec=30
•
StartLimitInterval=200
•
StartLimitBurst=5
3. After updating spl.conf, reload
systemctl by running the systemctl
daemon-reload command.
Troubleshooting | 159
Registering vCenter details task displays a warning
Description
You added a vSphere type of host and the Add Host operation completed successfully. However, the
SnapCenter Plug-in for VMware vSphere was not able to communicate with the vCenter using the
vCenter information you entered. The task "Registering vCenter details with SnapCenter Plug-in for
VMware vSphere" in the operation details displays error information and is marked with a warning.
Task marked with a warning
Registering vCenter details with SnapCenter Plug-in for VMware vSphere.
Corrective action
Perform the following steps to update the vCenter information in the SnapCenter Plug-in for
VMware vSphere:
1. In the left navigation pane, click Hosts.
2. In the Hosts page, select the vSphere-type host.
3. Click the Add/Update vCenter details button.
4. In the dialog box, select the type of information you want to update:
Add/Update vCenter Details
Add/Update SnapCenter Details
5. In the dialog box, enter only the information that needs to be updated. Blank fields are not
changed.
6. Click OK.
Unable to access cluster IP address from outside network
Description
There is no response when you try to access the cluster IP address from outside the network.
Corrective action
Verify that you can use ping to access the dedicated IP addresses of the cluster host from a computer
outside the router. If this test fails and you are using multiple network adapters, the issue is not
related to Network Load Balancing (NLB). If you are using a single network adapter for the
dedicated and cluster IP addresses, consider the following scenarios:
Scenario
Solution
If you are using multicast support, you might
find that your router has difficulty resolving the
primary IP address into a multicast media
access control (MAC) address by using the
Address Resolution Protocol (ARP)
Verify that you can use ping to access the
cluster from a client on the cluster's subnet and
the cluster host's dedicated IP address from a
computer outside the router. If these tests work
properly, the router is probably at fault. You
should be able to add a static ARP entry to the
router to circumvent the issue.
160 | SnapCenter Software Installation and Setup Guide
Scenario
Solution
When using NLB in multicast or unicast mode,
routers need to accept proxy ARP responses
(IP-to-network address mappings that are
received with a different network source address
in the ethernet frame).
You must ensure that that your router has proxy
ARP support turned on. You can also set a static
ARP entry to keep proxy ARP support disabled
in the router.
Internet control message protocol (ICMP) to the
cluster is blocked by a router or firewall.
Allow ICMP traffic through the router or
firewall.
However, allowing ICMP traffic through router
or firewall might expose your system to
additional security risk.
Unable to upgrade to SnapCenter 3.0 because
communication with MySQL Server fails
Description
While upgrading to SnapCenter 3.0, the upgrade to MySQL Server is successful, but the SnapCenter
Server fails to communicate with the MySQL Server. Therefore, the SnapCenter upgrade operation
fails.
Error message
Exception: Cannot connect to MySQL server on localhost.
Workaround
You must manually uninstall MySQL Server and delete the MySQL folder in %programdata%
before retrying the SnapCenter upgrade operation.
Unable to add storage systems after upgrading SnapCenter
Server
Description
After upgrading SnapCenter Server, if you try to add a storage system without upgrading the plug-ins
on the host, the operation fails.
Error message
Failed on Host: host_name. There was no endpoint listening local host that
could accept the message. This is often caused by an incorrect address or
SOAP action. See InnerException, if present, for more details.
Corrective Action
You must upgrade the plug-ins on the host before adding any storage system.
Troubleshooting | 161
Failed to uninstall SnapCenter Server
Description
If you do not have sufficient space on the drive where the SnapCenter Server was installed then while
uninstalling the SnapCenter Server using Add\Remove Programs option, the operation fails.
Error message
IDS_ERROR_NO_WIZARD_PAGES error.
Corrective action
While uninstalling the SnapCenter Server using Add\Remove Programs, ensure that you have at
least 2 GB of free space on the drive where the SnapCenter Server was installed.
Uninstall does not remove plug-in from vCenter
Description
You uninstalled SnapCenter Plug-in for VMware vSphere but the plug-in was not removed from
vCenter.
Corrective action
Perform the following steps to unregister the plug-in from vCenter:
1. From the vCenter mob, unregister the following extensions: com.netapp.aegis and
com.netapp.scvm.webclient.
2. Restart the vCenter web client service.
Related tasks
Restarting the vSphere web client service on page 110
162
Appendixes
These appendixes provide additional reference information for SnapCenter users.
Adding an ONTAP RBAC role using security login
commands
You can use the security login commands to add an ONTAP RBAC role when your storage
systems are running clustered ONTAP.
Before you begin
Before you create an ONTAP RBAC role for storage systems running clustered ONTAP, you must
identify the following:
•
The task (or tasks) that you want to perform
•
The privileges required to perform these tasks
About this task
Configuring an RBAC role requires that you perform the following actions:
•
Grant privileges to commands and/or command directories.
There are two levels of access for each command/command directory: all-access and read-only.
You must always assign the all-access privileges first.
•
Assign roles to users.
•
Vary your configuration depending on whether your SnapCenter plug-ins are connected to the
Cluster Administrator IP for the entire cluster or directly connected to a SVM within the cluster.
To simplify configuring these roles on storage systems, you can use the RBAC User Creator for Data
ONTAP tool, which is posted on the NetApp Communities Forum at
NetApp Community Document: RBAC User Creator for Data ONTAP
This tool automatically handles setting up the ONTAP privileges correctly. For example, RBAC User
Creator for Data ONTAP tool automatically adds the privileges in the correct order so that the allaccess privileges appear first. If you add the read-only privileges first and then add the all-access
privileges, ONTAP marks the all-access privileges as duplicates and ignores them.
Note: If you later upgrade SnapCenter or ONTAP, you should re-run the RBAC User Creator for
Data ONTAP tool to update the user roles you created previously. User roles created for an earlier
version of SnapCenter or ONTAP do not work properly with upgraded versions. When you re-run
the tool, it automatically handles the upgrade. You do not need to recreate the roles.
More information about setting up ONTAP RBAC roles is in the ONTAP Cluster-Mode Systems
Administration Guide.
ONTAP 9 SAN Administration Guide
Note: For consistency, the SnapCenter documentation refers to the roles as using privileges. The
OnCommand System Manager GUI uses the term “attribute” instead of “privilege.” When setting
up ONTAP RBAC roles, both these terms mean the same thing.
Appendixes | 163
Steps
1. On the storage system, create a new role by entering the following command:
security login role create <role_name> -cmddirname "command" -access all
–vserver <svm_name>
svm_name is the name of the SVM. If you leave this blank, it defaults to cluster administrator.
role_name is the name you specify for the role.
command is the ONTAP capability.
Note: You must repeat this command for each permission.
Note: Remember that all-access commands must be listed before read-only commands.
2. Create a user name by entering the following command:
security login create -username <user_name> -application ontapi authmethod <password> -role <name_of_role_in_step_1> –vserver <svm_name>
-comment "user_description"
user_name is the name of the user you are creating.
<password> is your password. If you do not specify a password, the system will prompt you for
one.
svm_name is the name of the SVM.
3. Assign the role to the user by entering the following command:
security login modify username <user_name> –vserver <svm_name> -role
<role_name> -application ontapi -application console -authmethod
<password>
<user_name> is the name of the user you created in Step 2. This command lets you modify the
user to associate it with the role.
<svm_name> is the name of the SVM.
<role_name> is the name of the role you created in Step 1.
<password> is your password. If you do not specify a password, the system will prompt you for
one.
4. Verify that the user was created correctly by entering the following command:
security login show –vserver <svm_name> -user-or-group-name <user_name>
user_name is the name of the user you created in Step 3.
This command displays information about the user and the role.
Minimum recommended RBAC roles for SnapCenter Plug-in
for VMware vSphere
The recommended roles contain all the privileges necessary to perform tasks on the storage systems
that are associated with each role.
Roles recommended for SnapCenter Plug-in for VMware vSphere
•
ONTAP role
We recommend that you create one ONTAP role for SnapCenter Plug-in for VMware vSphere
operations and assign it all the required privileges.
164 | SnapCenter Software Installation and Setup Guide
•
vCenter roles created by SnapCenter Plug-in for VMware vSphere
The following roles are created by SnapCenter Plug-in for VMware vSphere when it is installed
in vCenter:
◦
SCV Administrator
◦
SCV View
◦
SCV Backup
◦
SCV Restore
Minimum ONTAP privileges required
The minimum ONTAP privileges that are required vary according to the SnapCenter plug-ins you are
using for data protection.
All SnapCenter plug-ins require the following minimum privileges, except where noted in the
information following these tables.
All-access commands: Minimum privileges required for ONTAP 8.2.x and later
event generate-autosupport-log
job history show
job stop
lun
lun create
lun delete
lun igroup add
lun igroup create
lun igroup delete
lun igroup rename
lun igroup show
lun mapping add-reporting-nodes
lun mapping create
lun mapping delete
lun mapping remove-reporting-nodes
lun mapping show
lun modify
lun move-in-volume
lun offline
lun online
lun persistent-reservation clear
lun resize
lun serial
lun show
Appendixes | 165
All-access commands: Minimum privileges required for ONTAP 8.2.x and later
snapmirror policy add-rule
snapmirror policy modify-rule
snapmirror policy remove-rule
snapmirror policy show
snapmirror restore
snapmirror show
snapmirror update
snapmirror update-ls-set
version
volume clone create
volume clone show
volume clone split start
volume clone split stop
volume create
volume destroy
volume file clone create
volume file show-disk-usage
volume offline
volume online
volume modify
volume qtree create
volume qtree delete
volume qtree modify
volume qtree show
volume restrict
volume show
volume snapshot create
volume snapshot delete
volume snapshot modify
volume snapshot rename
volume snapshot restore
volume snapshot restore-file
volume snapshot show
volume unmount
166 | SnapCenter Software Installation and Setup Guide
All-access commands: Minimum privileges required for ONTAP 8.2.x and later
vserver cifs
vserver cifs share create
vserver cifs share delete
vserver cifs share show
vserver cifs show
vserver export-policy
vserver export-policy create
vserver export-policy delete
vserver export-policy rule create
vserver export-policy rule show
vserver export-policy show
vserver iscsi
vserver iscsi connection show
vserver show
Read-only commands: Minimum privileges required for ONTAP 8.2.x and later
network interface
network interface show
vserver
Additional information for SnapCenter Plug-in for Microsoft SQL Server
•
All-access command privilege that is not required: lun persistent-reservation clear.
•
If you are protecting virtualized databases or databases on VMs, you must also comply with the
requirements for SnapCenter Plug-in for VMware vSphere.
Additional information for SnapCenter Plug-in for Oracle Database
•
All-access command privileges that are not required:
vserver cifs share create
vserver cifs share delete
vserver cifs share show
vserver cifs show
vserver export-policy
vserver export-policy create
vserver export-policy delete
vserver export-policy rule create
vserver export-policy rule show
vserver export-policy show
vserver iscsi
vserver iscsi connection show
•
Read-only command privileges that are not required:
network interface
network interface show
Appendixes | 167
vserver
•
Additional all-access command privileges that are required:
lun attribute show
lun geometry
network interface
network interface show
vserver
•
If you are protecting virtualized databases or databases on VMs, you must also comply with the
requirements for SnapCenter Plug-in for VMware vSphere.
Additional information for SnapCenter Plug-in for Microsoft Windows
•
All-access command privilege that is not required: lun persistent-reservation clear.
•
If you are protecting virtualized file systems or file systems on VMs, you must also comply with
the requirements for SnapCenter Plug-in for VMware vSphere.
Additional information for SnapCenter Plug-in for VMware vSphere
•
If you are running ONTAP 8.2.x
You must login as vsadmin on the SVM to have the appropriate privileges for SnapCenter Plugin for VMware vSphere operations.
•
If you are running ONTAP 8.3 and later
You must login as vsadmin or with a role that has the minimum privileges listed in the tables in
this appendix.
Additional information for SnapCenter Custom Plug-ins
•
All-access command privileges that are not required:
lun
lun persistent-reservation clear
vserver export-policy
vserver iscsi
•
Read-only command privileges that are not required:
network interface show
vserver
•
Additional all-access command privileges that are required:
lun attribute show
lun geometry
network interface
vserver cifs shadowcopy show
•
If you are protecting virtualized data or data on VMs, you must also comply with the
requirements for SnapCenter Plug-in for VMware vSphere.
168 | SnapCenter Software Installation and Setup Guide
ONTAP CLI commands for creating SVM roles
There are several ONTAP CLI commands you must run when you create a role for a new SVM user
in ONTAP. This role is required if you configure SVMs in ONTAP to use with SnapCenter and you
do not want to use the vsadmin role.
ONTAP CLI command list
Command to run
security login role create -role SVM_Role_Name -cmddirname "event generate-autosupport-log" vserver SVM_Name -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "job history
show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "job stop" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun create" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun delete" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun igroup
add" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun igroup
create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun igroup
delete" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun igroup
rename" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun igroup
show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun mapping
add-reporting-nodes" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun mapping
create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun mapping
delete" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun mapping
remove-reporting-nodes" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun mapping
show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun modify" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun move-involume" -access all
Appendixes | 169
Command to run
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun offline" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun online" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun resize" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun serial" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "lun show" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "network
interface" -access readonly
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "network
interface show" -access readonly
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
policy add-rule" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
policy modify-rule" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
policy remove-rule" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
policy show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
restore" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
update" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "snapmirror
update-ls-set" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "version" access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume clone
create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume clone
show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume clone
split start" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume clone
split stop" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume create"
-access all
170 | SnapCenter Software Installation and Setup Guide
Command to run
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
destroy" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume file
clone create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume file
show-disk-usage" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
modify" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
offline" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
online" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume qtree
create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume qtree
delete" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume qtree
modify" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume qtree
show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
restrict" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume show"
-access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
snapshot create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
snapshot delete" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
snapshot modify" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
snapshot rename" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
snapshot restore" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
snapshot restore-file" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
snapshot show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "volume
unmount" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver cifs
share create" -access all
Appendixes | 171
Command to run
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver cifs
share delete" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver cifs
share show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver cifs
show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver exportpolicy create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver exportpolicy delete" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver exportpolicy rule create" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver exportpolicy rule show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver exportpolicy show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver iscsi
connection show" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver show"
-access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver" access readonly
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver exportpolicy" -access all
security login role create -vserver SVM_Name -role SVM_Role_Name -cmddirname "vserver iscsi" access all
172 | SnapCenter Software Installation and Setup Guide
Features enabled on your Windows host during installation
The SnapCenter Server installer enables the Windows features and roles on your Windows host
during installation. These might be of interest for troubleshooting and host system maintenance
purposes.
Category
Feature
Web Server
•
•
•
Internet Information Services
World Wide Web Services
Common HTTP Features
•
◦ Default Document
◦ Directory Browsing
◦ HTTP Errors
◦ HTTP Redirection
◦ Static Content
◦ WebDAV Publishing
Health and Diagnostics
•
◦ Custom Logging
◦ HTTP Logging
◦ Logging Tools
◦ Request Monitor
◦ Tracing
Performance Features
•
◦ Static Content Compression
Security
•
◦ IP Security
◦ Basic Authentication
◦ Centralized SSL Certificate Support
◦ Client Certificate Mapping Authentication
◦ IIS Client Certificate Mapping Authentication
◦ IP and Domain Restrictions
◦ Request Filtering
◦ URL Authorization
◦ Windows Authentication
Application Development Features
•
◦ .NET Extensibility 4.5
◦ Application Initialization
◦ ASP.NET 4.5
◦ Server-Side Includes
◦ WebSocket Protocol
Management Tools
◦
IIS Management Scripts and
Tools
•
•
IIS Management Console
IIS Management Service
Web Management Tools
Appendixes | 173
Category
Feature
.NET Framework 4.5.2 Features
•
•
•
.NET Framework 4.5.2
ASP.NET 4.5.2
Windows Communication Foundation (WCF) HTTP
Activation45
◦
◦
◦
TCP Activation
HTTP Activation
Message Queuing (MSMQ) Activation
Message Queuing
•
•
Message Queuing Services
Microsoft Message Queue (MSMQ) Server
Windows Process Activation
Service
•
Process Model
Configuration APIs
All
174
Copyright information
Copyright © 1994–2017 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
175
Trademark information
Active IQ, AltaVault, Arch Design, ASUP, AutoSupport, Campaign Express, Clustered Data ONTAP,
Customer Fitness, Data ONTAP, DataMotion, Element, Fitness, Flash Accel, Flash Cache, Flash
Pool, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexVol, FPolicy, Fueled by
SolidFire, GetSuccessful, Helix Design, LockVault, Manage ONTAP, MetroCluster, MultiStore,
NetApp, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANscreen,
SANshare, SANtricity, SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter,
SnapCopy, SnapDrive, SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover,
SnapProtect, SnapRestore, Snapshot, SnapValidator, SnapVault, SolidFire, SolidFire Helix,
StorageGRID, SyncMirror, Tech OnTap, Unbound Cloud, and WAFL and other names are
trademarks or registered trademarks of NetApp, Inc., in the United States, and/or other countries. All
other brands or products are trademarks or registered trademarks of their respective holders and
should be treated as such. A current list of NetApp trademarks is available on the web.
http://www.netapp.com/us/legal/netapptmlist.aspx
176
How to send comments about documentation and
receive update notifications
You can help us to improve the quality of our documentation by sending us your feedback. You can
receive automatic notification when production-level (GA/FCS) documentation is initially released or
important changes are made to existing production-level documents.
If you have suggestions for improving this document, send us your comments by email.
doccomments@netapp.com
To help us direct your comments to the correct division, include in the subject line the product name,
version, and operating system.
If you want to be notified automatically when production-level documentation is released or
important changes are made to existing production-level documents, follow Twitter account
@NetAppDoc.
You can also contact us in the following ways:
•
NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.
•
Telephone: +1 (408) 822-6000
•
Fax: +1 (408) 822-4501
•
Support telephone: +1 (888) 463-8277
Index | 177
Index
A
about this guide
deciding whether to use SnapCenter 8
access
assigning to users 45
logging in to SnapCenter 37
accounts
configuring with RBAC 91
administrator
logging in to SnapCenter as 37
role 40, 42, 83
Application Request Routing
configuring 30
removing server farm 144
requirements for installation 30
understanding 30
architecture
overview of SnapCenter components 9
ASM instance
setting up your Run As account credentials 52, 53
audience
for the installation and set up guide 8
authentication
encryption 13
for Run As credential 52
setting up your Run As account 52, 53
types 52
AutoSupport
enabling email notifications 153
enabling notifications for storage system connections
in SnapCenter 49
B
backup jobs, vCenter
See resource groups
backups
configuring log directory 69
resources, resource groups, and policies overview 14
using SnapMirror and SnapVault replication 113
best practices
for uninstalling plug-ins 140
for uninstalling SnapCenter 144
for volume and share configurations 127
getting started with SnapCenter 71
setting up your Run As account 52, 53
browsers
supported versions 27
C
capacity
calculating 47
clone operations
resources, resource groups, and policies overview 14
Cluster Shared Volumes
connecting to disks 124
creating disks 121
clusters, Microsoft
introduction to using FC RDM LUNs in 130
support limitations when using FC RDM LUNs 131
cmdlets
SnapCenter Plug-in for Microsoft Windows support
132
comments
how to send feedback about documentation 176
configuring
AutoSupport email notifications 153
host log directory 69
the frequency of software update checks 134
updating hypervisor message in host status 100
connections
required before installing SnapCenter 27
setting up for storage systems 86
setting up for storage systems in SnapCenter 49
credentials
setting up your Run As account 52, 53
supported for installing plug-ins for Windows 130
using RBAC 91
CSV
See Cluster Shared Volume
custom plug-ins
adding resources to SnapCenter Custom Plug-ins 72
custom user accounts
configuring using RBAC 91
D
dashboard notifications
adding for SnapCenter capacity licenses 47
Data ONTAP DSM
requirements for SAN environments 26
data protection
resources, resource groups, and policies overview 14
SnapCenter 9
data protection operations
where to get information about SnapCenter licensing
requirements 29
databases
adding 74
preparing for SnapMirror replication 114
preparing storage systems for SnapVault replication
115
datastores
supported storage types 80
disks
connecting to LUNs in SnapCenter 124
creating in SnapCenter 121
deleting LUNs in SnapCenter 127
disconnecting from LUNs in SnapCenter 126
resizing in SnapCenter 124
tasks you can perform using SnapCenter 121
viewing on a host 121
documentation
how to receive automatic notification of changes to
176
178 | SnapCenter Software Installation and Setup Guide
how to send feedback about 176
downloading
SnapCenter software updates 134
disconnecting LUNs from 126
domain requirements for installing SnapCenter 23
features enabled during installation on Windows 172
modifying an igroup 120
provisioning Windows with SnapCenter Plug-in for
Microsoft Windows 118
remote, installing Plug-in for VMware vSphere on
E
email notifications
adding for SnapCenter capacity licenses 47
enabling for AutoSupport messages 153
EMS messaging
enabling for storage systems connections in
SnapCenter 49
error messages
Error retrieving current directory 157
Failed to start SnapCenter plug-in loader 158
JAVA_HOME is set to an invalid directory 158
launching SnapCenter 154
ESX servers
limitations of SnapCenter Plug-in for Microsoft
Windows support 130
F
failure
uninstalling SnapCenter Server 161
FC RDM LUNs
creating shared 131
introduction to using in Microsoft clusters 130
Microsoft cluster support limitations when using 131
requirements for using in Microsoft clusters 130
FC-connected LUNs
creating 121
introduction to configuring with SnapCenter Plug-in
for Windows 118
FC/iSCSI
host requirements 26
features
enabled during installation on Windows hosts 172
of SnapCenter 9
feedback
how to send comments about documentation 176
G
GUI sessions
modifying the default timeout period 39
H
host
requirements for SnapCenter installation 23
host restarts
troubleshooting when plug-in loader fails to start
after 158
Host Utilities
requirements for SAN, FC/iSCSI environments 26
hosts
adding to SnapCenter 55, 61
creating an igroup in SnapCenter Plug-in for
Microsoft Windows 119
creating SMB shares 127
deleting an igroup 120
93
remote, installing prerequisites for plug-in packages
on 55
remote, requirements for installing Plug-in for
VMware vSphere on 80
removing from SnapCenter 140, 143
removing from SnapCenter, introduction to 140
renaming an igroup 120
requirements for SAN, FC/iSCSI environments 26
space and sizing requirements for installing
SnapCenter 24
supported systems 26
system requirements for installing SnapCenter 23
updating status for virtual machines (VMs) 100
viewing a list of disks on 121
vSphere, adding to SnapCenter 93
HTTP
error 503 launching SnapCenter 154
hypervisors
updating settings for 100
I
igroups
creating in SnapCenter Plug-in for Microsoft
Windows 119
deleting in SnapCenter Plug-in for Microsoft
Windows 120
managing 119
modifying 120
purpose 119
renaming 120
information
how to send feedback about improving
documentation 176
initiators
adding to an igroup 120
creating an igroup 119
installation
connection and port requirements for SnapCenter 27
domain requirements for packages 23
features enabled on Windows hosts 172
monitoring 69
plug-in checklist 57
preparing for 34
required information 34
SAN, FC/iSCSI host requirements 26
SnapCenter Plug-in Loader service 66
space requirements for packages 23
troubleshooting invalid username and password
issues 153
installation configurations
for Plug-in for VMware vSphere 92
installation fails
improper uninstallation 155
incorrect Java version 155
Index | 179
plug-in 156
installation methods
for installing Plug-in for VMware vSphere 92
installation packages
available SnapCenter independent plug-in 146
installation requirements
Plug-in for VMware vSphere 80
installing
on multiple hosts 68
overview for VMware vSphere users 79
Plug-in for VMware vSphere on remote hosts 93
preparation overview 21
preparation overview for Plug-in for VMware
vSphere 79
prerequisites for plug-in packages on remote hosts
55
SnapCenter 35
SnapCenter and the plug-ins, overview of 33
SnapCenter process overview for new users 16
SnapCenter process overview for SnapManager
users 18
Internet Explorer Protected Mode
disabling 155
iSCSI
disconnecting a session 119
establishing a session 118
iSCSI-connected LUNs
creating 121
introduction to configuring with SnapCenter Plug-in
for Windows 118
J
jobs
backups, configuring the log for 69
identifying available resources for 71
monitoring progress of plug-in package installation
69
L
licenses
adding SnapCenter 47
configuring capacity notification thresholds for 47
licensing requirements
where to get information about SnapCenter 29
limitations
MySQL HA 31
support when using FC RDM LUNs in Microsoft
clusters 131
VMware ESX server-related 130
Linked Mode
support by SnapCenter Plug-in for VMware vSphere
82
Linux
setting up your Run As account credentials on host
52, 53
Linux hosts
installing SnapCenter Plug-in for SAP HANA
Databases on, using the command-line interface 152
load balancing
best practices 30
using Application Request Routing 30
local hosts
troubleshooting issues with displaying web login
page on 155
logging in
as a SnapCenter administrator 37
as a SnapCenter user 37
SnapCenter 37
with more than one role 37
LUN storage
introduction to configuring with SnapCenter Plug-in
for Windows 118
LUNs
connecting to in SnapCenter 124
creating in SnapCenter 121
creating shared FC RDM 131
deleting in SnapCenter 127
disconnecting before deleting 126
disconnecting in SnapCenter 126
disk-related tasks you can perform using SnapCenter
121
FC RDM, requirements for using in a Microsoft
cluster 130
introduction to creating and managing using
SnapCenter Plug-in for Microsoft Windows in
VMware environments 129
prerequisites for iSCSI connections 118
RDM, support through PowerShell cmdlets 129
RDM, troubleshooting creation of 132
resizing in SnapCenter 124
LUNs, FC RDM
FC RDM Microsoft cluster support limitations when
using 131
introduction to using in Microsoft clusters 130
M
messages
enabling AutoSupport email notifications for 153
Microsoft clusters
introduction to using FC RDM LUNs in 130
support limitations when using FC RDM LUNs 131
Microsoft SQL Server
independently installing SnapCenter Plug-in for 148
silently installing SnapCenter Plug-in from
command line 149
migrating
VM backups, prerequisites for 103
VSC backups post-migration tasks 109
VSC host to SnapCenter Plug-in for VMware
vSphere 103
VSC host to SnapCenter plug-in, from SnapCenter
GUI 104
VSC host to SnapCenter plug-in, from vCenter 106
migrating VSC backups
restarting web client service 110
modifying
plug-in ports 65
MySQL HA
configuring Network Load Balancing 31
enabling and configuring Application Request
Routing 31
limitations 31
180 | SnapCenter Software Installation and Setup Guide
MySQL replication
for high availability 31
MySQL Server
identifying a repository for SnapCenter metadata 29
N
Network Load Balancing
configuring 30
removing cluster 144
understanding 30
non-root users
configuring sudo privileges for 57
installing plug-in for Oracle databases 57
notifications
enabling for AutoSupport email 153
O
objects
storage systems 88
vSphere 88
ONTAP
account permission requirements for SnapCenter 83
supported versions 26
ONTAP CLI commands
creating SVM roles 168
Oracle Database
independently installing SnapCenter Plug-in for 150
installing SnapCenter Plug-in from command line
151
interactively installing SnapCenter Plug-in for 150
setting up your Run As account credentials 52, 53
versions supported 26
P
permissions
associated with pre-defined roles 42
list of 40
role-based access control 40
setting for applications 52, 53
types of role-based access control in SnapCenter 39
understanding how to set 83
vCenter Server 88
plug-in loader
fails to start when host is restarted 158
failure 157
plug-in packages
introduction to installing 55
prerequisites to installing 55
upgrading 138
plug-in packages, SnapCenter
installing on remote hosts 61
plug-in ports
modifying 65
plug-ins
configuring 69
deployment checklist 57
description of 9
installing for Microsoft SQL Server independently
148
installing for Microsoft SQL Server silently from
command line 149
installing for Microsoft Windows independently 146
installing for Microsoft Windows silently from
command line 146
installing for Oracle Database from command line
151
installing for Oracle Database independently 150
installing for Oracle Database interactively 150
installing on multiple hosts 68
installing Plug-in for VMware vSphere on a local
host by using installer GUI 96
installing Plug-in for VMware vSphere using
cmdlets 95
installing SnapCenter Plug-in for VMware vSphere
from a local host using cmdlets 97
monitoring package installation 69
overview of installing SnapCenter and 33
preparation to install for Microsoft Windows 146
preparation to install for Oracle Database 150
preparation to install Microsoft SQL server 148
removing from a host 140
space and sizing requirements for SnapCenter
installation 24
uninstalling from SnapCenter, introduction to 140
uninstalling locally on host 142
uninstalling using command line 141, 142
updating SnapCenter information in SnapCenter
Plug-in for VMware vSphere 100
updating vCenter information in SnapCenter Plug-in
for VMware vSphere 100, 159
plug-ins package for Linux
uninstalling using command line 142
plug-ins package for Windows
uninstalling locally on host 142
uninstalling using command line 141
policies
used in SnapCenter data protection 14
port requirements
before installing SnapCenter 27
PowerShell cmdlets
reclaiming storage space with 128
SnapCenter Plug-in for Microsoft Windows support
132
prerequisites
for removing a host 143
privileges
list of minimum required 164
native vCenter Server 88
product level 89
SCV predefined roles 84
SnapCenter Plug-in for VMware vSphere 89
SnapCenter specific 88
R
RBAC
about 87
configuring 91
Data ONTAP privileges 87
minimum ONTAP privileges required 164
ONTAP 90
predefined vCenter roles 89
Index | 181
vCenter privileges 87
RBAC roles
adding using the CLI 162
changing VSC to SCV 109
recommended 163
removing VSC roles 109
roles
CLI commands for adding 162
RDM
minimum vCenter privileges required for operations
130
RDM LUNs
creating shared FC 131
introduction to using FC in Microsoft clusters 130
Microsoft cluster support limitations when using for
FC 131
requirements for FC support 130
troubleshooting creation of 132
reinstall plug-in for Linux
spl.properties is not updated 157
remote hosts
installing Plug-in for VMware vSphere on 93
installing SnapCenter plug-in packages on 61
prerequisites for installing plug-in packages on 55
requirements for installing Plug-in for VMware
vSphere 80
remote installation
on multiple hosts 68
remote plug-in installation
increasing timeout for 66
removing
a host from SnapCenter 140, 143
hosts from SnapCenter, introduction to 140
the Application Request Routing server farm 144
the Network Load Balancing cluster 144
the SnapCenter repository 144
replication
considerations for preparing storage systems for
SnapMirror and SnapVault 113
preparing storage systems for SnapMirror 114
preparing storage systems for SnapVault 115
repositories
for SnapCenter, overview of 9
identifying for SnapCenter metadata 29
repository database
supported upgrade scenarios 135
requirements
Application Request Routing 30
connection and port, before installing SnapCenter 27
for removing a host 143
for SnapCenter installation 34
resizing
disks 124
LUNs 124
resource groups
used in SnapCenter data protection 14
resources
adding to SnapCenter Custom Plug-ins 72
discovering 71
identifying available 71
used in SnapCenter data protection 14
restore operations
resources, resource groups, and policies overview 14
role-based access control
adding users to a role 45
assigning access to users 45
introduction to configuring for Plug-in for VMware
vSphere users 83
introduction to configuring for SnapCenter users 39
list of roles and permissions 40
pre-defined roles and permissions 42
predefined roles and permissions 84
types in SnapCenter 39
understanding for VMware vSphere 83
roles
adding users to 45
app backup and clone admin role, defined 42
available pre-defined 42
backup and clone viewer role, defined 42
configuring with RBAC 91
infrastructure admin role, defined 42
list of 40
SCV predefined 84
understanding role-based access control 83
roles for RBAC
recommended 163
Run As account
authentication methods 52
overview 83
setting up 52, 53
S
SAN environments
host requirements 26
security
configuring using RBAC 91
modifying the default GUI session timeout period 39
overview 13
servers
SQL, preparation to install SnapCenter plug-in for
148
SQL, silently installing SnapCenter plug-in for 149
VMware ESX limitations of SnapCenter Plug-in for
Microsoft Windows support 130
shared FC RDM LUNs
creating 131
using in a Microsoft cluster 131
shares, SMB
creating in SnapCenter Plug-in for Microsoft
Windows 127
simplify
SnapCenter installation process 34
SMB shares
creating in SnapCenter Plug-in for Microsoft
Windows 127
deleting in SnapCenter 128
SnapCenter
archiving Snapshot copies 115
components 9
connection and port requirements for installation 27
data protection 9
finding the URL 37
installation process overview for new users 16
installation process overview for SnapManager users
18
182 | SnapCenter Software Installation and Setup Guide
installation process overview for VMware vSphere
users 79
installation worksheet 34
installing 35
introduction to configuring role-based access control
for users 39, 83
migrating VSC host 104, 106
mirroring Snapshot copies 114
overview 9
overview of Plug-in for VMware vSphere 77
removing repository 144
templates for creating SMB shares 127
uninstalling 144
uninstalling, introduction to 140
upgrading plug-in packages 138
SnapCenter installation
space and sizing requirements for packages 24
SnapCenter licenses
types 46
SnapCenter Plug-in for Linux
installation failure 155, 156
SnapCenter Plug-in for Microsoft SQL Server
installing independently 148
installing silently from command line 149
overview of components 9
preparation to install 148
SnapCenter Plug-in for Microsoft Windows
creating an igroup 119
creating SMB shares 127
deleting an igroup 120
installing independently 146
installing silently from command line 146
limitations when using VMware ESX server 130
modifying an igroup 120
overview of components 9
PowerShell cmdlet support 132
preparation to install 146
prerequisites to install 146
renaming an igroup 120
SnapCenter Plug-in for Oracle Database
installing in console mode from command line 151
installing in silent mode from command line 151
installing independently 150
installing interactively 150
overview of components 9
preparation to install 150
prerequisites to install 150
SnapCenter Plug-in for SAP HANA Database
preparation to install 152
prerequisites to install 152
SnapCenter Plug-in for SAP HANA Databases
installing on the Linux host using the command-line
interface 152
prerequisite for installing independently 151
SnapCenter Plug-in for UNIX
overview of components 9
SnapCenter Plug-in for VMware
migrating VSC host to 103
SnapCenter Plug-in for VMware vSphere
configuring for SnapCenter Server 96
documentation errors 91
install requirements 77
installation requirements 80
installing from a local host using cmdlets 97
installing from the SnapCenter Server using cmdlets
95
installing on a local host by using installer GUI 96
introduction to configuring role-based access control
for users 83
introduction to installing 91
methods for installing 92
overview 77
overview of components 9
privileges 89
registering with vCenter Server 96, 97
support for ONTAP RBAC 90
support for virtualized data 77
types of installation configurations 92
upgrading 100
which GUI to use 78
SnapCenter Plug-in Loader service
start 66
status 66
stop 66
SnapCenter plug-ins
available independent installation packages 146
SnapCenter Plug-ins Package for Linux
installation failure 155
SnapCenter Server
overview 9
unable to communicate with the host 157
upgrading SnapCenter Server 136
which GUI to use 78
SnapMirror
considerations for preparing storage systems for
replication 113
differences from SnapVault 113
preparing storage systems for replication 114
Snapshot copies
features in SnapCenter 9
introduction to managing using SnapCenter Plug-in
for Microsoft Windows in VMware environments
129
preparing for SnapVault replication 115
preparing storage systems for SnapMirror replication
114
SnapVault
considerations for preparing storage systems for
replication 113
differences from SnapMirror 113
preparing storage systems for replication 115
software updates
configuring SnapCenter to automatically check for
134
space reclamation
on storage systems 128
SQL Server
setting up your Run As account credentials 52, 53
supported versions 26
storage system connections
enabling AutoSupport notifications for in
SnapCenter 49
enabling EMS messaging for in SnapCenter 49
storage systems
assigning permissions 88
configuring using RBAC 91
Index | 183
considerations for preparing for SnapMirror and
SnapVault replication 113
RBAC privileges 87
reclaiming space on 128
setting up connections to in SnapCenter 49
settings up connections to 86
storage types
supported by plug-ins package for Linux 23
supported by SnapCenter Plug-In for Microsoft SQL
Server 21
supported by SnapCenter Plug-In for Microsoft
Windows 21
supported by SnapCenter Plug-In for VMware
vSphere 80
supported VMs 80
SVMs 21, 80
VMs 21
storage, LUN
introduction to configuring with SnapCenter Plug-in
for Windows 118
sudo privileges
configuring for non-root user 53, 55
configuring for non-root users 57
suggestions
how to send feedback about documentation 176
support limitations
when using FC RDM LUNs in Microsoft clusters
131
SVMs
CLI commands to create SVM roles 168
setting up connections to 86
setting up connections to in SnapCenter 49
supported storage types 21, 23, 80
systems
considerations for preparing for SnapMirror and
SnapVault replication 113
domain requirements for SnapCenter installation 23
space and sizing requirements for SnapCenter
installation 24
T
templates
for creating SMB shares 127
terminology
resources, resource groups, and policies data
protection 14
timeout
increasing for remote plug-in installation 66
timeout periods
modifying the default GUI session 39
troubleshooting
cannot access cluster IP address 159
Failed to start SnapCenter plug-in loader error 158
features enabled during installation 172
HTTP error 503 154
installation issues with invalid username and
password 153
JAVA_HOME is set to an invalid directory error 158
RDM LUN creation 132
SnapCenter Server installation 153
unable to create SSL or TLS secure channel 154
unable to install or discover plug-ins 154
upgrade issues with Plug-in for Microsoft SQL
Server with databases on VMDK 154
upgrade issues with Plug-in for Microsoft Windows
154
upgrade issues with SnapCenter Server 160
web login page not displaying 155
Twitter
how to receive automatic notification of
documentation changes 176
U
uninstall
failure 161
plug-in for VMware not removed from vCenter 161
uninstalling
plug-ins from a host 140
SnapCenter 144
SnapCenter plug-ins, introduction to 140
SnapCenter, introduction to 140
VSC from host 109
updates, software
configuring SnapCenter to automatically check for
134
upgrade
limitations 135
troubleshooting issues with Plug-in for Microsoft
SQL Server with databases on VMDK 154
troubleshooting issues with Plug-in for Microsoft
Windows 154
unable to add storage systems 160
unable to communicate with MySQL Server 160
upgrading
overview 134
Plug-in for VMware vSphere 100
SnapCenter plug-in packages 138
user name
configuring custom with RBAC 91
user privileges
controlling using RBAC 87
users
adding to a role 45
assigning access to 45
introduction to configuring role-based access control
for 39, 83
using roles at login 37
V
vCenter
minimum privileges required for RDM operations
130
registering fails, updating vCenter information in
SnapCenter Plug-in for VMware vSphere 159
restarting web client service 110
restarting web client service in Linux 111
restarting web client service in Windows 110
updating SnapCenter Plug-in for VMware vSphere
100, 159
vCenter backup jobs
See resource groups
vCenter inventory
184 | SnapCenter Software Installation and Setup Guide
RBAC privileges 87
vCenter object
RBAC privileges 87
vCenter Server
permissions 88
predefined SnapCenter roles 89
vCenter servers
support for Linked Mode 82
virtual disks
tasks you can perform using SnapCenter 121
Virtual Storage Console
supported versions 26
virtualized environments
storage types supported 21
VM backups
prerequisites for migrating 103
VMs
supported storage types 21, 23, 80
which GUI to use 78
VMware
ESX servers limitations of SnapCenter Plug-in for
Microsoft Windows support 130
SnapCenter Plug-in for Windows support for 129
support for ESX iSCSI initiators 129
support for FC HBAs 129
support for guest OS platforms 129
support for iSCSI HBAs 129
support for iSCSI initiators 129
using Virtual Storage Console to provision Windows
hosts 118
VMware vCenter
which GUI to use 78
VSC
migrating to SnapCenter Plug-in for VMware 103
uninstalling from host 109
VSC host
migrating to SnapCenter plug-in, from SnapCenter
GUI 104
migrating to SnapCenter plug-in, from vCenter 106
VSC backups post-migration tasks 109
vSphere
objects 88
privileges not correct after upgrade 110
restarting web client service 110
restarting web client service in Linux 111
restarting web client service in Windows 110
W
web address
for SnapCenter 37
web client service
restarting in vCenter in Linux 111
restarting in vCenter in Windows 110
web login page
troubleshooting issues with displaying on local host
155
Windows hosts
creating an igroup in SnapCenter Plug-in for
Microsoft Windows 119
features enabled during installation 172
independently installing SnapCenter Plug-in for 146
silently installing SnapCenter Plug-in from
command line 146
Windows Process Activation Service (WAS)
enabling 154
Windows Server failover clusters
requirements for connecting to a disk 124
requirements for creating a disk 121
workflows
for VMware vSphere users 79
getting started 71
migrating VSC hosts 103
SnapCenter installation for new users 16
SnapCenter installation for SnapManager users 18
upgrading 134
upgrading Plug-in for VMware vSphere 100