A cross-machine restore is one where the restore destination is a different host from where the backup was taken.
Perform a cross-machine restore when the original database host has been damaged or destroyed.
The restore can take place to the same or different location on the new host.
You can restore to a SID that is different from the SID in the backup without connecting to the source and target database or recovery catalog.
Cross-Instance Restore Operations
Use a traditional backup or an IntelliSnap backup to restore an Oracle database to a new destination that has a different SID from the source SID.
Restore when you cannot use the Oracle DUPLICATE command, such as in the following cases:
-
You cannot connect to the source database or recovery catalog.
-
You want to restore from an IntelliSnap backup.
-
You want to restore from a file system backup copy.
-
You want to create a permanent database clone from an IntelliSnap backup or a file system based backup copy.
Note
Running a cross-instance restore to a different instance on the same machine is not permitted. This prevents the accidental overwriting and resulting loss of the source database. If you want to run a restore operation to another instance on the same machine, you can use Commvault Oracle database duplication. For more information, see Database Duplication for Oracle.
NID Script Invocation During Cross-Instance Restore Operations
|
Scenarios |
Change DBID |
NID Command Invoked |
|
Cross-instance restore operation between two databases with different names |
Yes |
DBID is changed (NID command is invoked) |
|
Cross-instance restore operation between two databases with different names |
No |
DBID is changed (NID command is invoked) |
|
Cross-instance restore operation between two databases with the same name |
Yes |
DBID is changed (NID command is invoked) |
|
Cross-instance restore operation between two databases with the same name |
No |
DBID is not changed (NID command is not executed) |
|
In-place restore operation |
No (option to change DBID is not available) |
DBID is not changed (NID command is not executed) |