Create a Restore Job Definition - Oracle

ECX leverages Copy Data Management technology for recovering application databases through Database Restore jobs. Your Oracle clones can be utilized and consumed instantly through ECX Instant Disk Restore jobs. ECX catalogs and tracks all cloned instances. Instant Disk Restore leverages ISCSI or fibre channel protocols to provide immediate mount of LUNs without transferring data. Snapshotted databases are cataloged and instantly recoverable with no physical transfer of data. Point-in-time recovery is supported with log forwarding.

The following Oracle Database workflows are supported: DevOps, which provides Instant Disk Restore or Instant Recovery to a new location using a masked image, created through a Restore job with data masking enabled, Instant Database Recovery, which provides Instant Disk Restore or Instant Recovery using a non-masked image and point-in-time transaction logs, and Instant Disk Restore, which mounts a database for RMAN restores with application and operating system support.

BEFORE YOU BEGIN:

  • Create and run an Oracle Backup job. See Create a Backup Job Definition - Oracle.
  • Review Oracle requirements. See Oracle Requirements and Oracle Database Support FAQ.
  • To ensure that filesystem permissions are retained correctly when ECX moves Oracle data between servers, ensure that the user and group IDs of the Oracle users (e.g. oracle, oinstall, dba) are consistent across all the servers. Refer to Oracle documentation for recommended uid and gid values.
  • Note that an automated disk mount of an ECX backup on LVM storage must not have the original disk for that backup still present and mounted while the lvm2-lvmetad service is active on the system. If Oracle data resides on LVM volumes, you must stop and disable the lvm2-lvmetad service before running Backup or Restore jobs. To disable the lvm2-lvmetad, run the following commands:

    systemctl stop lvm2-lvmetad

    systemctl disable lvm2-lvmetad

    Next, disable lvmetad in the LVM config file. Edit the file /etc/lvm/lvm.conf and set:

    use_lvmetad = 0

  • For email notifications, at least one SMTP server must be configured. Before defining a job, add SMTP resources. See Register a Provider.
  • You must add credentials to the destination virtual machine when recovering with the subnet option. See Add Credentials to a Virtual Machine.

ORACLE DATABASE CONSIDERATIONS:

  • Note that RAC databases cannot be recovered to their original location while the protected (source) database is still running, even if a new name is chosen for the recovered database. You must either recover the database to another cluster, or shut down the source database before recovering a copy to the same cluster.
  • For Oracle 12c databases, backups are created without placing the database in BACKUP mode through Oracle Storage Snapshot Optimization. All associated snapshot functionality is supported.
  • Note that point-in-time recovery is not supported when one or more datafiles are added to the database in the period between the chosen point-in-time and the time that the preceeding Backup job ran.
  • To properly recover Oracle databases, the ORACLE_BASE environment variable must be set in the login environment of the user that owns the Oracle home. In cases where multiple homes exist on a node, each with a different owner, the variable must be set for each of the owners.

Best Practice: Create a schedule before creating a job definition so that you can easily add the schedule to the job definition.

To create an Oracle Restore job definition:

  1. Click the Jobs Monitor tab icon tab. Expand the Database folder, then select Oracle.
  2. Click New New icon, then select Restore. The job editor opens.
  3. Enter a name for your job definition and a meaningful description.
  4. Select a template. Available options include DevOps DevOps icon , Instant Database Restore Restore icon , and Instant Disk Restore Instant Access icon .
  5. Click Source Source icon . From the drop-down menu select Application Browse to select a source site and an application server to view available database recovery points. Select resources, and change the order in which the resources are recovered by dragging and dropping the resources in the grid.
  6. Alternatively, select Application Search from the drop-down menu to search for application servers with available recovery points. Add copies to the job definition by clicking Add. Change the order in which the resources are recovered by dragging and dropping the resources in the grid.
  7. Click Copy Copy icon . Sites containing copies of the selected data display. Select a site. By default the latest copy of your data is used. To choose a specific version, select a site and click Select Version. Click the Version field to view specific copies and their associated job and completion time. If recovery from one snapshot fails, another copy from the same site is used.
  8. If creating an Instant Database Restore Restore icon job definition, an additional recovery option is available through the Select Version feature. Enable Allow Point-in-Time selection when job runs to leverage archived logs and enable a point-in-time recovery of the databases.
  9. If creating an Instant Disk Restore Instant Access icon job definition, the RMAN tag displays next to the time in the Version field. An Oracle administrator can correlate the RMAN backups to the ECX versions during job creation.
  10. Click Destination Destination icon . Select a source site and an associated Oracle home. Click the Destination field to enter an optional alternate name for the database.
  11. To create the job definition using default options, click Create Job. The job can be run manually from the Jobs Monitor tab icon tab.
  12. To edit options before creating the job definition, click Advanced. Set the job definition options.
  13. Optionally, expand the Notification section to select the job notification options.
  14. SMTP Server
  15. From the list of available SMTP resources, select the SMTP Server to use for job status email notifications. If an SMTP server is not selected, an email is not sent.
  16. Email Address
  17. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
  18. Optionally, expand the Schedule section to select the job scheduling options. Select Start job now to create a job that starts the job immediately. Select Schedule job to start at later time to view the list of available schedules. Optionally select one or more schedules for the job. As each schedule is selected, the schedule's name and description displays.
  19. Note: To create and select a new schedule, click the Configure Configure tab icon tab, then select Schedules Schedule icon. Create a schedule, return to the job editor, refresh the Available Schedules pane, and select the new schedule.
  20. When you are satisfied that the job-specific information is correct, click Create Job. The job runs as defined by your schedule, or can be run manually from the Jobs Monitor tab icon tab.

NEXT STEPS:

  • If you do not want to wait until the next scheduled job run, run the job session on demand. See Start, Pause, and Hold a Job Session.
  • Track the progress of the job session on the Jobs tab. See Monitor a Job Session.
  • If notification options are enabled, an email message with information about the status of each task is sent when the job completes.

 


Catalogic ECX™ 2.6

© 2017 Catalogic Software, Inc. | All rights reserved. | 6/12/2017

MySupportKnowledge Base | Trademarks | info@catalogicsoftware.com