Skip to content

Failover

app_failover


BlueprintFailoverCanceled

Canceled failover Recovery Plan '${name}' to '${location}'.
Severity Status Audit Event
Info Canceled No

BlueprintFailoverCanceling

Canceling failover for Recovery Plan '${name}' to '${location}'.
Severity Status Audit Event
Info Canceling No

BlueprintFailoverDataIngestionFailed

'${dataIngestionOperation}' process failed for Recovery Plan '${name}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

BlueprintFailoverDataIngestionStarted

Starting the '${dataIngestionOperation}' process for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverDataIngestionSucceed

'${dataIngestionOperation}' process succeeded for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverFailed

Failed to failover Recovery Plan '${name}' to '${location}': ${reason}.
Severity Status Audit Event
Critical Failure No

BlueprintFailoverFinalizeFailed

Final failover tasks failed for failover of Recovery Plan '${name}': ${reason}.
Severity Status Audit Event
Critical Failure No

BlueprintFailoverFinalizeStarted

Starting the final failover tasks for failover of Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverFinalizeSucceed

Final failover tasks succeeded for failover of Recovery Plan '${name}'.
Severity Status Audit Event
Info Success No

BlueprintFailoverIncrementalDataTransferFailed

Incremental data transfer process failed for Recovery Plan '${name}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

BlueprintFailoverIncrementalDataTransferStarted

Starting the incremental data transfer process for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverIncrementalDataTransferSucceed

Incremental data transfer process succeeded for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverPrepareDataFailed

Failover initialization process failed for Recovery Plan '${name}'. Reason: ${reason}.
Severity Status Audit Event
Critical TaskFailure No

BlueprintFailoverPrepareDataStarted

Starting the failover initialization process for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverPrepareDataSucceed

Failover initialization process succeeded for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverPrepareResourceFailed

Failover resource validation and initialization process failed for Recovery Plan '${name}'. Reason: ${reason}.
Severity Status Audit Event
Critical TaskFailure No

BlueprintFailoverPrepareResourceStarted

Starting the failover resource validation and initialization process for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverPrepareResourceSucceed

Failover resource validation and initialization process succeeded for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverProvisionFailed

Unable to set up the target Rubrik cluster '${targetClusterName}' for failover of Recovery Plan '${name}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

BlueprintFailoverProvisionStarted

Setting up the target Rubrik cluster '${targetClusterName}' for failover of Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverProvisionSucceed

Reconfiguration of virtual machines on target Rubrik cluster '${targetClusterName}' succeeded for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverProvisionSucceedWithNetworkReconfigureFailure

Reconfiguration of virtual machines on target Rubrik cluster '${targetClusterName}' failed for Recovery Plan '${name}'. Ignoring and continuing.
Severity Status Audit Event
Warning TaskSuccess No

BlueprintFailoverScheduled

Scheduled job to failover Recovery Plan '${name}' to '${location}'.
Severity Status Audit Event
Info Queued No

BlueprintFailoverStarted

Starting failover for Recovery Plan '${name}' to '${location}'. Failover error handling option is set to ${errorHandling}. Skipping network reconfiguration errors is ${skipNetworkError}.
Severity Status Audit Event
Info TaskSuccess No

BlueprintFailoverSuccess

Successfully completed the failover for Recovery Plan '${name}' to '${location}'.
Severity Status Audit Event
Info Success No

BlueprintTakeOnDemandSnapshotFailed

On demand snapshot for Recovery Plan '${blueprintName}' failed.
Severity Status Audit Event
Info Failure No

BlueprintTakeOnDemandSnapshotStarted

Starting on demand snapshot for Recovery Plan '${blueprintName}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintTakeOnDemandSnapshotSucceed

On demand snapshot for Recovery Plan '${blueprintName}' successfully completed.
Severity Status Audit Event
Info Success No

BlueprintWaitOnDemandSnapshotFailed

Waiting on demand snapshot for Recovery Plan '${blueprintName}' failed.
Severity Status Audit Event
Info Failure No

BlueprintWaitOnDemandSnapshotStarted

Waiting for on demand snapshot for Recovery Plan '${blueprintName}'.
Severity Status Audit Event
Info TaskSuccess No

BlueprintWaitOnDemandSnapshotSucceed

Waiting on demand snapshot for Recovery Plan '${blueprintName}' succeeded.
Severity Status Audit Event
Info Success No

CleanupFailoverCanceled

Canceled the failover cleanup for Recovery Plan '${name}'.
Severity Status Audit Event
Info Canceled No

CleanupFailoverCanceling

Canceling the failover cleanup for Recovery Plan '${name}'.
Severity Status Audit Event
Info Canceling No

