Typical Workflow for Backing Up and Restoring a Service Instance
To back up and restore an Oracle Java Cloud Service instance, consider this typical workflow.
Task | Description | More Information |
---|---|---|
Add a backup configuration to a service instance |
If you created an Oracle Java Cloud Service instance without configuring backups, you must add a backup configuration to the instance before performing other backup tasks. |
Add a Backup Configuration to an Oracle Java Cloud Service Instance |
Configure backups for a service instance |
Customize the following properties of backups for a service instance:
|
Configure Scheduled Backups for an Oracle Java Cloud Service Instance |
Initiate an on-demand backup of a service instance |
Create a backup immediately without having to wait for the next scheduled backup. |
|
Delete a backup |
Delete a backup that you no longer require to release storage or prevent an Oracle Java Cloud Service instance from being restored from the backup. |
|
Restore a service instance from a backup |
Undo configuration changes you don’t want by returning an Oracle Java Cloud Service instance to a particular state. |
|
Restore the database from a backup |
Restore the Oracle database that's associated with your Oracle Java Cloud Service instance. | |
Return an instance to service after restoration from a backup |
If necessary, manually modify a restored Oracle Java Cloud Service instance to ensure that it is in a consistent and valid state. |
Returning an Oracle Java Cloud Service Instance to Service After Restoration from a Backup |
Access files within a backup |
While testing or troubleshooting, use the REST API to extract the contents of an existing backup on the Administration Server node. |