Professional Documents
Culture Documents
5.0
December 2013
Legal Notice
Copyright 2013 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo, Veritas, Veritas Storage Foundation,
CommandCentral, NetBackup, Enterprise Vault, and LiveUpdate are trademarks or registered
trademarks of Symantec Corporation or its affiliates in the U.S. and other countries. Other
names may be trademarks of their respective owners.
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Symantec
Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights in
Commercial Computer Software or Commercial Computer Software Documentation", as
applicable, and any successor regulations, whether delivered by Symantec as on premises
or hosted services. Any use, modification, reproduction release, performance, display or
disclosure of the Licensed Software and Documentation by the U.S. Government shall be
solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports
primary role is to respond to specific queries about product features and functionality.
The Technical Support group also creates content for our online Knowledge Base.
The Technical Support group works collaboratively with the other functional areas
within Symantec to answer your questions in a timely fashion. For example, the
Technical Support group works with Product Engineering and Symantec Security
Response to provide alerting services and virus definition updates.
Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right amount
of service for any size organization
For information about Symantecs support offerings, you can visit our website at
the following URL:
www.symantec.com/business/support/index.jsp
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
Hardware information
Operating system
Network topology
Problem description:
Customer service
Customer service information is available at the following URL:
www.symantec.com/business/support/
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
customercare_apac@symantec.com
semea@symantec.com
supportsolutions@symantec.com
Documentation
Product guides are available on the media in PDF format. Make sure that you are
using the current version of the documentation. The document version appears on
page 2 of each guide. The latest product documentation is available on the Symantec
website.
https://sort.symantec.com/documents
Your feedback on product documentation is important to us. Send suggestions for
improvements and reports on errors or omissions. Include the title and document
version (located on the second page), and chapter and section titles of the text on
which you are reporting. Send feedback to:
doc_feedback@symantec.com
For information regarding the latest HOWTO articles, documentation updates, or
to ask a question regarding product documentation, visit the Storage and Clustering
Documentation forum on Symantec Connect.
https://www-secure.symantec.com/connect/storage-management/
forums/storage-and-clustering-documentation
Contents
Chapter 2
Chapter 3
.............. 16
16
16
18
19
19
20
20
21
21
21
Contents
Chapter 4
Index
23
25
26
27
.................................................................................................................... 28
Chapter
Supported software
Supported hardware
Supported software
For information on the software versions that the agent for EMC RecoverPoint
supports, see the Symantec Operations Readiness Tools (SORT) site:
https://sort.symantec.com/agents.
Supported hardware
The EMC RecoverPoint agent supports all the storage arrays supported by the
RecoverPoint appliance.
10
offline
The agent removes the lock file that the online function had
created for the resource.
monitor
clean
The agent removes the lock file from the local host.
open
The agent removes the online lock file on the host where the
function is called. This function prevents potential
concurrency violation if the service group fails over to another
node while this host is down.
The agent does not remove the lock file if the agent was
started after running the hastop -force command.
info
action/failover
11
action/start_transfer
action/pause_transfer
action/set_retry_migrate_flag The agent sets a flag that indicates that the previous
migration attempt must be retried. See Exceptional
Conditions and Recovery on page 13.
action/unset_retry_migrate_flag The agent clears a flag that indicates that the previous
migration attempt must be retried. See Exceptional
Conditions and Recovery on page 13.
action\GetCurrentRPO
Note: The agent does not compute the RPO when the group
is frozen.
The agent does not store the computed RPO; make a note
of the RPO for future reference.
12
Run the set_retry_migrate_flag action. This action sets a flag that indicates
that the agent must retry the migration attempt that had previously failed.
If you do not bring the RecoverPoint resource online, you must run the
unset_retry_migrate_flag action to clear the flag.
If the enabling of image access takes a long time to complete, and doesnt complete
before OnlineTimeout expires, then the agent flushes and freezes the group
indicating enabling image access hasnt completed. To recover from this condition,
perform the following steps:
13
Chapter
Download the Agent Pack from the Symantec Operations Readiness Tools
(SORT) site: https://sort.symantec.com/agents.
You can download the complete Agent Pack tar file or the individual agent tar
file.
If you downloaded the complete Agent Pack tar file, navigate to the directory
containing the package for the platform running in your environment.
Linux
cd1/linux/generic/vcs/replication/recoverpoint_agent/
agent_version/rpms/
Solaris
cd1/solaris/dist_arch/vcs/replication/recoverpoint_agent/
agent_version/pkgs/
If you downloaded the individual agent tar file, navigate to the pkgs directory
(for AIX, HP-UX, and Solaris), or rpms directory (for Linux).
Log in as superuser.
# rpm -ihv \
VRTSvcsrecpt-AgentVersion-Linux_GENERIC.noarch.rpm
Solaris
# pkgadd -d . VRTSvcsrecpt
# rpm -e VRTSvcsrecpt
Solaris
# pkgrm VRTSvcsrecpt
15
Chapter
RPAUser
Specifies the user name used to connect to the current site RPA.
Type-dimension: string-scalar
Example: admin
SSHBinary
Contains the absolute path to the SSH binary. SSH is the mode of
communication with the RPA.
Default : "/usr/bin/ssh"
Type-dimension: string-scalar
SSHPathToIDFile
Contains the absolute path to the identity file used for authenticating
the host with the RPA. The corresponding public key must be added
on the RPA so that the RPA can correctly authenticate the host.
Type-dimension: string-scalar
Example Value: /rpa/rpa_rsa
FailoverImage
IMAGE=latest
IMAGE=[bookmark_name]
IMAGE=latest
IMAGE=vss_exch
TIME=15:27:33:123456 22/01/2010
17
TryMigrate
18
StartTransfer
Specifies whether data transfer is started from the new source after
failover.
Valid values are 1 and 0.
If this attribute is set to 1, data transfer is started after failover.
If this attribute is set to 0, data transfer is not started after failover.
Default: 1
Type-dimension: integer-scalar
AgentOpts
Lists the options for controlling agent behavior. This attribute is for
future use.
Type-dimension: string-vector
int TryMigrate = 1
str FailoverImage{} = { IMAGE=latest }
int StartTransfer = 1
str AgentOpts[]
temp str VCSBookMark
temp int VCSRetryMigrate
int ComputeDRSLA = 1
)
Oracle
Mount
IP
DiskGroup
NIC
RecoverPoint
Verify that you have installed the agent on all systems in the cluster.
Make sure that the cluster has an effective heartbeat mechanism in place.
See About cluster heartbeats on page 20.
19
Generate public and private RSA keys using ssh-keygen with no passphrase.
For example:
bash-3.00# ssh-keygen -t rsa
Generating public/private rsa key pair.
Enter file in which to save the key (//.ssh/id_rsa): test_rsa
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in test_rsa.
Your public key has been saved in test_rsa.pub.
The key fingerprint is:
05:c1:ce:d0:f7:a1:9f:d1:33:20:bf:c2:9b:35:c8:43 root@thor393
Copy the above generated public key and add it on the RPA using the
add_ssh_key command.
To cache the RPA server key on to the host for further use, run the following
command from the host
/usr/bin/ssh -i <path to RSA private key file> -l <RPA user name>
<IP address of the RPA > <dummy_rp_command>
A message appears, asking you to cache the host key with that of the RPA
server.
Repeat the above steps on each VCS node where the Service Group contains
the RecoverPoint resource.
20
ICMP pings to highly available IP addresses. VCS global clusters also notify the
administrators when the sites cannot communicate.
To minimize the chances of split-brain, use the steward process.
21
Click Import.
If the service group is not configured as a global service group, configure the
service group using the Global Group Configuration Wizard.
See the Symantec Cluster Server Administrator's Guide for more information.
After configuration, the application service group must follow the dependency
diagram. See Sample configuration for the EMC RecoverPoint agent on page 19.
22
Chapter
Figure 4-1
A primary site RPA cluster is attached to the primary storage and the primary
application hosts.
A secondary site RPA cluster attached to the secondary storage and the
secondary application hosts.
Two hosts (Host A and Host B) are attached to the primary site RPA cluster.
Two hosts (Host C and Host D) are attached to the secondary site RPA cluster.
24
Ensure that the TryMigrate attribute is set to 1 (TryMigrate = 1), which is the
default setting.
In the Service Groups tab of the Cluster Explorer configuration tree, right-click
the service group and click Online to bring the service group online on the
primary cluster.
To switch over the service group from the primary cluster to the secondary
cluster, right-click the service group and select Remote Switch.
The service group comes online on the secondary cluster. Now, the secondary
copy becomes the production and the original primary copy becomes the remote
replica. The latest data is available after migration.
To switch back the service group to its original primary cluster, right-click the
service group and select Remote Switch.
The service group comes online on its original primary cluster, and the latest
data is available.
To test the global service group migration in global cluster setup using the command
line interface (CLI)
Switch over the global service group from the primary site to the secondary
site.
Perform the following steps:
Switch the global service group from the primary site to any node in the
secondary site.
hagrp -switch global_group -any -clus cluster_name
VCS brings the global service group online on a node at the secondary site.
Verify that the EMC RecoverPoint devices at the secondary site are
write-enabled, and the Copy is PRODUCTION.
Switch back the global service group from the secondary site to the primary
site.
Perform the following steps:
Switch the global service group from the secondary site to the primary site.
25
VCS brings the global service group online at the primary site.
Verify that the EMC RecoverPoint devices at the secondary site are
write-enabled, and the Copy is PRODUCTION.
Ensure that the TryMigrate attribute is set to 1 (TryMigrate = 1), which is the
default setting.
AutoVCS brings the faulted global service group online at the secondary
site.
Verify that the EMC RecoverPoint devices at the secondary site are
write-enabled, and the Copy is PRODUCTION.
Verify that the latest data is available.
To test disaster recovery for all hosts failure in global cluster setup, using the
command line interface (CLI)
Ensure that the TryMigrate attribute is set to 1 (TryMigrate = 1), which is the
default setting.
AutoVCS brings the faulted global service group online at the secondary
site.
26
Run the following command to verify that the global service group is online at
the secondary site:
hagrp -state global_group
Verify that the EMC RecoverPoint devices at the secondary site are
write-enabled, and the Copy is PRODUCTION.
Verify that the latest data is available.
ManualYou must bring the service group online at the secondary site. Set the
value of the TryMigrate attribute to 0. In the Service Groups tab of the Cluster
Explorer configuration tree, right-click the service group and click Online. After
the service group is online, Symantec recommends that you set the value of
the TryMigrate attribute to 1.
AutoIf the TryMigrate attribute is set to 1, VCS attempts to bring the faulted
global service group online at the secondary site. However, the service group
fails to come online, because the latest data cannot be obtained from the primary
site. To successfully bring the service group online in such a situation, first set
the value of the TryMigrate attribute to 0 and then bring the service group online
manually at the secondary site. In the Service Groups tab of the Cluster Explorer
configuration tree, right-click the service group and click Online. After the service
group is online, Symantec recommends that you set the value of the TryMigrate
attribute to 1.
Note: Disable automatic failback to the original cluster until the replication link is
restored.
27
Index
Attribute definitions 16
AgentOpts 16
ConsistencyGroupName 16
CopyName 16
FailoverImage 16
RPAAddr 16
RPAUser 16
SSHBinary 16
SSHPathToIDFile 16
StartTransfer 16
TryMigrate 16
C
cluster
heartbeats 20
Configuration concepts
attribute definitions 16
resource type definition 18
sample configuration 19
E
EMC RecoverPoint agent
About 9
Attributes 16
Functions 11
Sample configuration 19
supported modes of replication 9
testing 23
F
Functions
action functions 11
clean 11
info 11
monitor 11
offline 11
online 11
open 11
R
Recovery Point Objective (RPO)
Configuring RPO computation support 21
T
TryMigrate attribute
exceptions and recovery 13
U
uninstalling the agent
Linux systems 15
Solaris systems 15