![]() An incremental backup is not sufficient to restore a system on its own. Incremental backups contain only the changes made to your instance since the last full backup or previous incremental backup. See Prepare your system for restore earlier in this topic. You must prepare the system before restoring your system from an incremental backup. Logs recorded in /opt/phantom/data/phantom_backups/phantom_backup_restore_-23-03-06.log Restore your system from an incremental backup Running /opt/phantom/bin/start_phantom.sh Configuring NGINX SSL certificates (this may take a while) Dropping temporary archive tables used for backup Deleting existing Phantom database records ![]() Loading tables from backup into database This will overwrite any existing data upon restore. The backup file appears to be a full backup. Extracting backup tarball (this may take a while) opt/phantom/proxy/bin/splunk_proxyd is already stopped Stopping all Phantom services except PostgreSQL The -config option of the backup.pyc script will continue to work with ibackup.pyc. Documentation for the new script can be found at. Please use the ibackup.pyc script to perform backups and restores. The -all option of the backup.pyc script has been deprecated. restore.py:692 WARNING: The -all option of the backup.pyc script has been deprecated. The command output looks like this: bin]# phenv python restore.pyc -file /opt/phantom/data/phantom_backups/phantom_backup_-22-49-17.tgz Sudo phenv python restore.pyc -file For this use, you can safely ignore the deprecation warning.
0 Comments
Leave a Reply. |