How and when CDFs are saved

During installation, the SA Installer saves a temporary CDF whenever you press c to continue on an action confirmation screen, for example the Install Components screen:

Upgrade Components

=====================

Components to be Upgraded

-------------------------

Model Repository, First Core

Core Infrastructure Components

Slice

OS Provisioning Components

Software Repository - Content (install once per mesh)

Up-to-date Components (will not upgrade)

----------------------------------------

Oracle RDBMS for SAS

Enter one of the following directives

(<c>ontinue, <p>revious, <h>elp, <q>uit): c

The temporary CDF is saved in /var/tmp/cdf_<timestamp>_temp.xml. This file can be used to resume an interrupted installation. See Restarting an interrupted installation. This temporary file is updated as each component is processed thus maintaining the setup state as of the most recent action.

If you are concerned about security of CDFs, this file should be saved in a secure location or deleted. Before deleting, however, consider you may need to reuse the CDF in future for adding facilities, additional Slice Component bundles, upgrades and patching the SA Core or mesh.

Concluding the interview

After you have provided values for all the SA configuration parameters, the SA Installer automatically saves the CDF at the end of the installation. The location of the CDF is determined by:

• Whether the infrastructure component bundle host is known at the point of exit, if so, the CDF is saved on that host under /var/opt/opsware/install_opsware/cdf as cdf.xml. CDF backups are saved as cdf_<timestamp>.xml.
• If the Infrastructure host is unknown at the point of exit, the CDF is saved as cdf_tmp.xml under /var/tmp on the server on which the installer was invoked.