Backup and restore configuration arguments

Deployment options: Netezza Performance Server for Cloud Pak for Data System

Learn about the nzinstall modify command and the necessary backup and restore configuration arguments.

Syntax

nzinstall modify {arguments}

Arguments

--bnr-storage-src BNR_STORAGE_SRC
Specifies the storage source type for backup and restore. Storage is allocated based on the storage type or types that you choose.
Supported storage types:
local
Local storage that is available on the Red Hat OpenShift cluster nodes.
For more information, see Platform storage.
NFS
Storage that was made available by a customer-provided NFS server.
SAN
Storage that is made available on customer-provided storage assets, which are also connected over fibre channel to a connector node.
--local-config-data LOCAL_CONFIG_DATA
Specifies a space-separated list of details about Local storage. Used with --bnr-storage-src local.
Format: 
Size(in GiB):MountPath Size:MountPath
Example: 
500:/pod/local0 1000:/pod/local1
MountPath specifies the wanted mount path within the backup and restore pod.
--nfs-config-data NFS_CONFIG_DATA
Specifies a space-separated list of details about NFS servers and respective volume details for a single backup and restore setup. Used with --bnr-storage-src nfs.
Format: 
ServerIP:ExportPath:Size(in GiB):MountPath:MountOpts ServerIP:ExportPath:Size:MountPath:MountOpts
Example: 
9.x.x.x:/nfs/share1:500:/pod/share1:rw,nfsvers=4 9.x.x.x:/nfs/share2:1000:/pod/share2:
MountPath specifies the wanted mount path within the backup and restore pod.
--san-config-data SAN_CONFIG_DATA
Specifies a space-separated list of details about the SAN Fibre Channel storage for a single backup and restore setup. Used with --bnr-storage-src san.
Format: 
WWID:Size(in GiB):MountPath:FSType
Example: 
36005076881813458800000000200002c:4000:/dest/san01:xfs 36005076881813458800000000300002d:4000:/dest/san02:xfs
Where:
WWID
WWID is the same WWID for the LUNs that you configured. You can get this information from your storage admin or from your own storage box through its GUI or CLI.
MountPath
Specifies the wanted mount path within the backup and restore pod.
You can specify the mount path name so that it conforms to existing scripts and or for workflows that involve accessing the storage inside the backup and restore pods directly instead of only through established nz commands. For example, nzbackup and nzrestore. For more information, see Accessing the storage inside the backup and restore pods.

For more information about the nzinstall command, see The nzinstall command.

Note:
  1. MountPath must be unique across storage types.
  2. If you specify a different file system type than one that exists on that LUN file system, the existing volume might be wiped out and reformatted with a new file system.

  3. Restoring backup and restore configurations from 11.2.2.X to 11.2.2.3 is not supported. This feature is available only from 11.2.2.3. Starting from 11.2.2.3, you can add new storage sources by using nzinstall modify. The latest backup and restore configuration is preserved after you run nzinstall update.

    For example, if you upgrade from 11.2.2.3 to 11.2.2.X, the backup and restore configuration is preserved during the upgrade. You do not have to run nzinstall modify <BnR config details> after such an upgrade.

    If you upgrade from a version older than 11.2.2.3 to 11.2.2.3 and above, you must run nzinstall modify <BnR config details> after the upgrade.

    After you run nzinstall update against 11.2.2.2 or lower, your backup and restore config is lost. You must run nzinstall modify after you upgrade your instance and set up your backup and restore configuration from scratch.

  4. You are recommended to deploy your backup and restore setup with the nzinstall modify command as described in Deploying backup and restore setups.

What to do next