Rubrik CDM Version 6.0 Events Guide (Rev. A1)

Rubrik CDM Events Guide
Version 6.0
755-0178-01 Rev A1
Rubrik Headquarters: Palo Alto, California 94304

1-844-4RUBRIK www.rubrik.com
Legal Notices
Copyright and trademarks

Copyright
Copyright © 2021 Rubrik Inc.

All rights reserved. This document may be used free of charge. Selling without prior written consent is
prohibited. Obtain permission before redistributing. In all cases, this copyright notice and disclaimer must
remain intact.
THE CONTENTS OF THIS DOCUMENT ARE PROVIDED "AS IS," AND COPYRIGHT HOLDERS MAKE NO
REPRESENTATIONS OR WARRANTIES, EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO,
WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT,
OR TITLE; THAT THE CONTENTS OF THE DOCUMENT ARE SUITABLE FOR ANY PURPOSE; THAT THE
IMPLEMENTATION OF SUCH CONTENTS WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS,
TRADEMARKS OR OTHER RIGHTS.
COPYRIGHT HOLDERS WILL NOT BE LIABLE FOR ANY DIRECT, INDIRECT, SPECIAL OR CONSEQUENTIAL
DAMAGES ARISING OUT OF ANY USE OF THE DOCUMENT OR THE PERFORMANCE OR IMPLEMENTATION
OF THE CONTENTS THEREOF.
Trademarks
Registered in the U.S. Trademark Office

Rubrik, the Rubrik graphic, and Datos IO are registered trademarks of Rubrik, Inc. in the U.S. and other
countries. Additionally, Rubrik, Inc. holds common law trademark rights in Rubrik Polaris, Polaris GPS,
Polaris Radar, Polaris Sonar, Rubrik Envision, Rubrik Edge, and Mosaic in the U.S. and/or other countries.
All other trademarks are the property of their respective owners.
Legal Notices
Certain products and features, including the Rubrik-hosted mode of Polaris for Microsoft 365 Protection,
are subject to additional product-specific terms available at https://www.rubrik.com/en/legal.
By using the Rubrik Polaris Sonar application, you understand and acknowledge that Rubrik Polaris Sonar’s
pre-existing Policies and Analyzers contain general suggestions for data elements and formats based on
common data sets and formats. The suggested data elements and formats in Rubrik Polaris Sonar are not
intended to be a comprehensive or exhaustive list of data elements and formats regulated by the GDPR,
CCPA or any other applicable laws and regulations. We also do not guarantee that your Rubrik Polaris
Sonar search results will include every instance of each data element and format within your data set. We
Copyright and trademarks 07/20/2021 | ii

strongly recommend that you consult legal counsel for specific advice regarding compliance with applicable
laws and regulations.
Rubrik Polaris Sonar is designed to assist customers with identifying certain data elements and formats and
should not be solely relied upon to identify all data elements and formats of a certain type for any purpose,
including legal or compliance.
Use of the Polaris Management Console software is subject to additional product-specific terms available at
https://www.rubrik.com/en/legal.
Copyright and trademarks 07/20/2021 | iii

Preface
Welcome to Rubrik. We appreciate your interest in our products.
Rubrik is continually working to improve its products and regularly releases revisions and new versions.
Some information provided by this guide may not apply to a particular revision or version of a product.
Review the release notes for the product to see the most up-to-date information about that product.
Revision history
Revision Date Description
Rev. A0 June 2021 Directed Availability release of Rubrik CDM version 6.0.
Rev. A1 July 2021 General Availability release of Rubrik CDM version 6.0.
Support
Use one of the following methods to contact Rubrik Support.
Web Rubrik Support Portal

Phone See Get In Touch for contact options.
Email support@rubrik.com
Related documentation
Rubrik provides documentation that covers a broad range of related concepts, tasks, and reference
information.
• Rubrik Polaris User Guide
• Rubrik Polaris Radar Quick Start Guide
• Rubrik CDM Release Notes
• Rubrik CDM User Guide
• Rubrik CDM Install and Upgrade Guide
• Rubrik CDM Security Guide
• Rubrik CDM Cloud Cluster Setup Guide
• Rubrik CDM Hardware Guide
• Rubrik CDM CLI Guide
• Rubrik CDM Events Guide
Preface 07/20/2021 | iv
• Rubrik Edge Install and Upgrade Guide
• Rubrik Virtual Cluster Install Guide
• Rubrik Compatibility Matrix
Comments and suggestions

We welcome your comments and suggestions about our products and our product documentation.
Products
To provide comments and suggestions about our products contact Rubrik Support, as described in Support.
Product documentation
To provide comments and suggestions about the product documentation, please send your message by
email to: techpubs@rubrik.com.
Please include the following information about the product documentation to help us to find the content
that is the subject or your comments:
• Full title
• Part number
• Revision
• Relevant pages
Rubrik Build
Rubrik hosts community-based tools through the Rubrik Build program and associated GitHub repositories
for community-supplied tools.
Rubrik Build is an open source program that provides access to a growing community of enthusiasts and
experts across a number of languages and tools. Rubrik Build is used to create and improve projects that
simplify monitoring, testing, development, and automated workflows for Rubrik product deployments.
Rubrik Build includes the following resources:
• Software Development Kits
• Tooling Integrations
• Use Cases
• Community Projects
• Rubrik REST API documentation
Important: USE AT YOUR OWN RISK. Rubrik does not officially support the community tools. Carefully
investigate a community tool before using it. Always test a community tool on non-production data before
using the tool with production data.
Preface 07/20/2021 | v
Contents
Overview........................................................................................................................................... 7
Severity levels........................................................................................................................... 7
Configuring event email settings.................................................................................................7
Administrator email alerts.................................................................................................8
Event types............................................................................................................................... 9
Event descriptions..........................................................................................................................11
Events A to D..........................................................................................................................11
Events E to M......................................................................................................................... 15
Events N to R......................................................................................................................... 23
Events S to Z.......................................................................................................................... 32
Troubleshooting information.........................................................................................................38
Chapter 1
Overview
Overview
Rubrik CDM provides many events and notifications, ranging from informational to critical.
Events provide information to users at regular intervals concerning specific operations that have occurred
on Rubrik CDM. Events can appear in the Activity log, Syslog, and SNMP. Rubrik CDM classifies events by
type, for example configuration, hardware, or replication.
Notifications provide information for a subset of events and can be communicated through additional
channesl. For example, notifications can be sent to specific email addresses or to a Syslog server
depending on the Notification Settings. An email recipient list can be configured so that notifications are
sent only for specified event types. The email recipient list can also be configured to send notifications to a
Syslog server.
Severity levels
Rubrik CDM includes different severity levels for events.
Severity level Description

Informational Events that do not require any immediate action.
Rubrik CDM typically uses informational events
to inform users about processes occurring in the
system and to facilitate the creation of an audit
trail.
Warning Events about abnormal processes that have
occurred which do not directly cause failures.
Critical Events that require immediate attention. Critical
events are usually caused by failures.
Configuring event email settings

