IBM System Storage N series OnCommand Unified Manager ......IBM System Storage N series OnCommand...

IBM System Storage N series

OnCommand Unified ManagerInstallation and Setup Guide for Usewith Core Package 5.2 and Host Package1.3

GA32-1020-03

��

Contents

Preface ......................................................................................................... 10Supported features ..................................................................................................... 10Websites .................................................................................................................... 10Getting information, help, and service ...................................................................... 10Before you call .......................................................................................................... 11Using the documentation ........................................................................................... 11Hardware service and support ................................................................................... 11Firmware updates ...................................................................................................... 11How to send your comments ..................................................................................... 12

Overview of OnCommand Unified Manager manageability softwarecomponents ............................................................................................. 13

Core Package and Host Package installation and configuration checklists .............. 13OnCommand Unified Manager installation scenarios for different storage

environments ....................................................................................................... 14OnCommand Unified Manager architecture ............................................................. 15What a host service is (7-Mode environments only) ................................................. 16Contents of the OnCommand Unified Manager Core Package ................................ 17

Components installed with the OnCommand Unified Manager CorePackage .................................................................................................... 17

Functionality available with the OnCommand Unified Manager CorePackage .................................................................................................... 18

Contents of the OnCommand Unified Manager Host Package ................................. 19Components installed with the OnCommand Unified Manager Host

Package .................................................................................................... 19Functionality available with the OnCommand Unified Manager Host

Package in a VMware environment ........................................................ 20Comparison of OnCommand Unified Manager Express edition and Standard

editions (7-Mode environments only) ................................................................. 20Functionality available in the Standard and Express editions ....................... 21

System requirements .................................................................................. 24Browser support, requirements, and limitations ........................................................ 24

Accessing the OnCommand console on a Linux-based PC .......................... 25

Table of Contents | 3

License requirements ................................................................................................. 26License requirements for data protection ...................................................... 26

Network storage requirements for database files ...................................................... 27OnCommand Unified Manager Core Package hardware and software

requirements ........................................................................................................ 27Software required prior to installing OnCommand Unified Manager

Core Package ........................................................................................... 27Software required for Open Systems SnapVault ........................................... 28Software required for DataFabric Manager Host Agent (7-Mode

environments only) .................................................................................. 28Hardware requirements for Windows Server 2008 with 1 to 25 storage

systems .................................................................................................... 28Requirements for Windows Server 2008 with 25 or more storage

systems .................................................................................................... 29Requirements for Linux workstation or server with 1 to 25 storage

systems .................................................................................................... 30Requirements for Linux workstation or server with 25 or more storage

systems .................................................................................................... 31Required ports for the Core Package ............................................................. 31

OnCommand Unified Manager Host Package hardware and softwarerequirements ........................................................................................................ 33

Hardware requirements ................................................................................. 33Operating system requirements ..................................................................... 33Software required prior to installing OnCommand Unified Manager

Host Package ........................................................................................... 34Designated ports for the OnCommand Unified Manager Host Package ...... 35

Installing the OnCommand Unified Manager Core Package ................ 36Installation requirements specific to 7-Mode environments ..................................... 36Installation requirements specific to clustered environments ................................... 37Downloading OnCommand Unified Manager Core Package ................................... 37Installing OnCommand Unified Manager Core Package on Windows .................... 38Installing OnCommand Unified Manager Core Package on Linux .......................... 40Installing the OnCommand Unified Manager Core Package with a script ............... 42

Options you can use for the Windows installation script .............................. 43Options you can use for the Linux installation script .................................... 44

4 | Installation and Setup Guide

Setting up Web security after restoring a database on a new OnCommandUnified Manager Core Package installation ........................................................ 45

Installing N series Management Console .................................................................. 46Installing or upgrading OnCommand Unified Manager Windows PowerShell

cmdlets ................................................................................................................. 47Installing OnCommand Unified Manager Host Package ....................... 48

Downloading the OnCommand Unified Manager Host Package ............................. 48Prerequisites for installing the Host Package ............................................................ 48Installing OnCommand Unified Manager Host Package .......................................... 49Shared lock directories with Virtual Storage Console .............................................. 51

Setting up a shared lock directory ................................................................. 51Installing the OnCommand Unified Manager Host Package using a script .............. 52

Scripted install options for OnCommand Unified Manager Host Package.................................................................................................................. 53

Setting up your system ............................................................................... 55Configuring the OnCommand Unified Manager Express edition server (7-Mode

environments only) .............................................................................................. 55Configuring the OnCommand Standard edition server with host services (7-

Mode only) .......................................................................................................... 59Verifying that a host service is registered with the DataFabric Manager

server (7-Mode environments only) ........................................................ 60Authorizing a host service to access storage system credentials (7-Mode

environments only) .................................................................................. 61Associating a host service with vCenter Server (7-Mode environments

only) ......................................................................................................... 62Verifying communication between the host service and the

OnCommand plug-in ............................................................................... 65Associating storage systems with a host service (7-Mode environments

only) ......................................................................................................... 66Editing storage system login and NDMP credentials from the Host

Services tab (7-Mode environments only) .............................................. 68Determining whether a storage system belongs to a workgroup or a domain .......... 70

Certificate-based authentication ............................................................... 71Certificate information .............................................................................................. 71Managing certificates for cloud service clients ......................................................... 71

Generating a key and self-signed certificate ................................................. 72


Adding a certificate in the truststore ............................................................. 72Removing a certificate from the truststore .................................................... 72Displaying the list of certificates in a truststore ............................................ 72Displaying details about certificates in a truststore ....................................... 73Displaying the contents of the DataFabric Manager server key and

certificate file ........................................................................................... 73Displaying DataFabric Manager server certificate details ............................ 74Disabling certificate-based authentication .................................................... 74

Managing certificates for host services clients ......................................................... 75Authorizing a host service certificate ............................................................ 75

Migrating certificates, keys, and truststores manually .............................................. 75Enabling secure communication between the DataFabric Manager

server and Data ONTAP ....................................................................... 77Upgrading to OnCommand Unified Manager Core and Host

Packages ................................................................................................. 79Changes that affect upgrade to OnCommand Unified Manager Core Package ........ 79Upgrading OnCommand Unified Manager Core Package on Windows .................. 81Upgrading OnCommand Unified Manager Core Package on Linux ........................ 82Upgrading from Core Package 32-bit to Core Package 64-bit .................................. 83Upgrading Core Package to manage 7-Mode and clustered Data ONTAP

environments ....................................................................................................... 84Prerequisites for upgrading the Host Package ........................................................... 85Upgrading to OnCommand Unified Manager Host Package .................................... 86

Setting the port number manually ................................................................. 88Upgrade issues with DataFabric Manager 3.8 or earlier ........................................... 88

Uninstalling the OnCommand Unified Manager Core and HostPackages ................................................................................................. 92

Uninstalling the OnCommand Unified Manager Core Package from Windows ...... 92Uninstalling the OnCommand Unified Manager Core Package from Linux ............ 93Uninstalling the OnCommand Unified Manager Host Package ............................... 93

Troubleshooting OnCommand Unified Manager installation andsetup ........................................................................................................ 95

Address already in use ............................................................................................... 95There is a problem with this Windows Installer package ......................................... 95Cursor displays in multiple locations in the same dashboard panel .......................... 95Plug-in container for Firefox has stopped working ................................................... 96


No related objects are displayed for a virtual object ................................................. 96Could not find any storage mapping for virtual object ............................................. 97Storage mapping fails for virtual machine and datastore created on VMFS

datastore using FC LUN ...................................................................................... 97Operation timed out ................................................................................................... 98Primary key for table is not unique ........................................................................... 98Access is denied ........................................................................................................ 98Error 1067 while starting the DFM WebUI service .................................................. 98Verifying host service to DataFabric Manager server communication ..................... 99Administrators usergroup does not exist on <vFiler name> ..................................... 99Host service fails to connect to DataFabric Manager server after a restart ............... 99Host service is unresponsive after successful installation of OnCommand

Unified Manager Host Package ......................................................................... 100Installing and configuring the Core Package in an MSCS

environment ......................................................................................... 101Preparing to install the OnCommand Unified Manager Core Package in an

MSCS environment ........................................................................................... 101Prerequisites for installing the OnCommand Unified Manager Core

Package in MSCS .................................................................................. 101Configuration requirements for the OnCommand Unified Manager Core

Package in MSCS .................................................................................. 102Configuration limitations for the OnCommand Unified Manager Core

Package in MSCS .................................................................................. 103Installing the OnCommand Unified Manager Core Package in an MSCS

environment ....................................................................................................... 103Configuring MSCS for the OnCommand Unified Manager Core

Package installation ............................................................................... 103Installing the OnCommand Unified Manager Core Package in MSCS ...... 104Example of the MSCS initial setup ............................................................. 106DataFabric Manager server service resources added to MSCS .................. 107

Configuring the OnCommand Unified Manager Core Package in an MSCSenvironment ....................................................................................................... 107

Adding the cluster services using a script ................................................... 108Script options for configuring services in MSCS ........................................ 109Bringing DataFabric Manager server cluster services online in MSCS ...... 109


Configuring DataFabric Manager server to use the cluster name inMSCS .................................................................................................... 109

Configuring DataFabric Manager server in MSCS manually ..................... 110Configuring a host service in MSCS ........................................................... 115

Managing DataFabric Manager server in an MSCS environment .......................... 115Best practices to start and stop DataFabric Manager server services in

MSCS .................................................................................................... 115Restoring the DataFabric Manager server database in MSCS .................... 116Configuring DataFabric Manager server to use HTTPS in MSCS ............. 116DataFabric Manager server monitoring in MSCS ....................................... 119Data shared by MSCS cluster nodes ........................................................... 119Data that is not shared by MSCS cluster nodes .......................................... 119

Uninstalling the OnCommand Unified Manager Core Package in an MSCSenvironment ....................................................................................................... 120

Upgrading OnCommand Unified Manager Core Package in an MSCSenvironment ....................................................................................................... 121

Installing and configuring the Core Package in a VCS environment . 124Preparing to install OnCommand Unified Manager Core Package in a VCS

environment ....................................................................................................... 124Prerequisites for installing OnCommand Unified Manager Core Package

in VCS ................................................................................................... 124Configuration requirements for OnCommand Unified Manager Core

Package in VCS ..................................................................................... 125Configuration limitations for the OnCommand Unified Manager Core

Package in VCS ..................................................................................... 125Installing OnCommand Unified Manager Core Package in a VCS environment ... 126

Configuring VCS to install the OnCommand Unified Manager CorePackage .................................................................................................. 126

Installing OnCommand Unified Manager Core Package on VCS .............. 127Configuring OnCommand Unified Manager Core Package in a VCS

environment ....................................................................................................... 128DataFabric Manager server service resources added to VCS ..................... 128Script options for configuring services in VCS .......................................... 129Configuring DataFabric Manager server on the cluster nodes in VCS ....... 130Configuring DataFabric Manager server in VCS manually ........................ 131Configuring a host services in VCS ............................................................ 133


Best practices to start and stop DataFabric Manager server services inVCS ....................................................................................................... 133

Managing the DataFabric Manager server in a VCS environment ......................... 134Restoring the DataFabric Manager server database in VCS ....................... 134Changing default port numbers for HTTP and HTTPS protocols .............. 134Configuring the DataFabric Manager server to use HTTPS in VCS .......... 136Data shared by VCS cluster nodes .............................................................. 138Data that is not shared by VCS cluster nodes ............................................. 138

Uninstalling the OnCommand Unified Manager Core Package in a VCSenvironment ....................................................................................................... 139

Upgrading OnCommand Unified Manager Core Package in a VCS environment . 139Copyright information ............................................................................. 142Trademark information ........................................................................... 143Index ........................................................................................................... 146


Preface

Supported featuresIBM System Storage N series storage systems are driven by NetApp Data ONTAP software. Somefeatures described in the product software documentation are neither offered nor supported by IBM.Please contact your local IBM representative or reseller for further details.

Information about supported features can also be found on the N series support website (accessed andnavigated as described in Websites on page 10).

WebsitesIBM maintains pages on the World Wide Web where you can get the latest technical information anddownload device drivers and updates. The following web pages provide N series information:

• A listing of currently available N series products and features can be found at the following webpage:www.ibm.com/storage/nas/

• The IBM System Storage N series support website requires users to register in order to obtainaccess to N series support content on the web. To understand how the N series support webcontent is organized and navigated, and to access the N series support website, refer to thefollowing publicly accessible web page:www.ibm.com/storage/support/nseries/This web page also provides links to AutoSupport information as well as other important N seriesproduct resources.

• IBM System Storage N series products attach to a variety of servers and operating systems. Todetermine the latest supported attachments, go to the IBM N series interoperability matrix at thefollowing web page:www.ibm.com/systems/storage/network/interophome.html

• For the latest N series hardware product documentation, including planning, installation andsetup, and hardware monitoring, service and diagnostics, see the IBM N series InformationCenter at the following web page:publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

Getting information, help, and serviceIf you need help, service, or technical assistance or just want more information about IBM products,you will find a wide variety of sources available from IBM to assist you. This section contains


http://www.ibm.com/storage/nas/

http://www.ibm.com/storage/support/nseries/

http://www.ibm.com/systems//storage/network/interophome.html

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

information about where to go for additional information about IBM and IBM products, what to do ifyou experience a problem with your IBM N series product, and whom to call for service, if it isnecessary.

Before you callBefore you call, make sure you have taken these steps to try to solve the problem yourself:

• Check all cables to make sure they are connected.• Check the power switches to make sure the system is turned on.• Use the troubleshooting information in your system documentation and use the diagnostic tools

that come with your system.• Refer to the N series support website (accessed and navigated as described in Websites on page

10) for information on known problems and limitations.

Using the documentationThe latest versions of N series software documentation, including Data ONTAP and other softwareproducts, are available on the N series support website (accessed and navigated as described in Websites on page 10).

Current N series hardware product documentation is shipped with your hardware product in printeddocuments or as PDF files on a documentation CD. For the latest N series hardware productdocumentation PDFs, go to the N series support website.

Hardware documentation, including planning, installation and setup, and hardware monitoring,service, and diagnostics, is also provided in an IBM N series Information Center at the following webpage:

publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

Hardware service and supportYou can receive hardware service through IBM Integrated Technology Services. Visit the followingweb page for support telephone numbers:

www.ibm.com/planetwide/

Firmware updatesIBM N series product firmware is embedded in Data ONTAP. As with all devices, ensure that yourun the latest level of firmware. Any firmware updates are posted to the N series support website(accessed and navigated as described in Websites on page 10).

Preface | 11

http://publib.boulder.ibm.com/infocenter/nasinfo/nseries/index.jsp

http://www.ibm.com/planetwide/

Note: If you do not see new firmware updates on the N series support website, you are running thelatest level of firmware.

Verify that the latest level of firmware is installed on your machine before contacting IBM fortechnical support.

How to send your commentsYour feedback helps us to provide the most accurate and high-quality information. If you havecomments or suggestions for improving this document, please send them by email to [email protected].

Be sure to include the following:

• Exact publication title• Publication form number (for example, GC26-1234-02)• Page, table, or illustration numbers• A detailed description of any information that should be changed


mailto:[email protected]

Overview of OnCommand Unified Managermanageability software components

The OnCommand Unified Manager suite is composed of two installation packages: OnCommandUnified Manager Core Package and OnCommand Unified Manager Host Package. Understanding thecapabilities provided by each package helps you to install the packages based on your environment.

OnCommand Unified Manager Core Package provides backup and restore capabilities, monitoring,and provisioning for a physical storage environment. It also provides basic support for virtual storageenvironments. If you want to discover your virtual environment and want to take advantage of thefull range of management and monitoring capabilities for virtual storage environments, you mustinstall OnCommand Unified Manager Host Package as well.

OnCommand Unified Manager 5.1 and later supports Data ONTAP operating in 7-Modeenvironments or clustered environments. However, OnCommand Unified Manager 5.1 or later doesnot support management of both modes from the same OnCommand Unified Manager instance.During the OnCommand Unified Manager installation process, you are prompted to select either a 7-Mode environment or a clustered environment.

Core Package and Host Package installation andconfiguration checklists

It is helpful to use checklists to verify that you have completed each task in the installation andconfiguration process, including reviewing system requirements; downloading and installing avariety of software; and, if your environment includes virtual objects, configuring the host service.

Plan for, download, and install the software

This checklist provides an overview of the installation process for OnCommand Unified ManagerCore Package and OnCommand Unified Manager Host Package. The OnCommand Unified ManagerHost Package software is required only for a virtual environment. If you are installing in a purelyphysical environment and are not managing VMware virtual objects, you need not install the HostPackage software or configure the host service.

1. Review the system requirements: on page 24

• Browser requirements• License requirements• Network storage requirements• Core Package hardware and software requirements• Host Package hardware and software requirements

Required if installing in a virtual environment2. Download the OnCommand Core Package on page 37.

13

3. Download the OnCommand Host Package on page 48.Required if installing in a virtual environment.

4. Download the Host Agent software on page 28.

5. Download the Open Systems SnapVault software on page 28.

6. Install the Core Package software: Windows, on page 38 Linux, on page 40 or by script onpage 42.

7. Install the Host Package software: VMware on page 49 or by script on page 52.Required if installing in a virtual environment.

8. Install the Host Agent software on page 28.

9. Install the Open Systems SnapVault software on page 28.

10. Configure the host service: Standard installation on page 59 or Express installation on page55.

Configure the host service

If you selected the Express edition during the Core Package installation, you can use the ExpressConfiguration wizard to configure your software. The wizard can be accessed from theAdministration menu in the OnCommand console. After completing the wizard, you can use thefollowing checklist to verify the results.

If you selected the Standard edition during the OnCommand Unified Manager Core Packageinstallation, use this checklist to verify that you have completed all of the configuration tasks:

1. Verify that the host service is registered with the DataFabric Manager server on page 60.

2. Authorize the host service to access storage system credentials on page 61.

3. Associate the host service with the vCenter Server on page 62.

4. Verify that the host service is communicating with the VMware plug-in on page 65.

5. Associate storage systems with the host service on page 66.

6. Verify that storage system credentials are valid on page 68.

7. Install N series Management Console on page 46.

8. Install the OnCommand Windows PowerShell cmdlets on page 47.

When the configuration tasks are complete, you can create backup jobs from the Datasets tab.

OnCommand Unified Manager installation scenarios fordifferent storage environments

If your storage environment includes physical storage objects, you must install OnCommand UnifiedManager Core Package. If you have a VMware environment and want to manage both physical and


virtual objects, then you must install both OnCommand Unified Manager Core Package andOnCommand Unified Manager Host Package.

Related concepts

Installing the OnCommand Unified Manager Core Package on page 36OnCommand Unified Manager Core Package hardware and software requirements on page 27Installing OnCommand Unified Manager Host Package on page 48OnCommand Unified Manager Host Package hardware and software requirements on page 33

OnCommand Unified Manager architectureOnCommand Unified Manager Core and Host Packages include interaction among front-end userinterfaces (such as the OnCommand console, the N series Management Console, and the OperationsManager console) and back-end servers or services (such as the DataFabric Manager server, hostservices, VMware services plug-in, and storage systems).

You can launch the Operations Manager console and the N series Management Console to manageyour physical environment.

OnCommand console

APIs

OnCommand Host

Services

VMware plug-in

(back end)

Storage system

Storage system

Front-end GUI (direct user interaction)

Back-end server or service (not visible to the user)

(Provides access to Operations Manager and Management Console)

OnCommand console (GUI)

Caches schedules, catalog, and events for short periods, or execution without DataFabric Manager Server.

Management Console (GUI)

Operations Manager (GUI)

DataFabric Manager

(DFM) server

Related concepts

Contents of the OnCommand Unified Manager Core Package on page 17Contents of the OnCommand Unified Manager Host Package on page 19Comparison of OnCommand Unified Manager Express edition and Standard editions (7-Modeenvironments only) on page 20What a host service is (7-Mode environments only) on page 16

Overview of OnCommand Unified Manager manageability software components | 15

What a host service is (7-Mode environments only)A host service runs on physical or virtual machines and includes plug-ins that enable the DataFabricManager server to discover, back up, and restore virtual objects, such as virtual machines anddatastores. A host service also enables you to view virtual objects in the OnCommand UnifiedManager.

When you make changes to your virtual infrastructure, automatic notification is sent from the hostservice to the DataFabric Manager server. You can manually start a rediscovery job to see yourchanges. You might need to refresh the host service information to see the updates in theOnCommand console.

The host service software is included as part of the installation of the OnCommand Unified ManagerHost Package. You can install multiple host services on multiple vCenter Servers or virtualmachines.

You must register at least one host service with the DataFabric Manager server before you can backup or restore data. Registration can be done during the installation process or after installation, fromthe Host Services tab accessible from the Administration menu in the OnCommand console. Afterregistration, you can monitor and manage host services from the Host Services tab.

Host services notify the DataFabric Manager server about the progress of operations. If theDataFabric Manager server goes down, the host service caches messages and pushes the messages tothe server as soon as the server is available. The DataFabric Manager server reviews the messages,and if any operations are incomplete or have failed, the server might restart these operations.

In addition, if the DataFabric Manager server is unavailable, you can still perform backup and restoreoperations from the host service by using the OnCommand Unified Manager Windows PowerShellcmdlets.

Guidelines for managing host services

Following are some guidelines to consider when managing host services:

• Messages from host services are stored persistently in the DataFabric Manager server databasehsNotifications table. This table continues to grow over time and can quickly become huge in alarge environment. You can use the following global options to manage the size of this table:

• hsNotificationsMaxCount

• hsNotificationsPurgingInterval

• When you register a host service with the DataFabric Manager server, you can type the fullyqualified domain name (FQDN) or IP address in the IPv4 format.

• If you change the certificate on a host service or uninstall a host service and then reinstall it, youmust unregister the host service from DataFabric Manager server using the -f flag. See theunregister man page for more information.


• The OnCommand Unified Manager Host Package upgrade does not force host services to re-register with the DataFabric Manager server. Therefore, if you unregister a host service from theDataFabric Manager server prior to an OnCommand Unified Manager Host Package upgrade,you must manually register the host service to the DataFabric Manager server after the upgrade isfinished.

Related tasks

Installing OnCommand Unified Manager Host Package on page 49

Contents of the OnCommand Unified Manager CorePackage

Understanding what components compose the OnCommand Unified Manager Core Package andwhat these components enable you to do helps you determine which components you want to enableduring the installation and setup process.

Related concepts

Comparison of OnCommand Unified Manager Express edition and Standard editions (7-Modeenvironments only) on page 20

Components installed with the OnCommand Unified Manager CorePackage

Understanding the different components of the OnCommand Unified Manager Core Package helpsyou determine which components you want to enable during the installation and setup process.

The following components are installed on your system:

DataFabric Manager server Enabled by default.

DataFabric Manager serverservices

Enabled by default.

N series Management Console withprotection, provisioning, andPerformance Advisor capabilities

Bundled with the Core Package but must be installedseparately.

OnCommand Windows PowerShellcmdlets

Downloaded with the Core Package but must be installedseparately. Perform local backup and restore operations ofvirtual objects, as well as mount and unmount operations,using the Windows PowerShell interface.

Related tasks

Downloading OnCommand Unified Manager Core Package on page 37


Installing OnCommand Unified Manager Core Package on Windows on page 38Installing OnCommand Unified Manager Core Package on Linux on page 40

Functionality available with the OnCommand Unified Manager CorePackage

You can manage physical storage objects on primary and secondary storage after installingOnCommand Unified Manager Core Package software using OnCommand console, OperationsManager console, N series Management Console, and separate PowerShell Cmdlets for OnCommandUnified Manager, which all are installed with OnCommand Unified Manager Core Package.

The Core Package includes the OnCommand Unified Manager graphical user interface (GUI)console from which you can access storage management functionality that was previously accessiblethrough separate IBM N series software products. OnCommand Unified Manager delivers access tothis functionality through three GUI consoles and separate set of PowerShell Cmdlets forOnCommand Unified Manager:

OnCommand console

The OnCommand console enables you to perform the following tasks:

• View a set of dashboard panels that provide high-level status of physical and virtual objects andsupport drill-down capabilities.

• Create and edit datasets for protecting virtual objects.• Initiate backup and recovery of virtual objects, which is executed by the host service plug-ins.• Launch other capabilities in the Core Package.• Export, share, schedule, sort, filter, hide, and print data in the reports for physical objects.

Operations Manager console

The Operations Manager console enables you to perform the following tasks:

• Manage users and roles.• Monitor clusters, nodes, and vFiler units.• Monitor physical objects for performance issues and failures.• Manage storage systems, vFiler units, and virtual servers.• Schedule and manage scripts.• Track storage usage and available capacity.

N series Management Console

The N series Management Console enables you to perform the following tasks:

• Provision physical resources.• Back up and restore physical objects.• Manage space on secondary storage.• Provide disaster recovery for physical objects (automated failover and manual failback).


