KB labels


Ticket Product Version

Ticket Category

Ticket Assignee


Hot Fixes

Published Fixes
Your Arcserve Support User Profile
First Name:
Last Name:
email:
Phone:
Company:*
Customer Type:
Language:

Country:
Region:

Time zone:
Follow

arcserve-KB : Scenario: Integrating arcserve Central Protection Manager with Kaseya

Last Update: 2016-04-25 14:09:55 UTC
CA ARCSRV CENTRAL HOST-BASED VM BACKUP: 16.0
Last Modified Date:    07/30/2012
Document ID:    TEC574790
Tech Document
Title:  Scenario: Integrating CA ARCserve Central Protection Manager with Kaseya

1.0 Introduction

2.0 How to Integrate CA ARCserve Central Protection Manager with Kaseya
2.1 Install the Kaseya Agent
2.2 Configure the CA ARCserve Central Protection Manager Server to Communicate with the Kaseya Server
2.3 Configure the Log Parser for the Kaseya Server
2.4 Assign the Parser Sets on the Kaseya Server
  2.4.1 Examples of Parser Set Filters

3.0 Copyright

1.0 Introduction

Product: CA ARCserve Central Protection Manager
Release: r16

OS: Windows Server 2008 R2 (x64), Windows Server 2008 R2 (x64) SP1

This scenario describes how Storage Managers can configure CA ARCserve Central Protection Manager to publish information about alert messages in real time to a Kaseya Infrastructure management tool. This capability lets Kaseya Administrators respond to CA ARCserve Central Protection Manager alerts in an appropriate manner.

CA ARCserve Central Protection Manager monitors alerts that originate from the following applications:

  • CA ARCserve D2D
  • CA ARCserve Central Virtual Standby
  • CA ARCserve Central Host-Based VM Backup
  • CA ARCserve Central Protection Manager

The Kaseya server generates reports about nodes running these applications that Administrators can view using the Kaseya management tool. The Kaseya server can be configured to send email messages to the Administrators based on predefined criteria.

CA ARCserve Central Protection Manager integrates with the following Kaseya Infrastructure management tool:

  • Server: 6.1.0.0
  • Agent: 6.1.0.6

This Knowledge Base Article constitutes a portion of the official CA product documentation for this CA product. This Knowledge Base Article is subject to the following notices, terms and conditions.

2.0 How to Integrate CA ARCserve Central Protection Manager with Kaseya

Storage Managers can configure CA ARCserve Central Protection Manager to communicate alert messages to Kaseya servers. Kaseya administrators can configure Kaseya IT Infrastructure Management tools to detect CA ARCserve Central Protection Manager alerts, generate alert reports, and send email messages. The administrators can use the reports to manage the health of CA ARCserve D2D nodes.

The following diagram illustrates how Storage Managers integrate CA ARCserve Central Protection Manager with the Kaseya IT Infrastructure Management tool:

Follow these steps to integrate CA ARCserve Central Protection Manager with Kaseya:

  1. Install the Kaseya agent on the CA ARCserve Central Protection Manager server.
  2. Configure the CA ARCserve Central Protection Manager server to communicate with the Kaseya server.
  3. Configure the Log Parser for the Kaseya server.
  4. Assign the parser sets on the agent nodes.

2.1 Install the Kaseya Agent


Install the Kaseya agent on the CA ARCserve Central Protection Manager server to allow it to communicate with the Kaseya server. You install the agent by deploying it from the Kaseya IT management console.

Follow these steps:

  1. Open a browser window and log in to the Kaseya IT management console.

    From the navigation bar on the left side of the window, click Agent.

    The agent options appear.
  2. Expand Install Agents and click Deploy Agents.

    The deploy agents options appear.
  3. Click one of the following options:
    • Click to download default Agent

      Lets you download and save the installation file on the target computer.

      After the download completes, run the agent installation file directly on the target computer.
    • Create Package

      Lets you create an installation package utility to install the agent on one or more computers. Follow the on-screen instructions to create the installation package. For more information, see the Kaseya documentation.

The agent is installed.


