Backup and Restore a GigaFlow Configuration
Contents |
Creating a GigaFlow Configuration Backup For Use On A New Server
After making changes to the GigaFlow server’s configuration, it’s important to make a backup of the configuration.
All settings made to Gigaflow are stored in the Postgresql database. Consequently, it is necessary to use the Postgres pg_dump command to perform the backups.
Below you will find instructions for Windows and Linux on how to find where the binaries are:
Binaries For windows
This will will be installed in the Postgres installation folder.
- To find this folder, open up the services panel in Windows.
- Find the postgresqlXXXXX service.
- Right click the postgresqlXXXXX service, and note the "path to executable". This is the location required to run the next commands on (e.g. D:\Program Files\PostgreSQL\11\bin\).
Open an administrator command prompt, change to that folder and follow the backup/restore instructions below
Binaries For Linux
Open up a terminal window with suitable permissions
Run the following command "ps aux | grep postmaster"
you should get an output similar to
postgres 1834 0.0 0.4 17464052 443692 ? Ss Jul10 0:02 /usr/pgsql-11/bin/postmaster -D /var/lib/pgsql/11/data/
Here, "/usr/pgsql-11/bin/" is the location of the required file, change into that directory and follow the backup/restore instructions below.
Backing up
- Run:
pg_dump --table=attributecategories --table=attributevalues_0 --table=attributevalues_1 --table=attributevalues_2 --table=attributevalues_3 --table=attributevalues_4 --table=attributevalues_5 --table=attributevalues_6 --table=blacklistslocal --table=blacklistslocalentries --table=blacklistsources --table=customerdevicesettings --table=customersettings --table=dataaccessgroupmembers --table=dataaccessgroups --table=definedapplications --table=deviceinterfaces --table=devices --table=eventtriggers --table=eventtypes --table=flowobjects --table=forensicsreports --table=geoips --table=gigastors --table=integrations --table=interfacefilters --table=interfacealertsettings --table=interfacetypes --table=ldapgroups --table=ldapusers --table=ldapnestedgroups --table=multiservertargets --table=networkaudits --table=pentypes --table=penvendors --table=portalusers --table=portparams --table=profilers --table=profilerstoallowedprofiles --table=profilerstoentryprofiles --table=queryfielderservers --table=reportlinks --table=reportnameoverrides --table=savedreports --table=serverparams --table=serversubnetport --table=serversubnets --table=snmppollerclasses --table=snmppollerclassesforsysoid --table=sqlreports --table=standardapplications --table=stattypes --table=syslogprocessors --table=syslogprocessorsdefault --table=trafficgroups --table=trafficgroupsdeployed --table=trafficgroupsubnets --table=eventrunners --table=eventrunners_versioned --table=definedservers --table=usergroups --table=userldapsettings --table=userpermissions --table=users --table=whitelist --host=127.0.0.1 -U myipfix -f GigaFlowConfigBackup.sql
- You may be prompted for the database password, i.e. myipfix. This will create the file GigaFlowConfigBackup.sql in the current directory. Move this to wherever you archive configurations.
Restoring From a GigaFlow Configuration Backup
Warning: the following process will drop the existing database on the server.
- Stop the GigaFlow service (GigaFlow for windows or /etc/init.d/rosd for linux).
- Upload the required GigaFlowConfigBackup.sql file to the machine.
- psql --host=127.0.0.1 --username=myipfix -c "drop database myipfix" postgres //Only if getting rid of old data, you will have to "\c postgres" first and make sure gigaflow is stopped
- psql --host=127.0.0.1 --username=myipfix -c "create database myipfix owner=myipfix" postgres
-
psql --host=127.0.0.1 --username=myipfix < ./GigaFlowConfigBackup.sql
- You may be prompted for the database password, i.e. myipfix.
- Restart GigaFlow.
- Run below if you want to reset serverid on a new box:
psql --host=127.0.0.1 --username=myipfix -c "delete from serverparams where key in('serverid','installtime','license')"