Loading...

Advanced Options - External Data Connector

Table of Contents

Components Created after Discovery

Components Created after Migration

Discover Based on Specific Criteria

Advanced Discovery Options

Capture Metadata Using Decoupled Install

Troubleshooting

Related Reports

Components Created after Discovery

Your first discovery and migration operations lay the framework for protecting and recovering BackupExec clients using the CommCell software. By default, all future discovery operations occur incrementally; that is, only new or changed BackupExec information is merged into the CommCell. Similarly, migration operations occur on-demand as needed. In both cases, the Basic topic can be used to perform future discovery and migration operations.

After the discovery process is complete, BackupExec components, such as client computers, backup schedules, and media are mapped to the appropriate CommCell entity. The following versions of BackupExec are supported for these BackupExec component groupings:

BackupExec Grouping

Description

Supported BackupExec Versions*

Configuration

Clients, Policy Types, Policies, Policy Attributes (compression, encryption), Policy Schedules (frequency, calendar), Backup Types, Media Server.

2010, 2012, 2012 with SP2, 2014, and 2015

Jobs

Backup and Admin Policy Job information is migrated for CommCell reporting purposes.

2010, 2012, 2012 with SP2, 2014, and 2015

Media

Lifecycle Policies, Storage Units, Robots, and Media Status are migrated for CommCell reporting purposes.

2010, 2012, 2012 with SP2, 2014, and 2015

*Both Windows and Unix platforms are supported.

Configuration Entities

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

BackupExec Component

Notes

Clients

Clients are brought in initially as deconfigured clients and are shown under Client Computer Group in CommCell Console.

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

All BackupExec client computers discovered will, however, be initially grouped into a single Client Computer Group based on the instance from which the discovery operation was run.

Policy Type

BackupExec Policy Type

  • MS-Exchange-Server
  • MS-SharePoint
  • MS-SQL-Server
  • MS-Windows-NT
  • Oracle
  • Standard
  • All other BackupExec Policies

CommCell Agent

  • Exchange Database
  • SharePoint 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 BackupExec Policy.

Policies

BackupExec policies are migrated to CommCell subclients under a single backup set for each client. The Backup Selections of a BackupExec policy becomes the content of the subclient.

The Properties for subclients created by External Data Connector are read-only and cannot be changed.

Also, note that when previously merged policies are deleted from the BackupExec 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.

Policy Attributes (Compression)

Policy attributes, such as compression, becomes a subclient property. The properties for subclients created by External Data Connector are read-only and cannot be changed.

Policy Attributes (Encryption)

BackupExec encryption

  • BF - CFB
  • AES-128-CFB
  • AES-256-CFB
  • DES and other Legacy types

CommCell Encryption

  • BLOWFISH (128 Bit)
  • AES (128 Bit)
  • AES (256 Bit)
  • DES (192 Bit)

Policy Schedules (Frequency)

These schedule frequencies are migrated to a CommCell Schedule Policy:

  • Hourly
  • Daily
  • Monthly

Policy Schedules (Calendar)

BackupExec Calendar

  • Specific Dates
  • Recurring Week Days
  • Recurring Days of the Month

CommCell Schedule*

  • One Time
  • Monthly
  • Monthly

    *BackupExec calendar schedules are migrated to a CommCell Schedule Policy.

Backup Types

BackupExec

  • Full Backup
  • Incremental Backup
  • Cumulative Backup

CommCell

  • Full
  • Incremental
  • Differential

Media Server

BackupExec Media Servers are migrated to CommCell MediaAgents with all configured properties.

Job entities

The following table lists the BackupExec job entities that are discovered and how they are mapped to CommCell entities.

BackupExec Component

Notes

Policy Jobs

Backup and Admin Policy Job information is migrated for CommCell reporting purposes.

Media Entities

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

BackupExec Component

Notes

Lifecycle Policy

BackupExec lifecycle policies are migrated to CommCell storage policies. If the Lifecycle Policy had data retention settings configured, they are included in the CommCell Schedule Policy as well.

Storage Units

BackupExec Storage Unit

  • Disk Storage
  • Disk Path Name
  • Media Manager

CommCell Media

  • Disk Library
  • Mount Path
  • Tape Library

Robots

Robot mappings are migrated to CommCell libraries.

Media Status

BackupExec media that are in either of these states will display as FULL in the CommCell Properties of the media:

  • FULL
  • FROZEN
  • SUSPENDED

Components Created after Migration

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

BackupExec Policy Type

Corresponding CommCell Agent

CommCell Agent as Displayed in the CommCell Console

MS-Exchange-Server

Microsoft Exchange Database iDataAgent

Exchange Database

MS-SharePoint

Microsoft SharePoint Server iDataAgent

SharePoint Database

MS-SQL-Server

Microsoft SQL Server iDataAgent

SQL Database

MS-Windows-NT

Microsoft Windows File System iDataAgent

File System

Oracle

