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 believe
2. 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,
------------------------------
Huw Ringer
------------------------------
Original Message:
Sent: Fri June 26, 2020 03:45 PM
From: Chris Rodgers
Subject: Migration from Striper to CPDS NPS
Hey, anyone else going through migration from Striper to the new Cloud Pak for Data System (CPDS) Netezza Performance Server (NPS)? It seems like a mouthful, so we have just been calling it old Netezza to new Netezza. Any tips or tricks for a smoother transition? I know you could simply migrate it all and just point everyone to the new server, but we decided to coordinate with application and product owners and schedule different databases based on availability for folks to test and validate as well as different available outages. If we would have done it all at once, it would have been a large outage to migrate and validate 30 TB of data.
------------------------------
Chris Rodgers
------------------------------
#NetezzaPerformanceServer