Metadata Jobs - Running Default Jobs in VantageConsole - 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-11-10
dita:mapPath
gqe1746821105801.ditamap
dita:ditavalPath
paz1652209068143.ditaval
dita:id
wec1649710665916
Product Category
Teradata Vantage

Same-Site Default Jobs

For the new site onboardings starting VantageCloud Enterprise 2.4.7 and 3.1, you can see two default jobs by default in the Jobs tab of the Data Protection section in Vantage Console.

  • {site_id}_baas-default-job-dbc-all
  • {site-id}_baas-default-job-dbc-only
  • {site-id}_baas-default-core-system-data

The following are some important points to consider.

Execution Required: Users must run these jobs to generate the latest savesets for dbc only and core system data.

One Job per Site: Each site will have only one default dbc-only and one default core-system-data job.

Retention Settings: Retention from the main backup job does not apply to these metadata jobs. Users must explicitly set retention for them once visible in the console.

Default Jobs with Backup (DR)

Once you create a Backup (DR) job, the metadata jobs are created automatically, if they don't exist already. There are two types of metadata jobs created with dbc-only jobs and core-system-data jobs suffixes. The following are some additional details when you create a Backup (DR) on a DBC only system:
  • The metadata jobs are created with details such as, schemas, database configurations, and so on but doesn't include customer data.
  • The retention policy that you have provided during Backup (DR) creation is only for Data Jobs and not for Metadata jobs. If required, you can change the retention policy of metadata jobs once these jobs are created.
  • You'll only get the Objects tab for main data backup and core-system-data jobs but not for DBC-Only jobs.
  • You must schedule the DBC only and core-system backup DR jobs once they are created, so that you can get the restore points available on the target site, and use them to perform the restoration when required.

The following are the steps to use metadata jobs.

  1. Create a Backup(DR) job on the source site as explained in Creating a Standard Backup or Snapshot.
    The metadata jobs with names similar to the following are created:

    • <source_site_id>-<target_site_id>-dbc-only

    • <source_site_id>-<target_site_id>-core-system-data
    The metadata jobs are created only once for a pair of source and target sites.
  2. Run the metadata jobs on the source site and ensure they are successful.
  3. In both the source and target sites, verify the backup restore points in the Retained Copies tab.

By default, the metadata jobs available in the Jobs tab are disabled to run on a scheduled time. You must schedule these jobs to get their retained copies. The following section explains about scheduling the metadata jobs.

Creating Schedule for Default Jobs

The following steps explains the scheduling of metadata jobs.

  1. In the Jobs section of the Data Protection tab, select the job.
  2. Select Ellipsis, and then Overview.
  3. In the Settings tab, modify the Availability from Disabled to Enabled and also set the Retention Policy.
    By default, you'll have only one retained copy in both source and target sites. The retention count that you specify in the settings of metadata jobs is for the target site. The source site will only have one most recent backup restore point.
  4. Select Add Schedule in the Overview tab.
  5. Set the time and select Save.
  6. After the job runs successfully, verify the backup restore points in the Retained Copies tab of both source and target sites. For instance, if you specified four in Retention Policy, you'll see four copies on the target site and only the most recent copy on the source site.