Migrating on-premises backups to cloud
Follow these steps to migrate a backup image take on NPSaaS on Cloud Pak for Data System (on premises) to IBM® Netezza® Performance Server for IBM Cloud Pak® for Data as a Service.
-
Migrate your backup image to IBM Cloud Object Store.
Follow the steps that are described in:
-
Synchronize the on-premises backup image to the cloud instance by using the
nztool with thebnroption.$./nz bnr ls scan-object-store -host <NPS HOSTNAME> -u ADMIN -pw PASSWORD -unique-id BACKUP-UNIQUE-IDWhere the
-unique-idflag's value is the cloud directory structure following the bucket to where the backup image (starting NPS directory) is stored. Since NPSaaS controls backup/restore from the NPSaaS web console, NPSaaS creates a directory in the bucket that is named the same as the namespace name and puts the corresponding backup images in that directory. So, the default NPSaaSUNIQUE-IDis the namespace name, but if you are transferring backups from a filesystem to the bucket in the cloud, theBACKUP-UNIQUE-IDvalue is the path to the directory you store the backups in. -
Restore the backup by using the web console.
Follow the steps that are described in Restoring backups.
Optionally, you can restore by using
nz nzrestorecommand.- By using
azconnector:
./nz nzrestore -v -db <targetdbname> -sourcedb <sourcedbname> -backupset <> -npshost <> -connector az -connectorArgs "UNIQUE_ID=<>:STORAGE_ACCOUNT=<>:KEY=<>:CONTAINER=<>:REGION=<>:BLOCK_SIZE_MB=25" -u admin -pw <XXXX> -npshost <NPS HOSTNAME>- For S3:
nzrestore -v -db <> -npshost <> -streams AUTO -connector s3 -connectorArgs BUCKET_URL=<>:UNIQUE_ID=<>:ACCESS_KEY_ID=<>:SECRET_ACCESS_KEY=<>:DEFAULT_REGION=<> -u admin -pw <XXXX> -npshost <NPS HOSTNAME>Where the
<NPS HOSTNAME>is hostname that is specified in/nz/data/config/backupHostname.txtwhere backup was taken. - By using