

Introducing Arcserve Backup Agents and Options › Using Agents › Agent for Oracle (UNIX) › Restoring and Recovering Data › Restore and Recovery Limitations
Restore and Recovery Limitations
The following are restore and recovery limitations:
- The online redo logs are not backed up; consequently, they cannot be restored.
- If any users are logged into the database when a restore job is scheduled to begin, the job fails if you are restoring either a system tablespace or a tablespace containing rollback segments. To avoid this, set the ORACLE_SHUTDOWN_TYPE variable to immediate in the /opt/Arcserve/ABcmagt /agent.cfg file.
- The Catalog database SID should not be duplicated or shared with any other SID name.
- Arcserve Backup does not support restoring multiple, encrypted, Oracle RMAN sessions in a single restore job. You must restore encrypted Oracle RMAN backup sessions as individual restore jobs.
- Arcserve Backup does not support restore of old Oracle agent sessions using RMAN agent.
- If the restore job is submitted from Oracle RMAN command line, the job can’t be rescheduled. That is, when you right-click the job "Ready/Hold/Run Now/Modify/Reschedule" will be grey in the job queue option.
Copyright © 2016 .
All rights reserved.
 
|
|