Specify the types of events and the recipients for event notifications that are sent through email.
Procedure
1. Log in to the Rubrik CDM web UI.
2. Click the gear icon.
3. Click Notification Settings.
The Notification Settings page opens, and the Email Settings tab is selected by default.
4. Select the Notifications tab.
5. Click the + icon.
The Add Notification Setting wizard appears, set to the Event Types step.
Overview 07/20/2021 | 7
6. To send notifications for selective event types, select the event types and click Next.
The wizard advances to the Severity step.
7. Optional: To send notifications for all event types, click Event Types and then click Next.
8. Select severity types and click Next.
The Rubrik cluster sends notifications only for the selected severities. Click Severity to select all
severity levels.
The wizard advances to the Object Types step.
9. Select object types and click Next.
The Rubrik cluster sends notifications only for the selected object types. Click Object Types to select
all object types.
The wizard advances to the Send To step.
10. Optional: In the left-pane of the dialog box, click Emails and specify a list of recipient email
addresses.
Use commas to separate multiple email addresses. Select Send to all Administrators to send
notifications to all accounts that are part of the administrators group.
11. Optional: In the left-pane of the dialog box click Syslog > Send to syslog server.
12. Click Finish.
Result
The Rubrik cluster saves the event email settings.
Administrator email alerts

A Rubrik cluster sends email alerts to cluster users with the Administrator privilege level when specific
conditions occur. Each Rubrik cluster has individual settings for event notifications.
This table lists alert conditions that generate an email notification to all administrators on the Rubrik
cluster. The email messages include any recommended actions. To respond to an email alert, follow the
instructions in the email message.
Condition Description
Disk locked The cluster is unable to access an encrypted disk.
To clear this issue, reboot the node or check the
integrity of an attached key management system.
Disk lost A disk was removed from the node without
following the proper procedure for disk removal, or
that the disk has failed.
Unformatted disk present The Rubrik cluster has detected a disk that is not
part of the cluster. Add the disk from the Rubrik
CDM UI or API to make the new storage available.
Disk health notification A disk in the Rubrik cluster is in an unhealthy state,
such as being flagged as read-only.
Network interface down A node’s primary or backup network interfaces
are disconnected from the network. Review the
network, switch, and physical cabling configurations
to resolve this condition.
Node up The cluster has detected a node rejoining the
cluster.
Overview 07/20/2021 | 8
Condition Description
Node down A node is unavailable. The Rubrik cluster attempts
to reacquire the node for 2 hours before issuing this
alert.
Power supply missing One of the redundant power supplies in a Brik
appliance chassis is unavailable.
Failed to add node The cluster is unable to add a node to the cluster.
Use the IPMI interface to verify that the node
is powered on. If physical access to the node is
available, use the hardware power button to power
on the node.
Successfully added node A node was discovered and added to the cluster.
Automatic node removal failed The cluster failed to automatically remove a dead
node from the cluster.
Automatic node removal succeeded A node was automatically removed from the cluster.
Node recommissioned A node has rejoined the cluster after
decommissioning.
Node failed to recommission A formerly decommissioned node has failed to
rejoin the cluster.
Failed to remove node The Rubrik cluster is unable to remove a node.
Removed node The Rubrik cluster has successfully removed a
node.
Backup failure The Rubrik cluster has attempted, but failed, three
times to perform backup operations.
System storage threshold reached Total storage used in the cluster is now in excess of
the set threshold.
Failed to create MSSQL log The backup for the MS SQL log failed.
Event types
Rubrik cluster events are grouped by types.
Type Description
Archive Archive-related events. For example, events
concerning archival operations like snapshot
upload, consolidation, tiering, throttling and
associated statuses (failed/successful/ running, and
so on) across different object types.
Backup Backup and log backup related events, including
their statuses (failed, successful, running, and so
on) across different object types.
Classification Events related to data classification and
governance.
Overview 07/20/2021 | 9
Type Description
Configuration Configuration settings related to clusters, keys,
network, LDAP, certificates, subnets, and web
servers, Also includes delete and refresh related
events concerning different object types.
Diagnostic Network interface and disks events, including their
status (Up, Down, Locked, Formatted, Unformatted,
and so on).
Discovery Events related to the Oracle database discovery and
real application clusters.
Failover/ Test Failover Events related to failover and test failover for
appflows.
Hardware Events related to components, including chassis,
power supplies, bios, and so on.
Index Indexing operation events.
Instantiation and Conversion Events related to the instantiation processes,
including launching, cloud conversion, bolt
operations, creating AWS images, image readiness.
Includes the event status (for example, launch,
delete, success, started, cancelled, cancelling, and
so on).
Legal Hold Legal hold activity events, including placing a
resource, releasing a resource, and downloading
with checksum.
Recovery Recovery-related events such as file download,
file restore, instant recovery, live mount, export,
snapshot download, and so on. Also includes log
restore related events and their statuses (failed,
successful, running, and so on) across different
object types.
Replication Replication and log replication related events and
their statuses (failed, successful, running, and so
on) across different object types.
System Events related to managed volume capacity and
floating IP failover.
Storage Events related to system storage thresholds.
Upgrade Events related to upgrades and Rubrik cluster
upgrade status.
User Activity Events related to user activity and audits, including
logging in and out of the Rubrik cluster, assigning
SLA's, renaming, registration, on-demand activity,
adding and deleting objects, and so on.
Overview 07/20/2021 | 10
Chapter 2
Event descriptions
Event descriptions
Rubrik CDM information about individual events

Information about an event can be found by searching for the event based on the first letter of the event
message. Each event listing provides the event, the detailed event message, and the event type, status,
severity, and SNMP OID.
The SNMP OID shown with an event is the identifying extension for the message. For example, the OID
1.3.6.1.4.1.49929.2.2.4 is shown as 2.2.4. The static value 1.3.6.1.4.1.49929. is omitted.
Related reference
Events A to D
Event descriptions from A to D.
Events E to M
Event descriptions from E to M.
Events N to R
Event descriptions from N to R.
Events S to Z
Event descriptions from S to Z.
Events A to D
Event descriptions from A to D.
Notification Event message Type Status Severity SNMP OID

A disk on a node The disk on node ${nodeId} with Config Failure Critical 2.2.4
could not be marked mountpoint '${mountpoint}' could
removed not be marked removed. Please
contact Rubrik Support.
A disk on a node A disk on node ${nodeId} with Config Failure Critical 2.2.6
could not be set up mountpoint '${mountpoint}' could
not be set up. Please contact
Rubrik Support.
A disk on a node A disk device of type ${diskType} Diagnostic Warning Warning 2.2.9
failed health checks on node ${nodeId} failed health
checks
A disk on a node is Disk ${diskDeviceId} type Diagnostic Warning Warning 2.2.2
unavailable ${diskType} node ${nodeId}
cluster ${clusterName} is
unavailable
A disk on a node was Recovered ${diskType} disk Diagnostic Success Info 2.2.3
marked recovered device on node ${nodeId}
Event descriptions 07/20/2021 | 11

A disk on a node was The disk on node ${nodeId} with Config Success Info 2.2.5
successfully marked mountpoint '${mountpoint}' was
removed successfully marked removed.
A disk on a node was A disk on node ${nodeId} with Config Success Info 2.2.7
successfully set up mountpoint '${mountpoint}' was
successfully set up.
A task launched by A periodic task has failed on node Diagnostic Failure Critical 2.3.16
the node has failed ${nodeId}: ${message}
Troubleshooting information
includes a link to a Rubrik
Support KB article that resolves
this issue.
Added node(s) Added ${numNodes} node(s) Config Success Info 2.3.2