• Monitor performance.• View dashboards for physical objects.• Create and edit storage services.

PowerShell Cmdlets for OnCommand

The PowerShell Cmdlets for OnCommand enable you to manage OnCommand Unified Managerprotection-related capabilities through the command-line interface.

Related tasks

Downloading OnCommand Unified Manager Core Package on page 37Installing OnCommand Unified Manager Core Package on Windows on page 38Installing OnCommand Unified Manager Core Package on Linux on page 40

Contents of the OnCommand Unified Manager Host PackageUnderstanding what components compose the OnCommand Unified Manager Host Package andwhat these components enable you to do helps you determine which components you want to enableduring the installation and setup process.

Related concepts

What a host service is (7-Mode environments only) on page 16

Components installed with the OnCommand Unified Manager Host PackageUnderstanding the different components of the OnCommand Unified Manager Host Package helpsyou prepare for installing the Host Package on your system.

The following components are installed on your system:

OnCommand UnifiedManager host serviceVMware plug-in

A plug-in that receives and processes events in a VMware environment,including discovering, restoring, and backing up virtual objects such asvirtual machines or datastores. This plug-in executes the events receivedfrom the host service.

Host service Software that enables the DataFabric Manager server to forwardrequests, such as the request for a restore operation, to the appropriateplug-in and to send the final results of the specified job to that plug-in.

Host service WindowsPowerShell cmdlets

Cmdlets that perform virtual object discovery, local restore operations,and host configuration when the DataFabric Manager server isunavailable.


Related tasks

Downloading the OnCommand Unified Manager Host Package on page 48Installing OnCommand Unified Manager Host Package on page 49

Functionality available with the OnCommand Unified Manager HostPackage in a VMware environment

You can discover and manage virtual objects after installing OnCommand Unified Manager HostPackage software.

OnCommand Unified Manager Host Package enables you to perform the following tasks in aVMware environment:

• Create a dataset and then add virtual machines or datastores to the dataset for data protection• Assign local protection and optionally remote protection policies to the dataset• View storage details and space details about a virtual object• Perform an on-demand backup of a dataset• Mount existing backups onto an ESX server, to support tasks such as backup verification, single

file restore, and restoration of a virtual machine to an alternate location• Restore data from local and remote backups, as well as restoring data from backups made before

the introduction of OnCommand Unified Manager management software

Related tasks

Downloading the OnCommand Unified Manager Host Package on page 48Installing OnCommand Unified Manager Host Package on page 49

Comparison of OnCommand Unified Manager Expressedition and Standard editions (7-Mode environments only)

During an initial OnCommand Unified Manager Core Package installation in 7-Mode environments,you can choose to install either the Express edition or the Standard edition of the DataFabricManager server, depending on your deployment requirements.

The DataFabric Manager server is included as part of the OnCommand Unified Manager CorePackage installation and provides infrastructure services such as discovery, monitoring, role-basedaccess control (RBAC), auditing, and logging. If you are upgrading from a previous version of theDataFabric Manager server, the same edition you previously installed is automatically selected.

Express edition

The OnCommand Unified Manager Express edition is intended for smaller environments of no morethan four storage systems and no more than one vCenter Server.

Because of the reduced software footprint, the Express edition can be installed on a shared system. Ifyou are also installing the OnCommand Unified Manager Host Package for your virtualized


environment, you can install the Core and Host packages on the same system. After installation issuccessfully completed, you can use the Express Configuration wizard to set up the services installedon your system. The wizard simplifies configuration by automating aspects of the configurationprocess.

The Express edition has the same level of data protection capability as the Standard edition, but withreduced monitoring capabilities for storage. Smaller environments generally do not require all of thefunctionality needed for large-scale environments. Eliminating unnecessary monitoring increases theperformance levels in a small environment.

After installation of the Express edition, you must configure your environment before you can createbackups. The simplest way to complete the configuration is to use the Express Configuration wizard,accessed from the Administration menu in the OnCommand console. The wizard configures yourhost service (required for virtual environments), discovers storage on your system, and groups thatstorage into a logical entity called a resource pool.

You can upgrade from the Express edition to the Standard edition if you later determine that youwant to use the additional monitoring functionality provided by the Standard edition.

Standard edition

The OnCommand Unified Manager Standard edition provides functionality in the DataFabricManager server that is needed for larger deployments. This additional functionality requires thatOnCommand Unified Manager and its DataFabric Manager server must be installed on a dedicatedsystem.

The Standard edition does not offer a configuration wizard because its additional functionalityrequires more configuration considerations. You can do the post-installation configuration from theOnCommand console graphical user interface.

After the Standard edition is installed, you cannot downgrade to the OnCommand Unified ManagerExpress edition without losing the content of your existing database. The extended functionality andserver database cannot be downsized to work with the Express edition.

Related tasks


Functionality available in the Standard and Express editionsSpecific DataFabric Manager server functionality is automatically enabled or disabled in theStandard and Express editions of the OnCommand Unified Manager Core Package.

Functionality Availability inStandard edition

Availability inExpress edition

Chargeback reports Y Y

All DataFabric Manager services Y Y




Discovery of agents, and SAN in 7-ModeDiscovery of clusters, agents, and SAN inclustered environments

Y N

Discovery of storage systems Y Y

Events and alerts Y Y

Capability to manage the clustered environment Y N

Monitoring of agents, host RBAC, quotas, SANhosts, and Vservers in 7-ModeMonitoring of clusters, agents, host RBAC,quotas, SAN hosts, and Vservers in clusteredenvironments

Y N

Monitoring of multiple storage systemconfigurations

Y N

Performance Advisor, in the N seriesManagement Console

Y N

Protection capability, in the N series ManagementConsole

Y Y

Provisioning capability, in the N seriesManagement Console

Y Y

Role-based access control (RBAC) Y Y

Schedule pre-configured for DataFabric Managerserver database backups

N Y

SOAP and ZAPI Interfaces Y Y

Automatic configuration of storage services andresource pools

N Y

Web UI reporting Y Y




Capability to edit monitoring intervals, in theOperations Manager console and the CLI

All the monitoringintervals can be edited

The followingmonitoring intervalsare read-only;however, the defaultis set to a higherinterval than those inthe Standard edition:

• Snapshotmonitoringinterval

• File systemmonitoringinterval

• LUN monitoringinterval

• SnapMirrormonitoringinterval

• SnapVaultmonitoringinterval

• Discovery interval• shareMonInterval

(CLI-only)• dpReaperInterval

(CLI-only)


System requirements

Before you install the software, you must ensure that your storage system conforms to all supportedplatform requirements. Servers running OnCommand Unified Manager Core Package orOnCommand Unified Manager Host Package must meet specific software, hardware, and operatingsystem requirements.

Browser support, requirements, and limitationsTo ensure that you can install and launch the software successfully, you must follow therequirements and limitations for the Microsoft Internet Explorer and Mozilla Firefox browserssupported by the OnCommand Unified Manager management software.

Supported browsers

The OnCommand Unified Manager management software supports the following browsers, based onthe operating system and the GUI console used:

Operatingsystem

OnCommandpackage installed

OnCommand GUIconsole used

Supported browser

Windows Core Package only OnCommand consoleonly

• Microsoft Internet Explorer 8,9, 10

• Mozilla Firefox 17.0, 18.0,and 19.0

• Google Chrome 22.0, 23.0,24.0

Windows Core Package andHost Package

OnCommand consoleand OnCommand Plug-in for VMware

• Windows Internet Explorer 8,9, 10

• Mozilla Firefox 17.0, 18.0,and 19.0

• Google Chrome 22.0, 23.0,24.0

Linux Core Package only OnCommand consoleonly

Mozilla Firefox 17.0, 18.0, and19.0

See the N series interoperability matrix website (accessed and navigated as described in Websiteson page 10) Tool for possible updates to this information.


Browser requirements and limitations

MozillaFirefox

Not all versions of Firefox are supported. You should disable the automaticupgrade feature in Firefox to avoid installing an unsupported version.

MicrosoftInternetExplorer,version 8

• Mozilla Firefox versions 17.0, 18.0, and 19.0• To avoid browser display issues, you must disable the Compatibility View

feature before launching the OnCommand console. For details, see theMicrosoft support site.

• To ensure that OnCommand console can launch, you must ensure that activescripting and that binary and script behaviors are enabled.

• If enhanced security is enabled in Internet Explorer 8, you might have to addhttp://DataFabric Manager server IP address:8080 to the browser'slist of trusted sites so that you can access the server.You might also have to add port 8443 to the list of trusted sites if you areusing SSL.You can add ports and URLs in the Security tab under Tools > InternetOptions.

MicrosoftInternetExplorer,version 9

If enhanced security is enabled, you must disable it. If enhanced security isenabled in Internet Explorer 9, the OnCommand console might not load.

Related references

Required ports for the Core Package on page 31

Related information

Microsoft Support IBM N series interoperability matrix: www.ibm.com/systems/storage/network/interophome.html

Accessing the OnCommand console on a Linux-based PCIf you install and run DataFabric Manager server on a Linux workstation or server, you must launchthe OnCommand console GUI using the Internet Explorer 8 or Firefox browser on a separateWindows system to manage the DataFabric Manager server, which is running on a Linux-basedcomputer.

Steps

1. Install the OnCommand Unified Manager Core Package on a Linux workstation or server.

2. Install the N series Management Console on a Windows machine.

System requirements | 25

http://support.microsoft.com/

http://www.ibm.com/systems/storage/network/interophome.html

3. Install the Firefox or Internet Explorer browser on the same Windows machine as the N seriesManagement Console.

4. Configure the N series Management Console and the browser to point to the Linux workstation orserver where the DataFabric Manager server is installed.

5. Launch the OnCommand console GUI using the Internet Explorer or Firefox browser that isrunning on the Windows machine where it can communicate with the DataFabric Manager serverthat is running on the Linux workstation or server.

License requirementsEach of the OnCommand Unified Manager components has specific licensing requirements.

Core Package OnCommand Unified Manager Core Package does not require a license.

Host Package OnCommand Unified Manager Host Package requires one license per storagesystem, but it does not generate any license key.

DataFabricManager server

The DataFabric Manager server requires one core license key, which is freeand is used only to establish a unique serial number for the server.

Data ONTAPrequirements

Certain OnCommand Unified Manager functionality requires other types oflicenses for Data ONTAP.

OnCommand Unified Manager Core Package 5.2 does not support theBusiness Continuance Option (BCO) license because IBM has announced itsend of support. If you are using the BCO license to monitor and manage yourdata protection environment, use the data protection capability of the N seriesManagement Console in Core Package 5.2. Otherwise, use Core Package 5.1or earlier.

See the N series interoperability matrix website (accessed and navigated as described in Websiteson page 10) Tool for details.

Related information

IBM N series support website: www.ibm.com/storage/support/nseries

License requirements for data protectionIf you want to use the Business Continuance Option (BCO) license for data protection, you shoulduse Core Package 5.1 or earlier. If you want to upgrade to Core Package 5.2, you must use the Nseries Management Console to monitor and manage your data protection environment.

In OnCommand Unified Manager Core Package 5.2, you cannot use the BCO license to monitor andmanage your data protection environment. OnCommand Unified Manager Core Package 5.2 does notsupport the BCO license because IBM has announced end of support for this feature.


http://www.ibm.com/storage/support/nseries

Important: Before upgrading to OnCommand Unified Manager Core Package 5.2, all BCOfunctionality must be transferred to protection capability or removed.

Network storage requirements for database filesTo enable optimal database access and performance results, DataFabric Manager server requires thatthe DataFabric Manager server database files be installed on a server using either SAN or iSCSI toconnect to the network.

Sybase and DataFabric Manager server do not support accessing the DataFabric Manager serverSybase database files on NAS.

You should not delete the SQL files that are installed in the /tmp directory. If the SQL files aredeleted from the /tmp directory, the DataFabric Manager server cannot start.

Related information

Running a SQL Anywhere

OnCommand Unified Manager Core Package hardware andsoftware requirements

Before installing the OnCommand Unified Manager Core Package, ensure that your system meetsthe hardware and software requirements.

Software required prior to installing OnCommand Unified Manager CorePackage

Before installing OnCommand Unified Manager Core Package, you must install Adobe Flash Player8.0 or later on the machine from which you launch the OnCommand console.

You can download the software from the Adobe downloads site.

Before you download Flash Player, you should ensure that file downloads are enabled in your webbrowser and, if you are using Microsoft Internet Explorer, verify that the security settings forActiveX controls are enabled.

You must install Adobe Flash Player from each browser type that you intend to use with theOnCommand console, even if the browsers are on the same system. For example, if you have bothMozilla Firefox and Microsoft Internet Explorer on the same system and you think you might useboth browsers to access the OnCommand console, you must install Adobe Flash Player using theFirefox browser, and then install Adobe Flash Player using the Internet Explorer browser.


http://www.sybase.com/detail?id=1034790

Related information

Adobe Downloads

Software required for Open Systems SnapVaultYou must separately download and install Open Systems SnapVault software if you intend to backup and restore data residing on non-IBM N series physical storage systems; otherwise, you cannotback up and restore data on those storage environments.

OnCommand Unified Manager Core Package supports the use of Open Systems SnapVault to backup and restore virtual machines in a non-IBM N series storage environment, but it is not required.OnCommand Unified Manager Core Package supports Open Systems SnapVault 2.6.1, 3.0, and3.0.1.

Related information


Software required for DataFabric Manager Host Agent (7-Modeenvironments only)

You must separately download and install DataFabric Manager Host Agent software if you wantOnCommand Unified Manager to monitor SAN hosts.

The Host Agent software collects information such as operating system name and version, HBA portdetails, and file-system metadata, and then sends that information to the DataFabric Manager server.The DataFabric Manager Host Agent software must be installed on any Windows or Linux hostsfrom which you want to monitor SAN host IBM N series OnCommand management software.

DataFabric Manager Host Agent is also required if you want to remotely start, stop, or restart OpenSystems SnapVault software by using N series Management Console. In this case, the Host Agentmust be installed on the same machine as Open Systems SnapVault.

The minimum version supported by OnCommand Unified Manager Core Package is DataFabricManager Host Agent version 2.7.

Related information


Hardware requirements for Windows Server 2008 with 1 to 25 storagesystems

You must meet certain software and hardware requirements when you use systems running Windows64-bit OS on x64 hardware.

Operating system requirements

The software requirements are as follows:


http://www.adobe.com/downloads/



• Microsoft Windows Server 2008, Enterprise or Standard edition• Microsoft Windows 2008 R2, Enterprise or Standard edition• Microsoft Windows Server 2008 or 2008 R2 running on VMware ESX 3.5, 4.0, or 5.0

Hardware requirements

The hardware requirements are as follows:

Hardware Requirements

Processor • Intel or AMD x64 processor• 2 GHz or faster CPU

Memory • 4 GB RAM (minimum)

Disk space • 10 GB (minimum)• 40 GB (recommended)

Temporary disk space for installation • 4 GB

Requirements for Windows Server 2008 with 25 or more storage systemsYou must follow certain hardware and software requirements when you use systems runningWindows 64-bit OS on x64 hardware.


The software requirements are as follows:

• Microsoft Windows Server 2008, Enterprise or Standard edition• Microsoft Windows 2008 R2, Enterprise or Standard edition• Microsoft Windows Server 2008 or 2008 R2 running on VMware ESX 3.5, 4.0, or 5.0


The hardware requirements are as follows:



Memory • 6 GB RAM (minimum)• 12 GB RAM (recommended)



Disk space • 12 GB (minimum)• 60 GB (recommended)


Requirements for Linux workstation or server with 1 to 25 storage systemsTo ensure that your installation succeeds, you must follow certain software and hardwarerequirements when you use systems running Linux workstation or server.


The software requirements for 64-bit Linux workstation or server are as follows:

• Oracle Enterprise Linux 5.6, 6.0, or 6.1• Red Hat Enterprise Linux Server 5.6, 5.7, 5.8, 6, 6.1, or 6.2• SUSE Linux Enterprise Server 10 SP3, 10 SP4, 11, 11 SP1, or 11 SP2

The software requirements for 64-bit Linux server on VMware ESX 4.0, ESX 4.1, ESXi 4.0, ESXi4.1, or ESXi 5.0 are as follows:

• Red Hat Enterprise Linux Server 5.6, 5.7, 5.8, 6, 6.1, or 6.2• SUSE Linux Enterprise Server 10 SP3, 10 SP4, 11, 11 SP1, or 11 SP2


The hardware requirements for 64-bit Linux workstation or server and 64-bit Linux server onVMware ESX or ESXi are as follows:




Disk space • 4 GB of free disk space (minimum)• 8 GB (recommended)



Requirements for Linux workstation or server with 25 or more storagesystems

To ensure that your installation succeeds, you must meet certain software and hardware requirementswhen you use systems running Linux workstation or server.


The software requirements for 64-bit Linux workstation or server are as follows:

• Oracle Enterprise Linux 5.6, 6.0, or 6.1• Red Hat Enterprise Linux Server 5.6, 5.7, 5.8, 6, 6.1, or 6.2• SUSE Linux Enterprise Server 10 SP3, 10 SP4, 11, 11 SP1, or 11 SP2

The software requirements for 64-bit Linux server on VMware ESX 4.0, ESX 4.1, ESXi 4.0, ESXi4.1, or ESXi 5.0 are as follows:

• Red Hat Enterprise Linux Server 5.6, 5.7, 5.8, 6, 6.1, or 6.2• SUSE Linux Enterprise Server 10 SP3, 10 SP4, 11, 11 SP1, or 11 SP2


The hardware requirements for Linux workstation or server are as follows:



Memory • 6 GB RAM (minimum)• 12 GB RAM (recommended)

Disk space • 4 GB of free disk space (minimum)• 8 GB (recommended)


Required ports for the Core PackageYou might have to configure your firewall on OnCommand Unified Manager Core Package to opendefault ports that enable communication between DataFabric Manager server and variouscomponents, such as managed storage systems and agents. If a port is not open, communication failsbetween DataFabric Manager server and the storage system or other component.

The following default ports must be open on your firewall:


Default port number Description

22 The port used for initiating, on storage systems, a secure clusterconsole, secure storage system takeover and giveback, andsecure remote command executionThe port is also used for vFiler unit monitoring andmanagement.

23 The port used to initiate a Telnet session to managed storagesystems

25 The SMTP port used by DataFabric Manager server to sendemail for alarms and AutoSupport notification when theautosupportProtocol option is set to SMTP

80 The port used for storage system management

161 The port used to communicate with storage systems

162 The port used by managed storage systems to send SNMP trapsto DataFabric Manager server to speed up monitoring ofimportant eventsThis port is configurable.

443 The port used for SecureAdmin-based storage systemmanagement

514 The port used for initiating, on storage systems, a clusterconsole, storage system takeover and giveback, and remotecommand execution, as well as for vFiler unit monitoring andmanagement

4092 The port used to connect to the DataFabric Manager Host Agent

4093 The port used for a secure connection to the DataFabricManager Host Agent

8080 The port used for Operations Manager console access

8088 The port used for N series Management Console access

8443 The port used for secure Operations Manager console access

8488 The port used for secure N series Management Console access

10000 The port used by Protection Manager to monitor and managestorage system SnapVault and SnapMirror relationships, andSnapVault relationships from Open Systems SnapVault agents


Related references

Designated ports for the OnCommand Unified Manager Host Package on page 35

OnCommand Unified Manager Host Package hardware andsoftware requirements

Before installing OnCommand Unified Manager Host Package, you must ensure that your systemmeets the hardware and software requirements.

Hardware requirementsYour Windows system must meet minimum hardware requirements before you can installOnCommand Unified Manager Host Package. These requirements apply to all virtual environments.The actual requirements depend on your system configuration.


Processor • Intel or AMD x64 processor with 2 GHz or faster• Intel or AMD x86 processor with 2 GHz or faster


Disk space • 40 GB (minimum)

Temporary disk space for installation • 4 GBRequired for the Windows drive

Operating system requirementsYou must ensure that the OnCommand Unified Manager Host Package supports your operatingsystem.

Operating systems

The Host Package supports Microsoft Windows Server 2008 or 2008 R2 running on VMware ESX3.5 or later.

See the interoperability matrix Tool for details.

Related information

IBM N series interoperability matrix: www.ibm.com/systems/storage/network/interophome.html


http://www.ibm.com/systems/storage/network/interophome.html

Software required prior to installing OnCommand Unified Manager HostPackage

Before installing OnCommand Unified Manager Host Package for the first time, you must havecertain Microsoft .NET Framework, Microsoft Net.TCP Port Sharing Service, Microsoft WindowsPowerShell, Windows Installer, Microsoft Visual C++, and Microsoft hotfixes already installed oneach system on which Host Package is to be installed.

Microsoft .NET Framework

OnCommand Unified Manager supports Microsoft .NET 3.5 SP1 but not 4.0. If you have installed4.0, you do not have to downgrade; you can just install 3.5 SP1. If both .NET versions are installedon the system, OnCommand Unified Manager uses 3.5 by default.

Microsoft Net.TCP Port Sharing Service

This service is not enabled by default; it must be manually enabled prior to installing Host Package.See the Microsoft MSDN library for more information.

Microsoft Windows PowerShell

You can search using the text string “powershell” on the Microsoft Support site and select theappropriate version for your system. The minimum required version is PowerShell 1.0, butPowerShell 2.0 is required to use the DataFabric Manager server PowerShell cmdlets.

Note: On Windows Server 2008, PowerShell 1.0 is installed by default, but you must enable it onthe server. You must download and install PowerShell 2.0.

Microsoft Visual C++ 2008 SP Redistributable Package on Windows Server 2008Server Core installations

The following software packages are required only for the server core or minimal installation optionfor Windows Server 2008. You can view information about and download the software from theMicrosoft Download Center.

• You must install the Microsoft Visual C++ 2008 SP Redistributable Package (x86) and theMicrosoft Visual C++ 2008 SP Redistributable Package (x64).

Microsoft hotfix

The hotfix KB 981929 is required and can be downloaded from the Microsoft Support site.

Related information

Microsoft Support siteMicrosoft Download Center


http://msdn.microsoft.com/en-us/library/


http://www.microsoft.com/downloads/en/default.aspx

Designated ports for the OnCommand Unified Manager Host PackageThe OnCommand Unified Manager Host Package uses designated ports to enable communicationbetween components. If the Windows Firewall is enabled, you must ensure that the firewall is set toallow exceptions for the designated ports.

For firewalls other than Windows, you must manually grant access to the designated ports that are tobe used for the Host Package installation. The installer attempts to create the necessary exceptions todesignated ports in your Windows firewall; if you have other types of firewalls in place, verify thatthese ports are available.

Note: The installer automatically creates firewall exceptions for the first seven ports listed in thetable.

All of the ports except those so noted in the following table can be used to install the OnCommandUnified Manager Host Package with a script.

Designated port number Description

8699 The port used by the OnCommand Unified Manager hostservice administrator

808 The OnCommand Unified Manager TCP/IP endpoint

8799 The port used by the OnCommand Unified Manager hostservice agent

8897 The port used by the OnCommand Unified Manager fileservice

8044 The port used by the OnCommand Unified Manager hostservice VMware plug-in

8043 The port used by SnapManager for Virtual Infrastructure

8480 The port used by the DataFabric Manager server

8488 The DataFabric Manager server HTTPS port, which isused for HTTP connections

443 The port used by the vCenter Server

Note: This port is used only for installing theOnCommand Unified Manager Host Package with ascript.

Related references



Installing the OnCommand Unified Manager CorePackage

The OnCommand Unified Manager Core Package provides management capabilities for yourphysical storage environment and, when the OnCommand Unified Manager Host Package is alsoinstalled, the OnCommand console can display the physical-to-virtual mapping as well as providepolicy-based local and remote backup and recovery for virtual objects.

Installation requirements specific to 7-Mode environmentsSome OnCommand Unified Manager installation and setup features are specific to 7-Modeenvironments and are noted as 7-Mode only in the documentation. All other installation information,requirements, and instructions apply to both 7-Mode and clustered environments.

When you begin installing OnCommand Unified Manager in a 7-Mode environment, you must select7-Mode when prompted.

When you install OnCommand Unified Manager in a 7-Mode environment, you can choose either theExpress edition or the Standard edition of the software. If you are upgrading OnCommand UnifiedManager from a version earlier than 5.0, Express edition is not supported.

If you change your environment from clustered to 7-Mode, you must delete the clustered objectsfrom the DataFabric Manager server.

Related concepts

What a host service is (7-Mode environments only) on page 16Comparison of OnCommand Unified Manager Express edition and Standard editions (7-Modeenvironments only) on page 20Software required for DataFabric Manager Host Agent (7-Mode environments only) on page 28

Related tasks

Configuring the OnCommand Standard edition server with host services (7-Mode only) on page59Configuring the OnCommand Unified Manager Express edition server (7-Mode environmentsonly) on page 55


