SAS Safety Scalable Performance Data Server 4.5 Manual Do Utilizador

The client that performs the backup does not have to execute on the same machine as the
SPD Server. However, the client must be able to access the physical path of the SPD Server
domain that is being backed up. Access by the client to the physical path of the domain can
be direct or through a network connection.

Before a table is eligible for backup, you must create the SPD Server LIBNAME domain
using the 

 option in the parameter file. Here are two example LIBNAME

entries from a data's server's libname parameter file, libnames.parm, to explain how
domains are processed with and without the 

 option:

libname=nobackup pathname=/usr/foo/test;

libname=canbackup pathname=/usr/foo/test BACKUP=YES;

The entry for the LIBNAME domain called 

 creates tables in the directory 

, but no 

 option is specified. For this reason, tables created

through this domain definition are ineligible for backup. In contrast, the entry for the
LIBNAME domain 

, which also creates tables in the directory 

, has the 

 option. As a consequence, tables created through this domain

are eligible for backup.

When spdsbkup performs a backup, it checks every table in 

. However,

based on our example parameter file entries, spdsbkup backs up only the eligible tables
in 

. On the client connections created using pass-through or LIBNAME, the

 LIBNAME option can be used to override. Tables that are created when either

of these is in effect will be able to be backed up.

Before you can do an incremental backup of an SPD Server table, you must do a full backup
of the table. You have two alternatives for the full backup:

•

Use the system's full backup utility, and then inform spdsbkup of the system's last full
backup date.

•

Use spdsbkup to perform a full backup, if none has been done before.

After a full backup has been performed for an SPD Server table, you can then proceed with
an incremental backup strategy. The first incremental backup saves all table changes that
were performed after the last full backup date. Each successive incremental backup saves
the changes that were made after the previous incremental backup.