Use the Splunk Phantom repo not the msoc repo. BE SURE TO HAVE AT MOST 55% FREE space ( 45% used space)
backup docs https://docs.splunk.com/Documentation/Phantom/4.10.2/Admin/Restorefromabackup
08/2020
See Splunk docs!
Silence Phantom sensu checks
Stop Phantom
/opt/phantom/bin/stop_phantom.sh
Clean yum
yum clean all
Take an AWS snapshot in addition to the automatic snapshots! Naming Scheme: phantom-pre-upgrade-backup-
Update OS & reboot (only if kernel updated)
yum update --exclude=nginx
Start Phantom
/opt/phantom/bin/start_phantom.sh
Disable WAL
sed -i -e 's/archive_mode = on/archive_mode = off/i' /opt/phantom/data/db/postgresql.phantom.conf
restart postgres
/opt/phantom/bin/phsvc restart postgresql-9.4
Install new repo and keys
rpm -Uvh https://repo.phantom.us/phantom/4.9/base/7Server/x86_64/phantom_repo-4.9.35731-1.x86_64.rpm
Upgrade script
/opt/phantom/bin/phantom_setup.sh upgrade
Post Upgrade (Run IF the upgrade script produces the message!)
su - postgres -c '/usr/pgsql-11/bin/vacuumdb -h /tmp --all --analyze-in-stages'
phenv python3 /opt/phantom/bin/ibackup.pyc --setup
Verify postgres version
su - postgres -c '/usr/pgsql-11/bin/postgres --version'
Login into web to accept EULA
After the upgrade is complete, from Main Menu > Administration > Administration Settings > Search Settings, select Playbooks from the drop-down menu, then click the Reindex Search Data button.
Post Upgrade Steps
Have Phantom Administrator verify that email is working properly.
Clear Silence Done!
vagrant phantom creds admin/password Password1 ssh use the brad user and ssh key
TEST
PROD
stop phantom take snapshot of drive clean yum cache install RPM for repo upgrade phantom
Phantom Upgrade Steps Do not skip versions. Upgrade incrementally.
Post Upgrade Steps