Difference between revisions of "Backup and Restore a GigaFlow Configuration"
From Observer GigaFlow Support | VIAVI Solutions Inc.
Line 3: | Line 3: | ||
It is important to create a backup of the configuration after you did the changes to the GigaFlow server’s configuration. | It is important to create a backup of the configuration after you did the changes to the GigaFlow server’s configuration. | ||
− | = | + | = Create a GigaFlow configuration backup for use on a new server on Windows = |
All the settings made to Gigaflow are stored in the '''Postgresql''' database. Thus, it is necessary to use the Postgres <code>pg_dump</code> command to perform the backup. | All the settings made to Gigaflow are stored in the '''Postgresql''' database. Thus, it is necessary to use the Postgres <code>pg_dump</code> command to perform the backup. | ||
− | == Find the binaries for | + | == Find the binaries for Windows == |
The binaries will be installed in the '''Postgres''' installation folder. To find this folder, perform the following steps: | The binaries will be installed in the '''Postgres''' installation folder. To find this folder, perform the following steps: | ||
Line 25: | Line 25: | ||
== How to restore from a GigaFlow configuration backup == | == How to restore from a GigaFlow configuration backup == | ||
− | <strong> | + | <strong>Caution:</strong> The following process will drop the existing database on the server. |
− | # Stop the GigaFlow service | + | # In the '''Stop (Local)''' list, right-click the '''GigaFlow''' service and select the '''Stop''' option. |
# 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 | + | # If you want to delete the old data, then perform the following steps: |
+ | ## you will have to "\c postgres" first and make sure gigaflow is stopped''' run the following commands psql --host=127.0.0.1 --username=myipfix -c "drop database myipfix" postgres ''' | ||
# psql --host=127.0.0.1 --username=myipfix -c "create database myipfix owner=myipfix" postgres | # psql --host=127.0.0.1 --username=myipfix -c "create database myipfix owner=myipfix" postgres | ||
# <code>psql --host=127.0.0.1 --username=myipfix < ./GigaFlowConfigBackup.sql<br /> | # <code>psql --host=127.0.0.1 --username=myipfix < ./GigaFlowConfigBackup.sql<br /> | ||
Line 37: | Line 38: | ||
# Run the following command if you want to reset the '''serverid''' on a new box:<br />psql --host=127.0.0.1 --username=myipfix -c "delete from serverparams where key in('serverid','installtime','license')"</code> | # Run the following command if you want to reset the '''serverid''' on a new box:<br />psql --host=127.0.0.1 --username=myipfix -c "delete from serverparams where key in('serverid','installtime','license')"</code> | ||
+ | = Create a GigaFlow configuration backup for use on a new server on Linux = | ||
+ | All the settings made to Gigaflow are stored in the '''Postgresql''' database. Thus, it is necessary to use the Postgres <code>pg_dump</code> command to perform the backup. | ||
+ | == Find the binaries for Linux == | ||
− | |||
# Open a terminal window with suitable permissions. | # Open 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/'''. | # 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. | # Here, '''"/usr/pgsql-11/bin/"''' is the location of the required file, change into that directory and follow the backup/restore instructions below. | ||
+ | |||
+ | == How to create a backup == | ||
+ | |||
+ | # In the administrator command prompt shell, run the following command:<br /><code>pg_dump -E UTF8 --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 --table=aws_s3_bucket_config --table=awsconnections --table=cloudinstancetoip --table=fwevent --table=fwextcode --table=fwextcodestoappids --table=netflowignores --table=statnames --host=127.0.0.1 -U myipfix -f GigaFlowConfigBackup.sql</code> | ||
+ | # You may be prompted for the database password, that is <strong>myipfix</strong>.<br />This will create the file '''GigaFlowConfigBackup.sql''' in the current directory. | ||
+ | # Move the '''GigaFlowConfigBackup.sql''' file to the location where you store the archive configurations. | ||
+ | |||
+ | == How to restore from a GigaFlow configuration backup == | ||
+ | |||
+ | <strong>Warning: the following process will drop the existing database on the server.</strong> | ||
+ | |||
+ | # Stop the GigaFlow service (GigaFlow for windows or <code>systemctl stop rosd</code> 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 | ||
+ | # <code>psql --host=127.0.0.1 --username=myipfix < ./GigaFlowConfigBackup.sql<br /> | ||
+ | # You may be prompted for the database password, i.e. <strong>myipfix</strong>. | ||
+ | # Restart GigaFlow. | ||
+ | |||
+ | # Run the following command if you want to reset the '''serverid''' on a new box:<br />psql --host=127.0.0.1 --username=myipfix -c "delete from serverparams where key in('serverid','installtime','license')"</code> |
Revision as of 08:45, 23 October 2023
It is important to create a backup of the configuration after you did the changes to the GigaFlow server’s configuration.
Contents |
Create a GigaFlow configuration backup for use on a new server on Windows
All the settings made to Gigaflow are stored in the Postgresql database. Thus, it is necessary to use the Postgres pg_dump
command to perform the backup.
Find the binaries for Windows
The binaries will be installed in the Postgres installation folder. To find this folder, perform the following steps:
- Open the Services application in Windows.
- In the Services (Local) list, find the postgresqlXXXXX service.
- Right-click the postgresqlXXXXX service, and select the Properties option.
- From the General tab, copy the "path to executable" string.
Note: This folder is the location required to run the backup and restore commands on (for example, D:\Program Files\PostgreSQL\11\bin\). - Open an administrator command prompt shell, and change the current working directory to that folder.
How to create a backup
- In the administrator command prompt shell, run the following command:
pg_dump -E UTF8 --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 --table=aws_s3_bucket_config --table=awsconnections --table=cloudinstancetoip --table=fwevent --table=fwextcode --table=fwextcodestoappids --table=netflowignores --table=statnames --host=127.0.0.1 -U myipfix -f GigaFlowConfigBackup.sql
- You may be prompted for the database password, that is myipfix.
This will create the file GigaFlowConfigBackup.sql in the current directory. - Move the GigaFlowConfigBackup.sql file to the location where you store the archive configurations.
How to restore from a GigaFlow configuration backup
Caution: The following process will drop the existing database on the server.
- In the Stop (Local) list, right-click the GigaFlow service and select the Stop option.
- Upload the required GigaFlowConfigBackup.sql file to the machine.
- If you want to delete the old data, then perform the following steps:
- you will have to "\c postgres" first and make sure gigaflow is stopped run the following commands psql --host=127.0.0.1 --username=myipfix -c "drop database myipfix" postgres
- 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 the following command if you want to reset the serverid on a new box:
psql --host=127.0.0.1 --username=myipfix -c "delete from serverparams where key in('serverid','installtime','license')"
Create a GigaFlow configuration backup for use on a new server on Linux
All the settings made to Gigaflow are stored in the Postgresql database. Thus, it is necessary to use the Postgres pg_dump
command to perform the backup.
Find the binaries for Linux
- Open 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.
How to create a backup
- In the administrator command prompt shell, run the following command:
pg_dump -E UTF8 --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 --table=aws_s3_bucket_config --table=awsconnections --table=cloudinstancetoip --table=fwevent --table=fwextcode --table=fwextcodestoappids --table=netflowignores --table=statnames --host=127.0.0.1 -U myipfix -f GigaFlowConfigBackup.sql
- You may be prompted for the database password, that is myipfix.
This will create the file GigaFlowConfigBackup.sql in the current directory. - Move the GigaFlowConfigBackup.sql file to the location where you store the archive configurations.
How to restore 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
systemctl stop 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 the following command if you want to reset the serverid on a new box:
psql --host=127.0.0.1 --username=myipfix -c "delete from serverparams where key in('serverid','installtime','license')"