> Software > Databases > Sybase > Sybase High Availability Disaster Recovery (HADR)

Restoring Sybase Databases to the Current Location (In Place)

You can restore Sybase databases to the current location (in place).

For an in-place restore operation, the destination client and the destination instance are the same as the source client and the source instance.

Before You Begin

  • Verify that the time zone for the Sybase operating system user profile and the root user profile on the client is the same.

  • To handle client-side encryption key name conflicts, configure the bmodifyKeyNameOnCollision additional setting to True.

  • The user needs to do the following before performing system database restores on destination Sybase server:

    • Deactivate all Sybase HADR components, including Fault manager and Replication management agent (RMA).

    • Stop the HADR system. For more information, see Starting and Stopping the HADR System.

Procedure

  1. From the navigation pane, go to Protect > Databases.

    The Overview page appears.

  2. On the Instances tab, in the row for the database instance that you want to restore, click the Action button action_button, and then click Restore.

    The Backup content page appears.

  3. Select the content to restore, and then click Restore.

    The Restore options dialog box appears.

  4. Leave the In place option selected.

  5. From the Destination node list, select the destination physical node. If the destination node is selected as Auto detect, it automatically detects the primary node for database restore.

    Note

    If you select any specific destination node apart from Auto detect, the restore is performed only on the selected node.

  6. To change the database name and device path where you want to restore the database, do the following:

    1. Click Redirect Options.

      The Redirect options dialog box opens.

    2. Select a database and click Save.

    3. To find the database restore path and replace that with the new physical path, click Find and Replace.

      You can find the database restore path using the following properties:

      • Source device name

      • Source device physical path

      • Source device size

  7. To recover the databases at a specific point in time, select the Recover databases check box.

    Selecting this check box will bring the databases in the online state after the restore operation is complete.

  8. Under Pre or Post options, do the following:

    • In the Pre recovery command box, enter the name or path of the process to run before the restore. Alternately, select the file icon on the right side to select a physical client from the Physical client selection list.

    • In the Post recovery command box, enter the name or path of the process to run after the restore. Alternately, select the file icon on the right side to select a physical client from the Physical client selection list.

    • To run a post process for all restore operation attempts of a job phase whether it is successful, interrupted, suspended, or when the job fails, select Run post restore process for all attempts.

    • If you want to initiate pre and post restore commands as a user, move the Run as User toggle button to right, and then in the User name box, enter a user name.

  9. To send a notification email when the restore job completes, leave the When the job completes, notify me via email option selected.

  10. Click Submit.

Note

After a full server restore, both the primary and standby nodes remain inactive and in standby mode. Configure the system as primary and activate it by executing sap_hadr_admin primary followed by sap_hadr_admin activate. On the configured replication port, enable replication between the primary and secondary nodes by running sap_enablereplication primary on the primary node and sap_enablereplication secondary on the Secondary node. The sap_materialize command is not required in this scenario.

What to do next

After performing a full server restore, manually restart the replication agents and make sure all databases involved in replication are fully set up and synchronized.

×

Loading...