Oracle iDataAgent

Oracle Database

Standard

Microsoft Windows File System iDataAgent

Unix File System iDataAgent

File System

Note that the File System iDataAgent used will correspond to the operating system (Windows or Unix) associated with the original BackupExec Policy.

All other BackupExec Policies

Other External Agent

Other External Agent

Discover Based on Specific Criteria

In between your regular full or incremental discovery operations, it may be necessary to perform a discovery based on a specific set of criteria. The following sections describe the criteria-based discovery options available. All options are available in the General tab of the EDC Policy Properties dialog box, which is accessible by right-clicking the External Data Connector policy in the CommCell Browser and clicking Properties.

Discover Clients by Agent Type

If you only want to include clients that are configured with a specific application type, the Discover Clients by Agent Type can be used to identify clients with the desired application agent type to be included in the discovery process. This is especially useful if you need to generate an up-to-date report of the status of all clients running a specific application, such as an Exchange database, without having to collect information about clients running other applications.

The following Agent types are populated into Agent nodes in the CommCell Console following discovery:

  • Microsoft Exchange
  • Microsoft SharePoint Server
  • Microsoft SQL Server
  • Microsoft Windows File System
  • Oracle
  • Unix File System

Any other Agent types discovered will appear as Others in the Agent node.

Discover Clients by Client Name

If you know the names of the client computers you wish to discover, you can do so by entering the desired client names using available expressions. This option is useful if you only want a specific subset of clients to be incorporated into the CommServe database, such as clients on which you may later install CommCell software. Wildcard expressions may be used to filter out clients with specific naming characteristics. (Refer to the Wildcards documentation for information on supported wildcard expressions.)

Note that if this option is selected, only the jobs and configuration settings associated with the defined clients will be included. As such, schedules not associated with the defined clients must also be filtered out prior to running the discovery operation.

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 BackupExec 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 BackupExec clients. This option should be used if you want to ensure that all the latest client information from the BackupExec 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 BackupExec database information using a specified XML file. Use this option if you want to perform a full or incremental discovery of a BackupExec database without the need to communicate with the BackupExec Server itself.

Get Advanced Client Settings

This option populates BackupExec client settings above and beyond the jobs, schedules, and agents of the client. Use this option if you intend to migrate the client to the CommCell and wish to ensure client settings such as compression, encryption, and content filters, remain intact for future data protection and recovery operations.

Note that encryption settings configured for the BackupExec client computer will be mapped as follows:

BF - CFB - BLOWFISH (128 Bit)

AES-128-CFB - AES (128 Bit)

AES-256-CFB - AES (256 Bit)

DES and other Legacy types - DES (192 Bit)

Collect Storage Information

Use this option to obtain information about the storage media associated with the discovered clients, such as libraries and drive pools. This option is applicable for information pertaining to backup jobs.

Collect Jobs Information

Use this option to obtain information about backup jobs that have run for the discovered client.

Capture Metadata Using Decoupled Install

This method uses External Data Connector to populate BackupExec 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 BackupExec 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 BackupExec Master Server
  2. Create XML Files Containing BackupExec Database Information
  3. Populate the XML Files in a CommServe

The following sections describe these phases in detail.

Install External Data Connector on the BackupExec Master Server

External Data Connector must first be installed on the BackupExec 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 BackupExec Master Server. For instructions, see Custom Package.

Create an XML File Containing BackupExec Database Information

Once External Data Connector is installed on the BackupExec Master Server, a bundle file containing the BackupExec 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" –user "External_Database_Admin_User_Name" –password "External_Database_Admin_User_Password" -vm "Instance_Name" –cn "Client_Name"

    For example:

    CVForeignHandler –collectdata –vendor 13 –user "bsmith" –password "be348n2" -vm "Instance001" –cn "client1"

    By default, this command will populate all contents of the BackupExec 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" –user "External_Database_Admin_User_Name" –password "External_Database_Admin_User_Password" -vm "Instance_Name" –cn "Client_Name"

    For example:

    ../iDataAgent/CVForeignHandler –collectdata –vendor 13 –user "bsmith" –password "be348n2" -vm "Instance001" –cn "client2"

    By default, this command will populate all contents of the BackupExec database into a .gz file in the JobResults folder. Optionally, if you have previously populated BackupExec database information and only want to include recently changed data, you can use the -inc argument at the end of the command string.

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 BackupExec Master Server information. You can use the Browse option to navigate to the location of the XML file.
  4. Click OK.

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

Troubleshooting

External Data Connector (EDC) Discovery may fail with the following condition:

  • Schedules have no window defined.

    This issue can be resolved by defining a schedule window.

Related Reports

A variety of reports are available that provide detailed information on previously run BackupExec 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 BackupExec data protection and recovery jobs.

By default, all reports display information according to CommCell entities; that is, a BackupExec policy will appear as a subclient, and so on. However, several reports can be customized to display information according to the original BackupExec 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:22:05 PM