GMS 8.1 – FAQ on Reporting Database Version 3 – 8:12 PM Jan

4, 2016ContentsWhat is Reporting Database Version 2?......................................................................................................2

How does this look in MySonicWALL Download Center?............................................................................2

What will happen to existing deployments as of GMS 8.0 and below?.......................................................3

Which file should I use to upgrade my GMS 8.0?........................................................................................3

How do I know which version of the Reporting Database the customer is running?..................................3

Will the reporting data collected under previous versions migrated to Reporting Data Version 2?...........5

Are there any dependencies for GMS 8.1 upgrades?..................................................................................5

What happens if any of the dependencies are missed?..............................................................................5

What is the Upgrade path to 8.1 Rv2?.........................................................................................................5

How to upgrade to 8.1 Rv2?........................................................................................................................6

How do I know the status of the Reporting Data Migration from 8.0 to 8.1 Rv2?.....................................11

What will happen if there is not enough space to run the data migration?..............................................12

Can I continue with Reporting Database Version 1?..................................................................................12

What is Reporting Database Version 2?With Infobright version 4.8, the reporting database vendor has replaced the storage engine MySQL with Postgres. This is integrated into GMS 8.1 and all new customer or deployments as of Dec 23, 2015 will have access to only GMS 8.1 release.

How does this look in MySonicWALL Download Center? Virtual Appliance

I. SW 8.1 GMS/Analyzer Rv2 VA 950GB – The Rv2 in the name of the link indicates it is Reporting Database Version 2. This binary is used for new installations of GMS 8.1

II. SW 8.1 GMS/Analyzer Rv2 VA Upgrade – The keyword Upgrade in the name of the link indicates upgrade. This binary is used for upgrading existing deployments of GMS 8.0 to GMS 8.1 Reporting Database Version 2

III. SW 8.1 GMS/Analyzer VA Upgrade – Since there is NO mention of reporting database version, this binary is the original reporting database introduced with GMS 7.0. This binary is used for upgrading existing deployments of GMS 8.0 and continue with Reporting Database Version 1

Windows

The naming convention is the same for Windows binaries as well – Rv2 for Reporting Database Version 2

The same binary is used for Upgrade and Fresh installation as well

Note: The Windows version of Original Reporting database allows for fresh installation of GMS/Analyzer. However, we do track the registrations on the backend for any violations of new installations of GMS/Analyzer running Reporting Database Version after Jan 1, 2016 in the backend and contact the customer for License violations.

What will happen to existing deployments as of GMS 8.0 and below? Existing GMS 8.0 will have 2 options available to them.

Option 1: Upgrade to GMS 8.1 and continue with Reporting Database Version 1

Option 2: Upgrade to GMS 8.1 Reporting Database Version 2

Which file should I use to upgrade my GMS 8.0? You should first make a decision on whether to continue with Reporting Database Version 1 or upgrade to Reporting Database Version 2 introduced with GMS 8.1 release.

1. Option 1: Continue with Reporting Database Version 1

For Virtual Appliance: SW 8.1 GMS/Analyzer VA Upgrade

For Windows: SW 8.1 GMS/Analyzer Windows

2. Option 2: Upgrade to Reporting Database Version 2 (Rv2)

For Virtual Appliance: SW 8.1 GMS/Analyzer Rv2 VA Upgrade

For Windows system: SW 8.1 GMS/Analyzer Rv2 Windows

How do I know which version of the Reporting Database the customer is running? Multiple locations:

1. UMH->Deployment->Services

Reporting Database II for – Rv2

Reporting Database

2. Application->Console->Help->About

Reporting Database Version 2

Report Database Version:

PostgreSQL 9.2.2 (IB_33928), shared on x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.1.2 20080704 (Red Hat 4.1.2-44), 64-bit

Reporting Database – NO Reference at all

Will the reporting data collected under previous versions migrated to Reporting Data Version 2?Yes. By DEFAULT, the data is migrated automatically after upgrade. However, the user has options to control the amount of data to be migrated and disk space requirement. This is clearly explained in the following 4 locations:

1. 8.1 Software Download: Alert is displayed outlining the Dependencies, Data Migration Dependencies for Upgrades from 8.0

2. 8.1 Release Notes3. 8.0 SP1 Release Notes has instruction on the 8.1 upgrade in “Pre 8.1 Upgrade Preparation”4. 8.0 Hotfix #167675 Release Notes has instruction on the 8.1 upgrade in “Pre 8.1 Upgrade

Preparation”

Are there any dependencies for GMS 8.1 upgrades? Yes.

1. 8.0 SP12. 8.0 Super Hot Fix 167675

What happens if any of the dependencies are missed?There is NO loss to any data. However, the dependencies have some fixes that will help the Pre-Upgrade planning a bit easier.

With 8.0 SP1 + Hot Fix 167675 the /appliance/techSupport.html will have the following information:

Pending – Screen shot of the image

With 8.0 SP1 the /appliance/techSupport.html will have the following information:

Pending – Screen shot of the image

With 8.0 SP1 the /appliance/techSupport.html will have the following information:

Pending – Screen shot of the image

What is the Upgrade path to 8.1 Rv2?Preferred order of upgrade

1. 8.0 -> 8.0.1 -> 8.0 Super Hot fix 167675-> 8.1 Rv22. 8.0 -> 8.0.1 -> 8.1 Rv23. 8.0 -> 8.1 Rv2