Installation requirements specific to clustered environmentsOnCommand Unified Manager supports both clustered and 7-Mode environments, however; thereare some minor distinctions in the installation process in the clustered environment of which youshould be aware.

When you begin installing OnCommand Unified Manager in a clustered environment, you mustselect clustered environment when prompted.

If you are installing or upgrading OnCommand Unified Manager in a clustered environment, you caninstall only the Standard edition of the software.

When you upgrade your 7-Mode environment to a clustered environment, you must delete the 7-Mode objects from the DataFabric Manager server.

Upgrading from the Express edition of OnCommand Unified Manager to a clustered environment isnot allowed. If you currently have the Express edition of OnCommand Unified Manager installed,you must first upgrade to the Standard edition of OnCommand Unified Manager 5.0.

Host services and DataFabric Manager Host Agent are not supported in a clustered environment. Ifyou are managing host services when upgrading to a clustered environment, you are notified that thehost services will be removed. Information related to host services and DataFabric Manager HostAgent features are noted as 7-Mode only in the documentation. All other installation information,requirements, and instructions apply to both 7-Mode and clustered environments.

Downloading OnCommand Unified Manager Core PackageBefore installing OnCommand Unified Manager Core Package, you must download the executablefile, from the N series support website (accessed and navigated as described in Websites on page 10).

Related tasks

Downloading the OnCommand Unified Manager Host Package on page 48

Related information


Installing the OnCommand Unified Manager Core Package | 37


Installing OnCommand Unified Manager Core Package onWindows

After you have met the guidelines, requirements, and restrictions for installing OnCommand UnifiedManager Core Package, you can follow the prompts in the installation wizard to install the software.

Before you begin

• You must have administrator privileges for the Windows computer on which you are installingthe Core Package.

• You must have downloaded the setup file.• You must have the following items:

• The DataFabric Manager server license key• Credentials for network access• The IP address of the server on which you are installing the software• The path of the directory on which you want to install, if different from the default location

• In addition, your antivirus software must include the following changes:

• Either the antivirus software is disabled or an exclusion is added for the DataFabric Managerserver.If this condition is not met, the installation fails.

• The Sybase ASA files are excluded to avoid both DataFabric Manager server performanceissues and the possibility of database corruption.

About this task

If you have to manage both 7-Mode and clustered Data ONTAP server environments, you mustinstall two separate Core Packages on two Windows servers.

For optimal performance, the only other application that must be installed on the system runningCore Package software is OnCommand Unified Manager Host Package.

During the Core Package installation, if you select the Standard edition in the installation wizard, youconfigure the host service manually. If you select the Express edition, you can use the ExpressConfiguration wizard to configure a host service.

Note: The Express edition is available only when you choose 7-Mode as your environment.

Steps

1. Start the Core Package installation wizard by running the appropriate setup file.

2. Choose the environment: 7-Mode or Cluster-Mode.


Attention: After the Core Package installation is complete, you cannot change theenvironment.

3. Depending on your environment, perform the appropriate action:

If you selected ... Then...

7-Modeenvironment

a. Select Standard edition or Express edition to specify which version of theDataFabric Manager server you want to install:

• If you select the Standard edition, you can configure your environmentinformation and your future backup and recovery operations manually in theOnCommand console after the installation.

• If you select the Express edition, you can use the Express Configurationwizard to simplify the setup of your environment and your future backup andrecovery operations.

b. Continue responding to the prompts.

Cluster-Modeenvironment

Continue responding to the prompts.

4. Select the installation location, if different from the default.

Note: Do not change the default location of the local TempFolder directory, or the installationfails. The installer automatically extracts the installation files to the %TEMP% location.

5. Review the summary screen and consider whether you want to make changes before completingthe installation, and then click Install.

6. When the Installation Complete screen is displayed, click Next to continue.

7. If you want to start the OnCommand console, clear your browser cache, and then select LaunchOnCommand console.

If you have not yet installed OnCommand Unified Manager Host Package, download and installthe Host Package on the same server or on a different server, clear your browser cache, and thenstart the OnCommand console from your browser.

8. Click Finish.

After you finish

• During the installation process, the installer creates some temporary folders that are automaticallydeleted the next time you reboot the system.You can delete these folders without adversely affecting the installation of the Core Package.

• When you finish installing the Core Package, you can install the Host Package and use theconfiguration wizard to configure a host service.

Related concepts

Installing OnCommand Unified Manager Host Package on page 48


OnCommand Unified Manager Core Package hardware and software requirements on page 27Comparison of OnCommand Unified Manager Express edition and Standard editions (7-Modeenvironments only) on page 20

Related tasks

Downloading OnCommand Unified Manager Core Package on page 37Determining whether a storage system belongs to a workgroup or a domain on page 70

Related references

Software required prior to installing OnCommand Unified Manager Core Package on page 27

Installing OnCommand Unified Manager Core Package onLinux

After you have met the guidelines, requirements, and restrictions for installing OnCommand UnifiedManager Core Package, you can follow the prompts in the installation wizard to install the software.

Before you begin


• The DataFabric Manager server license key• Credentials for network access• The IP address of the server on which you are installing the software• The path of the directory on which you want to install, if different from the default location

• In addition, your antivirus software must include the following changes:

• Either the antivirus software is disabled or an exclusion is added for the DataFabric Managerserver.If this condition is not met, the installation fails.

• Sybase ASA files are excluded to avoid both DataFabric Manager server performance issuesand the possibility of database corruption.

• If you are installing the Core Package on Red Hat Enterprise Linux Advanced Platform 5.x, theSELinux status must be disabled.

About this task

If you have to manage both 7-Mode and clustered environments for Data ONTAP, you must installtwo separate Core Packages on two Linux servers.

For optimal performance, the only other application that must be installed on the system runningCore Package software is OnCommand Unified Manager Host Package.


During the Core Package installation, if you select the Standard edition, you configure the hostservice manually. If you select the Express edition in the Setup wizard, you can use the ExpressConfiguration wizard to simplify the setup of your environment.

Note: The Express edition is available only when you choose 7-Mode as the environment.

Steps


2. Follow the prompts and then select the environment: 7-Mode or Cluster-Mode.

Attention: After the Core Package installation is complete, you cannot change theenvironment.

3. Depending on your environment type, perform the appropriate action:

If you selected... Then...

7-Modeenvironment

a. Select Standard edition or Express edition to specify which version ofDataFabric Manager server you want to install.

• If you select the Standard edition, you can configure your environmentinformation and your future backup and recovery operations manually in theOnCommand console after the installation.

• If you select the Express edition, you can use the Express Configurationwizard to simplify the setup of your environment and your future backup andrecovery operations.

b. Continue responding to the prompts.

Cluster-Modeenvironment

Continue responding to the prompts.

When the URL for opening the OnCommand console is displayed, the installation is complete.

4. Copy and paste the URL to a browser to open the OnCommand console.

Related concepts

Installing OnCommand Unified Manager Host Package on page 48OnCommand Unified Manager Core Package hardware and software requirements on page 27Comparison of OnCommand Unified Manager Express edition and Standard editions (7-Modeenvironments only) on page 20

Related tasks



Related references

Software required prior to installing OnCommand Unified Manager Core Package on page 27

Installing the OnCommand Unified Manager Core Packagewith a script

You can quickly deploy the OnCommand Unified Manager Core Package using a scripted,unattended installation. The installation script contains the installation settings for the Core Package.

Before you begin


• The script must contain the following required information:

• OnCommand Unified Manager server license key• Credentials for network access• IP address of the server on which you are installing• Directory path where you want to install if different from the default location

About this task

The installation script can reside in one of the following locations:

• Default installation script• FTP• HTTP/HTTPS• NFS• Local disk• USB flash drive

Steps

1. Create a script using the supported commands.

2. Edit the installation script as needed to change the options that are unique for each installation.

3. Save the script to the location from which you want to run it.

4. Run the scripted installation or set a schedule for when the script is to run.

After you finish

• If you selected the Express edition in the Setup wizard during the installation process, you canuse the Express Configuration wizard to simplify the setup of your environment for initial backupand recovery operations.


• If you selected DataFabric Manager server Standard edition during the installation process, youmust configure your environment manually before backup and recovery operations can takeplace.

Related references


Options you can use for the Windows installation scriptYou can use the options to configure the settings in the installation script when installing the CorePackage on Windows.

You can use the following options in the script:

Script Description

/S Performs the installation silently, without any installationscreens appearing.

/OPMOD=7-Mode/OPMOD=Cluster-Mode

Specifies whether the environment is 7-Mode or clustered.If the option is set to 7-Mode, the Core Package for a 7-Mode environment is installed.If the option is set to Cluster-Mode, the Core Packagefor a clustered environment is installed.

/EXPRESS_EDITION=YES/EXPRESS_EDITION=NO

Specifies whether the Express edition or Standard editionis installed.If the option is set to YES, the Express edition is installed.If the option is set to NO, the Standard edition is installed.

Note: If you do not specify this option, for a newinstallation the Standard edition is installed; for anupgrade, the installer checks the previous edition that isin use, and then upgrades that edition.

/LICENSEKEY=license_key Specifies the license key.

/UPGRADE Specifies that an upgrade is required.

No options are available for the following situations:

• Accepting or rejecting the AutoSupport agreement from the CLI.When a silent installation is performed, the installation assumes that you accept the AutoSupportagreement.

• Specifying whether you want to perform a backup during the upgrade.In a silent upgrade, a backup is performed by default.


• Specifying the installation directory or database backup location directory; otherwise, the defaultDataFabric Manager server paths are used.

Options you can use for the Linux installation scriptYou can use the options to configure the settings in the installation script when installing the CorePackage on Linux.

You can use the following options in the script:

Option Description

-a yes

-a no

Specifies that the AutoSupport notice agreement is accepted.If the option is not specified, the AutoSupport notice isdisplayed, which prompts you to accept or decline.

-d installation_directory Specifies the path of the installation directory.If the option is not specified, the Core Package is installed inthe default directory, for example, /opt/IBMdfm

-l licenses_key Specifies the license key.If the option is not specified, a message is displayed duringthe installation that prompts you to enter the license key.

-b yes

-b no

Specifies whether to perform a database backup during theupgrade.

-Bbackup_file_name Specifies the backup file name.If the option is not specified, the default backup file name isstored in the data directory of the installation directory.

-n Removes NetCache support if you upgrade your DataFabricManager server.

Note: You should use this option only for upgrades fromDataFabric Manager server versions earlier than 3.8.

If the option is not specified and you are upgrading from aversion earlier than 3.8, a message is displayed about theremoval of NetCache support for DataFabric Managerserver.


Option Description

-m 7-Mode-m Cluster-Mode

Specifies whether the environment is 7-Mode or clustered.If the option is set to 7-Mode, the Core Package for a 7-Mode environment is installed.If the option is set to Cluster-Mode, the Core Package fora clustered environment is installed.If you do not specify a mode and if you have the Expressedition installed, your server is upgraded to the Expressedition.

-s yes

-s noSpecifies whether the Express edition or the Standard editionis installed.If the option is set to yes, the Express edition is installed; ifthe option is set to no, the Standard edition is installed.

Note: You cannot use the Express edition if you areinstalling in a clustered environment. However, if youupgrade to clustered environment with the Expressedition, you are prompted to select the edition.

If you do not specify the option, for a new installation, youare prompted to select an option; for an upgrade, the installerchecks the previous edition that is in use, and then upgradesthat edition.

-w wrapper_directory Specifies the path for installing the DataFabric Managerserver CLI wrappers.

Setting up Web security after restoring a database on a newOnCommand Unified Manager Core Package installation

You can restore a database backup from another DataFabric Manager server instance to the newDataFabric Manager server installation, for instance, when you want to upgrade your hardware;however, database backups do not include the key and certificate file, so these must be generated orimported, and HTTPS must be enabled if it was set on the old system.

About this task

Perform these steps from a console session on the new DataFabric Manager server after you installthe OnCommand Unified Manager Core Package.

Steps

1. Perform one of the following actions:


• Enter the dfm ssl service setup command to create new client certificates.• Enter dfm ssl server import to import an existing certificate.

2. If the HTTPS service was enabled on the system from which the database backup was made, youmust also enable the HTTPS service on the new system by entering dfm option sethttpsEnabled=Yes.

Installing N series Management ConsoleYou can download and install N series Management Console through the OnCommand console. Nseries Management Console is required to perform many of your physical storage tasks. You mustinstall N series Management Console 3.3, which contains bug fixes found in the 3.2 version.

Before you begin

You must be authorized to perform all the steps of this task; your RBAC administrator can confirmyour authorization in advance.

About this task

During this task, the OnCommand console launches the Operations Manager console. Depending onyour browser configuration, you can return to the OnCommand console by using the Alt-Tab keycombination or clicking the OnCommand console browser tab. After the completion of this task, youcan leave the Operations Manager console open, or you can close it to conserve bandwidth.

Steps

1. Log in to the OnCommand console if necessary.

2. Click the File menu, and then click Download Management Console.

A separate browser tab or window opens to the Management Console Software page in theOperations Manager console.

3. Click the download link for the Linux or Windows installation.

4. In the download dialog box, click Save File.

The executable file is downloaded to your local system, from the system on which theOnCommand Unified Manager Core Package was installed.

5. From the download directory, run the nmconsole-setup-xxx.xxx executable file.

The N series Management Console installation wizard opens.

6. Follow the prompts to install N series Management Console.

Result

After installation, you can access N series Management Console from the following locations:


• On Windows systems, the default installation path is C:\Program Files\IBM\ManagementConsole.You can launch the console from the IBM directory on the Start menu.

• On Linux systems, the default installation path is/usr/lib/IBM/management_console/.You can launch the console from /usr/bin.

Installing or upgrading OnCommand Unified ManagerWindows PowerShell cmdlets

To use Windows PowerShell cmdlets with the OnCommand console, you must manually installthem. You also must manually upgrade the cmdlets if you upgrade your version of the console.

Before you begin

You must have installed the appropriate version of OnCommand Unified Manager Core Package.

Steps

1. Navigate to the appropriate folder:

If you have installed the OnCommandUnified Manager Core Package on...

Then do this...

A Windows server Navigate to the DFM_Install_dir\DFM\web\clients folder.

A Linux server Navigate to the /opt/IBMdfm/web/clients folder.

This folder contains the Windows PowerShell installation package.

2. Execute the installation file:

If you are installing thecmdlets on...

Then do this...

The same Windows server Double-click the executable file and follow the installation wizard prompts.

A different Windowsserver

Copy the installation file to the server or workstation to which you want toinstall the cmdlets and then execute the installation.

A Linux server Copy the installation file to a Windows server on which you want to installthe cmdlets and then execute the installation.

Windows PowerShell Cmdlets are not supported on Linux.

After you finish

You can execute the Windows PowerShell cmdlets for OnCommand console.


Installing OnCommand Unified Manager HostPackage

OnCommand Unified Manager Host Package provides management capabilities for your virtualizedenvironment and, when OnCommand Unified Manager Core Package is also installed, for yourphysical storage environment.

You can install OnCommand Unified Manager Host Package using the installation wizard, or youcan run an unattended installation by using a script at the Windows command prompt.

Downloading the OnCommand Unified Manager HostPackage

The OnCommand Unified Manager Host Package provides management capabilities for your virtualenvironment. Before installing the OnCommand Unified Manager Host Package, you must downloadthe software package, which is either a 32-bit or 64-bit executable file, from the N series supportwebsite (accessed and navigated as described in Websites on page 10).

Related tasks


Prerequisites for installing the Host PackageYou must ensure that you meet all the installation requirements before you begin installing the HostPackage.

• You must be a member of the local administrators group on the system that you use for your HostPackage installation.

• You must be a member of the local administrators group or a domain user on the vCenter server.• vSphere 5.0 or later must be installed on your vCenter server.• You must have purchased a license for SnapManager for Virtual Infrastructure to back up and

recover data.• The system that you use for your Host Package installation must belong to a domain rather than a

workgroup.• You must have administrator privileges for the Windows computer on which you are installing

the Host Package.• The DNS name of the Windows computer on which you are installing the Host Package must

match the actual computer name, and the computer name must not be more than 15 characters.• The Windows firewall must be set to allow exceptions.


• You must have the following items available:

• A Windows system account user name and password• The path of the directory to which you want to install, if different from the default• The IP address, user name, and password of the DataFabric Manager server• The IP address, user name, and password of the vCenter server

• If you are installing the Host Package along with the Core Package, you must install CorePackage software before installing Host Package software.If you install Host Package software first, you must start the configuration wizard after you finishinstalling Core Package software.

Installing OnCommand Unified Manager Host PackageAfter you have reviewed the guidelines, requirements, and restrictions for installing OnCommandUnified Manager Host Package, you can execute the installation wizard to install the software.

About this task

If you are installing the Host and Core Packages on the same system, a fully qualified domain namemust be used for the Core Package instead of localhost.

The installer creates a locks directory, which is used to coordinate access to resources in the vSphereClient. The locks directory is located under the OnCommand Unified Manager directory. You mustnot change the name or the location of this directory.

The IP address and host name for the system on which you are installing OnCommand UnifiedManager Host Package must have a DNS registration that resolves properly between the host serviceand the DataFabric Manager server.

You should use a dedicated Windows server for each vCenter Server instance. Having otherapplications installed on the same server can consume valuable system resources and mightdrastically reduce performance.

If the installer fails during the installation of OnCommand Unified Manager Host Package, in somerare cases, the installer does not rollback the changes made to the system. When this happens, youmust manually remove OnCommand Unified Manager Host Package using the Control Panelapplication for your operating system and then delete the folder where the OnCommand UnifiedManager Host Package was installed.

Steps

1. Start the Host Package installation wizard by running the setup file.2. Depending on your operating system, either enable Windows PowerShell or install it before you

continue with the installation of OnCommand Unified Manager Host Package:

• On Windows Server 2008 R2, PowerShell is installed by default and you do not have toenable it on the server.

Installing OnCommand Unified Manager Host Package | 49

• On Windows Server 2008, PowerShell is not installed by default and you must enable it onthe server after it is installed.To enable PowerShell, you must follow the instructions in the pop-up dialog box.

3. Select the installation location.

4. On the Service Credentials page, type the user name and password for the system on which youare installing OnCommand Unified Manager Host Package.

You must type the user name in the following format:domain name\user name

5. On the Configure Communication Ports page, type the port numbers that you want to use oraccept the default port numbers.

Note: For custom firewalls, ensure that the Core and Host Packages are using the same portnumbers.

6. On the Configure DataFabric Manager server page, type the IP address and the user name andpassword used to access the DataFabric Manager server.

You can skip the validation of the DataFabric Manager server if you do not have the servercredentials available.

7. On the vCenter Server Information page, type the host name or IP address of the system on whichthe vCenter Server is installed and the user name and password that allows the vSphere Client tocommunicate with the vCenter Server.

8. Click Install on the summary page, and then click Finish.

When you next reboot the system, you might see some hidden MS-DOS command windowsbriefly appear in the background during the removal of installer support files that could not bedeleted during the installation of OnCommand Unified Manager Host Package.

After you finish

• During the installation process, the installer creates some temporary folders that are automaticallydeleted when you next reboot the system.If you want to delete these folders, you can do so without adversely affecting the installation ofthe Host Package.

• The host service must be configured to perform backups.

Related concepts

Comparison of OnCommand Unified Manager Express edition and Standard editions (7-Modeenvironments only) on page 20

Related tasks

Downloading the OnCommand Unified Manager Host Package on page 48Determining whether a storage system belongs to a workgroup or a domain on page 70


Configuring the OnCommand Unified Manager Express edition server (7-Mode environmentsonly) on page 55

Related references

Operating system requirements on page 33Software required prior to installing OnCommand Unified Manager Host Package on page 34Designated ports for the OnCommand Unified Manager Host Package on page 35

Shared lock directories with Virtual Storage ConsoleYou can use shared lock directories to coordinate mutually exclusive activities on shared resources.

OnCommand Unified Manager Host Package installs the following directories during installation:

• Locks• VMware Plug-in• Host Services

If you plan to install OnCommand Unified Manager Host Package on the same system as VirtualStorage Console 2.1.1 or later, a best practice is to set up a shared lock directory. A shared lockdirectory is used for products that share resources through the vSphere client. This ensures thatmutually exclusive functions do not occur in parallel—for example, cloning of a virtual machinethrough Virtual Storage Console at same time that OnCommand Unified Manager Host Package isattempting to restore the same virtual machine.

Setting up a shared lock directoryTo enable the coordination of mutually exclusive activities on shared resources when OnCommandUnified Manager Host Package and Virtual Storage Console are installed on the same system, youcan create a shared lock directory.

Before you begin

You must have installed Virtual Storage Console 2.1.1 or later to create a shared lock directory.

About this task

Both OnCommand Unified Manager Host Package and Virtual Storage Console install a locksdirectory that is not shared by default. You can disable the locks directory in OnCommand UnifiedManager Host Package and set up the Virtual Storage Console locks directory as a shared lockdirectory.

Steps

1. Stop the OnCommand Host Service VMware Plug-in:

a) Click Start > Control Panel.


b) Double-click Services.

A list of enabled and disabled services for the system is displayed.c) Locate the OnCommand Host Service VMware Plug-in.

You can filter the list of services by clicking any of the column headers at the top of the list.d) Right-click the OnCommand Host Service VMware Plug-in to open the context-sensitive

menu and select Stop.

The OnCommand Host Service VMware Plug-in is disabled.

2. Delete the locks subdirectory in the OnCommand Unified Manager Host Package installationdirectory: <OC installation directory>\locks.

3. Locate and open the smvi.override file.

This file is installed by default in: <OC installation directory>\VMware Plugin\etc\smvi.override.

4. Add the following line: shared.subplugin.lock.directory=<VSC installationdirectory>\locks

5. Save and close the smvi.override file.

6. Restart the OnCommand Host Service VMware Plug-in.

Result

OnCommand Unified Manager Host Package and Virtual Storage Console will share the same lockssubdirectory.

Installing the OnCommand Unified Manager Host Packageusing a script

You can quickly deploy the OnCommand Unified Manager Host Package by creating a scriptcustomized to the needs of your particular environment, and then performing an unattendedinstallation. The installation script that you create contains your customized installation settings forOnCommand Unified Manager Host Package.

Before you begin

• You must have administrator privileges for the Windows computer on which you are installingOnCommand Unified Manager Host Package.

• Your script must contain the following required information:

• Credentials for network access• IP address of the server on which you are installing• The path of the directory to which you want to install, if different from the default location


About this task

You can store your customized installation script in one of the following locations:

• Default installation script• FTP• HTTP/HTTPS• NFS• Local disk• USB flash drive

Steps

1. Create a script using the supported commands.

2. Edit the installation script as needed to change the options that are unique for each installation.

3. Save the script in the location from which you want to run it.

4. Run the scripted installation or set a schedule for when the script is to run.

After you finish

If you are installing OnCommand Unified Manager Host Package in a 7-Mode environment, youmust configure the host service to work with the DataFabric Manager server.

If you selected the OnCommand Unified Manager Express edition during the installation of the CorePackage, you can use the configuration wizard to configure the host service.

Related references


Scripted install options for OnCommand Unified Manager Host PackageIf you choose to install OnCommand Unified Manager Host Package in a Windows environment byusing an unattended script, you can use certain options to create that script.

The following options can be used in the script:

Option Description

setup.exe /s /V"/qn PLUGIN_TYPE • Performs the installation silently, without anyinteractive screens appearing

SVCUSERNAME • Specifies the host service user name

SVCUSERPASSWORD • Specifies the host service password


Option Description

SVCCONFIRMUSERPASSWORD • Confirms the host service password

DFM_SERVER_INFO • Specifies the DataFabric Manager server IPaddress

DFM_SERVER_USERNAME • Specifies the DataFabric Manager server username

DFM_SERVER_PASSWORD • Specifies the DataFabric Manager serverpassword

VMWARE_PLUGIN_IP • Specifies the vCenter Server IP address

VCENTER_USERNAME • Specifies the vCenter Server user name

VCENTER_PASSWORD • Specifies the vCenter Server password

Ports

VCENTER_PORT • Specifies the default port for vCenter

SMVI_PLUGIN_PORT • Specifies the default port through which securechannel communication (SSL traffic) betweenDataFabric Manager server and Host Serveroccurs

DFM_SERVER_SSL_PORT • Specifies the default port through which theDataFabric Manager server and host service SSLcommunicate

DFM_SERVER_COM_PORT • Specifies the default port through which theDataFabric Manager server and host servicecommunicate

HS_ADMIN_PORT • Specifies the administration port for the hostservice

HS_MGM_PORT • Specifies the management port for the hostservice

PLUGIN_PORT • Specifies the default port through which the hostservice communicates with the VMware Plug-in


Setting up your system

After you finish installing the OnCommand Unified Manager Host Package or Core Package, youcan configure your system.

Configuring the OnCommand Unified Manager Expressedition server (7-Mode environments only)

