Scrutinizer Upgrade Instructions

Scrutinizer is an enterprise/business class NetFlow and sFlow analysis tool. Scrutinizer provides historical trends of the company's critical network interfaces as well as the details on:

Who: The end system causing the traffic
What: The application/protocol that is being used
When: The time frame it has been occurring for
Where: The network connection that is affected

Moderators: scottr, Moderator Team

Post Reply
User avatar
tomp
Site Admin
Posts: 315
Joined: Wed Jul 27, 2005 10:53 am
Location: Sunny Sanford Maine
Contact:

Scrutinizer Upgrade Instructions

Post by tomp » Tue May 17, 2011 1:59 pm

Scrutinizer v.6 to v.7 Upgrade Instructions

The Scrutinizer upgrade including historical data is conducted in 2 phases. The application upgrade does not automatically bring forward historical data or configurations. The decision is left up to the administrator whether or not the historical and configuration data will be brought forward. The application must first be upgraded by running the Scrutinizer installer downloaded from plixer.com

After the application upgrade is complete, the user can then choose to bring forward the configurations and historical data to the new version. This process is done by running a utility that creates new databases that work with the new Scrutinizer schema by copying data from the old ones.

This is designed to be an optional process because converting hundreds of GBs of data can take a substantial amount of time to complete. The time involved to complete also depends on whether existing 1 minute data points are to be included or not.

What exactly is carried over with the historical data upgrade?
This utility will migrate Scrutinizer v6.x data to v7.x data. The following
information will be imported from v6:
- Historical Flow Data
- Maps / Groups
- Denika Connections
- SNMP Credentials
- Custom Device Names
- Custom Interface Names and Speeds

The following will not be imported due to the enhancements to v7:
- Existing Alarms
- User accounts
- Custom Applications
- Custom Reports and Scheduled Reports
- System Configuration (Admin Preferences)
- 3rd party integration
- Flow Analytic Configurations
- Mail Server Information
- syslog server
- Gadgets
- License Information

What should I backup prior to the upgrade?
Any important information needed from the list of items not imported by the historical data upgrade should be documented. This will make the process much easier.

The files and folders to be backed up are in the following instructions.

Configuration and Historical Data Migration of Scrutinizer v6.x to v7.x
The following instructions are for those who wish to migrate historical data and configurations on the same server (Not moving Scrutinizer to a different server). If Scrutinizer is to be moved to a different server, see instructions for the remote database migration further in the document.

You must have at least 3 times hard drive space used by the Scrutinizer database available for a successful data upgrade.

**You cannot upgrade a 6.x Scrutinizer installation if Denika/Logalot are installed on the same server unless you are willing to put Scrutinizer on a different server.**
* Internet Explorer 6 is not supported in Scrutinizer v7 – Use firefox or later version of Internet Explorer for best results*

Instructions for Configuration and Data upgrade on the same server
1) Stop scrutinizer_MySQL and dependent services on v6 server
2) Move (ie not copy)"\scrutinizer\mysql\data\scrutinizer_*" folder to a backup folder
3) copy the "\scrutinizer\mysql\data\scrutinizer" folder to a backup folder
4) copy the "\scrutinizer\html\gadgets\" folder to a backup folder
5) copy the "\scrutinizer\html\conf.cgi" file to a backup folder
6) Uninstall Flow Analytics for Scrutinizer Netflow Analyzer (if installed)
7) Uninstall Scrutinizer Netflow Analyzer
8) Make sure the v6 services and install folder were removed
A) If some Scrutinizer services remain, such as Scrutinizer collector, filer, or watcher service, read this forum post for removal instructions: http://forums.plixer.com/viewtopic.php?f=15&t=1472
sc delete scrutinizer
sc delete scrutinizer_filed
sc delete scrut_nba_watcher
sc delete scrut_nba_domains
sc delete scrutinizer_mysql
sc delete scrutinizer_apache2
9) Reboot
10) Download and Install latest release of Scrutinizer v7.x
A) Download from: http://www.plixer.com/support/availableUpdates.php


11) Enter licensing information and edit data history settings
A) This information is in the conf.cgi file backed up in step 5.
B) The v6 license key will work in v7. To enter the license in v7, go to Admin->Settings->Licensing, and enter the key in the Flow Analytics license key field.
12) Stop plixer_MySQL service (and dependent services)
13) Move backed up "scrutinizer" and "scrutinizer_*" folders to new \scrutinizer\mysql\data\ folder
14) Start plixer_MySQL, plixer_flow_collector,plixer_watcher,plixer_domain services

