Backing up and restoring data by using the Tivoli Storage Manager interfaces
About this task
You can use the IBM® Spectrum Protect (formerly Tivoli® Storage Manager) commands and interfaces to create a client node schedule, which is a record that defines a particular client operation such as a backup or a restore. By using client schedules, you can automate the backups of data from your Netezza Performance Server host without any user operator intervention. You can also automate the restore of data from one Netezza Performance Server system to another if you load data to a backup Netezza Performance Server system regularly.
To use the client scheduler to automate tasks for the Netezza Performance Server host client, you must install the BA client package on the Netezza Performance Server host as described in Configuring the Netezza Performance Server host.
Tivoli Storage Manager offers two ways to manage client scheduling: the client acceptor daemon-managed services, and a Tivoli Storage Manager traditional scheduler. You can use either method to manage client schedules. For details about configuring and managing the Tivoli Storage Manager client scheduler, see the IBM Tivoli Storage Manager for UNIX and Linux® Backup-Archive Clients: Installation and User's Guide, which is available from the IBM Support Portal at http://www.ibm.com/support.
If you create more than one scheduled operation, the Tivoli Storage Manager scheduler does not support overlapping schedules for operations; that is, one operation must start and complete before a new operation is allowed to start. If you create operations with overlapping schedules, the second operation is likely skipped (does not start) because the first operation is still running. Make sure that you allow enough time for the first operation to complete before a new operation is scheduled to run.
To create a client schedule, complete the following steps.
Procedure
Results
Because the script runs as root on the Netezza Performance Server host, the Netezza Performance Server user must be set inside the script by using the NZ_USER variable or specified with the -u user argument. The user password must be cached by using the nzpassword utility, set inside the script by using NZ_PASSWORD, or specified by using the -pw password argument.
You can use the backup history to check the status of a backup operation. For more information, see Backup History report.