Introduction to the SPD Server Backup and Restore Utilities

Overview

SPD Server provides the spdsbkup and spdsrstr utilities for backing up and restoring your server tables:
  • spdsbkup
    performs a full or incremental backup of a server table or domain, storing the information in a backup data file.
  • spdsrstr
    performs a full or incremental restore of a server table or domain using the backup data file that was created by the spdsbkup utility.

Path Requirements for SPD Server Utilities

SPD Server provides National Language Support (NLS) for multiple languages and character sets in database operations. As a result, all SPD Server utilities require access to the InstallDir/bin directory. You must ensure that the InstallDir/bin directory is included in your SPD Server library path specification.
Here is an example of a statement that specifies the necessary path:
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:InstallDir/bin
export LD_LIBRARY_PATH

Compatibility with Previous Versions

SPD Server 5.3 backup and restore utilities cannot restore SPD Server backup files created with SPD Server 3.x and earlier. You must use your SPD Server 3.x utilities to restore SPD Server 3.x backup files, and then archive the restored files using the SPD Server 5.3 utilities.

Privileged Access Protection

Running the SPD Server backup and restore utilities is a privileged operation. For a user to have access to the SPD Server backup and restore utilities, one of the following statements must be true:
  • The user ID that starts the SPD Server session must be identical to the user ID that runs the backup and restore utilities. By definition, the user ID that starts the SPD Server session is a privileged user.
  • The user has ACLSPECIAL=YES privileges.
Access to the backup and restore utilities is granted to the special user SPDSBKUP. You can use the user (-u) and password (-p) options for the utilities to give a specific privileged user access to the utilities.

Invoking the Backup and Restore Utilities

spdsbkup and spdsrstr can be invoked as stand-alone utilities, or they can be invoked in PROC SPDO by using the SPDSCMD statement. For more information about the PROC SPDO SPDSCMD statement, see SPDSCMD Statement.
The following environment variables must be established in order for the spdsbkup utility to be invoked as a stand-alone utility. Note that these are not needed if the utility is invoked in PROC SPDO.
For UNIX:
INSTDIR=<!replace with SPD Server 5.3 Installation Directory!>
 SASVER=9.4 
 SASHOME=<!replace with SPD Server 5.# Installation Directory!>
 LD_LIBRARY_PATH=$INSTDIR/bin:$SASHOME/SASFoundation/$SASVER/sasexe 
 export LD_LIBRARY_PATH
 LIBPATH=$INSTDIR/bin:$SASHOME/SASFoundation/$SASVER/sasexe
 export LIBPATH
 TKPATH=$INSTDIR/bin:$SASHOME/SASFoundation/$SASVER/sasexe:$SASHOME/SASFoundation
 /$SASVER/utilities/bin
 export TKPATH
 MSGPATH=$INSTDIR/misc/spds
 export MSGPATH 
For Windows:
SET SASROOT=<!replace with SPD Server 5.3 Installation Directory!>
SET INSTALLDIR=<!replace with SPD Server 5.3 Installation Directory!>
SET MSGPATH=@INSTALLDIR@\spds\sasmisc
SET TKPATH=@INSTALLDIR@\bin;@SASROOT@\core\sasext 
Last updated: February 3, 2017