Upgrade to 6.3 on *NIX

This topic describes the procedure for upgrading your *nix Splunk Enterprise instance.

Before you upgrade

Make sure you've read this information before proceeding, as well as the following:

Back your files up

Before you perform the upgrade, we strongly recommend that you back up all of your files, including Splunk Enterprise configurations, indexed data, and binaries.

Splunk Enterprise does not provide a means of downgrading to previous versions. If you need to revert to an older Splunk release, just reinstall it.

For information on backing up data, read "Back up indexed data" in the Managing Indexers and Clusters Manual.

For information on backing up configurations, read "Back up configuration information" in the Admin Manual.

How upgrading works

After performing the installation of the new version, Splunk Enterprise does not actually make changes to your configuration until after you restart it. You can run the migration preview utility at that time to see what will be changed before Splunk updates the files.

If you choose to view the changes before proceeding, the upgrade script writes the proposed changes to the $SPLUNK_HOME/var/log/splunk/migration.log.<timestamp> file.

Steps for upgrading

1. Execute the $SPLUNK_HOME/bin/splunk stop command.

Important: Make sure no other processes can start Splunk Enterprise automatically (such as Solaris SMF).

2. To upgrade and migrate from version 5.0 and later, install the Splunk Enterprise package over your existing deployment:

• If you are using a .tar file, expand it into the same directory with the same ownership as your existing Splunk Enterprise instance. This overwrites and replaces matching files but does not remove unique files.

  Note: AIX tar will fail to correctly overwrite files when run as a user other than root. Use GNU tar (gtar) to avoid this problem.

• If you are using a package manager, such as RPM, type rpm -U splunk_package_name.rpm
• If you are using a .dmg file (on Mac OS X), double-click it and follow the instructions. Be sure to specify the same installation directory as your existing installation.

3. Execute the $SPLUNK_HOME/bin/splunk start command.

Splunk Enterprise displays the following output:

This appears to be an upgrade of Splunk.
--------------------------------------------------------------------------------
Splunk has detected an older version of Splunk installed on this machine. To
finish upgrading to the new version, Splunk's installer will automatically
update and alter your current configuration files. Deprecated configuration
files will be renamed with a .deprecated extension.
You can choose to preview the changes that will be made to your configuration
files before proceeding with the migration and upgrade:
If you want to migrate and upgrade without previewing the changes that will be
made to your existing configuration files, choose 'y'.
If you want to see what changes will be made before you proceed with the
upgrade, choose 'n'.
Perform migration and upgrade without previewing configuration changes? [y/n]

4. Choose whether you want to run the migration preview script to see what changes will be made to your existing configuration files, or proceed with the migration and upgrade right away.

5. If you choose to view the expected changes, the script provides a list.

6. Once you've reviewed these changes and are ready to proceed with migration and upgrade, run $SPLUNK_HOME/bin/splunk start again.

Note: You can complete Steps 3 to 5 in one line:

To accept the license and view the expected changes (answer 'n') before continuing the upgrade:

$SPLUNK_HOME/bin/splunk start --accept-license --answer-no

To accept the license and begin the upgrade without viewing the changes (answer 'y'):

$SPLUNK_HOME/bin/splunk start --accept-license --answer-yes