8.7.2 Maintaining Common Control and AdvancedCopy Manager Repository

Backup the common control and AdvancedCopy Manager repository.

Information

Notation in Procedure

Directory Name	Explanation
$BAK_DIR	Backup destination directory.

Prepare for the backup.
For non-cluster operations, execute the following shell script to stop the service.
```
# /opt/FJSVesfcm/bin/stop-webservice.sh
```
For cluster operations, perform the following procedure:
1. Stop all cluster transactions which the Manager belongs to.
  Refer to "Cluster Transaction and Local Transaction" in the Cluster Environment Setup Guide for details about cluster transaction.
2. Mount the shared disks on the primary node.
3. Start the ETERNUS SF Manager Postgres service.
```
# /etc/init.d/startSFmanager start-postgres
```
Create a backup data.
1. Create the following backup directories:
```
# mkdir -p $BAK_DIR/Common
```
2. Execute the following command to create a backup data with OS Administrator privilege.
  If you did not change the port number, specify 15432 for portNumber. If you did change the port number, specify the changed port number for portNumber.
  The file name of the created backup data is fileName.
```
# /opt/FJSVesfcm/postgres/bin/pg_dump -U esfpostgres -C --attribute-inserts -p portNumber -f $BAK_DIR/Common/fileName esfdb
```
3. The prompt is displayed, and waiting for input. Input the following strings.
```
master01!
```
Start the Manager.
For non-cluster operations, execute the following shell script to start the service.
```
# /opt/FJSVesfcm/bin/start-webservice.sh
```
For cluster operations, perform the following procedure:
1. Stop the ETERNUS SF Manager Postgres service.
```
# /etc/init.d/startSFmanager stop-postgres
```
2. Unmount the shared disk mounted in step 1.
3. Start all cluster transactions which the Manager belongs to.

Restore the common control and AdvancedCopy Manager repository.

Information

Notation in Procedure

Directory Name	Explanation
$BAK_DIR	Backup destination directory.

Prepare for the restoration.
For non-cluster operations, execute the following shell script to stop the service.
```
# /opt/FJSVesfcm/bin/stop-webservice.sh
```
For cluster operations, perform the following procedure:
1. Stop all cluster transactions which the Manager belongs to.
  Refer to "Cluster Transaction and Local Transaction" in the Cluster Environment Setup Guide for details about cluster transaction.
2. Mount the shared disks on the primary node.
3. Start the ETERNUS SF Manager Postgres service.
```
# /etc/init.d/startSFmanager start-postgres
```
Restore a backup data. The following procedure must be implemented by a user with administrator privileges for the operating system.
1. Execute the following command.
  If you did not change the port number, specify 15432 for portNumber. If you did change the port number, specify the changed port number for portNumber.
```
# /opt/FJSVesfcm/postgres/bin/psql -U esfpostgres -p portNumber postgres
```
2. The prompt is displayed, and waiting for input. Input the following strings in order.
```
master01!
drop database esfdb;
\q
```
3. Execute the following command to restore the backup data.
  If you did not change the port number, specify 15432 for portNumber. If you did change the port number, specify the changed port number for portNumber.
  The fileName is the file name specified when the backup data was created.
```
# /opt/FJSVesfcm/postgres/bin/psql -U esfpostgres -p portNumber -f $BAK_DIR/Common/fileName postgres
```
4. The prompt is displayed, and waiting for input. Input the following strings.
```
master01!
```
Start the Manager.
For non-cluster operations, execute the following shell script to start the service.
```
# /opt/FJSVesfcm/bin/start-webservice.sh
```
For cluster operations, perform the following procedure:
1. Stop the ETERNUS SF Manager Postgres service.
```
# /etc/init.d/startSFmanager stop-postgres
```
2. Unmount the shared disk mounted in step 1.
3. Start all cluster transactions which the Manager belongs to.

Note

After restoring the shared control repository, it takes approximately 2 minutes before Web Console becomes available.

8.7.2 Maintaining Common Control and AdvancedCopy Manager Repository

8.7.2.1 Backup of Common Control and AdvancedCopy Manager Repository

8.7.2.2 Restore of Common Control and AdvancedCopy Manager Repository