You can use the Express Configuration wizard to simplify the setup of your system in a 7-Modeenvironment. The wizard sets up the Express edition server to discover and monitor storage systemsand host services, populates a default resource pool, associates available storage, and creates andattaches a default storage service.

Before you begin

• You must have installed the following:

• OnCommand Unified Manager Core Package• OnCommand Unified Manager Host Package• VMware vCenter• Adobe Flash Player 8.0 or later• OnCommand Unified Manager Windows PowerShell cmdlets

• You might need some or all of the following information to complete this task:

• IP address or FQDN for each host service• vCenter Server name and credentials• Name and credentials for each storage system• Port numbers, if different than the defaults• NDMP user name and password• SNMP credentials

About this task

The Express Configuration wizard configures two default storage services, remote backup andmirror, with deduplication enabled for increased efficiency. You can validate your performancerequirements to ensure that these policies align with your requirements.

Steps

1. Click the Administration menu, then click the Express Configuration option.

The Express Configuration wizard might open automatically the first time you log in to theOnCommand console after you finish the Express edition installation.

55

2. On the Add Host Service page, click Add to register a host service with the DataFabric Managerserver.

You must register each host service with the DataFabric Manager server, so that OnCommandUnified Manager is made aware of the host service and can manage it.

3. Enter values for IP Address/Name and Admin Port for the host service, then click Add.


If using the name, it must be the fully qualified domain name (FQDN). If you are installing theHost Package and the DataFabric Manager server on the same system, you must specify thehostname or a fully qualified domain name, not localhost, for the DataFabric Manager server.

4. Optional: If you need to edit settings for a host service, click Edit, make the changes, and thenclick OK.

Editing is enabled only for host services that you add manually to the list.

5. Add or edit other host services as needed, then click Next.

When you click Next, all of the hosts in the list are registered, authorized, and discovered.

6. In the Virtual Center Server Details page, select a host service from the list.

7. If a virtual center server is not listed for the host service, click Add and enter the virtual centerserver name and credentials, then click OK.

8. On the Add Storage System page, click Add to register a storage system with the DataFabricManager server.

You must register each storage system with the DataFabric Manager server, so that OnCommandUnified Manager is made aware of the storage system and can monitor it and use it for backup.

9. Enter values for IP Address/Name, User Name, and Password for the storage system.

The login credentials are validated and set in the DataFabric Manager server. Login credentialsare required for backups to succeed.

10. Modify the NDMP and SNMP settings in the Advanced Options section.

If the NDMP credentials are not set explicitly, then the login credentials are used for NDMP.NDMP credentials are required for backups to succeed.

Setting up your system | 57

11. Click Add.The credentials are validated and the storage system you added appears in the list of storagesystems.

12. Optional: If you need to edit the settings for a storage system, click Edit, make the changes, thenclick OK.

13. Optional: Add or edit other storage systems as needed, then click Next.The storage systems for which you set the credentials are pushed to the host service and thesystems are added to a default resource pool.

14. When the status screen appears, showing the configuration progress details, click Finish.

Result

The configuration wizard implements the following:

• The storage systems are configured in the DataFabric Manager server.• The storage systems are associated with the selected host service.• The storage systems are added to a default resource pool.• A default remote protection storage service is created.

After you finish

You can monitor details about discovered virtual machines from the Host Services window in theOnCommand console.

Verify that the SQL service is running. This service must be running for DataFabric Manager serverdatabase backup and restore operations to succeed.


Configuring the OnCommand Standard edition server withhost services (7-Mode only)

You must configure the host services to communicate with DataFabric Manager server, vCenterServers, and storage systems that are required for backup and recovery of your data.

Before you begin

You must have installed the following:

• OnCommand Unified Manager Core Package• OnCommand Unified Manager Host Package• Adobe Flash Player 8.0 or later• OnCommand Unified Manager Windows PowerShell cmdlets

About this task

The tasks identified in this configuration process can also be completed after initial installation andconfiguration. See the OnCommand console Help for information.

During the configuration process, job status and details about jobs can be viewed from the Jobs tab.

After you finish

After completing the configuration process, you can create backups of virtual objects from the Servertab.

Steps

1. Verifying that a host service is registered with the DataFabric Manager server (7-Modeenvironments only) on page 60

You must properly register a host service with a DataFabric Manager server before the server candiscover objects and before you can perform a backup in a virtual environment.

2. Authorizing a host service to access storage system credentials (7-Mode environments only) onpage 61

Before you can create backup jobs, you must authorize the host service to access the storagesystem credentials if it is not already authorized.

3. Associating a host service with vCenter Server (7-Mode environments only) on page 62In a VMware environment, you must authorize each host service and associate it with a vCenterServer instance. This provides part of the communication needed for discovery, monitoring,backup, and recovery of virtual server objects such as virtual machines and datastores.

4. Verifying communication between the host service and the OnCommand plug-in on page 65


You can verify that the host service is communicating with the OnCommand Unified ManagerVMware Plug-in by ensuring that virtual machines are associated with the host service. If the hostservice is not communicating with the plug-in, the software cannot perform backup jobs.

5. Associating storage systems with a host service (7-Mode environments only) on page 66For each host service instance, you must associate one or more storage systems that host virtualmachines for the host service. This enables communication between the service and storage toensure that storage objects, such as virtual disks, are discovered and that host service featureswork properly.

6. Editing storage system login and NDMP credentials from the Host Services tab (7-Modeenvironments only) on page 68

You must provide valid login and NDMP credentials for storage systems so that the DataFabricManager server can access them. If the server cannot access the storage, your backups might fail.

Verifying that a host service is registered with the DataFabric Managerserver (7-Mode environments only)

You must properly register a host service with a DataFabric Manager server before the server candiscover objects and before you can perform a backup in a virtual environment.

About this task

A host service can be registered either with the DataFabric Manager server during installation, orlater from the OnCommand console. However, you might want to verify that the registration is stillvalid when troubleshooting problems or prior to performing an action involving a host service, suchas adding a storage system to a host service.

Steps

1. From the Administration menu, select Host Services.

The Host Services tab opens.

2. In the host services list, verify that the name of the host service is listed.

When a host service is registered with the DataFabric Manager server, it displays in the hostservices list.

3. For the selected host service, verify that Discovery Status is OK and that Status is Up.

After you finish

If the host service is not displayed in the list, you must add and configure the new host service.

If Status is other than Up, or Discovery Status is other than OK, edit the host service to provide thecorrect properties.

Related tasks

Associating a host service with vCenter Server (7-Mode environments only) on page 62


In a VMware environment, you must authorize each host service and associate it with a vCenterServer instance. This provides part of the communication needed for discovery, monitoring,backup, and recovery of virtual server objects such as virtual machines and datastores.

Authorizing a host service to access storage system credentials (7-Modeenvironments only)

Before you can create backup jobs, you must authorize the host service to access the storage systemcredentials if it is not already authorized.

Before you begin

The host service must be registered with the DataFabric Manager server.

About this task

The DataFabric Manager server does not support a host service created as a generic service fromMicrosoft Windows Server Failover Cluster Manager.

Steps

1. From the Administration menu, select the Host Services option.

2. In the host service list, select the host service that you want to authorize and click Edit.

If a host service is not displayed in the list, you must add the host service and verify that it isregistered with the DataFabric Manager server.

3. In the Edit Host Service dialog box, click Authorize, review the certificate, and then click OK.

If the Authorize area is unavailable, the host service is already authorized.

When authorization is complete, the Authorize area becomes disabled.

4. Click OK.


After you finish

If you do not have storage systems associated with the host service, you must associate at least onestorage system to be able to perform backups.

After you finish editing the host service properties, you can view job progress from the Jobs subtabon the Manage Host Services window and you can view details about each job from the Jobs tab.

Associating a host service with vCenter Server (7-Mode environments only)In a VMware environment, you must authorize each host service and associate it with a vCenterServer instance. This provides part of the communication needed for discovery, monitoring, backup,and recovery of virtual server objects such as virtual machines and datastores.

Before you begin

The host service must be registered with the DataFabric Manager server; otherwise, it does notappear in the list of available host services.

The following information must be available:

• Name or IP address of the vCenter Server instance• User name and password for access to the vCenter Server instance

About this task


Steps

1. From the Administration menu, select the Host Services option.

2. In the host services list, select the host service that you want to associate and then click Edit.

If the host service is not displayed in the list, you must add the host service and verify that it isregistered with the DataFabric Manager server.

3. In the Edit Host Service dialog box, click Authorize, review the certificate, and then click OK.

If the Authorize area is disabled, the host service is already authorized.


4. Enter the vCenter Server properties.

You must specify the host name or the fully qualified domain name for host service registration.Do not use "localhost."

If the properties fields are populated, then a server is already associated with the host service thatyou selected.

If the vCenter Properties section is not displayed, you might have selected a host service that isinstalled in an environment other than VMware.

5. Click OK.

After you finish

If you do not have storage systems associated with the host service, you must associate at least onestorage system to be able to perform backups.


Related tasks

Verifying that a host service is registered with the DataFabric Manager server (7-Modeenvironments only) on page 60

You must properly register a host service with a DataFabric Manager server before the servercan discover objects and before you can perform a backup in a virtual environment.


Adding and registering a host service (7-Mode environments only)

Before you can use a VMware host, you must add the host service and register it with the DataFabricManager server.

Before you begin

The host service firewall must be disabled for the administration and management ports.

You must be authorized to perform all the steps of this task; your RBAC administrator can confirmyour authorization in advance.

Attention: Host services can be registered with only one DataFabric Manager server at a time.Before you register a host service with a new DataFabric Manager server, you must first manuallyunregister the host service from the previous DataFabric Manager server. See the DataFabricManager Host Agent Installation and Administration Guide for instructions on how to unregister ahost service from the DataFabric Manager server.

About this task


If you unregister a cluster-level host service, the DataFabric Manager server does not automaticallyregister the host service when you re-register the node. You must re-register or add the host serviceusing the cluster IP address.

Attention: If you change the name of the machine after installing the OnCommand UnifiedManager Host Package, you must uninstall the OnCommand Unified Manager Host Package andperform a fresh installation.

Steps

1. Click the Administration menu, then click the Host Services option.

2. In the Host Services tab, click Add.

3. In the Add Host Service dialog box, type the IP address or the DNS name of the host on whichthe host service is installed.

4. If the administrative port has been changed in the host service from the default, type the changedport number.

This is the port that is used by plug-ins to discover information about the host service.

5. Click Add.

Result

The host service is added and registered with the DataFabric Manager server.


Tip: If you see an error stating that the requested operation did not complete in 60 seconds, waitseveral minutes and then click Refresh to see if the host service was actually added.

After you finish

To make the host service fully operational, you might need to authorize the host service. In aVMware environment, you must edit the host service to add the vCenter Server credentials.

Related information


Verifying communication between the host service and the OnCommandplug-in

You can verify that the host service is communicating with the OnCommand Unified ManagerVMware Plug-in by ensuring that virtual machines are associated with the host service. If the hostservice is not communicating with the plug-in, the software cannot perform backup jobs.

About this task

If a host service is communicating with the VMware plug-in, the virtual machines associated with thehost service display in the VMs list on the Server tab.

Steps

1. Select the Administration menu and then select the Host Services option.

The Manage Host Services window opens.

2. In the Host Services list, identify the name of the host service that you want to validate.

3. Select the View menu and then select the Server option.

4. Scroll through the list of virtual machines to see if the VMs related to the host service are listed.

If the virtual machines are listed, the host service is communicating properly with the plug-in.

After you finish

If the virtual machines related to the host service do not display, consult the event logs on the hostservice system. You can also use the List-HSResources PowerShell cmdlet to verify that the hostservice is properly retrieving the virtual machine list from VMware.



Associating storage systems with a host service (7-Mode environmentsonly)

For each host service instance, you must associate one or more storage systems that host virtualmachines for the host service. This enables communication between the service and storage to ensurethat storage objects, such as virtual disks, are discovered and that host service features work properly.

Before you begin

You must have the following information available for each storage system you want to associate:

• IP address or name• Login and NDMP credentials• Access protocol (HTTP or HTTPS)

About this task

In a VMware environment, if the storage system that you add uses HTTP but has SSL enabled, thenthe host service uses HTTPS to communicate with the storage system. If the storage system that youadd uses HTTP and does not have SSL enabled, then the host service uses HTTP to communicatewith the storage system.

Steps

1. From the Administration menu, select Host Services.

2. In the host services list, select the host service with which you want to associate storage.

In the Storage Systems subtab is a list of storage systems currently associated with the hostservice you selected.

3. Click Edit to associate a new storage system.

The Edit Host Service dialog box opens.


4. In the Storage Systems area, click Associate.

5. Choose one of the following ways to associate the storage systems with the host service:

• To associate storage systems shown in the Available Storage Systems list, select the systemnames and click OK.

• To associate a storage system not listed in Available Storage Systems, click Add, enter therequired information, and click OK.


The newly associated storage system displays in the Storage Systems area.

6. In the list of storage systems, verify that the status is Good for the login and NDMP credentialsfor each storage system.

After you finish

If the login or NDMP status is other than Good for any storage system, you must edit the storagesystem properties to provide the correct credentials before you can use that storage system.


Editing storage system login and NDMP credentials from the Host Servicestab (7-Mode environments only)

You must provide valid login and NDMP credentials for storage systems so that the DataFabricManager server can access them. If the server cannot access the storage, your backups might fail.

Before you begin

Have the following storage system information available:

• IP address or name• Login and NDMP credentials• Access protocol (HTTP or HTTPS)


Steps

1. From the Administration menu, select Host Services.2. In the host services list, select a host service.

The storage systems associated with the selected host service display in the Host Services tab.3. In the Host Services tab, select a storage system with a login or an NDMP status of Bad or

Unknown.

4. Click Edit.5. In the Edit Host Service dialog box, click Edit.


6. Enter the appropriate login and NDMP credentials and click OK.

7. In the Host Services tab, verify that the Login Status and NDMP Status are Good.

8. Click OK.

The storage system status columns in the Host Services tab display the new status.

After you finish

After you finish editing the storage system properties, you can view job progress from the Jobssubtab on the Manage Host Services window and you can view details about each job from the Jobstab.

Determining whether a storage system belongs to aworkgroup or a domain

The storage system that you use for the OnCommand Unified Manager Core or Host Packageinstallation must belong to a domain rather than a workgroup. Prior to installing the Core or HostPackages, you must determine if the system belongs to a workgroup or a domain.

Step

1. Right‐click My Computer and click Properties and the Computer Name tab.

For details, see the documentation for your Windows operating system.

The Computer Name tab displays either a Workgroup label or a Domain label.


Certificate-based authentication

Connecting DataFabric Manager server to a virtual or cloud infrastructure network using certificate-based authentication means that authentication occurs using an SSL certificate. Using the certificatemakes the requirement for user names or passwords unnecessary.

Certificate-based authentication occurs when a client, such as the host service or cloud orchestrationtool, connects to the DataFabric Manager server with a Web service or ZAPI request. The clientpresents a self-signed certificate to DataFabric Manager server. In turn, DataFabric Manager serveraccepts the certificate, validates the certificate, and processes the request if it authenticates the client.

Certificate informationAn SSL certificate is a digital document whose legitimacy is signed off by its creator. The certificateis used to verify that a key belongs to an individual or organization.

When you install DataFabric Manager server or the host service, the truststore contains nocertificates to trust. You must add client certificates to the truststore before DataFabric Managerserver will trust those client connections.

By default, the DataFabric Manager server installs the DataFabric Manager server key and certificatepair, and any trusted certificates in a repository called the DataFabric Manager server truststore

When DataFabric Manager server is installed, it is configured to not trust any public certificateauthorities (CAs). If you want DataFabric Manager server to trust clients with certificates signed by apublic CA, you must add the root CA certificate to the truststore.

Certificates are identified in the Windows Trusted Root Certification Authorities store with thefollowing titles in the Issued To and Issued By columns:

• DataFabric Manager - VIM• DFM Host Services for VIM• DFM Plug-in for VIM

Managing certificates for cloud service clientsYou can manage certificates on your DataFabric Manager server for clients in a cloud infrastructurenetwork, including generating a key and a self-signed certificate, adding certificates to a truststore,

71

listing all certificates in a truststore, displaying details of certificates in a truststore, removing acertificate from a truststore, and disabling certificate-based authentication.

Generating a key and self-signed certificateYou can generate a key and certificate pair by using the dfm ssl service setup command.

Steps

1. On DataFabric Manager server, open a console session.

2. Enter the following command:dfm ssl service setup -f

The -f option causes the command to overwrite existing key and certificate pairs.

3. To force DataFabric Manager server to immediately use the newly generated key, enter thefollowing command:dfm ssl service reload

Adding a certificate in the truststoreYou can add a certificate in the DataFabric Manager server truststore for clients in a cloudinfrastructure network by using the dfm ssl service truststore add command.

Before you begin

The certificate must be in privacy-enhanced mail (PEM) format.

Step

1. On the DataFabric Manager server console, enter the following command:dfm ssl service truststore add -f cacert.pem

The -f option adds the certificate without prompting you for permission.

Removing a certificate from the truststoreYou can remove a cloud service client certificate from the DataFabric Manager server truststore byusing the dfm ssl service truststore remove command.

Step

1. On the DataFabric Manager server console, enter the following command:dfm ssl service truststore remove certificate_number

Displaying the list of certificates in a truststoreYou can use the DataFabric Manager server command-line interface to display a list of all thecertificates in a truststore. You might want to do this to determine how long a certificate is valid, to


find information about the certificate's issuer, or to find the certificate number assigned to a specificcertificate.

Step

1. On the DataFabric Manager server console, enter the following command:

dfm ssl service truststore list

Displaying details about certificates in a truststoreYou can display the details about one or more certificates in a truststore, including details about thecertificate serial number, signature algorithm, issuer, valid from and valid to dates, and public keyalgorithm.

Steps

1. On the DataFabric Manager server, open a console session.

2. Enter the following command:

dfm ssl service truststore detail certificate number

certificate number displays details about a specific certificate in the truststore.

You can use the dfm ssl service truststore list command to find the certificatenumbers.

Displaying the contents of the DataFabric Manager server key andcertificate file

You can display the contents of a key and certificate file, including the expiry date of the certificate,and verify whether the certificate is generated correctly by using the DataFabric Manager servercommand-line interface. The key and certificate file contents are displayed in hexadecimal format.

Step

1. On the DataFabric Manager server console, enter the following command:

dfm ssl service show -c -k -f -o output

-c selects the certificate for printing.

-k selects the key for printing.

-o saves the information to a file.

-f overwrites the file without prompting.

Certificate-based authentication | 73

Displaying DataFabric Manager server certificate detailsYou can display the DataFabric Manager server certificate details, including the certificate serialnumber, valid to and valid from dates, and signature algorithm.

Before you begin

The system date and time must be correct on the system where DataFabric Manager server isinstalled; otherwise, the Not Before and Not After dates might be displayed incorrectly in thecommand output.

Steps

1. On the DataFabric Manager server, open a console session.


dfm ssl service detail -f -o outputfile

-f overwrites the file without prompting.

-o saves the information to a file.

Disabling certificate-based authenticationThe DataFabric Manager server uses certificate-based authentication by default to authenticateclients in a cloud infrastructure network. You can disable this feature so that clients cannot use a rootcertificate to connect to the DataFabric Manager server. You might want to disable certificate-basedauthentication when a certificate is expiring or you are replacing a certificate.

Steps

1. On the DataFabric Manager server console, open the command-line interface.


dfm option set serverCertAuthEnabled=No


Managing certificates for host services clientsYou can manage certificates for host services clients on your DataFabric Manager server, includingregistering certificates, authorizing certificates, unregistering certificates, and displaying certificateinformation for a specific host service.

Authorizing a host service certificateWhen you register a new host service with DataFabric Manager server, you must manually authorizethe authentication certificate so that requests from the host service to DataFabric Manager server aresuccessful.

Steps

1. Enter the following command from a DataFabric Manager server console session:

dfm hs list

The host requesting authorization is listed with the status "Authorization Pending".

2. Record the ID number of the host requiring authorization.

The host ID is located in the first column of the list output.

3. Using the ID number you recorded in Step 2, enter the following command:

dfm hs authorize ID number

You are asked whether you authorize the host service to use this DataFabric Manager server.

4. Enter y to authorize the host service certificate.

Migrating certificates, keys, and truststores manuallyDuring DataFabric Manager server database backups, the directories containing certificates, keys,and truststores for both cloud service clients and host service clients are not backed up. If you want torestore database backups to a different DataFabric Manager server, you must manually migrate thecertificates, keys, and truststore directories or the restore fails.

About this task

This procedure is not required when you back up and restore the database to the same DataFabricManager server.

Steps

1. On the DataFabric Manager server you want to migrate, back up the database.

Certificate-based authentication | 75

2. On the DataFabric Manager server you just backed up, copy the following three folders from the\DataFabric Manager install directory\conf\keys\ directory:

• certs

• private_keys

• truststore

3. Restore the database to the new DataFabric Manager server.

4. Copy the three folders from the original DataFabric Manager server to the same directory on thedestination DataFabric Manager server.

5. Perform one of the following actions, depending on which type of clients you are migrating:

• If you migrate clients in a cloud infrastructure, after the migration, generate a new DataFabricManager server certificate on the destination DataFabric Manager server by entering dfm sslservice setup, and then load the new certificate by entering dfm ssl service reload

Note: If you do not generate a new certificate, the new DataFabric Manager server will loadthe certificate that was migrated from the original DataFabric Manager server causingDataFabric Manager server hostname validation to fail on cloud service clients.

• If you are migrating host service clients, after the migration, unregister the host service andthen register the new host service from the Host Services tab in the OnCommand console.

Related tasks

Verifying that a host service is registered with the DataFabric Manager server (7-Modeenvironments only) on page 60

You must properly register a host service with a DataFabric Manager server before the servercan discover objects and before you can perform a backup in a virtual environment.


Enabling secure communication between theDataFabric Manager server and Data ONTAP

You should configure the storage system running Data ONTAP and the DataFabric Manager serverto enable secure communication.

Before you begin

• You must have enabled secure communication on the storage system running Data ONTAP byusing OnCommand System Manager or the Data ONTAP command-line interface.

• You must have enabled SNMPv3 on the storage system running Data ONTAP and on theDataFabric Manager server.For more information about enabling SNMP, see the Data ONTAP Network Management Guideand the OnCommand Unified Manager Operations Manager Administration Guide.

Steps

1. Initialize the DataFabric Manager server private key and generate a self-signed certificate byrunning the following command and following the prompt:

dfm ssl server setup -f

2. Restart the HTTP service by running the following commands:

dfm service stop http

dfm service start http

3. Enable HTTPS by running the following command:

dfm option set httpsEnabled=Yes

4. Request for a signed certificate from a well-known CA by running the following command:

dfm ssl server req -f -o server.csr

The server.csr file should be signed by a CA.

5. Import the signed certificate to the DataFabric Manager server by running the followingcommand:

dfm ssl server import server.crt

6. Restart the HTTP service by running the following commands:



7. Enter the certificate information for a CA setup by running the following command and followingthe prompt:

77

dfm ssl self setup -f

The CA is ready to sign requests.

8. If the DataFabric Manager server is running a private CA, perform the following steps:

a) Run the following command to allow certificate signing requests:

dfm ssl self sign -f -o server.crt server.csr

b) Import the signed certificate to the DataFabric Manager server by running the followingcommand:

dfm ssl server import server.crt

9. Change the communication options by running the following commands:


dfm option set httpsEnabled=yes

dfm option set httpEnabled=no

dfm option set httpsPort=8443

dfm option set hostLoginProtocol=ssh

dfm option set hostAdminTransport=https

dfm option set perfAdvisorTransport=httpsOk


10. Verify that secure communication is enabled with the host by running the command:

dfm host diag hostID_or_hostIP

You should be able to connect to the OnCommand console by using the following URL: https://DataFabric_Manager_server_IP_or_hostname:httpsPort/

Related information

'IBM N series support website: www.ibm.com/storage/support/nseries



Upgrading to OnCommand Unified Manager Coreand Host Packages

You can upgrade to OnCommand Unified Manager Core or Host Packages to use the monitoringtools and dashboards of the OnCommand console.

If you are upgrading on a Windows 64-bit server, from DataFabric Manager server 4.x toOnCommand Unified Manager Core Package 5.0 or later, you must back up the DataFabric Managerserver 4.x database before the upgrade. When you restore the database after the upgrade, theinstallation directory C:\Program Files\IBM\DataFabric Manager\DFM\ is chosen based onthe 64-bit Core Package.

Note: If you do not back up before upgrading, the installer chooses the Program Files (x86)directory, which is the location for 32-bit applications.

Related references

License requirements for data protection on page 26

Changes that affect upgrade to OnCommand UnifiedManager Core Package

While planning your upgrade to OnCommand Unified Manager Core Package 5.2, you must considerthe changes in the product that affect the upgrade, such as changes to the database. Also,OnCommand Unified Manager Core Package 5.1 or later requires two separate DataFabric Managerservers to monitor and manage 7-Mode and cluster objects.

