Troubleshooting › Troubleshooting: I am Unable to Back Up Data Repository

Troubleshooting: I am Unable to Back Up Data Repository

Symptom:

When I run the vbr.py script to back up Data Repository, I see the message, "Another vbr instance is already running".

Solution:

This message indicates that a previous backup attempt failed, for any number of reasons (for example, password-less ssh was not set up correctly).

To reattempt to back up Data Repository, do the following steps:

1. Remove the /tmp/.initiator.mutex file from the computer where Data Repository you want to back up is installed.

   The next scheduled backup will occur normally.

Troubleshooting: Multiple SNMP Devices Trigger Intrusions Alarms

Symptom:

I have many SNMP devices behind a more restricted firewall configuration (such as DMZ networks). For security reasons, the SNMP devices have different community strings. I defined an SNMP profile for each different community string, but now I am getting intrusion alarms and have been logged out of CA Performance Center.

Solution:

To find the correct SNMP profile for a device, CA Performance Center tries all of the SNMP profiles. This behavior can trigger intrusion alarms and can log you out of CA Performance Center.

To resolve this issue, follow this process:

1. Create a separate discovery profile for a critical SNMP device.
2. Assign the SNMP profile with the correct community string to the discovery profile.
3. Repeat steps one and two for each critical SNMP device.

When discovery is run, only the assigned SNMP profile is used.