# Restoring Sybase Databases to a Different Location (Out of Place)

You can restore Sybase databases to a different location (out of place).

## 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.

- If you want to restore encrypted database keys, either the source or the destination can be encrypted but not both. You cannot restore encrypted database keys if both the source and destination are encrypted.

- 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 HADR components, including Fault manager and RMA.

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

## Procedure

1. From the Command Center 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 , 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. Select Out of place.

5. From the Restore type list, select one of the following:

   - Cross Instance Restore

   - Restore to disk

6. If you select Cross Instance Restore, complete the following steps:

   1. Select the Destination server and the Destination instance.

   2. From the Destination node list, select a physical destination node.

      Note

      - The Destination node field only appears when you select Sybase HADR client from the Destination server list and Sybase HADR instance from the Destination instance list.

      - If you select destination node as Auto detect, it automatically detects the primary node for restore.

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

   3. To change the database name and device path where you want to restore the database, complete 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

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

         If you select this check box, after the restore is complete, the restored databases are brought online.

7. If you select Restore to disk option, do the following:

   1. From the Destination client list, select the destination client.

   2. Select the time period for data that you want to include in the restore.

   3. From the Job(s) list, select the jobs to restore.

   4. In the Destination folder box, enter the path to restore the data to.

   5. Move the Impersonate user toggle key to the right to use a different account that contains the required privileges, and then enter the user name and password of the user account.

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. Select the Notify user on job completion checkbox to send a notification email when the restore job is completed.

10. You can configure a schedule to repeat this restore operation. To create a schedule, do the following:

    1. Click Schedule.

       The Add schedule dialog box appears.

    2. In the Name box, type a name for the schedule.

    3. Configure the Frequency and Repeat parameters.

    4. To specify exceptions to the schedule, click Exceptions.

       The Exceptions dialog box appears.

    5. Configure the exception parameters:

       - You can click Add Exception to save a set of exception parameters and continue adding sets of exception parameters.

       - Click Save when you have finished configuring the exception parameters.

    6. Under the Range of recurrence section, specify the Start date and End date to schedule the recurrence range of the restore operation.

    7. To save the schedule and return to the restore dialog box, click Schedule.

11. 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.

×

Loading...