Archives of the TeradataForum
Message Posted: Tue, 19 Jan 2010 @ 23:39:28 GMT
<-- Anonymously Posted: Tuesday, January 19, 2010 18:34 -->
There's no problem in doing this using your OTB, Open Teradata Backup tool, NetVault or NetBackup, detailed instructions are found in the Teradata Data Migration publications for each specific version.
After you RESTORE or COPY the old data with your backup tool you need to run a conversion script, which will adjust several internal structures and data to fit the current Teradata version, one or two additional steps may be needed in some cases, according to the manual. It is a simple task.
After the restore/copy execution in your backup tool, there will be a warning generated by arcmain in its log (invoked by OTB APIs) to remember the need to run the conversion script.
As Frank pointed out, same data backed up in 32-bit may use more space under 64-bit, so the manual instructs to increment database size in case there's no room for the old data under the new version. As a rule of thumb, if you are restoring/copying a complete database make sure it has about 10% free space in the target 64-bit platform before starting.
These data migration publications are available in www.info.teradata.com choose Data Warehousing under Browse by Category, then SUPR (Installation, Upgrade & Migration Single Unified Procedures), and you'll get a list of all which is available.
For instance if you took a backup under Teradata V2R6.2 in any OS, like MP RAS for instance, and you need to restore/copy it under Teradata 12.0.2 say in Linux, you need the manual called "Teradata Database Migrating Data to Release 12.0" Publication ID B035-1114-010K.
As it has been explained in the Forum, the OS makes no difference, except for the additional space need in the 32/64-bit data migration.
Hope this helps.
|Copyright 2016 - All Rights Reserved|
|Last Modified: 23 Jun 2019|