SnapCenter Software 3.0 Administration Guide

SnapCenter® Software 3.0
Administration Guide
July 2017 | 215-12102_A0
doccomments@netapp.com
Table of Contents | 3
Contents
Deciding whether to read this information ................................................ 6
SnapCenter overview ................................................................................... 7
SnapCenter features ..................................................................................................... 7
SnapCenter components .............................................................................................. 7
SnapCenter security features ..................................................................................... 11
How resources, resource groups, and policies are used in data protection ............... 12
Storage types supported by SnapCenter Plug-ins for Microsoft
Windows and for Microsoft SQL Server ............................................. 14
Storage types supported by SnapCenter Plug-in for Oracle Database
.................................................................................................................. 16
Logging in to SnapCenter .......................................................................... 17
Managing SnapCenter Standard and Advanced capacity licenses ........ 19
Adding SnapCenter capacity licenses ....................................................................... 19
Viewing SnapCenter Standard and Advanced capacity license details ..................... 20
Modifying SnapCenter Standard or Advanced capacity licenses ............................. 21
Deleting SnapCenter Standard or Advanced capacity licenses ................................. 22
Managing your storage system connections ............................................. 23
What SVMs are ......................................................................................................... 23
Setting up storage system connections ...................................................................... 23
Modifying your storage system connections ............................................................. 27
Deleting your storage system connections ................................................................ 28
Viewing storage controller SnapManager Suite license status .................................. 28
Managing virtualization plug-ins .............................................................. 30
Updating vCenter or SnapCenter information in the SnapCenter Plug-in for
VMware vSphere ................................................................................................. 30
Using role-based access control ................................................................. 31
Types of role-based access control in SnapCenter .................................................... 31
SnapCenter role-based access control ....................................................................... 32
Role-based access control permissions and roles .......................................... 32
Pre-defined SnapCenter roles and permissions ............................................. 33
Adding a user to a role .................................................................................. 36
Creating a new role ........................................................................................ 37
Assigning users access to assets .................................................................... 37
Modifying a role ............................................................................................ 38
Application-level role-based access control .............................................................. 38
Authentication methods for your Run As credentials ................................... 38
Setting up your Run As credentials ............................................................... 39
Configuring Run As account credentials for an individual SQL Server
resource .................................................................................................... 41
Configuring Run As account credentials for an Oracle database .................. 42
Using Application Request Routing and Network Load Balancing ...... 44
4 | SnapCenter Software Administration Guide
Application Request Routing requirements .............................................................. 44
Determining load balancing status and Application Request Routing
enablement ........................................................................................................... 45
Provisioning storage on Windows hosts ................................................... 46
Configuring LUN storage .......................................................................................... 46
Establishing an iSCSI session ....................................................................... 46
Disconnecting an iSCSI session .................................................................... 47
Creating and managing igroups ..................................................................... 47
Creating and managing disks ........................................................................ 49
Creating and managing SMB shares ......................................................................... 55
Creating an SMB share ................................................................................. 55
Deleting an SMB share ................................................................................. 56
Reclaiming space on the storage system ................................................................... 56
Using the SnapCenter Plug-in for Microsoft Windows in VMware environments ... 57
Supported VMware guest OS platforms ....................................................... 57
Using FC RDM LUNs in a Microsoft cluster ............................................... 58
Troubleshooting RDM LUN creation ........................................................... 59
SnapCenter Plug-in for Microsoft Windows cmdlets ............................................... 60
Working with managed hosts .................................................................... 61
Viewing details about managed hosts ....................................................................... 62
Modifying hosts and plug-ins .................................................................................... 63
Refreshing virtual machine information ................................................................... 64
Starting and restarting plug-in services ..................................................................... 64
Suspending schedules on hosts to place them in maintenance mode ........................ 64
Removing a host from SnapCenter Server ................................................................ 65
Prerequisites to remove a host ....................................................................... 65
Removing a host ............................................................................................ 66
Verifying the supported configurations for SnapCenter Plug-ins Package for
Linux .................................................................................................................... 66
Managing the SnapCenter Server repository .......................................... 67
Prerequisites for protecting the SnapCenter repository ............................................. 67
Configuring the SnapCenter repository for protection .............................................. 68
Getting backups of the SnapCenter database ............................................................ 69
Restoring the SnapCenter database backup .............................................................. 70
Migrating the SnapCenter repository ........................................................................ 70
Using SnapCenter reporting capabilities ................................................. 72
Centralized reporting options .................................................................................... 72
Information provided in Dashboard reports .............................................................. 73
Requesting job status reports from the Dashboard .................................................... 76
Configuring your dashboard ...................................................................................... 76
Types of reports ......................................................................................................... 77
Configuring your reports ........................................................................................... 77
Exporting or printing reports ..................................................................................... 78
Setting the SMTP server for email notifications using Global Settings .................... 78
Configuring the option to email reports .................................................................... 79
Table of Contents | 5
Monitoring jobs, schedules, events, and logs ........................................... 80
Monitoring SnapCenter jobs ..................................................................................... 80
Monitoring backup operations ...................................................................... 81
Stopping a scheduled job ............................................................................... 81
Canceling queued jobs .................................................................................. 82
Monitoring SnapCenter schedules ............................................................................ 82
Monitoring SnapCenter events .................................................................................. 82
Monitoring SnapCenter logs ..................................................................................... 83
Types of SnapCenter logs .............................................................................. 83
Event log locations ........................................................................................ 84
Using Microsoft Windows Installer log files ................................................ 84
Using the SnapCenter version.exe/debug log ................................................ 85
Exporting logs ............................................................................................... 85
Removing jobs and logs from SnapCenter ................................................................ 86
Administering EMS data collection .......................................................... 87
Stopping EMS data collection ................................................................................... 87
Starting EMS data collection ..................................................................................... 87
Changing EMS data collection schedule and target SVM ........................................ 88
Monitoring EMS data collection status ..................................................................... 88
Using SnapCenter REST APIs .................................................................. 90
Accessing REST APIs using the Swagger API web page ........................................ 90
List of available REST APIs ..................................................................................... 90
Troubleshooting REST APIs ..................................................................................... 91
Copyright information ............................................................................... 92
Trademark information ............................................................................. 93
How to send comments about documentation and receive update
notifications ............................................................................................ 94
Index ............................................................................................................. 95
6
Deciding whether to read this information
This information describes how to manage SnapCenter by managing your SVM connections,
virtualization plug-ins, hosts, and the SnapCenter Server repository, and how to provision storage on
Windows hosts, maintain role-based access control (RBAC), and use the centralized reporting
options.
You should read this information if you want to use SnapCenter in the following ways:
•
Update vCenter or SnapCenter information in the SnapCenter Plug-in for VMware vSphere
•
Create, modify, or remove a SnapCenter Standard or Advanced capacity license
•
Set up, modify, or delete SVM connections
•
Create or modify RBAC roles, then assign users to RBAC roles or assign assets to users
•
Use Application Request Routing and Network Load Balancing
•
Provision storage on Windows hosts or reclaim storage space
•
Create and manage SMB shares on Windows hosts
•
Modify hosts and plug-ins or remove a host
•
Start or restart plug-in services
•
Suspend or restart schedules on hosts
•
Configure, backup, or restore the SnapCenter repository
•
Configure your dashboard
•
Configure, export, or print reports
•
Monitor jobs, schedules, events, and logs
•
Stop, start, modify, and monitor EMS data collection
•
Use SnapCenter REST APIs
You should have already performed the following:
•
Read the SnapCenter Software 2.0 Release Notes
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
SnapCenter Software Resources page on the NetApp Support Site at mysupport.netapp.com.
NetApp SnapCenter Software Resources
7
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. The
SnapCenter Custom Plug-ins enables you to create your own custom plug-ins to protect data using
the same SnapCenter interface.
To support virtualized environments, and to protect VMs and datastores, SnapCenter also interacts
with the SnapCenter Plug-in for VMware vSphere.
SnapCenter includes these components.
8 | SnapCenter Software Administration Guide
SnapCenter Server
The SnapCenter Server 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 | 9
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.
•
Support for virtualized databases and Windows file systems
SnapCenter Plug-in for VMware vSphere provides support for virtualized applications
when you use the SnapCenter GUI to perform backup, recovery, and cloning
operations. SnapCenter reduces the complexity of protecting virtualized applications
by natively leveraging SnapCenter 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.
•
Support for VMs and datastores
SnapCenter Plug-in for VMware vSphere also provides a vSphere web client in
vCenter. The SnapCenter Plug-in for VMware vSphere GUI in vCenter allows you to
perform backup and restore operations of VMs and backups of datastores that are
registered with SnapCenter.
10 | SnapCenter Software Administration Guide
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.
The SnapCenter Plug-in for VMware vSphere is installed on a Windows host.
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:
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 supported.
SnapCenter Plug-in for UNIX
The Plug-in for UNIX handles the underlying host storage stack and enables you to
perform backup, restore, clone, mount, and unmount 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 used with the Data Fabric Solution for
Cloud Backup
With the Data Fabric Solution for Cloud Backup, storage administrators and IT generalists can
perform Snapshot copy-based data protection operations for file shares to and from public or private
cloud object stores. Delivering high service levels with fast Snapshot copies and efficient array-based
replication, the solution includes NetApp ONTAP, SnapCenter data management software, and
AltaVault cloud-integrated storage software.
If you are using SnapCenter Plug-in for NAS File Services as part of the Data Fabric Solution for
Cloud Backup deployment, you should look at the Data Fabric Solution for Cloud Backup
information first.
SnapCenter overview | 11
SnapCenter Custom Plug-ins
You can create custom plug-ins and use the SnapCenter Custom Plug-ins feature to manage
applications of your choice. The SnapCenter Custom Plug-ins feature supports customized plug-ins
that enable application-aware data protection and management of resources.
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 with NetApp SnapMirror technology to
create mirror copies of backup sets on another volume and use NetApp SnapVault technology to
perform disk-to-disk backup replication. The Custom Plug-ins can be used in both Windows and
Linux environments. In Windows environment, 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.
NetApp provides MySQL and DB2 custom plug-in samples with SnapCenter Software. These plugins 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 information
SnapCenter Software 3.0 Developer's Guide for Creating Custom Plug-ins
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.
12 | SnapCenter Software Administration Guide
•
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.
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 only backs up single resources if they are 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 | 13
The following image illustrates the relationship between resources, resource groups, and policies for
Windows files systems:
14
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
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
VMware 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.
Storage types supported by SnapCenter Plug-ins for Microsoft Windows and for Microsoft SQL Server | 15
Machine
Storage type
Provision using
Support notes
Hyper-V VM
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
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.
16
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
17
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.
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.
18 | SnapCenter Software Administration Guide
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 Windows Cmdlet Reference Guide
SnapCenter Software 3.0 Linux Command Reference Guide
19
Managing SnapCenter Standard and Advanced
capacity licenses
You can add new SnapCenter Standard or Advanced licenses, modify the capacity threshold
notifications, update the capacity value, or delete a license when it is no longer required.
You can perform the following tasks related to SnapCenter Standard and Advanced capacity licenses:
•
Add new licenses and configure capacity threshold notifications.
•
Modify capacity threshold notifications and license properties for existing licenses.
•
Delete a license.
Related concepts
Information provided in Dashboard reports on page 73
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 SnapCenterAdmin 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.
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.
b. Enter your password.
c. Enter your SnapCenter license serial number.
Note: This is not your storage controller serial number.
20 | SnapCenter Software Administration Guide
For this field...
NetApp License File
Do this...
a. Browse to the location of the license file.
b. Select the license file.
c. Click Open.
5. In the Add SnapCenter License wizard 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 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.
Viewing SnapCenter Standard and Advanced capacity
license details
You can view the SnapCenter Standard and Advanced capacity license details to quickly locate
information about each license.
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, view the following information:
Serial Number
The capacity package serial number.
Package
The type of capacity license.
Managing SnapCenter Standard and Advanced capacity licenses | 21
Capacity
The amount of licensed capacity.
Used
The amount of used capacity.
Over
The amount of used capacity over the licensed capacity.
4. To view additional details for a specific license, select a license, and then click Details.
5. To determine the type of capacity licenses you have installed in SnapCenter, the license capacity,
and other license license details, in the Details page, view the following information for the
selected license:
Serial Number
The serial number for the capacity license you selected.
Package
The type of license package you selected. For example, SW-SSP-SNAPCTR-STD-TRIAL
indicates a SnapCenter standard capacity trial license, and SW-SSP-SNAPCTR-ADVTRIAL indicates an advanced capacity trial license.
Capacity
The amount of licensed capacity.
Capacity notifications
The types of notifications you configured. For example, you can configure Email, EMS,
and AutoSupport notifications.
Support agreement
The license expiration date and a link to the support agreement on the NetApp Support
Site.
Modifying SnapCenter Standard or Advanced capacity
licenses
You can modify SnapCenter Standard or Advanced licenses when you want to replace the existing
license, for instance, to update the license capacity or to change the threshold notification settings.
Before you begin
You must have SnapCenter Admin privileges.
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, select the license you want to change, and then click
the Modify icon.
4. In the Modify SnapCenter License wizard, select one of the following methods to access the
license you want to update or replace:
22 | SnapCenter Software Administration Guide
For this field...
Do this...
NetApp Support Site
(NSS)
a. Enter your NSS user name.
b. Enter your password.
c. Enter your license serial number.
NetApp License File
a. Browse to the location of the license file.
b. Select the license file.
c. Click Open.
5. In the Notifications tab, provide the information you want to change, and then click Next.
6. Review the summary, and then click Finish.
Deleting SnapCenter Standard or Advanced capacity
licenses
You can delete SnapCenter Standard or Advanced capacity licenses when you want to replace an
existing license or when the license is no longer required.
Before you begin
You must have SnapCenter Admin privileges.
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, select the license you want to delete, and then click
the Delete icon.
23
Managing your storage system connections
Before you can perform backup, restore, clone and provisioning operations with SnapCenter, you
must set up your storage system connections so that you can connect to ONTAP storage systems.
What SVMs are
Storage Virtual Machines (SVMs, formerly known as Vservers) contain data volumes and one or
more data logical interfaces (LIFs) through which they serve data to the clients. SVMs can also have
multiple management LIFs. Before you can perform backup, restore, and clone operations, you must
set up your SVMs.
SVMs securely isolate the shared virtualized data storage and network, and each SVM appears as a
single dedicated server to the clients. Each SVM has a separate administrator authentication domain
and can be managed independently by its SVM administrator.
In a cluster, SVMs facilitate data access. A cluster must have at least one SVM to serve data. SVMs
use the storage and network resources of the cluster. However, the volumes and LIFs are exclusive to
the SVM. Multiple SVMs can coexist in a single cluster without being bound to any node in a cluster.
However, they are bound to the physical cluster on which they exist.
Setting up storage system connections
Before you can perform backup, restore, clone, and provisioning operations with SnapCenter, 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.
•
If you are installing SnapCenter Plug-in for Microsoft Windows on a SQL Server host, that
installation must be completed before you add a storage system connection.
•
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
•
Adding Storage Virtual Machines (SVMs) in vCenter
SVMs that are added using the SnapCenter GUI are also listed in the SnapCenter Plug-in for
VMware vSphere GUI in vCenter. SVMs that are added using the SnapCenter Plug-in for
VMware vSphere GUI in vCenter are also listed in the SnapCenter GUI.
•
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, or an
operation fails. These two features are available only if you choose ONTAP Cluster or ONTAP
SVM as the storage type.
24 | SnapCenter Software Administration Guide
•
Data Fabric Solution for Cloud Backup
If you are configuring connections for the Data Fabric Solution for Cloud Backup, you must
create connections to each AltaVault system and one to an ONTAP Cluster.
•
NAS File Services
If you are configuring connections for NAS File Services, you must create connections to each
ONTAP cluster.
•
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 Storage Virtual Machine (SVM) as
well as the source SVM.
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.
Steps
1. In the left navigation pane, click Storage Systems.
2. In the Storage Systems page, click New.
Managing your storage system connections | 25
3. In the New Storage Connection wizard, provide the following information:
26 | SnapCenter Software Administration Guide
For this field…
Do this…
Storage Type
Select ONTAP SVM, ONTAP Cluster, or AltaVault.
If you are configuring connections for SnapCenter application
plug-ins, choose ONTAP SVM as the storage type.
If you are configuring connections for NAS file services data, you
must add connections to each AltaVault system and to an ONTAP
Cluster. For each AltaVault system, choose AltaVault as the
storage type, and choose ONTAP Cluster as the second storage
type.
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 to ensure the following updates are
made:
Platform
•
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
Select either FAS or All Flash FAS, or ONTAP Cloud or ONTAP
Select.
If you check 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
Do one of the following:
•
ONTAP: Enter the credentials used (usually vsadmin) to access
the storage system. Use vsadmin when adding a SVM; use
admin when adding a cluster.
•
AltaVault: Enter the role-based access control credentials you
entered in AltaVault.
Site
Applicable only if you choose ONTAP Cluster or AltaVault as
your storage type. Enter the physical site name, for example, the
data center city. The site you enter is displayed in the SnapCenter
interface.
Protocol
Select the protocol used for connection to the SVM that was
configured during SVM setup, typically HTTPS.
Managing your storage system connections | 27
For this field…
Do this…
Port
Enter the port that the storage system accepts.
The defaults typically work.
If you are configuring the AltaVault connection, enter the
AltaVault port.
Timeout
Applicable only if you choose ONTAP Cluster, ONTAP SVM, or
AltaVault as the storage type. Enter the time in seconds that should
elapse before communication attempts are halted. The default
value is 60 seconds.
If you have questions about these values, consult your storage administrator.
4. Optional: If the SVM has multiple management interfaces, select the Preferred IP address check
box, and then enter the preferred IP address for SVM connections.
Note: If you have more than one iSCSI or FC session configured per SVM connected to the
host, then use the host device for multipathing rather than using the native device. While
performing a restore, clone, mount, or backup verification operation, if the storage system and
the host have iSCSI and FC configured together, then FC is preferred.
ONTAP 9 Cluster Management Using OnCommand System Manager
5. AutoSupport and EMS. 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 AutoSupport check box, the EMS messages check box is also selected
because EMS messaging is required to enable AutoSupport notifications.
6. Click OK.
Modifying your storage system connections
You can use SnapCenter to modify your storage system connections when you want to change the
user name, password, port, protocol, timeout period, preferred IP address, or messaging options
associated with the storage system.
About this task
You can modify storage connections for an individual user or for a group. If you belong to one or
more groups with permission to the same storage system, the storage connection name is displayed
multiple times in the storage connection list; once for each group with permission to the storage
system. The name of the group to which permission is assigned is displayed in the Domain Group
column. If permission to the storage system is assigned directly to you, the Domain Group column
remains blank.
Steps
1. In the left navigation pane, click Storage Systems.
2. In the Storage Connections list, select a storage system, and then click Modify.
3. In the Modify Storage Connections window, provide the information you want to change, and
then click OK.
Note: You cannot change the name of the storage system.
28 | SnapCenter Software Administration Guide
Deleting your storage system connections
You can use SnapCenter to delete any unused storage system connections. You might delete a storage
system when you are replacing it with a different storage system connection.
About this task
You can delete storage connections for an individual user or for a group. If you belong to one or more
groups with permission to the same storage system, the storage system name is displayed multiple
times in the storage connection list; once for each group with permission to the storage system. The
name of the group to which permission is assigned is displayed in the Domain Group column. If
permission to the storage system is assigned directly to you, the Domain Group column remains
blank.
Attention: When you delete a storage connection, all operations for that storage device will fail.
Steps
1. In the left navigation pane, click Storage Systems.
2. In the Storage Connections list, select a storage system , and then click Delete.
Viewing storage controller SnapManager Suite license
status
You can view the storage controller license status to determine whether a SnapManager Suite license
is installed on a FAS or All Flash FAS platform, and to identify which storage systems require
SnapManager Suite licenses.
About this task
SnapManager Suite licenses apply only to FAS and All Flash FAS SVMs on primary storage
systems.
Steps
1. In the left navigation pane, click Storage Systems.
2. In the Storage Connections list, locate the Controller License column.
The Controller License column displays the following statuses:
Indicates that a SnapManager Suite license is installed on a FAS or All
Flash FAS primary storage system.
Indicates that a SnapManager Suite license is not installed on a FAS or
All Flash FAS primary storage system.
Managing your storage system connections | 29
Not applicable
Indicates that a SnapManager Suite license is not applicable for this
controller. This message is displayed for the following storage:
•
AltaVault
•
Cloud ONTAP
•
ONTAP Select
•
Secondary storage
30
Managing virtualization plug-ins
After you install the SnapCenter Plug-in for VMware vSphere, you might need to update the
configuration information for the plug-in.
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.
31
Using role-based access control
SnapCenter provides centralized control and oversight for SnapCenter administrators, while
empowering individual application administrators to manage backup, restore, and cloning functions
through the use of roles and their access permissions.
Types of role-based access control in SnapCenter
SnapCenter role-based access control (RBAC) enables the SnapCenter administrator to create roles
and set access permissions. This centrally managed access empowers application administrators to
work securely within delegated environments. Configuring SnapCenter 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.
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 several predefined roles with permissions already assigned. You
can assign users or groups of users to these existing 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 by clicking Settings > User Assets.
This screen assigns permissions for access to SnapCenter objects such as hosts, storage
connections, and resource groups. You cannot change the permissions of the
SnapCenterAdmin role.
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 by clicking Settings > Roles.
Note: If you create a custom role, it must contain all the permissions of the
SnapCenterAdmin role. If you only copy some of the permissions, for example, Host
add or Host remove, you will not be able to 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.
32 | SnapCenter Software Administration Guide
SnapCenter Plug-in for VMware vSphere RBAC
SnapCenter 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.
Application-level RBAC
SnapCenter uses Run As credentials to ensure that authorized SnapCenter users also have
application-level 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 being
performed.
ONTAP permissions
You should ensure that you have vsadmin account permissions to access the storage system.
SnapCenter role-based access control
SnapCenter role-based access control (RBAC) enables you to manage or create roles, assign
permissions to those roles, and add domain-created and operating system-created users or groups to
these roles, to centrally manage SnapCenter access.
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
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
SnapCenter Plug-in for VMware vSphere ships with the following predefined VMware vSphere roles
in vCenter. You can either assign users and groups to these roles or create new ones.
•
SCV Administrator
Using role-based access control | 33
•
•
•
SCV Backup
SCV Restore
SCV View
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)
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. Before adding users to these pre-defined roles, it is helpful to understand
which permissions are enabled and which permissions are not enabled.
SnapCenter includes the following pre-defined roles:
•
SnapCenter Admin role
•
Backup and Clone Viewer role
•
App Backup and Clone Admin role
•
Infrastructure Admin role
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.
34 | SnapCenter Software Administration Guide
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
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 Installation
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.
Using role-based access control | 35
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
Resource
No
No
Yes
Yes
No
Plug-in Installation
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
36 | SnapCenter Software Administration Guide
Permissions
Enabled
Create
Read
Update
Delete
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 Installation
Yes
Not
applicable
Not
applicable
Not
applicable
Not
applicable
Migration
No
Not
applicable
Not
applicable
Not
applicable
Not
applicable
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.
Using role-based access control | 37
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.
Creating a new role
In addition to using the existing SnapCenter roles, you can create your own, customize the
permissions, and assign users or groups to the role.
Steps
1. In the left navigation pane, click Settings.
2. Ensure that the Roles page is selected.
3. Click New to launch the New Role wizard.
4. Provide the necessary information and click OK.
After you finish
You can now add users or groups to the role.
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 role-based access control
efficiencies.
You can also assign Run As credential maintenance to a user.
If you are planning to replicate Snapshot copies to a mirror or vault, 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.
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 you want to assign 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.
38 | SnapCenter Software Administration Guide
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.
Modifying a role
You can modify a SnapCenter role to add or remove users or groups, change the permissions
associated with the role, or rename it. It is especially useful to modify roles when you want to change
or eliminate the permissions used by an entire role.
About this task
You cannot modify or remove permissions for the SnapCenterAdmin role.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Roles.
3. From the Role name field, click the role you want to modify and then click Modify.
4. Use the Modify Role wizard to alter the permissions, users, and groups, as needed.
Application-level role-based access control
Application-level role-based access control (RBAC) enables SnapCenter users to provide Run As
account credentials for access to applications such as SQL Server or Oracle databases.
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.
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.
Using role-based access control | 39
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.
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.
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.
Before you begin
For NAS file services for CIFS shares only (not for NFS), you must create Run As credentials and
configure a CIFS server for the ONTAP cluster.
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
40 | SnapCenter Software Administration Guide
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.
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.
Using role-based access control | 41
For this field…
Do this…
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.
For Data Fabric Solution for Cloud Backup for CIFS shares only,
select Windows as the mode.
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.
Configuring Run As account credentials for an individual SQL Server
resource
You can configure Run As account credentials to perform data protection jobs on individual SQL
Server resources for each user. While you can configure the credentials globally, you might want to
do this only for a particular resource.
About this task
•
If you are using Windows credentials for authentication, you must set up your Run As account
before installing plug-ins.
However, if you are using an SQL Server instance for authentication, you must add the Run As
account after installing plug-ins.
•
If you have enabled SQL authentication while setting up the Run As credentials, the discovered
instance or database is shown with a red color lock icon.
If the lock icon appears, you must specify the instance or database credentials to successfully add
the instance or database to a resource group.
•
You must assign the Run As account to a role-based access control (RBAC) user without
sysadmin access when the following conditions are met:
◦
The Run As account is assigned to an SQL instance.
◦
The SQL instance or host is assigned to an RBAC user.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Run As Credentials.
3. To add a new Run As account, click New.
4. In the Run As Credentials page, configure the credentials for the Run As account:
For this field…
Do this…
Run As name
Enter a name for the Run As account.
42 | SnapCenter Software Administration Guide
For this field…
Do this…
Username/Password
Enter the user name and password that are to be used for SQL
Server authentication.
Add the domain name as the prefix to the user name.
Authentication mode
Select the SQL Server authentication mode.
You can also choose Windows authentication if the Windows user
has sysadmin privileges on the SQL server.
Host
Select the host.
SQL Server Instance
Select the SQL Server Instance.
5. Click OK to add the Run As account..
6. In the left navigation pane, click Resources.
7. In the Resources page, select Instance from the View drop-down list.
a. Click
, and then select the host name to filter the instances.
b. Click
to close the filter pane.
Note: The Run As account option does not apply to databases and availability groups.
8. In the Instance Protect page, protect the instance, and if required, click Configure Run As
Credentials.
If the user who is logged in to the SnapCenter Server does not have access to SnapCenter Plug-in
for Microsoft SQL Server, then the user has to configure the Run As credentials.
Configuring Run As account credentials for an Oracle database
You must configure Run As account credentials that are used to perform data protection operations
on Oracle databases.
About this task
If you have enabled an Oracle database authentication, a red color lock icon is shown in the resources
view. You must configure database Run As credentials to be able to protect the database or add it to
the resource group to perform data protection operations.
Note: While creating a Run As account if you specify wrong credentials, an error message is
displayed. You must click Cancel and then retry.
Steps
1. In the left navigation pane, click Resources, and then select the appropriate plug-in from the
drop-down list.
2. In the Resources page, select Database from the View drop-down list.
Click
and select the host name and the database type to filter the resources. You can then click
to close the filter pane.
3. Select the database, and then click Database Settings > Configure Database.
4. In the Configure database settings section, from the Use exisiting Run As drop-down list select
the Run As account that should be used to perform data protection jobs on the Oracle database.
Using role-based access control | 43
You can also create a Run As credential by clicking
.
Note: The database port number is auto populated.
5. In the Configure ASM settings section, from the Use exisiting Run As drop-down list select the
Run As account that should be used to perform data protection jobs on the ASM instance.
You can also create a Run As credential by clicking
.
Note: The ASM instance port number is auto populated.
6. In the Configure RMAN catalog settings section, from the Use exisiting Run As drop-down list
select the Run As account that should be used to perform data protection jobs on the Oracle
Recovery Manager (RMAN) catalog database.
You can also create a Run As credential by clicking
.
In TNSName, enter the Transparent Network Substrate (TNS) file name that will be used by the
SnapCenter Server to communicate with the database.
7. In Preferred RAC Nodes, specify the Real Application Cluster (RAC) nodes preferred for
backup.
The preferred nodes might be one or all cluster nodes where the RAC database instances are
present. The backup operation is triggered only on these preferred nodes in the order of
preference.
8. Click OK.
Related tasks
Setting up your Run As credentials on page 39
44
Using Application Request Routing and Network
Load Balancing
Application Request Routing (ARR) is a Microsoft Internet Information Services (IIS) feature that
you can use to enable SnapCenter load balancing across multiple servers with a user interface.
Network Load Balancing (NLB) is a Microsoft feature that SnapCenter uses to provide server high
availability.
You can perform certain tasks related to ARR and NLB.
•
Determining whether ARR was enabled during the SnapCenter installation.
•
Viewing NLB status.
Application Request Routing requirements
Application Request Routing (ARR) requires specific IIS features and configuration. You should
understand the basics of how ARR works and how you can set it up to support SnapCenter.
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.
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 Deploy 2.0
4. Web Farm Framework 2.0 (requires IIS and Web Platform Installer 3.0
Using Application Request Routing and Network Load Balancing | 45
5. Web Platform Installer 5 (upgrade from 3.0)
6. Web Deploy 3.5 (upgrade from 2.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
Determining load balancing status and Application Request
Routing enablement
A SnapCenter web farm is a web farm that groups IIS instances to perform SnapCenter load
balancing. Viewing the Load Balancer page helps you determine the status of load balancing and
determine whether Application Request Routing (ARR) was enabled during the SnapCenter
installation.
Before you begin
•
You have installed Microsoft Application Request Routing and any associated components.
•
You have configured Application Request Routing automatically during SnapCenter installation.
•
You have set up the SnapCenter Server Farm as part of the SnapCenter installation.
This is done automatically if you chose to enable ARR during the installation.
•
You have defined the ARR load balancing algorithm using IIS Manager.
About this task
Every instance of the IIS Server where SnapCenter is deployed requires the same SnapCenter farm
configuration.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Load Balancer.
3. View the NLB members and the state of ARR.
46
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 | 47
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:
48 | SnapCenter Software Administration 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 | 49
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.
50 | SnapCenter Software Administration Guide
Starting an iSCSI session on page 46
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 | 51
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.
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.
52 | SnapCenter Software Administration Guide
•
•
•
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.
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.
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.
Provisioning storage on Windows hosts | 53
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:
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:
54 | SnapCenter Software Administration Guide
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.
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.
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.
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.
Provisioning storage on Windows hosts | 55
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.
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.
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.
56 | SnapCenter Software Administration Guide
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.
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.
Provisioning storage on Windows hosts | 57
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.
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.
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
58 | SnapCenter Software Administration Guide
•
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.
•
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.
Provisioning storage on Windows hosts | 59
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.
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.
60 | SnapCenter Software Administration Guide
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.
•
“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 Windows Cmdlet Reference Guide
61
Working with managed hosts
You can add hosts and install SnapCenter plug-in packages, add a verification server, remove hosts,
migrate SnapCenter Plug-in for Microsoft SQL Server backup jobs, and update host to upgrade plugin packages or add new plug-in packages.
You can perform the following tasks related to hosts:
Tasks
SnapCenter
Plug-in for
Microsoft
SQL Server
SnapCenter
Plug-in for
Oracle
Database
SnapCenter Plug-in
for Microsoft
Windows
SnapCenter
Custom Plug-ins
Add hosts and
install plug-in
package
For details, see
installation
information.
✓
✓
✓
✓
Configure
plug-in
packages and
add a
verification
server in one
step
For details, see
installation
information.
✓
Update ESX
information for
a host
✓
Suspend
schedules and
place hosts in
maintenance
mode
✓
✓
✓
✓
Modify hosts
by adding
additional
plug-ins,
upgrading
plug-ins, or
removing plugins from
selected hosts
✓
✓
✓
✓
Remove hosts
from
SnapCenter
✓
✓
✓
✓
62 | SnapCenter Software Administration Guide
Tasks
SnapCenter
Plug-in for
Microsoft
SQL Server
SnapCenter
Plug-in for
Oracle
Database
SnapCenter Plug-in
for Microsoft
Windows
SnapCenter
Custom Plug-ins
Start and
restart plug-in
services
✓
✓
✓
✓
Import Data
You can use
the SnapCenter
import feature
to move
existing
SnapCenter
Plug-in for
Microsoft SQL
Server backup
jobs to
SnapCenter.
After
importing, you
can run them
in SnapCenter
the same way
you would
perform
different
operations
using
SnapCenter
plug-in.
For details, see
import
information.
✓
If you are using the SnapCenter Plug-in for NAS File Services, none of these options apply.
Related information
Installing and setting up SnapCenter
Importing SnapManager data into SnapCenter
Viewing details about managed hosts
The Host Details page enables you to determine whether a host managed by SnapCenter has a
verification host, whether the host is registered with Virtual Storage Console for VMware vSphere
(VSC), and whether there are any issues that need attention. Viewing host details can help you
troubleshoot.
Steps
1. In the left navigation pane, click Hosts.
2. In the Hosts page, click Managed Hosts.
Working with managed hosts | 63
3. In the Managed Hosts page, select the host for which you want to see additional details.
4. Click Details or double-click the host name.
5. In the Host Details page, view the following details for the selected host:
Name
Name of the host you selected.
IP
Name of the IP address for this host.
System
Indication of whether the host is stand-alone or clustered. For LINUX RAC, this is the
RAC node.
OS
The host operating system type.
Port
The communication port used.
Run As
Run As account name used for credentials. For LINUX hosts, root user credentials or a
sudo user account must be used.
Verification server
For SQL Server, indication of whether a verification server is configured for the host.
Virtualization host configured state
For SQL Server, indication of whether an application host is registered with VSC.
Issues
Any issues specific to the selected host. If there are no issues for the selected host, this
section is not displayed.
Modifying hosts and plug-ins
You can modify a host to add plug-ins when no plug-ins have been associated with a selected host.
You can also add additional plug-ins, upgrade plug-ins, or remove plug-ins associated with a selected
host that already has plug-ins associated with it.
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 you want to modify.
4. Click Modify.
5. Select whether you want to add plug-ins, upgrade plug-ins, remove plug-ins, or modify the plugin port.
6. Select Skip Prechecks if you do not want to validate whether the host meets the requirements to
install or upgrade the plug-in.
7. Select or enter information as needed and continue clicking Next.
8. Click Finish.
64 | SnapCenter Software Administration Guide
Refreshing virtual machine information
You must refresh your virtual machine information when Virtual Storage Console for VMware
vSphere credentials change or the database host restarts.
About this task
Refreshing you virtual machine information in SnapCenter initiates communication with Virtual
Storage Console for VMware vSphere and obtains vCenter credentials from VSC.
RDM-based disks are managed by the SnapCenter Plug-in for Microsoft Windows, which is installed
on the database host. To manage RDMs, the SnapCenter Plug-in for Microsoft Windows
communicates with the VSC server that manages the database host.
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 you want to update.
4. Click Refresh VM.
Starting and restarting plug-in services
Starting SnapCenter plug-in services enables you start services if they are not running or restart them
if they are running. You might want to restart services after maintenance has been performed.
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 you want to start.
4. From the Information section, select the plug-in and click Start Service or Restart Service.
Suspending schedules on hosts to place them in
maintenance mode
When you want to prevent the host from running any SnapCenter scheduled jobs, you can place your
host in maintenance mode. You must do this before you upgrade plug-ins. You might want to do this
if you are performing maintenance tasks on hosts.
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 you want to suspend.
4. From the Information section, select the plug-in and click Suspend Schedule to place the host
for this plug-in in maintenance mode.
Working with managed hosts | 65
Note: You do not have to stop the plug-in service first; the plug-in service can be in a running
or stopped state.
After you suspend schedules on the host, the Managed Hosts page shows “Suspended” in the
Overall status field for the host.
After you finish
After you complete host maintenance, bring the host out of maintenance mode by clicking Activate
Schedule.
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.
66 | SnapCenter Software Administration Guide
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.
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.
Verifying the supported configurations for SnapCenter Plugins Package for Linux
The configuration checker tool helps you to identify and verify the configurations supported by the
SnapCenter Plug-ins Package for Linux. This tool helps you to verify the supported SAN or NAS
configurations, host utilities, and file system types.
Steps
1. Log in to the host.
2. Browse to the folder: /opt/NetApp/snapcenter/spl/plugins/scu/scucore/
configurationcheck/
3. Run the configuration checker tool:
sh Config_Check.sh
4. Check if the configuration is supported by SnapCenter Plug-ins Package for Linux.
67
Managing the SnapCenter Server repository
Information related to various operations performed from SnapCenter is stored in the SnapCenter
repository. You must create backups of the repository to save and recover SnapCenter Server from
data loss.
You can perform the following tasks to protect the SnapCenter repository:
•
Protect the SnapCenter repository by setting the configuration that is required to create a backup
of it.
•
Obtain the SnapCenter repository backups that were backed up on schedule.
•
Restore the SnapCenter repository when required.
•
Migrate the SnapCenter repository to a different disk.
Prerequisites for protecting the SnapCenter repository
Your environment must meet certain prerequisites to protect the SnapCenter repository.
•
Managing Storage Virtual Machine (SVM) connections
You must configure the storage credentials.
•
Provisioning hosts
At least one NetApp storage disk should be present on the SnapCenter repository host. If a
NetApp disk is not present on the SnapCenter repository host, you must create one.
For details about adding hosts, setting up SVM connections, and provisioning hosts, see the
installation instructions.
•
To include SnapCenter repository in the SQL Server Availability Group (AG), you must perform
the following actions:
1. You must change the state of the NSM database to full recovery mode.
2. You must add NSM database to AG.
3. You must change the DBServer value in the web.config file to include the AG listener and
port number in AG listener, port format. For example, <add key="DBServer"
value="SCAGLIST2, 8644"/>
4. You must create a new SQL login in <domain>\<host name>$ format. For example,
DNAME\SC-SQL3$, DNAME\SC-SQL4$ where, DNAME is the domain name and SCSQL3 and SC-SQL4 are the host names. You must create SQL logins on all the instances of
the AG replica.
Note: Host name refers to SnapCenter Server name. In case of 2 node Application Request
Routing (ARR) or Network Load Balancing (NLB) configuration, you must add users using
both the SnapCenter Server host names.
Related information
Installing and setting up SnapCenter
68 | SnapCenter Software Administration Guide
Configuring the SnapCenter repository for protection
Configuring the SnapCenter repository helps protect it from data loss. You can configure the
repository by running the Protect-SmRepository cmdlet.
About this task
While upgrading to SnapCenter 3.0, the repository database is upgraded from Microsoft SQL Server
to MySQL Server. However, after upgrading the repository database, the protection of the repository
database is disabled and all the schedules related to repository operations are deleted. You must run
the Protect-SmRepository command to protect the repository and create new schedules.
Note: If you are upgrading from SnapCenter 2.0 installation with MySQL and NAS file server
protection to SnapCenter 3.0 with MySQL and NAS file server protection, you do not have to run
the Protect-SmRepository command to protect the repository.
The command accomplishes the following tasks:
•
Moves the SnapCenter repository from one disk to another disk; the destination must be NetApp
•
Creates a resource group and a policy
•
Creates a backup schedule for the SnapCenter repository
Steps
1. Launch PowerShell.
2. From the command prompt, enter the following command, and then provide credentials to
connect to the SnapCenter Server:
Open-SMConnection
3. Enter the following command to list the available PowerShell modules: Get-Module
4. Enter the following command to import the SnapCenter PowerShell module:
Import-Module SnapCenter
5. Protect the repository using the Protect-SmRepository command and options:
Protect-SmRepository [-HostName] string[-Path] string[Schedule]Hashtable
[[-RetentionCount] Int32] [[-CatalogBackupPath] string]
The options are as follows:
HostName
Specifies the SnapCenter database host name. If the SnapCenter database is hosted
by a failover cluster instance (FCI), then specify the FCI owner host name.
Path
Specifies the NetApp destination disk path for storing MySQL dumps. The use of
virtual disks, such as RDM LUNs, is not supported for repository protection.
Schedule
Specifies the backup schedule information.
Options are as follows:
ScheduleType
Specifies the backup schedule type. Possible options are Hourly, Daily, Weekly,
Monthly.
Managing the SnapCenter Server repository | 69
StartTime
Specifies the scheduled backup start time. The default is the current time.
EndTime
Specifies the scheduled end time.
RetentionCount
Specifies the number of backups to retain. By default, seven backups are retained.
CatalogBackupPath
Specifies an NFS mount point on ONTAP storage. The NFS mount point must be
accessible to all backup catalog servers.
This parameter is used only when you have NAS file services installed.
The following command configures the SnapCenter database on a specific host in a specific
location for hourly protection:
Protect-SmRepository -HostName NB-MVADEV057.nbsdsm.mycompany.netapp.in
-Path E:\DBs -Schedule
@{"ScheduleType"="hourly";"StartTime"="10/21/2016 5:18 PM"}
Getting backups of the SnapCenter database
You can display a list of backups created by running the Get-SmRepositoryBackups command.
The database backups are created according to the schedule specified in the ProtectSmRepository cmdlet. You can also create database backups from the SnapCenter GUI.
Steps
1. Launch PowerShell.
2. From the command prompt, enter the following command, and then provide credentials to
connect to the SnapCenter Server:
Open-SMConnection
3. List all available SnapCenter database backups using the Get-SmRepositoryBackups
command and options:
Get-SmRepositoryBackups [[-HostName] string] [[-SMSbaseUrl] string]
The options are as follows:
HostName
Specifies the SnapCenter database host name. If the SnapCenter database is hosted
by a failover cluster instance (FCI), the host name of the FCI owner must be
specified.
SMSbaseUrl
Specifies the SnapCenter Server URL. This URL is required when you are
executing the PowerShell cmdlet from a database host.
70 | SnapCenter Software Administration Guide
Restoring the SnapCenter database backup
You can restore the SnapCenter database when required by running the RestoreSmRepositoryBackup comdlet.
Steps
1. Launch PowerShell.
2. From the command prompt, enter the following command, and then provide credentials to
connect to the SnapCenter Server:
Open-SMConnection
3. Restore the backup using the Restore-SmRepositoryBackup command and options:
Restore-SmRepositoryBackup [-HostName] string [-BackupName] string [[SMSbaseUrl] string]
The options are as follows:
HostName
Specifies the SnapCenter database host name. If the SnapCenter database is hosted
by a failover cluster instance (FCI), the host name of the FCI owner host name must
be specified.
SMSbaseUrl
Specifies the SnapCenter Server URL. This URL is required when you are
executing the PowerShell command from a database host.
BackupName
Specifies the name of the backup that is to be restored.
The following cmdlet restores the SnapCenter MySQL database:
C:\PS>Restore-SmRepositoryBackup -BackupName
MYSQL_DS_SC_Repository_mva-x3550-s09_09-15-2016_10.32.00.4445
The following cmdlet restores the SnapCenter SQL database:
Restore-SmRepositoryBackup –BackupName DS_SC_Repository_NB-MVADEV057_05-15-2015_12.32.27.8228
Migrating the SnapCenter repository
You can migrate the SnapCenter repository, or NSM, from the default location to another disk. You
might migrate the repository when you want to relocate it to a disk with more space.
Steps
1. Stop the MYSQL57 service in Windows.
2. Locate the MySQL data directory.
Managing the SnapCenter Server repository | 71
You can usually find the data directory at C:\ProgramData\MySQL\MySQL Server
5.7\Data.
3. Copy the MySQL data directory to the new location, for example, E:\Data\nsm.
4. Right click on the new directory, and then select Properties > Security to add the Network
Service local server account to the new directory, and then assign the account full control.
5. Rename the original database directory, for example, nsm_copy.
6. From a Windows command prompt, create a symbolic directory link by using the mklink
command.
Example
"mklink /d "C:\ProgramData\MySQL\MySQL Server 5.7\Data\nsm" "E:\Data
\nsm" "
7. Start the MYSQL57 service in Windows.
8. Verify that the database location change is successful by logging in to SnapCenter and checking
database entries, or by logging in to the MySQL utility and connecting to the new NSM database.
9. Delete the original, renamed, database directory (nsm_copy).
72
Using SnapCenter reporting capabilities
SnapCenter provides a variety of reporting options that enable you to monitor and manage your
system health and operation success.
Centralized reporting options
SnapCenter makes it easy for you to monitor the health of your systems and your data protection job
status, get more detailed information about data protection jobs, monitor SnapCenter activity, and use
system log files for troubleshooting.
Dashboard
From the SnapCenter left navigation pane, the Dashboard gives you a first glance into the health of
your system, the status of your data protection jobs (backup, restore, and clone), your database
protection status, and a SnapVault status.
You can also request more detailed reports about data protection jobs from the Dashboard by clicking
one of the pie charts. The report you generate from here pertains only to the jobs you clicked.
Reports
From the SnapCenter left navigation pane, the Reports page offers a more detailed view into data
protection jobs (backup, restore, and clone) and plug-in information. You can run reports about all
jobs of the selected type (backup, clone, or restore), jobs for a specific host, jobs for a specific
resource group, jobs for a specific policy, jobs with a specific status (completed, failed, or warning),
and jobs for a specific resource. The plug-in report provides details about resource protection. You
can export reports in a variety of formats and print them.
Monitor options
From the SnapCenter left navigation pane, the Monitor page enables you to view the following
details:
Jobs
Displays information about host, resource group, policy, plug-in installation and
uninstallation, provision, discovery, backup, restore, clone, and verification jobs. You can
filter this view based on either start and end date, type of job, or status. You can also get
additional details by clicking Details after selecting a job. The Details window enables
you to view log details. You can also view the log details by clicking View Logs. For
backup, clone, and restore jobs, you can click Report and view the detailed report for that
specific job.
Schedules
Displays information about schedules you have created in your SnapCenter environment.
In the Schedule section, when you select a specific resource group from the drop-down
box and select a schedule type, the details about the schedule (such as the policy that
initiated the schedule, the host, the start time, the schedule expire time, the next run, and
the last run of the schedule) are displayed.
Events
Displays information about system activity, such as when a user creates a resource group
or when the system initiates activities, such as creating a scheduled backup. All job
information appears in the Events page. For example, when a backup job starts, a “backup
start” event appears. When the backup is complete, a “backup complete” event appears.
Using SnapCenter reporting capabilities | 73
Logs
Displays SnapCenter Server and plug-in logs. Plug-in logs are available by host and plugin. You can also filter by a specific source or message or select a log level. You can use
these logs for advanced troubleshooting.
Related concepts
Monitoring SnapCenter jobs on page 80
Monitoring SnapCenter schedules on page 82
Monitoring SnapCenter events on page 82
Monitoring SnapCenter logs on page 83
Information provided in Dashboard reports
The Dashboard gives you a first glance into the health of your system, the status of your data
protection jobs, SnapVault status for Microsoft SQL and Oracle databases, and NAS file services
protection status. To understand the information provided in SnapCenter reports, it is helpful for you
to know what information is available and what it means. Similar reports display on the Reports
pages.
Information displayed in the Dashboard view depends on the roles assigned to the user that is
currently logged in to SnapCenter. Some tiles or information in the tiles might not display if a role
assigned to a user does not have permission to view that information.
Host status tile
The host status tile gives you information about all hosts you have added to SnapCenter and the plugins you have installed on these hosts.
Note: After adding a new host or after starting SnapCenter, it might take several minutes for the
host status to be updated in reports.
Host status
Host up
The host is up and communicating with SnapCenter.
Host down
SnapCenter is not able to communicate with this host.
Plug-ins inactive
These hosts are up and communicating with SnapCenter but do not have
plug-ins running.
Plug-in
unsupported
These hosts have one or more unsupported plug-ins. An unsupported plug-in
is not compatible with this version of SnapCenter.
Plug-in upgradable
These hosts have one or more plug-ins that you can upgrade.
Storage Virtual Machine tile
The Storage Virtual Machine tile displays the total number of SVMs managed by the user currently
logged in to SnapCenter.
Storage Virtual Machines
Total
Specifies the total number of Storage Virtual Machines (SVMs) currently
managed by SnapCenter.
74 | SnapCenter Software Administration Guide
Licensed Capacity tile
The Licensed Capacity tile displays information about total licensed capacity, used capacity, capacity
threshold alerts and license expiration alerts for SnapCenter Standard or Advanced licenses.
If you are using only a controller-based license, or if no capacity licenses are required for your
environment, the Licensed Capacity tile is not displayed in the Dashboard.
Licensed Capacity
In use
Specifies the amount of capacity currently in use.
Notify
Specifies the capacity threshold at which notifications are displayed on the
Dashboard, and, if configured, when email notifications are sent.
Licensed
Specifies the amount of licensed capacity.
Over
Specifies the amount of capacity that has exceeded the licensed capacity.
Backup, restore, and clone job tiles
The backup, restore, and clone job tiles give you information about the data protection jobs you have
run during the specified time. You can customize the time frame for the report by using the dropdown list located in each tile. The default report provides information about data protection jobs run
for the past seven days.
Backup, restore, and clone jobs
Running
Specifies the number of jobs that are currently running.
Failed
Specifies the number of jobs that have failed.
Warning
Specifies the number of jobs that have experienced an error.
Completed
Specifies the number of jobs that have successfully completed.
Microsoft SQL Server Database Policy-Based Protection tile
The Microsoft SQL Server Database Policy-Based Protection tile provides information about the
databases you have on your primary storage system, whether they are associated with resource
groups, and if they are being successfully backed up.
Microsoft SQL Server Database Policy-Based Protection
Unprotected
Specifies the number of databases that are not part of any resource group
and have not been backed up.
Not backed up
Specifies the number of databases that are part of a resource group, but a
backup has not been performed during the specified time period.
Unprotected, backup
failed
Specifies the number of databases that are part of a resource group that has
run a backup during the specified time period, but the backup failed.
Protected
Specifies the number of databases in a resource group that have been
successfully backed up during the specified time period.
Microsoft SQL Server Database SnapVault Summary tile
The Microsoft SQL Server Database SnapVault Summary tile gives you information about Microsoft
SQL databases being backed up to secondary storage systems using SnapVault technology, as well as
the status of the SnapVault relationships.
Using SnapCenter reporting capabilities | 75
Microsoft SQL Server Database SnapVault Summary
SnapVault not
configured
The database is part of one or more resource groups that are not
configured for backups to be transferred to a SnapVault destination.
Successful SnapVault
transfers
Specifies the number of databases that have been successfully transferred
to a SnapVault destination.
Failed SnapVault
transfers
Specifies the number of databases with backups that have failed to transfer
to a SnapVault destination.
Microsoft SQL Database Clone Savings tile
The Microsoft SQL Database Clone Savings tile provides you with information about storage space
savings achieved by using NetApp FlexClone technology. Clone savings is updated every hour and is
based on all clone jobs that use the Microsoft SQL Server database plug-in.
Oracle Database Policy-Based Protection tile
The Oracle Database Policy-Based Protection tile gives you information about the Oracle databases
you have on your primary storage system, whether they are associated with resource groups, and if
they are being successfully backed up.
Oracle Database Protection on Primary Storage
Unprotected, no
backups configured
Specifies the number of databases that are not part of any resource group
and have not been backed up.
Unprotected, not
backed up
Specifies the number of databases that are part of a resource group, but a
backup has not been performed during the specified time period.
Unprotected, backup
failed
Specifies the number of databases that are part of a resource group that has
run a backup during the specified time period, but the backup failed.
Protected
Specifies the number of databases in a resource group that have been
successfully backed up during the specified time period.
Oracle Database SnapVault Summary tile
The Oracle Database SnapVault Summary tile gives you information about Oracle databases being
backed up to secondary storage systems using SnapVault and the status of the SnapVault
relationships.
Oracle Database SnapVault Summary
SnapVault not
configured
Specifies the database is part of one or more resource groups that are not
configured for backups to be transferred to a SnapVault destination.
Successful SnapVault
transfers
Specifies the number of databases that have been successfully transferred
to a SnapVault destination.
Failed SnapVault
transfers
Specifies the number of databases with a SnapVault relationship but with
updates that have failed.
Oracle Database Clone Savings tile
The Oracle Database Clone Savings tile provides you with information about storage space savings
achieved by using NetApp FlexClone technology. Clone savings is updated every hour and is based
on all clone jobs that use the Oracle database plug-in.
76 | SnapCenter Software Administration Guide
NAS File Services Policy-Based Protection tile
If you installed Data Fabric Solution for Cloud Backup for NAS file services protection, the NAS
File Services Policy-Based Protection tile provides you with information about the NAS volumes you
are protecting and if they are being successfully backed up.
NAS File Services Policy-Based Protection
Unprotected, no
backups configured
Specifies the number of volumes that have not been backed up.
Unprotected, not
backed up
Specifies the number of volumes that are not protected, and a backup has
not been performed during the specified time period.
Unprotected, backup
failed
Specifies the number of volumes for which a backup was run during the
specified time period, but the backup failed.
Protected
Specifies the number of volumes that have been successfully backed up
during the specified time period.
Requesting job status reports from the Dashboard
You can request reports about backup and restore jobs that have a particular status from the
Dashboard page. This is useful if you want to identify the total number of successful or failed jobs in
your SnapCenter environment.
Steps
1. In the left navigation pane, click Dashboard, and then select the appropriate plug-in from the
drop-down list.
2. Locate the pie chart for the job for which you want to obtain a job status report.
3. Click the pie slice representing the status for which you want a report.
Result
When you click the pie chart, you are redirected from Dashboard page to the Reports page. The
report displays only jobs with the status you selected. You can review the report or download it to
your local system.
Configuring your dashboard
You can modify the Dashboard display to best suit your SnapCenter configuration and information
needs.
Steps
1. In the left navigation pane, click Dashboard, and then select the appropriate plug-in from the
drop-down list.
2. Click Modify, select the tiles that you want to display in the Dashboard view, and then click
OK.
Using SnapCenter reporting capabilities | 77
Types of reports
SnapCenter provides customizable report options that provide you with details about your data
protection jobs and plug-in resource status.
Report type
Description
Backup Report
The Backup Report provides overall data about backup
trends for your SnapCenter environment, the backup success
rate, and some information about each backup performed
during the specified time. If a backup is deleted, the report
does not display any status information for the deleted
backup. The Backup Detail Report provides detailed
information about a specified backup job and lists the
resources successfully backed up and any that have failed.
Clone Report
The Clone Report provides overall data about clone trends
for your SnapCenter environment, the clone success rate,
and some information about each clone job performed
during the specified time. If a clone is deleted, the report
does not display any status information for the deleted
clone. The Clone Detail Report provides details about the
specified clone, including policy, resource group, clone host,
and clone job task status. If a task fails, the Clone Detail
Report displays information about the failure.
Restore Report
The Restore Report provides overall information about
restore jobs. The Restore Detail Report provides details
about a specified restore job, including host name, backup
name, job start and duration, and the status of individual job
tasks. If a task fails, the Restore Detail Report displays
information about the failure.
Plug-in Report
These reports provide protection details for resources
managed by all SnapCenter plug-in instances. You can see
an overview, details about databases outside of resource
groups (unprotected), databases that have not been backed
up during this report period, databases that belong to a
resource group for which backups have failed, and database
SnapVault status.
Configuring your reports
You might want to configure your reports according to a range of parameters, depending on the level
of detail and time span of information you require.
Steps
1. In the left navigation pane, click Reports.
2. If the Parameter view is not displayed, click the Toggle Parameters Area icon from the report
toolbar.
3. Specify the time range for which you want to run your report.
If you omit the end date, you retrieve all available information.
78 | SnapCenter Software Administration Guide
4. Filter your report information based on any of the following criteria:
•
•
•
•
•
Resource group
Host
Policy
Resource
Status
5. Click Apply.
Exporting or printing reports
Exporting SnapCenter reports enables you to view the report in a variety of alternative formats. You
can also print reports.
Steps
1. In the left navigation pane, click Reports.
2. From the reports toolbar:
If you want to...
Do this...
Preview a printable report
Click the Toggle Print Preview icon.
Export a report to an alternate
format
Choose a format from the Export icon drop-down list:
•
•
•
•
•
•
CSV
Excel
PDF
Rich Text Format
TIFF
Web Archive
3. To print a report, click the Print icon.
4. To view a specific report summary, scroll to the appropriate section of the report.
Setting the SMTP server for email notifications using Global
Settings
You can specify the SMTP server to use for sending data protection job reports to yourself or to
others. You can also send a test email to verify the configuration. The settings are applied globally for
any SnapCenter job for which you configure email notification.
About this task
This option configures the SMTP server for sending all data protection job reports. However, if you
want to have regular SnapCenter data protection job updates for a particular resource sent to yourself
or to others so that you can monitor the status of those updates, you can configure the option to email
the SnapCenter reports when you are creating a resource group.
Steps
1. In the left navigation pane, click Settings.
2. In the Settings page, click Global Settings.
Using SnapCenter reporting capabilities | 79
3. Enter the SMTP server and click Save.
4. To send a test email, enter the email address from and to which you will send the email, enter the
subject, and click Send.
Configuring the option to email reports
If you want to have regular SnapCenter data protection job updates sent to yourself or to others so
that you can monitor the status of those updates, you can configure the option to email the
SnapCenter reports when you are creating a resource group.
Before you begin
You must have configured your SMTP server on the Global Settings page under Settings.
Steps
1. In the left navigation pane, click Resources, and then select the appropriate plug-in from the
drop-down list.
2. Select the type of resource you want to view and click New Resource Group, or select an
existing resource group and click Modify to configure email reports for an existing resource
group.
3. In the Notification panel of the New Resource Group wizard, select from the pull-down menu
whether you want to receive reports always, on failure, or on failure or warning.
4. Enter the address the email is sent from, the address the email is sent to, and the subject of the
email.
80
Monitoring jobs, schedules, events, and logs
Viewing active jobs, scheduled tasks, events, and log information related to SnapCenter enables you
to monitor the health of your system, assess your data protection status, and use system log files for
troubleshooting.
You can perform the following tasks related to monitoring:
Using this page...
You can perform these tasks...
Jobs
View information about backup, clone, restore, and verification jobs.
You can filter this view based on start and end date, type of job,
resource group, policy, or SnapCenter plug-in. You can also get
additional details and log files for specified job.
Schedules
View backup, clone, or verification schedules that you created in your
SnapCenter configuration. You can filter this view by host, schedule
start date and time, schedule expiration date and time, and by job type.
Events
View information about SnapCenter system activities, such as when a
user creates a resource group or when the system initiates activities,
such as creating a scheduled backup. All job information appears in the
Events page. For example, when a backup job starts, a “backup start”
event appears. When the backup completes, a “backup complete” event
appears.
Logs
View SnapCenter Server and plug-in logs for troubleshooting.
Related concepts
Monitoring SnapCenter jobs on page 80
Monitoring SnapCenter schedules on page 82
Monitoring SnapCenter events on page 82
Monitoring SnapCenter logs on page 83
Monitoring SnapCenter jobs
You can view information about SnapCenter backup, clone, restore, and verification jobs. You can
filter this view based on start and end date, type of job, resource group, policy, or SnapCenter plugin. You can also get additional details and log files for specified jobs.
You can also monitor jobs related to SnapMirror and SnapVault operations.
You can monitor only the jobs that you created and that are relevant to you unless you are assigned
SnapCenter Admin or another super user role.
You can perform the following tasks related to monitoring jobs:
•
Monitor backup, clone, restore, and verification operations.
•
View job details and reports.
•
Stop a scheduled job.
Monitoring jobs, schedules, events, and logs | 81
Monitoring backup operations
You can monitor the progress of different backup operations by using the SnapCenter Jobs page. You
might want to check the progress of an operation 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
•
Cancelled
Steps
1. In the left navigation pane, click Monitor.
2. In the Monitor page, click Jobs.
3. Optional: In the Jobs page, perform the following steps:
a. Click
to filter the list so that only backup operations are listed.
b. Specify the start and end dates.
c. From the Type drop-down list, select Backup.
d. From the Status drop-down, select the backup status.
e. Click Apply to view the operations completed successfully.
4. Select a backup job, and then click Details to view the job details.
, when you click on job details you might see
Note: Though the backup job status displays
that some of the child tasks of the backup operation are still in progress.
5. Optional: In the Job Details page, click View logs.
The View logs button displays the detailed logs for the selected operation.
Stopping a scheduled job
If you are performing maintenance on a resource group or one of its resources, you should stop a
scheduled job by placing the resource group in maintenance mode or by detaching the policy from
the resource group.
Steps
1. In the left navigation pane, click Resources, and then select the appropriate plug-in from the
drop-down list.
82 | SnapCenter Software Administration Guide
2. Select the resource group for which you want to temporarily stop backup, restore, and clone
operations.
3. Click Maintenance.
4. Click Yes in the Maintenance window.
Canceling queued jobs
You can cancel backup, clone, and verification jobs that are queued in SnapCenter. SnapCenter
cleans up all activities associated with the job being canceled.
About this task
SnapCenter does not support the cancellation of jobs that are running.
Note: SnapCenter automatically cancels jobs when they are queued for an extended period of time.
Steps
1. In the left navigation pane, click Monitor.
2. Select the job you want to cancel, and then click Cancel Queued Job.
Monitoring SnapCenter schedules
You might want to view current schedules to determine when the operation starts, when it was last
run, and when it runs next. You can also determine the host on which the operation runs, along with
the operation's resource group and policy information.
Steps
1. In the left navigation pane, click Monitor..
2. In the Monitor page, click Schedules.
3. Select the resource group and the schedule type.
4. View the list of scheduled operations.
Monitoring SnapCenter events
You can view a list of SnapCenter events in the system, such as when a user creates a resource group
or when the system initiates activities, such as creating a scheduled backup. You might want to view
events to determine if an operation such as a backup or a restore operation is currently in progress.
About this task
All job information appears in the Events page. For example, when a backup job starts, a “backup
start” event appears. When the backup completes, a “backup complete” event appears.
Steps
1. In the left navigation pane, click Monitor.
2. In the Monitor page, click Events.
3. Optional. In the Filter box, enter the start or end date, category of event (such as backup, resource
group, or policy) and severity level, and click Apply. Alternatively, enter characters in the Search
box.
Monitoring jobs, schedules, events, and logs | 83
4. View the list of events.
Monitoring SnapCenter logs
You can view and download SnapCenter server logs, SnapCenter host agent logs, and plug-in logs.
You might want to view logs to help with troubleshooting.
You can filter the logs to show only a specific log severity level:
•
•
•
•
•
Debug
Info
Warn
Error
Fatal
You can also obtain job level logs: for example, logs that help you troubleshoot the reason for a
backup job failure. For job level logs, use the Monitor > Jobs option.
Steps
1. In the left navigation pane, click Monitor.
2. In the Monitor page, click Logs.
3. Select the log type, host, and instance.
If you select a log type of plugin, you can select a host or SnapCenter plug-in. You cannot do this
if the log type is server.
4. To filter the logs by a specific source, message, or log level, click the filter icon at the top of the
column heading.
To show all logs, choose “Greater than or equal to”" the level of “Debug”.
5. Click Refresh.
6. View the list of logs.
Related tasks
Monitoring backup operations on page 81
Types of SnapCenter logs
If you need to troubleshoot operations in SnapCenter, it is helpful to know the types of logs that you
can use.
Logs that appear in the Monitor > Logs page
The following types of logs appear on the Logs page:
Server logs
Include information from your SnapCenter Server. These are typically located at C:
\inetpub\wwwroot\SnapCenter\App_Data\log.
Plug-in logs
Show information from hosts that have SnapCenter plug-in packages installed. These
include logs from SMCore, as well as logs from SnapCenter plug-ins.
Note: You can find the plug-in log in the installation directory for the plug-in. For RDM
and VMDK support, you should also review VirtualizationAPI.log in the
installation directory for the SnapCenter Plug-in for Microsoft Windows.
84 | SnapCenter Software Administration Guide
Job logs
Show information associated with a specific job. Job logs can span from the SnapCenter
Server down to the hosts and plug-ins.
Installation logs
SnapCenter Server installer log (SMSInstall log)
A Microsoft Windows Installer (MSI) log file provided at the end of the installation or
uninstallation process. This log is useful if an error occurred in the process or the
installation was interrupted.
SMCore Installer log
An MSI log file provided at the end of the installation or uninstall process. This log is also
useful if an error occurred in the process or the installation was interrupted.
SnapCenterversion.exe/debug log
Installation and uninstallation logs that you can use to troubleshoot installation and
uninstallation processes.
Event log locations
SnapCenter gives you access to powerful event log monitoring and tracking capabilities. You should
know where to look for the types of events about which you want information.
Event type
Event log location
Completed and failed backup, restore, clone,
and verify jobs
Plug-in host event viewer | application
Start events for backup, restore, clone, and
verify jobs
SnapCenter host event viewer | application
Add, remove, and update policies and resource
groups events
SnapCenter host event viewer
Using Microsoft Windows Installer log files
A Microsoft Windows Installer (MSI) log file is provided at the end of an installation or
uninstallation process. This log is useful if an error occurred in the process or the installation was
interrupted.
About this task
MSI files show error and success codes at the “MainEngineThread is returning” line. If the file
includes “Remove = All”, the log file resulted from an uninstallation process.
Steps
1. To search through the log, search for “ error ” (without the quotes and including a space before
and after the word).
You can ignore lines such as the following containing the word “error” in the text:
SchedSecureObjectsRollback: Failed to store ACL rollback information
with error 0x80070002 - continuing
2. Note the text near the string “ error ”.
Monitoring jobs, schedules, events, and logs | 85
Using the SnapCenter version.exe/debug log
SnapCenter creates one or more installation and uninstallation logs in a single bundle installation log
file, InstallShield.log. You can use this version.exe/ log to troubleshoot installation and
uninstallation processes.
About this task
Each section of the log starts with a line that includes “InstallShield suite engine (Unicode) started.”
The log is located in the same folder as SnapCenterversion.exe.
Steps
1. To specify a log file location and name, enter the path and name.
Example
SnapCenter1.0.exe /debuglog c:\SCBundleInstallLog.txt
2. Look for the final status by searching for “final exit status” text.
The final status includes a code that indicates either that the installation was successful or that
errors occurred:
•
0x00000000 indicates success.
•
0x00000642 indicates that the user canceled the installation process.
•
0x00000643 indicates that an error occurred in the installation process.
3. Search for the error by searching up from the “final exit status” text at the end of the log section.
Example
4-24-2015[02:33:43 PM]: UI DLL: Display Error:
The following items are required to launch this setup:
System restart since there is a pending restart.
4. To determine which Microsoft Windows Installer (MSI) installer log includes the error, locate
“Parcel operation return status” and find the product code, which indicates the log you should
review:
•
{DEF09FA0-E342-4378-A38C-A4E49D3B05A9} indicates SnapCenter Server.
•
{3F29BA2D-F761-4A6C-AC76-EB07B5D1B713} indicates SMCore.
Exporting logs
Exporting SnapCenter logs enables you to view them in hard copy or in another format.
About this task
You can view logs from remote hosts for a specific log type or a specific SnapCenter plug-in and host
combination.
Note: Installer logs from the remote hosts are not included.
86 | SnapCenter Software Administration Guide
Steps
1. From the SnapCenter left navigation pane, click Monitor.
2. From the top navigation pane, click Logs.
3. Choose the log type, host, and instance.
If you select a log type of plugin, you can select a host or a plug-in. You cannot do this if the log
type is server.
4. Click Refresh.
5. To filter the results by a specific source, message, or log level, click the filter icon at the top of the
column heading.
To show all logs, choose “Greater than or equal to”" the level of “Debug”.
6. Click Download.
SnapCenter creates a .zip file that includes the specified logs.
Removing jobs and logs from SnapCenter
You can remove backup, restore, clone, and verification jobs and logs from SnapCenter. SnapCenter
stores successful and failed job logs indefinitely unless you remove them. You might want to remove
them to replenish storage.
Before you begin
There must be no jobs currently in operation.
About this task
You can remove a specific job by providing a Job ID or you can remove jobs within a specified
period.
You do not need to place the host in maintenance mode to remove jobs.
Steps
1. Launch PowerShell.
2. From the command prompt, enter:
Open-SMConnection
3. From the command prompt, enter:
Remove-SmJobs
4. In the left navigation pane, click Monitor.
5. In the Monitor page, click Jobs.
6. In the Jobs page, review the status of the job.
87
Administering EMS data collection
You can schedule and manage Event Management System (EMS) data collection using PowerShell
cmdlets. EMS data collection involves gathering details about the SnapCenter Server, the installed
SnapCenter plug-in packages, the hosts, and similar information, and then sending it to a specified
ONTAP Storage Virtual Machine (SVM).
Stopping EMS data collection
EMS data collection is enabled by default and runs every seven days after your installation date. You
can disable data collection at any time by using the PowerShell cmdlet DisableSmDataCollectionEMS.
Steps
1. From a PowerShell command line, enter:
Open-SmConnection
2. Now disable EMS data collection by entering:
Disable-SmDataCollectionEms
Starting EMS data collection
EMS data collection is enabled by default and is scheduled to run every seven days from the
installation date. If you have disabled it, you can start EMS data collection again by using the
Enable-SmDataCollectionEMS cmdlet.
Before you begin
The Data ONTAP event generate-autosupport-log permission has been granted to the Storage Virtual
Machine (SVM) user.
Steps
1. From a PowerShell command line, enter:
Open-SmConnection
2. Now enable EMS data collection by entering:
Enable-SmDataCollectionEMS
88 | SnapCenter Software Administration Guide
Changing EMS data collection schedule and target SVM
You can use PowerShell cmdlets to change the EMS data collection schedule or the target Storage
Virtual Machine (SVM).
Steps
1. From a PowerShell command line, enter the Open-SmConnection cmdlet.
Open-SmConnection
2. To change the EMS data collection target, enter the Set-SmDataCollectionEmsTarget
cmdlet.
This cmdlet has the format:
Set-SmDataCollectionEmsTarget
-Target SVM_name
SVM_name is the name of the SVM you want to use for the target.
3. To change the EMS data collection schedule, enter the Set-SmDataCollectionEmsSchedule
cmdlet.
This cmdlet has the format:
Set-SmDataCollectionEmsSchedule
-RunAs RunAs_account_credentials
-DaysInterval
-StartDateTime
RunAs_account_credentials is the Run As account that you set up earlier.
This cmdlet changes the Windows Scheduled Task that triggers the data collection EMS process.
Monitoring EMS data collection status
You can monitor the status of your EMS data collection using several PowerShell cmdlets. You can
get information about the schedule, Storage Virtual Machine (SVM) target, and status.
Steps
1. From a PowerShell command line, open the connection by entering:
Open-SmConnection
2. To retrieve information about the EMS data collection schedule, enter:
Get-SmDataCollectionEmsSchedule
3. To retrieve information about the EMS data collection status, enter:
Get-SmDataCollectionEmsStatus
Administering EMS data collection | 89
4. To retrieve information about the EMS data collection target, enter:
Get-SmDataCollectionEmsTarget
90
Using SnapCenter REST APIs
You can use REST APIs to perform several SnapCenter management operations.
Accessing REST APIs using the Swagger API web page
REST APIs are exposed through the Swagger web page. You can access the Swagger web page to
display the SnapCenter Server REST API documentation, as well as to manually issue an API call.
You can use REST APIs to help manage your SnapCenter Server.
Before you begin
You must know the management IP address or domain name of the SnapCenter Server on which you
want to execute the REST APIs.
Steps
1. From a browser, using the SnapCenter Server management IP address or domain name, enter the
URL to access the Swagger web page with the format https://
<SnapCenter_IP_address_or_name>:8146/swagger/.
Example
https://10.63.65.121:8146/swagger/
2. If the Swagger API documentation does not display automatically, in the Swagger Explore field,
type the URL to the location of the Swagger documentation: https://
<SnapCenter_IP_address_or_name>:8146/Content/swagger/SnapCenter.yaml, and
click Explore.
A list of API resource types, or categories, is displayed.
3. Click an API resource type to display the APIs in that resource type.
List of available REST APIs
You should be aware of the available REST APIs in SnapCenter so you can plan your management
API usage. The API calls are organized under the various resource types or categories.
You must refer to the Swagger web page for a complete list of the available API calls, as well as the
details of each call.
The management API calls are organized according to the following resource types:
•
Auth
•
Jobs
•
Hosts
•
Resources
•
Backups
•
Clones
•
Resource groups
Using SnapCenter REST APIs | 91
•
Policies
•
Storage Virtual Machines
•
Share
•
Catalog
•
Plugins
•
PSL
Troubleshooting REST APIs
If you encounter unexpected behavior when executing REST APIs, you can use log the files to
identify the cause and resolve the problem.
You can download the log files from the SnapCenter user interface by clicking Monitor > Logs >
Download.
File restore API gives error 400
Error 400 is displayed when restoring a file using /2.0/plugins/SP/resources/{key}/
restorefile API.
Corrective action
Use escape characters (\\) when providing a source path in Swagger. For example: \\\\vol1\
\path1\\path2.
92
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).
93
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
94
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 | 95
Index
A
C
about this guide
deciding whether to use 6
access
assigning to users 37
logging in to SnapCenter 17
administrator
logging in to SnapCenter as 17
role 31–33
Advanced licenses
deleting 22
modifying 21
viewing details for 20
Application Request Routing
overview 44
requirements for installation 44
understanding 44
architecture
overview of SnapCenter components 7
ARR
overview 44
ASM instance
setting up your Run As account credentials 39
audience
for this guide 6
authentication
encryption 11
for Run As credential 38
setting up your Run As account 39
types 38
AutoSupport
enabling notifications for storage system connections
canceling
queued backup jobs 82
capabilities, SnapCenter reporting
introduction to using 72
clone operations
resources, resource groups, and policies overview 12
clone reports
described 77
Cluster Shared Volumes
connecting to disks 52
creating disks 49
clusters, Microsoft
introduction to using FC RDM LUNs in 58
support limitations when using FC RDM LUNs 59
cmdlets
Disable-SmDataCollectionEms 87
Enable-SmDataCollectionEMS 87
Get-SmDataCollectionEmsSchedule 88
Get-SmDataCollectionEmsStatus 88
Get-SmDataCollectionEmsTarget 88
Set-SmDataCollectionEmsSchedule 88
Set-SmDataCollectionEmsTarget 88
SnapCenter Plug-in for Microsoft Windows support
23
B
backing up
monitoring progress in SnapCenter 81
prerequisites for protecting the SnapCenter
repository 67
backup details reports
described 77
backup reports
described 77
backups
overview of repository management 67
resources, resource groups, and policies overview 12
scheduling 80
backups, SnapCenter database
accessing 69
restoring 70
best practices
for volume and share configurations 55
setting up your Run As account 39
60
comments
how to send feedback about documentation 94
configuration checker tool
configuration checker
supported components 66
supported configurations 66
configuring
databases 42
reports 77
SnapCenter metadata repository for protection 68
the dashboard display 76
connections
setting up for storage systems 23
connections, storage system
deleting 28
connections, storage systems
modifying 27
connections, SVM
deleting 28
modifying 27
credentials
configuring for individual resources 41
configuring for Oracle databases 42
setting up your Run As account 39
supported for installing plug-ins for Windows 57, 58
CSV
See Cluster Shared Volume
D
dashboard
configuring 76
terminology 73
96 | SnapCenter Software Administration Guide
dashboard notifications
adding for SnapCenter capacity licenses 19
modifying for SnapCenter capacity licenses 21
viewing details for SnapCenter capacity licenses 20
data protection
resources, resource groups, and policies overview 12
SnapCenter 7
data protection job updates
configuring the option to email reports 79
database
backups 67
database backups, SnapCenter
accessing 69
restoring 70
databases
configuring SnapCenter metadata repository for
protection against data loss 68
prerequisites for protecting the SnapCenter
repository 67
deleting
SVM connections 28
details
viewing for managed hosts 62
disks
connecting to LUNs in SnapCenter 52
creating in SnapCenter 49
deleting LUNs in SnapCenter 54
disconnecting from LUNs in SnapCenter 54
resizing in SnapCenter 51
tasks you can perform using SnapCenter 49
viewing on a host 49
documentation
how to receive automatic notification of changes to
94
how to send feedback about 94
downloading
logs 83
E
email
configuring SnapCenter to send reports 79
testing configuration 78
email notifications
adding for SnapCenter capacity licenses 19
modifying for SnapCenter capacity licenses 21
viewing details for SnapCenter capacity licenses 20
EMS data collection
changing schedule 88
changing target SVM 88
disabling 87
getting status information 88
starting 87
EMS messaging
enabling for storage systems connections 23
ESX servers
limitations of SnapCenter Plug-in for Microsoft
Windows support 57
Event Management System
See EMS data collection
events
log locations 84
monitoring 80, 82
F
farm, SnapCenter web
adding an IIS instance to 45
load balancing with 45
FC RDM LUNs
creating shared 59
introduction to using in Microsoft clusters 58
Microsoft cluster support limitations when using 59
requirements for using in Microsoft clusters 58
FC-connected LUNs
creating 49
introduction to configuring with SnapCenter Plug-in
for Windows 46
features
of SnapCenter 7
feedback
how to send comments about documentation 94
files, log
using Microsoft Windows Installer 84
G
global settings
configuring SMTP server 78
H
host agent logs
downloading 83
monitoring 83
hosts
canceling queued jobs on 82
creating an igroup in SnapCenter Plug-in for
Microsoft Windows 47
creating SMB shares 55
deleting an igroup 48
disconnecting LUNs from 54
modifying 63
modifying an igroup 48
placing in maintenance mode 64
provisioning Windows with SnapCenter Plug-in for
Microsoft Windows 46
removing from SnapCenter 65, 66
renaming an igroup 48
tasks you can perform with 61
updating virtual machine information 64
viewing a list of disks on 49
viewing details about 62
I
igroups
creating in SnapCenter Plug-in for Microsoft
Windows 47
deleting in SnapCenter Plug-in for Microsoft
Windows 48
managing 47
modifying 48
purpose 47
renaming 48
information
Index | 97
how to send feedback about improving
documentation 94
initiators
adding to an igroup 48
creating an igroup 47
installation
troubleshooting 84, 85
iSCSI
disconnecting a session 47
establishing a session 46
iSCSI-connected LUNs
creating 49
introduction to configuring with SnapCenter Plug-in
for Windows 46
issues
troubleshooting using log files 91
J
job status reports
described 77
jobs
canceling queued backup 82
canceling queued clone 82
canceling queued verification 82
data protection status 72
monitoring 80
monitoring backup progress from the Jobs page 81
removing 86
status report from the Dashboard 76
stopping scheduled 81
L
license status
viewing for storage controllers 28
licenses
adding SnapCenter advanced and standard 19
configuring capacity notification thresholds for 19
deleting SnapCenter Advanced 22
deleting SnapCenter Standard 22
modifying capacity notification thresholds for 21
modifying SnapCenter Advanced 21
modifying SnapCenter Standard 21
viewing details about capacity notification thresholds
for 20
viewing details for SnapCenter Advanced 20
viewing details for SnapCenter Standard 20
limitations
support when using FC RDM LUNs in Microsoft
clusters 59
VMware ESX server-related 57
Linux
setting up your Run As account credentials on host
39
load balancing
best practices 44
using Application Request Routing 44
with the SnapCenter web farm 45
log files
accessing to resolve issues 91
using Microsoft Windows Installer 84
logging in
as a SnapCenter administrator 17
as a SnapCenter user 17
SnapCenter 17
with more than one role 17
logs
downloading 83
exporting 85
locations for viewing 84
monitoring 80, 83
removing 86
SnapCenter exe debug log 85
types of 83
LUN storage
introduction to configuring with SnapCenter Plug-in
for Windows 46
LUNs
connecting to in SnapCenter 52
creating in SnapCenter 49
creating shared FC RDM 59
deleting in SnapCenter 54
disconnecting before deleting 54
disconnecting in SnapCenter 54
disk-related tasks you can perform using SnapCenter
49
FC RDM, requirements for using in a Microsoft
cluster 58
introduction to creating and managing using
SnapCenter Plug-in for Microsoft Windows in
VMware environments 57
prerequisites for iSCSI connections 46
RDM, support through PowerShell cmdlets 57
RDM, troubleshooting creation of 59
resizing in SnapCenter 51
LUNs, FC RDM
FC RDM Microsoft cluster support limitations when
using 59
introduction to using in Microsoft clusters 58
M
maintenance mode
placing hosts in 64
managed hosts
tasks you can perform with 61
Microsoft clusters
introduction to using FC RDM LUNs in 58
support limitations when using FC RDM LUNs 59
Microsoft Windows Installer log files
using the MSI log file for troubleshooting 84
modifying
roles 38
the dashboard display 76
monitoring
EMS data collection status 88
events 82
jobs 80
jobs overview 80
logs 83
progress of SnapCenter backup operations 81
schedules 82
98 | SnapCenter Software Administration Guide
N
Q
Network Load Balancing
overview 44
NLB
overview 44
NSM
migrating to another disk 70
queued jobs
canceling backup 82
canceling clone 82
canceling verification 82
O
ONTAP
account permission requirements for SnapCenter 31
operations
monitoring backup progress from the Jobs page 81
Oracle Database
setting up your Run As account credentials 39
Oracle databases
configuring credentials for 42
P
parameters
used to filter report information 77
permissions
associated with pre-defined roles 33
list of 32
role-based access control 32
setting for applications 39
understanding how to set 31
plug-in logs
downloading 83
monitoring 83
plug-in reports
described 77
plug-ins
adding to host 63
description of 7
placing hosts in maintenance mode before upgrade
64
removing from host 63
restarting after a temporary stop 64
starting 64
tasks you can perform related to hosts 61
updating SnapCenter information in SnapCenter
Plug-in for VMware vSphere 30
updating vCenter information in SnapCenter Plug-in
for VMware vSphere 30
upgrading on host 63
policies
used in SnapCenter data protection 12
PowerShell cmdlets
reclaiming storage space with 56
SnapCenter Plug-in for Microsoft Windows support
60
prerequisites
for protecting the SnapCenter repository 67
for removing a host 65
protecting
SnapCenter metadata repository 68
R
RBAC
introduction to using 31
RDM
minimum vCenter privileges required for operations
57
RDM LUNs
creating shared FC 59
introduction to using FC in Microsoft clusters 58
Microsoft cluster support limitations when using for
FC 59
requirements for FC support 58
troubleshooting creation of 59
removing
a host from SnapCenter 65, 66
reporting capabilities, SnapCenter
introduction to using 72
reports
backup and backup details, described 77
configuring 77
configuring the option to email 79
exporting 78
job status 76
job status, described 77
options 72
parameters used to filter information 77
plug-in, described 77
printing 78
terminology 73
types of 77
repositories
for SnapCenter, overview of 7
repository
configuring for protection 68
repository management
overview 67
repository, SnapCenter
prerequisites for protecting 67
requirements
Application Request Routing 44
for removing a host 65
resizing
disks 51
LUNs 51
resource groups
configuring the option to email reports 79
stopping scheduled jobs 81
used in SnapCenter data protection 12
resource types
list of REST APIs 90
resources
configuring credentials for 41
used in SnapCenter data protection 12
REST APIs
accessing from Swagger 90
Index | 99
resource type list 90
troubleshooting 91
restore operations
resources, resource groups, and policies overview 12
restore reports
described 77
restoring
SnapCenter database backups 70
role-based access control
adding users to a role 36
assigning access to users 37
creating roles 37
introduction to using 31
list of roles and permissions 32
pre-defined roles and permissions 33
understanding 31
roles
adding users to 36
app backup and clone admin role, defined 33
available pre-defined 33
backup and clone viewer role, defined 33
creating 37
infrastructure admin role, defined 33
list of 32
modifying 38
understanding role-based access control 31
Run As account
authentication methods 38
configuring for individual resources 41
overview 31
setting up 39
run as credential
configuring for Oracle databases 42
S
schedules
monitoring 80, 82
stopping jobs 81
security
overview 11
server logs
downloading 83
monitoring 83
servers
VMware ESX limitations of SnapCenter Plug-in for
Microsoft Windows support 57
shared FC RDM LUNs
creating 59
using in a Microsoft cluster 59
shares, SMB
creating in SnapCenter Plug-in for Microsoft
Windows 55
SMB shares
creating in SnapCenter Plug-in for Microsoft
Windows 55
deleting in SnapCenter 56
SMTP server
configuring globally 78
SnapCenter
accessing database backups 69
adding an IIS instance to 45
components 7
Dashboard page terminology 73
data protection 7
finding the URL 17
overview 7
reporting options 72
Reports page terminology 73
repository protection 67
templates for creating SMB shares 55
web farm load balancing with 45
SnapCenter licenses
introduction to managing 19
SnapCenter metadata repository
configuring for protection 68
SnapCenter Plug-in for Microsoft SQL Server
overview of components 7
SnapCenter Plug-in for Microsoft Windows
creating an igroup 47
creating SMB shares 55
deleting an igroup 48
limitations when using VMware ESX server 57
modifying an igroup 48
overview of components 7
PowerShell cmdlet support 60
renaming an igroup 48
SnapCenter Plug-in for Oracle Database
overview of components 7
SnapCenter Plug-in for UNIX
overview of components 7
SnapCenter Plug-in for VMware vSphere
overview of components 7
SnapCenter repository
migrating to another disk 70
prerequisites for protecting 67
SnapCenter Server
overview 7
Snapshot copies
features in SnapCenter 7
introduction to managing using SnapCenter Plug-in
for Microsoft Windows in VMware environments 57
space reclamation
on storage systems 56
SQL Server
setting up your Run As account credentials 39
Standard licenses
deleting 22
modifying 21
viewing details for 20
starting
plug-in services 64
stopping hosts
by placing in maintenance mode 64
storage controller license
viewing status of 28
storage system connections
enabling AutoSupport notifications for 23
enabling EMS messaging for 23
storage systems
deleting connections to 28
modifying connections to 27
modifying connections to SVMs 27
reclaiming space on 56
settings up connections to 23
storage types
100 | SnapCenter Software Administration Guide
supported by plug-ins package for Linux 16
supported by SnapCenter Plug-In for Microsoft SQL
Server 14
supported by SnapCenter Plug-In for Microsoft
Windows 14
SVMs 14
VMs 14
storage, LUN
introduction to configuring with SnapCenter Plug-in
for Windows 46
sudo privileges
configuring for non-root user 39
suggestions
how to send feedback about documentation 94
support limitations
when using FC RDM LUNs in Microsoft clusters 59
SVMs
defined 23
deleting connections to 28
introduction to setting up to use with SnapCenter 23
modifying connections to 27
setting up connections to 23
supported storage types 14, 16
Swagger API web page
accessing REST APIs from 90
T
templates
for creating SMB shares 55
terminology
resources, resource groups, and policies data
protection 12
used on the Dashboard page display 73
used on the Reports page display 73
troubleshooting
monitoring logs 80
RDM LUN creation 59
types of logs you can use for 83
using the Microsoft Windows Installer log files 84
using the SnapCenter debug log 85
Twitter
how to receive automatic notification of
documentation changes 94
U
upgrading plug-ins
placing hosts in maintenance mode prior to 64
users
adding to a role 36
assigning access to 37
using roles at login 17
V
vCenter
minimum privileges required for RDM operations 57
updating SnapCenter Plug-in for VMware vSphere
30
verification server
configuration status for host 62
virtual disks
tasks you can perform using SnapCenter 49
virtual machines
updating information about 64
virtualization host configured state
viewing 62
virtualized environments
storage types supported 14
VMs
supported storage types 14, 16
VMware
ESX servers limitations of SnapCenter Plug-in for
Microsoft Windows support 57
SnapCenter Plug-in for Windows support for 57
support for ESX iSCSI initiators 57
support for FC HBAs 57
support for guest OS platforms 57
support for iSCSI HBAs 57
support for iSCSI initiators 57
using Virtual Storage Console to provision Windows
hosts 46
Vservers
See SVMs
W
web address
for SnapCenter 17
web farm, SnapCenter
adding an IIS instance to 45
load balancing with 45
Windows hosts
creating an igroup in SnapCenter Plug-in for
Microsoft Windows 47
Windows Server failover clusters
requirements for connecting to a disk 52
requirements for creating a disk 49
Download PDF
Similar pages