15) From an administrative command prompt in the [homedir]\scrutinizer\bin\ folder, run: (including the one minute data is not necessary and does speed up the process)
(Make sure Flow Analytics is turned off prior to running migrate.exe)

A) If not migrating one minute data:
"migrate --migrate"
B) To include one minute data in the migration:
"migrate --migrate --oneMin"

16) keep the command prompt open until it returns to the command line and then it’s ok to close the prompt and celebrate. – You’re done.

******** If the data migration fails to come to normal completion, the following command must be run prior to restarting the migration:
"migrate --retreat"
After correcting whatever caused the migration to fail initially, and running "retreat", then the migration can be restarted. *******

Instructions for Migrating V.6 Configurations and Historical Data to a remote V.7 Scrutinizer Installation

**** Before you stop exporting flows to the version 6.0.x Scrutinizer server, stop the Scrutinizer collector, filer and watcher services ****

1) Install 7.3 on new server
2) Enter licensing information and edit data history settings
3) Enable remote access to the v6 mysql database:
1. Open a DOS command prompt on the Scrutinizer v6 server.
2. Run the following command from the ~\SCRUTINIZER\mysql\bin directory:
mysql -u root --password=
3. A mysql> prompt should be displayed.
4. To create a remote user account with root privileges, run the following commands:
GRANT ALL PRIVILEGES ON *.* TO 'USERNAME'@'IP' IDENTIFIED BY 'PASSWORD';

'USERNAME' is the username to be created.
'IP' is the public IP address of the remote connection.
'PASSWORD' is the password to be assigned for this username.
(IP can be replaced with % to allow this user to logon from any host or IP)

mysql> FLUSH PRIVILEGES;
mysql> exit;

4) Make sure all flows sent to v6 are being sent to v7
5) From an administrative command prompt in the \scrutinizer\bin\ folder, run:
(Make sure Flow Analytics is turned off prior to running migrate.exe)

a) If not migrating one minute data:

migrate --migrate --v6user MYSQL_REMOTE_USER --v6pass MYSQL_REMOTE_PASS --v6host V6_IP

b) If migrating one minute data:

migrate --migrate --v6user MYSQL_REMOTE_USER --v6pass MYSQL_REMOTE_PASS --v6host V6_IP --oneMin


'MYSQL_REMOTE_USER' is the remote user you created in step 3
'MYSQL_REMOTE_PASS' is the remote password you created for the remote user in step 3
'V6_IP' is the ip address of the v6 server


If you have any questions or problems, please don't hesitate to call support at 207-324-8805 x4

- Tom

User avatar
tomp
Site Admin
Posts: 315
Joined: Wed Jul 27, 2005 10:53 am
Location: Sunny Sanford Maine
Contact:

Scrutinizer Upgrade Instructions

Post by tomp » Tue May 17, 2011 2:00 pm

Scrutinizer v.7.x to v.8.x Upgrade Instructions

The Scrutinizer v7.x to v8.x upgrade has been designed to be an over the top upgrade so users can run the latest installer on the server and be upgraded to the latest release.

Before upgrading a backup is recommended, but not required.
The files and folders to be backed up are in the following instructions.

What should I verify before upgrading?
Verify your "\scrutinizer\mysql\my.ini" contains the tmpdir parameter. If it does not contain tmpdir you must add it by doing the following:
1) Stop the plixer_mysql and dependent services
2) Navigate to the "\scrutinizer\mysql" folder and create a 'tmp' directory
3) Open the "\scrutinizer\mysql\my.ini" file and add the path to the 'tmp' directory you just created. You must use forward slashes in the path instead of back slashes:
a. Example: tmpdir="C:/Program Files/Scrutinizer/mysql/tmp/"
4) Start the plixer_mysql service
a. If the plixer_mysql service does not start then the tmpdir was not created correctly.

The upgrade will not bring over any host names resolved by DNS. If you want to import the custom host names from v7.x into v8.x they can be imported after the upgrade.