CleanupFailoverFailed

Failed to cleanup failover for Recovery Plan '${name}' with ${reason}.
Severity Status Audit Event
Critical Failure No

CleanupFailoverStarted

Started failover cleanup for Recovery Plan '${name}'.
Severity Status Audit Event
Info TaskSuccess No

CleanupFailoverSuccess

Successfully completed the failover cleanup for Recovery Plan '${name}'.
Severity Status Audit Event
Info Failure No

CleanupFailoverTaskFailed

Failed to cleanup Recovery Plan ${name}: ${reason}.
Severity Status Audit Event
Critical TaskFailure No

CleanupFailoverTaskFailedWithUserComment

Failed to cleanup Recovery Plan '${name}'. ${comment} : ${reason}.
Severity Status Audit Event
Critical TaskFailure No

CleanupFailoverTaskStarted

Started cleanup for Recovery Plan ${name}.
Severity Status Audit Event
Info Running No

CleanupFailoverTaskSucceed

Successfully completed the cleanup for Recovery Plan ${name}.
Severity Status Audit Event
Info TaskSuccess No

CleanupFailoverTaskSucceedWithUserComment

Successfully completed the cleanup for Recovery Plan '${name}'. ${comment}.
Severity Status Audit Event
Info TaskSuccess No

FailbackCloudMachineShutdownFailed

Failed to shut down ${instanceType} ${instanceName}.
Severity Status Audit Event
Info TaskFailure No

FailbackCloudMachineShutdownSucceed

Shut down ${instanceType} ${instanceName}.
Severity Status Audit Event
Info TaskSuccess No

FailbackCloudMachineShutdownTaskFailed

During failover, system was unable to shutdown the child ${instanceType} of Recovery Plan '${blueprintName}': ${reason}. Please shutdown the child ${instanceType} manually to avoid potential resource conflicts with the child ${instanceType} spun up during failover. Resource conflicts, such as IP address collisions, may result in failures, including failure to boot during failover.
Severity Status Audit Event
Warning TaskFailure No

FailbackCloudMachineShutdownTaskStarted

Started the shutdown process for Recovery Plan child ${instanceType}.
Severity Status Audit Event
Info Running No

FailbackCloudMachineShutdownTaskSucceed

Shut down all Recovery Plan child ${instanceType}.
Severity Status Audit Event
Info TaskSuccess No

FailbackCreateOnDemandBlueprintSnapshotTaskFailed

Failed to create a snapshot for the current state of the Recovery Plan '${blueprintName}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

FailbackCreateOnDemandBlueprintSnapshotTaskStarted

Started taking a snapshot for the current state of the Recovery Plan '${blueprintName}'.
Severity Status Audit Event
Info Running No

FailbackCreateOnDemandBlueprintSnapshotTaskSucceed

Created a snapshot for the current state of the Recovery Plan '${blueprintName}'.
Severity Status Audit Event
Info TaskSuccess No

FailbackDeprecatePrimaryAppTaskFailed

Failed to deprecate the primary Recovery Plan '${blueprintName}': ${reason}.
Severity Status Audit Event
Warning TaskFailure No

FailbackReprotectTaskFailed

Failed to reprotect the Recovery Plan '${blueprintName}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

FailbackReprotectTaskStarted

Reprotecting the Recovery Plan '${blueprintName}'.
Severity Status Audit Event
Info Running No

FailbackReprotectTaskSucceeded

Reprotected the Recovery Plan '${blueprintName}' with SLA '${slaName}'.
Severity Status Audit Event
Info TaskSuccess No

FailbackSyncRecoverySpecTaskFailed

The Recovery Plan '${blueprintName}' at the target cluster could not be synchronized with the source due to a communication issue. This could be a result of network issues between the source and target clusters or an incorrect replication configuration. Please resolve the issue to make sure the replication has been setup correctly between the source cluster and the target cluster, then retry the failover job.
Severity Status Audit Event
Critical TaskFailure No

FailbackSyncRecoverySpecTaskStarted

Started syncing the latest recovery spec to the target cluster.
Severity Status Audit Event
Info Running No

FailbackSyncRecoverySpecTaskSucceed

Successfully synced the latest recovery spec to the target cluster.
Severity Status Audit Event
Info TaskSuccess No

FailoverAssignClonedSLAFailed

Failed to assign the cloned SLA to the newly created Recovery Plan: ${reason}.
Severity Status Audit Event
Warning TaskFailure No

FailoverAssignSLAFailed

Failed to assign the SLA '${slaName}' to the newly created Recovery Plan: ${reason}.
Severity Status Audit Event
Warning TaskFailure No

