When you configure IBM® Storage Protect
Snapshot
for Oracle, set the configuration parameters when you run the Configuration
Wizard to create snapshots by using target volumes of remote mirroring relationships.
These target volumes are used to create application consistent snapshot backups.
About this task
To configure IBM Storage Protect
Snapshot with
SAN Volume Controller or Storwize® family Global Mirror and Metro Mirror, complete the
following steps:
Procedure
-
On the SAN Volume Controller or Storwize family system, create a partnership between the
primary and secondary clusters.
For example, you can run the following commands from the command-line interface:
ssh -i/dir/ssh-identity username@hostname or ip_primary_cluster
svctask mkpartnership -bandwidth bandwidth_in_mbps remote_cluster_name
or remote_cluster_id
-
Start the Global Mirror and Metro Mirror relationship by using either the graphical user
interface or command-line interface.
If you use the command-line interface, the following commands are provided as an example:
ssh -i/dir/ssh-identity username@hostname or ip_primary_cluster
svctask chpartnership -start remote_cluster_name or remote_cluster_id
-
Verify that the following information is true for the environment:
- The production volumes are on the primary storage system.
- The production volumes are in a remote mirror relationship with the remote volumes that are
either in the secondary cluster, or in the same cluster.
- All the remote mirror relationships are defined in a consistency group.
-
Run the Configuration Wizard to configure a dedicated device class for the
snapshot backups on the remote cluster. When you configure the new
DEVICE_CLASS
section with the wizard, look for the following prompt:
Is the FlashCopy/Snapshot taken from the mirror volumes {COPYSERVICES_REMOTE}.
Enter
yes. The
COPYSERVICES_REMOTE_SERVERNAME,
COPYSERVICES_REMOTE_USERNAME, and
TAKEOVER_HOST_NAME
parameters are also required for remote mirroring.
-
The SSH parameter SVC_SSHKEY_FULLPATH specifies the path and the file name
to the private SSH key file required for SAN Volume Controller.
For remote mirroring, SVC_REMOTE_SSHKEY_FULLPATH specifies the second SSH key
file to be used for authentication on the remote site storage device. The key file is used to
authenticate to the storage system with the user name specified for the
COPYSERVICES_REMOTE_USERNAME parameter. If you do not want to create a new key
pair for the remote site, one key can be shared for both storage sites.
-
If you are using SAN Volume Controller with static target
allocation, you must allocate target volumes. On the remote cluster of the SAN Volume Controller or Storwize family, specify the corresponding snapshot target
volumes for each source.
To specify the snapshot target volumes, use one of the following options: