Loading...

Discover and Migrate - EMC Networker Clients - Advanced Options

Table of Contents

Components Created After Discovery

Components Created After Migration

Assigning Discovered Client Nodes to Additional Client Computer Groups

Advanced Discovery Options

Capture Metadata Using Decoupled Install

Scheduling Discovery Jobs

Related Reports

Components Created After Discovery

After the first full discovery process is complete, each EMC Networker component, such as clients, schedules, etc. is mapped to the appropriate CommCell entity. The following versions of EMC Networker are supported for these EMC Networker components:

EMC Networker Grouping

Description

Supported EMC Networker Versions*

Configuration

Clients, Groups, Save Sets, Schedules, Jobs, Directives.

7.2, 7.6, 7.6.1, 8.0, and 8.1 and for Fujitsu Networker 7.6.2, 7.6.3, and 7.5

Jobs

Backup information is migrated for CommCell reporting purposes.

7.2, 7.6, 7.6.1, 8.0, and 8.1 and for Fujitsu Networker 7.6.2, 7.6.3, and 7.5

*Windows, Linux, and Unix supported.

Configuration entities

The following table lists the EMC Networker configuration entities that are discovered and how they are mapped to CommCell entities.

emc networker component

notes

Hosts

Hosts are brought in initially as deconfigured clients and appear under Client Computer Group in the CommCell Console.

To display the discovered hosts, clear the Hide deconfigured clients option in the User Preferences dialog box.

All EMC Networker host computers that are discovered are, however, initially grouped into a single Client Computer Group based on the instance from which the discovery operation was run.

Clients

EMC Networker Modules:

  • Unix FS

    Including Linux, HP-UX, Aix, and Solaris

  • DB2, Informix, and Oracle
  • Windows

    Including Exchange Server and SQL Server

CommCell Agents:

  • Exchange Database
  • SQL Server
  • File System*
  • Oracle Database
  • File System*
  • Other External Agents

    *The File System iDataAgent used will correspond to the operating system (Windows or Unix) associated with the original EMC Networker group.

Save Set

Schedule

EMC Networker clients are migrated to CommCell subclients under a single backup set for each client.

The Save Sets of an EMC Networker client become the content of the subclient.

The Schedules of an EMC Networker client become subclient schedules.

Also, note that when previously merged policies are deleted from the EMC Networker server, the corresponding subclients are not automatically deleted from the CommServe during the next merge operation. Thus, any subclients associated with deleted policies must be manually removed from the CommServe.

Compression Directive

Compression directives become the properties of CommCell subclients.

Encryption Directive

Networker Encryption

AES-256-CFB

CommCell Encryption

AES (256 Bit)

Backup Schedules

Networker

  • Default—Full on Sunday
  • Full Every Friday
  • Full on 1st Friday of the Month
  • Full on 1st of the Month
  • Quarterly—Full on 1st Day of each Quarter
  • Consolidate Every Friday
  • Consolidate on the 1st Friday of the Month
  • Consolidate on the 1st of the Month
  • Consolidate  Quarterly—Full on 1st Day of each Quarter

CommCell

  • Full on Sunday
  • Full Every Friday
  • Full on 1st Friday of the Month
  • Full on 1st of the Month
  • Full on 1st Day of each Quarter
  • Synthetic Full Every Friday
  • Synthetic Full on the 1st Friday of the Month
  • Synthetic Full on the 1st of the Month
  • Synthetic Full on 1st Day of each Quarter

Schedule Periods

Networker

  • Recurring Week Days
  • Recurring Days of the Month

CommCell

  • Monthly
  • Monthly

Storage Nodes

EMC Networker Storage Nodes are migrated to CommCell MediaAgents with all configured properties.

Device Entities

The following table lists the EMC Networker device entities that are discovered and how they are mapped to CommCell entities.

emc networker component

notes

Libraries

Networker

  • Library
  • Drives
  • Volumes

CommCell

  • Library
  • Drives
  • Tapes

Devices

Networker

  • Disk Devices
  • Disk Name
  • Tape Device

CommCell

  • Disk Library
  • Disk Mount Path
  • Tape Drive

Media Entities

The following table lists the EMC Networker media entities that are discovered and how they are mapped to CommCell entities.

emc networker component

CommCell Component

Media Pool

Storage Policy

Volumes

Tape and Disk Volume

Components Created After Migration

The following table illustrates the CommCell Agents that are created for EMC Networker clients during the migration process:

emc networker Policy Type

Corresponding CommCell Agent

CommCell Agent As Displayed in the CommCell Console

Filesystem

Filesystem*

*The File System iDataAgent used will correspond to the operating system (Windows or Unix) associated with the original EMC Networker group.

File System iDataAgent

All other EMC Networker Policies

Other External Agent

Other External Agent

SQLServer

SQL Server

SQL Server

Assigning Discovered Client Nodes to Additional Client Computer Groups

All EMC Networker client nodes discovered are initially grouped into a single Client Computer Group based on the instance from which the discovery operation was run.

Prior to a discovery operation, you can assign discovered client nodes to additional client computer groups as follows:

  1. From the CommCell Console, right-click on the External Data Connector node, select an instance.
  2. Right-click the subclient for which you want to discover EMC Networker data and click Properties.
  3. From the General tab, specify a client computer group by:
    • In Select a Client Group for Discovered Clients, choose a client group from the pulldown menu.
    • Click Create New Group. Enter a name for the group, add clients to the group, and click OK.
  4. Click OK.

Advanced Discovery Options

By default, incremental discovery operations collect only client configuration information. However, several additional options are available if you require more comprehensive information about the discovered clients. The following sections describe the options available.

To configure these settings, perform the following steps:

  1. In the CommCell Browser, right-click the default subclient for which you want to discover EMC Networker data and click Discover.
  2. From the General tab of the Discovery Options dialog box, click Advanced.
  3. From the Advanced Discovery Options dialog box, select the desired options and click OK.

The following table describes the advanced operations available.

Option

Description

Force a Full Sync

This option forces a full discovery of all EMC Networker clients. This option should be used if you want to ensure that all the latest client information from the EMC Networker database is in sync with the CommServe database, especially in cases where significant change (such as the addition or removal of a large number of clients) has occurred.

Merge Information From a Specific File

This option populates the CommServe database with EMC Networker database information using a specified XML file. Use this option if you want to perform a full or incremental discovery of a EMC Networker database without the need to communicate with the EMC Networker Server itself.

Capture Metadata Using Decoupled Install

This method uses External Data Connector to populate EMC Networker Master Server database information into an XML file, which is then applied to an existing CommServe. This method does not require any direct connectivity between the EMC Networker Master Server and the CommServe, which is useful if deploying a new CommServe is not desirable in a particular environment.

This method consists of three phases:

  1. Install External Data Connector on the EMC Networker Master Server
  2. Create XML Files Containing EMC Networker Database Information
  3. Populate the XML Files in a CommServe

The following sections describe these phases in detail.

Install External Data Connector on the EMC Networker Master Server

External Data Connector must first be installed on the EMC Networker Master Server. If you want to perform this installation in the absence of CommServe software, create a decoupled custom package with the External Data Connector and then install the package on the EMC Networker Master Server. For instructions, see Custom Package.

Create an XML File Containing EMC Networker Database Information

Once External Data Connector is installed on the EMC Networker Master Server, a bundle file containing the EMC Networker database information must be created. This can be accomplished from the command line as follows:

  1. From the command line, navigate to the base folder for the External Data Connector software.
  2. On Windows, execute the following command:

    CVForeignHandler –collectdata –vendor "Vendor_Type_Number" -vm "Instance_Name" –cn "Client_Name"

    For example:

    CVForeignHandler –collectdata –vendor "12" -vm "Instance001" –cn "client1"

    By default, this command will populate all contents of the EMC Networker database into a .zip file in the JobResults folder.

  3. On Linux and Unix, execute the following command:

    ../iDataAgent/CVForeignHandler –collectdata –vendor "Vendor_Type_Number" -vm "Instance_Name" –cn "Client_Name"

    For example:

    ../iDataAgent/CVForeignHandler –collectdata –vendor "12" -vm "Instance001" –cn "client2"

    By default, this command will populate all contents of the EMC Networker database into a .gz file in the JobResults folder.

