EMC Multiple Systems Management

EMC Multiple Systems Management Version 1.0 Getting Started Guide 302-003-416 REV 02

Copyright 2016-2017 Dell Inc. or its subsidiaries. All rights reserved. Published January 2017 Dell believes the information in this publication is accurate as of its publication date. The information is subject to change without notice. THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE, COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN APPLICABLE SOFTWARE LICENSE. Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of their respective owners. Published in the USA. EMC Corporation Hopkinton, Massachusetts 01748-9103 1-508-435-1000 In North America 1-866-464-7381 www.emc.com 2 EMC Multiple Systems Management 1.0 Getting Started Guide

CONTENTS Preface 5 Chapter 1 Multiple Systems Management Overview 9 Product overview...10 Monitoring multiple systems... 10 Managing multiple systems... 10 Managed Systems and Monitored Systems... 11 High level architecture... 12 Chapter 2 Installation 17 Deployment prerequisites...18 Checking the network setup...18 Hotfixes... 18 Deployment methods... 19 Deploying the Multiple Systems Management OVA...19 Deploying with the standalone installer...20 Verifying the deployment... 21 Access control...22 Default accounts...22 User authorization... 23 Installation directory structure... 23 Port information... 23 System services... 24 Certificate management... 24 Generating a self-sign certificate... 25 Generating a Certificate Signing Request (CSR)...25 Configuring LDAP...26 Adding LDAP to Multiple Systems Management...26 LDAP requirements...27 Chapter 3 Getting Started with Multiple Systems Management Administration 29 Logging in to Multiple Systems Management... 30 User interface overview...30 Main menu button... 30 Admin menu... 31 Accessing the Multiple Systems Management online help... 32 Filtering... 32 Sorting... 35 Chapter 4 Dashboard 37 Dashboard overview... 38 Backups and Replications widgets... 38 Avamar Health widget... 38 Alerts Today and Alerts by System widgets...39 Systems by Usage widget...39 EMC Multiple Systems Management 1.0 Getting Started Guide 3

CONTENTS Chapter 5 Configuration 41 Adding a group... 42 Adding a system... 42 Importing systems... 43 Chapter 6 Monitoring Systems 45 Adding a Data Domain System...46 System Information... 46 Viewing System Information... 46 Activating monitoring...47 Clients... 47 Viewing clients...47 Viewing client backups... 48 MSM Tasks... 48 Viewing MSM tasks... 48 Jobs...49 Viewing Jobs... 49 Alerts...49 Viewing Alerts...49 Events...51 Viewing Events...51 Chapter 7 Managing Systems 53 Viewing Systems... 54 Policies...55 Viewing policies... 55 Adding a policy... 55 Performing a policy based backup now...57 Retentions...58 Viewing retention policies...58 Adding a retention policy... 58 Schedules...59 Viewing schedules... 59 Adding a schedule...59 Datasets... 60 Viewing datasets... 60 Adding a dataset...60 Reset passwords...61 Resetting passwords... 61 Glossary 63 4 EMC Multiple Systems Management 1.0 Getting Started Guide