successfully
All backup windows All backup windows have expired Config Warning Warning
have expired
Archival location is Archival location Config Failure Critical
out of space. '${locationName}' is out of space.
Archival location Archival location Config Warning Warning
space usage high '${locationName}' is using
threshold reached. ${spaceUsagePercent}%
of storage capacity.
Remaining available space is
${availableSpace}.
space usage low '${locationName}' is using
${availableSpace}.
space usage medium '${locationName}' is using
${availableSpace}.
Automatically Automatically removed node Config Success Info 2.3.3
removed node to ${nodeId}
preserve the health of
the cluster
Backup of fileset has Backup of fileset Backup Warning Warning
no files '${protected_objectName}' on
'${source}' has no files. Check to
make sure that permissions are
correct for the host and that files
exist in the fileset path.

Backup of HDFS has Backup of '${hdfsName}' on Backup Warning Warning
no files '${source}' has no files. Check to
make sure that permissions are
correct for the host and that files
exist in the path.
Backup of Oracle logs Failed Backup Failure Critical
failed ${onDemandBackupString}log
backup of
${protected_objectType}
'${protected_objectName}'.
Reason: ${reason}.
Base snapshot no Could not find base snapshot Backup Warning Warning
longer exists on '${snapshotNaturalId}' for virtual
Nutanix cluster machine '${vmName}' on Nutanix
cluster, will proceed by ingesting
full
Base snapshot Could not find base Backup Warning Warning
volume no longer snapshot volume
exists on Storage '${baseSnapshotVolumeName}'
Array for storage array volume group
'${protected_objectName}' on
storage array. Performing a full
backup.
BIOS recovered BIOS recovered on node Hardware Success Info 2.1.11
${nodeId}
Change block tracking Change block tracking Recovery Warning Warning
has been reset has been reset for
${protected_objectName}.
Chassis recovered Chassis recovered on node Hardware Success Info 2.1.9
${nodeId}
Check power supply Check power supply AC input on Hardware Failure Critical 2.1.13
node ${nodeId}: ${message}
CIFS endpoint mount Failed to mount CIFS Config Failure Critical
failure target ${remoteTarget} at
${mountPath}
CIFS I/O operations ${cifsIoOperationErrorMsg} Backup Failure Critical
failure
Clock on machine is Node ${nodeId} has failed ntp Hardware Warning Warning 2.1.3
out of sync checks. Restarting ntp service on
the node.
Connected to archival Successfully connected to Config Success Info
location ${userVisibleLocationType}
archival location
'${locationName}'.

Connecting as reader Cluster is already connected to Recovery Failure Critical
to an archival location '${existingLocationName}' and
cannot connect as a reader to
the '${locationType}' archival
location.
Connecting as reader Cluster is already connected to Recovery Failure Critical
to an archival location '${existingLocationName}' and
location.
Cluster already owns Recovery Failure Critical
'${existingLocationName}' and
location.
Failed to add reader location Recovery Failure Critical
'${locationName}'. ${reason}
Successfully added reader Recovery Success Info
location '${locationName}'.
Owner cluster Recovery Failure Critical
'${ownerClusterUuid}' is used
in replication. Connecting as a
reader to the location owned by
replication source/target is an
unsupported configuration.
Created managed Successful creation of managed Config Success Info
volume volume '${mvName}'
Creating MSSQL log Failed Backup Failure Critical
failed ${onDemandBackupString}backup
of the transaction log
for SQL Server database
'${protected_objectName}' from
'${locationName}'. Reason:
${reason}
this issue.
Creating snapshot Failed Backup Failure Critical 4.0.1

failed ${onDemandBackupString}backup
of ${protected_objectType}
Failed
${onDemandBackupString}backup
of ${protected_objectType}
'${protected_objectName}' from
'${locationName}'.

Decommission Node decommission for node(s) Config Warning Warning 2.3.19
node(s) has started ${nodeIds} has started.
Decommission Node decommissioning for Config Warning Warning 2.3.18
node(s) in progress ${nodeIds} is in progress.
${msg}
Decommissioned Successfully completed node Config Success Info
node successfully decommission for: ${nodeIds}.
Decommissioned nodes can safely
be removed from the Rubrik
cluster.
Deleted archival Failed to delete archival location Config Failure Critical
location '${name}'
Successfully deleted archival Config Success Info
location '${name}'
DIMM recovered DIMM ${dimmId} recovered on Hardware Success Info 2.1.10
node ${nodeId}
Disconnected archival Failed to disconnect archival Config Failure Critical
location location '${name}'
Successfully disconnected archival Config Success Info
location '${name}'
Downloading unified Failed to generate script Config Failure Critical
view script for for export of snapshot
managed volume '${snapshotId}' taken
at '${snapshotDate}' for
the managed volume
'${managedVolumeName}'.
Reason: ${reason}.
Successfully generated Config Success Info
script for export of snapshot
'${snapshotId}' taken
at '${snapshotDate}' for
the managed volume
'${managedVolumeName}'.
Related Concepts
Event descriptions
Events E to M
Event descriptions from E to M.

Errors with BIOS BIOS errors detected on node Hardware Failure Critical 2.1.6
${nodeId}: ${message}

Errors with DIMM DIMM errors detected on node Hardware Failure Critical 2.1.5
Exported managed Failed to export snapshot Recovery Failure Critical
volume snapshot '${snapshotId}' of managed
volume '${mvName}' taken at
'${snapshotDate}'. Reason:
'${reason}'
Successful export of snapshot Recovery Success Info
'${snapshotId}' of managed
volume '${mvName}' taken at
'${snapshotDate}'.
Exporting database Failed to export database Recovery Failure Critical
'${sourceDb}' at ${recoveryPoint}
to '${destDb}': ${reason}
Exported SQL Server database Recovery Success Info
'${sourceDb}' at ${recoveryPoint}
to '${destDb}'
Exporting fileset Failed to export '${sourceDir}' Recovery Failure Critical
from '${source}' to
'${destination}' based
on snapshot taken at
'${snapshotDate}'.
Successful export of Recovery Success Critical
'${sourceDir}' from '${source}'
to '${destination}' based
'${snapshotDate}' Successfully
exported ${logicalSize} of data in
${numFiles} files, ${numLinks}
links, ${numHardlinks} hard
links, and ${numDirectories}
directories. Failed to export
${numErrorFiles} files,
${numErrorHardlinks} hard links
and ${numErrorDirectories}
directories.
Exporting HDFS Failed to export '${sourceDir}' Recovery Failure Critical
from '${source}' to
'${destination}' based
'${snapshotDate}'
Successful export of Recovery Success Info
'${sourceDir}' from '${source}'
'${snapshotDate}' Successfully
exported ${logicalSize} of
data in ${numFiles} files, and
${numDirectories} directories.
Failed to export ${numErrorFiles}