FailoverDeprecatePrimaryAppTaskFailed

Failed to deprecate the primary Recovery Plan '${blueprintName}': ${reason}, the ${instanceType} should be shutdown manually.
Severity Status Audit Event
Warning TaskFailure No

FailoverDeprecatePrimaryAppTaskStarted

Started to deprecate the primary Recovery Plan '${blueprintName}'.
Severity Status Audit Event
Info Running No

FailoverDeprecatePrimaryAppTaskSucceed

Successfully deprecated the primary Recovery Plan '${blueprintName}'.
Severity Status Audit Event
Info TaskSuccess No

FailoverSLANotFound

SLA not found when assigning SLA to the newly created Recovery Plan.
Severity Status Audit Event
Warning TaskFailure No

RecoveryPlanFailoverPartialSuccess

The failover for Recovery Plan, '${name}', to '${location}' was partially successful. ${partialFailureInfo}
Severity Status Audit Event
Info Success No

SyncFailbackTaskFailed

Failover failed on cluster '${clusterName}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

SyncFailbackTaskSucceed

Failover succeeded on cluster '${clusterName}'.
Severity Status Audit Event
Info TaskSuccess No

TriggerFailbackTaskFailed

Failed to trigger failover job for Recovery Plan to the point in time: ${recoveryPoint} on cluster '${clusterName}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

TriggerFailbackTaskFailedWithTimeRange

Failed to trigger failover job for Recovery Plan to the point in time: range from ${startTime} to ${endTime} on cluster '${clusterName}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

TriggerFailbackTaskStarted

Failover job for Recovery Plan to the point in time: ${recoveryPoint} triggered on cluster '${clusterName}'.
Severity Status Audit Event
Info Running No

TriggerFailbackTaskStartedWithTimeRange

Failover job for Recovery Plan to the point in time: range from ${startTime} to ${endTime} triggered on cluster '${clusterName}'.
Severity Status Audit Event
Info Running No

TriggerFailbackTaskSucceed

Triggered a failover job for Recovery Plan to the point in time: ${recoveryPoint} on cluster '${clusterName}'.
Severity Status Audit Event
Info TaskSuccess No

TriggerFailbackTaskSucceedWithTimeRange

Triggered a failover job for Recovery Plan to the point in time: range from ${startTime} to ${endTime}, on cluster '${clusterName}'.
Severity Status Audit Event
Info TaskSuccess No

ValidateRecoverySpecTaskFailed

Failed to validate the recovery spec of Recovery Plan '${blueprintName}' on cluster '${clusterName}': ${reason}.
Severity Status Audit Event
Critical TaskFailure No

ValidateRecoverySpecTaskStarted

The recovery spec of Recovery Plan '${blueprintName}' is being validated on cluster '${clusterName}'.
Severity Status Audit Event
Info Running No

ValidateRecoverySpecTaskSucceed

Validated the recovery spec of Recovery Plan '${blueprintName}' on cluster '${clusterName}'.
Severity Status Audit Event
Info TaskSuccess No

appflows


BlueprintFailoverCleanupStart

${userEmail} triggered cleanup job for recovery plan '${blueprintName}'.
Severity Status Audit Event
Info Success Yes

BlueprintFailoverStart

${userEmail} triggered failover for recovery plan '${blueprintName}' to ${targetSite}.
Severity Status Audit Event
Info Success Yes

BlueprintTestFailoverStart

${userEmail} triggered test failover for recovery plan '${blueprintName}' to ${targetSite}.
Severity Status Audit Event
Info Success Yes

rcv


RCVGRSFailoverReestablishmentPending

Rubrik Cloud Vault location '${locName}' has been successfully  failed over to '${regionType}' region, '${currentRegionName}'  with LRS redundancy. Rubrik is now attempting to re-establish  GRS redundancy in the ${pairedRegionName} region.
Severity Status Audit Event
Info Success No

RCVGRSPrimaryFailoverReestablishmentSuccess

The Rubrik Cloud Vault '${locName}' has failed back to the former  primary region '${primaryRegionName}' and Rubrik has successfully  re-established the GRS redundancy. You can now enable '${locName}'  to resume archival.
Severity Status Audit Event
Info Success No

RCVGRSSecondaryFailoverReestablishmentSuccess

Successfully re-established GRS redundancy for Rubrik Cloud Vault  location '${locName}' between the primary region ${primaryRegionName}  and the secondary region ${secondaryRegionName}. You may initiate a  failback to the former primary region ${primaryRegionName} at any time  to resume archival to '${locName}'.
Severity Status Audit Event
Info Success No