Monitoring and pair operations in Data Instance Director
Hitachi Block Snapshot or Replication Mount Wizard
This wizard is displayed when you mount a snapshot or replication from a Hitachi Block device.
This wizard allows you to expose volumes or mount the selected snapshot or replication.
Caution
- When a snapshot or replication is mounted, it is made writable. Any changes made to the mounted original snapshot or replication will persist even after it has been unmounted.
- Any attempt to mount two or more copies of the same volume(s) simultaneously on the same machine will fail. The base OS will experience problems if there is already an instance of that file system mounted. This is because snapshots and replications share the same disk partition IDs as the original volume. In extreme conditions it can cause corruption to both disks.
Note
- It is not possible to mount the SVOL of a GAD replication, paused or otherwise.
- For Oracle ASM the disks will be presented to the OS but will need to be manually mounted.
- When mounting a snapshot that contains a mounted sub directory, the subdirectory will be mounted as expected. However, the volume referenced by the subdirectory will also be mounted as a separate drive. Unmount will unmount both the expected and unexpected mounts.
- The mount operation can take several minutes to complete.
- If a mount operation needs to mount multiple disks and one of the mount operations fail, the snapshot/replication destination is shown as mounted rather than partially mounted. The logs will indicate the mount was only partially successful.
NoteOperating System Specific Behaviour
OS | Note |
Linux | When mounting a Linux snapshot to a different Linux machine; in order for the user and group names to be displayed correctly the users and groups must have the same ID's as the source. |
SUSE Linux | SUSE Linux is not able to perform automated mount operations if hosted on VMware. (RHEL and OEL Linux work as expected). |
AIX &
Solaris | The system command importvg is invoked by HDID to mount snapshots to the user specified location. importvg creates a directory for the user specified location plus an empty directory corresponding to the original mount point. Neither of these directories are removed by HDID when the snapshot is eventually unmounted, although neither will contain any data. |
Control | Description |
SAN | Adds the snapshot or replication to a Host Group. The wizard displays the Select Host Group page next. |
Host | Adds the snapshot or replication to a Host Group and confirms that it is available from the specified Host. The wizard displays the Select Host Group and host page next. |
OS | Adds the snapshot or replication to a Host Group and mounts it on the specified Host's operating system. The wizard displays the Select Host Group and host page next. |
Application | Displayed only for application snapshots. Adds the snapshot or replication to a Host Group and mounts it on the specified Host's operating system. The wizard displays the
Select Host Group and host page next. The final step in the wizard provides one of the following application specific mount options:
|
Control | Description |
Host Group | Manually specify or select a host group to use to expose a snapshot or replication.
NoteWhen exposing an LDEV, the host group specified must be in the same resource group as the secondary volumes.
|
Control | Description |
Host Group | Select from:
|
OS Host | Specify an HDID
OS Node to mount to or expose to.
NoteUnless the user selects a host group, the machine where the volume is to be mounted must have an existing volume on the same storage device. If there is no connection between the mount host and the block storage device then HDID will fail the mount operation after a timeout of 30 minutes.
|
VMware Node | Expose the volumes to the specified VMware host and mount them to the VM and RDM disks.
NoteExposing using a VMware host requires that a VMware Server node be configured in HDID and that the mount target VM has HDID Client and VMware Tools installed.
|
Datastore | Specifies a destination datastore when mounting to a VMware VM which is part of a cluster, in which case the default datastore may not be a suitable place to save the RDM mount information. If the datastore field is left blank then mount information is saved alongside the VM. |
Next/Finish | If Host was selected in the initial step then the Finish button is displayed. If OS was selected then the wizard displays the Select mount location page next. |
Control | Description | ||||||||||||||||||||||||||||||||||||
Mount Original | Mounts the original (Level 1) snapshot.
NoteIf the mounted snapshot is modified then those changes will remain when the snapshot is unmounted.
| ||||||||||||||||||||||||||||||||||||
Mount duplicate (cascaded snapshot) | Only enabled if the original (Level 1) snapshot was created in cascade mode. Mounts a copy of the original snapshot (i.e. a Level 2 snapshot).
NoteThe mounted snapshot will be discarded when it is unmounted.
| ||||||||||||||||||||||||||||||||||||
Mount Pool | Depending on the parameters specified for the snapshot operation on the data flow, a mount pool might or might not be required.
The following table lists all the scenarios:
The following message is displayed in a blue rectangle to explain the options:
|
Control | Description |
Original | The snapshot or replication is mounted at its original location.
NoteMounting at the original location will fail if there is already a volume mounted at that location.
|
Drive starting at letter | When mounting a snapshot or replication that contains multiple volumes, the first volume will mount at the specified drive and subsequent drives are used for each additional volume. |
Directory | When mounting a snapshot or replication that contains multiple volumes, each volume will be assigned a separate subdirectory. Click Browse to view the drives and directories on the selected host. To create a new directory, type in the required path.
NoteHDID does not check to make sure the directory selected as the mount point is empty. This means it is possible to mount a snapshot inside or even over the top of another mounted volume. This should be avoided.
|
Mount Wizard - Select Microsoft SQL Restore Options
When mounting block snapshots or replications created by a policy containing an MS SQL Server classification, HDID will display the following additional wizard page that allows application specific options to be configured:
NoteMicrosoft SQL server databases that are part of a multi-volume snapshot must be mounted using the Mount Location and Directory option in the Select mount location page of the Mount Hitachi Block Snapshot or Replication wizard, then recovered manually.
Control | Description |
Restore Only | Restores the backup without any further action. |
Add database to an instance and allow further manual recovery | Puts the database in a restoring state, so that the additional backups can be restored. The restore sequence can restore other backups and replay transaction logs to support roll forward. When the database is in a restoring state, no users can access the database or the database contents. |
Add database to an instance and bring up database | Recovers the database to a consistent state captured by the backup and brings the database online. No rolling-forward is performed to ensure that the transaction logs are not replayed. |
Instance | Only enabled for Add database to an instance... restore types. The name of the instance. |
Database Owner | Only enabled for Add database to an instance... restore types. The database owner's name. |
Backup Database Name | Only enabled for Add database to an instance... restore types. The backup database's name. |
Mount Wizard - Select Oracle Restore Options
When mounting block snapshots or replications created by a policy containing an Oracle Database classification, HDID will display the following additional wizard pages that allows application specific options to be configured:
This page of the wizard is displayed if the Advanced Options button is clicked on the Select Post Recovery Options page of the wizard.
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.
This page of the wizard is only displayed if Restore only or Recover to last consistent state in backup is selected in a previous step.
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. | 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. | 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. NoteWhen mounting, the current position is the latest point in time which is provided by the archive logs referenced in RMAN catalog. It does not include any archive logs or redo logs on the source machine which have not been backed up via RMAN. | 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.
Control | Description |
Change Oracle database ID (DBID) | Only available when Recover to last consistent state in backup is selected. Creates a new DBID for the database. TipA 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 | Only available when Recover to last consistent state in backup is selected. 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 | Only available when Recover to last consistent state in backup is selected. Disables database internal tasks scheduled for this database. TipThe 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. |
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. TipThis 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 withing the given memory target. |
Local Listener | Sets the network name of the Oracle Net local_listener . |
Control | Description |
Password for sys user | Depending on the Oracle version:
|
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. |
Hitachi Block Replication Swap Wizard
This wizard causes the direction of a replication to be reversed so that the secondary replicates to the primary.
CautionWhen a replication is swapped, the secondary becomes writeable and the primary becomes read-only.
Note
- If the swap cannot be completed then the replication pair enters the SSWS (suspended for swapping) state until the swap can be completed. The swap operation must be re-done by the user to complete a suspended swap.
- The flow direction of a replication pair should ONLY be determined by referring to the Storage Inventory. Primary and secondary volume information shown in the Log Attachments Dialog should not be used to infer the flow direction following a swap.
Control | Description |
Confirm Swap | The word SWAP must be explicitly typed in to confirm the action. |
Access Control Transfer Permissions Dialog
This dialog is displayed when the permissions for a resource are being tranferred from the current owner to new owner.
Control | Description |
Node | Select the node that will become the owner of this resource. |