files and ${numErrorDirectories}
directories
Exporting Hyper-V VM Export of snapshot Recovery Failure Critical
snapshot '${snapshotId}' from
'${vmName}' failed.
Export of snapshot Recovery Success Info
'${snapshotId}' from
'${vmName}' succeeded.
Exporting Nutanix VM Export of snapshot Recovery Failure Critical
snapshot '${snapshotId}' from
'${vmName}' failed. Reason:
${reason}
'${vmName}' succeeded
Exporting Oracle The ${exportType} of Recovery Failure Critical
database ${protected_objectType}
'${protected_objectName}' to
'${recoveryPoint}' on '${target}'
failed.
Successfully ${exportType} Recovery Success Info
${recoveryPoint} on ${target}.
Exporting Storage Export of snapshot Recovery Failure Critical
Array Volume Group '${snapshotId}' from
snapshot ${protected_objectType}
${reason}
Exporting virtual Export of snapshot Recovery Failure Critical
machine snapshot '${snapshotId}' from
${reason}
Failed to add node(s) Failed to add ${numNodes} Config Failure Critical 2.3.1
nodes due to - ${msg}

Failed to Automatic removal of node Config Failure Critical 2.3.4
automatically remove ${nodeId} failed due to - ${msg}
node to preserve the
health of the cluster
Failed to connect to Failed to connect to Config Failure Critical
archival location ${userVisibleLocationType}
archival location
'${locationName}'. ${reason}
Failed to consolidate Archival consolidation Archive Failure Critical
snapshots on archive failed on archival location
'${locationName}' for
'${reason}'
this issue.
Failed to create Failed to create managed volume Config Failure Critical

managed volume '${mvName}'. '${reason}'
Failed to Unable to complete node Config Failure Critical 2.3.6
decommission node decommission for ${nodeIds}
due to - ${msg}. Please contact
Rubrik Support.
Failed to delete Failed to delete ${numFiles} Backup Warning Warning
backed up archived archived log files for
log files from host ${protected_objectType}
These files have been successfully
backed up but could not be
deleted from the source:
${filenames}.
Failed to disconnect Failed to disconnect volume Backup Warning Warning
volume from host. '${volumeName}' from
host '${hostname}' for
storage array volume group
Failed to discover Oracle databases with unique Discovery Failure Critical
Oracle databases. names '${dbUniqueNames}' on
host '${hostName}' were not
discovered.
Failed to end Failed to end snapshot for Backup Failure Critical
managed volume managed volume ${mvName}
snapshot ID: ${mvId} Reason: ${reason}.
Mishandling snapshot end failures
can lead to data corruption.

Failed to export Failure while exporting tablespace Recovery Failure Critical
Oracle tablespace '${tablespaceName}' of
${source} to ${recoveryPoint}
Reason: ${reason}.
Failed to Node ${nodeId} failed to exit Config Failure Critical 2.3.12
recommission node maintenance mode due to -
${msg}
Failed to remove node Removal of node ${nodeId} Config Failure Critical
failed. Reason: '${msg}'
Failed to retrieve Failed to retrieve KMIP Config Failure Critical
KMIP key key '${keyName}' from
${serverAddress}. Please check
KMIP settings to ensure data can
be decrypted.
Failed to upload Failed to upload logs for Archive Failure Critical
Oracle logs ${protected_objectType}
'${locationName}'. Reason:
${reason}.
Failed to verify data Failed to verify encryption keys Config Failure Critical
at rest encryption for node ${nodeId}. Please
keys contact Rubrik Support.
this issue.
Failed to verify KMIP Failed to verify KMIP connectivity Config Failure Critical
connectivity to ${serverAddress}. Please
check KMIP settings to ensure
data can be decrypted.
Instantly recovering Failed to recover Recovery Failure Critical
Hyper-V VM snapshot ${protected_objectType}
'${protected_objectName}'
Recovered Recovery Success Info
Oracle DB ${protected_objectType}
'${sourceDatabaseName}' to
${recoveryPoint}.
${recoveryPoint}.

vCD vApp snapshot ${protected_objectType}
virtual machine ${protected_objectType}
snapshot '${protected_objectName}'
Insufficient Insufficient available Archive Warning Warning
bandwidth for archival ${bandwidthType} bandwidth for
consolidation archival consolidation on archival
location '${name}'. Disable
consolidation on that location or
provide additional bandwidth.
LDAP bind user LDAP (${dynamicDnsName}) still Config Warning Warning
credentials are uses the deprecated computer
unknown. user credentials. Open Settings >
Users > LDAP Servers to provide
the bind user credentials on the
Rubrik cluster.
LDAP service is Periodic health check succeeded Config Success Info
healthy. for LDAP (${name}).
LDAP service is LDAP (${name}) cannot be Config Failure Critical
unhealthy. accessed! (Error: ${exception}).
Fix LDAP integration to allow the
Rubrik cluster to send important
failure notifications. Open
Settings > Users > LDAP Servers
to correct the LDAP configuration
on the Rubrik cluster.
this issue.
Locked disk found on The disk device ${diskDeviceId} Diagnostic Warning Warning 2.2.1
a node on node ${nodeId} is locked

Log backup retention The specified retention Backup Warning Warning
greater than snapshot period for log backups of
replication retention. ${dbNameWithLocation}
(${logRetentionHours}
hours) in the replication
from '${sourceClusterName}'
to '${targetClusterName}'
exceeds the maximum snapshot
retention of the SLA Domain
('${slaDomainName}') assigned
to the database, which is
${slaDomainRetentionHours}
hours. Log backup retention
cannot exceed the maximum
snapshot retention.
Log backup retention The specified retention Backup Warning Warning
greater than snapshot period for log backups of
retention ${dbNameWithLocation}
(${logRetentionHours} hours)
exceeds the maximum snapshot
retention of the SLA Domain
('${slaDomainName}') assigned
to the database, which is
${slaDomainRetentionHours}
hours. Log backup retention
cannot exceed the maximum
snapshot retention.
Log shipping The log shipping configuration Recovery Warning Warning
configuration is between primary database
broken '${primaryDb}' and secondary
database '${secondaryDb}' is
broken. A reseed is required.
Reason: ${reason}
Log shipping Failed to ship logs from SQL Recovery Failure Critical
configuration is stale Server primary database
'${primaryDb}' to secondary
database '${secondaryDb}'.
Reason: ${reason}
Making up for log A makeup snapshot to Backup Warning Warning
chain breakage correct a transaction log
chain break for database
'${dbNameWithlocation}' cannot
be scheduled because transaction
log chain makeup limit was
reached.
A makeup snapshot has Backup Running Info
been scheduled for database
'${dbName}' because a break
in the transaction log chain was
detected.

