Revert to a full backup

Deployment options: IBM Netezza Appliance IBM Netezza Appliance

If you run an incremental backup, there are certain conditions that can trigger the nzbackup command to run a full backup for a particular table, such as:
  • Dropping and re-creating a table
  • Truncating a table
  • Using GROOM TABLE VERSIONS to resolve the versions of an altered table

If the nzbackup command performs a full backup of a table instead of an incremental backup, it writes a message to verbose output and to the backup log.

Restriction: After you use the nzhostrestore command, you cannot run an incremental backup on the database; you must run a full backup first.
Notes about backup-groom synchronization:
  • The system keeps groom/reclaim and incremental backups synchronized. GROOM TABLE uses information that is stored in the system catalog to identify incremental backups by using the most recent incremental backup for guidance. Groom limits its operation to transactions captured by that backup and its predecessors. Groom avoids the reclaiming of rows that are not yet captured in incremental backup.
  • You can override the default backup set synchronization by specifying a particular backup set on the GROOM TABLE command line.
  • When you perform any backup of a database, you trigger the synchronization. The system assumes that incremental backups follow a full backup.
To override the default groom behavior, use the backupset option.
  • To reclaim all rows, use backupset NONE.
  • You can also choose a specific backup set. For example, run the nzbackup -history command to view the backup set IDs in the report: 
    Database    Type           Start Date            Backup Set
---------------------------------------------------------------
dev         Full           2006-06-01 20:00:00   20060601200000
dev         Differential   2006-06-04 20:00:00   20060601200000
dev         Full           2006-06-08 20:00:00   20060608200000
dev         Differential   2006-06-11 20:00:00   20060608200000
    From this backup history report, you can choose to use the June 1 backup set rather than the June 8 backup set:
    GROOM TABLE dev RECLAIM BACKUPSET 20060601200000