Data Backup and Restoration

Periodically backing up the database is very essential, as it helps you restore Network Configuration Manager service back during planned maintenance as well as unplanned mishaps. Network Configuration Manager database contains two types of data:
Performance data: This is the data gathered by  Network Configuration Manager by periodically polling or querying the resources on a monitored device to determine its performance. This includes resources like CPU, Memory, Response time, Traffic etc.
Configuration data: There are quite a few configurations an administrator effects in Network Configuration Manager  for easy management and monitoring. The configurations include user settings, details of discovered devices, custom monitors, threshold settings, notification profiles, etc. Most configuration data is persisted in the database while a few configurations are written in conf files. So when you backup configuration data, you must take care to back up the ones you need.

Backup & restoration steps for Network Configuration Manager


Following table lists the backup utilities bundled with Network Configuration Manager and their purpose. Make sure you use the one that fits your backup need:                     Utility    Path Database           Purpose

BackupDB.bat (for windows) (for linux)

network-configuration-manager\bin\backup Mysql | MSSQL | PGSQL This utility does a backup of the complete database, viz., performance and configuration data.

BackupDB.bat -mode configdata (for windows) -mode configdata (for linux)

network-configuration-manager\bin\backup Mysql | MSSQL | PGSQL Use this tool if you want to backup only the configuration data with this we backup Conf, Images folder and get the details of Devices, Device Templates, Interfaces, Interface Template, Dashboards & Widgets, Infrastructure Views, Business Views, Credentials, Notification Profiles, Users but not the performance data.



To restore the backed up data,
Go to <network-configuration-manager Home>/bin/backup directory
Execute RestoreDB.bat (use for linux) with the backup file name as argument. See example below:
C:\<network-configuration-manager Home>\bin\backup>RestoreDB.bat "network-configuration-manager\backup\"
To restore the backed up data for MSSQL
Go to <network-configuration-manager Home>/bin/backup directory
Restore the data using RestoreDB.bat present under network-configuration-manager/bin/backup directory and restart network-configuration-manager.
For ex : C:\<network-configuration-manager Home>\bin\backup>RestoreDB.bat "c:\network-configuration-manager\backup\"
Important Note : If your migrating the database from PostgreSQL or MySQL to MSSQL, please follow the steps below.
Download the SQL Native Client from the link below. You will need to scroll down the page for the Native Client downloads: Microsoft SQL Server 2008 R2 Native Client (SQL Server Native Client) is a single dynamic-link library (DLL) containing both the SQL OLE DB provider and SQL ODBC driver. It contains run-time support for applications using native-code APIs (ODBC, OLE DB and ADO) to connect to Microsoft SQL Server 2000, 2005, or 2008. SQL Server Native Client should be used to create new applications or enhance existing applications that need to take advantage of new SQL Server 2008 R2 features. This redistributable installer for SQL Server Native Client installs the client components needed during run time to take advantage of new SQL Server 2008 R2 features, and optionally installs the header files needed to develop an application that uses the SQL Server Native Client API.                                  
X86 Package (sqlncli.msi) X64 Package (sqlncli.msi) IA64 Package (sqlncli.msi)
For more details on installing the native client, refer this site:
 Here is a quick video of SQL Native client installation.
Find the files bcp.exe and bcp.rll in MSSQL server and ensure to copy it under Network Configuration Manager home folder. If the MSSQL server is installed on a 64-bit OS, and Network Configuration Manager is installed on 32-bit server, the bcp.exe and bcp.rll copied from the MSSQL server will not work on the Network Configuration Manager machine. You'll need a 32-bit bcp.exe and bcp.rll.
While restoring the backup, the tables that are dropped or retained varies according to the backup file restored:

BackupDB.bat/sh: During restoration, all the existing tables are dropped, new tables are created, and the data are restored.

BackupDB.bat/sh -Mode configdata: During restoration, all the existing tables are dropped, new tables are created, and only the configuration data are restored.


Was this article helpful?