2.2 Configure the CA ARCserve Central Protection Manager Server to Communicate with the Kaseya Server


CA ARCserve Central Protection Manager lets you sent alert messages to Kaseya IT Management servers. To send the alert information, configure the CA ARCserve Central Protection Manager server to communicate with the Kaseya server.

Follow these steps:

  1. Log in to CA ARCserve Central Protection Manager and click Configuration on the Navigation bar.

    The Configuration options appear.
  2. Click IT Management Server Configuration in the Configuration list.

    The IT Management Server configuration options appear.
  3. Complete the following options:
    1. Click Enable.
    2. Click Kaseya.
    3. Specify a Repeat Method. The Repeat Method defines the days of the week to resend alert notifications to the Kaseya server when the original send process failed. The process of sending alerts can fail when the Kaseya server is not available or offline.
    4. Specify a Schedule. The Schedule defines the time of the day to resend the alert notifications to the Kaseya server.
  4. Click Save.

The CA ARCserve Central Protection Manager server is configured to communicate with the Kaseya server.


2.3 Configure the Log Parser for the Kaseya Server


To view information about CA ARCserve Central Protection Manager alerts, configure the Kaseya server to read the data in CA ARCserve Central Protection Manager alert log files.

Follow these steps:

  1. Open a browser window and log in to the Kaseya IT management console.
  2. From the navigation bar on the left side of the window, click Monitor.

    The monitor options appear.
  3. Expand Log Monitoring and click Log Parser.

    The Log Parser configuration options appear.
  4. In the Machine.Group ID list, click the check box next to the CA ARCserve Central Protection Manager server.

    From the Log File Parser drop-down list box, click

  1. Click New.

    The Log File Parser Definition dialog opens.
    1. Complete the following fields on the Log File Parser Definition dialog:
    2. Parser Name

      Defines the name of the Log File Parser file.

  • Log File Path

    Defines the path to the log file on the CA ARCserve Central Protection Manager server. The path to the log file is as follows:

    
    \ITMgmtIntegration\

    CA ARCserve Central Protection Manager generates log files that support Unicode and non-Unicode characters. The log file names are as follows:

    • Non-Unicode:
      
      CentralAppAlertsForKaseyaANSI.log

    • Unicode:
      
      CentralAppAlertsForKaseyaUTF8.log

    Important! The Kaseya IT management console does not support Unicode characters. Therefore, use the log file named CentralAppAlertsForKaseyaANSI.log.

  • Log Archive Path

    Defines the path to the archived log file on the CA ARCserve Central Protection Manager server. By default, Protection Manager archives the log file when it exceeds 10 MB.

    Note: To specify an alternative value for when Protection Manager archives the log file, modify the value of MaxLogFileSize (in MB) in the following file:

    
    \ITMgmtIntegration\Configuration\Edge-ITMgmtIntegration.INI

  • Description

    Defines the description of the Log File Parser file.

  • Template

    Defines the format of the data contained in the log file on the CA ARCserve Central Protection Manager server. Use the following syntax:

    
    $CACentral Protection Manager Machine Name$ [$Alert Generated Product$] 
    
    $Alert Generated Machine Name$ $Severity$ $Send Time From Origin Product$ $Alert Message$

  • Output Template

    Defines the format of the output data on the Kaseya server. Use the following syntax:

    
    $Protection Manager Server$ $Generated by$ $Host Name$ $Severity$ $Sent$ $Message$

  • Log File Parameters

    Create the following log file parameters:

    Note: Click Apply after you specify the Type (of parameter) to save the parameter.

    • CA ARCserve Central Protection Manager Machine Name

      Type: String

    • Alert Generated Product

      Type: String

    • Alert Generated Machine Name

      Type: String

    • Severity

      Type: String

    • Send Time From Origin Product

      Type: DateTime

      Format: YYYY-MM-DD hh:mm:ss

    • Alert Message

      Type: String

  1. Click Save.
  2. The Log Parser definition is saved.
  3. Click Close.

The Log Parser Definition dialog closes and the Log Parser Definition file is created and applied to the CA ARCserve Central Protection Manager server.

