Top
Systemwalker Runbook Automation Installation Guide
Systemwalker
Chapter 8 Maintenance > 8.3 Backup and Restoration > 8.3.2 Backing up Systemwalker Runbook Automation
PreviousNext

8.3.2 Backing up Systemwalker Runbook Automation

This section describes how to back up the Systemwalker Runbook Automation environment.

Back up as following steps

8.3.2.1 Stop Systemwalker Runbook Automation

Stop Systemwalker Runbook Automation Management Server by swrba_stop command.

[Windows]

[Systemwalker Runbook Automation Management Server install directory]\bin\swrba_stop

[Linux]

/opt/FJSVswrbam/bin/swrba_stop

8.3.2.2 Backup the Interstage Single Sign-On Resources

This section explains the procedure for backing up the Interstage Single Sign-On resources.

You do not need to execute this procedure in the environment of not using Interstage Single Sign-On authentication foundation.

Note

  • Here, the Interstage Single Sign-On resources constructed by using the ssoclsetup command are backed up.

    For the Interstage Single Sign-On resources constructed by not using the ssoclsetup, refer to the Interstage Application Server Operator's Guide and backup the resources.

  • Execute procedure in this section as an administrator authority.

8.3.2.2.1 Stop the Interstage Single Sign-On

The Interstage Single Sign-On is stopped by using the ssoclservicectl command. Refer to the Systemwalker Runbook Automation Reference Guide for the ssoclservicectl command

[Windows]

[Systemwalker Runbook Automation Management Install Directory]\sso\bin\ssoclservicectl stop

[Linux]

/opt/ FJSVswrbam /sso/bin/ssoclservicectl stop
8.3.2.2.2 Backup the Interstage Single Sign-On Resources

The Interstage Single Sign-On resources can be backed up by using the ssoclbackup command. Refer to the Systemwalker Runbook Automation Reference Guide for the ssoclbackup command.

[Windows]

  1. Create directory for back up

    mkdir X:\Backup\sso

  2. Back up with ssoclbackup command.

     [Systemwalker Runbook Automation Management Server Install Directory]\sso\bin\ssoclbackup X:\Backup\sso

[Linux]

  1. Create directory for back up

    mkdir /backup/sso

  2. Back up with ssoclbackup command

    /opt/FJSVswrbam/sso/bin/ssoclbackup /backup/sso

Note

Here, the following resources are backed up. Refer to Systemwalker Runbook Automation Reference Guide

  • Interstage Single Sign-On resources

  • Interstage HTTP Server resources

  • Interstage Directory Service resources

  • Interstage Certificate Environment resources

  • SSO repository name

8.3.2.2.3 Start the Interstage Single Sign-On

The Interstage Single Sign-On is started by using the ssoclservicectl command. Refer to Systemwalker Runbook Automation Reference Guide for the ssoclservicectl command.

[Windows]

[Systemwalker Runbook Automation Management Server Install Directory]\sso\bin\ssoclservicectl start

[Linux]

/opt/FJSVswrba/sso/bin/ssoclservicectl start

8.3.2.3 Backing up LDAP Resources

This section explains how to back up the LDAP resources.

If you use Interstage Single Sign-On authentication infrastructure, you do not execute this steps.

If Active Directory or OpenLDAP is used for LDAP, refer to the LDAP manual before performing the backup tasks.

In the backup method explained here, the Interstage Directory Service is used and a standard database is used for the repository database.

[Windows]

In the following example, the repository "rep001" is backed up to the backup directory "X:\Backup\rep001".

  1. Log in as the system administrator.

  2. Stop Interstage directory service.

    Stop "Interstage Directory Service(rep001)" from Control Panel- Administrative tool-Service. Or stop it by the following command.

    net stop "Interstage Directory Service(rep001)"

  3. Create a directory for backup. Note that there is no need to create a directory for rep001 in X:\Backup.

    mkdir X:\Backup

  4. Execute the backup command. 

    [Interstage Application Server installation directory]\bin\irepbacksys -d X:\Backup\rep001 -R rep001

  5. Start the Interstage Directory Service, if it is used.

    Click Start >> Control Panel >> Administrative Tools, and then, double-click Services. From the displayed list of services, right-click Interstage Directory Service(rep001) and click Start.

    Alternatively, start the Interstage Directory Service using the following command:

    net start "Interstage Directory Service(rep001)"

[Linux]

In the following example, the repository "rep001" is backed up to the backup files "/backup/rep001".

  1. Log in as the system administrator.

  2. Stop Interstage directory service by irepstop command. 

    /opt/FJSVirep/bin/irepstop -R rep001

  3. Create a directory for backup.

    mkdir /backup

  4. Execute the backup command.

    /opt/FJSVirep/bin/irepbacksys -f /backup/rep001 -R rep001

  5. If the Interstage Directory Service is used, start it.

    /opt/FJSVirep/bin/irepstart -R rep001

