Administer > Administer ITBA > System Administrator > Disaster and Recovery

Disaster and Recovery

The ITBA, SAP BusinessObjects Enterprise, or Vertica servers have become unusable, for example the hard disk has crashed. The following procedure describes how to recover the ITBA, BOE, and Vertica servers.

When you start the recovery process, you must have complete backups of the relevant databases, configuration files, and settings that are readily available. It is possible that you will lose history data. For details about the backups, see Business Analytics Back Up .

The following scenarios are independent from the external data sources and entities. Recovering from a scenario means that the component returns to a stable state.

ClosedAbout the recovery procedure

This section is a reference for the ITBA recovery process. The recovery process for your environment may vary according to your business needs and may require customization. Verify that the following processes are consistent with your architecture and environment before you proceed with real data.

ClosedRecovery from a ITBA and Postgresql server failure

The following procedure describes how to recover from a ITBA and Postgresql server failure.

  1. Back up the external sources directory contents and the external sources archive directory from the server machine where disaster has occurred.
  2. On a clean machine where you want to install ITBA, run the ITBA installer, and restore the external sources directory contents.

  3. Store the Postgresql database as follows:

    1. Stop ITBA and Start Postgresql

      [ba@ba10 bin]$ cd $HPBA_HOME/supervisor/bin
[ba@ba10 bin]$ ./hpba-stop.sh
[ba@ba10 bin]$ cd $HPBA_HOME/bin
[ba@ba10 bin]$ ./startpgsql.sh

    2. Drop the Postgresql database xs_mng and restore xs_mng from the backup dump.

      [ba@ba10 bin]$ cd $HPBA_HOME/pgsql/bin
[ba@ba10 bin]$ ./dropdb --host=<server_ip> --port=5432 --username=xsadmin xs_mng
[ba@ba10 bin]$ ./psql --host=<server_ip>  --port=5432 --username=xsadmin --set 
     ON_ERROR_STOP=on postgres < xs_mng.dump
[ba@ba10 bin]$ echo '\x \\ ALTER DATABASE xs_mng SET search_path = fnd, dwabc, 
     dwmetadata, app, dcs, cfm, dbo;' | ./psql --host==<server_ip>   --port=5432 
     --username=xsadmin --dbname=xs_mng

    3. Start ITBA

      [ba@ba10 bin]$ cd $HPBA_HOME/bin
[ba@ba10 bin]$ ./stoppgsql.sh
[ba@ba10 bin]$ cd $HPBA_HOME/supervisor/bin
[ba@ba10 bin]$ ./hpba-start.sh
  4. Run the ITBA Maintenance Tool to change the IP, host name and domain name of the new ITBA and Postgresql servers. For details, see Maintenance Tools .

ClosedRecovery from a BOE server failure

To recover from a SAP BusinessObjects Enterprise server failure, follow the instructions in the SAP BusinessObjects Enterprise Disaster Recovery documentation.

After the new BOE server is up, run the Maintenance Tool to change the relevant information (IP, host name and domain name) to the new server. For details, see Maintenance Tools .

ClosedRecovery from a Vertica server failure

The following procedure describes how to recover from a Vertica server failure.

  1. On a clean machine where you want to install ITBA, run the Vertica installation.
  2. Create a new database with the same database name and authentication.
  3. Stop the new Vertica database.
  4. In the vertica server, run the command opt/vertica/bin/vbr.py --task restore --config-file <configuration file name created during backup action>.

  5. Start up the Vertica database.

For details on restoring a Vertica database, see http://my.vertica.com/docs/7.1.x/PDF/HP_Vertica_7.1.x_AdministratorsGuide.pdf.

Send Help Center feedback