Alternatively, you could use the
-e
option of spdsrstr and restore all of the files with
one single command:
spdsrstr -d test -h hostname -s serv -e backup results
Note:
When you restore a single table, you do not need to restore the ACL files, because
they were not deleted.
Example 4: Restoring an SPD Server Domain
Use the following steps to restore an SPD Server domain named "test" that was lost due to
a system media failure that occurred on Friday, February 15, 2008.
1. If the domain was backed up fully using the system backup utility, use the system restore
utility to restore domain "test" to its state at the last full backup date of February 10,
2008. If the domain was backed up fully using the SPD Server utility, then skip this
step.
2. Use SAS to run a query on the backup table of contents table
bkup_toc
.
select bk_file from foo.bkup_toc
where domain = "test"
and dttime >= '10FEB2008:23:30:00'd;
The query results identify which SPD Server backup files are required to restore the
domain.
3. Restore the archived SPD Server backup files required to restore the domain.
4. Use the SPD Server restore utility to restore domain "test":
spdsrstr -aforce -d test -h host -s serv -e backup
The
-aforce
option will cause the domain ACLs to be updated for each restore file,
resulting in the latest backup of the ACLs being restored.
Using PROC SPDO to Back Up and Restore SPD
Server Tables
You can use the SAS
to run the SPD Server backup and restore
utilities. There is one constraint: you must submit the command using an SPD Server
LIBNAME that has 'special' privileges. Backup and restore utilities require privileged
access. To grant 'special', privileges, you must specify the LIBNAME option
ACLSPECIAL=YES
.
When you execute commands using the PROC SPDO
spdscmd
, the current working
directory is the root directory of SPD Server. Output messages from the commands are
echoed to the SAS log. In the next example, the SPD Server incremental backup and restore
utilities reside in the SPD Server directory. The incremental backup and restore files are
saved in the server directory
/spdsadm/bkup
.
Currently, there is a limitation when using the
-aforce
option with PROC SPDO to
restore on Windows. The
-aforce
option fails if ACLs exist and there are active
connections to the domain that were specified using the
-d
option during the restore.
ACLSPECIAL= connections to a libref must specify a domain that is separate from the
domain where you are attempting to restore the ACLs (if the ACLs currently exist). Making
ACLSPECIAL= libref connections that specify the domain where you are attempting to
restore the ACLs will cause the ACL restore operation to fail.
246
Chapter 19 • SPD Server Backup and Restore Utilities
Summary of Contents for Scalable Performance Data Server 4.5
Page 1: ...SAS Scalable Performance Data Server 4 5 Administrator s Guide...
Page 7: ...Part 1 Product Notes Chapter 1 SPD Server 4 5 Product Notes 3 1...
Page 8: ...2...
Page 12: ...6...
Page 63: ...Part 3 Migration Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility 59 57...
Page 64: ...58...
Page 70: ...64 Chapter 5 SPD Server 3 x to SPD Server 4 5 Conversion Utility...
Page 72: ...66...
Page 76: ...70 Chapter 6 Using the SPD Server Name Server to Manage Resources...
Page 94: ...88 Chapter 7 Administering and Configuring SPD Server Using the SAS Management Console...
Page 98: ...92 Chapter 8 SPD Server SQL Query Rewrite Facility...
Page 116: ...110 Chapter 10 Configuring Disk Storage for SPD Server...
Page 128: ...122 Chapter 11 Setting Up SPD Server Parameter Files...
Page 154: ...148...
Page 198: ...192 Chapter 14 ACL Security Overview...
Page 212: ...206 Chapter 15 Managing SPD Server Passwords Users and Table ACLs...
Page 214: ...208...
Page 224: ...218 Chapter 16 SPD Server Operator Interface Procedure PROC SPDO...
Page 236: ...230 Chapter 18 SPD Server Table List Utility Spdsls...
Page 256: ...250 Chapter 19 SPD Server Backup and Restore Utilities...
Page 264: ...258 Chapter 20 SPD Server Directory Cleanup Utility...
Page 270: ......