Submit a ticketCall us

Systems Monitoring for Dummies
Our new eBook will teach you the fundamentals and help you create monitors and alerts that are effective, meaningful, and actionable. Monitoring is more than a checkbox on your to-do list. This free eBook will give you practical advice to help you succeed in all aspects of monitoring – discovery, alerting, remediation, and troubleshooting. Don’t miss out on this indispensable resource for newbies, experienced IT pros, and everyone in between. Register Now.

Home > Success Center > Netflow Traffic Analyzer (NTA) > NTA 4.2.3 Administrator Guide > NTA settings > Best practices for NTA Flow Storage Database backups

Best practices for NTA Flow Storage Database backups

Considerations when scheduling backups

  • Higher utilization of resources: During the backup, your computer resources may be more utilized.
  • Initial backups take longer: The first database backup includes all data and is more time-consuming than further regular backups. If you migrate your data from a SQL database to the Flow Storage Database, the first backup after the migration takes longer because the database contains the migrated data.
  • Backups and update operations do not run simultaneously: If you launch an update operation when a backup is in progress, the updates are applied after the backup completes. If there is an update operation running when the backup starts, the backup will start after the update finishes. Update operations include:
    • Changing the status of applications from monitored to unmonitored, or from unmonitored to monitored.
    • Creating, updating, removing, enabling, or disabling IP groups.
    • Enabling or disabling interfaces.
  • Restoring backups - pick up where you finished last time: Updates are stored in a separate file which is updated regularly. When restoring the backup, NTA applies the most recent update settings on the backed up data. When you restore a backup, you will get your data in the same status as they were before the restore.

Optimize your backups

  • Execute backups at times when the utilization of your network is low, preferably at night.
  • Set high frequency for your backups. Backups are executed incrementally, only the new data are added to the backup. If you therefore set backups for each day, the backup will be executed more smoothly than if you back up your database once a month.
  • Do not use the same physical drive for saving your Flow Storage Database and your backups.
    • Flow Storage Database performance decreases during the backup.
    • If the hard drive fails, you will not be able to restore your database.
  • Do not schedule backups at the same time as maintenance. Both maintenance and backup are performance-intensive processes and running them at the same time may have a negatively affect SolarWinds NTA.

Last modified