HP 3PAR Application Software Suite for Microsoft Exchange - Manual (Page 152)

Table 10 HP 3PAR Recovery Manager Software for Microsoft Exchange Event Messages (continued)
Description/Action Error Message Event ID
The Mailbox Database is not mounted.
•
Use Exchange Management Shell to mount the database. Or use
Mount-Database cmdlet to mount the database
RME3009: ERROR: Could not
determine the mount status of
mailbox database '%1'. 3009
The circular logging must be disabled for the Mailbox database and to
continue with the restore operation.
•
Go to Mailbox properties, click on Maintenance tab and clear the
Enable Circular Logging box.
RME3010: ERROR: The Circular
logging is enabled for the
mailbox database '%1'. 3010
The circular logging must be disabled for the Mailbox database and to
continue with the restore operation.
• Go to Storage Group properties, under General tab and clear the
Enable Circular Logging box.
RME3011: ERROR: The Circular
logging is enabled for the
storage group '%1'. 3011
The backup server is unable to retrieve the cluster information. RME3012: ERROR: Failed to get
information for the Cluster
Mailbox '%1'. 3012
•
Install "Failover Clustering Tools" feature on the RM backup server.
• Ensure the settings for servers participating in cross domain
configuration are correct. Refer user guide for cross domain
configuration setup if necessary.
The clustered Mailbox server in CCR configuration is not a valid.
•
Correct the errors via Exchange Management Shell and continue the
operation again.
RME3013: ERROR: The
Clustered Mailbox Server '%1'
is NOT valid. 3013
Recovery Manager for Exchange version 4.3 does not support restore
operation of Virtual copy taken from a passive node within a cluster.
•
To restore from passive copy, perform the failover to passive node
and then perform the restore operation of the virtual copy.
RME3014: ERROR: The restore
operation is carried out on
virtual copy taken from Passive
Node '%1' of Cluster. 3014
For a FileCopy restore operation, mount the previously created virtual
copy to the originating server.
• To perform the FileCopy, unmount the VC and mount it to correct
production server.
RME3015: ERROR: The virtual
copy '%1' is not mounted to the
active server '%2' and can not
be filecopy restored. 3015
Recovery Manager for Exchange does not support restore operation of
a virtual copy taken from passive node within a cluster. RME3016: ERROR: The restore
of virtual copy '%1' is done from 3016
passive node. The volume
promote is not supported from
passive node in LCR
configuration.
The replication status for the storage group on server could not be
obtained because of exchange error.
•
Refer to the exchange error and take corrective actions.
RME3017: ERROR: Failed to get
replication status for the storage
group '%1' on server '%2'. 3017
The storage group on server cannot be suspended because of exchange
error.
•
Refer to the exchange error and take corrective actions.
RME3018: ERROR: Failed to
suspend replication for the
storage group '%1' on server
'%2'. 3018
The replication status for the storage group is suspended. RME3019: The replication for
the storage group '%1' is
suspended on server '%2'. 3019
For create and restore operations, the passive copy of cluster should be
in HEALTHY status. The replication status for the passive copy of the
storage group is not in sync with the active copy. RME3020: ERROR: The copy
status for the storage group '%1'
on server '%2' is not healthy. 3020
•
Wait for the replication to finish if the replication is pending.
• Or use EMS or cmdlet Update-StorageGroupCopy to update
the copy status.
152 Event Messages