Difference between revisions of "Backup and Restore a GigaFlow Configuration"

From Observer GigaFlow Support | VIAVI Solutions Inc.
Jump to: navigation, search
Line 4: Line 4:
 
After making changes to the GigaFlow server’s configuration, it’s important to make a backup of the configuration.
 
After making changes to the GigaFlow server’s configuration, it’s important to make a backup of the configuration.
  
−
Using Windows:
+
All settings made to Gigaflow are store in the Postgresql database. As such, it is necessary to use the Postgres pg_dump command to perform the backups.
  
−
# Open a Windows command prompt as administrator.
+
For windows, this will will be installed in the Postgres installation folder.
−
# Assuming that the PostgreSQL path has been added to windows, you can run the pg_dump command below directly. If not, either add it to the path or change the active directory to <code>C:\Program Files\PostgreSQL\X.X\bin</code>, where X.X is the PostgreSQL revision, e.g 9.5.
+
To find this folder, open up the services panel in windows.
−
# Run: <br /><code>"D:\Program Files\PostgreSQL\10\bin\pg_dump.exe" --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 -U myipfix -f c:/temp/GigaFlowConfigBackup.sql</code>
+
Find the postgresqlXXXXX service
−
# You may be prompted for the database password, i.e. <strong>myipfix</strong>. This will create the file GigaFlowConfigBackup.sql in the active directory. Move this to wherever you archive configurations.
+
Right click on it, 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 instructions below
 +
 
 +
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 instructions below.
 +
 
 +
 
 +
Backing up
 +
 
 +
# Run: <br /><code>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 -U myipfix -f GigaFlowConfigBackup.sql</code>
 +
# You may be prompted for the database password, i.e. <strong>myipfix</strong>. This will create the file GigaFlowConfigBackup.sql in the current directory. Move this to wherever you archive configurations.
  
 
== Restoring From a GigaFlow Configuration Backup ==
 
== Restoring From a GigaFlow Configuration Backup ==
Line 15: Line 30:
 
<strong>Warning: the following process will drop the existing database on the server.</strong>
 
<strong>Warning: the following process will drop the existing database on the server.</strong>
  
−
# Stop the GigaFlow service (GigaFlow.exe for windows or /etc/init.d/rosd for linux).
+
# Stop the GigaFlow service (GigaFlow for windows or /etc/init.d/rosd for linux).
 
# Upload the required GigaFlowConfigBackup.sql file to the machine.
 
# 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 "drop database myipfix" postgres '''//Only if getting rid of old data, you will have to "\c postgres" first and make sure gigaflow is stopped'''

Revision as of 09:24, 12 July 2023

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 store in the Postgresql database. As such, it is necessary to use the Postgres pg_dump command to perform the backups.

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 on it, 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 instructions below

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 instructions below.


Backing up

  1. 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 -U myipfix -f GigaFlowConfigBackup.sql
  2. 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.

  1. Stop the GigaFlow service (GigaFlow for windows or /etc/init.d/rosd for linux).
  2. Upload the required GigaFlowConfigBackup.sql file to the machine.
  3. 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
  4. psql --host=127.0.0.1 --username=myipfix -c "create database myipfix owner=myipfix" postgres
  5. psql --host=127.0.0.1 --username=myipfix < ./GigaFlowConfigBackup.sql
  6. You may be prompted for the database password, i.e. myipfix.
  7. Restart GigaFlow.


  1. 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')"
Retrieved from "https://gigaflowsupport.viavisolutions.com/index.php?title=Backup_and_Restore_a_GigaFlow_Configuration&oldid=1988"