Managing System Data

Transcription

1 CHAPTER 16 SMEs: New chapter to club all the system data collection, retention and cleanup topics in one place. Eventually will include how to setup and use Distributed Data Collectors, when that feature makes it into the product. One of the roles of an administrator is to manage Prime Infrastructure s network data collection and retention so that it: Scales to fit the real needsa of the system s users. Minimizes the burden on monitoried devices, applications, and network bandwidth. Survivies hardware failures. The following sections explain how to achieve these goals. Scaling the System SMEs: New planning section explaining the options administrator has in how data collection is done, controlling the size of the database, how much additional traffic the system generates, the size of log files, etc. SMEs: Questions for you: Is there any way the customer can check on how big his critical data stores are getting? The information under Administration > Appliance > Disk Space just gives Disk Space usage. How does he connect to that to, say, how long he is retaining Alarm and Event data, or Do we have any stats on how big these get given sizes of networks, OVAs? How do they track the size of these databases and log files? What are the tradeoffs in terms of amount of database and log file and audit data detail you can retain? For example how do the retention periods for Trend, Device Health, Performance, Network Audit and System Health data affect the growth of the database? Recommendations on where you should cut first, depending on what your emphasese are. For example, if performance data is critical, leave performance alone, cut trend data. List built-in controls, like Alarm/Event cleanup, and link to all the procedures associated with this. Controlling Background Data Collection Tasks, page 16-2 Checking on System Disk Usage, page

2 Scaling the System Chapter 16 Controlling Report Storage and Cleanup, page 16-3 Controlling Alarm, Event, and Syslog Retention, page 16-4 Controlling Health Data Retention, page 16-4 Controlling Trend Data Retention, page 16-5 Controlling Performance Data Retention, page 16-5 Controlling Audit Data Retention, page 16-6 Controlling Background Data Collection Tasks Table 16-1 Background Data Collection Tasks This task AP Image Pre-Download Status Autonomous AP CPU and Memory Utilization Autonomous AP Inventory Autonomous AP Radio Performance Autonomous AP Tx Power and Channel Utilization CCX Client Statistics CleanAir Air Quality Client Statistics Interferers Media Stream Clients Mesh link Performance Mesh Link Status Mobility Service Performance Radio Performance Rogue AP Switch Inventory Traffic Stream Metrics Unmanaged APs Wireless Controller Inventory Wireless Controller Performance Collection of data on The image pre-download status of the access points associated with wireless controllers, For this data to be available for collection, you must enable the Pre-download software to APs option when configuring software downloads to controllers. This data is used in the AP Image Pre-Download Status report. Wireless controller device inventory. This data is used in inventory and PCI DSS Detaile reports. Controls collection of wireless controller performance statistics. 16-2

3 Chapter 16 Scaling the System Table 16-1 Background Data Collection Tasks This task Running Data Collection Enabling Data Collection Tasks Disabling Data Collection Tasks Collection of data on Checking on System Disk Usage To check on the current disk usage: Choose Administration > Appliance > Appliance Status. Under Disk Usage, Prime Infrastructure displays the current storage allocation and percantage of use for each of the Prime Infrastructure subsystem:s in Table 16-2Appliance Status Data Sources, page Table 16-2 Appliance Status Data Sources Disk Source /dev/mapper/smosvg-rootvol /dev/mapper/smosvg-tmpvol /dev/sda3 /dev/mapper/smosvg-recvol /dev/mapper/smosvg-home /dev/mapper/smosvg-optvol /dev/mapper/smosvg-usrvol /dev/mapper/smosvg-varvol /dev/mapper/smosvg-storeddatavol /dev/mapper/smosvg-altrootvol /dev/mapper/smosvg-localdiskvol /dev/sda1 tmpfs Description SMEs: Need description for this and following data sources. What does this source contain? Why is it so importnat you give users a way to check on it? How is it affected by data retention policies or data collection? Controlling Report Storage and Cleanup All scheduled reports are stored in the Scheduled Reports Repository. You will want to ensure that scheduled reports are retained in the report repository for reasonable lengths of time only, and deleted on a regular basis. The default retention scheme is to retain generated reports for no more than 31 days. You can customize this retention period following the steps below. 16-3

4 Scaling the System Chapter 16 Select Report In Repository Path, change specify the repository path as needed. ) Under File Retain Period, change the schedule report retention period as needed Step 5 Controlling Alarm, Event, and Syslog Retention, page 16-1 Controlling Alarm, Event, and Syslog Retention As part of managing your system data, you will want to ensure that raw alarm, event and syslog data are retained for reasonable lengths of time only, and deleted on a regular basis. Data cleanup tasks run nightly to delete old alarms. In addition to the data cleanup task, Prime Infrastructure has an hourly task to check alarm table size. When the alarm table size exceeds 300K, the task deletes the oldest cleared alarms until the alarm table size is within 300 K.. The default retention scheme is to retain active alarms, cleared security alarms, events, and syslogs for no more than 30 days. Cleared non-security alarms are retained for 7 days only. You can customize these retention periods following the steps below. Step 5 Select Alarms and Events Under Alarm and Event Cleanup Options, change the alarm and event retention periods, as needed. Under Syslog Cleanup Options, change the syslog retention period as needed Controlling Health Data Retention Device Health and System Health data are assembled constantly, and deleted on an hourly, daily and weekly basis. SMEs: Why would someone want to change these? What does it mean that data are deelted on an hourly basis? What is retained after that to be deleted on the daily and weekly basis? You can customize these retention periods following the steps below. Select Data Retention. 16-4