Instructions for upgrading Scrutinizer on the same server:
1) Download the latest installer: http://www.plixer.com/support/availableUpdates.php
2) Verify your my.ini file contains the tmpdir if you have not already (see above)
3) Stop the plixer_mysql and dependent services
4) Copy the "\scrutinizer\mysql\data\scrut_*" folders to a backup folder
5) Copy the "\scrutinizer\mysql\data\plixer" folder to a backup folder
6) Start the plixer_mysql service
7) Run Scrutinizer-windows-installer.exe
8 ) If you’re not importing custom host names from v7.x then the upgrade has been completed

How to import custom host names from v7.x:
9) From the command line, navigate to "\scrutinizer\bin" and run "scrut_util –hostmigrate"

Instructions for upgrading and moving Scrutinizer to a different server:
The Scrutinizer database on the old server has to be upgraded before it can be migrated to a new server, so you will need to follow the instructions for upgrading Scrutinizer on the same server that are listed above, and then continue with the instructions below.

IMPORTANT NOTE: These instructions assume the new server will have the same IP address that the old server had. If the new server will have a different IP address you will need to contact Plixer Technical Support 207-324-8805 x4 with the new IP address to get a new license key.

1) Follow the instructions for upgrading Scrutinizer on the same server that are listed above
2) Using the same installer that upgraded the old server, install v8.x on the new server
3) Old server: stop the plixer_mysql and dependent services
4) New server: stop the plixer_mysql and dependent services
5) New server: copy the "\scrutinizer\mysql\data\plixer" folder to a backup location
6) Old server: copy the "\scrutinizer\mysql\data\scrut_*" folders to the same location on the new server
7) Old server: copy the "\scrutinizer\mysql\data\plixer" folder to the same location on the new server
8 ) New server: start the plixer_mysql and dependent services

FAQ
Q) During the upgrade from v7.x to v8.x I got an, “Error unpacking archive” and the installer has stopped. What do I do now?

A) DO NOT abort the install as it will leave Scrutinizer in a non-working state. This is a result of not being able to overwrite the file the installer has errored on. Call Plixer Technical Support 207-324-8805 x4.

User avatar
tomp
Site Admin
Posts: 315
Joined: Wed Jul 27, 2005 10:53 am
Location: Sunny Sanford Maine
Contact:

Scrutinizer v.8.x to v.9.x Upgrade Instructions

Post by tomp » Thu Jan 26, 2012 9:16 am

Scrutinizer v.8.x to v.9.x Upgrade Instructions

The Scrutinizer v8.x to v9.x upgrade has been designed to be an over the top upgrade so users can run the latest installer on the server and be upgraded to the latest release.

Before upgrading a backup is recommended, but not required.
The files and folders to be backed up are in the following instructions.

Instructions for upgrading Scrutinizer on the same server:
1) Download the latest installer: http://www.plixer.com/support/availableUpdates.php
2) Stop the plixer_mysql and dependent services
3) Copy the "\scrutinizer\mysql\data\scrut_*" folders to a backup folder
4) Copy the "\scrutinizer\mysql\data\plixer" folder to a backup folder
5) Start the plixer_mysql service
6) Run Scrutinizer-windows-installer.exe

Instructions for upgrading and moving Scrutinizer to a different server:
The Scrutinizer database on the old server has to be upgraded before it can be migrated to a new server, so you will need to follow the instructions for upgrading Scrutinizer on the same server that are listed above, and then continue with the instructions below.

IMPORTANT NOTE: These instructions assume the new server will have the same IP address that the old server had. If the new server will have a different IP address you will need to contact Plixer Technical Support 207-324-8805 x4 with the new IP address to get a new license key.

1) Follow the instructions for upgrading Scrutinizer on the same server that are listed above
2) Using the same installer that upgraded the old server, install v9.x on the new server
3) Old server: stop the plixer_mysql and dependent services
4) New server: stop the plixer_mysql and dependent services
5) New server: copy the "\scrutinizer\mysql\data\plixer" folder to a backup location
6) Old server: copy the "\scrutinizer\mysql\data\scrut_*" folders to the same location on the new server
7) Old server: copy the "\scrutinizer\mysql\data\plixer" folder to the same location on the new server
8 ) New server: start the plixer_mysql and dependent services

If you experience any problems with your upgrade, don’t hesitate to call Plixer Technical Support 207-324-8805 x4.

pauld
Posts: 222
Joined: Mon Jan 04, 2010 10:05 am
Location: Kennebunk, Maine
Contact:

Re: Scrutinizer Upgrade Instructions

Post by pauld » Fri Oct 26, 2012 10:27 am

Scrutinizer v9.x to v10.x Upgrade Instructions

The Scrutinizer v9.x to v10.x upgrade has been designed to be an over the top upgrade so users can run the latest installer on the server and be upgraded to the latest release.

Before upgrading a backup is strongly recommended, but not required.
The files and folders to be backed up are in the following instructions.

What should I verify before upgrading?
- Does the Scrutinizer server meet the system requirements?
http://www.plixer.com/products/netflow- ... ements.php

Instructions for upgrading Scrutinizer on the same server:
1) Download the latest upgrade installer: http://www.plixer.com/support/availableUpdates.php
2) Make a database backup; if you don’t need a backup, skip to step 7.
3) Stop the plixer_mysql and dependent services (plixer_apache, plixer_domain, plixer_flow_collector, plixer_flowalyzer_svc, plixer_notifyd, plixer_scheduler, plixer_smtpd, and plixer_syslogd)
4) Copy the “\Scrutinizer\mysql\data\scrut_*” folders to a backup folder
5) Copy the “\Scrutinizer\mysql\data\plixer” folder to a backup folder
6) Start the plixer_mysql service
7) Run Scrutinizer-windows-installer.exe

Instructions for upgrading and moving Scrutinizer to a different server

Before migrating Scrutinizer to a new server the old server must be upgraded because the database is only compatible with the same version of Scrutinizer.

IMPORTANT NOTE: These instructions assume the new server will have the same IP address that the old server had. If the new server will have a different IP address you will need to contact Plixer Technical Support 207-324-8805 x4 with the new IP address to get a new license key. It’s recommended to do this before upgrading.

1) On the old server, follow the “Instructions for upgrading Scrutinizer on the same server” for the appropriate version that you have installed.
2) Using the same installer that upgraded the old server, install Scrutinizer on the new server.
3) Old server: stop the services in the following order plixer_apache, plixer_domain, plixer_flow_collector, plixer_flowalyzer_svc, plixer_notifyd, plixer_scheduler, plixer_smtpd, plixer_syslogd and plixer_mysql.
4) New server: stop the services in the following order plixer_apache, plixer_domain, plixer_flow_collector, plixer_flowalyzer_svc, plixer_notifyd, plixer_scheduler, plixer_smtpd, plixer_syslogd and plixer_mysql.
5) New server: copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to a backup location (so you have a backup of the original database)
6) On the old server copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
7) On the old server copy the “[homedir]\scrutinizer\mysql\data\scrut_*” directories to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
8 ) New server: start the services in the following order plixer_mysql, plixer_scheduler, plixer_flow_collector, plixer_syslogd, plixer_smtpd, plixer_notifyd, plixer_domain and plixer_apache.
9) Change the new severs IP addresses, so the new server has the IP address that’s tied to the Scrutinizer license key.


FAQ

Q) During the upgrade I got an, “Error unpacking archive” and the installer has stopped. What do I do now?

A) DO NOT abort the install as it will leave Scrutinizer in a non-working state. This is a result of not being able to overwrite the file that’s included in the error message. Contact your support representative for additional assistance.

Q) I got a "Post Install Script Error" and the installer as stopped. What do I do now?

A) Contact your support representative for additional assistance.

pauld
Posts: 222
Joined: Mon Jan 04, 2010 10:05 am
Location: Kennebunk, Maine
Contact:

Re: Scrutinizer Upgrade Instructions

Post by pauld » Fri Jan 11, 2013 4:43 pm

Scrutinizer v10.x to v10.x Upgrade Instructions

The Scrutinizer v10.x to v10.x upgrade has been designed to be an over the top upgrade so users can run the latest installer on the server and be upgraded to the latest release.

Before upgrading a backup is strongly recommended, but not required.
The files and folders to be backed up are in the following instructions.

What should I verify before upgrading?
- Does the Scrutinizer server meet the system requirements?
http://www.plixer.com/products/netflow- ... ements.php

Instructions for upgrading Scrutinizer on the same server:
1) Download the latest upgrade installer: http://www.plixer.com/support/availableUpdates.php
2) Make a database backup; if you don’t need a backup, skip to step 7.
3) Stop the plixer_mysql and dependent services (plixer_apache, plixer_domain, plixer_flow_collector, plixer_flowalyzer_svc, plixer_notifyd, plixer_smtpd, and plixer_syslogd)
4) Copy the “\Scrutinizer\mysql\data\scrut_*” folders to a backup folder
5) Copy the “\Scrutinizer\mysql\data\plixer” folder to a backup folder
6) Start the plixer_mysql service
7) Run Scrutinizer-windows-installer.exe

Instructions for upgrading and moving Scrutinizer to a different server

Before migrating Scrutinizer to a new server the old server must be upgraded because the database is only compatible with the same version of Scrutinizer.

IMPORTANT NOTE: These instructions assume the new server will have the same IP address that the old server had. If the new server will have a different IP address you will need to contact Plixer Technical Support 207-324-8805 x4 with the new IP address to get a new license key. It’s recommended to do this before upgrading.

1) On the old server, follow the “Instructions for upgrading Scrutinizer on the same server” for the appropriate version that you have installed.
2) Using the same installer that upgraded the old server, install Scrutinizer on the new server.
3) Old server: stop the services in the following order plixer_apache, plixer_domain, plixer_flow_collector, plixer_flowalyzer_svc, plixer_notifyd, plixer_smtpd, plixer_syslogd and plixer_mysql.
4) New server: stop the services in the following order plixer_apache, plixer_domain, plixer_flow_collector, plixer_flowalyzer_svc, plixer_notifyd, plixer_smtpd, plixer_syslogd and plixer_mysql.
5) New server: copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to a backup location (so you have a backup of the original database)
6) On the old server copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
7) On the old server copy the “[homedir]\scrutinizer\mysql\data\scrut_*” directories to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
8 ) New server: start the services in the following order plixer_mysql, plixer_flow_collector, plixer_syslogd, plixer_smtpd, plixer_notifyd, plixer_domain and plixer_apache.
9) Change the new severs IP addresses, so the new server has the IP address that’s tied to the Scrutinizer license key.

FAQ

Q) During the upgrade I got an, “Error unpacking archive” and the installer has stopped. What do I do now?

A) DO NOT abort the install as it will leave Scrutinizer in a non-working state. This is a result of not being able to overwrite the file that’s included in the error message. Contact your support representative for additional assistance.

Auzinga
Posts: 8
Joined: Tue Dec 07, 2010 4:46 am

Re: Scrutinizer Upgrade Instructions

Post by Auzinga » Thu Apr 18, 2013 3:07 am

Hi

i don't have the plixer_scheduler. is this normal in the V10 or went something wrong during the installation?

KR
Martin

pauld
Posts: 222
Joined: Mon Jan 04, 2010 10:05 am
Location: Kennebunk, Maine
Contact:

Re: Scrutinizer Upgrade Instructions

Post by pauld » Thu Apr 18, 2013 8:30 am

Good catch Martin! In v10 there no longer is a plixer_scheduler service. I've fixed the instructions.

Thanks,
Paul

JakeB
Posts: 83
Joined: Thu Jan 10, 2013 2:15 pm

Re: Scrutinizer Upgrade Instructions

Post by JakeB » Mon Jun 24, 2013 8:59 am

Scrutinizer v10.x to v11.x Upgrade Instructions

The Scrutinizer v10.x to v11.x upgrade has been designed to be an over the top upgrade so users can run the latest installer on the server and be upgraded to the latest release.

Before upgrading a backup is strongly recommended, but not required.
The files and folders to be backed up are in the following instructions.

What should I verify before upgrading?
- Does the Scrutinizer server meet the system requirements?
http://www.plixer.com/products/netflow- ... ements.php
- Scrutinizer v11 and Denika are no longer compatible to run on the same server. Contact support for further assistance.

Instructions for upgrading Scrutinizer on the same server:
1) Download the latest upgrade installer: http://www.plixer.com/support/availableUpdates.php
2) Make a database backup; if you don’t need a backup, skip to step 7.
3) Stop the plixer_mysql and dependent services (plixer_apache, plixer_flow_collector, plixer_flowalyzer_svc, plixer_ipfixify, and plixer_syslogd)
4) Copy the “\Scrutinizer\mysql\data\scrut_*” folders to a backup folder
5) Copy the “\Scrutinizer\mysql\data\plixer” folder to a backup folder
6) Start the plixer_mysql service
7) Run Scrutinizer-windows-installer.exe

Instructions for upgrading and moving Scrutinizer to a different server

Before migrating Scrutinizer to a new server the old server must be upgraded because the database is only compatible with the same version of Scrutinizer.

IMPORTANT NOTE: These instructions assume the new server will have the same IP address that the old server had. If the new server will have a different IP address you will need to contact Plixer Technical Support 207-324-8805 x4 with the new IP address to get a new license key. It’s recommended to do this before upgrading.

1) On the old server, follow the “Instructions for upgrading Scrutinizer on the same server” for the appropriate version that you have installed.
2) Using the same installer that upgraded the old server, install Scrutinizer on the new server.
3) Old server: stop the services in the following order plixer_flow_collector, plixer_flowalyzer_svc, plixer_syslogd, plixer_ipfixify, plixer_apache, plixer_mysql
4) New server: stop the services in the following order plixer_flow_collector, plixer_flowalyzer_svc, plixer_syslogd, plixer_ipfixify, plixer_apache, plixer_mysql
5) New server: copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to a backup location (so you have a backup of the original database)
6) On the old server copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
7) On the old server copy the “[homedir]\scrutinizer\mysql\data\scrut_*” directories to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
8 ) New server: start the services in the following order plixer_mysql, plixer_apache, plixer_ipfixify, plixer_flow_collector, plixer_flowalyzer_svc, plixer_syslogd
9) Change the new severs IP addresses, so the new server has the IP address that’s tied to the Scrutinizer license key.

FAQ

Q) During the upgrade I got an, “Error unpacking archive” and the installer has stopped. What do I do now?

A) DO NOT abort the install as it will leave Scrutinizer in a non-working state. This is a result of not being able to overwrite the file that’s included in the error message. Contact your support representative for additional assistance.

seanh
Posts: 20
Joined: Thu Oct 17, 2013 8:50 am
Location: Kennebunk, ME

Re: Scrutinizer Upgrade Instructions

Post by seanh » Tue Jul 22, 2014 10:10 am

Scrutinizer v11.x to v12.x Upgrade Instructions

The Scrutinizer v11.x to v12.x upgrade has been designed to be an over the top upgrade so users can run the latest installer on the server and be upgraded to the latest release.

Before upgrading a backup is strongly recommended, but not required.
The files and folders to be backed up are in the following instructions.

What should I verify before upgrading?
- Does the Scrutinizer server meet the system requirements?
http://www.plixer.com/Scrutinizer-Netfl ... rsion.html
Scrutinizer v12.x.x only supports 64 bit architecture and Server 2008 or newer. Please verify your OS meets this requirement.
- Scrutinizer v11 and Denika are no longer compatible to run on the same server. Contact support for further assistance. This has not changed in Scrutinizer v12.

Instructions for upgrading Scrutinizer on the same server:
1) Download the latest upgrade installer: http://www.plixer.com/support/availableUpdates.php
2) Make a database backup; if you don’t need a backup, skip to step 7.
3) Stop the plixer_mysql and dependent services (plixer_apache, plixer_flow_collector, and plixer_syslogd)
4) Copy the “\Scrutinizer\mysql\data\scrut_*” folders to a backup folder
5) Copy the “\Scrutinizer\mysql\data\plixer” folder to a backup folder
6) Start the plixer_mysql service
7) Run Scrutinizer-windows-installer.exe
8 ) Verify your License Key is valid and not expired. Please contact support if you need a new one.

Instructions for upgrading and moving Scrutinizer to a different server.

Before migrating Scrutinizer to a new server the old server must be upgraded because the database is only compatible with the same version of Scrutinizer.

IMPORTANT NOTE: Unlike version 11.x.x, version 12.x.x keys are based on MachineID and not the server's IP address. A new key will have to be generated if the new server keeps the same IP address or changes to a new one. Step 2 goes over when that key needs to be generated.

