GMS/Analyzer 8.2 FAQ on Reporting Database Version 1 2:00 PM Jan 10, 2017

Transcription

1 GMS/Analyzer 8.2 FAQ on Reporting Database Version 1 2:00 PM Jan 10, 2017 Contents What 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?... 4 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? What will happen if there is not enough space to run the data migration? Can I continue with Reporting Database Version 1?... 12

2 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 above, available to all new customers or deployments as of Dec 23, 2015 and will have access to only GMS 8.1 release. How does this look in MySonicWALL Download Center? Virtual Appliance I. SW 8.2 GMS/Analyzer Rv2 VA 950GB 250GB 40GB 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.2 II. SW 8.2 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.1 to GMS 8.2 Reporting Database Version 2 or GMS 8.1 Reporting Database Version 2 that were already migrated under 8.1 III. SW 8.2 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.2 and continue with Reporting Database Version 1 Windows

3 The naming convention is the same for Windows binaries as well Rv2 for Reporting Database Version 2 The same binary is used for both Upgrade and Fresh installation as well and the installer will present you with the various options as follows: o Continue to use Reporting Database Version 1 o Upgrade to Reporting Database Version 2 and migrated the data 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 will be contacted by customer for Licensing violations. What will happen to existing deployments as of GMS 8.1 and below? Existing GMS 8.1 will have 2 options available to them. Option 1: Already Upgraded to Reporting Database Version 2 while moving from 8.0 to 8.1, the upgrade process is standard. Option 2: Upgrade from GMS 8.1 with Reporting Database Version 1 will have the following options: o Continue to use Reporting Database Version 1 o Upgrade to Reporting Database Version 2 and migrated the data Which file should I use to upgrade my GMS 8.1? 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: For Windows: SW 8.1 GMS/Analyzer VA Upgrade SW 8.1 GMS/Analyzer Windows 2. Option 2: Upgrade to Reporting Database Version 2 (Rv2) For Virtual Appliance: For Windows system: SW 8.1 GMS/Analyzer Rv2 VA Upgrade SW 8.1 GMS/Analyzer Rv2 Windows

4 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

5 2. Application->Console->Help->About Reporting Database Version 2 Report Database Version: PostgreSQL (IB_33928), shared on x86_64-unknown-linux-gnu, compiled by gcc (GCC) (Red Hat ), 64-bit Reporting Database NO Reference at all Will the reporting data 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: Software Download: Alert is displayed outlining the Dependencies, Data Migration Dependencies for Upgrades from Release Notes Software Download: Alert is displayed outlining the Dependencies, Data Migration Dependencies for Upgrades from Release Notes SP1 Release Notes has instruction on the 8.1 upgrade in Pre 8.1 Upgrade Preparation Hotfix # Release Notes has instruction on the 8.1 upgrade in Pre 8.1 Upgrade Preparation Are there any dependencies for GMS 8.2 upgrades? Yes Hot Fix Please Reboot the systems after installing this Hot Fix Report data migration from RV1 to RV2 should have been completed. The status of the migration can be verified by logging into Reporting UI What happens if any of the dependencies are missed? There is NO loss to any data. You will have to call Technical Support to recover. What is the Upgrade path to 8.2 Rv2? Preferred order of upgrade Rv2->8.1 Hot Fix >8.2 Rv > > 8.0 Super Hot fix > 8.1 Rv2 (Wait for Data Migration to complete Log into Reports UI to check the status)->8.1 Hot Fix (Reboot System)->8.2 Rv2

6 > > 8.1 Rv2(Wait for Data Migration to complete Log into Reports UI to check the status)->8.1 Hot Fix (Reboot System)->8.2 Rv > 8.1 Rv2(Wait for Data Migration to complete Log into Reports UI to check the status)- >8.1 Hot Fix (Reboot System)->8.2 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 Rv2 2. 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 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 host server, use the URL below. Where (x.x.x.x) is the GMS / Analyzer server IP: or Upon logging in, you will be on the System Management page

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

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

9 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

10 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 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

11 Step 6: Applying 8.1 upgrade file Click on the browse button and select the file gmsvp-updater-patch 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. or (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 :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 :37:46 GMSDev-IEE-PGSQL 0.0 sfm:12940 uf:0 et:0.00 nrq:0 cpu:0.0 execlog:"success!" Windows:

12 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.