test

Trusted Solaris 7 Installation and Configuration on the Sun Enterprise 10000

Back Up the SSP

Backing up an existing SSP is required if you want to retain the current SSP environment. The backup file must be created with the ssp_backup command on a Solaris SSP 3.1 or SSP 3.1.1 system; a SSP 3.0 backup file can not be restored to Trusted Solaris SSP 3.1.1. If you have a new system or you do not wish to restore the SSP environment after Trusted Solaris installation, you do not need to create backup file.

To determine what version of the SSP software is currently running, see your current SSP documentation.

To Back Up the SSP Environment
Note -

The size of the SSP backup file can range from approximately 4Mbytes to well over 80Mbytes, depending upon the contents of the adm, data, etc, ict, and .ssp_private directories in the /var/opt/SUNWssp/ directory). You can use the du(1M)ommand to determine the approximate amount of disk space required for the backup file. Delete any unnecessary message or log files from the /var/opt/SUNWssp/adm directory prior to invoking ssp_backup.

  1. On the main Solaris SSP, log in as superuser to create a backup file.

  2. Run the ssp_backup command:


    ssp# /opt/SUNWssp/bin/ssp_backup target_directory

    The directory specified by target_directory must exist. This is the directory where the backup file, named ssp_backup.cpio, will be created. After ssp_backup is run, do not make any changes to the Sun Enterprise 10000 environment, such as domain state or power status of boards, until you have completed the install procedure and restored the SSP environment.

  3. Save the /target_directory/ssp_backup.cpio file to a safe location.

    This file will be used during installation of Trusted Solaris SSP 3.1.1 to restore the SSP environment on a single SSP system, or to synchronize the SSP environment between the SSPs on a dual SSP system.

    Note -

    It is suggested that you also back up the SSP with ufsdump(1M) before the install. You can back up all of the files on the SSP using usfdump, instead of just the SSP configuration information that is backed up by ssp_backup. This backup can be used to restore the SSP in the event of a disk failure.