Back Up and Restore an Oracle Integration Classic (User-Managed) Instance
In Oracle Integration Classic (user-managed), you can back up and restore your Oracle Integration Classic instances to return their software and data to a particular state.
About Backing Up and Restoring an Oracle Integration Classic (User-Managed) Instance
By backing up your Oracle Integration Classic (user-managed) instances, you can preserve them in a particular state..
When you create an Oracle Integration Classic instance, you can choose whether or not to enable backups. These backups are recorded to local node storage as well as to an Oracle Cloud Infrastructure Object Storage Classic container.
What a Backup Contains
The contents of a backup depend on whether it is a full backup or an incremental backup.
A full backup contains all the runtime artifacts required to restore the instance’s configuration data. An incremental backup contains changes to configuration data on all nodes since the last scheduled full backup.
Note:
All incremental backups are automated scheduled backups. You cannot create an incremental backup on demand.
Contents of a Database Backup
A database backup contains Oracle database instance Oracle Fusion Middleware component schemas, and application data for an Oracle Integration Classic instance.
Note:
Only scheduled automated backups of an Oracle Integration Classic back up the database instance. On-Demand backups do not perform a database backup. Alternatively, you can back up your database using the associated Oracle Database Cloud Service database used by the instance.
Where Backups Are Stored
Oracle Integration Classic stores all backups in an Oracle Cloud Infrastructure Object Storage Classic container. To speed up restorations from recent backups, Oracle Integration Classic also keeps a local copy of any backup it has recently created.Note:
Do not attempt to download the backup files generated by Oracle Integration Classic. These files are encrypted and not accessible offline. You must use Oracle Integration Classic to restore an instance from a backup.By default, Oracle Integration Classic stores backups in the container that was specified when the instance was created.
Oracle Integration Classic automatically deletes a backup when the retention period for the backup has elapsed.
How Local Copies of Backups Are Stored
Oracle Integration Classic stores local copies in a dedicated volume mounted on the block storage attached to the node where the Administration Server is running.
-
For an incremental backup, Oracle Integration Classic stores the local copy for seven days before deleting it.
-
For a full backup, Oracle Integration Classic stores the local copy for seven days, or as long as the local copy of its last related incremental backups was stored, whichever is longer.
How Backups and Local Copies Are Deleted Automatically
After completing the day’s scheduled backup, Oracle Integration Classic deletes any backups or local copies that are due to be deleted that day. If the scheduled backup fails because of insufficient space, backups and local copies that are due to be deleted will still be deleted.
Note:
When an Oracle Integration Classic instance is deleted, all its backups are deleted.
What Happens During a Backup
During a backup of an Oracle Integration Classic instance, the instance continues to run and all applications deployed to the instance remain available.To prevent configuration changes during a backup, Oracle Integration Classic locks the Oracle WebLogic Server domain if the administration server is running. After locking the domain, Oracle Integration Classic backs up files on each node.
While the backup is in progress, you cannot start any other management operation on the instance. Similarly, if the administration server is not running at the time a backup is started, do not attempt to start this server until the backup completes.
When the backup is complete, Oracle Integration Classic unlocks the Oracle WebLogic Server domain. If the backup is a scheduled backup, Oracle Integration Classic also cleans up older backups as follows:
-
From local storage it deletes all backups old enough to be stored only in the Oracle Integration Classic container.
-
From all storage locations it deletes any remaining copies of backups whose retention period has elapsed. The default is 30 days.
What Happens When an Instance Is Restored
When restoration of an instance is initiated, Oracle Integration Classic shuts down the servers in the instance. After the restoration is complete, Oracle Integration Classic restarts these servers.
If the instance contains any managed server nodes that are not in the backup, Oracle Integration Classic warns you that it cannot restore these nodes.
Before trying to restore again, you can scale in the instance to delete these nodes.
If you choose to continue without scaling in the instance, Oracle Integration Classic asks you to confirm that you understand that the instance will be scaled in automatically.
If the backup contains any managed server nodes that are not currently in the instance, Oracle Integration Classic does not attempt to remove these managed servers from the Oracle WebLogic Server domain. You must use the WebLogic Server to manually remove these managed servers from the domain configuration after restoring the instance.
Oracle Integration Classic does not automatically remove any existing Oracle WebLogic Server transaction records after restoring an instance from a backup.
Typical Workflow for Backing Up and Restoring an Oracle Integration Classic (User-Managed) Instance
To back up and restore an Oracle Integration Classic (user-managed) instance, consider this typical workflow.
Task | Description | More Information |
---|---|---|
Configure backups for an Oracle Integration Classic instance |
Customize the following properties of backups for a service instance:
|
Configure an Automatic Backup for an Oracle Integration Classic (User-Managed) Instance |
Initiate an on-demand backup of an Oracle Integration Classic 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 Integration Classic instance from being restored from the backup. |
|
Restore an Oracle Integration Classic instance from a backup |
Undo configuration changes you don’t want by returning an Oracle Integration Classic instance to a particular state. |
Quick Tour of the Backup Page
You can use the Backup page to back up and restore an Oracle Integration Classic (user-managed) instance, and to manage backups for the service instance.
Element | Description |
---|---|
Backups on Cloud Storage |
The total amount of space, in megabytes or gigabytes, that backups are occupying in the Oracle Cloud Infrastructure Object Storage Classic container for storing backups. This amount includes space that is occupied by backups that have been manually uploaded to the container, if any, in addition to the space occupied by backups that Oracle Integration Classic has moved there. |
Backup Volume Used |
The total amount of space, in megabytes or gigabytes, that local copies of backups are occupying in the backup volume on the block storage of the node where the Administration Server is running. |
Backup Volume Used (%) |
The percentage of the available space that backups are occupying in the backup volume on the block storage of the node where the Administration Server is running. |
Incremental Backups |
Indicates the schedule for running incremental backups. |
Full Backups |
Indicates the schedule for running full backups. |
Most Recent Backup |
Indicates that the most recent backup failed and the time of its failure. |
Last Successful Backup |
Indicates the time of the last successful backup. |
Backup Now |
Click this button to create an on-demand backup of the Oracle Integration Classic instance. |
Configure Backups |
Click this button to update the backup schedule and where backups are stored. |
Disable Backups or Enable Backups |
Click this toggle button to disable/enable automated and on-demand backups. |
Available Backups |
List of available backups. By default, only backups for the last seven days are listed. Use the search field to specify a range of dates for which you want backups returned. |
Enter the start date of the period for which you want to filter the list of available backups or the restoration history. By default, the start date is set to seven days before the current date. Enter the date in the format mm/dd/yyyy.
Alternatively, click the calendar icon to select the date from a calendar. |
|
Enter the end date of the period for which you want to filter the list of available backups or the restoration history. Enter the date in the format mm/dd/yyyy.
Alternatively, click the calendar icon to select the date from a calendar. Note: The end date must not be earlier than the start date. |
|
Click to filter the list of available backups or the restoration history to show only backups or restorations from within the period specified by the Search from Date field and the Search to Date field. |
|
|
In-progress backup for the Oracle Integration Classic instance. The backup will not be available for use in restoring the service instance until it is completed. The backup is identified by the date and time when the backup operation was started, which is displayed adjacent to icon that represents the backup. Click the icon to see additional information about the backup. |
|
Completed backup for the Oracle Integration Classic instance. The backup is available for use in restoring the service instance. The backup is identified by the date and time when the backup was created, which is displayed adjacent to icon that represents the backup. Click the icon to see additional information about the backup, including its start date, complete date, expiration date and size. If a database backup is included, its tag or timestamp is also displayed. |
Completed backup with a warning message. Oracle Integration Classic instance tried but failed to move or delete one or more older backups. For information about when and why Oracle Integration Classic instance moves or deletes older backups. The backup is still available for use in restoring the service instance. To find out why Oracle Integration Classic instance could not move or remove the older backup, place the cursor over the icon. The presence of the older backup may cause future backups to fail because of insufficient space. The backup is identified by the date and time when the backup was created, which is displayed adjacent to icon that represents the backup. Click the icon to see additional information about the backup. |
|
The backup is in the process of being deleted. Click the icon to see additional information about the backup. |
|
Type |
A comma-separated pair of words that describes the type of the backup. The first word in the pair describes the extent of the backup:
The second word in the pair indicates how the backup was initiated:
|
Available Until |
The date and time until which the backup will be retained. |
Contains |
A row of up to two icons that indicates the content of the backup:
|
Notes |
Click the link to display the notes that were provided when the backup was created or the restoration was performed. |
Click to select the following options:
|
|
Restore History (Last 7 Days) |
Click the triangle adjacent to this label to display a list of all the restoration operations on this service instance. By default, only restoration operations for the last seven days are listed. Use the search field to specify a range of dates for which you want restoration operations returned. Click Select to include unsuccessful restore attempts to include the unsuccessful restoration operations in the list. |
Completed restoration operation for the Oracle Integration Classic instance. The restoration operation is identified by the date and time when it was started, which is displayed adjacent to icon that represents the restoration operation. Click the icon to see additional information about the restoration operation. |
|
In-progress restoration operation for the Oracle Integration Classic instance. The restoration operation is identified by the date and time when it was started, which is displayed adjacent to icon that represents the restoration operation. Click the icon to see additional information about the restoration operation. |
|
Unsuccessful restoration attempt for the Oracle Integration Classic instance. The restoration attempt is identified by the date and time when it was started, which is displayed adjacent to icon that represents the restoration attempt. Click the icon to see additional information about the restoration attempt. |
|
From Backup |
The date and time when the backup from which the service instance was restored was created. |
Status |
The status of the restoration operation:
Click the text to see detailed status messages for the operation. |
Contains |
A row of up to two icons that indicates the items that were restored:
|
Configure an Automatic Backup for an Oracle Integration Classic (User-Managed) Instance
You can configure backups for an instance to customize when the Oracle Integration Classic (user-managed) instance is automatically backed up and how backups are stored.
Because the changes affect only one service instance, you can configure different values for these properties for each of your service instances. Specifically, you can customize the following properties of the service instance:
Initiate an On-Demand Backup
You can create a full backup immediately without having to wait for the next scheduled automatic backup.
Create a backup when making major changes to your Oracle Integration Classic (user-managed) instance, for example, in these situations:
-
Before any configuration changes that you may need to undo
-
Before deploying an application
-
After deploying an application
Note:
Do not attempt to start the administration server while a backup is in progress.
While the backup is in progress, you cannot start any other management operation on the service instance.
When the backup is complete, it is added to the list of available backups on the Backup page.
Disable or Enable Backups
Backups in an Oracle Integration Classic (user-managed) instance are enabled by default on a new service instance but you can disable and enable this feature as required.
After disabling backups for a service instance:
-
Scheduled backups will not run.
-
Automated backups will not run prior to patching or scaling operations.
-
You cannot take an on-demand backup.
Disabling backups for a service instance does not affect any backups that were taken previously.
- Sign in to the Oracle Cloud Infrastructure Console.
- Click the name of your Oracle Integration Classic instance.
- In the Service Overview page, click the Administration tile.
- Click the Backup tab.
- Click Manage backups on this service next to Available Backups and select Disable Backups.
- When prompted for confirmation click Disable Backups.
- To enable backups again at a later time, return to the Backup page and click Enable Backups.
Restore a Backup
You can restore an Oracle Integration Classic (user-managed) instance from a backup to return the service instance to a particular state or recover the service instance after a loss of data.
Note:
If you restore a service instance's configuration files from a backup in which the hosts do not match the hosts in the service instance, Oracle Integration Classic handles the mismatch as follows:
-
If the service instance contains any managed server hosts that are not in the backup, Oracle Integration Classic warns you that it cannot restore the managed server hosts that are not part of the backup.
Before trying to restore again, you can scale in the service instance to delete the nodes that correspond to these managed server hosts. See Scale In an Oracle Integration Classic (User-Managed) Instance
If you choose to continue without scaling in the service instance, Oracle Integration Classic asks you to confirm that you understand that the service instance will be scaled in automatically.
-
If the backup contains any hosts that are not in the service instance, Oracle Integration Classic does not attempt to remove the managed servers on these hosts from the administration server configuration. You must use Oracle WebLogic Server to remove the managed servers on these hosts from the administration server configuration.
After you restore a service instance's configuration files from a backup that does not match the service instance, you might need to modify the restored service instance to return it to the state you require.
You can restore a service instance from an incremental backup without the need to restore the full backup to which the incremental backup is linked. In this situation, you are responsible for ensuring that the service instance is in a consistent state after the service instance is restored.
Restoration from a backup that is stored on block storage is faster than restoration from a backup that is stored in an Oracle Cloud Infrastructure Object Storage Classic container.
Before restoring an Oracle Integration Classic instance from a backup, you must disable the load balancer for the service instance.
The applications deployed to your instance will be unavailable during the restoration process.
Delete a Backup
You can delete a backup that you no longer require to release storage or prevent an Oracle Integration Classic (user-managed) instance from being restored from the backup.
Note:
You can’t delete a full backup with linked incremental backups without deleting the incremental backups. If the backup you’re deleting has linked incremental backups, Oracle Java Cloud Service asks if you want to delete both the full backup and its linked incremental backups.