Documentation forNetwork Configuration Manager
Managing network configurations is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Advanced edition. Network Configuration Manager (NCM) is also available in a standalone module.

NCM storage requirements

Several factors affect storage requirements in SolarWinds Network Configuration Manager (NCM). Understanding these factors can help you effectively manage disk space and optimize system performance.

Factors that affect storage requirements

The following sections describe key factors and how they affect storage requirements.

Number of managed devices

Impact More devices generate more configuration files, logs, and backup data, which increases storage requirements.
Management Regularly audit and remove any obsolete devices from NCM to manage storage efficiently.

Backup frequency

Impact Frequent configuration backups lead to increased storage usage. Each backup consumes space, especially if there are significant changes between backups.
Management Adjust the backup frequency based on criticality. For non-critical devices, consider less frequent backups.

For more information, see Schedule regular backups of network config files.

Retention policies

Impact Longer retention periods for configuration backups, logs, real-time change detection (RTCD), and reports result in higher storage usage.
Management Implement retention policies that balance the need for historical data with storage capacity. Regularly archive or delete older backups and logs. Also ensure that RTCD downloads only configs with changes you are interested in. Otherwise it could significantly increase the number of downloaded configs and the required storage space.

For more information, see:

Log data (session trace)

Impact Extensive logging for config backups, especially in large networks, can quickly consume significant disk space. By default, when session traces are enabled, config transfer details are logged for each config download on each node. (It logs each command sent to and received from the device during config downloads.)This can produce an enormous number of log files related to config transfers.
Management Set appropriate retention periods for log data. Filter logs to capture only essential information and set size limits on log files. If a session trace is enabled for troubleshooting, disable it afterward.

For more information, see Generate session trace logs for NCM and NPM modules.

Configuration file size

Impact Larger configuration files, common in complex devices with detailed configurations, consume more storage.
Management Regularly review and clean up unnecessary configuration lines or comments in device configurations.

Report and job data

Impact Reports and job outputs (for example, policy compliance checks and inventory reports) can take up considerable space if retained indefinitely. (This is especially true for Inventory ARP Tables and IP Route Tables.)
Management Set retention policies for reports and job outputs. Archive or delete older, non-essential reports.

For information about inventory jobs, see Troubleshoot NCM inventory job issues.

Database size

Impact The database grows with the accumulation of configuration data, logs, reports, and historical information.
Management Regularly perform database maintenance, such as indexing, cleanup, and optimization. Configure data purging and archiving policies.

For more information, see:

Job frequency and scope

Impact Frequent and comprehensive jobs (for example, inventory updates or policy compliance checks) generate more data and consume more storage.
Management Schedule jobs wisely to avoid unnecessary data generation. Limit the scope only to essential devices and information.

Practical steps for managing storage usage

By addressing these key factors, you can effectively manage storage usage in NCM, ensuring optimal performance and avoiding unnecessary disk space consumption.

Audit and cleanup

  • Regularly audit managed devices and remove devices that are no longer needed.

  • Periodically clean up old configuration backups, logs, and reports.

Configure appropriate retention policies

  • Set retention periods that align with your organization's data retention policies and regulatory requirements.

Database maintenance

  • Regularly perform maintenance tasks like reindexing, cleanup, and optimization to keep the database size manageable.

Log management

  • Filter and limit log data collection to essential information.

  • Set size limits and retention periods for log files.

Job scheduling

  • Optimize job schedules to balance operational needs with storage considerations. Avoid unnecessary data generation.