Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products

PowerProtect Data Manager 19.15 SAP HANA User Guide

Performing restore with dependency chaining or replication storage

Perform the following steps for a restore that involves dependency chaining between save sets of two different storage targets or a restore from a replication storage target.

  1. Edit the existing auto configuration file, and append the following [SECONDARY_SYSTEM] information in the file. Modify the configuration file parameter settings provides details about the configuration file.

    NOTE:

    The secondary CLIENT parameter is optional. If specified, then the query of the secondary storage target is performed by using the secondary client name. If not specified, then the query is performed by using the primary client name.

    Successive auto-configuration requests will overwrite the auto configuration file. To preserve the details from the file, make a copy of the file.

    [SECONDARY_SYSTEM]
    CLIENT=<client_name_used_during_backup>
    DDBOOST_USER = <DD_username>
    DEVICE_HOST = <DD_IP_address>
    DEVICE_PATH = <DD_storage_unit>
    

    For example:

    [SECONDARY_SYSTEM]
    CLIENT=newdb
    DDBOOST_USER = mypolicy-0662e093dd6b-37247
    DEVICE_HOST = 10.118.156.240
    DEVICE_PATH = /mypolicy-0662e093dd6b-37247
    
  2. In SAP HANA Studio, set all the following parameters to the pathname of the auto configuration file:

    • log_backup_parameter_file
    • data_backup_parameter_file
    • catalog_backup_parameter_file
  3. Start the restore from SAP HANA Studio. Performing restore and recovery by using SAP HANA Studio provides details.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\