Full System Restore Using the BAR Portlets - BAR - Data Stream Architecture - Follow these steps to do a full system restore of DBC and user data, using BAR portlets.

Teradata® DSA User Guide

Product
BAR
Data Stream Architecture
Release Number
16.20
Published
November 2019
Language
English (United States)
Last Update
2019-11-27
dita:mapPath
xfr1514490991957.ditamap
dita:ditavalPath
3150_DSA_UG_1650-working-RR-new.ditaval
dita:id
B035-3150
lifecycle
previous
Product Category
Software
Teradata Tools and Utilities
Prerequisite
When restoring an archive made on a source system with hardware block-level compression, you must install the hardware compression driver package (teradata-expressdx) on all TPA nodes of the destination system. The installation requires a reboot of these nodes. Because it allows the destination system to read the compressed archive, this requirement applies even if the destination system is not set up for hardware compression.
The teradata-expressdx driver package is provided with systems that are equipped with compression hardware.
For additional information, see the Teradata Vantage™ - Advanced SQL Engine Node Software Migration Guide or Teradata® Database Node Software Migration Guide specific to your database version.
These steps wipe the system. Use these steps for a full system restore.

The backup jobs must have successfully completed to create restore jobs from the save sets.

You must create four restore jobs from the two backup job save sets. One includes only the DBC database and three are from the save set that includes all the databases under DBC and excludes DBC.

  1. On the destination system, run SYSINIT with options appropriate to your system.
  2. On the destination system, check the Time Zone setting status , and disable the setting if it is enabled.
  3. On the destination system, start the DBS Database Initializing Program (DIP) and run the following:
    • [Advanced SQL Engine / Teradata Database 15.0 and later] Run the DIPMIG script, which runs DIPERRS, DIPDB, DIPVIEWS, DIPVIEWSV, and DIPBAR.
    • [Teradata Database 14.10] Run the DIPERRS, DIPVIEWS, and DIPBAR scripts (1, 4, and 21).
  4. From the BAR Setup portlet, check the activation status of the destination system and do one of the following: [DSA 16.10 and later]
    • If the destination system is configured and enabled in the BAR Setup portlet, click Update for Selector: Update system selector for JMS messages.
    • If the destination system is not configured in the BAR Setup portlet, add the system and click Apply.
    [Prior to DSA 16.10]
    • If the destination system is configured and enabled in the BAR Setup portlet, click Deactivate System, and then click Update system selector for JMS Messages.
    • If the destination system is not configured in the BAR Setup portlet, add the system and click Activate System.
  5. On the destination system, start DSMain from the Database Window (DBW) console supervisor screen by entering: start bardsmain -d DSCName , where DSCName is the unique name of your DSC server
  6. [DSA 16.0 or earlier] After DSMain starts, activate the system in the BAR Setup portlet.
  7. Enable logons for the DBC user only. On the destination system, enter the following from the DBW console supervisor screen: enable dbc logons
  8. Create a DBC-only restore job from the backup job save set that saved only the DBC database:
    Important: You need two sets of credentials for these steps: the DBC user and password for the target system and the DBC user and password for the source system.
    1. In the Bar Operations Saved Jobs view, click "" for the DBC only backup job, and select Create Restore Job.
    2. Enter a Job Name, such as Restore-DBC-Only.
    3. Select a Destination System from the list.
    4. When prompted, enter logon credentials for the current DBC user and password for the target system.
    5. Select a Target Group from the list.
    6. Click the Job Settings tab, then select Set Credentials to enter the credentials for the DBC user and password of the source system at the time the backup save set was generated.
    7. Click Save.
    8. Click "" for Restore-DBC-Only and select Run.
    After the DBC restore is complete, the DBC password is set to the source system DBC password.
    TroubleshootingIf there are any errors, follow the instructions in the log file to correct the problem and run the post dbc script again.
    • The post restore script output log files are saved in /var/opt/teradata/tdtemp/post_restore_dbs version .
    • If the DBC restore job fails, check the DSC job status log to correct the issue.
    • If the failure occurs before the postscript phase, you must run SYSINIT before rerunning the restore job.
    If you ran post_dbc_restore manually, you must update the JMS system selector in the BAR Setup portlet once post_dbc_restore completes successfully.
    • [DSA 16.10 and later]
      • If the destination system is configured and enabled in the BAR Setup portlet, click Update for Selector: Update system selector for JMS messages.
      • If the destination system is not configured in the BAR Setup portlet, add the system and click Apply.
    • [Prior to DSA 16.10]
      • If the destination system is configured and enabled in the BAR Setup portlet, click Deactivate System, and then click Update system selector for JMS Messages.
      • If the destination system is not configured in the BAR Setup portlet, add the system and click Activate System.
  9. Create a SYSLIB database restore job from the DBC ALL backup save set:
    1. In the Bar Operations Saved Jobs view, click "" on the backup job created for the databases under DBC, and select Create Restore Job.
    2. Enter a Job Name, such as Restore-SYSLIB.
    3. Select a Destination System from the list.
    4. When prompted, enter logon credentials for the current DBC user and password for the destination DBS.
    5. Select a Target Group from the list.
    6. On the Objects tab, clear the top checkbox, then expand the tree and select the checkbox for only SYSLIB.
    7. Click Save.
    8. Click "" on Restore-SYSLIB and select Run.
  10. Create a restore job for all other data from the DBC ALL backup save set (excluding SYSLIB and TD_SERVER_DB):
    1. In the Bar Operations Saved Jobs view, click "" for the backup job for the databases under DBC, and select Create Restore Job.
    2. Enter a Job Name, such as Restore-DBC-All.
    3. Select a Destination System from the list.
    4. When prompted, enter logon credentials for the current DBC user and password for the destination DBS.
    5. Select a Target Group from the list.
    6. [Advanced SQL Engine / Teradata Database 15.00 or later] Clear the checkbox for TD_SERVER_DB in the Objects tab. TD_SERVER_DB has dependencies that must be met before restoration.
    7. [Advanced SQL Engine / Teradata Database 15.00 or later] Clear the checkbox for SYSLIB in the Objects tab.
    8. Click Save.
    9. Click "" for Restore-DBC-All and select Run.
    10. If there are any errors, follow the instructions in the log file to correct the problem and run the post data script again. The post restore script output log files are saved in /var/opt/teradata/tdtemp/post_restore_dbs version .
  11. [Advanced SQL Engine / Teradata Database 15.00 and later] From the BAR Operations Saved Jobs view, create a TD_SERVER_DB restore job from the backup job save set of the databases under DBC, excluding DBC:
    1. Click "" for the backup job for the databases under DBC, and select Create Restore Job.
    2. Enter a Job Name, such as Restore-TD_SERVER_DB.
    3. Select a Destination System from the list.
    4. When prompted, enter logon credentials for the current DBC user and password for the destination DBS.
    5. Select a Target Group from the list.
    6. On the Objects tab, clear the top checkbox, then expand the tree and select the checkbox for only TD_SERVER_DB.
    7. Click Save.
    8. Click "" on Restore-TD_SERVER_DB and select Run.
  12. On the destination system, start the DIP and run the DIPALL script.
  13. If you disabled the Time Zone setting on the destination system, enable it .
  14. On the destination system, from the DBW console supervisor screen, enable logons for all users. enable logons