Archives of the TeradataForum
Message Posted: Tue, 02 Jul 2002 @ 11:32:11 GMT
I agree with the other comments that you've received on this one.
-- much faster backup and restore
-- operationally more complex: to restore from a cluster backup because you have to remember to restore the dictionary information first and then restore the data. I think that if you know that Teradata's internal 'version' for the table hasn't changed then you can probably just restore the data. Conversely an all-amp backup will hold the dictionary information on the backup file for you.
-- potentially more concurrent tape units required as (presumably) you'd only take this approach because you want the speed,
-- (I think) to restore even a single row table you have to restore all clusters
I tend to use the following general approach:
(1) start with all-amp backups for everything. Break the backup processing into manageable chunks so that individual jobs don't take too long, single backup files aren't too large
(2) only use cluster dumps when a single table all-amp backup takes too long (whatever your definition of too long is)
Ward Analytics Ltd: Information in motion (www.ward-analytics.com)
|Copyright 2016 - All Rights Reserved|
|Last Modified: 28 Jun 2020|