5 Chapter 16 Scaling the System Step 5 Under Device Health Data Retain Periods, change the hourly, daily and weekly retention period, as needed. Under System Health Data Retain Periods, change the hourly, daily and weekly retention period, as needed. Controlling Trend Data Retention Trend data is aggregated constantly, and deleted on an hourly, daily and weekly basis. SMEs: Why would someone want to change this? What does it mean that the data are aggregated? How is this different from the other data being retained? You can customize the retention period following the steps below. Select Data Retention. Under Trend Data Retain Periods, change the hourly, daily and weekly aggregated data retention period, as needed. Controlling Performance Data Retention Performance data is ssembled constantly, and deleted on a flexible short-, medium- and long-term basis. SMEs: Why would someone want to change this? What kind of data is deleted on the short-term basis? What on long-term? You can customize these retention periods following the steps below. Select Data Retention. Under Performance Data Retain Periods, change the short, medium and long-term data retention period, as needed. 16-5

6 Maintaining the Database Chapter 16 Controlling Audit Data Retention Network audit data is normally deleted after 90 days.. SMEs: Why would someone want to change this? You can customize this retention period following the steps below. Select Data Retention. Under Network Audit Data Retain Period, change the retention period, as needed. Maintaining the Database As with any other system upon which your organization relies, you will need to ensure that Prime Infrastructure s databases are backed up regularly and can be restored in case of hardware or other failures. Backups are always stored in a depository. You may specify remote FTP repositories as well as the default local repositories. Backups are aaved as.zip files in the ftp-install-dir/ftp-server/root/ncsbackup directory, with a filename in this format: dd-mmm-yy_ hh-mm-ss.zip (for example, 10-Dec-12_ zip). Running Database Backups On Demand, page 16-6 Scheduling Automatic Database Backups, page 16-7 Restoring the Database From Backups, page 16-7 Running Database Backups On Demand You will normally want to schedule automatic database backups, so that the time- and processor-intensive backup process occurs only at relatively low-traffice periods during the day. If you want to execute an immediate system backup, follow the steps below. Choose Administration > Task Manager > Background Tasks. Under Other Background Tasks, find the NCS Server Backup task. If you want to change the backup repository and maximum number of backups, click the NCS Server Backup link and adjust these values, then click Save. 16-6

7 Chapter 16 Maintaining the Database Step 5 Step 6 Step 7 Check the NCS Server Backup task checkbox. At the top of the page, select the command Execute Now. Click Go. Click Refresh to see the current status of the task. Scheduling Automatic Database Backups T.his section provides instructions for backing up the Prime Infrastructuredatabase. You can schedule regular backups through the user interface. Most machine-specifie settings are not included in the database backup. If you restore the backup to a different device, you will need to manually re-create these settings. Machine-specific settings include FTP enable and disable, the FTP port, the FTP root directory, TFTP enable and disable, the TFTP port, the TFTP root directory, HTTP forward enable and disable, the HTTP port, the HTTPS port, the report repository directory, and all high availability settings. To schedule automatic backups of the Prime Infrastructure database, follow these steps: Choose Administration > Task Manager > Background Tasks. Under Other Background Tasks, click NCS Server Backup. Complete the fields as follows: a. Make sure Enabled is checked b. Enter the maximum number of backups to keep (the default is 2). c. Specify an existing backup repository (local or remote) or click Create to create a new repository. d. Enter the number of days between each backup. For example, 1 = a daily backup, 2 = a backup every other day, 7 = a weekly backup, and so on. The default is 7, the minimum is 1, the maximum is 360. e. Enter the time when you want the backup to start. Use this format: hh:mm AM/PM (for example: 03:00 AM). Note Note Backing up a large database affects the performance of the server. You should schedule backups to run when the server is less active (for example, in the middle of the night). Click Save. The backup file will be saved as a.zip file in the ftp-install-dir/ftp-server/root/ncsbackup directory, with a filename in this format: dd-mmm-yy_ hh-mm-ss.zip (for example, 10-Dec-12_ zip). Restoring the Database From Backups SME: New section. Customer needs to know how to do this, otherwise pulling backups is meaningless. Last time I spoke to anyone about it, they said it could be done both in the GUI and at the command line. I have no info on how to do either. 16-7

8 Maintaining the Database Chapter