Triggering Events for Backup Servers

Products

• STORAGE RESOURCE MANAGEMENT SUITE

Issue/Introduction

When registering BAB11.1 backup server and selecting the Trigger Backup Events option, the message "Failed to mark event trigger for BAB server" appears in the registration log. The backup server registers as a backup server and the collection finishes, but no events are captured. How can we use the option for triggering backup event for BSRM11.5 to see daily, warning, and critical events?

Environment

Backup events are captured only if the following conditions exist:

• You must have installed BrightStor Storage Resource Manager r11.5

• You must have upgraded the BrightStor ARCserve Backup r11.1 iSponsor to the BrightStor ARCserve Backup r11.5 iSponsor

• You must have upgraded iGateway 3.0 to iGateway 4.0.

Resolution

Windows 2003 Server

To successfully upgrade on a BrightStor ARCserve Backup r11.1 machine when the BABiSponsor is installed on a Windows 2003 server, perform the following steps:

1. Remove the BrightStor ARCserve Backup r11.1 iSponsor. If there are any other iSponsors installed, you will also need to remove them.

• Upgrade iGateway 3.0 to iGateway 4.0.

• From My Computer, select Properties, select Advanced, and select Environment Variables.

• Verify that the following is identified as the value of the IGW_LOC environment variable:
  
  c:\Program Files\CA\iGateway
  
  Note: This verification is critical to the correct installation of the BrightStor ARCserve Backup r11.5 iSponsor.
  
  If this is not the value of the IGW_LOC environment variable, uninstall the iGateway, ensure that the IGW_LOC environment variable is cleared, and reinstall iGateway 4.0.

• Verify that the following directory does not exist:
  
  c:\Program Files\CA\SharedComponents\iTechnology
  
  Note: This verification is critical to the correct installation of the BrightStor ARCserve Backup r11.5 iSponsor.
  If this directory exists, uninstall the iGateway, ensure that the IGW_LOC environment variable is cleared, and reinstall iGateway 4.0.

• When all iGateway files are located in the directory identified by the environment variable IGW_LOC, install the BrightStor ARCserve Backup r11.5 iSponsor, and reinstall any other iSponsors that were removed during step #1 above.

• Use the Backup Servers registration wizard to register the machine in BrightStor Storage Resource Manager r11.5, and enable the Trigger Events option.

 

Windows 2000

To successfully upgrade on a BrightStor ARCserve Backup r11.1 machine when the BABiSponsor is installed on a Windows 2000 Server, perform the following steps:

1. Remove the BrightStor ARCserve Backup r11.1 iSponsor. If there are any other iSponsors installed, you will also need to remove them.

• Uninstall the iGateway.

• From My Computer, select Properties, select Advanced, and select Environment Variables.

• Verify that there is no IGW_LOC variable path and that the following directories do not exist:
  
  c:\Program Files\CA\Shared Components\iTechnology
  
  C:\Program Files\CA\iGateway
  
  Note: This verification is critical to the correct installation of the BrightStor ARCserve Backup r11.5 iSponsor and iGateway 4.0.

• Install iGateway 4.0 and change the default installation path for the iGateway to the following:
  
  c:\Program Files\CA\iGateway

• From My Computer, select Properties, select Advanced, and select Environment Variables. Verify that the following is identified as the path for the IGW_LOC environment variable:
  
  c:\Program Files\CA\iGateway

• Verify that the following directory does not exist:
  
  ...\CA\shared components\iTechnology

• Verify that the following folder exists:
  
  ...\Ca\iGateway

• When all iGateway files appear in the correct directory pointed to by the IGW_LOC environment variable, install the BrightStor ARCserve Backup r11.5 iSponsor, and reinstall any other iSponsors that were removed during step #1 above.

• Use the Backup Servers registration wizard to register the BrightStor ARCserve Backup machine in BrightStor Storage Resource Manager r11.5 and enable the Trigger Events option.