After restoring an Oracle Java Cloud Service instance from a backup, you may need to perform additional steps to return it back to a valid, consistent state.
If a service instance has been scaled since a backup was created, the topology of the service instance and the topology of the backup no longer match. If you restore the service instance's configuration files from the backup, how Oracle Java Cloud Service handles the mismatch depends on the cause of the mismatch.
You may also need to remove any records from the domain’s transaction log in the restored service instance.
- On the Backup Page, click the text Status Completed for the last successful restoration in the Restoration History of the service instance.A set of progress messages for the restoration is displayed.
- Examine the progress messages to determine whether the backup contained any hosts that are not in the service instance.
- If the backup contains additional nodes that are not in the current service instance, modify the service instance as follows:
- Use Oracle WebLogic Server to remove the managed servers on these nodes from the domain configuration.
- If you require your service instance to contain the number of nodes in the backup, scale out the service instance.When Oracle Coherence is enabled for a service instance: Scale out the Coherence data tier to also match the number of nodes in the backup.
- If you scaled out the service instance after the backup was taken, and you require your service instance to have the same number of nodes as the backup, scale in the service instance.When Oracle Coherence is enabled for a service instance: Scale in the Coherence data tier to also match the number of nodes in the backup.
- Remove any records from the transaction log in the Oracle WebLogic Server domain.Refer to the relevant documentation for the release of Oracle WebLogic Server that your service instance is running: