Restore Destinations - How To
Topics |
How To |
Related Topics
Restore Out-of-Place, Cross-Platform or
Cross-Application
Recover Out-of-Place or
Cross-Platform
Restore to a
Network Drive/NFS-Mounted File System
Restore Out-of-Place or Cross-Platform (DB2)
Restore Out-of-Place or
Cross-Application (Exchange iDataAgents)
Recover Out-of-Place or
Cross-Application (Exchange Mailbox/Public Folder Archiver Agents)
Retrieve Out-of-Place
or Cross-Application (Exchange Compliance Archiver Agent)
Restore Out-of-Place or Cross-Platform (Informix)
Restore and Recover a Database to a New Host with the Same Directory Structure
(Oracle and Oracle RAC)
Restore and Recover a Database to a New Host with a Different Directory Structure
(Oracle and Oracle RAC)
Restore Out-of-Place or Cross-Platform (SAP for Oracle)
Restore Out-of-Place or Cross-Platform (SAP for MAXDB)
Restore Out-of-Place or Cross-Platform
(Sybase)
Restore a Volume Out-of-Place or
Cross-Platform (Image Level, Image Level ProxyHost)
Restore Out-of-Place, Cross-Platform or Cross-Application
Before You Begin
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any
restore operation.
Required Capability: See
Capabilities and Permitted Actions
To
browse and restore data:
- Begin any restore procedure. See
Basic Restore or
Browse and Restore for step-by-step instructions.
- From the agent's Restore Options dialog box, select the restore
destination:
- Destination Computer - By default, data is restored to the same
computer from which it was backed up. To change the destination computer,
select one from the list. The list includes established clients within the CommCell, with Operating Systems that support the
out-of-place, cross-platform, or cross-application restore operation from this client.
- Restore to Same Paths - Specifies whether the restore operation must restore data to the Destination Computer
using the same path from which it was backed up. Clear this option if you want to restore
to a different path and activate the Destination
folder box.
- Destination Folder - Use this space to enter (or browse to) the path on the destination computer to which the data
must be restored. If the specified path does not exist, it will be created during the restore process.
On Windows computers,
the UNC path of a shared
drive can be specified. (e.g., \\servername\sharename\directory).
Deselect Restore to Same Paths and then type the UNC path of the shared drive in the
Destination Folder field.
- After completing your selections, continue with the restore procedure.
Recover Out-of-Place or Cross-Platform
Before You Begin
- Review the general and agent-specific recovery requirements accessed from
Recover Archived Data prior to performing any
recovery operation.
Required Capability: See
Capabilities and Permitted Actions
To
browse and recover data:
- Begin a browse and recovery procedure from the CommCell Console. See
Recover a File from the CommCell Console for step-by-step instructions.
- From the agent's Recover Options dialog box, select the recovery destination:
- Destination Computer - By default, data is recovered to the same
computer from which it was archived. To change the destination computer,
select one from the list. The list includes established clients within the CommCell, with Operating Systems that support the
out-of-place or cross-platform recovery operation from this client.
- Recover to Same Paths - Specifies whether the recovery operation must recover data to the Destination Computer
using the same path from which it was archived. Clear this option if you want to recover
to a different path and activate the Destination
folder box.
- Destination Folder - Use this space to enter (or browse to) the path on the destination computer to which the data
must be recovered. If the specified path does not exist, it will be created during the recovery process.
On Windows computers,
the UNC path of a shared
drive can be specified. (e.g., \\servername\sharename\directory).
Deselect Recover to Same Paths and then type the UNC path of the shared drive in the
Destination Folder field.
- After completing your selections, continue with the recovery procedure.
Restore to a Network Drive/NFS-Mounted File System
Before You Begin:
- On Windows computers, shared network drives exist as Windows share
directories (i.e., shares) on some other computer on the network. For data
security reasons, these shares possess access privileges that determine who
can access the share and the rights under which access is permitted. If your
Windows account does not have privileges to write data to the share, you must
be prepared to provide the login and password of a Windows account that does
have these privileges.
- For Unix computers, ensure that the destination computer has root permissions for the NFS-mounted
file system. If the destination computer does not have these
permissions, restores will fail.
- Ensure that the network drive / mounted file system to which you intend to restore the data is accessible as
a mapped network drive/ NFS-mounted file system from the destination computer.
- Review the general and agent-specific restore requirements accessed from Restore Backup Data prior to performing any restore operation.
Required Capability: See Capabilities and Permitted Actions
To browse and restore data using wildcards:
- Begin any restore procedure. See
Basic Restore or
Browse and Restore for step-by-step instructions.
- From the Restore Options dialog box, ensure that the Destination Computer is the source computer
from which the shared drive was backed up, not the computer that has the share. If the data did
not originate from the shared drive, de-select Restore to Same Paths
and then type the UNC path of the shared drive in
the Destination Folder field (e.g.,
\\servername\sharename\directory).
- To restore to a Windows computer, click Advanced.
If you do not have Change permissions for the share to which you intend to restore the
data, then you must select Impersonate NT User in the Advanced Restore
Options dialog box and provide the login and password of a Windows
account that does have these permissions. (Otherwise, the data cannot be
restored to the selected share. Ordinarily, if you can copy or create a
file in the share, you should be able to restore data to that share without
having to select this option.)
|
If the user account is established as a domain user
account, you must enter a fully qualified user name (e.g.,
<domain_name>\<user_name>) and password. |
- Optionally select the additional restore options that you want to use from the
Advanced
Restore Options dialog box.
- Click OK.
- Optionally select the additional restore options that you want to use from the
Restore
Options dialog box.
- Click OK.
- After completing your selections, you can either start an immediate
restore or schedule the restore.
- If you want to schedule the job, click the
Job Initiation
tab from the Restore Options dialog box, click Schedule, and enter your selections in the Schedule Details
(Schedule Details) dialog box. Clicking OK from this dialog box
saves your schedule. See
Scheduled Data Recovery
Operations for an overview of this feature.
- If you want to run the job now, accept or click Run Immediately
in the same tab and then click OK.
While the job is running, you can right-click the job in the Job Controller
and select Detail to view information on the job.
NOTES
- The restored data assumes the access characteristics of the destination
share.
- In the case of a File Level restore using the Image-Level iDataAgent,
the restored data assumes the access characteristics of the destination share.
Restore Out-of-Place or Cross-Platform
(DB2)
Before You Begin:
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any
restore operation.
Required Capability: See
Capabilities and Permitted Actions
To
restore out-of-place or cross-platform:
- Install the DB2 application software on the destination host.
- Install the DB2 iDataAgent
on the destination host.
- Configure the instance on the destination host. You can use the same name
as that for the instance on the source host, or you can assign a unique name.
- Go to the source machine and access the
Source & Destination tab of
the Restore Options dialog box.
- Select the name of the destination computer from the appropriate list.
- Select the name of the destination instance from the appropriate list.
- Either accept the name of the database in the
Target Database Name field or replace
this name with another appropriate database name. (You need not supply a
target database path.)
- If desired, use the other tabs to select any other restore options.
- Click OK.
Before You Begin
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any
restore operation.
Required Capability: See
Capabilities and Permitted Actions
To
browse and restore data:
- Begin any restore procedure. See Basic Restore or Browse and Restore for step-by-step instructions.
- From the agent's Restore Options (General) dialog box, select the restore
destination:
- If applicable, select To Mailbox.
- Restore to Original Client - By default, data is restored to the same
computer from which it was backed up.
- Restore to a Different Client - To change the destination computer,
select one from the list. The list includes established clients within the CommCell, with
Exchange Server versions that support the
out-of-place or cross-application restore operation from this client.
- If applicable, choose one of the following:
- To restore data to the same path, folder or mailbox, select Restore
to Same Path.
- To restore data to a different path, folder or mailbox, select Restore to Different Path then click Browse
to specify the location.
- To restore Exchange 2007 Database data out-of-place to a different
Storage Group, from the display pane in the
Restore Options (General) dialog select a store under the Source DB
column then
double-click the corresponding space in the Destination DB column to access the "..."
button. Next, click the "..." button,
select the appropriate destination from the
Choose Storage Group dialog then click OK.
- To restore Exchange 2007 Database data out-of-place to a non-Exchange location (i.e., any disk location on the Exchange Server), from the display pane in the Restore Options (General) dialog select a store under the Source DB column then double-click the corresponding space in the Destination DB column to access the "..." button. Next, click the "..." button, select either Restore to Non-Exchange Location <Out Of Place> (logs will be replayed), or Restore to Non-Exchange Location <Out Of Place, No Recover> (logs will not be replayed) from the Choose Storage Group dialog then click OK. Afterwards, double-click the corresponding row under the Out of Place Location column then type in or browse to the fully qualified destination path on the Exchange Server (for example, C:\staging_area).
- After completing your selections, continue with the restore procedure.
Before You Begin
- Review the general and agent-specific recovery requirements accessed from
Recover Archived Data prior to performing any
recovery operation.
Required Capability: See
Capabilities and Permitted Actions
To
browse and recover archived data:
- Begin a browse and recovery procedure from the CommCell Console. See
Recover a Message from the CommCell Console for step-by-step instructions.
- From the agent's Recovery Options (General) dialog box, select the recovery destination:
- If applicable, select To Mailbox.
- Recover to Original Client - By default, data is recovered to the same
computer from which it was archived.
- Recover to Different Client - To change the destination computer,
select one from the list. The list includes established clients within the CommCell,
with Exchange Server versions that support the
out-of-place or cross-application recovery operation from this client.
- If applicable, choose one of the following:
- To recover data to the same folder or mailbox, select Recover to Same Path.
- To recover data to a different folder or mailbox, select Recover to Different Path then click Browse
specify the location.
- After completing your selections, continue with the recovery procedure.
Before You Begin
Required Capability: See
Capabilities and Permitted Actions
To
browse and retrieve archived data:
- Begin a browse and retrieve procedure. See
Retrieve Mail Messages for step-by-step instructions.
- From the agent's Retrieve Options (General) dialog box, select
To Mailbox then select the retrieve destination:
- Retrieve to Original Client - By default, data is retrieved to the
same target mailbox on the same
computer from which it was archived.
- Retrieve to Different Client - To change the destination computer,
select one from the list. The list includes established clients within the CommCell,
with Exchange Server versions that support the
out-of-place or cross-application retrieve operation from this client.
- If you would like to retrieve to a different Target Mailbox,
select the corresponding checkbox and then select the desired target mailbox
from the list.
- Choose one of the following:
- To retrieve data to the default folder select Retrieve to Default
Destination Folder.
- To retrieve data to a different folder, select Retrieve to Different Folder then click Browse
to specify the location.
- After completing your selections, continue with the retrieve procedure.
Restore Out-of-Place or Cross-Platform
(Informix)
Before You Begin:
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any
restore operation.
Required Capability: See
Capabilities and Permitted Actions
To
restore out-of-place or cross-platform:
- Install the application software on the destination host.
- Create a simple instance on the destination host as discussed in
Create an Instance. To get the appropriate
parameters, go to the CommCell Console and access the property screen for the
instance on the source host; if this is not possible, use a link.
- On the destination host, start up the instance and then shut down the
instance.
- Install the Base client software (CVGxBase), either the HP-UX File System
or Solaris File System iDataAgent software (CVGxIDA), and the Informix
iDataAgent software (CVGxIfIDA) on the destination host.
- Using the CommCell Console, create a new instance for the Informix iDataAgent
on the destination host.
- Log in to the destination host and navigate to the $INFORMIXDIR/etc
directory. Then perform the following file copies (using cp):
ixbar.$servernum to ixbar.$servernum.org
onconfig.$servername to onconfig.$servername.org
oncfg_$servername.$servernum to oncfg_$servername.$servernum .org
- Use the appropriate directives in
Basic Restore or
Browse and Restore to cross-restore the ixbar, onconfig, and oncfg
files on the CommCell Console from the source host's backups.
- Modify the onconfig.$servername.org file to be identical to the
onconfig.$servername file (i.e., ensure that DBSERVERNAME, SERVERNUM, and
ROOTPATH are the same).
- Copy the onconfig.$servername.org file to
the onconfig.$servername file.
- Log in to the destination host and prepare dbspaces that refer to the
oncfg files. All dbspaces physical paths have to be the same (e.g, prepare the
cooked file space, cat /dev/null > $INFORMIXDIR/dbs/test1/data/testdbs1.c1,
chmod 666 $INFORMIXDIR/dbs/test1/data/testdbs1.c1,
chown -R informix:informix $INFORMIXDIR/dbs/test1/data/testdbs1.c1)
- Try to cross-restore the whole system by using the directives in
Basic Restore or
Browse and Restore.
It is recommended that you avoid performing a salvage backup (e.g., zeroing
out the root dbspace before restoring or performing a physical whole system
restore plus a logical whole system restore).
Restore and Recover a Database to a New Host with the Same Directory Structure
(Oracle and Oracle RAC)
The following procedure describes the steps involved in
restoring and recovering a database (either in ARCHIVELOG or NOARCHIVELOG) mode to a new host, with the
same directory structure.
|
When you are restoring data from a
database in NOARCHIVELOG mode, you must always restore and recover the
entire database. |
Before You Begin:
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data
prior to performing any restore.
- When you perform a database restore to a new host the source and destination
machines must have the following features:
- The same operating systems
- The same Oracle version
- The same database datafile directory structures
- The same ORACLE_SID
- Must be either a 32-bit or 64-bit system
-
In the destination machine
- Install the Oracle iDataAgent
or create the Oracle RAC client and configure as client in the same CommServe
in which the source machine resides
- Create and configure a new Oracle instance, similar to the one existing in
the source machine
- In addition the destination machine must have sufficient disk space to
accommodate the restored database.
Required Capability: See
Capabilities and Permitted Actions
To restore and recover a database to a new host with the same directory
structure:
- Verify that the destination machine's init <SID>.ora file is the same as the source
machine's file.
- Configure the destination machine's $TNS_ADMIN/tnsnames.ora
file to include the Recovery Catalog database's service entry. The easiest
way to configure this file is to copy the Recovery Catalog database's
service entry from the source machine's tnsnames.ora
file and append it to the destination machine's tnsnames.ora
file. The Recovery Catalog database's service entry should look similar to
the following:
<service_name> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = <protocol>)(HOST = <host>) (PORT =
<##>))
(CONNECT_DATA = (SID = <Recovery Catalog database>)))
-
Make sure that ORACLE_SID is set to the database that you are restoring and
that ORACLE_HOME is set appropriately. Note the following example for
Solaris:
#export ORACLE_SID= <target database SID>
#export ORACLE_HOME= <Oracle home directory>
Note the following example for Windows 2000 machines:
C:\set ORACLE_SID= <target database SID>
C:\set ORACLE_HOME= <Oracle home directory>
- From Server Manager or SQL Plus on the source machine, create a new user account
within the Recovery Catalog for the destination machine by executing the
commands in the following display:
SVRMGR>create user <username> identified
by <password>
2>temporary tablespace <temp_tablespace_name>
3>default tablespace <default_tablespace_name>
4>quota unlimited on <default_tablespace_name>;
Statement processed.
SVRMGR>grant connect, resource, recovery_catalog_owner to
<username>;
Statement processed.
|
Make sure that the <username>you
supply for the destination machine is different than the username for
the source machine.
When you are granting the user database permissions, make sure to
include the recovery_catalog_owner option shown above. |
- Transfer the Oracle password file "orapw<Oracle
SID name>" from the source machine to the destination
machine. Usually this file resides in ORACLE_HOME/dbs.
- From the source machine, use the Oracle exp
command to export the Recovery Catalog data. You are exporting the data by
user. For example, if the user ID for the Recovery Catalog owner is rman,
you would export the database backup information for the user rman.
- From the source machine, use the Oracle imp
command to import the contents of the file you created in the previous step
into the new user account for the destination machine. Depending on the
version of Oracle that you are running, you may receive the following error
when you run the imp command:
IMP-00044: unable to allocate enough memory for statement
- Perform these steps if you receive an error while running the imp
command:
- Drop the user.
- Recreate the user.
- Rerun the imp command.
- When you rerun the imp command, enter 1000000 when prompted for the
insert buffer file.
- If you receive the error message again, repeat the preceding
steps and increase the buffer by a million each time you run imp until
the error message is no longer displayed.
- Ensure that the database in NOMOUNT mode in the destination machine.
- If you want to perform the cross-machine restore from the CommCell Console
then continue on with this procedure. Otherwise, if you want to perform the
cross-machine restore from the RMAN command line using your own custom
script, then exit this help and run the script now (refer to Oracle's
Recovery Manager documentation for more information).
- From the CommCell Browser, right-click the instance that contains the
database you want to restore and recover to a new host, click All Tasks and then click Restore.
- From the Oracle Restore Options
(General)
dialog box, select or enter the following:
- Click the name of the client computer to which you want to restore in
the Destination Client box.
|
If your destination client is not
listed, check and ensure that all the requirements stated in the Before
you Begin section is satisfied. |
- Use the Catalog Connect fields to enter the connect string for
the catalog database of the destination machine.
- Select the Restore Control File option.
- Select the Restore Data and Recover options.
|
It is critical that the Recover option
is selected, as Recover applies any incremental backups that are
needed to bring the database back to a consistent state. |
- Select the entire database in The Latest
Database View pane (if it is
not already selected).
- Click the Advanced button and verify the following options are
selected in the identified tab for the Oracle Advanced Restore Options
dialog box:
- Restore Control File - To Point in Time
in Ctrl & SP Files
|
The Control file must be restored to a
point in time that is later than or equal to time set for the Restore
Data option in the
Restore
tab. |
- Restore Data
in Restore
|
The Restore Data option must be earlier
than or equal to the point in time that you specified for the Restore
Control File option in the
Ctrl & SP Files
tab. |
- Recover - Point In Time
in Recover
|
The point in time for the recover option
must be later than or equal to the point in time specified for the
Control file in the
Ctrl & SP Files
tab. |
- Click OK in the Oracle Advanced Restore Options dialog box.
- When restoring encrypted data, refer to Data Encryption.
- Optionally for Oracle RAC, from the
Oracle
Restore Options (Stream) dialog box, set the instance restore order per
stream allotment.
- Begin or schedule the restore.
|
Before the restore job is run, the system will check whether the database is in the correct mode for this type of restore. If it is not, a
message dialog will inform you of this and offer to automatically switch the database into the valid mode.
When this happens, either click Yes on the message dialog to have the system automatically switch the database to the valid mode
and continue the restore, or click No to manually switch the database to
the valid mode before proceeding. |
- View the progress of the restore in the Job Controller window.
- In ARCHIVELOG mode - When the data is restored, click OK on the confirmation
window. If
desired, click Detail to review information on the restore operation.
- In NOARCHIVELOG mode - The job will report the restore as failed. This is because no archive redo
log files exist. RMAN will report the following message, in reference to
this error:
RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: ch1
RMAN-00571:
======================================================
RMAN-00569:====== ERROR MESSAGE STACK FOLLOWS=========
RMAN-00571:
======================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-06054: media recovery requesting unknown log: thread 1 scn 72077
RMAN>
Recovery Manager Complete.
Perform the following steps if your database is in the NOARCHIVELOG mode.
- Manually recover and open the database using the following steps.
- From the Server Manager window, execute the command displayed in the
following example:
SVRMGR>recover database using backup control
file until cancel;
Server Manager displays several messages, including the
following:
Specify log: {<RET>=suggested | filename |
AUTO | CANCEL}
- Type cancel
The following message is displayed:
Media recovery cancelled.
- Execute the commands displayed in the following example:
SVRMGR>alter database open resetlogs;
SVRMGR>exit
- Reset the Recovery Catalog by executing the commands displayed in the
following example:
#rman rcvcat <catalog connect string>
Recovery Manager: Release 8.1.5.00 - Production
RMAN-06008: connected to recovery catalog database
RMAN>connect target;
RMAN-06005: connected to target database: <database_name> DBID=<##>)
RMAN> reset database;
RMAN-03022: compiling command: reset
RMAN-03023: executing command: reset
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN>exit
Resetting the Recovery Catalog creates a new incarnation of the
database. Before you can restore and recover the database to the current
time, you must perform another full backup and wait for it to complete
successfully.
- Perform an immediate offline full backup.
Restore and Recover a Database to a New Host with a Different Directory Structure (Oracle and Oracle RAC)
The following procedure describes the steps involved in restoring and recovering a database (either in ARCHIVELOG or NOARCHIVELOG) mode to a new host, with a different directory structure.
|
When you are restoring data from a database in NOARCHIVELOG mode, you must always restore and recover the entire database. |
Before You Begin:
Required Capability: See Capabilities and Permitted Actions
To restore and recover a database to a new host with a different directory structure:
- Copy the init<SID>.ora from the old host to the new host.
- Edit the init<SID>.ora file on the new host to reflect all the directory structure changes
(i.e., change the path for control files, archivelog destination and *dump destinations).
- Create the directory structures as defined in init<SID>.ora file for all paths.
- Configure the destination machine's $TNS_ADMIN/tnsnames.ora
file to include the Recovery Catalog database's service entry. The easiest
way to configure this file is to copy the Recovery Catalog database's
service entry from the source machine's tnsnames.ora
file and append it to the destination machine's tnsnames.ora
file. The Recovery Catalog database's service entry should look similar to
the following:
<service_name> =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = <protocol>)(HOST = <host>) (PORT =
<##>))
(CONNECT_DATA = (SID = <Recovery Catalog database>)))
- Make sure that ORACLE_SID is set to the database that you are restoring and
that ORACLE_HOME is set appropriately. Note the following example for
Solaris:
#export ORACLE_SID= <target database SID>
#export ORACLE_HOME= <Oracle home directory>
Note the following example for Windows 2000 machines:
C:\set ORACLE_SID= <target database SID>
C:\set ORACLE_HOME= <Oracle home directory>
- From Server Manager or SQL Plus on the source machine, create a new user account
within the Recovery Catalog for the destination machine by executing the
commands in the following display:
SVRMGR>create user <username> identified
by <password>
2>temporary tablespace <temp_tablespace_name>
3>default tablespace <default_tablespace_name>
4>quota unlimited on <default_tablespace_name>;
Statement processed.
SVRMGR>grant connect, resource, recovery_catalog_owner to
<username>;
Statement processed.
|
Make sure that the <username>you
supply for the destination machine is different than the username for
the source machine.
When you are granting the user database permissions, make sure to
include the recovery_catalog_owner option shown above. |
- Transfer the Oracle password file "orapw<Oracle
SID name>" from the source machine to the destination
machine. Usually this file resides in ORACLE_HOME/dbs.
- From the source machine, use the Oracle exp
command to export the Recovery Catalog data. You are exporting the data by
user. For example, if the user ID for the Recovery Catalog owner is
rman,
you would export the database backup information for the user
rman.
- From the source machine, use the Oracle imp
command to import the contents of the file you created in the previous step
into the new user account for the destination machine. Depending on the
version of Oracle that you are running, you may receive the following error
when you run the imp command:
IMP-00044: unable to allocate enough memory for statement
- Perform these steps if you receive an error while running the
imp
command:
- Drop the user.
- Recreate the user.
- Rerun the imp command.
- When you rerun the imp command, enter 1000000 when prompted for the
insert buffer file.
- If you receive the error message again, repeat the preceding
steps and increase the buffer by a million each time you run imp until
the error message is no longer displayed.
- Ensure that the database in NOMOUNT mode in the destination machine.
- If you want to perform the cross-machine restore from the CommCell Console
then continue on with this procedure. Otherwise, if you want to perform the
cross-machine restore from the RMAN command line using your own custom
script, then exit this help and run the script now (refer to Oracle's
Recovery Manager documentation for more information).
When performing cross-machine restore, do the following:
- Restore the control file and put the database in MOUNT mode.
- Login to SQL database in the destination computer and provide the
following syntax:
SQL> alter database rename
file '/oracle/oradata/rman10g1/redo01.log' to '/space/oracle/oracle10g2/oradata/redo01.log';
SQL> alter database rename file '/oracle/oradata/rman10g1/redo02.log'
to '/space/oracle/oracle10g2/oradata/redo02.log';
SQL> alter database rename file '/oracle/oradata/rman10g1/redo03.log'
to '/space/oracle/oracle10g2/oradata/redo03.log';
Here, '/oracle/oradata/rman10g1/ is
the source redo log location and
'/space/oracle/oracle10g2/oradata/ is the destination redo log
location.
- From the CommCell Browser, right-click the instance that contains the
database you want to restore and recover to a new host, click All Tasks and then click
Restore.
- From the Oracle Restore Options
(General)
dialog box, select or enter the following:
- Click the name of the client computer to which you want to restore in
the Destination Client box.
|
If your destination client is not
listed, check and ensure that all the requirements stated in the Before
you Begin section is satisfied. |
- Use the Catalog Connect fields to enter the connect string for
the catalog database of the destination machine.
- Select the Restore Control File option.
- Select the Restore Data and Recover options.
|
It is critical that the Recover option
is selected, as Recover applies any incremental backups that are
needed to bring the database back to a consistent state. |
- Select the entire database in The Latest
Database View pane (if it is
not already selected).
- Click the Advanced button and verify the following options are
selected in the identified tab for the Oracle Advanced Restore Options
dialog box:
- Restore Control File - To Point in Time
in Ctrl & SP Files
|
The Control file must be restored to a
point in time that is later than or equal to time set for the Restore
Data option in the
Restore
tab. |
- Restore Data
in Restore
|
The Restore Data option must be earlier
than or equal to the point in time that you specified for the Restore
Control File option in the
Ctrl & SP Files
tab. |
- Recover - Point In Time
in Recover
|
The point in time for the recover option
must be later than or equal to the point in time specified for the
Control file in the
Ctrl & SP Files
tab. |
- Redirect All Table Spaces to, along with the path, in
Redirect
|
The path for datafiles should be created manually because Oracle or Oracle
iDataAgent
will not create that path. |
- Click OK on the Oracle Advanced Restore Options dialog box.
- When restoring encrypted data, refer to
Data Encryption.
- Optionally for Oracle RAC, from the
Oracle
Restore Options (Stream) dialog box, set the instance restore order per
stream allotment.
- Begin or schedule the restore.
|
Before the restore job is run, the system will check whether the database is in the correct mode for this type of restore. If it is not, a
message dialog will inform you of this and offer to automatically switch the database into the valid mode.
When this happens, either click Yes on the message dialog to have the system automatically switch the database to the valid mode
and continue the restore, or click No to manually switch the database to
the valid mode before proceeding. |
- View the progress of the restore in the Job Controller window.
- In ARCHIVELOG mode - When the data is restored, click OK on the confirmation
window. If
desired, click Detail to review information on the restore operation.
- In NOARCHIVELOG mode - The job will report the restore as failed. This is because no archive redo
log files exist. RMAN will report the following message, in reference to
this error:
RMAN-03022: compiling command: recover(4)
RMAN-03026: error recovery releasing channel resources
RMAN-08031: released channel: ch1
RMAN-00571:
======================================================
RMAN-00569:====== ERROR MESSAGE STACK FOLLOWS=========
RMAN-00571:
======================================================
RMAN-03002: failure during compilation of command
RMAN-03013: command type: recover
RMAN-06054: media recovery requesting unknown log: thread 1 scn 72077
RMAN>
Recovery Manager Complete.
Perform the following steps if your database is in the NOARCHIVELOG mode.
- Manually recover and open the database using the following steps.
- From the Server Manager window, execute the command displayed in the
following example:
SVRMGR>recover database using backup control
file until cancel;
Server Manager displays several messages, including the
following:
Specify log: {<RET>=suggested | filename |
AUTO | CANCEL}
- Type cancel
The following message is displayed:
Media recovery cancelled.
- Execute the commands displayed in the following example:
SVRMGR>alter database open resetlogs;
SVRMGR>exit
- Reset the Recovery Catalog by executing the commands displayed in the
following example:
#rman rcvcat <catalog connect string>
Recovery Manager: Release 8.1.5.00 - Production
RMAN-06008: connected to recovery catalog database
RMAN>connect target;
RMAN-06005: connected to target database: <database_name> DBID=<##>)
RMAN>
reset database;
RMAN-03022: compiling command: reset
RMAN-03023: executing command: reset
RMAN-08006: database registered in recovery catalog
RMAN-03023: executing command: full resync
RMAN-08002: starting full resync of recovery catalog
RMAN-08004: full resync complete
RMAN>exit
Resetting the Recovery Catalog creates a new incarnation of the
database. Before you can restore and recover the database to the current
time, you must perform another full backup and wait for it to complete
successfully.
- Perform an immediate offline full backup.
Before You Begin:
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any
restore operation.
- Ensure that the following information is the same on both the source and
destination clients:
- ORACLE_SID name
- /oracle/GRP/sapbackup/cntrlGRP.dbf path
- SAPDATA_HOME environment variable
Required Capability: See
Capabilities and Permitted Actions
To
browse and restore data:
- Install the SAP for Oracle iDataAgent
on the source machine (e.g., Host A).
- Run several full, incremental, and log backups on the source machine.
- If the Oracle application is not already installed on the destination
machine (e.g., Host B), install the application on this machine. Do not
create an instance (database) on this machine.
- Set up Host B (destination machine) similar to how Host A (source
machine) is set up. Specifically, do the following:
- Create the same directory structure that is set up in Host A (e.g.,
include init.ora, tnsnames.ora)
- Add the following lines to the init.utl file:
srccrossclient
<source client display name in CommCell Console>
- Copy the ORAPWD file from Host A to
Host B
- Copy the sapbackup directory to Host
B
- Copy saparch/archCER.log to Host B
- On Host B (destination computer), ensure that the name of the instance is
the same as the name of the instance on Host A. Start the instance in the
NOMOUNT state (startup nomount).
- Install the SAP for Oracle iDataAgent
on Host B to the same CommServe as for Host A. Relink Oracle either during
the install or by using the <software installation
path>/iDataAgent/OraInstall.sh script.
- From the CommCell Console, create on Host B (destination machine) an
instance that has the same name as the instance on Host A (source machine).
- From Host B, restore the data backed from Host A as follows:
- To restore control files, enter the brrestore -m 0 command
- To restore data, enter the brrestore -d util_file -b last -m all
command
- To restore logs, enter the brrestore -d util_file -a -
command
- Recover the database manually.
Before You Begin:
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any
restore operation.
Required Capability: See
Capabilities and Permitted Actions
To
browse and restore data:
- Build a secondary (destination) client computer, and assign a different
name to this computer. Both the source client computer and the destination
client computer must have the same operating system.
- Install the SAP for MAXDB software on the destination client. On the
destination client, create the database and volume that are identical to
those on the source client. Ensure that the database is in ADMIN mode.
- Install the SAP for MAXDB iDataAgent
on the destination client and configure the database instance on the
CommServe.
- Define a backup medium on the destination computer using the
medium_put command.
- In the parameter file, include the
srccrossclient
parameter followed by the name of the source client. For example:
srccrossclient
magnum.company.com
- If the dbm.knl and
dbm.ebf catalog files do not exist on the
destination client and if the source client is still available, copy these
files if they are available. Otherwise, restore these files manually by
using the backint command. For example:
- Get the full set of backup job IDs. Specifically, create an input
file called file1.txt. Ensure that the contents of the file is
#NULL, and run an inquiry to get a list of backups. For example:
backint -u -f inquire -t file -p param -l file1.txt
- Using the last job ID to get the catalog files, create an input file
called file2.txt, and include the last job ID in the file (e.g.,
SAP_0_28). Then execute the following command:
backint -u -f
inquire -t file -p param -i file2.txt
- Restore the catalog files. Specifically, create an input file called
file3.txt. Include contents similar to the following in the file:
SAP_0_28 d:\maxdb\sdb\data\wrk\CLDB\dbm.ebf
SAP_0_28 d:\maxdb\sdb\data\wrk\CLDB\dbm.knl
Then execute the following command to restore the
dbm.knl and
dbm.ebf catalog files:
backup backint -u -f restore -t file -p param -i inp3.txt
- Perform the required data and log restores to the destination client by
using the following command:
backup_ext_ids_get BACKData2
backup_ext_ids_list
Activate the database and recover the full backup. Use a comma to
separate each ID specified.
db_activate RECOVER BACKData2 DATA ExternalBackupID "… , …"
Then restore from the incremental backups.
recover_start BackPages2 PAGES ExternalBackupID "… , …"
Then restore all the logs.
recover_start BackLog LOG ExternalBackupID "…"
recover_replace BackLog ExternalBackupID "…"
recover_replace BackLog ExternalBackupID "…"
…
recover_ignore
Restore Out-of-Place or Cross-Platform (Sybase)
Before You Begin
- Review the general and agent-specific restore requirements accessed from
Restore Backup Data prior to performing any
restore operation.
Required Capability: See
Capabilities and Permitted Actions
To
browse and restore data:
- Begin any restore procedure. See
Basic Restore or
Browse and Restore for step-by-step instructions.
- From the agent's Restore Options dialog box, click the
Destination Server.
- Continue with the restore procedure. Refer to
Restore Data - Sybase for more information.
Restore a Volume Out-of-Place or
Cross-Platform (Image Level, Image Level ProxyHost)
Before You Begin
- Review the general and agent-specific restore/ requirements accessed from
Restore Backup Data prior to performing any
restore operation.
Required Capability: See
Capabilities and Permitted Actions
To
browse and restore data:
- Begin any restore procedure. See
Basic Restore or
Browse and Restore for step-by-step instructions.
- From the agent's Restore Options dialog box, select the restore
destination:
- Destination Computer - By default, data is restored to the same
computer from which it was backed up. To change the destination computer,
select one from the list. The list includes established clients within the CommCell, with Operating Systems that support the
out-of-place or cross-platform restore operation from this client.
- Restore Paths & Destinations - When you select a source volume
whose data you want to restore to a different destination, the Destination
Volume drop-down box will become available. In the Destination Volume
drop-down box, select a destination volume, and click Apply. Your
selection will be displayed in the main panel next to the original volume,
as the Destination Volume.
- After completing your selections, continue with the restore procedure.