Managed volume Managed volume System Warning Warning
capacity '${managedVolumeName}'
channel '${channelId}' at node
'${nodeId}' has exceeded
${percent}% of its capacity. Used
size ${usedSize} out of total size
${totalSize} have been used
Managed volume System Warning Warning
'${managedVolumeName}' at
node '${nodeId}' has exceeded
${percent}% of its capacity. Used
size ${usedSize} out of total size
${totalSize} have been used
Mounting database Failed to mount Recovery Failure Critical
'${objectName}'. Reason:
${reason}
Mounted Recovery Success Info
'${objectName}'
Failed to Live Mount Recovery Failure Critical
${recoveryPoint} on location
${locationName}.
Completed Live Mount of Recovery Success Info
'${sourceDatabaseName}'
to ${recoveryPoint} as
${mountedDatabaseName} on
location ${locationName}.
Mounting Hyper-V VM Failed to mount Recovery Failure Critical
snapshot ${protected_objectType}
${objectName}. Reason:
${reason}
'${objectName}'
Mounting virtual Failed to mount virtual disk(s) to Recovery Failure Critical
machine snapshot '${objectName}'
Mounted virtual disk(s) to Recovery Success Info
'${objectName}'
Failed to mount Recovery Failure Critical
'${objectName}'

'${objectName}'
Related Concepts
Event descriptions
Events N to R
Event descriptions from N to R.

Network interface Cannot connect with network Hardware Warning Warning 2.1.1
down on a port interface ${interface} on node
${nodeId}
Network interface ${interface} on Diagnostic Failure Critical
node ${nodeId} not connected
NFS endpoint mount Failed to mount NFS Config Failure Critical
failure target ${remoteTarget} at
${mountPath}
NFS I/O operations ${nfsIoOperationErrorMsg} Backup Failure Critical
failure
No applicable guest No working credential found for Recovery Failure Critical
credentials found for virtual machine ${vmName}.
virtual machines
The guest OS on VM '${vmname}' Backup Warning Warning
is not running
Unable to get guest OS status on Backup Warning Warning
VM '${vmname}'
Guest OS account '${userName}' Backup Warning Warning
does not provide local
administrator privileges. This may
be caused by the 'Admin Approval
Mode' being enabled on the guest
OS. Cannot take a VSS consistent
snapshot. Instead, taking a crash
consistent snapshot
Cannot find a guest credential Backup Warning Warning
that permits a VSS consistent
snapshot on this virtual machine.
Taking a crash consistent
snapshot instead
Unable to verify guest credential Recovery Failure Critical
of '${username}'. It maybe an
invalid Guest OS credential.

Node detected Node ${nodeId} detected as Config Failure Critical 2.3.5
as automatically automatically removed
removed
Node is down, Node ${downNodeId} Diagnostic Failure Critical 2.3.9
recovery failed detected as BAD from node
${sourceNodeId}. Reason:
'${reason}'. Suggested remedial
action: '${remedy}'.
Node is down, Node ${downNodeId} Diagnostic Warning Warning 2.3.8
trying to recover detected as down from node
automatically ${sourceNodeId}. ${reason}.
${remedy}.
Node is up OK status for node Diagnostic Success Info 2.3.10
${upNodeId} detected by node
${sourceNodeId}.
Node replacement Replace node ${nodeId}: Hardware Failure Critical 2.1.7
required because of ${message}
hardware issues
Notification for Certificate '${certName}' will Config Warning Warning
impending certificate expire within ${numDays} days.
expiration Once you update the certificate,
users cannot connect to service
providers until you reconfigure
each service using that certificate,
to work with the new certificate.
Notification for not Did not schedule a conversion job Conversion Failure Critical
scheduling conversion for '${protected_objectName}'
job because of the following reasons:
${imageConversionFailures}${instantiateFailures}
Notification for storm Unable to find ${stormType} Config Failure Critical
image not present on image ${imageName} at
cloud location ${locationName} on
${locationType} ${region} region.
Please contact support.
Notification for storm Unable to confirm status for StormResource
Failure Critical
resource leakage on ${environment}. Termination
cloud of instances may not have
completed successfully. Please
delete them manually.
Notification on Could not enable CBT for Backup Warning Warning
enabling CBT failure '${vmname}' so a full snapshot
for vmware backup must be taken

Notification on The vCenter server Config Warning Warning
vCenter connection '${vcenterAddress}' has no
without certificates trusted certificates configured
validation and is unable to validate the
connection. Please manually
update the vCenter with a trusted
root certificate.
Notification on Array integration backup has Config Warning Warning
VMware virtual been enabled but is not possible
machines that have for the VMware virtual machines:
array integration '${vmNames}'.
enabled but cannot
use array integration.
Notifications for Failed to add cloud native source Config Failure Critical
adding cloud native ${sourceName} (${sourceType}).
source Reason: ${reason}.
Finished adding cloud native Config Success Info
source ${sourceName}
(${sourceType}).
Notifications for Failed to find total of Recovery Failure Critical
cloud native snapshot ${numSnapshots} snapshots
integrity across ${numVms} virtual
machines in the cloud source
${sourceName} (${sourceType}).
Please contact support. Snapshot
Details: ${vmSnapshotMap}
Notifications for Connectivity check for Config Failure Critical
connection status of ${specificInfo} failed.
archival locations and
cloud native sources
Notifications for The app cloud image ${imageId} Conversion Failure Critical
deleting cloud images could not be deleted from
location ${locationName}
The app cloud image ${imageId} Conversion Success Info
has been deleted from location
${locationName}
The cloud image ${imageId} on Conversion Failure Critical
location ${locationName} could
not be deleted
The cloud image ${imageId} Conversion Success Info
has been deleted from location
${locationName}
Notifications for Failed to terminate cloud instance Instantiate Failure Critical
deleting cloud ${instanceId}
instances
Cloud instance ${instanceId} was Instantiate Success Info
successfully terminated

Notifications for Failed to delete cloud native Config Failure Critical
deleting cloud native source ${sourceName}
source (${sourceType}). Reason:
${reason}.
Finished deleting cloud native Config Success Info
source ${sourceName}
(${sourceType}).
Notifications for Export of snapshot ${snapshotId} Recovery Failure Critical
exporting cloud native taken on ${date} from
VM snapshot cloud native virtual machine
${vmName} located at cloud
native source ${sourceName}
(${sourceType}) has failed.
Reason: ${reason}
Successfully exported snapshot Recovery Success Info
${snapshotId} taken on ${date}
from cloud native virtual machine
${vmName} located at cloud
(${sourceType}).
Notifications for Failed to refresh cloud native Diagnostic Failure Critical
refreshing cloud source ${sourceName}
native source (${sourceType}). Reason:
${reason}.
Finished refreshing cloud Diagnostic Success Info
(${sourceType}).
Notifications for Failed to restore cloud virtual Recovery Failure Critical
restoring cloud native machine ${vmName} in region
VM ${region} located at cloud
(${sourceType}). Reason:
${reason}
Finished restoring cloud native Recovery Success Info
virtual machine ${vmName} in
region ${region} located at cloud
(${sourceType}).
Notifications related Failed to download Recovery Failure Critical
to File Download ${numOfPaths} path(s)
from snapshot of
'${protected_objectName}' taken
at '${snapshotdate}'. Reason:
${reason}
Download link for ${numOfPath} Recovery Success Info
path(s) from snapshot of
'${protected_objectName}' taken
at '${snapshotdate}' is ready

