Page tree

Unsupported content

 

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

BMC PATROL Agents can failover from one BMC ProactiveNet Integration Service to another under the following scenarios:

  • When Integration Service goes down
  • Forceful failover of BMC PATROL Agents through BMC PATROL Configuration Manager from one integration service to another

Deployment in the failover test case

A BMC ProactiveNet Server is associated with two primary Integration Services (numbered 1 and 3) and two recover Integration Services (numbered 2 and 4). Using BMC PATROL Configuration Manager, failover is intentionally initiated to move the BMC PATROL Agents from the primary Integration Services to recovery Integration Services.

BMC ProactiveNet Server load and configuration for test case

Metric

Value

Number of devices monitored by BMC ProactiveNet Server

20 K

Number of monitor instance monitored in BMC ProactiveNet Server

100 K

Number of attributes monitored in BMC ProactiveNet Server

1.1 million

Number of Integration Services associated with BMC ProactiveNet Server

4

Number of BMC PATROL Agents

409

Auto-sync poll interval

5 minutes

Databases used by BMC ProactiveNet Server

Sybase

Timing for failover of BMC PATROL Agents

The following table shows the failover time for components and processes from Integration Service 1 to Integration Service 2. In this scenario, failover is initiated through BMC PATROL Configuration Manager.

Failover from Integration Service 1 to 2

Metric

Value

Number of PATROL Agents failover

208

Number of monitor instances failover

44 K

Number of attributes failover

490 K

Action

Time

Failover of BMC PATROL Agents

1 minute

Failover of monitor instances

29 minutes

Data collection to resume after failover

10 minutes

Failover from Integration Service 3 to Integration Service 4 was done first without the agent for Virtual Servers KM, and then with only the agent for Virtual Servers KM.

Failover from Integration Service 3 to 4, without Virtual Servers KM

Metric

Value

Number of PATROL Agents failover

200

Number of monitor instances failover

36 K

Number of attributes failover

510 K

Action

Time

Failover of BMC PATROL Agents

5 minutes

Failover of monitor instances

29 minutes

Data collection to resume after failover

10 minutes

Total time for failover (PATROL Agent + monitor instances

34 minutes


Failover from Integration Service 3 to 4, with only Virtual Servers KM

Metric

Value

Number of PATROL Agents failover

1

Number of monitor instances failover

3 K

Number of attributes failover

510 K

Action

Time

Failover of BMC PATROL Agents

30 seconds

Failover of monitor instances

29 minutes

Data collection to resume after failover

45 minutes

Total time for failover (PATROL Agent + monitor instances

29 minutes