Skip to content

Failover

app_failover


BlueprintFailoverCanceled

Canceled failover recovery plan '${name}' to '${location}'.

SeverityStatusAudit Event
InfoCanceledNo

BlueprintFailoverCanceling

Canceling failover for recovery plan '${name}' to '${location}'.

SeverityStatusAudit Event
InfoCancelingNo

BlueprintFailoverDataIngestionFailed

'${dataIngestionOperation}' process failed for recovery plan '${name}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

BlueprintFailoverDataIngestionStarted

Starting the '${dataIngestionOperation}' process for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverDataIngestionSucceed

'${dataIngestionOperation}' process succeeded for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverFailed

Failed to failover recovery plan '${name}' to '${location}': ${reason}.

SeverityStatusAudit Event
CriticalFailureNo

BlueprintFailoverFinalizeFailed

Final failover tasks failed for failover of recovery plan '${name}': ${reason}.

SeverityStatusAudit Event
CriticalFailureNo

BlueprintFailoverFinalizeStarted

Starting the final failover tasks for failover of recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverFinalizeSucceed

Final failover tasks succeeded for failover of recovery plan '${name}'.

SeverityStatusAudit Event
InfoSuccessNo

BlueprintFailoverIncrementalDataTransferFailed

Incremental data transfer process failed for recovery plan '${name}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

BlueprintFailoverIncrementalDataTransferStarted

Starting the incremental data transfer process for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverIncrementalDataTransferSucceed

Incremental data transfer process succeeded for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverPrepareDataFailed

Failover initialization process failed for recovery plan '${name}'. Reason: ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

BlueprintFailoverPrepareDataStarted

Starting the failover initialization process for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverPrepareDataSucceed

Failover initialization process succeeded for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverPrepareResourceFailed

Failover resource validation and initialization process failed for recovery plan '${name}'. Reason: ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

BlueprintFailoverPrepareResourceStarted

Starting the failover resource validation and initialization process for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverPrepareResourceSucceed

Failover resource validation and initialization process succeeded for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverProvisionFailed

Unable to set up the target Rubrik cluster '${targetClusterName}' for failover of recovery plan '${name}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

BlueprintFailoverProvisionStarted

Setting up the target Rubrik cluster '${targetClusterName}' for failover of recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverProvisionSucceed

Reconfiguration of virtual machines on target Rubrik cluster '${targetClusterName}' succeeded for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverProvisionSucceedWithNetworkReconfigureFailure

Reconfiguration of virtual machines on target Rubrik cluster '${targetClusterName}' failed for recovery plan '${name}'. Ignoring and continuing.

SeverityStatusAudit Event
WarningTaskSuccessNo

BlueprintFailoverScheduled

Scheduled job to failover recovery plan '${name}' to '${location}'.

SeverityStatusAudit Event
InfoQueuedNo

BlueprintFailoverStarted

Starting failover for recovery plan '${name}' to '${location}'. Abort and cleanup setting is ${undoOnFailure}. Skipping network reconfiguration errors is ${skipNetworkError}.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintFailoverSuccess

Successfully complete the failover for recovery plan '${name}' to '${location}'.

SeverityStatusAudit Event
InfoSuccessNo

BlueprintTakeOnDemandSnapshotFailed

On demand snapshot for recovery plan '${blueprintName}' failed.

SeverityStatusAudit Event
InfoFailureNo

BlueprintTakeOnDemandSnapshotStarted

Starting on demand snapshot for recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintTakeOnDemandSnapshotSucceed

On demand snapshot for recovery plan '${blueprintName}' successfully completed.

SeverityStatusAudit Event
InfoSuccessNo

BlueprintWaitOnDemandSnapshotFailed

Waiting on demand snapshot for recovery plan '${blueprintName}' failed.

SeverityStatusAudit Event
InfoFailureNo

BlueprintWaitOnDemandSnapshotStarted

Waiting for on demand snapshot for recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

BlueprintWaitOnDemandSnapshotSucceed

Waiting on demand snapshot for recovery plan '${blueprintName}' succeeded.

SeverityStatusAudit Event
InfoSuccessNo

CleanupFailoverCanceled

Canceled the failover cleanup for recovery plan '${name}'.

SeverityStatusAudit Event
InfoCanceledNo

CleanupFailoverCanceling

Canceling the failover cleanup for recovery plan '${name}'.

SeverityStatusAudit Event
InfoCancelingNo

CleanupFailoverFailed

Failed to cleanup failover for recovery plan '${name}' with ${reason}.

SeverityStatusAudit Event
CriticalFailureNo

CleanupFailoverStarted

Started failover cleanup for recovery plan '${name}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

CleanupFailoverSuccess

Successfully completed the failover cleanup for recovery plan '${name}'.

SeverityStatusAudit Event
InfoFailureNo

CleanupFailoverTaskFailed

Failed to cleanup recovery plan ${name}: ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

CleanupFailoverTaskFailedWithUserComment

Failed to cleanup recovery plan '${name}'. ${comment} : ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

CleanupFailoverTaskStarted

Started cleanup for recovery plan ${name}.

SeverityStatusAudit Event
InfoRunningNo

CleanupFailoverTaskSucceed

Successfully completed the cleanup for recovery plan ${name}.

SeverityStatusAudit Event
InfoTaskSuccessNo

CleanupFailoverTaskSucceedWithUserComment

Successfully completed the cleanup for recovery plan '${name}'. ${comment}.

SeverityStatusAudit Event
InfoTaskSuccessNo

FailbackCloudMachineShutdownFailed