Upgrade changes in OnCommand Unified Manager Core Package 5.2

Upgrade to OnCommand Unified Manager Core Package 5.2 might take a long time to completebecause the following processes are included during the upgrade:

• Validating the DataFabric Manager server database• Removing the storage objects that are marked-deleted in the database and the associated entries in

the history tablesSome storage objects might be manually or automatically deleted from a controller monitored bythe DataFabric Manager server. Such objects are marked-deleted on the DataFabric Managerserver database, but are not removed from the database.

• Removing events older than 180 days from the day of installation, or as specified in theeventsPurgeInterval option

Attention: If the database validation fails, the upgrade fails. You must contact technical support ifthe upgrade fails.

79

You can run the DFM Deleted Object Purge Tool before upgrading to determine an approximate timerequired for the upgrade. This tool can determine the additional upgrade time required due to thecleaning of marked deleted objects. You must install the tool by downloading it from the N seriessupport website (accessed and navigated as described in Websites on page 10).

Note: You should check the monitor.db file size and allocate approximately 15 minutes for eachgigabyte of data.

Upgrade from OnCommand Unified Manager Core Package 5.1 to OnCommandUnified Manager Core Package 5.2

Upgrade from OnCommand Unified Manager Core Package 5.1 to OnCommand Unified ManagerCore Package 5.2 takes a long time to complete because of the following change in the upgradeprocess:

• Cleaning and validation of the DataFabric Manager server database in Core Package 5.2

Upgrading from DataFabric Manager 3.x to OnCommand Unified Manager CorePackage 5.2

Upgrade from DataFabric Manager 3.x to OnCommand Unified Manager Core Package 5.2 takestime to complete due to the following changes in the product:

• Cleaning and validation of the DataFabric Manager server database in Core Package 5.2• Deleting of unwanted storage objects in Core Package 5.1, if you are monitoring and managing

controllers running Data ONTAP 7-Mode and clustered Data ONTAPIn OnCommand Unified Manager Core Package 5.1 or later, you must have two separateDataFabric Manager servers to monitor and manage controllers running Data ONTAP operatingin 7-Mode and clustered Data ONTAP. An upgrade to the clustered environment deletes all the 7-Mode controllers. Similarly, an upgrade to the 7-Mode environment deletes all the clustercontrollers.

Note: This is applicable during an upgrade or restore to Core Package 5.1.

• Changes in the Performance Advisor file format in DataFabric Manager server 4.0This is applicable if you use Performance Advisor. The delay in upgrade occurs because thePerformance Advisor data is read and rewritten in the new file format.

Related concepts

Upgrade issues with DataFabric Manager 3.8 or earlier on page 88

Related information




Upgrading OnCommand Unified Manager Core Package onWindows

You can upgrade to the Express edition in Data ONTAP operating in 7-Mode environments or to theStandard edition by installing OnCommand Unified Manager Core Package.

Before you begin


• If you are upgrading from the Express edition of OnCommand Unified Manager Core Package toclustered Data ONTAP, you must have first upgraded to OnCommand Unified Manager CorePackage 5.0 and installed the Standard edition.The Express edition is not supported in clustered environments.


• Credentials for network access• The IP address of the server on which you are installing the software• Directory path where you want to install, if different from the default location

If you are upgrading to OnCommand Unified Manager Core Package while also migrating toa new system, you should use the original DataFabric Manager server installation path toavoid errors caused by changes to the path setting option for DataFabric Manager serverdatabases.For example, if the original installation path is C:\Program Files (x86)\IBM\DataFabric Manager, you should use that path and not the new default path C:\ProgramFiles\IBM\DataFabric Manager.

About this task

The installation software automatically detects and stops any DataFabric Manager server servicesthat are running on the system.

You should perform a backup of the database. If you do not perform a backup, your data is notarchived.

Steps


2. Review and accept the license and AutoSupport agreements.

You cannot install the Core Package unless you accept the license agreement.

3. Select the Data ONTAP environment: 7-Mode or Cluster-Mode.

Upgrading to OnCommand Unified Manager Core and Host Packages | 81

Note: If you are upgrading using the Express edition, this prompt is not displayed.

4. When prompted, confirm if you want to back up the database.

Backing up the database can take several minutes to many hours, depending on the size of yourdatabase.

5. Review the summary screen and consider whether you want to make changes before completingthe installation, and then click Install.

6. When the Installation Complete screen is displayed, click Next to continue.

7. Click Finish to close the wizard.

After you finish

• When you finish installing the Core Package, you can install the Host Package and use theconfiguration wizard to configure a host service.

• You should clear the browser cache before you first start the OnCommand console and when youupgrade to a new version of the software.

Related tasks

Downloading OnCommand Unified Manager Core Package on page 37Installing OnCommand Unified Manager Core Package on Windows on page 38Determining whether a storage system belongs to a workgroup or a domain on page 70

Upgrading OnCommand Unified Manager Core Package onLinux

You can upgrade to the Express edition in Data ONTAP operating in 7-Mode environments or to theStandard edition by installing OnCommand Unified Manager Core Package.

Before you begin

• If you have a large database, you must have backed up the database before starting the setupwizard.

• You must have root user privileges for the Linux system on which you are installingOnCommand Unified Manager Core Package.

• If you are upgrading from the Express edition of OnCommand Unified Manager to clustered DataONTAP, you must have upgraded to OnCommand Unified Manager Core Package 5.0 andinstalled the Standard edition.The Express edition is not supported in clustered environments.


• Credentials for network access


• The IP address of the server on which you are installing the software• Directory path where you want to install, if different from the default location

About this task

The installation software automatically detects and stops any DataFabric Manager server servicesthat are running on the system.

You should perform a backup of the database. If you do not perform a backup, your data is notarchived.

Steps


2. Follow the prompts and select the Data ONTAP environment: 7-Mode or Cluster-Mode.

Note: If you are upgrading the Express edition, this prompt is not displayed.

3. Continue responding to the prompts.

When the URL for opening the OnCommand console is displayed, the upgrade is complete.

4. Copy and paste the URL to a browser to open the OnCommand console.

Related tasks

Downloading OnCommand Unified Manager Core Package on page 37Installing OnCommand Unified Manager Core Package on Linux on page 40

Upgrading from Core Package 32-bit to Core Package 64-bitOnCommand Unified Manager Core Package 5.2 does not support installation on a 32-bit server.Before you upgrade to Core Package 5.2 in your Windows or Linux server, you must back up andrestore your 32-bit DataFabric Manager server database.

Before you begin

• The installation directory must have twice the space of the backup data.The restore operation creates a temporary copy of the backup data and therefore the installationdirectory should have enough space.

• The new DataFabric Manager server must be on the same subnet as the old DataFabric Managerserver.

Steps

1. Create a backup of the 32-bit DataFabric Manager server database by running the followingcommand:


dfm backup create backup_filename

2. Install the OnCommand Unified Manager Core Package 5.2 on your 64-bit server.

3. Copy the 32-bit database backup to the 64-bit server.

4. Restore the 32-bit database backup on the 64-bit server by running the following command:dfm backup restore backup_filename

5. Run the following command to the view the old paths for the setup options:dfm options list setup_option_name

You should check the path for the following setup options: databaseBackupDir,dataExportDir, dfmencKeysDir, perfArchiveDir, perfExportDir, pluginsDir,reportDesignPath, reportsArchiveDir, and scriptDir.

Example

• Run the following command:dfm options list dataExportDir

Result: The command displays the path in which the dataExportDir data is located:installation_directory/data/ in Windows and /opt/IBMdfm/data/ in Linux.

6. Copy the data for each option to the new 64-bit install directory.

Example

Copy the data from the installation_directory/data/ location to the new installationdirectory in Windows.

Alternatively, copy the data from the /opt/IBMdfm/data/ location to the new installationdirectory in Linux.

7. Restart the DataFabric Manager server services by running the command:dfm service stop

dfm service start

Related tasks


Upgrading Core Package to manage 7-Mode and clusteredData ONTAP environments

You can install two separate instances of OnCommand Unified Manager Core Package and migratedata from earlier versions of DataFabric Manager server to enable management of both 7-Mode and


clustered Data ONTAP environments. OnCommand Unified Manager does not support managementof both 7-Mode and clustered environments from the same server.

Before you begin

You must have two DataFabric Manager server license keys, one for each server instance.

You must back up your existing database before you upgrade.

Steps

1. Download and install OnCommand Unified Manager Core Package.

2. When you are prompted, choose 7-Mode as your environment, and complete the installation.

3. On a second server, perform a new installation of OnCommand Unified Manager Core Package,choosing the clustered environment.

4. On the second server, restore the database that you backed up before the upgrade.

A warning message is displayed that all 7-Mode data will be deleted.

5. Disable the license key on the second server by entering the following command at the CLI:dfm license disable all

After the restore, the two DataFabric Manager server installations share the same license key;therefore, you must disable one license to avoid conflicts.

6. Add a new license key to the second server by entering the following command:dfm license install NewLicenseKey

7. Verify that the new license key is installed by entering the following command:dfm license list

The second server installation is complete.

Related tasks

Downloading OnCommand Unified Manager Core Package on page 37Installing OnCommand Unified Manager Core Package on Windows on page 38Installing OnCommand Unified Manager Core Package on Linux on page 40

Prerequisites for upgrading the Host PackageYou must ensure that you meet all the requirements before you begin upgrading the Host Package.

• You must be a member of the local administrators group on the system on which the HostPackage is installed.

• The system that you use for your Host Package installation must belong to a domain rather than aworkgroup.


• You must be a member of the local administrators group or a domain user on the vCenter server.• You must have administrator privileges for the Windows computer on which you are installing

the Host Package.• The DNS name of the Windows computer on which you are installing the Host Package must

match the actual computer name, and the computer name must not be more than 15 characters.• The smvi.override file from the previous installation directory must be backed up if you are

upgrading from Virtual Storage Console 2.0 to OnCommand Unified Manager Core Package.• The Windows firewall must be set to allow exceptions.• The Server Manager administrative tool on Windows 2008 or Windows 2008 R2 systems must be

stopped.• You must have installed at least PowerShell 1.0.

PowerShell 2.0 is recommended.

• On Windows Server 2008 R2, PowerShell is installed by default and you do not have toenable it on the server.

• On Windows Server 2008, PowerShell is not installed by default and you must enable it onthe server after it is installed.To enable PowerShell, you must follow the instructions in the pop-up dialog box that appearsduring upgrade.

• Any service or process that is using the same Java Runtime Environment (JRE) that is installedwith the Host Package must be stopped.

• You must have the following items available:

• A Windows system account user name and password• A Host Package installation location, if not the default• The IP address, user name, and password of the DataFabric Manager server• The IP address, user name, and password of the vCenter Server

• Each vCenter server instance must be a dedicated Windows server.If other applications are installed on the same server, they can consume valuable system resourcesand might drastically reduce performance.

Upgrading to OnCommand Unified Manager Host PackageYou can upgrade to OnCommand Unified Manager Host Package from a previous version ofSnapManager for Virtual Infrastructure to enable the DataFabric Manager server to use a host serviceto discover and monitor virtual objects such as virtual machines or datastores for the Backup andRecovery capability.

About this task

If you are installing the Host and Core Packages on the same system, a fully qualified domain namemust be used for the Core Package, instead of localhost.


The installer creates a locks directory, which is used to coordinate access to resources in the vSphereClient. The locks directory is located within the OnCommand Unified Manager directory. You mustnot change the name or the location of this directory.

The IP address and host name for the system on which you are installing the Host Package must havea DNS registration that resolves properly between the host service and the DataFabric Managerserver.

Note: If the installer fails during the installation of the Host Package, it might not revert the systemto its original state. You must manually remove the Host Package using the Control Panelapplication for your operating system and then delete the folder where the Host Package wasinstalled.

Steps

1. Start the Host Package installation wizard by running the setup file.

2. Click Next to accept the default installation location, or click Change to enter a differentlocation.

3. On the Service Credentials page, type the user name and password for the system on which youare installing the Host Package.

You must type the user name in the following format:domain name\user name

4. On the Configure Communication Ports page, type the port numbers that you want to use oraccept the default port numbers.

If you use custom firewalls, ensure that the Core and Host Packages use the same port numbers.

5. On the Configure DataFabric Manager server page, type the IP address and the user name andpassword used to access DataFabric Manager server.

If you want to monitor your virtual environment or use the Backup and Recovery capability, youmust type the credentials for the DataFabric Manager server. You can skip the validation of theDataFabric Manager server if you do not have the server credentials available.

6. On the Plug-in Service and vCenter Server Information page, provide the followinginformation:

a) Type the admin IP address of the system on which you are installing the Host Package.b) Type the host name or IP address of the system on which the vCenter Server is installed and

the user name and password that enables the vSphere Client to communicate with the vCenterServer.

7. Click Install on the summary page, and then click Finish.

After you finish

• During the installation process, the installer creates some temporary folders that are automaticallydeleted when you next reboot the system.


If you want to delete these folders, you can do so without adversely affecting the installation ofthe Host Package.

• The host service must be configured to perform backups.

Related tasks

Downloading the OnCommand Unified Manager Host Package on page 48Installing OnCommand Unified Manager Host Package on page 49Determining whether a storage system belongs to a workgroup or a domain on page 70Setting the port number manually on page 88

Related references


Setting the port number manuallyIf you have changed the port number of the host service during the upgrade of the Host Package, thehost service status displayed as Down, because it stops communicating with the DataFabric Managerserver. You must manually set the port numbers to restart the host services.

Steps

1. Set the new administration port by running the following command:

dfm hs set hsAdminPort=new-admin-port

2. Set the management port by running the following command:

dfm hs set hsMgmtPort=new-mgmt-port

3. Verify that the communication between the DataFabric Manager server and the host service isestablished by running the following command:

dfm hs diag

Upgrade issues with DataFabric Manager 3.8 or earlierYou can upgrade to OnCommand management software from previous versions of the DataFabricManager server. However, due to changes in system behavior between releases, you might have toresolve issues before upgrading.

The following issues are associated with upgrading to OnCommand Unified Manager Core Package5.1 from DataFabric Manager 3.8 and earlier. Issues associated with upgrading from DataFabricManager server 4.0 or later to OnCommand Unified Manager Core Package are covered in therequirements and installation instructions throughout this guide and in the OnCommand UnifiedManager Core Package Release Notes.


Supported methods to upgrade from Solaris to Windows or Linux

DataFabric Manager 3.8 and later does not support Solaris. Therefore, you must migrate theDataFabric Manager server database on Solaris to a server running Windows or Linux before youupgrade to DataFabric Manager 3.8 or later.

You can migrate the database by creating an archive copy of the backup by using the dfm backupcreate <backup_filename> command, then restore the database by using the dfm backuprestore <backup_filename> command.

Upgrade path from DataFabric Manager 3.5 to OnCommand Unified Manager CorePackage 5.x

You can upgrade to OnCommand Unified Manager Core Package 5.x from DataFabric Managerserver 4.0 or later. If you want to upgrade from DataFabric Manager server 3.5 to OnCommandUnified Manager Core Package 5.x, you must first upgrade to DataFabric Manager server 4.0.

Upgrading from DataFabric Manager 3.7.1

If you have created custom reports with GUILink and SecureGUILink as fields in DataFabricManager 3.7.1 or earlier, upgrading to DataFabric Manager 3.8 or later causes the dfm reportview command to fail. You must open the custom report in Operations Manager console and savethe report to view it.

Upgrading from DataFabric Manager 3.7 on Linux

If you are upgrading from DataFabric Manager 3.7 to DataFabric Manager 3.8 or later on Linux, theupgrade might fail with the following notification:

