IBACKUP FREEWARE UPGRADE
IBACKUP FREEWARE FULL
IBACKUP FREEWARE OFFLINE

INFO: Backup created at: /opt/phantom/data/backup/phantom_backup_group_0_level_0.tar

IBACKUP FREEWARE FULL

WARNING: no prior backup exists, incr backup has been changed to full INFO: Attempting to connect to Postgresql. INFO: Running ibackup - details will be logged to /var/log/phantom/backup/backup_T21:24:28.706665Z.log The following sample output shows a backup being run: If you already have a backup group and want to create a new full backup, use the -backup-type full argument. When a full backup exists, a new incremental backup is added to the group. If no backups exist, a full backup is created.

From the command line, SSH to one cluster node of your deployment.

In clustered deployments, all backup commands must be issued from the same cluster node. Prepare a cluster or deployment with an external PostgreSQL database for a backupįor deployments where the PostgreSQL database is external to the instance or in clustered deployments, you must take additional steps to prepare the deployment for backup. Running it a second time before any restore actions does nothing. Running the set up again after a restore resets the state file used by ibackup and archives all existing backup files. Re-run again ? Enter yes to proceed:Įnter yes to run the setup process again. If the instance or cluster has been setup for backups, the tool prompts you to confirm that you wish to run setup again: If you wish to continue, enter yes to proceed: yes Logs for this script run will be located at /opt/phantom/var/log/phantom/ibackup/ibackup_-22-45-24.logĪttempting to connect to Postgresql, connection errors are expected while bootstrapping. The command output looks like bin]$ phenv ibackup -setup

From the command line, SSH to your instance.

If your Splunk SOAR (On-premises) deployment uses a Warm Standby or if you intend to use a Warm Standby, you must configure Warm Standby before setting up backups. Psql: ERROR: pgbouncer cannot connect to server This causes the following error to be displayed during the setup process, which can be ignored: Services restart before setup is complete. ĭuring setup, ibackup temporarily stops services in order to make changes to the PostgreSQL database configuration.

IBACKUP FREEWARE UPGRADE

You must prepare by running the ibackup command with the -setup option after any upgrade of. Prepare for a backupīefore you can create backups, you must prepare by running the ibackup command with the -setup option. See Create a full backup for deployments with an external PostgreSQL database in RDS.

Make sure you have completed either the section Prepare for a back up or Prepare a cluster or deployment with an external PostgreSQL database, depending on your deployment's configuration.ĭeployments of Splunk SOAR (On-premises) in AWS that use RDS for their PostgreSQL database should not use ibackup to create backups of the Splunk SOAR (On-premises) database.

For privileged deployments, make sure that you have root or sudo permissions on the deployment.

IBACKUP FREEWARE OFFLINE

You do not need to take offline to do a backup.īefore you begin, check each of the following things.

Your deployment is backed up using command-line tools.

Ibackup freeware