Create a Restore Job Definition - SAP HANA

ECX leverages Copy Data Management technology for recovering application databases through Database Restore jobs. Your SAP HANA 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.

BEFORE YOU BEGIN:

CONSIDERATIONS:

  • Note that the End Job Session (No Cleanup) option leaves the temporary database and volumes intact. The Cancel Restore option removes mounts, but the original database is no longer usable and must be restored from a backup

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

To create a SAP HANA Restore job definition:

  1. Click the Jobs Monitor tab icon tab. Expand the Database folder, then select SAP HANA.
  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 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. Click Destination Destination icon . Select a source site and an associated database. Review the destination's database name mapping settings.
  9. To create the job definition using default options, click Create Job. The job can be run manually from the Jobs Monitor tab icon tab.
  10. To edit options before creating the job definition, click Advanced. Set the job definition options.
    11. ClosedApplication Options
  11. Rename Mount Points
  12. For more information about the Rename Mount Points options, see Restore Jobs - Rename Mount Points and Initialization Parameter Options.
    13. ClosedPolicy Options
  13. Continue with next source on failure
  14. 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.
  15. Automatically clean up resources on failure
  16. Enable to automatically clean up allocated resources as part of a restore if the database recovery fails.
  17. Allow to overwrite and force clean up of pending old sessions
  18. 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.
  19. Allow to overwrite vDisk
  20. In cases where the Make Permanent option is enabled, and the destination VM has conflicting VMDK files, enable the Allow to overwrite vDisk option to delete the existing VMDK and overwrite it with the selected source.
  21. Job-Level Scripts
  22. 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.
  23. 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 Scripts icon view on the Configure Configure tab icon tab. See Configure Scripts.
  24. 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.
  25. Repeat the above procedure to add additional Pre-Scripts and Post-Scripts. For information about script return codes, see Return Code Reference.
  26. 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.
  27. Select Continue operation on script failure to continue running the job if a command in any of the scripts associated with the job fails.
    28. ClosedStorage Options
  28. Make Permanent
  29. 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.
  30. Enabled - Always make permanent through full copy FlashCopy
  31. Disabled - Never make permanent
  32. User Selection - Allows the user to select Make Permanent or Cleanup when the job session is pending
  33. Protocol Priority
  34. 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.
  35. Optionally, expand the Notification section to select the job notification options.
  36. SMTP Server
  37. 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.
  38. Email Address
  39. Enter the email addresses of the status email notifications recipients. Click Add Add Node icon to add it to the list.
  40. 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.
  41. 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.
  42. 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.

Restoring a SAP HANA Instance Through the SAP HANA Client

After the ECX SAP HANA Instant Disk Restore job completes, you must restore the data volume, then finalize the restore using SAP HANA Client. Note that this procedure applies only to Instant Disk Restore jobs jobs utilizing the Make Permanent option.

Note: Users of SAP HANA 2.0 SP1 or later must register their systems with the Multiple Containers mode and the System database option selected. Further options specific to SAP HANA 2.0 SP1 or later are specified in the procedure below.

  1. On the SAP HANA Client, right-click the SAP HANA system and select Backup and Recovery, then select Recover System. SAP HANA 2.0 SP1 users should select Recover System Database. The SAP HANA system shuts down in preparation for the recovery.
  2. From a command line, perform the following steps:
  3. Unmount the original data volume (if present) through the following command: umount /<path of data installation> e.g. umount /hana/data
  4. Unmount the data volume recovered by ECX through the following command: umount /<path of recovered volume> e.g. umount /dev/sde1
  5. Mount the new data volume again through the following command: mount </dev/mapper/newID> /<path of original data installation> e.g. mount /dev/sde1 /hana/data
  6. For SAP HANA 2.0 SP1 or later environments: Back in the SAP HANA Client interface, keep the default selections and click Next until the last of the backup options display, then click Finish. Right-click the SAP HANA system and select Recover Tenant Database to continue with the recovery.
  7. For all SAP HANA versions: Back in the SAP HANA Client interface, on the Specify Recovery Type screen, select the Recover the database to a specific data backup or storage snapshot option, then click Next.
  8. In the Backup Location screen, keep the default selections and click Next.
  9. In the Select a Backup screen, select the backup marked with a green availability then continue clicking Next until the last of the backup options displays, then click Finish.
  10. Start the SAP HANA system.

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.

RELATED TOPICS:

 

Catalogic ECX™ 2.7.3

© 2018 Catalogic Software, Inc. | All rights reserved. | 9/18/2018

MySupport | Knowledge Base | Trademarks | info@catalogicsoftware.com