Failed to shut down ${instanceType} ${instanceName}.

SeverityStatusAudit Event
InfoTaskFailureNo

FailbackCloudMachineShutdownSucceed

Shut down ${instanceType} ${instanceName}.

SeverityStatusAudit Event
InfoTaskSuccessNo

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.

SeverityStatusAudit Event
WarningTaskFailureNo

FailbackCloudMachineShutdownTaskStarted

Started the shutdown process for recovery plan child ${instanceType}.

SeverityStatusAudit Event
InfoRunningNo

FailbackCloudMachineShutdownTaskSucceed

Shut down all recovery plan child ${instanceType}.

SeverityStatusAudit Event
InfoTaskSuccessNo

FailbackCreateOnDemandBlueprintSnapshotTaskFailed

Failed to create a snapshot for the current state of the recovery plan '${blueprintName}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

FailbackCreateOnDemandBlueprintSnapshotTaskStarted

Started taking a snapshot for the current state of the recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoRunningNo

FailbackCreateOnDemandBlueprintSnapshotTaskSucceed

Created a snapshot for the current state of the recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

FailbackDeprecatePrimaryAppTaskFailed

Failed to deprecate the primary recovery plan '${blueprintName}': ${reason}.

SeverityStatusAudit Event
WarningTaskFailureNo

FailbackReprotectTaskFailed

Failed to reprotect the recovery plan '${blueprintName}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

FailbackReprotectTaskStarted

Reprotecting the recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoRunningNo

FailbackReprotectTaskSucceeded

Reprotected the recovery plan '${blueprintName}' with SLA '${slaName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

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.

SeverityStatusAudit Event
CriticalTaskFailureNo

FailbackSyncRecoverySpecTaskStarted

Started syncing the latest recovery spec to the target cluster.

SeverityStatusAudit Event
InfoRunningNo

FailbackSyncRecoverySpecTaskSucceed

Successfully synced the latest recovery spec to the target cluster.

SeverityStatusAudit Event
InfoTaskSuccessNo

FailoverAssignClonedSLAFailed

Failed to assign the cloned SLA to the newly created recovery plan: ${reason}.

SeverityStatusAudit Event
WarningTaskFailureNo

FailoverAssignSLAFailed

Failed to assign the SLA '${slaName}' to the newly created recovery plan: ${reason}.

SeverityStatusAudit Event
WarningTaskFailureNo

FailoverDeprecatePrimaryAppTaskFailed

Failed to deprecate the primary recovery plan '${blueprintName}': ${reason}, the ${instanceType} should be shutdown manually.

SeverityStatusAudit Event
WarningTaskFailureNo

FailoverDeprecatePrimaryAppTaskStarted

Started to deprecate the primary recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoRunningNo

FailoverDeprecatePrimaryAppTaskSucceed

Successfully deprecated the primary recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

FailoverSLANotFound

SLA not found when assigning SLA to the newly created recovery plan.

SeverityStatusAudit Event
WarningTaskFailureNo

SyncFailbackTaskFailed

Failover failed on cluster '${clusterName}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

SyncFailbackTaskSucceed

Failover succeeded on cluster '${clusterName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

TriggerFailbackTaskFailed

Failed to trigger failover job for recovery plan to the point in time: ${recoveryPoint} on cluster '${clusterName}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

TriggerFailbackTaskFailedWithTimeRange

Failed to trigger failover job for recovery plan to the point in time: range from ${startTime} to ${endTime} on cluster '${clusterName}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

TriggerFailbackTaskStarted

Failover job for recovery plan to the point in time: ${recoveryPoint} triggered on cluster '${clusterName}'.

SeverityStatusAudit Event
InfoRunningNo

TriggerFailbackTaskStartedWithTimeRange

Failover job for recovery plan to the point in time: range from ${startTime} to ${endTime} triggered on cluster '${clusterName}'.

SeverityStatusAudit Event
InfoRunningNo

TriggerFailbackTaskSucceed

Triggered a failover job for recovery plan to the point in time: ${recoveryPoint} on cluster '${clusterName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

TriggerFailbackTaskSucceedWithTimeRange

Triggered a failover job for recovery plan to the point in time: range from ${startTime} to ${endTime}, on cluster '${clusterName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

ValidateRecoverySpecTaskFailed

Failed to validate the recovery spec of recovery plan '${blueprintName}' on cluster '${clusterName}': ${reason}.

SeverityStatusAudit Event
CriticalTaskFailureNo

ValidateRecoverySpecTaskStarted

The recovery spec of recovery plan '${blueprintName}' is being validated on cluster '${clusterName}'.

SeverityStatusAudit Event
InfoRunningNo

ValidateRecoverySpecTaskSucceed

Validated the recovery spec of recovery plan '${blueprintName}' on cluster '${clusterName}'.

SeverityStatusAudit Event
InfoTaskSuccessNo

appflows


BlueprintFailoverCleanupStart

${userEmail} triggered cleanup job for recovery plan '${blueprintName}'.

SeverityStatusAudit Event
InfoSuccessYes

BlueprintFailoverStart

${userEmail} triggered failover for recovery plan '${blueprintName}' to ${targetSite}.

SeverityStatusAudit Event
InfoSuccessYes

BlueprintTestFailoverStart

${userEmail} triggered test failover for recovery plan '${blueprintName}' to ${targetSite}.

SeverityStatusAudit Event
InfoSuccessYes

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.

SeverityStatusAudit Event
InfoSuccessNo

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.

SeverityStatusAudit Event
InfoSuccessNo

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}'.

SeverityStatusAudit Event
InfoSuccessNo