When mounting block snapshots or replications created by a policy containing an Oracle Database classification, Protector will display the following additional wizard pages that allows application specific options to be configured:
Note: To perform the mount operation, a snapshot should be available.
Figure. Snapshot to be mounted
| Control | Description |
|---|---|
| Name | Displays the name of the snapshots to be mounted. |
| Type | Displays the type of the snapshot. |
| Data Origin | Displays the Application Node that was used to create the snapshot. |
| Application | Displays the application on which the snapshot is running. |
| Policy | Displays the policy associated with the snapshot. |
| Operation | Displays the type of the operation for the snapshot. |
| Tags | Displays the tags associated with that snapshot. |
| Expiry Date | Displays the expiry date for the snapshot. |
| Mounted | States the status of the snapshot if it is mounted or not mounted. |
| Filter on Capture Date | Filters the snapshot on the date range on which it was created. |
| Filter on User Tags | Filters the displayed results based on Tags. |
| Filter on Application Node | Filters the snapshot by the name of the node. |
| Filter on Application Node Type | Filters the snapshot on the type of the Application node. |
| Filter on Mounted | Filters the snapshot by either Mounted or Not Mounted. |
| Filter on Data Flow | Filters the snapshot based on the Data Flow associated with a snapshot. |
| Filter on Operation Name | Filters the snapshot so that only entries with the specified Operation Name are displayed. |
| Filter on Type | Filters the snapshot based on its type. |
| Filter on Advanced Query String | Provides advanced search capabilities, allowing users to create filters based on combinations of API properties (see the API reference guide for more details). |
| Search | Returns the result on Advanced Query String. |
Figure. Select Mount Level
| Control | Description |
|---|---|
| SAN | Add this record to a Host Group. |
| Host | Add this record to a Host Group and confirm availability from Host. |
| OS | Add this record to a Host Group and mount to operating system. |
| Application | Add this record to a Host Group, mount to operating system configure by application (This will include ASM operations). |
Figure. Oracle Mount - Select Host
| Control | Description |
|---|---|
| Oracle node | The oracle node where the user will mount the snapshot representing the target Oracle app server environment. |
| OS Host | The node which hosts the Oracle application node. |
| VMware Node | Select the VMware Host or vCenter where the VM's disks will be mounted. |
| Datastore | Select the Datastore where the disk will be mounted. |
Figure. Mount Wizard - Specify Mount Location
| Control | Description |
|---|---|
| New ASM Disk Group | Mount the ASM disk groups using a new generated name to avoid conflicts with the original database or existing ASM disk groups. The new disk group name is auto generated. It comprises the original name and a numeric suffix, allowing for multiple copies of the same database to be mounted to a single host. Note: This option is only valid for backups of ASM based Oracle databases. The option will be disabled automatically if Protector detects a filesystem based Oracle database in a backup created with Protector 7.1 or newer.
|
| Original | Mount the database using the same ASM disk groups or filesystem paths as the original database the backup was created from. If the path or disk group name is in use by an existing database, the mount will fail. |
| Directory | Mount the database to the provided path. If the path in use by an existing database, the mount will fail. Note: This option is only valid for backups of filesystem based Oracle databases. The option will be deactivated automatically, if Protector detects an ASM based Oracle database in a backup created with Protector 7.1 or newer.
|
Figure. Mount Wizard - Select Oracle Restore Options
| Control | Description | Logs Reset Post Mount | Requires RMAN catalog | Requires control/spfile in RMAN backup |
|---|---|---|---|---|
| Restore only | The database is simply mounted. It is left to the database administrator to recover manually. | No | No | No |
| Recover to last consistent state in backup | The database is recovered to the consistent state which was captured by the backup. The database is brought online. This type of mount can be performed with the data in the backup alone. | Depends (see note 1) | No | No |
| Recover to point in time | A timestamp is entered which defines the point in time to recover. This requires a connection to the RMAN catalog and logs which are shared with/available to the host. Note: This is not applicable for DataGuard configuration.
|
Depends (see note 1) | Yes | Yes (see note 2) |
| Recover to system change number (SCN) | A system change number is entered which defines the change point to recover. This requires a connection to the RMAN catalog and logs which are shared with/available to the host. Note: This is not applicable for DataGuard configuration.
|
Depends (see note 1) | Yes | Yes (see note 2) |
| Recover to current position | The database is recovered to the most current position possible. This requires a connection to the RMAN catalog and logs which are shared with/available to the host. Note:
|
Depends (see note 1) | Yes | Yes (see note 2) |
Note: (1) In the table above, logs will only be reset when Open Database is selected in the Post Recovery Options page of the wizard (see below).
CAUTION:
(2) In the table above, for some recovery scenarios the RMAN catalog needs to hold a control file. RMAN can be configured to add a control/spfile backup every time an archive log backup is performed.
Figure. Mount Wizard - Select Post Recovery Options
| Control | Description |
|---|---|
| Change Oracle database ID (DBID) | Creates a new DBID for the database. Tip: A DBID is a unique, Oracle generated number identifying each database. It is found in control files as well as datafile headers and is used to determine which database that file belongs to.
|
| Change Oracle database unique name and SID | A new unique name and SID can be specified for the database. Tip: This changes the unique_database_name which is also used as the SID.
|
| Disable database schedule | Disables database internal tasks scheduled for this database. Tip: The Oracle scheduler allows the administrator to schedule SQL commands as jobs. By selecting this option existing schedules will be disabled.
|
| Open Database | If selected, then after recovery the database will placed in the OPEN state using the RESETLOGS or NORESETLOGS option, as per the requirements of the database. Otherwise the database will be left in the MOUNT state. |
| Advanced Options | Opens the Advanced Options page of the wizard. |
Figure. Mount Wizard - Advanced Mount Options
This page of the wizard is not be displayed if Restore only or Recover to last consistent state in backup is selected in a previous step.
| Control | Description |
|---|---|
| Oracle database Memory Target | Sets the database MEMORY_TARGET in GB. Entering a value here will remove all other memory management related customization of the database. Tip: This allows Oracle databases from very powerful source systems to be deployed on less powerful systems. The PGA and SGA memory areas will be managed by Oracle within the given memory target.
|
| Local Listener | Sets the network name of the Oracle Net local_listener. |
Figure. Mount Wizard - Provide details for changing database ID or name
This page of the wizard will only be displayed if either Change Oracle database ID (DBID) or Change Oracle database unique name and SID options are selected in a previous step.
| Control | Description |
|---|---|
| Password for sys user | Depending on the Oracle version:
|
Figure. Mount Wizard - Specify RMAN credentials
This page of the wizard is not displayed if Restore only or Recover to last consistent state in backup is selected in a previous step.
| Control | Description |
|---|---|
| RMAN Catalog Name | For RMAN only. Enter the RMAN Catalog Name as it is entered in the SQL*Net connect string to connect to the RMAN catalog. |
| Username | For RMAN only. Enter the username for the RMAN catalog. |
| Password | For RMAN only. Enter the password for the RMAN catalog. |