Image Update Error Occurred when Backup/Restore Run on Source Instance

After Backup/Restore was run from 21.3 to 21.4, Image Update may not work if the volumes are not named according to the original deployment naming conventions.

Workaround: Rename the attached volumes before running Image Update.

Note:

Ensure that you have policy to manage instance-family, to attach block volumes to the compute instance. For example:

allow dynamic-group marketplace-test-dynamic-group to manage instance-family in compartment test

Stop Essbase instance.

/u01/config/domains/essbase_domain/esstools/bin/stop.sh

Unmount data volume.
```
sudo umount /u01/data
```
Detach the data volume (on OCI console page).
Rename the data volume as tag-data-volume on OCI console page, where tag is a user-chosen name given at the time of the initial deployment.

Reattach the data volume using the following OCI CLI command (as opc user):

for 19.3.6.0, or 21.3 and higher:

oci compute volume-attachment attach-iscsi-volume --instance-id $instanceid
--volume-id $datavolumeid --display-name data-volume --auth
instance_principal

for 19.3.0.3.4 or 19.3.0.4.5

oci compute volume-attachment attach-iscsi-volume --instance-id $instanceid
--volume-id $datavolumeid --display-name data-volume-attachment --auth
instance_principal

for 19.3.0.2.3 or 19.3.0.0.2

oci compute volume-attachment attach-iscsi-volume --instance-id $instanceid
--volume-id $datavolumeid --display-name tag-data-volume-1-attachment --auth
instance_principal

where instanceid is the OCID of the compute instance and datavolumeid is the OCID of the data volume.

Use the iSCSI commands listed in the OCI console to connect your newly attached target block volumes.
Mount the data volume.
```
sudo mount -a
```
Start the Essbase instance. Note that this step is not necessary, but it validates that the process is working.
```
/u01/config/domains/essbase_domain/esstools/bin/start.sh
```
Perform Image Update to Essbase 21.4.