Parameters

The command includes several parameters that you can set, according to your needs. Parameters to gather the server information include the following:

Parameter

Description

vendor

Numeric value that represents the vendor type. Vendor types include the following:

  • 1 - NetBackup
  • 2 - NetApp
  • 8 - Tivoli Storage Manager
  • 12 - EMC Networker
  • 13 - BackupExec
  • 15 - Veeam

user

User name for the external database. This parameter is not applicable for EMC Networker.

password

Password associated with the user name for the external database in plain text. This parameter is not applicable for EMC Networker.

vm

Instance name as it will appear in the CommCell Console.

cn

Client name as it will appear in the CommCell Console.

inc

Forces an incremental discovery operation.

collectconfig

Contacts remote clients to collect configuration information.

dir

Specifies the directory where existing data should be read, instead of running commands.

Populate the XML File in the CommServe

Once the XML file is created, it must be copied to the CommServe computer and populated into the CommServe database. To do so:

  1. Copy the XML file into the desired location on the CommServe computer.
  2. From the CommCell Console, initiate a Discovery operation.
  3. From the General tab of the Advanced Discovery Options dialog box, select the following options:
    • Full Sync to populate all information in the XML file.
    • Merge from folder to identify the XML file that contains the EMC Networker Master Server information. You can use the Browse option to navigate to the location of the XML file.
  4. Click OK.

The EMC Networker Master Server information will be populated into the CommServe database.

Scheduling Discovery Jobs

If External Data Connector was installed on a client computer using the advanced install option, an EMC Networker instance was created automatically for you and Steps 1 and 2 can be skipped below. Otherwise, you will need to create an instance before running a Discovery operation.

  1. From the CommCell Console, right-click on the External Data Connector node, click New Instance, and select EMC Networker.

  2. Enter an instance name.

    Click OK.

    An instance, default backup set, and subclient are now created and ready for the discovery process.

  3. Right-click the subclient for which you want to discover EMC Networker data and click Discover.

  4. From the Job Initiation tab of the Discovery Options dialog box, select Schedule.

  5. From the Schedule Details dialog box that appears, select the appropriate scheduling options.

  6. Click Options to view the Advanced Schedule Options dialog box.

    Specify the following options:

    • Range of recurrence: Specify the date on which you want this schedule to take effect.
    • Repeat: Select the value for which you want to run the job repeatedly on the day in which the job is scheduled to run.
    • Time Zone: Select a specific time zone from which the job schedule time will be based.

    You can also confirm and/or edit (where applicable) your choices from the Job Summary tab. For a monthly or yearly schedule, you can select either a standard calendar or a custom calendar.

    Click OK once all the desired options have been configured.

  7. Click OK.

    Your discovery operation will execute according to the specified schedule. You can track the progress of the backup job from the Job Controller window. When the backup has completed, the Job Controller displays Completed.

Related Reports

A variety of reports are available that provide detailed information on previously run EMC Networker jobs, as well as jobs run using the CommCell software after migration, as described below:

Reports on CommCell Console

After your first discovery, you can run reports on the CommCell Console to obtain information on all past EMC Networker data protection and recovery jobs.

By default, all reports display information according to CommCell entities; that is, a EMC Networker policy will appear as a subclient, and so on. However, several reports can be customized to display information according to the original EMC Networker entity. While the details of the report remain the same in either case, this option is useful as a tool for new CommCell users who may not be familiar with CommCell components.

Refer to Find a Report by Location - CommCell Console for more information.

 

Last modified: 2/27/2018 8:27:08 PM