Notifications related Failed to launch Instantiate Failure Critical
to instantiating ${protected_objectName}'s
instance on cloud image ${imageId} on
from image location ${locationName}
(${errorMessage})
Launched an instance of the Instantiate Success Info
${protected_objectName}
image with ID ${imageId} on
${locationName} with instance id
${instanceId} at IP ${instanceIp}
Notifications related Failed to launch Conversion Failure Critical
to instantiating on ${protected_objectName}'s
cloud snapshot (${errorMessage})
Successfully created an instance Conversion Success Info
of ${protected_objectName}
using the snapshot taken at
${formattedDate} on location
${locationName}
this issue.
Notifications related Failed to download Recovery Failure Critical

to MSSQL Backup files ${numOfSnapshots} snapshot(s)
download and ${numOfLogs} log(s) of the
database ${databaseName}.
Reason: ${reason}
Download link for Recovery Success Info
${numOfSnapshots} snapshot(s)
and ${numOfLogs} logs(s) of the
database ${databaseName} is
ready
Notifications related Failed to retrieve archived files for Recovery Failure Critical
to MSSQL download ${downloadDescription}. Reason:
${reason}
Archived files retrieved Recovery Success Info
to local storage for
${downloadDescription}
Notifications related Failed to download archived Recovery Failure Critical
to Oracle download snapshots for restore of
${recoveryPoint}.
Downloaded archived snapshots Recovery Success Info
to local storage to restore
${recoveryPoint}.

Notifications Failed to download snapshot of Recovery Failure Critical
related to Snapshot ${protected_objectName} taken
Download on ${timestamp}.
Finished downloading snapshot of Recovery Success Info
${protected_objectName} taken
on ${timestamp}.
NTP is not configured Node ${nodeId} has failed NTP Config Failure Critical 2.3.17
properly configuration checks. Please
verify that configured NTP servers
are functional and reachable.
this issue.
Nutanix unreachable. Failed to connect to Nutanix Config Failure Critical

Cluster. Make sure it is accessible
and credentials are correct
Object(s) were ${username} assigned objects Audit Success Info
protected to SLA Domain '${slaName}' for
protection - ${objectNameList}
Object(s) were ${username} unprotected Audit Success Info
unprotected objects: ${objectNameList}
Oracle rac discovery Discovered Oracle rac Discovery Success Info
'${racName}' with ${numDbs}
databases.
Oracle standalone Discovered standalone Oracle Discovery Success Info
host discovery host '${oracleHostName}' with
${numDbs} databases.
Power supply Power supply ${psuId} recovered Hardware Success Info 2.1.12
recovered on node ${nodeId}
Promoted an archival Failed to promote archival Config Failure Critical
location location '${name}'. Reason:
${reason}
Successfully promoted archival Config Success Info
location '${name}'
Recommissioned node Node ${nodeId} exited Config Success Info 2.3.11
successfully maintenance mode
Refreshed an archival Failed to refresh archival location Recovery Failure Critical
location '${name}'. ${reason}
Completed metadata Recovery Success Info
refresh for archival
location '${locationName}',
successful objects:
${successfulprotected_objectCount},
failed objects:
${failedprotected_objectCount}.

Remote cluster Successfully checked Config Success Info
connectivity check connection with remote cluster
succeeded ${locationName}.
Remote cluster Unable to reach remote cluster Config Failure Critical
unreachable ${locationName}.
Removed node Node ${nodeId} removed Config Success Info 2.3.13
successfully
Replace chassis Replace Chassis on node Hardware Failure Critical 2.1.4
Replace power supply Replace power supply on node Hardware Failure Critical 2.1.8
Replicating MSSQL Failed to replicate logs for Replication Failure Critical
logs failed ${protected_objectType}
on '${locationName}' from
'${sourceClusterName}' to
'${targetClusterName}'. Reason:
${reason}
Replicating Oracle Failed to replicate logs for Replication Failure Critical
logs failed ${protected_objectType}
from '${sourceClusterName}' to
'${targetClusterName}'. Reason:
${reason}.
Replicating virtual Failed to replicate Replication Failure Critical
machine snapshot ${protected_objectType}
failed '${protected_objectName}'
from '${sourceClusterName}' to
'${targetClusterName}. Reason:
${reason}'
Replication retention The replication source has Replication Warning Warning
is lower than archival changed the retention
threshold policy for replicated data to
${retentionInDays} days.
Retention for this replicated
data is lower than the archival
threshold and the data will
not be archived. Local and
archived data from this replication
source that is older than
${retentionInDaysNew} days will
be expired.

Replication retention The replication source has Replication Warning Warning
is reduced while changed the retention
archival cascading is policy for replicated data to
enabled ${retentionInDays} days. Local
and archived data from this
replication source that is older
than ${retentionInDaysNew} days
will be expired.
Replication source Removed replication source Config Success Info
was deleted '${clusterName}'
Replication target ${username} paused replicating Audit Warning Warning
paused replication. snapshots to this cluster from all
connected clusters. This impacts
${sourceClusterCount} clusters
replicating snapshots to this
cluster.
${targetClusterName} Replication Warning Warning
paused replicating snapshots
from all source clusters.
${affectedClusterName}
is no longer replicating to
${targetCluster}.
Replication target ${username} resumed replicating Audit Warning Warning
resumed replication. snapshots to this cluster from all
connected clusters. Snapshots
taken before and during the
pause will not be replicated. This
impacts ${sourceClusterCount}
clusters replicating snapshots to
this cluster.
${username} resumed replicating Audit Warning Warning
snapshots to this cluster from all
connected clusters. This impacts
${sourceClusterCount} clusters
replicating snapshots to this
cluster.
${targetClusterName} Replication Warning Warning
resumed replicating snapshots
from all source clusters.
has resumed replication to
${targetCluster}.
${targetClusterName} resumed Replication Warning Warning
replicating snapshots from all
source clusters. Snapshots
taken before or during the
pause will not be replicated.
has resumed replication to
${targetCluster}.

Restoring database Failed to restore database Recovery Failure Critical
'${sourceDb}' to
${recoveryPoint}. Reason:
${reason}
Restored SQL Server database Recovery Success Info
'${sourceDb}' to ${recoveryPoint}
Restoring file Failed to complete job to restore Recovery Failure Critical
${count} file(s) from snapshot
of '${protected_objectType}'
'${vmname}' taken at
'${snapshotdate}'
Successfully restored Recovery Success Info
${count} file(s)(total
${size}) from snapshot of
'${protected_objectType}'
'${snapshotdate}' in ${seconds}
seconds. Transfer rate was
${rate}
Failed to complete job to restore Recovery Failure Critical
${count} file(s) from snapshot
of '${protected_objectType}'
'${snapshotdate}' to
'${destVmName}'
Successfully restored Recovery Success Info
${count} file(s)(total
${size}) from snapshot of
'${protected_objectType}'
'${snapshotdate}' to
'${destVmName}' in ${seconds}
seconds. Transfer rate was
${rate}
Restoring fileset Failed to restore '${sourceDir}' Recovery Failure Critical
'${snapshotDate}'.
Successful restore of Recovery Success Info
'${sourceDir}' to '${destination}'
based on snapshot taken at
'${snapshotDate}'. Successfully
restored ${logicalSize} of
data in ${numFiles} files,
${numLinks} symbolic links,
${numHardlinks} hard links, and
Failed to restore ${numErrorFiles}
files, ${numErrorHardlinks} hard

