Emc Networker: Virtual Edition Deployment Guide
Emc Networker: Virtual Edition Deployment Guide
Version 9.1
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
Figures 5
Preface 7
Chapter 2 Maintenance 31
Password maintenance...............................................................................32
Review password policies.............................................................. 32
Modify passwords..........................................................................33
Change the storage disk configuration....................................................... 33
Chapter 3 Troubleshooting 39
Enable SSH for root................................................................................... 40
NVE installation log files............................................................................. 40
As part of an effort to improve its product lines, EMC periodically releases revisions of
its software and hardware. Therefore, some functions 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
properly 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 describes how to set up NetWorker Virtual Edition in a NetWorker
environment.
Audience
This guide is part of the NetWorker documentation set, and is intended for use by
system administrators during the installation and setup of the NetWorker software.
Revision history
The following table presents the revision history of this document.
02 February 6, 2017 Second release of this document for EMC NetWorker 9.1.
Updates include:
l Preconfiguration checklist for information required before
deployment.
l Appendix with a blank preconfiguration checklist.
l Corrections to the "Configuring sendmail" section in the
"Deployment" chapter.
01 December 22, First release of this document for EMC NetWorker 9.1.
2016
Related documentation
The NetWorker documentation set includes the following publications, available on
EMC Online Support:
l EMC NetWorker Online Software Compatibility Matrix
Provides a list of client, server, and storage node operating systems supported by
the EMC information protection software versions. You can access the matrix at
http://compatibilityguide.emc.com:8080/CompGuideApp/.
NOTICE
Note
Typographical conventions
EMC uses the following type style conventions in this document:
Italic Used for full titles of publications that are referenced in text
Monospace Used for:
l System code
l System output, such as an error message or script
l Pathnames, file names, prompts, and syntax
l Commands and options
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.
Your comments
Your suggestions help to improve the accuracy, organization, and overall quality of the
user publications. Send your opinions of this document to
[email protected].
Note
You cannot update a NetWorker Server that resides on a physical host to an NVE
appliance.
Note
NVE does not support data migration from another instance of NetWorker.
System requirements
Networker Virtual Edition (NVE) supports the following VMware versions:
Memory 8 GB
Note
After the initial deployment, if you configure the virtual disks for the thick provision
eager zeroed, you will get better initial performance because the first write to the disk
will require fewer operations.
Note
A virtual machine that runs NVE aggressively uses disk I/O and is almost never idle.
VMware recommendations for appropriate resources for high-performance database
virtual machines are generally applicable to an NVE virtual machine. In particular, a
storage pool that is allocated from a group of dedicated physical disks in a RAID 1
(mirror) or RAID 10 (combines RAID 0 with RAID 1) configuration provides the best
performance.
Preconfiguration checklist
Before you deploy the NVE appliance, gather the following information.
Completed? Information
Network configuration details:
□ l IP address of the default gateway:
□ l DNS server:
□ l NVE IP address:
□ l NVE FQDN:
□ l Netmask:
□ l SMTP mail relay host (to send notifications):
Note
The OVA package for NVE does not support dual stack and IPv6, use
IPv4.
Ensure that the following firewall ports are open between the NetWorker
Server and the :
□
l 27000
□
l 27010
□
l 51000
Preconfiguration checklist 13
Deployment and Update
Completed? Information
The FQDN configuration is correct when the nslookup command returns the
correct IP address of the NVE.
3. To perform a reverse DNS lookup of the IP address of the vCenter server, type
the following command:
nslookup vCenter_FQDN DNS_Server_IP_address
The FQDN configuration is correct when the nslookup command returns the
correct IP address of the vCenter Server.
Results
If the nslookup commands return the proper information, close the command
prompt. If the nslookup commands do not return the correct information, before you
install NVE, resolve the DNS configuration.
Note
The following procedure and screen shots are specific to vCenter 6.0. Other vCenter
server versions might display the information in the deployment screens differently.
Procedure
1. Download the NVE OVA package from http://support.emc.com.
2. Connect to the vCenter server, by using the VMware vSphere Web Client. On
the Login screen, specify a user account that has administrative rights.
3. In the vCenter server console, browse to vCenter > vCenter server.
4. Right-click the vCenter server that manages the NVE appliance and select
Deploy OVF template.
The Deploy OVF Template wizard appears.
5. On the Select source page, select one of the following options, and then click
Next.
l URL—Type the path to the OVA file.
l Local file—Click Browse, and then search for the OVA file.
The following figure provides an example of the Select source page.
Figure 1 Select source page
6. On the Review details page, verify the details about the template, and then
click Next.
The following figure provides an example of the Review details page.
7. On the End User License Agreement page, if you agree to the license terms,
click Accept, and then click Next.
The following figure provides an example of the Accept License Agreements
page.
Figure 3 End User License Agreements page
8. On the Select a name and folder page page, type a descriptive name for the
NVE, select the inventory location, and then click Next.
The following figure provides an example of the Select a name and folder page
with a Datacenter named Burlington IDD lab selected.
9. On the Select a resource page, select the ESXi host, cluster, vApp, or resource
pool on which to run the deployed template, and then click Next.
The following figure provides an example of the Select a resource page with an
ESXi host selected.
Figure 5 Select a resource page
10. On the Select storage page, perform the following configuration tasks:
a. In the Select virtual disk format field, leave the default selection Thick
Provisioned Lazy Zeroed.
Thin provisioning is not supported with NVE.
11. On the Setup networks page, select the destination network, and then click
Next.
The following figure provides an example of the Setup networks page.
Figure 7 Setup networks page
12. On the Customize template page, perform the following configuration tasks,
and then click Next:
a. In the IP Address field, type the IPv4 address for the NVE appliance.
b. In the Netmask field, type the netmask address for the NVE appliance.
c. In the Default Gateway, type the address of the gateway host.
d. In the FQDN field, type the fully qualified domain name (FQDN) for the NVE
appliance.
e. In the DNS field, type the IP address of up to three DNS servers, which are
separated by commas.
The following figure provides an example of the Customize templates page.
13. On the Ready to complete page, confirm the deployment settings, select
Power on after deployment, and then click Finish.
The deployment might take several minutes. After the deployment completes,
the Recent tasks section of the vSphere Web Client displays the status of the
Deploy OVF template task as Completed. The following figure provides an
example of the Recent Tasks window after the deployment completes.
Figure 9 Recent Tasks
14. In the vCenter console, browse to the Hosts window and select the NVE virtual
machine. To monitor the progress of the installation, open the Virtual Console.
15. On the Summary tab, verify that the status for VMware Tools changes to
Running or Unmanaged.
The following figure provides an example of the Summary tab where the status
of VMware Tools appears as Running.
Note
The default password expiration policy on the NVE is once every 60 days. If the
password that you specify has expired, a messages similar to the following
appears:Error "Login failed. The password has already
expired or is within the warning period. You must change
and verify the password expiration date." To resolve this issue,
change the passwords assigned to the root and admin users. Modifying
passwords provides more information.
4. Click Login.
5. On the SW Releases tab, to the right of the NveConfig package, click Install.
The installation initialization begins. The initialization extracts files from the
package and prepares the environment for the installation. The process can
take a few minutes. After the initialization completes, the Installation Setup
page appears.
6. On the Authc Settings tab, specify the following attributes:
a. In the Tomcat KeyStore Password and Tomcat KeyStore password
(Confirm) fields, type a password for the keystore file that the NetWorker
Authentication Service uses to store data.
Specify a password that contains at least six characters and does not
contain dictionary words.
Note
You will use the administrator account to log in to the NMC Server.
c. Click Save.
7. (Optional) To install additional language packs, on the NetWorker Settings tab,
from the Value list, select the language pack, and then click Save.
8. On the Passwords tab, and specify the OS admin user and OS root user
passwords, and then click Save.
Ensure that the passwords comply with the following minimum requirements:
l Nine characters long
l One uppercase letter
l One lowercase letter
l One special character
l One numeric character
9. On the Server Settings tab, from the Value list, select the time zone for the
appliance, and then click Save.
10. (Optional) To configure Data Domain devices in the NetWorker datazone, on
the Data Domain Settings tab, select the box in the Value column, and then
specify the following configuration attributes:
a. In the Data Domain Address field, type the IP address or the FQDN of the
Data Domain system.
b. In the Data Domain Administrator Name field, type the username for a
Data Domain Administrator account.
c. In the Data Domain Administrator Password field, type the password for
the Data Domain Administrator account.
d. In the Data Domain Storage Folder field, type a new or existing name for a
folder that you want to use for DD Boost storage.
The installation process automatically creates a Storage Unit (SU) and folder
for the appliance in the hidden mount point folder, /data/col1. Do not
modify this folder structure, which all NetWorker server hosts use.
e. (Optional) To create a DD Boost account, select DDBoost create new login
account.
f. In the Data Domain Login field, type the account for the DD Boost user.
g. In the DDBoost Login Password field, type the password for the DD Boost
user that you specified in the Data Domain Login field.
Note
The DD Boost user that you specify must have an assigned role that is not
none.
h. In the DDBoost Login Password Confirm field, type the password for the
DD Boost user that you specified in the Data Domain Login field.
i. Click Save.
j. To specify the SNMP community string to monitor the Data Domain system,
on the NetWorker Settings tab, in the SNMP Community String field,
type the string value. Click Save.
The default SNMP Community String on a Data Domain system is Public.
11. (Optional) To install or upgrade the password hardening package, on the
Security Settings tab, select Show advanced settings, and then select the
box in the Value column. Click Save.
12. Click Continue.
The Installation Progress window appears and displays information about the
status of the installation actions. The Information Log pane displays messages
about the status of each task. To generate a file that contains each message,
click Export, and then select Excel to export the information to an Excel
spreadsheet or select PDF to export the information to a PDF file.
Results
The EMC NetWorker Installation Manager installs the NetWorker and NMC server
software on the NVE appliance.
After you finish
Install and configure the on a host in the datazone that the NetWorker server can
access. EMC NetWorker Licensing Guide provides more information.
Note
If you connect to the NMC server by using the IP address of the NMC server,
add an entry for the IP address in the following format:
http://ip_address:9000
5. Click OK.
6. In the Security Warning window, click Continue.
7. Click OK.
The following figure provides an example of the file association dialog box that
appears with the Mozilla Firefox browser.
Figure 11 Associating a jnlp file with Java (TM) web Start Launcher for Mozilla Firefox
Note
If the Start button does not appear but you see a warning message that states
that Java Runtime Environment cannot be detected, click the here hyperlink.
4. When you use Internet Explorer, if a security warning appears, select I accept
the risks and want to run this application, then click Run.
5. In the Log in page, specify the NetWorker Authentication Service administrator
username and password, and then click OK.
6. In the Licensing Agreement page, select Accept.
7. If you did not install a supported version of JRE on the host, then a prompt to
install JRE appears. Cancel the installation, install JRE, and then re-run the
installation.
8. In the Welcome to the NMC Server Configuration Wizard page, click Next.
9. In the Specify a list of managed NetWorker Servers page:
a. Specify the names of the NetWorker Servers that the NMC Server will
manage, one name per line.
Note
If the NMC Server is also the NetWorker Server, specify the name of the
NetWorker Server.
b. Leave the default options Capture Events and Gather Reporting Data
enabled.
Consider the following option:
l To allow the NMC Server to monitor and record alerts for events that occur
on the NetWorker Server, enable the Capture Events option.
l To allow the NMC Server to collect data about the NetWorker Server and
generate reports, enable the Gather Reporting Data option.
10. Click Finish. The installation starts the default web browser and connects to
the NMC server. The NetWorker Management Console and Getting Started
windows appear.
11. In the Enterprise window, right-click the NetWorker Server, and then select
Launch Application.
Note
If you do not specify any NetWorker Servers in the Specify a list of managed
NetWorker servers window, the NMC Enterprise window does not display any
NetWorker Servers. To add a host, right-click Enterprise in the left navigation
pane and click New > Host. The Add New Host wizard appears.
For example:
SENDMAIL_SMARTHOST="mysmtp_relay.corp.com"
5. Restart the sendmail service. At the command prompt, type the following
command:
service sendmail restart
When the test succeeds, output similar to the following example appears:
[email protected]... Connecting to [127.0.0.1] port 25 via
relay...
220 bu-idd-nve.iddlab.local ESMTP Sendmail 8.14.3/8.14.3/
SuSE Linux 0.8; Mon, 3 Oct 2016 10:36:58 -0400
>>> EHLO bu-idd-nve.iddlab.local
250-bu-idd-nve.iddlab.local Hello localhost.localdomain
[127.0.0.1], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH GSSAPI
250-DELIVERBY
250 HELP
>>> MAIL From:<[email protected]> SIZE=23
[email protected]
250 2.1.0 <[email protected]>... Sender ok
>>> RCPT To:<[email protected]>
>>> DATA
250 2.1.5 <[email protected]>... Recipient ok
354 Enter mail, end with "." on a line by itself
>>> .
250 2.0.0 u93Eaws2014693 Message accepted for delivery
[email protected]... Sent (u93Eaws2014693 Message accepted
for delivery)
Closing connection to [127.0.0.1]
>>> QUIT
221 2.0.0 bu-idd-nve.iddlab.local closing connection
6. Click OK.
7. Click OK.
9. Click OK.
l Password maintenance...................................................................................... 32
l Change the storage disk configuration............................................................... 33
Maintenance 31
Maintenance
Password maintenance
This section describes how to manage the root and admin passwords.
Note
If you connect by using the vSphere client to open a VM Console session, you
can log in to the NVE with the root or admin account. If you connect by using
SSH, you must log in as admin, and then use the su command to change to the
root account. The default password for the root and admin accounts is
changeme.
2. Use the chage command to determine the password expiration policy and the
scheduled expiration date for a user account.
For example, to determine the policy assigned to the root user account, and the
password expiration date, type:
chage -l root
Output similar to the following example appears:
Minimum: 1
Maximum: 60
Warning: 7
Inactive: -1
Last Change: Dec 07, 2015
Password Expires: Feb 05, 2016
Password Inactive: Never
Account Expires: Never
The following table provides more information about the chage output.
Option Definition
Minimum Defines the minimum numbers of days that
are allowed between password changes.
When this value is 0, a user can change the
password at any time.
Option Definition
account is locked out of the system. When
this value is -1, the inactive feature is disabled.
Last change Displays the date that the password was last
changed.
Account expires Defines the date that the user account will
expire.
Modify passwords
By default, the password expiration policy for the admin and root user accounts is 60
days.
Perform the following steps to change the passwords.
Procedure
1. Connect to the NVE, and perform the following tasks from a prompt.
Note
If you connect by using the vSphere client to open a VM Console session, you
can log in to the NVE with the root or admin account. If you connect by using
SSH, you must log in as admin, and then use the su command to change to the
root account. The default password for the root and admin accounts is
changeme.
2. Use the passwd command to change the password for an OS user account.
For example, to change the password for the root account, type:
passwd root
Modify passwords 33
Maintenance
/etc/init.d/networker status
Output similar to the following example appears when the daemons are not
running:
nsr_shutdown: There are currently no running NetWorker
processes.
d. Disable NetWorker:
chkconfig gst off networker off
b. Verify that the new /dev/sdc disk appears on the system, by typing the
following command:
ls /dev/sd*
Output similar to the following example appears:
/dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/
sda5 /dev/sda6 /dev/sda7 /dev/sda8 /dev/sdb /dev/
sdb1 /dev/sdc
e. Confirm that the new disk partition /dev/sdc1 appears, by typing the
following command:
ls /dev/sd*
Output similar to the following appears:
dev/sda /dev/sda1 /dev/sda2 /dev/sda3 /dev/sda4 /dev/
sda5 /dev/sda6 /dev/sda7 /dev/sda8 /dev/sdb /dev/
sdb1 /dev/sdc /dev/sdc1
i. Copy the contents from the old disk to the new disk, by typing the following
command:
cp -rfp /data01/* /tmpmnt/
j. Relabel the old and new disks, by typing the following command:
4. After the NVE power off completes, use the vSphere Web Client to perform the
following configuration tasks:
a. Right-click the appliance, and then select Edit Settings.
b. Hover over Hard disk 2, and then click X, do not select Delete files from
datastore. Click OK.
The following figure shows the Edit Settings screen, when the system
deletes the disk device.
Figure 12 Deleting a disk device
c. Right-click the virtual machine and select Power > Power On.
5. From the VM console of the NVE appliance, perform the following configuration
tasks:
a. Type mount and verify that disk /dev/sdc1 is mounted on /data01.
For example, the mount output would include the following line:
d. Start the NetWorker and NMC daemons, by typing the following commands:
e. Confirm that the NetWorker daemons have started, by typing the following
command: /etc/init.d/networker status
Note
Before you run this command, wait several minutes for the daemons to start.
Troubleshooting 39
Troubleshooting
vim /etc/ssh/sshd.config
4. In the Authentication section, remove the # from the beginning of the line
PermitRootLogIn yes
For example, the Authentication section will appear similar to the following:
#Authentication:
#LoginGraceTime 2m
PermitRootLogin yes
#StrictModes yes
#MaxAuthTries 6
#MaxSessions 10
Use the following checklist to record information the environment that you require to
deploy the NVE.
Completed? Information
Preconfiguration checklist 41
Preconfiguration checklist
Completed? Information