Preface As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions that are described in this document might not be supported by all versions of the software or hardware currently in use. The product release notes provide the most up-to-date information on product features. Contact your EMC technical support professional if a product does not function correctly or does not function as described in this document. Note This document was accurate at publication time. Go to EMC Online Support (https:// support.emc.com) to ensure that you are using the latest version of this document. Purpose This document includes information about how to install Multiple Systems Management and get started with Multiple Systems Management administration. Audience This document is intended for administrators of Multiple Systems Management. Revision history The following table presents the revision history of this document. Table 1 Revision history Revision Date Description 02 January 20, 2017 Updates include: Added Hotfixes subsection to the Deployment prerequisites section. Added a note in the Configuring LDAP section. 01 December 21, 2016 Initial release of the EMC Multiple Systems Management 1.0 Getting Started Guide. Related Documentation For information about Multiple Systems Management compatibility, go to the following website: http://compatibilityguide.emc.com:8080/compguideapp/ The Multiple Systems Management documentation set includes the following publications: EMC Multiple Systems Management Getting Started Guide EMC Multiple Systems Management Security Configuration Guide EMC Multiple Systems Management Release Notes EMC Multiple Systems Management Administration Guide Special notice conventions that are used in this document EMC uses the following conventions for special notices: Preface 5

Preface NOTICE Identifies content that warns of potential business or data loss. Note Contains information that is incidental, but not essential, to the topic. Typographical conventions EMC uses the following type style conventions in this document: Table 2 Style conventions Bold Italic Monospace Used for names of interface elements, such as names of buttons, fields, tab names, and menu paths (what the user specifically selects or clicks) Used for full titles of publications that are referenced in text Used for: System code System output, such as an error message or script Pathnames, file names, prompts, and syntax Commands and options Monospace italic Monospace bold Used for variables Used for user input [ ] Square brackets enclose optional values Vertical bar indicates alternate selections - the bar means or { } Braces enclose content that the user must specify, such as x or y or z... Ellipses indicate non-essential information that is omitted from the example Where to get help EMC support, product, and licensing information can be obtained as follows: Product information For documentation, release notes, software updates, or information about EMC products, go to EMC Online Support at https://support.emc.com. Technical support Go to EMC Online Support and click Service Center. Several options for contacting EMC Technical Support appear on the site. Note that to open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account. Online communities Go to the EMC Community Network at https://community.emc.com for peer contacts, conversations, and content on product support and solutions. Interactively engage online with customers, partners, and certified professionals for all EMC products. 6 EMC Multiple Systems Management 1.0 Getting Started Guide

Preface Your comments Your suggestions help to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to DPAD.Doc.Feedback@emc.com. 7

Preface 8 EMC Multiple Systems Management 1.0 Getting Started Guide

CHAPTER 1 Multiple Systems Management Overview Learn about Multiple Systems Management. Topics include: Product overview... 10 Monitoring multiple systems... 10 Managing multiple systems...10 Managed Systems and Monitored Systems...11 High level architecture...12 Multiple Systems Management Overview 9

Multiple Systems Management Overview Product overview Monitoring multiple systems Multiple Systems Management provides a centralized location to manage and monitor multiple Avamar and connected Data Domain systems. Multiple Systems Management includes multiple system monitoring features at the job, system, and alert level. The multiple systems monitoring features include: Job Monitor Includes functionality to indicate whether backup and replication jobs are successful. Alert Monitor Provides alert information for: Storage platforms Server software Core processes Managing multiple systems Capacity Monitor Provides capacity information at a system level for backup targets. Backup targets include Avamar server and Data Domain. Multiple Systems Management includes features to manage and monitor multiple systems, including existing Avamar deployments. Features include: Backup Management Provides the ability to: Perform backups, including on-demand backups View existing client backups User Management Provides the ability to perform password changes of local Avamar or operating system users. This functionality is available for the following system users in Avamar: OS root OS Admin OS dpn user Avamar admin Avamar MCUser Avamar repluser Avamar viewuser Policy Management Provides the ability to: Create, update, view, or delete the following: Retentions 10 EMC Multiple Systems Management 1.0 Getting Started Guide

Multiple Systems Management Overview Schedules Datasets Policies Perform an adhoc backup of all clients in a policy Perform property edits for all plug-in types in Datasets Assign or remove clients from a policy group Client Management Provides the ability to: View existing clients in the Avamar systems View existing client backups Managed Systems and Monitored Systems Learn about the differences between Managed Systems and Monitored Systems. Managed Systems A managed system includes all of the features available in a monitored system, in addition to the following: Management capabilities Viewing clients Viewing backups Creating, modifying, viewing, and deleting policies, schedules, retentions, and datasets Adding clients to policies Performing an adhoc backup of all clients in a policy Resetting OS passwords Resetting Avamar user passwords Note Only Avamar systems can be managed. Monitored Systems Avamar and Data Domain systems can be monitored. For Avamar systems: Monitored for system information, alerts, events, backup, and retention activity. Through Multiple Systems Management, Avamar systems cannot be added as a monitored system. Avamar systems can only be added as a managed system. When Avamar systems are added as a managed system, the Avamar system is automatically monitored. If you delete an Avamar from Multiple Systems Management, the system remains monitored until the monitoring system option is disabled from the Avamar. For Data Domain systems: Monitored for system information, and alert information. If the Data Domain system is configured in a monitored Avamar, the Data Domain system is automatically added as a monitored system. Managed Systems and Monitored Systems 11

Multiple Systems Management Overview High level architecture Multiple Systems Management runs on virtual servers, supporting Avamar servers and Data Domain backup targets. The architecture starts with Avamar. Multiple Avamars form a cluster. Figure 1 Avamar cluster Each Avamar uses an MSM adapter to send alerts and events to RabbitMQ, which is the message queue system. Figure 2 Avamars with MSM Adapter and RabbitMQ 12 EMC Multiple Systems Management 1.0 Getting Started Guide

Multiple Systems Management Overview Each Avamar grid forwards alerts and events to a Multiple Systems Management RabbitMQ. Figure 3 Multiple Systems Management RabbitMQ The Multiple Systems Management monitoring instance saves the events to MongoDB. Figure 4 Monitoring instance The Multiple Systems Management UI provides a centralized location for management and monitoring. High level architecture 13

Multiple Systems Management Overview Figure 5 Multiple Systems Management UI The Avamar Concerto REST API is used exclusively by Multiple Systems Management for management functions. Concurrent use of the Concerto REST API with Multiple Systems Management is not supported. Public access of the API has been removed. The following figure displays the complete Multiple Systems Management high level architecture. 14 EMC Multiple Systems Management 1.0 Getting Started Guide

Multiple Systems Management Overview Figure 6 High level architecture High level architecture 15

Multiple Systems Management Overview 16 EMC Multiple Systems Management 1.0 Getting Started Guide

CHAPTER 2 Installation Learn about how to install Multiple Systems Management. Topics include: Deployment prerequisites... 18 Deployment methods...19 Verifying the deployment...21 Access control... 22 Installation directory structure... 23 Port information...23 System services... 24 Certificate management...24 Generating a self-sign certificate... 25 Generating a Certificate Signing Request (CSR)... 25 Configuring LDAP... 26 Installation 17

Installation Deployment prerequisites Checking the network setup Learn about the Multiple Systems Management deployment prerequisites. To ensure that the network setup is correct: 1. Ensure that the time on the Avamar system is set correctly. For successful activation certificates, the time that appears on the Avamar system must be in sync with Multiple Systems Management. 2. Find out the Multiple Systems Management DNS hostname and domain name. 3. Check if Avamar is on the same domain. If Avamar is on the same domain, ensure that the DNS entry and search domain values are set. If Avamar is on a different domain, add the Multiple Systems Management DNS entry through the yast2 command, or by editing the /etc/resolv.conf file on Avamar. 4. To check whether Avamar can resolve the Multiple Systems Management Hostname and IP address, use the nslookup command. Run: nslookup<msm_hostname> Run: nslookup<msm_ip_address> 5. Check whether the Hostname resolves correctly. If the Hostname resolves correctly, the network setup is correctly configured. If the Hostname does not resolve correctly, check all previously entered values. Hotfixes Depending on the Avamar version in the environment, the following Avamar hotfixes must be installed before deploying Multiple Systems Management: In Avamar 7.3.1 environments, ensure that the 270536 hotfix is installed. In Avamar 7.3.0 environments, ensure that the 269427 hotfix is installed. Note The 269427 hotfix is not customer installable. If the 269427 hotfix is not installed, contact EMC support for assistance with the installation. In Avamar 7.2.1 environments, ensure that the 274741 hotfix is installed. 18 EMC Multiple Systems Management 1.0 Getting Started Guide

Installation Note Deployment methods The 274741 hotfix is not customer installable. If the 274741 hotfix is not installed, contact EMC support for assistance with the installation. To view the hotfixes that are installed in an environment, use one of the following methods: In the Avamar Installation Manager, view the History tab. Use the mccli version show command. The Avamar Management Console Command Line Interface (MCCLI) Programmer Guide includes information about the mccli version show command. The Avamar Administration Guide includes information about how to install hotfixes. The hotfix readme file includes additional details about the hotfix installation. There are two methods that can be used to deploy Multiple Systems Management: Multiple Systems Management OVA Standalone installer Deploying the Multiple Systems Management OVA Deploy the Multiple Systems Management OVA on a VMware vsphere client. Refer to the VMware documentation for specific information regarding how to deploy an OVF template. Before you begin Ensure that the following system requirements are met: Properly setup the DNS. This ensures that the Avamar is able to resolve the Multiple Systems Management hostname and FQDN name. VMware vcenter with VMware ESX 5.5 or later. You must deploy Multiple Systems Management OVA using vcenter. The Multiple Systems Management OVA does not deploy directly to the ESXi server. For environments with 25 Avamars or less, 4 CPUs and 8 GB of RAM are required. For environments with greater than 25 Avamars, 8 CPUs and 16 GB of RAM are required. This configuration supports up to 200 Avamars. 500 GB of disk space. FQDN, IP, Netmask, Gateway, DNS, and Timezone are configured. The FQDN must resolve to the IP address. The environment must use static network settings. 1. Log in to the vsphere client. 2. Select a server. 3. On the Network Properties window, specify the following information, and then click Next: a. In the Network IP address field, specify the IPv4 address or IPv6 address for the virtual appliance. Deployment methods 19

Installation Note For IPv6 addresses, use the nslookup command to resolve the hostname of the appliance to the IP address. Specify the IPv6 address in the format that appears in the nslookup output. b. In the Default Gateway field, specify the default gateway IPv4 address or IPv6 address that you want the virtual appliance to use. c. In the Network Netmask/Prefix field, when you use IPv4 addressing, specify the netmask of the virtual appliance. When you use IPv6 addressing specify the prefix length. d. In the DNS field, specify up to three domain name servers for this virtual appliance, separated by commas. e. In the FQDN field, specify the Fully Qualified Domain Name (FQDN) for the virtual appliance. Note Ensure that you correctly configure host name resolution for the name of the appliance. Forward and reverse lookups must succeed. 4. Deploy an OVF template: a. Accept the end user license agreement. b. Select the virtual disk format. When selecting the virtual disk format, the Thick Provision Lazy Zeroed option is recommended. Note The Thick Provision Eager Zeroed option yields the best performance but also takes the most time to initialize. Thick provisioning does not fill the drive unless eager zeroed is selected. If thick provisioning is selected, the storage capacity for the entire virtual disk is allocated on the data store at virtual disk create time. With Thin provisioning, the capacity on the data store is allocated to the virtual disk as required, up to the file size of the virtual disk. c. Specify all network properties. Deploying with the standalone installer The standalone installer allows you to manage an OS, or provide an SLES OS deployed in a physical or virtual server. Before you begin Ensure that the following system requirements are met: For environments with 25 data protection resources or less, 4 CPUs and 8 GB of RAM are required. For environments with greater than 25 data protection resources, 8 CPUs and 16 GB of RAM are required. This configuration supports up to 200 data protection resources. 20 EMC Multiple Systems Management 1.0 Getting Started Guide

Installation 500 GB of disk space. FQDN, IP, Netmask, Gateway, DNS, NTP, and Timezone are configured. The environment must use static network settings. Operating system security and software updates are installed. SLES12SP1, including java-1_8_0-openjdk, and postgresql94-server packages. SLES server is dedicated to Multiple Systems Management and is not sharing resources with other applications. 1. Verify that the network information of the host where you are about to deploy Multiple Systems Management is configured correctly: a. From a remote host, ping the FQDN of the host where you are about to deploy Multiple Systems Management. The FQDN must show the assigned static IP address. b. Within the host where you are about to deploy Multiple Systems Management, to verify the static network settings and the existence of a resolvable DNS name, type the following command: hostname -f 2. To verify that the java-1_8_0-openjdk, and postgresql94-server packages are configured correctly, type the following commands: * rpm -qa grep postgresql94-server * rpm -qa grep java-1_8_0-openjdk 3. Copy the installation package to the host where you are about to deploy Multiple Systems Management. 4. Ensure that you are using the root account. 5. To run the installer program, type the following command: java -jar emc-msm-xxx.jar Verifying the deployment When the deployment is complete, to verify that Multiple Systems Management was deployed successfully, perform the following steps. Before you begin If an OVA installation was performed, ensure that the virtual machine where the OVA file was deployed is powered on. 1. Open a browser, and then type the following in the Address field: https://<fqdn> Verifying the deployment 21

Installation Access control The Login page appears. 2. To log in to the UI, type the username and password in the respective fields. The default password for an admin or msm user account is changeme. The admin user account is only used to log into the Multiple Systems Management user interface. Access control settings provide protection of resources against unauthorized access. Default accounts The following table includes the Multiple Systems Management default account and password. Table 3 Default account names and passwords User account Password Description web and browser admin Linux OS admin root The admin password is set when Multiple Systems Management is installed. The account is admin and the default password is changeme. The admin password is set when Multiple Systems Management is installed. The account is msm and the default password is changeme. This user account is for an OVA/VM installation only. The default password is changeme. The default user for Multiple Systems Management web application administration. The default user for Multiple Systems Management web application administration. Only msm can log in using secure shell. After 5 failed login attempts, the msm account will lock out. Root operation system account. NOTICE It is recommended that you change the default passwords after completing the Multiple Systems Management installation. You can use the UNIX passwd command to change the password for the msm and root accounts. Only the msm account can log in using a secure shell (ssh). 22 EMC Multiple Systems Management 1.0 Getting Started Guide

Installation User authorization The admin and msm users are the authorized accounts for Multiple Systems Management. Installation directory structure Port information The installation directory structure is the same whether you deploy the standalone installer or the OVA. Directory structure details include: All Multiple Systems Management specific packages are installed under /usr/ local/msm/lib. Each package has its own subdirectory. For example, setup, monitor, and concerto. Each package has similar structures. For example, bin and conf. The /usr/local/msm/bin directory includes scripts to start or stop Multiple Systems Management services. To start or stop an individual Multiple Systems Management service, use the systemctl command. The /var/log/msm directory hosts all Multiple Systems Management related logs including Nginx, MongoDB, and RabbitMQ. The postgres log resides in the /var/lib/msm/postgres directory. The /var/lib/msm directory hosts all Multiple Systems Management generated data which consists of PostgreSQL, MongoDB, and RabbitMQ. The ports listed in the following table are the Multiple Systems Management default ports. Table 4 Default ports using the TCP protocol Component Port Additional information RabbitMQ 5671 The source is an Avamar adaptor. Port for accepting SSL RabbitMQ connections. Nginx 443 Avamar 7.3.x or later uses this port for registration purposes. Nginx 80 Avamar 7.2.x uses this port for registration purposes. User authorization 23

Installation System services The following table includes information about Multiple Systems Management services. Table 5 System services Name RPM systemd service name Additional information RabbitMQ erlang erlang-epmd rabbitmq-server rabbitmq-server.service Message Bus. Used by the MSM Monitor and Concerto. MongoDB mongodb-org-tools mongodb-org-shell mongodb-org-server mongod.service Database that is used by the MSM UI and MSM Monitor. Nginx nginx nginx.service http or https reverse proxy. MSM Setup msm-setup Not applicable Creates the initial SSL certificate and the runtime user msm. MSM Concerto msm-concerto msm-concerto.service Tomcat and Concerto web application. MSM UI msm-ui msm-ui.service Node.js and MSM UI. MSM Monitor msm-monitor msm-monitor.service MSM Monitor services. PostgreSQL postgresql-server postgresql.service Used by Concerto. Certificate management Consider the following when managing certificates: Certificates are used for secure http access (https) By default, Multiple Systems Management generates a default SSL self-signed certificate in the following location: /var/lib/msm/webcerts The self-signed certificate is sufficient to establish an encrypted channel between web browsers and the server. The self-signed certificate cannot be used for authentication. Consider company policies when creating certificates. You can create a self-sign certificate. You can create a certificate that is signed by trusted certificate authority (CA) vendor. 24 EMC Multiple Systems Management 1.0 Getting Started Guide

Installation Generating a self-sign certificate Use the following procedure to create a new private key and self-sign certificate. 1. To connect to the MSM server as a msm user, run the following command: ssh msm@server 2. To change to the root user, run the following command: su - 3. To change the directory to /var/lib/msm/webcerts, run the following command: cd /var/lib/msm/webcerts 4. To generate a new certificate, run the following command: openssl req -newkey rsa:2048 -sha256 -x509 -keyout privatekey.pem -out cert.pem -nodes -days 3650 5. Set the owner and group of the new certificate files to the following: chown msm *.pem 6. Restart Nginx. systemctl restart nginx 7. To verify the new self-sign certificate, browse Multiple Systems Management. Generating a Certificate Signing Request (CSR) Use the following procedure to generate a trusted certificate. 1. To connect to the MSM server as an msm user, run the following command: ssh msm@server 2. To change to the root user, run the following command: su - Generating a self-sign certificate 25

Installation 3. To change the directory to /var/lib/msm/webcerts, run the following command: cd /var/lib/msm/webcerts 4. To generate a new certificate using the private key at the self-sign step, run the following command: openssl req -newkey rsa:2048 -sha256 -key private-key.pem - out cert.csr 5. Send the cert.csr to a certificate authority (CA) vendor. 6. Replace the current cert.pem file to the certificate received from the CA vendor. 7. Restart Nginx. systemctl restart nginx Configuring LDAP 8. To verify the new certificate, browse Multiple Systems Management. Learn about LDAP requirements and configuration procedures. Note OpenLDAP is supported. Active Directory and role-based-access-control (RBAC) are not supported. Adding LDAP to Multiple Systems Management 1. Type the following command: ssh -l USERNAME MSMSERVER 2. To switch to the root user, type the following command: su - 3. Edit the following file: /var/lib/msm/concerto/conf/restserver.properties 4. Enter values for LDAP. For example: # specifying total ldap size ldap.servers.size=1 26 EMC Multiple Systems Management 1.0 Getting Started Guide

Installation # LDAP1 info ldap.server.1=ldap://vm-qa-0135.asl.lab.emc.com:389/cn=admin \,dc=asl\,dc=lab\,dc=emc\,dc=com ldap.anonymous.allowed.1=false ldap.admin.dn.1=uid=msmteam\,ou=msmteam\,cn=admin\,dc=asl \,dc=lab\,dc=emc\,dc=com ldap.admin.password.1=changeme ldap.user.search.dn.filter.1=(uid={0}) ldap.user.search.base.1=ou=msmteam 5. Save, and then close the file. 6. To restart Multiple Systems Management, run the following command: systemctl restart msm-concerto.service LDAP requirements Wait for concerto to start, and then log in with the username and password for the LDAP user account. 7. Log in to the Multiple Systems Management user interface. For example: https://msm_fqdn where MSM_fqdn is the Multiple Systems Management fully qualified domain name. This section outlines LDAP requirements. Table 6 LDAP requirements Property Valid Value Description ldap.servers.size 0, 1, 2,..., n Number of LDAP authentication providers. For every LDAP used, the following group of related properties must be repeated and set. Property names should be suffixed with LDAP number.1,.2, and so on. ldap.server.1 LDAP server URL in the form of ldap:// hostname:port/base_dn. Commas need to to be escaped with a back slash '\'. ldap.anonymous.allowed.1 true, false Whether anonymous access is allowed. ldap.admin.dn.1 ldap.admin.password.1 User ID. If anonymous access is not allowed, user credential must be specified for LDAP binding. Password. If anonymous access is not allowed, user credential must be specified for LDAP binding. ldap.user.search.dn.filter.1 Search filter as defined in RFC 2254. ldap.user.search.base.1 Context name to search in, relative to the base dn of the LDAP server. Empty string is allowed to signify full LDAP search. More LDAP requirements 27

Installation Table 6 LDAP requirements (continued) Property Valid Value Description efficient searches can be achieved, for example, to narrow down the search space, use ou=users. 28 EMC Multiple Systems Management 1.0 Getting Started Guide

CHAPTER 3 Getting Started with Multiple Systems Management Administration Learn about how to get started with Multiple Systems Management Administration. Topics include: Logging in to Multiple Systems Management...30 User interface overview... 30 Getting Started with Multiple Systems Management Administration 29

Getting Started with Multiple Systems Management Administration Logging in to Multiple Systems Management 1. In a browser address bar, type https://, and then the FQDN or IP address of the Multiple Systems Management server. 2. Type a username. 3. Type a password. 4. (Optional) To view the terms and conditions, click Terms and Conditions. 5. Click Login. User interface overview You are required to change the password the first time you log in. The Multiple Systems Management user interface includes the following core components: Page Header The page header includes the main menu, breadcrumb information, the admin menu, and provides access to the Multiple Systems Management online help. Dashboard The dashboard is a customizable interface which displays various widgets. For more information about the Multiple Systems Management Dashboard, refer to the Dashboard chapter. Configuration pages Systems and groups are added or deleted through the configuration pages. For more information about the Configuration pages, refer to the Configuration chapter. Monitoring pages The monitoring pages include option for working with Data Domains, system information, Clients, Jobs, Alerts, and Events. For more information about the Monitoring pages, refer to the chapter on Monitoring Systems. Management pages The managing pages include viewing systems, policies, retentions, schedules, datasets, and resetting passwords. For more information about the Management pages, refer to the chapter on Managing Systems. Main menu button Use the Main Menu to: Browse to the Dashboard. Browse to the Monitoring UI. Browse to the Management UI. Browse to the Configuration UI. Figure 7 Main menu button 30 EMC Multiple Systems Management 1.0 Getting Started Guide

Getting Started with Multiple Systems Management Administration Admin menu Use the admin menu to: Change a password. View information about MSM. Log out of the application. Figure 8 Admin menu Changing the Multiple Systems Management login password 1. In the page header, click the admin menu. Figure 9 Admin menu Viewing About MSM information 2. Select Change Password. The Change Password dialog box appears. 3. Type the old password. 4. Type the new password. Ensure that the new password meets the password criteria. 5. Retype the new password. 6. Click Change Password. You can view Multiple Systems Management version information in the About Multiple System Management page. 1. In the page header, click the admin menu. Figure 10 Admin menu 2. Select About MSM. The About Multiple System Management page appears. 3. To return to the dashboard, click Ok. Admin menu 31

Getting Started with Multiple Systems Management Administration Logging out of Multiple Systems Management 1. In the page header, click the admin menu. Figure 11 Admin menu 2. Select logout. The Multiple Systems Management UI closes. Accessing the Multiple Systems Management online help To access the Multiple Systems Management online help, click the following button: Figure 12 Help button Filtering Filtering allows you to customize the information that appears in Multiple Systems Management. Figure 13 Filter button Filters are stored in a browser's local storage. If you use the same browser each time you use Multiple Systems Management, you do not lose the filter settings that you specified in a previous session. Monitoring data is stored for 90 days. The All Time option is limited to data stored within the last 90 days. The following table includes information about the different filtering options that are available. Table 7 Filtering options Page Filter Options Additional information Clients OS Types Choice: All OS Types (default) Windows Allows you to filter on the operating system type. Linux MSM Tasks Time Choice: All Time (default) These are time filters used to view MSM 32 EMC Multiple Systems Management 1.0 Getting Started Guide

Getting Started with Multiple Systems Management Administration Table 7 Filtering options (continued) Page Filter Options Additional information Today This Week tasks within a certain time range. This Month Custom Date: On Not On Before After In The Range Not In The Range Jobs Type Choice: All (default) Backups View backup jobs, replication jobs, or all jobs. States Replications Choice: All (default) Completed Completed with Exceptions Running TimedOut Failed Halted Never Run Unknown Allow selection of one or more states to filter on. Alerts Time Choice: All Time (default) Last Hour Last 6 Hours These are time filters used to view system alerts within a certain time range. Today Last 3 Days This Week This Month Custom Date: Filtering 33

Getting Started with Multiple Systems Management Administration Table 7 Filtering options (continued) Page Filter Options Additional information On Not On Before After In The Range Not In The Range Systems Severity Choice: All Systems Avamar Data Domain Choice: All (default) Error Warning View system alerts from all systems, Avamar, or Data Domain. Select whether to see all alerts, warnings only, or errors only. Events Time Choice: All Time (default) Last Hour Last 6 Hours These are time filters used to view system events within a certain time range. System Type Today Last 3 Days This Week This Month Custom Date: On Choice: Not On Before After In The Range Not In The Range All Systems (default) Avamar View system events from all systems, Avamar, or Data Domain. 34 EMC Multiple Systems Management 1.0 Getting Started Guide

Getting Started with Multiple Systems Management Administration Table 7 Filtering options (continued) Page Filter Options Additional information Data Domain Severity Choice: All Error Warning Information Audit Allows you to filter on the severity type. Retentions Expiration Type Choice: All Types (default) Never Filter by expiration type. Computed Advanced Exact Schedules Type Choice: All Types (default) Daily Filter by schedule frequency type. Weekly Monthly On Demand Sorting You can sort information that is presented in lists within the user interface in ascending or descending order. To sort information in ascending order, click the following button: Figure 14 Sort in ascending order button To sort information in descending order, click the following button: Figure 15 Sort in descending order button Sorting 35

Getting Started with Multiple Systems Management Administration 36 EMC Multiple Systems Management 1.0 Getting Started Guide

CHAPTER 4 Dashboard Learn about how to get started with the Multiple Systems Management dashboard. Note The EMC Multiple Systems Management Administration Guide includes complete information about all Multiple Systems Management dashboard features. Topics include: Dashboard overview...38 Dashboard 37

Dashboard Dashboard overview The Multiple Systems Management dashboard provides at a glance insight into operational behavior. The following are the default list of widgets that are available in the dashboard: Backups Replications Systems by Usage Alerts Alerts by System Avamar Health Backups and Replications widgets Avamar Health widget The Backups and Replications widgets provide a high-level status for backup and replication jobs. For both Backups, and Replications, the following states are displayed for jobs: Failed Success Running Completed with Exceptions Does not include Replications. Total percentage for Success Rate Total calculation since midnight. To view information about jobs, click View Jobs. The Avamar Health quadrant of the Multiple Systems Management UI dashboard provides a high level status for a maximum of 99 systems. Systems are ranked based on the percent of capacity used. The Avamar Health quadrant displays the status for the following fields: Used (%). Checkpoint The checkpoint is used in the event of a system failure where the system can be rolled back to a specific checkpoint. Validated The validation checks the integrity of the Checkpoint. Garbage Collection (GC). Note A warning icon will display if a Checkpoint, Checkpoint Validation, or Garbage Collection has not been received in the last 24 hours. To view details, click View Systems. Servers in the Health quadrant are sorted according to the following criteria, in order of priority: 38 EMC Multiple Systems Management 1.0 Getting Started Guide

Dashboard Servers that have exceeded the configured warning threshold. All servers exceeding the configured warning threshold (default 80%) are sorted in order of the most full to the least full. Servers with failed or unknown HFS status. Servers with failed or unknown HFS validation status. Servers with failed or unknown GC status. The remaining servers are sorted from the most full to the least full. Alerts Today and Alerts by System widgets Systems by Usage widget The Alerts Today widget provides a total for all errors and warnings generated in Multiple Systems Management since midnight for all Avamar and Data Domain systems registered to the Multiple Systems Management server. The Alerts by System widget displays the five systems that have generated the most errors since midnight. To view more information about Alerts, click View Alerts. The Systems by Usage widget provides a high-level view for a maximum of 99 systems with the highest capacity. Click View Systems for more information. Alerts Today and Alerts by System widgets 39

Dashboard 40 EMC Multiple Systems Management 1.0 Getting Started Guide

CHAPTER 5 Configuration Learn about how to configure managed systems with Multiple Systems Management. Note The EMC Multiple Systems Management Administration Guide includes complete information about configuring systems in Multiple Systems Management. Topics include: Adding a group... 42 Adding a system...42 Importing systems...43 Configuration 41

Configuration Adding a group To organize systems, you can use groups. 1. To view the Main Menu, click the following button: Figure 16 Main Menu button 2. Click Configuration. The Configure Managed Systems page appears. 3. Click Add Group. 4. Specify a group name. 5. Click Add. 6. Click Apply. The Confirm configuration changes dialog box appears and displays the following: Are you sure you want to apply these changes? 7. Click OK. The new group appears in the Managed Systems list. Note Additional changes are not allowed if a configuration change is in progress. Adding a system 1. To view the Main Menu, click the following button: Figure 17 Main Menu button 2. Click Configuration. The Configure Managed Systems page appears. 3. Click Add System. 4. Specify the following system details: System name. Use the Avamar system's fully qualified domain name (FQDN). 42 EMC Multiple Systems Management 1.0 Getting Started Guide

Configuration Username. The username is MCUser. Password. You have to retype this password. The password is the MCUser's password. (Optional) Avamar port. The default Avamar port is 9443. OS root password. You have to retype this password. 5. Select the Group where you want the system added, and then click Add. Systems cannot be moved between Groups. If a system needs to be added to a different Group, the system needs to be deleted from the existing Group, and then added to the new Group. 6. Click Apply. The Confirm configuration changes dialog box appears and displays the following: Are you sure you want to apply these changes? 7. Click OK. The Systems page appears. A notification dialog box also appears that indicates the request is in progress. You can view the status of a request in the Jobs page. If the request is successful, the new system appears in the list in the Systems page. Note If multiple systems are being added, systems are added in sets of five systems. Requests to add systems may take 10 minutes or more to complete. Additional changes are not allowed if a configuration change is in progress. A maximum of 100 systems can be added simultaneously. Multiple Systems Management only supports 200 total systems. Importing systems You can bulk upload systems into Multiple Systems Management. Note If multiple systems are being added, systems are added in sets of five systems. Requests to add systems may take 10 minutes or more to complete. Additional changes are not allowed when a configuration change is in progress. A maximum of 100 systems can be added simultaneously. Multiple Systems Management only supports 200 total systems. 1. To view the Main Menu, click the following button: Figure 18 Main Menu button Importing systems 43

Configuration 2. Click Configuration. The Configure Managed Systems page appears. 3. Click Import. The Import Managed Systems page appears. 4. Click Load Sample Template or Browse: If you clicked Load Sample Template, manually modify the JSON file that appears. If you clicked Browse, specify a JSON file name, and then click Open. 5. Click Import. The new systems to be added appear. 6. Click Apply. The Confirm conifguration changes dialog box appears and displays the following: Are you sure you want to apply these changes? 7. Click OK. The Systems page appears. A notification dialog box also appears that indicates the request is in progress. You can view the status of a request in the Jobs page. If the request is successful, the new system appears on the list in the Systems page. 44 EMC Multiple Systems Management 1.0 Getting Started Guide

CHAPTER 6 Monitoring Systems Learn about how to monitor systems with Multiple Systems Management. Note The EMC Multiple Systems Management Administration Guide includes complete information about all Multiple Systems Management monitoring features. Topics include: Note Monitoring data may take up to 15 minutes to appear after a system is added. Adding a Data Domain System... 46 System Information...46 Clients...47 MSM Tasks... 48 Jobs... 49 Alerts... 49 Events... 51 Monitoring Systems 45

Monitoring Systems Adding a Data Domain System 1. To view the Main Menu, click the following button: Figure 19 Main Menu button System Information 2. Click Monitoring. The Monitoring page appears. 3. Click Configure Data Domains. 4. Specify details in the following fields: System Name/IP Username Password 5. Click Save. Viewing System Information System information in Multiple Systems Management refers to information about the selected status for an individual Avamar system. The following functions occur in system information: Reactivate Monitoring Attempts to reconnect the event mesaging connection between Avamar and Multiple Systems Management systems. Import Imports a new copy of the Avamar system information into Multiple Systems Management. Synchronize Folders Used to synchronize Multiple Systems Management folders with any new changes made after a system has been imported into Multiple Systems Management. 1. To view the Main Menu, click the following button: Figure 20 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Select a system or folder from the Managed or Monitored systems list. 46 EMC Multiple Systems Management 1.0 Getting Started Guide

Monitoring Systems Activating monitoring 4. Click the System Information tab. The System Information page appears. 1. To view the Main Menu, click the following button: Figure 21 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Select a system from the Managed Systems list. 4. Click the System Information tab. The System Information page appears. 5. To monitor the system, click Activate Monitoring. The Activate Monitoring dialog box appears. 6. To activate monitoring, type the password, and then click Activate. A dialog box appears indicating that the request is in progress. To view the progress of the request, click View Progress. Clients Viewing clients Clients in Multiple Systems Management are the physical and virtual machine Avamar clients. These clients have been added to an Avamar to be backed up. 1. To view the Main Menu, click the following button: Figure 22 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Select a system or folder from the list. 4. Click the Clients tab. The Clients page appears and displays a list of clients. Activating monitoring 47

Monitoring Systems Viewing client backups 1. To view the Main Menu, click the following button: Figure 23 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Select a system or folder from the list. 4. Click the Clients tab. The Clients page appears. 5. Select a client in the list. The Client Backups panel appears and displays a list of backups for the selected client. MSM Tasks MSM Tasks in Multiple Systems Management are tasks that were initiated through the MSM user interface. Viewing MSM tasks 1. To view the Main Menu, click the following button: Figure 24 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Click MSM Tasks. The MSM Tasks page appears and displays a list of tasks. 4. (Optional) To view detailed information about a task, select the task. To view the parameters for a task, click Show Parameters. 48 EMC Multiple Systems Management 1.0 Getting Started Guide

Monitoring Systems Jobs Viewing Jobs Jobs in Multiple Systems Management are backup and replication Avamar jobs that Multiple Systems Management is monitoring. All jobs are included, not just jobs that are initiated or configured in Multiple Systems Management. The following types of job information are available for you to view: The status of Multiple Systems Management jobs. The status of backup operations, and replication jobs for Avamar nodes. 1. To view the Main Menu, click the following button: Figure 25 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Select Jobs. The Jobs page appears The Jobs page displays information about the status of backup operations, and replication jobs for Avamar nodes. To view only the details for a specific Avamar system, click the specific Avamar system in the system list. Note Avamar monitors Data Domain backup and replication jobs. In Multiple Systems Management, Data Domain jobs are displayed as Avamar, however the storage that is attached is displayed as Data Domain. Alerts Viewing Alerts Alerts in Multiple Systems Management are all of the alerts from the monitored Avamar, Data Domain, and Multiple Systems Management system. You can view Alerts and Alert details for Avamar nodes and Data Domain systems configured for Multiple Systems Management. The following alert information details are available for you to view: Error or Warning alert Category Jobs 49

Monitoring Systems System Message Repeated Alert Details include the number of times the alert is repeated to avoid displaying the same alert numerous times. 1. To view the Main Menu, click the following button: Figure 26 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Select the Alerts tab. 4. (Optional) To view the details for an alert, click an alert. A panel will appear with the following information: System Alert Detail name System Time Repeated Host Category Message Alerts columns Alert categories The following list describes the columns in Alerts and their function: Category Lists the category of the alert. For example, Error or Warning. System Lists the system on which the alert occurred. Message Lists the specific Error, Warning, or System Alert message that describes the alert. Multiple occurrences of the same message are combined. Repeated Displays the number of times that the same message has occurred for the system. The following list describes the categories for system alerts: Warning An alert that might be informational or require user intervention. Error An alert that requires immediate user intervention to avoid system component failure or data loss. 50 EMC Multiple Systems Management 1.0 Getting Started Guide

Monitoring Systems Events Viewing Events Events in Multiple Systems Management are Avamar system generated events that Multiple Systems Management monitors. You can view Events in Multiple Systems Management. This section explains how to access Events: 1. To view the Main Menu, click the following button: Figure 27 Main Menu button 2. Click Monitoring. The Monitoring page appears. 3. Select the Events tab. Events 51

Monitoring Systems 52 EMC Multiple Systems Management 1.0 Getting Started Guide

CHAPTER 7 Managing Systems Learn about how to manage systems with Multiple Systems Management. Note The EMC Multiple Systems Management Administration Guide includes complete information about all management features. Topics include: Viewing Systems...54 Policies... 55 Retentions... 58 Schedules... 59 Datasets...60 Reset passwords... 61 Managing Systems 53