links and ${numErrorDirectories}
directories.
Restoring HDFS Failed to restore '${sourceDir}' Recovery Failure Critical
'${snapshotDate}'
Successful restore of Recovery Success Info
'${sourceDir}' to '${destination}'
based on snapshot taken at
'${snapshotDate}'. Successfully
restored ${logicalSize} of
data in ${numFiles} files, and
Failed to restore ${numErrorFiles}
files, and ${numErrorDirectories}
directories.
Rotated keys Successfully rotated data Config Success Info
successfully encryption keys protected by
${rotationDest}
Rubrik Backup Service Rubrik Backup Service Diagnostic Warning Warning
on host unreachable. unreachable on host
${hostName}. Reason:
${reason}.
Related Concepts
Event descriptions
Events S to Z
Event descriptions from S to Z.

Seeding secondary Failed to seed SQL Server Recovery Failure Critical
database for log secondary database '${destDb}'
shipping from primary database
'${sourceDb}'. Reason: ${reason}
Successfully seeded SQL Recovery Success Info
Server secondary database
'${destDb}' from primary
database '${sourceDb}'.
Set cluster-wide Successfully set cluster-wide Config Success Info
rksupport credential rksupport credential
successfully
Set KMIP Successfully configured KMIP on Config Success Info
configuration all nodes
successfully

Set web server TLS Successfully configured web Config Success Info
certificate successfully server TLS certificate on all nodes
SLA archival policy ${count} protected_objects is/ Diagnostic Failure Critical
violation are out of SLA compliance due to
missed archival snapshot. These
are: ${protected_objectInfoList}
this issue.
SLA domain ${username} edited SLA Domain Audit Success Info

parameter changed '${slaName}'
SLA policy violation ${count} protected_objects is/ Diagnostic Failure Critical
are out of SLA compliance due to
missed local snapshot. These are:
${protected_objectInfoList}
SMB Service failed. Failed to run SMB service for Config Failure Critical
${domainName}. Please re-
configure SMB security for
this domain. This failure can
happen due to either deletion
of computer user from Active
Directory or due to connectivity
issues to domain controllers of
this Active Directory.
SMB Service is SMB service for ${domainName} Config Success Info
healthy. is healthy.
Some nodes on Unable to reach node(s) Config Warning Warning
remote cluster ${nodeList} of remote cluster
unreachable ${locationName}.
Some volumes were Could not find volume(s) Backup Warning Warning
not present at time of ${volumeMountPoints} on host
snapshot '${hostname}', but snapshot will
proceed
Stuck jobs have been Stuck jobs have been detected Diagnostic Warning Warning
detected that cannot (${jobIdList}). Please contact
be canceled support.
Successfully exported Successfully exported tablespace Recovery Success Info
Oracle tablespace '${tablespaceName}' of
${source} to ${recoveryPoint}.
Support bundle ready Log collection from nodes failed Diagnostic Failure Critical
to download ${msg}
Log collection partially successful Diagnostic Success Info
due to limited disk space.

Download the logs from
${destination}.
Successfully collected the logs Diagnostic Success Info
from each node in the cluster.
Download the collected logs from
${destination}.
Support tunnel closed Support tunnel closed on node Support Warning Warning
due to inactivity ${nodeId} due to inactivity
System Storage Storage usage exceeds Storage Warning Warning
Usage Alert ${percent}% of system capacity.
Reduce storage usage by deleting
snapshots or removing data
protection from non-essential
objects to keep space available
for backup jobs. For Rubrik
clusters, increase total storage
capacity by adding nodes.
Taking a full direct Taking a full direct archive backup Backup Warning Warning
archive backup of of fileset '${filesetName}'. A full
fileset backup takes a longer time to
complete.
The log snapshot is The recoverable chain starting Backup Warning Warning
missing log sequence at ${startTime} has broken at
numbers ${endTime}. You cannot recover
to a point in time until you take a
database backup. Please trigger a
new database backup to resume
the recoverable chain. Reason:
${detailMsg}
Log backup detected some Backup Warning Warning
missing sequence numbers. You
cannot recover to a point in time
until you take a database backup.
Please trigger a new database
backup to resume the recoverable
chain. Details for the missing
archived logs: ${detailMsg}
The recoverable The recoverable chain will Recovery Warning Warning
chain is broken after be broken after the Instant
recovery Recovery of the database. Point-
in-time recovery is unavailable
until a new database backup
is complete. Please trigger a
new database backup after live
migrating the data files and
unmounting the live-mount to
resume the recoverable chain.
The recoverable chain will be Recovery Warning Warning
broken after recovering the
production database. Point-in-

time recovery is unavailable
until a new database backup
is complete. Please trigger a
new database backup to resume
recovery.
The transaction log Log backup for Recovery Warning Warning
chain is broken ${dbNameWithLocation} is
unrecoverable due to lack
of contiguity with any other
snapshots or logs for this
database. This log backup will not
be retained. The log file has been
successfully truncated.
Log backup for Recovery Warning Warning
${dbNameWithLocation} is
unrecoverable due to lack
of contiguity with any other
snapshots or logs for this
database. This log backup will
not be retained. The log file has
been successfully truncated. The
previous log backup was taken by
'${username}'.
TPM needs firmware TPM on node ${nodeId} needs Diagnostic Warning Warning 2.3.15
upgrade firmware upgrade
Unformatted disk The disk device ${diskDeviceId} Diagnostic Warning Warning 2.2.8
found on a node on node ${nodeId} is
unformatted
Unmounting database Failed to unmount Recovery Failure Critical
'${objectName}'
Failed to unmount Recovery Failure Critical
'${mountedDatabaseName}'.
Reason ${reason}.
Unmounted Recovery Success Info
'${objectName}'
'${mountedDatabaseName}'.
Unmounting Hyper-V Failed to unmount Recovery Failure Critical
VM snapshot ${protected_objectType}
'${objectName}'
'${objectName}'

Unmounting virtual Failed to unmount disks from Recovery Failure Critical
machine snapshot ${protected_objectType}
'${objectName}'
Unmounted disks from Recovery Success Info
'${objectName}'
Failed to unmount Recovery Failure Critical
'${objectName}'
'${objectName}'
Unperformed SQL A database state change EmbeddedEvent
EmbeddedEvent
Info
Server log shipping was requested but no logs
backup were shipped from SQL
Server primary database
'${primaryDb}' to secondary
database '${secondaryDb}'.
User is locked out Local user ${username} Audit Warning Warning
from cluster is locked out because of
${maxFailedLogin} failed
attempts to login
User-specified backup Failed executing Backup Failure Critical
script failed. Backup ${preOrPost} script for
job continued as ${protected_objectType}
requested. '${protected_objectDisplayName}'.
No working credential found
Failed executing Backup Failure Critical
${preOrPost} script for
'${protected_objectDisplayName}'.
Script finished with error code
'${errorCode}'
Failed executing Backup Failure Critical
'${protected_objectDisplayName}'
Timeout while executing Backup Failure Critical
'${protected_objectDisplayName}'.
Script did not finish within
'${timeout}' seconds
vCenter unreachable. Failed to refresh vCenter Config Failure Critical
'${vcenterAddress}'. Reason:
${reason}
Virtual machine was The virtual machine Recovery Warning Warning
unarchived ${protected_objectName} has

