ssoclbackup <BackupDirectory>
This command backs up an environment created with the Interstage Single Sign-On system creation command (ssoclsetup). Refer to "Interstage Single Sign-On System Creation Command" for information on the ssoclsetup command.
The following table shows the resources, files, and locations backed up by this command.
Backed up resources | Backed up files (*1) | Locations (*2) |
---|---|---|
Interstage Single Sign-On | Repository server definition file | <BackupDirectory>\ssoroot\SSO\sv_back |
・Authentication server definition file ・Message files displayed in the authentication server's Web browser | <BackupDirectory>\ssoroot\SSO\ac_back | |
・Business server definition file ・Message files displayed in the business server's Web browser | <BackupDirectory>\ssoroot\SSO\az_back | |
Interstage HTTP Server | The following files for all Web servers ・Interstage HTTP Server environment definition file ・Password file Public root directory | <BackupDirectory>\ssoroot\IHS\ |
Interstage directory service | The following files in the repository being used as the SSO repository ・Repository environment ・Repository data ・Access logs | <BackupDirectory>\ssoroot\IDS\rep_back\ |
Interstage certificate environment | ・Certificate environment files ・SSL definition File | <BackupDirectory>\ssoroot\SCS\ |
Information about the environment that was backed up is also stored in the following files.
Information stored | Details | Location ([Windows] above, [Linux] below) |
---|---|---|
SSO repository name | The name of the backed up SSO repository is stored as text. | <BackupDirectory>\ssoroot\info\rep_name.txt |
SSO repository configuration information | Configuration information about the backed up SSO repository. | <BackupDirectory>\ssoroot\info\rep_config.txt |
A list of the Interstage HTTP Server's Web server names | A list of the names of the backed up Web servers is stored as text. | <BackupDirectory>\ssoroot\info\web_server_list.txt |
*1: Refer to "Maintenance (Resource Backup)" - " Backing Up and Restoring Resources" - "Resources that can be Backed Up and Restored" in the "Interstage Application Server Operator's Guide" for details on files.
*2: This is a destination to store each backup resource. Specify this path when only a part of resources is restored individually. Refer to "Maintenance (Resource Backup)" - "Backing Up and Restoring Resources" in the "Interstage Application Server Operator's Guide" for information on restoring individually.
Option | Description | |
---|---|---|
BackupDirectory | Specify the directory where the resources are to be backed up, using a full path. Specify the path using no more than 100 bytes. If the specified backup directory does not exist, the directory is created. [Windows] The following characters cannot be used in the backup directory name. The colon can be used to indicate the drive letter and the backslash can be used as the directory separator.
|
Execute the command as an Administrator.
If the backup destination is /backup
$ su - Password: <Password for the superuser> # /opt/FJSVcfmg/sso/bin/ssoclbackup /backup
Note
Do not execute more than one of these commands at the same time.
Backup and restore can only be performed on the same operating systems.
Do not perform backup if backup or restore is being performed on the same server.
Before backing up, use the ssoclservicectl command to stop all services connected to Interstage Single Sign-On. Refer to "Interstage Single Sign-On Start and Stop Command" for information on the ssoclservicectl command.
This command will end with an error if backup resources ("ssoroot" directory) already exist in the backup directory.
Execute this command in an environment that has been created with the Interstage Single Sign-On system creation command (ssoclsetup).
When the single sign-on system created by not using configuration command is backed up, back up referring to "Maintenance (Resource Backup)"-" Backing Up and Restoring Resources" in the "Interstage Application Server Operator's Guide".
If there are contents or CGI outside of the directories specified by the Interstage HTTP Server DocumentRoot directive, use one of the following methods to back these up separately.
copy command or Explorer
If processing is interrupted after this command has been executed but before the processing has completed, backup will not have been completed. If this occurs, delete the backup directory and then execute the command again.