Spdsbkup - The SPD Server Table Backup Utility

Description

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

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 returned by the query
compresses the record data
stores the data in a flat data file so that the restore utility can use it later when restoring the tables

Important Details about 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 a full backup is restored, the table is created with those attributes, 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 will not be backed up, and a warning message will be sent to the log. The spdsbkup utility will continue to back up all specified tables.

Important Details about 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 an SPD Server incremental backup is restored, 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 spdsbkup return value is 0, the utility was successful. If the spdsbkup return value is 1, one or more data sets could not be backed up. In that case, examine your SAS log for warning messages. If the spdsbkup return value is 2, a critical error caused an early process termination. Examine your SAS log for warning and error messages.