How to upgrade to 8.1 Rv2?Upgrade to 8.1 Rv2 is a 2 step process.

1. Getting prepared for Report Database migration to Rv22. Applying upgrade to 8.1 Rv2

Phase 1: Getting prepared for Reporting Database migration to RV2

To complete this phase, Make sure that you have already installed the 8.0 SP1 & the HF 167675 before proceeding. Follow below steps to complete this phase 1

Step 1: Log into the Dell SonicWALL Universal Management Host (UMH) System Management Interface

Note: The Dell SonicWALL Universal Management Host (UMH) System Management Interface user/password maybe different from Dell SonicWALL GMS Management Interface user/password.

To access the UMH system management interface on the default HTTP port using a browser on the hostserver, use the URL below. Where (x.x.x.x) is the GMS / Analyzer server IP:

http://localhost/appliance/ or http:// x.x.x.x /appliance/

Upon logging in, you will be on the System Management page

This is for system management of the host server, including registration and licensing, setting the admin password, selecting the deployment role, and configuring other system settings.

Step 2: Access the GMS Tech Support page

To access the Tech Support page Change URL as below. The Tech Support URL takes you to the Tech Support warning page.

http://x.x.x.x/appliance/techSupport.html

Click the Accept button to access the Technical Support page and Scroll down to "Reporting Data Migration from MySQL to Postgres Database engine" section.

Step 3: Data Migration options

There are three data migration options available to choose from.

Option 1:Migrate the Data – (this is the default option)

The drop down box for "Do you want to migrate the data for the following months:"- auto set to Yes

No need to select data, all data will be migrated Click on Migrate

Option 2:Migrate the Data but choose the number of months to migrate

The drop down box for "Do you want to migrate the data for the following months:"- set to Yes Select the check boxes for the months to migrate Click on Migrate

Option 3:Do not migrate the data

The drop down box for "Do you want to migrate the data for the following months:"- set to No. Note: This will not migrate the existing data to new database but the New data will load into the new Reporting database (RV2)

Click on Migrate

Note: Clicking on ‘Migrate’ button will not start the data migration but will set the configuration option in the GMS to process the data accordingly (per options above) when applying upgrade to 8.1

By choosing one of the above options, GMS / Analyzer system is now configured and ready to upgrade to 8.1 RV2.

Phase 2: Upgrading to 8.1 RV2 (data migration)

After setting the data migration options above in phase 1, now Continue on to steps below to upgrade to 8.1 RV2.

Note: During following steps the actual data migration will take place and is subjected to the settings you choose earlier for migration. The process of data migration may take longer and you may not be able to view any of the reporting data until the migration process is completed.

Step 4: Login to the Mysonicwall account and download and save the corresponding file from the link ‘SW 8.1 GMS/Analyzer Rv2 VA Upgrade’

Step 5: Login to UMH (/appliance) page using http://localhost/appliance/Now click on Home button to go back to the UMH (/appliance) page. If you already logged out then log back into the Dell SonicWALL Universal Management Host (UMH) System Management Interface and go to System > Settings page

Step 6: Applying 8.1 upgrade file

Click on the browse button and select the file ‘gmsvp-updater-patch-8.1.8109.1184-release-IB-pg.sh’ and click on ‘Apply’

Once the patch is applied the system will reboot and

Step 6: After the system reboot, login to the main interface.

http://localhost/sgms or http:// x.x.x.x /sgms (x.x.x.x is IP of GMS / Analyzer system)

How do I know the status of the Reporting Data Migration from 8.0 to 8.1 Rv2?After the upgrade is done, login to the GMS > Firewall > Reports panel and if you see screen as below then data migration is still running. To get more details check the advance steps listed below.

The message in the above screen not necessarily mean issue with the ‘Reports Database’ service as the message could be due to data migration. Also the ‘Reports Database’ service on agent will not be running until the migration process is completed.

Note: Please check the migration logs first before restarting the service/s.

Advanced Steps: Check the following logs for the status on the data migration and lookout for below log entries.

IB-EMI-008e9 N 2015-11-30.13:37:36 GMSDev-IEE-PGSQL 0.0 sfm:12940 uf:0 et:0.00 nrq:0 cpu:0.0 execlog:"Creating table public.raw_201511"

IB-EMI-008dc N 2015-11-30.13:37:46 GMSDev-IEE-PGSQL 0.0 sfm:12940 uf:0 et:0.00 nrq:0 cpu:0.0 execlog:"Success!"

Windows:

Virtual Appliance:

/var/lib/Infobright_pg/ib_data/ibmigator.log

Windows:

<install drive>\GMSVP\infobright_pg\ib_data\ibmigrator.log

In case of distributed deployment, you may be able to see such screen as below which points out that migration / upgrade is not yet completed on one of the GMS system. In that case, please check and verify the logs on the agent/s.

What will happen if there is not enough space to run the data migration?

Migration will stop if the system does not have enough disk space. StdAppliance log file will show the error message (existing code)

Can I continue with Reporting Database Version 1?Yes.

Existing customers who have GMS deployments UP and Running as of Dec 31, 2015 can choose to continue with Reporting Database Version 1. They also can add new agents to the existing deployments and also re-install the deployment. The key timeline is the Date of Registration of GMS 8.0 and below.