Protector allows the
user to swap the direction of TrueCopy,
Universal Replicator and
Global-Active Device
replications. When a replication is swapped, the S-VOL takes-over the role of the primary
volume and the P-VOL takes over the role of the secondary volume. A swapped replication can,
of course, be swapped back to its normal state with the P-VOL as the primary and S-VOL as the
secondary. The swap operation can also be used to restore consistency between Protector and storage where the
direction of a replication in Protector does not match the current actual direction of the replication on
storage.
A swap operation is typically performed either because maintenance is required, an application failure has occurred, a storage device has failed or disaster has befallen the primary site. Fail-over to the secondary site is therefore necessary.
For active-passive replications (TC and UR):
If both P-VOL and S-VOL are operable and the link between the two sites is available then the replication will be reversed. This is called a swap takeover.
If the replication cannot be re-established once in the swapped state (S-VOL to P-VOL), then the pair is placed in the suspend for swapping (SSWS) state until the problem is resolved. Once the problem is resolved, the swap must be completed by retrying the operation. This is called an S-VOL takeover.
If a swap fully succeeds, the volume that is now the P-VOL will accept writes, and
the volume that is now the S-VOL will not.
For active-active replications (GAD):
A swap operation may be performed to move array processing load from the primary to the secondary device. If both P-VOL and S-VOL are operable and the link between the two sites is available, the secondary array will assume the higher processing load.
If the replication pair has entered an error or suspended state, then once the problem is resolved, the site with the
most recent data must be used to re-establish the replication. Because the replication is
active-active and cross-path set-ups are possible, depending on the nature of the fault,
the P-VOL or S-VOL could contain the most recent data:
If the P-VOL contains the most recent data, no swap is required:
If necessary, unsuspend and unpause the replication.
Resynchronize the replication (via manual trigger or data flow
reactivation).
If the S-VOL contains the most recent data:
Swap the replication to copy the data from the S-VOL to the
P-VOL.
Swap the replication again to restore the original direction. This
is optional, but highly recommended.
The swap operation will result in the both P-VOL and the S-VOL remaining writable.
The following limitations apply when performing a swap operation:
The replication must be implemented using an active live mover; paused or batch replications cannot be swapped.
The replication must be implemented using TrueCopy, Universal Replicator or Global-Active Device.
Snapshot (TI) and local replication (SI and RTI) operations can be assigned to the P-VOL or S-VOL, however remote replication (TC, UR, GAD and Failover) operations cannot.
The state of the takeover is shown on the Monitor page and via the Storage page.
The destination proxy node (ISM) must be available and active since it holds the required
metadata for the replication.
Volumes cannot be added or removed while the replication is reversed or in the SSWS state.
When a GAD replication is swapped, the original P-VOL is marked as reserved. If the replication is torn-down whilst in the swapped state, the reserved flag on the original P-VOL will prevent it being reused. By design Protector never modifies P-VOL properties, so the reserved flag must be manually reset. It is only safe to do this if the replication is no longer under Protector's control; as is the case when tear-down is complete.
Takeover is not integrated with any application swap automation (high availability fail-over or cluster management) software. Therefore additional steps may be required at the OS and/or application level to complete the process.
It is important that Protectors view of the replication direction matches that of the
storage. Replications should not be swapped outside of Protector. If this has
happened, it is important that the replication direction is corrected to match Protectors direction before
any non-swap operations are performed within Protector. This can be done using the swap operation to either
alter the replication direction on the storage to match Protector or vice versa
depending on the direction chosen in the wizard.
During the life cycle of Ops Center Protector, we add new
functionality in each release. However, overtime some functionality had to be deprecated and
removed from the product. To ensure your backups are usable, Ops Center Protector aims to enable restores
of previously created backups even if the capability to create new backups of the same type is
no longer available.
The following section details how to Restore data for backups created with legacy
features
Microsoft Exchange Server backups can be restored as files to a user-specified location.
You can then use Exchange Server’s management tools and/or PowerShell commands to use
them.
Block-based
Block-based backups can be mounted to a Windows client which enables access to the files.
You can then use Exchange Server’s management tools and/or PowerShell commands to use
them.
It is not possible to revert block-based Exchange Server backups.
Microsoft SQL Server backups can be restored as files to a user-specified
location. The backups can be attached to an existing SQL Server instance using the SQL
Server’s management tools.
It is not possible to apply transaction logs to the restored databases.
Block-based
Microsoft SQL Server backups can be mounted to a Windows client, which
provides access to the files. The backups can be attached to an existing SQL Server instance
using the SQL Server’s management tools.
It is not possible to apply transaction logs to the restored databases. It is
also not possible to revert block-based SQL Server backups.
SAP HANA backups can be mounted to a Linux client which makes the files
available at a user-specified path. In addition, the configuration files which are part of
the backup are restored to the following location:
$INSTALL_DIR/saphana_backup/<SID>/<backup_id>
where:
$INSTALL_DIR is the Protector installation dir,
<SID> is the SAP HANA SID,
<backup_id> is the snapshot ID
This section describes the Block Restore options, accessed via the Restore Inventory. Refer to the following sections for details on how to
restore the various block based protections operations.
This wizard is displayed when you restore a VMware snapshot from a Hitachi Block device.
Restore VMware Snapshot Wizard - Select VMs to Restore
Control
Description
VMs in snapshot
Select the specific VMs within this snapshot that are to be restored.
Restore VMware Snapshot Wizard - Select Location
Control
Description
Original location
If the Virtual Machine to be restored does not exist, it will be recreated. If the Virtual Machine to be restored does exist, it will first be backed up on the datastore and then rolled back to the state of the snapshot.
NoteIf you want to replace the existing VM with the restored one, then delete it before restoring.
Clone
The backup will be restored as a clone at the specified location.
The wizard displays the Set clone prefix and destination page when Next is clicked.
NoteA restored Virtual Machine will not overwrite any existing machines with the same name in the same location. If a VM of the same name exists at the restore location then the restore job will fail and log and error to that effect.
Restore VMware Snapshot Wizard - Clone Prefix and Destination
Control
Description
Cloned Virtual Machine Name Prefix
A prefix for the name(s) of the cloned VM(s) must be specified. If the resulting prefixed name is already used by an existing VM in the restore location then the restore will fail and an error will be logged.
Destination Node
Select the VMware Host or vCenter where the cloned VM(s) will be restored.
Select this option to leave the restored VM(s) in the powered off state after they are restored.
Powered on
Select this option to place the restored VM(s) in the powered on state after they are restored.
Network Card State
Select this option to connect the restored VM network card on the VM(s) after they are restored.
Restore VMware Snapshot Wizard – Select Host Groups
Control
Description
Automatically discover
Select this option to all the Host Groups to be automatically determined.
Selected
Use this option to specify the required Host Groups for exposing this restore point to the selected VMware system.
Restore VMware Snapshot Wizard - Select Mount Mode
Control
Description
Mount Original
Mounts the original (Level 1) snapshot and uses vMotion to move the restored VM(s) to the specified location.
CautionThe process of restoring the VM(s) removes it from the snapshot. The metadata for the snapshot will be updated, and thus it will disappear from the snapshot.
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 process of restoring the VM(s) removes it from the snapshot. However, because this is a copy, the original snapshot is preserved.
Mount Pool
Depending on the parameters specified for the snapshot operation on the data flow, a mount pool might be required. A message is displayed in a blue rectangle to explain if and why a mount pool is required.
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.
NoteThe selected mount host must have a pre-existing LUN mounted from the corresponding storage device (this is required for the auto discover feature to work). If not then the automated mount operation will fail and the error message "Cannot mount to machine that does not have path to storage" will be logged.
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.
It is not possible to perform an OS level mount of a backup that was created using a block host node as its source as there would be no way to know what filesystem(s) (if any) are present on the LDEVs to be mounted. If an OS level mount is desired, then the source should be either an application node (with the appropriate application classification) or an OS host node (with a file system path classification).
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
The system command importvg is invoked by Protector 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 Protector when the snapshot is eventually unmounted, although neither will contain any data.
Mount Wizard - Select mount level
Control
Description
SAN
Adds the snapshot or replication to a Host Group.
Host
Adds the snapshot or replication to a Host Group and confirms that it is available from the specified Host.
OS
Adds the snapshot or replication to a Host Group and mounts it on the specified Host's operating system.
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 final step in the wizard provides one of the following application specific mount options:
Mount Wizard - Select Host Group (SAN level mount only)
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.
Add Host Group
Click this button to add host groups when specifying a multi-path mount operation.
Mount Wizard - Select Host Group (Host and OS level mount only)
Control
Description
Automatically discover
Protector will automatically select a host group to use to expose the snapshot or replication.
Selected
The user must specify one or more host groups to use to expose the snapshot or replication.
Select a 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.
Add Host Group
Click this button to add host groups when specifying a multi-path mount operation.
Mount Wizard - Select Host (Host and OS only level mount only)
Control
Description
OS Host
Specify a Protector 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 Protector 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 as RDM disks.
NoteExposing using a VMware host requires that a VMware Server node be configured in Protector and that the mount target VM has Protector 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.
Mount Wizard - Specify mount location (OS level mount only)
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.
NoteProtector 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 mount mode
Control
Description
Mount Original
Mounts the replication or 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)
Enabled only for snapshots and 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:
Snapshot Pool Type (specified on data flow)
Provisioning Type (specified on data flow)
Mount Mode
Mount Pool
Thin Image
Floating Device
Original
Required(1)
Thin Image
Floating Device
Duplicate(4)
Required(1)
Thin Image
Fully Provisioned
Original
N/A(3)
Thin Image
Fully Provisioned
Duplicate(4)
Optional(2)
Hybrid
Floating Device
Original
Optional(2)
Hybrid
Floating Device
Duplicate(4)
Optional(2)
Hybrid
Fully Provisioned
Original
N/A(3)
Hybrid
Fully Provisioned
Duplicate(4)
Optional(2)
The following message is displayed in a blue rectangle to explain the options:
(1) “A mount pool is required because the snapshot is not fully provisioned and resides in a Thin Image pool.”
(2) “A mount pool is optional because the snapshot is fully provisioned and/or resides in a hybrid pool. If a mount pool is not specified the original or duplicate snapshot will use the cascade pool (if configured) or the snapshot pool of the original snapshot.”
(3) “A mount pool is not required because the secondary LDEVs are already fully provisioned.”
(4) “It is only possible to mount a duplicate of a snapshot created with cascade-mode enabled.”
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:
NoteTo perform the mount operation, a snapshot should be available.
Snapshot to be mounted
List of Snapshots 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.
Select Mount Level
Oracle - 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).
Oracle Mount - Select Host
Oracle - 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.
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.
NoteThis 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.
NoteThis 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.
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.
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.
Mount Wizard - Select Post Recovery Options
Control
Description
Change Oracle database ID (DBID)
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
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.
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.
Mount Wizard - Advanced Mount OptionsThis 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.
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 within the given memory target.
Local Listener
Sets the network name of the Oracle Net local_listener.
Mount Wizard - Provide details for changing database ID or nameThis 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:
Oracle 11g: The sys user password is required to change the Oracle database ID or database unique name.
Oracle 12 or newer: This field can be left empty.
Mount Wizard - Specify RMAN credentialsThis 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.
This wizard is displayed when you mount a VMware snapshot or replication from a Hitachi Block device.
Mount VMware Wizard - Select Mount Level
Control
Description
SAN
Expose this record to a Host Group
VMware mount
Mount the disks of a VM from the record, to a target VM
Mount VMware Wizard - Select Host Group
Control
Description
Host Group
Host Group to expose the record to. Multiple Host Groups can be
added
Mount VMware Wizard - Select Virtual Machine
Control
Description
Virtual Machine
Select the specific VM within this snapshot that is to have its disks mounted.
Mount VMware Wizard - Select Virtual Machine to Mount to
Control
Description
VMware Node
Select the VMware Host or vCenter where the VM's disks will be mounted.
Destination
Select the VMware Datacenter, sub-folder and VM where the VM's disks will be mounted.
Mount VMware Wizard - Select Mount Mode
Control
Description
Mount Original
Mounts the VM's VMDKs using the replication or the original (Level 1) snapshot.
CautionAny changes made to the VMDKs will persist when they are unmounted.
Mount duplicate (cascaded snapshot)
Not available for replications. Only enabled if the original (Level 1) snapshot was created in cascade mode. Mounts the VM's VMDKs using a copy of the original snapshot (i.e. a Level 2 snapshot).
CautionAny changes made to the VMDKs will be lost when they are unmounted.
Mount Pool
Not available for replications. Depending on the parameters specified for the snapshot operation on the data flow, a mount pool might be required. A message is displayed in a blue rectangle to explain if and why a mount pool is required.
This wizard allows a snapshot or local replication to be used to revert volume(s) to a prior state.
CautionReverting destroys any changes that were made to data on those volumes subsequent to the selected snapshot or local replication being taken.
Note
Before issuing a revert operation the user should ensure the volume being reverted is not having any other operation performed on it including being mounted, this can be confirmed in the Hitachi Block Replication Details (Storage). If it is mounted the revert will fail silently.
For replications in a cascaded data flow, the immediate upstream and downstream volumes must be in an appropriate state (typically paused or suspended for swap). This is enforced by the storage array hardware.
The revert operation can take some time to complete.
When reverting snapshots or local replications created by a policy containing an Application Classification, Protector will first display one of the following wizard pages that allow application specific options to be configured:
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.
Replication Swap Wizard
Control
Description
Confirm Swap
The word SWAP must be explicitly typed in to confirm the action.
Direction
The final intended direction of the replication after the swap successfully completes.
Enabled for non-VMware snapshots. Opens the Hitachi Block Revert Wizard. to guide you through reverting the snapshot.
Details
Lists the Snapshot details.
Tip
For Thin Image snapshots the Type field is set to Static Thin Snapshot indicating that the record is unchanging and requires the P-VOL to reconstruct an S-VOL.
Storage
Lists the following Storage details.
VMware Details for '<server>'
Only displayed for VMware snapshots. Lists the VMs included in the snapshot, the guest OS and whether the VM has been restored from the original snapshot and is thus no longer available to restore.
Nodes
Shows the nodes involved in the snapshot and opens the Node Details for node.
Links
Provides links to the following pages that provide additional information about the replication:
Data Flow - opens the Data Flow Details where the snapshot operation is assigned.
Policy - opens the Policy Details where the snapshot operation is defined.
This section describes the Host Based Restore options, accessed via the Restore Inventory. Refer to the following sections for details on
how to restore the various hast based protections operations.
This wizard is displayed when you restore a file system snapshot from a repository store.
Caution Be careful when restoring data to a location that is in the scope of one or more Ops Center Protector policies. The restored data will not be incorporated by Ops Center Protector into its data flows until after a resynchronization has occurred and synchronization errors for the restored data can be logged until that point. Perform a manual resynchronization to correct the inconsistent state.
NoteThe following data restoration limitations apply:
Because of issues with translating security streams, data originating from Linux machines cannot be restored to Windows machines and vice versa. Data can only be restored to compatible OS types.
Restore File System Wizard - Select restore scope
Control
Description
Entire snapshot
The entire contents of the snapshot will be restored. The wizard displays the Select restore options page when Next is clicked.
User Selection
Only those files selected by the user will be restored. The wizard displays the Select files and directories to restore page when Next is clicked.
Restore File System Wizard - Select files and directories to restore
Control
Description
File System Contents
Select the directories and/or files you want to restore by clicking the checkbox
to the left of its name (a tick mark is displayed next to every file that will be
restored). To expand/collapse a folder, click the arrow symbol to the left of its
name.
Restore File System Wizard - Select restore options
Control
Description
Destination Node
The target node for the restore.
Original Path
Use the original path names when restoring files.
Custom Path
Use a new path based on the Trim From Paths and Destination Path specification. Refer to the Trim From Path Examples in Destination Template Wizard.
Trim From Path
Presents a list of path prefixes that can be removed from the files being restored, whilst ensuring files remain grouped together in their respective folders.
Destination Path
The path specification to be prepended once the paths are trimmed.
Route via Node
Select a node to route via. Primarily used for Internet Connected Nodes where the destination is not directly connected to the repository node, so a proxy must be specified.
Attempt to overwrite colliding files, if that fails then rename
If overwriting fails then the file will be restored by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
Attempt to overwrite colliding files, if that fails then skip
If overwriting fails then the new file will NOT be restored.
Rename any colliding files
Differentiates all colliding files by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
Rename all restored files
Differentiates all restored files by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
This wizard is displayed when you restore a Ops Center snapshot from a repository store.
Caution Be careful when restoring data to a location that is in the scope of one or more Ops Center Protector policies. The restored data will not be incorporated by Ops Center Protector into its data flows until after a resynchronization has occurred and synchronization errors for the restored data can be logged until that point. Perform a manual resynchronization to correct the inconsistent state.
NoteThe following data restoration limitations apply:
Because of issues with translating security streams, data originating from Linux machines cannot be restored to Windows machines and vice versa. Data can only be restored to compatible OS types.
Restore Ops Center Application Wizard - Select application to restore
Control
Description
Applications to Restore
Select the applications you want to restore by clicking the checkbox to the left of the application name (a tick mark is displayed next to every file that will be restored). The wizard displays the Select restore options page when Next is clicked.
Restore Ops Center Application Wizard - Select restore options
Control
Description
Destination Node
The target node for the restore. This destination node must be set to the node hosting the application to be recovered.
Route via Node
Select a node to route via. Primarily used for Internet Connected Nodes where the destination is not directly connected to the repository node, so a proxy must be specified.
Custom Options
Custom options may be entered in the text box - these options will be saved to a file and that file given to the applications 'restore command/script s parameter '%3'. These should only be entered if stated in the documentation for the application.
This wizard is displayed when you restore a file system snapshot from an HCPstore.
Caution Be careful when restoring data
to a location that is in the scope of one or more Ops Center Protector
policies. The restored data will not be incorporated by Ops Center Protector into
its data flows until after a resynchronization has occurred and synchronization errors for
the restored data can be logged until that point. Perform a manual resynchronization to
correct the inconsistent state.
NoteThe following data restoration limitations apply:
Becauseof issues with translating security streams, data originating from Linux
machines cannot be restored to Windows machines and vice versa. Data can only be
restored to compatible OS types.
Restore HCP File System Wizard - Select restore scope
Control
Description
Entire snapshot
The entire contents of the snapshot will be restored. The wizard displays the Select restore options page when Next is clicked.
User Selection
Only those files selected by the user will be restored. The wizard displays the Select files and directories to restore page when Next is clicked.
Restore HCP File System Wizard - Select items to restore
Control
Description
File System Contents
Select the directories and/or files you want to restore by clicking the checkbox to the left of its name (a tick mark is displayed next to every file that will be restored). To expand/collapse a folder, click the plus/minus symbol (+/-) to the left of its name.
Restore HCP File System Wizard - Select restore options
Control
Description
Destination Node
The target node for the restore.
Original Path
Use the original path names when restoring files.
Custom Path
Use a new path based on the Trim From Paths and Destination Path specification. Refer to the Trim From Path Examples in Destination Template Wizard.
Trim From Path
Presents a list of path prefixes that can be removed from the files being restored, whilst ensuring files remain grouped together in their respective folders.
Destination Path
The path specification to be prepended once the paths are trimmed.
Route via Node
Select a node to route via. Primarily used for Internet Connected Nodes where the destination is not directly connected to the repository node, so a proxy must be specified.
Attempt to overwrite colliding files, if that fails then rename
If overwriting fails then the file will be restored by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
Attempt to overwrite colliding files, if that fails then skip
If overwriting fails then the new file will NOT be restored.
Rename any colliding files
Differentiates all colliding files by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
Rename all restored files
Differentiates all restored files by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
This wizard is displayed when you restore a file system snapshot from an S3 store.
Caution Be careful when restoring data
to a location that is in the scope of one or more Ops Center Protector
policies. The restored data will not be incorporated by Ops Center Protector into
its data flows until after a resynchronization has occurred and synchronization errors for
the restored data can be logged until that point. Perform a manual resynchronization to
correct the inconsistent state.
NoteThe following data restoration limitations apply:
Because of issues with translating security streams, data originating from Linux machines cannot be restored to Windows machines and vice versa. Data can only be restored to compatible OS types.
Restore S3 File System Wizard - Select restore scope
Control
Description
Entire snapshot
The entire contents of the snapshot will be restored. The wizard displays the Select restore options page when Next is clicked.
User Selection
Only those files selected by the user will be restored. The wizard displays the Select files and directories to restore page when Next is clicked.
Restore S3 File System Wizard - Select items to restore
Control
Description
File System Contents
Select the directories and/or files you want to restore by clicking the checkbox to the left of its name (a tick mark is displayed next to every file that will be restored). To expand/collapse a folder, click the plus/minus symbol (+/-) to the left of its name.
Restore S3 File System Wizard - Select restore options
Control
Description
Destination Node
The target node for the restore.
Original Path
Use the original path names when restoring files.
Custom Path
Use a new path based on the Trim From Paths and Destination Path specification. Refer to the Trim From Path Examples in Destination Template Wizard.
Trim From Path
Presents a list of path prefixes that can be removed from the files being restored, whilst ensuring files remain grouped together in their respective folders.
Destination Path
The path specification to be prepended once the paths are trimmed.
Route via Node
Select a node to route via. Primarily used for Internet Connected Nodes where the destination is not directly connected to the repository node, so a proxy must be specified.
Attempt to overwrite colliding files, if that fails then rename
If overwriting fails then the file will be restored by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
Attempt to overwrite colliding files, if that fails then skip
If overwriting fails then the new file will NOT be restored.
Rename any colliding files
Differentiates all colliding files by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
Rename all restored files
Differentiates all restored files by prepending the restore version (that is (VersionNumber)_filename.ext) to the file name.
Restore VMware Host Based Backup Wizard - Select files and directories to restore
Control
Description
Virtual Machine List
Select the VMs and Folders to restore. To expand/collapse a
folder, click the arrow symbol to the left.
Restore VMware Host Based Backup Wizard - Select location
Control
Description
Original location
If the Virtual Machine to be restored does not exist, it will be recreated. If the Virtual Machine to be restored does exist, it will first be backed up on the datastore and then rolled back to the state of the snapshot.
NoteIf you want to replace the existing VM with the restored one, then delete it before restoring
Clone
The backup will be restored as a clone at the specified location.
The wizard displays the Set clone prefix and destination page when Next is clicked.
NoteA restored Virtual Machine will not overwrite any existing machines with the same name in the same location. If a VM of the same name exists at the restore location then the restore job will fail and log and error to that effect.
Restore VMware Host Based Backup Wizard - Set clone prefix and destination
Control
Description
Destination Node
Specifies which vCenter or ESX/ESXi node the VMs are to be restored to.
Cloned Virtual Machine Name Prefix
Optional: Clones the original VMs with the prefix applied to the
name if specified.
Restore VMware Host Based Backup Wizard - Select clone destination
Control
Description
Datacenters/Folders
Select the datacenter or folder where the clones are to be located.
TipAll the operations available from the Restore UI are also available from the Storage UI (see the Storage UI Reference). The Storage UI also enables additional operations to be performed.
Ops Center Protector maintains an inventory of all available backups that can be viewed as follows:
Restore
Mount
Unmount
Revert
Swap
Repository Snapshot Tile
Hitachi Block Snapshot Tile
Hitachi Block Replication Tile
