HP Serviceguard Continentalcluster manual 332

Table 26 Error Messages and their Resolution

Log Messages	Cause	Resolution
The Remote Copy is not functioning	The error was caused by one of the	Start the Remote Copy volume group
from the remote storage system to the	following reasons:	manually using startrcopygroup
local storage system. The package is	• The Remote Copy volume group	command or via 3PAR Management
not allowed to start up. Start the		Console. Restart the package.
	was stopped manually by using
Remote Copy volume group manually
	stoprcopygroup command or
before restarting the package.
	via 3PAR Management Console.
	• There was a link failure followed
	by link restore with auto_recover
	policy not set.
The Remote Copy link is down and	The Remote Copy link is down and the	Create a FORCEFLAG file under the
data in the local storage system might	Remote Copy volume group status is	package directory using touch
not be up-to-date. The user has set	“Stopped”. AUTO_NONCURDATA	<package directory>/FORCEFLAG
AUTO_NONCURDATA parameter to 0,	parameter is not set to 1.	to start the package with or without the
and has not created the FORCEFLAG		latest data in the local storage system.
file. The package is not allowed to		Restart the package.
start up. To start the package forcefully
using non current data, use
FORCEFLAG file.
The Remote Copy volume group is in	The data is being synchronized from	Wait till the Remote Copy volume group
"Syncing" state and	the remote storage system to the local	is fully synchronized and is in “Synced”
RESYNC_WAIT_TIMEOUT parameter	storage system, and the virtual	state. Restart the package.
is set to 0. The package is not allowed	volumes of the Remote Copy volume
to start up.	group are in “Syncing” state.
	Metrocluster parameter
	RESYNC_WAIT_TIMEOUT is set to 0,
	and is configured not to start under
	this condition.
The Remote Copy volume group is set	The policy fail_wrt_on_err is not	Change the Remote Copy volume group
with fail_wrt_on_err and the link is	supported for a Remote Copy volume	policy to “no_fail_wrt_on_err” using the
down. The package is not allowed to	group in a Metrocluster environment.	command setrcopygroup pol
start up.		no_fail_wrt_on_err
		<rc_volume_group_name> or via
		3PAR Management Console.
The role of local Remote Copy volume	The package fails back from the	If application availability is more
group is “Primary” and the role of	remote site when the link is down. The	important than data currency, create a
remote Remote Copy volume group	role of local Remote Copy volume	FORCEFLAG file under the package
role is “Primary-Rev”. The package is	group “Primary” and the role of the	directory using touch <package
not allowed to start up. The link is	remote Remote Copy volume group is	directory>/FORCEFLAG and then
down and the user has not created the	“Primary-Rev”. The package is not	restart the package.
FORCEFLAG file.	started because the data written on
	the remote site has not been replicated
	to the local site. Starting the package
	on the local site discards all the
	changes that were made earlier on
	the remote site.
The Remote Copy volume group is	The Remote Copy volume group is	Start the replication using
either in “New” or “Stale” status. The	configured but not yet started.	startrcopygroup command, and
package is not allowed to start up.		then restart the package.
The role of local Remote Copy volume	The error was caused by one of the	Take corrective actions based on the
group is “Primary” and the role of	following reasons:	cause identified.
remote Remote Copy volume group is	• The storage system is down.
“Primary-Rev”. Start Remote Copy from	• The TCP/IP connectivity from the
the remote site to this site using
“recover” operation before restarting	node to the storage system is
the package.	down.

332 Building Disaster Recovery Serviceguard Solutions Using Metrocluster with 3PAR Remote Copy