2.4 Assign the Parser Sets on the Kaseya Server

You configure parser sets to filter information about CA ARCserve Central Protection Manager alerts in the Kaseya management console. The parser sets define the conditions that you filter. For example, you can filter the alerts that are based on severity level, backup failures, and so on.

Follow these steps:

  1. Open a browser window and log in to the Kaseya IT management console.


  2. From the navigation bar on the left side of the window, click Monitor.

    The monitor options appear.


  3. Expand Log Monitoring and click Assign Log Parser.

    The assign log parser sets options appear.


  4. In the section Assign log parser sets to selected machines, specify the alert options that you require.


  5. From the Select log parser drop-down list, click the Log Parser that you want to assign the parser sets.

    From the Define parser sets drop-down list, click .

    The Edit Parser Set dialog opens.


  6. In the Parser Set Name field, specify a name for the Parser Set and click New.

    The parsing options appear.


  7. Specify the following values:
    • Parser Column

      Defines the parameter that you want to filter.


    • Operator

      Defines how you want to filter the data contained in the parameter.


    • Parameter File


    • Defines the value of the parameter that you want to filter.

      Click Add and click Close.

      The filter is applied to the Parser Set and the Edit Parser Set dialog closes.

      Note: For examples of how to specify Parser Set filters, see Examples of Parser Set Filters.
  8. From the Select log parser drop-down list, click the Log Parser that you want to apply.

    From the Define parser sets drop-down list, click the Parser Set that you created.

    From the Machine IDs column, click the check box next to the servers that you want to apply the Parser Set.

    Click Apply.

The Log Parser and the Parser Set are assigned.

2.4.1 Examples of Parser Set Filters

To create Parser Sets that filter only alerts that contain errors, specify the following values:

  • Parser Column

    Severity


  • Operator

    Equal


  • Parameter Filter

    error

To create Parser Sets that display all alerts, regardless of severity level, specify the following values:

  • Parser Column

    Severity


  • Operator

    Contains


  • Parameter Filter

    error, warning, information

To create Parser Sets that display only alerts about failed backups, specify the following values:

  • Parser Column

    Alert Message


  • Operator

    Contains


  • Parameter Filter

    backup, failed

3.0 Copyright

This Documentation, which includes embedded help systems and electronically distributed materials, (hereinafter referred to as the 'Documentation') is for your informational purposes only and is subject to change or withdrawal by CA at any time.

This Documentation may not be copied, transferred, reproduced, disclosed, modified or duplicated, in whole or in part, without the prior written consent of CA. This Documentation is confidential and proprietary information of CA and may not be disclosed by you or used for any purpose other than as may be permitted in (i) a separate agreement between you and CA governing your use of the CA software to which the Documentation relates; or (ii) a separate confidentiality agreement between you and CA.

Notwithstanding the foregoing, if you are a licensed user of the software product(s) addressed in the Documentation, you may print or otherwise make available a reasonable number of copies of the Documentation for internal use by you and your employees in connection with that software, provided that all CA copyright notices and legends are affixed to each reproduced copy.

The right to print or otherwise make available copies of the Documentation is limited to the period during which the applicable license for such software remains in full force and effect. Should the license terminate for any reason, it is your responsibility to certify in writing to CA that all copies and partial copies of the Documentation have been returned to CA or destroyed.

TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THIS DOCUMENTATION 'AS IS' WITHOUT WARRANTY OF ANY KIND, INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU OR ANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT, FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUT LIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESS INTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA IS EXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCH LOSS OR DAMAGE.

The use of any software product referenced in the Documentation is governed by the applicable license agreement and such license agreement is not modified in any way by the terms of this notice.

The manufacturer of this Documentation is CA.

Provided with 'Restricted Rights.' Use, duplication or disclosure by the United States Government is subject to the restrictions set forth in FAR Sections 12.212, 52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section 252.227-7014(b)(3), as applicable, or their successors.

Copyright © 2012 CA. All rights reserved. All trademarks, trade names, service marks, and logos referenced herein belong to their respective companies.

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments