Upgrading from Splunk versions 3.0.x through 3.1.x to Splunk versions 3.1.x through 3.1.5

If you are upgrading from a Splunk version in the range of 3.0.x through 3.1.x to any version in the range 3.1.x through 3.1.3, you must back up your $SPLUNK_HOME/etc/* directories manually. These instructions explain how to do this.

Note: By convention, this document uses $SPLUNK_HOME to refer to the location of your Splunk install.

For rpm, pkg, and deb upgrades

Create a backup of your /etc directories:
- cp -a $SPLUNK_HOME/etc/ $SPLUNK_HOME/etc.bak
Upgrade Splunk using rpm -U on the Splunk rpm or pkg file.
Restore your configuration to the upgraded installation by copying your backed up /etc directories and files. Copy the following directories and files as indicated:
- $SPLUNK_HOME/etc.bak/auth/* to $SPLUNK_HOME/etc/auth/
- $SPLUNK_HOME/etc.bak/passwd to $SPLUNK_HOME/etc/
- $SPLUNK_HOME/etc.bak/bundles/local/* to $SPLUNK_HOME/etc/local/
- $SPLUNK_HOME/etc.bak/splunk.license to $SPLUNK_HOME/etc/splunk.license
- For any bundles directories you have created in your existing installation, copy:
  - $SPLUNK_HOME/etc.bak/bundles/<your bundles>/ to $SPLUNK_HOME/etc/

IMPORTANT: Copy these files and directories individually. Do not copy the entire $SPLUNK_HOME/etc.bak directory back to /etc. If you do so, the version number and other information will be incorrect.

Contact support with any questions.

For tar upgrades

For tar upgrades, it's not necessary to restore your configuration as with rpm/pkg/deb. However, Splunk recommends that you back up your /etc directories.

1. Create a back up of your /etc directories.

cp -a $SPLUNK_HOME/etc/ $SPLUNK_HOME/etc.bak

2. In the $SPLUNK_HOME directory, upgrade Splunk using tar to unpack the file.

Previous: Upgrading 2.1.x or 2.2.x to 3.1.x | Next: Upgrading a forwarder from 2.x to 3.x

Comments

Hi,

For Solaris packages do you need to pkgrm the splunk package first and then pkgadd it to reinstall it?
Posted by mpf on Feb 03 2008, 7:18pm