Migrating Teradata Plugin (4044126)

Migrating the Teradata Plugin essentially involves migrating the entire NetVault:Backup Server from the Source machine (e.g., MP-RAS) to the Target machine (e.g., Linux or Windows).

Pre-requisites:

The following requirements must be met/performed before you attempt the migration procedure:
•Connectivity to Existing Clients - The Target machine must have TCP/IP connectivity to all the existing NetVault Clients.
•Connectivity to Existing Libraries and Devices - The devices currently in use by the Source Server must be accessible to the Target machine.
•Same Version of NetVault Server Software - Both the Source and the Target Servers must be running the same version of NetVault Server software.
•Same Version of the Teradata Plugin in Use -Both the Source and the Target Servers must be running the same version of Teradata Plugin.
•Backing up the NetVault Database (NVDB) - It is strongly recommended that a backup of the NVDB be taken before you start Server migration. The NVDB contains metadata pertaining to the current NetVault environment, including data pertaining to Clients, libraries, scheduled jobs, media items, and backups. This data must be restored to the Target server in order to have the exact same setup that existed before migration.

The NVDB can be backed up using the NetVault Database Plugin that is available on the NetVault Server. This plugin gets automatically installed during the NetVault Server installation. For more information on using the NetVault Database Plugin, see NetVault®: Backup - Administrator’s Guide.
Make a note of the barcodes that identify the tapes to which the NVDB backup is written to. This can be used at a later stage to identify the tapes when restoring the NVDB data to the new NetVault Server.
Procedure for Migrating the NetVault Server
This migration procedure can be divided into the following steps:
•Step 1: Removing the Devices from Existing Server

Please refer to the text above