Disaster Recovery Sites | Backups | Vantage Console | VantageCloud Enterprise - Disaster Recovery - Teradata Vantage

Teradata® VantageCloud Enterprise
Deployment
VantageCloud
Edition
Enterprise
Product
Teradata Vantage
Release Number
3.1.0
Published
October 2025
ft:locale
en-US
ft:lastEdition
2025-12-10
dita:mapPath
gqe1746821105801.ditamap
dita:ditavalPath
lwe1652211139768.ditaval
dita:id
wec1649710665916
Product Category
Teradata Vantage
You can set up a disaster recovery (DR) solution with cross-site restore functionality of snapshots or backups.

Disaster Recovery with Snapshots

You can perform disaster recovery from snapshots and restore to cross-site. Make sure the following prerequisites are met:
CSR DR with Snapshot requires a CR to temporarily disable Data Dog alerts before the restore proceeds.
  • The database is on 17.10 version or later on both source and target systems.

    If you upgrade in VantageCloud Enterprise, the older snapshots become obsolete and you cannot use it for restorations. You can only restore to the same configuration and same versions. Post VantageCloud Enterprise upgrade, Teradata recommends taking a new Snapshot.

    CSR DR using Snapshots is available in VantageCloud Enterprise AWS and Azure sites only.

  • The number of nodes and AMPs must match on both systems.
  • The storage per node must be same or more in target system, as compared to source.
  • The VM type or size can vary, but must have the same number of AMPs per node.

See Creating a Standard Backup or Snapshot and Restoring a Snapshot for more details.

Disaster Recovery with DSA Backups

You can now perform disaster recovery or CSR DR from standard DSA backups. Make sure the following prerequisites are met:
Submit a CR to enable CSR DR feature flag for your VantageCloud Enterprise Sites.
  • To perform failover using standard DSA backups the VantageCloud Enterprise site must be on VantageCloud Enterprise 2.4.7 or VantageCloud Enterprise 3.1+ releases.
  • Prerequisites of partial backups are met on source site. See Standard Backups.
  • Prerequisites of same-site restore are met on target site. See Restoring a Standard Backup.

Restoring from a Backup (DR)

Perform the following steps on backup (DR).

  1. Sign in to https://cloud.vantage.teradata.com.
  2. Select Data protection .
  3. Select Retained copies.
  4. Select the retained copy, select "" and select Failover.
  5. In the Failover page, enter the name of the Failover job, details, and make sure that the target site is correct.
  6. In the Settings tab, select the following as required.
    Option Details
    Restore Metadata The metadata retained copy includes the database schema and configuration. See Using Metadata jobs for more details.
    Restore Dictionary The dictionary contains the DBC only retained copies. Selecting this.option will cleanup the target system along with data and restore it from the backup chosen.
    Continue on access rights violation The restore job proceeds even when the DUMP access rights violation occurs.
    Run as copy job Restores data into a database with a different internal database ID than the one in the backup set.
    Do not select this option when the database system is original, and the database ID matches with the saved backups.
    Rename objects during restore on the target site by adding a suffix. Select to add a suffix for renamed tables to differentiate from the original
    Restore to a different database on the target site Select to choose the database from the available list
    Skip statistics Select to skip collecting statistics during a backup or restore job.
  7. Open the Objects tab and select the required objects to restore using the respective selections. If prompted, provide credentials (of the Backup job).
  8. Select the Warning and select Start to start full system restore.
    Once you select Start, when prompted, enter the dbc password that you have used at the source site for creating the backup restore point.
  9. In the Jobs tab, you can view the status of the Restore operation as queued and also a header indicating that the Failover is in progress.
  10. Select the Details to view more details of the Failover operation being performed. The Details include:
    • Environment Activation with a series of operations to prepare the system for restoration. This operation may take sometime, around 60 minutes.
    • In Metadata restore, the DBC only backup is restored on the target system.
    • In Data Restore, the customer data is restored into target system.
    • In Post Data Restore phase, few steps are performed to make the system ready for use after the failover.
    • The cleanup phase usually contains all the clean up activities in case of a restore job failure.

    If in case any operation or step in the failover process fails, an automated customer visible ticket will be created and will be handled by Teradata support team.

  11. You can also view the Restore Operation is successful in the Overview tab.