For the Performance Analytics Engine component to store traffic data, you must configure a data storage location. It can be either a virtual disk on the Performance Analytics Engine instance, or a server in your IT infrastructure with a Server Message Block/Common Internet File System (SMB/CIFS) or Network File System (NFS) interface.
To perform this procedure, you must have Operator-level access, or higher.
In the BMC Application Management Console, point to System Deployment > Performance Analysis, and click Storage Location.
Local disk — Traffic data is stored on the virtual disk of the Performance Analytics Engine instance. This option implies less impact on the network load, compared to sending traffic to an NFS server or Samba drive. Provide Maximum Storage Size (in gigabytes).
Before selecting this option, ensure that:
The system has only one instance of Performance Analytics Engine configured. If the system has more instances configured, select remote data storage — NFS or SMB/CIFS, which enables the system to store an increasing amount of traffic without performance or capacity issues.
Performance Analytics Engine has a separate virtual disk for storing traffic data. If there is no empty disk, the system displays an error message.
Note
Do not use multiple virtual hard drives on a single virtual machine storage file. To add new virtual hard drive to the Performance Analytics Engine, use a separate storage file.
Server Message Block/Common Internet File System (SMB/CIFS) — Traffic data is stored on the Samba drive that you provide. SMB/CIFS is a protocol typically used on a Windows operating system.
Note
The virtual disk that you are going to provide is not used by another instance of Performance Analytics Engine. It is not recommended using the save virtual disk for multiple PAE instances.
Local disk: No parameters. The system finds an empty virtual disk on a Performance Analytics Engine instance and formats it.
Note
If you increase the size of this disk in the future, Performance Analytics Engine will still use the amount of disk space that was defined during the initial formatting.
Share name (for example, data).
Note
Because of the rolling buffer, it is not recommended using the same share for multiple Performance Analytics Engine instances – when the buffer is full, data from one instance will override data from other instance(s).
Maximum storage size (in gigabytes), which must not exceed the total disk size
Note
The storage mechanism uses a rolling buffer so that as it fills up, the system deletes old data to make room for new data (first in, first out, or FIFO). For detailed sizing information, see Sizing Performance Analytics Engine instances.
Click Save.
You have configured the storage location for the Performance Analytics Engine.