This section provides notes regarding Systemwalker Software Configuration Manager backup and restore. Refer to "Mechanism of Backup and Restoration" in the ServerView Resource Orchestrator Cloud Edition Operation Guide if linked to ServerView Resource Orchestrator.
Notes on operations that use coexistence with Systemwalker Operation Manager or Systemwalker Runbook Automation
Systemwalker Software Configuration Manager backup/restore is executed at the same time as Systemwalker Runbook Automation or Systemwalker Operation Manager backup/restore.
In order to use operations that use coexistence with Systemwalker Runbook Automation or Systemwalker Operation Manager, backup/restore Systemwalker Runbook Automation or Systemwalker Operation Manager using the same backup/restore procedure that is used for Systemwalker Software Configuration Manager. Do not execute backup/restore on the standalone Systemwalker Runbook Automation or Systemwalker Operation Manager.
Notes on the environments where backups and restorations are performed
The backup and restoration environments must follow the criteria below:
When OS are different in from backup and to restore
However, execution will be possible if the operating system versions of the same vendor are different.
When the product installation directories are different [Windows]
When the host information (host name/IP address) is different
When the code types are different
When the Process Management database storage directories are different
When the CMDB database storage directories are different
When the sub system number with using scheduling are different
When the Web server (Interstage HTTP Server), message broker, and server function port numbers are different
Notes on the timing of backups and restorations
When backup and restore are executed, it will be necessary to restart Systemwalker Software Configuration Manager. When linked to ServerView Resource Orchestrator, it will be necessary to restart Systemwalker Software Configuration Manager and ServerView Resource Orchestrator. For this reason, the operator should execute backup and restore in a time zone that does not use Systemwalker Software Configuration Manager and ServerView Resource Orchestrator.
The statuses of patch application, patch distribution, parameter setting, and script execution that were in effect at the time of backup will be restored. If restore is performed using backup resources for which script execution is in progress, operation will be resumed. Before performing backup, confirm that patch application, patch distribution, parameter setting, and script execution are not running.
If backup is executed while a Systemwalker Operation Manager job/job net/group is running, and that information is then restored, the job/job net/group that is running will end abnormally with the exit code 239. It is recommended that you execute this operation in a time zone in which the job/job net/group are not executed.
Handling backup resources
When moving backup resources to the restoration target, move the directory specified as the backup directory and all its files.
Do not delete the backup resources in the directory specified as the backup directory until the restoration completes.
The backup command cannot be used to back up data to the following types of media:
Optical disks such as CD-Rs and DVD-Rs
To save user assets to optical disks, first back up the data to the local disk, and then, write it to the media using a dedicated optical disk writer, for example.
Network paths [Windows]
Directories whose pathnames include spaces
Operations during backups and restorations
Do not operate the following middleware products during backups or restorations:
Interstage Application Server
Systemwalker Runbook Automation
Systemwalker Operation Manager
Systemwalker Centric Manager
Systemwalker Software Configuration Manager
