Failback or restore steps for object configuration

Use the following steps on a protocol node in the primary cluster to fail back or restore the object configuration data.

You need to determine the object_database_node on the primary cluster once repaired or replaced.

Object database node: This is the CES IP address which is configured to run the postgresql-obj database for object services. You can find this value as the address designated as the object_database_node in the output of the mmces address list command. For example:
```
mmces address list

Address        Node      Group   Attribute
--------------------------------------------------------------
10.0.100.115   vwnode3   none    object_database_node
10.0.100.116   vwnode3   none    object_singleton_node
```

Important:

The following object steps must be run on the node designated as object_database_node in the primary cluster. This ensures that postgresql-obj and Keystone servers can connect during this configuration process.

Stop the object protocol services using the following command:
```
mmces service stop OBJ --all
```
Restore the Postgres database information to the shared root directory. The directory needs to be first cleaned out before the archive is restored. This can be done with commands similar to the following, assuming that the directory was tar/zip when it was backed up:
1. Delete the old Postgres data:
```
rm -rf <shared_root_location>/object/keystone/*
```
2. Verify that the shared root directory is empty:
```
ls <shared_root_location>/object/keystone
```
3. Restore the current Postgres database:
```
tar xzf <tar_file_name>.gz -C <shared_root_location>
```
4. Delete the process status file from the primary:
```
rm -rf <shared_root_location>/object/keystone/postmaster.pid
```
5. List the Postgres files:
```
ls <shared_root_location>/object/keystone
```
Restore all object configuration CCR files except objRingVersion with a command similar to the following:
```
mmccr fput <file> <location>/<file>
```
If object policies are present, restore all of the object policy related CCR files (that is *.builder and *.ring.gz files).
Restore the object configuration CCR file objRingVersion.
Restore all object configuration CCR variables with a command similar to the following:
```
mmccr vput name value
```
Start the object protocol services using the following command:
```
mmces service start OBJ --all
```