반품
-
제목
False Alarms for Sybase Backup Server Status in Foglight -
설명
You are seeing false alarms for Sybase Backup Server (Availability) Connection Failed in Foglight.
When reviewing historical data, the data server status is correct, but the backup server information shows as n/a or is incomplete. -
원인
This usually happens when the Backup Server Alias property in the Sybase MDA agent is set incorrectly.
Often, the value is set to thesrvnetnameinstead of the requiredsrvname(typicallySYB_BACKUP).The agent uses the
srvnameto check connectivity to the backup server. If the alias is set incorrectly, the agent cannot connect and will report the backup server as unavailable, even if it is up and running—triggering a false alarm. -
해결 방안
1. Identify the Correct Backup Server Alias
- Log in to the Sybase server.
- Run the following SQL to view your backup server’s registered names:
select * from sysservers where srvname = 'SYB_BACKUP'- Note the value in the
srvnamecolumn (usuallySYB_BACKUP).
Do not use the value from thesrvnetnamecolumn.
2. Update the Foglight Agent Property
- In Foglight, go to the Sybase_MDA Agent properties.
- Locate the Backup Server Alias property.
- Set this value to match the
srvname(e.g.,SYB_BACKUP) from your Sybase server.
3. Test Backup Server Connectivity
- Connect to your Sybase instance.
- Run the following command to test connectivity to the backup server:
exec SYB_BACKUP...sp_who- If this command succeeds, the configuration is correct.
If it fails, verify the alias and network connectivity.
4. Validate in Foglight
- Wait for the next agent collection cycle or manually trigger one.
- Confirm that backup server status is now displayed correctly and that false alarms no longer occur.
Summary
Always set the Backup Server Alias property in Foglight to thesrvname(not thesrvnetname) as listed in the Sybasesysserverstable.
This ensures Foglight can correctly monitor the backup server and prevents false alarms due to configuration errors.