IBM Cloud Docs
Migrating on-premises backups to cloud

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.

  1. Migrate your backup image to IBM Cloud Object Store.

    Follow the steps that are described in:

  2. Synchronize the on-premises backup image to the cloud instance by using the nz tool with the bnr option.

    $./nz bnr ls scan-object-store -host <NPS HOSTNAME> -u ADMIN -pw PASSWORD -unique-id BACKUP-UNIQUE-ID
    

    Where the -unique-id flag'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 NPSaaS UNIQUE-ID is the namespace name, but if you are transferring backups from a filesystem to the bucket in the cloud, the BACKUP-UNIQUE-ID value is the path to the directory you store the backups in.

  3. Restore the backup by using the web console.

    Follow the steps that are described in Restoring backups.

    Optionally, you can restore by using nz nzrestore command.

    • By using az connector:
    ./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.txt where backup was taken.