Knowledge Base: BACKUP : Backup / Restore of Oracle-SBT
 
Backup / Restore of Oracle-SBT
Creation Date: March 02, 2010
Revision Date: April 10, 2013
Product: DS‑Client (Linux)
Summary
This article covers various backup/restore issues for the Oracle-SBT backup sets. “SBT” refers to the Oracle System Backup to Tape functionality. The Oracle-SBT backup set is a special configuration of DS-Client that allows a native Oracle-SBT process to be re-directed through DS-Client to DS-System (instead of to tape).
IMPORTANT:  This backup set type requires manual command input from the Oracle Server itself. All backup and restore commands must be initiated from the Oracle Server side (either through RMAN command-line or through Oracle Enterprise Manager. Only Oracle Database Administrators should attempt to use this backup set type.
See Also
“Oracle-SBT database backup sets (Linux or Mac)”
Additional documentation is available from the DS-Client installation DVD in the folder: \Tools\Oracle_SBT_Library
Troubleshooting
Error
The following error message may appear in the DS-Client Event Log when you restore from an Oracle-SBT backup set:
SBT restore canceled: Remote side stopped the restore of this file before all data was transmitted.
Reason
The RMAN restore successfully completed and the restored file is good.
This error may happen when you perform a tablespace restore. Because the restore is performed by RMAN, RMAN will read the backed up backup set and determine which tablespace needs to be restored. If the backup set contains the same named tablespace, you will not see this error. If the backup set contains any different tablespaces, you will see this error (i.e. if you are performing a selective restore of less than all the tablespaces in the backup set).
Example: You restore a tablespace from a whole database backup set, RMAN will read the backup set and restore only the tablespace you need. After the tablespace is restored, the SBT channel is released and RMAN stops. However, DS-Client still expects RMAN to continue sending the whole database in the backup set. This causes the above error in the DS-Client Event Log.