IBM Data Management Community Connect with Db2, Informix, Netezza, open source, and other data experts to gain value from your data, share insights, and solve problems. Join / Log in
Chris,Good luck with the migration. Couple of suggestions:1. I believe the catalog structure has changed slightly with new Netezza, so nzhostbackup and nzbackup -globals from the old system can't be restored (yet) on the new I don't think. Mark Fraase's /nz/support/bin/nz_ddl_all_grants (which will generate all the SQL to recreate the equivalent DCL commands from the old system that can then be executed on the new) should however work just fine I believe2. You could perform incremental database backup/restores from the old system to the new to keep the two in sync, thus reducing the migration effort for each separate database/application. The trick is to keep the new target database(s) locked, which means you can keep on applying incremental restores indefinitely until you're ready to switchover (incidentally, you can still query the data on the target for validation/comparison/UAT purposes - but won't be able to run any ETL type loads or updates until the database is unlocked).
3. to quickly check if old/new tables appear to be identical, use the /nz/support/bin/nz_cksum utility - the only problem with which is it doesn't tell you what the differences are between the tables if the checksums don't match (the best it can do is narrow it down to a particular column or data type if you use the -slow or -columns options)Hope that helps. We have tooling to automate pretty much the entire process, so if you're interested in a deeper discussion hit me up directly on LinkedIn.Best Regards,