Information

Refer to "Maintenance (Resource Backup)" in the Interstage Application Server Operator's Guide for information on how to back up the Interstage Directory Service.

8.3.2.4 Back up Systemwalker Runbook Automation execution environment

This section describes how to back up the Systemwalker Runbook Automation environment.

Checking the space available in the backup directory

Backing up resources


Checking the space available in the backup directory

To check how much free space is required for the backup directory, it is necessary to check the space required for the backup directory for Systemwalker Runbook Automation and the space required for the backup directory for the CMDB.

Guides to the amount of free space required in the backup directory are as follows.

Checking the space available in the backup directory

[Windows]

Space required for the backup directory =
Amount of backup resources for the Process Management Database (*1)
+ Total size of the files and directories under the installation directory for the Systemwalker Runbook Automation Management Server
+ Total capacity in the Systemwalker Operation Manager installation directory
+ 1 MB

*1:

Process Management Database directory size specified during setup

[Linux]

Space required for the backup directory =
Amount of backup resources for the Process Management Database (*1) +
+Total size of the files and directories under the /etc/opt/FJSVswrbam directory +
+Total size of the files and directories under the /var/opt/FJSVswrbam directory +
+ Total capacity in /var/opt/FJSVJMCMN/etc

+ Total capacity in /var/opt/FJSVjmcal

+ Total capacity in /var/opt/FJSVJOBSC

+ Total capacity in /var/opt/FJSVfwseo/config/JM (*2)

+ Total capacity in /opt/FJSVJOBSC/bin

+ Total capacity in /etc/mjes

+ Total capacity in /var/spool/mjes

+ 1 MB

*1:

Database directory size specified during setup

*2:

In the following cases, "FJSVfwseo" will be "FJSVfwsec".

  • When Systemwalker Centric Manager V13.4.0 is installed after Systemwalker Runbook Automation

  • When a version later than Systemwalker Centric Manager V13.4.0 is installed (this has nothing to do with the order of installation with regard to Systemwalker Runbook Automation)

Checking the space available in the CMDB backup directory

As a guide to the amount of free space required for the backup directory, check the size of the directories below:

[Windows]

Space required for the backup directory =
<CMDB Manager database directory>\FJSVcmdbm \Shunsaku\directorData
+ <CMDB Manage database directory r>\FJSVcmdbm\fcmdb\file
+100MB

[Linux]

Space required for the backup directory =
/opt/FJSVcmdbm/var/Shunsaku/directorData
+/opt/FJSVcmdbm/var/fcmdb/file
+100MB

Backing up resources

[Windows]

Describes the steps for backing up backup directory X:\Backup\swrba

  1. Login as a system administrator

  2. Create back up directory

    mkdir X:\Backup\swrba

  3. Execute back up command

    Back up the resources

    [Systemwalker Runbook Automation Management Server install directory]\bin\swrba_backup X:\Backup\swrba

  4. Backup will start.

    The message below will be displayed:

    Systemwalker Runbook Automation backup has started.

    Database backup has started.

    Database backup has completed successfully.

    File backup has started.

    File backup has completed successfully.

    Backup of the Scheduling is starting.

    Backup of the Scheduling has finished.

    Starting to back up the CMDB Manager.

    Finished backing up the CMDB Manager.

    Systemwalker Runbook Automation backup has completed successfully.

  5. E Backup will complete

    The message below will be displayed:

    Systemwalker Runbook Automation backup has completed successfully.

[Linux]

  1. Log in as a superuser on the system.

  2. Create back up directory

    mkdir /backup/swrba

  3. Back up the resources

    1. /opt/FJSVswrbam/bin/swrba_backup /backup/swrba.

  4. Backup will start.

    The message below will be displayed:

    Systemwalker Runbook Automation backup has started.

    Database backup has started.

    Database backup has completed successfully.

    File backup has started.

    File backup has completed successfully.

    Backup of the Scheduling is starting.

    Backup of the Scheduling has finished.

    Starting to back up the CMDB Manager.

    Finished backing up the CMDB Manager.

    Systemwalker Runbook Automation backup has completed successfully.

  5. Backup will complete.

    The message below will be displayed:

    Systemwalker Runbook Automation backup has completed successfully.

8.3.2.5 Start Systemwalker Runbook Automation

start Systemwalker Runbook Automation Management Server by swrba_start command.

[Windows]

[Systemwalker Runbook Automation Management Server install directory]\bin\swrba_start

[Linux]

/opt/FJSVswrbam/bin/swrba_start

PreviousNext
Copyright 2010-2012 FUJITSU LIMITED