1) On the old server, follow the “Instructions for upgrading Scrutinizer on the same server” for the appropriate version that you have installed.
2) Using the same installer that upgraded the old server, install Scrutinizer on the new server. Please contact support and have your new MachineID License Key generated for the fresh install. The machineID will be located under admin -> settings -> licensing.
3) Old server: stop the services in the following order plixer_flow_collector, plixer_syslogd, plixer_apache, and plixer_mysql.
4) New server: stop the services in the following order plixer_flow_collector, plixer_syslogd, plixer_apache, and plixer_mysql.
5) New server: copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to a backup location (so you have a backup of the original database)
6) On the old server copy the “[homedir]\scrutinizer\mysql\data\plixer” directory to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
7) On the old server copy the “[homedir]\scrutinizer\mysql\data\scrut_*” directories to the “[homedir]\scrutinizer\mysql\data\” directory on the new server.
8 ) New server: start the services in the following order plixer_mysql, plixer_apache, plixer_flow_collector, and plixer_syslogd.
9) Change the new severs IP addresses so the new server has the IP address of the old server. Apply the new machineID based License Key.

FAQ

Q) During the upgrade I got an, “Error unpacking archive” and the installer has stopped. What do I do now?

A) DO NOT abort the install as it will leave Scrutinizer in a non-working state. This is a result of not being able to overwrite the file that’s included in the error message. Contact your support representative for additional assistance.

ryans
Posts: 25
Joined: Mon Aug 04, 2014 10:47 am

Re: Scrutinizer Upgrade Instructions

Post by ryans » Tue Aug 04, 2015 8:54 am

Scrutinizer v12.x to v15.5 Upgrade Instructions

The Scrutinizer v12.x to v15.5 upgrade has been designed to be an over the top upgrade so users can run the latest installer on the server and be upgraded to the latest release. If you are on version 11.5.2 or higher, you can upgrade directly to v15.5. Any version before 11.5.2, you will need to upgrade to version 11.5.2 before moving to v15.5.

Before upgrading a backup is strongly recommended, but not required.
The files and folders to be backed up are in the following instructions.

What should I verify before upgrading?
- Does the Scrutinizer server meet the system requirements?
http://www.plixer.com/Scrutinizer-Netfl ... rsion.html
Scrutinizer v15.x only supports 64 bit architecture and Server 2008 or newer. Please verify your OS meets this requirement.
- Scrutinizer v11 and Denika are no longer compatible to run on the same server. Contact support for further assistance. This has not changed in Scrutinizer v12 or v15.

Instructions for upgrading Scrutinizer on the same server:
1) Download the latest upgrade installer: http://www.plixer.com/support/availableUpdates.php
2) Make a database backup; if you don’t need a backup, skip to step 7.
3) Stop the plixer_mysql and dependent services (plixer_apache, plixer_flow_collector, and plixer_syslogd)
4) Copy the “\Scrutinizer\mysql\data\*” folder to a backup folder
*5) For a backup of only the configuration files: Copy the “\Scrutinizer\mysql\data\plixer and \reporting” folders to a backup folder.
6) Start the plixer_mysql service
7) Run Scrutinizer-windows-installer.exe
8 ) Verify your License Key is valid and not expired. Please contact support if you need a new one.


FAQ

Q) During the upgrade I got an, “Error unpacking archive” and the installer has stopped. What do I do now?

A) DO NOT abort the install as it will leave Scrutinizer in a non-working state. This is a result of not being able to overwrite the file that’s included in the error message. Contact your support representative for additional assistance.

Jarrydb

Re: Scrutinizer Upgrade Instructions

Post by Jarrydb » Wed Nov 04, 2015 2:00 pm

UPGRADE Windows Version of Scrutinizer 10.1 - 16.3
  • Upgrades are staged in a specific path. 10.1 > 11.03 > 11.5.2 > 12.0.x >12.1 > 15.5 > 15.8 > 16.3
  • When upgrading from a version older then version 12, you can install up to 11.5.2 and then go straight to 15.5
  • If you are on a 12.0.x version, make sure that you upgrade to version 12.1 before proceeding to 15.5

System Requirements
Below are the minimum requirements for the downloadable Windows version of Scrutinizer.

Specifications (for production environments)
RAM = 8GB
Disks = 1+ TB 15k SCSI in a
RAID = 0 or 10 configuration
Processor = Quad Core 2GHz+
Operating System = Windows 2008/2012 Server

NOTE: Please keep in mind that the more Flows you push to Scrutinizer, the more resources the software will consume. It is recommended that users purchase the Scrutinizer Virtual or Hardware Appliance if high Flow volume (> 10K flows/second) is anticipated.

First – The Backup

We always suggest making a backup. This step is optional but it is always good to be safe

Stop all of the Plixer_* services
  • Plixer_flow_collector
  • Plixer_syslogd
  • Plixer_apache
  • Plixer_mysql

Make a copy of of either the whole /data folder or if you want just settings and reports /plixer and /reporting
************All Historical Data / Settings / Reports ***************
(Home Dir):\Program Files\Scrutinizer\mysql\data

***************Just the Saved Reports / Configs / Maps ***************
(Home Dir):\Program Files\Scrutinizer\mysql\data\plixer
and
(Home Dir):\Program Files\Scrutinizer\mysql\data\reporting

Start all the Plixer_ * services
  • Plixer_mysql
  • Plixer_flow_collector
  • Plixer_syslogd
  • Plixer_apache



The Upgrade
( Here are the following links and details you will need in order to upgrade)

11.03
Download the installer
http://files.plixer.com/archive/scrutin ... 11.0.3.exe
http://files.plixer.com/archive/scrutin ... 11.0.3.exe ( SSL VERSION )
• Make sure no Anti Viruses are running
• Right Click on the exe and run as admin
• Follow the prompts and when the install is done just open up the web ui and hit CTRL + F5 to clear the cache
• Check to make sure everything looks normal (this may take some time as data streams in)
• Celebrate!

11.5.2
Download the installer
https://files.plixer.com/archive/scruti ... 11.5.2.exe
https://files.plixer.com/archive/scruti ... 11.5.2.exe ( SSL VERSION )
• Make sure no Anti Viruses are running
• Right Click on the exe and run as admin
• Follow the prompts and when the install is done just open up the web ui and hit CTRL + F5 to clear the cache
• Check to make sure everything looks normal (this may take some time as data streams in
• Celebrate!

12.1
Download the installer
https://files.plixer.com/archive/scruti ... 12.1.0.exe
https://files.plixer.com/archive/scruti ... 12.1.0.exe ( SSL VERSION )
• Make sure no Anti Viruses are running
• Right Click on the exe and run as admin
• Follow the prompts and when the install is done just open up the web ui and hit CTRL + F5 to clear the cache
• Check to make sure everything looks normal (this may take some time as data streams in)
• Celebrate!

15.5
Download the installer
https://files.plixer.com/archive/scruti ... r_15.5.exe
https://files.plixer.com/archive/scruti ... l_15.5.exe ( SSL VERSION )
• Make sure no Anti Viruses are running
• Right Click on the exe and run as admin
• Follow the prompts and when the install is done just open up the web ui and hit CTRL + F5 to clear the cache
• Check to make sure everything looks normal (this may take some time as data streams in)
• Celebrate!

15.8
• Download the latest installer
https://files.plixer.com/archive/scruti ... r_15.8.exe
https://files.plixer.com/archive/scruti ... l_15.8.exe ( SSL VERSION )
• Make sure no Anti Viruses are running
• Right Click on the exe and run as admin
• Follow the prompts and when the install is done just open up the web ui and hit CTRL + F5 to clear the cache
• Check to make sure everything looks normal (this may take some time as data streams in)
• Celebrate!

16.3
• Download the latest installer
https://files.plixer.com/Scrutinizer-wi ... taller.exe
https://files.plixer.com/Scrutinizer-wi ... er-ssl.exe ( SSL VERSION )
• Make sure no Anti Viruses are running
• Right Click on the exe and run as admin
• Follow the prompts and when the install is done just open up the web ui and hit CTRL + F5 to clear the cache
• Check to make sure everything looks normal (this may take some time as data streams in)
• Celebrate!

donsisco
Posts: 1
Joined: Wed Nov 04, 2015 2:50 pm

Re: Scrutinizer Upgrade Instructions

Post by donsisco » Thu Jan 07, 2016 8:29 am

How do you upgrade to version 16 on the hardened appliance?

Jeff M
Posts: 16
Joined: Tue May 12, 2015 8:10 am

Re: Scrutinizer Upgrade Instructions

Post by Jeff M » Thu Jan 07, 2016 8:48 am

Hi Don

Due to the restricted root access to the HW Appliance we generally recommend scheduling a call with one of our support agents to assist. During the upgrade process we will want to update the OS as well.

If you'd like to schedule a call with one of our support, don't hesitate to reach out to us! You can reach us at +1(207)324-8805 X4.

Thanks for the great question!!

Post Reply

Who is online

Users browsing this forum: No registered users and 1 guest