been unarchived. Previous SLA
Domain ${lastSlaDomainName}.
vMotion move of Failed vMotion move of the Recovery Failure Critical
datastore for virtual datastore for virtual machine
machine to vCD ${vmName}. Reason: ${reason}
Volume no longer Could not find volume Backup Warning Warning
exists on Storage '${volumeName}' for
Array storage array volume group
storage array so we cannot take
its snapshot. Will proceed to back
up remaining volumes.
Windows Volume Failed to mount Recovery Failure Critical
Group mounted ${protected_objectType}
'${objectName}'.
'${objectName}'
Windows Volume Failed to unmount Recovery Failure Critical
Group unmounted ${protected_objectType}
'${objectName}'
'${objectName}'
Related Concepts
Event descriptions

Chapter 3
Rubrik provides troubleshooting information for many events in Knowledge Base articles that are available
through the Rubrik Support Portal.
Notification Event message Event description KB article link

Failed to verify data at Failed to verify Rubrik could not verify 000002932
rest encryption keys encryption keys for the validity of the
node ${nodeId}. Please encryption keys of the
contact Rubrik Support.. node.
LDAP service is LDAP (${name}) cannot Connection to LDAP 000003056
unhealthy. be accessed! (Error: server failed.
${exception}). Fix LDAP
integration to allow
the Rubrik cluster to
send important failure
notifications. Open
Settings > Users > LDAP
Servers to correct the
LDAP configuration on
the Rubrik cluster.
Creating MSSQL log Failed backup of Failed to backup the 000002973
failed the transaction Microsoft SQL Server
log for database database transaction log.
from '${locationName}'.
Reason: ${reason}"
SLA archival policy ${count} The archival is not up 000002904
violation protected_objects is/are to date for the specified
out of SLA compliance protected objects
due to missed archival according to their
snapshot. These are: SLA Domain archival
${protected_objectInfoList}policy, and one or more
snapshots are pending
archival.
A task launched by the A periodic task has failed Generally, this message 000003153
node has failed on node ${nodeId}: indicates that a basic
${message} condition has been
violated, such as missing
network configuration
files. These conditions
depend on the local
state of the node, not on
a cluster-wide state.
Troubleshooting information 07/20/2021 | 38

Failed to consolidate Archival consolidation Consolidation failed on 000002941
snapshots on archive failed on the specified archival
'${locationName}': location. The message
'${reason}' includes the reason.
NTP is not configured Node ${nodeId} has An NTP check failed on 000003370
properly failed NTP configuration the specified node.
checks. Please verify
that configured NTP
servers are functional
and reachable.
SLA archival policy ${count} The Rubrik cluster 000003086
violation protected_objects is/are missed taking a number
out of SLA compliance of snapshots for the
due to missed archival listed protected objects.
snapshot. These are:
${protected_objectInfoList}
None available The Hyper-V VM The Hyper-V virtual 000003381
has reached the machine has reached
maximum limitation of the maximum threshold
${hypervVmCheckpointLimit}
for checkpoints and
checkpoints will not perform a new
checkpoint.
The transaction log chain Log backup for The transaction log of 000002977
is broken ${dbNameWithLocation} the backup job cannot
is unrecoverable due to be used and will be
lack of contiguity with discarded.
any other snapshots or
logs for this database.
This log backup will not
be retained. The log file
has been successfully
truncated.
Notifications related to Failed to launch The listed protected 000002927
instantiating on cloud ${protected_objectName}'sobject image cannot be
snapshot instantiated.
(${errorMessage})
Successfully created
an instance of
${protected_objectName}
using the snapshot taken
at ${formattedDate}
on location
${locationName}

None available The Hyper-V virtual A virtual machine has 000003474
machine '${vmName}' two Hyper-V virtual disks
has multiple disks with the same identifier.
with the same
virtual disk identifier,
${diskIdentifier}. Virtual
disks in a Hyper-V virtual
machine must have
unique disk identifiers.
None available Cannot find a The Rubrik cluster did 000003554
valid replica of the not select an instance
availability database to source an Availability
${databaseName}. Group back up.
Reason: ${reason}
None available Unable to run The backup agent 000003352
sqlcmd.exe. Verify cannot find the
that sqlcmd.exe is sqlcmd.exe command,
installed and that causing a backup failure.
the system PATH
environment setting
contains the correct path
to sqlcmd.exe.
None available CDP Filter The CDP IO filter 000003147
${filterVersion} installation failed.
Installation Failed
on ${clusterName}.
VMware returned error:
${reason}

Rubrik CDM Version 6.0 Events Guide (Rev. A1)

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Rubrik CDM Version 6.0 Events Guide (Rev. A1)

Uploaded by

Copyright:

Available Formats

Rubrik CDM Events Guide

Rubrik Headquarters: Palo Alto, California 94304

Copyright and trademarks

Copyright © 2021 Rubrik Inc.

Registered in the U.S. Trademark Office

Copyright and trademarks 07/20/2021 | ii

Copyright and trademarks 07/20/2021 | iii

Web Rubrik Support Portal

Comments and suggestions

Severity level Description

Configuring event email settings

Administrator email alerts

Rubrik CDM information about individual events

Notification Event message Type Status Severity SNMP OID

Event descriptions 07/20/2021 | 11

Added node(s) Added ${numNodes} node(s) Config Success Info 2.3.2

Event descriptions 07/20/2021 | 12

Event descriptions 07/20/2021 | 13

Creating snapshot Failed Backup Failure Critical 4.0.1

Event descriptions 07/20/2021 | 14

Notification Event message Type Status Severity SNMP OID

Event descriptions 07/20/2021 | 15

Event descriptions 07/20/2021 | 16

Event descriptions 07/20/2021 | 17

Failed to create Failed to create managed volume Config Failure Critical

Event descriptions 07/20/2021 | 18

Event descriptions 07/20/2021 | 19

Event descriptions 07/20/2021 | 20

Event descriptions 07/20/2021 | 21

Event descriptions 07/20/2021 | 22

Notification Event message Type Status Severity SNMP OID

Event descriptions 07/20/2021 | 23

Event descriptions 07/20/2021 | 24

Event descriptions 07/20/2021 | 25

Event descriptions 07/20/2021 | 26

Notifications related Failed to download Recovery Failure Critical

Event descriptions 07/20/2021 | 27

Nutanix unreachable. Failed to connect to Nutanix Config Failure Critical

Event descriptions 07/20/2021 | 28

Event descriptions 07/20/2021 | 29

Event descriptions 07/20/2021 | 30

Event descriptions 07/20/2021 | 31

Notification Event message Type Status Severity SNMP OID

Event descriptions 07/20/2021 | 32

SLA domain ${username} edited SLA Domain Audit Success Info

Event descriptions 07/20/2021 | 33

Event descriptions 07/20/2021 | 34

Event descriptions 07/20/2021 | 35

Event descriptions 07/20/2021 | 36

Event descriptions 07/20/2021 | 37

Notification Event message Event description KB article link

Troubleshooting information 07/20/2021 | 38

Troubleshooting information 07/20/2021 | 39

Troubleshooting information 07/20/2021 | 40

You might also like