rpm: /opt/IBMdfm/lib/libgcc_s.so.1: version `GCC_4.2.0' not found (required

by /usr/lib/libstdc++.so.6)

You can resolve this issue by deleting the entry /opt/IBMdfm/lib from the environment variableLD_LIBRARY_PATH.

Upgrading from DataFabric Manager 3.7 or earlierIf you are upgrading from DataFabric Manager 3.7 or earlier to DataFabric Manager 3.8 or later, youmust delete the existing Data Source Name (DSN) entry for the Adaptive Server Anywhere 9.0driver and create a new DSN entry for SQL Anywhere 10.

Upgrading from DataFabric Manager 3.5 or earlierIf you are upgrading from DataFabric Manager 3.5 or earlier to DataFabric Manager 3.6 or later, ittakes a long time to upgrade the performance data files (data of 20 GB or more). The length of timedepends on the platform used. The space used by the performance data files increases by about 65%during the upgrade.


Upgrading from DataFabric Manager 3.2 or earlier

Because of database schema changes, you might experience a delay of several minutes to a few hourswhen upgrading from DataFabric Manager 3.2 or earlier.

The time required to perform the upgrade depends on the size of the database, the amount of historyin the database, the CPU speed, and the I/O throughput of the system. The following processes mightrequire a lot of time:

• Merging rotating history tables• Populating history tables• Populating volume history tables• Populating aggregate history tables• Reloading the database into the latest file format (at the end of upgrade)

Upgrading from DataFabric Manager 2.1 or earlier, on WindowsBecause of a database upgrade that is no longer supported on a Windows platform, you must firstupgrade to DataFabric Manager 2.2 or later (up to DataFabric Manager 3.2) before you upgrade toDataFabric Manager 4.0.

Windows installation path when upgrading to DataFabric Manager 3.6 or later

Following are the default installation paths for various software versions:

• DataFabric Manager 3.8 through 4.0.1 on Windows32-bit platform: C:\Program Files\IBM\DataFabric Manager64-bit platform: C:\Program Files (x86)\IBM\DataFabric Manager

• DataFabric Manager 3.6 or later (up to 3.7.1):C:\Program Files\IBM\DataFabric

• Versions earlier than DataFabric Manager 3.6:C:\Program Files\IBM\DataFabric

Installing OnCommand Unified Manager Core Package in a custom Linux directory

If you used the -d <new directory> command to install DataFabric Manager 3.2 or earlier in acustom directory, the software was installed in an IBMdfm directory that was automatically createdwithin the new directory you specified.

If you use the -d <new directory> command to install DataFabric Manager 3.3 or later in acustom directory, the software is installed in the new directory you specify; no additional IBMdfmdirectory is created.

Viewing dynamic dataTo use Disaster Recovery, the browser that you use to view Operations Manager console mustsupport Java applets.


Conversion of group names from DataFabric Manager 3.1 or earlier

The naming convention for hierarchical groups uses the forward slash character (/) as a separatorbetween levels in the hierarchy. If you upgrade from DataFabric Manager 3.1 or earlier, any groupthat uses the forward slash character in its name is renamed so that the group is not mistaken for asubgroup in a hierarchy.

Each forward slash character is replaced by a hyphen character (-). If the new name is already in useby another group, OnCommand Unified Manager adds an increasing numeric suffix to the name untilan unused name is derived. For example, OnCommand Unified Manager would try to rename groupapple/orange to appleorange, then to apple-orange1, then to apple-orange2, and so on, until anunused group name is found.

Upgrade considerations for configuration groupsAfter upgrading from DataFabric Manager 3.1 or earlier, some administrators of configurationresource groups might gain additional privileges through inheritance. Before upgrading, review theprivileges for group hierarchies that include configuration resource groups and make adjustments asnecessary.


Uninstalling the OnCommand Unified ManagerCore and Host Packages

If you are no longer using the package or need additional space, it might be necessary to uninstall andremove packages. When you uninstall the OnCommand Unified Manager Core or Host Package fromyour system, the installer automatically removes all components.

Uninstalling the OnCommand Unified Manager CorePackage from Windows

You can uninstall the OnCommand Unified Manager Core Package, for instance, when a CorePackage installation is unsuccessful, or when you want to reconfigure your system with a freshinstallation. You uninstall the Core Package using the Control Panel application for your operatingsystem.

Before you begin

You must have ensured that there are no other dependencies on the Core Package, because the wizarduninstalls all associated components.

Steps

1. On the Windows server where you installed the Core Package, navigate to the Windows ControlPanel and Control Panel > Programs and Features.


2. Scroll through the list of installed programs to find the program that you want to remove.

3. Click the program that you want to uninstall, and then click Uninstall/Change or Change/Remove, depending on your operating system.

The IBM N series install wizard opens.

4. Select Remove, and then click Next.

5. Click Uninstall.

6. If requested, reboot the system.

A system reboot is required when, during the uninstall process, the \DataFabric Manager\DFM program directory is not moved to a new directory. The new directory is created with aname that indicates the date and time that you performed the uninstall process: for example,\DataFabricManager\DFM-20110622140520\, which specifies that the OnCommandUnified Manager Core Package was uninstalled on June 22, 2011, at 2:05:20 PM. When this


uninstall directory is not created, you must reboot to complete the uninstall process and newlyinstall the OnCommand Unified Manager Core Package.

Related tasks

Installing OnCommand Unified Manager Core Package on Windows on page 38

Uninstalling the OnCommand Unified Manager CorePackage from Linux

You can use the command rpm -e to uninstall the OnCommand Unified Manager Core Package fromLinux, for instance, when a Core Package installation is unsuccessful, or when you want toreconfigure your system with a fresh installation.

Before you begin

You must have ensured that there are no other dependencies on the Core Package, because the wizarduninstalls all associated components.

Step

1. At the command prompt, type the command to uninstall the OnCommand Unified Manager CorePackage: for example, rpm -e IBMdfm.

The software automatically uninstalls.

Related tasks

Installing OnCommand Unified Manager Core Package on Linux on page 40

Uninstalling the OnCommand Unified Manager HostPackage

You can uninstall the OnCommand Unified Manager Host Package from your system using theControl Panel application for your operating system. When you uninstall the Host Package, the hostservice does not unregister from the DataFabric Manager server.

Before you begin

• You must save any files that contain data such as local backups, scheduled jobs, or datasets.You can find these files in the installation folder. The uninstall process removes all Host Packagefiles.

• You must stop any service or process that is using the same Java Runtime Environment (JRE)that is installed with the Host Package.

Uninstalling the OnCommand Unified Manager Core and Host Packages | 93

Steps

1. On the Windows server where you installed the Host Package, navigate to the Windows ControlPanel and select Control Panel > Programs and Features.


2. Scroll through the list of installed programs to find the program that you want to remove.

3. Click once on the program you want to uninstall and then click Uninstall/Change or Change/Remove, depending on your operating system.

You can also double-click the program name and Windows will uninstall OnCommand UnifiedManager Host Package by default.

This will open a prompt asking you to confirm you want to uninstall OnCommand UnifiedManager Host Package.

4. Click Yes to continue uninstalling OnCommand Unified Manager Host Package.

Result

OnCommand Unified Manager Host Package will uninstall without any additional prompts.

After you finish

• When you finish uninstalling the Host Package, you might need to manually close the port usedfor OnCommand Unified Manager Host Service Management.

• You must disable all the ports opened by the installer for all profiles as appropriate for youroperating system.

Related tasks

Installing OnCommand Unified Manager Host Package on page 49Upgrading to OnCommand Unified Manager Host Package on page 86

Related references



Troubleshooting OnCommand Unified Managerinstallation and setup

If you encounter unexpected behavior during the installation or when using OnCommand UnifiedManager, you can use specific troubleshooting procedures to identify and resolve the cause of suchissues.

Address already in useDescription This message occurs when the Windows computer has run out of outbound ports.

A Transmission Control Protocol (TCP) connection has closed, causing the socketpair associated with the connection to go into a TIME-WAIT state. This preventsother connections from using the TCP protocol, source Internet Protocol (IP)address, destination IP address, source port, and destination port for an unknownperiod of time.

Correctiveaction

Reduce the length of the TCP TIME-WAIT delay.See the Microsoft MSDN library for more information.

There is a problem with this Windows Installer packageDescription This message occurs when you uninstall an application by using the Add or

Remove Programs tool in Windows server. The Windows Installer servicemanages the installation and removal of programs. If there is a problem with theregistration of the Microsoft installation engine, you might not be able to removeprograms that you have installed by using the Windows installer.

Correctiveaction

Unregister and reregister the Windows Installer service. See KB891985 on the Microsoft support site for more information.

Cursor displays in multiple locations in the same dashboardpanel

Cause This problem occurs when you use the Firefox browser to open the OnCommandconsole.

Correctiveaction

Disable a browser setting in Firefox, as follows:

95



1. Open the Firefox browser and click the Tools menu, then click Options.

2. Click the Advanced tab.

3. Clear the Always use the cursor keys to navigate within pages option.

4. Restart the Firefox browser.

Plug-in container for Firefox has stopped workingCause While installing DataFabric Manager server Express edition, the configuration

wizard might crash.

Corrective action Update the Adobe Flash Player plug-in.

See the Mozilla Firefox Help for more information.

Related information

Firefox Help

No related objects are displayed for a virtual objectIssue No physical servers corresponding to a virtual object are displayed in the Related

Objects list in the Server tab of the OnCommand console.

Cause This problem occurs when you add or register a new host service but the mappingbetween the physical servers and virtual objects does not occur.

Correctiveaction

1. Refresh the monitor by opening a console session and type the followingcommand:

dfm host discover -m share <storage system>

2. To view the results, type the following command:

dfm details <storage system>

3. Search for the shareTimestamp value to ensure that discovery for the storagesystem is complete.

4. Click Rediscover in the Host Services tab of the OnCommand console torediscover the host service.

5. Verify that the physical servers are displayed in the Related Objects list in theServer tab.


http://support.mozilla.com/en-US/kb/The%20Adobe%20Flash%20plugin%20has%20crashed

Could not find any storage mapping for virtual objectDescription This message occurs in the following circumstances:

• When you create a new dataset in the OnCommand console that contains adatastore or a virtual machine from an NFS-based qtree

Correctiveaction

1. Refresh the monitor by opening a console session and type the followingcommand:

dfm host discover -m share <storage system>

2. To view the results, type the following command:

dfm details <storage system>

If you created a dataset from an NFS-based qtree, then you must set the exportpermission for the qtree in the storage system.

3. Search for the shareTimestamp value to ensure that discovery for the storagesystem is complete.

4. Click Rediscover in the Host Services tab of the OnCommand console torediscover the host service.

5. Verify that the physical servers are displayed in the Related Objects list in theServer tab.

Storage mapping fails for virtual machine and datastorecreated on VMFS datastore using FC LUN

Issue Host service does not display any storage mapping in the OnCommand consolefor virtual machine and datastore created on VMFS datastore using FC LUN.

Cause This problem occurs when you do not correctly unmap an FC LUN from the ESXhost and there are non-accessible LUNs in the datastore that you created, theSCSI target might not get updated in the vCenter Server inventory.

Correctiveaction

Remove the non-accessible LUN and rescan the storage adapter.

Troubleshooting OnCommand Unified Manager installation and setup | 97

Operation timed outDescription This message occurs when an ESX or vCenter Server is busy creating snapshots

or running local backups. In this instance, a copy operation for a restore mighttimeout from the vCenter server and the restore operation fails.

Correctiveaction

You can retry the restore operation when the ESX or vCenter Server is not asbusy or you can use a different ESX or vCenter Server that is also connected tothe same datastores.

Primary key for table is not uniqueDescription This message occurs if you move the virtual machine when adding the entire

virtual machine folder to the vCenter Server inventory. This causes the newvirtual machine to have the same universal unique identifier (UUID) as the virtualmachine from which the virtual machine folder was copied, and a UUID conflictoccurs causing the host service discovery to fail.

Correctiveaction

Delete the folder that was moved and then copy the virtual machine folder to thevCenter Server inventory.

Access is deniedDescription This message occurs when you successfully install the Host Package, then attempt

to modify the installation by setting new user credentials using the Add orRemove Programs tool in Windows server. This message might appear if the UserAccount Control (UAC) feature is enabled in Windows Server 2008 or WindowsServer 2008 R2.

Correctiveaction

Set the UAC security level to low or you can change the Host Package settings byrestarting the Host Package installer.

Error 1067 while starting the DFM WebUI serviceDescription This message occurs during the installation of the Core Package, when the server

has Java installation (older, newer, or same version) that sets Java-specificenvironment variables. This results in the DFM WebUI service failing to startwhen the installation is complete.


Correctiveaction

You can uninstall the tool or application that sets the Java-specific environmentvariables or you can delete these variables when the DFM WebUI service fails tostart after you install the Core Package. You can start the service manually bytyping the dfm service start webui/http command.

Verifying host service to DataFabric Manager servercommunication

Issue You can use the dfm hs diag command to verify that communication is enabledbetween the host service and the DataFabric Manager server, and to verify that thehost service can communicate with the VMware plug-in. You can use thiscommand to troubleshoot connectivity issues or to verify that communication isenabled before starting a host service backup.

Correctiveaction

1. On the DataFabric Manager server console, type the following command:

dfm hs diag <host service>

Administrators usergroup does not exist on <vFiler name>Description This message occurs when you have a vFiler and you did not run the RBAC

monitor for that vFiler, causing the vFiler configuration job for adding the vFilercredentials to the host service to fail.

Correctiveaction

1. Run the RBAC monitor for the vFiler using the command dfm hostdiscover -m rbac <Vfiler Name>.

2. Run the configuration job for the vFiler.

Host service fails to connect to DataFabric Manager serverafter a restart

Cause If there not enough space on the disk, the Windows Event Log automaticallystops the plug-in services.

Correctiveaction

You must ensure there is enough space on the system drive and then restart theservices that were stopped. The plug-in service has to be restarted before startingthe host service.

Troubleshooting OnCommand Unified Manager installation and setup | 99

Host service is unresponsive after successful installation ofOnCommand Unified Manager Host Package

Issue After you successfully install the Host Package, the host service does not display inthe Host Services tab of the OnCommand console. You cannot configure a hostservice and no virtual objects are discovered.

Cause This problem occurs because of a limitation in XML, when the host name containstwo hyphens in a row, causing the host service to become unresponsive.Additionally, another unusual sequence of characters might also cause this problem.

Correctiveaction

1. Stop the oncommandhostsvc service.

2. You must modify the hs_plugins.xml file, which is located in the installationdirectory.The location of this file is at C:\Program Files\IBM\OnCommand HostPackage\Host Service if you installed the Host Package in the defaultdirectory at C:\Program Files\IBM\OnCommand Host Package.

3. You must remove the text from the commented out section that begins with<PlugInEndpointInfo> and ends with </PlugInEndpointInfo>.

4. Restart the oncommandhostsvc service.


Installing and configuring the Core Package in anMSCS environment

Microsoft Cluster Server (MSCS) provides high-availability (HA) protection for your Windowsenvironment.

As part of the OnCommand Unified Manager Core Package installation process, the DataFabricManager server and its associated services are installed on your system. The cluster resources,including the services for the DataFabric Manager server, the network name, the network address,and the shared data disks, are always online and available on one of the nodes. You must configurethe network name and address, and the shared data disks, during the OnCommand Unified ManagerCore Package installation process.

When any failure occurs, whether a node failure or a failure of one of the resources, all the resourcesare automatically moved, or failed over, to the partner node by MSCS.

This failover process is assisted by using a quorum resource on the cluster. The quorum resource is aphysical storage device that can be accessed by both nodes in the cluster, although only one node hasaccess to the quorum resource at any given time. The node that has access to the quorum resource isthe node that has control of the cluster resource.

Preparing to install the OnCommand Unified Manager CorePackage in an MSCS environment

To ensure HA of the DataFabric Manager server, you must configure the services to beaccessible through a network name and a network address. The DataFabric Manager server can alsouse this network name or network address; therefore, you do not have to add new network resourcesfor the services.

An MSCS cluster that is configured with the DataFabric Manager server consists of two nodes, eachnode running the same version of the DataFabric Manager server.

All of the DataFabric Manager server data (database files, Performance Advisor files, and so on) isconfigured to be accessed from a shared data disk.

Prerequisites for installing the OnCommand Unified Manager Core Packagein MSCS

Before installing the Core Package in MSCS, you must set up two Windows servers running onidentical hardware platforms. You must ensure that all the requirements and guidelines forconfiguring cluster servers are met, according to the MSCS documentation.

During the MSCS setup, you must ensure that you have completed the following actions:

• Creating a shared data disk to be used as a quorum resource.

101

• Creating a network name resource and a network address resource.• Adding cluster resources to a resource group.

Related information

Introducing Microsoft Cluster Service (MSCS)

Configuration requirements for the OnCommand Unified Manager CorePackage in MSCS

You must meet specific configuration requirements when you set up your MSCS environment to useOnCommand Unified Manager Core Package.

To ensure OnCommand Unified Manager Core Package installs and functions properly in an MSCSenvironment, the following MSCS configuration conditions must exist:

• Microsoft Windows servers running Windows 2008 Enterprise Edition, or Data Center Editionhave the same patch versions on identical hardware.

Note: MSCS is not supported on Windows Server 2008. However, you can configureDataFabric Manager 3.8 or later for HA on these platforms by using FailoverClustering. For more details, see the technical report on High-Availability Support forDataFabric Manager server. This technical report contains information about NetApp productsthat IBM licenses and sometimes customizes. Technical reports might contain informationabout models and features that are not supported by IBM.

• The DataFabric Manager server is connected to the storage system using either iSCSI or FibreChannel (FC), and it is in a SAN environment.

• iSCSI-based storage is used for shared data disks with a IBM N series storage system as thestorage back end.

• Members of the cluster are member servers, and not domain controllers.• All DataFabric Manager server administrators are domain users, rather than local system users, so

that the user login is successful even when the DataFabric Manager server services fail over to thepartner node.

• 64-bit Perl in Windows 64-bit 2008 server is installed, to run DataFabric Manager serverconfiguration scripts.

Related information

Technical report 3767: High-Availability Support for DataFabric Manager server



http://media.netapp.com/documents/tr-3767.pdf

Configuration limitations for the OnCommand Unified Manager CorePackage in MSCS

OnCommand Unified Manager Core Package in MSCS is not supported on certain environmentalconditions of the MSCS environment.

The following are configuration limitations of installing OnCommand Unified Manager CorePackage in an MSCS environment:

• IPv6 virtual IP address on failover clustering is supported on Windows 2008 only.• Quorum type “node and disk majority” in Failover Cluster is supported on Windows 2008 server

only.• OnCommand Unified Manager Core Package in MSCS is not supported on Windows running in a

virtual machine.• DataFabric Manager server does not support a host service created as a generic service from

failover cluster manager in Microsoft Windows.

Installing the OnCommand Unified Manager Core Packagein an MSCS environment

Before installing the OnCommand Unified Manager Core Package, you must configure MSCS with ashared disk for a quorum resource, assign a network name and a network address, place the clusterresources in a cluster resource group.

After the installation is complete, you have to add DataFabric Manager server services to MSCS.You must install OnCommand Unified Manager Core Package on the first node, and repeat on thesecond node.

Configuring MSCS for the OnCommand Unified Manager Core Packageinstallation

Before you install OnCommand Unified Manager Core Package in MSCS, you must configure yourMSCS environment.

About this task

You must complete this task by using Cluster Administrator in the MSCS interface. See the MSCSdocumentation for more details.

You must configure MSCS to create the following:

• A shared quorum disk, which is used for storing the cluster configuration information• A network name and a network address, which are used for managing the cluster server and the

DataFabric Manager server• A resource group to store the resources so that all these resources are available to both the cluster

nodes

Installing and configuring the Core Package in an MSCS environment | 103

Steps

1. Select a domain user and add the domain user to the Administrators Group on both the clusternodes.

Example

Enter the following command in Administrators Group:domain\dfmuser

2. Create a shared data disk:a) Make the disk accessible to both the cluster nodes.b) Map the disk to a drive letter (such as drive S:).

Note: The data disk should be mapped to the same drive letter on both the cluster nodes.c) Add the shared data disk, as a physical disk resource, to the cluster server.

This disk is a resource for storing data specific to OnCommand Unified Manager Core Package.

3. Verify that the new resource group can successfully fail over to the partner node.

Result

Cluster Administrator displays the resources, nodes, and groups. In addition to the content displayedafter the initial setup, Cluster Administrator displays a physical disk resource named Disk S:.

Related information

Introducing Microsoft Cluster Service (MSCS)

Installing the OnCommand Unified Manager Core Package in MSCSYou can install the OnCommand Unified Manager Core Package in MSCS to ensure HAin a Windows environment. You must install the OnCommand Unified Manager Core Package on thefirst node, and repeat the installation procedure on the second node.

Before you begin

The following conditions must be met:

• Microsoft Cluster Server is installed and configured on both the nodes of the cluster.• The preinstallation tasks are completed.• You must have the Core license key.• The workstation meets the hardware requirements.• You have Local Administrator login permission for the DataFabric Manager server.• If you are upgrading from a previous version of the DataFabric Manager server, you should back

up your database before the installation or during the installation process.• The OnCommand Unified Manager Core Package installer from the N series support website

(accessed and navigated as described in Websites on page 10) is downloaded.



About this task

The two DataFabric Manager server nodes are configured to use the same database and to monitorthe same set of nodes. Therefore, you can install the same license on both the nodes.

If you are upgrading from an earlier licensed version of DataFabric Manager server, you do notrequire a license key. Both the installation and upgrade processes automatically install theAutoSupport feature with AutoSupport enabled and display a message about how to disable thefeature.

Steps

1. Log in to the first node of the cluster pair as a domain user, with administrator privileges on thelocal system.

2. Open the Cluster Administrator interface and select Owner of the Resources folder, to ensurethat the node owns the cluster resources.

3. Run the executable file.

4. Follow the setup prompts to complete the installation and note the installation directory path forlater reference.

5. Stop the DataFabric Manager server services after the installation is complete by entering thefollowing command:

dfm service stop

Attention: You should perform all cluster operations by using either Cluster Administrator orcluster.exe. Except where specifically indicated in installation and configurationprocedures, you must not use the dfm service start and dfm service stop commands.These commands interfere with cluster operations.

6. Move the cluster resources to the second node by using the Move Group option in MSCS.

7. Log in to the second node of the cluster pair as a domain user, with administrator privileges onthe local system.

Note: You must log in with the same user name you used on the first node.

8. Install the Core Package on the second node at the same directory path that you used on the firstnode.

9. Stop the DataFabric Manager server services on the second node by entering the followingcommand:

dfm service stop

10. Disable the automatic start-up of the DataFabric Manager server by entering the followingcommand on both the nodes:

dfm service enable -m


After you finish

You can start configuring both the cluster nodes by using the configuration scripts that are providedwith the installation, or you can perform the configuration manually.

Related concepts

OnCommand Unified Manager Core Package hardware and software requirements on page 27

Related tasks

Preparing to install the OnCommand Unified Manager Core Package in an MSCS environment onpage 101

Related information


Example of the MSCS initial setupYou should understand how the cluster, the nodes, the physical disk, the network name, and thenetwork IP address are displayed in the Cluster Administrator interface.The following image is an example of the Cluster Administrator interface after the initial setup ofMSCS:

The configuration displayed in this example is as follows:

• The cluster name is Cluster 1.• The first node name is Kalyani.• The second node name is Toddy.• The physical disk, the shared disk quorum resource, is created with the name Disk Q: and is

mapped to drive letter Q:.



• The network name resource is called Cluster Name.• The network IP Address resource is called Cluster IP Address.

DataFabric Manager server service resources added to MSCSYou must add the DataFabric Manager server cluster service resources to MSCS. The servicesinclude DFM Monitor, DFM Apache, DFM Watchdog, DFM Event, DFM Server, DFM Scheduler,DFM WebUI, and DFM Sybase.

These services are used for various purposes, such as monitoring storage systems, scheduling jobs,serving HTTP requests and executing servlets, processing events and database queries, andmonitoring all the other services.

The following illustration shows the services and the dependencies among the various resources:

Cluster Resource Dependencies

DFM Cluster ResourcesNon-DFM Cluster Resources

DFM Monitor

DFM Apache

DFM Watchdog

DFM Event

DFM Sybase

DFM WebUI

Cluster Name

Cluster IP Disk S:

DFM Server

DFM Scheduler

Configuring the OnCommand Unified Manager CorePackage in an MSCS environment

When you install the OnCommand Unified Manager Core Package, the DataFabric Manager serverservices are installed with it. To achieve HA, you must add the DataFabric Managerserver cluster services to MSCS. You can configure the services either by using scripts or by addingthe services manually.

The following service resources are added to MSCS:

• DFM Monitor


• DFM Apache• DFM Watchdog• DFM Event• DFM Server• DFM Scheduler• DFM WebUI• DFM Sybase

Adding the cluster services using a scriptYou can configure DataFabric Manager server in your cluster environment by running aconfiguration script.

Steps

1. Log in to the node that owns cluster resources.

2. Move the DataFabric Manager server data to the shared data disk by entering the followingcommand:dfm datastore setup new_clusterdisk_directory

3. Stop the DataFabric Manager server services by entering the following command:dfm service stop

This ensures that the DataFabric Manager server does not try to access the data disk to be movedto the secondary node.

4. Ensure that the DataFabric Manager server services do not start automatically by entering thefollowing command:dfm service enable -m

The -moption ensures that the DataFabric Manager server services do not start automatically.

5. Manually move the cluster group to the second node.

6. Verify that the secondary node owns the cluster resources.

7. Enter the following commands on the secondary node:dfm service enable -m

dfm datastore setup -n drive_name

Note: You must ensure that you use the same drive letter for the secondary node as the firstnode. The -n option ensures that the data is not copied again to the shared data disk.

8. Access the directory at C:\Program Files\IBM\DataFabric Manager\DFM\examplesor /opt/IBMdfm/examples.

9. Configure the DataFabric Manager server services in your cluster environment by running thefollowing script:


dfmcluster_add_resources.pl -t cluster_type -g cluster_group -icluster_ip_resource -n cluster_nameresource

Script options for configuring services in MSCSYou can use a configuration script to add the DataFabric Manager server generic service resources toMSCS.The command to add services to the DataFabric Manager server is as follows:perl dfmcluster_add_resources.pl option name ...

The perl dfmcluster_add_resources.pl command includes the following options:

-t cluster_type Cluster solution used for HA. The values are mscs(default) and vcs.

-g cluster_group Name of the cluster group to which the resources are added. Thisgroup already includes the other resources.

-i cluster_ip_resource Name of the cluster IP resource that is displayed under the Namecolumn in the Cluster Administrator.

-n cluster_nameresource Name of the cluster name resource.

-k data_disk_resource Name of the data disk resource.

Example

perl dfmcluster_add_resources.pl -g ClusterGroup1 -i 172.24.1.20 -n

Cluster1 -k Disk S:

Bringing DataFabric Manager server cluster services online in MSCSAfter you add the DataFabric Manager server services to MSCS, you must bring the services online.

Steps

1. In the MSCS interface, select Cluster Group under the Groups folder.

2. Click File, and then click Bring Online.

Configuring DataFabric Manager server to use the cluster name in MSCSWhen DataFabric Manager server sends e-mail alert messages to administrators, the DataFabricManager server uses the local system name in the URL, by default. These local system names are notaccessible to users in the cluster. Therefore, you must configure DataFabric Manager server to usethe cluster name instead.

Step

1. Configure the DataFabric Manager server to use the cluster name by entering the followingcommand:


dfm option set localHostName=fqdn-of-cluster

FQDN is the fully qualified domain name of the cluster.

Configuring DataFabric Manager server in MSCS manuallyYou can manually configure DataFabric Manager server in MSCS, which allows you to customizethe setup of the cluster. For example, you can move different DataFabric Manager server data files todifferent shared data disks. However, you cannot move the data files using the configuration scripts.

Configuring DataFabric Manager server services on the first node in MSCS

You must configure the DataFabric Manager server by manually adding the DataFabric Managerserver services.

Before you begin

You must be logged in as a domain user, with administrative privileges on the local system, to accessthe shared data drive. By default, the DataFabric Manager server services run using the local systemaccount, and therefore do not provide access to the shared drive where the database files and otherfiles reside.

Steps

1. In the Cluster Administrator interface, select the Owner field of the Resources folder.

2. Verify that the first node owns the resource group named Cluster Group.

3. Stop the DataFabric Manager server services by entering the following command:

dfm service stop


4. Specify a user account in the Logon As field:

a) Open the Services page from Windows Control Panel.b) Double-click DFM Sybase ASA.c) In the General tab, change the Startup type option to Manual.d) Click Apply.

5. Click the Log On tab.

6. Enter the name of the domain user account that you want to use to access the DataFabric Managerserver service from the shared drive.

7. Click OK.

8. Repeat Steps 4 through 7 to add the cluster services.


You must add the following services in the Administrative Tools: DFM Monitor, DFM Apache,DFM Watchdog, DFM Event, DFM Server, DFM Scheduler, DFM WebUI

After you finish

You must move the DataFabric Manager server data files to a shared disk.

Moving DataFabric Manager server data files to a shared disk

You must configure the DataFabric Manager server to allow access to data files in a shared disk.

Steps

1. For the first node, move the database files to a nonroot folder in the shared data drive.

The default location for database files is installation_directory\data.

Example

S:\dfm\data

2. Ensure that the DataFabric Manager server points to the relocated database by entering thefollowing command:dfm database set dbDir=S:\dfm\data

3. Verify that all the services are stopped by entering the following command:dfm service list

4. Move the following data files to appropriate folders in the shared disk:

• Performance Advisor data filesThe default location is installation_directory\perfdata (for example, S:\dfm\perfdata).

• Script plug-in filesThe default location is installation_directory\script-plugins (for example, S:\dfm\script-plugins).

• Configuration Management plug-in filesThe default location is installation_directory\plugins (for example, S:\dfm\plugins).

• Archived reportsThe default location is installation_directory\reports (for example, S:\dfm\reports).

5. Start the SQL service by entering the following command:dfm service start sql

6. Set the options to point to the new location of the relocated files by entering the followingcommands:


a) dfm option set perfArchiveDir=S:\dfm\perfdata

b) dfm option set pluginsDir=S:\dfm\plugins

c) dfm option set scriptDir=S:\dfm\script-plugins

d) dfm option set reportsArchiveDir=S:\dfm\reports

Note: The dfm option set command prompts you to start the services after setting eachoption. However, you must start the services only after you complete setting all the options.

7. Stop the SQL service by entering the following command:dfm service stop sql

Configuring DataFabric Manager server services on the second node in MSCS

After the first node is configured to allow access to all data files from a shared disk, you mustconfigure the second node to allow the same access.

Before you begin

You must be logged in as a domain user, with administrative privileges on the local system, to accessthe shared data drive. By default, the DataFabric Manager server services run using the local systemaccount, and therefore do not provide access to the shared drive where the database files and otherfiles reside.

Steps

1. In the Cluster Administrator interface, select the Owner field of the Resources folder.

2. Verify that the first node owns the resource group named Cluster Group.

3. Stop the DataFabric Manager server services by entering the following command:dfm service stop


4. Specify a user account in the Logon As field:

a) Open the Services page from Windows Control Panel.b) Double-click DFM Sybase ASA.c) In the General tab, change the Startup type option to Manual.d) Click Apply.

5. Click the Log On tab.

6. Enter the name of the domain user account that you want to use to access the DataFabric Managerserver service from the shared drive.

7. Click OK.


8. Repeat Steps 3 through 6 to add the cluster services.

You must configure all the services for the cluster to start working. You must enter the followingcluster service names in the Services tab in Administrative Tools:

• DFM Monitor• DFM Apache• DFM Watchdog• DFM Event• DFM Server• DFM Scheduler• DFM WebUI

9. Verify that all the services are stopped by entering the following command:

dfm service list

Configuring DataFabric Manager server services as cluster resources in MSCS

After you install the DataFabric Manager server services, you have to configure them as clusterresources and make them available to both nodes.

Before you begin

• The dependencies that exist between the various cluster resources must be determined.A dependency requires that one service must be running before its associated service can bebrought online. For example, most services cannot function unless Sybase ASA is alreadyrunning.

• You must be logged in to the node as a domain use, with administrator privileges on the localsystem.

About this task

You can use the following table to add the resource name, dependencies, and service name whenconfiguring each new cluster service:

Resource name field Dependencies field Service name field

DFM Sybase ASA Cluster IP, Cluster Name, SharedData Disk, Data Disk

DFMSybase

DFM Apache DFM Sybase ASA, DFM WebUI DFMApache

DFM Scheduler DFM Sybase ASA DFMScheduler

DFM Watchdog DFM Sybase ASA DFMWatchdog

DFM Server DFM Sybase ASA DFMServer

DFM Event DFM Sybase ASA DFMEvent


Resource name field Dependencies field Service name field

DFM Monitor DFM Event DFMMonitor

DFM WebUI DFM Sybase ASA DFMWebUI

Steps

1. In the Cluster Administrator interface, select the Owner field of the Resources folder andverify that the node owns all the cluster resources.

2. In the console tree, double-click the Groups folder.

3. In the Details pane, click the group named Cluster Group.

4. Select File menu, and then select New > Resource.

5. On the New Resource page, complete the following steps:

a) Enter the resource name in the Name field.b) Select Generic Service as the Service Type.c) Select Cluster Group as the group.d) Click Next.

6. On the Possible Owners page, complete the following steps:

a) Add both nodes as the possible owners of the resource.b) Click Next.

7. On the Dependencies page, complete the following steps:

a) Add dependencies related to the new service in the Dependencies field.

Example

Set DFM Sybase ASA Dependencies as the cluster IP address, cluster name, disk S:, anddata disk.

b) Click Next.

8. On the Generic Service Parameters page, complete the following steps:

a) Enter the name of the service in Service Name.

Example

Set the name to DFM Sybase.b) Clear the Use Network name for computer name option.

9. On the Registry Replication page, click Finish.

Note: You do not have to perform registry replication.

10. Repeat Steps 5 through 9 for every DataFabric Manager server service.


Related references

DataFabric Manager server service resources added to MSCS on page 107

Bringing DataFabric Manager server cluster services online in MSCS

After you add the DataFabric Manager server services to MSCS, you must bring the services online.

Steps

1. In the MSCS interface, select Cluster Group under the Groups folder.

2. Click File, and then click Bring Online.

Configuring a host service in MSCSWhen you add a new host service in a cluster environment, you must ensure that both nodes in acluster pair have access to the keys folder. This ensures that when one node fails, the second node ofthe cluster pair starts functioning.

Steps

1. Copy the keys folder from one node to the other in the cluster pair atinstallation_directory\conf.

2. In the Cluster Administrator interface, select the cluster group and click Move group, ormanually move the cluster group to the second node and verify that the second node owns theresources.

3. Enter the following command on the second node to start using the new setting:dfm ssl service reload

4. Launch the OnCommand console and verify that the host service status is Up in the HostServices tab.

Managing DataFabric Manager server in an MSCSenvironment

You can create and restore backups, set HTTPS options, and configure DataFabric Manager server toshare data on the DataFabric Manager server cluster nodes.

Best practices to start and stop DataFabric Manager server services inMSCS

After you set up DataFabric Manager server in MSCS, do not use the dfm service start and dfmservice stop commands, except where specifically indicated in installation and configurationprocedures. These commands interfere with the working of MSCS.You must start or stop all operations by using either the Cluster Administrator in MSCS or thecluster.exe command.


Note: Do not change the Service startup type to Automatic in the Service Control Manager onany of the nodes. You must ensure that this option is set to Manual.

Restoring the DataFabric Manager server database in MSCSRestoring a database enables the DataFabric Manager server to use the current settings. You canrestore the database by using Cluster Administrator.

Steps

1. Log in to the node that currently owns the cluster resources.

2. In Cluster Administrator, take the services offline by completing the following steps:

a) Right-click the DFM Sybase service.b) Select Take offline.

The other services are also taken offline.

3. Restore the database by entering the following command in the OnCommand console:dfm backup restore

4. Stop all the services by entering the following command in the OnCommand console:dfm service stop

5. In Cluster Administrator, bring the DataFabric Manager server services online:

a) Select Cluster Group under the Groups folder.b) Click File, and click Bring Online.

Configuring DataFabric Manager server to use HTTPS in MSCSYou can configure DataFabric Manager server to use HTTPS on both the cluster nodes for securedata transfers.

About this task

HTTPS is first set up with an SSL certificate, and then the HTTPS option is enabled on both thenodes.

Steps

1. Log in to the first node in the cluster.

2. In Cluster Administrator, take the DataFabric Manager server services offline:



3. Start the SQL service by entering the following command in the OnCommand console:


dfm service start sql

4. Create an SSL certificate for HTTPS by entering the following command:dfm ssl server setup

This creates two files, server.crt and server.key, in the installation_directory\conf folder.

5. Set the DataFabric Manager server option to enable HTTPS by entering the following command:dfm option set httpsEnabled=yes

6. Start the HTTP service by entering the following command:dfm service start http

Starting the service using dfm service start re-creates the httpd.conf file with thechanged options.


7. Ensure that the DataFabric Manager server services are offline.

If the services are not offline, the HTTP service is not enabled on the other node, because theconfiguration is not complete.

8. Stop all the services by entering the following command:dfm service stop

9. In Cluster Administrator, move the cluster group to the second node by using the Move Groupoption.

10. Log in to the second node in the cluster.

11. Copy the server.crt and server.key files created on the first node to theinstallation_directory\conf folder in the second node.

12. Start the services and verify that they are operating as required by entering the followingcommand:dfm service start

Starting the service by using dfm service start re-creates the httpd.conf file with thechanged options.

13. Stop the services by entering the following command:dfm service stop




Changing HTTP options in an MSCS environment

You can change the HTTP options to enable HTTPS, or change the default HTTP and HTTPS ports.

Steps

1. Log in to the first node in the cluster.




3. Start the SQL service by entering the following command:


Attention: You should perform all cluster operations by using either Cluster Administrator orcluster.exe. Except where specifically indicated in installation and configurationprocedures, do not use dfm service start and dfm service stop. These commandsinterfere with cluster operations.

4. Set the required HTTP option by entering the following command:

dfm option set option-name=option-value

Example


5. Start the HTTP service by entering the following command:


Starting the service by using dfm service start re-creates the httpd.conf file with thechanged options.

6. Stop all the services by entering the following command:

dfm service stop

Note: You must ensure that DataFabric Manager server services are offline before proceeding.Otherwise, HTTP is not enabled on the other node because the configuration is not complete.



9. Start the services by entering the following command:

dfm service start


10. Stop the services by entering the following command:

dfm service stop



DataFabric Manager server monitoring in MSCSMicrosoft provides the Server Clusters Management Pack as part of Microsoft Operations Manager.You can monitor the cluster server, and report node status, resource status, and alerts by usingCluster Administrator in MSCS. DataFabric Manager server does not provide any additional clustermonitoring or alerting functionality.

Data shared by MSCS cluster nodesYou must configure the DataFabric Manager server Microsoft Cluster Server (MSCS) nodes toaccess files from a shared disk. Using a shared disk ensures that any updates to these files arereflected in the files of the other nodes in the cluster after a failover.

The MSCS cluster nodes share the following files:

installation_directory\data Sybase database files

installation_directory\perfdata Performance Advisor data files

installation_directory\scriptplugins Installed script plug-ins and related files

installation_directory\plugins Storage system configuration plug-ins

installation_directory\reports Archived reports

installation_directory\dataExport DataFabric Manager server and PerformanceAdvisor data

installation_directory\jetty Libraries and Web application files

installation_directory\conf\keys Encryption keys

Data that is not shared by MSCS cluster nodesFiles such as executables, configuration files, and licenses are not shared by the MSCS cluster nodes.This ensures that the same version is maintained in the cluster nodes.

The following files are not shared:

installation_directory\bin Executable files

installation_directory\conf Configuration files

installation_directory\docs Third-party licenses


installation_directory\examples Cluster configuration scripts, and so on

installation_directory\log Log files

installation_directory\misc Configuration files

installation_directory\sbin Third-party executables

installation_directory\scripts Sybase_install.sql

installation_directory\src Storage system configuration plug-ins

installation_directory\web\clients Performance Advisor clients

installation_directory\web\com JAR files for applets

installation_directory\web\help Help files

installation_directory\web\man Manual pages

installation_directory\web\media Images used on Web interfaces

installation_directory\web\scripts Java script files

installation_directory\web\styles CSS style sheets

installation_directory\perfExport Exported performance counter data for specifiedobjects

Uninstalling the OnCommand Unified Manager CorePackage in an MSCS environment

You can uninstall the OnCommand Unified Manager Core Package from a cluster by deleting thecluster services from each cluster node.

Steps

1. In Cluster Administrator, delete all the DataFabric Manager server services:

a) Right-click the DFM Sybase resource.b) Select Delete.

The other DataFabric Manager server services are also deleted.

2. Log in to any one of the cluster nodes.

3. From the Windows Add or Remove Programs utility, uninstall the OnCommand Unified ManagerCore Package.

4. Repeat Steps 2 through 3 for the other nodes.


Upgrading OnCommand Unified Manager Core Package inan MSCS environment

You must ensure that all the nodes in the cluster are upgraded to the correct OnCommand UnifiedManager Core Package version.

Before you begin

• The OnCommand Unified Manager Core Package installer must be downloaded from the N seriessupport website (accessed and navigated as described in Websites on page 10).

• A backup of your existing DataFabric Manager server database must be created.• The database must be present at the following path: INSTALL_DIR/DFM/data.

The database files monitordb.db and monitordb.log must be available on the shared disk.• The DFM WebUI services must be added to the DataFabric Manager server.

Steps

1. From Cluster Administrator, take the DataFabric Manager server services offline:



2. Select the Owner field of the Resources folder to ensure that the first node owns the resourcegroup named Cluster Group.

3. Upgrade to the OnCommand Unified Manager Core Package installation on the first node:

a) Run the executable file.b) Follow the setup prompts to complete the installation.

4. Stop all the DataFabric Manager server services by entering the following command:

dfm service stop


5. Disable the automatic service start-up during reboot by entering the following command:


6. In Cluster Administrator, move the cluster group to the second cluster node by selecting thegroup name in Services and Applications, and then click Move this service or application toother node.


7. Select the Owner field of the Resources folder to upgrade the second node.

You must ensure that the second node owns all the cluster resources.

8. Perform a manual failover to the second node by entering the following commands on the secondnode:hagrp -switch cluster_group -to node2

hastop -sys node1 –force

9. Stop all the DataFabric Manager server services by entering the following command:dfm service stop

10. Optional: Move the DataFabric Manager server data to the shared data disk by entering thefollowing command:dfm datastore setup -n -d INSTALL_DIR/DFM/data

Important: You must perform this step if you are upgrading to OnCommand Unified ManagerCore Package 5.1 or later from any version from DataFabric Manager server 3.8 throughOnCommand Unified Manager Core Package 5.0.

Note: The -n option forces the server to use the database present at the specified path.

11. Point the Sybase database to use the new database by running the following command:dfm datastore setup -n -d LUN_PATH

12. Check the status of the SQL service by running the following command:dfm service list sql

If the service is not running, you must run the dfm service start sql command.

13. Upgrade to the OnCommand Unified Manager Core Package installation on the second node:


14. Disable the automatic service start-up during reboot by entering the following command:dfm service enable -m

15. In Cluster Administrator, click the console tree, and double-click the Groups folder.

16. In the Details pane, click the group named Cluster Group.

17. Select the File menu, and then select New > Resource.

18. On the New Resource page, complete the following steps:

a) In the Name field, enter the following name:DFM WebUI

b) Select Generic Service as the Service Type.c) Select Cluster Group as the group.


d) Click Next.

19. On the Possible Owners page, add both the nodes as the possible resource owners, and clickNext.

20. On the Dependencies page, add DFM Sybase ASA as a dependency on DFM WebUI, and clickNext.

21. On the DFM Apache Properties page, set DFM WebUI to be dependent on DFM Apache.

22. On the Generic Service Parameters page, complete the following steps:

a) In the Service Name field, enter the following name:

DFM WebUI

b) Clear the Use Network name for computer name option.

23. Bring the DataFabric Manager server services online:


24. Set the database path back to the upgraded database on the LUN by running the followingcommand:

dfm datastore setup -n -d LUN_PATH

Related tasks

Configuring DataFabric Manager server on the cluster nodes in VCS on page 130


Installing and configuring the Core Package in aVCS environment

Veritas Cluster Server (VCS) provides HA protection for cluster configurations.

As part of the OnCommand Unified Manager Core Package installation process, the DataFabricManager server and its associated services are installed on your system. The cluster resources,including the services for the DataFabric Manager server, the network name, the network address,and the shared data disks, are always online and available on one of the nodes. You must configurethe network name and address, and the shared data disks, during the OnCommand Unified ManagerCore Package installation process.

When a resource node failure is detected, all the resources are automatically moved, or failed over, tothe partner node by VCS.

Preparing to install OnCommand Unified Manager CorePackage in a VCS environment

To ensure HA of the DataFabric Manager server, you must configure the services to beaccessible through a network name and a network address. The DataFabric Manager server can alsouse this network name or network address; therefore, you do not have to add new network resourcesfor the services.

A VCS cluster configured with the DataFabric Manager server consists of two nodes, each noderunning the same version of the DataFabric Manager server. All of the DataFabric Manager serverdata (database files, Performance Advisor files, and so on) is configured to be accessed from a shareddata disk.

Prerequisites for installing OnCommand Unified Manager Core Package inVCS

Before installing OnCommand Unified Manager Core Package in Veritas Cluster Server (VCS), youmust ensure that the VCS configuration requirements are met.

VCS must be installed according to the instructions provided in the Veritas Cluster Server 5.0Installation Guide

Related information

Veritas Cluster Server Symantec Support


http://www.symantec.com/business/cluster-server

http://www.symantec.com/business/support

Configuration requirements for OnCommand Unified Manager CorePackage in VCS

Before installing OnCommand Unified Manager Core Package in Veritas Cluster Server (VCS), youmust ensure that the cluster nodes are properly configured to support the OnCommand UnifiedManager software.

You must ensure that the VCS configuration meets the following requirements:

• Both of the cluster nodes must be running a supported operating system version.The minimum supported operating systems are Red Hat Enterprise Linux 5.6 and SUSE LinuxEnterprise Server 10 with SP3.

• The same version of the OnCommand Unified Manager Core Package must be installed using thesame path on both of the cluster nodes.

• Veritas File System and Volume Manager on Native ext3 File System and Logical VolumeManager (LVM) must be used.

• The DataFabric Manager server should be connected to the storage system using Fibre Channel(FC).Also ensure that the FC link is active and that the LUNs created on the storage systems areaccessible to both of the cluster nodes.

• The shared data disk must have enough space to accommodate the DataFabric Manager serverdatabase, performance data, and script plug-in folders.

• A minimum of two network interfaces must be set up on each system: one for node-to-nodecommunication and the other for node-to-client communication.The name of the network interface used for node-to-client communication should be the same onboth the systems.

• A separate heartbeat link must be established between the cluster nodes; otherwise, the networkinterface is used to communicate between the cluster nodes.

Configuration limitations for the OnCommand Unified Manager CorePackage in VCS

You must be aware of the configuration limitations before you install the OnCommand UnifiedManager Core Package in a VCS environment.

The following are configuration limitations in VCS:

• Only two-node clusters are supported.• The OnCommand Unified Manager Core Package in VCS is not supported on VMware.• For shared disks, the storage back-end must be an FC-based storage only.• iSCSI storage is not supported for the OnCommand Unified Manager Core Package in VCS.

Installing and configuring the Core Package in a VCS environment | 125

Installing OnCommand Unified Manager Core Package in aVCS environment

You must install Veritas Storage Foundation first and then install OnCommand Unified ManagerCore Package in VCS. After you install these on both the nodes, you must configure the DataFabricManager server on the cluster node.

Configuring VCS to install the OnCommand Unified Manager Core PackageBefore you install the OnCommand Unified Manager Core Package in VCS, you must installSnapDrive, a Fibre Channel adapter, and Veritas Storage Foundation. You must then configure VCSand use SnapDrive for UNIX to create file systems.

Before you begin

• All requirements and guidelines for configuring cluster servers must be met, according to theVCS documentation.

• SnapDrive for UNIX must be installed.

Steps

1. Install Veritas Storage Foundation and HA Solutions 5.0 with Maintenance Pack 1(MP 1).

When you install Veritas Storage Foundation and HA Solutions 5.0, VCS is alsoinstalled.

2. Configure VCS by entering the following command:

installvcs -configure

3. Enter the network address (virtual IP address).

4. Use SnapDrive for UNIX to create file systems and logical volumes.

Related information

Veritas Cluster ServerVeritas Storage FoundationIBM N series support website: www.ibm.com/storage/support/nseries/


http://www.symantec.com/business/cluster-server

http://www.symantec.com/en/in/business/storage-foundation

http://www.ibm.com/storage/support/nseries/

Installing OnCommand Unified Manager Core Package on VCSTo ensure HA, you must install OnCommand Unified Manager Core Package on the twocluster nodes of VCS.

Before you begin

• VCS must be installed and configured on both the nodes of the cluster.• The same version of OnCommand Unified Manager Core Package must be installed on both the

nodes.• The installation directory is the same on both the nodes: for example, /opt/IBMdfm.• The first node must own the cluster resources.• You must have root privileges to log in to the DataFabric Manager server.• The OnCommand Unified Manager Core Package installer must be downloaded from the N series

support website (accessed and navigated as described in Websites on page 10)• You must have set the environment variable on both nodes as VCS PATH: PATH=/opt/

VRTSvcs/bin:$PATH.

About this task

During a new installation, you must specify the OnCommand Unified Manager Core license key. Ifyou are upgrading from an earlier licensed version of DataFabric Manager server, you do not requirea license key.

The two DataFabric Manager server nodes are configured to use the same database and to monitorthe same set of nodes. Therefore, you can use the same license on both the nodes.

The installation and upgrade process automatically installs the AutoSupport feature withAutoSupport enabled and displays a message about how to disable the feature.

Steps

1. Log in to the first node.

2. Run the executable file.

3. Follow the setup prompts to complete the installation.

4. Disable the automatic start-up of the DataFabric Manager server by entering the followingcommand:


Attention: You must perform all cluster operations using Cluster Manager. Other than ininstallation and configuration procedures, you must not use the dfm service start and dfmservice stop commands. These commands interfere with cluster operations.

5. When the installation is complete, enter the following command to stop the DataFabric Managerserver services:


dfm service stop

6. Log in to the second node.

7. Start the cluster service on the second node by entering the following command:

hastart

8. Perform a manual failover to the second node by entering the following command on the secondnode:

hagrp -switch cluster_group -to node2


9. Run the executable file on the second node.

10. Follow the setup prompts to complete the installation.

11. Restart the cluster service on the second by entering the following command:

hastart

12. Disable the automatic start-up of the DataFabric Manager server by entering the followingcommand:


13. Stop all services on the second node by entering the following command:

dfm service stop

Related information


Configuring OnCommand Unified Manager Core Package ina VCS environment

After installing OnCommand Unified Manager Core Package, you have to configure the DataFabricManager server in VCS.

DataFabric Manager server service resources added to VCSYou must add the DataFabric Manager server cluster service resources to VCS. There aredependencies among the various resources.

These services are used for various purposes, such as monitoring storage systems, scheduling jobs,processing events, and monitoring all the other services.

The following illustration shows the services and the dependencies among the various resources:



dfm-webserver dfm-scheduler dfm-monitor

dfm-dbsrv

dfm_mount

dfm_nic dfm_vol

dfmeventd

dfm-server dfm-watchdog

dfm_vip

dfm_vip: cluster virtual address. Eg: IP_10_72_181_243

dfm_nic: NIC Eg: eth0, eth1

dfm-webui

Script options for configuring services in VCSYou have to configure the DataFabric Manager server to add its service resources to VCS. You canadd the services manually, or by using the Perl configuration script.The command to add services to the DataFabric Manager server is as follows:

perl dfmcluster_add_resources.pl -t cluster_type option ...

The perl dfmcluster_add_resources.pl includes the following options:

-t cluster_type Cluster solution used for HA. The possiblevalues are vcs (default value on UNIX) and mscs.

-h cluster_node1 cluster_node2 Nodes used for cluster setup, separated by a space.

-g cluster_group_name Name of the cluster service group to which the resourcesare added.

-e nic_resource_name Name of the network interface card. This must be the sameon both cluster nodes.

-i cluster_ip_resource_name Name of the cluster IP resource.

-n cluster_name_resource_name Host name of the cluster, which is mapped to the clustervirtual IP address.

-f mount_point_resource_name Name of the mount resource.


-v volume_resource_name Name of the volume resource that contains the filesystem,represented by the mountpoint resource.

-d disk_group_resource_name Name of the disk group that contains the volume,represented by the volume resource.

-m netmask Netmask associated with the cluster IP address.

-l installation_directory OnCommand Unified Manager Core Package installationdirectory. The default location is /opt/IBMdfm.

Configuring DataFabric Manager server on the cluster nodes in VCSYou must configure the DataFabric Manager server on two nodes in a cluster to allow failover. Youhave to configure the DataFabric Manager server on the first node and then on the second node.

Steps

1. Stop the cluster service of the second node by entering the following command on the first node:hastop -sys node2 -force

2. Move all the shared data, such as database files and performance data files, from the first node byentering the following command:dfm datastore setup /mnt/vcsDisk1

/mnt/vcsDisk1 is the mount point.

3. Stop all services on the first node by entering the following command:dfm service stop

4. Add the cluster services as cluster resource by entering the following command on the first node:perl dfmcluster_add_resources.pl -t vcs -h node1 node2 -g cluster_group-i cluster_ip_resource_name -n cluster_name_resource_name -ddisk_group_resource_name -v volume_resource_name -fmount_point_resource_name -e nic_resource_name -m netmask

5. Verify the status of the cluster resources on the first node by entering the following commands:hasys –list

hastatus –summ

hagrp –state

hares –state

haclus –state

6. Start the cluster service on the second node by entering the following command:hastart

7. Perform a manual failover to the second node by entering the following command on the secondnode:




Note: You can run the snapdrive storage list -fs /mnt/vcsDisk1 command on thesecond node to verify the status of the mount point.

8. Configure the second node to use the shared data by entering the following command:

dfm datastore setup -n /mnt/vcsDisk1

Using the -n option while configuring the second node ensures that the DataFabric Managerserver uses the data that was copied during the configuration of the first node.

9. Stop all services on the first node by entering the following command:

dfm service stop

10. Start the cluster services on the first node by entering the following command:

hastart

11. Verify the status of the cluster resources on both nodes by entering the following commands onthe two nodes:

hasys –list

hastatus –summ

hagrp –state

hares –state

haclus –state

12. Start the services on the second node by entering the following command on the second node:

hagrp -online cluster_group -sys node2

Configuring DataFabric Manager server in VCS manuallyYou can manually configure the DataFabric Manager server by using the VCS ApplicationConfiguration wizard. Configuring the DataFabric Manager server in VCS manually enables you tocustomize the cluster.

Before you begin

You must have ensured that the DataFabric Manager server is installed at /opt/IBMdfm.

Steps

1. Run the VCS Application Configuration wizard by entering the following command on thenode where VCS is set up:

hawizard

2. Select Create Application Service Group and click Next.


3. Enter a name in Service Group Name and select the cluster from the Available Cluster list.

4. Click Next.

5. Enter the application details:

a) Specify /usr/bin/dfm as the path in Start Program.b) Select root as user.

6. Click Next.

7. Select the processes that must be monitored by the DataFabric Manager server by entering theappropriate process monitor string.

The following table lists the processes and their process monitor string:

Process Process monitor string

+ dfmmonitor /opt/IBMdfm/sbin/dfmmonitor

+ dfmserver /opt/IBMdfm/sbin/dfmserver

+ dfmscheduler /opt/IBMdfm/sbin/dfmscheduler

+ dfmeventd /opt/IBMdfm/sbin/dfmeventd

+ database server /opt/IBMdfm/sbin/dbsrv11@/opt/IBMdfm/conf/sybase.conf

+ Apache server /opt/IBMdfm/sbin/httpd/opt/IBMdfm/conf/httpd.comf

+Webui /opt/IBMdfm/java/bin/java/opt/IBMdfm/jetty/start.jar/opt/IBMdfm/conf/jetty.conf

8. Verify the process monitor string for each process by using the ps -u root -o argscommand.

9. Click Next.

10. Configure the mount resources and click Next.

11. Configure the IP and NIC resources and click Next.

12. Repeat Steps 5 through 11 for each DataFabric Manager server process.

13. Open Cluster Manager to configure the remaining cluster resources.

14. Select the service group dfm_sg in the left pane.

15. In the Resource tab, right-click Resource View.

16. Enter the details for each Resource Type.


On Linux, you should select only LVMLogicalVolume and Mount as the resource types. TheFSType attribute should be set to ext3 for Mount.

17. Select NIC from the Resource Type list.

18. Right-click the added resources and select Link.

19. Create a dependency tree and bring all the services online.

20. Ensure the DataFabric Manager server uses the cluster name (instead of the local system name)by entering the following command:dfm option set localHostName=fqdn-of-cluster

The DataFabric Manager server uses the name of the local system to send email alerts toadministrators.

Configuring a host services in VCSWhen you add a new host service in VCS, you must ensure that both nodes in a cluster pair haveaccess to the keys folder. This ensures that when one node fails, the second node of the cluster startsfunctioning.

Steps

1. Copy the keys folder from one node to the other in the cluster pair atinstallation_directory\conf.

2. Open the Cluster Manager by entering the following command at the command prompt:hagui

3. In the Cluster Manager, right-click the service group, click Switch To, and select the secondcluster node for failover

4. Enter the following command on the second node to start using the new setting:dfm ssl service reload

5. Launch the OnCommand console, verify that the host service status is Up in the Host Servicestab.

Best practices to start and stop DataFabric Manager server services in VCSAfter you set up DataFabric Manager server in VCS, do not use the dfm service start and dfmservice stop commands, except where specifically indicated in installation and configurationprocedures. You must perform all operations by using the Cluster Manager.

• You should disable the DataFabric Manager server init scripts after installation on both the clusternodes.

• You should not change the service start-up type to Automatic in Service Control Manager on anyof the nodes.The DataFabric Manager server reactivates these scripts during an upgrade and then disablesthem again when the upgrade is complete.


Managing the DataFabric Manager server in a VCSenvironment

You can create and restore backups, set HTTPS options, and configure DataFabric Manager server toshare data on the DataFabric Manager server cluster nodes.

Restoring the DataFabric Manager server database in VCSRestoring a database enables the DataFabric Manager server to use the current settings. You canrestore the DataFabric Manager server database by disabling it through Cluster Manager and usingthe dfm backup restore command.

Steps

1. In Cluster Manager, disable the DataFabric Manager server services by right-clicking the nameof the service group and then clicking Offline.

2. Select the first cluster node in which the services are online. N series Management Console

3. Ensure that one of the nodes owns the cluster resources (such as the mount point) by completingthe following steps:

a) Select the service group dfm_sg.b) In the Resources tab, right-click Resource View.c) Right-click the resource Mount, and then click Online

4. Restore the database by entering the command in the node that owns the Mount resource:dfm backup restore

5. In Cluster Manager, right-click the service group, click Online, and then select the first clusternode that is used for restore.

Changing default port numbers for HTTP and HTTPS protocolsYou can change the default port numbers for HTTP and HTTPS protocols.

Before you begin

The DFM Apache service must have been offline before the port numbers are changed in both thenodes.

Steps

1. Log in to the first node.


a) Right-click the DFM Sybase service.


b) Select Take offline.

All services go offline.

3. Start the SQL service by running the following command:


4. Set the new HTTP or HTTPS port numbers by running the following command:

dfm option set option_name=value

Example

Set the new HTTP port:

dfm option set httpPort=8081

Set the new HTTPS port


5. Restart the HTTP or HTTPS service by running the following commands:

• The following commands restarts the HTTPS service:

dfm service stop webui

dfm service start webui

• The following commands restarts the HTTP service:



6. Optional: Verify the changed port numbers by viewing the httpd.conf file.

7. Stop the HTTP and HTTPS services by running the following commands:


dfm service stop webui


9. Log in to the second node.

10. Start the HTTP and HTTPS services on the second node by entering the following commands:


dfm service start webui

11. Optional: Verify the changed port numbers by viewing the httpd.conf file.




Configuring the DataFabric Manager server to use HTTPS in VCSYou can configure the DataFabric Manager server to use HTTPS on both the cluster nodes for asecured data transfer.

About this task

You must not take the dfm-dbsrv service offline.

Steps

1. In Cluster Manager, take the DataFabric Manager server services offline:

a) Right-click the service group dfm-sg, and click Offline.b) Select the first cluster node where the services are online.c) In the Resources tab, right-click Resource View.d) Right-click the resource dfm-dbsrv and click Online.

2. Create an SSL certificate by entering the following command:

dfm ssl server setup

3. Copy the files server.crt and server.key to the second node before starting the services onthat node.

The files are located in the installation_directory/conf folder.

4. Enable HTTPS by setting the following DataFabric Manager server option to yes:

dfm option set httpsEnabled=yes

5. Start the HTTP service by entering the following command:


This re-creates the httpd.conf file with the changed options.

6. Stop all the services by entering the following command:

dfm service stop

Note: You must ensure that DataFabric Manager server services are offline. Otherwise, theHTTP service fails to be enabled on the other node, because the configuration is not complete.

7. In Cluster Manager, move the cluster group to the second node by using the option Switch To.


9. Copy the files server.crt and server.key created on the first node to the folder install-dir/conf.

10. Start the services and verify that they are operating by entering the following command:

dfm service start


This creates the httpd.conf file with the changed options.

11. Stop the services by entering the following command:dfm service stop

12. In Cluster Manager, reenable the DataFabric Manager server services.

Changing the HTTP options in a VCS environment

You can change the HTTP options to enable HTTPS, or change the default HTTP and HTTPS port.

About this task

You must not take the dfm-dbsrv service offline.

Steps

1. In Cluster Manager, take the DataFabric Manager server services offline:

a) Right-click the service group, and click Offline.b) Select the first cluster node where the services are online.c) In the Resources tab, right-click Resource View.d) Right-click the resource dfm-dbsrv and click Online.

2. Set the required HTTP option by entering the following command:dfm option set option-name=option-value

Example


3. Restart the HTTP service by entering the following command:dfm service start http

Attention: You must perform all cluster operations using Cluster Manager. Apart frominstallation and configuration procedures, you should not use the commands dfm servicestart and dfm service stop. These commands interfere with cluster operations.

4. Stop all the services by entering the following command:dfm service stop

This re-creates the file httpd.conf with the changed options.

Note: You must ensure that DataFabric Manager server services are offline. Otherwise, theHTTP service fails to come up on the other node because the configuration is not complete.

5. In Cluster Manager, move the cluster group to the second node by using the option Switch To.


7. Start the services by entering the following command:


dfm service start

8. Stop the services by entering the following command:

dfm service stop

9. In Cluster Manager, bring the DataFabric Manager server services online.

Data shared by VCS cluster nodesYou must configure DataFabric Manager server nodes to access files from a shared disk. If each nodeuses its own local copy of files, any updates to files might not be accessible to the other nodes, after afailover.

The VCS cluster nodes share the following files:

installation_directory/data Sybase database files

installation_directory/perfdata Performance Advisor data files

installation_directory/scriptplugins Installed script plug-ins and related files

installation_directory/plugins Storage system configuration plug-ins

installation_directory/reports Archived reports

installation_directory/dataExport DataFabric Manager server and PerformanceAdvisor data

installation_directory/jetty Libraries and Web application files

Data that is not shared by VCS cluster nodesTo ensure that the same version is maintained in both the cluster nodes, executable and configurationfiles, license information, and so on are not shared by the DataFabric Manager server cluster nodes.

The VCS cluster nodes do not share the following files:

installation_directory/bin Executable files

installation_directory/conf Configuration files

installation_directory/docs Third-party licenses

installation_directory/examples Cluster configuration scripts, and other script files

installation_directory/log Log files

installation_directory/misc Configuration files

installation_directory/sbin Third-party executables

installation_directory/scripts Location of the Sybase_install.sql file

installation_directory/src Storage system configuration plug-ins


installation_directory/web/clients Performance Advisor clients

installation_directory/web/com JAR files for applets

installation_directory/web/help Help files

installation_directory/web/man Manual (man) pages

installation_directory/web/media Images used on Web interfaces

installation_directory/web/scripts Java script files

installation_directory/web/styles CSS style sheets

Uninstalling the OnCommand Unified Manager CorePackage in a VCS environment

You can uninstall the OnCommand Unified Manager Core Package from a cluster by deleting all theDataFabric Manager server services from the cluster nodes.

Steps

1. In Cluster Manager, delete all the DataFabric Manager server services:a) Right-click the service group dfm-sg.b) Select Delete.

2. Log in to one of the cluster nodes.

3. Uninstall by entering the one of the following commands:

• rpm -e IBMdfm

• rpm -erase IBMdfm

4. Repeat Steps 2 through 3 for the other cluster nodes.

Upgrading OnCommand Unified Manager Core Package in aVCS environment

When you upgrade the OnCommand Unified Manager Core Package cluster nodes, you must ensurethat all the nodes in the cluster are upgraded.

Before you begin

• The DataFabric Manager server installer from the N series support website (accessed andnavigated as described in Websites on page 10) must be downloaded.

• A backup of your existing DataFabric Manager server database must be created.• The database must be present at the following path: INSTALL_DIR/DFM/data.


The database files monitordb.db and monitordb.log must be available on the shared disk.

Steps

1. From Cluster Administrator, take the DataFabric Manager server services offline by runningthe following commands on the first node:

hagrp -offline cluster_group -sys node1

hastatus –summ

2. Bring the cluster resources online on the first node by running the command:

hares -online data_mount -sys node1

3. Verify that the first node owns the cluster resources by running the command:

hastatus –summ

4. Optional: Update the monitoring process to point to the new database by running the followingcommand:

hares -modify dfm-dbserver MonitorProcesses "install_dir/sbin/dbsrv11@install_dir/conf/sybase.conf"


5. Upgrade to OnCommand Unified Manager Core Package on the first node:



dfm service stop




8. Perform a manual failover to the second node by entering the following commands on the secondnode:



9. From Cluster Administrator, take the DataFabric Manager server services offline by runningthe following commands on the second node:


hagrp -offline cluster_group -sys node2

hastatus –summ

10. Bring the cluster resources online on the second node by running the command:

hares -online data_mount -sys node2

11. Optional: Point the Sybase database to the old database by running the following command:

dfm datastore setup -n -d old_monitordb_location


12. Upgrade to the OnCommand Unified Manager Core Package installation on the second node:


13. Set Sybase to the shared database location by running the following command:

dfm datastore setup -n -d shared_monitordb_location


dfm service stop



16. From Cluster Administrator, bring the DataFabric Manager server services online by runningthe following command on the second node:

hagrp -online cluster_group -sys node2

Related tasks

Configuring DataFabric Manager server on the cluster nodes in VCS on page 130


Copyright and trademark information

Copyright ©1994 - 2013 NetApp, Inc. All rights reserved. Printed in the U.S.A.

Portions copyright © 2013 IBM Corporation. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosurerestricted by GSA ADP Schedule Contract with IBM Corp.

No part of this document covered by copyright may be reproduced in anyform or by any means— graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

References in this documentation to IBM products, programs, or services donot imply that IBM intends to make these available in all countries in whichIBM operates. Any reference to an IBM product, program, or service is notintended to state or imply that only IBM’s product, program, or service maybe used. Any functionally equivalent product, program, or service that doesnot infringe any of IBM’s or NetApp’s intellectual property rights may beused instead of the IBM or NetApp product, program, or service. Evaluationand verification of operation in conjunction with other products, except thoseexpressly designated by IBM and NetApp, are the user’s responsibility.

No part of this document covered by copyright may be reproduced in anyform or by any means— graphic, electronic, or mechanical, includingphotocopying, recording, taping, or storage in an electronic retrievalsystem—without prior written permission of the copyright owner.

Software derived from copyrighted NetApp material is subject to thefollowing license and disclaimer:

THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANYEXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITEDTO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESSFOR A PARTICULAR PURPOSE, WHICH ARE HEREBY DISCLAIMED. INNO EVENT SHALL NETAPP BE LIABLE FOR ANY DIRECT, INDIRECT,INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTEGOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESSINTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OFLIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT

© Copyright IBM Corp. 2013 142

(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUTOF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.

NetApp reserves the right to change any products described herein at anytime, and without notice. NetApp assumes no responsibility or liability arisingfrom the use of products described herein, except as expressly agreed to inwriting by NetApp. The use or purchase of this product does not convey alicense under any patent rights, trademark rights, or any other intellectualproperty rights of NetApp.

The product described in this manual may be protected by one or more U.S.A.patents, foreign patents, or pending applications.

RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by thegovernment is subject to restrictions as set forth in subparagraph (c)(1)(ii) ofthe Rights in Technical Data and Computer Software clause at DFARS252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).

Trademark information

IBM, the IBM logo, and ibm.com are trademarks or registered trademarks ofInternational Business Machines Corporation in the United States, othercountries, or both. A complete and current list of other IBM trademarks isavailable on the Web at http://www.ibm.com/legal/copytrade.shtml

Linux is a registered trademark of Linus Torvalds in the United States, othercountries, or both.

Microsoft, Windows, Windows NT, and the Windows logo are trademarks ofMicrosoft Corporation in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States andother countries.

NetApp, the NetApp logo, Network Appliance, the Network Appliance logo,Akorri, ApplianceWatch, ASUP, AutoSupport, BalancePoint, BalancePointPredictor, Bycast, Campaign Express, ComplianceClock, Cryptainer,CryptoShred, Data ONTAP, DataFabric, DataFort, Decru, Decru DataFort,DenseStak, Engenio, Engenio logo, E-Stack, FAServer, FastStak, FilerView,FlexCache, FlexClone, FlexPod, FlexScale, FlexShare, FlexSuite, FlexVol,FPolicy, GetSuccessful, gFiler, Go further, faster, Imagine Virtually Anything,Lifetime Key Management, LockVault, Manage ONTAP, MetroCluster,MultiStore, NearStore, NetCache, NOW (NetApp on the Web), Onaro,OnCommand, ONTAPI, OpenKey, PerformanceStak, RAID-DP, ReplicatorX,SANscreen, SANshare, SANtricity, SecureAdmin, SecureShare, Select, Service

143 IBM System Storage N series: OnCommand® Unified Manager Installation and Setup Guide For Use with

Core Package 5.2 and Host Package 1.3

Builder, Shadow Tape, Simplicity, Simulate ONTAP, SnapCopy, SnapDirector,SnapDrive, SnapFilter, SnapLock, SnapManager, SnapMigrator, SnapMirror,SnapMover, SnapProtect, SnapRestore, Snapshot, SnapSuite, SnapValidator,SnapVault, StorageGRID, StoreVault, the StoreVault logo, SyncMirror, TechOnTap, The evolution of storage, Topio, vFiler, VFM, Virtual File Manager,VPolicy, WAFL, Web Filer, and XBB are trademarks or registered trademarksof NetApp, Inc. in the United States, other countries, or both.

All other brands or products are trademarks or registered trademarks of theirrespective holders and should be treated as such.

NetApp, Inc. is a licensee of the CompactFlash and CF Logo trademarks.

NetApp, Inc. NetCache is certified RealSystem compatible.

Notices

This information was developed for products and services offered in theU.S.A.

IBM may not offer the products, services, or features discussed in thisdocument in other countries. Consult your local IBM representative forinformation on the products and services currently available in your area. Anyreference to an IBM product, program, or service is not intended to state orimply that only that IBM product, program, or service may be used. Anyfunctionally equivalent product, program, or service that does not infringe onany IBM intellectual property right may be used instead. However, it is theuser’s responsibility to evaluate and verify the operation of any non-IBMproduct, program, or service.

IBM may have patents or pending patent applications covering subject matterdescribed in this document. The furnishing of this document does not giveyou any license to these patents. You can send license inquiries, in writing to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, N.Y. 10504-1785U.S.A.

For additional information, visit the web at:http://www.ibm.com/ibm/licensing/contact/

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:

Copyright and trademark information 144

INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDESTHIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND,EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,THE IMPLIED WARRANTIES OF NON-INFRINGEMENT,MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Somestates do not allow disclaimer of express or implied warranties in certaintransactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes willbe incorporated in new editions of the publication. IBM may makeimprovements and/or changes in the product(s) and/or the program(s)described in this publication at any time without notice.

Any references in this information to non-IBM web sites are provided forconvenience only and do not in any manner serve as an endorsement of thoseweb sites. The materials at those web sites are not part of the materials forthis IBM product and use of those web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way itbelieves appropriate without incurring any obligation to you.

Any performance data contained herein was determined in a controlledenvironment. Therefore, the results obtained in other operating environmentsmay vary significantly. Some measurements may have been made ondevelopment-level systems and there is no guarantee that these measurementswill be the same on generally available systems. Furthermore, somemeasurement may have been estimated through extrapolation. Actual resultsmay vary. Users of this document should verify the applicable data for theirspecific environment.

Information concerning non-IBM products was obtained from the suppliers ofthose products, their published announcements or other publicly availablesources. IBM has not tested those products and cannot confirm the accuracyof performance, compatibility or any other claims related to non-IBMproducts. Questions on the capabilities of non-IBM products should beaddressed to the suppliers of those products.

If you are viewing this information in softcopy, the photographs and colorillustrations may not appear.

145 IBM System Storage N series: OnCommand® Unified Manager Installation and Setup Guide For Use with

Core Package 5.2 and Host Package 1.3

Index

7-Mode managementupgrading for 84

AAdobe Flash Player

version required 27associating storage systems 66authentication

certificate-based 71certificate-based, disabling 74certificate-based, generating a key and certificate 72

Bbest practices

for stopping and starting the services 115browser requirements

Firefox 24Internet Explorer 24OnCommand 24

Ccertificate details

displaying DataFabric Manager server 74certificates

about SSL 71authentication using 71displaying contents of key 73displaying details from truststore 73displaying list in a truststore 72installing in the truststore 72management of cloud service client 71management of host services client 75migrating manually 75removing from the truststore 72

changing user credentials 98checklist

configuration 13installation 13

cloud service clientcertificate management 71

cluster servicesadding using a script 108

clustered Data ONTAP managementupgrading for 84

cmdletsinstalling 47

configurationchecklist 13DataFabric Manager server in VCS, scripts for 129Express edition server 55Standard edition server 59

configuringDataFabric Manager server in MSCS 109DataFabric Manager server manually in VCS 131MSCS environment 103VCS nodes 130

connection issues 95Core Package

capabilities 13changes that affect upgrade to 79installing on Linux 40installing on Windows 38upgrading on Linux 82upgrading on Windows 81See also OnCommand Core PackageSee also OnCommand Core Package

core package cmdletsinstalling 47

credentialsstorage systems 68

cursor displays in multiple locations 95

Ddashboard panel, cursor displays in multiple locations 95data protection

license requirements 26data shared by cluster nodes 119database files

requirements for network storage 27DataFabric Manager Host Agent

versions supported 28DataFabric Manager server

adding cluster services using scripts 108Express edition functionality 21Standard edition functionality 21verifying host service registration 60with Express and Standard editions 20

Index | 146

DataFabric Manager server certificatedisplaying details 74

DataFabric Manager server in MSCSbringing services online 109, 115cluster service resources 107configuring 109configuring cluster services 113configuring HTTP and HTTPS

changing default HTTP and HTTPS ports 118configuring HTTPS 116configuring the first node 110configuring the second node 112data shared by cluster nodes 119guidelines to start and stop services 115monitoring 119moving data files 111restoring the database 116unshared data by cluster nodes 119

DataFabric Manager server in VCScluster service resources 128configuration scripts 129configuring HTTP and HTTPS 137configuring HTTPS 136configuring manually 131guidelines to start and stop services 133restore the database 134shared data by cluster nodes 138unshared data by cluster nodes 138

DataFabric Manager truststore 71See also truststore

deletion of certificates from the truststore 72designated ports

OnCommand Host Package 35disabling

certificate-based authentication 74disk space requirements 33duplicate UUID 98

Eenabling

secure communication between the DataFabricManager server and storage system 77

error messagesAccess is denied 98Address already in use 95Could not find any storage mapping for applicationobject 97Operation timed out 98Primary key for table is not unique 98

There is a problem with this Windows Installerpackage 95

ESX timeout 98Express edition

description 20Express edition server

configuring 55

FFirefox

browser requirements 24

Hhardware requirements

Linux workstation or server 30, 31OnCommand Host Package 33Windows Server 2008 28, 29

Host Packagecapabilities 13See also OnCommand Host Package

host service fails to connect to DataFabric Manager server99host service is unresponsive 100host service port

setting manually 88host services

adding 64associating with vCenter Server 62authorizing access to storage 61communication with plug-ins 65configuring in MSCS 115configuring in VCS 133overview 16registering 64registering with vCenter Server 62verifying communication with DataFabric Managerserver 99verifying server registration 60

host services clientcertificate management 75

hotfixes.NET Framework

Net.TCP Port Sharing ServiceWindows PowerShell

Windows Installer Visual C++ 34required before installing Host Package 34

HTTPsetting port number for 134


HTTPSenabling between the DataFabric Manager serverand storage system 77setting port number for 134

Iinstallation

clustered environment 37core package cmdlets 47of OnCommand Host Package 48prerequisites for 27scenarios for 14

installation checklist 13installation of OnCommand Core Package 36installation overview

7-Mode operating environment 36installation script

options, on Linux 44options, on Windows 43

installingCore Package in VCS 127Core Package on Linux 40Core Package on Windows 38OnCommand Host Package 49

Internet Explorerbrowser requirements 24

Kkeys

displaying contents 73migrating manually 75

keys and certificatesgenerating 72

keys foldersharing between nodes in a cluster 115, 133

Llicenses

for data protection, BCO 26requirements 26

Linux workstation or serverhardware requirements 30, 31operating system requirements 30, 31

login credentials 68

MManagement Console

installing 46manual migration

DataFabric Manager server certificates 75manual upgrade

cmdlets 47memory requirements 33Microsoft Cluster Server (MSCS) 101mixed-mode environments

upgrading to manage 84MSCS

changing HTTP options 118cluster service resources 107configuration requirements for Core Package in 102configuring DataFabric Manager server for HTTPS116configuring DataFabric Manager server services ascluster resources in 113configuring DataFabric Manager server services onthe first node 110configuring DataFabric Manager server services onthe second node 112guidelines to start and stop the services 115initial setup example 106installing the Core Package in 104moving data files to a shared disk 111preparing to install the Core Package 101restoring the DataFabric Manager server database116uninstalling OnCommand Core Package 120upgrading OnCommand Core Package 121

MSCS (Microsoft Cluster Server) 101MSCS environment

configuring 103configuring a host service in 115

NN series Management Console

functionality 18NDMP credentials 68

OOnCommand

architecture 15Express edition 20Express edition server configuration 55

Index | 148

Standard edition 20Standard edition configuration 59troubleshooting 95

OnCommand console 18OnCommand Core Package

changes that affect upgrade to 79configuring 55contents 17downloading software 37environment scenarios 14functionality 18hardware and software requirements 27installed components 17installing 36installing on Linux 40installing on Windows 38installing with a script 42options for install script on Linux 44options for installation script on Windows 43required ports 31required software 27storage environment and installation 14unattended install 42uninstalling 92uninstalling from Linux 93uninstalling from Windows 92upgrading 79upgrading on Linux 82upgrading on Windows 81

OnCommand Core Package in MSCSconfiguration 107configuration limitations 103configuration requirements 102installation 103installation prerequisites 101installing 104preparing to install 101supported configurations 102uninstalling 120upgrading 121

OnCommand Core Package in VCSconfiguration limitations 125configuring 128installation of 126installation prerequisites 124installing 127preparing to install 124supported configurations 125uninstalling 139upgrading 139

OnCommand Host Packageconfiguring 55contents 19designated ports 35downloading software 48functionality in a VMware environment 20hardware and software requirements 33hardware requirements 33installation 48installation prerequisites 48installed components 19installing 49installing with a script 52managing virtual environments 20operating system requirements 33prerequisites for upgrading 85required software 34scripted install options for VMware 53unattended install process 52uninstalling 92uninstalling in a VMware environment 93upgrading 79upgrading in a VMware environment 86

OnCommand Unified Managerbrowser requirements 24components overview 13Data ONTAP support 13license requirements 26

Open System SnapVaultversions supported 28

operating system requirementsLinux workstation or server 30

Operations Manager console 18options

for the installation script, Linux 44for the installation script, Windows 43

outbound ports, insufficient 95

Pphysical storage objects

managing on primary storage 18managing on secondary storage 18

plug-in container for Firefox stops working 96plug-ins

communication with host service 65ports

required for OnCommand Core Package 31setting for HTTP and HTTPS 134setting the number manually 88


ports, insufficient outbound 95PowerShell Cmdlets

functionality 18processor requirements 33

RRelated Objects list

no physical servers displayed 96requirements

for configuring the Core Package in MSCS 102for data protection, license 26for database files, network storage 27for installing Host Package 48for Linux workstation or server 30for upgrading the Host Package 85for Windows Server 2008 28, 29hardware 33licenses 26Linux workstation or server 31system 24

restore fails 98

Sscripts

options to use for installation 53secure communication

enabling between the DataFabric Manager serverand storage system 77

shared lock directorycreating 51with Virtual Storage Console 51

SNMPv3enabling between the DataFabric Manager serverand storage system 77

software requirements 27Standard edition

description 20Standard edition server

configuring 59storage mapping error 96, 97storage systems

associating with a host service 66authorizing host service access 61determining domain or workgroup 70login credentials 68NDMP credentials 68

system requirements 24

Ttemporary disk space requirements 33trust store

See truststoretruststore

contents of 71displaying certificate details from 73displaying certificates 72installing certificates 72migrating manually 75removing certificates 72

Uuninstallation

OnCommand Core Package from Windows 92upgrade

changes that affect 79upgrade issues

upgrading to 3.8 or earlier 88upgrading

32-bit server to 64-bit server 83Core Package

in Linux 83in Windows 83

Core Package, on Linux 82Core Package, on Windows 81OnCommand Core Package in MSCS 121OnCommand Core Package in VCS 139OnCommand Host Package 86

using FC LUNno physical servers displayed 97

VvCenter Server

associating a host service 62registering a host service 62

vCenter Server timeout 98VCS

adding cluster service to nodes in 130configuring DataFabric Manager server manually131configuring the Core Package in 128installing the Core Package in 127preparing to install the Core Package 124restore the DataFabric Manager server database 134uninstalling OnCommand Core Package 139upgrading OnCommand Core Package 139

Index | 150

VCS (Veritas Cluster Server) 124VCS environment

configuring 126configuring a host service in 133

Veritas Cluster Serverinstalling OnCommand Core Package in 124

Veritas Cluster Server (VCS) 124Virtual Storage Console

shared lock directories 51

WWindows Installer service error 95Windows Server 2008

hardware requirements 28, 29operating system requirements 28, 29


��

NA 210-06256_A0, Printed in USA

GA32-1020-03

Date post:	29-Sep-2020
Category:	Documents
Upload:	others
View:	1 times
Download:	0 times

IBM System Storage N series OnCommand Unified Manager ......IBM System Storage N series OnCommand...

Documents