The SPD Server Table Backup Utility spdsbkup

Description

The backup utility spdsbkup performs a full or incremental backup of an SPD Server table or LIBNAME domain. It also creates a backup file that contains full backups of newly created SPD Server tables or incremental backups of tables that have been backed up before.
During the backup process, the spdsbkup utility performs the following tasks:
  • connects to a specified SPD Server
  • uses the SPD Server pass-through facility to generate SQL queries on SPD Server domain tables
  • backs up the records that the query returned
  • compresses the record data
  • stores the data in a flat data file so that the restore utility can use it later when it restores the tables

Performing a Full Backup

When you do a full backup of an SPD Server table, all of the table rows and attributes (indexes, partition size, compression, sorted) are backed up. When you restore a full backup, the table is created with those attributes, and then all the rows are added. Any changes that were made to the table attributes since the last full backup was performed are not restored.
ACL files must be in the same physical directory as the domain. If any ACL file does not meet this requirement, the ACLs are not backed up, and a warning message is sent to the log. The spdsbkup utility continues to back up all specified tables.

Performing an Incremental Backup

When you perform an incremental backup of an SPD Server table, only changes that were made to the table rows since the last full backup are included in the backup. Changes to the table attributes are not backed up. When you restore an SPD Server incremental backup, the incremental changes to the rows are applied. Only attributes that were associated the table at the time of the last full backup (indexes, partition size, compression, sorted) are applied to the restored rows.

Return Values

When spdsbkup exits, it generates a return value. If the return value is 0, the utility was successful. If the return value is 1, one or more data sets were not backed up. In that case, examine your SAS log for warning messages. If the return value is 2, a critical error caused the process to terminate early. Examine your SAS log for warning and error messages.