HP StorageWorks Storage Mirroring scripting guide (T2558-96074, February 2008)
3 - 1
3 X Getting Started
Getting Started
Not all connection types can be established using the Storage Mirroring scripting language. Review the following lists to see
which connection types you can create using the Storage Mirroring Text Client, Command Line Client, or through scripts.
Providing disaster recovery for an entire server—If you are using the Storage Mirroring Server Recovery Option add-on,
you can protect the entire server, including your data and the server’s system state, which is the server’s configured
operating system and applications. Using the Management Console Connection Wizard, Server Recovery Option
automatically creates a replication set for you, selecting all of the data and system state data on the source. In the event
the source fails, you can recover the entire server, including the system state, to another machine. This connection type
is a disaster recovery solution only. You cannot protect your system state and date for disaster recovery using Storage
Mirroring commands. You must use the Management Console Connection Wizard to establish this type of protection.
See the Storage Mirroring User’s Guide for details on this connection type.
Providing high availability for an entire server—If you are using the Storage Mirroring Full-Server Failover feature, you
can protect the entire server, including your data and the server’s system state, which is the server’s configured operating
system and applications. Using the Full-Server Failover Manager, Full-Server Failover automatically creates a replication
set for you, selecting all of the data and system state data on the source. Additionally, Full-Server Failover automatically
establishes failover monitoring, providing high availability for the source. In the event the source fails, the target can
become the source after a reboot. You cannot protect your system state and date for high availability using Storage
Mirroring commands. You must use the Full-Server Failover Manager to establish this type of protection. See the Storage
Mirroring User’s Guide for details on this connection type.
Protecting specific data—To protect specific data, you identify the data on the source to be included in the replication
set. The connection sends that data to the target. If the event the source fails, the replication set data will be available on
the target. By itself, this connection type provides disaster recovery. You can also configure failover to provide high
availability for your data. See
Protecting Specific Data on page 4-1 for instructions on evaluating this type of connection.
Protecting applications and data—You cannot protect your applications and data using Storage Mirroring commands.
You must use the Application Manager, which is a Storage Mirroring add-on. This add-on has its own installation and
documentation. Download the add-on from the HP web site and look for the file
Application_Manager_Users_Guide.pdf
in the directory where you installed the add-on.
Protecting specifc data in a cluster environment—You cannot establish a connection for a cluster environment using
Storage Mirroring commands. You must use the Windows Cluster administrator to create a cluster resource which
controls the connection. See the Storage Mirroring User’s Guide for details on this connection type.
Protecting specific data across a NAT or firewall—If your source and target are on opposite sides of a NAT or firewall,
you can establish a data protection connection using the same Storage Mirroring commands as a connection without a
router. You will need to specify port setting when you establish your connection. See the notes included with the
connect command. See Protecting Specific Data on page 4-1 for more details.
Simulating a connection—Storage Mirroring offers a simple way for you to simulate a connection in order to generate
statistics that can be used to approximate the time and amount of bandwidth that the connection will use when actively
established. This connection uses the TDU (T
hroughput Diagnostics Utility), which is a built-in null (non-existent) target
to simulate a real connection. No data is actually transmitted across the network. Since there is no true connection, this
connection type helps you plan for a disaster recovery solution. See
Simulating a Connection on page 5-1 for details on
this connection type.