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:
- Click the Jobs tab. Expand the Database folder, then select Oracle.
- Click New , then select Restore. The job editor opens.
- Enter a name for your job definition and a meaningful description.
- Select a template. Available options include DevOps , Instant Database Restore , and Instant Disk Restore .
- Click Source . 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.
- 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.
- Click Copy . 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.
- If creating an Instant Database Restore 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.
- If creating an Instant Disk Restore 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.
- Click Destination . Select a source site and an associated Oracle home. Click the Destination field to enter an optional alternate name for the database.
- To create the job definition using default options, click Create Job. The job can be run manually from the Jobs tab.
- To edit options before creating the job definition, click Advanced. Set the job definition options.
- Record mounted copies in RMAN local repository
- This option is available for Instant Disk Restore workflows.
- Select this option to catalog mounted copies into RMAN at the end of the Instant Disk Restore job. This option is an alternative to the cataloging of ECX-created copies during a Backup job. If the RMAN cataloging option is selected in the Backup job definition, every copy created by ECX is cataloged in the source database immediately after the copy is created. By contrast, this option allows you to perform cataloging on-demand only for a specific copy and only when you intend to restore data from that copy through RMAN. Note that for the cataloging to succeed the target database must be running at the time the Instant Disk Restore job runs.
- Rename Mount Points and Database Initialization Parameters
- For more information about the Rename Mount Points and Database Initialization Parameters (Instant Database Recovery and DevOps workflows only) options, see Restore Jobs - Rename Mount Points and Initialization Parameter Options.
- ASM Disk Names
- Continue with next source on failure
- Toggle the recovery of a resource in a series if the previous resource recovery fails. If unselected, the Restore job stops if the recovery of a resource fails.
- Automatically clean up resources on failure
- Enable to automatically clean up allocated resources as part of a restore if the database recovery fails.
- Allow to overwrite and force clean up of pending old sessions
- Enabling this option allows a scheduled session of a recovery job to force an existing pending session to clean up associated resources so the new session can run. Disable this option to keep an existing test environment running without being cleaned up.
- Replace existing database
- This option is available for Instant Database Recovery workflows.
- Select this option to replace an existing database with the same name during recovery. When an Instant Database Recovery is performed for a database and another database with the same name is already running on the destination host/cluster, ECX shuts down the existing database before starting up the recovered database. If this option is not selected, the Instant Database Recovery fails when ECX encounters an existing running database with the same name.
- Leave database shut down after recovery
- This option is available for Instant Database Recovery and DevOps workflows.
- Select this option to shut down the recovered database once the recovery operation completes. The database can be started up manually once needed.
- Job-Level Scripts
- Job-level pre-scripts and post-scripts are scripts that can be run before or after a job runs at the job-level. A script can consist of one or many commands, such as a shell script for Linux-based virtual machines or Batch and PowerShell scripts for Windows-based virtual machines.
- In the Pre-Script and/or Post-Script section, click Select to select a previously uploaded script, or click Upload to upload a new script. Note that scripts can also be uploaded and edited through the Scripts view on the Configure tab. See Configure Scripts.
- Once complete, the script displays in the Pre-Script or Post-Script section. Click the Parameters field at add a parameter to the script, then click Add. Note additional parameters can be added to a script by entering parameters one at a time in the field, then clicking Add. Next, click the Identity field to add or create the credentials required to run the script. Finally, click the Application Server field to define the location where the script will be injected and executed.
- Repeat the above procedure to add additional Pre-Scripts and Post-Scripts. For information about script return codes, see Return Code Reference.
- For Restore job post-scripts only, the positional arguments state and status can be passed to the script. For information about this feature, see Using State and Status Arguments in Postscripts. State and status arguments are not supported for Backup jobs.
- Select Continue operation on script failure to continue running the job if a command in any of the scripts associated with the job fails.
- Make Permanent
- Set the default permanent restoration action of the job. All database recovery operations can leverage Instant or Test modes and then either be deleted or promoted to permanent mode. This behavior is controlled through the Make Permanent option.
- Enabled - Always make permanent through full copy FlashCopy
- Disabled - Never make permanent
- User Selection - Allows the user to select Make Permanent or Cleanup when the job session is pending
- Protocol Priority
- If more than one storage network protocol is available, select the protocol to take priority in the job. Available protocols include iSCSI and Fibre Channel.
- Optionally, expand the Notification section to select the job notification options.
- SMTP Server
- 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.
- Email Address
- Enter the email addresses of the status email notifications recipients. Click Add to add it to the list.
- 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.
- Note: To create and select a new schedule, click the Configure tab, then select Schedules . Create a schedule, return to the job editor, refresh the Available Schedules pane, and select the new schedule.
- 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 tab.
This option allows you to specify the disk naming pattern for restored ASM disks, if available. If Use default pattern is selected, ECX uses the default naming pattern, which is /dev/ecx-asmdisk/* in Linux environments or /dev/ecx_asm* in AIX environments. Select Specify a custom pattern to set ASM disks to follow any naming conventions that may be in use for existing disks. The custom pattern must begin with "/dev" and must end with an asterisk (*). During restore, ECX creates a device alias, or symlink, matching the specified pattern and replaces the asterisk with a unique disk name.
Note: This option has no effect if the database being restored does not use any ASM disks.
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.
MySupport | Knowledge Base | Trademarks | info@catalogicsoftware.com