Use the Deployment Engine (DE) backup script before installing
additional components or other products that are based on the Tivoli Integrated Portal platform. If you need to recover
the original configuration after a failure, you can then run the Deployment
Engine restore script.
About this task
The Deployment Engine performs the installation of new and
upgraded products. It keeps track of the installed components and
skips installing a given component if it is already present on the
system. Perform the following steps to back up or restore the DE database.
Procedure
- From the command line, change to the acsi directory:
cd C:\Program Files\IBM\Common\acsi

For Linux and UNIX-based systems, the
path to the acsi directory varies depending on
whether you are installing as root or as a non-root user, as follows:- Installing as a non-root user, the path is relative to the user's
home directory:
<non-root user
home directory>/.asci_<user_name>
- Installing as root, the path is as follows:
/var/ibm/common/asci
- Initialize the Deployment Engine environment from the command
line:
- Change to the bin directory:
Change to the bin child
directory, that is:
C:\Program Files\IBM\Common\acsi\bin

For Linux and UNIX-based systems, the
path to the bin directory varies depending on
whether you are installing as root or as a non-root user, as follows:- For a non-root user, change to the bin child
directory, that is:
<non-root user
home directory>/.asci_<user_name>/bin
- For root, the path is as follows:
/usr/ibm/common/asci/bin
- Run the backup script to back up the Deployment Engine
database, as follows:
de_backupdb.cmd

de_backupdb
- If you need to restore the Deployment Engine database,
from the bin directory run the restore script:
de_restoredb.cmd

de_restoredb
What to do next
If you backed up the Deployment Engine database, you can
run the installer now to add additional components or products. If
you restored the Deployment Engine database, you can resume using
the original installed environment.