diff --git a/API_Playground_1.md b/API_Playground_1.md new file mode 100644 index 0000000000000000000000000000000000000000..1e51cb3458f33c3a91dce06547c17ca64a4a6135 --- /dev/null +++ b/API_Playground_1.md @@ -0,0 +1,19 @@ +# API Playground + +Source: https://docs.rubrik.com/en-us/saas/gql/api_playground_2.html + +--- + +# API Playground + +API Playground is a development environment integrated with Rubrik Security Cloud that you can use to run various GraphQL API operations on the data managed in real time by RSC. + +API Playground is an integrated development environment (IDE) that you can use to browse, explore, and run GraphQL APIs offered by Rubrik Security Cloud (RSC). The IDE also provides reference to the latest Rubrik GraphQL API documentation. Running GraphQL queries and mutations in API Playground validates the GraphQL operations so that you can confirm that your queries or mutations will achieve the expected result when included in automation scripts. + +After logging in to API Playground with your RSC user account credentials, you can choose to run GraphQL queries and mutations either as yourself or with a service account. The level of access you have for running the GraphQL queries and mutations depends on the RBAC roles assigned to your user account or to the service account you are using. For enhanced security, API Playground does not persist the service account access credentials. + +Warning: + +If not used cautiously, the GraphQL mutations that you run in API Playground can result in data loss because they affect the data managed in real time by RSC. + +In addition to using the API Playground, you can also use the PowerShell SDK for RSC to enable seamless automation and management of various operations within RSC. You can download the SDK from the [PowerShell Gallery](https://www.powershellgallery.com/packages/RubrikSecurityCloud) or from the [Rubrikinc GitHub repository](https://github.com/rubrikinc/rubrik-powershell-sdk). diff --git a/Annapurna_1.md b/Annapurna_1.md new file mode 100644 index 0000000000000000000000000000000000000000..0c530e99a332af0c8137ee69ae21d8608258edaa --- /dev/null +++ b/Annapurna_1.md @@ -0,0 +1,35 @@ +# Annapurna + +Source: https://docs.rubrik.com/en-us/saas/ai/annapurna.html + +--- + +# Annapurna + +Rubrik Security Cloud includes the Annapurna application which you can use to obtain answers from your data, using generative AI. + +Annapurna is an enterprise application. By using the generative AI capabilities of Annapurna, you can leverage your protected data to obtain natural language answers to business questions through retrieval-augmented generation (RAG). + +You can use Annapurna in two different ways: + + * Custom chatbots can be created in Rubrik Security Cloud (RSC) to process your prompts through the large language model (LLM) of Azure OpenAI Service. + * Data chunks generated via RAG can be retrieved using an API endpoint, and these chunks can then be sent to your specified LLM within your custom GenAI application. + +To begin using Annapurna with your enterprise data, your administrators create chatbots. Each chatbot specifies which workload data to index and which sensitive data filters to apply. A chatbot can be configured to exclude sensitive user data based on your Data Security Posture policies. Data sources from the following workloads can be included: + + * Microsoft 365 + * Jira Cloud + * Salesforce + * Confluence[1](#fntarg_1) + +After specifying the data to include, your administrators assign a role to the chatbot. Only users with the assigned role will be able to use the chatbot. The data available to a user through a chatbot depends on the access permissions the user has for that data. Annapurna uses the permissions assigned by each source application to determine the access a user has to data from that application. + +Once chatbots are created, your enterprise users can launch a chatbot and ask natural language questions about the data available through the chatbot. Based on the query, Annapurna uses RAG to get relevant data from the available data sources. The retrieved data and the query are combined into a prompt and sent to the LLM. The user gets a natural language response to their query that is based on the data included in the prompt. This process does not involve training the LLM. + +The chatbots that your administrators create can use multiple data sources from different workload types. This means a chatbot can query data from various workloads at the same time. Queries through such a chatbot can give answers that combine data from different sources. + +Important: + +Annapurna uses generative AI to respond to your prompts. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. + +[1](#fnsrc_1) To enable Confluence as a data source, contact Rubrik Support. diff --git a/Anomaly_Detection_1.md b/Anomaly_Detection_1.md new file mode 100644 index 0000000000000000000000000000000000000000..d130be0336a437d850eea988384cad7708589e19 --- /dev/null +++ b/Anomaly_Detection_1.md @@ -0,0 +1,52 @@ +# Anomaly Detection + +Source: https://docs.rubrik.com/en-us/saas/saas/anomaly_detection.html + +--- + +# Anomaly Detection + +Anomaly Detection examines a range of file system statistics to check for anomalies in file system usage patterns. + +Anomaly Detection provides details about potentially anomalous incidents, including their location, Rubrik cluster, file details, and snapshot time. When you enable Orchestrated Recovery, objects that are part of a Recovery Plan are grouped together. + +When you enable Anomaly Detection for the data, Large Language Model (LLM) analysis for Anomaly Detection is enabled by default. When LLM analysis for Anomaly Detection is enabled, RSC uses a pre-trained LLM in Microsoft Azure OpenAI to detect suspicious activity. The model differentiates suspicious activity from legitimate changes caused by routine operations, such as upgrading an application or operating system. + +Identifying and differentiating malicious behavior from legitimate activities helps reduce the frequency of false alerts and enhances the experience of using Anomaly Detection to protect data. When you do not want to use LLM analysis on Anomaly Detection, you can disable it and use Anomaly Detection without it. + +When you enable Data Security Posture for an object that has an anomalous snapshot and a user account that has Data Security Posture privileges, the Sensitive files and Sensitive hits columns display values based on the base snapshot of the anomalous snapshot. The Sensitive files column shows the number of files that contain sensitive data, and the Sensitive hits column shows the number of sensitive hits for that object. + +Note: + +Anomaly Detection supports protected objects running in single-stack IPv6 environments. + +On the Anomaly Detection page, you can: + + * View the list of new and resolved investigations. + * Use the filters on the page to sort anomalies by time range, severity, encryption, object type, Rubrik cluster, and SLA Domain. + * Sort anomalous data by sensitive files or sensitive hits when you enable Data Security Posture. + * Filter anomalies by the selected policies when you enable Data Security Posture. + * Investigate and recover anomalous files in protected workloads. + * Recover a full snapshot for a virtual machine. + * Use the Search filter to search for protected workloads or Recovery Plans that have an identified anomaly. + * Initiate bulk recovery for vSphere-protected workloads or for Recovery Plans that have an identified anomaly. + * Perform cyber recovery on virtual machines based on threat hunting results to a local, isolated recovery environment. + * Download a CSV file of the changes identified for each protected workload. When you click Download CSV, RSC prepares a secure link for the file and displays a message about the download. You can also visit the File Preparation Center to access the downloaded file. + +RSC supports Anomaly Detection for: + + * VMware, AHV, and Hyper-V virtual machines + * NAS filesets + * Linux and Windows servers + * Windows Volume groups + * NAS CD data sets + * Azure virtual machines + * Azure Blob storage + * Microsoft OneDrive and SharePoint + * Amazon S3 buckets + * Amazon EC2 instances and EBS volumes + * Kubernetes virtual machines + * Kubernetes protection sets + * GCP GCE Instance + * GCP Persistent Disk + diff --git a/Anomaly_Detection_reports_1.md b/Anomaly_Detection_reports_1.md new file mode 100644 index 0000000000000000000000000000000000000000..607d3bb50881504fe5c80f5546cfee4bf09a4561 --- /dev/null +++ b/Anomaly_Detection_reports_1.md @@ -0,0 +1,13 @@ +# Anomaly Detection reports + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_reports.html + +--- + +# Anomaly Detection reports + +Anomaly Detection reports provide information about the changes in snapshots for anomaly events. You can also download, save, or delete the reports. + +The Anomaly Detection report displays information about anomalies detected in the Scanned Objects and Unscannable Objects tab. You can view details, including snapshot date, resource name, resource type, change in byte size, anomaly indicator, number of files added, number of files removed, and number of files modified. + +You can also download a CSV or PDF file of the report, send the report to an email address, and save or delete the report. diff --git a/CLI_administrator_role_1.md b/CLI_administrator_role_1.md new file mode 100644 index 0000000000000000000000000000000000000000..da53a964825cf4451d111fddf3583f8143a95e19 --- /dev/null +++ b/CLI_administrator_role_1.md @@ -0,0 +1,15 @@ +# CLI administrator role + +Source: https://docs.rubrik.com/en-us/saas/cdm/cli_administrator_role.html + +--- + +# CLI administrator role + +As a CLI administrator, a Rubrik cluster user can connect to nodes in Rubrik clusters through the CLI Secure Shell (SSH) protocol. + +As both an administrator and a CLI administrator, you can assign the CLI administrator role (CliAdminRole) to others who have the administrator role. With that role, they can connect to nodes in the Rubrik cluster through the Secure Shell (SSH) protocol and use the full range of CLI commands. + +The CLI administrator role cannot be assigned to a username that contains a dot (.) character. + +Regardless of their assigned roles, only Rubrik CDM local users can connect using SSH. LDAP and SSO users are denied SSH access. diff --git a/Cluster_configuration_considerations_1.md b/Cluster_configuration_considerations_1.md new file mode 100644 index 0000000000000000000000000000000000000000..64e41d138d458ad516f4e59f6545ca7c64091b4c --- /dev/null +++ b/Cluster_configuration_considerations_1.md @@ -0,0 +1,19 @@ +# Cluster configuration considerations + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_config_considerations.html + +--- + +# Cluster configuration considerations + +You determine network related settings and capabilities of a Rubrik cluster through the set up task. + +The initial setup of the cluster involves node discovery, and the configuration of data and management interfaces and services for all the nodes on the cluster. A UI to perform the initial configuration is available through any of the nodes. Alternatively, you can configure the cluster at the command line using the Rubrik CLI. + +If you have an IPv4 cluster deployment, you can optionally configure VLAN tagging for both the management network and the data network. You can configure VLAN tagging through either the UI or the Rubrik CLI. + +If your cluster deployment supports encryption of data at rest, Rubrik CDM enables data encryption by default during the initial configuration. You can disable the encryption of data at rest but this must be done through the CLI and should be done before protecting any data. If the encryption of data at rest setting is changed after system setup, a cluster reset is required, which will delete all stored data. + +The setting for encryption of data at rest is supported only on Brik models that have the hardware Trusted Platform Module (TPM).You will not have this option during setup for Brik models that use hardware data encryption at rest, such as the r6xxxF series Briks. + +Virtual clusters allow you to configure an encryption password when you enable encryption. diff --git a/Cluster_registration_1.md b/Cluster_registration_1.md new file mode 100644 index 0000000000000000000000000000000000000000..3c75b5b5fd9770ff5fe9251ce4e1b9c860052b54 --- /dev/null +++ b/Cluster_registration_1.md @@ -0,0 +1,17 @@ +# Cluster registration + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_registration.html + +--- + +# Cluster registration + +Rubrik offers two modes for registering clusters with Rubrik Security Cloud, online and offline. + +After configuring a Rubrik cluster, the next required task is to register it through your Rubrik Security Cloud account. Registration is performed over the internet using a web browser. + +The online registration method uses a secure internet connection from the Rubrik cluster to your Rubrik Security Cloud account to retrieve the registration key. When physical hardware is in use, that hardware must also be available and have access to the network. + +The offline registration method uses a manual method of retrieving the registration key and providing it to the Rubrik cluster. Offline registration requires access to a web browser for a one-time login to the Rubrik Security Cloud account to retrieve a unique registration key for each cluster. The registration key is valid only for two days from the time it is generated. + +Either way, the registration process requires signing into your Rubrik Security Cloud account using a web browser on a computer with an internet connection, even when the configuration of the cluster was performed through the CLI. The domain URL of your Rubrik Security Cloud account is available in the Rubrik Welcome email or on the Rubrik Support portal. diff --git a/Comments_and_suggestions_2.md b/Comments_and_suggestions_2.md new file mode 100644 index 0000000000000000000000000000000000000000..dfac7db80617d4eaf0a0b87d181191c7103e2cbb --- /dev/null +++ b/Comments_and_suggestions_2.md @@ -0,0 +1,33 @@ +# Comments and suggestions + +Source: https://docs.rubrik.com/en-us/saas/reuse/comments_suggestions.html + +--- + +# 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](support.html "Use one of the following methods to contact Rubrik Support."). + +## Product documentation + +To provide comments and suggestions about the product documentation, send an email to: [techpubs@rubrik.com](mailto:techpubs@rubrik.com). + +To help our writers identify the area that you are referencing, include the following requested information. + +For HTML documentation, include: + + * Page title + * Page address + * Page date + +For PDF documentation, include: + + * PDF title + * Part number + * Revision + * Relevant page numbers + diff --git a/Data_Security_Posture_1.md b/Data_Security_Posture_1.md new file mode 100644 index 0000000000000000000000000000000000000000..2e9ac7b8f38a0d9b10e361a8f96c819ab7385f60 --- /dev/null +++ b/Data_Security_Posture_1.md @@ -0,0 +1,29 @@ +# Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/data_security_posture.html + +--- + +# Data Security Posture + +Data Security Posture provides agile data security across multi-cloud environments for posture management and access governance. It also includes threat monitoring and response to protect your data. + +Organizations have innovated how they use cloud data, but not how they secure it. Users create, copy, share, and move cloud data rapidly. This drastic expansion and replication of data for business advantage protected by traditional data security controls creates a security gap. Data Security Posture provides the capability to effectively manage data security, for data located on premises, in the cloud, or on SaaS applications. This unified approach enables you to define, manage, and monitor policies regardless of where data resides. Rubrik Data Security Posture discovers and classifies all data across all your environments, including managed and self-hosted technologies to provide the following benefits: + + * Automated data discovery across on-prem, cloud, and SaaS workloads + * Data classification without impact on production workloads + * Built-in and customizable data categories and data types + * Identity inventory showing sensitive data access and blast radius + * Identification of data at risk and appropriate access remediation + * User Insights highlighting changes to sensitive data + * Detection of suspicious data activity + +Data Security Posture automatically discovers and classifies an extensive range of data detected across your multi-cloud environment while ensuring that sensitive data never leaves your environment. Data Security Posture focuses on the following: + + * Identifying sensitive and regulated data across your organization + * Locating objects that have sensitive data and their location and flagging their exposure + * Detecting violations of your data policy and identifying misconfigured, misplaced, or obsolete data + * User access to data and remedying access issues + * Monitoring for allowed access and providing alerts of anomalous activities + +You can use the insights from Data Security Posture with third-party integrations to maintain a data security environment resilient to external threats. diff --git a/Data_Threat_Analytics_dashboard_1.md b/Data_Threat_Analytics_dashboard_1.md new file mode 100644 index 0000000000000000000000000000000000000000..5e712e334efa2e7eaee9111ab66244f3a25b6056 --- /dev/null +++ b/Data_Threat_Analytics_dashboard_1.md @@ -0,0 +1,23 @@ +# Data Threat Analytics dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/dta_dashboard.html + +--- + +# Data Threat Analytics dashboard + +The Data Threat Analytics dashboard provides a comprehensive analysis of data threats including a summary of anomalies, threat monitoring matches, matched threat hunts for protected objects, and object timeline analysis. + +Widget | Description +---|--- +Threat Summary | Displays the number of backups completed with the percentage of healthy backups and the following Data Threat Analytics summary: + + * Anomaly Detection analysis completed and the number of anomalous objects found + * Threat Monitoring results with the details of the objects scanned for IOCs appear + * Active threat hunts with the number of matched hunts + +You can filter the data for the past 24 hours, 7 days, or 30 days. +Known IOCs | Displays a pie chart of the known IOCs for which Threat Monitoring checks. The chart displays known IOCs divided into file hashes and YARA rules. This widget also displays the time at which the known IOCs were updated. +Anomaly Detection | Displays the total percentage of anomalous and non-anomalous objects for the past 24 hours, 7 days, and 30 days. +Threat Monitoring | Displays the total percentage of objects with and without threats for the past 24 hours, 7 days, and 30 days.This widget is visible when Threat Monitoring is enabled. Threat Monitoring is available as part of the Rubrik Enterprise edition. +Timeline Analysis | The chart shows the number of anomalies and threats found over the past 7 days and 30 days. diff --git a/Data_Threat_Analytics_events_1.md b/Data_Threat_Analytics_events_1.md new file mode 100644 index 0000000000000000000000000000000000000000..bb51114e463c596ec061a3b1e3e1540c62e72054 --- /dev/null +++ b/Data_Threat_Analytics_events_1.md @@ -0,0 +1,15 @@ +# Data Threat Analytics events + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_events.html + +--- + +# Data Threat Analytics events + +Data Threat Analytics provides filters and real-time search capabilities that can be used to find specific events. + +When events are enabled, Data Threat Analytics sends an alert email when an anomaly is detected. The alert email contains a link to RSC. Accessing the link allows you to perform further investigation and, if necessary, recover files. The recovery process allows you to replace only the affected data without requiring that you perform a new analysis of the entire data set. + +Click on a Data Threat Analytics event to view the time line of snapshots taken for a specific time range, examine the file system of a series of snapshots, and determine approximately when the ransomware attack occurred. From this view, select the snapshot with the most recent clean versions of the files that were identified as compromised. Those files can be used as the starting point for file recovery. + +To support RBAC, CSV file downloads are only available from the Anomalies page and the anomaly details page. When you click Download CSV, RSC prepares a secure link for the file and displays a message about the download. You can also visit the File Preparation Center to access the downloaded file. diff --git a/Downloading_and_installing_Rubrik_CDM_1.md b/Downloading_and_installing_Rubrik_CDM_1.md new file mode 100644 index 0000000000000000000000000000000000000000..a051cb6cfc8dda2d178dd0ecc573d405a0beaf7f --- /dev/null +++ b/Downloading_and_installing_Rubrik_CDM_1.md @@ -0,0 +1,121 @@ +# Downloading and installing Rubrik CDM + +Source: https://docs.rubrik.com/en-us/saas/install/download_install_cdm_on_appliance_nodes.html + +--- + +# Downloading and installing Rubrik CDM + +Before you set up your Rubrik cluster, you can install a version of Rubrik CDM that is different from the one already installed on the Rubrik appliance nodes. This involves downloading the software, transferring it to one of the nodes, and running the installation. + +## About this task + +Rubrik appliance nodes are shipped with a recent major GA release package already installed. However, you will often want to install a more recent version of Rubrik CDM before you set up a new cluster. Or you may want to install a specific version on a new node before you add the node to an existing cluster. + +## Procedure + + 1. Download the Rubrik CDM installation package from the [Rubrik Support portal](https://support.rubrik.com/) to a computer with network access to the Rubrik appliance nodes. + +Part of the download process involves accepting the EULA. To be able to read and accept the EULA, you must disable the pop-up blocker setting in your web browser. + +When downloading a installation package for a new a node that you are adding to a running Rubrik cluster, select the installation package that contains the same version of Rubrik CDM that is on the running Rubrik cluster. + + 2. Unzip the package. + +The zip file contains an installation zip file and a signature file: + * rubrik-image-xyz.tar.gz + * rubrik-image-xyz_tar.gz.sig + +Where xyz is the release and patch number. + + 3. Use SSH over IPv6 to connect to the node. + +`ssh -6 admin@node_serial_number.local` + +Where `node_serial_number` is the serial number of the node. You can retrieve the serial number of the cluster node from the sticker attached to the node or by connecting directly to the node and running network ifconfig from the Rubrik CLI. + + 4. At the username prompt, enter `admin`. + 5. At the password prompt, enter `rubrik`. + +The Rubrik CLI prompt appears. + + 6. In the SSH session, enter the version-dependent command to view the IP address of the node. + +For Rubrik CDM version 5.0.4 and later, enter: + + network ifconfig + +For versions of Rubrik CDM earlier than 5.0.4, enter: + + ifconfig bond0 + +Keep the SSH session open to use later in this task. + +If cluster setup was previously run on the node, the IP address that appears will be an IPv4 address. If this is the first time you are configuring the node, the IP address will be an IPv6 address. The command also displays the interface name. + + 7. In a new terminal session, use SFTP to connect to the new node. + +For an IPv6 address, at the prompt, enter: + + sftp adminstaging@[ipv6address]%interface + +Where ipv6address is the IPv6 address and interface is the interface name determined in a previous step. For example: + + sftp adminstaging@[fe80::ae1f:6bff:fe55:8c77]%bond0 + +For an IPv4 address, at the prompt, enter: + + sftp adminstaging@ipv4address + +Where ipv4address is the IPv4 address determined in a previous step. For example: + + sftp adminstaging@10.1.79.12 + + 8. When prompted, enter the password. + +The password is `rubrik`. + + 9. Use SFTP to upload the installation package to the node. + +At the prompt, enter: + + put install-package /upgrade/ + +Where install-package is the name of the installation package. + + 10. Use SFTP to upload the signature file to the node. + +At the prompt, enter: + + put sig-file /upgrade/ + +Where sig-file is the name of the signature file. + + 11. Return to the SSH session and start the software installation. + +Enter: + + cluster install start + +A list of available versions of the CDM software appears. + + 12. When prompted, enter the number assigned to the software version that you want to install. + +A list of the available nodes appears. + + 13. When prompted, select the number assigned to a node that you want the software installed on. + +The installation script installs the software on the selected node and displays the list of nodes again, with an asterisk by the entry for each node that has the software successfully installed. + + 14. Repeat the previous step until all of the nodes that you want the software on are listed with an asterisk. + 15. **Optional:** To view the installation log, enter: + +`support log_view installer.log` + +## Results + +The installation script installs the selected software on all of the selected nodes. + +## What to do next + +After successfully completing the software installation process, perform the system setup task. diff --git a/Downloading_quarantined_files_for_forensic_analysis_1.md b/Downloading_quarantined_files_for_forensic_analysis_1.md new file mode 100644 index 0000000000000000000000000000000000000000..a1f8270c2d510f576c24d8258d4c9e9a6efec166 --- /dev/null +++ b/Downloading_quarantined_files_for_forensic_analysis_1.md @@ -0,0 +1,46 @@ +# Downloading quarantined files for forensic analysis + +Source: https://docs.rubrik.com/en-us/saas/saas/downloading_quarantined_files_analysis.html + +--- + +# Downloading quarantined files for forensic analysis + +Download quarantined files to examine and analyze them for malicious content. + +## Before you begin + +Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click the threat hunt of interest. + +If added to quarantine, the quarantined objects are listed along with details of their location, files matched, and match type. + + 5. Click an object to view the files in that object. + 6. Select the files to download. + 7. Click and select Download For Forensics. + +The Download for Forensics dialog box appears. + + 8. **Optional:** Click the snapshot column to choose any other non-expired snapshot containing the file. + +By default, the Download For Forensics wizard selects the latest non-expired snapshot for each file. + + 9. Click Download. + +Downloading the files can be dangerous if these files are malicious. Exercise caution to keep your systems safe. + +## Results + +RSC downloads the files as specified. diff --git a/Getting_started_with_RSC_1.md b/Getting_started_with_RSC_1.md new file mode 100644 index 0000000000000000000000000000000000000000..4a1e36caaddb619b1d9d8f1084e98259f0d1116f --- /dev/null +++ b/Getting_started_with_RSC_1.md @@ -0,0 +1,15 @@ +# Getting started with RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/common/getting_started_with_rsc.html + +--- + +# Getting started with RSC + +To start using Rubrik Security Cloud, add authorized user accounts before adding Rubrik clusters. + +Rubrik sets up the initial user account for the RSC domain and sends an email invitation to the primary owner from this account. After setting up the initial user account, the owner can invite other users to set up accounts on the domain. + +Any user account in the RSC domain with cluster-management permissions can add Rubrik clusters to the domain. + +RSC uses HTTPS to transmit data between RSC and Rubrik clusters. RSC requires that each Rubrik cluster enable outbound port 443 in both firewall and proxy settings. diff --git a/Guidelines_for_choosing_a_strong_password_1.md b/Guidelines_for_choosing_a_strong_password_1.md new file mode 100644 index 0000000000000000000000000000000000000000..ecf9f4b5a3bdec9df8858c4af4d54d65dbb55299 --- /dev/null +++ b/Guidelines_for_choosing_a_strong_password_1.md @@ -0,0 +1,34 @@ +# Guidelines for choosing a strong password + +Source: https://docs.rubrik.com/en-us/saas/install/guidelines_strong_password.html + +--- + +# Guidelines for choosing a strong password + +When choosing a password, you are required to follow the guidelines recommended by Rubrik to set a strong password that is difficult to guess or extract through a password cracker application, but is something that is easy to remember. + +When choosing a password, the goal is to make it difficult to guess but easy to remember. + +Rubrik recommends avoiding passwords with the following criteria: + + * Single words that can be found in a dictionary. + * Common passwords, such as passw0rd, letmein, or abc123. + * Repeated characters, such as aaaa or 2222. + * Character sequences, such as abcd or 1234. + * L33t speak, where numbers and symbols are used in place of letters, for example, 3 for e, @ for a, and $ for s. + * Patterns made up of adjacent keys on a keyboard, such as qwerty or ujm. + +You are required to incorporate the following characteristics to make a password difficult to guess but easy to remember: + + * Long strings (up to 1000 characters) of uncommon, unrelated words combined in a sequence, such as CorrectHorseBreadStaple. Rubrik clusters do not support passwords longer than 1000 characters. + * Unexpected caPitalizAtion. + * Numbers at the beginning or middle of the password or distributed throughout the password. + +As most users put a number at the end of their password, you must increase unpredictability by putting it at the beginning or in the middle, or distributing numbers throughout the password. + + * A series of short keyboard patterns with lots of turns. + +A turn corresponds to a change of direction on the keyboard from one character to the next. A turn can also refer to the gap between pattern segments in the password. + +To make the password easy to remember, you can try a long password (up to 1000 characters) made up of a series of dictionary words that are not commonly combined in a sequence, and include one or more numbers. diff --git a/Identities_in_Identity_Resilience_1.md b/Identities_in_Identity_Resilience_1.md new file mode 100644 index 0000000000000000000000000000000000000000..e923b2690228f27a4054659182c208dda240c884 --- /dev/null +++ b/Identities_in_Identity_Resilience_1.md @@ -0,0 +1,32 @@ +# Identities in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_identitites.html + +--- + +# Identities in Identity Resilience + +The identities page in Identity Resilience provides visibility into identities discovered in your environment. + +The Identities page within Identity Resilience provides a centralized and comprehensive view of all identities, both human and non-human, across your hybrid identity environment. This page is crucial for understanding the identity landscape and assessing associated risks. + +The Identities page offers a high-level summary of total identities discovered and the number of identities in your hybrid identity environment. + +RSC organizes identities into distinct categories, accessible through tabs for focused analysis: + + * All Identities: Displays a complete list of every discovered identity. + * Users: Focuses specifically on human user accounts. + * Groups: Lists security and distribution groups. + * Service Accounts: Highlights non-human identities often used by applications and services such as Group Managed Service Accounts (gMSA), Standalone Managed Service Accounts (sMSA), and enterprise apps. + +The Identities page is important for: + + * Visibility: Gaining a complete inventory of all identities and their characteristics. + * Identity insights: Quickly identifying identities that are at risk, privileged, or have access to highly sensitive data. + +Note: + +The highly sensitive data is available only if you have the DSPM license enabled. + + * Policy enforcement: Understanding which identities violate defined security policies. + diff --git a/Identity_Resilience_1.md b/Identity_Resilience_1.md new file mode 100644 index 0000000000000000000000000000000000000000..77067f440b579796de28b1eaea60284e2c4307ee --- /dev/null +++ b/Identity_Resilience_1.md @@ -0,0 +1,17 @@ +# Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/identity_resilience.html + +--- + +# Identity Resilience + +Rubrik Identity Resilience secures, monitors, and recovers the Identity Providers. + +Identity Resilience in Rubrik Security Cloud (RSC) offers protection services for identities in hybrid environments and safeguards the identity infrastructure in an organization. Identities, both human and non-human, are the most common entry points for cyberattacks, and any form of compromise in the identity infrastructure can cripple the ability of an organization to recover from a breach. + +Identity Resilience comprises security and recovery of identities in your hybrid identity infrastructure. Identity Resilience requires purchasing the Rubrik Identity Resilience License. + +Identity Resilience provides extensive capabilities, including protection, active risk identification, and robust remediation. It simplifies managing complexities in hybrid identity environments and addresses the increasing instances of cyberattacks, thereby minimizing the risks of identity compromise and data breaches. Additionally, it offers real-time monitoring to detect critical changes with Active Directory (AD), including modifications to privileged group membership and Group Policy Objects (GPOs). This enables immediate awareness of crucial security events. + +Identity Resilience provides automated, clean-room recovery, enabling swift restoration of compromised identities, and minimizes downtime. It also proactively mitigates risks by identifying risky privilege escalations and problematic access combinations. When combined with Data Security Posture Management (DSPM), Identity Resilience provides a holistic view of both data and identity, significantly strengthening the overall data security posture. diff --git a/Identity_Resilience_reports_1.md b/Identity_Resilience_reports_1.md new file mode 100644 index 0000000000000000000000000000000000000000..6e1e858f9ce3193aeab2dfba21993c6cb310b869 --- /dev/null +++ b/Identity_Resilience_reports_1.md @@ -0,0 +1,28 @@ +# Identity Resilience reports + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_reports.html + +--- + +# Identity Resilience reports + +The Identity Resilience Reports page offers comprehensive analytics and actionable insights into your identity security posture. It provides various report templates for protection status, identity violations, audit trails, and operational activities across Identity Providers. + +The Reports page in Rubrik Identity Resilience serves as the central hub for generating and managing analytical reports that provide deep insights into your identity security posture, protection status, and operational activities across your hybrid identity environments. This feature is crucial for compliance, auditing, risk assessment, and demonstrating the effectiveness of your identity resilience strategy. + +The page aggregates various reporting capabilities, allowing administrators to access predefined reports relevant to their specific needs. RSC organizes reports into categories, enabling users to quickly navigate to relevant areas of interest. + +You can generate the following reports for Identity Resilience: + + * Protection + * Protection Tasks Details + * Object Capacity + * SLA Audit + * Object Audit + * Recovery Tasks Details + * Event + * Identity Violations + +The Identity Violations report analyzes various identity-related security risks. + +The reports can transform raw operational and security data from your identity infrastructure into digestible, insightful formats, empowering organizations to make data-driven decisions regarding their identity resilience posture. diff --git a/Identity_summary_1.md b/Identity_summary_1.md new file mode 100644 index 0000000000000000000000000000000000000000..9fae3628b2ec10936564e4226a3f137681e63119 --- /dev/null +++ b/Identity_summary_1.md @@ -0,0 +1,37 @@ +# Identity summary + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_identity_summary.html + +--- + +# Identity summary + +RSC provides a summary of an individual identity and insights about various components of an identity. + +The identity summary overview page provides a detailed, centralized view of different aspects of a specific identity and activity within your hybrid environment. It serves as a single source for deep-dive investigations into any user, group, or service account. It also displays the essential attributes such as identity type, unique identifier, and current status. + +## Identity summary graph + +A dynamic graph illustrates the relationships of a specific identity within the environment and highlights immediate security concerns. This includes summarized insights such as risk status, privilege levels, and authentication posture, along with real-time counts of identity violations and alerts. + +For privileged identities, the graph also provides insights into their associated privileged memberships or roles. + +## Policy Violations + +The policy violations widget displays details of the violations associated with the identity and categorizes the violations based on severity. + +On the right, specific policy violations associated with the identity are detailed. This provides direct insight into non-compliance, alongside information about its data access by sensitivity, if available. + +## Snapshot Based Vulnerabilities Summary + +RSC provides a time-series trend graph that visually tracks the vulnerabilities or overall security posture of an identity over time. This allows administrators to observe historical trends, identify changes, and assess improvements or deteriorations in security state of the identity. + +RSC updates the vulnerabilities graph using the snapshot of the Identity Provider (IdP) object. When there are multiple snapshots of the IdP object in a day, the graph is updated only once after the last snapshot. + +## Data Access by Sensitivity + +Note: + +This requires a DSPM license. + +The data access by sensitivity widget provides information about the access to sensitive data, categorized by its sensitivity level. When data is available, it offers insights into the potential blast radius if the identity were compromised, based on data context. diff --git a/Jumbo_frame_support_1.md b/Jumbo_frame_support_1.md new file mode 100644 index 0000000000000000000000000000000000000000..b1401aff0ed7c87362e83ef395971a5e31e582c2 --- /dev/null +++ b/Jumbo_frame_support_1.md @@ -0,0 +1,31 @@ +# Jumbo frame support + +Source: https://docs.rubrik.com/en-us/saas/cdm/jumbo_frame_support.html + +--- + +# Jumbo frame support + +For Rubrik CDM versions 9.4 and later, you can set the value for the maximum transmission unit to a maximum value of 10000, instead of the default value of 1500. This larger unit size is called jumbo frames. + +You can use the Rubrik CLI to set the maximum transmission units (MTUs) for Rubrik CDM versions 9.4 and later to a maximum of 10000 bytes instead of the default value of 1500 bytes. This larger MTU size, called jumbo frames, provides a more efficient and much faster network throughput. The typical value for jumbo frames is 9000. + +Rubrik supports changing the MTU value for a Rubrik cluster only on bootstrapped physical machines, but not on cloud clusters. Changing the MTU is a cluster-wide parameter. If you set the MTU value on a node for an interface, this value applies to all the nodes in the cluster for that interface. If the Rubrik cluster includes a VLAN interface, this interface inherits the MTU value from the corresponding parent interface. + +Changes to the MTU value are persisted across: + + * Node and cluster reboots + * Cluster upgrades + * Node additions + +The MTU value from the Rubrik cluster is applied to the added node. + + * Node replacement + +The MTU value from Rubrik cluster is applied to the replacement node. + +Changes to the MTU value are not persisted across: + + * Node resets + * Operations that change the IP address + diff --git a/Key_features_of_Identity_Resilience_1.md b/Key_features_of_Identity_Resilience_1.md new file mode 100644 index 0000000000000000000000000000000000000000..7c89e932a8f80d1c0fc422264c55075fc106a706 --- /dev/null +++ b/Key_features_of_Identity_Resilience_1.md @@ -0,0 +1,46 @@ +# Key features of Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_key_features.html + +--- + +# Key features of Identity Resilience + +RSC provides unified identity management, identity protection, and identity security for human and non-human identities in hybrid identity environments. + +Rubrik Identity Resilience is a critical product offering designed to provide comprehensive security and recovery for the identity infrastructure in hybrid identity environments. + +The key features of Identity Resilience include: + +## Hybrid identity protection and recovery + + * Scope: Secures identities in complex hybrid setups. + * Automated discovery and protection: RSC automatically discovers AD domains, domain controllers (including FSMO roles, DNS, DHCP services), and Microsoft Entra ID tenants and objects for streamlined protection. + * Recovery: Offers automated, orchestrated recovery workflows to restore AD domain controllers, AD forests, and Microsoft Entra ID tenants quickly after attacks, reducing downtime. + * Clean-room recovery: Restores AD identities in a secure, isolated environment to prevent attacks by malware or persistent threats. + * SLA-based management: Applies defined SLA Domains for consistent backup frequency, retention, replication, and archival policies across your identity infrastructure. + * Granular restoration: Recovers specific AD or Microsoft Entra ID objects, such as users, groups, and service accounts, without full system rollback. + * Simplified process: Reduces manual recovery steps and accelerates restoration. + +## Real-time monitoring and alerts + + * Tamper-resistant monitoring: Provides real-time tracking of critical changes within AD. + * Privilege change tracking: Monitors additions or removals of users and groups from privileged AD groups, flagging potential escalations or unauthorized de-provisioning. + * GPO modification alerts: Immediately identifies and alerts on any changes to Group Policy Objects (GPOs), which are critical for maintaining security configurations. + * Notifications: Enables management of notification channels and email alerts for detected events. + * Rapid response: Enables early detection and faster response to identity-based threats. + +## Comprehensive risk analysis + + * Unified visibility: Provides a single dashboard to monitor human identities, such as user accounts and groups, and non-human identities, such as service accounts. + * Risk detection: Utilizes risk policies aimed at detecting security gaps across your identity and identity infrastructure configurations, enabling proactive remediation. + * Actionable remediation: Detects security violations and provides workflows to drive their remediation through IT Service Management (ITSM) integration, remediation guidance, and in-app remediation actions to close security gaps directly from RSC. + +## Identity and data context integration + +This requires a DSPM license. + + * Holistic view: Combines identity and sensitive data context for better prioritization of identity risks, identifies highly sensitive identities that require additional security measures, and assesses the potential blast radius of a compromised identity. + * Time-series data: Tracks identity and access changes over time for continuous monitoring and historical analysis. + * Enhanced threat investigation: Correlates identity risks with data access patterns to identify and respond to threats faster. + diff --git a/Legal_Notices_2.md b/Legal_Notices_2.md new file mode 100644 index 0000000000000000000000000000000000000000..b8083a672972cf7e53f30514e53ab1d757473e11 --- /dev/null +++ b/Legal_Notices_2.md @@ -0,0 +1,29 @@ +# Legal Notices + +Source: https://docs.rubrik.com/en-us/saas/reuse/notices.html + +--- + +# Legal Notices + +## Copyright + +Copyright © 2025 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. + +## Data Security Posture Legal Notices + +By using the Data Security Posture application, you understand and acknowledge that the pre-existing Policies and Analyzers of Data Security Posture contain general suggestions for data elements and formats based on common data sets and formats. The suggested data elements and formats in Data Security Posture 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 Data Security Posture search results will include every instance of each data element and format within your data set. We strongly recommend that you consult legal counsel for specific advice regarding compliance with applicable laws and regulations. + +Data Security Posture 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. diff --git a/Polaris_to_RSC_upgrade_1.md b/Polaris_to_RSC_upgrade_1.md new file mode 100644 index 0000000000000000000000000000000000000000..6bc8dac2cde1c1dfeb728471ed3058f31e29113a --- /dev/null +++ b/Polaris_to_RSC_upgrade_1.md @@ -0,0 +1,28 @@ +# Polaris to RSC upgrade + +Source: https://docs.rubrik.com/en-us/saas/install/upgrade_to_rubrik_security_cloud.html + +--- + +# Polaris to RSC upgrade + +Rubrik Security Cloud provides a unified user interface to manage all your Rubrik tasks. + +Upgrading to Rubrik Security Cloud (RSC) provides: + + * Global dashboard for an overview of data health and security + * Data Security Command Center (DSCC) to identify security gaps and provide recommendations for improving data security status + * Cluster dashboard offering meaningful insights into individual cluster health + * Unified user interface for managing all data center, cloud, and SaaS workloads + * Global search capability across RSC + * Ability to create and schedule custom reports or use predefined reports + +When you login to the Polaris web UI, a dialog box appears on the screen, prompting you to upgrade to the RSC experience. The upgrade dialog box provides an overview of the RSC upgrade and its capabilities. The dialog box does not prevent you from performing any operations. To learn more about the upgrade, you can watch the overview video or refer to the RSC upgrade documentation. + +The RSC upgrade is instantaneous and does not need any scheduled downtime. Rubrik cluster backups will continue as configured. Once upgraded, you can use RSC for daily operations. You can also upgrade SLA Domains created on a Rubrik cluster to RSC SLA Domains as required for centralized management. + +Limitations of RSC management are as follows: + + * Configuring the two-person rule (TPR) for changes or actions cannot be completed using RSC. These actions require Rubrik CDM workflows. + * Adding NAS systems managed in Rubrik CDM to RSC will trigger a new full backup and cause duplicate data protection of the NAS system. You can add the NAS host to RSC when the storage overhead is acceptable or continue to manage NAS hosts using Rubrik CDM. + diff --git a/Quarantine_overview_1.md b/Quarantine_overview_1.md new file mode 100644 index 0000000000000000000000000000000000000000..8af87cfaf23d1d85ed3c3bde3f68d36367674119 --- /dev/null +++ b/Quarantine_overview_1.md @@ -0,0 +1,59 @@ +# Quarantine overview + +Source: https://docs.rubrik.com/en-us/saas/saas/quarantine.html + +--- + +# Quarantine overview + +The Quarantine feature in Data Threat Analytics isolates potentially malicious files or objects to allow seamless data recovery and to avoid reinfection. + +Data recovery risks restoring malware, ransomware, or other unwanted applications. To restore data rapidly without compromising the recovered systems, you must: + + * Restore to a pre-malware infection state. + * Restore only uninfected files. + +By quarantining the snapshots that contain malware, you can quickly isolate potentially malicious files and identify healthy snapshots to use for performing a full system restore. + +## Quarantine operation and file version + +When you quarantine a file from a threat hunt or Threat Monitoring match, the system creates a quarantine operation. A quarantine operation is expressed as the unique combination of the object, file path, and file version. This operation fundamentally blocks the recovery of a specific file version. The file version is defined by its modification time (MTime). The MTime is a unique metadata stamp that records the exact date and time the file was last modified on the source object. This precision ensures you block the recovery of the specific malicious content that existed at that exact point in time. + +The quarantine operation applies to that specific file version across all existing and future snapshots for that object, including any replica and archival copies. This is the recommended behavior, as the operation uses file version metadata to automatically apply the quarantine to all current and future snapshots. If the file is modified and its MTime changes, the new version is not covered by the original operation. + +Note: + +In some cases, if the file version information is unavailable, such as with older Threat Monitoring matches or a threat hunt performed on Rubrik clusters running a version earlier than 9.2.3, the system will fall back to a limited quarantine scope that only affects the specific snapshots where the match was detected. To initiate the recommended full-scope quarantine for such a file, run a new threat hunt on the object to ensure the necessary file version metadata is populated, and then quarantine the file again. + +## Quarantine processing and recovery restrictions + +It is important to understand the following concepts regarding the quarantine mechanism and their impact on recovery: + + * Quarantine scope: Quarantining a file implicitly quarantines the file path and the snapshot. The operation applies to all snapshots, including future snapshots of the object that contain the relevant file path and version. + * Quarantine processing: When an object has active quarantine operations, RSC processes every snapshot to determine if the relevant file version exists. Until this process is complete, the snapshot is marked as Quarantine processing. Recovery is automatically blocked for any snapshot in this state. + +Snapshots are marked as Quarantine processing in two primary cases: + + * When a new snapshot first arrives at RSC, if the associated object has any active quarantine operations. Processing of the new snapshot usually completes in seconds to minutes, but can take up to 30 minutes in certain conditions. + * When a new quarantine operation or a remove from quarantine operation is applied to the object. All snapshots are temporarily reset to the Quarantine processing status and reprocessed. Processing of all affected snapshots usually completes in seconds to minutes, but can take up to 30 minutes in certain conditions. + +Recovery block: Quarantining a file or object blocks all image-level recovery options for the affected snapshot, including Live Mount, Export, and Instant Recovery. The following exceptions apply: + + * Exception for forensics: The quarantined data remains accessible for security operations only by using the password-protected Download for Forensics feature. + * RBAC override: This recovery block is automatically bypassed for users who have the Recover From Quarantine RBAC permission. + +## Supported workloads + +RSC supports quarantining on the following objects: + + * VMware virtual machines + * Linux filesets + * Windows filesets + * Nutanix AHV virtual machines + * Hyper-V virtual machines + * Volume groups + * NAS filesets + * Kubernetes virtual machines + * Kubernetes protection sets + +Using the Quarantine feature requires access to the Data Protection dashboard, the Data Threat Analytics dashboard, and either the threat hunt or Threat Monitoring feature. For detailed instructions on how to configure user permissions, refer to the [RBAC Permissions for Quarantine](rbac_permissions_for_quarantine.html "RBAC privileges are required to remove files or objects from quarantine, bypass quarantine, and download files for forensic analysis.") topic. diff --git a/Quarantining_matched_files_or_objects_1.md b/Quarantining_matched_files_or_objects_1.md new file mode 100644 index 0000000000000000000000000000000000000000..11b0e4098507152d6d0edd1151c8e85c4b375ef4 --- /dev/null +++ b/Quarantining_matched_files_or_objects_1.md @@ -0,0 +1,45 @@ +# Quarantining matched files or objects + +Source: https://docs.rubrik.com/en-us/saas/saas/quarantining_matched_objects_or_files.html + +--- + +# Quarantining matched files or objects + +Quarantine a matched file or object indicated in a threat hunt to separate potentially malicious objects or files before proceeding with recovery. + +## Before you begin + +Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click the threat hunt of interest. + +Quarantined objects are listed with details of their location, files matched, and match type. + + 5. **Optional:** Click an object to view the files in that object. + 6. Select items at the object or file level and click Quarantine. + +Matched files are quarantined only on the snapshots where they were matched in the threat hunt and cannot be recovered. When the file exists in a previous or later snapshot, it might still be recoverable. + +Quarantining a file implicitly quarantines the snapshot. Snapshots with a matched file have limited recovery options unless they are removed from quarantine. + +The Quarantine Objects wizard shows the files selected for quarantine. + + 7. In the Quarantine Objects wizard, click Quarantine. + +When the total request size exceeds the limit, you can make further selections on a subsequent request. + +## Results + +RSC quarantines the file and provides no recovery options in any quarantined snapshot until the file is removed from quarantine. Users with the Recover From Quarantine permission can still download the file for forensics or perform image-level recovery options for the snapshot. diff --git a/RBAC_privileges_for_quarantine_1.md b/RBAC_privileges_for_quarantine_1.md new file mode 100644 index 0000000000000000000000000000000000000000..0141fa70b665a328d9babda48dba2d93f45a6e15 --- /dev/null +++ b/RBAC_privileges_for_quarantine_1.md @@ -0,0 +1,28 @@ +# RBAC privileges for quarantine + +Source: https://docs.rubrik.com/en-us/saas/saas/rbac_permissions_for_quarantine.html + +--- + +# RBAC privileges for quarantine + +RBAC privileges are required to remove files or objects from quarantine, bypass quarantine, and download files for forensic analysis. + +All Data Threat Analytics users can view quarantined objects and files. Additional threat containment privileges are required to: + + * Add files to quarantine and remove files from quarantine + * Bypass quarantine and continue with recovery, and download for forensics + +You can assign additional threat containment privileges from the Users and Roles page. The administrator and owner roles are assigned these privileges by default. You can also assign these additional privileges to custom roles. + +Privilege | Description +---|--- +Add files to quarantine and remove files from quarantine | Users with this privilege can add files to quarantine and remove files from quarantine. The administrator and owner roles are assigned this privilege by default and this privilege can also be assigned to custom roles. +Recover quarantined files and snapshots | Users with this privilege can bypass quarantine and perform most recoveries for: + + * Image-level recoveries such as Live Mount, Export, and Instant Recovery + * File-level recoveries from the Hunts page + +Users can only download quarantined files or folders containing quarantined files. Other file recovery options are not available for quarantined files. + +All users with permission to view a workload in the Data Protection room can view the snapshots quarantined for that workload, as well as the files quarantined in a particular snapshot, in the Data Protection object details page. diff --git a/RSC_Data_Threat_Analytics_1.md b/RSC_Data_Threat_Analytics_1.md new file mode 100644 index 0000000000000000000000000000000000000000..a733dce8dab6057f34e187992ce626289e421428 --- /dev/null +++ b/RSC_Data_Threat_Analytics_1.md @@ -0,0 +1,17 @@ +# RSC Data Threat Analytics + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_ransomware_monitoring.html + +--- + +# RSC Data Threat Analytics + +RSC Data Threat Analytics provides Anomaly Detection and data recovery services on protected resources. + +Data Threat Analytics comprises Anomaly Detection, Threat Monitoring, Threat Hunting, and data recovery services on protected resources. + +Anomaly Detection identifies and analyzes anomaly events that can indicate a ransomware attack. When an attack is discovered, you can use Anomaly Detection to directly recover the original data. Anomaly Detection works in combination with other data security methods to provide an additional layer of protection. + +For each protected object, Anomaly Detection captures the changes in file system behavior and file content behavior that occur between snapshots. Anomaly Detection analyzes this information and provides a view of the changed behavior and changed content over time, when an incident has occurred. RSC retains the history of the metadata tracked by Data Threat Analytics for 30 days. + +Anomaly Detection does not support deep scanning for encryption for NAS Direct Archive. diff --git a/RSC_Orchestrated_Application_Recovery_1.md b/RSC_Orchestrated_Application_Recovery_1.md new file mode 100644 index 0000000000000000000000000000000000000000..0e6d7c23507bda147c9e31757ee5e14208f147d0 --- /dev/null +++ b/RSC_Orchestrated_Application_Recovery_1.md @@ -0,0 +1,32 @@ +# RSC Orchestrated Application Recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/oar.html + +--- + +# RSC Orchestrated Application Recovery + +The Orchestrated Application Recovery feature automates end-to-end recovery as well as disaster recovery and application migration from an on-premises data center to a secondary recovery site. + +Orchestrated Recovery uses Recovery Plans to group virtual machines for proactive testing and reporting and for production recovery situations. RSC creates Recovery Plans for a group of virtual machines and their associated target resource specifications for recovery. Orchestrated Recovery options to recover objects using a Recovery Plan include the following: + + * Disaster recovery + * Cyber recovery + * In-place recovery + +You can also initiate a cyber recovery as needed without a Recovery Plan by using the Cyber Recovery wizard. + +Orchestrated Recovery supports the following recovery types. You can filter for a recovery point based on Anomaly Detection and Quarantine results. + +You can use Orchestrated Recovery for the following workloads: + + * VMware virtual machines + * AHV virtual machines + * Azure virtual machines + +Only Cyber recovery is available for Azure virtual machines. + + * AWS EC2 instances + +Only Cyber recovery is available for AWS EC2 instances. + diff --git a/Removing_a_quarantined_file_or_object_1.md b/Removing_a_quarantined_file_or_object_1.md new file mode 100644 index 0000000000000000000000000000000000000000..c66202f561f34653ac2cd45f4ae5e873288d4abc --- /dev/null +++ b/Removing_a_quarantined_file_or_object_1.md @@ -0,0 +1,44 @@ +# Removing a quarantined file or object + +Source: https://docs.rubrik.com/en-us/saas/saas/removing_quarantined_file_or_object.html + +--- + +# Removing a quarantined file or object + +Remove a quarantined file or object to make it available for recovery. + +## Before you begin + +Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click the threat hunt of interest. + +When added to quarantine, the quarantined objects are listed with details of the location, files matched, and match type. + + 5. **Optional:** Click an object to view the files in that object. + 6. Select items for quarantining at the object or file level. + 7. Click select Remove from Quarantine. + +Releasing the selected files from quarantine removes the restrictions placed on those files. All matched snapshots in the threat hunt that contain the selected files then have full recovery options. + +The Remove from Quarantine wizard shows the files you selected for removal from quarantine. + + 8. In the Remove from Quarantine wizard, enter `REMOVE` to confirm and then click Remove. + +When the total request size exceeds the limit, you can make further selections on a subsequent request. + +## Results + +RSC removes the selected objects from quarantine and makes the object available for recovery. diff --git a/Rubrik_CDM_software_upgrade_1.md b/Rubrik_CDM_software_upgrade_1.md new file mode 100644 index 0000000000000000000000000000000000000000..125832bab489e1cc7f1d0c3a4c0f5ce3f5de7631 --- /dev/null +++ b/Rubrik_CDM_software_upgrade_1.md @@ -0,0 +1,36 @@ +# Rubrik CDM software upgrade + +Source: https://docs.rubrik.com/en-us/saas/saas/rbk_cdm_software_upgrade.html + +--- + +# Rubrik CDM software upgrade + +To take advantage of the latest features and improvements, you can upgrade your Rubrik CDM software running on your Rubrik clusters to the latest version. + +An upgrade is an operation for updating an older software version to a newer version, representing significant changes or improvements. Rubrik CDM software upgrades offer considerable changes and new functionality over previous versions, effectively superseding them. + +Some key advantages of upgrading your Rubrik CDM software to the latest version are as follows: + + * Maintaining business continuity and preventing unnecessary failures. + * Benefiting from essential security updates, new features, and integration with current technology trends and advancements, giving your business a competitive advantage. + * Safeguarding your systems and applications from viruses, spyware, and other malicious software that can harm or steal data or cause lengthy delays in problem resolution. + * Enhancing the quality of user experiences. + +If you are considering upgrading your Rubrik CDM software, Rubrik recommends that you evaluate the latest version available. Rubrik maintains a comprehensive Compatibility Matrix document that outlines which systems, protocols, and interfaces are supported for each product release. You can also check the Release Notes for the latest CDM software version to learn about new features, enhancements, and resolved issues. This way, you can ensure you are making the best choice for your needs. + +Rubrik follows the N-2 lifecycle policy, which supports the three most recent major releases (N, N-1, and N-2) of Rubrik CDM software. Each major release comes with a minimum support duration of 18 months. The Rubrik CDM Software Support Lifecycle documentation provides more information about the lifecycle policy. + +The Rubrik CDM Upgrades page provides all the information you need to make an informed decision about upgrading the CDM software. Some critical pieces of information you can gather include: + + * Checking the installed CDM software versions for your Rubrik clusters. + * Opening the Rubrik CDM Releases table to view details about the major release, its release notes, release adoption, release dates, latest minor release, Rubrik CDM software support policy, and Compatibility Matrix documentation. + +After you have decided to upgrade the Rubrik CDM software, you need to consider: + + * Choosing between a rolling upgrade and a fast upgrade. + * Reviewing the list of prerequisites and prechecks for your chosen upgrade type and ensuring you fulfill them for a successful upgrade. + * Selecting RSC or Rubrik CLI to perform the upgrade. + +Rubrik does not support using CLI commands to upgrade Rubrik clusters to the Rubrik CDM software version 9.0 or later. + diff --git a/Rubrik_MFA_with_TOTP_1.md b/Rubrik_MFA_with_TOTP_1.md new file mode 100644 index 0000000000000000000000000000000000000000..aabdb2df3282c7ddb2c98aceaf8132d805f4623a --- /dev/null +++ b/Rubrik_MFA_with_TOTP_1.md @@ -0,0 +1,17 @@ +# Rubrik MFA with TOTP + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_rmfa_totp.html + +--- + +# Rubrik MFA with TOTP + +The Rubrik two-step verification feature uses time-based one-time passwords in addition to the user login credentials to enforce multi-factor authentication on user accounts. + +Rubrik two-step verification is an implementation of 2FA for Rubrik Security Cloud (RSC). You can enable Rubrik two-step verification to use 2FA mediated by time-based one-time password (TOTP), which provides an additional layer of authentication security. By using TOTP, Rubrik enforces multi-factor authentication (MFA) with the help of a single-use numeric code in addition to your login credentials. You can use an application running on your personal device, for example a smart phone, to generate the single-use numeric code. Rubrik two-step verification works with any TOTP application that complies with RFC 6238. + +MFA enforcement is mandatory for all local RSC user accounts. Administrators must enforce Rubrik two-step verification for users at the global level. When enforced, each user must configure Rubrik two-step verification on an individual basis. + +Note: + +MFA enforcement does not impact user accounts authenticated through SAML-based SSO authentication providers. diff --git a/Rubrik_Security_Cloud_-_Offline_Recovery_1.md b/Rubrik_Security_Cloud_-_Offline_Recovery_1.md new file mode 100644 index 0000000000000000000000000000000000000000..75f1ecfe2879472a06d15f283faaaf3f85de3df3 --- /dev/null +++ b/Rubrik_Security_Cloud_-_Offline_Recovery_1.md @@ -0,0 +1,283 @@ +# Rubrik Security Cloud - Offline Recovery + +Source: https://docs.rubrik.com/en-us/latest/offrec/index.html + +--- + +[Rubrik CDM offline recovery](offrec/rubrik_offrec_or.html) + +In the unlikely event of a service disruption between the Rubrik cluster and RSC, Rubrik CDM version 9.2 and later can switch between running in recovery mode and in fully functional, read-write mode. + +[Logging in to Rubrik cluster](offrec/logging_in_off_rec.html) + +Log in to Rubrik cluster to recover workloads when RSC is + +[Logging out of the Rubrik cluster](offrec/logging_out_rsc_offrec_or.html) + +Log out of the Rubrik cluster. + +[Live Mounts in the Rubrik cluster](offrec/live_mounts_offrec.html) + +The Rubrik cluster displays a list of Live Mounts that are available for workload recovery. + +[The Rubrik cluster Events page](offrec/offrec_events_page.html) + +The Events page displays the events of the Rubrik cluster. + +[Viewing the Rubrik cluster inventory](offrec/viewing_rsc_offline_recovery_inventory.html) + +View the workloads inventory included with the Rubrik cluster. + +[SMB security in the Rubrik cluster](offrec/smb_security_or.html) + +With the SMB security, the Rubrik cluster provides security for SMB shares by requiring Active Directory authentication and enforcing SMB security. + +[Cyber Event Lockdown in Rubrik cluster](offrec/cyber_event_lockdown_or.html) + +When a suspected cyber attack, ransomware attack, or other event affecting data integrity impacts your environment, you can use Cyber Event Lockdown on the Rubrik cluster to protect the data. + +[Cluster details page in the Rubrik cluster](offrec/cluster_details_page_or.html) + +Information about Rubrik clusters and their configurations. + +[Viewing the cluster settings in the Rubrik cluster](offrec/viewing_the_cluster_settings.html) + +View the cluster settings for the Rubrik cluster. + +[Changing the cluster settings in the Rubrik cluster](offrec/changingl_cluster_settings.html) + +Change the general cluster settings for the Rubrik cluster. + +[Changing the network settings in the Rubrik cluster](offrec/changing_network_settings.html) + +Change the network settings for the Rubrik cluster. + +[Adding an NTP server to a Rubrik cluster](offrec/adding_ntp_server_cdm.html) + +Add an NTP server to the Rubrik cluster for network time synchronization. + +[Adding a VLAN to a Rubrik cluster](offrec/adding_vlan_cdm.html) + +Add a VLAN to the Rubrik cluster for a logical segmentation of networks. + +[Deleting a VLAN from a Rubrik cluster](offrec/deleting_vlans_offrec_or.html) + +Delete a VLAN if multiple VLANs are associated with a Rubrik cluster. + +[Pause and resume protection activity](offrec/pause_protection_activity_or.html) + +When you are performing maintenance activities on a Rubrik cluster, you can temporarily pause the protection activity and then resume it by using the pause and resume protection activity feature. + +[Support tunnel for Rubrik cluster](offrec/support_tunnels_or.html) + +Support tunnel allows authorized Rubrik Support engineers to gain secure, logged access to Rubrik clusters for diagnosis and resolution of hardware and software issues. + +[Checking RSC connectivity](offrec/checking_rsc_connectivity.html) + +Check the connectivity between RSC and the Rubrik cluster. + +[Creating a support bundle on Rubrik cluster](offrec/creating_a_support_bundle.html) + +Create a support bundle that Rubrik Support can use to evaluate any issues that occur during offline workload recovery. + +[Adding a static route in Rubrik cluster](offrec/adding_routing_table_cluster_or.html) + +Add a static route for a network destination in Rubrik cluster with other network details such as netmask, gateway, and interface for efficient network routing and better performance. + +[Deleting a static route from the Rubrik cluster](offrec/deleting_static_route_cluster_or.html) + +Delete an unnecessary static route from the routing table on Rubrik cluster. + +[Node Management](offrec/node_management_or.html) + +You can use Rubrik cluster to optimize the performance of the cluster nodes by adding nodes and setting up or removing disks. + +[Rubrik cluster workloads](offrec/offrec_workloads.html) + +Rubrik cluster securely manages and protects data from a wide variety of workload types. + +[File systems](offrec/filesystems/fs_filesystems_or.html) + +Rubrik cluster provides management and protection of file system data on supported Linux, Unix, and Windows hosts through filesets. + +[SQL Server databases](offrec/mssql/sql_server_databases_or.html) + +A Rubrik cluster provides data management and protection for Microsoft SQL Server databases. + +[AHV virtual machines](offrec/nutanix_ahv/virtual_machines_or.html) + +Rubrik cluster provides data management and protection for virtual machines deployed in a Nutanix Acropolis environment. + +[Managed Volumes and SLA Managed Volumes](offrec/managed_volumes/mv_managed_volumes_sla_managed_volumes_or.html) + +Managed Volumes in Rubrik cluster protect and manage data while SLA Managed Volumes schedule and initiate backups using an SLA Domain. + +[On-premises Active Directory](offrec/on_prem_ad/on_prem_active_directory_or.html) + +You can protect and recover on-premises Active Directory domains by using the protection services offered by Rubrik cluster. + +[NAS systems on Rubrik cluster](offrec/nas/nas_systems_or.html) + +Rubrik cluster manages and protects NFS and SMB shares on NAS systems for efficient data storage and retrieval. + +[Oracle databases on Rubrik cluster](offrec/oracle/oracle_databases_rsc_or.html) + +You an use Rubrik cluster to back up, archive, replicate, and recover Oracle databases. + +[VMware Cloud Director vApps](offrec/vcd/vmware_cloud_director_vapps_or.html) + +The Rubrik cluster provides SLA Domain protection and data management for VMware Cloud Director vApps. + +[Hyper-V virtual machines](offrec/hyper_v/hyperv_vm_or.html) + +The Rubrik cluster provides data management and protection for virtual machines that are deployed in a Microsoft Hyper-V environment. the Rubrik cluster can manage and protect virtual machines in an environment with multiple Hyper-V servers and virtual machines. + +[vSphere virtual machines](offrec/vsphere/vs_virtual_machines_or.html) + +Rubrik cluster provides data management and SLA Domain protection for virtual machines that are deployed in a VMware vSphere environment. + +[vCenter management](offrec/vsphere/vs_vcenter_management_or.html) + +The Rubrik cluster accesses virtual machine data through a connection with the VMware vCenter Server that manages the hypervisor running the virtual machine. + +[Windows volume groups](offrec/wvg/windows_volume_groups_or.html) + +A volume group is a Rubrik workload comprised of at least one data storage volume on a Windows host. + +[Archiving of data center workloads](offrec/archival/arch_dc_workloads_or.html) + +With a Rubrik cluster, you can recover your data from your data center archival locations in the event of a disaster or cyber event. + +[Archival Locations](offrec/archival/arch_loc_page_or.html) + +The Archival Locations page provides summary information about existing archival locations on the Rubrik cluster. + +[Connecting as a reader to the Rubrik cluster archival location](offrec/conn_as_reader_or_arch_loc.html) + +Connect to an Rubrik cluster archival location as a reader to recover snapshot data. + +[Disaster recovery using an archival location](offrec/archival/disaster_rec_using_arch_loc_or.html) + +Rubrik CDM supports recovering data from an existing archival location using a different Rubrik cluster than the Rubrik cluster that archived the data. + +[Azure archival locations](offrec/archival/arch_azure_or.html) + +With Rubrik cluster, you can connect as a reader to an existing Azure archival storage to read existing data to perform a recovery during a service disruption. The Azure archival storage was previously configured from a different Rubrik cluster. + +[Amazon S3 archival locations](offrec/archival/arch_amazon_s3_or.html) + +With Rubrik cluster, you can connect as a reader to an existing Azure archival storage to read existing data to perform a recovery during a service disruption. The Amazon S3 archival storage was previously configured from a different Rubrik cluster. + +[Google Cloud Platform archival locations](offrec/archival/arch_gcp_or.html) + +With the Rubrik cluster, you can connect as a reader to an existing Azure archival storage to read existing data to perform a recovery during a service disruption. The Google Cloud Platform archival storage was previously configured from a different Rubrik cluster. + +[NFS archival locations](offrec/archival/nfs_arch_loc_or.html) + +An NFS archival location is storage on an NFS server where you can archive snapshots from your Rubrik cluster. You must identify a specific location on the NFS server to serve as the archival location. + +[Object Store archival locations](offrec/archival/obj_store_archival_locations_or.html) + +With Rubrik cluster, you can connect as a reader to an existing Object Store archival storage configured from another cluster to read existing data to perform a recovery during a service disruption. + +[QStar tape archive](offrec/archival/archiving_qstar_tape_archive_or.html) + +QStar tape archive enables the Rubrik cluster to store data on tape for long-term retention and regulatory compliance using QStar Archive Manager on Windows servers. + +[User accounts for Rubrik cluster](offrec/security/security_or.html) + +Rubrik cluster provides RBAC and several methods for authenticating a user account. + +[Authentication for Rubrik cluster](offrec/security/cdm_authentication_or.html) + +The Rubrik cluster authenticates all login attempts. + +[Local authentication for Rubrik cluster](offrec/security/local_authentication_or.html) + +Local authentication methods control access to local accounts on the Rubrik cluster. + +[Roles for Rubrik cluster](offrec/security/roles_or.html) + +Roles help define privileges for user accounts on a Rubrik cluster. With the admin account, you can assign administrator roles that grant varying access permissions to user accounts for specific purposes. + +[Requirements for BIND user credentials for Rubrik cluster](offrec/security/requirements_for_bind_user_credentials_or.html) + +Rubrik CDM has specific requirements for BIND credentials. + +[LDAP authentication for Rubrik cluster](offrec/security/ldap_authentication_or.html) + +The Rubrik cluster uses LDAP to authenticate users who log in through the Rubrik cluster welcome screen. + +[Single Sign-on for Rubrik cluster](offrec/security/single_signon_or.html) + +Rubrik CDM supports single sign-on using the Security Assertion Markup Language 2.0 standard. + +[ADFS integration workflow for Rubrik cluster](offrec/security/cdm_adfs_integration_workflow_or.html) + +The workflow gives a high-level view of the tasks involved in configuring single sign-on with ADFS. + +[Okta integration workflow for Rubrik cluster](offrec/security/okta_sso_integration_workflow_or.html) + +The Okta integration workflow gives a high-level view of the tasks involved in configuring single sign-on with Okta. + +[Multifactor authentication for Rubrik cluster](offrec/security/multifactor_auth_or.html) + +Multifactor authentication is the practice of adding more factors to the basic authentication process. By using multifactor authentication, you can prevent unauthorized users from accessing your Rubrik clusters. + +[Certificate management for Rubrik cluster](offrec/security/certificate_management_or.html) + +Rubrik cluster Certificate Management provides a centralized dashboard to manage certificates for Rubrik cluster workflows. + +[Rubrik MFA with TOTP for Rubrik cluster](offrec/security/cdm_rmfa_totp_or.html) + +Rubrik MFA for Rubrik clusters uses time-based one-time passwords to provide secure authentication for local and LDAP users. Rubrik MFA does not apply for users authenticated via SAML-based SSO integrations. + +[CLI administrator role for Rubrik cluster](offrec/security/cli_administrator_role_or.html) + +As a CLI administrator, a Rubrik cluster user can connect to nodes in Rubrik clusters through the CLI SSH protocol. + +[Rubrik port specifications](ports/rubrik_port_specifications.html) + +Information about the ports that Rubrik clusters use. + +[Additional network requirements](ports/additional_network_requirement.html) + +To provide IPMI management information, Rubrik nodes must be able to receive packets sent from a local ping program. + +[Archiving ports](ports/archiving_ports.html) + +The Rubrik cluster requires a number of outbound ports for archiving. + +[Azure ports](ports/azure_ports.html) + +Configure the following ports for Azure virtual machines. + +[GCP ports](ports/gcp_ports.html) + +The Rubrik cluster requires specific ports to be configured for GCP virtual machines. + +[Kubernetes ports](ports/kubernetes_ports.html) + +The Rubrik cluster requires specific ports to be configured for Kubernetes clusters. + +[AWS ports](ports/aws_ports.html) + +The Rubrik cluster requires the following ports to be configured for AWS virtual machines. + +[Replication port information](ports/replication_port_information.html) + +Information about the assigned port number and behavior of the replication service. The replication service manages the incoming traffic for the Rubrik replication feature, which directs the management of replica snapshots or backups from a source Rubrik cluster to a target Rubrik cluster. + +[Legal Notices and additional resources](reuse/notices.html) + +Rubrik legal notices for this documentation, and topics with additional resources and information. + +[Legal Notices](reuse/notices.html) + +[Comments and suggestions](reuse/comments_suggestions.html) + +We welcome your comments and suggestions about our products and our product documentation. + +[Support](reuse/support.html) + +Use one of the following methods to contact Rubrik Support. diff --git a/Rubrik_Security_Cloud_1.md b/Rubrik_Security_Cloud_1.md new file mode 100644 index 0000000000000000000000000000000000000000..26edc3f5bc299d47488a4c4b7b095500d06e09eb --- /dev/null +++ b/Rubrik_Security_Cloud_1.md @@ -0,0 +1,57 @@ +# Rubrik Security Cloud + +Source: https://docs.rubrik.com/en-us/saas/index.html + +--- + +[Setup](install/rsc_cluster_deployment.html) + +Rubrik CDM software can be installed on many different platforms, both physical and virtual. The software can run on a single node computer and on multiple node computing clusters. + +[Data Protection](saas/common/getting_started_with_rsc.html) + +Rubrik Security Cloud - Data Protection provides the core tools and features for protecting, managing, and analyzing your data. + +[Workloads](rubrik/supported_workloads.html) + +Rubrik Security Cloud - Data Protection securely manages and protects data from a wide variety of workload types. + +[Identity Resilience](identity_resilience/identity_resilience.html) + +Rubrik Identity Resilience is designed to protect, monitor, and recover identities, both human and non-human identities, in hybrid identity environments. + +[Data Threat Analytics](saas/ri_ransomware_monitoring.html) + +Rubrik Security Cloud Data Threat Analytics provides anomaly detection and data recovery services on protected resources such as VMware virtual machines, NAS, and Linux and Windows servers. + +[Data Security Posture](dspm/data_security_posture.html) + +Rubrik Security Cloud Data Security Posture enables organizations to find specific types of data within the data that has been indexed by Rubrik clusters. + +[Annapurna](ai/annapurna.html) + +Annapurna is an enterprise application for querying your protected data. It allows you to create custom chatbots that use advanced language models and retrieval-augmented generation to answer natural language questions about your data. + +[Orchestrated Application Recovery](saas/oar.html) + +Rubrik Security Cloud Orchestrated Application Recovery provides disaster recovery and application migration from an on-premises data center to a secondary recovery site. + +[Ruby](saas-ai/ruby_2.html) + +Ruby is an AI assistant designed to help you ask natural language questions to better understand and use Rubrik Security Cloud. + +[GraphQL API Playground](gql/api_playground_2.html) + +The API Playground is a tool that allows you to browse, explore, and run the GraphQL APIs of Rubrik Security Cloud. + +[Offline Recovery](https://docs.rubrik.com/en-us/latest/offrec/index.html) + +In the unlikely event that you cannot connect to Rubrik Security Cloud, you can use the offline recovery UI on your Rubrik clusters to perform basic recovery and maintenance. + +[Legal Notices and additional resources](reuse/notices.html) + +Rubrik legal notices for this documentation, and topics with additional resources and information. + +[Comments and suggestions](reuse/comments_suggestions.html) + +We welcome your comments and suggestions about our products and our product documentation. diff --git a/Rubrik_Security_Cloud_service_types_1.md b/Rubrik_Security_Cloud_service_types_1.md new file mode 100644 index 0000000000000000000000000000000000000000..8870139a8d9cae4c1ccf9aaac602a4ee7cb5d8b8 --- /dev/null +++ b/Rubrik_Security_Cloud_service_types_1.md @@ -0,0 +1,17 @@ +# Rubrik Security Cloud service types + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_service_types.html + +--- + +# Rubrik Security Cloud service types + +Rubrik Security Cloud offers two distinct service types, SaaS mode and software mode, which provide different sets of functionality. + +Rubrik Security Cloud (RSC) can be configured in SaaS mode or software mode. + +RSC in SaaS mode provides many benefits through a unified control plane across multiple Rubrik clusters. The benefits of SaaS mode include a common UI, security layer and RBAC, common policy management, and reporting. Rubrik Security Cloud in SaaS mode cannot be converted to the software mode. + +If Rubrik Security Cloud becomes temporarily unavailable, the Rubrik cluster UI offers a recovery mode to handle critical tasks such as restoring data from a backup. + +RSC in software mode provides standalone, on-premises access to Rubrik CDM for data protection and recovery. The software mode uses appliances provided by Rubrik or selected compatible hardware. RSC in software mode provides a UI on the Rubrik cluster for your management tasks. diff --git a/Rubrik_Security_Cloud_workloads_1.md b/Rubrik_Security_Cloud_workloads_1.md new file mode 100644 index 0000000000000000000000000000000000000000..4f33a208ce88427241454a16e1ca32bdfb2acfe8 --- /dev/null +++ b/Rubrik_Security_Cloud_workloads_1.md @@ -0,0 +1,47 @@ +# Rubrik Security Cloud workloads + +Source: https://docs.rubrik.com/en-us/saas/rubrik/supported_workloads.html + +--- + +# Rubrik Security Cloud workloads + +RSC securely manages and protects data from a wide variety of workload types. + +Supported workload types: + + * [Active Directory forest](../adds/active_directory_forest.html "Rubrik Security Cloud offers protection services for the Active Directory forest hierarchy. You can protect and recover the entire forest hierarchy in the event of a disaster or ransomware attack.") + * [Active Directory domains and domain controllers](../adds/active_directory_domain_dc.html "You can protect and recover Active Directory domains and domain controllers by using the protection services offered by Rubrik Security Cloud.") + * [AHV virtual machines](../nutanix_ahv/ahv_virtual_machines.html "RSC provides data management and protection for virtual machines deployed in a Nutanix Acropolis environment.") + * [Amazon Web Services workloads](../saas/aws_workloads.html "RSC protects the following types of Amazon Web Services workloads: EC2 instances, EBS volumes, Amazon S3, Amazon RDS and Aurora databases, and Amazon DynamoDB.") + * [Azure DevOps](../azure_devops/azr_devops.html "RSC protects the data and resources of Azure DevOps projects and repositories within the Azure DevOps organization.") + * [Atlassian Jira](../jira/jira.html "To protect your Atlassian Jira data, you can back up and restore data, such as projects, settings, workflows, and issues, in your Jira site .") + * [File systems](../saas/fs_filesystems.html "RSC provides management and protection of file system data on supported Linux, Unix, and Windows hosts through filesets.") + * [Google Cloud Platform workloads](../gcp/gcp.html "RSC protects the following types of Google Cloud Platform workloads: Google Compute Engine instances and persistent disks.") + * [Hyper-V virtual machines](../saas/hyper_v/hyperv_virtual_machines.html "A Rubrik cluster provides data management and protection for virtual machines that are deployed in a Microsoft Hyper-V environment. The Rubrik cluster can manage and protect virtual machines in an environment with multiple Hyper-V servers and virtual machines.") + * [IBM Db2](../db2/ibm_db2.html "With IBM Db2 workloads, you can automate complex tasks such as database discovery and data protection for managing databases.") + * [Kubernetes protection](../kubernetes/k8s_workload_protection.html "You can use Kubernetes protection to protect your on-premise or cloud-native Kubernetes clusters using a protection set.") + * [Managed Volumes and SLA Managed Volumes](../managedvolumes/mv_managed_volumes_sla_managed_volumes.html "Managed Volumes in RSC protect and manage data while SLA Managed Volumes schedule and initiate backups using an SLA Domain.") + * [Microsoft Azure workloads](../saas/azr_workloads.html "RSC protects the data and resources of Azure virtual machines, Azure managed disks, Azure Blob Storage, and Azure SQL workloads in Azure subscriptions.") + * [Microsoft 365](../saas/m365.html "Using the data management and protection services offered by Rubrik Security Cloud, you can protect Microsoft 365 data operations.") + * [Microsoft 365 Backup Storage](../m365_backup_storage/m365_backup_storage.html "With the Microsoft 365 Backup Storage feature, you can back up Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. You can also restore large volumes of data during ransomware attacks, accidental deletion, or malicious data deletion and overwrite events.") + * [Microsoft Dynamics 365](../microsoft_dynamics_365/microsoft_dynamics_365.html "RSC protects the tables and metadata in your Microsoft Dynamics 365 subscription.") + * [Microsoft Entra ID](../saas/ms_entra_id.html "RSC supports backup and recovery of Microsoft Entra ID.") + * [Microsoft Exchange Server](../saas/ms_exchange_server.html "Rubrik Security Cloud provides protection for Microsoft Exchange Servers.") + * [MongoDB workloads](../mongodb/mongodb_workloads.html "Rubrik Security Cloud protects your MongoDB sources, databases, and collections, ensuring optimal storage efficiency and smooth database operations with its advanced security features and strong data protection.") + * [MySQL](../mysql/mysql.html "RSC protects the MySQL databases from accidental deletions, ransomware attacks, and other potential threats.") + * [NAS CD data sets](../saas/ncd_data_sets.html "Rubrik NAS Cloud Direct offers secure data protection with high-performance, scalable enterprise backup, and archive services for unstructured file data.") + * [NAS systems](../nas/nas_systems.html "RSC manages and protects NFS and SMB shares on NAS systems for efficient data storage and retrieval.") + * [Okta IdP](../okta/okta_idp.html "Rubrik Security Cloud provides protection and recovery for Okta Identity Provider objects. By integrating your Okta tenant with Rubrik, you can leverage a comprehensive set of data protection features designed for security, simplicity, and reliability.") + * [Oracle databases](../oracle/oracle_databases_rsc.html "You can use RSC to back up, archive, replicate, and recover Oracle databases.") + * [OpenStack virtual machines](../openstack/openstack_virtual_machines.html "RSC provides data management, SLA Domain protection, and recovery for OpenStack virtual machines.") + * [PostgreSQL](../postgresql/postgresql.html "Rubrik Security Cloud protects your PostgreSQL cluster by simplifying complex backup and recovery processes, discovering the databases automatically, and protecting data using SLA Domains.") + * [Salesforce Data Protection](../salesforce/salesforce_management.html "Salesforce Data Protection is a Rubrik-hosted SaaS service that extends RSC by securely backing up your critical Salesforce data and metadata for standard and custom objects.") + * [SAP HANA databases](../saas/sap_hana_protection.html "RSC enables administrators to implement backup policies on SAP HANA databases running on public clouds and on-premises.") + * [SnapMirror Cloud](../saas/snapmirror_cloud.html "RSC protects user data replicated by the NetApp SnapMirror Cloud service.") + * [Microsoft SQL Server databases](../common/sql_server_databases.html "A Rubrik cluster provides data management and protection for Microsoft SQL Server databases.") + * [VMware Cloud](../vmware_cloud/vmware_cloud.html "A Rubrik Cloud Cluster effectively protects virtual machines deployed on VMware Cloud on AWS, Microsoft Azure VMware Solution, and Google Cloud VMware Engine.") + * [vSphere virtual machines](../saas/vs_virtual_machines.html "Rubrik Security Cloud provides data management and SLA Domain protection for vSphere virtual machines, including vSphere VM templates that are managed either through a VMware vSphere environment or a content library.") + * [VMware Cloud Director vApps](../vcd/vmware_cloud_director_vapps.html "The Rubrik cluster provides SLA Domain protection and data management for VMware Cloud Director vApps.") + * [Windows volume groups](../saas/windows_volume_groups.html "A volume group is a Rubrik workload comprised of at least one data storage volume on a Windows host.") + diff --git a/Rubrik_cluster_deployment_1.md b/Rubrik_cluster_deployment_1.md new file mode 100644 index 0000000000000000000000000000000000000000..a692a519668a477dc43cd42beac29454c7375552 --- /dev/null +++ b/Rubrik_cluster_deployment_1.md @@ -0,0 +1,37 @@ +# Rubrik cluster deployment + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_deployment.html + +--- + +# Rubrik cluster deployment + +Deploying a Rubrik cluster running on Rubrik appliance nodes involves installing the CDM software on the nodes and setting up that software for your environment. + +## Appliance nodes + +Getting your Rubrik cluster up and running on Rubrik appliance nodes involves the following tasks: + + * Downloading and installing the Rubrik CDM software + * Setting up the Rubrik cluster + * Registering the Rubrik cluster + +Rubrik appliance nodes come with a recent version of the Rubrik CDM software already preloaded. Rubrik recommends that instead of running your Rubrik cluster with this factory loaded version, you consider downloading and installing the most recent GA version of the CDM software. By doing this you can avoid running multiple upgrades to get the cluster running the latest GA version. However, selecting a Rubrik CDM version that is not preloaded adds approximately 30 minutes to the setup process. + +Installing and configuring the Rubrik CDM software on a cluster usually involves running the configuration wizard from the UI provided by a node of the cluster. The wizard ensures that all nodes pass the pre-checks and meet the requirement of running the same version of Rubrik CDM before installing and configuring the software. + +When required, installing and configuring the software can also be done from the Rubrik CLI. + +After installing the software on all of your nodes, you perform the set up task. The set up task involves configuring each node to operate as part of a cluster. It also involves configuring the nodes with your network preferences. + +Your last step is registering the new Rubrik cluster. If your Rubrik cluster can connect to your Rubrik Security Cloud (RSC) domain, you can easily register your Rubrik cluster using a web browser. If your Rubrik cluster cannot connect to your RSC domain, you can use the offline method to register the cluster. + +## Other platforms + +Supported hardware other than the Rubrik appliance hardware is available from manufacturers such as Dell, Cisco, and Hewlett Packard Enterprise. Rubrik provides hardware-specific installation and configuration guides for each supported platform. These guides are available through the [Rubrik Support portal](https://support.rubrik.com/). + +The process of installing Rubrik CDM software on virtual instances such as Rubrik Edge, Rubrik Virtual Cluster, and Rubrik Cloud Cluster includes preparing the virtual hardware for those deployments. Rubrik provides documentation for each deployment type through the [Rubrik Support portal](https://support.rubrik.com/). + +## RSC association + +After the Rubrik cluster is successfully configured, you establish an association between the Rubrik cluster and Rubrik Security Cloud by registering the cluster using your RSC account. diff --git a/Ruby_2.md b/Ruby_2.md new file mode 100644 index 0000000000000000000000000000000000000000..c5ff13f34ea840457c66f48022266a7a6c623c04 --- /dev/null +++ b/Ruby_2.md @@ -0,0 +1,31 @@ +# Ruby + +Source: https://docs.rubrik.com/en-us/saas/saas-ai/ruby_2.html + +--- + +# Ruby + +Ruby is a generative AI assistant that extends Rubrik Security Cloud capabilities. You can interact with Ruby to use and manage RSC security features. + +Ruby is built on Microsoft Azure Open AI. This Rubrik partnership with Microsoft secures a private entry point into generative AI and ensures that your data remains private. Ruby uses Rubrik threat intelligence information based on machine learning to develop interactive workflows for data recovery during a security incident. + +Using RSC Data Threat Analytics, Data Security Posture, and Orchestrated Application Recovery, you can detect anomalies, uncover sensitive data, and identify and isolate threats in the environment. Ruby streamlines these multi-step workflows within RSC into a single process, allowing backup administrators to perform security-related tasks and collaborate with security teams. + +When Threat Monitoring detects an anomaly, you receive a security incident notification. Ruby is then available in the Notifications tab in the Inbox in RSC dashboards to guide you through an integrated and interactive message window. Ruby provides recommendations to remediate the security incident using Sensitive Data Monitoring, Threat Hunting, and Orchestrated Application Recovery. + +Ruby matches user intent to a defined workflow based on a pre-trained model. The Ruby workflow involves the following: + + * Viewing the threat details, including the indicators of compromise (IOCs), snapshot location, and time of the snapshot + * Searching for additional IOCs by using threat hunting + * Discovering the location of the sensitive data, including violations and the policies and objects impacted. For Microsoft 365 objects, you can also use Ruby to take remedial actions to address the issues identified. + * Quarantining snapshots that contain potentially malicious files or objects + * Creating Recovery Plans for data recovery + +While the notifications in the Inbox on the RSC dashboard are available to all users, Ruby only performs tasks for user accounts with the owner and administrator roles. Ruby recommends actions based on the RBAC permissions of the user account. Actions that do not correlate to user account permissions are not available. Ruby asks for user confirmation before proceeding with any recovery or quarantine action. The audit logs also indicate the user account that confirmed the specific actions performed using Ruby. + +Ruby is available as part of the Rubrik Enterprise edition. Enabling Ruby requires that Rubrik clusters are running CDM version 9.0.1 or later. For the threat detection and remediation use case, enabling Threat Monitoring is required. + +Note: + +Ruby is an AI assistant. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. diff --git a/System_shutdown_1.md b/System_shutdown_1.md new file mode 100644 index 0000000000000000000000000000000000000000..a7a99ec225ee9f24e8be45675dfab358818df872 --- /dev/null +++ b/System_shutdown_1.md @@ -0,0 +1,11 @@ +# System shutdown + +Source: https://docs.rubrik.com/en-us/saas/install/system_shutdown.html + +--- + +# System shutdown + +A system shutdown can be done from the Rubrik CLI. + +Typical operation of a Rubrik cluster does not require a system shutdown, but is occasionally necessary for business purposes or at the request of Rubrik Support. diff --git a/Threat_Monitoring_1.md b/Threat_Monitoring_1.md new file mode 100644 index 0000000000000000000000000000000000000000..d5d9dc60c95c722ddebd2495c7ec6b5285238c5e --- /dev/null +++ b/Threat_Monitoring_1.md @@ -0,0 +1,34 @@ +# Threat Monitoring + +Source: https://docs.rubrik.com/en-us/saas/saas/threat_monitoring.html + +--- + +# Threat Monitoring + +Threat Monitoring automatically and continuously scans snapshots for new and existing indicators of compromise, and provides visibility into potential threats. + +With an initial full scan at feature enablement, followed by incremental scans, Threat Monitoring scans snapshots for threats based on indicators of compromise (IOCs) from multiple threat intelligence sources. Threat Monitoring detects risk early by: + + * Identifying threat indicators within backups. + * Accelerating threat investigation. + * Reducing the threat duration and risk of reinfection during recovery. + +IOCs provide forensic evidence of potential intrusions on a host system or network. When enabled, Threat Monitoring automatically pushes a threat feed of Yet Another Recursive Acronym (YARA) rules and file hashes every 24 hours to all applicable Rubrik deployments. RSC uses a hash database created during backup indexing to perform the file hash scanning. After the threat feed is downloaded to the Rubrik cluster, subsequent Threat Monitoring jobs start YARA rule analysis using the threat feed details. The threat feed updates periodically to import new intelligence, as available, to identify threats. + +Threat Monitoring scans executable files in snapshots that are smaller than 15 MB in size. Threat Monitoring scans Windows files that have the following extensions: .acm, .ax, .bat, .cmd, .com, .cpl, .dll, .drv, .efi, .exe, .js, .jse, .msi, .mui, .ocx, .ps1, .psc1, .scr, .sys, .tsp, .vbe, .vbs, .wsf, and .wsh. Threat Monitoring scans only Linux files that have the executable bit set. + +Threat Monitoring uses two key detection methods: + + * YARA rule-based detection, which applies pattern-based analysis to identify potential threats, but does not rely on exact file-matching. As a result, YARA rules can sometimes generate false positives, detecting both malicious and benign files under the same logic. To maintain accuracy, RSC continuously monitors, reviews, and refines YARA rules, removing those that generate excessive false positives. + * Hash-based detection, which uses exact file-matching, ensuring high confidence in identifying known threats. + +Threat Monitoring uses only file hashes as IOCs to identify threats for Azure virtual machines and managed disks, Microsoft SharePoint and OneDrive objects, AWS EC2 instances and EBS volumes, and GCP GCE instances and persistent disks. For other workloads, Threat Monitoring supports monitoring with both YARA rules and file hashes as IOCs. + +For Rubrik clusters running CDM version 9.1.3-p2 and later, RSC offers the following capabilities: + + * Scanning using a full set of YARA rules and file hashes. + * File hash scanning using a hash database created during backup indexing. + * Incremental and full scanning of existing data. Incremental scans handle new data, while RSC performs full scans of existing data when IOC updates occur. For example, when hash IOCs are processed against the hash database and new YARA rules are applied to the last completed backups. + * Retroactively processing IOC updates, as well as up to 100 custom IOCs. + diff --git a/Threat_hunts_1.md b/Threat_hunts_1.md new file mode 100644 index 0000000000000000000000000000000000000000..bcf9c5da9b06ab2f94a03bf1216cb2f2968250a2 --- /dev/null +++ b/Threat_hunts_1.md @@ -0,0 +1,39 @@ +# Threat hunts + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_threat_hunts.html + +--- + +# Threat hunts + +On-demand threat hunts scan Rubrik backups for user-defined indicators of compromise and identify the systems potentially affected by an attack. + +When ransomware attacks happen, it is essential to respond quickly. Identifying which systems were compromised and when indicators of compromise (IOCs) were first present in those systems can be challenging. A threat hunt identifies files that might be at risk by scanning Rubrik backups to find when a compromise related to the attack occurred. + +Threat hunting is not a pattern-based anti-malware scanner, but an analysis tool for identifying specific IOCs. You can use threat hunt results to identify potentially malicious files and the snapshots in which they were present, avoiding malware reinfection during recovery. + +Threat hunting employs a full/incremental scanning method in which the initial scan is a full scan, but all subsequent scans are incremental. This reduces the number of files in subsequent scans and reduces the time to scan, optimizing the threat hunt. + +The presence of IOCs on a system indicates that malware might have compromised the system. You can configure threat hunts with the following key IOCs: + + * Yet Another Recursive Acronym (YARA) rules, which use scripts that look for certain characteristics to identify malware. YARA rules are available only for advanced threat hunts. + * File hashes, which use specific file hash values to search for malware (MD5, SHA1, or SHA256). + * File patterns, which use specific file paths to search for malware. File patterns are available only for advanced threat hunts. + +RSC limits the number of threat hunts it supports. For each 30-day period, the product of the number of threat hunts and the number of snapshots per threat hunt should be fewer than 10,000. + +Threat hunting is supported for the following workloads: + + * VMware, AHV, and Hyper-V virtual machines + * NAS filesets, excluding NAS Direct Archive filesets + * Microsoft Windows filesets + * Linux and Unix filesets + * Microsoft SharePoint and OneDrive + * Azure virtual machines, Blob storage, and managed disks + * AWS EC2 instances, S3 buckets, and EBS volumes + +Only turbo threat hunts are supported for Azure virtual machines, Blob storage, and managed disks, AWS EC2 instances, S3 buckets, and EBS volumes, Microsoft SharePoint, and OneDrive. + + * GCP GCE Instances + * GCP Disks + diff --git a/Viewing_quarantined_files_or_objects_in_threat_hunts_1.md b/Viewing_quarantined_files_or_objects_in_threat_hunts_1.md new file mode 100644 index 0000000000000000000000000000000000000000..fa329c5eba7fdcc2563cbbf6b05818482db51ba3 --- /dev/null +++ b/Viewing_quarantined_files_or_objects_in_threat_hunts_1.md @@ -0,0 +1,28 @@ +# Viewing quarantined files or objects in threat hunts + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_quarantined_files.html + +--- + +# Viewing quarantined files or objects in threat hunts + +You can view threat hunts that have quarantined files or objects as well as the number of impacted snapshots. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Select One or More in the Quarantined Matches filter. + +This allows you to view threat hunts that have multiple quarantined files or objects. + +## Results + +Threat hunts with quarantined matches, the number of quarantined files, and the number of impacted objects and snapshots appear. diff --git a/adds_active_directory_domain_dc.md b/adds_active_directory_domain_dc.md new file mode 100644 index 0000000000000000000000000000000000000000..d2ee6e59cf116bab3fb552c42b7412da5916b5a4 --- /dev/null +++ b/adds_active_directory_domain_dc.md @@ -0,0 +1,20 @@ +# Active Directory domains and domain controllers + +Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_domain_dc.html + +--- + +# Active Directory domains and domain controllers + +You can protect and recover Active Directory domains and domain controllers by using the protection services offered by Rubrik Security Cloud. + +Active Directory (AD) is a database that stores user credentials and information about computers and other resources on a network. Hence, AD services are used to authorize and authenticate users to access the resources within a network. By keeping access management within the network, AD provides an extra layer of security, which reduces the risk of unauthorized access. + +With Rubrik Security Cloud (RSC), you can protect your AD domains by recovering the domain controllers in the event of data threats. Additionally, RSC helps you to identify the changes made to AD objects. + +You can protect your AD domain controller by performing the following actions: + + * Installing Rubrik Backup Service (RBS) on a domain controller that you want to protect + * Adding the domain controller to Rubrik cluster as a Windows host + * Assigning an SLA Domain + diff --git a/adds_active_directory_forest.md b/adds_active_directory_forest.md new file mode 100644 index 0000000000000000000000000000000000000000..842ab8b968f0251218da80b64f4ceff2d7eeb65d --- /dev/null +++ b/adds_active_directory_forest.md @@ -0,0 +1,23 @@ +# Active Directory forest + +Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_forest.html + +--- + +# Active Directory forest + +Rubrik Security Cloud offers protection services for the Active Directory forest hierarchy. You can protect and recover the entire forest hierarchy in the event of a disaster or ransomware attack. + +Protecting and recovering the entire Active Directory (AD) forest requires purchasing Rubrik Identity Recovery License. RSC supports protection and recovery of an AD forest for Rubrik clusters running Rubrik CDM version 9.2.2 or later. The object and attribute comparison feature also requires the Rubrik Identity Recovery License. + +An AD forest is the topmost organizational boundary and logical container in an AD environment. It comprises one or more AD domains that share a common schema, configuration, and global catalog, enabling centralized management and coherent structure. Within an AD forest, domains can collaborate through trusted relationships, resource sharing, and unified security policies. This hierarchical framework facilitates the integration of diverse organizational units, users, computers, and policies, ensuring consistent access control and administration across large and complex enterprise networks. + +AD forest offers several key advantages for managing and organizing directory services in large, complex environments. + +RSC enables comprehensive recovery and protection of entire AD forest in the event of data threats. Key benefits include centralized domain management and discovery, SLA Domain assignment for protection, and automated recovery processes following best practices recommended by Microsoft. The solution minimizes downtime and mitigates the risk of malware reintroduction. It also enhances security, provides a detailed view of forest hierarchies, and supports various recovery use cases. Additional features include DNS recovery, advanced recovery settings, metadata erasure for unselected domain controllers, and recovery progress tracking. + +You can protect your AD forest by: + + * Adding the domain controller to Rubrik cluster as a Windows host: This task ensures that the AD domain controller is part of the Rubrik backup environment. + * Assigning an SLA Domain at the forest level: This task ensures that all domains within the forest receive the same level of protection. + diff --git a/adds_active_directory_inventory_management.md b/adds_active_directory_inventory_management.md new file mode 100644 index 0000000000000000000000000000000000000000..74eefe81a3ea83c06df204d769b8477de73d5ab5 --- /dev/null +++ b/adds_active_directory_inventory_management.md @@ -0,0 +1,20 @@ +# Active Directory inventory management + +Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_inventory_management.html + +--- + +# Active Directory inventory management + +The Active Directory inventory provides a summary of the actions involved in protecting the AD domain controllers in RSC. You can manage your domains and domain controllers using the information available in the AD inventory. + +With RSC, you can manage the domains and domain controllers in the AD inventory page by adding domain controllers to a Rubrik cluster. When you add a domain controller to a Rubrik cluster as a Windows host, RSC discovers the AD domain of the domain controller and the other domain controllers associated with that AD domain and displays them in the AD inventory page. You can start protecting a domain controller by assigning an SLA Domain. + +AD domains are logical entities that can be used to design a network hierarchy that meets your requirements. AD domain controllers, which are Windows servers running Active Directory, authenticate users and manage access to resources in an AD Domain. + +Information about all the discovered AD domains and associated domain controllers is displayed in the following tabs: + + * Domains: This tab displays information about all the discovered AD domains. + * Domain Controllers: This tab displays information about all the discovered domain controllers. + + *[ > ]: and then diff --git a/adds_active_directory_snapshots.md b/adds_active_directory_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..a9b96988aff93e15aada40cfd011f96a7d1eec46 --- /dev/null +++ b/adds_active_directory_snapshots.md @@ -0,0 +1,27 @@ +# Active Directory snapshots + +Source: https://docs.rubrik.com/en-us/saas/adds/active_directory_snapshots.html + +--- + +# Active Directory snapshots + +RSC protects and manages data by taking snapshots of the domain controller. You can take an on-demand snapshot, or you can configure an SLA Domain to take scheduled snapshots. + +RSC provides support for on-demand snapshots and scheduled snapshots. Scheduled snapshots are created based on the policies and rules of an assigned SLA Domain. + +The supported snapshot types are described as follows: + + * On-demand: Snapshots of AD domain controller that you can take whenever required using the take on-demand snapshot option. + * Scheduled: Snapshots created on a schedule according to the frequency specified in the SLA Domain. RSC takes scheduled snapshots using the manual snapshot API technology. + +The SLA Domain feature provides a configurable set of policies that you can apply to domains or domain controllers to achieve specific data protection objectives. The SLA Domain directs when to schedule backups of domain controller data and how long to keep the data. + +With RSC, you can perform the following actions for snapshots: + + * Take on-demand snapshots + * Change the retention policy for snapshots taken + * Delete the snapshots that have a Forever retention policy + * Recover the snapshots using the various recovery options RSC offers + + *[ > ]: and then diff --git a/adds_ad_dc_recovery_options.md b/adds_ad_dc_recovery_options.md new file mode 100644 index 0000000000000000000000000000000000000000..543ef5bff6e22e6c8de6992e0f1a71c050cf2f88 --- /dev/null +++ b/adds_ad_dc_recovery_options.md @@ -0,0 +1,23 @@ +# AD domain controller recovery options + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_dc_recovery_options.html + +--- + +# AD domain controller recovery options + +With RSC, you can recover Active Directory domain controller snapshots using either granular recovery or domain controller recovery options. + +You can take snapshots of the Active Directory (AD) domain controller using scheduled backups or take on-demand snapshots of the domain controller. RSC provides two options for recovering the snapshot information. + +The following table provides the AD domain controller recovery options. Recovery type | Description +---|--- +Granular recovery | Recovers the selected objects in an AD. The protected objects include containers, organization units, users, groups, contacts, group policies, and computers. +Domain controller recovery | Recovers the domain from the selected domain controller and restores it to one of the following destinations: + + * Restore to alternate host: Recovers the domain controller data to the alternative host that you selected. + * Restore to original domain controller: Recovers the domain controller data to the same domain controller by replacing the information with the selected snapshot information. + * Restore to new host or VM using bare-metal recovery: Recovers a failed server or domain controller to a separate host or a new virtual machine. + +Note: The AD domain controller recovery options restore additional roles, such as Active Directory Certificate Service (ADCS) and Network Policy and Access Services (NPAS), along with recovering data in an AD. + *[ > ]: and then diff --git a/adds_ad_domain_controller_protection.md b/adds_ad_domain_controller_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..2ab142b4cc154c8bb4c014f649b96e9e26891663 --- /dev/null +++ b/adds_ad_domain_controller_protection.md @@ -0,0 +1,33 @@ +# Active Directory domain controller protection + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_domain_controller_protection.html + +--- + +# Active Directory domain controller protection + +To protect the information on your AD domain controllers by applying RSC data protection policies, you can assign SLA Domains to the domain controllers + +RSC uses SLA Domains to apply data protection policies to Active Directory (AD) objects. The AD objects are domains and domain controllers. If there is no SLA Domain assigned to a domain controller, the SLA Domain assigned to the parent AD domain is inherited by the domain controllers of that specific AD domain. + +The minimum SLA Domain frequency required for AD domain controllers is four hours. You cannot assign an SLA Domain with a frequency of less than four hours to AD domain controllers. When you try to assign an SLA Domain with a frequency of less than four hours, RSC displays an error message indicating the minimum requirement of SLA Domain frequency to protect domain controllers. + +Rubrik recommends installing the Rubrik Backup Service (RBS) software on your Windows host to start taking backups of the information that resides on your AD domain controllers. + +You can start protecting the information on your domain controllers by: + + * Adding the DNS IP entries to a Rubrik cluster + * Assigning SLA Domains to domain controllers + * Configuring an SMB domain + +When RBS is running with an AD domain user account, the user account should be a member of backup operators and server operators AD groups for the AD backups to work as expected. However, to recover an entire AD or AD objects using Rubrik AD recovery, the service account must have Domain Admin privileges or LocalSystem account. To enhance security, you can initially add the user accounts to the backup operators and server operator AD groups. When a restore is needed, you can temporarily raise the user account privileges to Domain Admin or set it to LocalSystem. + +Rubrik requires you to restart the RBS services in the following scenarios for the changes to take effect: + + * When you change the logon user privileges + * When you change the logon user + +The logon user account that RBS is running with requires Write permission to the C:\programdata\Rubrik directory of the host that RBS is installed on. You must assign the Write permission recursively to all the child directories of the C:\programdata\Rubrik directory. An administrator can assign the permission to the user account using the Advanced option in the Windows Security tab for the C:\programdata\Rubrik directory. + +Rubrik recommends that you use a Microsoft Group Managed Service Account for the RBS service account instead of a traditional AD service account. Microsoft documentation provides more information about Microsoft Group Managed Service Account. + *[ > ]: and then diff --git a/adds_ad_domain_controllers_info.md b/adds_ad_domain_controllers_info.md new file mode 100644 index 0000000000000000000000000000000000000000..311e6ad126a285c5a9bbc44c662bf833733974f2 --- /dev/null +++ b/adds_ad_domain_controllers_info.md @@ -0,0 +1,25 @@ +# AD domain controllers information + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_domain_controllers_info.html + +--- + +# AD domain controllers information + +Information about the Active Directory domain controllers registered with Rubrik clusters. You can view information about domain controllers and start protecting a domain controller by assigning an SLA Domain. + +The Domain Controllers tab in the inventory page contains fields related to the Active Directory (AD) domain controllers registered with Rubrik clusters. You can also customize the view by adding, removing, pinning, and re-ordering the columns using the icon. + +Field | Description +---|--- +Domain Controller | The name associated with an AD domain controller. +FSMO Role | The FSMO roles assigned to the domain controller. +Server Role | The server roles assigned to the domain controller, for example, DNS and DHCP. +Domain | The domain name associated with the domain controller. +Rubrik Cluster | The Rubrik cluster associated with the domain controller. +SLA Domain | The SLA Domain assigned to the domain controller.If the domain controller does not have an SLA Domain assigned, it will inherit the SLA Domain of the parent AD domain. +RBS Status | The status of RBS. Only the domain controllers registered with a Rubrik cluster display the RBS status as Connected. +Snapshots | Number of snapshots available for the domain controller. +DC Location | Details about the location where the domain controller resides in your network. +Assignment | Type of assignment, indicating whether the SLA Domain assigned to the domain controller is direct or inherited from the AD domain. + *[ > ]: and then diff --git a/adds_ad_forest_discovery.md b/adds_ad_forest_discovery.md new file mode 100644 index 0000000000000000000000000000000000000000..3acd50d5dee34723d79a4c35449a3df143c5b000 --- /dev/null +++ b/adds_ad_forest_discovery.md @@ -0,0 +1,34 @@ +# AD forest discovery + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_forest_discovery.html + +--- + +# AD forest discovery + +When you add an Active Directory domain controller to a Rubrik cluster as a Windows host, RSC discovers the Active Directory forest and all the domains in the forest hierarchy. + +RSC discovers the Active Directory (AD) domains in a forest after: + + * You install Rubrik Backup Service (RBS) on a domain controller + * You add the domain controller to a Rubrik cluster as a Windows host + +RSC retrieves information about the applications running on the Windows host and identifies the Windows host as a domain controller. + +After you install RBS on a domain controller and add the domain controller to a Rubrik cluster as a Windows host, RSC performs the following actions as part of AD forest discovery: + +Discovery task | Description +---|--- +Discovering all AD domains | Discovers all the AD domains in an AD forest. +Discovering domain controllers | Discovers the other domain controllers that exist in the same AD domain and displays the discovered domains and domain controllers in RSC. +Identifying FSMO roles | Identifies the FSMO roles assigned to each of the discovered domain controllers and displays them in RSC. +Identifying Windows services | Identifies other Windows services, such as DNS and DHCP, if any domain controller in the AD domain is hosting these services. + +For Windows installations, all non-administrator RBS accounts must have access to the Rubrik registry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Rubrik Inc.\Backup Service\ and must be part of the backup operators group. If you install RBS on a host running CDM versions 9.0.3-p12, 9.1.3-p4, 9.2.1-p1, 9.2.2, or 9.3.0 and then later perform a CDM upgrade, all Windows hosts that are running RBS with a non-administrator account will be disconnected. + +You can reactivate RBS in one of the following ways: + + * By giving the user account or service account running RBS full access to the C:/Program Files/Rubrik directory. Restart RBS after adding the necessary permissions. + * By performing a clean reinstallation of RBS on the Windows host after upgrading CDM to versions 9.0.3-p12, 9.1.3-p4, 9.2.1-p1, 9.2.2, 9.3.0 or above. + + *[ > ]: and then diff --git a/adds_ad_forest_inventory_management.md b/adds_ad_forest_inventory_management.md new file mode 100644 index 0000000000000000000000000000000000000000..8294c77a65681dfe5eb70dee0d015563d65ea027 --- /dev/null +++ b/adds_ad_forest_inventory_management.md @@ -0,0 +1,25 @@ +# AD forest inventory management + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_forest_inventory_management.html + +--- + +# AD forest inventory management + +The Active Directory inventory provides a summary of the actions involved in protecting and recovering the Active Directory domains in forest hierarchy using RSC. You can manage the domain controllers in a forest using the information available in the Active Directory inventory. + +With RSC, you can manage the domains and domain controllers in the Active Directory (AD) inventory page by adding domain controllers to a Rubrik cluster. When you add a domain controller to a Rubrik cluster as a Windows host, RSC discovers the AD forest and all the domains in the forest and displays the discovered domains in the inventory page. + +Information about all the discovered forests and domains and associated domain controllers is displayed in the following tabs: + + * Forests/Domains: This displays information about all the discovered AD forests and domains. + * Domain Controllers: This displays information about all the discovered domain controllers. + +As part of inventory management for domains in a forest, you can: + + * Add your domain controllers to a Rubrik cluster as Windows hosts. + * Remove domain controllers from the Rubrik cluster if the AD domain data is corrupted or the Windows server fails. + +If all the domain controllers in a forest are deleted, the AD forest is automatically removed from RSC. + + *[ > ]: and then diff --git a/adds_ad_forest_protection.md b/adds_ad_forest_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..1ac11372ce96b1b3b5b8eeba44f4cb0488c1bc08 --- /dev/null +++ b/adds_ad_forest_protection.md @@ -0,0 +1,40 @@ +# AD forest protection + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_forest_protection.html + +--- + +# AD forest protection + +To protect and recover the information from the Active Directory domain controllers in a forest hierarchy, you can assign an SLA Domain at the forest level. You can apply the data protection policies and recover the entire forest hierarchy using the automated forest recovery that RSC provides. + +RSC uses SLA Domains to apply data protection policies to domains in a forest. If you do not assign an SLA Domain to a domain or domain controller, the domains and domain controllers in a forest hierarchy inherit the SLA Domain assigned to the Active Directory (AD) forest. + +The minimum SLA Domain frequency required for AD objects is four hours. You cannot assign an SLA Domain with a frequency of less than four hours to AD objects. When you try to assign an SLA Domain with a frequency of less than four hours, RSC displays an error message indicating the minimum requirement of SLA Domain frequency to protect AD objects. An AD object can be an AD forest, AD domain, or AD domain controller. + +You can start protecting a forest by assigning an SLA domain at the forest level, and all the domains automatically inherit the SLA Domain policies. + +Rubrik recommends installing the RBS software on your Windows host to start taking backups of the information that resides on your AD domain controllers. + +There are a few key considerations and requirements when setting up and managing AD forest and RBS. + +## AD forest protection requirements + +You can start protecting the information in the AD forest by: + + * Adding the DNS IP entries to a Rubrik cluster + * Assigning SLA Domains to the AD forest + * Configuring an SMB domain + +## RBS user account requirements + +For AD backups to function, if RBS is operating under an AD domain user account, that account must belong to the backup operators and server operators AD groups. + +## RBS logon user account permissions + +The logon user account that RBS is running with requires Write permissions for the C:\programdata\Rubrik directory of the host that RBS is installed on. Administrators must assign the Write permissions recursively to all the children of the C:\programdata\Rubrik directory. The administrator can also assign the permissions to the user account using the Advanced option in the Windows Security tab for the C:\programdata\Rubrik folder. + +## Service account recommendation + +Rubrik recommends that you use a Microsoft Group Managed Service Account for the RBS service account instead of a traditional AD service account. Microsoft documentation provides more information about Microsoft Group Managed Service Account. + *[ > ]: and then diff --git a/adds_ad_forest_protection_recovery_benefits.md b/adds_ad_forest_protection_recovery_benefits.md new file mode 100644 index 0000000000000000000000000000000000000000..b25d3c812f75f4904a94e1792833b6851b421c1c --- /dev/null +++ b/adds_ad_forest_protection_recovery_benefits.md @@ -0,0 +1,26 @@ +# AD forest protection and recovery benefits + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_forest_protection_recovery_benefits.html + +--- + +# AD forest protection and recovery benefits + +With RSC, you can effectively recover the entire Active Directory forest in the event of data threats. RSC provides many benefits through an automated recovery wizard to seamlessly recover the domains. + +The following table lists the primary benefits of protecting and recovering the domains in an Active Directory (AD) forest. Benefit | Description +---|--- +Centralized management and discovery | Adding a domain controller to the Rubrik cluster. This results in RSC discovering the entire forest and displaying its domains on the inventory page. RSCmanages and discovers domains at the forest level. +SLA Domain assignment and protection | Assigning an SLA Domain to the AD forest to ensure protection for all domains within the forest hierarchy. +Automated recovery process | Automating over 40 complex steps required to restore the AD forest, adhering to Microsoft best practices. +Minimizing downtime | Streamlining complex AD forest recovery with just a few clicks, utilizing immutable backups. +Reducing malware risk | Lowering the risk of malware re-introduction by restoring the AD forest to a new Windows environment. +Enhancing security | Automating the implementation of all security best practices to enhance forest security as recommended by Microsoft. +Providing detailed forest hierarchy | Offering a detailed view of the forest hierarchy in the RSC inventory. +Identifying FSMO roles and services | Identifying FSMO roles on domain controllers, DNS, and DHCP services, along with their geolocation. +Supporting specific recovery use cases | Supporting Disaster Recovery, Cyber Recovery, and Test or Compliance purposes. +Offering flexible recovery options | Supporting recovery to the original or an alternate setup, including DNS recovery of AD integrated DNS services. +Configuring advanced recovery settings | Allowing settings configuration, such as Windows Time Service and Global Catalog Servers and resetting Kerberos password. +Managing metadata | Providing an option to erase metadata of domain controllers not selected during recovery. +Tracking recovery progress | Allowing tracking of recovery progress from the forest inventory page. + *[ > ]: and then diff --git a/adds_ad_forests_domains_info.md b/adds_ad_forests_domains_info.md new file mode 100644 index 0000000000000000000000000000000000000000..25e868b0a22a8f1323f06305071ae8929234840e --- /dev/null +++ b/adds_ad_forests_domains_info.md @@ -0,0 +1,21 @@ +# AD forests and domains information + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_forests_domains_info.html + +--- + +# AD forests and domains information + +Information about the Active Directory forest and domains discovered by RSC. You can view the information about Active Directory forests and domains and manage protection for the domains by assigning an SLA Domain. + +The Forests/Domains tab in the inventory page contains fields related to the Active Directory (AD) forests and domains discovered by RSC. You can also customize the view by adding, removing, pinning, and re-ordering the columns using the icon. + +Field | Description +---|--- +Forest/Domain | The AD root domain and the child domain names in the forest hierarchy discovered in your network. +Domain Controller | The total number of domain controllers associated with the AD domain. +SLA Domain | The SLA Domain assigned to the AD domain. +SLA Assigned | Type of assignment, indicating whether the SLA Domain assigned to the AD domain is direct or inherited from the AD forest. +Last Backup | The date and time of the last backup. +Rubrik Cluster | The Rubrik cluster associated with the AD domain. + *[ > ]: and then diff --git a/adds_ad_object_comparison.md b/adds_ad_object_comparison.md new file mode 100644 index 0000000000000000000000000000000000000000..28605d737df9a7caa036408de279ed9ccadeb9b2 --- /dev/null +++ b/adds_ad_object_comparison.md @@ -0,0 +1,18 @@ +# AD object comparison + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_object_comparison.html + +--- + +# AD object comparison + +With RSC, you can select and recover specific attributes of the selected Active Directory object. You can compare the attributes with the live Active Directory to view the changes in attribute values for the selected Active Directory object. + +AD object comparison to recover specific attributes of an Active Directory (AD) requires the Rubrik Identity Recovery License. + +RSC enhances the granular recovery workflow by adding Active Directory (AD) object comparison. The AD object comparison analyzes the attribute values for the selected AD object between the snapshot and the live AD instance, displaying any changes in attribute values. You can select specific attributes of an AD object and recover them. + +To compare attributes of an AD object from the selected snapshot with the live AD object, you can use the Compare Attributes option. You can also view the attribute value in the snapshot and in the live AD object. + +The Show Altered Attributes Only option is turned on by default, displaying the snapshot attributes values that are different from the live AD. You can turn off the option to view other attributes values of the selected AD object. To view the details of the changes in attribute values, you can use the view details option. The view details wizard displays the comparison of the attribute changes between the snapshot and the live AD instance. + *[ > ]: and then diff --git a/adds_ad_protection.md b/adds_ad_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..4d73444208e9315f8b70049d7e8b383f651de6d3 --- /dev/null +++ b/adds_ad_protection.md @@ -0,0 +1,21 @@ +# Active Directory protection + +Source: https://docs.rubrik.com/en-us/saas/adds/ad_protection.html + +--- + +# Active Directory protection + +Rubrik Security Cloud offers capabilities for protecting Active Directory, including features for backing up and recovering individual domain controllers and entire Active Directory forests, designed to enhance the identity resilience of an organization. + +Rubrik Security Cloud (RSC) provides comprehensive protection and recovery solutions for Active Directory (AD), which is a critical component for identity and access management in many organizations. Recognizing that identity systems are prime targets for cyberattacks, Rubrik focuses on ensuring the availability and integrity of AD to maintain business continuity. + +RSC supports the protection of AD domain controllers. When you add a domain controller to a Rubrik cluster as a Windows host and install the Rubrik Backup Service (RBS), RSC automatically discovers the AD domain and its associated domain controllers. + +## Forest-wide protection and recovery + +RSC capabilities extend beyond individual domain controllers to encompass entire AD forests. This feature is crucial for recovering from widespread cyberattacks or disasters. + +Note: + +Protecting an AD forest requires a Rubrik Identity Recovery License. diff --git a/adds_adding_ad_domain_controller.md b/adds_adding_ad_domain_controller.md new file mode 100644 index 0000000000000000000000000000000000000000..179288697893fb7716a8fd2c43745fc5bd4298f3 --- /dev/null +++ b/adds_adding_ad_domain_controller.md @@ -0,0 +1,59 @@ +# Adding an AD domain controller + +Source: https://docs.rubrik.com/en-us/saas/adds/adding_ad_domain_controller.html + +--- + +# Adding an AD domain controller + +Add an Active Directory domain controller as a Windows host to a Rubrik cluster to start protecting the domain controller. + +## Before you begin + +Ensure the following: + + * Data source management privileges on the Windows host are available. + * Rubrik Backup Service (RBS) is installed and has sufficient privileges to access the AD domain. + * RBS is running with a service account that has the necessary privileges to access the AD domain. + +If required, change the service account by using the services.msc command in Windows and then restart RBS. + + * Latest Visual C++ Redistributable is installed on the host in order to add it as a domain controller. You can download the latest Visual C++ Redistributable from . + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Active Directory inventory card. + +The Active Directory inventory dashboard appears and displays a list of AD domains. + + 5. In the Active Directory page, click Manage Domain Controllers. + +Alternatively, you can also add a Windows host to the Rubrik cluster from the Data Sources in Settings menu. + +The Windows page in Data Sources appears. + + 6. Click Add Hosts. + 7. Select a Rubrik Cluster from the dropdown list. + +RSC adds the Windows host to the selected Rubrik cluster. + + 8. Select I have already installed and registered the RBS software. + 9. In Host IP addresses or FQDNs, enter an IP address or FQDN. + +You can add multiple IP addresses or FQDNs. + + 10. Click Add. + +## Results + +RSC checks the connectivity with the Windows host and adds the domain controller to the Rubrik cluster. The discovered AD domain and domain controllers appear on the Active Directory inventory page. + *[ > ]: and then diff --git a/adds_configuring_rbrk_clstr_primry_win_host.md b/adds_configuring_rbrk_clstr_primry_win_host.md new file mode 100644 index 0000000000000000000000000000000000000000..07ba20a6812bfca1ed332c072b0642fcdadb2dcf --- /dev/null +++ b/adds_configuring_rbrk_clstr_primry_win_host.md @@ -0,0 +1,33 @@ +# Configuring a Rubrik cluster as primary for a Windows host + +Source: https://docs.rubrik.com/en-us/saas/adds/configuring_rbrk_clstr_primry_win_host.html + +--- + +# Configuring a Rubrik cluster as primary for a Windows host + +Configure Windows host settings to set a Rubrik cluster as the primary cluster for an AD domain controller host. + +## About this task + +A domain controller host communicates with the primary cluster, which can either be a source or target cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Sources > Windows. + +The Windows page in Data Sources appears listing all the hosts that are added to Rubrik clusters. + + 4. Click for a domain controller host that you want to set as primary and select Configure as Primary Cluster. + +You can change only the domain controller host with the RBS status as Secondary cluster to primary using the Configure as Primary Cluster option. + +## Results + +RSC configures the selected Rubrik cluster as a primary cluster for the AD domain controller host and the RBS status updates to Connected. This operation might take a few minutes to complete. You can track the progress from the Events page. + *[ > ]: and then diff --git a/adds_discovery_ad_domains_dc.md b/adds_discovery_ad_domains_dc.md new file mode 100644 index 0000000000000000000000000000000000000000..6b01c02c2cafab3c67cebb6c02801ab1e31562cc --- /dev/null +++ b/adds_discovery_ad_domains_dc.md @@ -0,0 +1,38 @@ +# Discovery of AD domains and domain controllers + +Source: https://docs.rubrik.com/en-us/saas/adds/discovery_ad_domains_dc.html + +--- + +# Discovery of AD domains and domain controllers + +When you add an AD domain controller to a Rubrik cluster as a Windows host, RSC discovers the AD domain of the domain controller and the associated domain controllers of that AD domain. This allows you to start protecting the domain controller you added. + +RSC discovers the AD domains and domain controllers after you complete the following: + + * You install Rubrik Backup Service (RBS) on a domain controller + * You add the domain controller to a Rubrik cluster as a Windows host + +RSC retrieves information about the applications running on the Windows host and identifies the Windows host as a domain controller. + +After you install RBS on a domain controller and add the domain controller to a Rubrik cluster as a Windows host, RSC performs the following actions as part of discovery: + +Discovery task | Description +---|--- +Discovering AD domain | Discovers the AD domain to which the domain controller belongs. +Discovering domain controllers | Discovers the other domain controllers that exist in the same AD domain and displays the discovered domains and domain controllers in RSC. +Identifying FSMO roles | Identifies the FSMO roles assigned to each of the discovered domain controllers and displays them in RSC. +Identifying Windows services | Identifies other Windows services, such as DNS and DHCP, if any domain controller in the AD domain is hosting these services. + +Although RSC displays all the discovered domain controllers, you can protect only the domain controllers that have RBS installed on them. + +As part of managing protection for domain controllers, you can add your domain controllers to a Rubrik cluster as Windows hosts and remove them from the Rubrik cluster if the AD domain data is corrupted or the Windows server fails. If all the domain controllers in an AD domain are deleted, the AD domain is automatically removed from RSC. + +For Windows installations, all non-admin RBS accounts must have access to the Rubrik registry at Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Rubrik Inc.\Backup Service\ and must be part of the backup operators group. If you install RBS on a host running CDM versions 9.0.3-p12, 9.1.3-p4, 9.2.1-p1, 9.2.2, or 9.3.0 and then later perform a CDM upgrade, all Windows hosts that are running RBS with a non-administrator account will be disconnected. + +Resolve in one of the following ways: + + * By giving the user account or service account running RBS full access to the C:/Program Files/Rubrik directory. Restart RBS after adding the necessary permissions. + * By performing a clean reinstallation of RBS on the Windows host after upgrading CDM to versions 9.0.3-p12, 9.1.3-p4, 9.2.1-p1, 9.2.2, 9.3.0 or above. + + *[ > ]: and then diff --git a/adds_managing_protection_ad_forest.md b/adds_managing_protection_ad_forest.md new file mode 100644 index 0000000000000000000000000000000000000000..4d9d3f1f86fb41470da7e5af69a1a30166c6742e --- /dev/null +++ b/adds_managing_protection_ad_forest.md @@ -0,0 +1,79 @@ +# Managing protection for AD forest + +Source: https://docs.rubrik.com/en-us/saas/adds/managing_protection_ad_forest.html + +--- + +# Managing protection for AD forest + +As an RSC user with the required privileges, manage protection for all the domains and domain controllers in an Active Directory forest by assigning an SLA Domain at the Active Directory forest level. + +## Before you begin + +Ensure the following: + + * You have purchased RSC Identity Cyber Recovery License. + * Manage protection data management privileges are assigned to start protecting Active Directory (AD) objects. + * The Rubrik cluster has a global DNS configured. + +When it is not configured, use a DNS server to resolve the domain names and add DNS IP entries to the Rubrik cluster, as described in [Editing DNS and search domains for a Rubrik cluster](../saas/common/edit_dns_search_domains_rubrik_cluster.html "Edit the DNS and search domains for a Rubrik cluster to improve the network efficiency, security, and accessibility."). + + * An SMB domain is configured to take a backup of an AD domain controller. + +You can configure an SMB domain as described in [Adding a Rubrik cluster to an SMB Domain](../saas/adding_rubrik_cluster_to_smb_domain.html "To enforce user authentication through Active Directory, add a Rubrik cluster that hosts SMB shares to an SMB domain."). + +The SMB security documentation provides more information about SMB configuration. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Active Directory inventory card. + +The Active Directory inventory dashboard appears and displays a list of AD forests and domains within a forest. + + 5. Select a forest and click Manage Protection. + +The Manage Protection wizard starts, and the Assign SLA Domain page appears. + + 6. Select a protection option. + +Option| Description +---|--- +SLA Domain | The SLA Domain is assigned to the selected objects. +Don't protect | The selected objects are excluded from all further SLA Domain assignments and protection. +Clear existing assignment | The SLA Domain is derived from the next higher level object based on inheritance rules. + + 7. (Don't protect) In Existing snapshot retention, select an option for the existing snapshots. + +Option| Description +---|--- +Use current SLA Domain for retention | The retention is derived from the current SLA Domain. +Keep forever | The snapshots are retained until they are manually deleted. +Expire immediately | The snapshots are deleted from the Rubrik cluster. + + 8. Click Next. + +When you have selected SLA Domain, a confirmation page appears in the wizard, displaying the summary of SLA Domain changes. + +When you have selected Clear existing assignment, the Inherit SLA Domain page appears and displays an option to apply changes to existing snapshots. + +When you have selected Don't protect, the Don't Protect wizard appears, displaying a message that the selected objects have been excluded from any future assignments to the SLA Domain. + + 9. **Optional:** Turn on Apply changes to existing snapshots. + +The Include on-demand and downloaded snapshots checkbox appears. + + 10. Click Assign. + +## Results + +RSC processes the specified assignments and initiates protection for the selected AD forest. + *[ > ]: and then diff --git a/adds_recovering_ad_forest.md b/adds_recovering_ad_forest.md new file mode 100644 index 0000000000000000000000000000000000000000..654ecb1968502be9c4fdd7a24cb2a1c5271e13cf --- /dev/null +++ b/adds_recovering_ad_forest.md @@ -0,0 +1,147 @@ +# Recovering AD forest + +Source: https://docs.rubrik.com/en-us/saas/adds/recovering_ad_forest.html + +--- + +# Recovering AD forest + +In the event of a ransomware attack or disaster, recover the entire forest to restore all the domains in a forest. RSC provides a master wizard that combines all the steps to recover all the domains in a forest. + +## Before you begin + +Ensure the following: + + * You have purchased the RSC Identity Cyber Recovery license. + * The user account has the exportFiles on DC, forestRestore on forest, and provisionOnInfra on target host privileges to recover Active Directory (AD) forest to an alternate host. + * The user account has the restoreToOrigin, exportFiles on DC, and forestRestore on forest privileges to recover AD forest to the original host. + * The user account has Export snapshots and Restore over original data management recovery privileges. + * For alternate host recovery, ensure that you have fulfilled the prerequisites described in [AD alternate host recovery prerequisites](ad_ahr_prereq.html "Information about Microsoft-recommended prerequisites that you must fulfill to successfully recover domain controllers or domains in an Active Directory forest."). + * For AD host promotion, ensure that the host is on a Rubrik cluster running CDM version 9.4.1 or later and you have fulfilled the prerequisites as described in [AD host promotion prerequisites](ad_host_promotion_prereqs.html "Information about the specific requirements for promoting a vanilla Windows host to an Active Directory domain controller using replication."). + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Active Directory inventory card. + +The Active Directory inventory dashboard appears and displays a list of AD domains. + + 5. Select a forest and click Recover Forest. + +The Forest Recovery master wizard appears. + + 6. Click Start Recovery. + 7. Select a point in time for recovery and click Next. + * Closest point-in-time + * Latest + +For closest point-in-time recovery, you can select a custom time and date. + + 8. Select a recovery target and click Next. + * Recover to alternate Windows hosts + * Recover to original hosts + +For recovering to an alternate Windows host, there are two types of recovery methods, system state recovery and bare-metal recovery. + + 9. Select an option to configure and recover DNS. + * Configure DNS automatically + * Enter IP Addresses for DNS + * Leave DNS settings intact + +Based on your reason for recovery, RSC selects the recovery settings automatically to recover the selected forest. You can change the settings by configuring them manually. + + 10. **Optional:** Click Configure Advanced Settings to launch the settings page and click Save to save the changes you made in the advanced settings. + +The AD forest recovery advanced settings options topic provides more details about the available options for advanced settings. + + 11. Click Next. + 12. Configure domains for recovery. + +Based on the recovery target you selected, configure the AD domains by performing one of the following actions: + +Recovery target| Actions +---|--- +Recover to alternate Windows hosts | + * Confirm which domain controller in a domain to recover. + * Select a target Windows host for the selected domain controller. + * Enter the domain admin credentials. +Recover to original hosts | + * Confirm which domain controller in a domain to recover. + * Enter the domain admin credentials. + +RSC selects a domain controller for each domain based on your chosen point in time for recovery. You can configure each domain to select a different domain controller for recovery. + +Note: + +Configuring each domain in a forest is necessary to proceed with the recovery process. + +You can use the Configure option in the Configuration column to select a different domain controller for each domain. Once you complete this, you can proceed further with the AD forest recovery. + + 13. For each domain in a forest, click Configure and select the recovery option. + * Recover DCs only + * Recover DCs and promote hosts + 14. For Recover DCs and promote hosts, select the host promotion method. + * Promote via replication + * Promote using an Install From Media (IFM) package + 15. Click Next. + +For recovering to an alternate Windows host, you can select the recovery method and the target host from the Select Target Host page. The list of target hosts available for selection depends on the selected recovery method. When there is no alternate Windows host configured, you can add a Windows host to the Rubrik cluster from the Data Sources using the Settings menu. + + 16. **Optional:** In Retain IP address of, select the option from which you want to retain the IP address. + +You can retain the IP address of either the target host or the source DC to avoid losing connection to the target host after recovery. After the recovery, the target host will use the selected IP address and network settings. + +RSC supports retaining IP addresses for system state recovery of snapshots taken on the Rubrik clusters starting from Rubrik CDM version 9.4.1 and for bare-metal recovery starting from Rubrik CDM version 9.4.1-p1. + + 17. **Optional:** Click Edit DC Selection to select a different domain controller for recovery and click Save. + +RSC selects a domain controller for recovery based on your recovery reason. When other domain controllers are available, you can select a different domain controller for recovery from the Edit DC Selection page. + + 18. **Optional:** Click Configure Unselected Domain Controllers, either to erase the metadata or leave the metadata intact for the unselected domain controllers of a specific domain, and click Save. + +RSC erases the metadata of the AD object and the DNS entries related to the domain controller. However, RSC provides an option to leave the metadata intact for the unselected domain controllers. + + 19. Click Next. + +The Enter Domain Admin Credentials page appears. + + 20. Enter the username and password and click Next. + 21. For AD host promotion, click Select Hosts. + +The Select Hosts to Promote wizard appears. + + 22. In Select Hosts to Promote, select the hosts from the list of Windows hosts that you want to promote as domain controllers, and click Save. + +The Create Password for DSRM Admin Account page appears. + + 23. Enter the Directory Services Repair Mode (DSRM) password for each host that you selected. + +The password must meet the required criteria. + +For Promote using an Install From Media (IFM) package option, you must also select the DC which has the snapshot to promote the Windows host to a domain controller. + + 24. **Optional:** Click Edit Hosts to select different hosts or make any modifications to the host selection and click Save. + 25. Click Next. + +You have completed the configuration for the selected domain. You must complete the configuration settings for each domain in the AD forest. + + 26. Click Next. + +The Recovery Confirmation page appears. + + 27. Review your selections and click Recover. + +## Results + +RSC starts the recovery for each domain and recovers the domain controller data to the target host. + +When a host promotion fails, the AD forest recovery still succeeds with warnings, and the entire AD forest recovery job does not fail. + *[ > ]: and then diff --git a/ai_annapurna-chat-controls.md b/ai_annapurna-chat-controls.md new file mode 100644 index 0000000000000000000000000000000000000000..53700197cf15b496cce707a1efa4290d5ef9b6d6 --- /dev/null +++ b/ai_annapurna-chat-controls.md @@ -0,0 +1,20 @@ +# Annapurna chat controls + +Source: https://docs.rubrik.com/en-us/saas/ai/annapurna-chat-controls.html + +--- + +# Annapurna chat controls + +Annapurna provides several UI elements that help you work with your chats. + +Location | Control | Description +---|---|--- +Chatbot | Change | On the title field of a chatbot the Change element closes the chatbot and displays the available chatbots. +Chatbot | View Details | In the responses from a chatbot the View Details element displays the data chunks that were included in the prompt sent to the LLM. +Chatbot | Pin This Chat | On a chatbot the Pin This Chat element places the chat history listing for the chat at the top of the Chat History pane, beneath any previously pinned chats. +Chat History | | The element closes the current chatbot and displays the available chatbots. +Chat History | and | The collapses the Chat History panel and the expands the Chat History panel. +Chat History | | On the menu of each Chat History entry, the element can be used to change the title of the entry. +Chat History | | On the menu of each Chat History entry, the element can be used to delete the entry. + *[ > ]: and then diff --git a/ai_annapurna.md b/ai_annapurna.md new file mode 100644 index 0000000000000000000000000000000000000000..0c530e99a332af0c8137ee69ae21d8608258edaa --- /dev/null +++ b/ai_annapurna.md @@ -0,0 +1,35 @@ +# Annapurna + +Source: https://docs.rubrik.com/en-us/saas/ai/annapurna.html + +--- + +# Annapurna + +Rubrik Security Cloud includes the Annapurna application which you can use to obtain answers from your data, using generative AI. + +Annapurna is an enterprise application. By using the generative AI capabilities of Annapurna, you can leverage your protected data to obtain natural language answers to business questions through retrieval-augmented generation (RAG). + +You can use Annapurna in two different ways: + + * Custom chatbots can be created in Rubrik Security Cloud (RSC) to process your prompts through the large language model (LLM) of Azure OpenAI Service. + * Data chunks generated via RAG can be retrieved using an API endpoint, and these chunks can then be sent to your specified LLM within your custom GenAI application. + +To begin using Annapurna with your enterprise data, your administrators create chatbots. Each chatbot specifies which workload data to index and which sensitive data filters to apply. A chatbot can be configured to exclude sensitive user data based on your Data Security Posture policies. Data sources from the following workloads can be included: + + * Microsoft 365 + * Jira Cloud + * Salesforce + * Confluence[1](#fntarg_1) + +After specifying the data to include, your administrators assign a role to the chatbot. Only users with the assigned role will be able to use the chatbot. The data available to a user through a chatbot depends on the access permissions the user has for that data. Annapurna uses the permissions assigned by each source application to determine the access a user has to data from that application. + +Once chatbots are created, your enterprise users can launch a chatbot and ask natural language questions about the data available through the chatbot. Based on the query, Annapurna uses RAG to get relevant data from the available data sources. The retrieved data and the query are combined into a prompt and sent to the LLM. The user gets a natural language response to their query that is based on the data included in the prompt. This process does not involve training the LLM. + +The chatbots that your administrators create can use multiple data sources from different workload types. This means a chatbot can query data from various workloads at the same time. Queries through such a chatbot can give answers that combine data from different sources. + +Important: + +Annapurna uses generative AI to respond to your prompts. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. + +[1](#fnsrc_1) To enable Confluence as a data source, contact Rubrik Support. diff --git a/ai_annapurna_benefits.md b/ai_annapurna_benefits.md new file mode 100644 index 0000000000000000000000000000000000000000..3ec60bd37bbd75d92d07c0d6fb27ac6672cb81f8 --- /dev/null +++ b/ai_annapurna_benefits.md @@ -0,0 +1,19 @@ +# Benefits of Annapurna + +Source: https://docs.rubrik.com/en-us/saas/ai/annapurna_benefits.html + +--- + +# Benefits of Annapurna + +Annapurna enables enterprises to securely leverage retrieval-augmented generation and generative AI for enhanced data understanding, solving complex business use cases by correlating data from multiple sources without disrupting backup and recovery operations. + +As a Rubrik customer, you can use the generative AI features of Annapurna to solve complex business problems. This involves connecting data from different sources without affecting normal backup and recovery operations in RSC. + +The following table describes the benefits that Annapurna provides for your enterprise. Benefit | Description +---|--- +Accelerated GenAI | Achieve fast AI development and production with quick access to many data sources. Use an AI-ready platform with pre-built connectors and many tools. +CISO-approved AI data foundation | Ensure compliance and security throughout the lifecycle of your GenAI applications. This includes suppressing sensitive data and managing data access governance. +Application aware embedding models | Enhance compatibility, performance, and speed by using smart embedding models made for the data from your applications. +Reduced costs | Reduce the storage and computing costs of creating a data lake, as well as the licensing costs for technology and security tools. Shift your AI team from building AI infrastructure to developing GenAI applications. + *[ > ]: and then diff --git a/ai_annapurna_framework.md b/ai_annapurna_framework.md new file mode 100644 index 0000000000000000000000000000000000000000..c4f7572f2cb043ea71f03b332f0343348d0567ec --- /dev/null +++ b/ai_annapurna_framework.md @@ -0,0 +1,23 @@ +# Annapurna framework + +Source: https://docs.rubrik.com/en-us/saas/ai/annapurna_framework.html + +--- + +# Annapurna framework + +Annapurna uses an embedding model to change source data and chatbot questions into vector embeddings. These embeddings are stored in a vector database. The vector embeddings from the data source that match the query vector embeddings are then combined to create the prompt sent to the LLM. + +Annapurna is a generative AI application built on a retrieval-augmented generation (RAG) framework. It uses data embedding models to turn the source data and user questions into vector embeddings, which are stored in a vector database. When a user types a question into an Annapurna chatbot, the framework compares the vector embeddings of the question with the source data vector embeddings in the database. This comparison finds a data set that matches the question. Annapurna then combines this relevant data with the user's question to create the prompt sent to the LLM. + +The following image represents the flow of source data and prompts through the Annapurna framework. + + 1. Rubrik protects your data through backups and snapshots of the data on premises, in the cloud, and in SaaS data sources. The combined data is available in your data lake. + 2. In your RSC domain, an administrator creates a chatbot. + 3. Annapurna generates vector embeddings from your data stored in the data lake and saves them in a vector database in the cloud. The embeddings in the database are refreshed with each source data update. Embeddings for new or modified files are automatically created and stored in the vector database. + 4. An end user enters a query in the chatbot. + 5. The embedding model converts the user prompt into a vector representation and passes it on to the vector database where the source data vectors are stored. Annapurna compares the vector models and determines a data set that matches the context of the query. + 6. Annapurna passes a prompt consisting of the data set and the query to the LLM. + 7. The LLM sends a response and the response appears in the chatbot interface. + + *[ > ]: and then diff --git a/ai_creating_annapurna_chatbot.md b/ai_creating_annapurna_chatbot.md new file mode 100644 index 0000000000000000000000000000000000000000..c72efd5d5c7a1fe00a52a5282b50b6871dab1cea --- /dev/null +++ b/ai_creating_annapurna_chatbot.md @@ -0,0 +1,93 @@ +# Creating a chatbot + +Source: https://docs.rubrik.com/en-us/saas/ai/creating_annapurna_chatbot.html + +--- + +# Creating a chatbot + +Create an Annapurna chatbot that uses retrieval-augmented generation to answer your data-related questions. + +## Before you begin + + * Log in with an account that has the Annapurna privileges: View chatbot, Chat with chatbot, and Manage chatbot. + * Use SLA Domain assignments to protect the workloads that will have data sources assigned to the chatbot. + * Take full snapshots of the workload data sources. + * Configure the sensitive data exclusion rules that will be used by the chatbot. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Annapurna. + +The Annapurna Chat page appears. + + 3. Click Manage Chatbots. + +The Annapurna Manage Chatbots page appears. + + 4. Click Create Chatbot. + +The Create a Chatbot wizard appears. + + 5. In Name, enter a name for your chatbot. + 6. In Description, enter a description for your chatbot. + 7. Click Next. + +The Select Data Sources page appears. In the Hierarchy section, the available workloads appear. + + 8. Next to a workload, click to select data sources from that workload. + +The Select Data Sources panel appears. + + 9. Click a top-level data source, navigate the hierarchy to individual data sources, and select data sources. + +You can select multiple data sources. + +The data from each selected data source is included for queries from the chatbot. + + 10. Click Save. + +The wizard returns to the top-level Select Data Sources panel. The number of data sources selected for the workload appears next to the workload. + + 11. **Optional:** Repeat the steps to select data sources for additional workloads types. + +Data from all of the selected data sources will be available for queries from this chatbot. Queries from each individual user will only include data for which the user has access permissions. + + 12. Click Next. + +The Exclude Sensitive Data page appears. + + 13. **Optional:** Select Data Security Posture policies. + +Data from the selected data sources will be filtered based on the selected policies. Data that matches a rule of a selected policy will be excluded from all queries. + + 14. Click Next. + +The Additional Source Data Parameters page appears. + + 15. **Optional:** Turn on Include only specific file types as data source and select file extensions. + +Data from files with a filename that ends in a selected extension will be included for queries. Data from all other files will not be included for queries. When this setting is turned on, at least one extension must be selected. + + 16. Click Next. + +The Assign to a Role page appears. + + 17. Select an option for assigning a role to the chatbot. + +Option| Description +---|--- +Create a new role | Select to create a role with access to this chatbot and assign users and SSO groups to the role. The name specified for the new role must be unique in your RSC namespace. +Assign to an existing role | Select an existing role to enable access to this chatbot for the users and SSO groups assigned to that role. + + 18. Click Next. + +The Confirmation screen appears. + + 19. Confirm the chatbot configuration details and click Publish. + +## Results + +RSC creates the chatbot and adds it to the Annapurna Chat page. + *[ > ]: and then diff --git a/ai_deleting_annapurna_chatbot.md b/ai_deleting_annapurna_chatbot.md new file mode 100644 index 0000000000000000000000000000000000000000..b1f127d80b22a51f5aa17ff8560584d5df60d6b3 --- /dev/null +++ b/ai_deleting_annapurna_chatbot.md @@ -0,0 +1,39 @@ +# Deleting a chatbot + +Source: https://docs.rubrik.com/en-us/saas/ai/deleting_annapurna_chatbot.html + +--- + +# Deleting a chatbot + +Delete a chatbot to prevent users from accessing the chatbot. + +## Before you begin + +Log in with an account that has the Annapurna privileges: View chatbot, Chat with chatbot, and Manage chatbot. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Annapurna. + +The Annapurna Chat page appears. + + 3. Click Manage Chatbots. + +The Annapurna Manage Chatbots page appears. + + 4. Select a chatbot, open and click Delete. + +A Delete Chatbot confirmation page appears. + + 5. Click Delete. + +The Delete Chatbot confirmation dialog box appears. + + 6. Click Delete. + +## Results + +RSC deletes the chatbot and the Annapurna Manage Chatbots page appears. + *[ > ]: and then diff --git a/ai_editing_annapurna_chatbot.md b/ai_editing_annapurna_chatbot.md new file mode 100644 index 0000000000000000000000000000000000000000..682e72be83a4a32c78228cd46e2184b0c46ff1bb --- /dev/null +++ b/ai_editing_annapurna_chatbot.md @@ -0,0 +1,61 @@ +# Editing a chatbot + +Source: https://docs.rubrik.com/en-us/saas/ai/editing_annapurna_chatbot.html + +--- + +# Editing a chatbot + +Edit an Annapurna chatbot to modify the settings. + +## Before you begin + +Log in with an account that has the Annapurna privileges: View chatbot, Chat with chatbot, and Manage chatbot. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Annapurna. + +The Annapurna Chat page appears. + + 3. Click Manage Chatbots. + +The Annapurna Manage Chatbots page appears. + + 4. On a chatbox listing, open and select Edit. + +The Edit Chatbot wizard appears. + + 5. **Optional:** In Name, change the name of the chatbot. + 6. **Optional:** In Description, change the description of the chatbot. + 7. Click Next. + +The Select Data Sources page appears. In the Hierarchy section, the available workloads appear. + + 8. **Optional:** Next to a workload, click to change the data sources from that workload. + 9. Click Save or Next. + +Click Save if data source changes were made. Click Next if no changes were made to the selected data sources. + +The Exclude Sensitive Data page appears. + + 10. **Optional:** Change the selected Data Security Posture policies. + 11. Click Next. + +The Additional Source Data Parameters page appears. + + 12. **Optional:** Turn on Include only specific file types as data source and select file extensions. + +Data from files with a filename that ends in a selected extension will be included for queries. Data from all other files will not be included for queries. When this setting is on, at least one extension must be selected. + + 13. Click Next. + +The Confirmation screen appears. + + 14. Confirm the chatbot configuration changes and click Update. + +## Results + +RSC updates the chatbot settings. + *[ > ]: and then diff --git a/ai_using_annapurna_chatbot.md b/ai_using_annapurna_chatbot.md new file mode 100644 index 0000000000000000000000000000000000000000..8ddeed034cfab222dbab2fc6ced5b331f2731ba3 --- /dev/null +++ b/ai_using_annapurna_chatbot.md @@ -0,0 +1,43 @@ +# Using a chatbot + +Source: https://docs.rubrik.com/en-us/saas/ai/using_annapurna_chatbot.html + +--- + +# Using a chatbot + +Use an Annapurna chatbot to start a natural language conversation about your data. + +## About this task + +The Annapurna chatbots you can access are determined by RBAC rules and the privileges assigned to your role. + +Important: + +Annapurna uses generative AI to respond to your prompts. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Annapurna. + +The Annapurna Chat page opens and displays the chatbots available to you. It also displays your chat history. + + 3. Click a chatbot. + +Alternatively, click an entry in the Chat History panel to continue a previous chat. The questions and answers from your previous chats with this chatbot are included in each new prompt sent to the LLM. + +The chatbot opens and provides an entry field for your questions. + + 4. Enter a question. + +The chatbot provides a response to your question based on the data sources assigned to it and the access permissions you have for those data sources. + + 5. **Optional:** After each response, ask a new question. + +The chatbot uses your previous questions and the responses to refine its responses to your subsequent questions. + +## Results + +The chatbot answers your questions based on the data sources it has and the access permissions you have for those data sources. Annapurna adds an entry to the Chat History pane for the chat and formulates a title for the entry based on the conversation. + *[ > ]: and then diff --git a/amazon_S3_amazon_s3.md b/amazon_S3_amazon_s3.md new file mode 100644 index 0000000000000000000000000000000000000000..c411d4d65e77f1d9c5a055cead566d746885f5b3 --- /dev/null +++ b/amazon_S3_amazon_s3.md @@ -0,0 +1,42 @@ +# Amazon S3 + +Source: https://docs.rubrik.com/en-us/saas/amazon_S3/amazon_s3.html + +--- + +# Amazon S3 + +By using the protection services offered by RSC, you can protect and recover your Amazon S3 buckets and objects. + +Amazon Simple Storage Service (S3) is a highly scalable and secure cloud-based storage service that caters to the storage management needs of businesses and industries of all sizes. Amazon S3 can be used for storage management by data lakes, mobile applications, backup and restore, archival support, enterprise applications, IoT devices, and big data analytics. + +Amazon S3 buckets contain critical, business-sensitive data that you must protect for business continuity and compliance. While you are protecting the data stored in your Amazon S3 buckets, you might face challenges because of the following reasons: + + * S3 buckets are stored across multiple accounts, causing a management overhead. + * S3 buckets might contain billions of objects, where recovery of a specific set of objects becomes a concern. + * S3 snapshots might be required to be stored in a different account and region. + * S3 snapshots need to be immutable to prevent deletion. + +With RSC, you can achieve the following results: + + * Protect your S3 buckets and objects against ransomware attacks by taking immutable snapshots and storing those snapshots in a different location. + * Store S3 bucket snapshots to lower-cost storage tiers to optimize cost. + * Manage all your S3 buckets and objects from a dashboard. + * Recover the required buckets or objects, thus avoiding restoring a full bucket when you must recover specific objects within a bucket. + +Each object in Amazon S3 has a storage class associated with it. For example, if you list the objects in an S3 bucket, the AWS Management console shows the storage class for all the objects in the list. Amazon S3 offers various storage classes for the objects that you store. However, RSC supports only the source Amazon S3 objects with the following storage classes: + + * S3 Standard + * S3 Standard-IA + * S3 One Zone-IA + +In RSC, while you are creating an Amazon S3 SLA Domain to take snapshots of your S3 buckets and objects for protection, you must specify an S3 bucket where you want the snapshots to be stored. RSC supports the following storage classes for this bucket: + + * S3 Standard + * S3 Standard-IA + * S3 One Zone-IA + * S3 Glacier Instant Retrieval + * S3 Glacier Flexible Retrieval + * S3 Glacier Deep Archive + + *[ > ]: and then diff --git a/archival_archiving_data_center_workloads.md b/archival_archiving_data_center_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..f65b131d1b9fb8e9beea2f2320a78015c8674ccd --- /dev/null +++ b/archival_archiving_data_center_workloads.md @@ -0,0 +1,33 @@ +# Archiving of data center workloads + +Source: https://docs.rubrik.com/en-us/saas/archival/archiving_data_center_workloads.html + +--- + +# Archiving of data center workloads + +With Rubrik Security Cloud, you can create and manage archival locations to archive the disaster recovery and long-term retention data of data center workloads. + +An archival location refers to a storage bucket in which a Rubrik cluster archives its backed-up data. When one cluster archives data to a specific archival location, other clusters cannot archive to this location, but can connect to this archival location to read the data. + +When possible, the cluster uses an encrypted connection to transfer data to the archival location. The cluster deduplicates, compresses, and, when supported by the archival location type, encrypts the data on the client side before writing it to the archival location. + +A cluster can archive to multiple archival locations of different storage types. + + * Rubrik Cloud Vault + * Microsoft Azure + * Amazon S3 + * Google Cloud Platform + * NFS Shares + * Object Store (S3 compatible) + * Tape + +You can create an archival location and then add it to an SLA Domain to create an archival policy. You can configure the SLA Domain archival policy with rules that determine how data from protected workloads is archived to this archival location. + +An SLA Domain can include up to two archival policies that specify: + + * The archival locations to use for archiving snapshots on different archival locations. + * The minimum time required for archiving data after a backup. + * The duration for which that data is retained in the archival locations. + + *[ > ]: and then diff --git a/azure_blob_azr_manage_blob_storage.md b/azure_blob_azr_manage_blob_storage.md new file mode 100644 index 0000000000000000000000000000000000000000..cbf4c52ce01e6026a9955e72f79b92a0845dd2a5 --- /dev/null +++ b/azure_blob_azr_manage_blob_storage.md @@ -0,0 +1,30 @@ +# Manage Azure Blob Storage + +Source: https://docs.rubrik.com/en-us/saas/azure_blob/azr_manage_blob_storage.html + +--- + +# Manage Azure Blob Storage + +By using the protection services offered by RSC, you can protect and recover your objects in Azure Blob Storage. + +Azure Blob Storage is a cloud-based object storage solution by Microsoft. It is optimized for storing large amounts of unstructured data, which refers to data that does not adhere to a specific data model or definition, such as text or binary data. + +You can utilize Azure Blob Storage for various purposes, such as the following: + + * Serving images or documents directly to a browser + * Storing files for distributed access + * Streaming video and audio + * Writing to log files + * Storing data for backup and restore, disaster recovery, and archiving + * Storing data for analysis by an on-premises or Azure-hosted service + +RSC offers various features to safeguard objects in your Azure Blob Storage. With RSC, you can achieve the following results: + + * Protect your objects in Azure Blob Storage against ransomware attacks by taking immutable snapshots and storing those snapshots in a different location. + * Optimize costs by storing snapshots of Azure Blob Storage in lower-cost storage tiers. + * Adhere to your compliance requirements by storing your data in lower-cost storage tiers. + * Manage your Azure Blob Storage and its objects from a dashboard. + * Recover either an entire Azure Blob Storage workload or only specific objects without needing to restore the entire workload. + + *[ > ]: and then diff --git a/azure_devops_azr_devops.md b/azure_devops_azr_devops.md new file mode 100644 index 0000000000000000000000000000000000000000..2a21a48f560fedd744afa2520c7092ad8e1f82f1 --- /dev/null +++ b/azure_devops_azr_devops.md @@ -0,0 +1,25 @@ +# Azure DevOps + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops.html + +--- + +# Azure DevOps + +RSC protects the data and resources of Azure DevOps projects and repositories within the Azure DevOps organization. + +Azure DevOps is a cloud-based platform for software development, providing services for teams to collaborate on code, manage projects, and deploy applications. While Microsoft secures the underlying infrastructure, organizations retain the responsibility for protecting their application code and associated development data stored in Azure DevOps. Code repositories typically hold this application code and development data. As the intellectual property of an organization, code repositories face vulnerabilities such as outages, cyber attacks, sensitive data exposure risks, and accidental loss. + +Traditional backup solutions provide organization-level restoration. Recovering a single repository requires rolling back all organizational changes, which creates a critical gap for business continuity and data protection. + +Rubrik provides a streamlined solution to these challenges with RSC, its data protection platform based on SaaS. RSC secures and automates data protection processes for Azure DevOps organizations, ensuring data remains protected against accidental deletions, ransomware attacks, and other potential threats. With RSC, organizations can automate backup and recovery across Azure regions using a global policy model called an SLA Domain. + +RSC provides an enterprise-grade solution to secure and automate data protection processes for Azure DevOps, focusing on the critical repositories. + +Protecting Azure DevOps repositories with RSC involves a structured approach that ensures comprehensive and consistent data protection policies across the cloud infrastructure of an organization. By breaking down the tasks into three main categories, authorization, configuration, and protection, RSC simplifies the steps required to protect your Azure DevOps organization. Each task category addresses specific aspects of data security, from granting secure access to applying global policies and enforcing data protection measures. + +Task category | Description +---|--- +Authorization | For authorization, you grant RSC secure access to your Azure DevOps organization through a defined authentication and authorization workflow. This process follows the least permission model. +Configuration | For configuration, you set up backup storage locations and SLA Domains to automatically protect Azure DevOps repositories. SLA Domains enable you to define a global policy model for backup frequency and retention. The minimum frequency that you can configure in an SLA Domain is 8 hours. +Protection | For protection, you enforce data security by assigning SLA Domains to Azure DevOps projects or individual repositories and organizations. RSC then automates the backup process. diff --git a/azure_devops_azr_devops_access_reports.md b/azure_devops_azr_devops_access_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..d3810ebdd83eef1881f191c7e8101ed20981b86d --- /dev/null +++ b/azure_devops_azr_devops_access_reports.md @@ -0,0 +1,29 @@ +# Access Azure DevOps reports + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_access_reports.html + +--- + +# Access Azure DevOps reports + +With RSC, you can create and download reports based on templates to monitor the protection status of your Azure DevOps organizations, projects, and repositories. + +You can use the reporting feature of RSC for the following requirements: + + * Operational and monitoring: Monitoring backup job logs in real time and receive immediate failure notifications. + * Compliance and verification: Configuring backup reports to verify storage locations, encryption keys, and compliance adherence. + +## Available report templates + +The report templates available in RSC focus on the core security and operational aspects of protecting your Azure DevOps organizations: + + * Compliance: Provides details about policy adherence, encryption key verification, and secure storage location confirmation. + * Protection: Provides an overview of resource coverage and the overall health of protection policies. + * Protection task details: Provides detailed logs for all successful and failed backup jobs. + * Recovery task details: Provides detailed logs for all recovery and restore operations. + +Note: + +The reporting feature utilizes system metrics that enables you to perform audits and data management planning for your Azure DevOps organizations. + + *[ > ]: and then diff --git a/azure_devops_azr_devops_add_orgs.md b/azure_devops_azr_devops_add_orgs.md new file mode 100644 index 0000000000000000000000000000000000000000..7e859dd7a1805cd9ab87a2c8a26a5dba51ecc16f --- /dev/null +++ b/azure_devops_azr_devops_add_orgs.md @@ -0,0 +1,18 @@ +# Add Azure DevOps organization to RSC + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_add_orgs.html + +--- + +# Add Azure DevOps organization to RSC + +You can add Azure DevOps organization in RSC to start protecting Azure DevOps resources. + +Adding Azure DevOps organization to RSC to protect Azure DevOps resources involves the following planning tasks: + + 1. Learning about the permission categories and how to implement the least-permission model for enhanced security, as described in [Permission categories for Azure DevOps](azr_devops_permission_categories.html "For the backup and recovery tasks associated with Azure DevOps organization, projects, and repositories, RSC requires specific permissions. RSC groups these permissions into categories for granular management so that you can include or exclude these categories as required."). + 2. Setting up Exocompute for various operations such as backup and recovery to protect Azure DevOps organization, as described in [Set up Exocompute for Azure DevOps](azr_devops_set_up_exocompute.html "With the Exocompute on Azure feature, RSC launches an Azure Kubernetes Service cluster to perform backup and recovery operations to protect Azure DevOps organizations. RSC uses the Azure Kubernetes Service cluster to serve as a compute resource in your Azure DevOps organization."). + 3. Setting up backup location for backing up the Azure DevOps repositories, as described in [Set up backup location for Azure DevOps](azr_devops_set_up_backup_loc.html "RSC protects your Azure DevOps organizations, projects, and repositories. You can set up a backup location in Azure for storing the snapshots of Azure DevOps organizations, projects, and repositories."). + +After the planning is complete, you can add your Azure DevOps organization to RSC, as described in [Adding Azure DevOps organization](azure_devops_adding_orgs.html "Add Azure DevOps organization to RSC to back up and recover repositories, manage organizations, and minimize downtime."). + *[ > ]: and then diff --git a/azure_devops_azr_devops_creating_reports.md b/azure_devops_azr_devops_creating_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..4fb4656fa079fe42b605eb88217b4e10940ce98c --- /dev/null +++ b/azure_devops_azr_devops_creating_reports.md @@ -0,0 +1,33 @@ +# Creating reports for Azure DevOps + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_creating_reports.html + +--- + +# Creating reports for Azure DevOps + +Create reports for the Azure DevOps organization to view information such as compliance status and protection status using the available templates. You can use the information generated in the reports to perform audits and data management planning. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. Click Reports. + +The Reports page appears. + + 4. Click Create Report. + +The Create a Report wizard appears. + + 5. Select a report template from the list of templates. + 6. Click Preview and Edit. + 7. Review your settings and click Create. + +## Results + +RSC displays the report. + *[ > ]: and then diff --git a/azure_devops_azr_devops_manage_organizations.md b/azure_devops_azr_devops_manage_organizations.md new file mode 100644 index 0000000000000000000000000000000000000000..604d7403291cb74d33e692f03acbf8c987b67a2a --- /dev/null +++ b/azure_devops_azr_devops_manage_organizations.md @@ -0,0 +1,56 @@ +# Manage Azure DevOps organizations + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_manage_organizations.html + +--- + +# Manage Azure DevOps organizations + +After completing the protection setup for Azure DevOps organizations, projects, and repos, RSC takes automated snapshots of those repos based on the configured policies in SLA Domains. You can also take on-demand snapshots and refresh Azure DevOps organizations for better resource management. + +After you have completed the protection setup for Azure DevOps organizations, projects, and repos, RSC starts taking automated snapshots of those repos according to the data protection policies you configured in the assigned SLA Domains. + +You can view detailed snapshot information on the inventory page for Azure DevOps organizations, projects, and repos. + +The following table describes the actions and management capabilities available across the Summary, Projects, Repos, and Organizations tabs within the Azure DevOps inventory page. Tab | Description +---|--- +Summary | You can perform the following actions: + + * Adding organizations + * Viewing organization status to understand the number of organizations connected and missing permissions + * Viewing the number of connected projects and repos + * Viewing the percentage of successful and failed backup jobs + * Viewing events + + +Projects | You can perform the following actions: + + * Viewing the list of projects in various organizations + * Sorting and filtering projects based on the assigned SLA Domain or Organization + * Managing protection of projects + * Searching for a project + + +Repos | You can perform the following actions: + + * Viewing the list of repos within various projects + * Managing protection of repos + * Searching for a repo + * Sorting and filtering the repos based on the assigned SLA domain, organization, project, and status + * Viewing snapshots associated with each repo + * Recovering repos + * Taking an on-demand snapshot of a repo + + +Organizations | You can perform the following actions: + + * Viewing the list of added organizations + * Sorting the organizations based on the assigned SLA Domain + * Refreshing organizations + * Managing protection of organizations + * Searching for an organization + * Editing the organization details + * Updating missing permissions + * Removing an organization + + *[ > ]: and then diff --git a/azure_devops_azr_devops_plan_protection.md b/azure_devops_azr_devops_plan_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..a401e14b33886f2252483d81f5a58353b8f73f3f --- /dev/null +++ b/azure_devops_azr_devops_plan_protection.md @@ -0,0 +1,20 @@ +# Plan your Azure DevOps protection + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_plan_protection.html + +--- + +# Plan your Azure DevOps protection + +Before setting up an Azure DevOps organization in RSC, you are required to plan the user and access management for designated RSC users. This planning also involves reviewing the permissions that RSC requires in your Azure environment to protect your Azure DevOps organizations. + +When planning Azure DevOps protection, it is important that you understand the following information and complete the required tasks: + + * Establish a clear framework for user and access management to ensure secure and efficient operations within your Azure environment. You can start by categorizing your RSC users based on their roles and responsibilities and by assigning appropriate privileges through roles to limit access according to the principle of least privilege. For more information, see [RSC user management for Azure DevOps](azr_devops_user_management.html "Designating specific users with appropriate privileges and roles in RSC enhances security for managing Azure DevOps organization."). + * Review the specific permissions that RSC requires to protect your Azure DevOps organizations. Understanding these permissions helps explain why they are needed. By doing this, you can gain clarity on the operations being implemented to protect your Azure DevOps organizations. For more information, see [Required RSC permissions for Azure DevOps](azr_devops_req_rsc_perms.html "RSC requires certain permissions to protect Azure DevOps organization, configure an Exocompute instance, store data, and manage encryption of the stored data."). + * Review the protection limitation associated with Azure DevOps protection. For more information, see [Azure DevOps protection limitations](azr_devops_protection_limitation.html "Information about RSC limitations for Azure DevOps protection."). + +Note: + +After completing the planning for Azure DevOps protection, the next step is to [Add Azure DevOps organization to RSC](azr_devops_add_orgs.html "You can add Azure DevOps organization in RSC to start protecting Azure DevOps resources."). + *[ > ]: and then diff --git a/azure_devops_azr_devops_protection_key_features.md b/azure_devops_azr_devops_protection_key_features.md new file mode 100644 index 0000000000000000000000000000000000000000..6efb29bab2f4eea62c383d707cb17190cb94ef54 --- /dev/null +++ b/azure_devops_azr_devops_protection_key_features.md @@ -0,0 +1,60 @@ +# Key features for protecting Azure DevOps + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_protection_key_features.html + +--- + +# Key features for protecting Azure DevOps + +RSC provides unified data management, automated global data protection, various recovery options, and additional security features to protect your Azure DevOps organization. + +RSC offers a comprehensive approach for protecting your Azure DevOps organization by focusing on key security and data management principles. While native Azure tools have limitations, RSC provides enhanced capabilities to ensure the cyber resilience of your source code and pipelines. + +The key features for Azure DevOps organization protection include: + + * Unified data management + * Automated global data protection through SLA Domains + * Immutable backup copies + * Recovery option for Azure DevOps repositories + +## Unified data management + +Feature | Description +---|--- +RSC | Provides a SaaS platform for Azure DevOps organization protection. RSC acts as a single, unified management plane for protecting data. This reduces complexity and operational overhead, giving you a clear, centralized view of your data protection posture. +Consolidated monitoring and reporting | Provides unified reporting to track SLA Domain assignment, protection and recovery activity, and SLA Domain policy compliance. +Enhanced compliance and governance | Enables you to meet regulatory and compliance mandates by providing auditable backup and recovery processes. + +## Comprehensive data protection + +Feature | Description +---|--- +Cyber resilient automated backups | RSC provides automated, policy-based backups of your Azure DevOps projects and repositories, addressing the critical gap where native Azure version control lacks a robust, air-gapped backup solution against malicious deletions, ransomware, or accidental data loss. +Immutability | RSC creates immutable backups that cannot be altered or deleted, thereby protecting your data from ransomware and other threats that attempt to corrupt or destroy backups. +Air-gapped backups | RSC stores backups in a separate, secure location, thereby making sure that your backup data remains isolated and safe even if your Azure DevOps environment is compromised. +Backup of all Azure DevOps resources | RSC backs up all projects and repositories within your Azure DevOps organization. +Incremental backups and immutable storage | RSC provides an enterprise-grade solution for efficient and frequent backups with protection against modification or deletion. + +## Advanced recovery capabilities + +Feature | Description +---|--- +Rapid restore | RSC provides a near-zero Recovery Time Objective (RTO), enabling you to quickly recover data and minimize impact on development and delivery cycles. +Disaster recovery support | RSC provides flexible restore capabilities, including options for restoring data to a new, dedicated recovery organization, across different organizations, or across projects. +Automated restore | RSC supports the prioritization of critical applications and repositories for quicker automated recovery. + +## Security and control + +Feature | Description +---|--- +Air-gapped backups | Ensures backups are logically isolated and not immediately accessible from the development environment to mitigate ransomware risk. +Strict security controls | Provides 256-bit encryption, Server-Side encryption (SSE), and verification of the backup process and data flow. +Data sovereignty and Bring Your Own Storage (BYOS) | Supports control over data sovereignty and the BYOS model, important for large enterprises and financial institutions. + +## Enterprise-ready management + +Feature | Description +---|--- +Role-based Access Control (RBAC) | Defines specific permissions for different roles. This means granting read-only access for standard backup operations, typically performed by a service account, and reserving elevated access only for restore operations. RBAC also differentiates access between central administrators and individual team members. +Scalability | Handles large-scale environments. + *[ > ]: and then diff --git a/azure_devops_azr_devops_quick_links.md b/azure_devops_azr_devops_quick_links.md new file mode 100644 index 0000000000000000000000000000000000000000..fc12da73c8c28e2eb917c68db5eb6ffe99f04eb5 --- /dev/null +++ b/azure_devops_azr_devops_quick_links.md @@ -0,0 +1,35 @@ +# Quick links for Azure DevOps + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_quick_links.html + +--- + +# Quick links for Azure DevOps + +Immediate access to important tasks and information, enabling quick setup, daily operations, and critical recovery. + +## Initial setup and onboarding + + * [Required RSC permissions for Azure DevOps](azr_devops_req_rsc_perms.html "RSC requires certain permissions to protect Azure DevOps organization, configure an Exocompute instance, store data, and manage encryption of the stored data.") + * [Adding Azure DevOps organization](azure_devops_adding_orgs.html "Add Azure DevOps organization to RSC to back up and recover repositories, manage organizations, and minimize downtime.") + * [Managing granular permissions for Azure DevOps organization](azr_devops_managing_granular_permissions.html "Update granular permissions for Azure DevOps organization when needed.") + * [Set up Exocompute for Azure DevOps](azr_devops_set_up_exocompute.html "With the Exocompute on Azure feature, RSC launches an Azure Kubernetes Service cluster to perform backup and recovery operations to protect Azure DevOps organizations. RSC uses the Azure Kubernetes Service cluster to serve as a compute resource in your Azure DevOps organization.") + * [Set up backup location for Azure DevOps](azr_devops_set_up_backup_loc.html "RSC protects your Azure DevOps organizations, projects, and repositories. You can set up a backup location in Azure for storing the snapshots of Azure DevOps organizations, projects, and repositories.") + * [Creating a custom SLA Domain for Azure DevOps](azr_devops_creating_custom_sla_domain.html "Create a custom SLA Domain to streamline and customize the Azure DevOps organization protection and management policies.") + * [Assigning protection to Azure DevOps](azr_devops_assigning_protection.html "Assign a data protection policy to specific Azure DevOps organization, projects, or repositories.") + +## Daily operations and monitoring + + * [Viewing Azure DevOps inventory](azr_devops_viewing_inventory.html "View the Azure DevOps inventory page to manage Azure DevOps organizations, projects, and repos.") + * [Refreshing an Azure DevOps Organization](azr_devops_refreshing_organization.html "Refresh an Azure DevOps organization as an on-demand task to retrieve the latest metadata of all projects and repositories from Azure DevOps.") + * [Taking on-demand snapshots of Azure DevOps repository](azr_devops_taking_ods.html "Take an on-demand snapshot of the Azure DevOps repository.") + * [Azure DevOps details](azure_devops_details.html "RSC monitors, analyses, and restores Azure DevOps repositories associated with the Azure DevOps projects and organizations. RSC also shows the important details such as organization status, protected projects, and protected repos, and summary of backup jobs.") + * [Viewing events for Azure DevOps](azr_devops_viewing_events.html "View the Events page from the Data Protection dashboard to see the events for the Azure DevOps organization.") + * [Event log details for Azure DevOps](azr_devops_event_log_details.html "The Events page displays the events occurring in all Azure DevOps organizations, shown in the local time zone.") + * [Creating reports for Azure DevOps](azr_devops_creating_reports.html "Create reports for the Azure DevOps organization to view information such as compliance status and protection status using the available templates. You can use the information generated in the reports to perform audits and data management planning.") + +## Recovery and troubleshooting + + * [Recovering Azure DevOps projects and repos](azr_devops_recovering_proj_repos.html "Recover Azure DevOps projects and repositories from a protected snapshot.") + + *[ > ]: and then diff --git a/azure_devops_azr_devops_recover.md b/azure_devops_azr_devops_recover.md new file mode 100644 index 0000000000000000000000000000000000000000..980b140ee188913e5e587788648533d6c6b32511 --- /dev/null +++ b/azure_devops_azr_devops_recover.md @@ -0,0 +1,18 @@ +# Recover Azure DevOps + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_recover.html + +--- + +# Recover Azure DevOps + +After RSC takes snapshots of your Azure DevOps repositories, you can recover the necessary details. + +After completing the protection setup for your Azure DevOps organizations, RSC starts protecting your data by taking snapshots based on the configured policies in the assigned SLA Domains. You can recover the projects and repositories from these snapshots using various recovery options based on your specific requirements. + +Note: + +Rubrik recommends adding an Azure DevOps organization based on the least privilege model, which involves selecting only the Basic permission category. When a recovery operation becomes necessary, you can then elevate the permissions for recovery purposes. + +Before beginning the recovery operations, it is important to evaluate the privilege elevation options and learning how to assign a permission category for recovery. If the destination organization lacks recovery permissions, you can elevate those permissions using an option available during the recovery process itself. + *[ > ]: and then diff --git a/azure_devops_azr_devops_set_up_protection.md b/azure_devops_azr_devops_set_up_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..e11b6a95f4f9f6dad489d656478de1b4087964cd --- /dev/null +++ b/azure_devops_azr_devops_set_up_protection.md @@ -0,0 +1,26 @@ +# Set up protection for Azure DevOps + +Source: https://docs.rubrik.com/en-us/saas/azure_devops/azr_devops_set_up_protection.html + +--- + +# Set up protection for Azure DevOps + +You can set up SLA Domains to apply data protection policies, ensuring automatic and hierarchical protection of Azure DevOps organizations, projects, and repositories, with granular control overriding higher-level assignments. + +Ensuring that your Azure DevOps organizations, projects, and repositories are secure and recoverable is essential. The SLA Domain feature of Rubrik offers a structured way to apply data protection policies across various Azure DevOps organizations, ensuring consistent and reliable backup and recovery processes. An SLA Domain is a set of policies that define the backup and recovery objectives for your data. These policies specify the frequency of snapshots and the retention period for these snapshots. + +By assigning SLA Domains to Azure DevOps organizations, you ensure that your data protection strategies align with your organizational requirements and compliance standards. RSC enables hierarchy-based, automatic protection for Azure DevOps. This automatic protection mechanism simplifies the process of assigning protection to large numbers of workloads. The hierarchy-based approach simplifies protection assignment across large numbers of repositories and ensures your data protection strategies align with organizational requirements. + +After you add an Azure DevOps organization to RSC, you need to create one or more SLA Domains to begin protecting Azure DevOps organizations. Then, you can assign these SLA Domains to different Azure DevOps organizations, projects, and repositories. RSC then starts backing up the snapshots associated with Azure DevOps organizations. + +Note: + +RSC supports a minimum snapshot frequency of 8 hours. + +Entity | Description +---|--- +Azure DevOps organization | Assigning SLA Domain settings at the organization level to ensure all the projects and repositories within this organization adhere to the protection policies. +Projects | Assigning SLA Domain settings at the project level for managing protection policies for grouped resources. A project is a logical grouping within an organization where teams collaborate on software development. A project contains repos, pipelines, work items, artifacts, and settings. +Repos | Assigning SLA Domain settings to a specific Azure DevOps repository for granular control. + *[ > ]: and then diff --git a/cdm_ahv_network_segmentation_on_nutanix_clusters.md b/cdm_ahv_network_segmentation_on_nutanix_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..6ce525ae58cb21de006dd65d7b05a51026c70133 --- /dev/null +++ b/cdm_ahv_network_segmentation_on_nutanix_clusters.md @@ -0,0 +1,22 @@ +# Network segmentation on Nutanix clusters + +Source: https://docs.rubrik.com/en-us/saas/cdm/ahv_network_segmentation_on_nutanix_clusters.html + +--- + +# Network segmentation on Nutanix clusters + +Rubrik supports AHV virtual machine backup from Nutanix clusters that have network segmentation enabled. + +When network segmentation is enabled on Nutanix clusters, Rubrik clusters back up Nutanix virtual machines over the segmented volumes network instead of using the default AOS management network. + +The network segmentation process creates a separate network for service-specific communication on a Nutanix cluster and enables logical segmentation of traffic over a selected VLAN through a new segmented data services IP address. + +Using the segmented data services IP address to route the backup traffic from the Nutanix cluster to the Rubrik cluster makes it easy to secure the traffic by isolating the traffic into a separate network. + +Backing up AHV virtual machines from Nutanix clusters with network segmentation enabled requires the following: + + * A Rubrik cluster running Rubrik CDM version 6.0.2 or later + * Data center network configuration to encapsulate, decapsulate, and route packets between the Rubrik backup VLAN and the Nutanix volume VLAN + + *[ > ]: and then diff --git a/cdm_ahv_virtual_machine_scripts.md b/cdm_ahv_virtual_machine_scripts.md new file mode 100644 index 0000000000000000000000000000000000000000..c6ce447d578aec5c12b32346effc1d98b20d0393 --- /dev/null +++ b/cdm_ahv_virtual_machine_scripts.md @@ -0,0 +1,50 @@ +# AHV virtual machine scripts + +Source: https://docs.rubrik.com/en-us/saas/cdm/ahv_virtual_machine_scripts.html + +--- + +# AHV virtual machine scripts + +You can configure the Rubrik cluster to run scripts on a guest OS before creating a snapshot, after creating a snapshot, and after the Rubrik cluster completes the backup process. + +The ability to have the Rubrik cluster initiate scripts on a host system allows you to: + + * Put the guest OS in a specific state before creating a snapshot + * Change the guest OS state after the snapshot is created on the host system + * Perform other actions after the Rubrik cluster processes a snapshot + +Rubrik Backup Service (RBS) must be installed to enable the Rubrik cluster to run scripts. + +To allow the Rubrik cluster to start scripts, you must provide Guest OS credentials with sufficient privileges. + +For example, you can run a script to quiesce applications before a snapshot, another script to restore the applications to their normal running status after the snapshot, and a final script to perform clean-up at the end of the backup process. + +The scripts can consist of any sequence of operations that can be run by the command line interpreter of the guest OS. + +The following table describes the virtual machine pre/post scripts. + +Name | Description +---|--- +Pre-Backup Script | + + * You can use the pre-backup script to prepare for a backup by quiescing the applications on the virtual machine. + * The pre-backup script requires that a timeout value be specified. + * The Web UI provides an option to cancel the backup task when the pre-backup script does not complete successfully. + + +Post-Snap Script | Must be idempotent, script may be invoked several times during a single backup task. + + * You can use a post-snap script to minimize stun time and resume all applications on the virtual machine. + * You can use a post-snap script to perform clean-up tasks if a backup task fails. + * The post-snap script requires that a timeout value be specified. + * The post-snap script runs immediately after the host snapshot task completes. + + +Post-Backup Script | Must be idempotent, script may be invoked several times during a single backup task. + + * You can use a post-backup script to perform custom post-processing at the end of the backup process. + * The post-backup script requires that a timeout value be specified. + * The post-backup script runs after the snapshot is copied to the Rubrik cluster and released on the virtual machine host, and the Rubrik cluster completes all data and metadata processing tasks. + + *[ > ]: and then diff --git a/cdm_cli_access_through_ssh.md b/cdm_cli_access_through_ssh.md new file mode 100644 index 0000000000000000000000000000000000000000..9414478866c6f0f16a5229f38d85e45903013e4e --- /dev/null +++ b/cdm_cli_access_through_ssh.md @@ -0,0 +1,34 @@ +# CLI access through SSH + +Source: https://docs.rubrik.com/en-us/saas/cdm/cli_access_through_ssh.html + +--- + +# CLI access through SSH + +SSH protocol is the standard way for Rubrik CDM users to access the Rubrik CLI. To use the SSH protocol, users require both administrator and CLI administrator roles. + +If you are a Rubrik CDM user and have both the administrator role and the CLI administrator role, you can connect to the Rubrik CLI through SSH. + +If you have not already set up multifactor authentication (MFA) through the Rubrik CDM UI, at your first Rubrik CLI session, when you enter your password, you are prompted to set up MFA. + +You can perform the following SSH password support actions: + + * Enable or disable password support for SSH passwords from the Rubrik cluster web UI. + * Establish and change the SSH key that the Rubrik cluster uses to authenticate SSH login attempts that do not require passwords. + +LDAP and SSO users do not have SSH access. + +Password authentication for SSH sessions is enabled by default. Based on the configuration, SSH sessions might require individual users to generate an SSH key specific to that user account. You can configure Rubrik CDM so that it does not require a password for accounts configured to use SSH key authentication. An account that does not require a password uses the SSH key exchange between the system that initiates the terminal session and the Rubrik cluster for authentication. Authentication that uses an SSH key might also require a passphrase at each login. The passphrase is set when generating the SSH key. The passphrase is not the same as the account password. + +With SSH key authentication, a user with the administrator role must upload the public component of the SSH key to the Rubrik cluster. Uploading the public component of the key pair does not require the CLI administrator role. + +Changes to authentication methods for the CLI can take up to a minute to propagate to all nodes in the Rubrik cluster. + +A 10-minute idle session timeout for idle login sessions is enabled by default. You can configure this setting with the following local Forge configuration variables. + +Variable | Description +---|--- +killIdleSession | Enables the idle session killer +idleSessionTimeout | Displays the timeout for idle login sessions in seconds + *[ > ]: and then diff --git a/cdm_cli_administrator_role.md b/cdm_cli_administrator_role.md new file mode 100644 index 0000000000000000000000000000000000000000..da53a964825cf4451d111fddf3583f8143a95e19 --- /dev/null +++ b/cdm_cli_administrator_role.md @@ -0,0 +1,15 @@ +# CLI administrator role + +Source: https://docs.rubrik.com/en-us/saas/cdm/cli_administrator_role.html + +--- + +# CLI administrator role + +As a CLI administrator, a Rubrik cluster user can connect to nodes in Rubrik clusters through the CLI Secure Shell (SSH) protocol. + +As both an administrator and a CLI administrator, you can assign the CLI administrator role (CliAdminRole) to others who have the administrator role. With that role, they can connect to nodes in the Rubrik cluster through the Secure Shell (SSH) protocol and use the full range of CLI commands. + +The CLI administrator role cannot be assigned to a username that contains a dot (.) character. + +Regardless of their assigned roles, only Rubrik CDM local users can connect using SSH. LDAP and SSO users are denied SSH access. diff --git a/cdm_config_ssh_key_auth_for_cli.md b/cdm_config_ssh_key_auth_for_cli.md new file mode 100644 index 0000000000000000000000000000000000000000..0f6caa209f95dc23dff12f77baa909e970aa8d7c --- /dev/null +++ b/cdm_config_ssh_key_auth_for_cli.md @@ -0,0 +1,32 @@ +# Configuring authentication to the Rubrik CLI by SSH key pair + +Source: https://docs.rubrik.com/en-us/saas/cdm/config_ssh_key_auth_for_cli.html + +--- + +# Configuring authentication to the Rubrik CLI by SSH key pair + +You can assign a Secure Shell key to a user account. With this key users can authenticate as a Rubrik cluster administrator without the need to transmit an account password. + +## Before you begin + +You must obtain the public Secure Shell (SSH) protocol key for the user account and copy the SSH key to the clipboard. The key must be in the OpenSSH format. + +## About this task + +This task assigns an SSH key to a user account. Multiple methods and utilities exist for generating SSH keys. You can use any OpenSSH format method that results in a valid SSH key. Authenticating with an SSH key pair does not require transmitting the password to the user account, but key pairs generated with a passphrase still require the passphrase to authenticate a login attempt. + +## Procedure + + 1. Log in to the Rubrik CDM web UI as the Rubrik cluster administrator. + 2. From the dropdown, select SSH Configuration. + +The SSH configuration dialog box appears. + + 3. In the SSH keys field, paste the SSH key. + 4. Click Update. + +## Results + +The Rubrik cluster saves the configuration and the SSH key can be used to create authenticated sessions for the account. + *[ > ]: and then diff --git a/cdm_disabling_ssh_passwords.md b/cdm_disabling_ssh_passwords.md new file mode 100644 index 0000000000000000000000000000000000000000..ba2c8fc967730b43d5c84118c9c91034bfd2d46a --- /dev/null +++ b/cdm_disabling_ssh_passwords.md @@ -0,0 +1,35 @@ +# Disabling SSH password authentication + +Source: https://docs.rubrik.com/en-us/saas/cdm/disabling_ssh_passwords.html + +--- + +# Disabling SSH password authentication + +Disable password authentication for Secure Shell sessions to authenticate using SSH key pairs. + +## About this task + +Password support for connecting to a Rubrik cluster node using the Secure Shell (SSH) protocol is enabled by default. Disabling password support limits authentication to using SSH key pairs. + +## Procedure + + 1. Log in to the Rubrik CDM web UI as a user with the Administrator role. + 2. Click the gear icon. + 3. Click Users. + +The Users page appears. + + 4. Select the Users and Groups tab. + 5. Click the ellipsis menu in the top bar and select SSH Authentication Options from the list. + +By default, Secure Shell (SSH) password authentication is enabled. + +The SSH Authentication Options dialog box appears. + + 6. Turn off SSH Password Authentication and click Save. + +## Results + +The Rubrik cluster disables SSH password authenticated sessions on its nodes. + *[ > ]: and then diff --git a/cdm_enabling_jumbo_frames.md b/cdm_enabling_jumbo_frames.md new file mode 100644 index 0000000000000000000000000000000000000000..84ba25e100a25001ad743beefd59bb43655a5ebc --- /dev/null +++ b/cdm_enabling_jumbo_frames.md @@ -0,0 +1,75 @@ +# Enabling jumbo frames + +Source: https://docs.rubrik.com/en-us/saas/cdm/enabling_jumbo_frames.html + +--- + +# Enabling jumbo frames + +Use the Rubrik CLI to enable jumbo frames by changing the maximum transmission unit settings on the Rubrik cluster. + +## About this task + +The network mtu set command can indicate whether your deployment uses a shared or split network interface. + + * Clusters in a shared deployment use the same network interface for DATA and MANAGEMENT. + * Clusters in a split deployment use different network interfaces for DATA and MANAGEMENT + +## Procedure + + 1. Log in to the Rubrik CLI using the administrator account by opening an SSH session on a node of the Rubrik cluster. + 2. At the prompt, enter `ssh admin@node_ip`. + +Where node_ip is the IPv4 address of the node with the maximum transmission unit (MTU) setting you want to view. + +A field to enter the administrator password appears. + + 3. At the prompt, enter the password for the administrator account. + +The Rubrik CLI prompt appears. + + 4. At the Rubrik CLI prompt, enter `rkcli` to start the Rubrik CLI shell. + +The Rubrik CLI prompt appears + + 5. Enter the network mtu set command to configure your MTU settings. + 6. In Network Interface Type, specify the interface type for which you are setting the MTU. + +In a shared deployment, Network Interface Type requires a value of MANAGEMENT. In a split deployment, Network Interface Type requires a value of MANAGEMENT or DATA. + + 7. In MTU value, enter the value to which you are setting the MTU for the network interface on this Rubrik cluster specified in step [6](#enabling_jumbo_frames__network_interface). + +The Rubrik cluster allows for a minimum value for MTU of 1500, and a maximum value for MTU of 10000. + + 8. Enter `yes` to confirm the MTU setting change. + +## Results + +You have enabled jumbo frames by changing the MTU value for the Rubrik cluster. + +## Example + +This example sets the value for MTU on MANAGEMENT interface on the Rubrik Cluster to 9000: + + + vm-machine-123abc >> network mtu set + ==================================== + Set MTU for InterfaceType on Cluster + ==================================== + This is a Shared DATA/MANAGEMENT Cluster + Supported Interface Type for MTU is MANAGEMENT + DATA and MANAGEMENT, both are on bond0 + + Enter the input ... + + Network Interface Type: management + Invalid input, retry. + Network Interface Type: MANAGEMENT + MTU value: 9000 + Confirm MTU Setting: + { + "networkInterfaceType": "MANAGEMENT", + "mtuValue": 9000 + } + Type "yes" to continue: yes + *[ > ]: and then diff --git a/cdm_envoy_features.md b/cdm_envoy_features.md new file mode 100644 index 0000000000000000000000000000000000000000..9047d527a775be282ce96e75714186986e26ed1b --- /dev/null +++ b/cdm_envoy_features.md @@ -0,0 +1,61 @@ +# Envoy features + +Source: https://docs.rubrik.com/en-us/saas/cdm/envoy_features.html + +--- + +# Envoy features + +The Rubrik Envoy virtual appliance connects tenant networks to the Rubrik cluster. Multiple features make the data movement possible. + +A Managed Service Provider (MSP) multi-tenant environment hosts tenants that manage their own networks. Tenants can have NAT devices that block access from outside. Most workloads, however, require direct connectivity to backup targets. This means that backup hosts must be reachable and addressable. Rubrik Envoy provides a data-path proxy solution for data movement from the tenant networks, through the service provider network, to the Rubrik cluster and back. + +Rubrik Envoy uses the Virtual Disk Development Kit (VDDK) software development kit to back up and recover the snapshot files of a tenant virtual machine. + +## Supported workloads + +Envoy protects and provides file-level recovery for: + + * Linux and Unix filesets + * Microsoft Windows filesets + * Microsoft Windows volume groups + * Microsoft SQL Server databases + * NFS-based Oracle databases + * VMware virtual machine images (block-level copies of an entire hard drive from which you can restore files) + +## Backup-as-a-service (BaaS) + +Envoy facilitates backup-as-a-service offerings in multitenant environments with segmented or overlapping network topologies. + +## Simple setup + +In most situations, Envoy requires no change to the tenant-side firewall, because each virtual appliance requires only outbound network communication with the provider-side Rubrik cluster. + +## Dual network interface support + +In Rubrik CDM version 8.0.2 and later, Envoy supports both single and dual Ethernet interfaces. The default mode has a single eth0 interface and establishes a secure tunnel through outbound and inbound firewalls over defined ports. An optionally configured second interface, eth1, allows Rubrik Envoy to act as a bridge between the two interfaces (bridge mode). + +## Scale out + +Multiple instances of Envoy can work together in the same tenant network of a single organization to increase performance and provide high availability. You can add or remove Rubrik Envoy virtual appliances to allow tenant workloads to redistribute among all available Rubrik Envoy virtual appliances registered with the tenant organization. + +## Deployment file format + +The Envoy virtual appliance is distributed in an .ova (vmware) format. + +## Envoy appliance support + +Each tenant organization can support up to four registered Envoy virtual appliances. + +## Self-service registration + +Any user who has a global administrator role on the Rubrik cluster of the organization can manage Envoy appliances connected to the organization. + +## Secure communication + +After Envoy is registered, it establishes a bidirectional, secure connection between itself and the Rubrik cluster. This connection uses AES256 encryption with a TLS 1.2 cipher to ensure secure communication. + +## Command Line Interface (CLI) + +Support for access to a Envoy CLI by administrator accounts. The Envoy CLI can handle most Envoy configuration and registration tasks. + *[ > ]: and then diff --git a/cdm_envoy_security.md b/cdm_envoy_security.md new file mode 100644 index 0000000000000000000000000000000000000000..169d8df34c05f3f20af5ca823edead52793c8056 --- /dev/null +++ b/cdm_envoy_security.md @@ -0,0 +1,20 @@ +# Envoy security + +Source: https://docs.rubrik.com/en-us/saas/cdm/envoy_security.html + +--- + +# Envoy security + +Rubrik Envoy provides secure multitenancy. + +The goal of secure multitenancy is to maintain effective tenant boundaries. Rubrik Envoy allows each tenant network to operate independently and have its own outbound firewall. + +Envoy uses a shared NAT configuration to provide each tenant network with secure connectivity for protected workloads. Each tenant network can configure its own firewall for outbound communication to a single, shared inbound address at the provider. In many cases, this outbound firewall can be the same firewall that is connected to the internet, but it could also be connected to a shared, isolated portion of the network, if public IP addresses are either not available or are undesirable. + +Envoy passes the protected workload data securely to the Rubrik cluster over an encrypted secure connection. Multiple tenants, regardless of the networks they use, can then securely access and use Rubrik services on a shared Rubrik cluster. + +Registering Envoy with a Rubrik cluster requires authentication when establishing a connection. If the NAT target is an internet IP address, the TCP port 443 (HTTPS) must be available on Rubrik CDM. + +To authenticate Envoy during registration, you can use an API session token. A user with the organization administrator role in the tenant organization, or a user with the administrator role on the Rubrik Security Cloud, can register Envoy to an organization network. + *[ > ]: and then diff --git a/cdm_envoy_topology.md b/cdm_envoy_topology.md new file mode 100644 index 0000000000000000000000000000000000000000..f539582e450f8a0140802662a2579424096c6663 --- /dev/null +++ b/cdm_envoy_topology.md @@ -0,0 +1,22 @@ +# Envoy topology + +Source: https://docs.rubrik.com/en-us/saas/cdm/envoy_topology.html + +--- + +# Envoy topology + +Rubrik Envoy allows tenant organizations to connect to Rubrik services on a shared Rubrik cluster. + +Acting as a network proxy, Rubrik Envoy allows multiple tenants to connect securely to Rubrik services on a shared Rubrik cluster, regardless of the IP networks used by the tenants. + +Envoy works within service provider environments where the tenants manage or define their own networks. Due to the potential mix of networks, the management routing domain in such environments offers no connectivity to tenant workloads that require data protection and security. Envoy is designed to reside in that management routing domain and provide secure connectivity for those protected tenant workloads. + +Envoy can be configured to connect to NAT addresses in a shared routing space, such as the internet or a designated isolated portion of a network. This permits multiple tenants to securely access and use Rubrik services on a shared Rubrik CDM cluster, regardless of their network configurations. Envoy passes the protected data securely to the Rubrik cluster through an encrypted connection. + +Envoy is stateless, meaning it does not retain any customer data. You can deploy two or more Envoy virtual appliances to allow connection redundancy. As new Rubrik Envoy virtual appliances are added or removed, tenant workloads can redistribute among all available Rubrik Envoy virtual appliances registered with the tenant organization. + +Envoy consists of one or more virtual appliances deployed in a tenant network. Preparing to deploy a Envoy virtual appliance starts with specifying the target address of the Rubrik CDM interface. Envoy initiates the connection, allowing it to pass through an outbound NAT, which is the PAT that maps multiple private IP addresses to a single public IP address by using different ports. + +When Envoy successfully authenticates with a Rubrik cluster a secure bidirectional connection is established. This secure connection eliminates the need for inbound firewall rules at the tenant perimeter. + *[ > ]: and then diff --git a/cdm_guest_os_credentials.md b/cdm_guest_os_credentials.md new file mode 100644 index 0000000000000000000000000000000000000000..38f9466d5db58f488c6172139e94a09d6d9d1a7b --- /dev/null +++ b/cdm_guest_os_credentials.md @@ -0,0 +1,46 @@ +# Guest OS credentials + +Source: https://docs.rubrik.com/en-us/saas/cdm/guest_os_credentials.html + +--- + +# Guest OS credentials + +Guest OS credentials are the username and password that a Rubrik cluster uses to provide access to the guest operating system and files of a vSphere virtual machine. When Rubrik Backup Service is not installed or disconnected, you can use guest OS credentials to recover virtual machine files. + +To provide file-level protection of a vSphere virtual machine, a Rubrik cluster requires either guest OS credentials for the virtual machine or a valid installation of Rubrik Backup Service (RBS) on the virtual machine. Installing and registering RBS is the preferred method of providing the required access to a guest operating system, but guest OS credentials can be used instead. + +To enable a Rubrik cluster to operate effectively on a vSphere virtual machine, it must have guest OS credentials that permit the following actions: + + * Running scripts + * Performing file-level restores + * Deploying RBS on the vSphere virtual machine + * Taking snapshots of the vSphere virtual machine + * Recovering files through VMware tools + * Executing pre- or post-backup scripts through VMware tools + +To run scripts on a virtual machine, a Rubrik cluster requires one of the following: + + * RBS installed on the virtual machine and registered with the Rubrik cluster. + * Guest OS credentials with sufficient privileges for the virtual machine and a current version of VMware Tools installed on the virtual machine. + +## Guest OS credentials for file-level restores + +While creating or updating an organization or role, you can assign specific permissions to a user role for managing or viewing the guest OS credentials. + +The guest OS credentials that you provide to permit file-level restores on a virtual machine require specific permissions based on the operating system type, either Linux or Windows. + +## Guest OS permissions + +For a Linux guest operating system, the guest OS credential must provide Write permission for the restore locations. + +For a Windows guest operating system, the required credentials must provide permissions that enable file-level restore and application-consistent snapshots. To do this, the guest OS credentials must provide administrator-level access to the guest operating system. This can be either through an administrator account on the guest operating system or a domain account that has administrator access to the guest operating system. + +## Considerations while selecting Windows guest accounts + +Selecting an account type for accessing a Windows guest involves considering the following aspects: + + * Providing a local administrator account for each Windows guest involve significant administrative effort. + * Using a domain-level account that has administrator access to Windows guests involve domain security considerations. + +Rubrik recommends that you use a domain-level account that limits permissions to only administrator access for the relevant Windows guest virtual machines. You can create several accounts of this type to meet your organizational data restrictions. diff --git a/cdm_guest_os_settings.md b/cdm_guest_os_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..3c0aeda316e3ee7be57c3db76827d859e2b7e3eb --- /dev/null +++ b/cdm_guest_os_settings.md @@ -0,0 +1,14 @@ +# Guest OS settings + +Source: https://docs.rubrik.com/en-us/saas/cdm/guest_os_settings.html + +--- + +# Guest OS settings + +Enable the administration of guest OS credentials for virtual machines. When Rubrik Backup Service is not installed or not connected to your cluster, you can recover vSphere virtual machine files through guest OS credentials. + +From the Guest OS Settings page, you can manage the administration of guest OS credentials for virtual machines such as, adding, editing, deleting, and viewing guest OS credentials. + +The Rubrik cluster uses guest OS credentials to provide application-consistent snapshots of vSphere virtual machines running in a Windows or Linux guest operating system. The Rubrik cluster also uses guest OS credentials to enable direct restore of files and folders to guest operating systems that do not have the RBS installed. The guest OS credentials are added through the Restore File dialog box during a direct restore. + *[ > ]: and then diff --git a/cdm_hyperv_vm_snapshots.md b/cdm_hyperv_vm_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..0f1f1c18851a83c27000cb8ff7dc59a030acad82 --- /dev/null +++ b/cdm_hyperv_vm_snapshots.md @@ -0,0 +1,16 @@ +# Hyper-V virtual machine snapshots + +Source: https://docs.rubrik.com/en-us/saas/cdm/hyperv_vm_snapshots.html + +--- + +# Hyper-V virtual machine snapshots + +The Rubrik cluster provides protection for virtual machines by combining native snapshot technology with the fast and scalable cloud data management platform of the Rubrik cluster. + +Using native snapshot technology and a flexible cloud data management platform, Rubrik clusters protect virtual machines. The Rubrik cluster creates Application Consistent snapshots. If an Application Consistent snapshot cannot be created, a Crash Consistent snapshot is used. + +A Rubrik cluster provides file system consistent snapshots on supported Linux guest OS types. + +Archival snapshots provide long term storage of snapshot data outside of the local Rubrik cluster. The Rubrik cluster deduplicates and compresses the data in archival snapshots. The Rubrik cluster uses client-side encryption to encrypt the archival snapshot data stored on all archival locations except NFS exports. + *[ > ]: and then diff --git a/cdm_impact_of_sla_domain_changes_on_snapshots.md b/cdm_impact_of_sla_domain_changes_on_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..c9f0521a94a9d848129e4bff30ffc1910b549e44 --- /dev/null +++ b/cdm_impact_of_sla_domain_changes_on_snapshots.md @@ -0,0 +1,34 @@ +# Impact of SLA Domain changes on snapshots + +Source: https://docs.rubrik.com/en-us/saas/cdm/impact_of_sla_domain_changes_on_snapshots.html + +--- + +# Impact of SLA Domain changes on snapshots + +Examples showing the impact of changing the retention policy of the SLA Domain assigned to an object. Examines the impact of retroactive and non-retroactive retention changes on local, archived, and replicated snapshots. + +Original SLA Domain | Changes SLA Domain | Impact on snapshots +---|---|--- +Frequency = 1 day Retention = 7 days | Frequency = 1 dayRetention = 10 daysChanges not applied to existing snapshots. | Existing snapshots derive the retention policy of the original SLA Domain and does not change. New snapshots derive the retention policy of the modified SLA Domain. +Frequency = 1 day Retention = 7 days | Frequency = 1 day Retention = 10 days Changes applied to existing snapshots. | Existing snapshots derive the retention policy of the modified SLA Domain and are retained for 10 days. New snapshots derive the retention policy from the modified SLA Domain.Older snapshots are retained for 10 days. +Frequency = 1 day Retention = 7 days | Frequency = 1 day Retention = 5 days Changes not applied to existing snapshots. | Existing snapshots derive the retention policy from the original SLA Domain and does not change. New snapshots derive the retention policy from the modified SLA Domain. +Frequency = 1 dayRetention = 7 days | Frequency = 1 day Retention = 5 days Changes applied to existing snapshots. | Existing snapshots derive the retention policy from the modified SLA Domain and are retained for 5 days. Likely that some snapshots expire immediately.New snapshots derive the retention policy from the modified SLA Domain and are retained for a shorter duration. +Frequency = 1 dayRetention = 7 days | Frequency = 5 dayRetention = 7 days | Likely that some snapshots expire immediately. +SLA Domain SD1 Frequency = 2 months Retention = 3 months | SLA Domain SD2 Frequency = 2 months Retention = 3 months Archival location = AL1Archival threshold = 1 month Changes applied to existing snapshots | The local retention for new snapshots is decreased to 1 month. The local retention for existing snapshots is decreased to 1 month. As a result, existing snapshots older than 1 month will expire immediately and are deleted locally. All snapshots older than 1 month are archived to location AL1 and the archival retention is based on SD2. +SLA Domain SD1 Frequency = 2 monthsRetention = 3 months Archival location = AL1 Archival threshold = 1 month | SLA Domain SD2 Frequency = 2 months Retention = 3 months Archival location = AL2Archival threshold = 15 days Changes not applied to existing snapshots. | Archiving starts after 15 days. The local retention for new snapshots is decreased to 15 days.The local retention for existing snapshots does not change and is 1 month. All local snapshots older than 15 days are archived to location AL2. Snapshots already archived to location AL1 will not be archived again. The archival retention for the existing snapshots not archived are derived from SD1 and will decrease. +SLA Domain SD1 Frequency = 2 monthsRetention = 3 months Archival location = AL1Archival threshold = 1 month | SLA Domain SD2 Frequency = 2 monthsRetention = 3 months Archival location = AL2Archival threshold = 15 days Changes applied to existing snapshots. | The local retention for new snapshots is decreased to 15 days. The local retention for existing snapshots is decreased to 15 days. As a result, some existing snapshots expire immediately and are deleted locally. All local snapshots older than 15 days are archived to location AL2. Snapshots already archived to location AL1 will not be archived again. +SLA Domain SD1 Frequency = 2 monthsRetention = 3 months Archival location = AL1Archival threshold = 1 month | SLA Domain SD2Frequency = 2 monthsRetention = 3 months Archival location = AL2Archival threshold = 45 days Changes applied to existing snapshots. | The local retention for new snapshots is 45 days. The local retention for existing snapshots is increased to 45 days.All local snapshots older than 45 days are archived to location AL2. Snapshots already archived to location AL1 will not be archived again. The total retention for all snapshots is derived from SD2. +SLA Domain SD1 Frequency = 2 monthsRetention = 3 months Archival location = AL1Archival threshold = 1 month | SLA Domain SD2 No archival location Changes not applied to existing snapshots. | Local retention of existing snapshots will remain as 1 month, as specified in SD1. Local retention for new snapshots is based on SD2. The existing snapshots that have been archived to AL1 are retained there for the archival retention policy specified by SD1. The existing snapshots that have not been archived will not be archived and are retained locally for the duration specified in SD1. +SLA Domain SD1 Frequency = 2 months Retention = 3 months Archival location = AL1 Archival threshold = 1 month | SLA Domain SD2 No archival location Changes applied to existing snapshots. | Local retention policy for existing snapshots is specified in SD2.The snapshots that have been archived to AL1 are retained there for the retention policy specified by SD2. The existing snapshots that have not been archived will not be archived and their retention policy is derived from SD2. +SLA Domain SD1Frequency = 1 monthRetention = 2 months No replication. | SLA Domain SD2 Frequency = 1 monthRetention = 2 months Replication target = RT1Replication retention = 10 days Changes not applied to existing snapshots. | All snapshots from the last 30 days, if available, are eligible for replication to the new target. Snapshots are retained on the replication target for 10 days. +SLA Domain SD1 Frequency = 1 monthRetention = 2 months No replication. | SLA Domain SD2 Frequency = 1 month Retention = 2 monthsReplication target = RT1Replication retention = 10 days Changes not applied to existing snapshots. | All snapshots from the last 30 days, if available, are eligible for replication to the new target. Snapshots retained on the replication target RT1 for 10 days. +SLA Domain SD1 Frequency = 1 month Retention = 2 months | SLA Domain SD2Frequency = 1 monthRetention = 2 months Replication target = RT1Replication retention = 10 days Changes applied to existing snapshots. | Any snapshot from the last 30 days is eligible for replication to the new target location. Snapshots retained on the replication target RT1 for 10 days. Note: The replication retention window starts from the time the snapshot is created. +SLA Domain SD1 Replication target = RT1Replication retention = 10 days | SLA Domain SD2 Replication target = RT1Replication retention = 20 days Changes not applied to existing snapshots. | Snapshots already replicated are retained on replication target RT1 for 10 days.Snapshots not yet replicated are replicated to RT1 and are retained for 20 days. New snapshots will follow the retention policy specified by SD2. +SLA Domain SD1Replication target = RT1 Replication retention = 10 days | SLA Domain SD2 Replication target = RT1Replication retention = 20 daysChanges applied to existing snapshots. | Snapshots already replicated are retained on replication target RT1 for 10 days. Snapshots not yet replicated are replicated to RT1 and are retained for 20 days. New snapshots follow the retention policy specified by SD2. +SLA Domain SD1 Replication target = RT1 Replication retention = 10 days. | SLA Domain SD2 Replication target = RT2Replication retention = 20 days Changes not applied to existing snapshots | Snapshots already replicated are retained on replication target RT1 for 10 days.All snapshots are replicated to RT2 and retained for 20 days. +SLA Domain SD1 Replication target = RT1Replication retention = 10 days | SLA Domain SD1Replication target = RT2Replication retention = 20 days Changes applied to existing snapshots. | Snapshots already replicated are retained on replication target RT1 for 10 days. All snapshots are replicated to RT2 and retained for 20 days. +SLA Domain SD1 Replication target = RT1 Replication retention = 10 days | SLA Domain SD2 Replication target = RT1Replication retention = 10 days Replication target = RT2 Replication retention = 20 days Changes not applied to existing snapshots. | Snapshots already replicated are retained on replication target RT1 for 10 days. All snapshots from the last 30 days are replicated to RT2 and are retained for 20 days.Snapshots not yet replicated are replicated to RT1 and are retained for 10 days. +SLA Domain SD1 Replication target = RT1Replication retention = 10 days | SLA Domain SD2 Replication target = RT1 Replication retention = 10 days Replication target = RT2 Replication retention = 20 days Changes applied to existing snapshots. | Snapshots already replicated are retained on replication target RT1 for 10 days. Snapshots not replicated are replicated to RT1 and retained for 20 days.All snapshots from the last 30 days are replicated to RT2 and are retained for 20 days.Snapshots not yet replicated are replicated to RT1 and are retained for 10 days. +SLA Domain SD1 Replication target = RT1Replication retention = 10 days | Object deleted. | Snapshots already replicated are retained on replication target RT1 for 10 days. Snapshots not replicated are replicated based on SD1. Existing snapshots are retained locally based on SD1. + *[ > ]: and then diff --git a/cdm_impact_retention_changes_arch_rep_policies.md b/cdm_impact_retention_changes_arch_rep_policies.md new file mode 100644 index 0000000000000000000000000000000000000000..ddce9945ae22efeb12548c313e1acbad4b883dcb --- /dev/null +++ b/cdm_impact_retention_changes_arch_rep_policies.md @@ -0,0 +1,18 @@ +# Impact of retention changes on archival and replication policies + +Source: https://docs.rubrik.com/en-us/saas/cdm/impact_retention_changes_arch_rep_policies.html + +--- + +# Impact of retention changes on archival and replication policies + +When the retention period associated with any SLA rule is changed, it can potentially trigger an automatic change of existing archival and replication policies in an SLA Domain. + +These changes are described in the following sections: + + * [Archival policy](../saas/archival_policy.html "A Rubrik cluster archives data according to an archival policy that instructs the Rubrik cluster to copy protected data to archival locations.") + * [Replication policy changes](../replication/replication_policy_changes.html "Editing an SLA Domain results in a variety of changes that impact the replication policy.") + * [Creating a custom SLA Domain](../saas/rsc_creating_custom_sla_domain.html "Create a custom SLA Domain to streamline and customize workload protection and management policies.") + +Before changing the retention period of an SLA rule, consider the automatic changes to archival and replication policies that result from the change. + *[ > ]: and then diff --git a/cdm_ip_address_changes_envoy.md b/cdm_ip_address_changes_envoy.md new file mode 100644 index 0000000000000000000000000000000000000000..c7136586b0ee9b6177192d18c37af17d49ec81ca --- /dev/null +++ b/cdm_ip_address_changes_envoy.md @@ -0,0 +1,19 @@ +# IP address changes in Rubrik Envoy + +Source: https://docs.rubrik.com/en-us/saas/cdm/ip_address_changes_envoy.html + +--- + +# IP address changes in Rubrik Envoy + +The effect of changes to the IP address of a Rubrik Envoy virtual appliance. + +After a Envoy virtual appliance is registered with the Rubrik cluster, its IP address must remain the same. If the IP address changes, Envoy becomes undetectable by the Rubrik cluster. In that case, the CDM web UI and Rubrik CLI continue to show the IP address that was used to register Envoy with the Rubrik cluster. + +While an unanticipated change to the IP address of a properly configured and registered Envoy virtual appliance is not common, it can happen in situations such as the following: + + * Someone with administrator privileges manually changes the Envoy IP address by mistake. + * During reboot after a long shutdown, the Envoy virtual appliance receives a different IP address from the DHCP server. + +In the event of an IP address change, change it back to the original IP address. If changing the IP address is not possible, then correct the situation by deregistering and then re-registering the Envoy virtual appliance. + *[ > ]: and then diff --git a/cdm_jumbo_frame_support.md b/cdm_jumbo_frame_support.md new file mode 100644 index 0000000000000000000000000000000000000000..b1401aff0ed7c87362e83ef395971a5e31e582c2 --- /dev/null +++ b/cdm_jumbo_frame_support.md @@ -0,0 +1,31 @@ +# Jumbo frame support + +Source: https://docs.rubrik.com/en-us/saas/cdm/jumbo_frame_support.html + +--- + +# Jumbo frame support + +For Rubrik CDM versions 9.4 and later, you can set the value for the maximum transmission unit to a maximum value of 10000, instead of the default value of 1500. This larger unit size is called jumbo frames. + +You can use the Rubrik CLI to set the maximum transmission units (MTUs) for Rubrik CDM versions 9.4 and later to a maximum of 10000 bytes instead of the default value of 1500 bytes. This larger MTU size, called jumbo frames, provides a more efficient and much faster network throughput. The typical value for jumbo frames is 9000. + +Rubrik supports changing the MTU value for a Rubrik cluster only on bootstrapped physical machines, but not on cloud clusters. Changing the MTU is a cluster-wide parameter. If you set the MTU value on a node for an interface, this value applies to all the nodes in the cluster for that interface. If the Rubrik cluster includes a VLAN interface, this interface inherits the MTU value from the corresponding parent interface. + +Changes to the MTU value are persisted across: + + * Node and cluster reboots + * Cluster upgrades + * Node additions + +The MTU value from the Rubrik cluster is applied to the added node. + + * Node replacement + +The MTU value from Rubrik cluster is applied to the replacement node. + +Changes to the MTU value are not persisted across: + + * Node resets + * Operations that change the IP address + diff --git a/cdm_min_cryptographic_ops_privileges.md b/cdm_min_cryptographic_ops_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..1ead456dcb92fc58c7bdded34c914b91321f9915 --- /dev/null +++ b/cdm_min_cryptographic_ops_privileges.md @@ -0,0 +1,21 @@ +# Minimum cryptographic operations privileges + +Source: https://docs.rubrik.com/en-us/saas/cdm/min_cryptographic_ops_privileges.html + +--- + +# Minimum cryptographic operations privileges + +The vCenter Server role assigned to a Rubrik cluster must have the minimum cryptographic operations privileges on the vCenter Server. + +The minimum cryptographic operations privileges allow Rubrik to manage tasks for encrypted virtual machines or virtual Trusted Platform Module (vTPM)-enabled virtual machines. These tasks include cloning, encrypting, migrating, and registering virtual machines during recovery operations. The privilege must be assigned to the object listed in the Required On column, either directly or through inheritance. + +The following table lists the required cryptographic privileges by Privilege Name in the vSphere Client, along with their descriptions and the vSphere objects (Required On) for assignment. Privilege name in the vSphere client | Description | Required on +---|---|--- +Cryptographic operations > Direct Access | Gives access to encrypted resources during recovery operations. | virtual machine, host, or datastore +Cryptographic operations > Clone | Clones an encrypted virtual machine during recovery operations. | virtual machine +Cryptographic operations > Encrypt | Encrypts a virtual machine or a virtual machine disk during recovery operations. | virtual machine +Cryptographic operations > Encrypt new | Encrypts a virtual machine when creating a virtual machine or adding a disk during recovery operations. | virtual machine folder +Cryptographic operations > Migrate | Migrates an encrypted virtual machine to a different ESXi host during recovery operations. | virtual machine +Cryptographic operations > Register VM | Registers an encrypted virtual machine with an ESXi host during recovery operations. | virtual machine folder + *[ > ]: and then diff --git a/cdm_mtu_settings_verification.md b/cdm_mtu_settings_verification.md new file mode 100644 index 0000000000000000000000000000000000000000..093f1a5ab4e381b519aaa79dc2ac8d55a6d25be1 --- /dev/null +++ b/cdm_mtu_settings_verification.md @@ -0,0 +1,87 @@ +# MTU settings verification + +Source: https://docs.rubrik.com/en-us/saas/cdm/mtu_settings_verification.html + +--- + +# MTU settings verification + +You can use a few methods to verify the maximum transmission unit settings after you reconfigure them. + +## MTU settings verification using the Rubrik CLI + +You can run the Rubrik CLI network mtu get command to display the current maximum transmission unit (MTU) settings. For example: + + + vm-machine-123abc >> network mtu get + ====================================== + Interface MTU Configuration on Cluster + ====================================== + This is a Shared DATA/MANAGEMENT Cluster + DATA and MANAGEMENT, both are on bond0 + MTU Information is: + [ + { + "networkInterfaceType": "MANAGEMENT", + "mtuValue": 9000 + } + ] + +## MTU settings verification using ifconfig + +You can run the Unix ifconfig command to display the current MTU settings. This is a partial output for the ifconfig command. + + + bond0: flags=5187 mtu 9000 + inet 10.0.118.99 netmask 255.255.0.0 broadcast 10.0.255.255 + inet6 fe80::ae1f:6bff:fe55:625b prefixlen 64 scopeid 0x20 + ether ac:1f:6b:55:62:5b txqueuelen 1000 (Ethernet) + RX packets 409047587 bytes 93936775303 (93.9 GB) + RX errors 0 dropped 978893 overruns 0 frame 0 + TX packets 178968325 bytes 89712796457 (89.7 GB) + TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 + + bond1: flags=5187 mtu 1500 + inet6 fe80::ae1f:6bff:fe59:19ad prefixlen 64 scopeid 0x20 + ether ac:1f:6b:59:19:ad txqueuelen 1000 (Ethernet) + RX packets 648810 bytes 49274643 (49.2 MB) + RX errors 0 dropped 5261 overruns 0 frame 0 + TX packets 10278 bytes 1816284 (1.8 MB) + TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 + . . . + +## MTU settings verification using the interface configuration file + +After waiting from 30 to 60 seconds after changing the MTU settings, you can verify the change in the interface configuration file for the specific interface, bond0, bond1, and so on. + +This example displays the interface configuration file for bond0 located at /etc/network/interfaces.d/bond0.cfg. + + + cat /etc/network/interfaces.d/bond0.cfg + auto rketh3 + iface rketh3 inet manual + pre-up ip addr flush dev rketh3 + pre-up sleep 10 + bond-master bond0 + + auto rketh2 + iface rketh2 inet manual + pre-up ip addr flush dev rketh2 + pre-up sleep 10 + bond-master bond0 + + auto bond0 + iface bond0 inet static + pre-up ip addr flush dev bond0 + pre-up sleep 10 + pre-up ifconfig bond0 hw ether $(ethtool -P rketh3 | cut -d ' ' -f 3) + address 10.0.118.99 + netmask 255.255.0.0 + gateway 10.0.0.255 + mtu 9000 + bond-mode 4 + bond-lacp-rate 1 + bond-xmit-hash-policy 4 + bond-miimon 100 + bond-slaves none + *[ > ]: and then diff --git a/cdm_multitenancy_and_rubrik_envoy.md b/cdm_multitenancy_and_rubrik_envoy.md new file mode 100644 index 0000000000000000000000000000000000000000..8d964f61d5de92ae5582f96b3241d332d9eadbfa --- /dev/null +++ b/cdm_multitenancy_and_rubrik_envoy.md @@ -0,0 +1,19 @@ +# Multitenancy and Rubrik Envoy + +Source: https://docs.rubrik.com/en-us/saas/cdm/multitenancy_and_rubrik_envoy.html + +--- + +# Multitenancy and Rubrik Envoy + +With Rubrik Envoy, you can enable secure data movement between Rubrik clusters and a tenant organization network. + +In many service-provider environments, there is no easy and secure way to send data from service-provider management components into tenant environments. A tenant typically handles its own routing. The IP networks used between tenant and provider, or among tenants, might overlap. + +Rubrik Envoy provides secure connectivity and simplified access to a provider-managed Rubrik cluster when using NAT or overlapping network addressing between the provider and tenant networks. + +Rubrik Envoy serves as a data-path proxy connecting segmented and isolated networks that do not share a common routing domain to Rubrik data protection services. + +Rubrik Envoy eliminates direct data routing from a Rubrik cluster to a protected workload. This allows service providers to reach and protect workloads that are otherwise inaccessible through routed connections from the Rubrik cluster. + +Tenant workloads benefit from these data protection and security services regardless of whether the networks were inaccessible due to network separation or network isolation methods that overlapped with the provider or tenant networks. diff --git a/cdm_snapshot_management.md b/cdm_snapshot_management.md new file mode 100644 index 0000000000000000000000000000000000000000..91279a247acba235c95da2d8e4b25fbe049cf196 --- /dev/null +++ b/cdm_snapshot_management.md @@ -0,0 +1,20 @@ +# Snapshots + +Source: https://docs.rubrik.com/en-us/saas/cdm/snapshot_management.html + +--- + +# Snapshots + +Snapshots and backup information for relic objects and protected objects appear on the Snapshots page. + +You can view the snapshots and backup information for relic objects and protected objects on the Snapshots page. Protected objects appear on the Snapshots page if they have one of the following types of snapshot: + + * On-demand snapshot + * Downloaded snapshot + * Legal-hold snapshot + +The Snapshots page provides a centralized view of all snapshots on legal hold. + +The protected object level provides information for all supported virtual machines, Windows, Linux hosts and NAS filesets, and databases. + *[ > ]: and then diff --git a/cdm_snapshot_management_2.md b/cdm_snapshot_management_2.md new file mode 100644 index 0000000000000000000000000000000000000000..cc903f7e440456b7b9b3f0094ad0deffaed9e097 --- /dev/null +++ b/cdm_snapshot_management_2.md @@ -0,0 +1,20 @@ +# Snapshots + +Source: https://docs.rubrik.com/en-us/saas/cdm/snapshot_management_2.html + +--- + +# Snapshots + +Snapshots and backup information for relic objects and protected objects appear on the Snapshots page. + +You can view the snapshots and backup information for relic objects and protected objects on the Snapshots page. Protected objects appear on the Snapshots page if they have one of the following types of snapshot: + + * On-demand snapshot + * Downloaded snapshot + * Legal-hold snapshot + +The Snapshots page provides a centralized view of all snapshots on legal hold. + +The protected object level provides information for all supported virtual machines, Windows, Linux hosts and NAS filesets, and databases. + *[ > ]: and then diff --git a/cdm_snapshot_window.md b/cdm_snapshot_window.md new file mode 100644 index 0000000000000000000000000000000000000000..e1d936c64cadb536796f4920e097c334019bc10c --- /dev/null +++ b/cdm_snapshot_window.md @@ -0,0 +1,16 @@ +# Snapshot window + +Source: https://docs.rubrik.com/en-us/saas/cdm/snapshot_window.html + +--- + +# Snapshot window + +An SLA Domain can be configured to include a snapshot window. + +You can configure an SLA Domain to include a snapshot window, which determines the period in a day that can initiate policy-driven snapshots of the workloads. + +You can configure an SLA Domain to include a snapshot window, which determines the period in a day that the RSC can initiate policy-driven snapshots. Modifying the snapshot window causes RSC to use the new snapshot window when taking new snapshots. + +When using the snapshot window policy, the specified window must be long enough to accommodate the number of objects that are assigned to the SLA Domain. You must monitor the snapshot activity of the SLA Domain to ensure that all policy-driven snapshots are successfully completed. When necessary, you can increase the period to permit all snapshots to be completed successfully. + *[ > ]: and then diff --git a/cdm_tenant_storage_quota.md b/cdm_tenant_storage_quota.md new file mode 100644 index 0000000000000000000000000000000000000000..b74cb0210a34b1f4c65a6a3a218bc985ab2b975d --- /dev/null +++ b/cdm_tenant_storage_quota.md @@ -0,0 +1,16 @@ +# Tenant organization storage quota + +Source: https://docs.rubrik.com/en-us/saas/cdm/tenant_storage_quota.html + +--- + +# Tenant organization storage quota + +Storage-based quotas can be assigned to tenant organizations in multitenant environments to restrict resource utilization and protect resource availability. + +Organization storage quotas help service providers and multi-organization enterprises manage Rubrik resources by assigning a storage quota, or limit, on a cluster for an organization. If the organization usage exceeds the quota, scheduled and on-demand snapshots for objects on the cluster assigned to the organization are blocked. + +Assigning storage quotas to tenant organizations in multitenant environments provides a mechanism for capacity planning and resource allocation. Administrators can assign storage quotas with both hard and soft limits to tenant organizations. Only global administrators can assign, view, and edit organization storage quotas. + +When the used storage quota exceeds the assigned soft limit, the Organization Management page and the tenant organization details page display this information for the administrators of the global organization and the tenant organization. Within 30 minutes of the overage, RSC sends the organization administrator an email and the Events page also displays this information. When the used storage quota exceeds the hard limit, a red x symbol appears on the Organization Management page and the tenant organization details page. RSC stops further backups and storage operations, though you can still perform recovery and live mount operations. Backups and storage operations are resumed once the used storage is reduced or the assigned quota has been increased. Any global administrator can increase or decrease the storage quota limit as required, and the Organization details page displays these changes as well. + *[ > ]: and then diff --git a/cdm_viewing_current_mtu_settings.md b/cdm_viewing_current_mtu_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..195e6b3317deb5d28454075ad2916a66cb7c3bef --- /dev/null +++ b/cdm_viewing_current_mtu_settings.md @@ -0,0 +1,56 @@ +# Viewing the current MTU settings + +Source: https://docs.rubrik.com/en-us/saas/cdm/viewing_current_mtu_settings.html + +--- + +# Viewing the current MTU settings + +Use the Rubrik CLI to view the current maximum transmission unit settings. + +## Procedure + + 1. Log in to the Rubrik CLI using the administrator account by opening an SSH session on a node of the Rubrik cluster. + +A field to enter the administrator password appears. + + 2. At the prompt, enter `ssh admin@node_ip`. + +Where node_ip is the IPv4 address of the node with the maximum transmission unit (MTU) setting you want to view. + +A field to enter the administrator password appears. + + 3. At the prompt, enter the password for the administrator account. + +The Rubrik CLI prompt appears. + + 4. At the Rubrik CLI prompt, enter `rkcli` to start the Rubrik CLI shell. + +The Rubrik CLI prompt appears + + 5. At the prompt, enter `network mtu get`. + +## Results + +The Rubrik cluster displays the MTU settings + +## Example + +This example displays a Rubrik cluster with the MTU settings configured for jumbo frames: + + + vm-machine-123abc >> network mtu get + ====================================== + Interface MTU Configuration on Cluster + ====================================== + This is a Shared DATA/MANAGEMENT Cluster + DATA and MANAGEMENT, both are on bond0 + MTU Information is: + [ + { + "networkInterfaceType": "MANAGEMENT", + "mtuValue": 9000 + } + ] + + *[ > ]: and then diff --git a/cdm_vmc_hotadd_proxy_reqs_4.md b/cdm_vmc_hotadd_proxy_reqs_4.md new file mode 100644 index 0000000000000000000000000000000000000000..40a845eed08970d944770151b45008a655951924 --- /dev/null +++ b/cdm_vmc_hotadd_proxy_reqs_4.md @@ -0,0 +1,30 @@ +# Virtual machine HotAdd proxy requirements + +Source: https://docs.rubrik.com/en-us/saas/cdm/vmc_hotadd_proxy_reqs_4.html + +--- + +# Virtual machine HotAdd proxy requirements + +Each cloud-based datastore that hosts virtual machines protected by a Rubrik cluster requires a number of HotAdd proxies, which is determined by the number of nodes in the Rubrik cluster and the number of ESXi hosts. + +ESXi hosts | Rubrik cluster nodes +---|--- +3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 +1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 | 1 +2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 | 2 +3 | 2 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 | 3 +4 | 2 | 3 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 +5 | 2 | 3 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 | 4 +6 | 2 | 3 | 4 | 4 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 | 5 +7 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 | 6 +8 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 7 | 7 | 7 | 7 | 7 | 7 +9 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 8 | 8 | 8 | 8 +10 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 8 | 8 | 8 | 8 +11 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 9 | 9 | 9 | 9 +12 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 9 | 10 | 10 | 10 +13 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 9 | 10 | 10 | 11 +14 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 9 | 10 | 10 | 11 +15 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 9 | 10 | 10 | 11 +16 | 2 | 3 | 4 | 4 | 5 | 6 | 6 | 7 | 8 | 8 | 9 | 10 | 10 | 11 + *[ > ]: and then diff --git a/cdm_vmware_cloud_on_aws.md b/cdm_vmware_cloud_on_aws.md new file mode 100644 index 0000000000000000000000000000000000000000..df79ad7d60fde4e4cda8f747b020d101176736bb --- /dev/null +++ b/cdm_vmware_cloud_on_aws.md @@ -0,0 +1,20 @@ +# VMware Cloud on AWS + +Source: https://docs.rubrik.com/en-us/saas/cdm/vmware_cloud_on_aws.html + +--- + +# VMware Cloud on AWS + +A Rubrik Cloud Cluster can protect virtual machines deployed on VMware Cloud on AWS. + +VMware Cloud (VMC) provides a software-defined data center, or SDDC, that hosts virtual machines in the AWS cloud. Rubrik Cloud Clusters protect VMC data by ingesting the data from the SDDC using HotAdd proxy virtual machines. + +A HotAdd proxy virtual machine loads the Virtual Machine Disk, or VMDK, that is in use by the source virtual machine. The Rubrik Cloud Cluster takes snapshots of the VMDK from the proxy virtual machine. + +When the Rubrik Cloud Cluster discovers a new SDDC, the cluster launches jobs to instantiate a number of HotAdd proxies determined by the size of the SDDC data store and the total number of protected virtual machines. The Rubrik Cloud Cluster increases or decreases the number of HotAdd proxies as the inventory of protected virtual machines increases or decreases. + +Rubrik CDM does not support Instant Recovery, Live Mount for virtual machine, or Live Mount for virtual disk for virtual machines on VMC. + +Once configured, you can manage protected virtual machines in the same manner as any other vSphere virtual machine. See Recovery of virtual machines for details. + *[ > ]: and then diff --git a/cdm_vmware_cloud_on_aws_2.md b/cdm_vmware_cloud_on_aws_2.md new file mode 100644 index 0000000000000000000000000000000000000000..fa0d6c89ee7c8fd99157b1bdc8b3a0a860e8f6b9 --- /dev/null +++ b/cdm_vmware_cloud_on_aws_2.md @@ -0,0 +1,20 @@ +# VMware Cloud on AWS + +Source: https://docs.rubrik.com/en-us/saas/cdm/vmware_cloud_on_aws_2.html + +--- + +# VMware Cloud on AWS + +A Rubrik Cloud Cluster can protect virtual machines deployed on VMware Cloud on AWS. + +VMware Cloud (VMC) provides a software-defined data center, or SDDC, that hosts virtual machines in the AWS cloud. Rubrik Cloud Clusters protect VMC data by ingesting the data from the SDDC using HotAdd proxy virtual machines. + +A HotAdd proxy virtual machine loads the Virtual Machine Disk, or VMDK, that is in use by the source virtual machine. The Rubrik Cloud Cluster takes snapshots of the VMDK from the proxy virtual machine. + +When the Rubrik Cloud Cluster discovers a new SDDC, the cluster launches jobs to instantiate a number of HotAdd proxies determined by the size of the SDDC data store and the total number of protected virtual machines. The Rubrik Cloud Cluster increases or decreases the number of HotAdd proxies as the inventory of protected virtual machines increases or decreases. + +Rubrik CDM does not support Instant Recovery, Live Mount for virtual machine, or Live Mount for virtual disk for virtual machines on VMC. + +Once configured, you can manage protected virtual machines in the same manner as any other vSphere virtual machine. See Recovery of virtual machines for details. + *[ > ]: and then diff --git a/cdm_vmware_cloud_on_azure.md b/cdm_vmware_cloud_on_azure.md new file mode 100644 index 0000000000000000000000000000000000000000..0ce310171774f2faad05123f4e21d45a5d33674d --- /dev/null +++ b/cdm_vmware_cloud_on_azure.md @@ -0,0 +1,24 @@ +# Microsoft Azure VMware Solution + +Source: https://docs.rubrik.com/en-us/saas/cdm/vmware_cloud_on_azure.html + +--- + +# Microsoft Azure VMware Solution + +A Rubrik cluster can protect virtual machines deployed on the Microsoft Azure VMware Solution. + +Azure VMware Solution (AVS) provides a software-defined data center, or SDDC, that hosts virtual machines in the Azure cloud. Rubrik clusters protect AVS data by ingesting the data from the SDDC using HotAdd proxy virtual machines. + +A HotAdd proxy virtual machine mounts a copy of the Virtual Machine Disk (VMDK) that is used by the source virtual machine. The Rubrik cluster takes snapshots of the VMDK mounted on the proxy virtual machine. + +When the Rubrik cluster discovers a new SDDC, it launches jobs to deploy HotAdd proxies. The number of ESXi hosts and the number of nodes in the Rubrik cluster determine the number of proxies deployed. The Rubrik cloud cluster increases or decreases the number of HotAdd proxies as the number of ESXi hosts or nodes in the Rubrik cluster changes. + +Rubrik CDM does not support the following operations for virtual machines on AVS: + + * Instant Recovery + * Live Mount for virtual machines + * Live Mount for virtual disk + +After associating an SDDC with a Rubrik cluster, you can manage protected virtual machines in the same manner as any other vSphere virtual machine. + *[ > ]: and then diff --git a/cdm_vmware_cloud_on_azure_2.md b/cdm_vmware_cloud_on_azure_2.md new file mode 100644 index 0000000000000000000000000000000000000000..5706c997d4256552ffafd68773e80d161c3c7304 --- /dev/null +++ b/cdm_vmware_cloud_on_azure_2.md @@ -0,0 +1,24 @@ +# Microsoft Azure VMware Solution + +Source: https://docs.rubrik.com/en-us/saas/cdm/vmware_cloud_on_azure_2.html + +--- + +# Microsoft Azure VMware Solution + +A Rubrik cluster can protect virtual machines deployed on the Microsoft Azure VMware Solution. + +Azure VMware Solution (AVS) provides a software-defined data center, or SDDC, that hosts virtual machines in the Azure cloud. Rubrik clusters protect AVS data by ingesting the data from the SDDC using HotAdd proxy virtual machines. + +A HotAdd proxy virtual machine mounts a copy of the Virtual Machine Disk (VMDK) that is used by the source virtual machine. The Rubrik cluster takes snapshots of the VMDK mounted on the proxy virtual machine. + +When the Rubrik cluster discovers a new SDDC, it launches jobs to deploy HotAdd proxies. The number of ESXi hosts and the number of nodes in the Rubrik cluster determine the number of proxies deployed. The Rubrik cloud cluster increases or decreases the number of HotAdd proxies as the number of ESXi hosts or nodes in the Rubrik cluster changes. + +Rubrik CDM does not support the following operations for virtual machines on AVS: + + * Instant Recovery + * Live Mount for virtual machines + * Live Mount for virtual disk + +After associating an SDDC with a Rubrik cluster, you can manage protected virtual machines in the same manner as any other vSphere virtual machine. + *[ > ]: and then diff --git a/cdm_vmware_cloud_on_gcve.md b/cdm_vmware_cloud_on_gcve.md new file mode 100644 index 0000000000000000000000000000000000000000..a58670543daae9022a66cf266e48d7abaa6df2e3 --- /dev/null +++ b/cdm_vmware_cloud_on_gcve.md @@ -0,0 +1,24 @@ +# Google Cloud VMware Engine + +Source: https://docs.rubrik.com/en-us/saas/cdm/vmware_cloud_on_gcve.html + +--- + +# Google Cloud VMware Engine + +A Rubrik cluster can protect virtual machines deployed on the Google Cloud VMware Engine. + +Google Cloud VMware Engine (GCVE) provides a software-defined data center, or SDDC, that hosts virtual machines in the Google cloud. Rubrik clusters protect GCVE data by ingesting the data from the SDDC using HotAdd proxy virtual machines. + +A HotAdd proxy virtual machine mounts a copy of the Virtual Machine Disk (VMDK) that is used by the source virtual machine. The Rubrik cluster backs up the VMDK mounted on the proxy virtual machine. + +When the Rubrik cluster discovers a new SDDC, it launches jobs to deploy HotAdd proxies. The number of ESXi hosts and the number of nodes in the Rubrik cluster together determine the number of proxies deployed. The Rubrik cloud cluster increases or decreases the number of HotAdd proxies as the number of ESXi hosts or nodes in the Rubrik cluster change. + +Rubrik CDM does not support the following operations for virtual machines on GCVE: + + * Instant Recovery + * Live Mount for virtual machines + * Live Mount for virtual disk + +After associating an SDDC with a Rubrik cluster, you can manage protected virtual machines in the same manner as any other vSphere virtual machine. + *[ > ]: and then diff --git a/cdm_vmware_cloud_on_gcve_2.md b/cdm_vmware_cloud_on_gcve_2.md new file mode 100644 index 0000000000000000000000000000000000000000..148e7a768342fb7301ae6019ae892bf501117cc9 --- /dev/null +++ b/cdm_vmware_cloud_on_gcve_2.md @@ -0,0 +1,24 @@ +# Google Cloud VMware Engine + +Source: https://docs.rubrik.com/en-us/saas/cdm/vmware_cloud_on_gcve_2.html + +--- + +# Google Cloud VMware Engine + +A Rubrik cluster can protect virtual machines deployed on the Google Cloud VMware Engine. + +Google Cloud VMware Engine (GCVE) provides a software-defined data center, or SDDC, that hosts virtual machines in the Google cloud. Rubrik clusters protect GCVE data by ingesting the data from the SDDC using HotAdd proxy virtual machines. + +A HotAdd proxy virtual machine mounts a copy of the Virtual Machine Disk (VMDK) that is used by the source virtual machine. The Rubrik cluster backs up the VMDK mounted on the proxy virtual machine. + +When the Rubrik cluster discovers a new SDDC, it launches jobs to deploy HotAdd proxies. The number of ESXi hosts and the number of nodes in the Rubrik cluster together determine the number of proxies deployed. The Rubrik cloud cluster increases or decreases the number of HotAdd proxies as the number of ESXi hosts or nodes in the Rubrik cluster change. + +Rubrik CDM does not support the following operations for virtual machines on GCVE: + + * Instant Recovery + * Live Mount for virtual machines + * Live Mount for virtual disk + +After associating an SDDC with a Rubrik cluster, you can manage protected virtual machines in the same manner as any other vSphere virtual machine. + *[ > ]: and then diff --git a/cdm_vs_vm_continuous_data_protection.md b/cdm_vs_vm_continuous_data_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..720c840256a5e0ddff78217a4eed048d59c5bea3 --- /dev/null +++ b/cdm_vs_vm_continuous_data_protection.md @@ -0,0 +1,29 @@ +# Continuous Data Protection + +Source: https://docs.rubrik.com/en-us/saas/cdm/vs_vm_continuous_data_protection.html + +--- + +# Continuous Data Protection + +Continuous Data Protection uses VMware vSphere APIs for I/O Filtering to continuously capture changes to data on a vSphere virtual machine and sends them to a Rubrik cluster. + +Continuous Data Protection (CDP) utilizes the vSphere APIs for I/O Filtering (VAIO) framework from VMware to provide continuous protection for vSphere virtual machines. CDP runs as a service and captures changes to data on a virtual machine and sends them to a Rubrik cluster. CDP uses a CDP filter on an ESXi host (version 6.7 or later) to capture any changes made on a Virtual Machine Disk (VMDK) on a VMware host. RSC stores all the changes made since the previous snapshot as metadata and log files on a cluster, a replicated cluster, or both. + +CDP is intended as a near-term solution for data recovery. Depending on the CDM version running on the cluster, CDP can record data changes for up to 24 hours using a log file. You can use the Keep Recovery Points For (Hours) settings to configure the time period while creating an SLA Domain. The SLA Domains with CDP enabled topic provides more information on the Keep Recovery Points For (Hours) settings and the supported CDM versions. + +The two use cases for CDP are: + + * Recovery of a vSphere virtual machine from the most recent point in time (PIT) + * Recovery of a vSphere virtual machine from a specific PIT + +Using CDP requires you to complete the following actions: + + * Installing the CDP filter on the vCenter Server using the RSC user interface. + * Creating an SLA Domain with CDP enabled and assigning the SLA Domain to a vSphere virtual machine. + * Recovering a vSphere virtual machine from a PIT. + +You can select a PIT from the last PIT stored on the cluster or any PIT specified within the SLA policy. + +When you upgrade the CDM version of a cluster, you might need to upgrade the CDP filter to ensure continuous protection of your data. + *[ > ]: and then diff --git a/common_add_lacp.md b/common_add_lacp.md new file mode 100644 index 0000000000000000000000000000000000000000..5ed58bf50edd42e73119b3682a3dd2d94e394b4f --- /dev/null +++ b/common_add_lacp.md @@ -0,0 +1,28 @@ +# Add LACP + +Source: https://docs.rubrik.com/en-us/saas/common/add_lacp.html + +--- + +# Add LACP + +Link aggregation control protocol combines multiple network connections in parallel to increase throughput. Rubrik CDM provides the ability to enable link aggregation control protocol to achieve greater network throughput and fault tolerance. + +Link aggregation control protocol (LACP) uses network bonding to combine two or more network interfaces into a single, logical interface, increasing the bandwidth and providing redundancy. Network bonding ensures that if a specific network interface card (NIC) experiences a problem, communications are not affected significantly as long as the other NICs remain active on that interface. + +LACP provides bandwidth aggregation and fault tolerance. For example, you can utilize bandwidth aggregation by combining two 20 Gb physical links to form an LACP bundle to become a single 40 G interface, or combine eight 1 Gb physical links to form an 8 Gb interface. LACP will redistribute traffic over the remaining active links if a link is down or unresponsive. + +In systems configured without LACP, Rubrik CDM supports an active-backup bond mode. For example, in a system that includes two 10 Gb NICs in the bond interface, only one of them is actively carrying traffic. The other bond interface acts only as a backup, and Rubrik CDM limits throughput to only 10 Gb. LACP actively uses both NICs, allowing Rubrik CDM to deliver 20 Gb of throughput. + +Rubrik recommends that customers configure network switches in an individual state. In this state, the switch detects the Rubrik bond configuration and allows a connection if it is using either LACP or active backup. + +Rubrik CDM allows for a mix-mode configuration for LACP. That is, a cluster can be a combination of nodes that are enabled with LACP and nodes that are not enabled with LACP. + +Between any pair of network nodes, there can be many Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) sessions, and these sessions may attach to different links. Each TCP or UDP session uses a fixed link for the entire session. However, any single TCP or UDP session is limited to 10 Gb bandwidth. If there are sufficient number of sessions, the same pair of nodes can utilize both links and receive up to 20 Gb of bandwidth. + +Rubrik clusters utilize the 10 G – 25 G Bond0 and Bond1 interfaces for data backup, restore, and node communication. From Rubrik CDM versions 9.3.1 and later, you can set LACP bond mode to both bond0 and bond1. You can change the bond mode between Active-Backup and LACP using the CLI. + +You can configure LACP for a pre-bootstrapped or bootstrapped nodes using CLI. LACP is a supported configuration prior to bootstrapping for all physical Rubrik cluster platforms. Virtual platforms do not support LACP. + +Once configured, LACP remains active during all cluster operations. + *[ > ]: and then diff --git a/common_saas_creating_reports_instances.md b/common_saas_creating_reports_instances.md new file mode 100644 index 0000000000000000000000000000000000000000..c2be8dcf24564e7575e0c5df7f95eb6b236c50ce --- /dev/null +++ b/common_saas_creating_reports_instances.md @@ -0,0 +1,35 @@ +# Creating reports for SaaS applications + +Source: https://docs.rubrik.com/en-us/saas/common/saas_creating_reports_instances.html + +--- + +# Creating reports for SaaS applications + +Create reports for SaaS applications to view information in your application, such as compliance status and protection status, using the available templates, which you can customize for each report type. You can use the data gathered in the reports to perform audits and data management planning. + +## About this task + +Reports contain data for instances with access to RSC. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click Reports. + +The Reports page appears and displays only the reports created for SaaS workloads. + + 4. Select Create Report and select the report template to use. + +The report page for the selected report appears. + + 5. Specify your settings and click Create. + +## Results + +RSC displays the new report. + *[ > ]: and then diff --git a/common_saas_creating_sla_domains.md b/common_saas_creating_sla_domains.md new file mode 100644 index 0000000000000000000000000000000000000000..fdb7724b90d38ebeec1a2adb73e9d8d5cfdcba1f --- /dev/null +++ b/common_saas_creating_sla_domains.md @@ -0,0 +1,53 @@ +# Creating an SLA Domain for SaaS applications + +Source: https://docs.rubrik.com/en-us/saas/common/saas_creating_sla_domains.html + +--- + +# Creating an SLA Domain for SaaS applications + +Create an SLA Domain with custom backup frequency and retention policies to retain snapshot data beyond a year. + +## About this task + +While RSC provides Silver Lite and Bronze Lite default SLA Domains for SaaS application protection, you can create a customized SLA Domain with custom backup frequency and retention policies. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click SLA Domains. + 4. Click Create SLA Domain. + +The Create SLA Domain wizard opens. + + 5. Select the workloads to protect. + 6. Click Next. + +The Retention Lock page appears. + + 7. Turn on Retention Lock. + +By default, Retention Lock is turned off. Enabling Quorum Authorization (QAuth) in RSC is mandatory to turn on Retention Lock. If QAuth is not enabled, you must contact your RSC administrator to enable QAuth. + + 8. Click Next. + 9. In Take Snapshots, enter the frequency (in hours) in which snapshots are taken. + +Enter a value greater than or equal to 12, because 12 hours is the minimum frequency at which RSC takes snapshots. + + 10. In Retain snapshots, enter the number of months or years to retain the snapshot. + 11. Click Next. + +The Confirmation page appears. + + 12. In SLA Domain Name, enter a name for the SLA Domain. + 13. In Description, enter a description for the SLA Domain. + 14. Review the configuration details and click Create. + +## Results + +RSC creates the SLA Domain, which you can assign to the SaaS application. + *[ > ]: and then diff --git a/common_saas_deleting_sla_domain.md b/common_saas_deleting_sla_domain.md new file mode 100644 index 0000000000000000000000000000000000000000..9edbd39d49c02495298710efa2d4d628ecbb8fd6 --- /dev/null +++ b/common_saas_deleting_sla_domain.md @@ -0,0 +1,36 @@ +# Deleting an SLA Domain for SaaS applications + +Source: https://docs.rubrik.com/en-us/saas/common/saas_deleting_sla_domain.html + +--- + +# Deleting an SLA Domain for SaaS applications + +Delete an SLA Domain you created for SaaS applications from RSC when it is no longer needed. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click SLA Domains. + +The SLA Domains page appears and displays only the SLA Domains created for SaaS workloads. + + 4. Select the SLA Domain that you want to delete. + +The SLA Domain details page appears. + + 5. Click and select Delete SLA Domain. + +The Delete SLA Domain dialog box appears. + + 6. **Optional:** In Add a Note, add a note to describe the reason for deleting the SLA Domain. + 7. Click Delete. + +## Results + +RSC deletes the SLA Domain. + *[ > ]: and then diff --git a/common_saas_events.md b/common_saas_events.md new file mode 100644 index 0000000000000000000000000000000000000000..5b686097d87b2193e71f42bb426ac6ced0594cc1 --- /dev/null +++ b/common_saas_events.md @@ -0,0 +1,12 @@ +# SaaS application events + +Source: https://docs.rubrik.com/en-us/saas/common/saas_events.html + +--- + +# SaaS application events + +RSC tracks, monitors, and displays all SaaS application events in a unified view for all connected instances. For example, you can view backup and recovery events and statuses, such as succeeded or failed. + +You can view various SaaS application events, such as recovery events, which are events that are generated during different stages of recovery. You can view, filter, and search for point-in-time events on the Events page, which displays all connected instances in the local timezone. The Events feature also provides an audit log that shows messages for system events on the connected instances. + *[ > ]: and then diff --git a/common_saas_managing_protection.md b/common_saas_managing_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..ea1820a474ddac60c20a9d53f275fc4275023420 --- /dev/null +++ b/common_saas_managing_protection.md @@ -0,0 +1,54 @@ +# Managing protection for SaaS applications + +Source: https://docs.rubrik.com/en-us/saas/common/saas_managing_protection.html + +--- + +# Managing protection for SaaS applications + +Protect SaaS applications, such as Atlassian Jira and Salesforce, by assigning them to an SLA Domain. This protects the instance by applying backup frequency and retention policies. + +## About this task + +If you have a quorum authorization policy configured for changing SLA Domain assignments for SaaS applications, you require approval from a set of approvers before you can assign a different SLA Domain to the SaaS application instance. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click a SaaS application instance. + +The details page for the application appears. + + 4. In Backup Summary, click Manage Protection. + +The Assign SLA Domain wizard appears. + + 5. Select a protection option. + +Option| Description +---|--- +SLA Domain | Assigns the SLA Domain to the chosen instance. +Don't protect | Excludes all objects of an instance from all further SLA Domain protection. + + 6. Click Next and then click Assign. + +If you have created a quorum authorization policy for this operation, you need to submit a request for quorum authorization. + + 7. For quorum authorization, select a run type action. + +Option| Description +---|--- +Automatically schedule | Schedules the action to automatically run after approval. +Manually schedule | Schedules the action to run within 24 hours after the approval. Actions not run 24 hours after approval will expire. + + 8. **Optional:** For quorum authorization, in Comment, enter a comment to provide additional details about the request. + 9. For quorum authorization, click Submit Request. + +## Results + +RSC begins processing the specified assignments and protecting the selected instance according to your settings. If you have created a quorum authorization policy, RSC completes the action according to the specified run type option after the request is approved. + *[ > ]: and then diff --git a/common_saas_report_templates.md b/common_saas_report_templates.md new file mode 100644 index 0000000000000000000000000000000000000000..70f01f2605a744fe2857b912fa065f5edb5ec54d --- /dev/null +++ b/common_saas_report_templates.md @@ -0,0 +1,17 @@ +# SaaS application report templates table + +Source: https://docs.rubrik.com/en-us/saas/common/saas_report_templates.html + +--- + +# SaaS application report templates table + +RSCprovides a template for each report category. You can use default reports as basic templates and modify them to create new reports. The following table describes the available report template types. + +Template type | Description +---|--- +Compliance | Displays compliance status of the selected instance. +Protection | Displays protection information for the selected instance. +Protection Tasks Details | Displays the protection tasks for each instance and a summary table with more detailed information. +Recovery Tasks Details | Displays the status of the recovery tasks for each instance and a summary table with more detailed information. + *[ > ]: and then diff --git a/common_sass_reporting.md b/common_sass_reporting.md new file mode 100644 index 0000000000000000000000000000000000000000..5d0ed593726313300e9a5696421858638e61ad2f --- /dev/null +++ b/common_sass_reporting.md @@ -0,0 +1,16 @@ +# SaaS application reporting + +Source: https://docs.rubrik.com/en-us/saas/common/sass_reporting.html + +--- + +# SaaS application reporting + +You can create reports about SaaS application data protection to view status information about an instance. You can use the provided report type templates and customize the default templates as needed. + +To view status information, you can create reports based on templates, which you can also customize. RSC provides templates for each report type, for example, recovery task details reports. + +You can create views of the most commonly used system metrics by using the Reporting feature. You can use the data gathered in the reports to perform audits and data management planning. + +Reports contain data for instances with access to RSC. + *[ > ]: and then diff --git a/common_sql_always_on_availability_groups.md b/common_sql_always_on_availability_groups.md new file mode 100644 index 0000000000000000000000000000000000000000..e5d8fdbefbd42beb9705793d6f54dc24df3f4eb4 --- /dev/null +++ b/common_sql_always_on_availability_groups.md @@ -0,0 +1,38 @@ +# Always On Availability Groups + +Source: https://docs.rubrik.com/en-us/saas/common/sql_always_on_availability_groups.html + +--- + +# Always On Availability Groups + +The Rubrik cluster supports data protection for availability databases in an Always On availability group. + +The Rubrik Backup Service software must be installed on each of the Windows Server hosts to protect the availability databases. + +The account running the Rubrik Backup Service on each Windows Server host must have appropriate permissions. These are the same permissions required to access a standalone Windows Server host. + +Each Microsoft SQL Server host added must have its own name. Do not add the availability group listener as a Windows host. + +Prioritizing the synchronous secondary replica for protection by the Rubrik cluster minimizes impact on the primary replica. + +The Rubrik cluster supports export of an availability database backup as a database that exists outside of the Always On availability group. The Rubrik cluster does not support in-place restore of an availability database backup. Availability databases are actively involved in database mirroring sessions and cannot be directly replaced by a backup. + +Rubrik clusters support availability databases in an Always On availability group and provide auto-protection for availability databases based on the Microsoft SQL Server database backup settings described in the following table. + +Database setting | Description +---|--- +sys.availability_groups.automated_backup_preference_desc | + + * PRIMARY: only use the primary replica for backups + * SECONDARY_ONLY: only use a secondary replica for backups + * SECONDARY: prefer using a secondary replica, but use a primary if no secondaries are available + * NONE: no preference with respect to whether a replica is primary or secondary + + +sys.availability_replicas.backup_priority | A value from 0 to 100, with higher numbers assigning higher priority. Set this value to 0 to never use this replica. + +For details on managing these settings, refer to the Microsoft SQL Server documentation. + +In order to prevent unauthorized access to database replicas, Rubrik clusters rely on the availability groups information in the sys.availability_databases_cluster table during the discovery process. Restrict the visibility of the group_id and group_database_id identifiers to the smallest practicable number of people to further reduce the risk of unauthorized access. + *[ > ]: and then diff --git a/common_sql_change_block_tracking.md b/common_sql_change_block_tracking.md new file mode 100644 index 0000000000000000000000000000000000000000..3d8955762abc15b23b96f715fe21f2d3bd8db970 --- /dev/null +++ b/common_sql_change_block_tracking.md @@ -0,0 +1,14 @@ +# SQL Change Block Tracking + +Source: https://docs.rubrik.com/en-us/saas/common/sql_change_block_tracking.html + +--- + +# SQL Change Block Tracking + +Change Block Tracking uses a filter driver to track SQL database file changes as they happen. + +Without Change Block Tracking (CBT), the entire database is scanned at each backup interval to determine if any changes have occurred. By using CBT only the tracked changes are scanned to determine modifications, resulting in improved backup performance. + +CBT improves backup performance for environments with large databases, low change rate, frequent backups, or any environment where the full scan time is adversely affecting performance. Enabling CBT requires a small amount of memory and CPU on the host to track changes. + *[ > ]: and then diff --git a/common_sql_live_mount.md b/common_sql_live_mount.md new file mode 100644 index 0000000000000000000000000000000000000000..43286d29b6dc23d5689ef6bc3fdaf65418845e07 --- /dev/null +++ b/common_sql_live_mount.md @@ -0,0 +1,36 @@ +# Live Mount + +Source: https://docs.rubrik.com/en-us/saas/common/sql_live_mount.html + +--- + +# Microsoft SQL Server database details + +The Microsoft SQL Server database details page provides detailed information about the database, its protection status, Live Mounts, available snapshots, database events and snapshots. + +You can view detailed information about the Microsoft SQL Server database in the database details page. + +The Overview tab provides detailed information about the database, its protection status, Live Mounts, available snapshots, and tasks related to the database and snapshots. + +The Events tab provides detailed information about the status of database events including the event type, Rubrik cluster, object, location, and time.# Microsoft SQL Server database details + +The Microsoft SQL Server database details page provides detailed information about the database, its protection status, Live Mounts, available snapshots, database events and snapshots. + +You can view detailed information about the Microsoft SQL Server database in the database details page. + +The Overview tab provides detailed information about the database, its protection status, Live Mounts, available snapshots, and tasks related to the database and snapshots. + +The Events tab provides detailed information about the status of database events including the event type, Rubrik cluster, object, location, and time. + +The Snapshots tab provides information about the snapshots, their type, and the SLA Domain. + +# Live Mount + +A Live Mount creates a new database from a point-in-time copy of the source database. The Rubrik cluster provides a Samba share of the new database directly from the Rubrik cluster storage layer. + +Live Mount databases can be attached to Microsoft SQL Servers on any Windows Server host that is running the Rubrik Backup Service. Specific requirements are listed in the Rubrik Compatibility Matrix. + +Transmissions between the Rubrik cluster and the host of the Live Mount are secured by end-to-end encryption. + +Using Live Mount to access a copy of a database can significantly reduce the RTO for the database. A Live Mount database cannot be protected through the Rubrik cluster. + *[ > ]: and then diff --git a/common_sql_point_in_time_recovery.md b/common_sql_point_in_time_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..8196d437a12a1ac6a9349b64a1e4b16f51afcfb9 --- /dev/null +++ b/common_sql_point_in_time_recovery.md @@ -0,0 +1,24 @@ +# Point-in-time recovery + +Source: https://docs.rubrik.com/en-us/saas/common/sql_point_in_time_recovery.html + +--- + +# Point-in-time recovery + +For a database that uses the full recovery model or the bulk-logged recovery model, the Rubrik cluster uses a combination of a snapshot of the database and the database transaction log backups to recover a database. + +The Rubrik Backup Service obtains the snapshot of the database by using the VSS writer on the Microsoft SQL Server host to create a full backup of the database. + +The combination of a snapshot of the database and the transaction log backups from the database permits the Rubrik cluster to recover a database to the state it was in at a selected point in time. + +To recover to a selected point in time, the Rubrik cluster uses two pieces of information: + + * Last snapshot created before the selected point in time + + * Log backups created between the time of the snapshot and the selected point in time + +The Rubrik cluster first recovers the database from the snapshot. Then the Rubrik cluster unrolls and applies the contents of the logs until the selected point in time is reached. + +The closer that the snapshot is to the selected point in time, the shorter the recovery time objective (RTO) that is achieved by the process. To minimize RTO, assign a database to an SLA Domain with frequent snapshots. + *[ > ]: and then diff --git a/common_sql_requirements.md b/common_sql_requirements.md new file mode 100644 index 0000000000000000000000000000000000000000..c78ba7959f6d30df24895ccb9fb3f369a79a19ec --- /dev/null +++ b/common_sql_requirements.md @@ -0,0 +1,17 @@ +# Microsoft SQL Server requirements + +Source: https://docs.rubrik.com/en-us/saas/common/sql_requirements.html + +--- + +# Microsoft SQL Server requirements + +A Rubrik cluster provides data management and protection for Microsoft SQL Server databases when specific requirements are met. + +Requirement | Description +---|--- +Operating system | Refer to the Rubrik Compatibility Matrix for current version support. +Database management system | Refer to the Rubrik Compatibility Matrix for current version support. +Windows service | Microsoft SQL Server VSS Writer (running) +Network protocol | TCP/IP or Shared Memory protocol enabled for each Microsoft SQL Server database + *[ > ]: and then diff --git a/common_sql_server_database_protection.md b/common_sql_server_database_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..ca9518d2121c6eae17606fcfac9c3adbdc6ca257 --- /dev/null +++ b/common_sql_server_database_protection.md @@ -0,0 +1,26 @@ +# Microsoft SQL Server database protection + +Source: https://docs.rubrik.com/en-us/saas/common/sql_server_database_protection.html + +--- + +# Microsoft SQL Server database protection + +After adding a Windows Server host to a Rubrik cluster, the Microsoft SQL Server databases on that host can be managed through the web UI. + +A Rubrik cluster can manage Microsoft SQL Server databases, including databases with filestreams and in-memory tables, that are configured to use any of the following models: + + * Full recovery + * Bulk-logged recovery + * Simple recovery + +A database that is configured to use the Full recovery model or the Bulk-logged recovery model can be protected through policy-driven snapshots and backups of the transaction log, or through policy-driven snapshots only. + +A database that is configured to use the Simple recovery model can be protected through policy-driven snapshots only. + +For databases that use the Full recovery model or the Bulk-logged recovery model, and have policy-based snapshots and transaction log backups enabled on the Rubrik cluster, the following log backup options can be configured: + + * Default frequency for transaction log backups by the Rubrik cluster + * Frequency and retention of transaction log backups through settings associated with an assigned SLA Domain + + *[ > ]: and then diff --git a/common_sql_server_databases.md b/common_sql_server_databases.md new file mode 100644 index 0000000000000000000000000000000000000000..caba42d9b7014835c46fc7af3614b8f4b626da8f --- /dev/null +++ b/common_sql_server_databases.md @@ -0,0 +1,36 @@ +# Microsoft SQL Server databases + +Source: https://docs.rubrik.com/en-us/saas/common/sql_server_databases.html + +--- + +# Microsoft SQL Server databases + +A Rubrik cluster provides data management and protection for Microsoft SQL Server databases. + +A Rubrik cluster can manage and protect Microsoft SQL Server databases that are configured to use the full recovery model, bulk-logged recovery model, or the simple recovery model. + +For a database that uses the full recovery model or the bulk-logged recovery model, the Rubrik cluster performs policy-driven VSS snapshots of the database and frequent interim backups of the transaction log. The combination of a snapshot of the database and transaction log backups permits granular restore of a database to a specified recovery point. + +For a database that uses the simple recovery model, the Rubrik cluster performs policy-driven snapshots of the database. The snapshots permit recovery of the database to its state at the time of a snapshot. + +The following table lists some of the protection features that a Rubrik cluster provides for Microsoft SQL Server databases. + +Feature | Description +---|--- +Physical and virtual instance support | The Rubrik cluster supports Microsoft SQL Server databases running on physical installations of Windows Server, and running on guest OS installations of Windows Server running in a virtual environment. +Windows Server Failover Clustering support | The Rubrik cluster supports Microsoft SQL Server databases running on Windows Failover Clustering (WSFC) instances of Microsoft SQL Server. +Full, bulk-logged, and simple recovery models | The Rubrik cluster provides protection for full recovery model, bulk-logged recovery model, and simple recovery model databases. +Automatic discovery | After installing the Rubrik Backup Service software on a Windows Server, the Rubrik connector automatically discovers all instances of Microsoft SQL Server and all Microsoft SQL Server databases on the Windows Server. The Rubrik connector provides this information to the Rubrik cluster, and the objects appear in the web UI. +Automatic upgrade | When new versions of the Rubrik Backup Service software are available, the Rubrik cluster automatically upgrades the software on all Windows Server hosts. +SLA Domain-based protection | SLA Domains provide simplified management of Microsoft SQL Server database protection. Setting the snapshot frequency and retention, snapshot window, replication policy, and archival policy for a database can be accomplished by assigning the database to an SLA Domain. +Derived protection assignments | Databases can derive SLA Domain protection through an SLA Domain assignment made to the Microsoft SQL Server database or the Windows Server host. Databases added at a later date automatically derive the protection of the parent entity. +Configurable log backups | For any database, the log backup frequency setting can be derived from the system defaults, or the log backup frequency and retention can be configured through an SLA Domain assignment. Log backups can also be disabled entirely. +Copy Only backups | When a database is assigned to an SLA Domain, Copy Only backups can be specified for that database. +Source-side compression | The Rubrik Backup Service compresses the data from Microsoft SQL Server database backups before sending the data to the Rubrik cluster. +Replication | Based on SLA Domain policy, snapshots and transaction log backups can be replicated to another Rubrik cluster. +Archiving | Based on SLA Domain policy, snapshots and transaction log backups can be archived to a supported archival location. +Point-in-time recovery | A database can be recovered from a snapshot or to a point in time between snapshots. The Rubrik cluster returns the recovered database to the state it was in at the time specified by the user. +VDI support | The Rubrik cluster fully supports the Microsoft Virtual Device Interface (VDI) API for transaction log backup and restore operations. However, VDI requires that the agent performing backups or restores have sysadmin privileges on the server. +Point in time export | A database can be exported to another Microsoft SQL Server database of the same version or higher, on the same Windows Server host or on another Windows Server host. Export of the database can be based on a snapshot, or on a snapshot combined with transaction log backups. +On-demand individual and group snapshots | On-demand snapshots are available for Microsoft SQL Server hosts or instances, creating individual snapshots of all the databases on the host or instance. Group snapshots are also available for multiple databases from different Microsoft SQL Server hosts or instances. When snapshots are grouped in this way, the count of incoming snapshots is the number of snapshot groups, rather than the number of individual snapshots. diff --git a/common_sql_server_log_shipping.md b/common_sql_server_log_shipping.md new file mode 100644 index 0000000000000000000000000000000000000000..7caad8f4d3432cee47e7645c44b8d0b9fa23dd2d --- /dev/null +++ b/common_sql_server_log_shipping.md @@ -0,0 +1,18 @@ +# Microsoft SQL Server log shipping + +Source: https://docs.rubrik.com/en-us/saas/common/sql_server_log_shipping.html + +--- + +# Microsoft SQL Server log shipping + +Automatically send transaction log backups from a primary database running on a primary server instance to one or more secondary databases running on separate secondary server instances by using the Microsoft SQL Server log shipping feature. + +Microsoft SQL Server log shipping is typically used for disaster recovery or in reporting instances but can also be used to migrate databases to new servers or to seed availability groups in the Rubrik cluster. Transaction log backups are applied individually to each of the secondary databases. Secondary databases are also known as target databases. + +You can add a secondary database to another database server using the Add Log Shipping Secondary feature. Using the Reseed operation drops the database on the target side and restores the latest snapshot and log backups up to the latest log backup in the Rubrik cluster. The Reseed operation is used only to resolve a broken log shipping relationship between the primary database and a secondary database. + +The secondary databases are in a state of Restoring or Standby. Databases in the Standby state allow users to read the database, but users cannot write to the database. While the database is in Standby state, it is online and readable. Log backups can be restored only when no users are accessing the database. When moving a database into the Standby state, you must determine whether the Rubrik cluster disconnects users before applying the log backups. + +Secondary databases in the Restoring state are offline to users and allow log backups to be freely restored to the database. + *[ > ]: and then diff --git a/common_sql_windows_server_hosts.md b/common_sql_windows_server_hosts.md new file mode 100644 index 0000000000000000000000000000000000000000..847ba417fa1802588f246c73c987a7b2bae39f1b --- /dev/null +++ b/common_sql_windows_server_hosts.md @@ -0,0 +1,14 @@ +# Windows Server hosts + +Source: https://docs.rubrik.com/en-us/saas/common/sql_windows_server_hosts.html + +--- + +# Windows Server hosts + +Manage and protect Microsoft SQL Server databases through the Rubrik Backup Service running on a Windows Server host. + +Adding a Windows Server host to a Rubrik cluster establishes a secure connection between the Rubrik cluster and the Rubrik Backup Service on the Windows Server host. After the Windows Server host is added, the Microsoft SQL Server databases and Microsoft SQL Server databases on the Windows Server host appear in the web UI. + +Remove a Windows Server host from the Rubrik cluster to stop managing the data of the Microsoft SQL Server databases on that host. The Microsoft SQL Server instances on the removed Windows Server host move to the Snapshots tab. The Rubrik cluster continues to provide access to existing snapshots and log backups until the snapshots expire due to SLA Domain policies, the log backups expire due to the retention settings, or the data (snapshots/logs) is otherwise removed manually. + *[ > ]: and then diff --git a/common_switch_configuration_examples.md b/common_switch_configuration_examples.md new file mode 100644 index 0000000000000000000000000000000000000000..37b23c998f955c337ec9edcca3e69d62e2361e04 --- /dev/null +++ b/common_switch_configuration_examples.md @@ -0,0 +1,78 @@ +# Switch configuration examples + +Source: https://docs.rubrik.com/en-us/saas/common/switch_configuration_examples.html + +--- + +# Switch configuration examples + +Rubrik CDM is compatible with a number of switch models, each of them requiring a specific configuration. + +Rubrik recommends configuring network switches in a mode that detects the bond configuration of the end device and allows it to connect whether it uses LACP or Active-Backup, if this mode is available. Some vendors refer to this as a fallback LACP mode. + +These examples show switch configurations for Arista and Cisco Nexus. The port channel configurations in these examples also include LACP fallback modes to the individual port configurations that support non-LACP configuration in case the node is reconfigured with an Active-Backup bond mode. + +Platform | Port-channel configuration | Member port configuration +---|---|--- +Arista | + + + interface Port-Channel400 + description POC-4 .90 channel + switchport access vlan 2228 + port-channel lacp fallback individual + port-channel lacp fallback timeout 180 + spanning-tree portfast + +| + + + interface Ethernet20 + description POC-4 eth2 + switchport access vlan 2228 + spanning-tree portfast + channel-group 400 mode active + + interface Ethernet21 + description POC-4 eth3 + switchport access vlan 2228 + spanning-tree portfast + channel-group 400 mode active + +Cisco Nexus | + + + interface port-channel 1989 + description sjc-b005-a-lb + switchport mode access + switchport access vlan 20 + spanning-tree port type edge + spanning-tree bpduguard enable + storm-control broadcast level 10.00 + storm-control multicast level 10.00 + storm-control unicast level 10.00 + no lacp suspend-individual + +| + + + interface Ethernet1/20 + switchport mode access + switchport access vlan 20 + spanning-tree port type edge + spanning-tree bpduguard enable + storm-control broadcast level 10.00 + storm-control multicast level 10.00 + storm-control unicast level 10.00 + channel-group 1989 mode active + + interface Ethernet1/21 + switchport mode access + switchport access vlan 20 + spanning-tree port type edge + spanning-tree bpduguard enable + storm-control broadcast level 10.00 + storm-control multicast level 10.00 + storm-control unicast level 10.00 + channel-group 1989 mode active + *[ > ]: and then diff --git a/db2_adding_db2_db_instance.md b/db2_adding_db2_db_instance.md new file mode 100644 index 0000000000000000000000000000000000000000..54550bcc383d0f0c05809b1fb8682f000d430e22 --- /dev/null +++ b/db2_adding_db2_db_instance.md @@ -0,0 +1,48 @@ +# Adding a Db2 database instance + +Source: https://docs.rubrik.com/en-us/saas/db2/adding_db2_db_instance.html + +--- + +# Adding a Db2 database instance + +Add a Db2 database instance to a Rubrik cluster to establish a connection for database protection. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Click Add Instance. + 6. In Db2 Instance Name, enter the name of the Db2 instance. + +Rubrik CDM version 9.3.0 and later support adding a Db2 instance hosted on Windows hosts. RSC only protects Db2 instances that are part of the default Db2 installation on a Windows host. + + 7. In Rubrik Cluster, select a Rubrik cluster for the instance to connect. + 8. In IPs/Hostnames, select an IP address or a hostname for this instance. + +For Rubrik CDM version 9.1.0 and later, you can select only one host. RSC automatically discovers the remaining hosts. + +For Rubrik CDM versions earlier than version 9.1.0, you can select multiple IP addresses or host names. + + 9. In Username, enter a username. + +Username is optional for Rubrik CDM versions later than 8.1.2 and earlier than 9.0.1. + + 10. In Password, enter a password. + +Password is optional for Rubrik CDM versions later than 8.1.2 and earlier than 9.0.1. + + 11. Click Add. + +## Results + +RSC checks connectivity with the specified IP address or hostname and adds a Db2 database instance. + *[ > ]: and then diff --git a/db2_adding_db2_db_instance_cdm8.1.1.md b/db2_adding_db2_db_instance_cdm8.1.1.md new file mode 100644 index 0000000000000000000000000000000000000000..f03519f9292661b39cc78e283d74eb6ee7ec09b1 --- /dev/null +++ b/db2_adding_db2_db_instance_cdm8.1.1.md @@ -0,0 +1,43 @@ +# Adding a Db2 database instance for CDM version 8.1.1 or earlier + +Source: https://docs.rubrik.com/en-us/saas/db2/adding_db2_db_instance_cdm8.1.1.html + +--- + +# Adding a Db2 database instance for CDM version 8.1.1 or earlier + +To establish a connection for database protection, add a Db2 database instance to a Rubrik cluster running CDM version 8.1.1 or earlier. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Click Add Instance. + +The Instance settings of the Add Instance dialog box appears. + + 6. In Db2 Instance Name, enter the name of the instance. + 7. In Rubrik Cluster, select a Rubrik cluster for the instance to connect. + 8. In IPs/Hostnames, select an IP address or a hostname for the instance. + +You can select multiple IP addresses or hostnames. + + 9. In Username, enter a username. + +The Db2 instance owner credentials are supported. Users with SYSADM, SYSCTRL, or SYSMAINT authorities are supported for CDM version 8.1.1 and later. + + 10. In Password, enter a password. + 11. Click Add. + +## Results + +RSC checks connectivity with the specified hosts and adds an instance. + *[ > ]: and then diff --git a/db2_changing_retention_db2_snapshot.md b/db2_changing_retention_db2_snapshot.md new file mode 100644 index 0000000000000000000000000000000000000000..80201bb7a2ab11ded8064a9959d4af1316351b3e --- /dev/null +++ b/db2_changing_retention_db2_snapshot.md @@ -0,0 +1,56 @@ +# Changing retention policy of a Db2 snapshot + +Source: https://docs.rubrik.com/en-us/saas/db2/changing_retention_db2_snapshot.html + +--- + +# Changing retention policy of a Db2 snapshot + +You can change the retention policy of a Db2 snapshot to optimize storage and data accessibility of Db2 databases. The SLA Domain policy retains snapshots for the maximum SLA Domain period, while the Forever retention policy retains snapshots until you delete them manually. + +## Before you begin + +Db2 backup retention policy requirements vary, depending on the installed Rubrik CDM version: + + * CDM versions 8.0.2 to 9.1.3 support only the Forever retention policy. + * CDM version 9.1.3 and later support changing the retention policy only of a full snapshot to either that of any applicable SLA Domain policy or to the Forever retention policy for any snapshot type. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Click Databases. + 6. Click a database name. + +The Object details page of the selected database appears. + + 7. Click Snapshots. + 8. Select a snapshot and click Change Retention. + +You can select multiple snapshots. + + 9. Select a retention policy for a selected snapshot. + +Option| Description +---|--- +SLA Domain | Retains only a full snapshot at all locations for the maximum retention period specified by the selected SLA Domain. +Forever | Retains any snapshot type until you manually delete it. + + 10. Click Next. + +The Confirmation page appears. + + 11. Review the summary information and click Assign. + +## Results + +RSC updates the retention policy for the selected Db2 snapshot or snapshots. + *[ > ]: and then diff --git a/db2_configuration_parameters_db2_databases.md b/db2_configuration_parameters_db2_databases.md new file mode 100644 index 0000000000000000000000000000000000000000..3a9f982239c14cd160f977e237bd5dd76ab56674 --- /dev/null +++ b/db2_configuration_parameters_db2_databases.md @@ -0,0 +1,31 @@ +# Configuration parameters for Db2 databases + +Source: https://docs.rubrik.com/en-us/saas/db2/configuration_parameters_db2_databases.html + +--- + +# Configuration parameters for Db2 databases + +Configuration parameters for Db2 databases. + +The following table describes the configuration parameters for each Db2 database. Configuration parameters | Description +---|--- +TRACKMOD | Taking delta or incremental backups requires the `TRACKMOD` database configuration be set to `ON`. Setting `TRACKMOD` to `ON` enables a database to track changes from the previous backup. Performing a full backup after updating the `TRACKMOD` configuration from `OFF` to `ON` is a requirement. When the configuration value is already set to `ON`, a full backup is not required. The following command configures `TRACKMOD`: + + + db2 update db cfg for database_name using TRACKMOD ON + +Where, database_name is the name of the database for which backup is being configured. +LOGARCHMETHx | Either `LOGARCHMETH1` or `LOGARCHMETH2` can specify the vendor path. When `LOGARCHMETH1` is set to `OFF`, Rubrik recommends using an alternative value, such as `LOGRETAIN` or `DISK:`. When `LOGARCHMETH1` is set to `vendorlib`, `LOGARCHMETH2` cannot be used as the archival method, and similarly, when `LOGARCHMETH2` is set to `vendorlib`, `LOGARCHMETH1` cannot be used as the archival method. Additionally, when `LOGARCHMETH1` is set to `USEREXIT` or `LOGRETAIN`, Db2 does not allow setting up LOGARCHMETH2. You can use the following command to configure `LOGARCHMETH1`: + + + db2 update db cfg for database_name using LOGARCHMETH1 LOGRETAIN + +Where, database_name is the name of the required database. + +Updating the configuration parameters requires performing a full backup using the following commands: + + * su - + * db2 backup db + + *[ > ]: and then diff --git a/db2_db2_adding_host.md b/db2_db2_adding_host.md new file mode 100644 index 0000000000000000000000000000000000000000..1d851f562ac46b2b7133c08a181b14710ffa0e6a --- /dev/null +++ b/db2_db2_adding_host.md @@ -0,0 +1,45 @@ +# Adding a Db2 host + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_adding_host.html + +--- + +# Adding a Db2 host + +To establish a connection between the Db2 server and RSC, add a host for enabling backup and recovery operations. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Click Manage Hosts. + +By default, the Linux & Unix page appears. + + 6. To add a Windows host, in Data Sources dropdown list, click Windows. + +The Windows page appears. + + 7. Click Add Hosts. + 8. In Rubrik cluster, select a Rubrik cluster for the host to connect. + 9. Select an option for using the Rubrik Backup Service (RBS). + +Option| Description +---|--- +I have already installed and registered the RBS software | Selecting this setting confirms the successful installation and registration of the RBS software. In Host IP addresses or FQDNs, enter an IP address or a host. You can add multiple IP addresses or hosts. +I want to install and register the RBS software now | Selecting this setting initiates the installation and registration process for the RBS software. Select the platform and version to install the RBS. Additionally, you can click to copy the RBS version or click to download the RBS package. + + 10. Click Add. + +## Results + +RSC checks connectivity with the specified hosts and adds the Db2 hosts. + *[ > ]: and then diff --git a/db2_db2_data_retrieval.md b/db2_db2_data_retrieval.md new file mode 100644 index 0000000000000000000000000000000000000000..3583876dae4b891067934dbeb1f8ec1363a437d7 --- /dev/null +++ b/db2_db2_data_retrieval.md @@ -0,0 +1,16 @@ +# Db2 data retrieval + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_data_retrieval.html + +--- + +# Db2 data retrieval + +Data retrieval methods such as db2_fetch_tool or db2_fetch_log_main ensures data integrity and continuity by downloading the data and log backup images if a Db2 system fails. + +The db2_fetch_tool simplifies the process of downloading data and log backup images to a specified location on the Db2 host. The db2_fetch_tool requires parameters such as workload ID, backup ID, and backup type for data backup image retrieval. Additionally, on the Db2 host, the db2_fetch_tool also requires a specified path to the location where the images will be downloaded and stored. As a prerequisite, you must add the Db2 instance associated with the instance owner of the fetch tool to RSC. The db2_fetch_tool plays a crucial role in ensuring the integrity of backup images before restore operations proceed. The db2_fetch_tool is primarily useful when you need to access, verify, or work with backup data within your Db2 environment. Standalone, Database Partitioning Feature (DPF), and High Availability Disaster Recovery (HADR) configurations support data backup images and log backup images. + +Rubrik CDM versions 9.0.1 and later support db2_fetch_tool. + +The db2_fetch_log_main downloads log backup images during restore. Rubrik CDM versions 8.0 through 9.0.0 support db2_fetch_log_main. + *[ > ]: and then diff --git a/db2_db2_db_details.md b/db2_db2_db_details.md new file mode 100644 index 0000000000000000000000000000000000000000..78642c2a454ae99c0b91e0b1aae956ce3fa3670c --- /dev/null +++ b/db2_db2_db_details.md @@ -0,0 +1,27 @@ +# Db2 database details + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_db_details.html + +--- + +# Db2 database details + +Information about the selected Db2 database, including the Overview, Events, and Snapshots tabs, and the available actions. + +On the Db2 database details page, you can view the following tabs: + + * Overview + * Events + * Snapshots + +The following table describes the actions that are available on all tabs. Action | Description +---|--- +Click | Provides the following options: + + * Configure Parallelism + * Configure Sessions + + +Manage Protection | Provides the option to select an SLA Domain and configure Db2 protection. +Take On-Demand Snapshot | Takes an immediate snapshot, overriding the SLA Domain backup schedule. This is usually done before high-risk tasks or maintenance to ensure quick restoration in case of issues. + *[ > ]: and then diff --git a/db2_db2_db_protection.md b/db2_db2_db_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..fa4529bd99d63989f49b7d3c6d01e659c4425c22 --- /dev/null +++ b/db2_db2_db_protection.md @@ -0,0 +1,28 @@ +# Db2 database protection + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_db_protection.html + +--- + +# Db2 database protection + +Db2 database protection uses SLA Domains to provide configurable data protection policies and enhanced security through retention-locked modes, ensuring consistent and secure management of Db2 workloads. + +Db2 database protection through SLA Domains consolidates data protection policies, providing a unified approach for your Db2 workloads. SLA Domains offer a configurable set of policies, including the following aspects: + + * Frequency + * Retention + * Archival + * Replication + * Db2-specific settings + * Retention lock + +These SLA Domain policies can be applied to Db2 database objects to achieve your data protection objectives. By assigning an SLA Domain to your Db2 workloads, you ensure that protection policies are applied consistently across your environment. + +For enhanced security, you can assign a retention-locked SLA Domain to your Db2 workloads, available in both governance mode and compliance mode: + + * Governance mode: Ensures data security by preventing accidental or malicious deletion or changes to retention settings, providing more flexibility + * Compliance mode: Enforces strict controls to prevent premature deletion of snapshots + +If a selected Db2 database object is protected by a retention-locked SLA Domain, it cannot be reassigned to an SLA Domain without a retention lock or to one with a shorter retention period. This maintains data integrity and compliance according to the set retention policies. + *[ > ]: and then diff --git a/db2_db2_db_restore_rollforward_processes.md b/db2_db2_db_restore_rollforward_processes.md new file mode 100644 index 0000000000000000000000000000000000000000..52930556ab2efcdcc42ed2eb2c2a30b685e54105 --- /dev/null +++ b/db2_db2_db_restore_rollforward_processes.md @@ -0,0 +1,48 @@ +# Db2 database restore and rollforward processes + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_db_restore_rollforward_processes.html + +--- + +# Db2 database restore and rollforward processes + +When incidents that result in data failure or corruption occur, the Db2 restore and rollforward processes recover data from backups to ensure that all data is available, accurate, and complete. + +## Db2 restore process + +In the event of data failure or corruption, the Db2 database restore process recovers your data to a previous state. This process involves two key steps. + + * Restoring database files: This step restores your backed-up files to the required location, which reconstructs the original structure of your database. Before restoring database files, you must first add the target host and Db2 instance to RSC. + * Applying transaction logs: This step tracks every change made to your data before the incident. By applying the logs, the process replays those changes, ensuring that your database reflects the state it was in at the time of the backup. + +Db2 restore brings your database back online with its data restored and consistent, enabling recovery from unforeseen incidents. + +## Rubrik CDM features for Db2 recovery + +Rubrik CDM versions 9.x provides an improved process with features such as: + + * Automatic log fetching during rollforward processes. + * Seamless restoration when restoring to the same or different database instances. + * Direct download of data and log backups to the Db2 host. + +For Rubrik CDM version 8.x, restoration involves manual log fetching when restoring to the same or different database instances. + +Rubrik recommends upgrading to Rubrik CDM version 9.x for an improved Db2 database restore and rollforward process. + +## Supported Db2 configurations + +Rubrik CDM supports restoration for specific Db2 configurations depending on the version. + +Rubrik CDM versions 9.x support restoration for the following configurations: + + * Database Partitioning Feature (DPF) + * Standalone + * High Availability Disaster Recovery (HADR) + * pureScale + +Rubrik CDM versions 8.x support restoration for the following configurations: + + * Database Partitioning Feature (DPF) + * Standalone + + *[ > ]: and then diff --git a/db2_db2_high_avail_clstrng_config.md b/db2_db2_high_avail_clstrng_config.md new file mode 100644 index 0000000000000000000000000000000000000000..fe84b7a431e3991fc123aad4b91f010c2c2a1fb6 --- /dev/null +++ b/db2_db2_high_avail_clstrng_config.md @@ -0,0 +1,26 @@ +# Db2 high availability cluster configurations + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_high_avail_clstrng_config.html + +--- + +# Db2 high availability cluster configurations + +High availability cluster configurations are host-side configurations for Db2 environments on AIX and Linux operating systems. These configurations manage the failover of applications and resources to ensure application availability during hardware or software failures. + +High availability cluster configurations provide failover capabilities that allow multiple hosts with unique IP addresses to function as a single cluster. At any given time, one host acts as the active node and handles connections to the Db2 database, while the other hosts remain inactive. If a failover occurs, an inactive host in the cluster becomes active to keep the Db2 databases continually available. + +You can use RSC to protect a Db2 instance by adding a host using a virtual IP (VIP) address or by adding hosts using their individual IP addresses. + +## Configuration using VIP address + +High Availability cluster configuration to protect a single Db2 instance requires adding a host, using a VIP address, and then adding a Db2 instance. Both the active and inactive hosts share the same resource groups and the VIP address, which always points to the active node. + +After updating the certificate, the inactive host becomes active, ensuring continuous availability of the Db2 databases. Following a failover, manually update the host certificate from the Edit Host in RSC to detect the new active node. If you do not update the certificate manually, you must wait 1 to 1.15 hours for the default periodic host certificate update to run automatically and detect the change. In case of a failover, there is only a single Db2 object, and the recoverable ranges still continue without any breaks. + +## Configuration using individual IP addresses + +The high availability cluster configuration protects host data individually by host for different workloads along with the Db2 instance. After a failover, the inactive host becomes active automatically, without the need to update the certificate. However, this configuration results in multiple Db2 objects after the first failover. + +This configuration requires adding each host in the cluster individually, using its IP address and then adding a Db2 instance. In the event of a failover, the inactive host automatically becomes active. After a failover, it takes up to 15 minutes for the system synchronization to complete and detect the changes. This configuration creates multiple Db2 objects in RSC. The result is that recoverable ranges are broken after a failover, which creates a new Db2 object for the first failover only. This consequence is an issue only for the first backup after failover. Subsequent failovers do not create multiple Db2 objects. + *[ > ]: and then diff --git a/db2_db2_protection_hierarchy_for_db2_instances.md b/db2_db2_protection_hierarchy_for_db2_instances.md new file mode 100644 index 0000000000000000000000000000000000000000..39d9497dada254effc85d90b0cb44160162ed6ce --- /dev/null +++ b/db2_db2_protection_hierarchy_for_db2_instances.md @@ -0,0 +1,15 @@ +# Db2 instances protection hierarchy + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_protection_hierarchy_for_db2_instances.html + +--- + +# Db2 instances protection hierarchy + +For Db2 instances, RSC provides automated protection based on the protection hierarchy. The automated protection mechanism simplifies the assignment of protection to multiple Db2 instances, facilitating the assignment of SLA Domains to all Db2 instances within the Db2 databases. + +Level | Description +---|--- +Db2 instances | By default, all the Db2 databases belonging to a Db2 instance will inherit an SLA Domain assignment or a Don't protect setting made to that Db2 instance. +Db2 databases | By default, Db2 databases derive their SLA from the Db2 instance. An SLA Domain assignment or a Don't protect setting made to the Db2 database overrides this default assignment. + *[ > ]: and then diff --git a/db2_db2_purescale.md b/db2_db2_purescale.md new file mode 100644 index 0000000000000000000000000000000000000000..cd79ca2d388195dfe0033ad2175f8491615e4c95 --- /dev/null +++ b/db2_db2_purescale.md @@ -0,0 +1,18 @@ +# Db2 pureScale + +Source: https://docs.rubrik.com/en-us/saas/db2/db2_purescale.html + +--- + +# Db2 pureScale + +Db2 pureScale is a clustered system that facilitates collaborative and scalable processing of database requests. With Db2 pureScale, you can achieve enhanced performance and shared data management by adding members to the pureScale cluster. + +Db2 pureScale is a multi-member database solution for IBM Db2. It provides a scalable and highly available database solution for your enterprise needs. With pureScale, you can achieve the following results: + + * Scale on demand: Based on changing business requirements, add or remove Db2 members without complex reconfiguration or disruption to applications. + * Boost performance: Distribute incoming database requests across multiple members, improving processing speed and response times. + * Maximize uptime: Ensure continuous database availability in the event of hardware or software failures. pureScale automatically redirects requests to other available members, minimizing downtime and data loss. + * Simplify management: Manage the entire cluster as a single entity, streamlining administration and reducing complexity. + + *[ > ]: and then diff --git a/db2_deleting_db2_db_instance.md b/db2_deleting_db2_db_instance.md new file mode 100644 index 0000000000000000000000000000000000000000..4fe17b0e48d842a030cd726ad66bc3cffa375584 --- /dev/null +++ b/db2_deleting_db2_db_instance.md @@ -0,0 +1,36 @@ +# Deleting a Db2 database instance + +Source: https://docs.rubrik.com/en-us/saas/db2/deleting_db2_db_instance.html + +--- + +# Deleting a Db2 database instance + +To manage and organize the Rubrik cluster by removing databases that are not contributing to a Db2 workload, delete the Db2 database instance. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Open the ellipsis menu for the instance you want to delete and select Delete Instance. + +A confirmation dialog box appears. + + 6. Click Delete. + +## Results + +RSC deletes all the metadata associated with the selected instance. + +Rubrik maintains configuration files on the Db2 host to ensure log archiving and data backups. These files are updated or removed whenever the protection status of a database object changes. If failures occur, such as due to loss of network connectivity, Rubrik might be unable to update or remove these files. In such cases, logs might continue to be archived to Rubrik. + +To prevent such situations, Rubrik recommends updating the LOGARCHMETH1 configuration for these databases to reflect the new archival location or resetting it as required. + *[ > ]: and then diff --git a/db2_editing_db2_db_instance.md b/db2_editing_db2_db_instance.md new file mode 100644 index 0000000000000000000000000000000000000000..019f3d9bd34373ad46e2540f6f55cb946a87c48b --- /dev/null +++ b/db2_editing_db2_db_instance.md @@ -0,0 +1,37 @@ +# Editing a Db2 database instance + +Source: https://docs.rubrik.com/en-us/saas/db2/editing_db2_db_instance.html + +--- + +# Editing a Db2 database instance + +To modify a Db2 database instance protected by a Rubrik cluster, edit the Db2 database instance settings. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Open the ellipsis menu of an instance and select Edit Instance. + 6. Make changes to the IP address or hostname. + +For Rubrik CDM versions 9.1.0 and later, you can select only one host. RSC will automatically discover the remaining hosts. + +For Rubrik CDM versions earlier than version 9.1.0, you can select multiple IP addresses or hostnames. + + 7. In Username, enter a username. + 8. In Password, enter a password. + 9. Click Save. + +## Results + +RSC modifies the information for the selected instance. + *[ > ]: and then diff --git a/db2_editing_db2_db_instance_cdm8.1.1.md b/db2_editing_db2_db_instance_cdm8.1.1.md new file mode 100644 index 0000000000000000000000000000000000000000..0c9d6f32eaa8b5d3819e5adce4599a9b2ae1cbb4 --- /dev/null +++ b/db2_editing_db2_db_instance_cdm8.1.1.md @@ -0,0 +1,30 @@ +# Editing a Db2 database instance for CDM version 8.1.1 or earlier + +Source: https://docs.rubrik.com/en-us/saas/db2/editing_db2_db_instance_cdm8.1.1.html + +--- + +# Editing a Db2 database instance for CDM version 8.1.1 or earlier + +To modify a Db2 database instance protected by a Rubrik cluster running CDM version 8.1.1 or earlier, edit the Db2 database instance settings. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Open the ellipsis menu of an instance and select Edit Instance. + 6. Make changes to the IP address or hostname, username, and password. + 7. Click Save. + +## Results + +RSC modifies the information for the selected instance. + *[ > ]: and then diff --git a/db2_high_availability_disaster_recovery.md b/db2_high_availability_disaster_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..ea615cd5367bce8dda5ee502a96e0ce0d91989b7 --- /dev/null +++ b/db2_high_availability_disaster_recovery.md @@ -0,0 +1,30 @@ +# High Availability Disaster Recovery + +Source: https://docs.rubrik.com/en-us/saas/db2/high_availability_disaster_recovery.html + +--- + +# High Availability Disaster Recovery + +High Availability Disaster Recovery in Db2 for Linux, Unix, and Windows ensures uninterrupted system operation and data protection against hardware failures, software errors, natural disasters, power outages, and network issues. + +High Availability Disaster Recovery (HADR) supports the following features for Db2 instances: + + * HADR is based on log replay. + * HADR replicates data in real-time from a primary database to one or more standby databases. + * The primary database ships its transaction log data to standby database through a TCP connection. The standby database continuously replays the log records to keep itself in sync with the primary database. + * If the primary database fails, you must run a takeover HADR by force command on the standby database to make it the new primary database. + * The database will only identify a HADR entity if the primary database is added to Rubrik application. + +You must configure HADR in the Db2 environment with primary and standby databases for high availability and disaster recovery. + +HADR allows you to have up to three standby databases in your setup. You can designate one of these databases as the principal HADR standby database. Any other standby database is an auxiliary HADR standby database. Both types of HADR standby databases are synchronized with the HADR primary database through a direct TCP/IP connection, and both types support reads on standby database. You can configure both types of standby databases for time-delayed log replay. Additionally, you can issue a forced or non-forced takeover on any standby database. + +HADR protects against data loss and downtime from site failures by replicating data changes from a primary database to a standby database. These Db2 systems come as a primary-standby database pair, enabling takeover and failback, in case the primary database goes down. + +RSC provides a single pane of glass for data management across all workloads and environments and protection for Db2 systems. HADR automates the discovery of Db2 databases. The data and log backups are written to the briks on the Rubrik cluster. Additionally, HADR supports incremental, delta, and log backups. + +When the failover happens, the same log file may be archived from the old and new primary databases for HADR entities. As a result, the duplicate log files will be saved with Rubrik. The log fetching is interactive, which means that if multiple instances of the same log file exist, you will be prompted to choose which version of the file to retrieve during restoration. + +HADR databases do not inherit the SLA Domain assigned to the Db2 instance. You can assign an SLA Domain for Db2 HADR database either through the HADR or through the database details page. + *[ > ]: and then diff --git a/db2_ibm_db2.md b/db2_ibm_db2.md new file mode 100644 index 0000000000000000000000000000000000000000..12279c9e99aa0f2749900422830d2bf2879b6a12 --- /dev/null +++ b/db2_ibm_db2.md @@ -0,0 +1,15 @@ +# IBM Db2 + +Source: https://docs.rubrik.com/en-us/saas/db2/ibm_db2.html + +--- + +# IBM Db2 + +With IBM Db2 workloads, you can automate complex tasks such as database discovery and data protection for managing databases. + +Rubrik provides native protection by the policies defined in SLA Domains. The databases are discovered in an automated way and protected with the SLA Domains. The Db2 protection integrates with the vendor library while providing support for full, incremental, delta, and log backups. Rubrik delivers compliance and capacity reports in addition to supporting various types of recovery of Db2 backup using native Db2 tools. + +SLA Domains can apply the data protection policies and management policies to Db2 objects. + +Db2 databases derive the assigned SLA Domain from the Db2 instances. However, an individual assignment to the Db2 database overrides the assignment derived from the Db2 instance. diff --git a/db2_parallelism_sessions_database_level.md b/db2_parallelism_sessions_database_level.md new file mode 100644 index 0000000000000000000000000000000000000000..25c14b534d98a9bef2ec4adeec5e07f6d4c5d082 --- /dev/null +++ b/db2_parallelism_sessions_database_level.md @@ -0,0 +1,18 @@ +# Parallelism and sessions at the database level + +Source: https://docs.rubrik.com/en-us/saas/db2/parallelism_sessions_database_level.html + +--- + +# Parallelism and sessions at the database level + +Parallelism is the ability to simultaneously read and back up different sections within the database during backup operations. Sessions are the highest permissible concurrent connections between Db2 and the Rubrik cluster. With support for parallelism and sessions at the database level, you can optimize your backup process for improved efficiency and speed. + +Using Db2, you can perform backup operations to protect your data. The performance of backup operations can be affected by two important settings, backup parallelism and backup sessions. + +Parallelism refers to the ability to perform multiple tasks at the same time. In the context of backup, parallelism determines how many parts of the database can be read and backed up simultaneously. It specifies the number of table spaces that can be processed concurrently during the backup operation. With high parallelism, backups are faster because the workload is divided among multiple resources. + +Backup sessions represent the maximum number of simultaneous connections allowed between Db2 and the Rubrik cluster. This determines the number of files that can be written to the backup system concurrently. Multiple sessions allow for simultaneous backup of multiple files, resulting in a faster backup process. + +You can configure the number of sessions and the level of parallelism required for your backups through RSC to optimize the backup process, making it faster and efficient. Additionally, these settings provide the flexibility to switch between configurations that can be applied at various levels: database level, host level, or to all the databases in a host. + *[ > ]: and then diff --git a/db2_post_rbs_upgrade_mgmt_db2_win.md b/db2_post_rbs_upgrade_mgmt_db2_win.md new file mode 100644 index 0000000000000000000000000000000000000000..9afa70f192ec29537a18c9df01fefb84beadc9d9 --- /dev/null +++ b/db2_post_rbs_upgrade_mgmt_db2_win.md @@ -0,0 +1,20 @@ +# Post RBS upgrade management for Db2 on Windows + +Source: https://docs.rubrik.com/en-us/saas/db2/post_rbs_upgrade_mgmt_db2_win.html + +--- + +# Post RBS upgrade management for Db2 on Windows + +After the Rubrik Backup Service upgrade, Db2 may encounter errors due to outdated processes. Restarting the database manager fixes the issue by updating necessary processes, ensuring seamless operation. + +The Rubrik cluster automatically upgrades the Rubrik Backup Service (RBS) software after a Rubrik CDM upgrade. + +## Issue during RBS upgrade + +During an RBS upgrade, the Rubrik vendor DLL also gets updated. Db2 uses the `vendorlib` DLL to connect to RBS for archiving logs. When the upgrade occurs during a backup, the RBS process stops. The vendor process used for archiving logs for Db2 on a Windows machine does not restart and continues using the old `vendorlib` DLL to communicate with RBS, which can lead to errors. + +## Solution + +To resolve the RBS upgrade issue, you can terminate the old vendor process by restarting the database manager using `db2stop` and `db2start` commands. Subsequently, Db2 automatically creates a new vendor process for archiving logs and loads the new `vendorlib` DLL. + *[ > ]: and then diff --git a/db2_recoverable_range_db2.md b/db2_recoverable_range_db2.md new file mode 100644 index 0000000000000000000000000000000000000000..32038bc31ab3be1c90b8a3343980f2ee1d10a47e --- /dev/null +++ b/db2_recoverable_range_db2.md @@ -0,0 +1,18 @@ +# Recoverable range for Db2 database + +Source: https://docs.rubrik.com/en-us/saas/db2/recoverable_range_db2.html + +--- + +# Recoverable range for Db2 database + +The recoverable range for a Db2 database is a visual representation of the duration within which you can recover a database to a specific point in time. + +You can restore a Db2 database to a specific point in time using one of the following methods: + + * Identifying a base full snapshot followed by a continuous change of log snapshots to that specific point in time. + * Identifying a chain of one full, one incremental, and one or more delta backups followed by a chain of continuous log snapshots to that specific point in time. + * Identifying a chain of one full and one or more delta backups followed by a chain of continuous log snapshots to that specific point in time. + +Rubrik defines recoverable range as a base full snapshot followed by a continuous chain of log snapshots. A break in the continuity of log snapshots leads to a break in the recoverable range of the Db2 database. + *[ > ]: and then diff --git a/db2_refreshing_db2_db_instance.md b/db2_refreshing_db2_db_instance.md new file mode 100644 index 0000000000000000000000000000000000000000..368475a74bc47178bf83409d75abe7ff5d34ec95 --- /dev/null +++ b/db2_refreshing_db2_db_instance.md @@ -0,0 +1,30 @@ +# Refreshing a Db2 database instance + +Source: https://docs.rubrik.com/en-us/saas/db2/refreshing_db2_db_instance.html + +--- + +# Refreshing a Db2 database instance + +To ensure that the information on a Rubrik cluster is up to date and accurate, refresh the Db2 database instance. When you refresh a Db2 database instance, all databases local to the selected instance are discovered and the relevant metadata is updated. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Open the ellipsis menu for the instance you want to refresh and select Refresh. + +The instance takes a few minutes to refresh. + +## Results + +The Db2 database instance is refreshed. RSC discovers all the databases local to the selected instance and updates the relevant metadata. + *[ > ]: and then diff --git a/db2_requirements_db2_protection.md b/db2_requirements_db2_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..3f24db7a1ca13c18659fd50271d737c86421eefe --- /dev/null +++ b/db2_requirements_db2_protection.md @@ -0,0 +1,56 @@ +# Requirements for Db2 protection + +Source: https://docs.rubrik.com/en-us/saas/db2/requirements_db2_protection.html + +--- + +# Requirements for Db2 protection + +Requirements for adding Db2 hosts and Db2 database instances to RSC for data protection. + +Rubrik CDM version 9.3 and later support Db2 for Windows. Db2 version upgrades on Rubrik clusters require different actions depending on the Rubrik CDM version. + + * For CDM version 8.1.2 or later with the passwordless discovery feature enabled, there is no need to restart the RBS. + * For CDM versions earlier than 8.1.2, the RBS requires restarting, using the service rubrikagents restart command. + +Rubrik recommends restarting the vendor process after upgrading the Rubrik cluster. Restarting the vendor process ensures that the vendor process operates on the latest code version, reducing the risk of compatibility issues, and maintaining optimal performance. + +The following table describes requirements for protecting a Db2 database. Requirement type | Requirement +---|--- +Db2 version compatibility | Protecting only one version of a Db2 workload at a time on a given host. +Python version | Installing Python version 3.6 or later on the Db2 host for CDM versions earlier than 8.1.1. +File path | Ensuring that the db2nodes.cfg file is present in the /sqllib/db2nodes.cfg path for Db2 instance configuration. +Command interpreter | Ensuring that ksh or bash script is set as the default command interpreter for the instance user when adding the Db2 instance. +Backup administrator limitation | Allowing only the instance user to be a backup administrator. +Ports | Opening ports 12800 and 12801 on the Db2 host and port 9639 on the nodes of the Rubrik cluster for communication and data transfer. +Database configuration parameters | Setting the TRACKMOD and LOGARCHMETH1 parameters for each database. +RBS installation | Installing the latest version of RBS from the Rubrik cluster on the Db2 hosts using the following commands: + + * For Linuxrpm -ivh rubrik-agent.x86_64.rpm + * For AIXrpm -ivh rubrik-agent-aix.pcc.rpm + * For WindowsManually installing RBS using RubrikBackupService.zip + + +RBS download | Adding RBS to the Db2 host and retrieving the host using the wget command. Using the following command: + + * For Linuxwget https://IP address/connector/rubrik-agent.x86_64.rpm \--no-check-certificate + * For AIXwget https://IP address/connector/rubrik-agent-aix.pcc.rpm \--no-check-certificateWhere https://IP address/connector/rubrik-agent.x86_64.rpm is the copied part from RSC. + * For WindowsDownload the installer from https://IP address/connector/RubrikBackupService.zip + + +Locale limitation | Deploying Db2 is supported only in the English language. +Permission management | For Linux: + + * Using the Db2 instance owner role to manage backup and restore permissions. + +For Windows: + + * Managing backup and restore permissions using user groups. Db2 instance owners must either belong to the Administrators group or create a new user group. When you name the new user group as Rubrik_Db2, RBS automatically validates it. + * Assigning the RBS logon user to the SYSADM_GROUP, SYSCTRL_GROUP, or SYSMAINT_GROUP for all Db2 instances that Rubrik will protect. + +Alternatively, you can contact Rubrik Support for the following: + + * Setting a custom group name other than Rubrik_Db2 that RBS automatically validates + * Preventing backup and restore access for the Administrators group + + *[ > ]: and then diff --git a/db2_taking_on_demand_snapshot_db2_db.md b/db2_taking_on_demand_snapshot_db2_db.md new file mode 100644 index 0000000000000000000000000000000000000000..a35cb0473040a4bb83260af88c9a96a7ba1ff7a2 --- /dev/null +++ b/db2_taking_on_demand_snapshot_db2_db.md @@ -0,0 +1,42 @@ +# Taking an on-demand snapshot of a Db2 database + +Source: https://docs.rubrik.com/en-us/saas/db2/taking_on_demand_snapshot_db2_db.html + +--- + +# Taking an on-demand snapshot of a Db2 database + +To protect critical data for immediate restoration and enhance overall snapshot security, take an on-demand snapshot of a Db2 database. You can take on-demand snapshots of a Db2 database during high-risk tasks, maintenance windows, or peak activity. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Db2 inventory card. + +The Db2 page appears. + + 5. Click Databases. + 6. Click a database name. + +The Object details page of the selected database appears. + + 7. Click Take on demand snapshot. + 8. Select the retention option for the on-demand snapshot. + +Option| Description +---|--- +SLA Domain | The retention is derived from the rules and polices of the selected SLA Domain. +Forever | The on-demand snapshot is retained indefinitely. + + 9. Click Next. + 10. Review the information on the confirmation dialog box and click Confirm. + +## Results + +RSC adds the on-demand snapshot task to the task queue. + *[ > ]: and then diff --git a/dscc_data_security_command_center.md b/dscc_data_security_command_center.md new file mode 100644 index 0000000000000000000000000000000000000000..3e7b8844e84910d375300132e59e5ce2da0f2e3c --- /dev/null +++ b/dscc_data_security_command_center.md @@ -0,0 +1,34 @@ +# Data Security Command Center + +Source: https://docs.rubrik.com/en-us/saas/dscc/data_security_command_center.html + +--- + +# Data Security Command Center + +The Data Security Command Center provides you with an assessment of the data security readiness for your organization, providing scores for different categories and overall. The Data Security Command Center also offers recommendations to improve low data security scores. + +The Data Security Command Center (DSCC) evaluates security risks to the data belonging to your organization and assesses data security readiness along the following categories: + + * Platform Security + * Data Threat Analytics + * Data Security Posture + * Data Protection & Recoverability + +For each category, DSCC extracts key metrics from the supported workloads and provides a score, identifies the causes for the score, and offers recommendations to improve the score. A higher score means better compliance with data security. Besides category scores, DSCC also provides an overall data security score, which is calculated as the average of the category scores. + +A score timeline plots data that correlates changes in score with changes in the underlying metrics impacting the score. You can view changes in the score timeline as a daily, weekly, or monthly view for up to 12 months. + +The DSCC dashboard displays category scores and the overall Data Security Score. The score ranges are colored as follows: + + * Green - ≥75 to ≤100 + * Orange - ≥50 to <75 + * Red - ≥0 to <50 + +Recommendations to improve low scores focus on increasing the metric ranges to achieve optimal scores. + +Note: + +Metrics such as the number of users who use TOTP represent the total number of accounts registered through RSC that require multifactor authentication. Accounts registered in a Rubrik cluster are not included in this total and might require manual verification. + +The categories Data Threat Analytics and Data Protection & Recovery provide links to their respective pages in RSC for further information on metrics. diff --git a/dscc_dscc_dashboard.md b/dscc_dscc_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..5dcab8c3c50873afc2f932b7c3a5474745397367 --- /dev/null +++ b/dscc_dscc_dashboard.md @@ -0,0 +1,19 @@ +# Data Security Command Center dashboard + +Source: https://docs.rubrik.com/en-us/saas/dscc/dscc_dashboard.html + +--- + +# Data Security Command Center dashboard + +The Data Security Command Center dashboard displays data security health scores and recommendations to improve the data security readiness of your organization. + +Security data risks in the Rubrik data protection system are quantified into a single score between 1 and 100. You can see this score, its categories, and the trend over a period of time in the Data Security Command Center (DSCC). + +The DSCC dashboard is used to explore the following capabilities: + + * Data observability: Automated risk identification, which includes the ability to assess and review risk. + * Security posture trends: Risk identification and remediation tracking over days, weeks, and months. Data security reports can be easily generated and shared with stakeholders. + * Intelligent data risk management: Intuitive, single SaaS console for collaborative efforts between the IT and Security teams. Industry standard best security practice recommendations are provided to address security risks. + + *[ > ]: and then diff --git a/dscc_dscc_metrics.md b/dscc_dscc_metrics.md new file mode 100644 index 0000000000000000000000000000000000000000..3e83ad9253e91bbf8ce526c5b8db24cfc2334cd4 --- /dev/null +++ b/dscc_dscc_metrics.md @@ -0,0 +1,41 @@ +# Data Security Command Center metrics + +Source: https://docs.rubrik.com/en-us/saas/dscc/dscc_metrics.html + +--- + +# Data Security Command Center metrics + +The Data Security Command Center extracts metrics from supported workloads and provides scores for each category. + +Category | Metrics +---|--- +Platform Security | + + * Number of users that use TOTP. + * Number of Rubrik clusters that are running an unsupported version. + * Number of Rubrik clusters that have a newer major version or a minor update available. + * A metric to track whether the RSC account is connected to the Rubrik Support portal. + +Note: Version checks are performed only for accounts that are logged into the Rubrik Support portal. The collected metrics do not affect the Platform Security score of users or the overall Data Security Score and are only used to generate recommendations. +Ransomware Investigation | + + * Number of Rubrik clusters enabled for Data Threat Analytics. + * Number of anomaly events that have occurred in the past week.This metric does not impact the score of the category and is only used to generate recommendations. + + +Sensitive Data Discovery | + + * Number of Rubrik clusters enabled for Data Security Posture. + * Number of sensitive files with open access. + + +Data Protection & Recoverability | + + * Number of workload objects (excluding those marked as Don't Protect from the calculation). + * Number of retention-locked SLA Domains. + * Number of objects in compliance with their SLA Domain. + * Number of Rubrik clusters that have fewer than 30 days of runway remaining. + * Workload objects marked as Don't Protect.This metric is provided as insight and does not impact the score of the category. + + *[ > ]: and then diff --git a/dscc_viewing_the_dscc_dashboard.md b/dscc_viewing_the_dscc_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..567ddc05392812084ef17c22de4fd98bcfe132bf --- /dev/null +++ b/dscc_viewing_the_dscc_dashboard.md @@ -0,0 +1,19 @@ +# Viewing Data Security Command Center dashboard + +Source: https://docs.rubrik.com/en-us/saas/dscc/viewing_the_dscc_dashboard.html + +--- + +# Viewing Data Security Command Center dashboard + +Access the Data Security Command Center dashboard to view the Data Security Score for the supported workloads. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Security Command Center. + +## Results + +The Data Security Command Center dashboard appears. + *[ > ]: and then diff --git a/dspm_assigning_resources_classification.md b/dspm_assigning_resources_classification.md new file mode 100644 index 0000000000000000000000000000000000000000..cde62235536a79d89cd67f0ff41dcb6239aa1646 --- /dev/null +++ b/dspm_assigning_resources_classification.md @@ -0,0 +1,40 @@ +# Assigning resources for classification + +Source: https://docs.rubrik.com/en-us/saas/dspm/assigning_resources_classification.html + +--- + +# Assigning resources for classification + +You can assign data categories to resources such as objects or clusters located in data centers, M365 workloads, and optionally to Azure virtual machines. After assignment, Data Security Posture scans resources to detect related data types. Cloud objects are scanned automatically. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture Dashboard appears. + + 3. Click Policies > Data Classification. + +The Data Classification page appears, displaying the list of data categories. + + 4. Click Resources. + 5. Select a data category and click Assign Resources. + 6. Select an option for assigning data categories to resources in your environment. + +| +---|--- +By cluster | Select By cluster, click Next, and then select the Rubrik clusters you want to assign this data category toSelecting this option assigns the data categories to Rubrik clusters. The assignment will apply to all current and future objects on the chosen clusters. +By object type | Select By object type, click Next, and then select the object types you want to assign this data category toYou can use the edit icon to assign the data category to all existing and future protected objects or to specific objectsSelecting this option assigns the data categories to specific object types. + + 7. Click Next. + +The Confirm data category Assignment page appears. + + 8. Confirm that the correct objects are selected and click Assign. + +## Results + +RSC assigns the data category as selected and performs an initial classification of data. + *[ > ]: and then diff --git a/dspm_creating_data_category.md b/dspm_creating_data_category.md new file mode 100644 index 0000000000000000000000000000000000000000..6ba400ee66c45f885e4a8e7238da89c06ccfc18d --- /dev/null +++ b/dspm_creating_data_category.md @@ -0,0 +1,36 @@ +# Creating a data category + +Source: https://docs.rubrik.com/en-us/saas/dspm/creating_data_category.html + +--- + +# Creating a data category + +Create a data category to look for specific classification information in Data Security Posture. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture Dashboard appears. + + 3. Click Policies > Data Classification. + +The Data Classification page appears, displaying the list of data categories. + + 4. Click Create Category. + +The Create a Data Category wizard appears. + + 5. Select the data types that you want to include in the new data category. + +You can use the search bar or the filters on the page to search for specific data types. + + 6. In Category Details, enter the name and description of the data category. + 7. Click Create. + +## Results + +Data Security Posture creates a data category + *[ > ]: and then diff --git a/dspm_creating_data_type.md b/dspm_creating_data_type.md new file mode 100644 index 0000000000000000000000000000000000000000..e72e3d138799cb266766388fab75fa3b4769bb0a --- /dev/null +++ b/dspm_creating_data_type.md @@ -0,0 +1,61 @@ +# Creating a data type + +Source: https://docs.rubrik.com/en-us/saas/dspm/creating_data_type.html + +--- + +# Creating a data type + +You can create customized data types to reflect your business and security policies and processes. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture Dashboard appears. + + 3. Click Policies > Data Classification. + +The Data Classification page appears, displaying the list of data categories. + + 4. Click Data Types. + +The Data Types page appears, with the list of data types available in Data Security Posture. + + 5. Click Create Data Type. + +The Create a data type wizard appears. + + 6. Provide a name and data category for the data type. + +Rubrik recommends assigning the data type to at least one data category. Data types not assigned to a data category here are automatically placed in the Uncategorized data category. + + 7. Select a sensitivity level for the data type. + +| +---|--- +Nonsensitive | Exposure of data classified as nonsensitive is unlikely to harm your company. +Low | Exposure of data classified as low sensitivity may have minimal impact on your company. +Medium | Exposure of data classified as medium sensitivity may have moderate impact on your company. +High | Exposure of data classified as medium sensitivity may have severe impact on your company. + + 8. Click Next. + 9. Select an option for detecting your data type: + * Regex to detect a sequence of characters that specifies a search pattern. + * Dictionary to detect a comma-separated list of phrases. + 10. Enter a value and structured key for the structured data. + +Structured data is typically stored in databases and spreadsheets, for example .json, .csv, and .xml files. + + 11. Enter a value and structured key for the unstructured data. + +Unstructured data is typically stored in an unstructured file, for example .txt, .docx, or .md files. + + 12. **Optional:** Turn on Validate to validate unstructured regex values using sample text. + 13. Click Finish. + +## Results + +Data Security Posture creates the data type based on the specifications. + *[ > ]: and then diff --git a/dspm_creating_policies_in_dsp.md b/dspm_creating_policies_in_dsp.md new file mode 100644 index 0000000000000000000000000000000000000000..b7a5230d6455969f9c998a3e00d2d33cb258ec99 --- /dev/null +++ b/dspm_creating_policies_in_dsp.md @@ -0,0 +1,67 @@ +# Creating policies in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/creating_policies_in_dsp.html + +--- + +# Creating policies in Data Security Posture + +Create a policy with specific conditions to identify violations in Data Security Posture. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. Click Policies > Data Security Policies. + +The Data Security Policies page appears, displaying the list of policies and their specifications. + + 4. Click Create Policy. + +The Create a Policy wizard appears. + + 5. In the Details and Severity Level page, enter a name for the policy. + 6. In Category, select a category for the policy. + * Misplaced + * Overexposed + * Obsolete + * Misconfigured + 7. **Optional:** Enter a description for this policy. + +You can include what the policy will detect in the environment, and how this violation should be resolved. + + 8. Select a Severity Level for this policy. + * Low + * Medium + * High + * Critical + +Each violation will inherit the selected severity. + + 9. Click Next. + +The Conditions page appears. + + 10. Define the conditions for the policy. + +A violation is triggered when conditions are met. For example, when the exposure is public and sensitivity is high, or when the data category is financial and the Microsoft Information Protection (MIP) label is not highly confidential. + + 11. Click Next. + +The Automate Remediation page appears. + + 12. **Optional:** Click Automate Remediation to assign an MIP label automatically to the policy. + 13. **Optional:** Click Prevent this MIP label from lowering the sensitivity of existing assigned labels to prevent the label from being replaced with a label with a lower priority. + 14. Click Next. + +The Confirmation page appears. + + 15. Review policy details. To make changes, click Back. When you are finished, click Create. + +## Results + +You have successfully created the policy.Data Security Posture lists the new policy on the Data Security Policies page. + *[ > ]: and then diff --git a/dspm_creating_ticket_remediate_violations.md b/dspm_creating_ticket_remediate_violations.md new file mode 100644 index 0000000000000000000000000000000000000000..727c18f3c4a0fe43ae7be794be379e1bcac939ce --- /dev/null +++ b/dspm_creating_ticket_remediate_violations.md @@ -0,0 +1,48 @@ +# Creating a ticket to remediate violations in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/creating_ticket_remediate_violations.html + +--- + +# Creating a ticket to remediate violations in Data Security Posture + +Create a ServiceNow ticket to remediate any violations indicated in Data Security Posture. + +## Before you begin + +Configure the DSPM Ticketing Integration to create remediation tickets in ServiceNow. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. On the navigation bar, click Violations. + +The Data Security Violations page appears. You can sort the list of violations by policy or object. RSC groups by policy, by default. + + 4. Select the method for taking a remediation action. + * Click a policy name to view the list of affected objects, and then click the object on which you are taking the action. + * Click Object to group by objects, then click an object to view the list of violations and click the violation to address. + +A details window for the violation or object appears. + + 5. Click Remediate and select Create Ticket. + +The Create Ticket dialog box appears. + + 6. In Title, enter a title name to identify the remediation action. + 7. In Description, add additional information or edit what has been populated by RSC. + 8. **Optional:** Clear Attachments if you do not want to provide an attachment. + +The Attachment field provides an attachment with a list of files at risk for this violation. + + 9. In Comments, add any additional comments for information. + 10. Review the ticket information and click Create. + +## Results + +You have successfully created a ServiceNow ticket to remediate the violation. RSCsends the ticket to ServiceNow. + *[ > ]: and then diff --git a/dspm_data_classification_mgmt.md b/dspm_data_classification_mgmt.md new file mode 100644 index 0000000000000000000000000000000000000000..faaa995ebf32b5a5df1684b9427468fdcab4812e --- /dev/null +++ b/dspm_data_classification_mgmt.md @@ -0,0 +1,31 @@ +# Data classification management + +Source: https://docs.rubrik.com/en-us/saas/dspm/data_classification_mgmt.html + +--- + +# Data classification management + +You can manage data categories and data types, assign resources, and start on-demand classification according to your requirements in Data Security Posture. + +Data Security Posture organizes data categories into discovered data types. For example, data containing CVV or credit card numbers are categorized as Financial. Working with data categories enables you to quickly find information important to specific teams or tasks in your organization and track down data category-based data security violations when built into data security policies. + +Data Security Posture provides an extensive set of data types that cover an extensive range of information. Data Types represent various records living in your cloud environment. A record might be one of the following: + + * SSN in a cell in an Excel sheet + * Bank account number in a SQL database + * Username and password saved in a log file + * Passport number in a picture or scan of a passport + +Data Security Posture retrieves information about the record but does not extract or expose the actual data. Instead, Data Security Posture displays a data label that represents the actual data. This means, for example, that Data Security Posture might discover credit cards or CVVs stored in an account but will create a credit card or CVV data type to represent this information. Data Security Postureorganizes data types discovered into the following categories; Medical, Financial, Personal, Location, and Digital. + +You can create data categories by using data types and assigning objects and resources. Classification jobs created by data categories search sensitive data using industry regulations as search criteria. + +You can create a custom data category by using existing or custom data types and assigning objects to the data category. Classification jobs created by custom data category search sensitive data to address unique needs. + +You can assign policies to objects at the workload or cluster level or to individual objects. You can only assign policies to objects protected by an SLA Domain. Current limitations of policy assignment are the following: + + * By default, you can assign Data Security Posture data category to a maximum of 50,000 Microsoft 365 objects or 15,000 objects for other workloads. To increase this limit, contact Rubrik Support. + * Data Security Posture does not display data classification and data category assignment as a hierarchical list, though you can assign policies at a hierarchical level. + + *[ > ]: and then diff --git a/dspm_data_masking.md b/dspm_data_masking.md new file mode 100644 index 0000000000000000000000000000000000000000..ca4e744efe01ad4eafc325614357de440644a0d6 --- /dev/null +++ b/dspm_data_masking.md @@ -0,0 +1,53 @@ +# Data masking + +Source: https://docs.rubrik.com/en-us/saas/dspm/data_masking.html + +--- + +# Data masking + +Data masking replaces sensitive values in sampled data with obfuscated substitutes. This feature protects privacy while preserving the ability to understand data classified by Data Discovery and Classification. + +RSC supports data masking for Microsoft 365 objects protected by SLA Domains. + +## Masking Functionality + +You can verify Data Discovery and Classification accuracy by previewing data samples without exposing real records or original field combinations. This applies to structured data, such as tables and JSON objects. For unstructured free text, only detected sensitive tokens are masked in place, and no shuffling is applied. + +## Sampling behavior + +Data Discovery and Classification returns sample values only, not full records. Structured fields are shuffled across records. Each sample row is a synthetic mix of fields from different records. Original combinations of fields from the same record are never shown. + +## Shuffling method + +For each sensitive field, Data Discovery and Classification collects values across the sampled set, independently permutes each field list, and reassembles sample rows by position. For example, the sample data might include a credit card number from record A, a CVV from record B, and an expiration date from record C. + +## Masking scope and examples + +Data Discovery and Classification applies masking to all data after shuffling and before any data leaves the processing context. + +Here are some examples of how Data Discovery and Classification masks data: + + * Credit card numbers show only allowed digits and mask the remaining digits. + * CVV numbers are fully masked. + * Expiration dates are partially masked. + * Email addresses show the domain and mask the local portion. + +## Data handling and security + +When handling data, Data Discovery and Classification does not permit clear data to leave the organization in a readable form. Sampling runs in a protected, ephemeral context, and only masked, shuffled output is returned to the UI and API. RSC controls access by RBAC and audits every sample request. No row preserves the original combination of credit card number, CVV, and expiration date. + +The following is an example of source data: + + cc_number, cvv, exp_date + 4111111111111111, 123, 05/2027 + 5555555555554444, 987, 12/2028 + 4012888888881881, 456, 01/2026 + +The following is an example of returned data: + + cc_number , cvv, exp_date + 411111XXXXXX1111, 2** , 12/XXXX + 555555XXXXXX4444, *4* , 01/XXXX + 401288XXXXXX1881 3** , 05/XXXX + *[ > ]: and then diff --git a/dspm_data_security_posture.md b/dspm_data_security_posture.md new file mode 100644 index 0000000000000000000000000000000000000000..2e9ac7b8f38a0d9b10e361a8f96c819ab7385f60 --- /dev/null +++ b/dspm_data_security_posture.md @@ -0,0 +1,29 @@ +# Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/data_security_posture.html + +--- + +# Data Security Posture + +Data Security Posture provides agile data security across multi-cloud environments for posture management and access governance. It also includes threat monitoring and response to protect your data. + +Organizations have innovated how they use cloud data, but not how they secure it. Users create, copy, share, and move cloud data rapidly. This drastic expansion and replication of data for business advantage protected by traditional data security controls creates a security gap. Data Security Posture provides the capability to effectively manage data security, for data located on premises, in the cloud, or on SaaS applications. This unified approach enables you to define, manage, and monitor policies regardless of where data resides. Rubrik Data Security Posture discovers and classifies all data across all your environments, including managed and self-hosted technologies to provide the following benefits: + + * Automated data discovery across on-prem, cloud, and SaaS workloads + * Data classification without impact on production workloads + * Built-in and customizable data categories and data types + * Identity inventory showing sensitive data access and blast radius + * Identification of data at risk and appropriate access remediation + * User Insights highlighting changes to sensitive data + * Detection of suspicious data activity + +Data Security Posture automatically discovers and classifies an extensive range of data detected across your multi-cloud environment while ensuring that sensitive data never leaves your environment. Data Security Posture focuses on the following: + + * Identifying sensitive and regulated data across your organization + * Locating objects that have sensitive data and their location and flagging their exposure + * Detecting violations of your data policy and identifying misconfigured, misplaced, or obsolete data + * User access to data and remedying access issues + * Monitoring for allowed access and providing alerts of anomalous activities + +You can use the insights from Data Security Posture with third-party integrations to maintain a data security environment resilient to external threats. diff --git a/dspm_document_type_classification.md b/dspm_document_type_classification.md new file mode 100644 index 0000000000000000000000000000000000000000..e3e66b84e19f5beb03cb4fc894c8554762db3c45 --- /dev/null +++ b/dspm_document_type_classification.md @@ -0,0 +1,37 @@ +# Document type classification + +Source: https://docs.rubrik.com/en-us/saas/dspm/document_type_classification.html + +--- + +# Document type classification + +The document type classification provided by Data Security Posture helps you to set better data protection policies, reduce risks, and ensure regulatory compliance. + +Document type classification is available as part of the Rubrik DSPM license. + +Data Security Posture provides you with accurate document type classification for enhanced data security and control. The document type classification uses AI Large Language Models (LLMs) to determine the topic or essence of each unstructured document and provides this information in the Document Type column in the object inventory. RSC provides this information for Microsoft 365 objects. + +RSC supports the following document types for document type classification. + +Document type | Document type +---|--- +Audit Report | Employee Performance Review +Employment Agreement or Contract | Expense Report +Financial Transaction Record | General Internal Communications +Intellectual Property Documentation | Internal Company Processes and Procedures +Invoice or Receipt | IRS Form +Machine Generated Log | Medical Records +Mergers and Acquisitions Information | Organizational Budget Planning +Organizational Payroll Information | Pay Stub or Pay Slip +Police Report | Product or Service Brochure +Proprietary Project Planning | Report of Financial Results +Resume | Safety and Incident Reports +Sales Contract | Strategic Company Plans +Supplier Agreement or Contract | Training Material +Travel Itineraries and Plans | User Manual + +Note: + +AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. + *[ > ]: and then diff --git a/dspm_downloading_violating_files_log.md b/dspm_downloading_violating_files_log.md new file mode 100644 index 0000000000000000000000000000000000000000..4f910f4124267bc4abaad619df92d3a0ae521d76 --- /dev/null +++ b/dspm_downloading_violating_files_log.md @@ -0,0 +1,45 @@ +# Downloading the violating files log in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/downloading_violating_files_log.html + +--- + +# Downloading the violating files log in Data Security Posture + +Generate and download a log of violating files in Data Security Posture. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. On the navigation bar, click Violations. + +The Data Security Violations page appears. You can sort the list of violations by policy or object. RSC groups by policy, by default. + + 4. Select the method for taking a remediation action. + * Click a policy name to view the list of affected objects, and then click the object on which you are taking the action. + * Click Object to group by objects, then click an object to view the list of violations and click the violation to address. + +A details window for the violation or object appears. + + 5. Click the and then Quick View in the row for a violation. + +The violations details window appears. + + 6. Click Remediate and select Download All Files at Risk as CSV. + +The Preparing File window appears. + + 7. Click View all files. + +The File Preparation Center window appears. + + 8. Click on the row for the file to download. + +## Results + +You have successfully generated the log. RSC downloads the log of all files at risk for the selected violation as a CSV file. + *[ > ]: and then diff --git a/dspm_downloading_violating_files_log_2.md b/dspm_downloading_violating_files_log_2.md new file mode 100644 index 0000000000000000000000000000000000000000..979962a079eb7cae8018ebb37ed62aa3a4c94b78 --- /dev/null +++ b/dspm_downloading_violating_files_log_2.md @@ -0,0 +1,45 @@ +# Downloading the violating files log in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/downloading_violating_files_log_2.html + +--- + +# Downloading the violating files log in Data Security Posture + +Generate and download a log of violating files in Data Security Posture. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. On the navigation bar, click Violations. + +The Data Security Violations page appears. You can sort the list of violations by policy or object. RSC groups by policy, by default. + + 4. Select the method for taking a remediation action. + * Click a policy name to view the list of affected objects, and then click the object on which you are taking the action. + * Click Object to group by objects, then click an object to view the list of violations and click the violation to address. + +A details window for the violation or object appears. + + 5. Click the and then Quick View in the row for a violation. + +The violations details window appears. + + 6. Click Remediate and select Download All Files at Risk as CSV. + +The Preparing File window appears. + + 7. Click View all files. + +The File Preparation Center window appears. + + 8. Click on the row for the file to download. + +## Results + +You have successfully generated the log. RSC downloads the log of all files at risk for the selected violation as a CSV file. + *[ > ]: and then diff --git a/dspm_dsp_aws_identities_information.md b/dspm_dsp_aws_identities_information.md new file mode 100644 index 0000000000000000000000000000000000000000..2a514497bda35bf10c0e1eafaf6ff73da53528b1 --- /dev/null +++ b/dspm_dsp_aws_identities_information.md @@ -0,0 +1,26 @@ +# AWS identities information + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_aws_identities_information.html + +--- + +# AWS identities information + +The AWS Identities page provides data access assessment and monitoring capabilities for data found in assets across your cloud landscape. + +The AWS Identities information is available on the AWS Identities page for AWS identities. + +To explore the details of an identity further, you can do the following: + * Clicking an identity on the main AWS Identities page displays a subsequent page. This page shows additional associated identities and the accessible objects for that specific identity within their respective tabs. + * Clicking an identity on this subsequent page opens the Identity Details page. This page further displays members, associated identities, and accessible objects in their dedicated tabs. + +## AWS identity types + +The Identity Inventory lists identities that are learned from the AWS Identity and Access Management (IAM) system. These identities include the following types: + +Identity Types | Description +---|--- +Roles | A role is an identity with specific permissions granted to the user assigned to the role. +Groups | A group of users. Rubrik recommends granting permissions to groups rather than directly to users, aligning with a business need. +Users | An identity defining the set of permissions a specific person or entity has within the environment. This option usually refers to human identities. + *[ > ]: and then diff --git a/dspm_dsp_enterprise_edition_dashboard.md b/dspm_dsp_enterprise_edition_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..49b574b71fd2f26af87625683014507d64d3ba06 --- /dev/null +++ b/dspm_dsp_enterprise_edition_dashboard.md @@ -0,0 +1,27 @@ +# Data Security Posture Enterprise Edition dashboard + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_enterprise_edition_dashboard.html + +--- + +# Data Security Posture Enterprise Edition dashboard + +The Data Security Posture dashboard for the Rubrik Enterprise Edition provides a high-level view of your sensitive data, across protected workloads configured for Data Security Posture. + +The Data Discovery and Classification dashboard is available for users with the Rubrik Enterprise Edition. + +The following table describes the different elements of the Data Security Posture dashboard. Dashboard element | Description +---|--- +Object coverage | A bar showing the percentage of total objects covered by Data Security Posture. Coverage for these objects starts when you assign SLA Domains and Data Security Posture policies to objects to provide a comprehensive view of your Data Security Posture.The dashboard data reflects only the objects for which Data Security Posture has been enabled. +Sensitivity aggregation | A widget showing the number of high-sensitivity objects, total files with hits, and the number of total hits for cloud, datacenter, and SaaS objects. +Data distribution | A bar graph showing the distribution of sensitive data in different object types. You can filter the data by: + + * Object type or account + * Time, which can be the past 7 days, the past 30 days, or the past 90 days + * Environment, which can be all environments, or datacenter, cloud, or SaaS environment + +Clicking View All displays the Object Inventory page. +Data categories | A pie chart showing the distribution of sensitive hits in objects, broken down as objects with high-sensitivity, medium-sensitivity, low-sensitivity, and non-sensitive hits.You can filter the data by environment, all environments, datacenter, cloud, or SaaS environment. +Top sensitive objects | A list of the top sensitive objects with the number of hits by sensitivity and the impacted data categories.You can filter the data by environment, all environments, datacenter, cloud, or SaaS environment. Clicking View All displays the Object Inventory page.Clicking View All displays the Object Inventory page. +Data hits over time | A bar graph showing the distribution of data hits in objects, broken down as objects with high-sensitivity, medium-sensitivity, low-sensitivity, and non-sensitive hits.You can filter the data for the past 7 days, the past 30 days, the past 90 days, or the past six months. + *[ > ]: and then diff --git a/dspm_dsp_epe_dashboard.md b/dspm_dsp_epe_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..39c8e9e50f2a1018859c2e2df47aa76a3406207a --- /dev/null +++ b/dspm_dsp_epe_dashboard.md @@ -0,0 +1,48 @@ +# Data Security Posture management dashboard + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_epe_dashboard.html + +--- + +# Data Security Posture management dashboard + +The Data Security Posture management dashboard provides a unified view of where sensitive data resides across cloud, datacenter, and SaaS environments. Interactive charts and detailed breakdowns allow you to quickly identify, investigate, and address data most at risk to strengthen overall data security. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +The Data Security Posture management dashboard is available for users with the RSC Enterprise Proactive Edition, UCL Enterprise Proactive Edition, and Data Security Posture licenses. The Data Security Posture dashboard displays the type of sensitive data contained in folders, data that matches any policies, and other issues detected in classification jobs. + +The following table describes the different elements of the Data Security Posture dashboard. Dashboard element | Description +---|--- +Overview | A widget showing the following information: + + * Percentage of cloud, datacenter, and SaaS objects covered by Data Security Posture that are being scanned for sensitive data and data violations. + * Total number of objects with sensitive hits. On hovering, RSC displays the breakdown of cloud, datacenter, and SaaS objects with sensitive hits and the number of new objects with sensitive hits in the time period selected. + * The number of active violations broken down as Critical, High, or Other. RSC also shows the number of new violations of these types in the time period selected. + +You can filter the data in this widget for the past 7 days, 30 days, or 90 days.Coverage for on-prem objects starts when you assign SLA Domains and data categories to objects to provide a comprehensive view of your Data Security Posture. The dashboard data reflects only the objects for which Data Security Posture has been enabled.You can add additional protected objects to Data Security Posture and data categories to these objects to increase coverage. +Active Violations by Category | A bar graph that displays the active violations for the misplaced, redundant, overexposed, and unprotected data categories. Data Security Posture also provides a breakdown of the violations by severity level and indicates the number of new violations per category.You can filter this information for the past 7 days, past 30 days, or past 90 days. +Top Active Violations | A list of violations with the highest severity and the largest volume of data at risk. The widget shows the severity, data at risk broken down by sensitivity, and the number of violations for the top impacted policies. Clicking View All displays the Violations page. +New and Resolved Violations | A chart showing the number of created violations and resolved violations over time. You can view this information for the past 7 days, past 30 days, or the past 90 days. Clicking a point in the graph shows the number of active and resolved violations listed by severity at that point in time. +Data Distribution | A bar graph showing the distribution of sensitive data in different object types. You can filter the data by: + + * Object type or account + * Time, which can be the past 7 days, the past 30 days, or the past 90 days) + * Environment which can be all environments, or a datacenter, cloud, or SaaS environment + +Clicking View All displays the Object Inventory page. +Data Categories | A pie chart showing the distribution of sensitive hits in different object types. You can filter the data by: + + * Impacted policy or all policies + * Time, which can be the past 7 days or the past 30 days + +Hovering over the data distribution for a specific object provides the breakdown of hits and the percentage change over the time period selected. +Insights | A list showing access changes calculated using the data for the current day and the previous day, highlighted by user and object, including the following details: + + * Number of users with access changes + * Number of objects with access changes + * The relevant AD group that the users belong to + * The changes that caused the access changes + +Clicking the objects and users links displays the Objects page and Identity Inventory page, respectively. The data is available in RSC for 30 days. + *[ > ]: and then diff --git a/dspm_dsp_policies.md b/dspm_dsp_policies.md new file mode 100644 index 0000000000000000000000000000000000000000..14005b77a01e3fc7028484a8f6feec24f90e097e --- /dev/null +++ b/dspm_dsp_policies.md @@ -0,0 +1,25 @@ +# Data Security Posture policies + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_policies.html + +--- + +# Data Security Posture policies + +Data Security Posture policies deliver specific data security frameworks for protecting data and simplifying the management of data breaches in complex cloud infrastructures. + +Data Security Posture policies can be applied to data regardless of its storage location, configuration semantics, and underlying infrastructure technology. By focusing on the data, rather than the infrastructure, policies offer an effective and efficient means of protecting sensitive information. Data Security Posture policies are continuously evaluated against the state of the environment including the data, configuration, and activity to detect new violations and determine if existing violations are resolved. Data Security Posture offers policies covering important areas of data security. Policies in Data Security Posture identify these four different types of security challenges: + + * Misplaced data, which refers to sensitive data that has been saved without appropriate access controls. For example, PII data that is GDPR-regulated, but is stored outside of Europe. + * Overexposed data, which refers to sensitive data that can be accidentally exposed through open access. For example, SQL database backup with sensitive financial data being exposed to a third-party vendor. + * Obsolete data, which refers to sensitive data that has not been accessed in a long time. For example, an unmanaged database backup with sensitive data of which the origin database has been deleted. + * Misconfigured data, which refers to data without appropriate protection, such as data without encryption at rest and/or in transit. For example sensitive data without activity logging. + +You can activate, create, or modify policies to meet your unique security and regulatory requirements. You can use policies and violation tools to do the following: + + * Monitoring data security risks using both built-in and custom policies. + * Understanding the data risk and its root cause. + * Prioritizing data security violations. + * Expediting resolution with remediation guidance and integrations. + + *[ > ]: and then diff --git a/dspm_dsp_single_violation_details.md b/dspm_dsp_single_violation_details.md new file mode 100644 index 0000000000000000000000000000000000000000..570af24c982d96914e4c9bb46800f75091073786 --- /dev/null +++ b/dspm_dsp_single_violation_details.md @@ -0,0 +1,29 @@ +# Single violation details + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_single_violation_details.html + +--- + +# Single violation details + +You can view the details of a single violation for an object, the data at risk, and the object. + +## Single violation details window + +You can access the details for a single violation by clicking a violation. This window shows data at risk and provides options for fixing the violation on the object. + +The single violation details window includes the following elements. Tab | Description +---|--- +Overview | Provides the following information: + * Details section, which displays the impacted category of the violation, the date it was detected, the date it was last evaluated, and the related ticket. + * Data at Risk by Sensitivity donut chart, which displays all data hits on files matching the policy condition. You can go to the Data at Risk tab to get a more detailed view of the data affected by this violation. + * Object Details section, which displays the name of the object, the object type, the object location, the relevant Rubrik cluster, the time the object was last accessed, the object creation date, and the time the object was last classified. +Data at Risk | Provides the following information: + * The data at risk due to the violation is sorted by sensitivity. Red indicates high sensitivity, orange indicates medium sensitivity, and blue indicates low sensitivity of the data at risk. The total hits due to the violation are also indicated. + * The impacted Data Categories due to the violation. + * The impacted Data Types due to the violation. + * Microsoft Information Protection (MIP) labels if any were added. + * The top files at risk due to the violation, determined by files with the most sensitive hits. +Clicking View Files displays the Object Details page for the files in the violation. +Access Graph | Displays an interactive graph for the violation that shows the relationship between identities, permissions, and data.With this graph, you can identify and visualize access to data to more easily remediate access violations. When you select an element in the graph, it opens an information panel for that element. You can use the filter application to focus on and investigate a part of the graph in more detail. + *[ > ]: and then diff --git a/dspm_dsp_single_violation_details_2.md b/dspm_dsp_single_violation_details_2.md new file mode 100644 index 0000000000000000000000000000000000000000..a70bec2ed4973a5be5b1594d346782467f964996 --- /dev/null +++ b/dspm_dsp_single_violation_details_2.md @@ -0,0 +1,138 @@ +# Single violation details + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_single_violation_details_2.html + +--- + +# Performing cyber recovery for AWS EC2 instances using a Recovery Plan + +Perform cyber recovery using a Recovery Plan to recover AWS EC2 instances. + +## About this task + +If you are recovering AWS EC2 instances to an isolated environment, ensure that you include all fundamental infrastructure services required for these EC2 instances to function. These infrastructure services might include, but are not limited to, DNS and authentication services. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + 4. Click AWS EC2. + 5. Select the recovery plan from the list. + 6. Click Recover. + 7. Enter a Recovery Name. + +If you do not enter a recovery name, RSC names the recovery as "Recovery_Plan_Name_Recovery_Date_Recovery_Number by default, where Number stands for an assigned number. + +When you provide a name, RSC names the recovery accordingly. + + 8. Click Next. + +The Select Snapshots page appears. + + 9. **Optional:** In Boot Settings, select the option to launch in the power off state. + 10. In Error Handling for VM Recovery, choose an option for error handling. + +Option| Description +---|--- +Pause and resume manually after assessing the error | RSC stops the recovery if there is an error during the recovery.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort and clean up the recovered objects | RSC stops the recovery and cleans up the recovery jobs and any resources in use if there is an error during the recovery.# Performing cyber recovery for AWS EC2 instances using a Recovery Plan + +Perform cyber recovery using a Recovery Plan to recover AWS EC2 instances. + +## About this task + +If you are recovering AWS EC2 instances to an isolated environment, ensure that you include all fundamental infrastructure services required for these EC2 instances to function. These infrastructure services might include, but are not limited to, DNS and authentication services. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + 4. Click AWS EC2. + 5. Select the recovery plan from the list. + 6. Click Recover. + 7. Enter a Recovery Name. + +If you do not enter a recovery name, RSC names the recovery as "Recovery_Plan_Name_Recovery_Date_Recovery_Number by default, where Number stands for an assigned number. + +When you provide a name, RSC names the recovery accordingly. + + 8. Click Next. + +The Select Snapshots page appears. + + 9. **Optional:** In Boot Settings, select the option to launch in the power off state. + 10. In Error Handling for VM Recovery, choose an option for error handling. + +Option| Description +---|--- +Pause and resume manually after assessing the error | RSC stops the recovery if there is an error during the recovery.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort and clean up the recovered objects | RSC stops the recovery and cleans up the recovery jobs and any resources in use if there is an error during the recovery. + + 11. Click Next. + +The Select Snapshots page appears. + + 12. In Snapshot Selection, choose a recovery point in time. + +Option| Description +---|--- +Latest Snapshot Taken Before | The cyber recovery uses the most recent snapshot for each virtual machine in the Recovery Plan. +Select Snapshots | Specify a snapshot to use for each virtual machine in the Recovery Plan. Open for each virtual machine and click Select Snapshot to choose a snapshot. Then, click Save Selection to save your selected snapshot. + +When you choose to select snapshots for each virtual machine, you can filter them based on the Data Threat Analytics outcome. + + 13. (Select snapshot) In Latest Snapshot Taken Before, select the date and time, and in Anomaly Detection Outcome, select a snapshot type. + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides a filtered list of non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides a filtered list of quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides a filtered list of anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a filtered list of snapshots without considering snapshot status. + + 14. (Select snapshots) Select snapshots for the objects and click Save Selection. + 15. Click Next. + +The Network Configuration page appears. + + 16. **Optional:** (Editing network configuration) Edit the network configuration settings and click Save. + +You can edit the VPC, Subnet, and Security Group for the Recovery Plan. Security Groups are optional and are not used by default. + + 17. Click Recover. + +## Results + +RSC starts the cyber recovery and updates the Recoveries tab. You can view Recovery information in the Recoveries and Events pages. + +# Single violation details + +You can view the details of a single violation for an object, the data at risk, and the object. + +## Single violation details window + +You can access the details for a single violation by clicking a violation. This window shows data at risk and provides options for fixing the violation on the object. + +The single violation details window includes the following elements. Tab | Description +---|--- +Overview | Provides the following information: + * Details section, which displays the impacted category of the violation, the date it was detected, the date it was last evaluated, and the related ticket. + * Data at Risk by Sensitivity donut chart, which displays all data hits on files matching the policy condition. You can go to the Data at Risk tab to get a more detailed view of the data affected by this violation. + * Object Details section, which displays the name of the object, the object type, the object location, the relevant Rubrik cluster, the time the object was last accessed, the object creation date, and the time the object was last classified. +Data at Risk | Provides the following information: + * The data at risk due to the violation is sorted by sensitivity. Red indicates high sensitivity, orange indicates medium sensitivity, and blue indicates low sensitivity of the data at risk. The total hits due to the violation are also indicated. + * The impacted Data Categories due to the violation. + * The impacted Data Types due to the violation. + * Microsoft Information Protection (MIP) labels if any were added. + * The top files at risk due to the violation, determined by files with the most sensitive hits. +Clicking View Files displays the Object Details page for the files in the violation. +Access Graph | Displays an interactive graph for the violation that shows the relationship between identities, permissions, and data.With this graph, you can identify and visualize access to data to more easily remediate access violations. When you select an element in the graph, it opens an information panel for that element. You can use the filter application to focus on and investigate a part of the graph in more detail. + *[ > ]: and then diff --git a/dspm_dsp_threats.md b/dspm_dsp_threats.md new file mode 100644 index 0000000000000000000000000000000000000000..77b3572ffeb1f2bbe008c41e1451af1ce157871c --- /dev/null +++ b/dspm_dsp_threats.md @@ -0,0 +1,28 @@ +# Threats feature in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_threats.html + +--- + +# Threats feature in Data Security Posture + +You can use the Threats feature in Data Security Posture to detect external and internal data breaches in your environment. + +Data Security Posture detects threats in near real-time, enabling quick containment and minimizing potential damage to your organization. Threat information is also enriched with important contextual information, facilitating rapid investigation and triage. The Threats feature identifies anomalies and suspicious activities that impact data in your environment and sends alerts regarding: + + * Data exfiltration + * Suspicious third-party activity + * Suspicious insider activity + * Accidental data leaks + +Data Security Posture supports threat information for the following environments: + + * AWS S3 buckets using S3 server access logs. + +Before you begin working with the Threats feature, verify that you have enabled these logs. + + * Azure Blob storage using logs streaming into Azure Event Hub. + + * You must set up Azure logs in Azure before working with this option. + + *[ > ]: and then diff --git a/dspm_dsp_violations.md b/dspm_dsp_violations.md new file mode 100644 index 0000000000000000000000000000000000000000..a6149b00d6008124ddcad11a9ef8cc30830b55a3 --- /dev/null +++ b/dspm_dsp_violations.md @@ -0,0 +1,12 @@ +# Violations in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_violations.html + +--- + +# Violations in Data Security Posture + +Policy violations in Data Security Posture provide detailed information and analysis of why a data security or compliance violation is indicated. + +Data Security Posture has an extensive range of predefined policies that help you quickly handle critical data security challenges. You can also create custom policies to instruct Data Security Posture to send policy violations when the conditions you define are matched. This is important when secrets such as passwords and tokens are stored outside of a vault or when sensitive data is detected in testing and production environments or in an unauthorized geographic location. Data Security Posture continuously evaluates policies against the state of the environment, such as data, configuration, and activity, to detect new violations and determine if existing violations have been resolved. It can take up to four hours to detect a violation or resolve it. Data Security Posture tracks the status of violations and changes the status to Resolved when it no longer detects them. + *[ > ]: and then diff --git a/dspm_dsp_violations_2.md b/dspm_dsp_violations_2.md new file mode 100644 index 0000000000000000000000000000000000000000..4e1d00e238e7645656773523de5fa143694795df --- /dev/null +++ b/dspm_dsp_violations_2.md @@ -0,0 +1,12 @@ +# Violations in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_violations_2.html + +--- + +# Violations in Data Security Posture + +Policy violations in Data Security Posture provide detailed information and analysis of why a data security or compliance violation is indicated. + +Data Security Posture has an extensive range of predefined policies that help you quickly handle critical data security challenges. You can also create custom policies to instruct Data Security Posture to send policy violations when the conditions you define are matched. This is important when secrets such as passwords and tokens are stored outside of a vault or when sensitive data is detected in testing and production environments or in an unauthorized geographic location. Data Security Posture continuously evaluates policies against the state of the environment, such as data, configuration, and activity, to detect new violations and determine if existing violations have been resolved. It can take up to four hours to detect a violation or resolve it. Data Security Posture tracks the status of violations and changes the status to Resolved when it no longer detects them. + *[ > ]: and then diff --git a/dspm_dsp_violations_info.md b/dspm_dsp_violations_info.md new file mode 100644 index 0000000000000000000000000000000000000000..9e0aaf1f0257787e40575669bec9b262ad941ac2 --- /dev/null +++ b/dspm_dsp_violations_info.md @@ -0,0 +1,42 @@ +# Data Security Posture violations information + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_violations_info.html + +--- + +# Data Security Posture violations information + +The Data Security violations page in Data Security Posture provides information on the active, created, and resolved violations on objects that Data Security Posture protects. + +The Data Security violations page includes the following elements. Element | Description +---|--- +Active Violations by Severity | Donut chart that displays the critical, high, medium, and low active violations. You can filter the information on this chart for the following: + * Past 7 days + * Past 30 days + * Past 90 days +Active Violations by Category | Bar graph that displays the misplaced, obsolete, overexposed, and misconfigured active violations. You can filter the information on this graph for the following: + * Past 7 days + * Past 30 days + * Past 90 days +New and Resolved Violations | Line graph that displays the created versus resolved violations over time. You can filter the information on this graph for the following: + * Past 7 days + * Past 30 days + * Past 90 days +List of violations | A list of violations that you can filter by policy or object. This helps in identifying the violation that puts most data at risk.You can filter data by: + * Violation Status + * Policy + * Severity + * Object Type + * Cloud Account + * Sensitivity + * Data Category + * Data Type + * Category + * Detected on + * Resolved On +Sensitivity levels of the data at risk are indicated by color: + * Red indicates high sensitivity + * Orange indicates medium sensitivity + * Blue indicates low sensitivity +When you group violations by policy, you can view the impacted policies, the violations and their severity, and the affected data category.When you group violations by object, you can view the impacted objects, the violations and their severity, the relevant account and location of the violation, and the time the violation was detected. + *[ > ]: and then diff --git a/dspm_dsp_violations_info_2.md b/dspm_dsp_violations_info_2.md new file mode 100644 index 0000000000000000000000000000000000000000..b48f133f606a44d4099b37217fb7b8557444e263 --- /dev/null +++ b/dspm_dsp_violations_info_2.md @@ -0,0 +1,42 @@ +# Data Security Posture violations information + +Source: https://docs.rubrik.com/en-us/saas/dspm/dsp_violations_info_2.html + +--- + +# Data Security Posture violations information + +The Data Security violations page in Data Security Posture provides information on the active, created, and resolved violations on objects that Data Security Posture protects. + +The Data Security violations page includes the following elements. Element | Description +---|--- +Active Violations by Severity | Donut chart that displays the critical, high, medium, and low active violations. You can filter the information on this chart for the following: + * Past 7 days + * Past 30 days + * Past 90 days +Active Violations by Category | Bar graph that displays the misplaced, obsolete, overexposed, and misconfigured active violations. You can filter the information on this graph for the following: + * Past 7 days + * Past 30 days + * Past 90 days +New and Resolved Violations | Line graph that displays the created versus resolved violations over time. You can filter the information on this graph for the following: + * Past 7 days + * Past 30 days + * Past 90 days +List of violations | A list of violations that you can filter by policy or object. This helps in identifying the violation that puts most data at risk.You can filter data by: + * Violation Status + * Policy + * Severity + * Object Type + * Cloud Account + * Sensitivity + * Data Category + * Data Type + * Category + * Detected on + * Resolved On +Sensitivity levels of the data at risk are indicated by color: + * Red indicates high sensitivity + * Orange indicates medium sensitivity + * Blue indicates low sensitivity +When you group violations by policy, you can view the impacted policies, the violations and their severity, and the affected data category.When you group violations by object, you can view the impacted objects, the violations and their severity, the relevant account and location of the violation, and the time the violation was detected. + *[ > ]: and then diff --git a/dspm_dspm_identity_inventory.md b/dspm_dspm_identity_inventory.md new file mode 100644 index 0000000000000000000000000000000000000000..5349f028b20f46b3dd6c96a9b82386c7a2e9e1f9 --- /dev/null +++ b/dspm_dspm_identity_inventory.md @@ -0,0 +1,38 @@ +# Identities in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/dspm_identity_inventory.html + +--- + +# Identities in Data Security Posture + +The Identity Inventory feature provides visibility into data that identities in your environment can access. + +The Identity Inventory provides comprehensive visibility into identities, their access permissions, entitlement scope, and access provisioning methods without relying on external agents. You can utilize the Identity Inventory to pinpoint excessive permissions and identify data access configurations misaligned with the best practices and policies of your organization. The Identity Inventory addresses the challenge of determining and monitoring who has access to which data in your organization and how that data is classified. + +## Data exposure risk management + +With the Identity Inventory, you can assess your data exposure risk and set access limits to achieve least-privilege access. The Identity Inventory identifies and analyzes user access factors and any changes to these factors, individually and in combination with each other. + +Note: + +The Identity Inventory is available as part of the Data Security Posture license. + +You can perform the following actions in the Identity Inventory: + + * Identifying high-impact users, groups, and roles to monitor their access to sensitive data and work with stakeholders to reduce access where required. + * Evaluating the blast radius of potentially compromised identities. + * Analyzing which identities in your organization are exposed to the most sensitive data types. You can then work with your internal teams to reduce that access as required. + +## Identity Inventory population process + +Data Security Posture performs the following tasks to populate the Identity Inventory: + + * Connects to your Identity and Access Management (IAM) system + +RSC supports the AWS, Entra ID, and Active Directory IAM systems. + + * Ingests IAM configurations + * Analyzes configurations to learn who can access what data + * Provides visibility around data access through the Identity Inventory + diff --git a/dspm_dspm_identity_inventory_2.md b/dspm_dspm_identity_inventory_2.md new file mode 100644 index 0000000000000000000000000000000000000000..98fd7c78d2dd6b2179b318accd01954256b71260 --- /dev/null +++ b/dspm_dspm_identity_inventory_2.md @@ -0,0 +1,39 @@ +# Identities in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/dspm_identity_inventory_2.html + +--- + +# Identities in Data Security Posture + +The Identity Inventory feature provides visibility into data that identities in your environment can access. + +The Identity Inventory provides comprehensive visibility into identities, their access permissions, entitlement scope, and access provisioning methods without relying on external agents. You can utilize the Identity Inventory to pinpoint excessive permissions and identify data access configurations misaligned with the best practices and policies of your organization. The Identity Inventory addresses the challenge of determining and monitoring who has access to which data in your organization and how that data is classified. + +## Data exposure risk management + +With the Identity Inventory, you can assess your data exposure risk and set access limits to achieve least-privilege access. The Identity Inventory identifies and analyzes user access factors and any changes to these factors, individually and in combination with each other. + +Note: + +The Identity Inventory is available as part of the Data Security Posture license. + +You can perform the following actions in the Identity Inventory: + + * Identifying high-impact users, groups, and roles to monitor their access to sensitive data and work with stakeholders to reduce access where required. + * Evaluating the blast radius of potentially compromised identities. + * Analyzing which identities in your organization are exposed to the most sensitive data types. You can then work with your internal teams to reduce that access as required. + +## Identity Inventory population process + +Data Security Posture performs the following tasks to populate the Identity Inventory: + + * Connects to your Identity and Access Management (IAM) system + +RSC supports the AWS, Entra ID, and Active Directory IAM systems. + + * Ingests IAM configurations + * Analyzes configurations to learn who can access what data + * Provides visibility around data access through the Identity Inventory + + *[ > ]: and then diff --git a/dspm_identity_inventory_details.md b/dspm_identity_inventory_details.md new file mode 100644 index 0000000000000000000000000000000000000000..928ad575b9f550a712ad770a0d999a6d6f6b4a78 --- /dev/null +++ b/dspm_identity_inventory_details.md @@ -0,0 +1,21 @@ +# Identity Inventory details + +Source: https://docs.rubrik.com/en-us/saas/dspm/identity_inventory_details.html + +--- + +# Identity Inventory details + +The Identity details page provides detailed and contextual information about an individual identity, such as a user, group, or role. + +Clicking a Data Security Posture identity displays its dedicated details page, organized into three informative tabs: + + * Members: Displays the members associated with the identities. Hovering over next to the identity displays the name and designation of the user along with an option to view further details. + +This tab is only available for a group. + + * Associated Identities: Displays any sub-identities further associated with the primary identity. + * Accessible Objects: Lists all objects that the identity can access. + +All three tabs display the accessible files, hits by sensitivity, and impacted data categories. Additionally, the Accessible Objects tab includes an Access Types column. This column indicates how users access the object, which can be direct or indirect. Indirect access typically results from a group role assignment. + *[ > ]: and then diff --git a/dspm_managing_allowed_hits.md b/dspm_managing_allowed_hits.md new file mode 100644 index 0000000000000000000000000000000000000000..6141acd3e0e3b3854dd0cd60fed0aa019dc576dd --- /dev/null +++ b/dspm_managing_allowed_hits.md @@ -0,0 +1,67 @@ +# Managing allowed hits + +Source: https://docs.rubrik.com/en-us/saas/dspm/managing_allowed_hits.html + +--- + +# Actions available for data security policies + +Actions available on the Data Security Policies page. + +The following actions are available for a data security policy. + +Action | Description +---|--- +Clicking Create Policy | Opens the Create Policy wizard for creating a new data security policy. +Turning on Show disabled policies | Displays data security policies that have been disabled. +Clicking in the policy row and then Edit Policy | Opens the Edit Policy wizard for creating a new data security policy. +Clicking and then Duplicate Policy | Duplicates the selected policy so that it can be reused as required.Because predefined policies are not editable, you can duplicate a predefined policy and edit it as required. +Clicking Disable Policy | Turns off the selected policy.All violations detected by the policy are then closed. You can also enable the policy at a later time.# Actions available for data security policies + +Actions available on the Data Security Policies page. The following actions are available for a data security policy. | Action | Description +---|--- +Clicking Create Policy | Opens the Create Policy wizard for creating a new data security policy. +Turning on Show disabled policies | Displays data security policies that have been disabled. +Clicking in the policy row and then Edit Policy | Opens the Edit Policy wizard for creating a new data security policy. +Clicking and then Duplicate Policy | Duplicates the selected policy so that it can be reused as required.Because predefined policies are not editable, you can duplicate a predefined policy and edit it as required. +Clicking Disable Policy | Turns off the selected policy.All violations detected by the policy are then closed. You can also enable the policy at a later time. +Clicking Delete Policy | Deletes the selected policy from the Data Security Policies page. All violations detected by the policy are then closed. +Using the Category, Severity, Policy Type, and Last Updated filters on the page | Sorts the data security policies on the page according to the applied filters. + +# Managing allowed hits + +Manage allowed hits in Data Security Posture for current and future files. + +## About this task + +Allowed hits are hits that are allowed for current and future files. Allowed hits can be managed at the folder or file level. If detected in these locations, data types hits will not be displayed in the Object Inventory. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. On the navigation bar, click Objects. + +The Object Inventory page appears, displaying the protected objects and showing the breakdown of hits for each object. + + 4. Click an object to view details. + +The object details page appears, displaying the Overview tab that shows detailed information for the selected object. + + 5. Click Browse to manage allowed hits. + +To manage at the file level, click Files and then click the name of the required file. + + 6. Click Actions > Manage Allowed Hits for the file or folder. + +The Manage allowed hits dialog box opens, displaying the data categories, data types, and hits for the files in that folder. + + 7. Select the data types to allow hits for the selected files and click Save. + +## Results + +A message confirms that the selection is successful. Hits in the selected location are hidden by default for current and future files. + *[ > ]: and then diff --git a/dspm_object_inventory.md b/dspm_object_inventory.md new file mode 100644 index 0000000000000000000000000000000000000000..f45a4ba83462675cdfddd23d3ba5a9ab3a9324cd --- /dev/null +++ b/dspm_object_inventory.md @@ -0,0 +1,29 @@ +# Object inventory + +Source: https://docs.rubrik.com/en-us/saas/dspm/object_inventory.html + +--- + +# Object inventory + +The object inventory provides complete data and insights into the objects in your cloud information. The Object Inventory page provides an overview of the different objects and their type, the sensitive hit details, the impacted data categories, and active violations. + +Data Security Posture provides classification data in the Object Inventory page. You can view a breakdown of hits by sensitivity, data categories impacted, the active violations in those objects, classified by severity, relevant account information for cloud objects, and the location of these objects. You can also filter the information by the filters available on the page, including the following: + + * Object information such as the object type, account, data type, platform, and Rubrik cluster protecting the object. + +Account information is relevant for objects located on the cloud. + +For Microsoft 365 objects, RSC also provides document type information. This feature is available as part of the Rubrik DSPM license. + + * Classification information such as sensitivity of the hits, data categories impacted, and violation severity. + * Backup information such as whether the object has been backed up, the last scan of the object, when it was first seen, the creation date, and the last accessed time. + * Access information such as network access, users with access, exposure, and logging. + +You can complete the following actions in the Object Inventory page: + + * Using filters to sort the object information + * Searching by the object name in the search bar + * Selecting any historical point-in-time classification data using the snapshot picker and viewing the sensitive data classification at that time + + *[ > ]: and then diff --git a/dspm_object_sensitive_data_info.md b/dspm_object_sensitive_data_info.md new file mode 100644 index 0000000000000000000000000000000000000000..f4f9dcebfbb9301f4d5f39c518c5d99e7a4e7424 --- /dev/null +++ b/dspm_object_sensitive_data_info.md @@ -0,0 +1,31 @@ +# Sensitive data information + +Source: https://docs.rubrik.com/en-us/saas/dspm/object_sensitive_data_info.html + +--- + +# Sensitive data information + +The object details page in Data Security Posture provides information about the sensitive data in an object. + +Tab | Description +---|--- +Overview | Displays an overview of sensitive data in the object in the following widgets: + * Object Details provides information about the Rubrik cluster account, object type, provider, region the object is located, size of the object, when it was last accessed, when it was last classified, and its creation date.The Security Posture section in the widget also provides information about the exposed files in the object and their encryption, logging, backup, and network access. + * Active Violations provides a list of the violations detected, the date they were detected, their severity, and status. + * Data Categories shows the breakdown of data detected on this object in a pie chart, based on sensitivity of the hits and data category type.Clicking View All Files displays the Files tab for that object. + * Top 10 Sensitive Files shows the list of top ten sensitive files with their sensitive hits. Clicking View All displays the Files tab for that object. +Browse | Displays a list of folders in the object, with the hits by sensitivity and the data categories impacted. You can filter the information by sensitivity, data category, data types, and level of exposure. You can search within the folder for specific files by using complete file or folder names for the search. Clicking a folder displays its contents in the following tabs: + * Classification, which shows the hits sorted by sensitivity, data categories and data types impacted, MIP labels used, and a list of files sorted by sensitivity. + * Details, which shows the path, file or folder size, and access details for the file or folder. The folder size is the sum of all files with sensitive information under this path.The Security Posture section indicates the number of files exposed publicly, either within the organization, or with restricted internal exposure. +You can manage allowed hits or download a CSV file showing the sensitive hits in that folder from this tab. +FilesTables, when the object is a database | Displays the list of files in the object with the path, hits by sensitivity, and the data categories impacted. For Microsoft 365 objects, the document type is also provided.You can filter the information by sensitivity, data category, data types, and level of exposure. You can search for specific files by using complete file names for the search. Clicking a file displays its details in the following tabs: + * Classification, which shows the hits sorted by sensitivity, data categories and data types impacted, MIP labels used, and a list of files sorted by sensitivity.The File Structure section on this tab shows the internal structure of documents, such as CSV, JSON, or XML. + * Permissions, which shows the owner and permissions configured for the files in the folder.Configuring LDAP on the Rubrik cluster is required for Data Security Posture to provide the permissions information for the sensitive files. The Rubrik CDM User Guide provides more information on specifying credentials to communicate with an LDAP server. + * Activity, which shows user activity on that object. + * Details, which shows the path, file or folder size, and access details for the file or folder. The folder size is the sum of all files with sensitive information under this path. +You can manage allowed hits or download a CSV file showing the sensitive hits in that file from this tab. +Users This information is only available for Windows objects. | Displays the list of users with their specific User Principal Name (UPN), which is a login name for a user in Microsoft Active Directory, the list of sensitive hits on files accessed by the user, and list of files organized by sensitivity. + +You can download a CSV file with the hits in that object from all the tabs on the page. + *[ > ]: and then diff --git a/dspm_overview_dsp.md b/dspm_overview_dsp.md new file mode 100644 index 0000000000000000000000000000000000000000..96794a770f707eb5ef4d362eda441193067e780c --- /dev/null +++ b/dspm_overview_dsp.md @@ -0,0 +1,19 @@ +# Data Security Posture overview + +Source: https://docs.rubrik.com/en-us/saas/dspm/overview_dsp.html + +--- + +# Data Security Posture overview + +Using Data Security Posture, you can leverage extensive information about data living in your cloud, SaaS, and on-prem environments to easily prevent data breaches. Additionally, you can create effective data security guardrails, and meet compliance and regulatory needs. + +Data Security Posture provides a global, unified view of the data in your environment, where it lives, who can access it, and access activity. You can view where the data is stored, the sensitivity of the data, and how it is classified, such as whether it contains personally identifiable information or financial records. + +In addition, you can use Data Security Posture to discover and investigate data security risks of misplaced, overexposed, obsolete, or misconfigured data and remediate these issues by following object-specific remediation guidance. The Threats feature helps you effortlessly detect incidents as they occur so you can quickly contain active threats and minimize potential damage to your business. Data Security Posture continuously monitors, assesses, and improves an organization’s data security posture to provide the following benefits: + + * Autonomous and continuous discovery of all cloud-resident data, not just known or manually tagged assets. The platform uses multi-step contextual validation to identify and classify sensitive data residing in AWS, Microsoft Azure, Microsoft 365, and on-premises environments. + * Data Security Posture deployment without an agent or connectors, where production workloads are not impacted. You can easily enable Data Security Posture after purchasing the appropriate license. + * Complete and ongoing visibility using the Identity Inventory into which identities can access data in your environments, how much data they have access to, and how their access is changing over time. Using activity logging, Data Security Posture also provides information on the action those identities take on the data. + + *[ > ]: and then diff --git a/dspm_predefined_data_categories.md b/dspm_predefined_data_categories.md new file mode 100644 index 0000000000000000000000000000000000000000..fd231e7d958edb9551a9e497684497c48d6d7f82 --- /dev/null +++ b/dspm_predefined_data_categories.md @@ -0,0 +1,198 @@ +# Predefined data types + +Source: https://docs.rubrik.com/en-us/saas/dspm/predefined_data_categories.html + +--- + +# Predefined data types + +Predefined data types are used in predefined data categories. They are available in RSC for creating custom data categories to detect sensitive data. + +Data Type | Description | Data Category, Predefined data category (if any) | Sensitivity +---|---|---|--- +ABA Routing Number | A 9-digit code used in the US to identify a specific financial institution | Financial, US Financials | High +Advertising Identifier | A unique code that identifies a user's device for the purpose of targeted advertising | Digital | Medium +Amazon Auth Token | A temporary security credential used to authenticate API requests to AWS | Digital | Low +American Bankers CUSIP | A unique 9-digit alphanumeric code used to identify American and Canadian securities such as stocks and bonds | Financial, US Financials | Low +AU Bank Account Number | A unique number used to identify a specific bank account in Australia | Financial | High +AU BSB Code | Bank-State-Branch code, a 6-digit number used to identify individual bank branches in Australia | Financial | High +AU Medical Account Number | A unique number used to identify a medical record in an Australian healthcare system | Medical | High +AU Passport Number | A passport number of an Australian passport | Personal | High +Australia Driver's License Number | A unique number given to a driver's license in Australia | Personal | High +Australian Business Number | A unique 11-digit number used to identify a business by the Australian government | Business | Medium +Australian Company Number | A unique 9-digit number used to identify a company by the Australian Securities and Investments Commission (ASIC) | Business | Medium +Australian TFN | A unique identifier for an individual or organization used by Australian tax authorities | Personal | High +Auth0 Domain URL | A unique URL endpoint for an Auth0 tenant | Digital | Low +Auth0 OAuth Client ID | A unique identifier assigned to a registered application in Auth0 | Digital | Low +AWS Access Token | A security credential used to authenticate API requests to AWS | Digital | Low +AWS API key | A security credential used to authenticate API requests to AWS | Digital | Low +AWS Connection String | A configuration string used by applications to connect to AWS | Digital | Low +AWS Secret | A cryptographic key used for authentication to AWS | Digital | Low +Azure Client Secret | A cryptographic key used in conjunction with a client ID to authenticate to Azure through Active Directory | Digital | Low +Azure Connection String | A configuration string used by applications to connect to Azure | Digital | Low +Bank Account Number | A number used to identify a bank account | Financial, US Financials, CCPA | High +Belgium Driver's License Number | A unique number given to a driver's license in Belgium | Financial | High +Belgium National Number (BNN) | A unique number used to identify residents of Belgium | Personal | High +Belgium Passport Number | A passport number of a Belgian passport | Personal | High +Birth Date | The date of birth of an individual | Personal | Medium +Bitbucket Client ID | A unique identifier assigned to a registered application on Bitbucket | Digital | Low +Bitbucket Client Secret | Cryptographic key used to authenticate an application accessing Bitbucket | Digital | Low +Bitcoin Address | A unique identifier for a bitcoin wallet where bitcoins can be sent | Digital | Medium +Bitcoin Secret | A cryptographic key used to access and control bitcoin wallets | Digital | High +Blood Type | Blood type | Medical | High +Brazilian Boleto Number | A unique identifier used by boleto bancário, a popular Brazilian payment method, to process payments | Financial | High +California Driver's License Number | A unique number given to a driver's license in California | Personal, CCPA, US PII | High +California ZIP Code | A zip code from the state of California | Geographical | No risk +Canada Bank Account Number | A unique number used to identify a specific bank account in Canada | Financial | High +Canada Health Service Number | A unique number used to identify an individual to healthcare services in Canada | Medical | High +Canada Passport Number | A passport number of a Canadian passport | Personal | High +Canada Personal Health Identification Number (PHIN) | A unique number used to identify an individual to healthcare services in Canada | Medical | High +Canada SIN | A Canadian Social Insurance Number, used to identify Canadian citizens. Similar to an American Social Security Number | Personal | High +Canadian Routing Number | A 9-digit code used in Canada to identify a specific financial institution | Financial | High +CC Last Four | The last 4 digits of a credit card | Financial | No risk +City | The name of a city | Geographical | No risk +Client ID | A number used to identify a client, can vary between different businesses | Personal | No risk +CloudElements API Key | A unique string of characters used to authenticate a user or application to CloudElements | Digital | Low +CloudFlare API Key | A unique string of characters used to authenticate a user or application to Cloudflare | Digital | Low +CloudFlare API Token | A temporary credential used to authenticate to Cloudflare | Digital | Low +CloudFlare Certificate Key | A cryptographic key used in the authentication process to Cloudflare | Digital | Low +CloudImage API Key | A unique string of characters used to authenticate a user or application to Cloudimage | Digital | Low +CloudMersive API Key | A unique string of characters used to authenticate a user or application to Cloudmersive | Digital | Low +CloudPlan API Key | A unique string of characters used to authenticate a user or application to Cloudplan | Digital | Low +CloudSmith API Key | A unique string of characters used to authenticate a user or application to Cloudsmith | Digital | Low +Coinbase Access Token | A unique string of characters used to authenticate a user or application to Coinbase | Digital | Low +Country | A country | Geographical | No risk +Country Code | A short alphanumeric code used to represent a country | Geographical | No risk +County | A geographical subdivision of a country or state | Geographical | No risk +Credit Card | Credit card number | Financial, GLBA, US Financials, PCI-DSS | High +Credit Score | A score between 200 and 850 used by financial institutions to represent an individual's worthiness of receiving a loan | Financial | Low +Cryptographic Certificate | A cryptographic document used to prove ownership of a public cryptographic key | Digital | No risk +Current Procedural Terminology (HCPCS I) | A standardized code used to report medical, surgical, and diagnostic services | Medical | Medium +CVV | Card Verification Value, a 3- or 4-digit number associated with a credit card as an additional security measure, usually printed on the back of a credit card | Financial | High +Databricks API Token | A unique string of characters used to authenticate a user or application making API requests to Databricks | Digital | Low +Datadog Access Token | A unique string of characters used to authenticate a user or application to Datadog | Digital | Low +Device ID | A unique code that identifies a specific electronic device such as a smartphone or computer | Digital | Medium +Digital Certificate | A cryptographic document used to prove ownership of a public cryptographic key | Digital | High +Disability Status | A classification of an individual based on the presence of a physical or mental impairment that limits one or more major life activities, often used for accommodation | Medical | Medium +Drug Enforcement Agency Number | A unique identifier assigned by the American Drug Enforcement Agency (DEA) to a healthcare provider | Medical, US PII/Medical data | Low +Elastic API Key | A unique string of characters used to authenticate a user or application to Elastic | Digital | Low +Email Address | Email address | Personal | High +Ethereum Address | A unique identifier for an Ethereum wallet where Ethereum can be sent | Digital | Medium +Ethereum Contract Address | A unique identifier for an Ethereum smart contract | Digital | Medium +Ethereum Secret | A cryptographic key used to access and control Ethereum wallets | Digital | High +Ethnicity | The ethnicity of an individual | Personal | Medium +EU Country | A country in the European Union | Geographical | No risk +EU Country Code | A country code associated with a country in the European Union | Geographical | No risk +EU Email Address | An email address that is associated with a European domain | Personal | High +EU IBAN code | An International Bank Account Number associated with a bank account in the European Union | Financial | Medium +EU Nationality | A nationality that is associated with a country in the European Union | Personal | Medium +EU Phone Number | A phone number with a country code associated with a country in the European Union | Personal | High +EU Swift Code | A SWIFT code associated with a financial institution in the European Union | Financial | Medium +Expiration Date | The expiration date of a credit card | Financial | Medium +First Name | The first name of an individual | Personal | Medium +France Social Security Number | A French Social Security Number, used to identify Canadian citizens. Similar to an American Social Security Number | Personal | High +Full Address | A complete street address of a house or building | Geographical | No risk +Full Name | The full name of an individual | Personal | High +GCP API key | A unique string of characters used to authenticate a user or application to GCP | Digital | Low +GCP OAuth Refresh Token | A credential in GCP used to obtain new access tokens | Digital | Low +Gender | The gender of an individual | Personal | Medium +German Birth Date | The date of birth of a German national | Personal | Medium +German Credit Card | A credit card issued by a German credit institution | Financial | High +German Credit Card Holder | An individual that has ownership of a German Credit Card | Financial | High +German Phone Number | A phone number in Germany | Personal | High +German Tax Identification Number | A unique identifier used by individuals for tax purposes in Germany | Personal | High +Germany Driving License Number | A unique number given to a driver's license in Germany | Personal | High +Germany Identity Card Number | A unique alphanumerical code used to identify German citizens | Personal | High +Germany Passport Number | A passport number of a German passport | Personal | High +Git Token | A token for Git service | Digital | Low +GitHub OAuth Refresh Token | A credential in Github used to obtain new access tokens | Digital | Low +Gitlab Personal Access token | A unique string of characters used to authenticate a user or application to Gitlab | Digital | Low +Health Insurance Claim Number | Health Insurance Claim Number, a unique identifier for an insurance claim | Medical | Medium +IBAN | International bank account number, used to identify a bank account in a globally standardized way | Financial | High +IBM API Key | A unique string of characters used to authenticate a user or application to IBM | Digital | Low +ICD10 Code | International Classification of Diseases Code, version 10. A short numeric code for a disease used by businesses | Medical | Medium +ICD9 Code | International Classification of Diseases Code, version 9. A short numeric code for a disease used by businesses | Medical | Medium +IMEI | International Mobile Equipment Identity, a unique number for a mobile phone | Digital | High +IMSI | International Mobile Subscriber Identity, a unique number for a user of a cellular network | Digital | High +IPv4 | An IP address for IP version 4 | Digital | Medium +IPv4 with Port | An IP address for IP version 4, with a TCP/UDP port | Digital | Medium +IPv6 | An IP address for IP version 6 | Digital | Medium +Ireland Drivers License | A unique number given to a driver's license in Ireland | Personal | High +Ireland Passport Number | A passport number of an Irish passport | Personal | High +Ireland personal public service (PPS) number | A unique number used to identify Irish citizens | Personal | High +ISIN | A number used in the United Kingdom to identify securities such as stock, equities, and bonds | Financial | No risk +Israeli ID Number | A unique identification number used to identify an Israeli citizen | Personal | High +Israeli Vehicle ID Number | A vehicle identification number used by the Israeli motor vehicle office | Personal | Medium +ITIN | Individual Tax Identification Number, a tax processing number issued by the IRS | Personal, GLBA, US PII, CCPA | High +JSON Web Token | A compact token used to securely transmit information as a JSON object (JWT) | Digital | Low +Last Four SSN | The last four digits of an American Social Security Number | Personal | High +Last Name | The last name of an individual | Personal | Medium +Latitude | An imprecise latitude that is accurate to over 10 meters | Geographical | No risk +Launchdarkly Access Token | A unique string of characters used to authenticate a user or application to Launchdarkly | Digital | Low +Linux Passwd Entry | Information about a user account including username, user ID, group ID, and home directory saved in a Linux operating system | Digital | High +Linux Shadow Password Entry | Secure information about a user account including username, hashed password, password age, and account expiration saved in a Linux operating system | Digital | High +Loan ID | A unique number that identifies a specific loan in a financial institution's system | Financial | Medium +Longitude | An imprecise longitude that is accurate to over 10 meters | Geographical | No risk +MAC Address | A MAC address | Digital | Medium +Medicare ID | Medicare ID number, a unique identifier for a person using medicare | Medical | High +National Health Service Number | A unique identifier for an individual used by the National Health Service of the United Kingdom | Medical, UK PII | High +Nationality | Nationality | Personal | Medium +NCCI Code | National Council on Compensation Insurance code used to classify a business | Medical | Low +NDC Code | A unique number used to identify a drug product by the American Federal Drug Administration (FDA) | Medical | Low +Netherlands Citizen's Service Number (BSN) | A unique number used to identify Dutch citizens | Personal | High +Netherlands Driver's License Number | A unique number given to a driver's license in Ireland | Personal | High +Netherlands Passport Number | A passport number of a German passport | Personal | High +Netherlands Tax Identification Number | A unique number used to identify Dutch citizens | Personal | High +Netherlands Value Added Tax Number | A unique identifier assigned to businesses in the Netherlands | Personal | High +Nicename | A human readable version of a name, often used in online platforms in place of standard usernames | Digital | Medium +OKTA API Domain | A URL endpoint on an Okta organization's API | Digital | Low +OKTA Key | A cryptographic key used to sign and verify Okta tokens | Digital | Low +Passport Number | Passport number | Personal, UK PII, US PII,CCPA | High +Password | Password | Digital | Medium +Patent Serial Number | A unique serial number used to identify a patent in the United States Patent and Trademark Office | Business | Low +Patient Date of Birth | The date of birth of an individual with regards to a patient in a healthcare institution | Medical | High +Patient Number | A number used to identify a patient in a healthcare institution | Medical | Low +Paypal Access Token | A unique string of characters used to authenticate a user or application to Paypal | Digital | Low +Paypal Payer ID | A unique number that identifies a Paypal user | Financial | High +Phone Number | Phone number | Personal | High +Physician Name | The name of a treating physician in a healthcare institution | Medical | High +PO Box | The number for a post office box | Geographical | Medium +Port | A TCP/UDP port | Digital | No risk +Precise Latitude | A precise latitude that is accurate to under 10 meters | Geographical | Medium +Precise Location | A precise geolocation represented by latitude and longitude and accurate to under 10 meters | Geographical | Medium +Precise Longitude | A precise longitude that is accurate to under 10 meters | Geographical | Medium +Private Key | An alphanumeric string used as a cryptographic key to decrypt data or create digital signatures | Digital | High +Procedure Code (HCPCS) | A standardized code that describes healthcare services, items, and procedures | Medical | Medium +Relationship info | Information regarding a relationship between two people, such as marital status | Personal | Medium +Social Security Number (SSN) | An American Social Security Number, used to identify US citizens | Personal, US PII, CCPA | High +Splunk API Key | A unique string of characters used to authenticate a user or application to Splunk | Digital | Low +Street | The name of a street | Geographical | No risk +Stripe Fingerprint | A unique identifier generated by Stripe for a credit card | Financial | High +Student ID | An ID number for a student given by a school or university | Personal | High +Sweden Driving License Number | A unique number given to a driver's license in Sweden | Personal | High +Sweden National ID | A unique number used to identify Swedish citizens | Personal | High +Sweden Passport Number | A passport number of a Swedish passport | Personal | High +Sweden Tax Identification Number | A unique number used to identify Swedish citizens for tax purposes | Personal | High +Swift Code | A unique code made up of numbers and digits used to identify a bank. Also known as a business identifier code (BIC) | Financial | Medium +Synthetic Credit Card | A credit card number that is fake or synthetic and used for demonstrative purposes | Financial | High +Synthetic SSN | An American Social Security Number that is fake or synthetic and used for demonstrative purposes | Personal | No risk +TMSI | Temporary Mobile Subscriber Identity, a non-unique number used to temporarily identify a user of a cellular network | Digital | Medium +TravisCI API Key | A unique string of characters used to authenticate a user or application to TravisCI | Digital | Low +Twitter ID | A unique ID that identifies a Twitter (X) user | Personal | Medium +UDI-DI | Unique Device Identifier, a number used to identify a medical device type | Medical | No risk +UK Driver's License Number | A unique number given to a driver's license in the UK | Personal, UK PII | High +UK Electoral Roll Number | A unique number assigned to individuals in the UK on the electoral register | Personal | High +UK National Insurance Number | A unique number used to identify a citizen of the United Kingdom, equivalent to an American Social Security Number | Personal, UK PII | High +UK Unique Taxpayer Reference (UTR) | A unique number used to identify a taxpayer in the United Kingdom | Financial, UK PII | High +UK Zip Code | A zip code used in the United Kingdom | Geographical | No risk +Universal Loan Identifier | A unique alphanumeric code assigned to a loan application by financial institutions in the USA | Financial | Medium +U.S. Employer Identification Number (EIN) | A unique 9-digit number used to identify businesses for tax purposes by the American Internal Revenue Service (IRS) | Business, US PII | Medium +US Healthcare National Provider Identifier (NPI) | A unique 10-digit number used to identify a healthcare provider in the USA | Medical, US PII | High +US Phone Number | An American phone number | Personal | High +US State | One of the states in the United States of America | Geographical | No risk +USCIS | Green Card Number, a unique identifier found on an American Permanent Resident Card (Green Card) and used to identify a permanent resident of the USA | Personal | High +User ID | An identification string used to identify a user in a system or service | Personal | Low +Username | Username | Digital | Medium +Vehicle ID Number | A unique code that identifies a motor vehicle | Personal, US PII | Medium +ZIP Code | A zip code used in the USA | Geographical | Restricted + *[ > ]: and then diff --git a/dspm_previewing_data_samples.md b/dspm_previewing_data_samples.md new file mode 100644 index 0000000000000000000000000000000000000000..2e427e910a2761608634f467fdf203d9a4c5bbed --- /dev/null +++ b/dspm_previewing_data_samples.md @@ -0,0 +1,39 @@ +# Previewing data samples + +Source: https://docs.rubrik.com/en-us/saas/dspm/previewing_data_samples.html + +--- + +# Previewing data samples + +Preview data samples to verify Data Discovery and Classification accuracy. + +## About this task + +You can preview a subset of masked data samples to validate that data is accurately classified. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. On the navigation bar, click Objects. + +The Object Inventory page appears. + + 4. Click the name of an object. + +The object details page appears with the details for that object. + + 5. Click Files in the main section on the page. + +The page displays all files within the object, including hits by sensitivity and data categories. + + 6. Click Actions > View Data Samples in the Actions for the file. + +## Results + +The Data Samples dialog box appears, displaying a preview of random data classification samples from the selected file. + *[ > ]: and then diff --git a/dspm_rbac_dsp.md b/dspm_rbac_dsp.md new file mode 100644 index 0000000000000000000000000000000000000000..256f13728b2a20fd34cc983bfb1be8d6fe3cfb94 --- /dev/null +++ b/dspm_rbac_dsp.md @@ -0,0 +1,49 @@ +# RBAC for Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/rbac_dsp.html + +--- + +# RBAC for Data Security Posture + +Information about the privileges required for Data Security Posture access. These privileges help in configuring Role-Based Access Control for users. + +RSC provides two roles for assigning RBAC privileges for Data Security Posture: the Data Security Posture administrator and Data Security Posture analyst roles. + +The following table describes the privileges for the roles in Data Security Posture. Role | Privileges +---|--- +Data Security Posture administrator | Has the following capabilities: + + * Full privileges in Data Security Posture + * Account management privileges to install or delete accounts + * Privileges to edit policies and take remedial actions + + +Data Security Posture analyst | Has the following capabilities: + + * Privileges to manage classification + * No privileges to manage policies or take remedial actions + * No privileges to edit policies or take remedial actions + + + +The following table describes the privileges for Data Security Posture. Privileges | Capability provided +---|--- +View Data Security Posture results | Viewing Data Security Posture results when the appropriate license has been purchased. +Manage data classification settings | Creating and editing data categories and data types, updating the sensitivity, and the data categories assignment. +Download classification results | Downloading the classification results as a CSV file across the object inventory. +Manage security violations | Opening tickets and changing ticket status. +Manage security policies | + + * Creating, editing, duplicating, disabling, and deleting custom policies + * Duplicating and disabling predefined policies + + +Take remediation action | Taking remediation action in Data Security Posture, such as assigning Microsoft Information Protection ( MIP) labels. +View data access governance | Viewing Threats and Identity Inventory information in Data Security Posture. +View data threat alerts | Viewing Threats information in Data Security Posture. + +Note: + +Both data access governance and threat information privileges have a global permissions scope, enabling any user with access to view all objects within the environment. This global scope does not apply to other Data Security Posture privileges. + *[ > ]: and then diff --git a/dspm_single_identity_details.md b/dspm_single_identity_details.md new file mode 100644 index 0000000000000000000000000000000000000000..8092b5a6a8a1b01c9ae093fb04660a618ee73f89 --- /dev/null +++ b/dspm_single_identity_details.md @@ -0,0 +1,21 @@ +# Single identity details + +Source: https://docs.rubrik.com/en-us/saas/dspm/single_identity_details.html + +--- + +# Single identity details + +You can view detailed information about a single identity, the assigned groups, and assigned radius in Data Security Posture. + +You can access the single identity details window by clicking a single identity. The single identity details window provides visibility into identity access to sensitive data. + +Tab | Description +---|--- +Overview | Provides identity details in the following sections: + * Identity Details: Shows the name, type, and the groups and users assigned to this identity. + * Blast Radius: Shows the impact of the identity access to sensitive data. This impact is indicated by the data hits by sensitivity, data type, and account. + * Access Graph: Illustrates the access path to sensitive data for the identity. +Assigned Groups | Provides information on the roles assigned to group members. +Assigned Users | Provides information on the users assigned to groups and the data they can access. + *[ > ]: and then diff --git a/dspm_supported_file_types.md b/dspm_supported_file_types.md new file mode 100644 index 0000000000000000000000000000000000000000..822999e4566ecc0d61418721f5f4fe8964a29e55 --- /dev/null +++ b/dspm_supported_file_types.md @@ -0,0 +1,57 @@ +# Supported file types + +Source: https://docs.rubrik.com/en-us/saas/dspm/supported_file_types.html + +--- + +# Supported file types + +Information about the file types that Data Security Posture analyzes and performs deep inspection for classifying the data discovered. + +The following table lists and describes the types of file and storage formats Data Security Posture can analyze to detect sensitive data. + +For each supported file type, the table also lists the applicable file name extensions. File or storage type | Description | Files +---|---|--- +Structured and semi-structured text | Tabular and object-based file formats store information not necessarily consisting of a specific structure, such as delimiter-separated value files and JavaScript Object Notation files. | + * .json + * .ndjson + * .jsonl + * .csv + * .tsv + * .psv + * .xml + * .xls + * .xlsx +Documents, presentations, and technical drawings | Adobe Portable Document Format files, Microsoft Word documents, and more. | + * .pdf + * .doc + * .docx + * .pptx or any other plain text file with or without an extension +Big data | Apache Avro object containers and Apache Parquet files | .avro, .parquet +Unstructured text | Unstructured files, non-binary text files | .vtt, .txt, .md, or any other plain text file without an extension. +Email messages | Electronic mail files whose contents comply with the requirements specified by an IETF RFC for electronic mail messages, such as RFC 2822. | .eml, .msg +Backup | Files used for backing up a database so that its contents can be restored in the event of data loss. | + * .sql + * .mysql_dump + * .phpmyadmin + * .bson +Images | Image file formats. Optical Character Recognition (OCR) technology is used to recognize text within a digital image. | + * .jpg + * .jpeg + * .png + * .tif + * .tiff +Logging | File extensions used for logging and telemetries | .log +Code and developer secret | Files used to store application code, scripts, and development secrets. | + * .htm + * .html + * .js + * .groovy + * .ps1 + * .sh + * .ppk + * .pfx + * .key + * .pem +Medical imaging files | Digital Imaging and Communications in Medicine (DICOM®) is a software integration standard used in medical imaging. It's a set of specifications and interfaces to provide a diagnostically accurate representation of medical imaging data and includes tools to transfer, store, and display the information. | .dcm. For more information, contact Rubrik support. + *[ > ]: and then diff --git a/dspm_threat_alert_information.md b/dspm_threat_alert_information.md new file mode 100644 index 0000000000000000000000000000000000000000..a60c56266bb1eb7ecce6c49930696532c3e91be3 --- /dev/null +++ b/dspm_threat_alert_information.md @@ -0,0 +1,21 @@ +# Threat information in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/dspm/threat_alert_information.html + +--- + +# Threat information in Data Security Posture + +The Threats feature in Data Security Posture identifies anomalies and malicious indicators that impact sensitive data and alerts you about data exfiltration, suspicious third-party access, insider threats, accidental data leaks, data misuse, and other threats. + +By using the Threats feature in Data Security Posture, you can detect threats in real time and access contextual information to help you quickly contain them. + +The following table describes the different elements of the Data Threat Alerts dashboard. Dashboard element | Description +---|--- +Active alerts by severity | A pie chart displaying the number of active alerts broken down by severity as critical, high, medium, and low +Alerts detected per day | A bar chart displaying the number of alerts detected per day over the past 30 days +Activity event processing | A bar chart displaying the number of log events that have been analyzed on assets across your organization +Active and closed threats | A list of threats displayed in the Active and Closed tabs. You can sort the threats by severity, first event, last event, alert, actor, actor type, and account + +Clicking Manage SIEM integrations displays the SIEM Integrations page where you can add any of the available integrations. + *[ > ]: and then diff --git a/dspm_viewing_data_security_policies.md b/dspm_viewing_data_security_policies.md new file mode 100644 index 0000000000000000000000000000000000000000..c0a322663562eb9e02734af62b6425295e63d603 --- /dev/null +++ b/dspm_viewing_data_security_policies.md @@ -0,0 +1,23 @@ +# Viewing data security policies + +Source: https://docs.rubrik.com/en-us/saas/dspm/viewing_data_security_policies.html + +--- + +# Viewing data security policies + +View the details of the data security policies for your organization. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. Click PoliciesData Security Policies. + +## Results + +The Data Security Polices page appears with the list of policies and their severity, policy type, last updated time and open violations. + *[ > ]: and then diff --git a/dspm_viewing_object_inventory.md b/dspm_viewing_object_inventory.md new file mode 100644 index 0000000000000000000000000000000000000000..e15674b28b6330859b85bbf653221807bef4aaa4 --- /dev/null +++ b/dspm_viewing_object_inventory.md @@ -0,0 +1,28 @@ +# Viewing the object inventory + +Source: https://docs.rubrik.com/en-us/saas/dspm/viewing_object_inventory.html + +--- + +# Viewing the object inventory + +View the object inventory in Data Security Posture to understand the sensitive hits, data categories impacted, and active violations for the object. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. On the navigation bar, click Objects. + 4. **Optional:** Click the name of an object. + +The object details page appears with the details for that object. + +## Results + +The Object Inventory page displays the protected objects and showing the breakdown of hits for each object. + +To filter further, search by the object name in the search bar or select any historical point-in-time classification data using the snapshot picker. + *[ > ]: and then diff --git a/dspm_violation_remediation.md b/dspm_violation_remediation.md new file mode 100644 index 0000000000000000000000000000000000000000..5a79968a53f7348e2f48a6b306dea79d8c015c5f --- /dev/null +++ b/dspm_violation_remediation.md @@ -0,0 +1,19 @@ +# Violation remediation + +Source: https://docs.rubrik.com/en-us/saas/dspm/violation_remediation.html + +--- + +Identity Inventory# Violation remediation + +Remediate a violation from the single violation details window. + +Remediate violations to help ensure that your environment is compliant and secure. Depending on the violation, one or more of the following actions is available as a remediation option: + + * Downloading a file with the paths on which sharing links are configured. + * Fixing public and organization exposure on Microsoft 365 SharePoint and OneDrive objects. This removes all sharing links causing the violation on this object. + * Creating a ticket to fix the violation. + * Downloading a remediation log for a violation. + * Downloading a violation file log that lists all impacted files in a CSV file. + * Assigning Microsoft Information Protection (MIP) labels to Microsoft 365 SharePoint and OneDrive objects + *[ > ]: and then diff --git a/dspm_violation_remediation_2.md b/dspm_violation_remediation_2.md new file mode 100644 index 0000000000000000000000000000000000000000..d97a4599e39c321fa0b0af4ff66f149293a6abcf --- /dev/null +++ b/dspm_violation_remediation_2.md @@ -0,0 +1,19 @@ +# Violation remediation + +Source: https://docs.rubrik.com/en-us/saas/dspm/violation_remediation_2.html + +--- + +# Violation remediation + +Remediate a violation from the single violation details window. + +Remediate violations to help ensure that your environment is compliant and secure. Depending on the violation, one or more of the following actions is available as a remediation option: + + * Downloading a file with the paths on which sharing links are configured. + * Fixing public and organization exposure on Microsoft 365 SharePoint and OneDrive objects. This removes all sharing links causing the violation on this object. + * Creating a ticket to fix the violation. + * Downloading a remediation log for a violation. + * Downloading a violation file log that lists all impacted files in a CSV file. + * Assigning Microsoft Information Protection (MIP) labels to Microsoft 365 SharePoint and OneDrive objects + *[ > ]: and then diff --git a/dspm_violation_tracking_management.md b/dspm_violation_tracking_management.md new file mode 100644 index 0000000000000000000000000000000000000000..a4acb3be245aef8d3bfd742889a689ecc604ebde --- /dev/null +++ b/dspm_violation_tracking_management.md @@ -0,0 +1,25 @@ +# Violation tracking and management + +Source: https://docs.rubrik.com/en-us/saas/dspm/violation_tracking_management.html + +--- + +# Violation tracking and management + +Manage and track violations from the violations details page. + +Data Security Posture detects violations at the object level and provides information on the severity, category, and data at risk by sensitivity. By clicking a violation, you can access the violations details page, which includes filters to understand the risk. You can also manage the violation status on this page. Clicking a single violation here displays the dedicated single violation page where you can view information about the data found on the object that is at risk, and options for remediating the violation on the object. + +A violation can have one of the following statuses. + +Open + The violation has been created and the status remains unchanged. +In Progress + An action has been taken on a violation through Data Security Posture, automatically updating its status. You can also manually change the status to In Progress to track what is being worked on. +Dismissed + A user has dismissed the violation, ensuring that no further violations of the same policy occur on the same object. +Remediated + Rubrik has marked the in-progress violation as remediated when it no longer detects it in a subsequent scan. +Closed + Rubrik has marked the open violations as closed when the policy conditions are no longer met. For example, the violating object or file has been deleted or the violating identity is no longer observed. + *[ > ]: and then diff --git a/dspm_violation_tracking_management_2.md b/dspm_violation_tracking_management_2.md new file mode 100644 index 0000000000000000000000000000000000000000..3a158102967206b0dd5ab06093cd5015b78093a6 --- /dev/null +++ b/dspm_violation_tracking_management_2.md @@ -0,0 +1,25 @@ +# Violation tracking and management + +Source: https://docs.rubrik.com/en-us/saas/dspm/violation_tracking_management_2.html + +--- + +# Violation tracking and management + +Manage and track violations from the violations details page. + +Data Security Posture detects violations at the object level and provides information on the severity, category, and data at risk by sensitivity. By clicking a violation, you can access the violations details page, which includes filters to understand the risk. You can also manage the violation status on this page. Clicking a single violation here displays the dedicated single violation page where you can view information about the data found on the object that is at risk, and options for remediating the violation on the object. + +A violation can have one of the following statuses. + +Open + The violation has been created and the status remains unchanged. +In Progress + An action has been taken on a violation through Data Security Posture, automatically updating its status. You can also manually change the status to In Progress to track what is being worked on. +Dismissed + A user has dismissed the violation, ensuring that no further violations of the same policy occur on the same object. +Remediated + Rubrik has marked the in-progress violation as remediated when it no longer detects it in a subsequent scan. +Closed + Rubrik has marked the open violations as closed when the policy conditions are no longer met. For example, the violating object or file has been deleted or the violating identity is no longer observed. + *[ > ]: and then diff --git a/envoy_organization_networks.md b/envoy_organization_networks.md new file mode 100644 index 0000000000000000000000000000000000000000..2c7a4d5c1c9d9809792b53b9205904820c7d81e4 --- /dev/null +++ b/envoy_organization_networks.md @@ -0,0 +1,49 @@ +# Organization networks + +Source: https://docs.rubrik.com/en-us/saas/envoy/organization_networks.html + +--- + +# Organization networks + +An organization network provides a secure tunnel for point-to-point communication with organization resources. An organization network also provides secure connectivity when NAT is used between a network segment and a shared Rubrik cluster that is not directly routable. + +An organization network provides a secure connection for resources located in an isolated network that require connectivity to a Rubrik cluster using Rubrik Envoy. Each organization network uses Envoy to connect a tenant organization to the Rubrik cluster, to enable protection of workloads located in those tenant organizations. + +Features of organization networks include the following: + + * Organization networks are part of a tenant organization. + +A tenant organization can contain one or more organization networks. An organization network can, however, only be part of a specific tenant organization. + + * An organization network is only required when using Envoy. + +An organization network must be created to provide connectivity to a tenant organization using Envoy. When Rubrik Envoy is not used, workloads in the tenant organizations must connect directly to the Rubrik cluster. + + * While a tenant organization may connect to multiple Rubrik clusters and a Rubrik cluster may connect to multiple tenant organizations, an organization network provides secure connectivity between a specific tenant organization and a Rubrik cluster. + +Requirements for enabling organization networks include the following: + + * Organization networks feature enabled + * Rubrik CDM 8.1.3-p5 or later, but not Rubrik CDM 8.1.4. + * RSC registered with the Rubrik cluster + * A minimum of 2 vCPU, 4 GB of memory, and a 30 GB hard drive for Envoy + +The workflow process to enable multitenancy using Envoy requires performing the following steps: + + * Creating a tenant organization + * Creating the organization network corresponding to the tenant organization + * Deploying Envoy on the network where it can directly reach tenant organization hosts + * Setting Rubrik CDM NAT addresses if applicable + * Registering the Envoy virtual appliance + +You can optionally check the validity of the certificate displayed during Envoy registration in the Rubrik CLI with the web certificate downloaded directly from the Rubrik cluster. + +For additional security, Rubrik strongly recommends a comparison of the web certificates. The Rubrik CDM User Guide contains information about this process. + + * Completing additional steps for configuring multitenancy such as configuration steps for RBAC, host registration, SLA Domain configuration, and so on. + +Existing Rubrik CDM tenant organizations must be switched to RSC. The process does not support switching existing Envoy virtual appliances or registering them with RSC. + +For Rubrik CDM versions 9.0 and later, legacy Rubrik CDM organizations can still be present. However, legacy Rubrik CDM organizations are no longer qualified or supported for use with or without Envoy. + *[ > ]: and then diff --git a/envoy_reqs_configuring_specific_workloads_envoy.md b/envoy_reqs_configuring_specific_workloads_envoy.md new file mode 100644 index 0000000000000000000000000000000000000000..fe690eeee218d671d58cdad87d73f5989570c4f9 --- /dev/null +++ b/envoy_reqs_configuring_specific_workloads_envoy.md @@ -0,0 +1,43 @@ +# Requirements for configuring specific workloads to use Envoy + +Source: https://docs.rubrik.com/en-us/saas/envoy/reqs_configuring_specific_workloads_envoy.html + +--- + +# Requirements for configuring specific workloads to use Envoy + +vSphere virtual machines, filesets, SQL Server databases, and Oracle databases have additional requirements for using Rubrik Envoy and connecting to the organization network. + +The following table describes the requirements for protecting vSphere virtual machines, Filesets, SQL Server databases, and Oracle databases and using the Rubrik Envoy virtual appliance after the prerequisites are met. + +Workload | Requirements +---|--- +vSphere virtual machines | + + * Rubrik Backup Service installed on the target hosts. This is not required for vSphere virtual machines if the vCenter Server does not belong to the tenant organization. + * Workload protection is configured as described in [Adding a VMware Cloud vCenter Server](../saas/vmc_adding_a_vmc_vcenter_server.html "Protect the virtual machines of a vCenter Server hosted in VMware Cloud by adding the vCenter Server to a Rubrik Cloud Cluster."). + +When workload protection is initiated, the data transfer automatically uses the Envoy virtual appliance. +Filesets | + + * Rubrik Backup Service installed on the target hosts. + * The Allow users to create and manage objects permission is selected when configuring Self-Service privilege for the tenant organization. + * Workload protection is configured as described in [Protecting a host fileset](../saas/fs_protecting_a_host_fileset.html "Create a host fileset by pairing a fileset with a host. Assign an SLA Domain to the host fileset to protect the data in the host fileset."). The host must be connected. + * When workload protection is initiated, the data transfer automatically uses the Envoy virtual appliance. + + +SQL Server databases | + + * Rubrik Backup Service installed on the target hosts. + * A host is added as described in [Adding a Microsoft SQL Server database host](../saas/mssql_adding_sql_server_db_host.html "Add a Windows Server host with Microsoft SQL Server databases to the Rubrik cluster to begin managing and protecting Microsoft SQL Server databases.") + * SQL Server databases protection is configured using one of the methods as described in [Protecting databases through a parent object](../saas/mssql_protecting_dbs_through_parent_obj.html "Assign an SLA Domain to a Windows Server host, Microsoft SQL Server instance, or individual databases to protect Microsoft SQL Server databases. Derived assignments from a host or instance allow uniform management and protection of database groups.") or [Protecting individual Microsoft SQL Server databases](../saas/mssql_protecting_individual_dbs.html "To provide data management and protection for an individual Microsoft SQL Server database, assign that database to an SLA Domain."). + +When workload protection is initiated, the data transfer automatically uses the Rubrik Envoy virtual appliance. +Oracle databases | + + * Rubrik Backup Service installed on the target hosts. + * You can add a host as described in[Adding a fileset host](../saas/fs_adding_a_fileset_host.html "To begin managing and protecting filesets on a host, add the host to a Rubrik cluster."). + * You can configure Oracle Databases protection as described here [Protecting Oracle databases](../oracle/rbk_protecting_oracle_databases.html "Choose a data protection policy for the discovered Oracle databases."). + +When workload protection is initiated, the data transfer will automatically utilize the Envoy virtual appliance. + *[ > ]: and then diff --git a/gcp_common_gcp_protection_terms.md b/gcp_common_gcp_protection_terms.md new file mode 100644 index 0000000000000000000000000000000000000000..f4b25e496e64c207fbd6a7838ebe282945c8703a --- /dev/null +++ b/gcp_common_gcp_protection_terms.md @@ -0,0 +1,41 @@ +# Common GCP protection terms + +Source: https://docs.rubrik.com/en-us/saas/gcp/common_gcp_protection_terms.html + +--- + +# Common GCP protection terms + +It is important to understand some common terms when protecting GCP workloads with RSC. + +By familiarizing yourself with common protection terms, you can better understand and navigate the steps and components involved in protecting GCP workloads. + +Term | Definition +---|--- +Google Cloud Platform (GCP) | A subsidiary of Google that provides on-demand cloud computing platforms and APIs to individuals, companies, and governments, billed on a metered pay-as-you-go basis. +GCP region | A distinct geographical area independent from other regions in terms of location, power, cooling, and water supply, for high availability and fault tolerance. Each region consists of one or more zones to prevent failures and reduce latency. +GCP zone | A deployment area within a GCP region.Zones store data and ensure redundancy and reliability. Each zone is identified by a name that combines a letter identifier with the name of the region. For example, zone a in the East Asia region is named asia-east1-a.Resources that reside in a zone, such as GCE instances or zonal persistent disks, are zonal resources. Other resources, such as static external IP addresses, are regional. Regional resources can be used by any resource in that region, regardless of zone, while zonal resources can only be used by other resources in the same zone. +GCP Organization | The root node of the GCP resource hierarchy, grouping all resources that belong to an organization.It provides central visibility and control over every resource within the organization. The Organization resource is the hierarchical ancestor of project resources and folders. After an Organization resource is created for a domain, all GCP projects created by members of the account domain will by default belong to this Organization. +GCP Folder | A grouping mechanism in the GCP resource hierarchy that isolates different GCP projects.You can consider a folder as sub-organizations within the Organization. You can use folders to model different legal entities, departments, and teams within a company. +GCP Project | The base-level organizing entity in the GCP resource hierarchy.Organizations and folders may contain multiple projects. You require a project to use GCP services. Through projects, you can create, enable, and use all GCP services, manage APIs, enable billing, add and remove collaborators, and manage permissions.Each project includes a unique project ID for identification, an automatically assigned project number, a mutable display name, the lifecycle state (ACTIVE or DELETE_REQUESTED), labels for filtering, and a creation timestamp.The customer-owned GCP project contains the resources protected by the cloud-native protection feature of RSC. RSC binds to a Cloud IAM Role in the customer-owned GCP project with a Cloud IAM service account from the same GCP project to make the API calls necessary to protect GCE instances and GCE disks. The snapshots that RSC takes continue to reside in the customer-owned GCP project, only metadata is stored in RSC. +GCP Project ID | A unique identifier for a GCP project.RSC requires a GCP Project ID to differentiate which project a resource, such as a GCE instance, belongs to. +GCP resource | Manageable items available through GCP, such as GCE instances, persistent disks, buckets, VPCs, IAM roles, security groups, and labels. +GCP workload | A GCP resource for which RSC can take a snapshot for data protection, such as a GCE instance and a persistent disk. +GCP Console | A graphical interface to manage compute, storage, and other GCP resources. +GCP Identity and Access Management (IAM) member | A GCP IAM member can be a Google account for end users, a service account for applications and virtual machines, a Google group, or a G Suite or Cloud Identity domain that can access a resource.The identity of a member is an email address associated with a user, service account, or Google group; or a domain name associated with G Suite or Cloud Identity domains. +IAM policy | The IAM policy binds one or more members to a role. When you want to define who (member) has what type of access (role) on a resource, you create a policy and attach it to the resource. +IAM role | A collection of permissions. Permissions determine which operations are allowed on a resource. When you grant a role to a member, you grant all the permissions that the role contains. +Service account | An account used by an application or compute workload, such as a GCE instance, rather than by a person. A service account is identified by its email address, which is unique to the account.Applications use service accounts to make authorized API requests by either authenticating as the service account itself or as Google Workspace or Cloud Identity users through domain-wide delegation. When an application authenticates as a service account, it can access all the resources that the service account is permitted to access. +Google Cloud Engine (GCE) instance | A virtual server running in GCP. The machine type dictates the CPU, RAM, and other performance characteristics of the instance. Instances can run the public images for Linux and Windows Server that Google provides as well as private custom images that a user can create or import from their existing systems.Instances run in a subnet within virtual networks known as Virtual Private Cloud (VPC) networks. Each subnet is associated with one region and multiple zones, thus each instance runs within a single zone in a single region. +GCE image | An image file in GCP that contains all the necessary information required to launch a GCE instance.When a GCP user launches an image through the GCP console or through the GCE API, they must specify the image ID that will be used for launch. +GCE disk or persistent disk | A block storage device that GCP users can attach to or detach from GCE instances.Each GCE disk is redundant within a zone and optionally across zones, but not across regions. Most GCE instances have at least one GCE disk, also known as the boot persistent disk, attached to them. They may also have additional data disks attached to them as well. To take backups of GCE disks, RSC calls the GCP APIs to create GCE snapshots of the disks. This means that these snapshots are visible and accessible in the GCP Console. +GCP Key Management Service (KMS) | A managed service that enables GCP users to create and control the keys used for cryptographic operations easily.This service is a highly available key generation, storage, management, and auditing solution allowing users to encrypt or digitally sign data in their applications or to control the encryption of data across GCP services. GCP creates and manages KMS keys, typically referred to as Default Keys, while users can create and manage their own keys, known as Customer Managed Keys (CMKs). +Source snapshot | A captured state of a GCE instance or persistent disk at a specific point in time, saved on the same physical storage system as the source instance or disk. This local snapshot ensures data consistency and allows for quick recovery or analysis of the instance or disk as it existed at that specific moment. +Relic | A GCE instance that you have deleted while there are still existing snapshots for the instance. These snapshots are retained according to the SLA Domain assigned to the instance at the time of deletion. You can delete on-demand snapshots as usual. +Rubrik-owned GCP Project | A GCP project that hosts the RSC instance. API calls to the customer-owned GCP project originate from this project. +SLA Domain | A Rubrik feature you configure to define policies for data protection, including snapshot frequency, retention duration, and archiving requirements. You can configure and apply these policies to workloads, ensuring consistent and automated data protection. +Exocompute | A Rubrik service that provides scalable and automated compute resources for running data operations, such as indexing, file recovery, and storage tiering. +File indexing | A data operation that catalogs and organizes the files stored in backups, making it easier for users to search for and retrieve specific files or folders. When a backup is taken, RSC indexes the files and their metadata, including file names, paths, sizes, and timestamps. This indexed information facilitates efficient search and recovery operations. +Infrastructure Manager | An interface within the GCP environment that facilitates the execution of Infrastructure-as-Code (IaC) templates, such as Terraform. In the RSC manual onboarding flow, Infrastructure Manager is used to execute the downloaded Terraform plan to provision IAM roles and bindings in your project. +Google Artifact Registry (GAR) | A fully managed Google Cloud service used to store, manage, and distribute software artifacts, including container images and language packages. The Rubrik Exocompute on GCP feature utilizes GAR to store necessary container images for running data operations on Google Kubernetes Engine (GKE) clusters. + *[ > ]: and then diff --git a/gcp_enabling_ad_gce_pd.md b/gcp_enabling_ad_gce_pd.md new file mode 100644 index 0000000000000000000000000000000000000000..96a7dc1874eccc49365e102e7496257440a6f716 --- /dev/null +++ b/gcp_enabling_ad_gce_pd.md @@ -0,0 +1,40 @@ +# Enabling Anomaly Detection for GCE instances and persistent disks + +Source: https://docs.rubrik.com/en-us/saas/gcp/enabling_ad_gce_pd.html + +--- + +# Enabling Anomaly Detection for GCE instances and persistent disks + +Enable Anomaly Detection for a GCP project to analyze behavior and content of the GCE instances and persistent disks within the GCP project. This will show details about incidents that might be unusual. Enabling Anomaly Detection for a GCP project helps protect the data in the GCE instances and persistent disks from ransomware attacks. + +## Before you begin + +Directly enable file indexing or assign an SLA Domain with an archival location for the GCP project to protect with Anomaly Detection. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +RSC supports Anomaly Detection for snapshots based on SLA Domains and on-demand snapshots. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Threat Analytics and select Cloud Accounts. + 4. Click GCP projects. + +The GCP projects page appears with a list of GCP projects. + + 5. Turn on Anomaly Detection for a GCP project. + +## Results + +RSC enables Anomaly Detection for GCP project. + +When Anomaly Detection detects an anomalous incident, it sends an event email with a severity level of either Warning or Critical to the specified email recipients. Incidents with a Warning status indicate low levels of detected encryption and those with a Critical status indicate high levels of detected encryption. + *[ > ]: and then diff --git a/gcp_exocompute_gcp.md b/gcp_exocompute_gcp.md new file mode 100644 index 0000000000000000000000000000000000000000..5c2ba1530bf7afc1fc5d0f3efc6cf640d6cb607b --- /dev/null +++ b/gcp_exocompute_gcp.md @@ -0,0 +1,33 @@ +# Exocompute on GCP + +Source: https://docs.rubrik.com/en-us/saas/gcp/exocompute_gcp.html + +--- + +# Exocompute on GCP + +With the Exocompute on GCP feature, RSC launches a Google Kubernetes Engine cluster to perform various operations to protect GCP workloads. RSC uses the Google Kubernetes Engine cluster to serve as a compute resource in your GCP project. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +The Exocompute on GCP feature of RSC uses a container-based framework and is designed to perform various data processing tasks in your GCP environment. By leveraging Google Kubernetes Engine (GKE), Exocompute manages compute resources to perform essential operations, such as file indexing, file recovery, and storage tiering. + +## Key operations of Exocompute + +Exocompute uses GKE to perform the following operations: + + * File indexing: When you enable the file search feature for a GCE instance or a persistent disk, each new backup of the instance or disk initiates a file indexing operation. + * File recovery: When you initiate a recovery operation for the files in the backup of a GCE instance or a persistent disk, RSC launches a GKE cluster to read the file data from the backup. + * GCP storage tiering: When a snapshot reaches the archival threshold specified in the SLA Domain, RSC launches a GKE cluster to tier the snapshot to the specified GCP project. + * Recovery from archived snapshots: When you initiate a restore or export operation using an archived snapshot, RSC launches a GKE cluster to restore or export the snapshot data from archival storage. + +## GKE integration + +Exocompute leverages GKE to launch and manage GKE clusters for orchestrating Exocompute nodes. A GKE cluster comprises two primary components: the GKE control plane and the GKE nodes registered with the control plane. The GKE control plane consists of control plane components that run the Kubernetes software, such as etcd and the Kubernetes API server. Google Cloud manages the control plane functionality, and the Kubernetes API is exposed through the GKE endpoint associated with the cluster. GKE nodes operate within your GCP project and connect to the control plane through the API server endpoint and a certificate. + +The roles and responsibilities of each component are as follows: + + * Control plane nodes: These nodes orchestrate the lifecycle of the GKE nodes, including launching, assigning tasks, and terminating them as required. The control plane ensures the coordination and management of the entire cluster but does not execute user-provided logic or tasks directly. + * Worker nodes: These nodes execute the core logic assigned by Exocompute, including tasks such as file search, file recovery, and GCP storage tiering. GKE nodes are deployed as a node pool with a minimum number of nodes defined during configuration. Depending on the load and workload requirements, additional GKE nodes may be automatically created or terminated. + + *[ > ]: and then diff --git a/gcp_gce_instances_persistent_disks.md b/gcp_gce_instances_persistent_disks.md new file mode 100644 index 0000000000000000000000000000000000000000..eae4a8435ffd9c44739a88415aa9aa74238fbb63 --- /dev/null +++ b/gcp_gce_instances_persistent_disks.md @@ -0,0 +1,12 @@ +# GCE instances and persistent disks + +Source: https://docs.rubrik.com/en-us/saas/gcp/gce_instances_persistent_disks.html + +--- + +# GCE instances and persistent disks + +After you set up protection for GCE instances and persistent disks, RSC takes automated snapshots of those instances and disks based on the policies configured in SLA Domains. You can also take on-demand snapshots and refresh GCP projects. + +After you have completed the protection setup for GCE instances and persistent disks, RSC starts taking automated snapshots of those instances and disks according to the data protection policies you have configured in the assigned SLA Domains. You can view detailed snapshot information on the Inventory page for GCP. Based on your requirements, you can take on-demand snapshots of your workloads, perform snapshot management tasks such as modifying retention policies and deleting snapshots, and refresh a GCP project on-demand to retrieve the latest metadata. + *[ > ]: and then diff --git a/gcp_gcp.md b/gcp_gcp.md new file mode 100644 index 0000000000000000000000000000000000000000..8ef8e4bde3a7683344b5f8b5a4b95db9108228ca --- /dev/null +++ b/gcp_gcp.md @@ -0,0 +1,21 @@ +# Google Cloud Platform workloads + +Source: https://docs.rubrik.com/en-us/saas/gcp/gcp.html + +--- + +# Google Cloud Platform workloads + +RSC protects the following types of Google Cloud Platform workloads: Google Compute Engine instances and persistent disks. + +As organizations expand their use of Google Cloud Platform (GCP), they encounter new complexities in protecting, managing, and securing their data. Complex deployments can be at greater risk of threats to data integrity and operational stability, putting businesses at risk of data breaches, accidental data loss, and ransomware attacks. The Shared Responsibility Model established by GCP makes it clear that, while GCP secures the infrastructure, the ultimate responsibility for application and data protection rests with the organization. + +Rubrik provides a streamlined, SaaS-based solution to these challenges with Rubrik Security Cloud (RSC). RSC secures and automates data protection processes for GCP workloads, making sure that data remains protected against accidental deletions, ransomware attacks, and other potential threats. With RSC, organizations can automate backup, archiving, and recovery across GCP projects and regions using SLA Domain policies that allow organizations to align data protection seamlessly with business requirements. + +Protecting GCP workloads with RSC involves an approach that makes sure that data is comprehensively and consistently protected across the cloud infrastructure of an organization. By breaking down the tasks into three main categories, Authorization, Configuration, and Protection, RSC simplifies the steps required to protect GCP workloads. Each category addresses specific aspects of data security, from granting secure access to applying global policies that enable comprehensive cyber resiliency. + +Task category | Description +---|--- +Authorization | For authorization, you grant RSC secure access to your GCP projects that need protection. You can achieve this through a GCP Identity and Access Management (IAM) role workflow that aligns with GCP security best practices. +Configuration | For configuration, you set up SLA Domains to protect GCP workloads automatically, according to your business objectives.Using SLA Domains, you can define and manage data protection policies uniformly across different regions. +Protection | For protection, you enforce data security by assigning SLA Domains to GCP workloads. If the situation arises, RSC provides quick recovery options for Google Compute Engine (GCE) instances and persistent disks, and individual files within or across regions. diff --git a/gcp_gcp_project_setup.md b/gcp_gcp_project_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..2d02a531461c53d4b5b4a440dbc3f8472bf314f7 --- /dev/null +++ b/gcp_gcp_project_setup.md @@ -0,0 +1,18 @@ +# GCP project setup + +Source: https://docs.rubrik.com/en-us/saas/gcp/gcp_project_setup.html + +--- + +# GCP project setup + +You can set up a GCP project by adding the project to RSC and start protecting your GCP workloads. + +Setting up a GCP project in RSC to protect your GCP workloads involves detailed planning. This process includes: + + * Referring to the recommendations from Rubrik for adding GCP projects. + * Learning about the permission categories and how to implement the least-permission model for enhanced security. + * Evaluating various options for adding a GCP project to ensure the choice aligns with your requirements. + +After the evaluation is complete, you can proceed with the setup by adding your GCP project to RSC. + *[ > ]: and then diff --git a/gcp_gcp_storage_tiering_setup.md b/gcp_gcp_storage_tiering_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..ba9f4cf4243250e4a08ad6e7e06d2081c894fdd0 --- /dev/null +++ b/gcp_gcp_storage_tiering_setup.md @@ -0,0 +1,26 @@ +# GCP storage tiering setup + +Source: https://docs.rubrik.com/en-us/saas/gcp/gcp_storage_tiering_setup.html + +--- + +# GCP storage tiering setup + +You can use GCP storage tiering to archive GCE instance or persistent disk snapshots that are older than a specified threshold to GCS storage classes. By archiving snapshots to these storage classes, you can optimize costs. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Industries in the public sector, such as financial services and healthcare, require snapshots to be retained for several years to meet regulatory and compliance requirements. GCP storage tiering enables cost optimization by archiving such snapshots to Google Cloud Storage (GCS) storage classes. + +Backups of certain workloads might need to be retained for an extended period, for example, more than a year. In such cases, you can leverage GCP storage tiering to optimize costs by archiving GCE instance or persistent disk snapshots to low-cost GCS storage classes such as Standard, Nearline, Coldline, and Archive. + +You can use GCP storage tiering to move all weekly, monthly, quarterly, or yearly backups with extended retentions of more than one year to the GCS storage classes to manage costs. + +## Tiered snapshots immutability + +RSC supports GCP immutability to protect the tiered snapshots against accidental deletion or malicious activity, such as ransomware attacks. RSC leverages the GCS Object Lock feature for immutable data, which locks the GCS object data with a Write-Once, Read-Many (WORM) lock for a specified interval. After the GCS Object Lock feature is set, you can read and create objects but cannot modify or delete objects until the retention period expires. The retention period for the snapshots is managed through the SLA Domains. For example, if you specify the retention period as five weeks in the SLA Domain, the snapshot stays in the immutable state for five weeks. + +Note: + +To archive snapshots of GCP workloads, you must first create a GCP archival location and link it to an SLA Domain. After you assign the SLA Domain to your GCP workloads, RSC takes snapshots according to the configured policies within that SLA Domain. RSC then sends these snapshots to the archival location linked to the SLA Domain. These archived snapshots are immutable by default, requiring no additional user action. + *[ > ]: and then diff --git a/gcp_gcp_workload_protection_setup.md b/gcp_gcp_workload_protection_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..0a1d12dece3f26b1a8ce280552f970196f3069cd --- /dev/null +++ b/gcp_gcp_workload_protection_setup.md @@ -0,0 +1,24 @@ +# GCP workloads protection setup + +Source: https://docs.rubrik.com/en-us/saas/gcp/gcp_workload_protection_setup.html + +--- + +# GCP workloads protection setup + +You can set up SLA Domains to apply data protection policies, ensuring automatic and hierarchical protection of GCP projects and individual GCP workloads, with granular control overriding higher-level assignments. + +In cloud data protection, ensuring that your GCP workloads are secure and recoverable is essential. Rubrik SLA Domains offer a structured way to apply data protection policies across various GCP workloads, ensuring consistent and reliable backup and recovery processes. An SLA Domain is a set of policies that defines the backup and recovery objectives for your data. These policies specify the frequency of snapshots, the retention period for these snapshots, and the archiving requirements. + +By assigning SLA Domains to GCP workloads, you ensure that your data protection strategies align with your organizational requirements and compliance standards. RSC enables hierarchy-based, automatic protection of GCP workloads. This automatic protection mechanism simplifies the protection of large numbers of workloads. + +After you add a GCP project to RSC, you can create one or more customized SLA Domains to begin protecting GCP workloads. Although RSC provides Gold, Silver, and Bronze SLA Domains, these defaults may not fully meet the specific requirements of your organization. Creating customized SLA Domains allows for precise control over snapshot frequency, retention periods, and archival policies, ensuring alignment with your organizational and compliance standards. After creation, you can assign these customized SLA Domains to different GCP entities. RSC then starts creating, archiving, and expiring snapshots to protect the relevant workloads based on the parameters defined in the assigned SLA Domain. + +The following table summarizes where you can assign an SLA Domain: + +Entity | Description +---|--- +GCP project | Assigning SLA Domain settings at the project level for managing protection policies for the associated workloads. +Individual GCP workload | Assigning SLA Domain settings to a specific GCE instance and persistent disk for granular control. +Label | Assigning SLA Domain settings to a label, which groups multiple GCE instances and persistent disks across GCP projects. + *[ > ]: and then diff --git a/gcp_gcp_workload_recovery.md b/gcp_gcp_workload_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..3acf9ef2074de23c025d41d46cceee544e8e5ff1 --- /dev/null +++ b/gcp_gcp_workload_recovery.md @@ -0,0 +1,19 @@ +# GCP workloads recovery + +Source: https://docs.rubrik.com/en-us/saas/gcp/gcp_workload_recovery.html + +--- + +# GCP workloads recovery + +After RSC takes snapshots of your GCE instances and persistent disks, you can recover the required instances and disks using these snapshots. + +After you complete the protection setup for your GCP workloads, RSC starts protecting your data by taking snapshots based on the configured policies in the assigned SLA Domains. You can recover the workloads from these snapshots using various recovery options based on your specific requirements. Rubrik recommends adding a GCP project based on the least privilege model, which involves selecting only the Basic permission category. When a recovery operation becomes necessary, you can then elevate the permissions for recovery purposes. + +Before recovering your GCE instances and persistent disks, it is important to do the following: + + * Learning about the privilege elevation option and how to assign a permission category for recovery. + * Familiarizing yourself with the various recovery options for GCE instances and persistent disks to ensure that your choice aligns with your recovery requirements. + * Performing file indexing if your recovery requirements include the ability to search and recover individual files and folders from the snapshots of GCE instances and persistent disks. + + *[ > ]: and then diff --git a/gcp_high_level_arch_gcp_protection.md b/gcp_high_level_arch_gcp_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..b4837f4fd13a335f3040a3695febc4bca7466826 --- /dev/null +++ b/gcp_high_level_arch_gcp_protection.md @@ -0,0 +1,12 @@ +# High-level architecture for GCP protection + +Source: https://docs.rubrik.com/en-us/saas/gcp/high_level_arch_gcp_protection.html + +--- + +# High-level architecture for GCP protection + +A high-level architectural overview of how RSC protects GCP workloads and RSC and GCP IAM roles provisioning process. + +Rubrik uses various architectural strategies and workflows to protect your GCP workloads. This includes explaining how cloud-native protection for your GCP workloads operates and how RSC communicates with your GCP project. + *[ > ]: and then diff --git a/gcp_key_features_gcp_protection.md b/gcp_key_features_gcp_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..528a1a5ba805bdca838b348b74948048364228f2 --- /dev/null +++ b/gcp_key_features_gcp_protection.md @@ -0,0 +1,45 @@ +# Key features for protecting GCP workloads + +Source: https://docs.rubrik.com/en-us/saas/gcp/key_features_gcp_protection.html + +--- + +# Key features for protecting GCP workloads + +RSC provides unified data management, automated global data protection, and various recovery options to protect your GCP workloads. + +The cloud-native protection that RSC provides for GCP workloads includes comprehensive features to streamline data management, enable quick recovery, and reduce costs. + +The key features of cloud-native protection for GCP workloads include: + + * Unified data management + * Automated global data protection through SLA Domains + * Storage tiering to archive data for reducing cloud storage costs + * Immutability of the archived data + * Various recovery options for GCP workloads within or across regions + +## Unified data management + +Feature | Description +---|--- +Rubrik Security Cloud | Provides a SaaS platform for hybrid and multicloud environments that does not require persistent resources in GCP projects. +Consolidated monitoring and reporting | Provides unified reporting to track SLA Domain assignment, protection and recovery activities, and SLA Domain policy compliance. + +## Automated global data protection with SLA Domains + +Feature | Description +---|--- +SLA Domains | Enforces data protection policies across workload types and GCP projects for simplified data protection management. +Project level protection | Automatically assigns SLA Domains to entire GCP projects and makes sure that GCE instances provisioned in the respective project, irrespective of the region, receive the required level of data protection without the need for individual assignments.You can override project-level SLA Domain assignments by using label-based assignment or by directly assigning SLA Domains to GCP workloads. +Label-based protection | Assigns SLA Domains to GCE instances and persistent disks when specific label keys or key-value pairs are found on a GCE instance and persistent disk in a GCP project. +Storage tiering | Sends the compressed GCE instance or persistent disk snapshots to a target Google Cloud Storage (GCS) bucket and makes sure that the backups are immutable.You can specify the target GCP project, select the source or specific region, and configure the associated encryption for that region. Additionally, you can select the GCS storage class of the destination GCS bucket, offering the possibility of reducing long-term protection costs. + +## Recovery options + +Recovery option | Description +---|--- +GCE instance export | Creates GCE instances from snapshots, with options to define instance details and security settings. +Persistent disk export | Creates encrypted persistent disks using snapshots, with options to define disk type, size, and more. +GCE instance restore | Rolls the currently running instance to the state captured in the selected snapshot. This process preserves the InstanceId, internal and external IP addresses, encryption scheme, and RDP/SSH key. +File-level recovery from a snapshot of GCE instances and persistent disks | Searches and downloads specific files or folders from the selected snapshots to a GCS bucket. + *[ > ]: and then diff --git a/gcp_planning_gcp_protection.md b/gcp_planning_gcp_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..e8ff107603a0add113e98e1b58759e434593dd2d --- /dev/null +++ b/gcp_planning_gcp_protection.md @@ -0,0 +1,14 @@ +# Planning for GCP protection + +Source: https://docs.rubrik.com/en-us/saas/gcp/planning_gcp_protection.html + +--- + +# Planning for GCP protection + +Before setting up a GCP project in RSC, you need to plan user and access management for designated RSC users. This planning also involves reviewing the permissions that RSC requires in your GCP environment to protect your GCP workloads. + +When planning GCP protection, it is important that you establish a clear framework for user and access management to ensure secure and efficient operations within your GCP environment. You can start by categorizing your RSC users based on their roles and responsibilities and by assigning appropriate privileges through roles to limit access according to the principle of least privilege. + +Additionally, it is important that you review the specific permissions that RSC requires to protect your GCP workloads. Understanding these permissions helps explain why they are needed. This ensures clarity on the operations that protect your GCP workloads. + *[ > ]: and then diff --git a/gql_accessing_api_playground.md b/gql_accessing_api_playground.md new file mode 100644 index 0000000000000000000000000000000000000000..d9f83692610c8a5bcada9d3a2f1d8aa852817827 --- /dev/null +++ b/gql_accessing_api_playground.md @@ -0,0 +1,41 @@ +# Accessing API Playground + +Source: https://docs.rubrik.com/en-us/saas/gql/accessing_api_playground.html + +--- + +# Accessing API Playground + +Access API Playground available in your RSC domain by authenticating to RSC using your account credentials. With access to API Playground, you can explore the Rubrik GraphQL schema and perform data security operations using GraphQL queries and mutations. + +## About this task + +You can access API Playground through the RSC Settings menu or directly through a web browser. You can also use the global search in RSC to search for API Playground. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click API Playground. + +The API Playground page appears. + + 4. Click Open API Playground. + +The URL of the API Playground page is in the following format: + + https://rsc_domain_url/playground/ + +Where, rsc_domain_url is the IPv4 address or resolvable hostname of your RSC domain. + +Using the preceding URL for your RSC domain, you can directly open API Playground in a web browser. + +API Playground opens in a new browser tab. + +## Results + +API Playground is available for you to run GraphQL queries and mutations on your RSC data. + *[ > ]: and then diff --git a/gql_api_playground.md b/gql_api_playground.md new file mode 100644 index 0000000000000000000000000000000000000000..b7b60e860b605dd57ceee9c37636782a2d933f6c --- /dev/null +++ b/gql_api_playground.md @@ -0,0 +1,20 @@ +# API Playground + +Source: https://docs.rubrik.com/en-us/saas/gql/api_playground.html + +--- + +# API Playground + +API Playground is a development environment integrated with Rubrik Security Cloud that you can use to run various GraphQL API operations on the data managed in real time by RSC. + +API Playground is an integrated development environment (IDE) that you can use to browse, explore, and run GraphQL APIs offered by Rubrik Security Cloud (RSC). The IDE also provides reference to the latest Rubrik GraphQL API documentation. Running GraphQL queries and mutations in API Playground validates the GraphQL operations so that you can confirm that your queries or mutations will achieve the expected result when included in automation scripts. + +After logging in to API Playground with your RSC user account credentials, you can choose to run GraphQL queries and mutations either as yourself or with a service account. The level of access you have for running the GraphQL queries and mutations depends on the RBAC roles assigned to your user account or to the service account you are using. For enhanced security, API Playground does not persist the service account access credentials. + +Warning: + +If not used cautiously, the GraphQL mutations that you run in API Playground can result in data loss because they affect the data managed in real time by RSC. + +In addition to using the API Playground, you can also use the PowerShell SDK for RSC to enable seamless automation and management of various operations within RSC. You can download the SDK from the [PowerShell Gallery](https://www.powershellgallery.com/packages/RubrikSecurityCloud) or from the [Rubrikinc GitHub repository](https://github.com/rubrikinc/rubrik-powershell-sdk). + *[ > ]: and then diff --git a/gql_api_playground_2.md b/gql_api_playground_2.md new file mode 100644 index 0000000000000000000000000000000000000000..1e51cb3458f33c3a91dce06547c17ca64a4a6135 --- /dev/null +++ b/gql_api_playground_2.md @@ -0,0 +1,19 @@ +# API Playground + +Source: https://docs.rubrik.com/en-us/saas/gql/api_playground_2.html + +--- + +# API Playground + +API Playground is a development environment integrated with Rubrik Security Cloud that you can use to run various GraphQL API operations on the data managed in real time by RSC. + +API Playground is an integrated development environment (IDE) that you can use to browse, explore, and run GraphQL APIs offered by Rubrik Security Cloud (RSC). The IDE also provides reference to the latest Rubrik GraphQL API documentation. Running GraphQL queries and mutations in API Playground validates the GraphQL operations so that you can confirm that your queries or mutations will achieve the expected result when included in automation scripts. + +After logging in to API Playground with your RSC user account credentials, you can choose to run GraphQL queries and mutations either as yourself or with a service account. The level of access you have for running the GraphQL queries and mutations depends on the RBAC roles assigned to your user account or to the service account you are using. For enhanced security, API Playground does not persist the service account access credentials. + +Warning: + +If not used cautiously, the GraphQL mutations that you run in API Playground can result in data loss because they affect the data managed in real time by RSC. + +In addition to using the API Playground, you can also use the PowerShell SDK for RSC to enable seamless automation and management of various operations within RSC. You can download the SDK from the [PowerShell Gallery](https://www.powershellgallery.com/packages/RubrikSecurityCloud) or from the [Rubrikinc GitHub repository](https://github.com/rubrikinc/rubrik-powershell-sdk). diff --git a/gql_api_playground_ui.md b/gql_api_playground_ui.md new file mode 100644 index 0000000000000000000000000000000000000000..d477b10e1109849e0b02c9c6ce866956876b8e91 --- /dev/null +++ b/gql_api_playground_ui.md @@ -0,0 +1,34 @@ +# API Playground user interface + +Source: https://docs.rubrik.com/en-us/saas/gql/api_playground_ui.html + +--- + +# API Playground user interface + +The API Playground user interface in RSC uses the GraphiQL integrated development environment framework to run Rubrik GraphQL operations. + +API Playground leverages the powerful user interface of the GraphiQL integrated development environment (IDE). Using the API Playground user interface, you can refer to the latest Rubrik GraphQL API documentation. The interface also provides an editor, which you can use to compose your queries and mutations, and a results area, where you can see the result of the API operation. + +The following table describes the icons available on the user interface and the associated functionality. The Icon column refers to the icons using the text that appears when you hover over each icon. + +Icon | Description +---|--- +Show Documentation Explorer | + + * Displays the Rubrik GraphQL documentation derived from the latest schema reference. + * Provides a search option to search for specific queries and mutations. + + +Show History | Displays a list of GraphQL operations run using the API Playground user interface in the current browser session. +Re-fetch GraphQL Schema | Refreshes the documentation with the latest Rubrik GraphQL schema reference, on demand. +Open short keys dialog | Displays a list of keyboard shortcuts for frequently performed actions on the editor. +Open settings dialog | Displays additional settings for the web page. +Execute query | Runs the GraphQL query or mutation that is entered in the editor. +Prettify query | Formats the content of the editor. +Merge fragments into query | Merges fragments with the main query for ease of understanding and readability. +Copy query | Copies the editor content to the clipboard. +Add tab | Adds a tab to the editor. + +For more details about the GraphiQL IDE, refer to the official GraphiQL IDE documentation. + *[ > ]: and then diff --git a/gql_sa_session_non_persistence_api_playground.md b/gql_sa_session_non_persistence_api_playground.md new file mode 100644 index 0000000000000000000000000000000000000000..7d109fdb9ce95a95052afafa742bdbaa601d8e94 --- /dev/null +++ b/gql_sa_session_non_persistence_api_playground.md @@ -0,0 +1,22 @@ +# Non-persistence of service account sessions on API Playground + +Source: https://docs.rubrik.com/en-us/saas/gql/sa_session_non_persistence_api_playground.html + +--- + +# Non-persistence of service account sessions on API Playground + +When you use a service account to run GraphQL API operations in API Playground, for security reasons, API Playground does not persist the service account credentials and renders them invalid when the service account is not in use. + +To run Rubrik GraphQL queries and mutations using service account credentials, the API Playground obtains an access token, which is valid for 24 hours. To maintain the security of your RSC domain, API Playground does not save the service account credentials or the access token in the browser session. + +The following actions render the service account access token invalid and unusable for further requests: + + * Ending the service account session using the End Testing option on the API Playground user interface + * Refreshing the API Playground web page + * Navigating forward or backward in the browser + * Closing the browser tab + * Remaining inactive on the API Playground web page for more than 15 minutes + +When the service account access token is rendered invalid, you can continue to use API Playground with the user account that you previously used to log in to API Playground. + *[ > ]: and then diff --git a/gql_using_sa_to_run_gql.md b/gql_using_sa_to_run_gql.md new file mode 100644 index 0000000000000000000000000000000000000000..7680cac384c79074f12f24c4872f683e3f5d122f --- /dev/null +++ b/gql_using_sa_to_run_gql.md @@ -0,0 +1,45 @@ +# Using a service account to run GraphQL APIs + +Source: https://docs.rubrik.com/en-us/saas/gql/using_sa_to_run_gql.html + +--- + +# Using a service account to run GraphQL APIs + +In API Playground, to test and validate the use of a service account in automation scripts, use a service account to run GraphQL queries and mutations. + +## Before you begin + +Add a service account with the required RBAC roles to run the GraphQL queries and mutations, as described in [Adding a service account](../saas/adding_a_service_account.html "Add a service account in RSC to generate client credentials and enable client-side applications to authenticate to RSC."). + +## Procedure + + 1. In a web browser, open API Playground. + +Open https://rsc_domain_url/playground/. + +Where, rsc_domain_url is the IPv4 address or resolvable hostname of your RSC domain. + +When a valid user session does not exist in the browser, the RSC login page appears. + + 2. Log in to RSC. + +The API Playground web page appears. + + 3. Click Test with Service Account. + 4. Enter the Client ID and Client Secret. + +The Client ID and Client Secret identify the service account you want to use to run the GraphQL APIs. + + 5. Click Authenticate. + +RSC authenticates the service account credentials, using which you can test the GraphQL APIs on behalf of the service account. + + 6. **Optional:** Click End Testing. + +API Playground ends the service account session and invalidates the service account access token for further use, but you can continue to run GraphQL API operations with the user account that you used previously to log in to RSC. + +## Results + +You can use API Playground to test GraphQL APIs on behalf of a service account. + *[ > ]: and then diff --git a/identity_resilience_identity_resilience.md b/identity_resilience_identity_resilience.md new file mode 100644 index 0000000000000000000000000000000000000000..77067f440b579796de28b1eaea60284e2c4307ee --- /dev/null +++ b/identity_resilience_identity_resilience.md @@ -0,0 +1,17 @@ +# Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/identity_resilience.html + +--- + +# Identity Resilience + +Rubrik Identity Resilience secures, monitors, and recovers the Identity Providers. + +Identity Resilience in Rubrik Security Cloud (RSC) offers protection services for identities in hybrid environments and safeguards the identity infrastructure in an organization. Identities, both human and non-human, are the most common entry points for cyberattacks, and any form of compromise in the identity infrastructure can cripple the ability of an organization to recover from a breach. + +Identity Resilience comprises security and recovery of identities in your hybrid identity infrastructure. Identity Resilience requires purchasing the Rubrik Identity Resilience License. + +Identity Resilience provides extensive capabilities, including protection, active risk identification, and robust remediation. It simplifies managing complexities in hybrid identity environments and addresses the increasing instances of cyberattacks, thereby minimizing the risks of identity compromise and data breaches. Additionally, it offers real-time monitoring to detect critical changes with Active Directory (AD), including modifications to privileged group membership and Group Policy Objects (GPOs). This enables immediate awareness of crucial security events. + +Identity Resilience provides automated, clean-room recovery, enabling swift restoration of compromised identities, and minimizes downtime. It also proactively mitigates risks by identifying risky privilege escalations and problematic access combinations. When combined with Data Security Posture Management (DSPM), Identity Resilience provides a holistic view of both data and identity, significantly strengthening the overall data security posture. diff --git a/identity_resilience_ir_activity_log.md b/identity_resilience_ir_activity_log.md new file mode 100644 index 0000000000000000000000000000000000000000..6e05cc41727ec81bd8a074df680225f5af90f610 --- /dev/null +++ b/identity_resilience_ir_activity_log.md @@ -0,0 +1,47 @@ +# Activity log in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_activity_log.html + +--- + +# Activity log in Identity Resilience + +The Rubrik Identity Resilience provides a comprehensive, immutable, and actionable audit log of all changes within an Identity Provider, such as Active Directory. + +The activity log feature in Identity Resilience provides detailed chronological logs of actions performed by identities, including pre- and post-change values. RSC supports logging activities only for Active Directory (AD) Identity Provider (IdP). + +## Immutable audit logs + +The audit log feature delivers a comprehensive, chronological audit log that details all actions on AD objects. It detects real-time changes and provides details of the events, including the actor who performed the action, the time the action took place, and after values of the change. This rich context addresses the gap in native event logs, which often miss the specific settings and modified values. + +## Actor identification + +RSC monitors and logs changes made to critical AD objects using its own monitoring capabilities. However, to identify the actor responsible for detected actions, you must enable Windows activity logging. While correlating the actor, RSC displays the actor as Identifying. After detecting the actor, RSC displays the actor details who performed the action. When RSC cannot identify the actor, it displays the actor as Unidentified. The actor identification is attempted for 24 hours before concluding that the actor cannot be identified. + +Note: + +For attribute modifications such as lastlogontimestamp performed by AD, RSC displays the actor as System. + +## Support matrix for activity log + +The following table lists the support matrix for different types of objects, IdPs, and whether objects support actor identification. Object | IdP | Activity logging | Actor identification +---|---|---|--- +User | AD | Supported | Supported +Group | AD | Supported | Supported +Service account | AD | Supported | Supported +GPO | AD | Supported | Not supported + +## Activity types + +RSC monitors and logs the following activity types: Activity type | Description +---|--- +Creation | Records the addition of a new object to the AD. Supported objects are Users, Groups, and Computers. +Deletion | Records the removal of an existing object from the AD. +Attribute Change | Tracks a change to properties of an object, such as display name, phone number, or manager. +Membership Change | Monitors modifications to the membership of an object in a group or Organizational Unit (OU). +ACL Change | Monitors a modification to the Access Control List (ACL) of an object, altering which identities have access to it and their level of permission. +GPO Settings Change | Audits a change to the settings within a GPO or a change to where that GPO is linked. + +Note: + +RSC does not track sign-in and authentication events. diff --git a/identity_resilience_ir_activity_log_filters.md b/identity_resilience_ir_activity_log_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..1836b9d77b8de566e1f60f1b12810485e7c3495b --- /dev/null +++ b/identity_resilience_ir_activity_log_filters.md @@ -0,0 +1,44 @@ +# Activity log filters + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_activity_log_filters.html + +--- + +# Activity log filters + +RSC provides filters for all the activity logs in your hybrid identity environments based on various criteria. + +The following table describes the filtering options to narrow down the activity logs and focus on specific areas of concern. Filter | Description +---|--- +Time Range | Filters activity logs during a specific time range. You can choose from the following options: + + * Past 24 hours + * Past 7 days + * Past 30 days + * Past 12 months + * Custom + + +Action Type | Filters activity logs based on the type of action performed in the identity system: + + * Creation + * Deletion + * Attribute Change + * Membership Change + * ACL Change + * GPO Settings Change + +You can select one or more action types to filter the activity logs. +Actor | Filters activity logs of a specific actor. You can select from the list or you can enter the actor name in the Search Actor field to search for a specific actor.You can select one or more actors to filter activity logs. +Target Entity | Filters the activity logs of a specific target entity. You can select from the list or you can enter the target entity name in the Search Target Entity field to search for a specific target entity. +Target Entity Type | Filters the activity logs based on a specific target entity type. Supported entity types: + + * Users + * Groups + * Service Accounts + * GPOs + +You can select one or more target entity types to filter the activity logs. +Source | Filters the activity logs of a specific domain to which the actor belongs. You can select from the list or you can enter the source name in the Search Source field to view activity logs of a specific source. +Source DC | Filters the activity logs of a specific domain controller. This filter helps in further granular search of activity logs from a specific source domain controller. + *[ > ]: and then diff --git a/identity_resilience_ir_adding_idp.md b/identity_resilience_ir_adding_idp.md new file mode 100644 index 0000000000000000000000000000000000000000..cf0c76d39f6654de06f82770cd548eb52c38e025 --- /dev/null +++ b/identity_resilience_ir_adding_idp.md @@ -0,0 +1,43 @@ +# Adding an Identity Provider + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_adding_idp.html + +--- + +# Adding an Identity Provider + +Add your first Identity Provider to RSC to start protecting the identities in your hybrid identity environment. + +## Before you begin + +Adding an Identity Provider (IdP) requires administrator privileges. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Welcome to the Identity App page appears. + + 3. Click Get Started. + +The Add Your First Identity Provider page appears. + + 4. Click Add Identity Provider. + +The Add an Identity Provider wizard appears. + + 5. Select an Identity Provider and click Next. + * Microsoft Entra ID + * Microsoft Active Directory + 6. For Microsoft Entra ID, configure a cloud account with or without OAuth. + +The Adding Microsoft Entra ID with OAuth and Adding Microsoft Entra ID without OAuth topics describe the procedure for configuring a cloud account for Entra ID. + + 7. For Microsoft Active Directory, add a domain controller to the Rubrik cluster. + +The Adding an AD domain controller topic describes the procedure for adding a domain controller as a Windows host to a Rubrik cluster. + +## Results + +You have added your first Identity Provider to RSC. RSC discovers the identity data and displays it on the Identity Resilience Inventory page. diff --git a/identity_resilience_ir_alerts.md b/identity_resilience_ir_alerts.md new file mode 100644 index 0000000000000000000000000000000000000000..78d38005584506a2f212022a56a695857ba7ce8a --- /dev/null +++ b/identity_resilience_ir_alerts.md @@ -0,0 +1,35 @@ +# Alerts in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_alerts.html + +--- + +# Alerts in Identity Resilience + +The Alerts feature within Rubrik Identity Resilience provides real-time, live tracking of critical events and suspicious activities detected within your Active Directory environment. + +Important: + +The system resource utilization could impact performance, and Rubrik cannot be held responsible for any resulting effects. + +The Alerts page in Rubrik Identity Resilience helps IT administrators to monitor, investigate, and manage suspicious or disruptive activities detected within your identity environment. It provides immediate visibility into these activities, enabling rapid response and mitigation to protect your critical identity systems. + +The Alerts page is fundamental to Identity Resilience as it offers real-time monitoring capability for critical Active Directory (AD) changes, irrespective of traditional event log collection, enabling customers to: + + * Identify malicious or disruptive activities: Pinpoint potentially malicious or disruptive activities and respond to them before serious impact occurs. + * Gain granular visibility: Access a clear audit trail of significant identity-related changes, whether malicious or benign. + +RSC generates alerts for specific, high-impact scenarios, focusing on key areas of identity risk: + +Identity risk | Scenario +---|--- +Privilege group membership changes | + + * User or group addition into a privileged group: RSC triggers alerts when a user account is added to a privileged AD group. This flags potential privilege escalation, a common step in attack chains. + * User or group removal from a privileged group: RSC also raises alerts if a user is unexpectedly removed from a privileged group. This could indicate malicious activity, such as an attacker trying to hide tracks, or unauthorized de-provisioning. + + +Group Policy Object (GPO) modifications | Changes to GPOs: Any alteration to a GPO initiates an alert. GPOs are fundamental to AD security and configuration, and unauthorized changes can have widespread implications, making their modification a critical event to monitor. + +You can filter alerts using the Status, Time Range, and Alert Type filters that RSC provides. + *[ > ]: and then diff --git a/identity_resilience_ir_benefits.md b/identity_resilience_ir_benefits.md new file mode 100644 index 0000000000000000000000000000000000000000..ad06cc33deebbbe44f1b5d3f657bfbe014e120d4 --- /dev/null +++ b/identity_resilience_ir_benefits.md @@ -0,0 +1,21 @@ +# Identity Resilience benefits + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_benefits.html + +--- + +# Identity Resilience benefits + +Rubrik Identity Resilience offers faster recovery from identity-based attacks, reduces risk by identifying security gaps, supports scalable recovery across environments, and integrates identity and data protection for comprehensive security. This aids in global compliance and ransomware resilience. + +The benefits of Rubrik Identity Resilience include: + + * Faster recovery: Reduces recovery time from identity-based attacks, which is critical for business continuity. + * Reduced risk: Proactively identifies and mitigates identity security posture gaps, lowering breach impact and likelihood. + * Rapid detection: Detects critical changes to Active Directory (AD) infrastructure in real time, enabling rapid response and limiting their impact. + * Alternate setup recovery: Facilitates secure, isolated recovery of compromised AD identity services to a separate environment, which can help reduce the risk of re-infection after a cyberattack. + * Holistic security: Integrates identity and data protection for a unified approach to cyber resilience. + * Compliance support: Helps organizations meet stringent regulatory compliance requirements for recovery of critical systems. + * Ransomware resilience: Acts as a critical component in ransomware recovery strategies by ensuring a clean, immutable source for restoring identity services, preventing attackers from hindering recovery. + * Global impact: Protects millions of identities worldwide, aligning with industry needs. + diff --git a/identity_resilience_ir_changing_policy_violation_status.md b/identity_resilience_ir_changing_policy_violation_status.md new file mode 100644 index 0000000000000000000000000000000000000000..3a9fd37ed9f42384ab78aff108b86f08e544d419 --- /dev/null +++ b/identity_resilience_ir_changing_policy_violation_status.md @@ -0,0 +1,41 @@ +# Changing policy violation status + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_changing_policy_violation_status.html + +--- + +# Changing policy violation status + +Change the status of a policy to manage the violation investigation and response. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Violations. + +The Violations page appears, displaying a list of policies that have active violations. + + 4. Click for a policy and select Investigate Violations. + +You can also click the name of the policy to view the identities that violate the selected policy. + +A list of identities or domains and the violations associated with them appears. + + 5. Select an identity and click Change Status. + +Option| Description +---|--- +Open | Select this option when the violation is not remediated and you want to investigate the violation. +In Progress | Select this option when the violation is in the process of being remediated. +Dismissed | Select this option when the violation does not require any action. + +You can select multiple identities and also search for a specific identity using the Search by identity display name field. + +## Results + +You have changed the violation status for the selected identities. + *[ > ]: and then diff --git a/identity_resilience_ir_configure_actor_identification.md b/identity_resilience_ir_configure_actor_identification.md new file mode 100644 index 0000000000000000000000000000000000000000..3759ee5d16c3dfa2828b32a1d10a85b484eaf34e --- /dev/null +++ b/identity_resilience_ir_configure_actor_identification.md @@ -0,0 +1,21 @@ +# Configure actor identification + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_configure_actor_identification.html + +--- + +# Configure actor identification + +You can enable activity logs for actor identification by setting up some specific requirements. + +To configure actor identification, you must meet the following requirements: + + * Setting up System Access Control List (SACL) to audit all modification events on the Active Directory (AD) domain. + * Setting up a Group Policy Object (GPO) policy to enable audit logs for Directory Service Changes. + * Adding the Rubrik Backup Service (RBS) logon user to the Event Log Readers group to collect the logs. + +Note: + +These privileges should already be available for the LocalSystem and DomainAdmin accounts. + + *[ > ]: and then diff --git a/identity_resilience_ir_creating_servicenow_ticket_violations.md b/identity_resilience_ir_creating_servicenow_ticket_violations.md new file mode 100644 index 0000000000000000000000000000000000000000..84b7862f55c9b027c908baf6681eb8c74c615f8b --- /dev/null +++ b/identity_resilience_ir_creating_servicenow_ticket_violations.md @@ -0,0 +1,48 @@ +# Creating a ServiceNow ticket for violations + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_creating_servicenow_ticket_violations.html + +--- + +# Creating a ServiceNow ticket for violations + +Create a ServiceNow ticket to track and remediate the policy violations for an identity. + +## Before you begin + +You must integrate ServiceNow with RSC as described in [Connecting a ServiceNow instance](../saas/connecting_servicenow_instance.html "To enable ServiceNow ticket creation for Data Security Posture directly from RSC, connect a ServiceNow instance to RSC."). + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Violations. + +The Violations page appears, displaying a list of policies that have active violations. + + 4. Click for a policy and select Investigate Violations. + +You can also click the name of the policy to view the identities that violate the selected policy. + +A list of identities or domains and the violations associated with the identity appears. + + 5. Hover over the identity and click View Details. + +A page appears displaying an overview of the selected policy violation, including details of the breached policy, the affected identity or IdP, and recommended remediation steps. + + 6. Click Remediate and select Create Ticket. + +The Create Ticket option is not enabled if a ticket is already created for this policy violation. + +The Create a Ticket dialog box appears and displays the ticket title and description. + + 7. **Optional:** In Comments, add any additional comments you want to note. + 8. Click Create. + +## Results + +You have created a ServiceNow ticket to track and remediate the selected policy violation for an identity. + *[ > ]: and then diff --git a/identity_resilience_ir_dashboard.md b/identity_resilience_ir_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..fcf5ab8e2d0db369b12ed20115afe06b99f4653e --- /dev/null +++ b/identity_resilience_ir_dashboard.md @@ -0,0 +1,37 @@ +# Identity Resilience dashboard + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_dashboard.html + +--- + +# Identity Resilience dashboard + +The Identity Resilience dashboard provides a unified overview of identity-related policy violations, security alerts, and the protection status of hybrid identity environments. + +Users with the Rubrik Identity Resilience License can access the Identity Resilience dashboard. The dashboard provides a comprehensive view of policy violations, identity insights, protection overview, and alerts associated with identities in the hybrid identity environments. + +Users with a DSPM license can view detailed information and analysis of why a data security or compliance violation is indicated. + +The following table describes the different elements in the Identity Resilience dashboard. Dashboard element | Description +---|--- +Active Violations | Displays the total number of active policy violations detected within the identity environment. It provides a quick severity breakdown: Critical, High, Medium, and Low. This severity breakdown uses a donut chart, allowing administrators to prioritize remediation efforts based on the risk level. +Violations by Category | Categorizes and quantifies policy violations across different aspects of identity security. Identity Resilience displays the following categories: + + * IdP Configurations + * Identity Hygiene + * Identity Privileges + * Authentication Settings + +The categories help you understand where the policy violations are occurring within your identity infrastructure. It helps administrators understand the specific areas of their identity security posture that require attention, allowing for more targeted remediation efforts. +Summary of All Violations | Presents a trend graph illustrating the number of violations detected each day, over a selected time period.You can view the violation summary for the past 7 days, past 30 days, or past 12 months.You can also hover over the specific severities in the widget to observe specific severities of violations reported over time. +Alerts | Provides a summary of security alerts related to identity resilience. You can filter this information for the past 7 days, past 30 days, or past 12 months.This shows the number of Open Alerts and In-Progress Alerts and includes a trend line graph of Alerts Reported over time. This offers real-time insight into the volume and status of detected critical changes to Active Directory, specifically Group Policy Object (GPO) changes and privileged group membership changes, requiring attention from security teams. +Identity Insights | Offers a high-level view of key identity risk metrics. It quantifies the number of At risk, Privileged, and Highly sensitive identities, indicating potential attack targets. It also distinguishes between Human identities and Non-human identities, providing a breakdown of the types of identities being monitored and their associated risks.You can filter to view identities for a specific IdP. +Protection Overview | Summarizes the current protection status of your hybrid identity environments. For AD, this displays the number of forests and domains RSC protects. + + * For an AD forest to be reported as protected, every domain within that forest must have at least one domain controller that has successfully established a connection to the Rubrik cluster through RBS and an SLA Domain must be assigned. + * For an AD domain to be reported as protected, it must have at least one domain controller that has successfully established a connection to the Rubrik cluster through RBS and an SLA Domain must be assigned. + +For Entra ID, it shows the proportion of tenants that have an SLA Domain assigned. This widget provides a quick confirmation of how many domains, forests, or tenants of your identity infrastructure RSC protects. +Data at Risk by Sensitivity | Summarizes the current severity, category, and data at risk by sensitivity. By clicking View Data Access in Detail , you can view filters to understand the risk.Note: The Data at Risk by Sensitivity element is available as part of the Rubrik DSPM license. + +All the elements in the Identity Resilience dashboard are interactive. You can click the elements to go to the associated page in the Identity Resilience application. diff --git a/identity_resilience_ir_disabling_policy.md b/identity_resilience_ir_disabling_policy.md new file mode 100644 index 0000000000000000000000000000000000000000..3821e365bd1594ac1d351102d0e5f15a22a9e6bd --- /dev/null +++ b/identity_resilience_ir_disabling_policy.md @@ -0,0 +1,31 @@ +# Disabling a policy in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_disabling_policy.html + +--- + +# Disabling a policy in Identity Resilience + +Disable a predefined policy to stop evaluating the policy and prevent the generation of new violations. Disabling a policy closes the violations associated with the policy. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Policies. + +The Policies page appears displaying a list of predefined Rubrik policies. + + 4. Click for a policy and select Disable Policy. + +The Disable Policy confirmation dialog box appears. + + 5. Click Disable. + +## Results + +The selected policy is no longer enabled. + *[ > ]: and then diff --git a/identity_resilience_ir_enabling_policy.md b/identity_resilience_ir_enabling_policy.md new file mode 100644 index 0000000000000000000000000000000000000000..276ba86d10e0a53b65c0e83a25cee415050a10a4 --- /dev/null +++ b/identity_resilience_ir_enabling_policy.md @@ -0,0 +1,31 @@ +# Enabling a disabled policy in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_enabling_policy.html + +--- + +# Enabling a disabled policy in Identity Resilience + +Enable a disabled policy to identify violations associated with that policy. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Policies. + +The Policies page appears displaying a list of predefined Rubrik policies. + + 4. Turn on Show disabled policies. + +The policies page refreshes to display the disabled policies along with the policies that are already enabled. + + 5. Click for a disabled policy and select Enable Policy. + +## Results + +The selected policy is enabled. + *[ > ]: and then diff --git a/identity_resilience_ir_events.md b/identity_resilience_ir_events.md new file mode 100644 index 0000000000000000000000000000000000000000..c3581f92567576549dc13fa95530af9fd0be787a --- /dev/null +++ b/identity_resilience_ir_events.md @@ -0,0 +1,25 @@ +# Events in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_events.html + +--- + +# Events in Identity Resilience + +The Identity Resilience Events page provides a detailed operational log and audit trail for managing and protecting your hybrid identity environments, distinct from security alerts. + +The Events page in Rubrik Identity Resilience serves as a comprehensive operational log and audit trail for all activities related to the management and protection of your identity infrastructure. Unlike alerts, which focus on identity risks, the Events page provides granular details about the operational status of protection jobs, configuration changes, and other routine or triggered actions within RSC. + +You can use the following filters on the Events page to narrow down the events and quickly find specific information: + + * Time Range: Filters events based on their occurrence time. You can select from predefined period, such as Past 15 minutes, 24 hours, 7 days, or Custom range. + * Clusters: Filters events related to specific Rubrik clusters. + * Severity: Filters events by their impact or importance, such as Critical, Warning, or Informational. + * Status: Filters events by the outcome, such as, Succeeded, Failed, or In Progress. + * Event Type: Filters by the nature of the event. + +Identity Alert and Identity Security Violation are event types specific to Identity Resilience. + + * Object Type: Filters by the type of identity provider object involved, such as Domain Controller, Forests, Entra ID. It also provides filters for human and non-human identity types such as User, computer, GPO, Service Account. + +The Events page provides administrators the necessary transparency and logging to ensure that the Identity Resilience platform operates as expected and effectively protects their critical hybrid identity environments. diff --git a/identity_resilience_ir_identities_filters.md b/identity_resilience_ir_identities_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..72423009916879d0da055d8d0e3e46989eb9d648 --- /dev/null +++ b/identity_resilience_ir_identities_filters.md @@ -0,0 +1,41 @@ +# Identities filters + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_identities_filters.html + +--- + +# Identities filters + +RSC provides filters for identities discovered from your hybrid identity environments based on various criteria. + +The following table describes the filtering options to narrow down the identity list and focus on specific areas of concern. Filter | Description +---|--- +Insights | Filters identities for specific concerns. + + * At risk: Filters identities that have active violations. + * Privileged: Filters the privileged identities that have permissions to manage the Identity Provider (IDP) and identity settings. + * Highly sensitive: Filters identities that are highly sensitive and have access to sensitive data.Note: The highly sensitive filter is available as part of the Rubrik DSPM license. + + +Identity Type | Filters identities by identity type: + + * User + * Group + * Service Account + + +Native Type | Filters identities based on the native environment. +Sensitivity | Filters identities based on the sensitivity level of the data accessible to the identity. +Source | Filters identities by specific originating or owning entity.You can also search for a specific source using the search field. +Identity Status | Filters identities by status, whether it is active or disabled. +Origin | Filters internal and external identities. +Creation Date | Filters identities created during a specific time range. You can choose from the following options: + + * All + * Past 24 hours + * Past 7 days + * Past 30 days + * Custom + +You can also specify a custom time range. + *[ > ]: and then diff --git a/identity_resilience_ir_identitites.md b/identity_resilience_ir_identitites.md new file mode 100644 index 0000000000000000000000000000000000000000..e923b2690228f27a4054659182c208dda240c884 --- /dev/null +++ b/identity_resilience_ir_identitites.md @@ -0,0 +1,32 @@ +# Identities in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_identitites.html + +--- + +# Identities in Identity Resilience + +The identities page in Identity Resilience provides visibility into identities discovered in your environment. + +The Identities page within Identity Resilience provides a centralized and comprehensive view of all identities, both human and non-human, across your hybrid identity environment. This page is crucial for understanding the identity landscape and assessing associated risks. + +The Identities page offers a high-level summary of total identities discovered and the number of identities in your hybrid identity environment. + +RSC organizes identities into distinct categories, accessible through tabs for focused analysis: + + * All Identities: Displays a complete list of every discovered identity. + * Users: Focuses specifically on human user accounts. + * Groups: Lists security and distribution groups. + * Service Accounts: Highlights non-human identities often used by applications and services such as Group Managed Service Accounts (gMSA), Standalone Managed Service Accounts (sMSA), and enterprise apps. + +The Identities page is important for: + + * Visibility: Gaining a complete inventory of all identities and their characteristics. + * Identity insights: Quickly identifying identities that are at risk, privileged, or have access to highly sensitive data. + +Note: + +The highly sensitive data is available only if you have the DSPM license enabled. + + * Policy enforcement: Understanding which identities violate defined security policies. + diff --git a/identity_resilience_ir_identity_summary.md b/identity_resilience_ir_identity_summary.md new file mode 100644 index 0000000000000000000000000000000000000000..dab995e6fc580cd48029ad8218eb0a3d73003254 --- /dev/null +++ b/identity_resilience_ir_identity_summary.md @@ -0,0 +1,37 @@ +# Identity summary + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_identity_summary.html + +--- + +# Identity summary + +RSC provides a summary of an individual identity and insights about various components of an identity. + +The identity summary overview page provides a detailed, centralized view of different aspects of a specific identity and activity within your hybrid environment. It serves as a single source for deep-dive investigations into any user, group, or service account. It also displays the essential attributes such as identity type, unique identifier, and current status. + +## Identity summary graph + +A dynamic graph illustrates the relationships of a specific identity within the environment and highlights immediate security concerns. This includes summarized insights such as risk status, privilege levels, and authentication posture, along with real-time counts of identity violations and alerts. + +For privileged identities, the graph also provides insights into their associated privileged memberships or roles. + +## Policy Violations + +The policy violations widget displays details of the violations associated with the identity and categorizes the violations based on severity. + +On the right, specific policy violations associated with the identity are detailed. This provides direct insight into non-compliance, alongside information about its data access by sensitivity, if available. + +## Snapshot Based Vulnerabilities Summary + +RSC provides a time-series trend graph that visually tracks the vulnerabilities or overall security posture of an identity over time. This allows administrators to observe historical trends, identify changes, and assess improvements or deteriorations in security state of the identity. + +RSC updates the vulnerabilities graph using the snapshot of the Identity Provider (IdP) object. When there are multiple snapshots of the IdP object in a day, the graph is updated only once after the last snapshot. + +## Data Access by Sensitivity + +Note: + +This requires a DSPM license. + +The data access by sensitivity widget provides information about the access to sensitive data, categorized by its sensitivity level. When data is available, it offers insights into the potential blast radius if the identity were compromised, based on data context. diff --git a/identity_resilience_ir_idp_protection_planning.md b/identity_resilience_ir_idp_protection_planning.md new file mode 100644 index 0000000000000000000000000000000000000000..663660b35c01277a44b335b448ff7bbc8c67f17d --- /dev/null +++ b/identity_resilience_ir_idp_protection_planning.md @@ -0,0 +1,31 @@ +# IdP protection planning + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_idp_protection_planning.html + +--- + +# IdP protection planning + +Effective planning for Identity Provider protection involves defining the scope, assessing criticality, strategizing onboarding and integration, managing permissions and credentials, establishing SLA Domains, and preparing for recovery scenarios to ensure robust defense and rapid recovery of identity environments. + +Planning for Identity Provider (IdP) protection within Identity Resilience focuses specifically on securing your hybrid identity environments. This involves a set of strategic steps to ensure these critical identity sources are fully protected and rapidly recoverable. + +Here are the key planning areas: + + * Scope of protection: Identifying all IdP objects that Rubrik Identity Resilience needs to protect. + * Criticality assessment: Prioritizing protection based on the criticality of each IdP to the operations and security of your organization. + * Onboarding and integration strategy: Planning Active Directory (AD) integration by adding domain controllers to the Rubrik cluster with Rubrik Backup Service (RBS) and ensuring network connectivity. For Microsoft Entra ID, you need to decide on OAuth or manual credentials, and configure application registration if using OAuth. + * Permissions and credential management: Planning for effective permissions and credential management involves the following. + * Least privilege principle: Defining and configuring the minimum necessary permissions for Rubrik to perform discovery, backup, and recovery operations on your hybrid identity environments. This typically involves specific roles or delegated permissions rather than broad administrative access. + * Secure credential storage: Planning how the required credentials, such as service accounts for AD, application secrets or certificates for Entra ID, will be securely stored and managed within Rubrik. + * SLA Domain strategy for identity data: The SLA Domain strategy for identity data involves the following key considerations. + * Defining RPO and RTO: Determining the Recovery Point Objectives (RPO) and Recovery Time Objectives (RTO) specific to your AD and Microsoft Entra ID data. This will drive the backup frequency. + * Retention policies: Establishing retention periods for identity data backups to meet compliance, legal, and operational recovery requirements. For example, 7 years for specific AD attributes and 30 days for operational recovery. + * Replication and archiving: Deciding if identity data needs to be replicated to another Rubrik cluster for disaster recovery or archived to long-term, immutable cloud storage for compliance. + * SLA Domain assignment: Planning how specific SLA Domains will be assigned to your AD domains, Organizational Units (OUs), or Microsoft Entra ID tenants or objects to ensure consistent protection. + * Recovery preparedness and testing: Key elements of recovery preparedness and testing include the following. + * Scenario planning: Identifying critical recovery scenarios for your IdPs, such as granular AD object restore, single domain controller restore, full AD forest recovery, Microsoft Entra ID user, group, or application restore. + * Clean-room strategy: For major incidents like ransomware, planning the setup of an isolated clean-room environment where compromised IdPs, especially AD forests, can be safely restored, verified, and remediated before reintroduction to the production network. + * Regular drills: Scheduling and planning for regular, non-disruptive recovery drills to validate the effectiveness of your IdP protection. + +By meticulously planning these aspects, you can establish a robust defense for your identity providers using Rubrik Identity Resilience. This significantly enhances the ability to withstand and recover from cyberattacks that target the authentication and authorization systems. diff --git a/identity_resilience_ir_info_identities.md b/identity_resilience_ir_info_identities.md new file mode 100644 index 0000000000000000000000000000000000000000..7a61bed4a0ccd51970593749e4d50c7c065bc894 --- /dev/null +++ b/identity_resilience_ir_info_identities.md @@ -0,0 +1,46 @@ +# Information about identities + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_info_identities.html + +--- + +# Information about identities + +Information about the identities discovered by RSC. + +RSC discovers the identities in your hybrid identity environments and displays the details on the Identities page in Identity Resilience. You can also customize the view by adding, removing, pinning, and reordering the columns using the icon. You can use the Reset option to set the default view for the Identities page. + +The following table describes the columns that provide details about identities in your hybrid identity environments. Column | Description +---|--- +Identity Display Name | Name of the identity discovered after scanning the Identity Provider (IdP) snapshots.RSC provides a tooltip for each identity; upon clicking, the tooltip displays the identity name, unique identifier of the identity, and a link to view the Identity Summary of that specific identity. +Identity Type | The type of identity: + + * User + * Group + * Service Account + + +Insights | Classification of identities, indicating their risk or potential impact. +Policy Violations | Number of policies the identity is violating. RSC also flags the critical violations. +Data Access by Sensitivity | This column classifies data accessible to the identity based on the sensitivity of the data.Note: The Data Access by Sensitivity information is available as part of the Rubrik DSPM license. +Source | The owning entity of an identity is the source. + + * For Active Directory (AD), the source is domain. + * For Entra ID, the source is tenant. + + +Origin | The origin of the identity: + + * Internal: Identities managed within IdP. + * External: Identities managed outside IdP. The external identities can also include guest users. + + +Native Type | Identity type as defined in the specific IdP. +Unique Identifier | A unique identifier for an identity is a distinct value assigned to a specific identity within a system or across multiple systems. Its primary purpose is to unambiguously distinguish one identity from all others, ensuring that each individual, group, or service account can be precisely referenced and managed. +Title | Title assigned to the identity.Note: This is applicable only to identity type User. +Department | Department name of the identity.Note: This is applicable only to identity type User. +Data Categories | The data an identity has access to, grouped by their data category. Data categories are formed by grouping data types together.Note: The Data Categories information is available as part of the Rubrik DSPM license. +Data Types | The number of times a specific data type was found in the data accessible to an identity.Note: The Data Types information is available as part of the Rubrik DSPM license. +Creation Date | The system created the identity on this date and time. +Identity Provider | Identity provider name. + *[ > ]: and then diff --git a/identity_resilience_ir_key_features.md b/identity_resilience_ir_key_features.md new file mode 100644 index 0000000000000000000000000000000000000000..7c89e932a8f80d1c0fc422264c55075fc106a706 --- /dev/null +++ b/identity_resilience_ir_key_features.md @@ -0,0 +1,46 @@ +# Key features of Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_key_features.html + +--- + +# Key features of Identity Resilience + +RSC provides unified identity management, identity protection, and identity security for human and non-human identities in hybrid identity environments. + +Rubrik Identity Resilience is a critical product offering designed to provide comprehensive security and recovery for the identity infrastructure in hybrid identity environments. + +The key features of Identity Resilience include: + +## Hybrid identity protection and recovery + + * Scope: Secures identities in complex hybrid setups. + * Automated discovery and protection: RSC automatically discovers AD domains, domain controllers (including FSMO roles, DNS, DHCP services), and Microsoft Entra ID tenants and objects for streamlined protection. + * Recovery: Offers automated, orchestrated recovery workflows to restore AD domain controllers, AD forests, and Microsoft Entra ID tenants quickly after attacks, reducing downtime. + * Clean-room recovery: Restores AD identities in a secure, isolated environment to prevent attacks by malware or persistent threats. + * SLA-based management: Applies defined SLA Domains for consistent backup frequency, retention, replication, and archival policies across your identity infrastructure. + * Granular restoration: Recovers specific AD or Microsoft Entra ID objects, such as users, groups, and service accounts, without full system rollback. + * Simplified process: Reduces manual recovery steps and accelerates restoration. + +## Real-time monitoring and alerts + + * Tamper-resistant monitoring: Provides real-time tracking of critical changes within AD. + * Privilege change tracking: Monitors additions or removals of users and groups from privileged AD groups, flagging potential escalations or unauthorized de-provisioning. + * GPO modification alerts: Immediately identifies and alerts on any changes to Group Policy Objects (GPOs), which are critical for maintaining security configurations. + * Notifications: Enables management of notification channels and email alerts for detected events. + * Rapid response: Enables early detection and faster response to identity-based threats. + +## Comprehensive risk analysis + + * Unified visibility: Provides a single dashboard to monitor human identities, such as user accounts and groups, and non-human identities, such as service accounts. + * Risk detection: Utilizes risk policies aimed at detecting security gaps across your identity and identity infrastructure configurations, enabling proactive remediation. + * Actionable remediation: Detects security violations and provides workflows to drive their remediation through IT Service Management (ITSM) integration, remediation guidance, and in-app remediation actions to close security gaps directly from RSC. + +## Identity and data context integration + +This requires a DSPM license. + + * Holistic view: Combines identity and sensitive data context for better prioritization of identity risks, identifies highly sensitive identities that require additional security measures, and assesses the potential blast radius of a compromised identity. + * Time-series data: Tracks identity and access changes over time for continuous monitoring and historical analysis. + * Enhanced threat investigation: Correlates identity risks with data access patterns to identify and respond to threats faster. + diff --git a/identity_resilience_ir_managing_notifications_violations.md b/identity_resilience_ir_managing_notifications_violations.md new file mode 100644 index 0000000000000000000000000000000000000000..a8914b75fdab4a5bf9c6eef510d514b5285356f4 --- /dev/null +++ b/identity_resilience_ir_managing_notifications_violations.md @@ -0,0 +1,36 @@ +# Managing notifications for violations + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_managing_notifications_violations.html + +--- + +# Managing notifications for violations + +Manage notification channels for violations detected in your environment. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Notifications and select one of the following: + +Option| Action +---|--- +Emails | Click Add Notification Setting to configure email notifications. +Webhooks | Click Add Webhook to send alerts to an external service. + +The Add Webhook or Add Notification Setting wizard appears based on your selection. + + 4. While configuring the settings for emails and webhooks, select the event type Identity Security Violation and select all severity levels. + +The Adding webhooks topic provides detailed instructions about configuring webhooks in RSC to manage notification channels. + +The Adding an email notification setting topic provides detailed instructions about adding email notification settings. + +## Results + +You have configured the notification settings for webhooks or email notifications for violations. + *[ > ]: and then diff --git a/identity_resilience_ir_policies_violations.md b/identity_resilience_ir_policies_violations.md new file mode 100644 index 0000000000000000000000000000000000000000..2c783c186bfa4151113bcfd3923f6d42dd5e8402 --- /dev/null +++ b/identity_resilience_ir_policies_violations.md @@ -0,0 +1,52 @@ +# Policies and violations in Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_policies_violations.html + +--- + +# Policies and violations in Identity Resilience + +Identity Resilience policies are predefined by Rubrik to identify gaps in your identity security posture and simplify the process to mitigate identity-based cyber risks. + +## Policies + +Rubrik predefined policies are the building blocks of Identity Resilience to enforce security best practices and ensure compliance with organizational and regulatory standards. These policies are applied to hybrid identity environments. Policies help with identifying the security issues and also provide insights about the severity of the violation. You can leverage the policy violation information to safeguard your Identity Provider (IdP) data. + +The following table describes the policy categories, their purpose, implementation, and benefits. Category | Purpose | Implementation | Benefit +---|---|---|--- +IdP Configurations | To ensure the fundamental security, health, and hardening of the core IdP settings. | Rubrik scans and assesses the setup parameters, architectural configurations, and best practice adherence of your hybrid identity environments. It identifies deviations from secure baseline configurations. | + + * Prevents vulnerabilities stemming from misconfigured directory services + * Maintains the integrity and availability of core identity infrastructure + * Supports compliance with foundational security frameworks + + +Identity Hygiene | To maintain the cleanliness, efficiency, and security of individual identity objects (users, groups, and service accounts) throughout their lifecycle, reducing potential attack surfaces. | Rubrik identifies and flags accounts that are violating the identity hygiene. It also flags inconsistencies in identity lifecycle management. | + + * Reduces the number of exploitable accounts + * Minimizes the attack surface by eliminating unnecessary identities + * Improves overall security posture and operational efficiency + + +Identity Privileges | To govern and monitor the access rights and permissions assigned to identities, preventing privilege escalation and ensuring the principle of least privilege. | Rubrik flags accounts that are over-privileged, detects problematic access combinations, and monitors memberships in sensitive or administrative groups. It identifies potential privilege escalation paths. | + + * Minimizes the blast radius of a compromised identity + * Strengthens access control and governance + * Ensures critical resources are only accessible by truly authorized and necessary accounts + + +Authentication Settings | To ensure that the methods and configurations used for verifying identity are robust, secure, and compliant with modern security standards, preventing unauthorized access. | Rubrik assesses the implementation of multi-factor authentication (MFA), the use of insecure or legacy authentication protocols, and checks for weaknesses in credential storage and password protection mechanisms within the IdP. | + + * Prevents unauthorized access through weak authentication + * Reduces the risk of credential compromise + * Enhances the overall security and resilience of user and service authentication processes + + + +The Policies page provides filters to view specific policies based on severity and category. You can turn on the Show disabled policies toggle to view the disabled policies along with the predefined policies enabled in your environment. You can also search for a specific policy using the Search by policy name field. + +## Violations + +Using predefined policies, RSC automatically scans the identities in your environment. RSC generates violations for identities violating these policies. + +The Violations page provides a centralized view of security policy violations. For each violation, it displays the specific policies breached and identifies the associated identities or domains that are non-compliant. The violations feature helps with assessing your compliance posture against predefined rules related to identity security. You can view information about the violations associated with each policy along with detailed information about the severity, number of violations, and category of the policy violation. This detailed insight facilitates the prioritization and planning of effective remediation strategies to address the identified security gaps. You can also customize your view using the filters to view a specific policy based on the status, severity, and category detected over a specific time. diff --git a/identity_resilience_ir_prereq.md b/identity_resilience_ir_prereq.md new file mode 100644 index 0000000000000000000000000000000000000000..60fdbba209ad112a47663247afdc2d35852f5953 --- /dev/null +++ b/identity_resilience_ir_prereq.md @@ -0,0 +1,17 @@ +# Identity Resilience prerequisites + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_prereq.html + +--- + +# Identity Resilience prerequisites + +Information about specific requirements for Identity Resilience. + +Prerequisite | Description +---|--- +License | Rubrik Identity Cyber Recovery License or Rubrik Identity Resilience License. +Operating System (for Active Directory) | Windows Server 2012 to Windows Server 2022Note: Rubrik does not provide support for Windows Server 2025. +Rubrik CDM Version (for Active Directory) | Rubrik cluster running Rubrik CDM version 9.4.2 or later. +Required Permissions | For Microsoft Entra ID directories added to RSC without OAuth, you must add specific Microsoft Entra ID permissions to the Microsoft Entra ID domain. The Permissions for adding Microsoft Entra ID without OAuth topic describes the required Microsoft Entra ID permissions for RSC.For Microsoft Entra ID directories added to RSC with OAuth, a global administrator of that Entra ID domain should add your Entra ID domain.The Microsoft Entra ID documentation provides more information about Microsoft permissions. + *[ > ]: and then diff --git a/identity_resilience_ir_protection_identities.md b/identity_resilience_ir_protection_identities.md new file mode 100644 index 0000000000000000000000000000000000000000..f630cf1936a103245b2df56b23f8d3e7630bad45 --- /dev/null +++ b/identity_resilience_ir_protection_identities.md @@ -0,0 +1,41 @@ +# Protection for identities + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_protection_identities.html + +--- + +# Protection for identities + +RSC provides the core features of data protection and recovery for identities in Identity Resilience. You can configure, manage, and monitor the protection status of your identity infrastructure. + +## Overview + +The Protection tab in Rubrik Identity Resilience serves as the central control panel for configuring, managing, and continuously monitoring the protection status of your critical identity infrastructure. This tab provides a unified interface for adding and overseeing the defense of your hybrid identity environments. + +You can establish the foundational resilience for your identities by adding the Identity Provider (IdP) and defining how Rubrik will safeguard them. It offers clear visibility into the inventory of protected domains, domain controllers, and the specific count of users and groups actively under protection, ensuring that your most valuable identity assets are secured according to your defined policies. Through this single point of management, organizations can ensure comprehensive coverage, streamline the addition of new IdPs, and gain confidence in their ability to recover from identity-based threats. + +The inventory for Active Directory (AD) and Microsoft Entra ID remains the same as it is in Data Protection. The overview details, recovery, and all operations related to snapshots also remain the same. You can add an IdP to Identity Resilience to start protecting the identities in your hybrid environment. + +## Supported IdPs and protection steps + +Rubrik protects the following IdPs: + + * Microsoft Active Directory + * Microsoft Entra ID + +You can protect the identities in your IdP by: + + * Adding the IdP to Identity Resilience. + * Assigning an SLA Domain to the objects. + +## Identity Resilience Inventory + +The Identity Resilience Inventory page acts as your starting point for understanding your identity protection landscape. It offers: + + * Centralized visibility: A unified view of all your protected identity environments. + * Protection status at a glance: Quick metrics on how many identities, domains, and tenants are under protection. + * Onboarding facilitation: Provides the gateway to add more identity providers. + * Foundation for policy management: After RSC discovers the identities, these inventory items can then be managed through SLA Domains and other policy configurations. + +The Active Directory Protection and Microsoft Entra ID sections in the Rubrik Security Cloud User Guide provide more information about protecting and recovering the AD and Entra ID objects. + *[ > ]: and then diff --git a/identity_resilience_ir_rbac.md b/identity_resilience_ir_rbac.md new file mode 100644 index 0000000000000000000000000000000000000000..2d51f4e9ab32bc6dd858b0d70fa0d5ee1029090b --- /dev/null +++ b/identity_resilience_ir_rbac.md @@ -0,0 +1,34 @@ +# RBAC for Identity Resilience + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_rbac.html + +--- + +# RBAC for Identity Resilience + +Information about the privileges required for Identity Resilience access. These privileges help in configuring role-based access control for users. + +RSC provides specific roles to perform specific operations in Identity Resilience. + +The following table describes the privileges for Identity Resilience roles. Role | Privileges +---|--- +Identity Security Administrator | Full privileges in Identity Resilience, such as manage policies, view and remediate violations. +Identity Risk Auditor | Privileges to view all pages in the Identity Resilience application. + +The following table describes the privileges for Identity Resilience. Privilege | Description +---|--- +View Identity Resilience application | Grants you the view access to all pages of Identity Resilienceapplication, including the dashboard, identity inventory, policy violations, and alerts.Note: This is a global privilege and is not limited by specific data management privileges. +Manage policies, violations, alerts | Grants you the ability to: + + * Enable and disable policies. + * View and change the status of violations. + * View and change the status of alerts. + +Note: This is a global permission and is not limited by specific data management privileges. +Remediate policy violations | Grants you the ability to: + + * Perform remediation actions for policy violations. + * Create tickets for violations and alerts. + +Note: This privilege is restricted to the Active Directory (AD) or Entra ID objects you have been granted access to using data management privileges. + *[ > ]: and then diff --git a/identity_resilience_ir_remediating_violations.md b/identity_resilience_ir_remediating_violations.md new file mode 100644 index 0000000000000000000000000000000000000000..e61a22d52e7e1c49e65140749c76832e341037fb --- /dev/null +++ b/identity_resilience_ir_remediating_violations.md @@ -0,0 +1,43 @@ +# Remediating violations + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_remediating_violations.html + +--- + +# Remediating violations + +Remediate policy violations by investigating the impacted identities, understanding the violations, and initiating remediation through direct action or ticket creation. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Violations. + +The Violations page appears, displaying a list of policies that have active violations. + + 4. Click for a policy and select Investigate Violations. + +You can also click the name of the policy to view the identities that violate the selected policy. + +A list of identities or domains and the violations associated with the identity appears. + + 5. Hover over the identity and click View Details. + +A page appears displaying an overview of the selected policy violation, including details of the breached policy, the affected identity or IdP, and recommended remediation steps. + + 6. Click Remediate and select the required action. + * Recommended remediation action + * Create a ticket + +You can change the status of the violation using the Status dropdown. + +You can also remediate the violation manually, and RSC will identify and update the violation status as Remediated. + +## Results + +The remediation action for the selected identity is now complete. + *[ > ]: and then diff --git a/identity_resilience_ir_remediation_actions.md b/identity_resilience_ir_remediation_actions.md new file mode 100644 index 0000000000000000000000000000000000000000..72e5242a2acb9e3023c59a0e678aeea099e2a6bf --- /dev/null +++ b/identity_resilience_ir_remediation_actions.md @@ -0,0 +1,27 @@ +# Remediation actions + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_remediation_actions.html + +--- + +# Remediation actions + +Information about remediation steps and guidance Rubrik recommends to resolve identified security violations and mitigate risks within your identity environment. + +In Identity Resilience, the following remediation actions are available: + + * Create Ticket + * Disable Inheritance + * Disable Delegation + * Disable Never Expires Setting + * Remove Identities From Group + * Enable Kerberos Pre-authentication + * Force Reset Password + * Disable Protocol Transition + * Enable AES Encryption + * Clear AltSecurity Attribute + * Disable Reversible Encryption + * Disable DES Encryption + * Clear Attribute Value + + *[ > ]: and then diff --git a/identity_resilience_ir_reports.md b/identity_resilience_ir_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..f003df9aa5c0e5658b823dbf2d0125631d304596 --- /dev/null +++ b/identity_resilience_ir_reports.md @@ -0,0 +1,29 @@ +# Identity Resilience reports + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_reports.html + +--- + +# Identity Resilience reports + +The Identity Resilience Reports page offers comprehensive analytics and actionable insights into your identity security posture. It provides various report templates for protection status, identity violations, audit trails, and operational activities across Identity Providers. + +The Reports page in Rubrik Identity Resilience serves as the central hub for generating and managing analytical reports that provide deep insights into your identity security posture, protection status, and operational activities across your hybrid identity environments. This feature is crucial for compliance, auditing, risk assessment, and demonstrating the effectiveness of your identity resilience strategy. + +The page aggregates various reporting capabilities, allowing administrators to access predefined reports relevant to their specific needs. RSC organizes reports into categories, enabling users to quickly navigate to relevant areas of interest. + +You can generate the following reports for Identity Resilience: + + * Protection + * Protection Tasks Details + * Object Capacity + * SLA Audit + * Object Audit + * Recovery Tasks Details + * Event + * Identity Violations + +The Identity Violations report analyzes various identity-related security risks. + +The reports can transform raw operational and security data from your identity infrastructure into digestible, insightful formats, empowering organizations to make data-driven decisions regarding their identity resilience posture. + *[ > ]: and then diff --git a/identity_resilience_ir_rolling_back_gpo_changes.md b/identity_resilience_ir_rolling_back_gpo_changes.md new file mode 100644 index 0000000000000000000000000000000000000000..7ce550fbfba1f55a18ca0bfc845f540404ed0da4 --- /dev/null +++ b/identity_resilience_ir_rolling_back_gpo_changes.md @@ -0,0 +1,46 @@ +# Rolling back GPO changes + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_rolling_back_gpo_changes.html + +--- + +# Rolling back GPO changes + +Roll back Group Policy Object changes to mitigate risks and protect your identity systems. RSC raises an alert if there are modifications to Group Policy Object. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.4.1 or later. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Alerts. + +The Alerts page appears, displaying the alerts generated for privilege group membership changes and Group Policy Object (GPO) modifications. + + 4. Click the name of the GPO change alert for which you want to roll back the GPO changes. + +The details of the alert, including the recommended response and GPO changes appear. + + 5. To track and respond to the alert, click Resolution Options > Roll Back GPO. + +You can also change the status of a specific alert using the Status dropdown. + +The Roll Back GPO wizard appears, displaying the live version and the rolled back version of the GPO. + +Note: + +The rollback action will undo the selected GPO change and any change that occurred after this alert. + + 6. In Domain controller, select the domain controller for GPO rollback. + 7. Click Roll Back. + +## Results + +RSC rolls back the GPO to the previous version by erasing the GPO modifications that were made. + *[ > ]: and then diff --git a/identity_resilience_ir_sla_domains.md b/identity_resilience_ir_sla_domains.md new file mode 100644 index 0000000000000000000000000000000000000000..43449dcc9b5423c9fe1630d69cfd188dd8e827ac --- /dev/null +++ b/identity_resilience_ir_sla_domains.md @@ -0,0 +1,16 @@ +# Identity Resilience SLA Domains + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_sla_domains.html + +--- + +# Identity Resilience SLA Domains + +The SLA Domains page in Identity Resilience manages policy-driven automation for protecting your hybrid identity infrastructure. It defines how identity data is backed up, retained, replicated, and archived, ensuring consistent and compliant protection for your Identity Providers. + +The SLA Domains page in Identity Resilience is the central hub for defining, managing, and applying policy-driven automation to protect your hybrid identity infrastructure. An SLA Domain is a reusable set of data protection policies that dictate how your identity data is backed up, retained, replicated, and archived. By assigning an SLA Domain to identity objects, you can ensure consistent and compliant data protection. + +Within Identity Resilience, SLA Domains are exclusively designed to protect object types for AD and Entra ID. You can create and assign these SLA Domains to your hybrid Identity and Access Management (IAM) object types to initiate their protection. + +You can view and manage SLA Domains created in Identity Resilience from the broader Data Protection application in RSC. However, you can only view and manage SLA Domains specifically assigned to AD or Entra ID object types from the dedicated Identity Resilience application within RSC. + *[ > ]: and then diff --git a/identity_resilience_ir_supported_func_idp.md b/identity_resilience_ir_supported_func_idp.md new file mode 100644 index 0000000000000000000000000000000000000000..96629efc8396d57b071b5b8df7c602c80ab188f9 --- /dev/null +++ b/identity_resilience_ir_supported_func_idp.md @@ -0,0 +1,42 @@ +# Supported functionalities and identities for IdP + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_supported_func_idp.html + +--- + +# Supported functionalities and identities for IdP + +Information about the functionalities and identities supported for specific Identity Provider in Identity Resilience. + +The following table provides information about the supported functionalities and identity types for specific Identity Provider (IdP). IdP | Supported functionality | Supported identity types +---|---|--- +Microsoft Entra ID | + + * Violations + * Identity Inventory + * Remediation Actions + +| + + * Users + * Groups + * Service accounts + * Data Context (Data Access Governance) + +Note: Data Context (Data Access Governance) is available as part of the Rubrik DSPM license. +Microsoft Active Directory (AD) | + + * Alerts + * Violations + * Identity Inventory + * Remediation Actions + +| + + * Users + * Groups + * gMSA (Group Managed Service Accounts) + * sMSA (Standalone Managed Service Accounts) + * Data Context (Data Access Governance) + +Note: Data Context (Data Access Governance) is available as part of the Rubrik DSPM license. diff --git a/identity_resilience_ir_viewing_activity_log.md b/identity_resilience_ir_viewing_activity_log.md new file mode 100644 index 0000000000000000000000000000000000000000..526dca92397efaf5f1c564a29689f951e1e71ee7 --- /dev/null +++ b/identity_resilience_ir_viewing_activity_log.md @@ -0,0 +1,29 @@ +# Viewing activity log + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_viewing_activity_log.html + +--- + +# Viewing activity log + +View the activity logs of your identity system to investigate any activities that might be non-compliant or could compromise security. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Activity > Activity Log. + +The Activity Log page appears, displaying a chronological event log of actions performed on specific Active Directory (AD) objects. + + 4. Click the name of an action for the overview. + +The action overview opens on a separate card. + +## Results + +RSC displays the detailed overview of the selected action. + *[ > ]: and then diff --git a/identity_resilience_ir_viewing_identity_summary.md b/identity_resilience_ir_viewing_identity_summary.md new file mode 100644 index 0000000000000000000000000000000000000000..ec6af9731de812f680dfc32302ab52f77b64fd30 --- /dev/null +++ b/identity_resilience_ir_viewing_identity_summary.md @@ -0,0 +1,30 @@ +# Viewing identity summary + +Source: https://docs.rubrik.com/en-us/saas/identity_resilience/ir_viewing_identity_summary.html + +--- + +# Viewing identity summary + +View the identity summary page to investigate a specific identity suspected of compromise or non-compliance. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Identities. + +The system discovers a list of identities in all your connected Identity Providers. + + 4. Click the name of an identity or click for an identity and select Investigate. + 5. **Optional:** Hover over the identity name, click the information icon, and click View Identity Summary. + +This opens the identity summary page in a new tab. + +## Results + +RSC displays the detailed summary of the selected identity. + *[ > ]: and then diff --git a/index.md b/index.md new file mode 100644 index 0000000000000000000000000000000000000000..26edc3f5bc299d47488a4c4b7b095500d06e09eb --- /dev/null +++ b/index.md @@ -0,0 +1,57 @@ +# Rubrik Security Cloud + +Source: https://docs.rubrik.com/en-us/saas/index.html + +--- + +[Setup](install/rsc_cluster_deployment.html) + +Rubrik CDM software can be installed on many different platforms, both physical and virtual. The software can run on a single node computer and on multiple node computing clusters. + +[Data Protection](saas/common/getting_started_with_rsc.html) + +Rubrik Security Cloud - Data Protection provides the core tools and features for protecting, managing, and analyzing your data. + +[Workloads](rubrik/supported_workloads.html) + +Rubrik Security Cloud - Data Protection securely manages and protects data from a wide variety of workload types. + +[Identity Resilience](identity_resilience/identity_resilience.html) + +Rubrik Identity Resilience is designed to protect, monitor, and recover identities, both human and non-human identities, in hybrid identity environments. + +[Data Threat Analytics](saas/ri_ransomware_monitoring.html) + +Rubrik Security Cloud Data Threat Analytics provides anomaly detection and data recovery services on protected resources such as VMware virtual machines, NAS, and Linux and Windows servers. + +[Data Security Posture](dspm/data_security_posture.html) + +Rubrik Security Cloud Data Security Posture enables organizations to find specific types of data within the data that has been indexed by Rubrik clusters. + +[Annapurna](ai/annapurna.html) + +Annapurna is an enterprise application for querying your protected data. It allows you to create custom chatbots that use advanced language models and retrieval-augmented generation to answer natural language questions about your data. + +[Orchestrated Application Recovery](saas/oar.html) + +Rubrik Security Cloud Orchestrated Application Recovery provides disaster recovery and application migration from an on-premises data center to a secondary recovery site. + +[Ruby](saas-ai/ruby_2.html) + +Ruby is an AI assistant designed to help you ask natural language questions to better understand and use Rubrik Security Cloud. + +[GraphQL API Playground](gql/api_playground_2.html) + +The API Playground is a tool that allows you to browse, explore, and run the GraphQL APIs of Rubrik Security Cloud. + +[Offline Recovery](https://docs.rubrik.com/en-us/latest/offrec/index.html) + +In the unlikely event that you cannot connect to Rubrik Security Cloud, you can use the offline recovery UI on your Rubrik clusters to perform basic recovery and maintenance. + +[Legal Notices and additional resources](reuse/notices.html) + +Rubrik legal notices for this documentation, and topics with additional resources and information. + +[Comments and suggestions](reuse/comments_suggestions.html) + +We welcome your comments and suggestions about our products and our product documentation. diff --git a/install_download_install_cdm_on_appliance_nodes.md b/install_download_install_cdm_on_appliance_nodes.md new file mode 100644 index 0000000000000000000000000000000000000000..a051cb6cfc8dda2d178dd0ecc573d405a0beaf7f --- /dev/null +++ b/install_download_install_cdm_on_appliance_nodes.md @@ -0,0 +1,121 @@ +# Downloading and installing Rubrik CDM + +Source: https://docs.rubrik.com/en-us/saas/install/download_install_cdm_on_appliance_nodes.html + +--- + +# Downloading and installing Rubrik CDM + +Before you set up your Rubrik cluster, you can install a version of Rubrik CDM that is different from the one already installed on the Rubrik appliance nodes. This involves downloading the software, transferring it to one of the nodes, and running the installation. + +## About this task + +Rubrik appliance nodes are shipped with a recent major GA release package already installed. However, you will often want to install a more recent version of Rubrik CDM before you set up a new cluster. Or you may want to install a specific version on a new node before you add the node to an existing cluster. + +## Procedure + + 1. Download the Rubrik CDM installation package from the [Rubrik Support portal](https://support.rubrik.com/) to a computer with network access to the Rubrik appliance nodes. + +Part of the download process involves accepting the EULA. To be able to read and accept the EULA, you must disable the pop-up blocker setting in your web browser. + +When downloading a installation package for a new a node that you are adding to a running Rubrik cluster, select the installation package that contains the same version of Rubrik CDM that is on the running Rubrik cluster. + + 2. Unzip the package. + +The zip file contains an installation zip file and a signature file: + * rubrik-image-xyz.tar.gz + * rubrik-image-xyz_tar.gz.sig + +Where xyz is the release and patch number. + + 3. Use SSH over IPv6 to connect to the node. + +`ssh -6 admin@node_serial_number.local` + +Where `node_serial_number` is the serial number of the node. You can retrieve the serial number of the cluster node from the sticker attached to the node or by connecting directly to the node and running network ifconfig from the Rubrik CLI. + + 4. At the username prompt, enter `admin`. + 5. At the password prompt, enter `rubrik`. + +The Rubrik CLI prompt appears. + + 6. In the SSH session, enter the version-dependent command to view the IP address of the node. + +For Rubrik CDM version 5.0.4 and later, enter: + + network ifconfig + +For versions of Rubrik CDM earlier than 5.0.4, enter: + + ifconfig bond0 + +Keep the SSH session open to use later in this task. + +If cluster setup was previously run on the node, the IP address that appears will be an IPv4 address. If this is the first time you are configuring the node, the IP address will be an IPv6 address. The command also displays the interface name. + + 7. In a new terminal session, use SFTP to connect to the new node. + +For an IPv6 address, at the prompt, enter: + + sftp adminstaging@[ipv6address]%interface + +Where ipv6address is the IPv6 address and interface is the interface name determined in a previous step. For example: + + sftp adminstaging@[fe80::ae1f:6bff:fe55:8c77]%bond0 + +For an IPv4 address, at the prompt, enter: + + sftp adminstaging@ipv4address + +Where ipv4address is the IPv4 address determined in a previous step. For example: + + sftp adminstaging@10.1.79.12 + + 8. When prompted, enter the password. + +The password is `rubrik`. + + 9. Use SFTP to upload the installation package to the node. + +At the prompt, enter: + + put install-package /upgrade/ + +Where install-package is the name of the installation package. + + 10. Use SFTP to upload the signature file to the node. + +At the prompt, enter: + + put sig-file /upgrade/ + +Where sig-file is the name of the signature file. + + 11. Return to the SSH session and start the software installation. + +Enter: + + cluster install start + +A list of available versions of the CDM software appears. + + 12. When prompted, enter the number assigned to the software version that you want to install. + +A list of the available nodes appears. + + 13. When prompted, select the number assigned to a node that you want the software installed on. + +The installation script installs the software on the selected node and displays the list of nodes again, with an asterisk by the entry for each node that has the software successfully installed. + + 14. Repeat the previous step until all of the nodes that you want the software on are listed with an asterisk. + 15. **Optional:** To view the installation log, enter: + +`support log_view installer.log` + +## Results + +The installation script installs the selected software on all of the selected nodes. + +## What to do next + +After successfully completing the software installation process, perform the system setup task. diff --git a/install_guidelines_strong_password.md b/install_guidelines_strong_password.md new file mode 100644 index 0000000000000000000000000000000000000000..ecf9f4b5a3bdec9df8858c4af4d54d65dbb55299 --- /dev/null +++ b/install_guidelines_strong_password.md @@ -0,0 +1,34 @@ +# Guidelines for choosing a strong password + +Source: https://docs.rubrik.com/en-us/saas/install/guidelines_strong_password.html + +--- + +# Guidelines for choosing a strong password + +When choosing a password, you are required to follow the guidelines recommended by Rubrik to set a strong password that is difficult to guess or extract through a password cracker application, but is something that is easy to remember. + +When choosing a password, the goal is to make it difficult to guess but easy to remember. + +Rubrik recommends avoiding passwords with the following criteria: + + * Single words that can be found in a dictionary. + * Common passwords, such as passw0rd, letmein, or abc123. + * Repeated characters, such as aaaa or 2222. + * Character sequences, such as abcd or 1234. + * L33t speak, where numbers and symbols are used in place of letters, for example, 3 for e, @ for a, and $ for s. + * Patterns made up of adjacent keys on a keyboard, such as qwerty or ujm. + +You are required to incorporate the following characteristics to make a password difficult to guess but easy to remember: + + * Long strings (up to 1000 characters) of uncommon, unrelated words combined in a sequence, such as CorrectHorseBreadStaple. Rubrik clusters do not support passwords longer than 1000 characters. + * Unexpected caPitalizAtion. + * Numbers at the beginning or middle of the password or distributed throughout the password. + +As most users put a number at the end of their password, you must increase unpredictability by putting it at the beginning or in the middle, or distributing numbers throughout the password. + + * A series of short keyboard patterns with lots of turns. + +A turn corresponds to a change of direction on the keyboard from one character to the next. A turn can also refer to the gap between pattern segments in the password. + +To make the password easy to remember, you can try a long password (up to 1000 characters) made up of a series of dictionary words that are not commonly combined in a sequence, and include one or more numbers. diff --git a/install_registering_clusters_offline.md b/install_registering_clusters_offline.md new file mode 100644 index 0000000000000000000000000000000000000000..3ea98d8a9dca05c30de3008d827ebf92f6e1e4be --- /dev/null +++ b/install_registering_clusters_offline.md @@ -0,0 +1,89 @@ +# Registering Rubrik clusters using the offline method + +Source: https://docs.rubrik.com/en-us/saas/install/registering_clusters_offline.html + +--- + +# Registering Rubrik clusters using the offline method + +Use the offline registration method when the cluster cannot establish a connection with Rubrik Security Cloud. + +## Before you begin + + * Perform the configuration tasks that prepare the cluster for registration, as described in the Setting up a Rubrik cluster using the UI topic . + * Verify receipt of the Rubrik Welcome email. + * Verify access to the credentials of the Rubrik Security Cloud account. + +## Procedure + + 1. In a web browser, access the Rubrik cluster node using its IP address. + +This step is also required when the initial configuration tasks were performed through the Rubrik CLI. + +The Bootstrap complete page of the cluster onboarding wizard appears. + + 2. In Username, enter the username of the administrative account. + 3. In Password, enter the account password. + 4. Click Sign in. + +The Register your cluster with Rubrik page appears. + + 5. Click Try offline registration. + +The Offline Registration dialog box appears. + + 6. In Step 1: Retrieve registration key, select an action to obtain the JSON file required for retrieving the key. + * Click the copy icon to copy the contents of the JSON file. + * Click the download icon to download the JSON file. + 7. In a different browser window, open the Welcome email from Rubrik and click the registration link. + +Alternatively, navigate to rubrik_account_name.my.rubrik.com/offlineregistration in a web browser. + +The web browser loads the login page for RSC. + + 8. Log in to RSC. + +The Cluster Registration Key dialog box appears. + + 9. Select your service type. + * Select Rubrik Security Cloud (SaaS) to manage all your data through Rubrik Data Protection. + * Select CDM (Software) to manage your clusters locally. + +When you own licenses for both service types, you can register the cluster with either service type. When you own a license for a single service type, you must follow the cluster registration process applicable to that service. + + 10. Click Confirm. + +The Rubrik End User License Agreement appears. + + 11. Read the agreement and click I Agree. + +The Cluster Registration Key dialog box reappears. + + 12. In Input JSON, provide the contents of the JSON file to generate the registration key. + * Paste the contents of the JSON file if you copied them from the Offline Registration dialog box. + * Click Upload JSON File to upload the JSON file. + 13. In Registration key, click Generate Key. + +The offline registration key appears. + + 14. Copy the offline registration key and click Done. + 15. Go back to the browser window that shows the Offline Registration dialog box. + 16. In Step 2: Enter registration key here, paste the offline registration key. + 17. Click Register. + +The cluster registration process begins. When registration completes, the corresponding message appears on the screen. + + 18. Click Access Cluster. + +The Access Cluster button appears when the registration completes successfully. + +A Security Notice dialog box appears, prompting you to configure and apply time-based, one-time password (TOTP)-based multifactor authentication (MFA) settings. + +## Results + +Offline cluster registration completes successfully and a dialog box appears with options for configuring MFA on the cluster. + +## What to do next + +Configure TOTP-based MFA on the newly registered clusters, as described in [Enabling MFA](rsc_enabling_mfa.html "Enable multi-factor authentication for newly registered clusters."). + *[ > ]: and then diff --git a/install_registering_clusters_online.md b/install_registering_clusters_online.md new file mode 100644 index 0000000000000000000000000000000000000000..50db71445c79bc3790c8e3ae39d44dbc5a28691e --- /dev/null +++ b/install_registering_clusters_online.md @@ -0,0 +1,74 @@ +# Registering Rubrik clusters using the online method + +Source: https://docs.rubrik.com/en-us/saas/install/registering_clusters_online.html + +--- + +# Registering Rubrik clusters using the online method + +When internet connectivity is available, register your Rubrik cluster using the online method. + +## Before you begin + + * Perform the configuration tasks that prepare the cluster for registration, as described in the Setting up a Rubrik cluster using the UI topic. + * Confirm that the Rubrik cluster can connect to the Rubrik Security Cloud (RSC) domain URL, either directly or through a proxy. + * Verify receipt of the Rubrik Welcome email. + * Verify access to the credentials of the Rubrik Security Cloud account. + +## Procedure + + 1. In a web browser, access the Rubrik cluster node using its IP address. + +This step is also required when the initial configuration tasks were performed through the Rubrik CLI. + +The Bootstrap complete page of the cluster onboarding wizard appears. + + 2. In Username, enter the username of the administrative account. + 3. In Password, enter the account password. + 4. Click Sign in. + +The Register your cluster with Rubrik page appears. + + 5. **Optional:** Click I don't have domain or credentials. + +You can retrieve the RSC domain URL from the Rubrik Welcome email or the Rubrik Support portal. + +The My Products tab of Rubrik Support portal appears and displays your RSC domain URL and the name of the account owner. + + 6. In Rubrik domain URL, enter the URL of your RSC account. + 7. Click Sign in. + +The login page of RSC appears. + + 8. Log in to RSC. + +The Online Cluster Registration dialog box appears. + + 9. Select your service type. + * Select Rubrik Security Cloud (SaaS) to manage all your data through Rubrik Security Cloud. + * Select CDM (Software) to manage your clusters locally. + +When you own licenses for both service types, you can register the cluster with either service type. When you own a license for a single service type, you must follow the cluster registration process applicable to that service. + + 10. Verify the details of the cluster to be registered and click Next. + +The Rubrik End User License Agreement appears. + + 11. Read the agreement and click I Agree. + +The cluster registration process begins. When registration completes, the corresponding message appears on the screen. + + 12. Click Access Cluster. + +The Access Cluster button appears when the registration completes successfully. + +A Security Notice dialog box appears, prompting you to configure and apply time-based, one-time password (TOTP)-based multifactor authentication (MFA) settings. + +## Results + +Online cluster registration completes successfully and a dialog box appears with options for configuring MFA on the cluster. + +## What to do next + +Configure TOTP-based MFA on the newly registered clusters, as described in the Enabling MFA topic. + *[ > ]: and then diff --git a/install_rsc_cluster_config_considerations.md b/install_rsc_cluster_config_considerations.md new file mode 100644 index 0000000000000000000000000000000000000000..64e41d138d458ad516f4e59f6545ca7c64091b4c --- /dev/null +++ b/install_rsc_cluster_config_considerations.md @@ -0,0 +1,19 @@ +# Cluster configuration considerations + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_config_considerations.html + +--- + +# Cluster configuration considerations + +You determine network related settings and capabilities of a Rubrik cluster through the set up task. + +The initial setup of the cluster involves node discovery, and the configuration of data and management interfaces and services for all the nodes on the cluster. A UI to perform the initial configuration is available through any of the nodes. Alternatively, you can configure the cluster at the command line using the Rubrik CLI. + +If you have an IPv4 cluster deployment, you can optionally configure VLAN tagging for both the management network and the data network. You can configure VLAN tagging through either the UI or the Rubrik CLI. + +If your cluster deployment supports encryption of data at rest, Rubrik CDM enables data encryption by default during the initial configuration. You can disable the encryption of data at rest but this must be done through the CLI and should be done before protecting any data. If the encryption of data at rest setting is changed after system setup, a cluster reset is required, which will delete all stored data. + +The setting for encryption of data at rest is supported only on Brik models that have the hardware Trusted Platform Module (TPM).You will not have this option during setup for Brik models that use hardware data encryption at rest, such as the r6xxxF series Briks. + +Virtual clusters allow you to configure an encryption password when you enable encryption. diff --git a/install_rsc_cluster_deployment.md b/install_rsc_cluster_deployment.md new file mode 100644 index 0000000000000000000000000000000000000000..a692a519668a477dc43cd42beac29454c7375552 --- /dev/null +++ b/install_rsc_cluster_deployment.md @@ -0,0 +1,37 @@ +# Rubrik cluster deployment + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_deployment.html + +--- + +# Rubrik cluster deployment + +Deploying a Rubrik cluster running on Rubrik appliance nodes involves installing the CDM software on the nodes and setting up that software for your environment. + +## Appliance nodes + +Getting your Rubrik cluster up and running on Rubrik appliance nodes involves the following tasks: + + * Downloading and installing the Rubrik CDM software + * Setting up the Rubrik cluster + * Registering the Rubrik cluster + +Rubrik appliance nodes come with a recent version of the Rubrik CDM software already preloaded. Rubrik recommends that instead of running your Rubrik cluster with this factory loaded version, you consider downloading and installing the most recent GA version of the CDM software. By doing this you can avoid running multiple upgrades to get the cluster running the latest GA version. However, selecting a Rubrik CDM version that is not preloaded adds approximately 30 minutes to the setup process. + +Installing and configuring the Rubrik CDM software on a cluster usually involves running the configuration wizard from the UI provided by a node of the cluster. The wizard ensures that all nodes pass the pre-checks and meet the requirement of running the same version of Rubrik CDM before installing and configuring the software. + +When required, installing and configuring the software can also be done from the Rubrik CLI. + +After installing the software on all of your nodes, you perform the set up task. The set up task involves configuring each node to operate as part of a cluster. It also involves configuring the nodes with your network preferences. + +Your last step is registering the new Rubrik cluster. If your Rubrik cluster can connect to your Rubrik Security Cloud (RSC) domain, you can easily register your Rubrik cluster using a web browser. If your Rubrik cluster cannot connect to your RSC domain, you can use the offline method to register the cluster. + +## Other platforms + +Supported hardware other than the Rubrik appliance hardware is available from manufacturers such as Dell, Cisco, and Hewlett Packard Enterprise. Rubrik provides hardware-specific installation and configuration guides for each supported platform. These guides are available through the [Rubrik Support portal](https://support.rubrik.com/). + +The process of installing Rubrik CDM software on virtual instances such as Rubrik Edge, Rubrik Virtual Cluster, and Rubrik Cloud Cluster includes preparing the virtual hardware for those deployments. Rubrik provides documentation for each deployment type through the [Rubrik Support portal](https://support.rubrik.com/). + +## RSC association + +After the Rubrik cluster is successfully configured, you establish an association between the Rubrik cluster and Rubrik Security Cloud by registering the cluster using your RSC account. diff --git a/install_rsc_cluster_registration.md b/install_rsc_cluster_registration.md new file mode 100644 index 0000000000000000000000000000000000000000..3c75b5b5fd9770ff5fe9251ce4e1b9c860052b54 --- /dev/null +++ b/install_rsc_cluster_registration.md @@ -0,0 +1,17 @@ +# Cluster registration + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_cluster_registration.html + +--- + +# Cluster registration + +Rubrik offers two modes for registering clusters with Rubrik Security Cloud, online and offline. + +After configuring a Rubrik cluster, the next required task is to register it through your Rubrik Security Cloud account. Registration is performed over the internet using a web browser. + +The online registration method uses a secure internet connection from the Rubrik cluster to your Rubrik Security Cloud account to retrieve the registration key. When physical hardware is in use, that hardware must also be available and have access to the network. + +The offline registration method uses a manual method of retrieving the registration key and providing it to the Rubrik cluster. Offline registration requires access to a web browser for a one-time login to the Rubrik Security Cloud account to retrieve a unique registration key for each cluster. The registration key is valid only for two days from the time it is generated. + +Either way, the registration process requires signing into your Rubrik Security Cloud account using a web browser on a computer with an internet connection, even when the configuration of the cluster was performed through the CLI. The domain URL of your Rubrik Security Cloud account is available in the Rubrik Welcome email or on the Rubrik Support portal. diff --git a/install_rsc_disabling_mfa.md b/install_rsc_disabling_mfa.md new file mode 100644 index 0000000000000000000000000000000000000000..0f9551a3ac87cc939f2c65338d38e907c219d20e --- /dev/null +++ b/install_rsc_disabling_mfa.md @@ -0,0 +1,49 @@ +# Disabling MFA + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_disabling_mfa.html + +--- + +# Disabling MFA + +Disable multi-factor authentication for newly registered clusters. + +## Before you begin + +Register the Rubrik cluster to the point where you see the Access Cluster button as described in [Registering Rubrik clusters using the online method](registering_clusters_online.html "When internet connectivity is available, register your Rubrik cluster using the online method.") and [Registering Rubrik clusters using the offline method](registering_clusters_offline.html "Use the offline registration method when the cluster cannot establish a connection with Rubrik Security Cloud."). + +## About this task + +Rubrik recommends using multi-factor authentication (MFA) on a Rubrik cluster to increase the security of your data. Complete this task only when you do not want to follow that recommendation. The task picks up from the point in the registration process where the Access Cluster button appears. + +## Procedure + + 1. Click Access Cluster. + +The Access Cluster button appears when the registration completes successfully. + +A Security Notice dialog box appears, prompting you to configure and apply time-based, one-time password (TOTP)-based MFA settings. + + 2. Click Options. + +The Two-step Verification Options dialog box appears. + + 3. Turn off the Global Enforcement toggle. + +The Security Warning dialog box opens, prompting for a confirmation to disable global MFA enforcement. + + 4. In Confirmation Text, enter `Disable`. + 5. Click Confirm. + +The Security Warning dialog box closes. + + 6. In Two-step Verification Options, click Continue. + +## Results + +You are redirected to RSC. + +## What to do next + +When the selected service type is Rubrik Security Cloud (SaaS), verify that the Rubrik cluster appears on the Clusters page of RSC. + *[ > ]: and then diff --git a/install_rsc_enabling_mfa.md b/install_rsc_enabling_mfa.md new file mode 100644 index 0000000000000000000000000000000000000000..7b60c691c75ac532180d50c0091a72296a6e5f1d --- /dev/null +++ b/install_rsc_enabling_mfa.md @@ -0,0 +1,77 @@ +# Enabling MFA + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_enabling_mfa.html + +--- + +# Enabling MFA + +Enable multi-factor authentication for newly registered clusters. + +## Before you begin + +Register the Rubrik cluster to the point where you see the Access Cluster button as described in [Registering Rubrik clusters using the online method](registering_clusters_online.html "When internet connectivity is available, register your Rubrik cluster using the online method.") and [Registering Rubrik clusters using the offline method](registering_clusters_offline.html "Use the offline registration method when the cluster cannot establish a connection with Rubrik Security Cloud."). + +## About this task + +Rubrik recommends using multi-factor authentication (MFA) on a Rubrik cluster to increase the security of your data. Complete this task to follow that recommendation. The task picks up from the point in the registration process where the Access Cluster button appears. + +## Procedure + + 1. Click Access Cluster. + +The Access Cluster button appears when the registration completes successfully. + +A Security Notice dialog box appears, prompting you to configure and apply time-based, one-time password (TOTP)-based MFA settings. + + 2. Choose a configuration option. + * Click Enable Globally to enable MFA on the cluster by scanning a QR code. + * Click Options to configure MFA options before enabling it on the cluster. + 3. (For Options) In Two-step Verification Options, configure MFA settings. + 4. Turn on the Global Enforcement toggle. + +This requires a time-based, one-time password (TOTP) to authenticate a user to the cluster for all local and LDAP login attempts. + + 5. **Optional:** Turn on the Two-Step Reminders toggle. + +This reminds you to configure Two-step Verification for Rubrik accounts at login. + +When global enforcement is active, reminders are not displayed even when the Two-Step Reminders toggle is turned on. + + 6. In Remember Device (Days), enter an integer. + +The integer specifies the number of days that the Rubrik cluster accepts the device as verified. After a successful login, users that select Remember this device at login are not asked to provide a valid TOTP for the specified number of days. A value of zero requires a valid TOTP at every login. + + 7. Click Continue. + +The Multifactor Authentication dialog box appears with a QR code. + + 8. Launch the authenticator app on your device and add a new account. + +The app opens the camera on the device. + + 9. Focus the camera on the QR code. + +If your device cannot scan a QR code, you can click Copy on the Multifactor Authentication dialog box to copy the code to your clipboard and view a setup key for manually enrolling the account on your device. + +The authenticator app adds a new account on the device and displays a TOTP. + + 10. In Verification Code, enter the TOTP. + 11. Click Done. + +The Multifactor Authentication dialog box displays a success message. + + 12. Click Finish. + +The End User License Agreement for using Rubrik products appears. + + 13. Read the terms and conditions of the agreement and click Accept. + +## Results + +You are redirected to RSC. + +## What to do next + +When the selected service type is Rubrik Security Cloud (SaaS), verify that the Rubrik cluster appears on the Clusters page of RSC. + *[ > ]: and then diff --git a/install_rsc_resolving_cluster_regn_issues.md b/install_rsc_resolving_cluster_regn_issues.md new file mode 100644 index 0000000000000000000000000000000000000000..2e0e8f9710a3fcb8fe798b4559c3aca2b7bd0130 --- /dev/null +++ b/install_rsc_resolving_cluster_regn_issues.md @@ -0,0 +1,42 @@ +# Resolving cluster registration issues + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_resolving_cluster_regn_issues.html + +--- + +# Resolving cluster registration issues + +Provide the Rubrik Support team secure and time-limited access to the cluster for assistance with resolving issues faced during cluster registration with Rubrik Security Cloud. + +## Before you begin + + * Make sure your node is entitled. + * Contact Rubrik Support. [Support](../reuse/support.html "Use one of the following methods to contact Rubrik Support.") lists the methods you can use to contact the support team. + +## About this task + +If you have an issue when registering a Rubrik cluster from the Register your cluster with Rubrik page, follow the steps in this task to get help from Rubrik Support. + +## Procedure + + 1. Click Having trouble? Get help from Rubrik Support. + +A page appears with controls you can use to allow Rubrik Support to have access to the Rubrik cluster and help with resolving the registration issue. + + 2. Turn on the Enable Support Tunnel toggle. + 3. Enter a duration, in hours, for the support tunnel. + +The support tunnel automatically closes after the specified number of hours. Click Close Support Tunnel to close the support tunnel before the specified duration elapses. + + 4. **Optional:** In Configure Internet Proxy, configure the details of a proxy server. + +When the Rubrik cluster cannot connect to the internet directly, the proxy server enables connecting the Rubrik cluster with Rubrik Security Cloud to complete the registration process. + + 5. Click Enable Support Tunnel. + +The support tunnel opens and the Register your cluster with Rubrik page re-appears with the details of the open support tunnel. + +## Results + +Support tunnel is opened to enable Rubrik Support to assist you with the registration process. + *[ > ]: and then diff --git a/install_rsc_service_types.md b/install_rsc_service_types.md new file mode 100644 index 0000000000000000000000000000000000000000..8870139a8d9cae4c1ccf9aaac602a4ee7cb5d8b8 --- /dev/null +++ b/install_rsc_service_types.md @@ -0,0 +1,17 @@ +# Rubrik Security Cloud service types + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_service_types.html + +--- + +# Rubrik Security Cloud service types + +Rubrik Security Cloud offers two distinct service types, SaaS mode and software mode, which provide different sets of functionality. + +Rubrik Security Cloud (RSC) can be configured in SaaS mode or software mode. + +RSC in SaaS mode provides many benefits through a unified control plane across multiple Rubrik clusters. The benefits of SaaS mode include a common UI, security layer and RBAC, common policy management, and reporting. Rubrik Security Cloud in SaaS mode cannot be converted to the software mode. + +If Rubrik Security Cloud becomes temporarily unavailable, the Rubrik cluster UI offers a recovery mode to handle critical tasks such as restoring data from a backup. + +RSC in software mode provides standalone, on-premises access to Rubrik CDM for data protection and recovery. The software mode uses appliances provided by Rubrik or selected compatible hardware. RSC in software mode provides a UI on the Rubrik cluster for your management tasks. diff --git a/install_rsc_unified_cluster_regn.md b/install_rsc_unified_cluster_regn.md new file mode 100644 index 0000000000000000000000000000000000000000..512111f9511c8f5d2ed4e2e28699edaa35204a6a --- /dev/null +++ b/install_rsc_unified_cluster_regn.md @@ -0,0 +1,25 @@ +# Unified cluster registration + +Source: https://docs.rubrik.com/en-us/saas/install/rsc_unified_cluster_regn.html + +--- + +# Unified cluster registration + +The unified cluster registration process applies to all types of Rubrik cluster deployments. + +Rubrik Security Cloud manages and protects data on single-node and multi-node Rubrik clusters running on physical hardware and running in public clouds. + +Deployments that Rubrik Security Cloud can manage include: + + * Data center deployments, with Rubrik clusters running on Rubrik appliances or on other industry-standard hardware. + * Remote site deployments, with virtual appliance instances running on remote site hypervisors. + * Public cloud deployments, with Rubrik clusters running in a public cloud. + * Data center virtualization deployments, with Rubrik Virtual Clusters running on data center hypervisors. + +Rubrik Security Cloud employs a unified registration process for all types of Rubrik cluster deployments. The unified cluster registration process offers many benefits, including: + + * Eliminating the need to register Rubrik Virtual Clusters through the Rubrik Support portal. + * Eliminating the CLI entitlement requirement for third party hardware nodes before configuration can be accomplished. With unified registration, registering the cluster with Rubrik Security Cloud automatically entitles the nodes. + + *[ > ]: and then diff --git a/install_setting_up_rubrik_cluster_VLAN_using_cli.md b/install_setting_up_rubrik_cluster_VLAN_using_cli.md new file mode 100644 index 0000000000000000000000000000000000000000..8d3121376e7d602c1e5ae409ab551ef937d8542d --- /dev/null +++ b/install_setting_up_rubrik_cluster_VLAN_using_cli.md @@ -0,0 +1,142 @@ +# Setting up a Rubrik cluster with VLAN using the CLI + +Source: https://docs.rubrik.com/en-us/saas/install/setting_up_rubrik_cluster_VLAN_using_cli.html + +--- + +# Setting up a Rubrik cluster with VLAN using the CLI + +Set up a Rubrik cluster using the Rubrik CLI and provide VLAN support. VLAN support allows you to set up logical segmentation and management of network traffic. + +## Before you begin + +Ensure that you have installed the Rubrik CDM software on all of the nodes that will be part of the cluster. + +## About this task + +Setting up a Rubrik cluster using the CLI is an alternative to the preferred method of setting the cluster up by using the UI. This setup task configures a new Rubrik cluster to use IPv4 and to provide VLAN support. You must choose the IPv4 internet protocol for the Rubrik cluster if you want to enable VLAN support. You initially connect to a node using SSH over IPv6. This permits a connection with the node before an IP address has been assigned. Connection to the node is established through the mDNS hostname of the node. After the IPv6 connection to the node is established, you can start the setup over either bond0 or bond1. However, the setup requires a connection on bond0 and full IPv4 network connectivity to complete. + +## Procedure + + 1. Use SSH over IPv6 to connect to a node. + + ssh -6 admin@node_serial_number.local + +Where `node_serial_number` is the serial number of a Rubrik appliance node. You can retrieve the serial number of the node from the sticker attached to the node or by connecting directly to the node and running network ifconfig from the Rubrik CLI. + + 2. At the username prompt, enter `admin`. + 3. At the password prompt, enter `rubrik`. + +The Rubrik CLI prompt appears. + + 4. Start node discovery. + +Enter: + + cluster discover + +The command lists nodes that are available on the same network segment. + + 5. Select an internet protocol for the cluster. + * To start setting up your Rubrik cluster to use IPv4, enter `cluster bootstrap` + * To start setting up your Rubrik cluster to use IPv6, enter`cluster bootstrap --ipv6` + * To skip IPMI setup, enter `cluster bootstrap --skipIpmiSetup` + +When you choose to skip IPMI configuration while setting up the Rubrik cluster with VLAN using the CLI, you cannot manage IPMI configuration using Rubrik CDM. To configure IPMI, you can choose not to enter the `cluster bootstrap --skipIpmiSetup` flag, and you will receive a prompt to enter the details for IPMI Gateway and IPMI Subnet Mask in the subsequent steps. + +Virtual platforms do not support the IPMI configuration. + +The installer starts the IPv4 setup. + + 6. At Input your role:, enter a role number from the list of options. + 7. At E-mail, enter a valid email address. + +The Rubrik cluster sends messages for the admin account to this email address. + + 8. At Password, enter a password for the admin account. + +The password must be at least eight characters and no more than 1000 characters. + +Store the password in a secure location. + +The password entered in this step becomes the new password for the default admin account. + + 9. At Re-enter Password, re-enter the password. + +The Cluster configuration section appears. + + 10. At Cluster name, enter a name for the Rubrik cluster. + 11. At DNS Nameservers, enter a comma-separated list of IP addresses for the DNS servers. + +Optionally, you can click Enter to accept the default DNS server 8.8.8.8, which is the Google DNS server. + + 12. **Optional:** At DNS Search Domains, enter a comma-separated list of search domains. + 13. At NTP Servers, provide the FQDN or IP address for each NTP server. + +Optionally, you can click Enter to accept the default NTP server pool.ntp.org, which is the virtual cluster of NTP servers provided for public use by the NTP Pool Project. + +If you see an invalid NTP server configuration message, you must correct the NTP server settings. An invalid NTP server will prevent you from connecting with vCenter servers, Windows hosts, and Linux hosts. + + 14. At Management Gateway, enter the IP address assigned to the Management Network Gateway. + +What you enter depends on whether you will separate the data network from the management network. If you will separate them, then enter the gateway address for the management network. If you will combine them, then enter the gateway address to be used by both. + + 15. At Management Subnet Mask, enter the subnet mask for the Management Network. + 16. At Management VLAN, enter a unique VLAN tag for the Management Network VLAN. + +Enter an integer from 2 to 4094. + + 17. (IPMI) At IPMI Gateway, enter the IP address assigned to the IPMI gateway. + 18. (IPMI) At IPMI Subnet Mask, enter the subnet mask for the IPMI subnet. + 19. **Optional:** At Data Subnet Mask, enter the data subnet mask. + +Entering a subnet mask value here will separate the data network from the management network. Leaving the prompt empty will combine the data network with the management network and use the value provided for the management network. Entering a subnet mask for the Data Network configures the Data Network to bond on the Data Network sockets, and the Management Network to bond on the Management Network sockets. + +The addition of the Data Subnet Mask causes the Data VLAN prompt to appear. + + 20. **Optional:** At Data VLAN, enter a unique VLAN tag for the Data VLAN. + +Enter an integer from 2 to 4094. + + 21. At Data Gateway, enter the gateway for the data network. + +If the data network will share the same gateway as the management network, then enter the value 0.0.0.0. + +If the data network is separate from the management network, then enter an IP address for the Data Gateway. Use an IP address value that meets the requirements of the internet protocol you selected for the cluster. + + 22. **Optional:** At Enable Software Encryption, enter `y` to enable software-based encryption of the data at rest. + +This option will only appear for Rubrik appliance models that have the hardware Trusted Platform Module (TPM). + +Node Configuration appears with a list of the discovered nodes. + + 23. From the list of discovered nodes select a node index number or node name and enter it. + +This step initiates the setup task on the selected node. Provide the network details for the selected node and then select another, until all of the nodes for the cluster have been set up. After a node is set up an asterisk (*) appears next to it in the listing. + +All nodes are set up and you see an asterisk by each node that you want to be part of the cluster. + + 24. Press Enter. + +The installer displays the nodes and their configurations in JSON format. + + 25. Enter `y` to confirm the nodes and settings and proceed with the installation. + +The installer returns to the Rubrik CLI prompt while the installation proceeds. Bootstrap is automatically triggered after the software is successfully installed on all of the nodes. + + 26. **Optional:** Use status watch to check the status of the setup. + +Enter: + + cluster bootstrap status watch + +The installer displays the current status, pending tasks, completed tasks, and messages for the installation. + +## Results + +The installer completes the setup process and joins the nodes into a running Rubrik cluster. + +## What to do next + +Register the Rubrik cluster. + *[ > ]: and then diff --git a/install_setting_up_rubrik_cluster_using_cli.md b/install_setting_up_rubrik_cluster_using_cli.md new file mode 100644 index 0000000000000000000000000000000000000000..51876659d3248f353b3d7b136a21f6be29fecada --- /dev/null +++ b/install_setting_up_rubrik_cluster_using_cli.md @@ -0,0 +1,149 @@ +# Setting up a Rubrik cluster using the CLI + +Source: https://docs.rubrik.com/en-us/saas/install/setting_up_rubrik_cluster_using_cli.html + +--- + +# Setting up a Rubrik cluster using the CLI + +Use the Rubrik CLI to set up a new Rubrik cluster. + +## Before you begin + +Ensure that you have installed the Rubrik CDM software on all of the nodes that will be part of the cluster. + +This task does not describe how to set up the data VLAN. Instead, follow the steps in [Setting up a Rubrik cluster using the UI](setting_up_rubrik_cluster_using_ui.html "Set up a Rubrik cluster using the system setup UI provided on a node.") or [Setting up a Rubrik cluster with VLAN using the CLI](setting_up_rubrik_cluster_VLAN_using_cli.html "Set up a Rubrik cluster using the Rubrik CLI and provide VLAN support. VLAN support allows you to set up logical segmentation and management of network traffic.") when you require a Rubrik cluster with VLAN support. + +## About this task + +Setting up a Rubrik cluster using the CLI is an alternative to the preferred method of setting up the cluster up by using the UI. + +You must initially connect to a node using SSH over IPv6. This permits a connection with the node before an IP address has been assigned. Connection to the node is established through the mDNS hostname of the node. As part of this setup task you can choose to configure the Rubrik cluster to communicate using either the IPv4 or the IPv6 internet protocol. + +## Procedure + + 1. Use SSH over IPv6 to connect to one of the Rubrik appliance nodes. + + ssh -6 admin@node_serial_number.local + +Where `node_serial_number` is the serial of a Rubrik appliance node. You can retrieve the serial number of the node from the sticker attached to the node or by connecting directly to the node and running network ifconfig from the Rubrik CLI. + + 2. At the username prompt, enter `admin`. + 3. At the password prompt, enter `rubrik`. + +The Rubrik CLI prompt appears. + + 4. Start node discovery. + +Enter: + + cluster discover + +The command lists nodes that are available on the same network segment. + + 5. Select an internet protocol for the cluster. + * To start setting up your Rubrik cluster to use IPv4, enter `cluster bootstrap` + * To start setting up your Rubrik cluster to use IPv6, enter `cluster bootstrap --ipv6` + * To skip IPMI setup, enter `cluster bootstrap --skipIpmiSetup` + +When you choose to skip IPMI configuration while setting up the Rubrik cluster using CLI, you cannot manage IPMI configuration using Rubrik CDM. To configure IPMI, you can choose not to enter the `cluster bootstrap --skipIpmiSetup` flag, and you will receive a prompt to enter the details for IPMI Gateway and IPMI Subnet Mask in the subsequent steps. + +Virtual platforms do not support the IPMI configuration. + + 6. At Input your role:, enter the number for a role from the list of options. + 7. At E-mail, enter a valid email address. + +The Rubrik cluster sends messages for the admin account to this email address. + + 8. At Password, enter a password for the admin account. + +The password must be at least eight characters and no more than 1000 characters. + +Store the password in a secure location. + +The password entered in this step becomes the new password for the default admin account. + + 9. At Re-enter Password, re-enter the password. + +The Cluster configuration section appears. + + 10. At Cluster name, enter a name for the Rubrik cluster. + 11. At DNS Nameservers, enter a comma-separated list of IP addresses for the DNS servers. + +Optionally, you can click Enter to accept the default DNS server 8.8.8.8, which is the Google DNS server. + + 12. **Optional:** At DNS Search Domains, enter a comma-separated list of search domains. + 13. At NTP Servers, provide the FQDN or IP address for each NTP server. + +Optionally, you can click Enter to accept the default NTP server pool.ntp.org, which is the virtual cluster of NTP servers provided for public use by the NTP Pool Project. + +If you see an invalid NTP server configuration message, you must correct the NTP server settings. An invalid NTP server will prevent you from connecting with vCenter servers, Windows hosts, and Linux hosts. + + 14. At Management Gateway, enter the IP address assigned to the Management Network Gateway. + +What you enter depends on whether you will separate the data network from the management network. If you will separate them, then enter the gateway address for the management network. If you will combine them, then enter the gateway address to be used by both. + + 15. At Management Subnet Mask, enter the subnet mask for the Management Network. + +What you enter depends on the internet protocol that you selected for the cluster when starting the setup. If you selected IPv4, then enter the IPv4 subnet mask value. If you selected IPv6, then enter the integer value of the prefix length. + +For IPv4 setup, the optional Management VLAN step appears. Leave the prompt empty and press Enter to continue setup. + + 16. (IPMI) At IPMI Gateway, enter the IP address assigned to the IPMI gateway. + +Use an address that complies with the internet protocol you selected, either IPv4 or IPv6. + + 17. (IPMI) At IPMI Subnet Mask, enter the subnet mask for the IPMI subnet. + +What you enter depends on the internet protocol that you selected for the cluster when starting the setup. If you selected IPv4, then enter the IPv4 subnet mask value. If you selected IPv6, then enter the integer value of the prefix length. + + 18. **Optional:** At Data subnet mask, enter the subnet mask for the data network. + +Entering a subnet mask value here will separate the data network from the management network. Leaving the prompt empty will combine the data network with the management network and use the value provided for the management network. Entering a subnet mask for the Data Network configures the Data Network to bond on the Data Network sockets, and the Management Network to bond on the Management Network sockets. + +If you choose to enter a value, what you enter depends on the internet protocol that you selected for the cluster when starting the setup. If you selected IPv4, then enter the IPv4 subnet mask value. If you selected IPv6, then enter the integer value of the prefix length. + +For IPv4 networks, providing a value will cause the Data VLAN prompt to display. Leave that field empty and press enter to continue the setup. + + 19. At Data Gateway, enter the gateway for the data network. + +If the data network will share the same gateway as the management network, then enter the value 0.0.0.0. + +If the data network is separate from the management network, then enter an IP address for the Data Gateway. Use an IP address value that meets the requirements of the internet protocol you selected for the cluster. + + 20. **Optional:** At Enable Software Encryption, enter `y` to enable software-based encryption of the data at rest. + +This option will only appear for Rubrik appliance models that have the hardware Trusted Platform Module (TPM). + +Node Configuration appears with a list of the discovered nodes. + + 21. From the list of discovered nodes, select a node index number or node name and enter it. + +This step initiates the setup task on the selected node. Provide the network details for the selected node and then select another, until all of the nodes for the cluster have been set up. After a node is set up an asterisk (*) appears next to it in the listing. + +All nodes are set up and you see an asterisk by each node that you want to be part of the cluster. + + 22. Press Enter. + +The installer displays the nodes and their configurations in JSON format. + + 23. Enter `y` to confirm the nodes and settings and proceed with the installation. + +The installer returns to the Rubrik CLI prompt while the installation proceeds. Bootstrap is automatically triggered after the software is successfully installed on all of the nodes. + + 24. **Optional:** Use status watch to check the status of the setup. + +Enter: + + cluster bootstrap status watch + +The installer displays the current status, pending tasks, completed tasks, and messages for the installation. + +## Results + +The installer completes the setup process and joins the nodes into a running Rubrik cluster. + +## What to do next + +Register the Rubrik cluster. + *[ > ]: and then diff --git a/install_setting_up_rubrik_cluster_using_ui.md b/install_setting_up_rubrik_cluster_using_ui.md new file mode 100644 index 0000000000000000000000000000000000000000..403c047525e49966af6faddeaf3196283d3af42a --- /dev/null +++ b/install_setting_up_rubrik_cluster_using_ui.md @@ -0,0 +1,141 @@ +# Setting up a Rubrik cluster using the UI + +Source: https://docs.rubrik.com/en-us/saas/install/setting_up_rubrik_cluster_using_ui.html + +--- + +# Setting up a Rubrik cluster using the UI + +Set up a Rubrik cluster using the system setup UI provided on a node. + +## Before you begin + +Ensure that you have installed the Rubrik CDM software on all of the nodes that will be part of the cluster. + +## About this task + +To set up all the nodes in a Rubrik cluster, connect to any node. Use the UI to provide the required information and complete the setup. In most cases, the UI is the recommended interface to use when setting up a Rubrik cluster. + +## Procedure + + 1. Determine the mDNS hostname of one of the Rubrik nodes. + +The mDNS hostname of a Rubrik node is the serial number of the node, with .local appended to it. + +For example, if the node serial number is RBK34DC56789012, the mDNS hostname of the node would be: + + RBK34DC56789012.local + + 2. Use the mDNS hostname of a node to access the node in your web browser. + +In the address field of the web browser, enter: + + https://node_serial_number.local + +Where node_serial_number is the node serial number. + +The Welcome page appears. + + 3. Click Start Setup. + +The setup wizard discovers the nodes available for the Rubrik cluster. After node discovery, the Node Configuration page appears with the each node listed in Rubrik appliance sections. + + 4. Select an internet protocol. + * IPv6 + * IPv4 + +Your selection determines the internet protocol used by the Rubrik cluster for network communication. + + 5. **Optional:** Turn on Use IPMI (out-of-band-management) to use IPMI configuration for nodes. + +Virtual platforms do not support the IPMI configuration. + +When you turn on Use IPMI (out-of-band-management), the IPMI (out-of-band-management) field will be available on the Node Configuration page. On the Network Configuration page, the Subnet Mask and IP address fields for IPMI will be available. + + 6. **Optional:** Click Separate management and data. + +Use this option if you want the data network and the management network to use separate bonding interfaces. The data network must use bond0. + +The IP address fields for each node split into separate management and data fields, allowing configuration of a separate data network on bond0. + + 7. **Optional:** (IPv4 only) Click Auto populate IP addresses. + +The Auto IP Setup wizard opens so that you can arrange the nodes in the required sequence and assign IP addresses to the first node listed. The wizard then uses that information to assign IP addresses sequentially to the other nodes. + + 8. For each Rubrik appliance that will be part of the cluster, turn on Include in cluster. + 9. **Optional:** For each Rubrik appliance, click X adjacent to each node that should be removed from the cluster. + 10. For each node, provide the requested IP addresses. + +Using the internet protocol that you selected, either IPv4 or IPv6, provide addresses for that node in Management & Data, or Management (Bond1) and Data (Bond0), and in IPMI. + + 11. Click Next. + +The Network Configuration page appears. + + 12. In DNS IPs, enter the name of a DNS server for the cluster to use. + +You can add additional DNS servers by clicking the +. + +Optionally, you can accept the default DNS server IP, 8.8.8.8, which is the Google DNS server. + + 13. **Optional:** In DNS Search Domains, enter a DNS search domain name for the cluster to use. + +You can add additional search domains by clicking the +. + + 14. In NTP Server Names, enter a NTP server name for the cluster to use. + +You can add additional NTP servers by clicking the +. + +Optionally, you can accept the address of the default NTP server, pool.ntp.org. This address identifies the virtual cluster of NTP servers provided for public use by the NTP Pool Project. + + 15. In Management and Data Network (Bond 0) or in Management (Bond1) and Data (Bond0), enter the management and data network information. + +The management and data network interface information for the Rubrik cluster includes a subnet mask, an IP address, and, when you have selected IPv4, a VLAN ID. What you enter depends on the internet protocol that you selected for the cluster. If you selected IPv6, then enter the integer value of the prefix length. If you selected IPv4, then enter the IPv4 subnet mask value. Also, when you selected IPv4, you can optionally set a VLAN tag for the interface. This must be an integer from 2 to 4094. + + 16. (IPMI) In IPMI, enter the subnet mask and gateway IP address. + +The Subnet Mask and Gateway IP address fields are available only when you turn on IPMI (out-of-band-management) on the Node Configuration page. + + 17. Click Next. + +The Cluster Settings page appears. + + 18. In Cluster Name, enter a name. + +The name identifies the Rubrik cluster in Rubrik Security Cloud. + + 19. In Admin Account Email, enter an administrator account email address. + +The admin account is the primary local account with administrator privileges. You use the credentials for the account to log in to the Rubrik cluster after the initial configuration and registration of the cluster. + +The default value of the username for the account is 'admin' and cannot be changed through the UI. + + 20. In Enter Password, enter an administrator password. + 21. In Re-enter Password, reenter the administrator password. + +Store the password in a secure location. + + 22. In What is your role?, select a role. + * Customer + * Support + * Professional Service + * Partner + * Sales Engineer + 23. In Choose Software Version, select a version of the Rubrik CDM software to be used by the cluster. + +The version that is pre-installed is identified. Any other versions that have been installed and staged on the nodes will also appear in the list. Selecting a version other than the version that is pre-installed will add approximately 30 minutes to the configuration process. + + 24. Click Next. + +The installer completes the software installation and configuration on all of the selected nodes. This procedure includes running bootstrap pre-checks, installing the software, configuring the cluster, and starting the networking processes. A completion page appears after the successful installation and configuration. + + 25. Enter the account name and password for the admin account and click Sign in. + +## Results + +The configuration wizard completes the Rubrik cluster configuration and the cluster registration page appears. + +## What to do next + +Continue through the wizard to register your Rubrik cluster using the online or offline method. + *[ > ]: and then diff --git a/install_shutting_down_a_node.md b/install_shutting_down_a_node.md new file mode 100644 index 0000000000000000000000000000000000000000..a388aa6f99505908cc6cd227635b0ac4cb142331 --- /dev/null +++ b/install_shutting_down_a_node.md @@ -0,0 +1,36 @@ +# Shutting down a node + +Source: https://docs.rubrik.com/en-us/saas/install/shutting_down_a_node.html + +--- + +# Shutting down a node + +The node shutdown process powers down a specific node in a Rubrik cluster. + +## Procedure + + 1. Open an SSH connection to the node. + +In a terminal session, enter: + + ssh admin@node_ip + +Where node_ip is the IP address of the Rubrik cluster node to be shut down. + + 2. Enter the password. + +You must provide the authentication credentials for the admin account on the Rubrik cluster to display the Rubrik CLI prompt. + + 3. Enter `cluster poweroff_node`. + +The poweroff confirmation prompt appears: + +Warning: This operation will power off the node, any running jobs will be terminated!!! + + 4. Enter `yes`. + +## Results + +The Rubrik cluster performs a graceful power down of the selected node. + *[ > ]: and then diff --git a/install_shutting_down_rubrik_cluster.md b/install_shutting_down_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..014284b4da80d634e77d2f7c4d9a347e013cc8a8 --- /dev/null +++ b/install_shutting_down_rubrik_cluster.md @@ -0,0 +1,45 @@ +# Shutting down the Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/install/shutting_down_rubrik_cluster.html + +--- + +# Shutting down the Rubrik cluster + +To power down all the nodes in a Rubrik cluster, shut down the cluster using CLI. + +## Before you begin + +Shutting down a cluster requires administrator privileges. + +## Procedure + + 1. In a terminal window, enter: + +`ssh admin@node_ip` + +where node_ip is the IP address of a Rubrik cluster node. + + 2. Enter the password. + +To display the Rubrik CLI prompt, provide the authentication credentials for the administrator account on the Rubrik cluster. + + 3. Enter `cluster poweroff_cluster`. + +Select an option to shut down the cluster: + +Option| Description +---|--- +`cluster poweroff_cluster` with no option | Performs a node status check before shutting down all nodes in the Rubrik cluster.This command also terminates all the running jobs while shutting down a cluster. +`cluster poweroff_cluster` with `-–skip_node_status_check`option | Shuts down the cluster without performing a status check on the nodes.This option shuts down only the nodes that Rubrik cluster can reach. These nodes need not have an OK status to be shut down, but they must be reachable to return any status. + +The Rubrik cluster cannot send commands to nodes it cannot reach or communicate with. + +A warning that this operation powers off the cluster and terminates running jobs appears. + + 4. Enter `Yes` to confirm the shutdown. + +## Results + +The Rubrik cluster performs a graceful power down of all nodes and terminates all the jobs running on the nodes. + *[ > ]: and then diff --git a/install_system_shutdown.md b/install_system_shutdown.md new file mode 100644 index 0000000000000000000000000000000000000000..a7a99ec225ee9f24e8be45675dfab358818df872 --- /dev/null +++ b/install_system_shutdown.md @@ -0,0 +1,11 @@ +# System shutdown + +Source: https://docs.rubrik.com/en-us/saas/install/system_shutdown.html + +--- + +# System shutdown + +A system shutdown can be done from the Rubrik CLI. + +Typical operation of a Rubrik cluster does not require a system shutdown, but is occasionally necessary for business purposes or at the request of Rubrik Support. diff --git a/install_upgrade_to_rubrik_security_cloud.md b/install_upgrade_to_rubrik_security_cloud.md new file mode 100644 index 0000000000000000000000000000000000000000..6bc8dac2cde1c1dfeb728471ed3058f31e29113a --- /dev/null +++ b/install_upgrade_to_rubrik_security_cloud.md @@ -0,0 +1,28 @@ +# Polaris to RSC upgrade + +Source: https://docs.rubrik.com/en-us/saas/install/upgrade_to_rubrik_security_cloud.html + +--- + +# Polaris to RSC upgrade + +Rubrik Security Cloud provides a unified user interface to manage all your Rubrik tasks. + +Upgrading to Rubrik Security Cloud (RSC) provides: + + * Global dashboard for an overview of data health and security + * Data Security Command Center (DSCC) to identify security gaps and provide recommendations for improving data security status + * Cluster dashboard offering meaningful insights into individual cluster health + * Unified user interface for managing all data center, cloud, and SaaS workloads + * Global search capability across RSC + * Ability to create and schedule custom reports or use predefined reports + +When you login to the Polaris web UI, a dialog box appears on the screen, prompting you to upgrade to the RSC experience. The upgrade dialog box provides an overview of the RSC upgrade and its capabilities. The dialog box does not prevent you from performing any operations. To learn more about the upgrade, you can watch the overview video or refer to the RSC upgrade documentation. + +The RSC upgrade is instantaneous and does not need any scheduled downtime. Rubrik cluster backups will continue as configured. Once upgraded, you can use RSC for daily operations. You can also upgrade SLA Domains created on a Rubrik cluster to RSC SLA Domains as required for centralized management. + +Limitations of RSC management are as follows: + + * Configuring the two-person rule (TPR) for changes or actions cannot be completed using RSC. These actions require Rubrik CDM workflows. + * Adding NAS systems managed in Rubrik CDM to RSC will trigger a new full backup and cause duplicate data protection of the NAS system. You can add the NAS host to RSC when the storage overhead is acceptable or continue to manage NAS hosts using Rubrik CDM. + diff --git a/install_upgrading_to_rubrik_security_cloud.md b/install_upgrading_to_rubrik_security_cloud.md new file mode 100644 index 0000000000000000000000000000000000000000..7a8dadfce21ada5d67f89f7ebe064537f83efdfc --- /dev/null +++ b/install_upgrading_to_rubrik_security_cloud.md @@ -0,0 +1,43 @@ +# Upgrading Polaris to RSC + +Source: https://docs.rubrik.com/en-us/saas/install/upgrading_to_rubrik_security_cloud.html + +--- + +# Upgrading Polaris to RSC + +To ensure you have the latest security features, you can choose to upgrade from Polaris to Rubrik Security Cloud manually or let an automatic upgrade occur based on the scheduled date displayed in the notification banner. + +## About this task + +Experience an enhanced functionality by upgrading to the latest version, which provides a unified dashboard. This comprehensive interface enables you to efficiently manage all your Rubrik tasks within a single user interface. + +Note: + +If you are in the process of upgrading to Rubrik Security Cloud, the extension period for the upgrade will remain valid for up to 15 days. + +## Procedure + + 1. Log in to the Polaris web UI. + 2. Click Upgrade Now. + +The upgrade to RSC initiates immediately. + + 3. Select the following options. + * Click Postpone upgrade until July 31, 2023 to postpone the upgrade. + * Click Got It to dismiss the auto upgrade dialog box and persistent notification banner appears at the top of the page. This banner notifies you about the upcoming auto upgrade, displaying the specific number of days for the upgrade to occur. + 4. Click Learn More. + +Clicking this option from the notification banner allows you to bring back the upgrade dialog box. + +The Upgrade to Rubrik Security Cloud dialog box appears. + + 5. Click the navigation buttons to review all the features of RSC. + +If the Upgrade to Rubrik Security Cloud dialog box is closed, a notification banner at the top will display the countdown of days remaining for the automatic upgrade. + +## Results + +You will successfully initiate the automatic upgrade process to Rubrik Security Cloud or postpone the upgrade until the specified date, based on your preference. Rubrik CDM and Data Protection configurations are retained and backup, archival, and replication tasks continue as set up. + +You can upgrade SLA Domains created on a Rubrik cluster to RSC SLA Domains as required and manage them. diff --git a/install_vlan_tagging_cluster_mgmt_networks.md b/install_vlan_tagging_cluster_mgmt_networks.md new file mode 100644 index 0000000000000000000000000000000000000000..0ba881c729d175cfe5457a2bc0eb6c0952f05652 --- /dev/null +++ b/install_vlan_tagging_cluster_mgmt_networks.md @@ -0,0 +1,43 @@ +# VLAN tagging Rubrik cluster management and data networks + +Source: https://docs.rubrik.com/en-us/saas/install/vlan_tagging_cluster_mgmt_networks.html + +--- + +# VLAN tagging Rubrik cluster management and data networks + +You can add VLAN tagging to a Rubrik cluster to help manage network traffic. + +IPv4 deployments of Rubrik CDM can optionally use Virtual Local Area Networks (VLAN) tagging on a Rubrik cluster to switch network traffic efficiently using VLAN tagging. + +You can configure VLAN tagging either to include or exclude tagging on the Rubrik side. + +Table 1. VLAN tagging configuration on the Rubrik side Option | Requirements +---|--- +VLAN tagging in use on Rubrik side | + + * Switch ports are set to Trunk ports. + * During bootstrapping, IP addresses were entered under the Management network. + * VLAN integers are specified. + + +VLAN tagging not in use on Rubrik side | + + * During bootstrapping, IP addresses were entered under the Management network. + * No VLAN integers are specified. + * Switch ports are connected to the Rubrik nodes as Access ports, resulting in no VLAN tagging, or are configured as Native VLAN, resulting in native-only VLAN tagging.Native VLAN configures the Rubrik side under the bond0 interface. This interface covers both management and data traffic. + + + +Each VLAN is partitioned and isolated at the data link layer. VLAN tags applied to network packets allow separating the network traffic of some applications on a physical network from the network traffic of other applications on the same physical network. + +In enterprise data centers, VLAN tagging is typically used to segregate network traffic according to organizational group, application type, or security policy. Segregating network traffic using VLAN tagging can optimize network throughput and promote data security. + +To enable VLAN tagging, you can use either the UI method or the CLI method to install and configure the software. The VLAN tag must be unique within the network trunk. Many switches reserve VLAN 1 for the default native VLAN. To avoid conflicts with this setting, a valid VLAN tag in the node configuration can be any integer from 2 to 4094. + +You can use the optional Data Subnet Mask and Data VLAN parameters to create separate networks for the Management Network and the Data Network. When you enter a Data Network subnet mask, the Management Network and Data Network do not share the same network connections. You can establish a network connection by physically connecting separate cables for both the Management Network and the Data Network. + +When the Management Network and Data Network share the same r6000 10 GbE or 25 GbE network connection, you can bypass the optional Data Subnet Mask and Data VLAN parameters in the CLI. + +You can separate traffic into distinct interfaces on a Split Network. To do this, both the bond0 interface and the bond1 interface must be physically connected, and you must specify both management and data networks. + *[ > ]: and then diff --git a/jira_jira.md b/jira_jira.md new file mode 100644 index 0000000000000000000000000000000000000000..a02469d22616508f92e6d3f01960560e01fd91ad --- /dev/null +++ b/jira_jira.md @@ -0,0 +1,15 @@ +# Atlassian Jira + +Source: https://docs.rubrik.com/en-us/saas/jira/jira.html + +--- + +# Atlassian Jira + +To protect your Atlassian Jira data, you can back up and restore data, such as projects, settings, workflows, and issues, in your Jira site . + +RSC protection for Atlassian Jira simplifies managing backups of Jira sites to restore Jira data when the data is either compromised or lost. Leveraging the RSC protection, you can back up and restore Jira data types such as projects and settings while keeping data relationships intact. You can automatically back up Jira data in either 12-hour or 24-hour frequencies or back up data on demand. + +You can also analyze data to determine if and when data was lost, which would help streamline investigations and recoveries. + +Jira protection is licensed per user, where the product counts all users that have access to the site being protected. diff --git a/jira_jira_adding_instance.md b/jira_jira_adding_instance.md new file mode 100644 index 0000000000000000000000000000000000000000..8233542c7cc5f30d2b1cb0a714c9632723371ccc --- /dev/null +++ b/jira_jira_adding_instance.md @@ -0,0 +1,63 @@ +# Adding an Atlassian Jira instance + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_adding_instance.html + +--- + +# Adding an Atlassian Jira instance + +Add an Atlassian Jira instance of the Jira site that you want to back up and restore. For example, you can back up and restore data types such as projects, workflows, and issues. You can add more Jira instances if your have multiple sites that you want to protect. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps Dashboard appears. + + 3. Click the inventory card for the Jira instance. + +The details page for the Jira instance appears. + + 4. Click Add instance. + +The Set Up Jira Software wizard appears. + + 5. Click Next. + +The Add a Jira instance page appears. + + 6. In Jira instane URL, enter the URL of the Jira instance you want to protect. + 7. Click Log in to authenticate to give permission for RSC to access your Atlassian data. + +A browser window appears and takes you to the Atlassian login page. + + 8. Log in to the Atlassian account with the global administrator credentials of the Jira instance. + +After a successful login, your Jira account is authenticated with RSC and the Set Up Jira Software dialog box appears. + + 9. Click Next. + +The Assign SLA Domain page appears. + + 10. In SLA Domain, select the SLA Domain to assign to your Jira instance. + +Option| Description +---|--- +Bronze lite | Performs backups every 24 hours and retains these backups for one year. +Silver lite | Performs backups every 12 hours and retains these backups for one year. +Custom SLA Domain | Provides the custom SLA Domain that you configured. + +The first full snapshot will be taken after you select the SLA Domain. + + 11. In the Storage Region dropdown list, select the region where you want to store the backup and subsequent snapshots. + 12. Click Next. + +The Confirmation dialog box appears. + + 13. Confirm your settings and click Setup. + +## Results + +The Jira account is added. RSC connects the Jira account and displays the Jira instance on the Saas Apps dashboard. + *[ > ]: and then diff --git a/jira_jira_analyzing_data.md b/jira_jira_analyzing_data.md new file mode 100644 index 0000000000000000000000000000000000000000..dec26a02d6f88efad33c258f75494c4b8216ae22 --- /dev/null +++ b/jira_jira_analyzing_data.md @@ -0,0 +1,43 @@ +# Analyzing Atlassian Jira data + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_analyzing_data.html + +--- + +# Analyzing Atlassian Jira data + +RSC provides graphs about snapshot activity for an Atlassian Jira instance that helps you analyze the point in time to use to restore data when an anomaly is detected in deleted, changed, or added issues or settings. Analyzing data helps you understand if and when data was lost and what data was lost. + +## About this task + +You can analyze Atlassian Jira data to restore settings and projects when an anomaly is detected. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps Dashboard appears. + + 3. Click the inventory card for the Jira instance. + +The details page for the Jira instance appears. + + 4. Click Analyze. + +The Changed Issues Summary graph appears, which provides information about all the added, modified, and deleted projects and issues or Jira settings on a given day. + + 5. In Data Type, select if you want to view information about projects or settings. + +Option| Description +---|--- +Project | View changes for all projects and their issues. +Settings | View changes for Jira settings. + + 6. **Optional:** Click the calendar icon in the Changed Issues Summary graph to view all the issues across all the projects in your Jira instance for the past 7 days. + 7. **Optional:** Click on a day in the Changed Issues Summary graph to view all the projects and issues or all the settings that were modified on a given day for the past 7 days. + +## Results + +RSC provides information about your data, which you can use to determine if there was data loss and also use to restore data. + *[ > ]: and then diff --git a/jira_jira_backups.md b/jira_jira_backups.md new file mode 100644 index 0000000000000000000000000000000000000000..fb17a9d12fa325f76450c04b8e208c221c4a9a1b --- /dev/null +++ b/jira_jira_backups.md @@ -0,0 +1,23 @@ +# Atlassian Jira backups + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_backups.html + +--- + +# Atlassian Jira backups + +You can securely back up your Atlassian Jira data types with snapshots and restore your data from those snapshots. You can back up data such as tasks and subtasks and restore that information if the data is compromised. + +You can back up your Atlassian Jira data automatically or on demand so that you can restore data if data is compromised by malicious activity. For backups,RSC takes snapshots of the data on your Atlassian Jira site, and you can restore your data from these snapshots. + +You can: + + * Back up and restore the following Jira data types: projects, issues, attachments, workflows, screens, permissions, sprints, boards, epics, dashboards, filters, and notifications. + +Data backup and restore also keeps relationships between Jira data types intact, for example, relationships between tasks and subtasks. + + * Automatically back up data in either 12-hour or 24-hour frequencies so that you have daily restore points. + * Compare snapshots to see the differences between snapshot data or metadata to determine which snapshot you want to restore. + * Take on-demand snapshots to back up data on-demand. + + *[ > ]: and then diff --git a/jira_jira_deleting_instance.md b/jira_jira_deleting_instance.md new file mode 100644 index 0000000000000000000000000000000000000000..49f6c1b0890a0f42f045b249105a85264c99761a --- /dev/null +++ b/jira_jira_deleting_instance.md @@ -0,0 +1,49 @@ +# Removing Jira instances + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_deleting_instance.html + +--- + +# Removing Jira instances + +Remove a Jira instance to remove all snapshots and configurations from RSC. + +## About this task + +During removal, RSC removes all snapshots of the Jira instance and deletes all existing configurations. Adding this Jira instance back to RSC requires you to complete the entire setup process again. + +If you have a quorum authorization policy configured for removing the instance, you require approval from a set of reviewers before deleting a Jira instance. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps Dashboard appears. + + 3. Click the inventory card for the Jira instance. + +The details page for the Jira instance appears. + + 4. Click and select Remove Jira Site. + +The Remove SaaS Instance dialog box appears. + + 5. Click Remove. + +If you have created a quorum authorization policy for this operation, you need to submit a request for quorum authorization. + + 6. For quorum authorization, select a run type action. + +Option| Description +---|--- +Automatically schedule | Schedules the action to automatically run after approval. +Manually schedule | Schedules the action to run within 24 hours after the approval. Actions not run 24 hours after approval will expire. + + 7. **Optional:** For quorum authorization, in Comment, enter a comment to provide additional details about the request. + 8. For quorum authorization, click Submit Request. + +## Results + +RSC initiates the removal of the Jira instance. If you have created a quorum authorization policy, RSC completes the action according to the specified run type option after the request is approved. + *[ > ]: and then diff --git a/jira_jira_instance_details.md b/jira_jira_instance_details.md new file mode 100644 index 0000000000000000000000000000000000000000..453e47b6610aa5a824b716019d59a5a931a7bba1 --- /dev/null +++ b/jira_jira_instance_details.md @@ -0,0 +1,32 @@ +# Atlassian Jira instance details + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_instance_details.html + +--- + +# Atlassian Jira instance details + +The Atlassian Jira details page helps you monitor and analyze your data to view important details, such the number of backups during a specified time period. You can also access features from the details page, such as managing protection and restoring data. + +The details page for the Atlassian Jira instance helps you monitor backup information, such as the number of changed snapshots over a period of time. You can also view details and access features. For example, you can view protection information, and you can restore data. The following table describes the different tabs on the details page. + +The following table describes the details you can view. + +Tab | Description +---|--- +Monitor | + + * Change summary displays the number of deleted, modified, and added snapshots during the past 7 or 30 days.You can select a date to view all snapshots, or you can or the select the icon for deleted, modified, or added snapshots. + * Backup jobs displays the number of backups that have failed or succeeded in the past 7 or 30 days.You can select a date to view all snapshots, or you can select the icon for deleted, modified, or added snapshots. + * Status displays whether Atlassian Jira protection is online and provides access to reauthenticating to Atlassian Jira. + * Backup Summary displays protection information and provides access to managing protection on the Jira instance. + + +Restore | + + * Restore issues provides access to restoring issues and issue types. + * Restore settings provides access to restoring settings and setting types. + + +Analyze | Provides access to analyzing data changes in snapshots, for example, the number of issues added, modified, or deleted, on a given day. + *[ > ]: and then diff --git a/jira_jira_oauth_authentication.md b/jira_jira_oauth_authentication.md new file mode 100644 index 0000000000000000000000000000000000000000..30854af901cf9f0dcbda01a4ea69a893760229c2 --- /dev/null +++ b/jira_jira_oauth_authentication.md @@ -0,0 +1,16 @@ +# Oauth authentication for Atlassian Jira site connection + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_oauth_authentication.html + +--- + +# Oauth authentication for Atlassian Jira site connection + +RSC uses OAuth to connect to the Atlassian Jira sites that you want to back up. You must use a Jira user or a Jira service account with the appropriate permissions. + +RSC connects to the Atlassian Jira sites that you want to back up with OAuth. You must use a Jira user acount or a Jira service account that has Jira organization or site privileges to back up data on the site. The account used for authorization should also have administrator access to the site. + +Tokens are exchanged between RSC and Jira, which expire after one year. After one year, you will need to reauthenticate Jira with RSC. + +As a best practice, Rubrik recommends using a Jira service account, because a user account is tied to a user. If the user account no longer exists, for example, if the user leaves the organization, backups might stop working. A user account is tied to a user and, if the user account no longer exists, backups might stop working. + *[ > ]: and then diff --git a/jira_jira_protection_sla_domain.md b/jira_jira_protection_sla_domain.md new file mode 100644 index 0000000000000000000000000000000000000000..249b126133604706499480c7bbf2336c7575a726 --- /dev/null +++ b/jira_jira_protection_sla_domain.md @@ -0,0 +1,24 @@ +# Atlassian Jira protection using SLA Domains + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_protection_sla_domain.html + +--- + +# Atlassian Jira protection using SLA Domains + +You can manage protection for Atlassian Jira sites by using SLA Domains. SLA Domains provide protection policies for your sites so that you can securely back up and restore data. + +You can assign an SLA Domain to an Atlassian Jira site to manage protection of your Jira data. With an SLA Domain, you can specify the frequency of backups and the amount of time to retain the backup snapshots. + +RSC provides the following default SLA Domains for Altassian Jira protection: + + * Bronze lite performs backup every 24 hours and retains those backups for one year. + * Silver lite performs backups every 12 hours and retains those backups for one year. + +You also have additional options for SLA Domain configuration, such as the following: + + * Creating a custom SLA Domain to specify a custom backup frequency and retention period. + * Editing and cloning SLA Domains. + * Configuring a quorum authorization policy for data management actions, which requires approval from a set of approvers for assigning a different SLA Domain to the Jira instance. + + *[ > ]: and then diff --git a/jira_jira_rbac_required_permissions.md b/jira_jira_rbac_required_permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..c8e31414b7b993accd040840aea764dd74326b00 --- /dev/null +++ b/jira_jira_rbac_required_permissions.md @@ -0,0 +1,29 @@ +# Required RBAC permissions for Atlassian Jira + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_rbac_required_permissions.html + +--- + +# Required RBAC permissions for Atlassian Jira + +Accessing Atlassian Jira protection features within RSC requires the appropriate RBAC permissions. You can use the default Jira Admin role or a custom role. + +With RBAC permissions, you can access Atlassian Jira management features within RSC. The default Jira Admin role provides all required permissions, which the following table describes, and you can also create a custom role with the following required permissions. + +Permission | Permission type +---|--- +View | View protectable objects +Protection | + + * Manage protection: Enables access to managing protection on an Atlassian Jira site by adding, modifying, or deleting a backup policy and assigning objects to policies. + * On-demand snapshots:- Enables access to taking an on-demand snapshot to back up data on demand. + + +Recover | + + * Download files: Enables access to downloading files from the File Preparation Center . + * Restore over original: Enables access to restoring data to its original location. + + +Data management source | Provides access to connect and authenticate to Jira sites. + *[ > ]: and then diff --git a/jira_jira_reauthenticate.md b/jira_jira_reauthenticate.md new file mode 100644 index 0000000000000000000000000000000000000000..13bcd0bd3d45d0cbfb223974b1f8b57ebe196bba --- /dev/null +++ b/jira_jira_reauthenticate.md @@ -0,0 +1,43 @@ +# Reauthenticating your Atlassian Jira account + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_reauthenticate.html + +--- + +# Reauthenticating your Atlassian Jira account + +Reauthenticate your Atlassian Jira account when Jira revokes authentication after a period of time or when the account used to authenticate is no longer active in the Jira site. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps Dashboard appears. + + 3. Click the inventory card for the Jira instance. + +The details page for the Jira instance appears. + + 4. In Status, click Reauthenticate. + +Reauthenticating gives RSC permission to access your data in your Atlassian Jira instance. + + 5. Enter the global administrator credentials for the Jira instance. + +The Reauthenticate Jira Account dialog box appears. + + 6. Click Log in to Authenticate. + +A browser window appears. + + 7. Log in to your Atlassian account. + +After you successfully log in to your Atlassian account, the browser returns to RSC, and the Reauthenticate dialog box appears. + + 8. Click Finish. + +## Results + +Your Altassian account is reauthenticated. + *[ > ]: and then diff --git a/jira_jira_recovery.md b/jira_jira_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..ff5a6f91c0c08112b236cbab7619c82b9b871dd2 --- /dev/null +++ b/jira_jira_recovery.md @@ -0,0 +1,14 @@ +# Atlassian Jira recovery + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_recovery.html + +--- + +# Atlassian Jira recovery + +You can restore data for your Atlassian Jira issues and Jira settings to their original location from any point-in-time snapshot. + +You can restore Atlassian Jira issues, such as tasks and subtasks, and Jira settings, to their original location. You can either use one snapshot to recover all Jira data types, or you can restore each data type with a different snapshot. + +Because Jira is a relational database, Jira data has dependencies. Therefore, all data and their relationships are backed up. While you can restore parent data types without restoring child data types, you can choose to restore the child data types to ensure data integrity. + *[ > ]: and then diff --git a/jira_jira_regions.md b/jira_jira_regions.md new file mode 100644 index 0000000000000000000000000000000000000000..9ebcd2ee7956da6d27612a2ff88ec9b478f8d827 --- /dev/null +++ b/jira_jira_regions.md @@ -0,0 +1,27 @@ +# Supported regions for Atlassian Jira + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_regions.html + +--- + +# Supported regions for Atlassian Jira + +RSC provides support for Atlassian Jira protection in several regions. You select the region when you set up the Jira instance in RSC. + +RSC supports the following regions on which Atlassian Jira can be hosted: + + * Australia East + * Canada Central + * Central India + * East US 2 + * France Central + * Germany West Central + * Israel Central + * Japan East + * North Europe + * Norway East + * UK South + * West Europe + * West US 2 + + *[ > ]: and then diff --git a/jira_jira_restoring_settings.md b/jira_jira_restoring_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..ccfe019c86ffdf36b6ac01d5e11668c97c0c251b --- /dev/null +++ b/jira_jira_restoring_settings.md @@ -0,0 +1,82 @@ +# Restoring Altassian Jira settings + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_restoring_settings.html + +--- + +# Restoring Altassian Jira settings + +Restore Atlassian Jira settings, including workflows, filters, dashboards, and screens, to their original location. Use any point-in-time snapshot to restore data if your data is lost. + +## About this task + +You can use a single snapshot to restore all selected Atlassian Jira settings or specify a different snapshot to restore each setting. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps Dashboard appears. + + 3. Click the inventory card for the Jira instance. + +The details page for the Jira instance appears. + + 4. Click Restore. + 5. In Restore Jira Settings, click Next. + +The Select Setting Type page appears. + + 6. Select a setting that you want to restore. + 7. In Setting Category, select the type of setting you want to recover: issue settings, product settings, or system settings. + 8. In Setting Type, select the type of setting to recover. + 9. Click Next. + +The Select Issue Resolution page appears. + + 10. Select all of the instances of the setting type that you want to restore. + 11. Click Next. + +The page for the setting type that you selected to restore appears + + 12. Select the instances of the setting type to restore. + 13. Click Next. + +The Select Snapshot page appears. + + 14. Select the snapshot you want to use to restore the selected issues. + +Option| Description +---|--- +Select the same snapshot for all selected issues | Select this option to use the snapshot to restore data for all the selected issues. +Select a different snapshot for each issue | Select this option to use a different snapshot to restore data for each issue. + +The details page shows only snapshots that contain changes. + + 15. To compare the contents of two different snapshots, hover over the ellipsis menu and click Compare. + +The Compare snapshots dialog box appears. + + 16. Select the snapshots to compare. + +The dialog box provides information comparing the selected snapshots, such as the issue key and status. + + 17. Click Next. + +The Restore Options page appears. + + 18. In Cascading impact, select the related data you want to restore along with the selected items. + +If you cannot select an item in this field, the data of that item is restored when you restore the selected items. + + 19. Click Next. + +The Confirmation page appears. + + 20. Confirm your selections and click Restore. + +## Results + +RSC restores the Altassian Jira settings to their original location. + *[ > ]: and then diff --git a/jira_jira_supported_data_types.md b/jira_jira_supported_data_types.md new file mode 100644 index 0000000000000000000000000000000000000000..5eebcee99a8edd6a3d0a568fef752ae5f507dc1f --- /dev/null +++ b/jira_jira_supported_data_types.md @@ -0,0 +1,62 @@ +# Supported Atlassian Jira data types + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_supported_data_types.html + +--- + +# Supported Atlassian Jira data types + +RSC can back up and restore a variety of Atlassian Jira data types, such as project issues and workflows. + +The following tables show the Atlassian Jira data types that RSC can back up and restore. + +Table 1. Jira software projects Data type | Backup | Restore +---|---|--- +Jira software company-managed projects | Yes | No +Jira software team-managed projects | Yes | No + +Table 2. Jira service management projects | | +---|---|--- +Jira service management company-managed projects | No | No +Jira service management team-managed projects | No | No + +Table 3. Project issues Data type | Backup | Restore +---|---|--- +| | +Issue comments | Yes | Yes +Issue attachments | Yes | Yes +Issue fields | Yes | Yes +Issue links | Yes | Yes +Issue transitions | Yes | Yes + +Table 4. Issue settings Data type | Backup | Restore +---|---|--- +Custom fields | Yes | Yes +Field configurations | Yes | Yes +Field configuration schemes | Yes | Yes +Issue priorities | Yes | Yes +Issue resolutions | Yes | Yes +Issue security schemes | Yes | Yes +Issue statuses | Yes | Yes +Issue type schemes | Yes | Yes +Issue type screen schemes | Yes | Yes +Issue types | Yes | Yes +Notification schemes | Yes | Yes +Permission schemes | Yes | Yes +Project categories | Yes | Yes +Screens | Yes | Yes +Screen schemes | Yes | Yes +Workflow schemes | Yes | Yes +Workflows | Yes | Yes + +Table 5. Product settings Data type | Backup | Restore +---|---|--- +Dashboards | Yes | Yes +Filters | Yes | Yes + +Table 6. System settings Data type | Backup | Restore +---|---|--- +Users | Yes | No +Groups | Yes | Yes +Project roles | Yes | Yes + *[ > ]: and then diff --git a/jira_jira_viewing_details.md b/jira_jira_viewing_details.md new file mode 100644 index 0000000000000000000000000000000000000000..428f63ad4cc16c344906d14a902b8c0dc4c79d47 --- /dev/null +++ b/jira_jira_viewing_details.md @@ -0,0 +1,23 @@ +# Viewing details about an Atlassian Jira instance + +Source: https://docs.rubrik.com/en-us/saas/jira/jira_viewing_details.html + +--- + +# Viewing details about an Atlassian Jira instance + +View details about an Atlassian Jira instance to monitor and analyze data and to access features, such as managing protection. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click the Jira Software inventory card. + +## Results + +The details page for the Atlassian Jira instance appears. + *[ > ]: and then diff --git a/kubernetes_K8s_crd_rsc.md b/kubernetes_K8s_crd_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..013781e27bf5c16148fbae99f5ca0b03fd82ecb6 --- /dev/null +++ b/kubernetes_K8s_crd_rsc.md @@ -0,0 +1,29 @@ +# RSC Custom resource definitions + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/K8s_crd_rsc.html + +--- + +# RSC Custom resource definitions + +You can use the RSC custom resource definitions to create custom resources for backup and recovery workflows using APIs native to Kubernetes. + +If you are a Kubernetes application owner, you can automate protection for Kubernetes protection sets using RSC custom resource definitions (CRDs). These CRDs create custom resources that extend the functionality of APIs native to Kubernetes, allowing you to assign SLA Domains, take on-demand snapshots, and recover Kubernetes snapshots. The CRDs are available only in the Kubernetes Protection workload. + +Custom resources are registered dynamically to a cluster. Once the custom resource is registered, you can create, update, and delete its CRD using kubectl, similar to how users interact with built-in resources such as pods, deployments, and services. + +A CRD acts like any other Kubernetes object, using all the features of the Kubernetes ecosystem. For example, a CRD uses the Kubernetes CLI, security, API services, and RBAC. The CRD is also stored in the etcd cluster with appropriate replication and lifecycle management. CRDs also eliminate the need for self-directed implementation. + +CRDs are not available through the RSC UI. RSC supports the following CRDs from the Kubernetes command line: + + * hooks.apps.kupr.rubrik.com + * k8sclusters.clusters.kupr.rubrik.com + * protectionsets.apps.kupr.rubrik.com + * recoveryjobs.jobs.kupr.rubrik.com + * rubrikclusters.clusters.kupr.rubrik.com + * sladomains.sla.kupr.rubrik.com + * snapshotjobs.jobs.kupr.rubrik.com + * snapshots.apps.kupr.rubrik.com + +The Kubernetes website includes additional information about CRDs. + *[ > ]: and then diff --git a/kubernetes_anomaly_detection_k8.md b/kubernetes_anomaly_detection_k8.md new file mode 100644 index 0000000000000000000000000000000000000000..46469307a194a8d357b50286faf64a135fcdcd2f --- /dev/null +++ b/kubernetes_anomaly_detection_k8.md @@ -0,0 +1,40 @@ +# Anomaly Detection for Kubernetes + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/anomaly_detection_k8.html + +--- + +# Anomaly Detection for Kubernetes + +You can enable Anomaly Detection for Kubernetes virtual machines and protection sets to identify and analyze anomalous events that can indicate a ransomware attack. + +Anomaly Detection checks for anomalies in file system usage patterns to identify potential ransomware attacks. You can enable Anomaly Detection for Kubernetes virtual machines and protection sets at the Rubrik cluster level from the Settings page in RSC. + +## Anomaly Detection for Kubernetes virtual machines + +Enabling Anomaly Detection for Kubernetes virtual machines has the following requirements: + + * The Rubrik cluster must be running CDM version 9.3.2 or later. + * You must configure Kubernetes virtual machines with block volumes or Kubernetes file system volumes as disks only, or with any combination of these two options. You can utilize block volumes directly as a virtual machine disk. For Kubernetes file system volumes, you can configure and utilize the virtual machines as virtual machine disks. + +RSC does not support Anomaly Detection for Kubernetes virtual machines that include any Kubernetes file system volumes that are not configured and used as virtual machine disks. This is applicable even if the virtual machine also contains the other supported volume types, for example, block volumes or file system volumes that are used as disks. + + * For RSC to accurately display the file paths within the virtual machine during indexing, the virtual machine root folder must be a PersistentVolumeClaim (PVC) that is being actively backed up. If the root folder is not a backed-up PVC, paths may appear with generic identifiers instead of their recognizable names. + +For example, a path might appear as /disk_0_part_1/lockbit_files0/file103.lockbit. However, if the root folder, which corresponds to a specific mount location, such as /mnt/appdata, is correctly configured as a backed-up PVC, the path instead reflects the /mnt/appdata/lockbit_files0/file103.lockbit mount point and not the generic disk_0_part_1. + +## Anomaly Detection for Kubernetes protection sets + +You can enable Anomaly Detection for Kubernetes protection sets to identify and analyze anomalous events that can indicate a ransomware attack. + +Enabling Anomaly Detection for Kubernetes protection sets has the following requirements: + + * The Rubrik cluster must be running CDM version 9.4.1 or later. + * You must configure Kubernetes protection sets with Kubernetes file system volumes as disks only. RSC does not support Anomaly Detection for Kubernetes protection sets that include any Kubernetes block volumes as disks. This applies even if the system contains other file system volumes as disks. + +Anomaly Detection for Kubernetes protection sets has specific limitations because the system does not currently support file-level downloads: + + * Download For Forensics option does not appear on the Summary page. + * Recover is the only recovery option that appears on the Browse page. + + *[ > ]: and then diff --git a/kubernetes_k8s_browse_kubernetes_snapshots.md b/kubernetes_k8s_browse_kubernetes_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..44b7f4f877286c498892e1b7c1c96ee32aff385e --- /dev/null +++ b/kubernetes_k8s_browse_kubernetes_snapshots.md @@ -0,0 +1,24 @@ +# Browse Kubernetes snapshots + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_browse_kubernetes_snapshots.html + +--- + +# Browse Kubernetes snapshots + +You can use RSC to browse the resources in a Kubernetes snapshot for protection sets and virtual machines. + +You can browse protection set and virtual machine snapshots to view the Kubernetes resource objects they contain. + +RSC lists snapshot objects on the Resources tab of the snapshot details page, with the latest snapshot listed first. You can search for other snapshots by date and time. + +The snapshot page lists the resources included in each snapshot, with the resource objects classified by their API group and API type. You can view the configuration of each resource object by selecting the YAML file. From the YAML file, you can copy or download the resource object configuration. + +User accounts with backup administrator and K8S admin privileges can: + + * Browse the contents of a Kubernetes snapshot + * View the configuration of a Kubernetes resource object + * View and copy the contents of the configuration of a Kubernetes resource object + * Download the contents of a Kubernetes resource object configuration while browsing the content of a snapshot on the RSC UI + + *[ > ]: and then diff --git a/kubernetes_k8s_cluster_onboard_discover_rsc.md b/kubernetes_k8s_cluster_onboard_discover_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..e18dc9b2f8e707db0fb662eb6f2f0fd4969b7e81 --- /dev/null +++ b/kubernetes_k8s_cluster_onboard_discover_rsc.md @@ -0,0 +1,33 @@ +# Kubernetes cluster onboarding + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_cluster_onboard_discover_rsc.html + +--- + +# Kubernetes cluster onboarding + +To onboard your Kubernetes cluster, add it to your RSC domain and provide RSC with access to the cluster and sufficient permissions. + +Protecting the namespace-scoped resources and persistent application data in your Kubernetes cluster through Kubernetes protection, starts with onboarding your Kubernetes cluster. Onboarding a Kubernetes cluster requires that RSC has access to the Kubernetes cluster through a Rubrik cluster. This is accomplished by adding your Kubernetes cluster to RSC and providing a Rubrik cluster with the permissions needed to access your cluster. + +The requirements to add a Kubernetes cluster to RSC depend on the location of the cluster and the type of Kubernetes distribution: + + * On-premises or Azure Kubernetes Service (AKS) cloud-native Kubernetes cluster + * Cloud-native Amazon Elastic Kubernetes Service (EKS) cluster + +## On-premises or Azure Kubernetes Service + +You provide access to your on-premises Kubernetes cluster or your Azure Kubernetes Service (AKS) cluster by adding the cluster to RSC and uploading the kubeconfig file. The kubeconfig file includes the information that a Rubrik cluster needs to establish a connection with the Kubernetes cluster. The user account configured in the kubeconfig file must have administrative privileges to read objects from and write objects to the Kubernetes cluster during backup and recovery. + +## Amazon Elastic Kubernetes Service + +You provide access to your Amazon Elastic Kubernetes Service (EKS) cluster by adding it to RSC and creating a cloud account for it in RSC. The cloud account must have EKS cluster protection enabled and the Amazon Resource Name (ARN) of the EKS cluster. You must also configure RBAC for the IAM role associated with the cloud account and the role must have the permissions required to access the EKS cluster. + +## After you provide access + +After establishing a connection with the Rubrik cluster, the Kubernetes cluster downloads the Rubrik Kubernetes Protection Agent container images from Docker Hub into a custom namespace, called the `rubrik-kupr` namespace. The `rubrik-kupr` namespace includes the Rubrik Backup Service (RBS) and the Rubrik controllers that interact with the Kubernetes API server for data backup, recovery, and refresh operations. Collectively, these services are called the Rubrik Kubernetes Protection Agent. Deleting a Kubernetes cluster from RSC removes the `rubrik-kupr` namespace from the Kubernetes cluster. + +The process of adding a Kubernetes cluster to RSC will fail if the `rubrik-kupr` namespace already exists on the Kubernetes cluster. + +After adding a Kubernetes cluster to RSC, you must refresh the cluster to view the namespaces that you can protect. + *[ > ]: and then diff --git a/kubernetes_k8s_cluster_protection_set.md b/kubernetes_k8s_cluster_protection_set.md new file mode 100644 index 0000000000000000000000000000000000000000..77d183950e6377cc143ed6d0bcb2d746da31b164 --- /dev/null +++ b/kubernetes_k8s_cluster_protection_set.md @@ -0,0 +1,18 @@ +# Protection sets for Kubernetes cluster workloads + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_cluster_protection_set.html + +--- + +# Protection sets for Kubernetes cluster workloads + +A Kubernetes cluster protection set is a protectable workload that you create and protect using RSC. A protection set might include an entire Kubernetes namespace or a subset of resources within the namespace. + +A protection set is a protectable Kubernetes workload that you define in RSC to protect Kubernetes cluster objects and data. The protection set can include an entire Kubernetes namespace or a subset of the namespace. The subset might comprise Kubernetes resources or objects, such as Deployments, Services, or Pods, along with the associated Persistent Volumes. + +To start protecting your Kubernetes cluster resources, you are required to create at least one protection set for your Kubernetes cluster and assign an SLA Domain to the protection set. Each protection set maps to one namespace in the Kubernetes cluster. When you create a protection set to protect the entire namespace, RSC protects all the resources within the namespace with the same SLA Domain that you assign to the protection set. + +Within a namespace, protecting different resources with different SLA Domains requires that you create multiple protection sets for the namespace. For each protection set, you can include and exclude resources by the kind or label of the resource. + +For any protection set, you can edit the resources that you protect through the protection set. When you do not need resource protection, you can delete the protection set. + *[ > ]: and then diff --git a/kubernetes_k8s_deployment_architecture.md b/kubernetes_k8s_deployment_architecture.md new file mode 100644 index 0000000000000000000000000000000000000000..9f6e37aca04e4a8dc9d51c7afc835869dc65fcab --- /dev/null +++ b/kubernetes_k8s_deployment_architecture.md @@ -0,0 +1,18 @@ +# Deployment architecture for Kubernetes protection + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_deployment_architecture.html + +--- + +# Deployment architecture for Kubernetes protection + +For the data protection deployment architecture in Kubernetes protection, RSC serves as the control plane and stores the Persistent Volume backups on a Rubrik cluster. + +The main components of the Kubernetes deployment architecture are: + + * Rubrik Security Cloud (RSC) + * A Rubrik cluster connected to RSC + * The Kubernetes cluster to protect + +RSC serves as the control plane for Kubernetes protection and provides the user interface for backing up Kubernetes cluster data. The connected Rubrik cluster serves as the immutable storage target and stores the Persistent Volume (PV) data backups of the Kubernetes cluster. + *[ > ]: and then diff --git a/kubernetes_k8s_least_privilege_configuration.md b/kubernetes_k8s_least_privilege_configuration.md new file mode 100644 index 0000000000000000000000000000000000000000..82b26b8ee943fe4797428d0a58b1ea8043971e6f --- /dev/null +++ b/kubernetes_k8s_least_privilege_configuration.md @@ -0,0 +1,19 @@ +# Least privilege configuration for Kubernetes + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_least_privilege_configuration.html + +--- + +# Least privilege configuration for Kubernetes + +You can set up your Kubernetes kubeconfig with the least privileges so that only minimal RBAC permissions are assigned to users and service accounts. + +The concept of least privilege in a RBAC system is a security principle that requires that users only have the minimum permissions necessary to perform their specific jobs. Rubrik considers it a best practice to assign RSC with only the minimum permissions on the Kubernetes cluster that are required to perform backup and recovery operations. However, occasionally you may need to broaden or refine the set of permissions. The Kubernetes documentation includes information about the permissions that are required to perform specific tasks. + +Before setting up Kubernetes for least privileged configuration, it is important that you make sure: + + * The rubrik-kupr namespace does not exist in the Kubernetes cluster. RSC creates the rubrik-kupr namespace when adding the Kubernetes cluster. + * The Kubernetes cluster supports the transport method before you select the LoadBalancer or NodePort transport method as part of adding the Kubernetes cluster to RSC. RSC creates a service of type LoadBalancer or NodePort in the rubrik-kupr namespace to perform backup and recovery of PVCs. This LoadBalancer or NodePort endpoint is used to communicate with the Rubrik Backup Agent deployed in the Kubernetes cluster. + +When recovering resources like Roles, ClusterRoles, RoleBindings, and ClusterRoleBindings, the least privilege kubeconfig configuration fails if you create roles or bindings that have greater permissions than the kubeconfig user. This, in turn, causes the recovery to fail. You must provide permissions to the kubeconfig user that enables them to create these roles and bindings during recovery. + *[ > ]: and then diff --git a/kubernetes_k8s_openshift_clusters.md b/kubernetes_k8s_openshift_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..c3759334d40fb6890424b26be80a18562ed6a7ac --- /dev/null +++ b/kubernetes_k8s_openshift_clusters.md @@ -0,0 +1,12 @@ +# OpenShift Virtual Machine workload + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_openshift_clusters.html + +--- + +# OpenShift Virtual Machine workload + +You can use RSC to protect containers and virtual machines managed on Kubernetes OpenShift clusters. + +Kubernetes containers and clusters managed on Kubernetes OpenShift clusters can be protected through RSC. Virtual machines managed by OpenShift can be seen on the Virtualization tab of the Kubernetes details page of RSC. OpenShift managed virtual machines can be discovered automatically by RSC and SLA Domain protection can be assigned automatically. + *[ > ]: and then diff --git a/kubernetes_k8s_prereqs.md b/kubernetes_k8s_prereqs.md new file mode 100644 index 0000000000000000000000000000000000000000..194a14b071984a387a2be89f582de7bdd70422b6 --- /dev/null +++ b/kubernetes_k8s_prereqs.md @@ -0,0 +1,14 @@ +# Kubernetes protection prerequisites + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_prereqs.html + +--- + +# Kubernetes protection prerequisites + +There are common and specific prerequisites for Kubernetes protection. + +There are several prerequisites that apply to Kubernetes protection. + +Before you onboard the Kubernetes cluster to RSC, Rubrik recommends that you manually verify that VolumeSnapshot is functional by creating a PersistentVolumeClaim and taking a snapshot. + *[ > ]: and then diff --git a/kubernetes_k8s_protection.md b/kubernetes_k8s_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..75211982b099550080685751d52d7fd71cd4b395 --- /dev/null +++ b/kubernetes_k8s_protection.md @@ -0,0 +1,18 @@ +# Kubernetes protection requirements + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_protection.html + +--- + +# Kubernetes protection requirements + +You can use Rubrik Security Cloud to secure your on-premise or public cloud Kubernetes clusters by protecting either entire Kubernetes namespaces or specific subsets within a namespace using the protection set filtering feature. + +You can use Rubrik Security Cloud (RSC) to protect your on-premise or cloud-native Kubernetes clusters using a protection set. A protection set is a protectable Kubernetes workload that you define in RSC. The protection set can include an entire Kubernetes namespace or a subset of the namespace. The subset might comprise Kubernetes resources or objects, such as Deployments, Services, or Pods, along with the associated Persistent Volumes. + +To successfully protect the Persistent Volumes (PVs) in your Kubernetes cluster, RSC requires that the PVs are provisioned using a Container Storage Interface (CSI) that supports VolumeSnapshot and the ability to create a PersistentVolumeClaim (PVC) from a VolumeSnapshot. RSC updates Kubernetes version support on major and minor Kubernetes feature releases. Rubrik Compatibility Matrix provides more information on the latest supported Kubernetes versions. + +To protect Kubernetes cluster objects and data, you must create protection sets, select resources to be included and excluded from the protection set, and then assign SLA Domains to the protection sets to manage them. You can take both policy-based and on-demand snapshots for Kubernetes protection sets. + +When snapshots are available, you can recover entire protection sets or specific PVCs within a protection set. You can recover a protection set in-place by replacing the original resources in the protection set within the same namespace, or you can export the protection set to a new namespace in the same or different Kubernetes cluster. + *[ > ]: and then diff --git a/kubernetes_k8s_snapshot_retention.md b/kubernetes_k8s_snapshot_retention.md new file mode 100644 index 0000000000000000000000000000000000000000..aded1ff80955a934549e0004d4910e9198c7a7b5 --- /dev/null +++ b/kubernetes_k8s_snapshot_retention.md @@ -0,0 +1,18 @@ +# Kubernetes snapshot retention + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_snapshot_retention.html + +--- + +# Kubernetes snapshot retention + +RSC allows changing the retention period of Kubernetes snapshots with the help of SLA Domains. Kubernetes snapshot retention works only with Rubrik clusters running Rubrik CDM version 7.0.2-p2 and later. + +SLA Domains determine how often snapshots are generated and how long the snapshots are retained after they are generated. When the SLA Domain includes a replication policy, the replication policy determines the retention period of the replica snapshots. + +RSC allows changing the retention for both on-demand and policy-based snapshots. For on-demand snapshots, you can select a specific snapshot and change its retention from the Snapshots tab of the Kubernetes namespace. + +For policy-based snapshots, RSC does not allow changing the retention from the Snapshots tab. You can change the retention of policy-based snapshots of a Kubernetes object by changing the SLA Domain assignment of the object using the Manage Protection option on RSC. When the SLA Domain of a Kubernetes object is changed, RSC changes the retention of all the existing policy-based snapshots of this Kubernetes object based on the retention policy specified in the new SLA Domain. + +The Forever retention policy enables RSC to retain snapshots until they are manually deleted. For an on-demand snapshot, you can assign the Forever retention policy when you change its retention. RSC assigns the Forever retention policy to the policy-based snapshots of a workload when you select the Don't protect option when you assign an SLA Domain to the workload. You can only delete snapshots that are assigned the Forever retention policy. + *[ > ]: and then diff --git a/kubernetes_k8s_supported_distributions.md b/kubernetes_k8s_supported_distributions.md new file mode 100644 index 0000000000000000000000000000000000000000..49083238de4797154ed8392aa44c242d9ab81aed --- /dev/null +++ b/kubernetes_k8s_supported_distributions.md @@ -0,0 +1,26 @@ +# Supported Kubernetes distributions + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_supported_distributions.html + +--- + +# Supported Kubernetes distributions + +RSC provides data protection for containerized applications and business-critical data deployed on conforming Kubernetes distributions. + +This table describes the distributions RSC supports for Kubernetes. + +Resource | Kubernetes distributions +---|--- +Containerized applications | + + * VMware Tanzu + * Red Hat OpenShift + * Upstream Kubernetes + * SUSE Rancher + * AWS EKS + * Azure AKS + * Azure Red Hat OpenShift (ARO) + * Red Hat OpenShift Service on AWS (ROSA) + + *[ > ]: and then diff --git a/kubernetes_k8s_workload_protection.md b/kubernetes_k8s_workload_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..a12531f322915eb8ee08b6e6bfbf70663358722c --- /dev/null +++ b/kubernetes_k8s_workload_protection.md @@ -0,0 +1,37 @@ +# Kubernetes protection + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_workload_protection.html + +--- + +# Kubernetes protection + +You can use Kubernetes protection to protect your on-premise or cloud-native Kubernetes clusters using a protection set. + +Rubrik Security Cloud (RSC) provides Kubernetes protection to secure your on-premise or public cloud Kubernetes clusters by protecting either entire Kubernetes namespaces or specific subsets within a namespace. + +Kubernetes protection uses protection sets to define a set of Kubernetes resources to backup. Protection sets can include an entire Kubernetes namespace or a subset of resources within a namespace. A subset is defined using inclusion or exclusion filters. Subsets can contain Kubernetes resources or objects, such as Deployments, Services, or Pods, along with the associated Persistent Volumes (PVs). + +Note: + +To successfully protect the PVs in your Kubernetes cluster, the PVs must be provisioned using a Container Storage Interface (CSI) that supports VolumeSnapshot and can create a PersistentVolumeClaim (PVC) from a VolumeSnapshot. + +You can use kind and label filters available through Kubernetes protection to explicitly include or exclude specific resources within a namespace. For example, if you want to protect App1 and App2 in the same namespace with different SLA Domains, you can create two protection sets and use the filters to specify resources in each application to protect. You can then assign an SLA Domain with specific policies to each protection set. + +Protecting Kubernetes cluster objects and data requires that you create a protection set, select resources to be included and excluded from the protection set, and then assign an SLA Domain to the protection set. In addition to the policy-based snapshots initiated by the SLA Domain you can also create on-demand snapshots for your protection sets. + +From the snapshots, you can recover the whole protection set or specific PVCs within the protection set. You can recover a protection set in-place in the original namespace by replacing the original resources in the protection set with those in the snapshot. Or you can export the protection set to a new namespace on the same Kubernetes cluster or on a different one. + +Protecting the applications and data in your Kubernetes namespace involves the following tasks: + + * Adding the Kubernetes cluster + * Creating a protection set for the namespace + * Assigning an SLA Domain to the protection set + * Generating policy-based and on-demand snapshots of the protection set + * Using the protection set snapshots for recovery + +The functionality of protection sets can be used programmatically through Custom Resource Definitions (CRDs), Rubrik GraphQL, and the RSC UI. Protection sets can be used to protect resources that are on Kubernetes clusters that are on-premises and cloud-native. + +After Kubernetes resources are identified as a protected set, the Rubrik cluster communicates with the Kubernetes cluster through the connectivity provided by RSC. If you need to run backup and recovery workflows using Kubernetes-native APIs, RSC will also run controllers on the Kubernetes cluster. This requires outbound connectivity from the Kubernetes nodes to either Rubrik Docker Hub or to a private registry that can mirror the Rubrik Docker Hub. + +RSC updates Kubernetes version support on major and minor Kubernetes feature releases. The Rubrik Compatibility Matrix provides more information on the latest supported Kubernetes versions. diff --git a/kubernetes_k8s_workload_protection_policies.md b/kubernetes_k8s_workload_protection_policies.md new file mode 100644 index 0000000000000000000000000000000000000000..9b6abb84e3f548464a37e4f2e509e047c2d549a2 --- /dev/null +++ b/kubernetes_k8s_workload_protection_policies.md @@ -0,0 +1,14 @@ +# Kubernetes workload protection policies + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/k8s_workload_protection_policies.html + +--- + +# Kubernetes workload protection policies + +In RSC, you can take both policy-based and on-demand snapshots of Kubernetes protection sets. + +You can use RSC to back up the resources and Persistent Volumes included in your Kubernetes protection sets with the help of policy-based and on-demand snapshots. The snapshots include backups of the metadata that describes the Kubernetes resources and the data on the Persistent Volumes that are linked to resources through a PersistentVolumeClaim (PVC). + +For policy-based snapshots, you can assign SLA Domains to the Kubernetes clusters and to the individual protection sets that you create for the cluster namespaces. When you assign an SLA Domain to a Kubernetes cluster, all the associated protection sets derive their SLA Domain assignment from the parent cluster. Assigning an SLA Domain directly to a protection set overrides the SLA Domain assignment that the protection set derives from the parent Kubernetes cluster. You can take on-demand snapshots only at the protection set level. + *[ > ]: and then diff --git a/kubernetes_kubernetes_labels.md b/kubernetes_kubernetes_labels.md new file mode 100644 index 0000000000000000000000000000000000000000..5f1d7e63517d7018c9c62705a3ea251256dba6c4 --- /dev/null +++ b/kubernetes_kubernetes_labels.md @@ -0,0 +1,22 @@ +# Kubernetes labels + +Source: https://docs.rubrik.com/en-us/saas/kubernetes/kubernetes_labels.html + +--- + +# Kubernetes labels + +RSC integrates with Kubernetes native labels to manage data protection, enabling you to use Kubernetes labels to identify and group resources, and then associate those labels with SLA Domains. + +You can assign labels to virtual machines or namespaces. When you assign a label to a namespace, all included virtual machines use the same label. When you assign a label to an SLA Domain, objects attached to that label inherit the SLA Domain, reducing manual intervention by automatically applying SLA Domains to a large number of virtual machines with the same label. + +Adding labels to Kubernetes resources requires configuring the labels first on the Kubernetes cluster and then logging in to RSC and refreshing the cluster to display the Kubernetes resources with the labels. You assign labels by adding the `rubrik.com/protection:SLA Domain` prefix to the Kubernetes virtual machines or namespaces YAML definition. + +Kubernetes labels on RSC are read-only. Each Kubernetes label maps to a single SLA Domain, but each SLA Domain can map to multiple labels. + +RSC displays details about Kubernetes labels on the Labels tab of the Kubernetes details page. The Labels tab also displays the number of virtual machines and their corresponding Kubernetes cluster and SLA domain. You can select a label on this page to list all virtual machines and namespaces to which it is attached. + +RSC with Kubernetes native labels can recover and export files. You can restore files from a snapshot to a specific folder on the virtual machine. With Export, you can select a destination namespace on the same Kubernetes cluster to which the virtual machines are exported. + +Using RSC with Kubernetes native labels requires no changes to Role-Based Access Control (RBAC) permissions for users to access labels. + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_adding_subscriptions.md b/m365_backup_storage_m365_b_s_adding_subscriptions.md new file mode 100644 index 0000000000000000000000000000000000000000..794e2ce9ee2e211e9cf6f3da2c7cfec813968acf --- /dev/null +++ b/m365_backup_storage_m365_b_s_adding_subscriptions.md @@ -0,0 +1,83 @@ +# Adding Microsoft 365 Backup Storage subscriptions + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_adding_subscriptions.html + +--- + +# Adding Microsoft 365 Backup Storage subscriptions + +Add a Microsoft 365 subscription to back up and restore data associated with Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes using Microsoft 365 Backup Storage. + +## Before you begin + +Before adding a Microsoft 365 subscription to RSC, ensure the following: + + * Global administrator credentials for Microsoft 365 is available to authorize access to Microsoft 365 applications and associated objects. + * Data source management privilege assigned to the RSC user account, which is used to add the subscription, as described in [Data management permissions](../saas/data_management_permissions.html "Details of data management permissions that are available for assignment to different roles in RSC."). + +## About this task + +You can add a Microsoft 365 subscription to RSC for RSC to access the Microsoft 365 applications data protected using Microsoft Backup Storage. Additionally, you can add multiple subscriptions one at a time. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS App Protection dashboard appears. + + 3. Click Add Instance. + +The Add a SaaS App Instance wizard appears. + + 4. Select Microsoft 365 Backup Storage. + 5. Click Next. + +The Set Up Microsoft 365 Backup Storage page appears with information related to what you can expect. + + 6. Review the information and click Next. + +On the Set Up Microsoft 365 Backup Storage page, information appears indicating that the application is configuring Azure regions. After the configuration is complete, the Grant RSC Access to Microsoft 365 Backup Storage page appears. + + 7. Click Log In. + 8. Enter your Microsoft global administrator credentials. + 9. Review the permissions requested and click Accept. + +RSC redirects you to the Set Up Microsoft 365 Backup Storage page on RSC. The connection status appears as App connected for Microsoft 365 Backup Storage. The Microsoft 365 Backup Storage permissions topic provides detailed information about the requested permissions. + + 10. Click Next. + +A Connect Microsoft 365 Management App page appears. + + 11. Click Connect App next to Microsoft 365 Management. + 12. Enter your Microsoft global administrator credentials. + 13. Review the permissions requested and click Accept. + +RSC redirects you to the Set Up Microsoft 365 Backup Storage page on RSC. The connection status appears as App connected for Microsoft 365 Management. The Microsoft 365 Backup Storage permissions topic provides detailed information about the requested permissions. + + 14. Click Next. + +The Assign SLA Domain page appears displaying the SLA Domain predefined by Microsoft to protect the objects. You need to manually assign the SLA Domain to start protecting the objects. + + 15. Select one of the following: + +Option| Description +---|--- +Subscription | Assigns the SLA Domain predefined by Microsoft to the entire subscription, including all applications and the associated objects.Do the following in a sequence: + * Select Exchange, OneDrive, or SharePoint as needed. + * Click Next.A confirmation message appears. + * Click Yes to confirm. +Objects | Assigns the predefined SLA Domain to specific objects after the setup is complete.Do the following in a sequence: + * Select Objects. + * Click Next. + +A confirmation message appears indicating that RSC will protect your subscription and objects using the SLA Domain predefined by Microsoft. + + 16. Click Set Up. + +A message appears indicating that you have successfully set up Microsoft 365 Backup Storage. It takes a few hours to sync all your Microsoft 365 Backup Storage data. Syncing status changes to connected when the setup is complete. You can begin protecting the objects. + +## Results + +RSC adds your subscription and displays the Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes on the SaaS App Protection dashboard. + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_dashboard.md b/m365_backup_storage_m365_b_s_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..118f5f79e8f0b89723cb679c0731dcafe64abd9d --- /dev/null +++ b/m365_backup_storage_m365_b_s_dashboard.md @@ -0,0 +1,28 @@ +# Microsoft 365 Backup Storage dashboard + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_dashboard.html + +--- + +# Microsoft 365 Backup Storage dashboard + +The Microsoft 365 Backup Storage dashboard provides details about the status, protection policy, and number of protected objects. + +RSC displays the Microsoft 365 applications data protected using Microsoft 365 Backup Storage on the respective dashboards to provide important insights related to connection status, predefined protection policy, total objects, and protected objects. + +You can view a specific dashboard for the following Microsoft 365 applications that are protected using Microsoft 365 Backup Storage: + + * SharePoint sites + * OneDrive user accounts + * Exchange mailboxes + +These dashboards provide options to perform the following tasks: + + * Viewing the connection status of Microsoft 365 Backup Storage and the last time you checked the status. + * Viewing the SLA Domain predefined by Microsoft. + * Assigning an SLA Domain to manage protection of the Microsoft 365 applications and associated objects. + * Viewing the total and protected objects associated with SharePoint sites, OneDrive user accounts, and Exchange mailboxes. + * Viewing used license capacity under License Usage. + * Restoring objects to its original location. + + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_data_recovery.md b/m365_backup_storage_m365_b_s_data_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..099f7ba50b7fd9a18def89f72adf4cce4b97d400 --- /dev/null +++ b/m365_backup_storage_m365_b_s_data_recovery.md @@ -0,0 +1,53 @@ +# Data Recovery using Microsoft 365 Backup Storage + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_data_recovery.html + +--- + +# Data Recovery using Microsoft 365 Backup Storage + +Using Microsoft 365 Backup Storage, you can recover data associated with Microsoft 365 applications, such as SharePoint sites, OneDrive user accounts, or Exchange mailboxes. + +Microsoft 365 Backup Storage offers a solution to mitigate data loss events, such as accidental deletion, ransomware attacks, or other unforeseen incidents. Using Microsoft 365 Backup Storage, you can restore data associated with Microsoft 365 applications, such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes, ensuring business continuity and data integrity. + +## Key recovery features + +The key recovery features of Microsoft 365 Backup Storage are as follows: + + * In-place recovery: When you need to restore data associated with Microsoft applications, such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes after an accidental deletion, ransomware attack, or other data loss event, you can use Microsoft 365 Backup Storage to restore the backed-up data to its original location. + * Restore points: For restoring data from the backup, you need to choose a restore point manually. A restore point is a prior point in time from which you can restore a healthy version of your data. Currently, you can restore the data associated with SharePoint sites, OneDrive user accounts, and Exchange mailboxes from a specific point prior in time from the backups. RSC retrieves the restore points from Microsoft through an API call. + * Express restore points: For SharePoint sites and OneDrive user accounts, you can choose to restore data from application-recommended express restore points. It is recommended to choose express restore points for full SharePoint site or OneDrive user account restores, as this provides the fastest data restore experience. + * Restore data using the latest express restore point, or those closest to a specific date or time: For SharePoint sites and OneDrive user accounts, you can recover data using the express restore points that are either the most recent or closest to a specific date or time. + +## Restoration capabilities + +While restoring data, you can use the following features: + + * Searching for files and quickly locating a specific SharePoint site, OneDrive user account, or Exchange mailbox. + * Sorting the objects based on the Preferred Data Location (PDL) and Status filters. + * Selecting the specific objects, choosing a restore point, and restoring those objects. + * Selecting latest express restore point, or a restore point closest to a specific date or time for restoring data. + +Note: + +When you restore the Microsoft 365 Exchange objects using Microsoft 365 Backup Storage, it is possible that some objects are restored to a new folder named Recovered Items YYYY-MM-DD, HH:MM instead of the original folder. This can happen if the original folder is deleted. + +## Available filters for sorting objects + +You can sort the objects based on the following filters: + + * Preferred Data Location: Sorts objects based on the selected geographical region. + * Status: Sorts objects based on the Active and Relic options. The Active status indicates the objects that are available in the Microsoft database. The Relic status indicates the objects that have been deleted from the database. + +The backup for the relic objects is retained for a year. Currently, you can only view the relic objects from the Relic option. + +## Post-recovery actions and monitoring + +After restoring data, you can do the following: + + * Viewing the events related to all the backup jobs associated with SharePoint sites, OneDrive user accounts, and Exchange mailboxes completed using Microsoft 365 Backup Storage. You can also view the recovery status in the local time zone. + * Tracking and monitoring all the events related to Microsoft 365 applications. + * Changing filters to dynamically change the Events page view and filtering the events by time range, severity, status, and event type from the left pane. + +If an object does not have the Recovery permission, a Role-based Access Control (RBAC) data management permission, and the backup job fails due to the lack of the Recovery permission, then it is indicated in the Events tab. + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_deployment_reqs.md b/m365_backup_storage_m365_b_s_deployment_reqs.md new file mode 100644 index 0000000000000000000000000000000000000000..6656611c7044e0e7b6829164a00a1b601f07ddb4 --- /dev/null +++ b/m365_backup_storage_m365_b_s_deployment_reqs.md @@ -0,0 +1,17 @@ +# Microsoft 365 Backup Storage deployment requirements + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_deployment_reqs.html + +--- + +# Microsoft 365 Backup Storage deployment requirements + +Information about requirements for the Rubrik-hosted deployment mode for Microsoft 365 Backup Storage. + +It is important to fulfill specific requirements before you start adding the Microsoft 365 subscription to RSC. These requirements are important for authorization while adding subscriptions and for accessing resources associated with Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. + +The following table describes the requirements for the Rubrik-hosted deployment mode for Microsoft 365 Backup Storage: Requirement | Description +---|--- +Enabling Microsoft 365 Backup Storage data source on the RSC account | Enabling Microsoft 365 Backup Storage data source on RSC to access the Microsoft 365 subscription from RSC requires purchasing the license for Microsoft 365 Backup Storage. +Creating an RSC user account with the global administrator role | Creating an RSC user account with a global administrator role that has the necessary Role-Based Access Control (RBAC) privileges to perform actions on specific objects. + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_get_start_protecting_apps.md b/m365_backup_storage_m365_b_s_get_start_protecting_apps.md new file mode 100644 index 0000000000000000000000000000000000000000..1da9f4d760c31b161a53cae500a4bf01dcc0ba1e --- /dev/null +++ b/m365_backup_storage_m365_b_s_get_start_protecting_apps.md @@ -0,0 +1,45 @@ +# Get started with protecting M365 applications + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_get_start_protecting_apps.html + +--- + +# Get started with protecting M365 applications + +You can manage protection and recover data associated with Microsoft 365 applications protected using Microsoft 365 Backup Storage by completing a series of tasks. + +To begin protecting Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes with Microsoft 365 Backup Storage, it is necessary to follow these tasks in a logical sequence: + + * Requirements and permissions review + * Microsoft 365 subscription addition + * Discovered applications review + * Administrator user account creation + * Additional requirement-based tasks completion + +## Requirements and permissions review + +First, it is essential to review the necessary requirements and permissions for the Rubrik-hosted deployment mode. You must complete this task to add a subscription to RSC and ensure that RSC can seamlessly protect your Microsoft 365 applications. + +## Microsoft 365 subscription addition + +The next step is adding the subscription to enable RSC to access the resources associated with Microsoft 365 applications. During this process, you have the choice to assign the SLA Domain predefined by Microsoft at either the subscription level or the object level. If you select the subscription-level option, RSC applies the SLA Domain policies to all objects within the subscription. If you select the object-level option, RSC does not apply the SLA Domain policies to objects by default. However, after you finish adding the subscription, you can manually assign the SLA Domain to specific objects to apply the policies. + +## Discovered applications review + +After you have added the Microsoft 365 subscription, RSC displays the Microsoft 365 applications on the SaaS App Protection dashboard. You can track and review all applications in one place. It is important that you check the discovered applications and ensure that the applications you want to protect are available in RSC. + +## Administrator user account creation + +Next, you must create an RSC user account with an administrator role, which includes the necessary Role-Based Access Control (RBAC) privileges to perform actions on specific objects. + +## Additional requirement-based tasks completion + +After adding the Microsoft 365 subscription to RSC, you can perform the following additional tasks based on your requirements: + + * Manually updating data protection policies: If you assigned the SLA Domain at the subscription level when adding the subscription, the policies are applied to all objects within the subscription. You can use the Manage Protection option in RSC to update policies for specific objects. For example, if the subscription has 10 objects, you can exclude certain objects from the assignment. + +If you assigned the SLA Domain at the object level when adding the subscription, RSC does not apply the policies by default. You can now use the Manage Protection option to manually assign the SLA Domain to specific objects of your choice. + + * Restoring Data: When you need to restore the Microsoft 365 applications data, you can use Microsoft 365 Backup Storage for in-place recovery to the original location. After restoring the data, you can monitor events from the Events page of RSC to verify the status of backup jobs. + + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_groups.md b/m365_backup_storage_m365_b_s_groups.md new file mode 100644 index 0000000000000000000000000000000000000000..a2458ae1e9c23e86e3cb452bd058ceec2741bf89 --- /dev/null +++ b/m365_backup_storage_m365_b_s_groups.md @@ -0,0 +1,41 @@ +# Microsoft 365 Backup Storage groups + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_groups.html + +--- + +# Microsoft 365 Backup Storage groups + +You can use groups in RSC to assign data protection policies uniformly to Microsoft 365 Backup Storage objects, such as user Exchange mailboxes, OneDrive accounts, and SharePoint sites. + +Using groups in RSC enables RSC administrators to efficiently manage and apply data protection policies uniformly across Microsoft 365 Backup Storage objects, such as user mailboxes, OneDrive accounts, and SharePoint sites. By leveraging group-based management, RSC administrators can ensure consistent policy application and significantly enhance overall operational efficiency. + +## Benefits of using groups + +Benefits of using Microsoft 365 Backup Storage groups are as follows: + + * Uniform policy application: Assigns consistent data protection policies across multiple Microsoft 365 Backup Storage objects. + * Simplified management: Manages and updates data protection policies at the group level instead of individual objects. + * Enhanced efficiency: Reduces the administrative overhead of manually assigning data protection policies to each Microsoft 365 Backup Storage object. + +## Group types + +RSC uses the following types of groups for managing Microsoft 365 Backup Storage object data protection: + + * Entra ID group: RSC uses Entra ID groups to manage and apply data protection policies to Exchange Mailboxes and OneDrive users. Entra ID groups are a core component of IAM services of Microsoft, enabling RSC administrators to manage user identities and access to resources efficiently. + +You can efficiently manage user assignments by adding custom attributes to a list of Entra ID users and subsequently assigning these users to specific groups based on the custom attribute. + + * SharePoint groups: RSC uses SharePoint groups for managing SharePoint sites. SharePoint groups are a native feature of Microsoft SharePoint that facilitate the management of permissions and access control for SharePoint sites and content. + +SharePoint groups use wildcard patterns to associate specific SharePoint objects to a group. To limit the SharePoint group to objects that are part of a specific location, you can apply a Preferred Data Location (PDL). + +## SLA Domain filters + +You can sort the groups based on the following SLA Domain filters available on the Entra ID Groups and SharePoint Groups pages: + + * Microsoft 365 Backup Storage + * Don't Protect + * No SLA Domain + + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_permissions.md b/m365_backup_storage_m365_b_s_permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..eed9fa94d19723b7ffdac97c59d4241657285444 --- /dev/null +++ b/m365_backup_storage_m365_b_s_permissions.md @@ -0,0 +1,48 @@ +# Microsoft 365 Backup Storage permissions + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_permissions.html + +--- + +# Microsoft 365 Backup Storage permissions + +Information about the permissions that RSC requires to protect your Microsoft 365 applications using Microsoft 365 Backup Storage. + +RSC requires specific permissions to access and manage Microsoft 365 applications data using Microsoft 365 Backup Storage. To achieve this, RSC leverages Microsoft Graph, a comprehensive and unified API endpoint that facilitates access to a broad array of data and services within Microsoft 365 environments. + +The permissions required for RSC to operate effectively are categorized into two main types: Controller permissions and Management permissions. The Microsoft Graph permissions reference topic in Microsoft documentation provides more information about the permissions. + +## Controller permissions + +Controller permissions are the permissions that RSC requires to access Microsoft 365 applications protected using Microsoft 365 Backup Storage. + +Controller permission | Scope | Use case +---|---|--- +`BackupRestore-Configuration.ReadWrite.All` | Application | Allows RSC to read all backup configurations and lists of Microsoft 365 Backup Storage resources to be backed up without a signed-in user. +`BackupRestore-Monitor.Read.All` | Application | Allows RSC to monitor all backup and restore jobs and view quota usage and billing details without a signed-in user. +`BackupRestore-Search.Read.All` | Application | Allows RSC to search all backup snapshots for Microsoft 365 Backup Storage resources without a signed-in user. +`BackupRestore-Restore.ReadWrite.All` | Application | Allows RSC to search all backup snapshots for Microsoft 365 Backup Storage resources and restore Microsoft 365 Backup Storage resources from a backed-up snapshot without a signed-in user. +`BackupRestore-Control.ReadWrite.All` | Application and delegated | Allows RSC to update or read the status of Microsoft 365 Backup Storage service without a signed-in user. + +## Management permissions + +Management permissions are the permissions that RSC requires to retrieve metadata for Microsoft 365 applications. + +Permission | Scope | Use case +---|---|--- +`ServiceHealth.Read.All` | Application | Allows RSC to read the service health information associated with the tenant without a signed-in user. Health information includes service issues or service health overviews. +`Group.Read.All` | Application | Allows RSC to read group properties and memberships and read conversations for all groups without a signed-in user. +`User.Read.All` | Application | Allows RSC to read user profiles without a signed-in user. +`Sites.Read.All` | Application | Allows RSC to read documents and list items in all site collections without a signed-in user. +`Reports.Read.All` | Application | Allows RSC to read all service usage reports without a signed-in user. Services that provide usage reports include Office 365 and Azure Active Directory. +`AdministrativeUnit.Read.All` | Application | Allows RSC to read administrative units and administrative unit membership without a signed-in user. +`Application.Read.All` | Application | Allows RSC to read all service usage reports without a signed-in user. Services that provide usage reports include Office 365 and Azure Active Directory. +`MailboxSettings.Read` | Application | Allows RSC to read mailbox settings of a user without a signed-in user. It does not include the permission to send an email. +`Mail.ReadBasic.All` | Application | Allows RSC to read basic email properties in all mailboxes without a singed-in user. +`Application.Read.All` | Application | Allows RSC to read all applications and service principals without a signed-in user. +`User.Read.All` | Application | Allows RSC to read user profiles without a signed-in user. +`AdministrativeUnit.Read.All` | Application | Allows RSC to read administrative units and administrative unit membership without a signed-in user. +`Application.Read.All` | Application | Allows RSC to read all applications and service principals without a signed-in user. +`User.Read.All` | Application | Allows RSC to read user profiles without a signed-in user. +`Sites.Read.All` | Application | Allows RSC to read documents and list items in site collections without a signed-in user. + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_protection.md b/m365_backup_storage_m365_b_s_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..0c92fdafae9b4b80d3cf36ae4deb525ae8aa7e4b --- /dev/null +++ b/m365_backup_storage_m365_b_s_protection.md @@ -0,0 +1,36 @@ +# Microsoft 365 Backup Storage protection + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_protection.html + +--- + +# Microsoft 365 Backup Storage protection + +You can use the SLA Domain predefined by Microsoft to apply the data protection and management policies to protect Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes using Microsoft 365 Backup Storage. + +Data protection is important for organizations using Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. Ensuring backup and recovery of these applications is essential for maintaining business continuity during accidental deletion, ransomware attacks, or other data loss incidents. Microsoft 365 Backup Storage protects Microsoft 365 applications through the SLA Domains predefined by Microsoft and hierarchical protection strategies. + +For Microsoft 365 Backup Storage, an SLA Domain defines the backup frequency and retention policies. These policies ensure that data protection is consistent and reliable across various Microsoft 365 applications. + +The SLA Domain predefined by Microsoft for Microsoft 365 applications includes: + + * Frequent Backup: A backup every 10 minutes with a retention of 2 weeks. + * Long-Term Backup: A backup once a week with a retention of 1 year. + +When you assign an SLA Domain to Microsoft 365 applications, the data protection policy predefined by Microsoft is applied to all the objects associated with Microsoft 365 applications. The process is hierarchical and automated, simplifying the protection of large numbers of objects. You can select the objects associated with the Microsoft 365 application and assign the SLA Domain to specific objects too. + +The key aspects of SLA Domain assignment are: + + * Hierarchy-Based Protection: The protection mechanism is designed to apply SLA Domains to all objects under a subscription automatically. + * Individual Overrides: While the subscription-level SLA Domain applies to all underlying objects, individual assignments to specific SharePoint sites, OneDrive user accounts, or Exchange mailboxes can override these assignments. + +Using Microsoft 365 Backup Storage, you have several options for managing data protection: + + * Applying the SLA Domain predefined by Microsoft to Microsoft 365 applications to ensure consistent backup and protection. + * Choosing not to protect certain Microsoft 365 applications and excluding them from future backups. + * Clearing existing assignments so that resources inherit the SLA Domain of the next higher-level object in the hierarchy. + +When you apply an SLA Domain at the subscription level, any new user accounts or objects created within SharePoint sites, OneDrive user accounts, or Exchange mailboxes are automatically detected and protected. This ensures that all new data is immediately subjected to the same data protection policies. + +In the event of data loss due to accidental deletion, ransomware attacks, or other issues, Microsoft 365 Backup Storage allows an in-place recovery so that you can restore the backed-up data directly to its original location within SharePoint sites, OneDrive user accounts, or Exchange mailboxes. + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_rbac.md b/m365_backup_storage_m365_b_s_rbac.md new file mode 100644 index 0000000000000000000000000000000000000000..3495a3b77ae57ae113ee619f71d1d950c8d266a6 --- /dev/null +++ b/m365_backup_storage_m365_b_s_rbac.md @@ -0,0 +1,50 @@ +# RBAC for Microsoft 365 Backup Storage in RSC + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_rbac.html + +--- + +# RBAC for Microsoft 365 Backup Storage in RSC + +Role-Based Access Control and implicit permissions in RSC streamline the management and security of Microsoft 365 Backup Storage, enhancing efficient navigation and access control for essential data. + +Permissions are essential in managing Microsoft 365 applications, as they ensure security and accessibility. The Microsoft 365 Backup Storage, managed by RSC, uses implicit permissions to enhance operational efficiency. Understanding how these implicit permissions work is essential, especially in relation to the Role-Based Access Control (RBAC) model and the hierarchical structure of Microsoft 365 objects. + +## Hierarchical structure of Microsoft 365 objects + +The organization of objects in Microsoft 365 follows a hierarchical system, with the Microsoft 365 application acting as the root. This hierarchy reflects common business structures and helps streamline the management of applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. + + + Microsoft 365 Application (Root) + │ + ├── SharePoint Sites + │ ├── Site Collection + │ │ ├── Subsite + │ │ │ ├── Document Library + │ │ │ │ ├── Documents + │ │ │ │ └── Folders + │ │ │ └── Lists + │ └── Permissions + ├── OneDrive User Accounts + │ ├── Account Data + │ ├── Folders + │ └── Files + └── Exchange Mailboxes + ├── Mail Folders + ├── Emails + └── Attachments + +Each object in this hierarchy has parent-child relationships that impact how you assign and manage permissions. + +## Explicit versus implicit permissions + +Explicit permissions are those that you directly assign to a specific object. For instance, if you grant access to a particular SharePoint subsite, you are giving explicit permission to that subsite. + +Implicit permissions are derived logically from the explicit permissions. When you assign explicit permission for a child object, you automatically create implicit permissions for parent objects necessary for navigating to that child object. However, RSC hides objects for which you only have implicit permissions to keep your view simplified. + +## RBAC and implicit permissions + +RBAC is essential for efficiently managing permissions. Within the RBAC framework, you define roles with specific access rights and assign users to these roles based on their responsibilities. RSC applies implicit permissions to ensure that users can navigate through required parent objects without manual intervention. For example, if you have explicit permission to access a specific folder within a OneDrive user account, implicit permissions enable you to navigate the OneDrive hierarchy to reach that folder. + +Suppose you are an administrator managing a SharePoint site. You have explicit permissions for a specific document library within a subsite. To access this document library, you must navigate the site collection and the subsite. Implicit permissions enable you to move through these parent objects without needing explicit permission for each object. These parent objects remain hidden in your view within RSC, keeping your interface simplified. + *[ > ]: and then diff --git a/m365_backup_storage_m365_b_s_removing_subscriptions.md b/m365_backup_storage_m365_b_s_removing_subscriptions.md new file mode 100644 index 0000000000000000000000000000000000000000..e428745839106c23a33a3b83f2e8a92b8a1b3889 --- /dev/null +++ b/m365_backup_storage_m365_b_s_removing_subscriptions.md @@ -0,0 +1,41 @@ +# Removing Microsoft 365 Backup Storage subscriptions + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_b_s_removing_subscriptions.html + +--- + +# Removing Microsoft 365 Backup Storage subscriptions + +Remove a Microsoft 365 subscription associated with Microsoft 365 applications using Microsoft 365 Backup Storage when no longer needed. + +## About this task + +Removing the Microsoft 365 subscription disconnects RSC from Microsoft 365 Backup Storage. This means that RSC will no longer be the controller for Microsoft 365 Backup Storage. If you do not add another controller to the Microsoft 365 subscription within 30 days, your data in the Microsoft 365 Backup Storage will be deleted. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS App Protection dashboard appears. + + 3. Click on one of the following inventory cards: + +Inventory card| Description +---|--- +Microsoft 365 Backup Storage SharePoint | Select the Microsoft 365 Backup Storage SharePoint inventory card when you want to view details, manage protection, and recover data associated with the Microsoft 365 SharePoint sites. +Microsoft 365 Backup Storage Exchange | Select the Microsoft 365 Backup Storage Exchange inventory card when you want to view details, manage protection, and recover data associated with the Microsoft 365 Exchange mailboxes. +Microsoft 365 Backup Storage OneDrive | Select the Microsoft 365 Backup Storage OneDrive inventory card when you want to view details, manage protection, and recover data associated with the Microsoft 365 OneDrive user accounts. + +The selected dashboard appears. + + 4. Click and select Remove Subscription. + +A confirmation window appears. + + 5. Click Remove. + +## Results + +RSC removes the Microsoft 365 subscription associated with Microsoft 365 applications using Microsoft 365 Backup Storage. + *[ > ]: and then diff --git a/m365_backup_storage_m365_backup_storage.md b/m365_backup_storage_m365_backup_storage.md new file mode 100644 index 0000000000000000000000000000000000000000..8a11d637c37e73e11331ecbfbe44b803b1688979 --- /dev/null +++ b/m365_backup_storage_m365_backup_storage.md @@ -0,0 +1,26 @@ +# Microsoft 365 Backup Storage + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/m365_backup_storage.html + +--- + +# Microsoft 365 Backup Storage + +With the Microsoft 365 Backup Storage feature, you can back up Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. You can also restore large volumes of data during ransomware attacks, accidental deletion, or malicious data deletion and overwrite events. + +To safeguard the data of your organization and ensure easy data recovery, Microsoft has introduced the Microsoft 365 Backup Storage feature. This feature provides the ability to back up all or specific Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. You can also restore large volumes of data during ransomware attacks, accidental deletion, or malicious data deletion and overwrite events. + +Microsoft offers the Microsoft 365 Backup Storage feature through two options: + + * Microsoft 365 admin center + * Rubrik as a partner + +Note: + +You can use only one of these options at a time. + +RSC can integrate with the Microsoft 365 Backup Storage APIs to provide backup and storage solutions. + +When you choose to protect your Microsoft 365 applications using Microsoft 365 Backup Storage through Rubrik, RSC acts as a controller, which means RSC has permissions to perform backup and recovery using Microsoft 365 Backup Storage. + +The Microsoft 365 Backup Storage feature is in addition to the Microsoft 365 Data Protection solution and requires purchasing separate licenses. diff --git a/m365_backup_storage_mass_recovery_m365_b_s.md b/m365_backup_storage_mass_recovery_m365_b_s.md new file mode 100644 index 0000000000000000000000000000000000000000..8ed2d1c587eb7ec4d49e29c9bdd5d4b4307cdb76 --- /dev/null +++ b/m365_backup_storage_mass_recovery_m365_b_s.md @@ -0,0 +1,18 @@ +# Microsoft 365 Backup Storage mass recovery events + +Source: https://docs.rubrik.com/en-us/saas/m365_backup_storage/mass_recovery_m365_b_s.html + +--- + +# Microsoft 365 Backup Storage mass recovery events + +Information about the progress and results of mass recovery operations for your Microsoft 365 Backup Storage data. You can view these details on the mass recovery events page. + +## Mass recovery success and failure + +The success of mass recovery depends on how well individual objects are recovered during the operation. A mass recovery operation is successful when 5% or more of the objects are restored. The operation fails when the successful restoration rate falls below 5%. The default threshold value is 5%, and you can configure this value. + +## Availability of Recovery Event Messages and Reports + +Mass recovery event messages and their reports are available on RSC for 90 days after the mass recovery event occurs. After 90 days, the event messages will not be displayed, and you cannot download the recovery report for that mass recovery operation. Rubrik recommends downloading these reports within 90 days if you want to retain them for a long time. + *[ > ]: and then diff --git a/managedvolumes_mv_backup_script_settings.md b/managedvolumes_mv_backup_script_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..cbf6f2dd1d4e476687ef26840383466c9cf0928e --- /dev/null +++ b/managedvolumes_mv_backup_script_settings.md @@ -0,0 +1,22 @@ +# Backup script settings + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_backup_script_settings.html + +--- + +# Backup script settings + +Information about backup script settings for SLA Managed Volume creation, including details on host script execution and pre- and post-backup commands. + +Component | Setting +---|--- +Script to run on the host | The command or full path to the script to perform backup on the host.The text string represents the full path to the script on the host or a single OS command that runs before the backup runs. The integer represents the timeout in seconds.For Rubrik CDM versions 9.0.0 and later, SLA-based Managed Volumes must include the substring `rubrik/scripts` in their backup script paths. This change does not affect the Managed Volumes after the update, but it continues to indicate invalid script paths.For Windows hosts, RSC only supports batch (.bat) scripts as backup scripts. If you want to use PowerShell or any other type of script, you must wrap it inside a batch script. +Enable pre- and post-backup commands | The fields to enable for setting actions that occur before and after the backup: + + * Command to run before backup. + * Option to cancel backup if pre-backup command fails + * Command to run after a successful backup + * Command to run after a failed backup + +The commands and scripts have an associated timeout value. RSC terminates the commands or scripts if the runtime exceeds the timeout value.Pre- and post-backup scripts have limited access to the SLA Managed Volume. The pre-backup script has read-only access to the SLA Managed Volume before the backup begins. The post-backup script has read-only access to the SLA Managed Volume only after a successful backup. + *[ > ]: and then diff --git a/managedvolumes_mv_channel_guidelines.md b/managedvolumes_mv_channel_guidelines.md new file mode 100644 index 0000000000000000000000000000000000000000..7adde637867e84b5050fffcbe4b8f0e9e4a97ccf --- /dev/null +++ b/managedvolumes_mv_channel_guidelines.md @@ -0,0 +1,31 @@ +# Guidelines for channel creation + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_channel_guidelines.html + +--- + +# Guidelines for channel creation + +Guidelines for creating Managed Volume and SLA Managed Volume channels. + +From the Managed Volume page in RSC, you can change the volume name and client name assigned to a Managed Volume or an SLA Managed Volume. However, you cannot change the names assigned to the channels or the number of channels for that volume. The channel names are automatically generated as set values when you create a Managed Volume or an SLA Managed Volume. Also, the number of channels to assign when you create a Managed Volume or an SLA Managed Volume becomes a set value that you cannot modify. To modify the number of channels, creating a Managed Volume or an SLA Managed Volume with a different number of channels is recommended. + +## Managed Volume channels + +Component | Recommendation | Additional Information +---|---|--- +Managed Volume channels | Maximum number of channels per node is 16. | When you back up an Oracle databases to a Managed Volume, you can use the same number of Managed Volume channels and RMAN channels. +Maximum recommended size for Managed Volumes is 50 TB per channel. | A given RMAN channel must write to the same Managed Volume channel on all backup jobs. +Maximum number of Managed Volumes | Maximum number of Managed Volumes is 64 per channel or four channels of 16 Managed Volumes each. | The minimum snapshot interval is one hour. +Maximum size for a single file in any Managed Volume | Maximum file size for a single file in any Managed Volume is 16 TB. | When you back up an Oracle database to a Managed Volume, the maximum recommended file size of the backup is 16 TB. + +## SLA Managed Volume channels + +Component | Recommendation | Additional Information +---|---|--- +SLA Managed Volumes Channels (for both NFS and SMB) | Maximum number of channels per node is 16. | Maximum recommended size for SLA Managed Volumes is 50 TB per channel. +Maximum number of SLA Managed Volumes (for both NFS and SMB) | Maximum number of SLA Managed Volumes is 128 per channel or four channels of 32 SLA Managed Volumes each. | The minimum snapshot interval for this scale is 15 minutes. +The maximum number of SLA Managed Volumes is 192 per channel or four channels of 48 SLA Managed Volumes each. | The minimum snapshot interval for this scale is 30 minutes. +The maximum number of SLA Managed Volumes is 256 per channel or four channels of 64 SLA Managed Volumes each. | The supported snapshot interval for this scale is 45 minutes. +Maximum size for a single file in any SLA Managed Volume | Maximum file size for a single file in any SLA Managed Volume is 16 TB. | When you back up an Oracle database to an SLA Managed Volume, the maximum recommended file size of the backup is 16 TB. + *[ > ]: and then diff --git a/managedvolumes_mv_creating_mv.md b/managedvolumes_mv_creating_mv.md new file mode 100644 index 0000000000000000000000000000000000000000..ec363db8415d38537de3894d00f6be3a87263c53 --- /dev/null +++ b/managedvolumes_mv_creating_mv.md @@ -0,0 +1,46 @@ +# Creating a Managed Volume + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_creating_mv.html + +--- + +# Creating a Managed Volume + +Create a Managed Volume for each application that Rubrik protects. + +## Before you begin + +Set up floating IP addresses for the Rubrik cluster. + +RSC supports Managed Volumes only on Rubrik CDM versions 7.0.2-p2 and 8.0.1 or later. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click the relevant tab for the workload type. + * Managed Volumes + * SLA Managed Volumes + +The list of workloads appears. + + 6. Click Add Volume to configure SLA Managed Volumes and Managed Volumes. + +The Add Volume dialog box appears. + + 7. Complete the configuration specific to Managed Volumes and click Add. + +## Results + +The Rubrik cluster creates a Managed Volume with the configuration provided, and the new Managed Volume appears on the Managed Volumes page. + +The first snapshot taken for a Managed Volume might show a higher Data Transferred value in the Activity Detail due to internal, one-time filesystem metadata initialization, such as `inode` tables and `extent` maps. + *[ > ]: and then diff --git a/managedvolumes_mv_creating_sla_mv.md b/managedvolumes_mv_creating_sla_mv.md new file mode 100644 index 0000000000000000000000000000000000000000..730c46ab0f9a76308de5b9033601e7c2b52357d0 --- /dev/null +++ b/managedvolumes_mv_creating_sla_mv.md @@ -0,0 +1,50 @@ +# Creating an SLA Managed Volume + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_creating_sla_mv.html + +--- + +# Creating an SLA Managed Volume + +Create an SLA Managed Volume on a Rubrik cluster to schedule and initiate backups using an SLA Domain. + +## Before you begin + +Install the Rubrik Backup Service (RBS) on the NFS or SMB host and add the host to the Rubrik cluster. + +## About this task + +You must protect databases running on Windows with a Managed Volume or an SLA Managed Volume only if the databases are running an Active Directory service account. + +Oracle databases with dNFS enabled do not support SLA Managed Volumes and are required to use Always Mounted Managed Volumes. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click the relevant tab for the workload type. + * Managed Volumes + * SLA Managed Volumes + +The list of workloads appears. + + 6. To configure SLA Managed Volumes, click Add Volume. + +The Add Volume dialog box appears. + + 7. Complete the configuration specific to SLA Managed Volumes and click Add. + +## Results + +The Rubrik cluster creates an SLA Managed Volume with the configuration provided, and the new SLA Managed Volume appears on the SLA Managed Volumes page. + +The first snapshot taken for an SLA Managed Volume might show a Data Transferred value in the Activity Detail that is larger than the actual amount of ingested data. This is due to an internal, one-time filesystem metadata initialization, such as `inode` tables and `extent` maps. + *[ > ]: and then diff --git a/managedvolumes_mv_deleting_managed_volume_sla_managed_volume.md b/managedvolumes_mv_deleting_managed_volume_sla_managed_volume.md new file mode 100644 index 0000000000000000000000000000000000000000..a22af15c463f4d68bfa98aa58d88db8a2d9100a2 --- /dev/null +++ b/managedvolumes_mv_deleting_managed_volume_sla_managed_volume.md @@ -0,0 +1,53 @@ +# Deleting a Managed Volume or SLA Managed Volume + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_deleting_managed_volume_sla_managed_volume.html + +--- + +# Deleting a Managed Volume or SLA Managed Volume + +You can log in to the RSC web UI using your account privileges and delete a Managed Volume or SLA Managed Volume. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click the relevant tab for the workload type. + * Managed Volumes + * SLA Managed Volumes + +The list of workloads appears. + + 6. In Name, click the name of the Managed Volume or SLA Managed Volume you want to delete. + +Alternatively, enter a name in the search field or use the filters at the top left of the list. + +The Local page for the selected workload appears. + + 7. Open the ellipsis menu at the top of the page and select Delete. + +The Delete Managed Volume or SLA Managed Volume dialog box appears. + + 8. Select how to handle the existing snapshots of the Managed Volume or SLA Managed Volume. + +Choose from the following options. + +Option| Description +---|--- +Mark Snapshots as Relics | A snapshot of an object that is managed by, but is no longer accessible to the Rubrik cluster. +Expire Snapshots immediately | Deletes the host filesets and all associated backups. + + 9. Click Delete. + +## Results + +The Rubrik cluster deletes the specified Managed Volume or SLA Managed Volume and applies the selected choice to the existing snapshots. + *[ > ]: and then diff --git a/managedvolumes_mv_editing_mv_rsc.md b/managedvolumes_mv_editing_mv_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..9e5f07960b90f2ca8e2abea7abd435dde9100b9d --- /dev/null +++ b/managedvolumes_mv_editing_mv_rsc.md @@ -0,0 +1,41 @@ +# Editing a Managed Volume + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_editing_mv_rsc.html + +--- + +# Editing a Managed Volume + +You can modify the volume name and client name of a Managed Volume. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click Managed Volumes. + 6. Click the name of the Managed Volume you want to edit. + +Alternatively, enter a name in the search field or filter the Managed Volumes by Rubrik cluster, SLA Domain, or Status. + +The Local page for the Managed Volume appears. + + 7. Click and select Edit. + +The Edit Managed Volume dialog box appears. + + 8. Complete the configuration specific to Managed Volumes and click Save. + +From the Managed Volume page in RSC, you can change the volume name and client name assigned to a Managed Volume. However, you cannot change the names assigned to those channels or the number of channels for that volume. The names of channels are automatically generated as set values when you create a Managed Volume. Also, you cannot modify the number of channels you assign when you create a Managed Volume as it becomes a set value. To have a Managed Volume with a different number of channels, you must create a new one. + +## Results + +The Rubrik cluster makes the specified changes to the information for the Managed Volume. + *[ > ]: and then diff --git a/managedvolumes_mv_editing_sla_mv.md b/managedvolumes_mv_editing_sla_mv.md new file mode 100644 index 0000000000000000000000000000000000000000..c6a455aeae1206a124debccf982cfe165d81479a --- /dev/null +++ b/managedvolumes_mv_editing_sla_mv.md @@ -0,0 +1,38 @@ +# Editing an SLA Managed Volume + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_editing_sla_mv.html + +--- + +# Editing an SLA Managed Volume + +To modify the volume name, provisioned size, and client name of an SLA Managed Volume, edit the associated values on the SLA Managed Volumes page. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click SLA Managed Volumes. + 6. In the Name column, click the name of the SLA Managed Volume you want to edit. + +Alternatively, enter a name in the search field or use the filters at the top left of the list. + +The Local page for the SLA Managed Volume appears. + + 7. Click and select Edit. + 8. Complete the configuration specific to SLA Managed Volumes and click Save. + +RSC does not support modifications to the names or to the number of channels. RSC automatically generates the names of the channels while creating an SLA Managed Volume. RSC requires that you create an SLA Managed Volume to modify the number of channels. + +## Results + +The Rubrik cluster makes the specified changes to the information for the SLA Managed Volume. + *[ > ]: and then diff --git a/managedvolumes_mv_floating_ip_addresses.md b/managedvolumes_mv_floating_ip_addresses.md new file mode 100644 index 0000000000000000000000000000000000000000..d48a2eb0ca813b04f6a67724be4dcb3e8ca14984 --- /dev/null +++ b/managedvolumes_mv_floating_ip_addresses.md @@ -0,0 +1,24 @@ +# Floating IP addresses + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_floating_ip_addresses.html + +--- + +# Floating IP addresses + +Floating IP addresses must be set up before creating any Managed Volume. + +Floating IPs provide the following functionalities: + + * Floating IP addresses provide a consistent connection to the Rubrik cluster even when a cluster node becomes unavailable. + * The number of floating IP addresses should match the number of nodes on the Rubrik cluster because an equal distribution of floating IP addresses between the nodes ensures efficient distribution of the work between the nodes. + * After the floating IP addresses are configured, the Rubrik cluster assigns each node a floating IP address. The nodes handle communication through the assigned floating IP address. In the event, a node cannot handle the communication, the Rubrik cluster assigns (floats) that address to another node. This prevents disruption of data transmission over the floating IP address and maintains the availability of the Managed Volumes. + * The number of channels per floating IP address is limited to 16, including main and live mounts. If the limit is exceeded, exporting of the newly created Managed Volume fails with an error message about an insufficient number of available floating IPs. + +Requirement | Description +---|--- +Number | Same number of floating IP addresses as the number of nodes on the Rubrik cluster. +Subnet | Same subnet as the static data IP addresses of the Rubrik cluster. +Uniqueness | Each IP address must be unique within the subnets and cannot be the same as the management IP address or the data IP address. +Network bonding | Floating IP addresses must be configured on bond0. + *[ > ]: and then diff --git a/managedvolumes_mv_managed_volume_application_tags.md b/managedvolumes_mv_managed_volume_application_tags.md new file mode 100644 index 0000000000000000000000000000000000000000..7c81734685033a5194802fd38a627cb2e1893dd4 --- /dev/null +++ b/managedvolumes_mv_managed_volume_application_tags.md @@ -0,0 +1,32 @@ +# Managed Volume application tags + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_managed_volume_application_tags.html + +--- + +# Managed Volume application tags + +Application tags specify the type of application data that is stored on a Managed Volume. + +Application tags specify the application content type in the Managed Volume. The Rubrik cluster optimizes the use of CPU and memory during data reduction based on the selected application content type. When no tag is selected, data reduction uses more CPU and memory. + +RSC configures deduplication and data reduction settings based on the application tag. Because deduplication requires computational resources and time, aggressive deduplication settings can affect data ingestion time. Application tags configure deduplication for an optimal balance of deduplication and performance. + +RSC also uses application tags to configure the mount point settings of log backups. For example, an application tag can specify mount point settings for log backups that take into consideration the increased frequency of backups when using the NFS protocol. + +The following table lists the relative effects of the application tag settings. + +Application tag | Deduplication | Ingest performance +---|---|--- +No tag | High | High +Oracle | High | High +Oracle Incremental Merge | Low | High +Microsoft SQL Server | High | High +SAP HANA | High | High +MySQL | High | High +PostgreSQL | High | High +SAP HANA Log | Low | Medium +DB transaction log | Low | Medium + +When the data in the Managed Volume does not correspond to a listed application tag, you can apply suitable settings by selecting a tag that most closely corresponds to the properties of the data. For data with a high deduplication potential, you can use the default tag setting, and for data with infrequent backups and low deduplication, you can use the Oracle Incremental Merge tag which applies low deduplication and high performance. + *[ > ]: and then diff --git a/managedvolumes_mv_managed_volume_configuration.md b/managedvolumes_mv_managed_volume_configuration.md new file mode 100644 index 0000000000000000000000000000000000000000..133269c515a69fcc27402e10b02bcf5cd66138bd --- /dev/null +++ b/managedvolumes_mv_managed_volume_configuration.md @@ -0,0 +1,26 @@ +# Managed Volume configuration + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_managed_volume_configuration.html + +--- + +# Managed Volume configuration + +Information about the configuration settings used when creating a Managed Volume. + +Component | Setting +---|--- +Volume Name | Name of the Managed Volume being protected to simplify identification. +Provisioned Size (GiB) | Size, in gigabytes.Creating the Managed Volume requires enough space to contain all of the data from the recovery period. There is a requirement for additional space for unexpected data growth. The actual size allotted could be up to 15% lesser than the provisioned size. For example, a 1 TB data source with a 5% change rate requires approximately 1.3 TB for a 7-day recovery period and 1.6 TB for a 14-day recovery period.You can only increase the size of the Managed volumes. +Rubrik Cluster | Name of the Rubrik cluster. +Subnet (Optional) | Direct network traffic of the Managed Volume to a specific VLAN when VLAN tagging is configured on the Rubrik cluster.You must create all Managed Volumes on the same subnet and enter a subnet mask value in CIDR format to limit the network traffic for the Managed Volume to that subnet. Creating all Managed Volumes on a single subnet enables optimal load balancing. +Number of channels | The same number as the number of nodes in the Rubrik cluster. Based on the resources available on the node, this value can be between 1 and 32. +Application tags (Optional) | The type of application data stored on a managed volume. +Protocol | Communications protocol for the Managed Volume. The Rubrik cluster automatically identifies the protocol: NFS for Linux-based hosts and SMB for Windows-based hosts.Rubrik supports clients configured with NFS protocol versions 3 and 4. The Managed Volumes supported protocols section in the Rubrik Compatibility Matrix provides more information about the supported NFS versions.You must use the secure SMB protocol for live mounts of snapshots for this Managed Volume and enable secure SMB connections to use secure SMB for live mounts of Managed Volumes. The cluster automatically identifies this protocol for Windows-based hosts.Note: Rubrik does not support local SMB for Managed Volumes. +Client Name Patterns | Hosts identified to mount the shares from the Managed Volume and the Managed Volume snapshots.Managed volumes using the NFS protocol support multiple FQDNs, IPv4 addresses, a range of IPv4 addresses, or an IPv4 subnet. The SMB protocol allows only IPv4 addresses.Managed volumes using the NFS protocol use these IPv4 addresses as a client allowlist for filtering and authentication. Managed volumes using the secure SMB protocol map these IPv4 addresses to a domain. Each IPv4 address must be mapped to exactly one domain.When this field is empty or contains a single asterisk (*), the Rubrik cluster allows any host to mount the shares from the NFS protocol Managed Volume. Managed volumes using SMB do not support a Client Name Patterns field that is empty or contains an asterisk. For example, to use the subnet range 10.128.45.0 – 10.128.45.63, you must enter 10.128.45.0/26. The Rubrik cluster limits the network traffic of the Managed Volume to the specified subnet. +SLA Domain assignment | Data management policies to apply to snapshots in the Managed Volume. You must assign an SLA Domain to a Managed Volume before directing any backups into that Managed Volume. When the Managed Volume is not assigned to an SLA Domain, the Rubrik cluster assigns the snapshots to the unmanaged policy group and does not expire the snapshots. + +Note: + +Encrypting application backups can lead to ineffective deduplication. Files encrypted with different encryption keys do not trigger content-based matching. + *[ > ]: and then diff --git a/managedvolumes_mv_managed_volume_object_details.md b/managedvolumes_mv_managed_volume_object_details.md new file mode 100644 index 0000000000000000000000000000000000000000..48166494fb37a6aad628e187b1fe9be39a69e4c9 --- /dev/null +++ b/managedvolumes_mv_managed_volume_object_details.md @@ -0,0 +1,16 @@ +# Managed Volume object details + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_managed_volume_object_details.html + +--- + +# Managed Volume object details + +Managed Volumes object details include an overview of Managed Volumes and information on events and snapshots. + +The Overview tab in the Managed Volumes object details page provides a summary of the Managed Volumes. + +From the Events tab, you can monitor in-progress, failed, canceled, completed, and scheduled Managed Volume tasks. + +From the Snapshots tab, you can browse the snapshots that reside on the local Rubrik cluster and on the archival location for the selected Managed Volume. The Snapshots card provides access to snapshot information through a series of calendar views. Each calendar view uses color spots to indicate the presence of snapshots on a date and the status of SLA Domain compliance for the Managed Volume on that date. You can search for files across all of the snapshots of the Managed Volume. + *[ > ]: and then diff --git a/managedvolumes_mv_managed_volume_snapshot_management.md b/managedvolumes_mv_managed_volume_snapshot_management.md new file mode 100644 index 0000000000000000000000000000000000000000..917aca300cf20400c202e8e7cd5797dfba701db1 --- /dev/null +++ b/managedvolumes_mv_managed_volume_snapshot_management.md @@ -0,0 +1,18 @@ +# Managed Volumes snapshot management + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_managed_volume_snapshot_management.html + +--- + +# Managed Volumes snapshot management + +An SLA Domain is assigned to a Managed Volume to enable policy-driven management of the Managed Volume snapshots. + +An SLA Domain is assigned to a Managed Volume before using the volume for backups to prevent differences in the policies applied to the snapshots of the Managed Volume. + +When an SLA Domain is not initially assigned to a Managed Volume, and backups are written to the Managed Volume, default policies are applied to the snapshots. These policies can differ substantially from the policies applied to the Managed Volume through an SLA Domain assignment. + +Managed Volumes rely on your scripts to take backups and use the frequency in SLA Domain to determine the snapshots to be persisted for the SLA Domain retention period. + +SLA Managed Volumes take backups based on the backup frequency defined in the SLA Domains and retain it according to the retention configurations in the SLA Domain. + *[ > ]: and then diff --git a/managedvolumes_mv_managed_volumes_sla_managed_volumes.md b/managedvolumes_mv_managed_volumes_sla_managed_volumes.md new file mode 100644 index 0000000000000000000000000000000000000000..99990603f497d42ceb615d0add0220197b4f6489 --- /dev/null +++ b/managedvolumes_mv_managed_volumes_sla_managed_volumes.md @@ -0,0 +1,21 @@ +# Managed Volumes and SLA Managed Volumes + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_managed_volumes_sla_managed_volumes.html + +--- + +# Managed Volumes and SLA Managed Volumes + +Managed Volumes in RSC protect and manage data while SLA Managed Volumes schedule and initiate backups using an SLA Domain. + +The Managed Volumes card in the Inventory tab shows the number of Managed Volumes and SLA Managed Volumes, the amount of data provisioned, and the amount of data protected. + +Managed Volumes provide hosts with a backup target location on a Rubrik cluster. The cluster manages snapshots of the data through the policies of a specified SLA Domain. + +An SLA Managed Volume provides a service-level agreement that orchestrates the backups that go into a Managed Volume. SLA Managed Volumes consist of two primary components: a backup script or command to run on the data host and an SLA Domain assignment to provide backup management. + +Rubrik controls the mount management of SLA Managed Volumes on the Rubrik cluster as well as on the hosts. Rubrik has greater flexibility with the sizing of SLA Managed Volumes which means that the Rubrik cluster can support more SLA Managed Volumes. + +The Managed Volumes page opens with the SLA Managed Volumes tab displaying a list of SLA Managed Volumes across all clusters. These can be filtered by cluster and SLA domain. + +An SLA Managed Volume is visible to user accounts with a custom role, only if the role includes access to the Windows or Linux host associated with the SLA Managed Volume. diff --git a/managedvolumes_mv_prohibited_mount_points_script_dirs_sla_mv.md b/managedvolumes_mv_prohibited_mount_points_script_dirs_sla_mv.md new file mode 100644 index 0000000000000000000000000000000000000000..8034121fb7ab17b50eb7928bd1b7ffe1ac6ef835 --- /dev/null +++ b/managedvolumes_mv_prohibited_mount_points_script_dirs_sla_mv.md @@ -0,0 +1,66 @@ +# Prohibited mount points and script directories for SLA Managed Volumes + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_prohibited_mount_points_script_dirs_sla_mv.html + +--- + +# Prohibited mount points and script directories for SLA Managed Volumes + +For SLA Managed Volumes, RSC prevents the use of some paths as mount points and host-side script locations. + +Operating System | Prohibited mount points | Prohibited script directory paths +---|---|--- +Linux | + + * /bin + * /boot + * /dev + * /etc + * /lib + * /lost+found + * /media + * /opt + * /proc + * /run + * /sbin + * /srv + * /sys + * /usr + * /var + +| + + * /boot + * /etc + * /lost+found + * /proc + * /run + * /sys + * /dev + + +Solaris | + + * /bin + * /dev + * /etc + * /kernel + * /lib + * /opt + * /platform + * /proc + * /sbin + * /usr + * /var + * /vol + +| + + * /dev + * /etc + * /kernel + * /platform + * /proc + * /vol + + *[ > ]: and then diff --git a/managedvolumes_mv_protecting_mv_slamv.md b/managedvolumes_mv_protecting_mv_slamv.md new file mode 100644 index 0000000000000000000000000000000000000000..c4317f8c95211206e6813c67c3a4c6b226e8c235 --- /dev/null +++ b/managedvolumes_mv_protecting_mv_slamv.md @@ -0,0 +1,68 @@ +# Protecting Managed Volumes and SLA Managed Volumes + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_protecting_mv_slamv.html + +--- + +# Protecting Managed Volumes and SLA Managed Volumes + +Choose a data protection policy for Managed Volumes or SLA Managed Volumes. + +## Before you begin + +Use an account that has an assigned role with the privilege to manage protection. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click the relevant tab for the workload type. + * Managed Volumes + * SLA Managed Volumes + +The list of workloads appears. + + 6. Click the name of the workload. + +Alternatively, enter a name in the search field. + +The Local page for the selected workload appears. + + 7. Click Managed Protection. + +The Manage Protection dialog box appears. + + 8. Choose a protection option. + +Option| Description +---|--- +SLA Domain | The SLA Domain is assigned to the chosen user accounts. +Clear existing assignment | The SLA Domain is assigned from the next higher level object based on inheritance rules. +Don't protect | The chosen user accounts are excluded from all further SLA Domain assignments. + + 9. Click Next. + +The Confirmation page appears. + + 10. Review the information on the summary page. + 11. (Edit SLA Domain) In Apply changes to existing snapshots, choose one of the following options. + * Accept the default setting to apply changes to the existing snapshots. + * Clear the setting to leave the retention policy of existing snapshots unchanged. + 12. Select Include on-demand and downloaded snapshots to update the retention period applied to on-demand snapshots and to snapshots downloaded from an archival location. + +If unselected, the retention policy of on-demand and downloaded snapshots remains unchanged. This action does not change the retention period of replicated copies of these snapshots. + + 13. Click Assign. + +## Results + +The Rubrik cluster saves the settings and begins managing the snapshots of the Managed Volumes or SLA Managed Volumes. + *[ > ]: and then diff --git a/managedvolumes_mv_resizing_a_managed_volume_sla_managed_volume.md b/managedvolumes_mv_resizing_a_managed_volume_sla_managed_volume.md new file mode 100644 index 0000000000000000000000000000000000000000..d14d221e7e5e79d124041401fff0c0ea2d548076 --- /dev/null +++ b/managedvolumes_mv_resizing_a_managed_volume_sla_managed_volume.md @@ -0,0 +1,52 @@ +# Resizing a Managed Volume or SLA Managed Volume + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_resizing_a_managed_volume_sla_managed_volume.html + +--- + +# Resizing a Managed Volume or SLA Managed Volume + +Resize a Managed Volume or an SLA Managed Volume to increase its size. + +## About this task + +Managed Volumes and SLA Managed Volumes can be resized to up to 1024 times their original size. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click the relevant tab for the workload type. + * Managed Volumes + * SLA Managed Volumes + +The list of workloads appears. + + 6. In Name, click the name of the Managed Volume or SLA Managed Volume you want to resize. + +Alternatively, enter a name in the search field or use the filters at the top left of the list. + +The local page for the Managed Volume or SLA Managed Volume appears. + + 7. Open the ellipsis menu at the top of the page and select Edit. + +The Edit Managed Volume or Edit SLA Managed Volume dialog box appears based on the workload type selected. + + 8. In Provisioned Size, enter the new size of the Managed Volume or SLA Managed Volume in GiB. + +The new size of the Managed Volume or SLA Managed Volume must be greater than the old size. + + 9. Click Save. + +## Results + +The Rubrik cluster resizes the Managed Volume or SLA Managed Volume as a background task. The Managed Volume or SLA Managed Volume remains in the read-only state and is inaccessible until the resizing operation completes. + *[ > ]: and then diff --git a/managedvolumes_mv_setup_requirements_slamv.md b/managedvolumes_mv_setup_requirements_slamv.md new file mode 100644 index 0000000000000000000000000000000000000000..f7cad339c7d53c6b5bef3340270afa1a7023b4bd --- /dev/null +++ b/managedvolumes_mv_setup_requirements_slamv.md @@ -0,0 +1,33 @@ +# Managed Volumes setup requirements + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_setup_requirements_slamv.html + +--- + +# Managed Volumes setup requirements + +Establishing a Managed Volume or an SLA Managed Volume protected by an SLA Domain requires a specific setup. Once established, the Managed Volume is treated as any other protected data source. + +To configure Managed Volumes and SLA Managed Volumes, you must set up the following: + + * Service account for API access. + * Rubrik MFA with TOTP. + * Floating IP addresses for the Rubrik cluster for Managed Volumes. + * Rubrik Backup Service (RBS) on the NFS or SMB host for SLA Managed Volumes. You must add the host to a Rubrik cluster to allow the cluster to manage data on the host. + +You must enable secure SMB connections for use in Live Mounts of Managed Volumes. + +You can now create a Managed Volume or an SLA Managed Volume workload, assign an SLA domain to the new workload, and manage snapshots. + +Note: + +RSC only supports Managed Volumes on Rubrik CDM versions 7.0.2-p2 and 8.0.1 or later. + +RSC supports clients configured with NFS protocol versions 3 and 4. However, there are certain limitations with NFSv4 protocol support, and it does not support the following: + + * TLS (encryption) for data in transit + * Kerberos-based authentication + * File locking + * ACL and parallel NFS features + + *[ > ]: and then diff --git a/managedvolumes_mv_sla_mv_configuration.md b/managedvolumes_mv_sla_mv_configuration.md new file mode 100644 index 0000000000000000000000000000000000000000..13f8bed273f0eb6abb7605a2a25f194ea70f0100 --- /dev/null +++ b/managedvolumes_mv_sla_mv_configuration.md @@ -0,0 +1,46 @@ +# SLA Managed Volume configuration + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_sla_mv_configuration.html + +--- + +# SLA Managed Volume configuration + +Information about the configuration settings used when creating an SLA Managed Volume. + +Component | Description +---|--- +Volume Name | Name of the SLA Managed Volume being protected to simplify identification. +Provisioned Size (GiB) | The amount of space provisioned for the SLA Managed Volume, in gigabytes.The actual size allotted could be up to 15% lesser than the provisioned size. You must create SLA Managed Volumes with sufficient space to contain all the data from the recovery period and some additional space for unexpected data growth.For example, a 1 TB data source with a 5% change rate works out to 50 GB every day, which requires approximately 1.3 TB for a 7-day recovery period and 1.7 TB for a 14-day recovery period. You can only increase the size of the Managed Volumes. +Rubrik Cluster | The name of the Rubrik cluster. +IP or Hostname | The IP address or hostname of the client host. +Number of channels (optional) | The number of channels equals the number of nodes in the Rubrik cluster. Based on the resources available on the node, this value can be between 1 and 32.SLA Managed Volumes have the following requirements: + + * Number of channels for each SLA Managed Volume cannot exceed the number of nodes in the Rubrik cluster. + * You can support SLA Managed Volumes over 50 TB in size by creating more than one channel. + +When backing up Oracle databases to an SLA Managed Volume, Rubrik recommends using the same number of SLA Managed Volume channels as RMAN channels. An RMAN channel must write to the same SLA Managed Volume channel on all backup jobs. +Subnet (optional) | The IP addresses of the subnet. You can enter multiple floating IP addresses. Creating all SLA Managed Volumes on a single subnet enables optimal load balancing.You can direct network traffic of the SLA Managed Volume to a specific VLAN when VLAN tagging is configured on the Rubrik cluster. You are required to create all SLA Managed Volumes on the same subnet and a subnet mask value provided in CIDR format to limit the network traffic for the SLA Managed Volume to that subnet. For example, to use the subnet range 10.128.45.0 - 10.128.45.63, you are required to enter 10.128.45.0/26. The Rubrik cluster limits the network traffic of the Managed Volume to the specified subnet. +Application tags (optional) | Application tags specifying the type of application content in the Managed Volume. The Rubrik cluster optimizes the use of CPU and memory during data reduction based on the selected type. If no tag is selected, data reduction uses more CPU and memory. +Protocol | Communication protocol for the Managed Volume. The Rubrik cluster automatically identifies the protocol: NFS for Linux-based hosts and SMB for Windows-based hosts.NFS protocol for live mounts of snapshots for this managed volume. You can type the user account used to execute backup scripts.Oracle databases with dNFS enabled do not support SLA Managed Volumes. Oracle databases with dNFS enabled are required to use Always Mounted Managed Volumes.To use secure SMB for live mounts of Managed Volumes, you are required to enable secure SMB connections. You are required to enter the domain user account used to run the Rubrik Backup Service on the Windows host here.Note: Rubrik does not support local SMB for SLA Managed Volumes. +Username | The user account of the NFS or SMB servers. + + * NFS: The user account used to run backup scripts for the NFS server. + * SMB: Domain user account of the SMB server used to run the Rubrik Backup Service on the Windows host. Specifying the value for this field in the format "username@domain" might cause backup failure in Rubrik CDM versions 8.1.1 and later. To avoid failure, specify only the username without the domain name. + + +NFS Version | The NFS protocol version for backup and live mount.Rubrik supports NFS protocol versions 3 and 4. The Managed Volumes supported protocols section in the Rubrik Compatibility Matrix provides more information about the supported NFS versions.Note: When you select the NFSv4 protocol for a Managed Volume and the client host does not support the NFSv4, the mount will fail.When you edit an SLA Managed Volume, Rubrik supports switching between the NFSv3 and v4 protocol. +Mount point path on the host | The full path to mount the channels on the NFS or SMB host.The number of fields corresponds to the number of channels specified. +Domain | The name of the Active Directory domain of the SMB Server. +Active Directory Groups (optional) | The Active Directory groups that require backup and restore access to the SMB shares.A Managed Volume or an SLA Managed Volume must protect databases running on Windows only if the databases are running an Active Directory service account. +Enable pre- and post-backup commands. | Option to enable pre-backup and post-backup options for the following: + + * Script to run before taking a backup. + * Script to run after a successful backup job. + * Command to run after backup job fails. + + +Script to run on the host | The full path to the script to perform backup on the host. +Timeout (seconds) | An associated timeout value. The value represents the number of seconds before the Rubrik cluster terminates the pre-backup script because the script cannot be completed. +Cancel backup if the pre-backup script fails | A notification of pre-backup script failure.When you select this checkbox, RSC displays a notification if f the script fails. Any script exit status other than 0 is considered a script failure. + *[ > ]: and then diff --git a/managedvolumes_mv_versus_sla_managed_volumes.md b/managedvolumes_mv_versus_sla_managed_volumes.md new file mode 100644 index 0000000000000000000000000000000000000000..63a1859675dbe08aefa249a0e361ed1d3651b493 --- /dev/null +++ b/managedvolumes_mv_versus_sla_managed_volumes.md @@ -0,0 +1,27 @@ +# Managed Volumes versus SLA Managed Volumes + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/mv_versus_sla_managed_volumes.html + +--- + +# Managed Volumes versus SLA Managed Volumes + +Differences between Managed Volumes and SLA Managed Volumes that indicate when to select either option. + +The following differences between Managed Volumes and SLA Managed Volumes can help you determine when to select either feature. + + * You can choose SLA Managed Volumes when a large number of database backups are required. Rubrik manages these backups in SLA Managed Volumes using the SLA Domain backup frequency. + * When you require more than 16 channels per node, you can use SLA Managed Volumes regardless of the Managed Volumes size or size per channel. The size per channel includes the main mounts and live mounts together but not all of them active and taking backups simultaneously. + * Legacy Managed Volume resets require manual intervention owing to a lack of floating IPs on the Cloud clusters. SLA Managed Volumes do not rely on floating IPs for failovers. + +The following table describes the differences between Managed Volumes and SLA Managed Volumes. + +Description | Managed Volume | SLA Managed Volume +---|---|--- +RBS requirement | No | Yes +Backups initiated by SLA Domain | No | Yes +Backup frequency control in Rubrik | No | Yes +Floating IP address requirement | Yes | No +Cloud cluster support | Supported without failover | Supported with failover +Invoking begin/end snapshots APIs | Yes | No + *[ > ]: and then diff --git a/managedvolumes_rbk_setting_up_floating_ip_addresses.md b/managedvolumes_rbk_setting_up_floating_ip_addresses.md new file mode 100644 index 0000000000000000000000000000000000000000..d5d57db4c08e381f52a9f539a005315818a0fe61 --- /dev/null +++ b/managedvolumes_rbk_setting_up_floating_ip_addresses.md @@ -0,0 +1,58 @@ +# Setting up floating IP addresses + +Source: https://docs.rubrik.com/en-us/saas/managedvolumes/rbk_setting_up_floating_ip_addresses.html + +--- + +# Setting up floating IP addresses + +Set up floating IP addresses to ensure that all Managed Volumes are available if a Rubrik node fails. + +## About this task + +One floating IP address must be defined for each Rubrik node, and the floating IP address should be on the same subnet as the static data IP addresses of the Rubrik nodes. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Managed Volumes inventory card. + +The Managed Volumes page appears. + + 5. Click the relevant tab for the workload type. + * Managed Volumes + * SLA Managed Volumes + +The list of workloads appears. + + 6. Click the name of a cluster. + +The Clusters page appears. + + 7. Click Network Settings. + +The Network Settings page appears. + + 8. Open the ellipsis menu and select Floating IPs. + 9. Choose an IP address type. + * IPv4 + * IPv6 + 10. (IPv4) In Floating IPs IPv4, enter a comma-separated list of IPv4 addresses. + +As a best practice, provide the same number of IP addresses as the number of nodes in the Rubrik cluster. Each IP address must be on the same subnet as the static data IP addresses of the Rubrik nodes or on one of the service VLANs. + + 11. (IPv6) In Floating IPs IPv6, enter a comma-separated list of IPv6 addresses. + +As a best practice, provide the same number of IP addresses as the number of nodes in the Rubrik cluster. Each IP address must be on the same subnet as the static data IP addresses of the Rubrik nodes or on one of the service VLANs. + + 12. Click Confirm. + +## Results + +The Rubrik cluster stores the floating IP addresses and assigns the floating IP addresses to the nodes. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_backup_recovery.md b/microsoft_dynamics_365_d365_backup_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..3ea137ff300de6b037d92a690eb7a7d8ad777b8a --- /dev/null +++ b/microsoft_dynamics_365_d365_backup_recovery.md @@ -0,0 +1,12 @@ +# Dynamics 365 backup and recovery + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_backup_recovery.html + +--- + +# Dynamics 365 backup and recovery + +After RSC takes snapshots of your Microsoft Dynamics 365 workloads, you can recover the required rows or metadata whenever required. + +Ensuring the reliability and availability of data within Microsoft Dynamics 365 workloads is important for seamless business operations. Using RSC, you can assign an SLA Domain to your Microsoft Dynamics 365 subscription. After the SLA Domain assignment, RSC takes snapshots of the associated Microsoft Dynamics 365 workloads based on the data protection policies specified in the SLA Domain. These snapshots are important because they let you quickly and efficiently recover specific rows or metadata whenever needed. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_comm_rsc_dynamics_subs.md b/microsoft_dynamics_365_d365_comm_rsc_dynamics_subs.md new file mode 100644 index 0000000000000000000000000000000000000000..b467d65f70f7b5bb1f7c7cd4ffb240b4b2524c0b --- /dev/null +++ b/microsoft_dynamics_365_d365_comm_rsc_dynamics_subs.md @@ -0,0 +1,23 @@ +# Communication between RSC and Dynamics 365 subscription + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_comm_rsc_dynamics_subs.html + +--- + +# Communication between RSC and Dynamics 365 subscription + +A high-level architecture overview of how RSC uses Microsoft Entra ID and OAuth 2.0 authorization flows to manage Microsoft Dynamics 365 workloads securely. + +RSC integrates with Microsoft Dynamics 365 to secure your data by using Microsoft Entra ID application and OAuth 2.0 authorization flows. With this integration, RSC securely protects data within Microsoft Dynamics 365 and Power Platform environments, such as Dataverse, through authorized API interactions. + +The detailed process consists of the following steps: + + * Onboarding of a Microsoft Dynamics 365 environment: Onboarding a Microsoft Dynamics 365 environment to RSC involves securely setting up a Microsoft Entra ID application to enable authenticated API calls to Microsoft platform APIs. This process includes creating an application user within your Dataverse environment and assigning it a security role, such as a system administrator, to handle tasks such as backup, recovery, and management. + +RSC uses Microsoft Entra ID applications for secure, authenticated Microsoft API access through OAuth 2.0. The integration process consists of several key steps. It is important to create Entra ID applications in advance and maintain them in a secure internal pool to streamline the onboarding process, reduce potential delays, and eliminate issues arising from on-demand application creation. + + * OAuth 2.0 authorization: During onboarding, RSC initiates OAuth 2.0 authorization through the OAuth authorization endpoint, where you provide consent, resulting in an OAuth authorization code. RSC exchanges this code for an OAuth access token using the authorization code flow, with scopes such as .default and offline_access. + * Environment selection and configuration: With the OAuth access token, RSC queries the Power Platform environments API to list all Microsoft Dynamics 365 environments in your account, allowing you to select the specific environment you want to protect. Once the environment is selected, RSC creates and configures an application user in the Dataverse environment using the Power Platform API. You then assign the system administrator role to the application user, granting the necessary privileges for secure data backup and management. + * Post-setup operations: Post-setup, RSC interacts with your Microsoft Dynamics 365 environment through the OAuth 2.0 client_credentials grant flow. RSC obtains short-lived access tokens from Entra ID to securely execute backup, restore, management, and data protection API calls. These operations are conducted within the permissions assigned through the system administrator role granted to the application user. + + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_common_terms_protection.md b/microsoft_dynamics_365_d365_common_terms_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..ecce5644e800e0bb75da0ab7230a8a591a87b9dd --- /dev/null +++ b/microsoft_dynamics_365_d365_common_terms_protection.md @@ -0,0 +1,32 @@ +# Common terms for Dynamics 365 protection + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_common_terms_protection.html + +--- + +# Common terms for Dynamics 365 protection + +It is important to understand some common terms when protecting Microsoft Dynamics 365 workloads with RSC. + +By learning common protection terms, you can better understand and navigate the steps and components involved in protecting Microsoft Dynamics 365 workloads. + +Term | Definition +---|--- +Microsoft Dynamics 365 environment | A secure and isolated space where Microsoft Dynamics 365 applications run and store data, customized based on the needs of an organization. The Microsoft Dynamics 365 environment supports functions such as sales, customer service, marketing, and field service. +Microsoft Dynamics 365 Customer Relationship Management (CRM) module | An integrated suite of CRM applications designed to streamline sales, customer service, marketing, and field service operations. +Microsoft Dynamics 365 subscription | A Microsoft Dynamics 365 environment that you have onboarded to RSC. +Microsoft Dynamics 365 workload | All tables associated with Microsoft Dynamics 365 and protected by RSC become one workload, and all table metadata along with global metadata become another workload. +Attribute | A container for a piece of data within an table. Microsoft Dynamics 365 supports many types of attributes. +Tables | Data structures that store and manage data for various business processes. Each table consists of rows representing individual data instances and attributes defining specific data points. +Rows | Individual instances of data within a table. Each row comprises attributes, known as fields, that store specific data points, such as customer details in a customer table or order information in an orders table. +Metadata | Data structures that store and manage data related to various business processes. +Table metadata | Information about the tables or the data they contain. It includes properties such as table relationships, data item attributes, and how these items interact with other data items. +Global metadata | Metadata that spans across all tables or pertains to the overall Microsoft Dynamics 365 environment such as, global option sets. +Relationship | A relationship defines how two tables are associated with each other. Types of relationships include one-to-many, many-to-one, many-to-many, and self-referential. These relationships help maintain data integrity and enable the organization to model complex business scenarios, ensuring that data can be linked and cross-referenced effectively across different tables. +Power platform | A suite of Microsoft tools designed to enhance and extend the capabilities of Microsoft Dynamics 365 applications. It includes Power BI for data analytics and visualization, Power Apps for low-code custom application development, Power Automate for workflow automation, and Power Virtual Agents for creating intelligent chatbots. Together, these tools integrate seamlessly with Microsoft Dynamics 365, enabling users to analyze data, automate processes, build custom solutions, and improve overall productivity and decision making. +Option set | Reusable sets of options that you can share across multiple tables and fields. These reusable sets enable consistent data entry and simplify maintenance. You can define the set of options once and use it in various places within the application. For example, a set of options provided for a picklist. Several picklist attributes may use a global option set so that the options they provide are always the same and can be maintained in one location. +Option | One of the values available in an option set. Each option in an option set has a unique integer value and an associated set of localized labels. +SLA Domain | An RSC feature you configure to define policies for data protection, including snapshot frequency and retention duration. You can configure and apply these policies to workloads, ensuring consistent and automated data protection. +Snapshot | Point-in-time copies of protected workloads, used for recovery. +Retention lock | A security feature in RSC that prevents premature deletion of snapshots. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_dashboard_details.md b/microsoft_dynamics_365_d365_dashboard_details.md new file mode 100644 index 0000000000000000000000000000000000000000..51f10bd67b3e2b2777272cd9c333e41af0123614 --- /dev/null +++ b/microsoft_dynamics_365_d365_dashboard_details.md @@ -0,0 +1,24 @@ +# Dynamics 365 dashboard details + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_dashboard_details.html + +--- + +# Dynamics 365 dashboard details + +RSC monitors, analyses, and restores Dynamics 365 data and shows the important details, such as backup jobs, status, changed rows, and backup summary. + +The details page for the Dynamics 365 subscription helps you monitor backup information, such as backup jobs, status, changed rows, backup summary, and license usage. You can take an on-demand snapshot and manage protection from the dashboard. + +You can also analyse and restore rows and metadata from the Restore tab. + +The following table describes information on the Monitor tab of the details page. + +Field | Description +---|--- +Backup Jobs | Displays the failed or successful snapshots in the past seven or 30 days.You can view a timeline of when RSC successfully or unsuccessfully backed up snapshots for either the past seven days or past 30 days. You can click an icon to view the successful snapshots, failed snapshots, and failed metadata snapshots. +Status | Displays whether dynamics 365 protection service is online. +Take a Snapshot | Provides access to taking an on-demand snapshot. +Backup Summary | Displays protection information and provides access to managing protection on the Dynamics 365 subscription. +Changed rows | Displays a timeline of added, modified, and deleted Dynamics 365 table rows during different time ranges. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_event_log_details.md b/microsoft_dynamics_365_d365_event_log_details.md new file mode 100644 index 0000000000000000000000000000000000000000..eb69049d8c4b86624fe4bbec0bb9ddb04deed0b8 --- /dev/null +++ b/microsoft_dynamics_365_d365_event_log_details.md @@ -0,0 +1,60 @@ +# Event log details + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_event_log_details.html + +--- + +# Event log details + +The Events page displays the events occurring in all Dynamics 365 subscriptions, shown in the local time zone. + +RSC tracks, monitors, and displays all events associated with all Dynamics 365 subscriptions. You can apply or change filters to alter the Events page view dynamically. + +The following table describes the RSC filters on the Event Logs page. Filter | Description +---|--- +Time range | Displays events aggregated over the specified time. + + * Past 15 minutes + * Past 2 hours + * Past 24 hours + * Past 7 days + * Past 30 days + * CustomWith the Custom date range, you can specify a date range to include a specific number of days, including beyond 30 days. + + +Severity | Displays the severity of the events. + + * Critical - System event that requires attention, such as failed backup, archiving, or replication. + * Warning - System event finished with a backup, archiving, or recovery warning. + * Informational - System event for information only. + + +Status | Displays events based on the event status. + + * Failed + * In progress + * Succeeded + * Succeeded with warnings + * Canceled + * Queued + + +Event type | Displays events based on the specified type. This filter supports multi-selection. + + * Backup + * Configuration + * Diagnostic + * Recovery + * Sync + * Unknown event + + +Object type | Displays events of the following object types related to the Dynamics 365 subscription on RSC: + + * Dynamics 365 Table + * Dynamics 365 Metadata + * Dynamics 365 Organization + + +Instance | Displays a list of Dynamics 365 subscriptions. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_key_features_protection.md b/microsoft_dynamics_365_d365_key_features_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..ec2820c461ef39dbd6658265397f3f4bada5cd05 --- /dev/null +++ b/microsoft_dynamics_365_d365_key_features_protection.md @@ -0,0 +1,47 @@ +# Key features for Dynamics 365 protection + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_key_features_protection.html + +--- + +# Key features for Dynamics 365 protection + +RSC provides unified data management, automated global data protection, various recovery options for Microsoft Dynamics 365 Customer Relationship Management workloads, and advanced security features to protect your workloads. + +RSC provides a comprehensive suite of features to protect and manage Microsoft Dynamics 365 Customer Relationship Management (CRM) module data. Here are the key features: + +## Unified data management + +Feature | Description +---|--- +Rubrik Security Cloud data protection | Provides a SaaS platform for multicloud environments to protect the Microsoft Dynamics 365 data. +Consolidated monitoring and reporting | Provides unified reporting to track SLA Domain assignment, protection and recovery activities, and SLA Domain policy compliance. +Comprehensive dashboard | Manages all Microsoft Dynamics 365 subscriptions, backups, and recovery operations from a single, unified interface, streamlining administrative tasks and reducing complexity. + +## Automated global data protection through SLA Domains + +Feature | Description +---|--- +Protection policies | Assigning and managing protection policies, known as SLA Domains, for Microsoft Dynamics 365 organizations to ensure that backup and recovery operations meet business needs. +Automated backups | Using SLA Domains to automate backups, setting schedules to regularly protect your Microsoft Dynamics 365 data without manual intervention. + +## Backup and restore capabilities + +Feature | Description +---|--- +On-demand backups | Initiating backups anytime as needed, providing you the flexibility to protect data outside of predefined schedules. +Granular and metadata recovery | Restoring table rows, providing flexibility in data recovery scenarios. Also, you can restore both table-related metadata and global metadata, including properties of tables, data item attributes, and global option sets. + +## Role-based access control (RBAC) + +Feature | Description +---|--- +Administrator permissions | Setting user role permissions specific to Microsoft Dynamics 365, including the ability to set or change backup configurations, perform restores, download data, and view data. +Granular control | Providing detailed permissions to administrators to manage data protection operations and maintain security. + +## Cascading support + +Feature | Description +---|--- +Data relationships | Supporting cascading effects for data tables based on Dataverse relationships, such as child-to-parent and parent-to-child deletions, linkages, and restores.Cascading support ensures that changes made to data tables are reflected appropriately across related tables, maintaining data integrity and consistency. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_microsoft_dataverse.md b/microsoft_dynamics_365_d365_microsoft_dataverse.md new file mode 100644 index 0000000000000000000000000000000000000000..ee44af795aabf4dcd4adf491fdb9246a97454ea5 --- /dev/null +++ b/microsoft_dynamics_365_d365_microsoft_dataverse.md @@ -0,0 +1,21 @@ +# Dynamics 365 and Microsoft Dataverse + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_microsoft_dataverse.html + +--- + +# Dynamics 365 and Microsoft Dataverse + +Microsoft Dataverse is a data storage platform that stores the data associated with the Microsoft Dynamics 365 application. + +Microsoft Dynamics 365 Customer Relationship Management (CRM) applications, such as Sales and Service, use Microsoft Dataverse as their data storage platform. Microsoft Dataverse stores the data associated with these Microsoft Dynamics 365 applications. + +In Microsoft Dynamics 365, all data and metadata are organized into tables within Dataverse. The data in Dataverse follows a relational structure, meaning it consists of multiple related tables. Each table contains rows and attributes. You can access this data and metadata through Web APIs. + +In the context of Microsoft Dynamics 365, metadata can be broadly categorized into two types: + + * Table metadata: This includes information about the tables or the data they contain. The table metadata encompasses properties such as table relationships, data item attributes, and the interactions between data items. + * Global metadata: This metadata type spans across all tables or pertains to the overall Microsoft Dynamics 365 environment. An example is global option sets, which are reusable sets of options that you can share across multiple tables and fields. + +For each Microsoft Dynamics 365 environment, individual tables in the Dataverse are protected and become workload. The metadata corresponding to these tables is stored as part of these workloads. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_planning_protection.md b/microsoft_dynamics_365_d365_planning_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..7d0d1f1dfeb7e9c5ba08f6636cc1e9e09348dc9e --- /dev/null +++ b/microsoft_dynamics_365_d365_planning_protection.md @@ -0,0 +1,14 @@ +# Planning for Dynamics 365 protection + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_planning_protection.html + +--- + +# Planning for Dynamics 365 protection + +Before setting up a Microsoft Dynamics 365 subscription in RSC, you need to plan user and access management for designated RSC users. This planning also involves reviewing the permissions that RSC requires in your Microsoft Dynamics 365 environment to protect your Microsoft Dynamics 365 workloads. + +When planning Microsoft Dynamics 365 protection, it is important to understand the Role-based Access Control (RBAC) mechanisms of RSC. You need to establish a clear framework for user and access management. This ensures secure and efficient operations within your Microsoft Dynamics 365 environment. You can start by categorizing your RSC users based on their roles and responsibilities and by assigning appropriate privileges through roles to limit access according to the principle of least privilege. + +Additionally, it is important that you review the specific permissions that RSC requires to protect your Microsoft Dynamics 365 workloads. Understanding these permissions helps explain why they are needed. This ensures clarity on the operations that protect your Microsoft Dynamics 365 workloads. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_protection_setup.md b/microsoft_dynamics_365_d365_protection_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..3f786311801b7b31916fc2e509e70dca84a30db3 --- /dev/null +++ b/microsoft_dynamics_365_d365_protection_setup.md @@ -0,0 +1,20 @@ +# Dynamics 365 workload protection setup + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_protection_setup.html + +--- + +# Dynamics 365 workload protection setup + +You can set up SLA Domains to apply data protection policies, ensuring automatic protection of Microsoft Dynamics 365 workloads. + +Rubrik SLA Domains offer a structured way to apply data protection policies across various Microsoft Dynamics 365 subscriptions ensuring consistent and reliable backup and recovery processes. An SLA Domain is a set of policies that defines the backup and recovery objectives for your Dynamics 365 workloads. These policies specify the frequency of snapshots and the retention period for these snapshots. + +By assigning SLA Domains to a Microsoft Dynamics 365 subscription, you ensure that your data protection strategies align with your organizational requirements and compliance standards. + +After you add a Microsoft Dynamics 365 subscription to RSC, you can create one or more customized SLA Domains to begin protecting Microsoft Dynamics 365 workloads. Although RSC provides Silver Lite and Bronze Lite SLA Domains, these defaults may not fully meet the specific requirements of your organization. Creating customized SLA Domains allows for precise control over snapshot frequency and retention periods, ensuring alignment with your organizational and compliance standards. After creation, you can assign these customized SLA Domains to the Microsoft Dynamics 365 subscription. RSC then starts creating and expiring snapshots to protect the relevant workloads based on the parameters defined in the assigned SLA Domain. + +Note: + +You can assign an SLA Domain only at the Microsoft Dynamics 365 subscription level. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_reporting.md b/microsoft_dynamics_365_d365_reporting.md new file mode 100644 index 0000000000000000000000000000000000000000..eb9bdef8fd5584bce443af52ae9394e13e721368 --- /dev/null +++ b/microsoft_dynamics_365_d365_reporting.md @@ -0,0 +1,21 @@ +# Dynamics 365 reporting + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_reporting.html + +--- + +# Dynamics 365 reporting + +You can create and download reports for Dynamics 365 data protection to view status information about a subscription. + +To view status information, you can create reports based on the available templates. RSC provides the following report templates for Dynamics 365 subscription: + + * Compliance: + * Protection + * Protection task details + * Recovery task details + +You can create views of the most commonly used system metrics by using the Reporting feature. You can use the data gathered in the reports to perform audits and data management planning. + +Reports contain data for instances with access to RSC. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_setup.md b/microsoft_dynamics_365_d365_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..d8c208d5bae38de6ea08dbcdc2ceb6e0914934cc --- /dev/null +++ b/microsoft_dynamics_365_d365_setup.md @@ -0,0 +1,17 @@ +# Dynamics 365 setup + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_setup.html + +--- + +# Dynamics 365 setup + +You can set up a Microsoft Dynamics 365 subscription in RSC and start protecting your Microsoft Dynamics 365 environments. + +Setting up a Microsoft Dynamics 365 subscription in RSC to protect your Dynamics 365 environments involves detailed planning. This process includes: + + * Referring to the recommendations from Rubrik for adding a Microsoft Dynamics 365 subscription. + * Learning about the required permissions. + +After you complete the planning, you can proceed with adding your Microsoft Dynamics 365 subscription to RSC. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_table_analysis.md b/microsoft_dynamics_365_d365_table_analysis.md new file mode 100644 index 0000000000000000000000000000000000000000..5225cba53875a2ef1b9911ec766ba8c29638fb22 --- /dev/null +++ b/microsoft_dynamics_365_d365_table_analysis.md @@ -0,0 +1,20 @@ +# Dynamics 365 table analysis + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_table_analysis.html + +--- + +# Dynamics 365 table analysis + +RSC generates comprehensive insights about the changes in Microsoft Dynamics 365 data, making it easier to analyze and restore data securely. + +You can view detailed insights about the changes in your Microsoft Dynamics 365 tables before restoring the data. With the data analysis capability, you can monitor and analyze the additions, deletions, and modifications in the Microsoft Dynamics 365 environment. By identifying any suspicious activity and unusual spikes or patterns in the modified records, you can reduce the risk of data breaches and ensure compliance with data protection regulations. If you notice any issue, you can selectively restore the required records from a snapshot taken before the update to ensure minimal disruption. + +## Data changes visualization with interactive graphs + +RSC displays a comprehensive graph that represents the changes in Microsoft Dynamics 365 data over a seven-day period. The graph includes three lines for added, deleted, and modified records. By clicking a specific date on the graph, you can view the records that were changed on that day. You can use additional filters to narrow down the records you want to see and use the column picker to show more columns for the records. You can analyze the records and decide whether to restore them from a snapshot. + +## Comparison of records for detailed analysis + +You can download the records to review and compare the record changes in the table. When you download the records, RSC provides a ZIP file containing two CSV files. One CSV file has the record values from the selected date, while the other CSV file contains the record values from the previous snapshot. Comparing these CSV files helps you to identify changes in the Microsoft Dynamics 365 data and take appropriate actions. + *[ > ]: and then diff --git a/microsoft_dynamics_365_d365_viewing_events.md b/microsoft_dynamics_365_d365_viewing_events.md new file mode 100644 index 0000000000000000000000000000000000000000..c84eafe149c0c342ea42a9e76c7d2f6d12c05666 --- /dev/null +++ b/microsoft_dynamics_365_d365_viewing_events.md @@ -0,0 +1,29 @@ +# Viewing events for Dynamics 365 + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/d365_viewing_events.html + +--- + +# Viewing events for Dynamics 365 + +View the Events page from the Dashboard to see the events for Dynamics 365 subscription. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click Events. + +The Events page appears and displays only the events for SaaS workloads. + + 4. **Optional:** Select filters to apply to the events. + +The available filters are Time Range, Severity, Status, Event Type, Object Type, and Instance. + +## Results + +RSC fills the Event Logs page with the aggregate values based on the selected filter and displays the Dynamics 365 events. You can click an event to view the series of events leading up to it. + *[ > ]: and then diff --git a/microsoft_dynamics_365_microsoft_dynamics_365.md b/microsoft_dynamics_365_microsoft_dynamics_365.md new file mode 100644 index 0000000000000000000000000000000000000000..0a3c6f69440fd6c0395d2986796b1f748d283f3f --- /dev/null +++ b/microsoft_dynamics_365_microsoft_dynamics_365.md @@ -0,0 +1,29 @@ +# Microsoft Dynamics 365 + +Source: https://docs.rubrik.com/en-us/saas/microsoft_dynamics_365/microsoft_dynamics_365.html + +--- + +# Microsoft Dynamics 365 + +RSC protects the tables and metadata in your Microsoft Dynamics 365 subscription. + +Microsoft Dynamics 365 is a set of intelligent business applications that help you run your entire business and achieve better results through predictive and AI-driven insights. It offers a suite of applications that combine Customer Relationship Management (CRM) and Enterprise Resource Planning (ERP) capabilities on a cloud-based platform. These applications and services enable you to manage various operations, including sales, customer service, field service, finance, operations, and marketing. Given the importance of the data stored in Microsoft Dynamics 365, it is imperative to have a reliable backup and recovery solution in place. + +Note: + +Rubrik supports data protection only for the Microsoft Dynamics 365 CRM module. + +By adding a Microsoft Dynamics 365 CRM module subscription to RSC, you can: + + * Ensure data protection: Automatically back up essential data elements, including both table and metadata, reducing the risk of data loss. + * Facilitate data recovery: Quickly restore Microsoft Dynamics 365 data to a previous state in case of accidental deletion, corruption, or other data loss incidents. + * Simplify compliance: Meet industry regulations and internal compliance standards by maintaining secure and retrievable backups of your Microsoft Dynamics 365 data. + +Protecting Microsoft Dynamics 365 workloads with RSC involves a strategic approach to ensure comprehensive and consistent data protection across the cloud infrastructure of an organization. To simplify the protection of your Microsoft Dynamics 365 workload, RSC breaks down the tasks into three main categories, Authorization, Configuration, and Protection. + +Task category | Description +---|--- +Authorization | For authorization, you grant RSC secure access to your Microsoft Dynamics 365 subscription that needs protection. You can provide authorization to RSC while adding the subscription. +Configuration | For configuration, you set up SLA Domains to protect Microsoft Dynamics 365 workloads automatically, according to your business objectives. +Protection | For protection, you enforce data security by assigning SLA Domains to Microsoft Dynamics 365 workloads. diff --git a/mongodb_logical_backup_recv_mdb_protection.md b/mongodb_logical_backup_recv_mdb_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..010ec3aa667666b73ecce3b6433047bf51c6b513 --- /dev/null +++ b/mongodb_logical_backup_recv_mdb_protection.md @@ -0,0 +1,22 @@ +# Logical backup and recovery for MongoDB database protection + +Source: https://docs.rubrik.com/en-us/saas/mongodb/logical_backup_recv_mdb_protection.html + +--- + +# Logical backup and recovery for MongoDB database protection + +RSC protects your MongoDB databases, ensuring optimal storage efficiency and streamlined database operations through advanced security features and robust data protection. + +The following are some of the key features of MongoDB logical backup and recovery in RSC: + + * Utilizes a Zero-Trust model with the Rubrik cluster. + * Provides immutable backups that protect against ransomware attacks, ensuring that data is always recoverable. + * Facilitates granular, collection-level recovery with any-point-in-time recoverability, enabling precise data recovery. + * Implements SLA Domain-based protection and centralized reporting uniformly across all workloads, making it easier to manage the databases. + * Serves as a Single Point of Governance (SPOG), resulting in low Total Cost of Ownership (TCO). + * Automatically discovers and protects all objects. + * Offers retention lock for MongoDB sources, databases, and collections. + * Supports Cloud Cluster Elastic Storage (CCES) on AWS, Azure, and GCP. + + *[ > ]: and then diff --git a/mongodb_mongodb_db_protection.md b/mongodb_mongodb_db_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..dde893b508785cabf45cd2584ab7f2b1bde8de07 --- /dev/null +++ b/mongodb_mongodb_db_protection.md @@ -0,0 +1,21 @@ +# MongoDB database protection + +Source: https://docs.rubrik.com/en-us/saas/mongodb/mongodb_db_protection.html + +--- + +# MongoDB database protection + +With the MongoDB protection feature, you can use SLA Domains to apply data protection and management policies to MongoDB workloads to ensure optimal protection. + +You can assign SLA Domains to protect your MongoDB databases by configuring backup frequencies and retention periods according to your requirements. You can also configure authentication methods and granular, role-based access control (RBAC) for enhanced security. MongoDB databases automatically inherit the SLA Domain assigned to their sources. You can, however, override this assignment manually and assign a specific SLA Domain to individual databases. With this level of granularity, you can configure the data protection settings for each MongoDB database according to your requirements. + +When you install Rubrik Backup Service (RBS) on the MongoDB host, the Rubrik cluster automatically discovers the MongoDB host and all MongoDB database instances running on it. The cluster can then create database snapshots and manage retention, replication, and archiving for these snapshots. These tasks perform according to the SLA Domain policies assigned to, or inherited by, each discovered database. + +Database and backup administrators use the cluster to perform these management activities for MongoDB databases: + + * Managing point-in-time copies of MongoDB databases through snapshots facilitates capturing the state of a database at a specific point, enabling recovery of the database to minimize downtime. + * Recovering entire databases or granular data points from specified snapshots ensures fast data retrieval while minimizing downtime. + * Restoring entire MongoDB databases from specified snapshots minimizes downtime. + + *[ > ]: and then diff --git a/mongodb_mongodb_workloads.md b/mongodb_mongodb_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..5da3a426b214326b16c526458a4338c064396b7e --- /dev/null +++ b/mongodb_mongodb_workloads.md @@ -0,0 +1,15 @@ +# MongoDB workloads + +Source: https://docs.rubrik.com/en-us/saas/mongodb/mongodb_workloads.html + +--- + +# MongoDB workloads + +Rubrik Security Cloud protects your MongoDB sources, databases, and collections, ensuring optimal storage efficiency and smooth database operations with its advanced security features and strong data protection. + +Rubrik Security Cloud (RSC) offers comprehensive MongoDB backup solutions to ensure data security and integrity. These solutions include both logical and physical integration. The following are the two integration methods: + + * Logical Backup and Recovery: RSC supports logical backups for MongoDB workloads by taking snapshots without relying on any APIs, ensuring seamless backup operations. An Enterprise Advanced (EA) License, Community Edition, and Percona MongoDB are necessary to access Logical Backup and Recovery. + * Physical Backup and Recovery via Ops Manager: RSC protects MongoDB sources with physical backups by utilizing MongoDB vendor-certified Ops Manager APIs to perform backups, securely transferring data from host machines to the Rubrik cluster for backup and restore. A MongoDB EA license is necessary to access Physical Backup and Recovery via Ops Manager. + diff --git a/mongodb_physical_backup_recv_mdb_ops_mgr.md b/mongodb_physical_backup_recv_mdb_ops_mgr.md new file mode 100644 index 0000000000000000000000000000000000000000..5a4a16a949db5189de6351cb15329b0248150441 --- /dev/null +++ b/mongodb_physical_backup_recv_mdb_ops_mgr.md @@ -0,0 +1,24 @@ +# Physical backup and recovery of MongoDB sources using Ops Manager + +Source: https://docs.rubrik.com/en-us/saas/mongodb/physical_backup_recv_mdb_ops_mgr.html + +--- + +# Physical backup and recovery of MongoDB sources using Ops Manager + +A MongoDB source is a single MongoDB deployment that contains a list of databases and collection objects. RSC protects MongoDB data using the Physical Backup and Recovery via Ops Manager integration method for backups, transferring data from host machines to the Rubrik cluster for secure storage and recovery. + +RSC protects MongoDB sources by using MongoDB certified Ops Manager APIs to perform physical backups, transferring data from host machines to the Rubrik cluster for secure backup and restore. Additionally, RSC also supports incremental backup using the Ops Manager APIs. RSC supports all operations at the source level, not at the database or collection level. + +RSC provides the following key capabilities while backing up and protecting MongoDB sources: + + * Discovers databases automatically after adding the MongoDB source. + * Implements full and incremental backups driven by SLA Domain-driven, along with on-demand snapshots of MongoDB source. + * Enables restoration of MongoDB sources to either the same or a different target. + * Supports log backup and point-in-time recovery of MongoDB sources. + * Facilitates archival and replication of MongoDB source snapshots. + * Provides a unified platform for managing protection, reporting, and compliance. + * Offers retention lock for MongoDB source snapshots. + * Supports Cloud Cluster Elastic Storage (CCES) on AWS, Azure, and GCP. + + *[ > ]: and then diff --git a/mongodb_prereq_mongodb_workload_protection.md b/mongodb_prereq_mongodb_workload_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..6fe1f4268d6928705332768a7641c908ec38e3ec --- /dev/null +++ b/mongodb_prereq_mongodb_workload_protection.md @@ -0,0 +1,36 @@ +# Prerequisites for MongoDB workload protection + +Source: https://docs.rubrik.com/en-us/saas/mongodb/prereq_mongodb_workload_protection.html + +--- + +# Prerequisites for MongoDB workload protection + +RSC has some prerequisites and general requirements for protecting MongoDB workloads. + +Table 1. PrerequisitesThe following table describes the prerequisite tasks for MongoDB logical backup and recovery. Prerequisite task | Description +---|--- +Rubrik cluster | You must configure the Rubrik cluster in RSC before adding it to the MongoDB environment. +RBS | You must remove older versions of RBS from the MongoDB host.You must use the wget command to copy new versions of RBS from the Add Host workflow into the MongoDB hosts.For example, `wget path-to-rbs-rpm--no-check-certificate`, where path-to-rbs-rpm is the path provided byRSC.You must download and install the latest RBS installer on all the hosts running MongoDB nodes. +NFS utility | You must install the `nfs-utils` package on all hosts running MongoDB nodes. +SLA Domain | You must assign SLA Domains to sources and databases to start protecting the MongoDB objects. +Roles | You must create roles with permissions for backup and restore operations in the MongoDB environment. +MongoDB user permissions | It is important to grant specific permissions to MongoDB authenticated users at the cluster, database, and collection levels.You must configure the MongoDB user on all mongos instances and individual shards in a sharded MongoDB deployment.Following are the commands for view permissions: + + * Cluster-level actions: `getCmdLineOpts, listDatabases, replSetGetConfig, replSetGetStatus` + * Database-level actions: `collStats, find, dbStats, listCollections, listIndexes` + * Collection actions:` local.oplog.rs find` + * Database actions: `rubrik_backup_agent_db convertToCapped, createCollection, createIndex, insert, update` + + +Time series collections | RSC does not support backups for time series collections.You must assign Don't Protect to the time series collection and the internal collections belonging to system.* before assigning an SLA when a MongoDB database includes any time series collections. + +Table 2. General requirementsThe following table describes the requirements for MongoDB workloads. Requirement | Description +---|--- +MongoDB deployment | On-premise or on-cloud IaaS replica set +MongoDB version | Versions 4.0, 5.0, and 6.0 on CentOS, RHEL, or Ubuntu +Rubrik CDM version | Version 9.0.1 or later +Allowlist ports | MongoDB nodes require ports 12800 and 12801 to enable communication between the Rubrik cluster and Rubrik Backup Service (RBS).MongoDB nodes require ports 32764 through 32769 to enable communication between Rubrik clusters and MongoDB instances during backup and recovery operations.Hosts running MongoDB nodes must have ports 111 and 2049 accessible to support NFS exports.The Rubrik port specifications topic in Rubrik CDM User Guide provides more information about port requirements. +MongoDB host space | Each MongoDB host requires at least 10GB of free space in the `/var` directory for the log backups to continue running without interruption.If your MongoDB host does not have 10GB of space available in the `/var` directory, you can change the default log backup directory path before adding the MongoDB source. +Direct recovery | Direct recovery of collections and databases requires you to permit connections to the MongoDB instance from the cluster nodes. If the cluster uses SSL for authentication, RSC temporarily copies your SSL certificates to the cluster and removes them after the recovery. Direct recovery of replica sets requires you to permit connections to the primary shard member of the deployment. Direct recovery of sharded deployments requires you to permit connections to the mongos instances of the deployment. Note: If you do not want to permit these connections or copy certificates temporarily to the cluster, you can perform standard recovery through the host. + *[ > ]: and then diff --git a/mongodb_protecting_mongodb_workload.md b/mongodb_protecting_mongodb_workload.md new file mode 100644 index 0000000000000000000000000000000000000000..6ccb30610b6c70eebf6eba0be9e983cb133e6151 --- /dev/null +++ b/mongodb_protecting_mongodb_workload.md @@ -0,0 +1,53 @@ +# Protecting a MongoDB workload + +Source: https://docs.rubrik.com/en-us/saas/mongodb/protecting_mongodb_workload.html + +--- + +# Protecting a MongoDB workload + +To ensure the security of your MongoDB workload, protect it by implementing a data protection policy. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the MongoDB inventory card. + +The MongoDB page appears. + + 5. Select a MongoDB source and click Manage Protection. + +You can select multiple MongoDB sources. + +The Manage Protection wizard appears. + + 6. Select a protection option. + +Option| Description +---|--- +SLA Domain | Assigns the SLA Domain to the selected objects.A Confirmation wizard appears, displaying a summary of SLA Domain, including the frequency and retention details of existing snapshots. +Don't protect | Excludes the selected objects from all further SLA Domain assignments and protection.The Don't Protect wizard appears, displaying a message that the selected objects have been excluded from any future assignments to the SLA Domain. +Clear existing assignment | Derives the SLA Domain from the next higher level object, based on inheritance rules.The Inherit SLA Domain wizard appears, displaying a message that the selected objects inherits the SLA Domain assignment of the next higher level object. + + 7. (Don't protect) In Existing snapshot retention, select an option for the existing unprotected snapshots. + +Option| Description +---|--- +Use current SLA Domain for retention | Derives the retention period from the current SLA Domain.This is the default option. +Expire immediately | Deletes the snapshots from the cluster. + + 8. Click Next. + 9. Click Assign. + +## Results + +RSC processes the specified assignments and begins protecting the selected MongoDB workloads according to the assignments. + *[ > ]: and then diff --git a/mysql_mysql.md b/mysql_mysql.md new file mode 100644 index 0000000000000000000000000000000000000000..7c27c52f721193cdad247315756a736108fe160e --- /dev/null +++ b/mysql_mysql.md @@ -0,0 +1,13 @@ +# MySQL + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql.html + +--- + +# MySQL + +RSC protects the MySQL databases from accidental deletions, ransomware attacks, and other potential threats. + +As organizations rely on MySQL databases to power critical applications, whether deployed on-premises or in various cloud environments, there are growing complexities in ensuring the protection, management, and security of this vital data. Complex MySQL deployments are particularly susceptible to threats to data integrity and operational stability, exposing your business to the risks of data breaches, accidental data loss, and ransomware attacks. While the providers of underlying infrastructure secure their foundational services, you are responsible for the data residing within the MySQL databases. This includes data backup, recovery, and security against potential threats. + +Rubrik provides a streamlined, SaaS-based solution to manage these challenges with Rubrik Security Cloud (RSC). RSC secures and automates data protection processes for MySQL databases, ensuring that your critical data remains protected against accidental deletions, ransomware attacks, and other potential threats. With RSC, you can automate backup, recovery, and replication schedules for your MySQL databases. This ensures the continuous availability and resilience of your critical MySQL data, enabling you to meet stringent Recovery Point Objectives (RPOs) and Recovery Time Objectives (RTOs), while maintaining robust data governance and compliance. diff --git a/mysql_mysql_common_protection_terms.md b/mysql_mysql_common_protection_terms.md new file mode 100644 index 0000000000000000000000000000000000000000..fd5fafb300d7d9d502872bff3b896750eac501f1 --- /dev/null +++ b/mysql_mysql_common_protection_terms.md @@ -0,0 +1,26 @@ +# Common MySQL protection terms + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_common_protection_terms.html + +--- + +# Common MySQL protection terms + +It is important to understand some common terms when protecting MySQL instances with RSC. + +By learning the common MySQL protection terms, you can better understand and navigate the steps and components involved in protecting your MySQL instances. + +Term | Definition +---|--- +MySQL instance | A running MySQL server that manages one or more databases. This is the primary entity that RSC protects. You can recover MySQL workloads at the instance level. +MySQL database | A structured collection of tables, views, stored procedures, and other objects managed by a MySQL instance. You can recover MySQL workloads at the database level. +Table (Storage Engine) | The fundamental data structure within a MySQL database, organized into rows and columns, where the actual data resides. +Binary log (Binlog) | A log of data modification activities, including table creations, data alterations, and statements that may have impacted the data. Binlog is important for replication and point-in-time recovery in MySQL. +MySQL host | The physical or virtual machine on which one or more MySQL instances are running and is registered with RSC for protection. +MySQL workload | The MySQL instance and its associated databases that RSC protects and manages. +SLA Domain | A RSC feature that you configure to define policies for data protection, including snapshot frequency, retention duration, archival and replication targets. For binary logs, you can also configure log snapshot frequency and retention. You apply these policies to MySQL workloads for consistent and automated data protection. +Snapshot | A point-in-time copy of a protected MySQL workload that RSC captures. You can use these snapshots for recovery operations. +Archival location | A configured external storage target where RSC moves the MySQL snapshots for long-term, cost-effective retention according to SLA Domain policies. +Replication target | A secondary Rubrik cluster or Rubrik Cloud Cluster (RCC) where MySQL snapshots are replicated from a source Rubrik cluster, providing an offsite copy for disaster recovery purposes. +Retention lock | A security feature in RSC that provides mechanisms to enforce immutable retention periods on backups, preventing unauthorized deletion or modification of data for compliance and legal requirements. You can configure retention lock in your SLA Domain. You cannot reduce the retention period in a retention locked SLA Domain, as it may lead to premature deletion of the snapshots. + *[ > ]: and then diff --git a/mysql_mysql_high_level_architecture.md b/mysql_mysql_high_level_architecture.md new file mode 100644 index 0000000000000000000000000000000000000000..57e3a3514caa4a0ccf0f3812c47cc142c7d6e3b1 --- /dev/null +++ b/mysql_mysql_high_level_architecture.md @@ -0,0 +1,33 @@ +# High-level architecture for MySQL protection + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_high_level_architecture.html + +--- + +# High-level architecture for MySQL protection + +A high-level architectural overview of how RSC protects your MySQL databases. + +By using an agent-based approach, RSC protects MySQL databases running on physical or virtual hosts. You can achieve this by installing a lightweight Rubrik Backup Service (RBS) on the MySQL host machine. The RBS communicates securely with the Rubrik cluster and manages the backup and recovery operations, enabling you to protect your MySQL instances, manage the snapshot lifecycle, and perform granular, point-in-time recoveries. + +The following image describes a high-level architectural diagram illustrating the protection workflow for MySQL databases: + +At a high level, Rubrik uses the following workflow to protect MySQL databases: + + 1. Agent installation and discovery: You begin by installing the RBS package on the host machine running the MySQL database. After installation, RSC securely communicates with the agent to automatically discover the MySQL instances on the host for protection. + 2. Secure communication: All commands and control signals between RSC and the RBS transmit over a secure and authenticated channel over secure Thrift API. This ensures that all operations, from initiating backups to triggering restores, are secure. + 3. Backup and data ingestion: Rubrik supports three types of backups for MySQL databases. + * Full backups for MyIASM tables + * Full and Incremental backups for InnoDB tables + * Binary Log backups for MyIASM & InnoDB tables + +The following list outlines the backup processes of MySQL databases: + * Full and incremental backups: When RSC initiates a backup as per the assigned SLA Domain, RSC instructs the RBS to begin the process. RBS uses bundled MySQL backup and cluster scripts to interact with the MySQL instance using the native MySQL client binary. The backup data then transfers from the MySQL data directory to the Rubrik cluster through secure Thrift layer that enables parallel data ingestion for high performance. + * Log backups: For point-in-time recovery, the SLA Domain also schedules frequent log backups. The RBS also captures these logs and sends them to the Rubrik cluster over the same secure and efficient data path. + + 4. Snapshot lifecycle management: After the backup data and logs are ingested, RSC manages them as immutable snapshots. The SLA Domain policies dictate the frequency of backups, the retention period for the snapshots, and replication or archival policies for long-term retention and disaster recovery. + 5. Recovery workflow: RSC provides flexible recovery options for your MySQL databases. + * Data restore (full restore): To restore a full backup, you initiate the task from RSC. RSC presents the snapshot data to the target host through a secure read-mount over the Network File System (NFS v3) protocol. The MySQL backup and cluster scripts on the host then manage the process of restoring the data to the MySQL instance. + * Log restore (point-in-time recovery): To recover to a specific point in time, you can perform a log restore. The log data is restored directly to the agent over the secure Thrift channel, not using NFS. This allows for granular recovery to a precise moment, minimizing data loss. + + *[ > ]: and then diff --git a/mysql_mysql_planning_protection.md b/mysql_mysql_planning_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..98f0d721c7f723c677cb7b201c0610aaf84f34e6 --- /dev/null +++ b/mysql_mysql_planning_protection.md @@ -0,0 +1,19 @@ +# Planning for MySQL protection + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_planning_protection.html + +--- + +# Planning for MySQL protection + +Before setting up a MySQL instance in RSC, it is necessary to plan user and access management for designated RSC users. This planning also involves reviewing the permissions that RSC requires in your MySQL environment to protect your MySQL instance. + +When planning MySQL protection, understanding the Role-based Access Control (RBAC) mechanisms of RSC is important and establishing a clear framework for user and access management is necessary. This ensures secure and efficient operations within your MySQL environment. You can start by categorizing your RSC users based on their roles and responsibilities and by assigning appropriate privileges through roles to limit access according to the principle of least privilege. + +Additionally, it is important to: + + * Review the specific permissions that RSC requires to protect MySQL instances. Understanding these permissions helps explain why they are needed. This ensures clarity on the operations that protect your MySQL instances. + + * Review RSC limitations when protecting MySQL instances with RSC. Understanding these limitations helps to avoid unexpected issues and ensures successful protection. + + *[ > ]: and then diff --git a/mysql_mysql_protection_key_features.md b/mysql_mysql_protection_key_features.md new file mode 100644 index 0000000000000000000000000000000000000000..a49e44dfdb91bebba9a86769c9176d3d548d9f9b --- /dev/null +++ b/mysql_mysql_protection_key_features.md @@ -0,0 +1,70 @@ +# Key features of MySQL protection + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_protection_key_features.html + +--- + +# Key features of MySQL protection + +RSC provides unified data management, automated global data protection, various recovery options for MySQL databases, and advanced security features to protect your critical data. + +RSC offers a comprehensive suite of features to protect and manage your MySQL instances. + +## Unified data management + +Feature | Supported CDM versions | Description +---|---|--- +RSC data protection | 9.4.0 or later | Provides a SaaS platform for managing and protecting MySQL databases across various deployment environments, such as cloud or on-premises. +Consolidated monitoring and reporting | 9.4.0 or later | Offers unified reporting to track SLA Domain assignment, protection and recovery activities, and SLA Domain policy compliance for your MySQL workloads. +Comprehensive dashboard | 9.4.0 or later | Enables you to manage all your MySQL instances, backups, and recovery operations from a single, unified interface within RSC, streamlining administrative tasks and reducing complexity. + +## Automated global data protection through SLA Domains + +Feature | Supported CDM versions | Description +---|---|--- +Protection policies | 9.4.0 or later | Assigns and manages protection policies, known as SLA Domains, for MySQL instances to ensure that backup and recovery operations meet defined business needs, RTO, or RPO requirements. +Automated backups | 9.4.0 or later | Utilizes SLA Domains to automate backups of your MySQL instances, setting schedules to regularly protect your MySQL data without manual intervention. + +## Backup and recovery + +Feature | Supported CDM versions | Description +---|---|--- +On-demand backups | 9.4.0 or later | Enables you to take backups of your MySQL instances anytime as needed, providing the flexibility to protect data outside of predefined schedules. +Instance-level backup | 9.4.0 or later | Supports taking comprehensive backups at the MySQL instance-level, capturing all databases and associated data within that instance.Rubrik MySQL native protection supports two types of storage engines: + + * InnoDB: Supports forever incremental backup for InnoDB storage engine + * MyISAM: Supports only full backup + + +Granular recovery | 9.4.0 or later | Provides the ability to restore entire MySQL instances or specific MySQL databases from a backup, offering flexibility in data recovery scenarios.Rubrik MySQL protection also provides the capability to back up binary logs. This is required for point-in-time recovery. +Archival | 9.4.0 or later | Enables long-term retention of MySQL snapshots by tiering them to lower-cost archival storage, such as cloud object storage, for compliance and cost efficiency. +Snapshot replication | 9.4.0 or later | Facilitates the replication of MySQL backup snapshots to other Rubrik clusters for disaster recovery purposes, ensuring offsite data availability. +Retention lock | 9.4.0 or later | Provides mechanisms to enforce immutable retention periods on backups, preventing unauthorized deletion or modification of data for compliance and legal requirements. You can configure retention lock while configuring SLA Domain. You cannot reduce the retention period in a retention locked SLA Domain, as it may lead to premature deletion of the snapshots. +High Availability (HA) | 9.4.0 or later | Rubrik supports the following MySQL deployment types: + + * Standalone and primary-secondary (InnoDB and MyISAM) + * InnoDB Replica Set + * InnoDB Cluster + + + +## Security and access control + +Feature | Supported CDM versions | Description +---|---|--- +Role-based Access Control (RBAC) | 9.4.0 or later | Offers granular permissions to administrators to manage data protection operations for MySQL workloads, ensuring security and compliance with organizational access policies. +Secure connectivity | 9.4.0 or later | Establishes secure communication channels for data transfer and management operations between MySQL instances and RSC.The methods for secure communication and data transfer between MySQL instances and RSC are as follows: + + * Management and control operations using either socket-based or TCP-based authentication, and configuring SSL for secure connectivity. + * Transferring backup data using secure thrift. + * Restoring data over NFS. + * Restoring logs using secure thrift. + + + +## Networking + +Feature | Supported CDM versions | Description +---|---|--- +VLAN support | 9.4.1 or later | Enables VLAN compatible IP addresses for NFS mounts during restore operations. This ensures that you can perform data restoration over the NFS layer within a secure, VLAN segmented network. + *[ > ]: and then diff --git a/mysql_mysql_protection_setup.md b/mysql_mysql_protection_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..dab03eeb8c816da7817db8859ae767fa70c0da20 --- /dev/null +++ b/mysql_mysql_protection_setup.md @@ -0,0 +1,16 @@ +# MySQL protection setup + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_protection_setup.html + +--- + +# MySQL protection setup + +Protect MySQL instances using automated, policy-driven backups, ensuring data resilience and compliance with organizational standards. + +RSC offers robust data protection capabilities for MySQL instances. By adding MySQL instances to RSC, you can maintain the availability and resilience of your critical database environments. + +RSC provides automated, policy-driven backup and recovery for MySQL instances using SLA Domains, to help safeguard data against loss, corruption, or cyber threats. The SLA Domain feature offers a structured way to apply data protection policies to MySQL instances, ensuring consistent and reliable backup and recovery processes. An SLA Domain is a set of policies that defines the backup and recovery objectives for your data. These policies specify the frequency of snapshots, the retention period for these snapshots, and the archiving and replication requirements. + +Assigning SLA Domains to a MySQL instance helps align the data protection strategies with your organizational requirements and compliance standards. After you assign an SLA Domain to a MySQL instance, RSC creates, archives, replicates, and expires snapshots to protect the MySQL instance, based on the parameters defined in the SLA Domain. + *[ > ]: and then diff --git a/mysql_mysql_recovery.md b/mysql_mysql_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..71c23f692944889d55a7cc3fd4b3384c7224da5d --- /dev/null +++ b/mysql_mysql_recovery.md @@ -0,0 +1,16 @@ +# MySQL recovery + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_recovery.html + +--- + +# MySQL recovery + +After RSC takes snapshots of your MySQL workloads, you can recover the required workloads using different recovery options. + +RSC offers comprehensive recovery capabilities for MySQL instances and databases. These options ensure rapid restoration and business continuity. By leveraging automated, policy-driven snapshots and maintaining immutable backups, RSC significantly reduces recovery time objectives (RTOs) and recovery point objectives (RPOs) for MySQL workloads, regardless of their deployment location. This approach provides a critical layer of defense, making your MySQL data highly recoverable and protected against evolving threats such as ransomware. + +RSC offers versatile options for restoring MySQL data to meet various operational needs and disaster scenarios. The choice of recovery target dictates how the restored data integrates back into your environment. You can restore data back to the original MySQL instance from which you backed up or to a new instance. + +You can also perform MySQL database recovery to enable the restoration of individual databases within an instance. This targeted approach is useful when you only want to recover specific data. + *[ > ]: and then diff --git a/mysql_mysql_setup.md b/mysql_mysql_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..7e4544df3637f9d2357214a2c7635d8df24de473 --- /dev/null +++ b/mysql_mysql_setup.md @@ -0,0 +1,12 @@ +# MySQL setup + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_setup.html + +--- + +# MySQL setup + +You can protect MySQL database using RSC by configuring MySQL hosts and instances with it. This setup automates backups and enables rapid recovery from threats such as ransomware, providing unified data security and resilience for your MySQL databases. + +RSC protects MySQL databases by integrating the Linux hosts and instances. This involves installing the Rubrik Backup Service (RBS) agent on each host to enable communication and data transfer. After you install RBS on the MySQL host, RSC discovers MySQL instances and enables you to configure them with necessary credentials. This setup automates backups, provides unified data security, and enables rapid recovery from threats such as ransomware for your MySQL databases. + *[ > ]: and then diff --git a/mysql_mysql_unmounting_restore_mp.md b/mysql_mysql_unmounting_restore_mp.md new file mode 100644 index 0000000000000000000000000000000000000000..fa709290ed07268b6acc2963262e59a05df4101f --- /dev/null +++ b/mysql_mysql_unmounting_restore_mp.md @@ -0,0 +1,35 @@ +# Unmounting the restore mount point after MySQL snapshot recovery + +Source: https://docs.rubrik.com/en-us/saas/mysql/mysql_unmounting_restore_mp.html + +--- + +# Unmounting the restore mount point after MySQL snapshot recovery + +After recovering MySQL snapshots, unmount the restore mount point to remove the metadata associated with the selected MySQL cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Live Mounts. + +The Live Mounts page appears. + + 4. Click MySQL Instance. + +A list of the mounted MySQL Instances appears. + + 5. Hover over the required mount and click Unmount. + +A confirmation dialog box appears. + + 6. Click Unmount. + +## Results + +You have successfully unmounted the MySQL database restore mount point and removed the metadata associated with the selected MySQL database. + *[ > ]: and then diff --git a/nas_adding_nas_system.md b/nas_adding_nas_system.md new file mode 100644 index 0000000000000000000000000000000000000000..17482508d536b868a8ebe8e5644edb8f859aa1c0 --- /dev/null +++ b/nas_adding_nas_system.md @@ -0,0 +1,50 @@ +# Adding a NAS system + +Source: https://docs.rubrik.com/en-us/saas/nas/adding_nas_system.html + +--- + +# Adding a NAS system + +To enhance data management and protection in a NAS share, add a system type to the NAS system. + +## About this task + +Rubrik recommends that you add and manage a NAS System type only in RSC. Managing a NAS system type in both CDM and RSC results in two full backups, which increases the overhead on the cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the NAS Systems inventory card. + +The NAS Systems page appears. + + 5. Click Manage NAS Systems. + 6. Click Add NAS System. + 7. In Rubrik Cluster, select the Rubrik cluster that is managing a NAS system. + 8. Select a system type. + * NetApp Cluster Mode + * Dell EMC Isilon + * Generic NAS + * Nutanix File Server + * Pure System + 9. Enter the IP address or hostname of the NAS cluster management interface. + 10. Enter the administrator username and password. + 11. **Optional:** Select Provide SMB credentials Manually. + +When you select this option, Rubrik creates an SMB user for backup and restore. + + 12. Click Add. + +## Results + +RSC adds the selected system type to the NAS system. + *[ > ]: and then diff --git a/nas_nas_manage_protection.md b/nas_nas_manage_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..1cdbf2990d9293f582ce7a7e9baa6d7fddd0f806 --- /dev/null +++ b/nas_nas_manage_protection.md @@ -0,0 +1,17 @@ +# Manage protection for NAS systems + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_manage_protection.html + +--- + +# Manage protection for NAS systems + +You can manage protection for NAS shares and directories by assigning them an SLA Domain. + +In RSC, you can assign two types of protection for NAS systems: + + * Share protection: Protects the entire NAS share, including all files and directories. You can use Share Rules to protect a subset of the share by specifying Include, Exclude, and Do Not Exclude directory paths instead of the entire share. + * Directory protection: Protects a subset of the share by specifying Include, Exclude, and Do Not Exclude directory paths. Directory protection is useful for protecting specific files on the share. + +You can protect a NAS share using either or both methods, and with different SLA Domains. + *[ > ]: and then diff --git a/nas_nas_manage_protection_netapp_snapmirror.md b/nas_nas_manage_protection_netapp_snapmirror.md new file mode 100644 index 0000000000000000000000000000000000000000..aa2dbb97d365d39ea4ec35c06c66003e0c3eb0d0 --- /dev/null +++ b/nas_nas_manage_protection_netapp_snapmirror.md @@ -0,0 +1,14 @@ +# Manage protection for NetApp SnapMirror NAS volumes + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_manage_protection_netapp_snapmirror.html + +--- + +# Manage protection for NetApp SnapMirror NAS volumes + +RSC backs up the latest snapshot of read-only NetApp SnapMirror volumes, allowing the flexibility to specify a particular snapshot. + +RSC provides protection for read-only NetApp SnapMirror volumes. By default, RSC backs up the latest available snapshot on the SnapMirror volume. You can optionally provide a SnapMirror snapshot label to specify the snapshot to back up. + +Because NetApp SnapMirror volumes are read-only, these volumes cannot be the target of RSC restore operations. RSC does not display information about the SnapMirror relationship between the NetApp source and NetApp target. Additionally, RSC does not control or manage the SnapMirror relationship between the NetApp source and NetApp target. For example, RSC does not control the snapshot replication, replication frequency, or retention period from the NetApp SnapMirror source to the target. + *[ > ]: and then diff --git a/nas_nas_management.md b/nas_nas_management.md new file mode 100644 index 0000000000000000000000000000000000000000..43c3291b21dfc00d77f64131179b8359acf646c8 --- /dev/null +++ b/nas_nas_management.md @@ -0,0 +1,20 @@ +# NAS management + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_management.html + +--- + +# NAS management + +You can register, refresh, and delete NAS shares from the NAS systems page in Rubrik Security Cloud. + +For protection and recovery of NAS cluster data, Rubrik recommends you to first register the NAS cluster through Rubrik Security Cloud (RSC) and Rubrik CDM. + +When you add a NAS share, an automatic NAS share discovery job adds all available NAS shares to the Rubrik cluster. After discovering the NAS share, you can manage NAS shares through RSC. RSC manages protection, SLA Domains, on-demand snapshots, and recovery of NAS shares. + +If you are migrating NAS from a Rubrik cluster to RSC, Rubrik recommends that you do not assign an SLA Domain to the discovered NAS shares after adding the NAS system to RSC. This will result in, a full backup, which will increase the storage overhead on the Rubrik cluster. + +The migration wizard provides the mechanism to migrate NAS from the Rubrik cluster to RSC. The migration wizard is available by accessing the CDM NAS Hosts under the NAS Inventory in the Rubrik CDM web UI. + +When you no longer need to protect a NAS share, you can hide the NAS share through RSC. When you no longer need to protect the NAS system managing the NAS share, you can delete the NAS system from RSC. + *[ > ]: and then diff --git a/nas_nas_ods.md b/nas_nas_ods.md new file mode 100644 index 0000000000000000000000000000000000000000..86f3d090c60538c49ba24366d29875a3fdaf17f8 --- /dev/null +++ b/nas_nas_ods.md @@ -0,0 +1,14 @@ +# On-demand snapshots of NAS shares and directories + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_ods.html + +--- + +# On-demand snapshots of NAS shares and directories + +In addition to policy-based snapshots, you can use the on-demand snapshot process to take snapshots of protected NAS shares and directories. + +According to the rules of the associated SLA Domain, the Rubrik cluster automatically creates policy-based snapshots of protected NAS shares and directories. You can create additional snapshots of protected NAS shares and snapshots of unprotected NAS shares by using the on-demand snapshot process. + +You can take an on-demand snapshot at the NAS share or directory level. You can view the number of on-demand snapshots for the object on the snapshots card on the NAS share details page. + *[ > ]: and then diff --git a/nas_nas_recovery_of_nas_shares.md b/nas_nas_recovery_of_nas_shares.md new file mode 100644 index 0000000000000000000000000000000000000000..027c65d2ae30711e92dbf11552a76161fff9ff4b --- /dev/null +++ b/nas_nas_recovery_of_nas_shares.md @@ -0,0 +1,18 @@ +# NAS shares recovery options + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_recovery_of_nas_shares.html + +--- + +# NAS shares recovery options + +Rubrik Security Cloud supports recovery from backups of NAS shares. + +You have the following options to recover NAS shares on Rubrik Security Cloud: + + * Download, where a link is created to download the selected file or folder + * Overwrite original, where existing files are replaced with the selected ones + * Recover to separate folder, which provides File Level Restore (FLR) for files and folders from any local snapshot + * Export to NAS share, which recovers files or folders to a different NAS share as selected + + *[ > ]: and then diff --git a/nas_nas_share_recovery_export.md b/nas_nas_share_recovery_export.md new file mode 100644 index 0000000000000000000000000000000000000000..cc9f189d0ed99e7b28a52249700cd0ac6e606a41 --- /dev/null +++ b/nas_nas_share_recovery_export.md @@ -0,0 +1,56 @@ +# Exporting NAS shares + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_share_recovery_export.html + +--- + +# Exporting NAS shares + +You can recover selected NAS shares by exporting them. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the NAS Systems inventory card. + +The NAS Systems page appears. + + 5. Click the name of a NAS system. + +The list of NAS shares appears. + + 6. Select the name of the NAS share to protect. + +The NAS share details page appears. + + 7. In the Snapshot card, click Recover on the snapshot to recover. + +The NAS Share Recovery wizard appears. + + 8. Select the folders or files to recover. + +Multiple files or folders can be selected for recovery. + + 9. Click Next. + 10. Select Export to NAS Share as the recovery option. + 11. Click Next. + +The Export to share screen appears. + + 12. Enter an export path for the share to be recovered. + 13. **Optional:** Select Ignore export errors. + 14. Click Recover. + +The files or folders are recovered and a log is recorded in the Events tab. + + 15. Click Done after recovering the files or folders. + + *[ > ]: and then diff --git a/nas_nas_smb_local_user_mgmt.md b/nas_nas_smb_local_user_mgmt.md new file mode 100644 index 0000000000000000000000000000000000000000..9eba4ab671cd84bbc1ed0c1eb8c0ca218d737e3e --- /dev/null +++ b/nas_nas_smb_local_user_mgmt.md @@ -0,0 +1,38 @@ +# SMB local user management of NAS components + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_smb_local_user_mgmt.html + +--- + +# SMB local user management of NAS components + +SMB local user management of NAS components is crucial for mounting, protecting, and managing SMB backup effectively, and for restore operations. + +## RSC requirements for SMB local users + +RSC requires having a local SMB user on each NAS system and namespace to facilitate the mounting, protection, and management of SMB backups and restores. NetApp systems refer to this user as a local user, while Isilon systems refer to this user as an SMB user. + +## SMB account credential generation + +The method of generating SMB account credentials depends on the read-only properties of the host. + +For NAS systems and namespaces that are not read-only, RSC, by default, automatically creates a local SMB user on both the NAS system and the namespace. You can also create the local SMB user manually. + +If the host has read-only properties, such as for NetApp read-only storage virtual machines and Isilon read-only zones, RSC cannot create local SMB users. In such cases, it is necessary to provide the SMB credentials manually. + +## Backup and restore privileges + +Each local SMB user, whether automatically generated or manually provided, requires backup and restore privileges. You can configure these privileges on the NAS system. + +## SMB credentials for read-only namespaces + +For read-only namespaces, where RSC cannot automatically create users, the local SMB user must be provided manually and must have backup and restore privileges. You have the flexibility to provide these credentials at various levels: + + * System level: Adding credentials manually at the system level protects all namespaces and SMB shares on that system. + * Namespace level: Adding credentials manually at the namespace level protects all SMB shares under that specific namespace. + * NAS SMB share level: Provides credentials directly to the individual NAS SMB share. + +## Post-credential configuration + +After the SMB credentials have been provided or updated at the NAS system, namespace, or share level, you can configure protection policies, including SLA Domain assignment, for your NAS components. + *[ > ]: and then diff --git a/nas_nas_systems.md b/nas_nas_systems.md new file mode 100644 index 0000000000000000000000000000000000000000..29cb6d3ad2259891c8895de28ff068d03b11bb12 --- /dev/null +++ b/nas_nas_systems.md @@ -0,0 +1,27 @@ +# NAS systems + +Source: https://docs.rubrik.com/en-us/saas/nas/nas_systems.html + +--- + +# NAS systems + +RSC manages and protects NFS and SMB shares on NAS systems for efficient data storage and retrieval. + +RSC data protection for enterprise NAS environments provides benefits, such as the following: + + * Reliable backups + * Rapid recovery of data + * Flexible data management + +You can add a NetApp system, Dell EMC Isilon, Nutanix File Server, generic NAS system, or Pure System to RSC for protection. You can simplify the file backup process by using specific API integrations with NetApp SnapDiff and Dell EMC Isilon Changelist. + +When you add a NAS system, the auto-discovery feature of managing NAS systems in RSC offers the following benefits: + + * Does hourly discovery of namespaces, volumes, and shares in NAS systems + * Performs MetroCluster auto discovery for systems that have this feature enabled + * Facilitates protection of newly discovered shares by adding them to SLA Domains at either the NAS system or directory level + * Pauses protection for shares deleted from the source NAS system + * Provides options in RSC for downloading and exporting recovery data for paused shares + +The share-level and directory-level protections are available for NAS systems in RSC. You can protect a NAS share by using either mechanism or both mechanisms, and by using them with different SLA Domains. diff --git a/nas_rsc_nas_service_account.md b/nas_rsc_nas_service_account.md new file mode 100644 index 0000000000000000000000000000000000000000..aed75ca4e652c15ae2a08750c0c1d4ca293ad08d --- /dev/null +++ b/nas_rsc_nas_service_account.md @@ -0,0 +1,16 @@ +# RSC service account for NAS systems + +Source: https://docs.rubrik.com/en-us/saas/nas/rsc_nas_service_account.html + +--- + +# RSC service account for NAS systems + +RSC creates a Rubrik service account and an associated role with the necessary privileges on the NAS system and uses the service account for backup, restore, and auto-discovery of NAS systems. + +When you add a NetApp NAS system to RSC, RSC creates a Rubrik service account and an associated role at the Netapp cluster level to perform API operations during backup, restore, and auto-discovery for NAS systems and the NetApp SnapMirror Cloud service. RSC creates a role with the necessary privileges and assigns it to the Rubrik service account user. RSC also creates a local user on each storage virtual machine within the NetApp cluster to manage SMB backups and restores. + +When the NetApp NAS hosts are running ONTAP version 9.8 or later, RSC creates a role with REST API privileges and assigns a user to that role. When the ONTAP version is earlier than version 9.8, RSC creates a role with ZAPI privileges. + +When you add an Isilon NAS system, RSC creates a Rubrik service account and an associated role with the necessary privileges.RSC also creates a user and adds the role with the necessary privileges to the user. RSC uses this service account to issue API calls during backup, restore, and auto-discovery. This RSC user is created within the system zone. RSC also creates a user in each zone, including all the non-system zones, in the Isilon system for SMB backup and restore. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_addition_nx_cluster_to_rsc.md b/nutanix_ahv_ahv_addition_nx_cluster_to_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..31e576cbb16ff6dd6c8805a3c2c2b36914116cd6 --- /dev/null +++ b/nutanix_ahv_ahv_addition_nx_cluster_to_rsc.md @@ -0,0 +1,19 @@ +# Addition of Nutanix clusters to RSC + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_addition_nx_cluster_to_rsc.html + +--- + +# Addition of Nutanix clusters to RSC + +By adding Nutanix clusters, Nutanix Cloud Clusters (NC2), or Nutanix Prism Central to RSC, you can protect the AHV virtual machines deployed on Nutanix clusters or NC2. + +To protect the AHV virtual machines deployed on Nutanix clusters or Nutanix Cloud Clusters (NC2), you can add Nutanix clusters to RSC in the following ways: + + * Adding individual Nutanix clusters or NC2 + * Adding Nutanix Prism Central that manages Nutanix clusters or NC2 + +This option is available only with Rubrik clusters that are running Rubrik CDM version 9.0 or later. + +The Nutanix clusters or NC2 that you add appears on the Nutanix Virtual Machines inventory page in RSC, and you can start protecting your AHV virtual machines. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_dr_support_prism_central.md b/nutanix_ahv_ahv_dr_support_prism_central.md new file mode 100644 index 0000000000000000000000000000000000000000..4263d56363381e0678bfae8a25257e3c6d949e56 --- /dev/null +++ b/nutanix_ahv_ahv_dr_support_prism_central.md @@ -0,0 +1,23 @@ +# Disaster Recovery support for Nutanix Prism Central + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_dr_support_prism_central.html + +--- + +# Disaster Recovery support for Nutanix Prism Central + +Disaster Recovery for Nutanix Prism Central ensures uninterrupted protection of the AHV virtual machines during a planned failover. + +Nutanix Prism Central supports disaster recovery by replicating and backing up virtual machines to a secondary site during a disaster, such as hardware failures, network issues, natural disasters, or cyberattacks. RSC enhances the disaster recovery capability of Nutanix Prism Central by providing uninterrupted data protection when the virtual machines migrate between sites. You can enable the disaster recovery in RSC while adding a Nutanix Prism Central or modify an existing Nutanix Prism Central to enable this functionality. + +During a planned failover, when the AHV virtual machines migrate from one site to another site, RSC creates a link between the old virtual machine and the new virtual machine to preserve the snapshots, SLA Domains, and other configurations. This eliminates the need of taking a full backup of the virtual machine even after migration. You can take incremental backup of the snapshots in the new virtual machine and optimize the storage resources. + +To utilize the disaster recovery feature in RSC, you need to perform the following tasks: + + * Mapping the Nutanix cluster in the secondary site to a CDM cluster. You can either use a single CDM cluster to protect all your Nutanix clusters or use a different CDM cluster for each Nutanix cluster within a Prism Central. If you are using a single CDM cluster, RSC preserves all the properties of the virtual machine, such as snapshot properties, Exclude Disk properties, and SLA Domains. If you are using a different CDM cluster for each Nutanix cluster, RSC preserves only the snapshot properties and Exclude Disk properties. RSC cannot preserve the SLA Domain information. + * Creating an SLA Domain to enable replication between the CDM clusters, if you have used different CDM clusters. For example, if you have CDM cluster A associated with the primary Nutanix cluster, and CDM cluster B associated with the secondary Nutanix cluster, you need to create an SLA Domain to enable replication between CDM clusters A and B. This allows migration of virtual machines during a planned failover. + +Note: + +In the event of an unplanned failover, the virtual machine IDs assigned by RSC change and RSC considers the migrated virtual machines as new objects. As a result, RSC doesn't support disaster recovery in the event of an unplanned failover. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_excluding_vm_disks.md b/nutanix_ahv_ahv_excluding_vm_disks.md new file mode 100644 index 0000000000000000000000000000000000000000..a46011cefdb06b7acac5b1b7c343f37f3a580376 --- /dev/null +++ b/nutanix_ahv_ahv_excluding_vm_disks.md @@ -0,0 +1,44 @@ +# Excluding AHV virtual machine disk files + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_excluding_vm_disks.html + +--- + +# Excluding AHV virtual machine disk files + +Exclude specific managed disks while protecting other managed disks attached to a virtual machine instance. + +## About this task + +All virtual machine disk files do not need protection, and hence they can be excluded. The Rubrik cluster can ignore some of the virtual machine disk (VMDK) files of a virtual machine while protecting the other VMDK files of that virtual machine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the AHV VMs inventory card. + +The Nutanix Virtual Machines page appears. + + 5. Click the name of a virtual machine on the Virtual Machines tab. + 6. Open the ellipsis menu and select Exclude Disks. + +The Exclude Disks From Snapshots dialog box appears. + + 7. Select the disks to exclude. + +For the subsequent tasks of excluding virtual machine disk files, the excluded disks are selected by default. + + 8. Click Exclude. + +## Results + +RSC excludes the selected VMDK files from all future backups of the virtual machine. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_local_host_page.md b/nutanix_ahv_ahv_local_host_page.md new file mode 100644 index 0000000000000000000000000000000000000000..bddbe3944089b08d4155a60381ad9dfda8280777 --- /dev/null +++ b/nutanix_ahv_ahv_local_host_page.md @@ -0,0 +1,17 @@ +# Local host page for AHV virtual machine + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_local_host_page.html + +--- + +# Local host page for AHV virtual machine + +The local host page provides detailed information about the virtual machine, protection of the virtual machine, available snapshots, and tasks related to the virtual machine and snapshots. + +The local host page provides the following tabs: + + * Overview + * Events + * Snapshots + + *[ > ]: and then diff --git a/nutanix_ahv_ahv_nc2_on_aws_and_azure.md b/nutanix_ahv_ahv_nc2_on_aws_and_azure.md new file mode 100644 index 0000000000000000000000000000000000000000..29961b94a41a3d0699e2dca0bd64d38631a68360 --- /dev/null +++ b/nutanix_ahv_ahv_nc2_on_aws_and_azure.md @@ -0,0 +1,24 @@ +# Nutanix Cloud Clusters on AWS and Azure + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_nc2_on_aws_and_azure.html + +--- + +# Nutanix Cloud Clusters on AWS and Azure + +Nutanix NC2 provides a platform for running applications in public clouds and for extending your on-premises Nutanix infrastructure in AWS and Azure. With RSC, you can protect Nutanix NC2 workloads on AWS and Azure. + +Nutanix Cloud Clusters (NC2) extends the use of Nutanix Hyperconverged Infrastructure (HCI) software and the Nutanix stack to AWS and Azure. Nutanix NC2 on AWS runs on the bare metal EC2 instance and can leverage all AWS services. Nutanix NC2 on Azure runs on the bare metal as a service (BMaaS) to deploy and install Nutanix NC2 software on bare-metal nodes and access all the Azure services. + +You can add NC2 on AWS and Azure to RSC and utilize RSC capabilities to manage and protect the NC2 workloads. + +In RSC, you can set up your NC2 on AWS and Azure workloads by using the following workflow: + + * Reviewing and fulfilling the Nutanix prerequisites + * Adding the NC2 on AWS and Azure to RSC + * Reviewing the workloads on the AHV VMs Inventory page + * Assigning an SLA Domain to your NC2 + * Recovering NC2 snapshots using the Live Mount and Export options + +The process of adding and recovering Nutanix clusters or Nutanix cloud clusters (NC2) in RSC is the same for both on-premises Nutanix clusters or NC2 on AWS and Azure. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_ods.md b/nutanix_ahv_ahv_ods.md new file mode 100644 index 0000000000000000000000000000000000000000..fe4f322640917f8b8eb9f6c2b1f12631cd207bff --- /dev/null +++ b/nutanix_ahv_ahv_ods.md @@ -0,0 +1,12 @@ +# On-demand snapshots of AHV virtual machines + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_ods.html + +--- + +# On-demand snapshots of AHV virtual machines + +In addition to policy-based snapshots, you can create AHV virtual machine snapshots by using the on-demand snapshot process. + +The SLA rules of the associated SLA Domain specifies that a Rubrik cluster can create policy-based snapshots of protected virtual machines automatically. You can create additional snapshots of protected virtual machines and snapshots of unprotected virtual machines by using the on-demand snapshot process. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_rbs_installation.md b/nutanix_ahv_ahv_rbs_installation.md new file mode 100644 index 0000000000000000000000000000000000000000..0aea3565e66c5e564cf52a960a3befe41c2f8926 --- /dev/null +++ b/nutanix_ahv_ahv_rbs_installation.md @@ -0,0 +1,18 @@ +# Rubrik Backup Service installation for AHV + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_rbs_installation.html + +--- + +# Rubrik Backup Service installation for AHV + +The Rubrik Backup Service is a software installed on a host that coordinates activity between the Rubrik cluster and the host. + +Configuring the Rubrik Backup Service (RBS) includes: + + * Downloading the RBS package + * Installing the RBS on the Nutanix virtual machine + * Registering the virtual machine running the RBS + +Downloading the RBS software, Obtaining the RBS software by URL, Installing RBS on Linux and Unix hosts, Installing RBS on Windows, and RBS firewall rules in the CDM User Guide provides more information about configuring RBS. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_snapshot_consistency.md b/nutanix_ahv_ahv_snapshot_consistency.md new file mode 100644 index 0000000000000000000000000000000000000000..27d6e9dfb9ad1c7e3bc17f6025f31943bfec9411 --- /dev/null +++ b/nutanix_ahv_ahv_snapshot_consistency.md @@ -0,0 +1,30 @@ +# AHV snapshot consistency + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_snapshot_consistency.html + +--- + +# AHV snapshot consistency + +With the AHV snapshot consistency feature, you can select the type of snapshot you want RSCto take. Depending on your specific requirements, RSCcan take either application-consistent snapshots or crash-consistent snapshots. + +Using the AHV snapshot consistency feature, you can select the type of snapshot that you want RSC to take for your AHV virtual machines. + +The available snapshot types that you can select are as follows: + + * Application-consistent or automatic snapshot: A snapshot of an AHV virtual machine is considered application consistent if, in addition to capturing all of the data at the instant of the crash, the running applications have completed all their operations and flushed their buffers to the disk attached to the AHV virtual machine. Rubrik recommends using application-consistent snapshots for database operating systems and applications such as SQL, Oracle, and Microsoft Exchange. + +By default, RSC takes application-consistent snapshots for your AHV virtual machines. + + * Crash-consistent snapshot: A crash-consistent snapshot captures only the data already written to the disks attached to the AHV virtual machine. Any data that is still in memory or pending I/O operations will not be captured in the snapshot. Rubrik suggests using the crash-consistent snapshot for non-database operating systems and applications such as file servers, DHCP servers, or print servers. + +You can configure the AHV snapshot consistency for the following: + + * Nutanix cluster: When you configure an application-consistent or a crash-consistent snapshot for a Nutanix cluster, RSC takes the configured snapshot for all the AHV virtual machines running on the Nutanix cluster. + +Configuring the AHV snapshot consistency for a Nutanix cluster is only available for a Rubrik cluster running Rubrik CDM version 9.1 or later. + + * AHV virtual machine: When you configure an application-consistent or a crash-consistent snapshot for an AHV virtual machine, RSC takes the configured snapshot for that AHV virtual machine. Regardless of the snapshot type configured at the Nutanix cluster level, the snapshot type you configure at the AHV virtual machine level always takes precedence. + +You can configure the AHV snapshot consistency feature while adding a Nutanix cluster to RSC or from the Nutanix Virtual Machines inventory page. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_virtual_machine_protection.md b/nutanix_ahv_ahv_virtual_machine_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..4afb0f8736fb20d2513cfedc24b68a9e8535eb88 --- /dev/null +++ b/nutanix_ahv_ahv_virtual_machine_protection.md @@ -0,0 +1,18 @@ +# AHV virtual machine protection + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_virtual_machine_protection.html + +--- + +# AHV virtual machine protection + +SLA Domains can be used to apply the data protection policies to an individual virtual machine or a selected set of virtual machines. + +A virtual machine can be protected by assigning an SLA Domain setting individually to the virtual machine. A virtual machine can also be protected by deriving an SLA Domain setting through automatic protection. + +Automatic protection occurs in one of the following ways: + + * An administrator assigns an object that contains the virtual machine to an SLA Domain. + * An administrator moves the virtual machine into the hierarchy of an object that is assigned to an SLA Domain. + + *[ > ]: and then diff --git a/nutanix_ahv_ahv_virtual_machines.md b/nutanix_ahv_ahv_virtual_machines.md new file mode 100644 index 0000000000000000000000000000000000000000..d6123f9d072762177d9f4cf5ccf20585b4d41b3f --- /dev/null +++ b/nutanix_ahv_ahv_virtual_machines.md @@ -0,0 +1,11 @@ +# AHV virtual machines + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_virtual_machines.html + +--- + +# AHV virtual machines + +RSC provides data management and protection for virtual machines deployed in a Nutanix Acropolis environment. + +RSC manages the protection and recovery of Nutanix Acropolis (AHV) virtual machines managed by multiple Rubrik clusters. diff --git a/nutanix_ahv_ahv_vm_protection.md b/nutanix_ahv_ahv_vm_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..9ae9971391eeaa3b5bfdee41121969f85ef185f6 --- /dev/null +++ b/nutanix_ahv_ahv_vm_protection.md @@ -0,0 +1,12 @@ +# AHV virtual machine protection + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_vm_protection.html + +--- + +# AHV virtual machine protection + +RSC provides protection for AHV virtual machines either by individually assigning the virtual machine to an SLA Domain or through automatic protection. + +RSC provides flexibility in the protection assignments made for virtual machines. Virtual machines can be either protected automatically or by individual assignment. Virtual machines that are protected by individual assignment can either derive a protection setting from a higher-level object or they can be set to Don't protect mode. + *[ > ]: and then diff --git a/nutanix_ahv_ahv_vm_recovery.md b/nutanix_ahv_ahv_vm_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..b138e3428e864e4b7895037948910a8a620d6328 --- /dev/null +++ b/nutanix_ahv_ahv_vm_recovery.md @@ -0,0 +1,25 @@ +# Recovery of AHV virtual machines + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/ahv_vm_recovery.html + +--- + +# Recovery of AHV virtual machines + +You can recover an AHV virtual machine or specific disks within a virtual machine from snapshots that are locally available on a Rubrik cluster. + +Locally available snapshots are snapshots that are downloaded from archival locations or from replication targets to a Rubrik cluster. You can recover an AHV virtual machine or specific disks within a virtual machine from these snapshots. + +You cannot recover an AHV virtual machine from snapshots that are available only at remote archival locations or replication targets, or from local snapshots that have expired. + +For recovery of AHV virtual machines, Rubrik clusters provide the following options: + + * Recover files: Restores the files and folders from a snapshot. + * Live mount: Creates and mounts a new virtual machine on a Nutanix cluster using a snapshot. + * Export: Creates a virtual machine from a point-in-time copy of the source virtual machine. + * Mount virtual disks: Attaches specific virtual disks to a virtual machine. The recovered virtual disks use the Rubrik cluster as their data source. + * Download virtual disks: Downloads specific virtual disks without downloading the entire virtual machine. + * In-place recovery: Recovers the data by transferring only the changed blocks of virtual disk data directly from the Rubrik cluster data store to the Nutanix cluster. + * Instant recovery: Restores a virtual machine from a snapshot and replaces the original virtual machine with a functional point-in-time copy of the virtual machine hosted on the Rubrik cluster. The Rubrik cluster powers on the recovered virtual machine and connects it to the source network. + + *[ > ]: and then diff --git a/nutanix_ahv_performing_ahv_vm_instant_recovery.md b/nutanix_ahv_performing_ahv_vm_instant_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..1eddb0bfb866f635cc7513fe56e9298020ab5b9a --- /dev/null +++ b/nutanix_ahv_performing_ahv_vm_instant_recovery.md @@ -0,0 +1,71 @@ +# Performing AHV virtual machine instant recovery + +Source: https://docs.rubrik.com/en-us/saas/nutanix_ahv/performing_ahv_vm_instant_recovery.html + +--- + +# Performing AHV virtual machine instant recovery + +Perform an instant recovery of an AHV virtual machine to replace the source virtual machine with a fully functional point-in-time copy of the source virtual machine. + +## Before you begin + +Ensure that the AHV virtual machine is on a Rubrik cluster that is running Rubrik CDM version 9.3.1 or later. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the AHV VMs inventory card. + +The Nutanix Virtual Machines page appears. + + 5. Click the name of a virtual machine for which you want to perform the instant recovery. + +The Details page for the selected virtual machine appears. + + 6. Click a date on the calendar to view the list of snapshots taken on that day. + 7. Hover over a snapshot and click Recover. + +The Virtual Machine Recovery wizard appears. + + 8. Select Instant Recovery and click Next. + +The Select network page appears. + + 9. In NIC Index 0, select a network to live mount the recovered virtual machine. + +You can select either the original network associated with the source virtual machine or a different network for the recovered virtual machine connection. + + 10. **Optional:** In Advanced settings, select an option. + +Option| Description +---|--- +Remove all network devices | Removes all networks and associated network devices from the recovered virtual machine. Select this if you do not want the recovered virtual machine to be associated with any network.Note: When you select this option, RSC removes any network that you have selected to live mount the recovered virtual machine. +Assign the MAC address from the snapshot to the recovered VM | Recovers the MAC address from the selected snapshot associated with the virtual machine you want to recover.Note: If this MAC address is already assigned to a different virtual machine, RSC assigns a new MAC address to the recovered virtual machine. + + 11. Click Next. + 12. Select a container to mount the recovered virtual machine. + 13. **Optional:** Select Migrate immediately. + +If you select this option, the recovered virtual machine migrates from the Rubrik cluster to the selected container as soon as the instant recovery finishes. + + 14. **Optional:** Select Recover the categories assigned to the VM. + +You can select this option to recover the Nutanix categories associated with the virtual machine being recovered. + + 15. Click Recover. + +## Results + +RSC performs the instant recovery of the virtual machine. + +Rubrik cluster assigns the original name of the source virtual machine to the recovered virtual machine, powers on the recovered virtual machine, and then configures the network based on your selections. + *[ > ]: and then diff --git a/okta_configure_okta_idp.md b/okta_configure_okta_idp.md new file mode 100644 index 0000000000000000000000000000000000000000..f00a5b8b081c074f8e9bb381f55ad90eb0c6d6ee --- /dev/null +++ b/okta_configure_okta_idp.md @@ -0,0 +1,33 @@ +# Configure Okta IdP + +Source: https://docs.rubrik.com/en-us/saas/okta/configure_okta_idp.html + +--- + +# Configure Okta IdP + +Configure your Okta Identity Provider by adding Okta tenants to RSC and perform other maintenance operations, such as editing and removing the Okta tenants. + +To begin backing up your Okta IdP, you must add the Okta tenant to RSC. This process establishes a secure connection between your Okta environment and RSC. + +Before adding the Okta tenant to RSC, you need to: + + * Add and verify the RSC application on the Okta Integration Network (OIN). + * Ensure you have securely saved the following essential credentials obtained during the RSC application setup in Okta, as they are required for tenant registration in RSC: + * Domain URL, which is your Okta tenant URL. For example, `https://[your-company].okta.com` + * Client ID + * Client Secret + +## Maintenance operations + +After you have added the Okta tenant to RSC, you can perform the following maintenance operations: + + * You can change the Domain URL, Client ID, and Client Secret if required, as described in [Editing Okta tenant](editing_okta_tenants.html "Edit an Okta tenant to update the domain URL, client ID, and client secret. You cannot change the backup location."). + +Note: + +You cannot change the backup region after you add the Okta tenant to RSC. + + * You can remove any Okta tenant that is no longer needed, as described in [Removing Okta tenant](removing_okta_tenant.html "Remove an Okta tenant from RSC when that tenant is no longer needed for protection."). + + *[ > ]: and then diff --git a/okta_deleting_okta_snapshots.md b/okta_deleting_okta_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..e397357f0633c503c2a2945e701f6e78c5c39655 --- /dev/null +++ b/okta_deleting_okta_snapshots.md @@ -0,0 +1,47 @@ +# Deleting Okta snapshots + +Source: https://docs.rubrik.com/en-us/saas/okta/deleting_okta_snapshots.html + +--- + +# Deleting Okta snapshots + +Manually delete an Okta snapshot from RSC if that snapshot is no longer required. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Identity Resilience. + +The Identity Resilience dashboard appears. + + 3. On the navigation bar, click Protection > Inventory. + +The Inventory page appears. + + 4. Click the Okta inventory card. + +The Okta page appears with a list of Okta tenants. + + 5. In Status, select one of the following: + +Status| Description +---|--- +Active | To view only the active Okta tenants.This is the default status. These tenants are currently protected and have an assigned SLA Domain. +Relic | To view only the relic Okta tenants.These are tenants that have been removed from RSC but whose snapshots are still retained for a defined period. You can only browse and delete the relic snapshots. + + 6. Click the tenant containing the snapshot you want to delete. + +The Overview page of the tenant appears, displaying the calendar view of the snapshots. + + 7. In the calendar, click the date containing the snapshot you want to delete. + +A list of snapshots from the selected date appears. + + 8. Click for the snapshot you want to delete. + 9. Click Delete Snapshot. + +## Results + +You have successfully deleted the Okta snapshot. + *[ > ]: and then diff --git a/okta_evaluate_okta_configuration_options.md b/okta_evaluate_okta_configuration_options.md new file mode 100644 index 0000000000000000000000000000000000000000..4695838cc8b8d267a732fc00614dc2cd49adb208 --- /dev/null +++ b/okta_evaluate_okta_configuration_options.md @@ -0,0 +1,18 @@ +# Evaluate Okta configuration options + +Source: https://docs.rubrik.com/en-us/saas/okta/evaluate_okta_configuration_options.html + +--- + +# Evaluate Okta configuration options + +You can add Okta tenants to RSC using the Identity Resilience inventory, Data Protection inventory, or Settings menu. + +To add Okta tenants to RSC, you must have the Rubrik Identity Okta Recovery License. + +The following table describes the configuration options for Okta. Configuration Options | Navigation +---|--- +Identity Resilience inventory | You can navigate to and then click Identity Resilience > Protection > Inventory > Add Identity Provider. The Add an Identity Provider wizard appears. You can then select Okta and click Next. The Add an Okta Tenant wizard appears. +Data Protection inventory | You can navigate to and then click Data Protection > Inventory > Identity. After you click the Okta inventory tile, RSC redirects you to the Identity Resilience page for Okta. You can then click Add Okta Tenant. +Settings menu | You can navigate to and then click Settings > Identity Providers > Okta > Add Tenant. + *[ > ]: and then diff --git a/okta_manage_okta_tenants.md b/okta_manage_okta_tenants.md new file mode 100644 index 0000000000000000000000000000000000000000..b05689904a2e958c1bab46b09af909e4e209c738 --- /dev/null +++ b/okta_manage_okta_tenants.md @@ -0,0 +1,34 @@ +# Manage Okta tenants + +Source: https://docs.rubrik.com/en-us/saas/okta/manage_okta_tenants.html + +--- + +# Manage Okta tenants + +Viewing and analyzing detailed information about your protected Okta IdP from the Inventory page enables you to make informed decisions. Key aspects include viewing tenants, checking protection status, reviewing detailed object attributes, browsing the snapshot calendar, viewing events log for audit and compliance, and performing maintenance such as deleting snapshots. + +## Inventory details overview + +After you add an Okta tenant to RSC, you can manage and monitor its protection status through the Inventory details page. + +The following table describes various tabs available on the Okta inventory details page: Tab | Description +---|--- +Overview | + + * Protection: Displays the assigned SLA Domains, the date when RSC started protecting the tenant, and the backup region. + * Object Details: Displays the number of users, groups, applications, policies, and policy rules for the Okta tenant. + * Snapshots calendar: Displays visual snapshot information for the entire year, month, and day. Green dots on specific dates signify that a snapshot was taken on that date, providing a clear visual representation of your backup history. + + +Events | Displays a historical log of all recovery and snapshot events, such as successes and failures. This provides a detailed audit trail essential for audit and compliance processes. + +## Operational tasks + +The following table provides an overview of the key operational tasks and their objectives within the Okta IdP management workflow: Task | Objective | Use case +---|---|--- +Viewing Okta tenants | Viewing a list of all protected tenants. | Verifying onboarding and checking high-level metrics, such as assigned SLA Domain and last backup. +Viewing Okta tenant details | Viewing the comprehensive status of a single tenant. | Checking protection status, reviewing object counts, and monitoring event logs for audit. +Viewing Okta snapshots | Reviewing the backup history. | Confirming successful backups on specific dates and determining potential recovery points. +Deleting Okta Snapshots | Manually removing unwanted snapshots. | Performing maintenance and freeing up storage space. + *[ > ]: and then diff --git a/okta_manage_protection_okta_idp.md b/okta_manage_protection_okta_idp.md new file mode 100644 index 0000000000000000000000000000000000000000..936caa732c7664b5e867d94c5cc99c1e22e66f70 --- /dev/null +++ b/okta_manage_protection_okta_idp.md @@ -0,0 +1,23 @@ +# Manage protection for Okta IdP + +Source: https://docs.rubrik.com/en-us/saas/okta/manage_protection_okta_idp.html + +--- + +# Manage protection for Okta IdP + +You can use SLA Domains to apply data protection and management policies to Okta tenants for optimal protection. + +You can create SLA Domains and assign them to your Okta tenants. This process lets you configure specific protection policies, including the required backup frequencies and retention periods. + +You can also initiate on-demand backups at any time. Taking on-demand backups is useful for immediately capturing a recovery point before a major configuration change or critical migration, minimizing risk. + +## Data security and storage + +Rubrik employs a robust strategy for securing your backed-up Okta data: + + * Geographical separation: Rubrik stores your backup data in a geographically separate cloud location that is managed entirely by Rubrik. This ensures resilience against regional disasters or localized service disruptions. + * Operational simplicity: This managed service abstracts away the operational complexity and capital expenditure traditionally associated with managing the underlying storage infrastructure for backup data. + * Logical air gap: Your backup data is stored in a logical air gap, completely isolated from your production network and your primary Okta tenant. This crucial feature prevents unauthorized access. Even if your primary Okta tenant is compromised, your backups remain secure and recoverable. + + *[ > ]: and then diff --git a/okta_okta_idp.md b/okta_okta_idp.md new file mode 100644 index 0000000000000000000000000000000000000000..a3e792fc62e30c5f238bad7bca98d8a5450dfd9a --- /dev/null +++ b/okta_okta_idp.md @@ -0,0 +1,26 @@ +# Okta IdP + +Source: https://docs.rubrik.com/en-us/saas/okta/okta_idp.html + +--- + +# Okta IdP + +Rubrik Security Cloud provides protection and recovery for Okta Identity Provider objects. By integrating your Okta tenant with Rubrik, you can leverage a comprehensive set of data protection features designed for security, simplicity, and reliability. + +Note: + +Okta Identity Provider (IdP) protection requires you to purchase the Rubrik Identity Okta Recovery license. + +Okta is a cloud-based Identity and Access Management (IAM) platform that serves as a central authority for managing and securing user access to various applications and resources. + +Key functionalities of Okta include: + + * Single Sign-On (SSO): Enables users to log in through one authentication event using a single set of credentials to access multiple applications. + * Universal directory: Centralizes and organizes user identities within a cloud-based user store. + * Multi-Factor Authentication (MFA): Requires multiple verification factors to enhance security for gaining access. + * Lifecycle management: Automates user provisioning and deprovisioning to streamline the onboarding and offboarding processes. + +Okta operates on a shared responsibility model, which means while Okta ensures platform resilience, the user is responsible for the data and configurations within their tenant. Okta does not offer a native, robust solution for full tenant backup and restore. This creates a significant gap in the security and business continuity strategy of an organization, leaving it vulnerable to data loss from human error, misconfigurations, or malicious attacks. + +Rubrik offers Okta integration to fill this gap by providing an automated, secure, and intelligent solution for Okta IdP. The core focus of this solution is reliable, non-disruptive recovery from human error and misconfiguration, which is the most frequent and impactful challenge for an organization. This solution leverages a pre-built application in the Okta Integration Network (OIN) to ensure a seamless, secure, and user-friendly integration experience. diff --git a/okta_okta_key_features_protection.md b/okta_okta_key_features_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..e8836ef2a39b3e4b90e9da1c1f1102ff7c74d3ed --- /dev/null +++ b/okta_okta_key_features_protection.md @@ -0,0 +1,40 @@ +# Key features for protecting Okta IdP + +Source: https://docs.rubrik.com/en-us/saas/okta/okta_key_features_protection.html + +--- + +# Key features for protecting Okta IdP + +RSC provides unified identity management, identity protection, and recovery for critical Okta IdP objects. + +The Okta integration with RSC provides comprehensive features to protect your data for security, simplicity, and reliability. The solution is built on a foundation of native security, a unified platform, and intelligent recovery. + +The important features for protecting Okta IdP include: + + * Data protection and storage + * Security and operational efficiency + +## Data protection and storage + +Feature | Description +---|--- +Automated and on-demand backup | Continuous data protection for critical Okta objects, with the flexibility for administrators to take a snapshot before a major change. This feature minimizes the risk from major configuration changes by providing an immediate, reliable restore point. +Natively secure storage | Backups are inherently protected against cyberattacks. + + * Immutable: The backups are secure and cannot be altered or deleted. + * Off-site storage: All backup data is stored in a Rubrik-owned, geographically separate cloud location. + * Air-gapped: The storage is logically isolated from the production network of a user, preventing unauthorized access even if the primary tenant is compromised. + + +In-place granular recovery | The ability to restore misconfigured, corrupted, or deleted objects back to their original location in the live Okta tenant.This feature minimizes disruption, data loss, and manual effort compared to a full tenant restore. + +## Security and operational efficiency + +Feature | Description +---|--- +Unified platform | Provides a single unified platform for protecting critical identity data across multiple IdPs, including Okta, Active Directory (AD), and Entra ID. +Intelligent, dependency-aware recovery engine | Understands the complex relationships between objects such as users, groups, and applications to automatically restore them in the correct, logical order.Prevents restore failures and incomplete recoveries caused by broken object links and interdependencies. +Conflict resolution | Identifies discrepancies between the backup and the live tenant, offering administrators a choice to merge or overwrite the current values during a restore.This feature prevents unintended data loss from overwriting valid, recent changes in the live Okta tenant. +Restore preview | Provides administrators with a user interface that clearly shows the exact outcome of a restore before execution, including a detailed view of the objects RSC will overwrite, recreate, or leave untouched.This feature gives an administrator full control and minimizes the risk of new, unintended data loss. + *[ > ]: and then diff --git a/okta_okta_supported_objects.md b/okta_okta_supported_objects.md new file mode 100644 index 0000000000000000000000000000000000000000..97e3f0be48d12a4c7bded5b2b2e4eb73600acddb --- /dev/null +++ b/okta_okta_supported_objects.md @@ -0,0 +1,21 @@ +# Supported Okta objects + +Source: https://docs.rubrik.com/en-us/saas/okta/okta_supported_objects.html + +--- + +# Supported Okta objects + +Information about the critical Okta objects supported by Rubrik for backup and granular recovery, including those related to user access, security, and application functionality. + +The Rubrik Okta IdP protection and recovery address the most frequent and impactful pain points of a user: the need for a reliable, non-disruptive recovery from human error and misconfiguration. Through this Okta IdP integration, Rubrik establishes the essential capability to solve this core problem. + +Rubrik supports the backup and granular recovery of the following critical Okta objects, which are essential for maintaining user access, security, and application functionality: + + * User + * Group + * Application + * Policy + * Policy Rules + + *[ > ]: and then diff --git a/okta_plan_okta_idp_protection.md b/okta_plan_okta_idp_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..f455e4145afa69229685f76cb9ed61114da96052 --- /dev/null +++ b/okta_plan_okta_idp_protection.md @@ -0,0 +1,22 @@ +# Plan your Okta IdP protection + +Source: https://docs.rubrik.com/en-us/saas/okta/plan_okta_idp_protection.html + +--- + +# Plan your Okta IdP protection + +Before integrating Okta IdP with RSC, you must meet certain requirements to start protecting your critical Okta objects. + +When planning Okta IdP protection with RSC, you must meet the following requirements: + + * Rubrik Identity Okta Recovery license: You must purchase the Rubrik Identity Okta Recovery license to start protecting your data in the Okta tenant. + * Okta tenant access: You must have an active Okta Workforce Identity tenant. + * Okta administrator privileges: You must have an Okta account with Super Administrator privileges or a custom administrator role with permissions to: + * Browse and add applications from Okta Integration Network (OIN). + * View and configure settings of an application you added. + * Access and copy the Client ID and Client Secret for an API service application. + * RSC access: You must have access to RSC account with an administrative role that has permissions to add and manage data sources. + +After you fulfill the planning requirements, the final planning step is to add the RSC application in Okta, as described in [Adding RSC application in Okta](adding_rsc_app_oin.html "Add the RSC application within your Okta Admin Console and generate secure credentials required for the Okta integration with RSC."). + *[ > ]: and then diff --git a/okta_recover_okta_objects.md b/okta_recover_okta_objects.md new file mode 100644 index 0000000000000000000000000000000000000000..06e7d2c1924c867ab0109d02df81cc7f2fdaf1f6 --- /dev/null +++ b/okta_recover_okta_objects.md @@ -0,0 +1,21 @@ +# Recover Okta objects + +Source: https://docs.rubrik.com/en-us/saas/okta/recover_okta_objects.html + +--- + +# Recover Okta objects + +RSC provides protection for critical Okta objects. You can assign an SLA Domain to your Okta tenant to begin the automated backups. You can recover the required Okta objects using the automated backups or on-demand snapshots. + +After you add your Okta tenant to RSC and assign an SLA Domain, RSC automatically starts protecting your data by taking snapshots based on the policies you configured in that SLA Domain. + +When an accidental deletion, unintended change, or misconfiguration occurs, you can recover the required objects from these snapshots. RSC provides the flexibility for granular recovery of individual Okta objects, along with their related objects and the complex relationships between them. For example, a user and their assigned groups or applications. + +To perform a successful recovery, you must first understand how RSC handles the following relationships and data conflicts: + + * Relationship restore scope + * Recreate objects and restore relationships + * Multi-valued data recovery rules + + *[ > ]: and then diff --git a/openstack_add_openstack_virtual_machine.md b/openstack_add_openstack_virtual_machine.md new file mode 100644 index 0000000000000000000000000000000000000000..d629d00d412be325cc24f66bf4a3a5c92594f62d --- /dev/null +++ b/openstack_add_openstack_virtual_machine.md @@ -0,0 +1,12 @@ +# Add an OpenStack virtual machine + +Source: https://docs.rubrik.com/en-us/saas/openstack/add_openstack_virtual_machine.html + +--- + +# Add an OpenStack virtual machine + +Add an OpenStack virtual machine to RSC so you can perform snapshots to protect your data. + +After adding your OpenStack virtual machine to RSC, you can configure SLA Domains to create snapshots for data protection. + *[ > ]: and then diff --git a/openstack_exporting_openstack_vm_snapshots.md b/openstack_exporting_openstack_vm_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..24e8a1ddc3c2cff5f5ef9d6ff23f5b7850fff9a2 --- /dev/null +++ b/openstack_exporting_openstack_vm_snapshots.md @@ -0,0 +1,70 @@ +# Exporting OpenStack virtual machine snapshots + +Source: https://docs.rubrik.com/en-us/saas/openstack/exporting_openstack_vm_snapshots.html + +--- + +# Exporting OpenStack virtual machine snapshots + +Export an OpenStack virtual machine snapshot to create a point-in-time copy for backup or migration. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory and then Data Center. + +The Inventory page appears. + + 4. Click on the OpenStack inventory card. + +The inventory list for OpenStack appears. + + 5. Select the Virtual Machines page. + +Alternatively, enter a name in the search field or use the filters. + +The virtual machine details page displays the Snapshots card showing the calendar view. + + 6. Select the virtual machine that includes the files or folders for export. + 7. On the Snapshots card, select a day that has a green dot. + +The green dot indicates that at least one successful snapshot was created on that day. + +The Snapshots card displays the Day view. + + 8. Open for the snapshot and select Recover. + +The VM Recovery wizard appears. + + 9. Select Export and click Next. + +The VM Recovery wizard displays the Select a Project page. + + 10. Select the projects to recover and click Next. + 11. Select the availability zones to recover and click Next. + 12. Select the networks to recover and click Next. + 13. Select the volume type to recover and click Next. + 14. Configure the details for the new virtual machine and click Next. + +Detail| Description +---|--- +Flavor | Configuration of the virtual hardware resources +Key Pair | Key pair used to authenticate the virtual machine +Security Groups | Security groups associated with this virtual machine +Export VM Name | Optional. Name for the exported virtual machine +Power on exported VM | Optional. Powers on the exported virtual machine. + + 15. Review the confirmation details and click Export. + +## Results + +You have successfully exported an OpenStack virtual machine snapshot. RSC creates a new virtual machine from the selected snapshot. + +## What to do next + +You can monitor the progress of the export task from the Events page. + *[ > ]: and then diff --git a/openstack_manage_protection_openstack_vms.md b/openstack_manage_protection_openstack_vms.md new file mode 100644 index 0000000000000000000000000000000000000000..053f2e477155f010c206bebfdddadf8b01ffb50e --- /dev/null +++ b/openstack_manage_protection_openstack_vms.md @@ -0,0 +1,12 @@ +# Manage protection for OpenStack virtual machines + +Source: https://docs.rubrik.com/en-us/saas/openstack/manage_protection_openstack_vms.html + +--- + +# Manage protection for OpenStack virtual machines + +After completing the protection setup for OpenStack virtual machines, RSC takes automated snapshots of those virtual machines and disks based on the configured policies in SLA Domains. You can also take on-demand snapshots, recover files and folders from OpenStack virtual machines, and export OpenStack virtual machine snapshots. + +After you have completed the protection setup for OpenStack virtual machines, RSC starts taking automated snapshots of those virtual machines and disks according to the data protection policies you configured in the assigned SLA Domains. You can view detailed snapshot information on the Inventory page for OpenStack virtual machines. Based on your requirements, you can take on-demand snapshots of your workloads and perform snapshot management tasks such as modifying retention policies and deleting snapshots. + *[ > ]: and then diff --git a/openstack_openstack_virtual_machines.md b/openstack_openstack_virtual_machines.md new file mode 100644 index 0000000000000000000000000000000000000000..8d183150306981444893ac31fa836b7fde818bd0 --- /dev/null +++ b/openstack_openstack_virtual_machines.md @@ -0,0 +1,15 @@ +# OpenStack virtual machines + +Source: https://docs.rubrik.com/en-us/saas/openstack/openstack_virtual_machines.html + +--- + +# OpenStack virtual machines + +RSC provides data management, SLA Domain protection, and recovery for OpenStack virtual machines. + +RSC can manage the protection and recovery of OpenStack virtual machines. + +RSC secures and automates data protection processes for OpenStack virtual machines, ensuring that data remains protected against accidental deletions, ransomware attacks, and other potential threats. With RSC, organizations can automate backup and recovery using a global policy model called an SLA Domain. SLA Domains allow organizations to reduce management complexity by automating the snapshot process. + +Protecting OpenStack virtual machines with RSC involves a structured approach that ensures comprehensive and consistent data protection policies. diff --git a/openstack_openstack_vm_management.md b/openstack_openstack_vm_management.md new file mode 100644 index 0000000000000000000000000000000000000000..1fb3c880cd80dd436cc617f4ecb0bbc39c9c060c --- /dev/null +++ b/openstack_openstack_vm_management.md @@ -0,0 +1,16 @@ +# OpenStack virtual machine management + +Source: https://docs.rubrik.com/en-us/saas/openstack/openstack_vm_management.html + +--- + +# OpenStack virtual machine management + +You can use RSC to onboard, refresh, edit, monitor, and delete OpenStack virtual machines. + +After you complete the onboarding and protection setup for OpenStack virtual machines, RSC takes automated snapshots of those virtual machines based on the configured policies in SLA Domains. You can also take on-demand snapshots, add, edit, or remove OpenStack environments, recover OpenStack files and folders, and export OpenStack snapshots. + +From the OpenStack virtual machine dashboard, you can view detailed snapshot information on the Inventory page for OpenStack virtual machines. + +Based on your requirements, you can take on-demand snapshots of your workloads and perform snapshot management tasks such as modifying retention policies and deleting snapshots. + *[ > ]: and then diff --git a/openstack_recover_openstack_vms.md b/openstack_recover_openstack_vms.md new file mode 100644 index 0000000000000000000000000000000000000000..e4783a1f1e22fb700084183cc989281435b375ad --- /dev/null +++ b/openstack_recover_openstack_vms.md @@ -0,0 +1,19 @@ +# Recover OpenStack virtual machines + +Source: https://docs.rubrik.com/en-us/saas/openstack/recover_openstack_vms.html + +--- + +# Recover OpenStack virtual machines + +You can recover files and folders used by OpenStack virtual machines by mounting snapshots from local clusters or remote archival locations. You can also export an OpenStack virtual machine snapshot to create a point-in-time copy for backup or migration. + +To recover files and folders from an OpenStack virtual machine, a Rubrik cluster mounts a point-in-time copy of that virtual machine. + +You can recover the files and folders from snapshots available in the following locations: + + * Snapshots that are locally available on the Rubrik cluster. Local snapshots include those downloaded from archival locations or replication targets to a Rubrik cluster. + + * Snapshots that are only available at remote archival locations or replication targets, or from local snapshots that have expired. + + *[ > ]: and then diff --git a/openstack_setup_protection_openstack_vms.md b/openstack_setup_protection_openstack_vms.md new file mode 100644 index 0000000000000000000000000000000000000000..edd7c95f2a8c8085d03c6806b6995e8b6f6582dc --- /dev/null +++ b/openstack_setup_protection_openstack_vms.md @@ -0,0 +1,16 @@ +# Set up protection for OpenStack virtual machines + +Source: https://docs.rubrik.com/en-us/saas/openstack/setup_protection_openstack_vms.html + +--- + +# Set up protection for OpenStack virtual machines + +RSC protects OpenStack virtual machines and regions using SLA Domains and on-demand snapshots. + +RSC provides protection for OpenStack virtual machines and regions through two methods: + + * SLA Domains: You can create and assign SLA Domains to protect OpenStack virtual machines and regions. + * On-demand snapshots: You can take on-demand snapshots to create a recovery point for your OpenStack virtual machines and regions. + + *[ > ]: and then diff --git a/oracle_about_db_clones.md b/oracle_about_db_clones.md new file mode 100644 index 0000000000000000000000000000000000000000..28880772104548d0a9126499ad698b19ee04da6e --- /dev/null +++ b/oracle_about_db_clones.md @@ -0,0 +1,44 @@ +# Database clones for Oracle + +Source: https://docs.rubrik.com/en-us/saas/oracle/about_db_clones.html + +--- + +# Database clones for Oracle + +You can clone an Oracle database by selecting a recovery point to clone to a target location. + +The target location must be an Oracle host or Oracle RAC cluster other than the source Oracle host or RAC cluster. Using the source Oracle host or RAC cluster as the target location can damage the source database during the cloning process. + +The target Oracle host or Oracle RAC must be registered with the same Rubrik cluster as the source for files-only mount and files-only export, archive log restore, and validation. To ensure compatibility, the target host or RAC cluster must also use the same version of Oracle binaries. + +Rubrik supports the following clone scenarios: + + * Oracle RAC database to Oracle RAC database + * Single instance database using FS to another single instance server using FS + * Single instance database using ASM storage to another single instance server using ASM + * Clone to another instance using a minimal `spfile` to provide the clone configuration parameters. In this case the source database `spfile` is restored on the target host, replacing the minimal `spfile` provided to create the clone. + +The Rubrik cluster supports automated recovery only for databases created using an SPFILE file. Databases created using a PFILE must use DBA managed recovery. + +Cloning a database uses pre-recovery and post-recovery scripts. These scripts must exist at the provided path on all the target nodes for a RAC and must be executable by the Oracle user defined for the target Oracle host or RAC nodes. The Rubrik cluster considers a script exit status other than 0 to be a script failure. The Rubrik cluster displays notifications of script failures in the Activity Log. + +For an Oracle RAC database clone, the target Oracle RAC must have at least as many nodes as the number of instances from the source Oracle RAC database. Nodes are assigned in numerical order. + +During a clone operation, BCT is enabled on the target database if it is enabled on the source database. + +Any existing tempfiles on the target host that use the same path as any tempfiles associated with the source database are overwritten during clone or Live Mount operations. + +## Oracle RAC database clone + +Clone configuration for an Oracle RAC database with four nodes, n1, n2, n3, and n4, and a database running on two of those nodes, n3 and n4. The Oracle RAC database is cloned to a target Oracle RAC system with nodes t1, t2, t3, and t4. The Rubrik cluster brings up the database on nodes t1 and t2. + +The configuration can be manually changed to match the configuration of the original Oracle RAC. + +The following table describes the available clone configuration options. + +Option | Description +---|--- +Fully-automated clone | Restores the database files and recovers the database. Starts the database instance after creating it and updates the /etc/oratab file. +DBA-managed clone | The database files and archived logs are exposed for DBA recovery with custom scripts.For automated recovery back to the source host or Oracle RAC, if the recovery point is not the most recent snapshot, a full backup is created after the recovery completes. + *[ > ]: and then diff --git a/oracle_aco_custom_pfiles.md b/oracle_aco_custom_pfiles.md new file mode 100644 index 0000000000000000000000000000000000000000..653ebe3fa999d45a056566525d59943efccbe56b --- /dev/null +++ b/oracle_aco_custom_pfiles.md @@ -0,0 +1,29 @@ +# Advanced Cloning Operations and custom PFILES + +Source: https://docs.rubrik.com/en-us/saas/oracle/aco_custom_pfiles.html + +--- + +# Advanced Cloning Operations and custom PFILES + +You can use the Advanced Cloning Operations or a custom PFILE options when you require the target recovery operation to use a different configuration than the source database backup. + +Custom PFILE or Advanced Cloning Operation (ACO) recovery allow for database Live Mounts or clones that use configurations other than the original SPFILE configuration, providing you with a broader range of recovery options. + +ACO is a Rubrik-defined recovery configuration format. PFILE are Oracle-defined files. + +ACOs support overriding a limited set of configuration parameters, whereas a custom PFILE supports all recovery parameters recognized by the version of Oracle on the target host. + +When you use a custom PFILE during a clone operation, the ACO file supports only these parameters: + + * ORACLE_HOME + * SPFILE_LOCATION + +When you use a custom PFILE during a Live Mount, the ACO file supports only these parameters: + + * ORACLE_HOME + * SPFILE_LOCATION + * DB_CREATE_ONLINE_LOG_DEST_n + +You must add all other ACO parameters to the custom PFILE. + *[ > ]: and then diff --git a/oracle_archive_log_restoration.md b/oracle_archive_log_restoration.md new file mode 100644 index 0000000000000000000000000000000000000000..77c037ca0c2b917d8daca7615222206787215878 --- /dev/null +++ b/oracle_archive_log_restoration.md @@ -0,0 +1,16 @@ +# Archive log restore + +Source: https://docs.rubrik.com/en-us/saas/oracle/archive_log_restoration.html + +--- + +# Archive log restore + +Archive log restore reinstates archived logs from a specified time range or log sequence period. + +Archive log restore enables database administrators (DBAs) to roll forward a database by applying only selected archive logs and enables log mining for historical information by obtaining a series of events that occurred on the database using the archive logs as input. Archive log restore is available on Rubrik CDM versions 5.3.3 and later. + +Archive log restore uses a time period as input to determine the logs included in the operation. Archive logs falling within the specified time period are mounted on the target host or RAC cluster over NFS. The DBA can also manually restore the archive logs. + +Archive logs are exposed at the granular level for log snapshots. If an archive log falls within a time period, all files from that log snapshot are exposed, including the Oracle control files. These files are redistributed among separate log directories. For log snapshots taken since Rubrik CDM version 5.3, archive logs are exposed as backup sets rather than individual log files. + *[ > ]: and then diff --git a/oracle_backups_arch_redo_logs.md b/oracle_backups_arch_redo_logs.md new file mode 100644 index 0000000000000000000000000000000000000000..d74ec35be125c53b56a9c6ef72d6a1c1fb0bda4a --- /dev/null +++ b/oracle_backups_arch_redo_logs.md @@ -0,0 +1,28 @@ +# Backups and archived redo logs + +Source: https://docs.rubrik.com/en-us/saas/oracle/backups_arch_redo_logs.html + +--- + +# Backups and archived redo logs + +The Rubrik cluster protects Oracle databases with backups and archived redo log backups, running as separate jobs and at different frequencies in the Rubrik cluster. + +Database backups and archived redo log backups are required for the database to be recoverable. When on-demand snapshots are taken, both on-demand database backups and log backups are required. The Rubrik cluster requires the on-demand log backup to collect archived redo logs. When configuring log backup, you must configure the log frequency and log retention. + +The Rubrik cluster creates snapshots of the archived redo logs as part of a database snapshot job. A backup of all the archived redo logs, generated during the database snapshot, is required to restore from a snapshot. If a database snapshot appears as unrecoverable, verify the archived redo log snapshots are available to capture the archived redo logs generated over the duration of the database snapshot. + +By default, the Rubrik cluster deletes the logs from the source after it saves the log snapshots. The cluster retains the RMAN script execution logs on the host for three days in the /var/log/rubrik/script_logs/database_name directory, where database_name is the unique name of the database to which the logs belong. + +If instant archiving is configured, logs are archived to the cloud, and expired from the cloud, in accordance with the configured log backup retention policy. + +Database backups are governed by SLA Domain assignments. Archived redo log backups are governed by log backup frequency. Database backup retention is governed the SLA Domain assignment, and archived redo log backup retention is governed by log retention hours. + +The Rubrik cluster leverages Oracle RMAN to perform database backups. This activity directly writes data to the Rubrik cluster through the Oracle RMAN channels. + +Oracle Enterprise version is required to support parallel streaming through all channels. + +The database log backup frequency value is inherited from the parent Oracle host or Oracle RAC. Setting a value directly for the database overrides this value. If no value is specified, log backup jobs are not scheduled. Rubrik clusters pause Oracle log backups during a cluster-wide pause in backups. + +Database backups become expired based on the SLA Domain. Archived redo log backups become expired based on the defined log backup retention policy. The Database backup retention configuration should be longer than log backup retention configuration. + *[ > ]: and then diff --git a/oracle_export_database_logs_usb.md b/oracle_export_database_logs_usb.md new file mode 100644 index 0000000000000000000000000000000000000000..5df56df903175bf3dcec80335c653a7f9f19c76c --- /dev/null +++ b/oracle_export_database_logs_usb.md @@ -0,0 +1,20 @@ +# Export Oracle database logs to a USB device + +Source: https://docs.rubrik.com/en-us/saas/oracle/export_database_logs_usb.html + +--- + +# Export Oracle database logs to a USB device + +You can use Rubrik REST APIs to export logs from multiple Oracle databases to USB devices. + +You can use Rubrik REST APIs to export multiple Oracle database logs to a USB device attached to a Rubrik cluster node using a single API call. You can safely use the USB device to export the database logs to another Rubrik cluster or server without risking corruption, essentially allowing the export of the logs to an air-gapped environment. + +After issuing the REST APIs to transfer the database log, the Rubrik cluster checks for sufficient available space in the USB device. The cluster then provides a warning if the space available is insufficient for the database log. The Rubrik cluster does not, however, perform space management operations. If more space is required for the database log export, you can manually free space on the USB device. The Rubrik cluster includes dynamic checkpoints for each database and tracks which logs should be exported to the USB device. + +Rubrik REST APIs are designed to export only log files. You cannot use them to export data files. RSC exports the logs in native format and does not encrypt them during export. + +Rubrik recommends formatting the USB devices with a single ext4 partition and assigning them an alphanumeric label name. The Rubrik cluster successfully exports to USB devices that are not formatted for ext4, but the export performance could be degraded. + +You can use Rubrik REST APIs to export multiple database logs to a USB device, retrieve details about the log export, and view the current database checkpoint. + *[ > ]: and then diff --git a/oracle_number_of_channels_in_recovery.md b/oracle_number_of_channels_in_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..5df4a32ded4c82490630490a4dda331ea436e921 --- /dev/null +++ b/oracle_number_of_channels_in_recovery.md @@ -0,0 +1,18 @@ +# Number of channels in recovery + +Source: https://docs.rubrik.com/en-us/saas/oracle/number_of_channels_in_recovery.html + +--- + +# Number of channels in recovery + +The value for the number of channels in recovery can be configured for Live Mount, Clone, Restore, Instant Recovery, and Validation operations. + +Changing the number of recovery channels for operations is optional. By default, the number of channels used for recovery is the same as the number of channels used in the database and log snapshots being recovered. + +The value for the number of channels in recovery determines the number of channels allocated in the RMAN scripts. The total number of channels must be greater than zero and less than or equal to 32. + +Changing the number of channels in recovery affects CPU and memory usage during the recovery process. + +Contact Rubrik Support to configure the maximum number of channels in recovery to a higher threshold. + *[ > ]: and then diff --git a/oracle_oracle_adv_clone_mount_params.md b/oracle_oracle_adv_clone_mount_params.md new file mode 100644 index 0000000000000000000000000000000000000000..2edc053e254738ee5fa09371fc6a42fb741ab96a --- /dev/null +++ b/oracle_oracle_adv_clone_mount_params.md @@ -0,0 +1,22 @@ +# Advanced Oracle DB clone and mount parameters + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_adv_clone_mount_params.html + +--- + +# Advanced Oracle DB clone and mount parameters + +A parameters file allows you to specify advanced recovery options for live mount and cloning tasks. + +You can customize the database parameters during live mount or clone recoveries by creating a configuration parameters file to input database parameters before initiating the recovery job. + +For a successful recovery of standalone databases on file systems and Oracle RAC databases, you must configure either `DB_RECOVERY_FILE_DEST` or `DB_CREATE_FILE_DEST`. If both parameters are not set in the source database, at least one must be set in the configuration file. + +Important: + +The Oracle Home Owner must ensure that the location directories already exist on the target Oracle host or Oracle RAC and are accessible. Existing files at the locations specified in the configuration file are overwritten during the recovery. + +RSC running Rubrik CDM versions 9.3 and later allows you to include any advanced cloning options (ACO) parameters available from Oracle, providing a greater variety of options for workloads protected by Oracle. RSC supports using these ACO parameters for cloning options and for live mounts with a database name change. You can include these ACO parameters using REST APIs or using the RSC UI. + +When using the ACO parameters, ensure that RSC performs only a syntactical validation before passing the parameters to Oracle and does not validate the data included with these parameters. Providing an invalid ACO parameter that results in an unexpected value may impact the recovery and your Oracle database environment. + *[ > ]: and then diff --git a/oracle_oracle_config.md b/oracle_oracle_config.md new file mode 100644 index 0000000000000000000000000000000000000000..aba4b090b0d6c94c40ae8f8a37484b332f2556dc --- /dev/null +++ b/oracle_oracle_config.md @@ -0,0 +1,14 @@ +# Oracle configuration + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_config.html + +--- + +# Oracle configuration + +Initial configuration of the Rubrik cluster for Oracle requires at least one open or mounted Oracle database and a user account with SYSDBA privileges. + +After initial configuration, you can create a database administrator account with the ability to manage, protect, and recover selected Oracle databases. The permissions granted to this account can be limited to specific databases. + +Auto discovery requires a host with at least one database in the `OPEN` or `MOUNTED` state. If no database is available, create an empty /etc/oratab file. + *[ > ]: and then diff --git a/oracle_oracle_data_guard_rubrik_clusters.md b/oracle_oracle_data_guard_rubrik_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..fea50718e111693b11bb685805f7571b8f3c2213 --- /dev/null +++ b/oracle_oracle_data_guard_rubrik_clusters.md @@ -0,0 +1,32 @@ +# Oracle Data Guard on Rubrik clusters + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_data_guard_rubrik_clusters.html + +--- + +# Oracle Data Guard on Rubrik clusters + +Rubrik clusters support Oracle Data Guard configurations to back up primary and standby databases and to discover new Data Guard groups. + +Oracle Data Guard creates, manages, and monitors standby databases that protect Oracle databases against disasters and data corruption. An Oracle Data Guard configuration consists of synchronized primary and standby databases that aid in performing disaster recovery. The standby database in a Data Guard configuration is a physical standby. In the event of a primary site disaster, the primary database fails over to the standby database, which then becomes the new primary database. + +Rubrik clusters discover primary and standby databases that are part of a Data Guard configuration and register them as a single logical entity. This single logical entity is known as a Data Guard group. + +Rubrik clusters support backups from physical standby databases in an Active Oracle Data Guard configuration, which allows read-only access to the standby node while it simultaneously applies archived transactions from the primary node. For regular Data Guard with standby in mounted mode, you can perform a backup on a standby host if the primary database is registered to the same cluster or if the Oracle host has SEPS wallet configured. + +When Rubrik CDM version 9.0.1 or later performs a backup, it checks whether the Data Guard member used for the current backup is different from the member used for the previous backup. The Data Guard member can be either a primary or standby database. If the Rubrik cluster compares the current and previous members and determines that it can safely perform an incremental backup instead of a full backup, the Rubrik cluster performs an incremental backup to save time and resources. If the difference between the backups is sufficient to require a full backup, then the Rubrik cluster performs a full backup. + +Rubrik clusters monitor database role changes for switchover and failover events, making it easier to track the database roles as they change. For example, if a database role changes from primary database to standby database, the Rubrik cluster tracks the change and displays the current role of the database in the Rubrik CDM web UI. + +Note: + +Rubrik recommends always performing a full database backup after a failover, failback, or switchover operation, because these operations create new database versions, causing a database incarnation change. + +Rubrik clusters perform database and log backups for both primary and standby databases. Offloading a backup task to a standby database helps to free resources on the production environment. + +Rubrik clusters discover only Data Guard databases that have the DG_CONFIG option set in the `LOG_ARCHIVE_CONFIG` parameter. The Oracle Database Reference provides more information about the `DG_CONFIG` option. + +During every log backup job, Rubrik clusters delete logs from all the members of the Data Guard group added to the Rubrik clusters. + +The Rubrik Compatibility Matrix provides more information about supported Oracle versions and specific fixes that might affect the Oracle Data Guard feature. + *[ > ]: and then diff --git a/oracle_oracle_databases_rsc.md b/oracle_oracle_databases_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..29a9a73bd96e2dea6f2fef86de75522142d57798 --- /dev/null +++ b/oracle_oracle_databases_rsc.md @@ -0,0 +1,13 @@ +# Oracle databases + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_databases_rsc.html + +--- + +# Oracle databases + +You can use RSC to back up, archive, replicate, and recover Oracle databases. + +With RSC, standard Oracle databases and Oracle Data Guard configurations are automatically discovered and protected by SLA Domains. + +For Oracle databases protected by RSC, RMAN script or catalog management is eliminated and Automated Live Mount and Instant Recovery features are enabled. diff --git a/oracle_oracle_instant_recovery.md b/oracle_oracle_instant_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..253c80ebbfb9e4a7a67bb1017d210c5c26688cdb --- /dev/null +++ b/oracle_oracle_instant_recovery.md @@ -0,0 +1,48 @@ +# Instant Recovery for Oracle + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_instant_recovery.html + +--- + +# Instant Recovery for Oracle + +Instant Recovery for Oracle replaces an existing database with a point-in-time copy, requiring specific configurations and directory setup. + +Instant Recovery for Oracle enables you to recover an Oracle database to a specific point-in-time by mounting a database snapshot directly on the target standalone Oracle host or Oracle Real Application Clusters (RAC). + +## Prerequisites + +Before attempting an Instant Recovery, you must meet the following prerequisites: + + * Delete the existing database using the DROP DATABASE command. + +Important: + +Do not use Oracle Database Configuration Assistant (DBCA) or similar tooling that deletes the entire database including the base directories. + + * Confirm the source database is running an `spfile`. Instant Recovery fails on Oracle databases without an `spfile`. The Rubrik cluster supports automated recovery only for databases created using an SPFILE. Databases created using a PFILE must use DBA-managed recovery. + * Remove any stale backup files on the target host (including the FRA) that belong to the database being restored. + +## Considerations + +It is important that you consider the following points when performing the Instant Recovery: + + * During an Instant Recovery, the Rubrik cluster expects the parent directories for the different parameters such as datafile paths, control file paths, redo log paths, audit file destination, FRA path, and spfile path to already exist on the Oracle host, or individual node of the Oracle RAC, before the recovery process. This applies to both local file-system paths and ASM paths. + * For an Oracle RAC or standalone Oracle host with ASM database, if the control files are present on both ASM and local file-system, only the files on ASM are restored during Instant Recovery. + * An Instant Recovery does not change the location for redo logs but does consolidate the multiple members of redo log groups into a single member for each group. + * You can use the Oracle live migration feature after Instant Recovery to gradually move database storage back to the native storage on the database host. Oracle manages live migration outside of the Rubrik cluster. For more information, refer to the Oracle documentation. Instant Recovery brings up the database storage with datafiles present. However, redo logs and control files are on the host, File System (FS) or Automatic Storage Management (ASM), to allow live migration. + +Note: + +Instant Recovery requires a database backup containing all the datafiles. However, if a new datafile is added after a database backup but before the recovery point-in-time, Instant Recovery automatically restores the newly added file. + +## Instant Recovery process + +The Rubrik cluster mounts the database snapshot on the selected standalone Oracle host or Oracle RAC, connects the recovered single instance Oracle host or Oracle RAC to the network, and powers up the new instance. + +The Rubrik cluster requires a number of parent directories to exist on the Oracle host or individual node of the Oracle RAC system prior to the recovery process. + +During the process, messages about the status appear in the Activity Log. After the process is complete, the Rubrik cluster records the final result of the task in the Activity Log. The Rubrik cluster lists the recovered Oracle database on the Live Mounts page of Rubrik. + +The instantly recovered Oracle database derives SLA Domain protection from parent objects. Even though the SLA Domain is inherited, backups fail until it is migrated off storage and unmounted. + *[ > ]: and then diff --git a/oracle_oracle_live_mount.md b/oracle_oracle_live_mount.md new file mode 100644 index 0000000000000000000000000000000000000000..74ebb476bbc6c23c2770351e783d7aa2924efafa --- /dev/null +++ b/oracle_oracle_live_mount.md @@ -0,0 +1,36 @@ +# Oracle Live Mount + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_live_mount.html + +--- + +# Oracle Live Mount + +An Oracle Live Mount creates a database from a point-in-time copy of the source database to speed up recovery time. + +The Live Mount recovery method is often used for: + + * Reducing recovery time when there is a problem with the source database. + * Testing the database using a copy of the source database. + +## Requirements and restrictions + +To perform a fully automated Live Mount recovery, the source and target configurations must be the same. For example, you can recover an Oracle Real Application Clusters (RAC) to an Oracle RAC, an Oracle single instance to an Oracle single instance, and an ASM-managed database to an ASM-managed database. + +The source and target configurations need not be the same on a files-only Live Mount recovery, which allows the Database Administrator (DBA) to mount the backup images from the Rubrik cluster at a specified location on the Oracle host or RAC. By default, mount points are persistent across reboots. If a host shuts down, you can remount the paths to the Live Mount files after it reboots. + +## Operations and Live Mount options + +Any existing tempfiles on the target host that use the same path as any tempfiles associated with the source database are overwritten during clone or Live Mount operations. + +The Rubrik cluster supports automated recovery only for databases created using an SPFILE. Databases created using a PFILE must use the DBA-managed recovery. + +Block Change Tracking (BCT) is not enabled on the target database during a Live Mount operation even if it is enabled on the source database. + +To restore to a point-in-time after a data file is added but before the next database backup is taken, you must use either a Clone or a Restore operation. + +The following table describes the Live Mount options. Option | Description +---|--- +Fully-automated Live Mount | During the Live Mount of an Oracle database backup, the Rubrik cluster automatically mounts the data files, creates the database instance, and adds the new database to the /etc/oratab file on the Oracle host. +DBA-managed Live Mount | As part of the Live Mount operation, the Rubrik cluster provides the alternative to mount the datafile backups, log backups, and the control files at a specified location on the Oracle host. The data remains on the Rubrik cluster with a specified mount point on the Oracle host. This method allows the DBA to perform the actual recovery using custom scripts. + *[ > ]: and then diff --git a/oracle_oracle_pluggable_databases.md b/oracle_oracle_pluggable_databases.md new file mode 100644 index 0000000000000000000000000000000000000000..bd28cb2c48a6655f41aad7831eab4ec74de3a270 --- /dev/null +++ b/oracle_oracle_pluggable_databases.md @@ -0,0 +1,31 @@ +# Oracle pluggable databases + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_pluggable_databases.html + +--- + +# Oracle pluggable databases + +You can restore, mount, and clone Oracle pluggable databases on the Rubrik cluster. + +In Oracle servers, databases are organized into a multitenant container architecture, which uses container databases (CDB) to hold pluggable databases (PDBs). + +A CDB: + + * Is a collection of zero, one, or many customer-created PDBs. + * Includes containers that are either a PDB or a root database. + +Containers within a CDB can contain a combination of the objects described in the following table. + +Object | Description +---|--- +Root database | A root database is a collection of schemas, schema objects, and non-schema objects for all PDBs. +PDB | A PDB is a user-created database that contains the data and code required for a specific set of features or an application.For example, a PDB can support a specific application, such as a human resources or sales application, and the data required to support these applications. When a CDB is created, PDBs do not exist (except for PDB$SEED, which is a template for new PDBs). You must create the PDBs based on your business requirements. +Application container | Application containers store data and metadata for multiple application backends. Application containers are user-created and consist of an application root, an optional application seed PDB, and the application PDBs plugged into this application root. An application root belongs to the CDB root and does not belong to any other container. + +Multitenant architecture often provides simple methods to protect the entire CDB but rarely provides a method to protect a single PDB. Rubrik cluster protection of CDBs allows granular recovery at the PDB level, providing simple and fast methods for protecting PDBs. + +Rubrik cluster protection of CDBs provides a reduced recovery time by allowing you to restore only the required PDB data and ignore the remaining PDB data that does not need to be restored. Because Rubrik PDB restore is automatic, it eliminates the process of manually restoring the PDB and saves time for database administrators. + +The Oracle user documentation includes a detailed description of PDBs and CDBs. + *[ > ]: and then diff --git a/oracle_oracle_recovery_using_scns.md b/oracle_oracle_recovery_using_scns.md new file mode 100644 index 0000000000000000000000000000000000000000..186242eee1ff017ae2e4d4eca3439dc2e8ba0a2e --- /dev/null +++ b/oracle_oracle_recovery_using_scns.md @@ -0,0 +1,23 @@ +# Oracle recovery using SCNs + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_recovery_using_scns.html + +--- + +# Oracle recovery using SCNs + +You can recover Oracle snapshots and mount archive logs using the system change number instead of the date and time when the snapshot occurs, providing a more accurate point of recovery. + +With Rubrik CDM version 9.3 and later, you can use the Oracle system change number (SCN) to recover Oracle live mounts and to mount archive logs. Recoveries using the Oracle SCN are generally more precise than recoveries based on a specific time, because the Oracle database provides an SCN for each transaction as it occurs. Since the granularity of these changes is far more precise than a time-based recovery, recoveries that use an SCN are also much more precise. + +When using Oracle SCNs to recover Oracle databases, it is important to remember that you cannot use them: + + * For a clone recovery. + * For a download. + * For a pluggable database (PDB) restore. You can, however, restore PDBs using SCNs using Rubrik REST APIs. + * To perform a live mount to the same host. + * To perform a live mount that uses a new name. + * To select SCN PDBs during a live mount. You can, however, select PDBs during a live mount using Rubrik REST APIs. + +When you are unsure which Oracle SCN to specify during a recovery, you can view the SCNs RSC used for log and database snapshots in the backup events in the Events tab of the RSC. + *[ > ]: and then diff --git a/oracle_oracle_seps_wallet.md b/oracle_oracle_seps_wallet.md new file mode 100644 index 0000000000000000000000000000000000000000..1bbb192adea0cdf9dba5e12cf8846dd69aa9afbd --- /dev/null +++ b/oracle_oracle_seps_wallet.md @@ -0,0 +1,28 @@ +# Oracle SEPS wallet + +Source: https://docs.rubrik.com/en-us/saas/oracle/oracle_seps_wallet.html + +--- + +# Oracle SEPS wallet + +The Oracle Secure External Password Store wallet feature provides additional security for connections by not exposing your username and password on the command line when you log in. The feature stores the password credentials in the client-side Oracle wallet. + +After you configure Oracle Secure External Password Store (SEPS), this feature stores the password credentials required for connecting to databases in a client-side Oracle SEPS wallet, which serves as a secure software container. The password credentials include the username and password. When you use the SEPS wallet, you can establish connections using the /@db_alias syntax, which prevents the connection details from being exposed on the command line. + +The SEPS wallet directory and files can be owned by a user other than the default Oracle Home owner. Changing ownership of the SEPS wallet creates an additional layer of security by ensuring that the owner of the Oracle binaries cannot view or modify the wallet. + +When an Oracle host has only the SEPS wallet feature enabled, RSC supports only backup, discovery, and files-only recoveries that are managed by database administrators. You must provide the SYSDBA user account for automated recovery. + +RSC supports the SEPS wallet feature during database discovery and backup and during log switch. + +By default, the SEPS wallet is a 3DES encrypted wallet. Although 3DES provides strong encryption, you can also implement advanced encryption, such as AES256 for the SEPS wallet. The Oracle documentation provides instructions for converting the 3DES wallet to AES256. The SEPS wallet does not require a license for the Advanced Security Option (ASO). + +For Oracle Data Guard databases, the Rubrik cluster uses the SEPS wallet to establish a connection with the primary database and initiate a log-switch operation on the primary database during log backups. Additionally, the Rubrik cluster uses the SEPS wallet to establish a connection from the standby database to the primary database, to convert backup system change numbers (SCNs) to timestamps while backing up the standby database in mounted mode. + +To prepare for a Data Guard switchover or failover operation, you must include a SEPS wallet on both primary and standby servers, and on all RAC nodes. + +The Oracle document Using The Secure External Password Store (Doc ID 340559.1) provides more information about using and configuring the SEPS wallet. + +Oracle documentation and Oracle support provide more information about setting up SEPS wallets for advanced Oracle configurations such as RAC, TDE plus SEPS wallets, and Oracle versions 18c and 19c. + *[ > ]: and then diff --git a/oracle_point-in-time_recovery.md b/oracle_point-in-time_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..c005089834e7bec8309c2e996d478c36e9ee5bc5 --- /dev/null +++ b/oracle_point-in-time_recovery.md @@ -0,0 +1,37 @@ +# Point-in-time recovery + +Source: https://docs.rubrik.com/en-us/saas/oracle/point-in-time_recovery.html + +--- + +# Point-in-time recovery + +Point-in-time recovery restores database and log snapshots to the defined point in time. + +Recover to a specific point-in-time by selecting a recovery time from the recoverable range. + +Recovery points are based on the last snapshot created before the selected point in time and the archived redo log backups created between the time of the snapshot and the selected recovery point. The Rubrik cluster recovers the database from the snapshot and the log content is unrolled and applied up to the selected point in time. + +Assign a database to an SLA Domain with frequent snapshots to ensure quick recovery. The closer the snapshot to the selected recovery point, the shorter the recovery time objective (RTO) the process requires. + +Supported recovery options are: + + * Database recovery to a different single instance Oracle host or Oracle RAC with RBS installed + * Database recovery to a different single instance ASM-managed Oracle host with RBS installed + * Tablespace recovery to the same single instance Oracle host or Oracle RAC with a database configured + * Files only (data files, archived logs and control files) + * The Clone files only option copies all the files to the host + * The Live Mount files only option keeps the files on the mounted (through NFS) the Rubrik cluster storage + * Live Mount recovery to a different single instance Oracle host or Oracle RAC system + * Live Mount recovery to a different single instance ASM-managed Oracle host + * Instant Recovery to the same single instance Oracle host or Oracle RAC where the original database is destroyed + * Instant Recovery to the same single instance ASM-managed Oracle host where the original database is destroyed + * Same host recovery to restore a database back to the production Oracle host or Oracle RAC + * Roll forward recovery to restore to a specific archive log destination on the host. Archive logs in that directory are applied on the database. + * PDB restore for Oracle Container Databases (CDBs), during which one or more pluggable databases (PDBs) can be restored back to the source CDB + * Log mount reinstates archived logs from a specified time range or log sequence period + +To resume protection of a restored database, assign an SLA Domain to the database separately. Live mounted databases are not backed up. A Live Mount must be migrated off the Rubrik cluster storage and unmounted before a backup can be created. An SLA Domain cannot be assigned to a live mounted database directly. The Live Mount can inherit the SLA Domain from its parent but backups cannot occur until the live mounted database is migrated and unmounted. + +By default, restore operations allocate 30% of the host memory as the value of the `SGA_TARGET` parameter, which specifies the total memory size of the System Global Area. Restore operations also allocate 10% of host memory as the value for the `PGA_AGGREGATE_TARGET` parameter, which specifies the total memory size of the Program Global Area. To enable successful restore operations, the value of the `SHMMAX` setting must be at minimum 40% of the memory available on the host. The `SHMMAX` setting defines the maximum size of a segment of shared memory. + *[ > ]: and then diff --git a/oracle_rbk_oracle_database_management.md b/oracle_rbk_oracle_database_management.md new file mode 100644 index 0000000000000000000000000000000000000000..661148ce5457d777bc1e79430445746ebd2642e6 --- /dev/null +++ b/oracle_rbk_oracle_database_management.md @@ -0,0 +1,51 @@ +# Oracle database management + +Source: https://docs.rubrik.com/en-us/saas/oracle/rbk_oracle_database_management.html + +--- + +# Oracle database management + +Manage discovered Oracle hosts and Oracle RAC systems from the Rubrik Oracle Databases page. + +To work with Oracle databases on the Rubrik cluster, click Inventory > Oracle Databases. + +If the .bashrc file contains or sources a file containing an interactive prompt, Rubrik jobs can also stop responding. The smallest unit to which an SLA Domain can be applied is the database. Tablespaces can be recovered but not individually protected. Oracle records transactions in redo logs before committing to the database. Redo logs are archived periodically, and backed up to enable point-in-time recovery. + +Connected instances are organized by Hosts or RAC, All Databases, and Data Guard Groups. Toggle the view by selecting either tab. The following describes the information available on each tab. + +Tab | Details +---|--- +Hosts or RAC | This page displays: + + * Name - Name of the single instance Oracle host or RAC + * Nodes - Number of nodes on the RAC + * Rubrik Cluster - Rubrik cluster to which the database belongs. + * Databases - Number of databases on the single instance Oracle host or RAC + * SLA Domain - Name of the assigned SLA Domain + * RBS Status - Connection status (connected, disconnected, partially connected) + + +All Databases | This page displays: + + * Name - Name of the database + * Host or RAC - Name of the cluster or host + * Data Guard Group - Name of the Data Guard group to which the database belongs + * Log Backup - Amount of time, in minutes, since the last log backup was captured + * Instances - Number of instances associated with the cluster or host + * Tablespaces - Number of tablespaces protected + * Rubrik Cluster - Rubrik cluster to which the database belongs + * SLA Domain - Name of the assigned SLA Domain + * Assignment - Indicates if the SLA Domain assignment is Direct or Inherited. + + +Data Guard Groups | This page displays: + + * Name - Name of the Data Guard group + * Rubrik Cluster - Rubrik cluster to which the Data Guard group belongs. + * Group Members - Number of databases in the Data Guard group + * Tablespaces - Number of tablespaces protected + * SLA Domain - Name of the assigned SLA Domain + * Assignment - Indicates if the SLA Domain is assigned. + + *[ > ]: and then diff --git a/oracle_rbk_restoring_tablespaces.md b/oracle_rbk_restoring_tablespaces.md new file mode 100644 index 0000000000000000000000000000000000000000..11eec0ae41882a091ec178e7aed329e84665814c --- /dev/null +++ b/oracle_rbk_restoring_tablespaces.md @@ -0,0 +1,70 @@ +# Restoring tablespaces + +Source: https://docs.rubrik.com/en-us/saas/oracle/rbk_restoring_tablespaces.html + +--- + +# Restoring tablespaces + +The Rubrik cluster restores tablespaces by exporting them in-place on the same database. + +## Before you begin + +Set the database to `ARCHIVELOG` mode before attempting a tablespace recovery. + +## About this task + +To initiate a tablespace recovery, select a snapshot or any point-in-time point target from the available range. The Rubrik cluster restores tablespaces in-place only to the same database. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Oracle Databases inventory card. + +The Oracle Databases page appears. + + 5. Click All Databases. + 6. In the Name column, click the name of a database. + +Alternatively, enter a name in the search field or use the filters in the left pane. + +The Local page for the database appears, with the Snapshots card showing the month view. + + 7. On the Snapshots card, select a day that has a green dot. + +The green dot indicates a successful snapshot taken on that day. + +The Snapshots card displays the Day view. + + 8. Select a snapshot from the timeline. + 9. Click View & Recover Tablespaces. + +The Tablespace Recovery dialog box appears. + + 10. Select the tablespace to restore. + +Alternatively, enter a name in the search field or use the filters at the top left of the list. + + 11. Click Next. + +The Confirmation page appears. + + 12. In Auxiliary Destination Path, enter the full path to a directory that Rubrik can use for storing data files for auxiliary instances. + 13. Click Recover. + +## Results + +The Rubrik cluster exports the tablespace and restores the tablespace to the selected point-in-time on the same database. + +## What to do next + +Take an on-demand snapshot to ensure immediate availability of changes for recovery operations. + *[ > ]: and then diff --git a/oracle_rbk_taking_an_on_demand_snapshot.md b/oracle_rbk_taking_an_on_demand_snapshot.md new file mode 100644 index 0000000000000000000000000000000000000000..973da638a20d8f9628b0e1dcd086fc5f92dae24d --- /dev/null +++ b/oracle_rbk_taking_an_on_demand_snapshot.md @@ -0,0 +1,59 @@ +# Taking an on-demand snapshot + +Source: https://docs.rubrik.com/en-us/saas/oracle/rbk_taking_an_on_demand_snapshot.html + +--- + +# Taking an on-demand snapshot + +Manually initiate a database snapshot in addition to the policy-based snapshots of the database. Assign an SLA Domain to manage that snapshot. + +## Before you begin + +Confirm the configuration is complete as defined in [Oracle database management](rbk_oracle_database_management.html "Manage discovered Oracle hosts and Oracle RAC systems from the Rubrik Oracle Databases page."). + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Oracle Databases inventory card. + +The Oracle Databases page appears. + + 5. Click All Databases. + 6. In the Name column, click the name of a database. + +Alternatively, enter a name in the search field or use the filters in the left pane. + +The Local page for the database appears, with the Snapshots card showing the month view. + + 7. Open the ellipsis menu and select Take Database Backup. + +The Take On Demand Snapshot dialog box appears. + + 8. Choose a retention period for the snapshot. + +Options| Description +---|--- ++ | Create an SLA Domain. +Assign an SLA Domain | Select one of the listed SLA Domains to assign to the host. Use the search field to find an SLA Domain that is not listed.The Rubrik cluster uses the rules and policies of the selected SLA Domain to manage the on-demand snapshot. The selected SLA Domain can be different from the SLA Domain that protects the database.The snapshots you initiate may not be recoverable on the replication target or at the archival location because the log snapshots are not uploaded along with the database snapshots. To upload log snapshots to the replication or archival location, assign an SLA Domain to the database that includes the same replication or archival policy as the SLA Domain for the initiated snapshots. +Forever | Retain the snapshot until it is manually deleted. + + 9. **Optional:** Click Take Full Database Backup. + 10. Click Next. + +The Confirmation page appears. + + 11. Click Confirm. + +## Results + +The Rubrik cluster adds the specified on-demand backup to the task queue. The Activity Log tracks the status of the on-demand backup task. The Rubrik cluster manages the snapshot based on the rules and policies of the selected SLA Domain. + *[ > ]: and then diff --git a/oracle_recovery_rac_standalone_oracle_hosts.md b/oracle_recovery_rac_standalone_oracle_hosts.md new file mode 100644 index 0000000000000000000000000000000000000000..233faf9dc0ba6b1d94394d7ced4089f2c062f720 --- /dev/null +++ b/oracle_recovery_rac_standalone_oracle_hosts.md @@ -0,0 +1,31 @@ +# Recovery from RAC to standalone Oracle hosts + +Source: https://docs.rubrik.com/en-us/saas/oracle/recovery_rac_standalone_oracle_hosts.html + +--- + +# Recovery from RAC to standalone Oracle hosts + +For RSC running Rubrik CDM version 9.2 or later, you can perform live mounts or clones of Oracle RAC snapshots to an Oracle standalone host. + +If RSC is running Rubrik CDM version 9.2 or later, you can perform a live mount or a clone recovery from Oracle RAC to a standalone host configured for Automatic Storage Management (ASM) or file system (FS). + +Performing a live mount or clone recovery requires that you include these ACO parameters during the live mount or clone: + + * SPFILE_LOCATION + * CONTROL_FILES + * DB_CREATE_FILE_DEST + * DB_RECOVERY_FILE_DEST or DB_CREATE_ONLINE_LOG_DEST_n + * ORACLE_HOME + +Note: + +You cannot include the `log_file_name_convert` ACO parameter with your live mount or clone recovery from an Oracle RAC to a standalone host. + +Recoveries from an Oracle RAC host to an Oracle standalone host has these restrictions: + + * You cannot perform a live mount or clone recovery from a standalone Oracle host to an Oracle RAC host. + * If you are performing a live mount or clone recovery to an ASM host, then all the paths provided in the ACO parameters must be ASM paths. + * If you are performing a live mount or a clone recovery to an Oracle host configured for FS, then all the paths provided in the ACO parameters must be FS paths. + + *[ > ]: and then diff --git a/oracle_role_based_access.md b/oracle_role_based_access.md new file mode 100644 index 0000000000000000000000000000000000000000..48bea3ac139cffe22984a9801fe0fddc7f9e7ae4 --- /dev/null +++ b/oracle_role_based_access.md @@ -0,0 +1,12 @@ +# Role based access + +Source: https://docs.rubrik.com/en-us/saas/oracle/role_based_access.html + +--- + +# Role based access + +Rubrik provides role-based access control, along with options for integrating with existing directory services. + +Role-based access control (RBAC) allows multiple tenants to access a restricted set of resources on a shared cluster. To set up a multi-tenant environment, start by creating a central organization that is managed by the `SYSADMIN` role. The central organization accesses resources on behalf of tenant organizations. The `SYSADMIN` role can create Org Admin roles for each organization, and assign specific privileges to each role. + *[ > ]: and then diff --git a/oracle_samehost_recover.md b/oracle_samehost_recover.md new file mode 100644 index 0000000000000000000000000000000000000000..bfb79b2ce80aa883ba228623a258f43bab3aa5fd --- /dev/null +++ b/oracle_samehost_recover.md @@ -0,0 +1,18 @@ +# Same Host Recovery + +Source: https://docs.rubrik.com/en-us/saas/oracle/samehost_recover.html + +--- + +# Same Host Recovery + +Recover a database to the source Oracle host or Oracle RAC. + +Important: + +Same host recovery fails on Oracle databases without an `spfile`. + +During a Same Host Recovery all existing archived logs are deleted and a new set of archived logs are generated for the new instance, unless the logs from the host are not applied. The feature supports options to point to a specific archived log path from which the archived logs are applied during the recovery. The original spfile of the source database is used during the recovery. Any additional parameters must be set after the restore job is completed. Before running a recovery, ensure that the parent directories of the required parameters exist on the Oracle host or each node of the Oracle RAC. This applies to both local file system paths and ASM paths. A Same Host Recovery does not change the location for redo logs but does consolidate the multiple members of redo log groups into a single member for each group. + +The Rubrik cluster supports automated recovery only for databases created using an SPFILE file. Databases created using a PFILE must use DBA managed recovery. + *[ > ]: and then diff --git a/oracle_tablespace_recovery.md b/oracle_tablespace_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..6c924389e71bee98adb4a7ada5defb257b5e5791 --- /dev/null +++ b/oracle_tablespace_recovery.md @@ -0,0 +1,35 @@ +# Tablespace recovery + +Source: https://docs.rubrik.com/en-us/saas/oracle/tablespace_recovery.html + +--- + +# Tablespace recovery + +Restore a tablespace in place to the same database. + +Recovery tasks use the tablespaces protected in the nearest database snapshot before the selected point-in-time. + +Adding single or multiple tablespaces to a databases involves changing multiple components in the database. Changes are written to the Rubrik cluster as scheduled by the assigned SLA Domain. However, Rubrik recommends taking an on-demand snapshot after dropping or adding a tablespace to ensure immediate availability of changes for recovery operations. + +Before restoring tablespaces, confirm the preliminary requirements listed in the following table. + +Component | Description +---|--- +Oracle Edition | Tablespace recovery requires an Oracle Database Enterprise Edition license with the RMAN TSPITR feature. +Permissions | A file system where the oracle user has the permission to create directories. +Auxiliary Destination Path | + + * Ensure that the device on which the auxiliaryDestination path is created has enough free disk space to store the control file, online redo logs, and the SYSTEM, SYSAUX, TEMP, and UNDO tablespaces for recovery operations on the target host, and also to accommodate the auxiliary database. The path must be an absolute file system path. It cannot be a relative path or a path in an ASM disk group. + * The tablespace export script creates an auxiliary destination directory. + +Information on how to export tablespaces can be found in [Restoring tablespaces](#tablespace_recovery "Restore a tablespace in place to the same database."). +Configuration | Set the Oracle database DB_CREATE_FILE_DEST parameter to the tablespace datafiles restoration location before the tablespace export is triggered. Provide the restoration location value as a string equal to the directory name or the disk group name. +Free storage space | The tablespace datafile recovery target device must meet the minimum storage space requirements: + + * AIX - The host must have free disk space equal to at least twice the size of the tablespace datafiles. + * Other Linux distributions - The host must have free disk space equal to the at least the size of the tablespace datafiles. + + +RMAN | Before starting a tablespace recovery, take the tablespace offline, then manually drop it. This ensures a clean and complete RMAN operation. + *[ > ]: and then diff --git a/ports_hotadd_proxy_port_requirements_4.md b/ports_hotadd_proxy_port_requirements_4.md new file mode 100644 index 0000000000000000000000000000000000000000..bc04ec07bbb60c1d7560997cf8c95ccd696cfc46 --- /dev/null +++ b/ports_hotadd_proxy_port_requirements_4.md @@ -0,0 +1,18 @@ +# HotAdd proxy port requirements + +Source: https://docs.rubrik.com/en-us/saas/ports/hotadd_proxy_port_requirements_4.html + +--- + +# HotAdd proxy port requirements + +A Rubrik Cloud Cluster requires access to several TCP ports in order to protect virtual machines in a cloud-based environment. + +Port | Location | Source | Destination | Purpose +---|---|---|---|--- +443 TCP | Management gateway | Rubrik cluster IPs or subnet, Rubrik HotAdd Proxy IPs or subnet | vCenter, ESXi host | vSphere discovery and command execution +902 TCP | Management gateway | Rubrik cluster IPs or subnet, Rubrik HotAdd Proxy IPs or subnet | ESXi | Virtual machine block location discovery +8077 TCP | Compute gateway | Rubrik cluster IPs or subnet | Rubrik HotAdd Proxy IPs or subnet | Diagnostics +12800-12801 TCP | Compute gateway | Rubrik cluster IPs or subnet | Workload virtual machines | Support for RBS (optional) +58000 TCP | Compute gateway | Rubrik cluster IPs or subnet | Rubrik HotAdd Proxy IPs or subnet | Proxy command and control + *[ > ]: and then diff --git a/ports_ports_comm_btwn_cluster_nodes.md b/ports_ports_comm_btwn_cluster_nodes.md new file mode 100644 index 0000000000000000000000000000000000000000..e74c8e59cec8a19fb1a120f95cb9520653d8e83c --- /dev/null +++ b/ports_ports_comm_btwn_cluster_nodes.md @@ -0,0 +1,36 @@ +# Communication between nodes in a cluster + +Source: https://docs.rubrik.com/en-us/saas/ports/ports_comm_btwn_cluster_nodes.html + +--- + +# Communication between nodes in a cluster + +Rubrik uses several ports for communication between nodes in a cluster. + +The following table list the nodes that communicate with the Rubrik cluster. Port/Protocol | Destination | Description +---|---|--- +22 TCP | Rubrik node | Validates and runs diagnostics on a Rubrik cluster. +123 UDP | Rubrik node | Facilitates time synchronization between Rubrik peer nodes. +443 TCP | Rubrik node | Provides information about other nodes. Used as an API server port for specific operations using API calls. +873 UDP | Rubrik cluster | Used during the upgrade process for rsync file synchronization. +1445 TCP | Local host | Handles SMB traffic between local services. +2013 TCP | Carbon-relay Line Receiver | Allows sharing of statistics between nodes of a Rubrik cluster. +2014 TCP | Carbon-relay Pickle Receiver | Allows sharing of statistics between nodes of a Rubrik cluster. +2015 TCP | Rubrik node | Restores metadata from backups. +2200 TCP | SSH | Enables node-to-node SSH communication during upgrade. +5353 UDP | Rubrik node | Allows zeroconf node discovery. +5766-5767 TCP | Rubrik internal database | Allows process arbitration for encrypted CockroachDB traffic between nodes of a Rubrik cluster. Port 26257 also handles this traffic. +7096 TCP | Rubrik cluster | Allows secure communication among Rubrik clusters and between nodes within a cluster. +7780 TCP | Rubrik node | Handles cluster configuration during cluster operations such as bootstrap and node add. +7781 TCP | Cluster Configuration | Permits the Rubrik cluster to load basic software and configuration information (bootstrap) during cluster configuration. +7784 TCP | Rubrik node | Allows TLS over TCP communication among nodes within a Rubrik cluster. +7790 TCP | Rubrik node | Handles metadata operations related to replication. +8081 TCP | Graphite | Enables node-to-node communication to the Graphite web server. +8082, 8086 TCP | Rubrik node | Enables communication with InfluxDB. +9368 TCP | Rubrik node | Allows node-to-node communication for the Rubrik data service to perform maintenance operations, for example, snapshot expiry or cleanup. +10000-10003 TCP | Rubrik node | Allows node-to-node SDFS internal communication. +10016 TCP | Rubrik node | HTTPS REST endpoint that manages Rubrik cluster upgrades. +10000-62000 UDP | Local host | Used by the syslog server configured by the user. The syslog server randomly chooses a port within the specified range. These local-node-only syslog ports are not assigned by Rubrik CDM. +26257 TCP | Rubrik internal database | Allows process arbitration for encrypted CockroachDB traffic between nodes of a Rubrik cluster. Ports 5766-5767 also handle this traffic. + *[ > ]: and then diff --git a/postgresql_adding_host_for_postgresql.md b/postgresql_adding_host_for_postgresql.md new file mode 100644 index 0000000000000000000000000000000000000000..514175bf09c062319e28113609e2a030419bdaa9 --- /dev/null +++ b/postgresql_adding_host_for_postgresql.md @@ -0,0 +1,49 @@ +# Adding a host for PostgreSQL + +Source: https://docs.rubrik.com/en-us/saas/postgresql/adding_host_for_postgresql.html + +--- + +# Adding a host for PostgreSQL + +To establish a connection between the PostgreSQL cluster and RSC, add a host for performing backup and recovery operations. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the PostgreSQL inventory card. + +The PostgreSQL page appears. + + 5. Click Manage Hosts. + +The Linux & Unix page appears. + + 6. Click Add Hosts. + +The Add Hosts dialog box appears. + + 7. Select a Rubrik cluster. + 8. Select an option for using RBS. + +Option| Description +---|--- +I have already installed and registered the RBS software | Provide the IP address or the hostname of the host and click Add. +I want to install and register the RBS software now | Select the platform and version for deploying RBS. + + 9. In Host IP addresses or FQDNs, enter the IP addresses or the names for the PostgreSQL host. + 10. Click Add. + +## Results + +RSC checks connectivity with the specified hosts and adds the host. + +## What to do next + +Add a PostgreSQL cluster as described in [Adding a PostgreSQL cluster](adding_postgresql_cluster.html "Add a PostgreSQL cluster to establish a connection with the Rubrik cluster with the required configuration details."). + *[ > ]: and then diff --git a/postgresql_adding_postgresql_cluster.md b/postgresql_adding_postgresql_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..f1fbaffee4a0a6c33923e40f97ea7ce7299c4b14 --- /dev/null +++ b/postgresql_adding_postgresql_cluster.md @@ -0,0 +1,48 @@ +# Adding a PostgreSQL cluster + +Source: https://docs.rubrik.com/en-us/saas/postgresql/adding_postgresql_cluster.html + +--- + +# Adding a PostgreSQL cluster + +Add a PostgreSQL cluster to establish a connection with the Rubrik cluster with the required configuration details. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the PostgreSQL inventory card. + +The PostgreSQL page appears. + + 5. Click Add PostgreSQL Cluster. + +The Add PostgreSQL Cluster wizard appears. + + 6. In PostgreSQL Cluster Name, enter the PostgreSQL cluster name. + 7. In Rubrik Cluster, select a Rubrik cluster from the dropdown menu. + 8. In IP Address or Hostname, select the IP address or hostname of the PostgreSQL cluster. + 9. In PostgreSQL Linux Username, enter the username of the account with access to the PostgreSQL cluster. + 10. Enter the port number. + +The default port is 5432. If the port changes, enter the correct port. + + 11. Click Add. + +RSC initiates a request to add a PostgreSQL cluster to the Rubrik cluster and automatically detects the PostgreSQL variant, such as Community PostgreSQL, EDB PostgreSQL Advanced Server, or EDB PostgreSQL Extended Server. + +## Results + +You have successfully added a PostgreSQL cluster. + +## What to do next + +You can view PostgreSQL variants on the PostgreSQL page and PostgreSQL cluster details page. For more information on PostgreSQL variants, see Rubrik Compatibility Matrix on the Rubrik Support Portal. + +You can track the task status on the Events page. + *[ > ]: and then diff --git a/postgresql_changing_retention_policy_postgresql.md b/postgresql_changing_retention_policy_postgresql.md new file mode 100644 index 0000000000000000000000000000000000000000..b4ab0f3cc8b34e96a13de9da4eb6ecba71789d5a --- /dev/null +++ b/postgresql_changing_retention_policy_postgresql.md @@ -0,0 +1,48 @@ +# Changing the retention policy of a PostgreSQL snapshot + +Source: https://docs.rubrik.com/en-us/saas/postgresql/changing_retention_policy_postgresql.html + +--- + +# Changing the retention policy of a PostgreSQL snapshot + +To optimize data accessibility, change the retention policy of a PostgreSQL snapshot. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the PostgreSQL inventory card. + +The PostgreSQL page appears. + + 5. Click a PostgreSQL cluster name. + +The PostgreSQL cluster details page appears. + + 6. Click Snapshots. + 7. Select a snapshot and click Change Retention. + +You can also select multiple snapshots. + + 8. Select a retention policy. + +Option| Description +---|--- +SLA Domain | Retains only a full snapshot at all locations for the maximum retention period specified by the selected SLA Domain. +Forever | Retains any snapshot type until you manually delete it. + + 9. Click Next. + +The confirmation page appears. + + 10. Review the information and click Assign. + +## Results + +RSC changes the retention policy for the selected PostgreSQL snapshots. + *[ > ]: and then diff --git a/postgresql_creating_restore_mp_postgresql.md b/postgresql_creating_restore_mp_postgresql.md new file mode 100644 index 0000000000000000000000000000000000000000..3ad6ccd5a8870092797338b1a280264717616854 --- /dev/null +++ b/postgresql_creating_restore_mp_postgresql.md @@ -0,0 +1,60 @@ +# Creating restore mount point for a PostgreSQL cluster + +Source: https://docs.rubrik.com/en-us/saas/postgresql/creating_restore_mp_postgresql.html + +--- + +# Creating restore mount point for a PostgreSQL cluster + +To recover a PostgreSQL cluster, create a restore mount point by mounting a snapshot of backup data to the mount point using NFS and then performing the recovery instructions. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the PostgreSQL inventory card. + +The PostgreSQL page appears. + + 5. Click a PostgreSQL cluster name. + +The PostgreSQL cluster details page appears. + + 6. Select a snapshot from the calendar view. + +A green dot indicates that at least one snapshot was created on that day. + +You can use the sliding time scale by clicking the snapshot icon, which displays a scheduled snapshot for performing a Fixed-Point-In-Time Recovery (FPITR). By clicking anywhere along the sliding time scale, you can initiate Any-Point-In-Time Recovery (APITR). + +The Snapshots card lists the snapshots taken on that day. A sliding scale displays the time when the snapshots were taken. + + 7. Hover over the snapshot and click Recover. + +The PostgreSQL Recovery wizard appears. + + 8. In Mount Settings, provide the mount point for recovery. + +The data backup is mounted to the mount point using NFS. + + 9. Click Next. + +A confirmation page in the PostgreSQL recovery wizard appears. + + 10. Click View Recovery Instructions to view the instructions to recover your PostgreSQL cluster. + +Performing the manual steps mentioned in the recovery instructions is required after you create the mount point. You can also download the instructions by clicking Download Instructions. + + 11. Review the selections and click Mount. + +## Results + +RSC creates an NFS mount with the corresponding data files in the restore mount point. The corresponding log files are exposed through secure thrift to the recovery host. + +## What to do next + +Recover the PostgreSQL cluster by following the manual recovery instructions as described in [Recovering a PostgreSQL cluster](recovering_postgresql_cluster.html "After you have created a mount point for the PostgreSQL cluster, recover the cluster manually by following the recovery instructions."). + *[ > ]: and then diff --git a/postgresql_deleting_postresql_cluster.md b/postgresql_deleting_postresql_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..9abe462b52b3c9ac27a093b2536b4b3dec39b3ca --- /dev/null +++ b/postgresql_deleting_postresql_cluster.md @@ -0,0 +1,32 @@ +# Deleting a PostreSQL cluster + +Source: https://docs.rubrik.com/en-us/saas/postgresql/deleting_postresql_cluster.html + +--- + +# Deleting a PostreSQL cluster + +To remove a PostgreSQL cluster that is no longer required, delete the PostgreSQL cluster from the Rubrik cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the PostgreSQL inventory card. + +The PostgreSQL page appears. + + 5. Click for a PostgreSQL cluster and select Delete PostgreSQL Cluster. + +A confirmation dialog box appears. + + 6. Click Delete. + +## Results + +RSC deletes the selected PostgreSQL cluster and all the relevant metadata from the Rubrik cluster. + *[ > ]: and then diff --git a/postgresql_editing_postrgesql_cluster.md b/postgresql_editing_postrgesql_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..9ea0415a3f6f87b62bbad738e7d86b10485679c8 --- /dev/null +++ b/postgresql_editing_postrgesql_cluster.md @@ -0,0 +1,34 @@ +# Editing a PostgreSQL cluster + +Source: https://docs.rubrik.com/en-us/saas/postgresql/editing_postrgesql_cluster.html + +--- + +# Editing a PostgreSQL cluster + +To modify a PostgreSQL cluster, edit the PostgreSQL cluster settings. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the PostgreSQL inventory card. + +The PostgreSQL page appears. + + 5. Click for a PostgreSQL cluster and select Edit PostgreSQL Cluster. + 6. Modify the PostgreSQL Cluster Name and PostgreSQL Linux Username. + 7. **Optional:** Turn on Advanced Configuration and enter the port number. + +The default port is 5432. If the port is changed, enter the correct port. Use this port for client-server communication, enabling clients to establish connections with the PostgreSQL server. + + 8. Click Save. + +## Results + +RSC initiates a request to refresh the PostgreSQL cluster and connects to the PostgreSQL cluster with the updated information. + *[ > ]: and then diff --git a/postgresql_ha_postgres_cluster.md b/postgresql_ha_postgres_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..61dc07001a6921c6a6851a946de643c07006da2c --- /dev/null +++ b/postgresql_ha_postgres_cluster.md @@ -0,0 +1,24 @@ +# High Availability for a PostgreSQL cluster + +Source: https://docs.rubrik.com/en-us/saas/postgresql/ha_postgres_cluster.html + +--- + +# High Availability for a PostgreSQL cluster + +High Availability for a PostgreSQL cluster ensures uninterrupted system operation and data protection against hardware and software failures, natural disasters, power outages, and network failures. + +High Availability (HA) for PostgreSQL clusters guarantees continuous system functionality and safeguards data integrity against hardware and software malfunctions. HA ensures PostgreSQL clusters remain functional and can quickly recover from interruptions. + +HA for PostgreSQL clusters is based on a master and standby PostgreSQL cluster setup. In the event of a failover, the HA setup automatically promotes the standby server to take over the master role. The PostgreSQL workload does not include built-in backup and recovery support for HA setups, so Rubrik recommends adding the master and standby PostgreSQL clusters to RSC as distinct workloads for backup and recovery procedures. + +When the master PostgreSQL cluster is active, the SLA Domain assigned to the master PostgreSQL workload continues to take backups while the standby PostgreSQL cluster remains quiescent. When a failover occurs, the standby PostgreSQL cluster becomes the new master PostgreSQL cluster, and the SLA Domain assigned to this new master cluster starts the backups. The previous master PostgreSQL cluster becomes inactive at this point. The master and standby PostgreSQL clusters, treated as separate PostgreSQL workloads, create their own backup chains. The previous master cluster retains backups taken prior to the failover, and the new master cluster starts a new backup chain after promotion. + +Adding an HA setup for backup and recovery of PostgreSQL clusters requires the following: + + * Adding the master and standby PostgreSQL clusters to RSC as separate workloads. + * Assigning SLA Domains to both master and standby PostgreSQL clusters. + +The SLA Domain assignment for the master cluster must match the specific SLA Domain requirements for that workload when the PostgreSQL cluster functions as the master cluster. This also means that the configuration of the SLA Domain assignment for the standby cluster must anticipate the performance when failover occurs and the standby cluster becomes the master cluster. + + *[ > ]: and then diff --git a/postgresql_postgresql.md b/postgresql_postgresql.md new file mode 100644 index 0000000000000000000000000000000000000000..388c55547e315aee7a1231ac0d709aef681a953b --- /dev/null +++ b/postgresql_postgresql.md @@ -0,0 +1,44 @@ +# PostgreSQL + +Source: https://docs.rubrik.com/en-us/saas/postgresql/postgresql.html + +--- + +# PostgreSQL + +Rubrik Security Cloud protects your PostgreSQL cluster by simplifying complex backup and recovery processes, discovering the databases automatically, and protecting data using SLA Domains. + +PostgreSQL is an object-relational database management system (ORDBMS) that seamlessly integrates relational database functionality with an object-oriented design. Using the object-oriented features provided by PostgreSQL, programmers can achieve: + + * Object-based interactions: Communicates with database servers using objects within their code, streamlining database interactions and enhancing code readability. + * Custom data types: Defines complex custom data types, enabling representation of sophisticated data structures that align with the specific needs of their applications. + +Note: + +Rubrik supports PostgreSQL version 12 or later, running on Linux on x86 architecture. + +## PostgreSQL cluster protection + +Rubrik Security Cloud (RSC) provides a unified solution for PostgreSQL clusters running on on-premises infrastructure and on AWS, Azure, and Google Cloud Platform (GCP) public clouds. + +You can protect your PostgreSQL clusters by performing the following actions in a sequence: + + * Ensuring the prerequisites are met + * Adding a host + * Adding a PostgreSQL cluster + * Managing protection by assigning SLA policy + * Performing different recovery operations + +## PostgreSQL cluster protection capabilities + +RSC provides the following capabilities while protecting PostgreSQL clusters: + + * Data backup and point-in-time recovery: Comprehensive options for both data backups and Write-ahead log (WAL) backups that ensure data integrity. + * File-level incremental backup: Efficient incremental backups at the file level to minimize storage and bandwidth usage. + * On-demand and SLA policy—based backup: Flexible backup options triggered on demand or scheduled based on custom SLA policies. + * Support for on-premises and cloud service providers: Unified solution for on-premises and public cloud (AWS, Azure, and GCP). + * Restore options: Recent State, Point-in-time, Current, or Different Host. + * Lower Recovery Point Objective (RPO): Reduced RPO to as low as 5 minutes, minimizing data loss in case of a failure. + * High availability support: Assured system availability and reduced downtime through high-availability support mechanisms. + * RSC features: Immutability, replication, archival, retention lock, single-node failure resiliency, and reporting. + diff --git a/postgresql_postgresql_automated_recovery.md b/postgresql_postgresql_automated_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..21dfc05d7cc5d97dc90436ca9e66c49c2fec5a90 --- /dev/null +++ b/postgresql_postgresql_automated_recovery.md @@ -0,0 +1,39 @@ +# PostgreSQL automated recovery + +Source: https://docs.rubrik.com/en-us/saas/postgresql/postgresql_automated_recovery.html + +--- + +# PostgreSQL automated recovery + +PostgreSQL automated recovery allows you to recover PostgreSQL clusters on RSC from Rubrik CDM versions 9.4.1 and later without requiring manual steps. + +PostgreSQL automated recovery is a simplified recovery process on RSC and does not require you to run manual scripts. When you perform an automated recovery, RSC stops the running PostgreSQL cluster and then deletes and overwrites the data and all tablespace directories at the target location. The PostgreSQL cluster restarts automatically once the system completes the recovery. + +With PostgreSQL automated recovery, you can perform both point-in-time recovery (PITR) and data-snapshot-only recovery. + +## Considerations for PostgreSQL automated recovery + +Before you initiate the recovery, you must consider the following points. + + * Software version compatibility: The PostgreSQL version on the target system must be equivalent to that of the source cluster. + * You cannot perform cross-version recovery. For example, recovering PostgreSQL version 13 to PostgreSQL version 16. + * You cannot perform cross-OS recovery. For example, recovering PostgreSQL version 13 cluster installed on RHEL to a PostgreSQL version 13 cluster installed on SLES. + * You cannot perform cross-variant recovery. For example, recovering Community PostgreSQL version 13 cluster to EDB PostgreSQL Advanced Server version 13 cluster. + * Configuration files: RSC does not overwrite the PostgreSQL configuration file. RSC copies the original PostgreSQL configuration file before recovery and restores it after the recovery process is finished. The timestamp on the configuration file changes, but the content remains the same. + +## Prerequisites and limitations + +Following are the prerequisites for PostgreSQL automated recovery: + + * You must run the PostgreSQL cluster on the specified host and port. You cannot use a cluster that is unavailable as a recovery target. + * For PITR, the PostgreSQL cluster installation must include `pg_waldump`. PostgreSQL provides `pg_waldump` as a native optional utility, and optional packages or modules such as `postgres-contrib` typically offer it. RSC uses this utility to retrieve commit timestamps from PostgreSQL WAL files, allowing for the determination of accurate recoverable ranges. + * When recovering a PostgreSQL cluster to an alternate cluster, you must map the PostgreSQL clusters to the same Rubrik CDM cluster. + +Following are the limitation for PostgreSQL automated recovery: + + * You must run the PostgreSQL cluster as a `systemctl` service on the host to allow the automated job to stop and start the PostgreSQL service. Alternatively, if the host does not support `systemctl`, you can contact Rubrik Support to stop and start the PostgreSQL service using custom scripts. + * You cannot perform PITR to a time with no transaction commits after it. If the cluster is inactive, the time of the last commit is the latest possible PITR time. However, data snapshot-only recovery works even for inactive clusters. + * High Availability (HA) configuration: RSC does not guarantee that the HA configuration will be retained after recovery in a PostgreSQL HA setup. You must manually establish the HA setup after the recovery completes. + + *[ > ]: and then diff --git a/postgresql_postgresql_cluster_protection.md b/postgresql_postgresql_cluster_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..180b41d477840655980e0e716f6cff9b355da241 --- /dev/null +++ b/postgresql_postgresql_cluster_protection.md @@ -0,0 +1,31 @@ +# PostgreSQL cluster protection + +Source: https://docs.rubrik.com/en-us/saas/postgresql/postgresql_cluster_protection.html + +--- + +# PostgreSQL cluster protection + +PostgreSQL cluster protection uses SLA Domains to provide configurable data protection policies, ensuring consistent and secure management of PostgreSQL cluster workloads. + +PostgreSQL cluster protection through SLA Domains consolidates data protection policies, providing a unified approach for PostgreSQL cluster workloads. SLA Domains offer a configurable set of policies, which includes: + + * Frequency + * Retention + * Archival + * Replication + * Retention lock + * PostgreSQL cluster specific settings + +This helps you to provide the retention period for the backed up log files. You can apply these SLA Domain policies to PostgreSQL cluster objects to achieve your data protection objectives. + +By assigning an SLA Domain to your PostgreSQL cluster, you ensure that protection policies are applied consistently across your environment. + +## Snapshot management + +RSC provides support for on-demand snapshots and policy-based snapshots. The SLA Domain policies and rules assigned to a PostgreSQL cluster create policy-based snapshots. Policy-based snapshots can be either scheduled snapshots or continuous snapshots. + +Note: + +The backup and restore operations for a PostgreSQL workload happen only at the PostgreSQL cluster level and not at the database level. + *[ > ]: and then diff --git a/postgresql_postgresql_protection_key_features.md b/postgresql_postgresql_protection_key_features.md new file mode 100644 index 0000000000000000000000000000000000000000..6b9c43ce31bc6899554d381af9c3e550b56dee49 --- /dev/null +++ b/postgresql_postgresql_protection_key_features.md @@ -0,0 +1,69 @@ +# PostgreSQL protection key features + +Source: https://docs.rubrik.com/en-us/saas/postgresql/postgresql_protection_key_features.html + +--- + +# PostgreSQL protection key features + +RSC provides unified data management, automated global data protection, backup and recovery options for PostgreSQL databases, and advanced security features to protect critical data. + +The RSC features for PostgreSQL clusters offer comprehensive capabilities for protection and management. + +## Unified data management + +The following table provides details about the unified data management features for PostgreSQL. Feature | Supported CDM versions | Description +---|---|--- +RSC data protection | 9.2.1 or later | Provides a SaaS platform to manage and protect PostgreSQL databases across various deployment environments, such as cloud or on-premises. +Consolidated monitoring and reporting | 9.2.1 or later | Offers unified reporting to track SLA Domain assignments, protection and recovery activities, and SLA Domain policy compliance for the PostgreSQL workloads. +Comprehensive dashboard | 9.2.1 or later | Manages the PostgreSQL clusters, backups, and recovery operations from a unified interface within RSC, streamlining administrative tasks and reducing complexity. +Cloud Cluster Elastic Storage (CCES) Support | 9.2.1 or later | Extends data protection capabilities for PostgreSQL clusters deployed on cloud environments, such as AWS and Azure. + +## Automated global data protection through SLA Domains + +The following table details the automated global data protection features for PostgreSQL. Feature | Supported CDM versions | Description +---|---|--- +Protection policies | 9.2.1 or later | Assigns and manages the SLA Domain protection policies for PostgreSQL clusters to ensure that backup and recovery operations meet defined business needs, Recovery Time Objectives (RTO), or Recovery Point Objectives (RPO) requirements. +Automated backups | 9.2.1 or later | Uses SLA Domains to automate backups of PostgreSQL clusters, setting schedules to protect the PostgreSQL data without manual intervention. + +## Backup and recovery + +The following table details the backup and recovery features of PostgreSQL. Feature | Supported CDM versions | Description +---|---|--- +On-demand backups | 9.2.1 or later | Supports taking backups of PostgreSQL clusters as needed, outside of predefined schedules. +Cluster-level backup | 9.2.1 or later | Supports taking comprehensive backups at the PostgreSQL cluster level, capturing all databases and associated data within that cluster. +Archival | 9.2.1 or later | Enables long-term retention of PostgreSQL snapshots by tiering them to lower-cost archival storage, such as cloud object storage, for compliance and cost efficiency. +Snapshot replication | 9.2.1 or later | Facilitates the replication of PostgreSQL backup snapshots to other Rubrik clusters for disaster recovery, ensuring offsite data availability. +Retention lock | 9.4.0 or later | Provides compliance and legal requirement mechanisms to enforce immutable retention periods for backups, preventing unauthorized deletion or modification of data. You can configure retention lock while configuring SLA Domain; however, you cannot reduce the retention period in a retention-locked SLA Domain, which can lead to premature snapshot deletion. +RSC-based automated recovery | 9.4.1 or later | Provides a simple RSC workflow to restore snapshots and logs, based on requirements.Note: RSC supports manual recovery of PostgreSQL clusters prior to CDM version 9.4.1. +High Availability (HA) | 9.2.1 or later | Supports protection of PostgreSQL clusters configured with a master and standby HA setup, ensuring backup continuity upon failover. Considerations include: + + * The PostgreSQL HA master and standby clusters must be two separate workloads in RSC. + * Master and standby clusters each require separate SLA Domains. + * The master and standby clusters maintain independent backup chains. + * Backups are performed actively on the current master cluster. The standby cluster remains inactive for backups until a failover occurs. + +For more information, see HA for a PostgreSQL cluster. + +## Security and access control + +The following table outlines the security and access control features for PostgreSQL. Feature | Supported CDM versions | Description +---|---|--- +Role-based Access Control (RBAC) | 9.2.1 or later | Offers granular permissions to administrators to manage data protection operations for PostgreSQL workloads, ensuring security and compliance with organization access policies. +Quorum Authorization | 9.2.1 or later | Enforces authorized approvals to modify data protection decisions, such as policy changes and deletion requests, to prevent unauthorized actions and protect data integrity. +Secure connectivity | 9.2.1 or later | Establishes secure communication channels for data transfer and management operations between PostgreSQL clusters and RSC.The methods for secure communication and data transfer between PostgreSQL clusters and RSC are as follows: + + * Using either socket-based or TCP-based authentication for management and control operations, and configuring SSL for secure connectivity. + * Transferring backup data using NFS. + * Transferring Write-ahead log (WAL) files over secure thrift. + * Restoring data over NFS. + * Restoring logs using the secure thrift protocol. + + + +## Networking + +This feature addresses compatibility requirements within segmented network environments, specifically for data restoration. Feature | Supported CDM versions | Description +---|---|--- +VLAN support | 9.3.3, 9.4.1 or later | Enables VLAN-compatible IP addresses for NFS mounts during restore operations. This enables data restoration over the NFS layer within a secure, VLAN-segmented network. + *[ > ]: and then diff --git a/postgresql_postgresql_protection_limitations.md b/postgresql_postgresql_protection_limitations.md new file mode 100644 index 0000000000000000000000000000000000000000..2edecfc0277d87cf8fab909a179fdb3e35e50d38 --- /dev/null +++ b/postgresql_postgresql_protection_limitations.md @@ -0,0 +1,23 @@ +# PostgreSQL protection limitations + +Source: https://docs.rubrik.com/en-us/saas/postgresql/postgresql_protection_limitations.html + +--- + +# PostgreSQL protection limitations + +PostgreSQL clusters are subject to certain protection limitations. + +The following table provides details on the limitations for protecting PostgreSQL clusters with RSC . Limitation | Description +---|--- +Platform support | Supports only the Linux platform. Does not support the Windows platform. The Rubrik Compatibility Matrix provides more information about the supported Linux operating systems. +Backup type | Supports only file-level backups. Does not support block-level incremental backups. +Discovery | Automatically discovers only PostgreSQL databases. Does not discover PostgreSQL clusters. +Backup or restore scope | Offers backup and restore operations only at the PostgreSQL cluster level, not at the database level. +Recovery features | Does not support live mounts. +Recovery workflow automation | Requires manual steps to start and stop the database; the recovery workflow is not fully automated.For CDM version 9.4.1 and later, automated recovery based on RSC automates the workflow, including stopping and starting the PostgreSQL cluster service on the host. +High Availability (HA) | Requires manual intervention; the HA workflow is not fully automated. +Scalability | Does not support multinode ingestion. Backup ingestion is limited to a single node. +Data governance | Does not support legal hold, retention lock, or multiple archival locations (MAL). +Replication | Does not support downloading replicated snapshots from the target location. + *[ > ]: and then diff --git a/postgresql_postgresql_protection_prereq.md b/postgresql_postgresql_protection_prereq.md new file mode 100644 index 0000000000000000000000000000000000000000..c04c20d7072be9a1c3f24b31528031f065dd71fc --- /dev/null +++ b/postgresql_postgresql_protection_prereq.md @@ -0,0 +1,33 @@ +# PostgreSQL protection prerequisites + +Source: https://docs.rubrik.com/en-us/saas/postgresql/postgresql_protection_prereq.html + +--- + +# PostgreSQL protection prerequisites + +Information about the specific prerequisites that RSC requires for protecting PostgreSQL clusters. + +The following table describes the requirements for protecting PostgreSQL clusters. Component | Prerequisites +---|--- +Rubrik CDM | + + * Rubrik CDM version 9.2.1 or later for Community PostgreSQL. + * Rubrik CDM version 9.2.3 or later for EDB PostgreSQL Advanced Server (EPAS). + * Rubrik CDM version 9.3.1 or later for EDB PostgreSQL Extended Server (PGE). + + +Ports | + + * Ports 12800 and 12801: For communication between Rubrik CDM and Rubrik Backup Service. + * Ports 111 and 32764 to 32769: For data backup through NFS connection. + * Port 9639: For Write-Ahead Log (WAL) archiving or log backup. + * Port 5432: For establishing connection with the PostgreSQL server.Note: This is the default port. If the port is changed, you must use the correct port to establish a connection with the PostgreSQL server. + + +Operating system on host | Linux is the only supported operating system.The Rubrik Compatibility Matrix guide provides information about the supported Linux OS versions.For PostgreSQL clusters running on RHEL, the PostgreSQL user requires access permission when SELinux is enabled. Using the `sudo semanage permissive -a postgresql_t` command provides the access to the PostgreSQL user. +PostgreSQL version | Community PostgreSQL or EDB PostgreSQL Advanced Server (EPAS) or EDB PostgreSQL Extended Server (PGE).The Rubrik Compatibility Matrix guide provides information about the supported PostgreSQL versions. +PostgreSQL Archive mode | You must turn on the archive mode.Setting the `wal_level` configuration parameter to replica or higher performs WAL archiving. +PostgreSQL user permission | The PostgreSQL user requires Superuser privileges to perform data backup and WAL backup.Rubrik connects to the PostgreSQL cluster using peer authentication. +NFS client | Rubrik recommends installing the latest version of the NFS client on the host because the NFS protocol is used for data backup. + *[ > ]: and then diff --git a/postgresql_recovering_postgresql_cluster.md b/postgresql_recovering_postgresql_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..f1c8ecda7e21b89437ebe7a2d0da9b941738bddd --- /dev/null +++ b/postgresql_recovering_postgresql_cluster.md @@ -0,0 +1,129 @@ +# Recovering a PostgreSQL cluster + +Source: https://docs.rubrik.com/en-us/saas/postgresql/recovering_postgresql_cluster.html + +--- + +# Recovering a PostgreSQL cluster + +After you have created a mount point for the PostgreSQL cluster, recover the cluster manually by following the recovery instructions. + +## Before you begin + +Make sure that you have created a NFS restore mount point as described in [Creating restore mount point for a PostgreSQL cluster](creating_restore_mp_postgresql.html "To recover a PostgreSQL cluster, create a restore mount point by mounting a snapshot of backup data to the mount point using NFS and then performing the recovery instructions."). + +## Procedure + + 1. Stop the services on the PostgreSQL server that you want to restore. + +Running the stop service command requires that you be the root user. + +Following is an example command: + + systemctl stop postgresql@16-main.service + + 2. Copy the existing PostgreSQL cluster data directory to a safe location. + +Run the copy command as a PostgreSQL user. This safety measure makes sure that a current operating copy is retained and can be used to restore the data in the event of restore failure. + +Following is an example command: + + cp -rv /var/lib/postgresql/16/main /tmp/backup_main + + 3. Delete the content of the existing data directory. + +Run the delete command as a PostgreSQL user. + +Following is an example command: + + rm -rv /var/lib/postgresql/16/main + + 4. Copy the contents of the base_backup folder present in the restore mount point to the PostgreSQL cluster data directory. + +Following is an example command: + + cp -rv /mnt/rubrik/postgres/restore_snapshot_test/base_backup /var/lib/postgresql/16/main + + 5. Copy the contents of the pg_wal folder present in the restore mount point to the PostgreSQL cluster pg_wal directory. + +Following is an example command: + + cp -rv /mnt/rubrik/postgres/restore_snapshot_test/pg_wal /var/lib/postgresql/16/main + + 6. Set the restore command in the PostgreSQL .conf file for snapshot recovery. + +Following is an example command : + + restore_command = ‘cp /mnt/rubrik/postgres/restore_new_vm/pg_wal/%f %p' + +Note: + +When the restore command is not set, recovery fails and displays an error FATAL: must specify restore_command when standby mode is not enabled.. + + 7. Set the restore command and recovery target time in the PostgreSQL .conf file for point-in-time recovery. + +Following is an example command : + + recovery_target_time = 'recovery time in UTC' + + restore_command = 'sg rubrik_group -c "/etc/rubrik/scripts/postgres/log_data_recovery.sh livemount:/%f %p "' + +You can obtain the exact command to use from the View Recovery Instructions section in the PostgreSQL recovery wizard. + + 8. Set the ownership of all the copied files in the data directory to PostgreSQL. + +Following is an example command: + + chown -rv postgres:postgres /var/lib/postgresql/16/main + + 9. Set the file permissions of all the files in the data directory to 700. + +Following is an example command: + + chmod -rv 0700 /var/lib/postgresql/16/main + + 10. Check and remove the tablespace_map if it is empty. + +The recovery fails if the file is empty. Following is an example command: + + cat /var/lib/postgresql/16/main/tablespace_map + { + } + rm /var/lib/postgresql/16/main/tablespace_map + + 11. Create a recovery.signal file inside the main data directory for PostgreSQL version 12 and later. + +Following is an example command: + + touch /var/lib/postgresql/16/main/recovery.signal + +When PostgreSQL cluster discovers the recovery.signal file during startup, the cluster launches a special recovery mode and disables all client connections. + + 12. Start the PostgreSQL server. + +Following is an example command: + + systemctl start postgresql@16-main.service + + 13. Monitor the PostgreSQL application logs to view data recovery process from the archives. + +Following is an example command: + + tail /var/log/postgresql/postgresql-16-main.log + +The logs display that the database system is ready to accept connections. + +## Results + +You have recovered the PostgreSQL cluster using the NFS mount point. + +## What to do next + +After recovery is complete, verify the recovered tables and data in the recovered PostgreSQL cluster. + +Note: + +After you complete point-in-time recovery, the databases is in read-only mode. To enable read/write mode, run the following command in the PostgreSQL session. + +`select pg_wal_replay_resume();` + *[ > ]: and then diff --git a/postgresql_refreshing_postgresql_cluster.md b/postgresql_refreshing_postgresql_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..c34da1420492b230e2d0ada9ba8e58f669461bed --- /dev/null +++ b/postgresql_refreshing_postgresql_cluster.md @@ -0,0 +1,28 @@ +# Refreshing a PostgreSQL cluster + +Source: https://docs.rubrik.com/en-us/saas/postgresql/refreshing_postgresql_cluster.html + +--- + +# Refreshing a PostgreSQL cluster + +To ensure that the PostgreSQL cluster information is up to date, refresh the PostgreSQL cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the PostgreSQL inventory card. + +The PostgreSQL page appears. + + 5. Click for a PostgreSQL cluster and select Refresh. + +## Results + +RSC refreshes the PostgreSQL cluster information and also discovers all the databases of the PostgreSQL cluster and updates the relevant metadata. + *[ > ]: and then diff --git a/postgresql_unmouting_restore_mount_point_postgresql_cluster.md b/postgresql_unmouting_restore_mount_point_postgresql_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..aa02c40f11ee6e6494a72141bc5fd09d0c0806f8 --- /dev/null +++ b/postgresql_unmouting_restore_mount_point_postgresql_cluster.md @@ -0,0 +1,32 @@ +# Unmounting restore mount point after PostgreSQL cluster recovery + +Source: https://docs.rubrik.com/en-us/saas/postgresql/unmouting_restore_mount_point_postgresql_cluster.html + +--- + +# Unmounting restore mount point after PostgreSQL cluster recovery + +After recovering a PostgreSQL cluster, unmount it to remove the metadata associated with the selected PostgreSQL cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Live Mounts. + +The Live Mounts page appears. + + 4. Click PostgreSQL Database Cluster. + +A list of the mounted PostgreSQL Clusters appears. + + 5. Hover over a PostgreSQL cluster and click Unmount. + +A confirmation dialog box appears. + + 6. Click Unmount. + +## Results + +RSC unmounts the PostgreSQL cluster restore mount point and removes the metadata associated with the selected PostgreSQL cluster. + *[ > ]: and then diff --git a/qauth_quorum_authorization.md b/qauth_quorum_authorization.md new file mode 100644 index 0000000000000000000000000000000000000000..dc2abefb50802fb24d0c8456d66098d026ca34f4 --- /dev/null +++ b/qauth_quorum_authorization.md @@ -0,0 +1,26 @@ +# Quorum authorization + +Source: https://docs.rubrik.com/en-us/saas/qauth/quorum_authorization.html + +--- + +# Quorum authorization + +Quorum authorization is a security feature that enforces the requirement of getting additional approvals before a requester can perform data-modifying actions in RSC. + +Quorum authorization ensures that no single user has the authority to perform important actions on critical data secured by RSC. With quorum authorization enabled, a user requires additional approvals to perform data-modifying actions. + +Note: + +RSC supports quorum authorization for data protected by Rubrik clusters running Rubrik CDM version 9.0.1 or later. + +When quorum authorization is enabled, a global RSC administrator creates quorum authorization policies to specify the actions that require additional approval. + +Quorum authorization applies to actions that are related to the following aspects: + + * Data management at the workload level, Rubrik cluster level, and SLA Domain level + * System configuration at the Rubrik cluster level + * Global configuration at RSC level + * Management of quorum authorization policies and roles + + *[ > ]: and then diff --git a/rbs_oracle_rbs.md b/rbs_oracle_rbs.md new file mode 100644 index 0000000000000000000000000000000000000000..2622d75be5fab35da451984c378307a6340e1db0 --- /dev/null +++ b/rbs_oracle_rbs.md @@ -0,0 +1,18 @@ +# Rubrik Backup Service + +Source: https://docs.rubrik.com/en-us/saas/rbs/oracle_rbs.html + +--- + +# Rubrik Backup Service + +Rubrik Backup Service is required in order to perform automated discovery of Oracle hosts, Oracle RAC systems, and Oracle databases. + +Install Rubrik Backup Service (RBS) on an Oracle host, and add that host to the Rubrik cluster, to start automatic discovery of the following resources on the Oracle host: + + * Oracle databases + * Oracle database metadata + * List of long running Oracle database instances and tablespaces + +RBS software can only be used with the Rubrik cluster from which the software is obtained. Each Rubrik cluster generates a copy of the RBS software that includes authentication information specific to that Rubrik cluster. This method ensures that the Rubrik cluster and a hosted deployment of the RBS can successfully authenticate. + *[ > ]: and then diff --git a/rbs_rbs_installing_windows.md b/rbs_rbs_installing_windows.md new file mode 100644 index 0000000000000000000000000000000000000000..22f2b2d1b89a1f6be057e0692d90a880a33ebcea --- /dev/null +++ b/rbs_rbs_installing_windows.md @@ -0,0 +1,39 @@ +# Installing RBS on Windows + +Source: https://docs.rubrik.com/en-us/saas/rbs/rbs_installing_windows.html + +--- + +# Installing RBS on Windows + +Install the Rubrik Backup Service software on a computer or virtual machine that is running the Windows Server operating system. + +## Before you begin + + * Copy the zip file containing the most up-to-date version of the Rubrik Backup Service (RBS) software to a temporary location that the Windows Server operating system can access. + * For CDM version 9.3 and later, ensure that the RBS directories are not present on the host before starting the installation. + +## Procedure + + 1. Log in to the Windows operating system. + +Use an account that has local Administrator group privileges. + + 2. Extract the contents of the ZIP file containing the RBS software to a temporary location. + +The ZIP file contains the Windows installer package, RubrikBackupService.msi and the security certificate that is used for authentication and encryption of all communication with the Rubrik cluster, backup-agent.crt. + +The Windows installer package and the security certificate must be in the same folder on the Windows Server host during installation of the software. + + 3. Double-click RubrikBackupService.msi and follow the on-screen instructions. + +## Results + +The Windows installer package installs the RBS software. + +The installation process creates an Agent UUID for the Rubrik Backup Service. The Agent UUID uniquely identifies the host as the owner of backups and links it to a snapshot chain once backups are initiated. + +## What to do next + +Add hosts that have RBS to the Rubrik cluster. + *[ > ]: and then diff --git a/rbs_rbs_sap_hana.md b/rbs_rbs_sap_hana.md new file mode 100644 index 0000000000000000000000000000000000000000..4f09dfa1d4594b6327158c7157523d1807fd67e4 --- /dev/null +++ b/rbs_rbs_sap_hana.md @@ -0,0 +1,23 @@ +# Rubrik Backup Service for SAP HANA + +Source: https://docs.rubrik.com/en-us/saas/rbs/rbs_sap_hana.html + +--- + +# Rubrik Backup Service for SAP HANA + +Install and configure the Rubrik Backup Service on a SAP HANA host to allow backup and restore of SAP HANA databases. + +Follow the Linux rpm instructions when downloading the rubrik-agent.x86_64.rpm binary and installing the Rubrik Backup Service (RBS) software. + +rubrik-agent.x86_64.rpm creates transition locks in /var/lib/rpm. Make sure the permissions are set correctly in this directory to create these locks. + +Installing RBS copies the following executable files to /usr/bin/rubrik/sap_hana: + + * sap_hana_agent_main – The SAP HANA backint binary that performs backup and restore operations using third party tools. + * sap_hana_bootstrap_main – The RBS setup script that configures backint for Rubrik CDM. + +Important: + +Before the RBS software is upgraded, pause any SAP HANA backups. RBS software upgrade can occur automatically whenever the Rubrik CDM software is upgraded on the associated Rubrik cluster. + *[ > ]: and then diff --git a/replication_creating_cross_acct_connection.md b/replication_creating_cross_acct_connection.md new file mode 100644 index 0000000000000000000000000000000000000000..cb73d080dd8b76c0afdd2487a45479281b5e122e --- /dev/null +++ b/replication_creating_cross_acct_connection.md @@ -0,0 +1,59 @@ +# Creating a cross-account connection + +Source: https://docs.rubrik.com/en-us/saas/replication/creating_cross_acct_connection.html + +--- + +# Creating a cross-account connection + +To facilitate the synchronization of Rubrik cluster metadata, create a cross-account connection between two accounts. The metadata synchronization is required for cross-account replication between the RSC account of the service consumer and the tenant organization in the RSC account of the service provider. + +## Before you begin + +In the RSC account of the service provider, create or edit a tenant organization to enable cross-account replication, as described in [Creating a tenant organization for cross-account replication](creating_tenant_org_for_cross_acct_replication.html "In the RSC account of the service provider, create a tenant organization for cross-account replication by allocating Rubrik clusters to be used as replication targets and assigning the tenant organization administrator role to at least one user from the RSC account of the service consumer."). + +When accounts involved in a cross-account pairing exist in different deployments and IP allowlisting is enabled for one of the accounts, you must add the IP addresses from the other deployment to the allowlist. Adding these IP addresses allows RSC to allowlist them and establish a secure connection to fetch required information for cross-account operations. + +The [Finding the RSC domain region](../saas/finding_rsc_region.html "Find the region in which your RSC domain is running.") and [Finding the RSC IP address](../saas/finding_ip_address.html "Locate the IP address of your RSC domain for various use cases.") topics provide more information on finding the deployment information and IPs. + +## About this task + + * Only a tenant organization administrator with permissions to create, view, and manage cross-account replication pairing in the RSC account of the service consumer can create a cross-account connection with the tenant organization of the service provider. + * During the metadata synchronization, you can retrieve only the metadata of the Rubrik clusters with the `useAsReplicationTarget` permission. + * After a cross-account connection is established with a tenant organization within a provider account, Rubrik does not support migrating the cross-account connection to a different tenant organization within same provider account. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Organizations and select Cross-Account Connections. + 4. Click Connect Organization. + +The Connect Organization dialog box appears. + + 5. In Organization FQDN, enter the FQDN of the tenant organization that you created in the RSC account of the service provider. + 6. Click Log In. + +RSC redirects you to the Welcome page of the tenant organization. + + 7. Log in to the tenant organization using the credentials of the tenant organization administrator. + +When the authentication succeeds, the Confirm Connection dialog box appears. + + 8. Click Connect. + +The tenant organization authorizes the connection request from the RSC account of the service consumer and redirects you back to the UI on the service consumer account, which displays the success message. + + 9. Click Go To Overview. + +## Results + +The Cross-account Connections page displays the URL of the newly connected tenant organization and metadata synchronization begins between the two RSC accounts. The synchronization completes after a few minutes, and the RSC account of the service consumer receives a notification in the Inbox on the web UI. Messages are also logged on the Events page. + +## What to do next + +Create a cross-account replication pairing as described in [Creating replication pairings using private network](creating_rep_pairings_pvt_ntwrk.html "Create replication pairings between source and target Rubrik clusters using a private network to ensure secure and efficient replication between clusters.") and [Creating replication pairings using NAT](creating_replication_pairings_nat.html "Create replication pairings between source and target Rubrik clusters using Network Address Translation to enable data replication and facilitate monitoring and auditing of replication activities."). + *[ > ]: and then diff --git a/replication_cross_account_replication.md b/replication_cross_account_replication.md new file mode 100644 index 0000000000000000000000000000000000000000..efd723780f5e2d6ebb034ee4343d031aa45dc9e9 --- /dev/null +++ b/replication_cross_account_replication.md @@ -0,0 +1,27 @@ +# Cross-account replication + +Source: https://docs.rubrik.com/en-us/saas/replication/cross_account_replication.html + +--- + +# Cross-account replication + +Cross-account replication is a disaster-recovery feature that you can use to create a replication pairing between Rubrik clusters that are connected to different RSC accounts. + +Cross-account replication is a mechanism that provides disaster recovery as a service (DRaaS). Using cross-account replication, you can replicate data from a Rubrik cluster in your RSC account to a Rubrik cluster in an RSC account that you do not own. + +The most common use case for cross-account replication involves a managed service provider (MSP) and a service consumer, where both entities are also Rubrik customers. If you are an MSP, you can use cross-account replication to provide DRaaS to your consumers. As a consumer of services provided by an MSP, you can use cross-account replication to replicate data from a source Rubrik cluster in your RSC account to a target Rubrik cluster in the RSC account of the service provider. + +To enable cross-account replication, an administrator in the RSC account of the service provider creates a tenant organization with the following configuration: + + * At least one Rubrik cluster that is assigned replication privileges to serve as the replication target cluster. + * At least one user from the RSC account of the service consumer who is invited to access the replication target cluster. + +After configuring the tenant organization in the RSC account of the service provider, for cross-account replication to begin, the following tasks are required in the RSC account of the service consumer: + + * Creating a cross-account connection to synchronize Rubrik cluster metadata between the RSC account of the service consumer and the tenant organization created in the RSC account of the service provider. + * Creating a replication pair to associate the replication source and target Rubrik clusters. + * Configuring an SLA Domain with a replication policy that uses the cross-account replication pair. + * Assigning the SLA Domain configured with the cross-account replication policy to workloads. + + *[ > ]: and then diff --git a/replication_replication.md b/replication_replication.md new file mode 100644 index 0000000000000000000000000000000000000000..3223c57725c23bc0df551cc8b45c4310fef80fe4 --- /dev/null +++ b/replication_replication.md @@ -0,0 +1,24 @@ +# Replication + +Source: https://docs.rubrik.com/en-us/saas/replication/replication.html + +--- + +# Replication + +The replication feature directs the Rubrik cluster to send replicas of source snapshots or backups to a target Rubrik cluster and defines the maximum time to keep the replica on each cluster. + +When a replication policy is enabled for a local SLA Domain, the remote Rubrik cluster (target Rubrik cluster) rapidly copies the snapshot and backup data for that SLA Domain from the local Rubrik cluster (source Rubrik cluster). + +A source Rubrik cluster and a target Rubrik cluster use the Transport Layer Security (TLS) protocol to encrypt all replication data in-flight. + +A Rubrik cluster can have multiple target Rubrik clusters. Each SLA Domain on the source can direct replication to the target that best accomplishes business goals. + +A Rubrik cluster can be the target for many source Rubrik clusters. + +When issues interfere with the network connection between the source Rubrik cluster and a target Rubrik cluster, the replication task is retried. The Rubrik cluster retries the task a number of times, depending on the tasks configured. + +Important: + +When constraints, such as limited bandwidth, interfere with the completion of all of the replication tasks that are specified for an SLA Domain, the Rubrik cluster may skip replication of older snapshots and backups to ensure that the newest data is successfully replicated. In this scenario the SLA does not govern the retention policy. Older snapshots that are outside of the local retention policy are deleted. + *[ > ]: and then diff --git a/reuse_comments_suggestions.md b/reuse_comments_suggestions.md new file mode 100644 index 0000000000000000000000000000000000000000..dfac7db80617d4eaf0a0b87d181191c7103e2cbb --- /dev/null +++ b/reuse_comments_suggestions.md @@ -0,0 +1,33 @@ +# Comments and suggestions + +Source: https://docs.rubrik.com/en-us/saas/reuse/comments_suggestions.html + +--- + +# 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](support.html "Use one of the following methods to contact Rubrik Support."). + +## Product documentation + +To provide comments and suggestions about the product documentation, send an email to: [techpubs@rubrik.com](mailto:techpubs@rubrik.com). + +To help our writers identify the area that you are referencing, include the following requested information. + +For HTML documentation, include: + + * Page title + * Page address + * Page date + +For PDF documentation, include: + + * PDF title + * Part number + * Revision + * Relevant page numbers + diff --git a/reuse_notices.md b/reuse_notices.md new file mode 100644 index 0000000000000000000000000000000000000000..b8083a672972cf7e53f30514e53ab1d757473e11 --- /dev/null +++ b/reuse_notices.md @@ -0,0 +1,29 @@ +# Legal Notices + +Source: https://docs.rubrik.com/en-us/saas/reuse/notices.html + +--- + +# Legal Notices + +## Copyright + +Copyright © 2025 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. + +## Data Security Posture Legal Notices + +By using the Data Security Posture application, you understand and acknowledge that the pre-existing Policies and Analyzers of Data Security Posture contain general suggestions for data elements and formats based on common data sets and formats. The suggested data elements and formats in Data Security Posture 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 Data Security Posture search results will include every instance of each data element and format within your data set. We strongly recommend that you consult legal counsel for specific advice regarding compliance with applicable laws and regulations. + +Data Security Posture 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. diff --git a/reuse_support.md b/reuse_support.md new file mode 100644 index 0000000000000000000000000000000000000000..2bc40b74cb06f8b0c3966c424c76a0b761102dd5 --- /dev/null +++ b/reuse_support.md @@ -0,0 +1,13 @@ +# Support + +Source: https://docs.rubrik.com/en-us/saas/reuse/support.html + +--- + +# Support + +Use one of the following methods to contact Rubrik Support. + +Web | [Rubrik Support Portal](https://support.rubrik.com) +---|--- +Phone | [Contact numbers](https://www.rubrik.com/support/#contact-numbers) diff --git a/rubrik_supported_workloads.md b/rubrik_supported_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..4f33a208ce88427241454a16e1ca32bdfb2acfe8 --- /dev/null +++ b/rubrik_supported_workloads.md @@ -0,0 +1,47 @@ +# Rubrik Security Cloud workloads + +Source: https://docs.rubrik.com/en-us/saas/rubrik/supported_workloads.html + +--- + +# Rubrik Security Cloud workloads + +RSC securely manages and protects data from a wide variety of workload types. + +Supported workload types: + + * [Active Directory forest](../adds/active_directory_forest.html "Rubrik Security Cloud offers protection services for the Active Directory forest hierarchy. You can protect and recover the entire forest hierarchy in the event of a disaster or ransomware attack.") + * [Active Directory domains and domain controllers](../adds/active_directory_domain_dc.html "You can protect and recover Active Directory domains and domain controllers by using the protection services offered by Rubrik Security Cloud.") + * [AHV virtual machines](../nutanix_ahv/ahv_virtual_machines.html "RSC provides data management and protection for virtual machines deployed in a Nutanix Acropolis environment.") + * [Amazon Web Services workloads](../saas/aws_workloads.html "RSC protects the following types of Amazon Web Services workloads: EC2 instances, EBS volumes, Amazon S3, Amazon RDS and Aurora databases, and Amazon DynamoDB.") + * [Azure DevOps](../azure_devops/azr_devops.html "RSC protects the data and resources of Azure DevOps projects and repositories within the Azure DevOps organization.") + * [Atlassian Jira](../jira/jira.html "To protect your Atlassian Jira data, you can back up and restore data, such as projects, settings, workflows, and issues, in your Jira site .") + * [File systems](../saas/fs_filesystems.html "RSC provides management and protection of file system data on supported Linux, Unix, and Windows hosts through filesets.") + * [Google Cloud Platform workloads](../gcp/gcp.html "RSC protects the following types of Google Cloud Platform workloads: Google Compute Engine instances and persistent disks.") + * [Hyper-V virtual machines](../saas/hyper_v/hyperv_virtual_machines.html "A Rubrik cluster provides data management and protection for virtual machines that are deployed in a Microsoft Hyper-V environment. The Rubrik cluster can manage and protect virtual machines in an environment with multiple Hyper-V servers and virtual machines.") + * [IBM Db2](../db2/ibm_db2.html "With IBM Db2 workloads, you can automate complex tasks such as database discovery and data protection for managing databases.") + * [Kubernetes protection](../kubernetes/k8s_workload_protection.html "You can use Kubernetes protection to protect your on-premise or cloud-native Kubernetes clusters using a protection set.") + * [Managed Volumes and SLA Managed Volumes](../managedvolumes/mv_managed_volumes_sla_managed_volumes.html "Managed Volumes in RSC protect and manage data while SLA Managed Volumes schedule and initiate backups using an SLA Domain.") + * [Microsoft Azure workloads](../saas/azr_workloads.html "RSC protects the data and resources of Azure virtual machines, Azure managed disks, Azure Blob Storage, and Azure SQL workloads in Azure subscriptions.") + * [Microsoft 365](../saas/m365.html "Using the data management and protection services offered by Rubrik Security Cloud, you can protect Microsoft 365 data operations.") + * [Microsoft 365 Backup Storage](../m365_backup_storage/m365_backup_storage.html "With the Microsoft 365 Backup Storage feature, you can back up Microsoft 365 applications such as SharePoint sites, OneDrive user accounts, and Exchange mailboxes. You can also restore large volumes of data during ransomware attacks, accidental deletion, or malicious data deletion and overwrite events.") + * [Microsoft Dynamics 365](../microsoft_dynamics_365/microsoft_dynamics_365.html "RSC protects the tables and metadata in your Microsoft Dynamics 365 subscription.") + * [Microsoft Entra ID](../saas/ms_entra_id.html "RSC supports backup and recovery of Microsoft Entra ID.") + * [Microsoft Exchange Server](../saas/ms_exchange_server.html "Rubrik Security Cloud provides protection for Microsoft Exchange Servers.") + * [MongoDB workloads](../mongodb/mongodb_workloads.html "Rubrik Security Cloud protects your MongoDB sources, databases, and collections, ensuring optimal storage efficiency and smooth database operations with its advanced security features and strong data protection.") + * [MySQL](../mysql/mysql.html "RSC protects the MySQL databases from accidental deletions, ransomware attacks, and other potential threats.") + * [NAS CD data sets](../saas/ncd_data_sets.html "Rubrik NAS Cloud Direct offers secure data protection with high-performance, scalable enterprise backup, and archive services for unstructured file data.") + * [NAS systems](../nas/nas_systems.html "RSC manages and protects NFS and SMB shares on NAS systems for efficient data storage and retrieval.") + * [Okta IdP](../okta/okta_idp.html "Rubrik Security Cloud provides protection and recovery for Okta Identity Provider objects. By integrating your Okta tenant with Rubrik, you can leverage a comprehensive set of data protection features designed for security, simplicity, and reliability.") + * [Oracle databases](../oracle/oracle_databases_rsc.html "You can use RSC to back up, archive, replicate, and recover Oracle databases.") + * [OpenStack virtual machines](../openstack/openstack_virtual_machines.html "RSC provides data management, SLA Domain protection, and recovery for OpenStack virtual machines.") + * [PostgreSQL](../postgresql/postgresql.html "Rubrik Security Cloud protects your PostgreSQL cluster by simplifying complex backup and recovery processes, discovering the databases automatically, and protecting data using SLA Domains.") + * [Salesforce Data Protection](../salesforce/salesforce_management.html "Salesforce Data Protection is a Rubrik-hosted SaaS service that extends RSC by securely backing up your critical Salesforce data and metadata for standard and custom objects.") + * [SAP HANA databases](../saas/sap_hana_protection.html "RSC enables administrators to implement backup policies on SAP HANA databases running on public clouds and on-premises.") + * [SnapMirror Cloud](../saas/snapmirror_cloud.html "RSC protects user data replicated by the NetApp SnapMirror Cloud service.") + * [Microsoft SQL Server databases](../common/sql_server_databases.html "A Rubrik cluster provides data management and protection for Microsoft SQL Server databases.") + * [VMware Cloud](../vmware_cloud/vmware_cloud.html "A Rubrik Cloud Cluster effectively protects virtual machines deployed on VMware Cloud on AWS, Microsoft Azure VMware Solution, and Google Cloud VMware Engine.") + * [vSphere virtual machines](../saas/vs_virtual_machines.html "Rubrik Security Cloud provides data management and SLA Domain protection for vSphere virtual machines, including vSphere VM templates that are managed either through a VMware vSphere environment or a content library.") + * [VMware Cloud Director vApps](../vcd/vmware_cloud_director_vapps.html "The Rubrik cluster provides SLA Domain protection and data management for VMware Cloud Director vApps.") + * [Windows volume groups](../saas/windows_volume_groups.html "A volume group is a Rubrik workload comprised of at least one data storage volume on a Windows host.") + diff --git a/saas-ai_enabling_ruby.md b/saas-ai_enabling_ruby.md new file mode 100644 index 0000000000000000000000000000000000000000..8defed0f793fb455860e1ba9a6c5d8b7ba5acb76 --- /dev/null +++ b/saas-ai_enabling_ruby.md @@ -0,0 +1,33 @@ +# Enabling Ruby + +Source: https://docs.rubrik.com/en-us/saas/saas-ai/enabling_ruby.html + +--- + +# Enabling Ruby + +Enable Ruby to use its guided interaction process for threat detection and data recovery. + +## Before you begin + +Ensure that you are using the Rubrik Enterprise edition. + +## About this task + +After enabling Ruby, you can use it to perform the required actions, based on user roles. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click **Ruby**. + 4. Select the checkbox to accept the terms and conditions associated with Ruby. + 5. Click Enable Now. + 6. Turn on **Enable Ruby**. + +## Results + +Ruby is now enabled in RSC. diff --git a/saas-ai_ruby.md b/saas-ai_ruby.md new file mode 100644 index 0000000000000000000000000000000000000000..c3f4bcf0cdaf361169e47ed5562b3e1b01657b86 --- /dev/null +++ b/saas-ai_ruby.md @@ -0,0 +1,32 @@ +# Ruby + +Source: https://docs.rubrik.com/en-us/saas/saas-ai/ruby.html + +--- + +# Ruby + +Ruby is a generative AI assistant that extends Rubrik Security Cloud capabilities. You can interact with Ruby to use and manage RSC security features. + +Ruby is built on Microsoft Azure Open AI. This Rubrik partnership with Microsoft secures a private entry point into generative AI and ensures that your data remains private. Ruby uses Rubrik threat intelligence information based on machine learning to develop interactive workflows for data recovery during a security incident. + +Using RSC Data Threat Analytics, Data Security Posture, and Orchestrated Application Recovery, you can detect anomalies, uncover sensitive data, and identify and isolate threats in the environment. Ruby streamlines these multi-step workflows within RSC into a single process, allowing backup administrators to perform security-related tasks and collaborate with security teams. + +When Threat Monitoring detects an anomaly, you receive a security incident notification. Ruby is then available in the Notifications tab in the Inbox in RSC dashboards to guide you through an integrated and interactive message window. Ruby provides recommendations to remediate the security incident using Sensitive Data Monitoring, Threat Hunting, and Orchestrated Application Recovery. + +Ruby matches user intent to a defined workflow based on a pre-trained model. The Ruby workflow involves the following: + + * Viewing the threat details, including the indicators of compromise (IOCs), snapshot location, and time of the snapshot + * Searching for additional IOCs by using threat hunting + * Discovering the location of the sensitive data, including violations and the policies and objects impacted. For Microsoft 365 objects, you can also use Ruby to take remedial actions to address the issues identified. + * Quarantining snapshots that contain potentially malicious files or objects + * Creating Recovery Plans for data recovery + +While the notifications in the Inbox on the RSC dashboard are available to all users, Ruby only performs tasks for user accounts with the owner and administrator roles. Ruby recommends actions based on the RBAC permissions of the user account. Actions that do not correlate to user account permissions are not available. Ruby asks for user confirmation before proceeding with any recovery or quarantine action. The audit logs also indicate the user account that confirmed the specific actions performed using Ruby. + +Ruby is available as part of the Rubrik Enterprise edition. Enabling Ruby requires that Rubrik clusters are running CDM version 9.0.1 or later. For the threat detection and remediation use case, enabling Threat Monitoring is required. + +Note: + +Ruby is an AI assistant. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. + *[ > ]: and then diff --git a/saas-ai_ruby_2.md b/saas-ai_ruby_2.md new file mode 100644 index 0000000000000000000000000000000000000000..c5ff13f34ea840457c66f48022266a7a6c623c04 --- /dev/null +++ b/saas-ai_ruby_2.md @@ -0,0 +1,31 @@ +# Ruby + +Source: https://docs.rubrik.com/en-us/saas/saas-ai/ruby_2.html + +--- + +# Ruby + +Ruby is a generative AI assistant that extends Rubrik Security Cloud capabilities. You can interact with Ruby to use and manage RSC security features. + +Ruby is built on Microsoft Azure Open AI. This Rubrik partnership with Microsoft secures a private entry point into generative AI and ensures that your data remains private. Ruby uses Rubrik threat intelligence information based on machine learning to develop interactive workflows for data recovery during a security incident. + +Using RSC Data Threat Analytics, Data Security Posture, and Orchestrated Application Recovery, you can detect anomalies, uncover sensitive data, and identify and isolate threats in the environment. Ruby streamlines these multi-step workflows within RSC into a single process, allowing backup administrators to perform security-related tasks and collaborate with security teams. + +When Threat Monitoring detects an anomaly, you receive a security incident notification. Ruby is then available in the Notifications tab in the Inbox in RSC dashboards to guide you through an integrated and interactive message window. Ruby provides recommendations to remediate the security incident using Sensitive Data Monitoring, Threat Hunting, and Orchestrated Application Recovery. + +Ruby matches user intent to a defined workflow based on a pre-trained model. The Ruby workflow involves the following: + + * Viewing the threat details, including the indicators of compromise (IOCs), snapshot location, and time of the snapshot + * Searching for additional IOCs by using threat hunting + * Discovering the location of the sensitive data, including violations and the policies and objects impacted. For Microsoft 365 objects, you can also use Ruby to take remedial actions to address the issues identified. + * Quarantining snapshots that contain potentially malicious files or objects + * Creating Recovery Plans for data recovery + +While the notifications in the Inbox on the RSC dashboard are available to all users, Ruby only performs tasks for user accounts with the owner and administrator roles. Ruby recommends actions based on the RBAC permissions of the user account. Actions that do not correlate to user account permissions are not available. Ruby asks for user confirmation before proceeding with any recovery or quarantine action. The audit logs also indicate the user account that confirmed the specific actions performed using Ruby. + +Ruby is available as part of the Rubrik Enterprise edition. Enabling Ruby requires that Rubrik clusters are running CDM version 9.0.1 or later. For the threat detection and remediation use case, enabling Threat Monitoring is required. + +Note: + +Ruby is an AI assistant. AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. diff --git a/saas-ai_using_the_ruby_message_window.md b/saas-ai_using_the_ruby_message_window.md new file mode 100644 index 0000000000000000000000000000000000000000..b448c25656feac60964ec25dfafe9ff761065191 --- /dev/null +++ b/saas-ai_using_the_ruby_message_window.md @@ -0,0 +1,42 @@ +# Using the Ruby message window + +Source: https://docs.rubrik.com/en-us/saas/saas-ai/using_the_ruby_message_window.html + +--- + +# Using the Ruby message window + +After you enable Ruby, you can access its available capabilities in the message window. + +## Before you begin + +Ensure that you have enabled Ruby. + +## About this task + +You can access the Ruby message window to perform the recommended recovery actions using prompts. + +The user account role must have the required permissions to perform any actions using the prompts in Ruby. + +## Procedure + + 1. Log in to RSC. + 2. Click Inbox > Notifications to access a threat notification. + 3. Click Let's investigate and build a response plan together to manage a detected threat using Ruby. + +The Ruby message window appears. + + 4. In the Ruby message window, provide a prompt or click a suggested prompt to perform an action. + +Ruby saves any conversation sessions that you initiate in its message window. + + 5. **Optional:** Click Pin this chat to pin the conversation session with Ruby. + +The Chat History pane lists the conversation sessions. The pinned conversation appears at the top of the list. You can close the message window to end the message session. + + 6. **Optional:** Click to revisit a conversation session. + +## Results + +You can now use the message window to interact with Ruby. + *[ > ]: and then diff --git a/saas_Configuring_ri_events_for_protected_objects.md b/saas_Configuring_ri_events_for_protected_objects.md new file mode 100644 index 0000000000000000000000000000000000000000..a4417309b3447391b6b47d43bdb4bff6aa922d12 --- /dev/null +++ b/saas_Configuring_ri_events_for_protected_objects.md @@ -0,0 +1,44 @@ +# Configuring Anomaly Detection events for protected objects + +Source: https://docs.rubrik.com/en-us/saas/saas/Configuring_ri_events_for_protected_objects.html + +--- + +# Configuring Anomaly Detection events for protected objects + +Configure Anomaly Detection events for protected objects of connected Rubrik clusters for more fine-grained control of alerts. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page displays cards for every protectable object type. + + 4. Select an RSC Datacenter card. + +The list of the protected objects for the selected object type appears. + + 5. Click an object. + +The object details page appears. + + 6. Open the ellipsis menu and select a configuration option. + +Option| Description +---|--- +Enable Anomaly Detection events | Successfully enables Data Threat Analytics events for the object. +Disable Anomaly Detection events > Confirm | Successfully disables Data Threat Analytics events for the object. + +The confirmation prompt appears. + +The prompt confirms that Anomaly Detection events are successfully configured for the object. + +## Results + +Anomaly Detection events are successfully configured for the object. + *[ > ]: and then diff --git a/saas_RSC_customizable_dashboards.md b/saas_RSC_customizable_dashboards.md new file mode 100644 index 0000000000000000000000000000000000000000..5fb73eb6d094dde57d8e4be69505cc46de403d77 --- /dev/null +++ b/saas_RSC_customizable_dashboards.md @@ -0,0 +1,12 @@ +# Customizable dashboards + +Source: https://docs.rubrik.com/en-us/saas/saas/RSC_customizable_dashboards.html + +--- + +# Customizable dashboards + +You can customize the Data Protection dashboard and adjust it to display widgets from the Data Security Posture, Data Threat Analytics, and M365 dashboards. + +The Data Protection dashboard displays summary information for each installed RSC app in a dedicated pane for that app. The panes provide interactive elements for related data that are discoverable for the app. You can customize these panes to display the required information and discoverable data. + *[ > ]: and then diff --git a/saas_access_mgmt_tenant_org_users.md b/saas_access_mgmt_tenant_org_users.md new file mode 100644 index 0000000000000000000000000000000000000000..877f279b3f5bdbeeb29e1af87cfdbb791a24e072 --- /dev/null +++ b/saas_access_mgmt_tenant_org_users.md @@ -0,0 +1,34 @@ +# Access management for tenant organization users + +Source: https://docs.rubrik.com/en-us/saas/saas/access_mgmt_tenant_org_users.html + +--- + +# Access management for tenant organization users + +You can add a tenant organization to manage user access to the NAS CD data sets. Following the recommended sequence to add users, user permissions, and NAS CD systems is necessary for successful system access management. + +A global administrator user can add a tenant organization. When you add a tenant organization for NAS CD data sets, you can assign users to the organization and make at least one user an organization administrator. With the required permissions assigned, the organization administrator can access the NAS CD UI to add systems in NAS CD. The systems that the organization administrator adds in theNAS CD UI reflects in RSC for the organization members after the global administrator edits the NAS CD organization to add the systems. + +When managing the access to NAS CD data sets for the tenant organization members, it is important to perform the following requirements in sequence: + + * Creating a tenant organization for NAS CD data sets with an organization administrator and other users. Only a global administrator user can add a tenant organization. RSC requires that you not add any system for the organization before adding necessary permissions to for the users to view the systems. The Creating a tenant organization topic provides more information about creating a tenant organization. + +Note: + +The Assign Datacenter Archival Locations and Select SLA Domains are not applicable for NAS CD data sets. + + * Adding systems by the organization administrator from the NAS CD UI. + +Note: + +The added systems in NAS CD are visible in RSC only for the global administrator. The NAS CD user guide provides more information about adding a system using the NAS CD UI. + + * Adding permission to view the systems for the NAS CD tenant organization. As a global administrator user, you can edit the NAS CD organization to add permission to view specific NAS systems from the Data Management Privileges card on the Assign Privileges page. The Edit an organization topic provides information about this. + * Adding a user role with permission to view the added systems. An organization administrator can assign this role to a user. The Creating custom roles for NAS Cloud Direct data sets topic provides information about adding a custom user role with required permissions. After you assign the user role, the organization users can see the added systems on the RSC Inventory page. + +Note: + +Only an organization administrator with the Federated access and view cluster permissions can access the NAS CD UI after the global administrator edits the organization to add the required systems. A user with Federated access, View cluster, and Data Source Management permission can also access the NAS CD UI. + + *[ > ]: and then diff --git a/saas_accessing_identity_inventory.md b/saas_accessing_identity_inventory.md new file mode 100644 index 0000000000000000000000000000000000000000..4e41c5b92198130d934c1e1a1ac9b7b94354f67a --- /dev/null +++ b/saas_accessing_identity_inventory.md @@ -0,0 +1,38 @@ +# Accessing the Identity Inventory + +Source: https://docs.rubrik.com/en-us/saas/saas/accessing_identity_inventory.html + +--- + +# Accessing the Identity Inventory + +When you enable the Identity Inventory, you can view details of user access, risk contributors, and risk changes over time on the Identity Inventory page. + +## Before you begin + +Enabling Rubrik Data Security Posture Management is required to complete this task. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. Select an option to view identities. + +Option| Description +---|--- +In the navigation bar, click Identities > Identity Inventory . | Displays the Identity Inventory page.The top bar on the page displays the total number of identities, categorized as Entra ID and Active Directory identities. +In the navigation bar, click Identities > AWS Identities. | Displays the AWS Identities page. + +Data Security Posture displays the identities on the selected page. + + 4. **Optional:** Click an identity name. + +RSC displays additional information about the identity in the Members, Associated Identities, and Accessible objects tab. + +## Results + +Data Security Posture displays details of identities on the specific page as selected. You can use the filters provided to filter the information and understand your data access risk. + *[ > ]: and then diff --git a/saas_actions_available_recovery.md b/saas_actions_available_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..a3e84e4433a3995d4e1fe7c9fcafbbad787dc471 --- /dev/null +++ b/saas_actions_available_recovery.md @@ -0,0 +1,18 @@ +# Actions available for a recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/actions_available_recovery.html + +--- + +# Actions available for a recovery + +You can take specific actions for a selected recovery from the recovery details page. + +The following actions are available for a recovery. + +Action | Description +---|--- +Clicking and then Resume Recovery | Resumes a recovery that has been paused during the recovery process. +Clicking and then Lock Recovery | Locks the recovery to prevent accidental cleanup and changes to the recovery in future Orchestrated Recovery operations. Orchestrated Recovery does not manage the recovery after you lock it, and you can retain, move, or delete the recovered virtual machines. +Clicking Clean Up | Deletes the virtual machines recovered after a test failover or cyber recovery. +Clicking Download report | Downloads a report as a PDF file with a recovery overview, recovery history, objects recovered, target resources, and any errors that might have occurred. diff --git a/saas_adding_a_host.md b/saas_adding_a_host.md new file mode 100644 index 0000000000000000000000000000000000000000..bb490a2feefd94a89074ce0616a2afc982ec606b --- /dev/null +++ b/saas_adding_a_host.md @@ -0,0 +1,49 @@ +# Adding an SAP HANA host + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_a_host.html + +--- + +# Adding an SAP HANA host + +To begin managing and protecting SAP HANA databases on a Linux host, add the host to the Rubrik cluster. + +## Before you begin + +The RSC user account must have permissions for the Linux/Unix hosts and SAP HANA Databases object types. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Sources and select Linux and Unix. + +The Linux & Unix page appears. + + 4. Click Add Hosts. + 5. In Cluster, choose a Rubrik cluster. + 6. Choose an option for using Rubrik Backup Service. + +Option| Description +---|--- +I have already installed and registered the Rubrik Backup Service connector | Use the existing installation of the Rubrik Backup Service. +I would like to download the Rubrik Backup Service connector now | + 1. In Platform, choose the platform for Rubrik Backup Service. + 2. In Version, choose the platform version. + 3. Click the download icon. + + 7. In IPs or hostname, enter the IP addresses or the names for the SAP HANA host. + +Multiple comma-separated IP addresses or hostnames can be added to protect a scale-out SAP HANA system. + + 8. Click Add. + +## Results + +RSC checks connectivity with the specified hosts and adds the hosts. + +The RBS status column provides information about the state of the connection. + *[ > ]: and then diff --git a/saas_adding_a_sap_hana_system.md b/saas_adding_a_sap_hana_system.md new file mode 100644 index 0000000000000000000000000000000000000000..2bdd186c2ae3c72582979ce4ea49fd9de8a4377b --- /dev/null +++ b/saas_adding_a_sap_hana_system.md @@ -0,0 +1,120 @@ +# Adding an SAP HANA system + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_a_sap_hana_system.html + +--- + +# Adding an SAP HANA system + +Add an SAP HANA system to the RSC domain to start protecting SAP HANA workloads. + +## Before you begin + +After an upgrade of the CDM software, the Rubrik cluster automatically updates the Rubrik Backup Service (RBS) software to the correct version on associated SAP HANA hosts, except when upgrading from Rubrik CDM version 5.3 to version 6.0.1. After upgrading from Rubrik CDM version 5.3 to version 6.0.1, retrieve and update the new RPM package as described in [Updating RBS when upgrading from Rubrik CDM version 5.3 to version 6.0.1](updating_rbs_when_upgrading_from_rubrik_cdm_version_5_3_to_version_6_0_1.html "Update the Rubrik Backup Service when upgrading from Rubrik CDM version 5.3 to version 6.0.1."). + +For more information about RBS for SAP HANA, refer to the Rubrik CDM User Guide. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click on the SAP HANA inventory card. + +The SAP HANA page appears. + + 5. Click Add System. + +The Add System dialog box appears. + + 6. In SAP HANA System ID, enter the system identifier (SID) of the database. + 7. In Instance Number, enter the instance number for the SAP HANA system. + 8. In IP Addresses or Hostnames, enter the IP addresses or hostnames for the SAP HANA system. + +For a scale-out system, you must add the IP addresses or hostnames for all the hosts. + +For an SAP HANA system with replication, add a secondary master IP address if you want the secondary master to take backups when a failover occurs. + + 9. Select a method for RSC to authenticate to the SAP HANA system. + +Authentication Type| Description +---|--- +User Credentials | Requires username and password of the backup administrator. +HDB Userstore Key | Requires the SAP HANA Secure User Store (hdbuserstore) key of the backup administrator, instead of the username and password of the backup administrator. + + 10. For User Credentials, in Backup Admin User and Password, enter the login credentials. + +The backup administrator must belong to the SYSTEM database, not a tenant database, and must have BACKUP ADMIN, CATALOG READ, DATABASE ADMIN, and INIFILE ADMIN privileges. + + 11. For HDB Userstore Key, in Secure User Key, enter the name of the hdbuserstore key that the backup administrator created on the active SAP HANA primary or master host. + +The backup administrator must belong to the SYSTEM database, not a tenant database, and must have BACKUP ADMIN, CATALOG READ, DATABASE ADMIN, and INIFILE ADMIN privileges. + + 12. Select SSL encryption. + +Selecting this option enables you to authenticate the communication between the SAP HANA database and RBS running on the same SAP HANA host. + + 13. In Key store path, enter the path to the key store file that contains the identity of the client. + +The path can be relative to $SECUDIR. The path is available under global.ini > communication > sslkeystore. + + 14. In Trust store path, enter the path to the trust store that contains the public certificates of the server. + +The path can be relative to $SECUDIR. The path is available under global.ini > communication > ssltruststore. + + 15. In Crypto library path, provide the absolute path to the libsapcrypto.so library. + +RSC auto-fills this field with the default location of the library after you provide the SAP HANA ID and instance number. The library is located in the $DIR_EXECUTABLE directory. + + 16. In Host name in certificate, provide the hostname in the trust certificate if you want the server certificate to be validated using the default truststore. + +The sapgenpse get_my_name -p sapsrv.pse command retrieves the details of the certificate. The hostname is available under Subject : CN=. + + 17. Click Next. + 18. Turn on Configure Storage Snapshot Location if you want to take storage snapshots of your SAP HANA system running on Azure virtual machine. + 19. **Optional:** In Cloud Account, select an Azure cloud account that contains the Azure virtual machine running your SAP HANA system. + +Alternatively, you can click the plus icon to create an Azure cloud account for the Cloud Cluster ES protection use case. + +RSC stores the storage snapshots of your SAP HANA system in the selected Azure cloud account. + + 20. Click Next. + 21. Select an option to trigger the backup. + +Option| Description +---|--- +Trigger via SLA Domains in RSC | RBS triggers backups based on the frequency defined in the SLA Domain. +Trigger via external tools | Full, incremental, and differential backups are triggered using external tools such as SAP HANA Studio, Cockpit, API calls, cron jobs, or direct command-line execution. The SLA Domain manages retention, archival, and replication of backups.Important: If you select this option, you must use external tools to schedule and start backups. Rubrik does not trigger backups automatically. The SAP HANA external backup trigger topic provides more information about how externally initiated backups work and affect SLA Domain compliance in Rubrik. + +All databases discovered under an added SAP HANA system inherits the selected backup trigger type. + +Note: + +Contact Rubrik Support to enable the external backup trigger feature in your RSC domain. Rubrik supports this feature only on Rubrik clusters running Rubrik CDM version 9.4 or later. + + 22. Click Add. + +## Results + +The SAP HANA system has been added to RSC. + +Hovering over the SAP HANA system in the Systems tab displays the status of the system. + +The Database tab lists the discovered SAP HANA databases connected to the SAP HANA system. + +## What to do next + +To start protecting the databases, assign an SLA Domain to the system databases. The Rubrik Backint client starts taking backups only after you assign an SLA Domain. + +After you assign the SLA Domain, do the following: + + * Set the backup trigger for each database. + * Ensure that the external frequency of full backups matches the frequency in the assigned SLA Domain. + + *[ > ]: and then diff --git a/saas_adding_a_service_account.md b/saas_adding_a_service_account.md new file mode 100644 index 0000000000000000000000000000000000000000..9fbd997f50258aca3210e7e4765d35755076d00c --- /dev/null +++ b/saas_adding_a_service_account.md @@ -0,0 +1,47 @@ +# Adding a service account + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_a_service_account.html + +--- + +# Adding a service account + +Add a service account in RSC to generate client credentials and enable client-side applications to authenticate to RSC. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users and Access and select Service Accounts. + +The Service Accounts page appears. + + 4. Click Add Service Account. + +The Service Account Details wizard appears. + + 5. In Name, enter the name of the service account. + 6. **Optional:** In Description, enter the description of the service account. + 7. Click Next. + +The Roles wizard appears. + + 8. Select the roles to be assigned to the service account. + 9. Click Add. + +RSC creates the Service account. RSC displays the name of the service account, Client ID, Client Secret, and the Access Token URI to be used by the client application that owns the service account. + + 10. Copy the client credentials and the access token URI. + 11. **Optional:** Click Download As JSON. + +Use this option to download a file containing the client credentials and the access token URI in the JSON format. + + 12. Click Done. + +## Results + +RSC creates the service account and generates credentials that client applications can use in order to authenticate themselves and invoke RSC API endpoints. + *[ > ]: and then diff --git a/saas_adding_additional_accounts.md b/saas_adding_additional_accounts.md new file mode 100644 index 0000000000000000000000000000000000000000..5b3bcb97991a300664b460658518749036e11b54 --- /dev/null +++ b/saas_adding_additional_accounts.md @@ -0,0 +1,51 @@ +# Adding additional accounts + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_additional_accounts.html + +--- + +# Adding additional accounts + +The initial RSC user account, and every subsequently added user account, can add additional users. + +## Procedure + + 1. Log in to RSC. + 2. Click the silhouette icon and select Invite users. + +The Invite users dialog box appears. + + 3. In Email, enter an email address. + 4. Click Invite. + +RSC sends the invitation to the specified email address. + +If an RSC user account with the specified email address already exists, or if RSC has already sent an invitation to the specified email address, a message stating User exists or has already been invited appears. + +The recipient receives an email from support@rubrik.com. + + 5. In the email, click Continue. + +The RSC login page appears. + + 6. In Email, enter the email address. + +Enter the email address to which the RSC Password Reset email was sent. + + 7. In Password, enter a password for the new account. + +RSC accepts the password and activates the Login button. + + 8. Click Login. + +The Rubrik Security Cloud end user license agreement (EULA) appears. + + 9. Read the EULA, scrolling through to the end of the document. + +The accept button becomes active. + + 10. Click I accept these terms and conditions. + +## Results + +RSC stores the account credentials, and the RSC Dashboard page appears. diff --git a/saas_adding_cluster.md b/saas_adding_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..e6786dd923bfe39098209f1ea8b3fb5fdad5b0b1 --- /dev/null +++ b/saas_adding_cluster.md @@ -0,0 +1,45 @@ +# Adding a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_cluster.html + +--- + +# Adding a Rubrik cluster + +To enhance data protection capabilities, add a Rubrik cluster to a Rubrik Security Cloud account. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click and select Import Rubrik cluster. + +The Import Rubrik cluster dialog box appears. + + 5. Copy the single-use token to your clipboard. + 6. Click Done. + +The dialog box closes. + + 7. Log in to the Rubrik cluster using the administrator account or an account with administrator privileges. + 8. Click the on the top bar of the web UI. + +The Settings menu appears. + + 9. Select Cluster Settings. + +The Cluster Settings page appears. + + 10. In Global Cluster Manager Token, paste the token from your clipboard. + +Rubrik clusters use HTTPS when initially connecting to RSC. During this process, the system upgrades the connection protocol to WebSocket Secure (WSS) for secure bidirectional communication. The network administrator should verify that the WSS protocol is allowed across the network between the Rubrik cluster and RSC. + + 11. Click Update. + +## Results + +The Rubrik cluster saves the values and initiates a secure connection with RSC. + +After a secure connection is established, the Rubrik cluster appears on the Clusters page in RSC domain. + *[ > ]: and then diff --git a/saas_adding_entra_id_with_oauth.md b/saas_adding_entra_id_with_oauth.md new file mode 100644 index 0000000000000000000000000000000000000000..a497c116ff5602a2510affb975503d233187bd1a --- /dev/null +++ b/saas_adding_entra_id_with_oauth.md @@ -0,0 +1,72 @@ +# Adding Microsoft Entra ID with OAuth + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_entra_id_with_oauth.html + +--- + +# Adding Microsoft Entra ID with OAuth + +Add Microsoft Entra ID as a protected workload that uses OAuth for authentication. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, select Inventory > Identity > Microsoft Entra ID . + +The inventory list for Microsoft Entra ID appears. + + 4. Click Manage Directories. + +The Microsoft Entra ID Settings page appears. + + 5. Click Add Microsoft Entra ID. + +The RSC displays the Configure cloud account page of the Add Microsoft Entra ID wizard. + + 6. Select Configure with OAuth. + +This is the recommended selection because RSC creates a valid application in Microsoft Entra ID with the correct level of permission. + + 7. In Microsoft Entra ID Domain, enter the domain for Microsoft Entra ID. + 8. In Region, select a region and click Next. + +RSC uses this region to store the Microsoft Entra ID snapshot data. + + 9. In Access, select an access level and click Next. + +Due to the Microsoft 365 dependency on Microsoft Entra ID for metadata recovery, to prevent data loss, Rubrik recommends that you assign Full Access to the Rubrik service principal before initiating a full Teams or SharePoint relic recovery operation. + +Option| Description +---|--- +Full access | Provides RSC with read and write access to the domain. Additional permissions are not required during a recovery. +Just-in-time access | Grants RSC limited read-only access to the domain for ongoing backups. This option requires additional write permissions for recovery. + +The Add Microsoft Entra ID page appears. + + 10. Click Log in to Microsoft Entra ID. + +The Microsoft Pick an account screen appears. + + 11. Select a Microsoft account. + +The Permissions requested screen appears with a list of permissions requested for RSC. + + 12. Click Accept. + +When the authorization is successful, RSC is granted the required read and write permissions to manage your Microsoft Entra ID data. + + 13. Click Add Microsoft Entra ID. + 14. **Optional:** View the progress on the Events page or create a new SLA Domain to protect your Microsoft Entra ID directories. + +## Results + +You have added a Microsoft Entra ID domain with OAuth authentication to RSC. + *[ > ]: and then diff --git a/saas_adding_entra_id_without_oauth.md b/saas_adding_entra_id_without_oauth.md new file mode 100644 index 0000000000000000000000000000000000000000..1fe3e1590b4e4b7b7dc4d07dd8e6b07d39d5d7b9 --- /dev/null +++ b/saas_adding_entra_id_without_oauth.md @@ -0,0 +1,60 @@ +# Adding Microsoft Entra ID without OAuth + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_entra_id_without_oauth.html + +--- + +# Adding Microsoft Entra ID without OAuth + +Add a Microsoft Entra ID directory as a protected workload without OAuth, and instead use your existing Microsoft Entra ID application registration. + +## About this task + +If you do not use OAuth, you are responsible for setting up the Microsoft Entra ID application with the correct permissions. RSC cannot verify the Microsoft Entra ID application validity and permissions during configuration. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, select Inventory > Identity > Microsoft Entra ID . + +The inventory list for Microsoft Entra ID appears. + + 4. Click Manage Directories. + +The Microsoft Entra ID Settings page appears. + + 5. Click Add Microsoft Entra ID. + +The RSC displays the Configure cloud account page of the Add Microsoft Entra ID wizard. + + 6. Select Configure without OAuth. + +You can use your Microsoft Entra ID application from the Microsoft portal and manage the related permissions. + + 7. In Microsoft Entra ID Domain, type the domain for Microsoft Entra ID. + 8. In Region, select a region. + 9. In Application ID, enter the ID of the application running on Microsoft Entra ID. + +The application ID is available in your Azure account on the Azure portal. + + 10. In Client Secret, type the client secret for the application running on Microsoft Entra ID. + +The client secret is available in your Azure account on the Azure portal. + + 11. Click Add Microsoft Entra ID. + 12. **Optional:** View the progress or create a new SLA Domain. + +Option| Description +---|--- +Go to Events | View the progress on the Events page. +Create SLA | Create an SLA Domain to protect your Microsoft Entra ID directories. + + +## Results + +You have added Microsoft Entra ID to RSC. + *[ > ]: and then diff --git a/saas_adding_guest_os_credentials.md b/saas_adding_guest_os_credentials.md new file mode 100644 index 0000000000000000000000000000000000000000..d642ecd91f447a0d50cfbbd3eaa1c1859a4498ce --- /dev/null +++ b/saas_adding_guest_os_credentials.md @@ -0,0 +1,47 @@ +# Adding guest OS credentials + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_guest_os_credentials.html + +--- + +# Adding guest OS credentials + +Add guest OS credentials for a virtual machine. Guest OS credentials provide service account details with the appropriate privileges. + +## Before you begin + +To add a guest OS credential, use an RSC user account that is assigned the administrator role and the Manage guest OS credentials permission. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC using the administrator account credentials. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Source > Access Credentials. + +The Access Credentials page appears. + + 4. Click Guest OS Settings tab. + 5. Click Add Guest OS Credentials. + +The Add Guest OS Credentials page appears. + + 6. Select the cluster that contains the virtual machine files you want to recover. + 7. **Optional:** In Domain, enter the domain IP address. + 8. **Optional:** In Description, enter the description. + +The description field is available only for Rubrik clusters running Rubrik CDM version 9.2 or later. + + 9. Enter the username and password for the guest OS. + 10. Click Add. + +## Results + +RSC adds the guest OS credentials to the Rubrik cluster. + *[ > ]: and then diff --git a/saas_adding_netapp_system.md b/saas_adding_netapp_system.md new file mode 100644 index 0000000000000000000000000000000000000000..91615f802fa3529f25942851d1e09aacc0e8b235 --- /dev/null +++ b/saas_adding_netapp_system.md @@ -0,0 +1,53 @@ +# Adding a NetApp system + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_netapp_system.html + +--- + +# Adding a NetApp system + +Add a NetApp system for the SnapMirror Cloud to protect. + +## Before you begin + +Verify that the Rubrik cluster used to protect the NetApp host volume is running Rubrik CDM version 7.0.4 or later (except for CDM version 8.0.0). + +## Procedure + + 1. Log in to RSC. + 2. From the app tray, select Settings. + +The Settings page appears. + + 3. Click Data Sources > NAS Systems. + +A list of configured NetApp systems appears. + + 4. Click Add NAS System. + +The Add System dialog box appears. + + 5. In Rubrik Cluster, select a Rubrik cluster. + 6. In System Type, select NetApp Cluster Mode. + 7. In IPs or Hostnames, enter the IP address or resolvable hostname of the NetApp cluster. + 8. **Optional:** Turn on MetroCluster Support. + +When this option is enabled, all systems that are part of the MetroCluster must be added separately, with this option enabled. + + 9. Choose Credentials. + +Option| Description +---|--- +Provide temporary root access | Provide credentials that RSC uses only once to create a service account with the required privileges to perform backup and recovery jobs on the NetApp system. +Provide API user credentials | Provide credentials for a system-level API account with manually assigned privileges to perform backup and recovery jobs on the NetApp system. + + 10. **Optional:** For SMB credentials, in Username and Password, enter the credentials of an SMB user with backup and restore privileges. + +The password is case-sensitive. + + 11. Click Add. + +## Results + +RSC connects to the NetApp system and discovers volumes and shares. + *[ > ]: and then diff --git a/saas_adding_node_cces.md b/saas_adding_node_cces.md new file mode 100644 index 0000000000000000000000000000000000000000..ba197a6a9f86b55388605a494806d7deeb65a6f6 --- /dev/null +++ b/saas_adding_node_cces.md @@ -0,0 +1,56 @@ +# Adding a node to Cloud Cluster ES + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_node_cces.html + +--- + +# Adding a node to Cloud Cluster ES + +Add a node to a Cloud Cluster ES to increase capacity and improve performance. + +## Before you begin + + * Ensure that you have created a cloud account. + * Confirm that the Rubrik Cloud Cluster ES is registered with RSC. + * Verify that you are assigned a role that has the Add cluster nodes permission required to add a node. + +## About this task + +You can use RSC to add a node to a Cloud Cluster ES only if the Cloud Cluster ES is running Rubrik CDM versions 8.0.2 and later. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click the card for the Rubrik Cloud Cluster ES where you want to add a node. + +You can use the Deployment filter to filter Rubrik Cloud Clusters. + +A page with the details of the selected Rubrik Cloud Cluster ES appears. + + 5. Click Nodes. + +A list of nodes and their details appears. + + 6. Click Add Node. + +The Add Node dialog box appears. + + 7. Select Deploy from marketplace, and then click Next. + 8. In Account, select the cloud account where the Rubrik Cloud Cluster ES was created. + +RSC auto-fills the cloud account value if you created the Rubrik Cloud Cluster ES through RSC. + +The selected cloud account must grant RSC permission to access the cloud subscription associated with the Rubrik Cloud Cluster ES. + + 9. In Number of Nodes, enter the number of nodes to add. + +Although you can add multiple nodes simultaneously, Rubrik recommends adding one node at a time. + + 10. Click Add. + +## Results + +RSC initiates a job to add the specified number of nodes to the Rubrik Cloud Cluster ES. The Events page provides the status updates. + *[ > ]: and then diff --git a/saas_adding_node_predeployed_cces.md b/saas_adding_node_predeployed_cces.md new file mode 100644 index 0000000000000000000000000000000000000000..9977480927fe7074785d35de70494d825fb766ae --- /dev/null +++ b/saas_adding_node_predeployed_cces.md @@ -0,0 +1,45 @@ +# Adding a pre-deployed node to Rubrik Cloud Cluster ES + +Source: https://docs.rubrik.com/en-us/saas/saas/adding_node_predeployed_cces.html + +--- + +# Adding a pre-deployed node to Rubrik Cloud Cluster ES + +Add a node that you have manually deployed in AWS or Azure to the Rubrik Cloud Cluster ES in RSC. Additional nodes increase capacity and improve performance. + +## Before you begin + + * Confirm that the Rubrik Cloud Cluster ES is registered with RSC. + * Verify that you are assigned a role that has the Add cluster nodes permission required to add a node. + * Manually deploy a node in AWS or Azure. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click the card for a Rubrik Cloud Cluster ES. + +You can use the Deployment filter to filter Rubrik Cloud Clusters. + +A page with the details of the selected Rubrik Cloud Cluster ES appears. + + 5. Click Nodes. + 6. Click Add Node. + +The Add Node dialog box appears. + + 7. Click Add from pre-deployed nodes, and then click Next. + 8. In Node ID, enter the ID of the new node. + 9. In IP address, enter the IP address of the new node. + 10. In Subnet mask, enter the subnet mask of the new node. + 11. In Gateway, enter the gateway of the new node. + 12. Click Add. + +RSC adds the nodes. + +## Results + +RSC initiates a job to add the specified number of nodes to the Rubrik Cloud Cluster ES. The Events page provides the status updates. + *[ > ]: and then diff --git a/saas_anomaly_detection.md b/saas_anomaly_detection.md new file mode 100644 index 0000000000000000000000000000000000000000..92081dc4b963ddc87883d4ef294616ffce1d0e3c --- /dev/null +++ b/saas_anomaly_detection.md @@ -0,0 +1,53 @@ +# Anomaly Detection + +Source: https://docs.rubrik.com/en-us/saas/saas/anomaly_detection.html + +--- + +# Anomaly Detection + +Anomaly Detection examines a range of file system statistics to check for anomalies in file system usage patterns. + +Anomaly Detection provides details about potentially anomalous incidents, including their location, Rubrik cluster, file details, and snapshot time. When you enable Orchestrated Recovery, objects that are part of a Recovery Plan are grouped together. + +When you enable Anomaly Detection for the data, Large Language Model (LLM) analysis for Anomaly Detection is enabled by default. When LLM analysis for Anomaly Detection is enabled, RSC uses a pre-trained LLM in Microsoft Azure OpenAI to detect suspicious activity. The model differentiates suspicious activity from legitimate changes caused by routine operations, such as upgrading an application or operating system. + +Identifying and differentiating malicious behavior from legitimate activities helps reduce the frequency of false alerts and enhances the experience of using Anomaly Detection to protect data. When you do not want to use LLM analysis on Anomaly Detection, you can disable it and use Anomaly Detection without it. + +When you enable Data Security Posture for an object that has an anomalous snapshot and a user account that has Data Security Posture privileges, the Sensitive files and Sensitive hits columns display values based on the base snapshot of the anomalous snapshot. The Sensitive files column shows the number of files that contain sensitive data, and the Sensitive hits column shows the number of sensitive hits for that object. + +Note: + +Anomaly Detection supports protected objects running in single-stack IPv6 environments. + +On the Anomaly Detection page, you can: + + * View the list of new and resolved investigations. + * Use the filters on the page to sort anomalies by time range, severity, encryption, object type, Rubrik cluster, and SLA Domain. + * Sort anomalous data by sensitive files or sensitive hits when you enable Data Security Posture. + * Filter anomalies by the selected policies when you enable Data Security Posture. + * Investigate and recover anomalous files in protected workloads. + * Recover a full snapshot for a virtual machine. + * Use the Search filter to search for protected workloads or Recovery Plans that have an identified anomaly. + * Initiate bulk recovery for vSphere-protected workloads or for Recovery Plans that have an identified anomaly. + * Perform cyber recovery on virtual machines based on threat hunting results to a local, isolated recovery environment. + * Download a CSV file of the changes identified for each protected workload. When you click Download CSV, RSC prepares a secure link for the file and displays a message about the download. You can also visit the File Preparation Center to access the downloaded file. + +RSC supports Anomaly Detection for: + + * VMware, AHV, and Hyper-V virtual machines + * NAS filesets + * Linux and Windows servers + * Windows Volume groups + * NAS CD data sets + * Azure virtual machines + * Azure Blob storage + * Microsoft OneDrive and SharePoint + * Amazon S3 buckets + * Amazon EC2 instances and EBS volumes + * Kubernetes virtual machines + * Kubernetes protection sets + * GCP GCE Instance + * GCP Persistent Disk + + *[ > ]: and then diff --git a/saas_anomaly_detection_report_details.md b/saas_anomaly_detection_report_details.md new file mode 100644 index 0000000000000000000000000000000000000000..9262eb9c5346a2aff8d548bd93b3421d7a2c3fc4 --- /dev/null +++ b/saas_anomaly_detection_report_details.md @@ -0,0 +1,20 @@ +# Anomaly Detection report details + +Source: https://docs.rubrik.com/en-us/saas/saas/anomaly_detection_report_details.html + +--- + +# Anomaly Detection report details + +The Anomaly Detection report provides information about scanned and unscannable objects. You can download a CSV or PDF file of the report or save a copy of the report. + +Tab | Description +---|--- +Scanned Objects | Provides the following: + * Graphs of the scanned snapshots that you can sort by severity, Rubrik cluster, and time. Both anomalous and non-anomalous details for the objects are available. + * List of scanned snapshots of objects including details such as the Rubrik cluster name, location, object type, and snapshot date. +Unscannable Objects | Provides the following: + * Information about anomalies detected by VM Encryption Detection in the Unscannable Anomalies Timeline widget. + * The list of Unscannable Anomalies, including the object, location, Rubrik cluster, and analyzed time. You can filter the information using the Time Range or Clusters filters. +The Unscannable Objects information is available only in RSC and is not available in the downloaded PDFs of Anomaly Detection reports. + *[ > ]: and then diff --git a/saas_anomaly_event_details.md b/saas_anomaly_event_details.md new file mode 100644 index 0000000000000000000000000000000000000000..39d808a4ee3f257d7a4147e76c9a9d3841565fe6 --- /dev/null +++ b/saas_anomaly_event_details.md @@ -0,0 +1,28 @@ +# Anomaly event details + +Source: https://docs.rubrik.com/en-us/saas/saas/anomaly_event_details.html + +--- + +# Anomaly event details + +Data Threat Analytics provides detailed information about the detected anomaly events, including the event timeline and an option to investigate the specific snapshot. + +Column | Description +---|--- +Encryption | Displays the likelihood of files being encrypted. + * High + * Low +This element is not available for an anomaly flagged by VM Encryption Detection. +Anomaly | Displays information relevant to the detected anomaly. Anomalies flagged by VM Encryption Detection are indicated as Ransomware - Hypervisor. +Snapshot | Displays the time at which the last snapshot was taken. This information is not available for anomalies flagged by VM Encryption Detection. +Suggested actions | Investigate Snapshot: Provides the option to investigate snapshots and recover files.This option is not available for an anomaly flagged by VM Encryption Detection.This option does not appear if there are no anomaly events. Note: To support RBAC, CSV downloads are only available from the Anomalies page and the anomaly details page. +Files changed | Displays the number of files created, deleted, and modified in the anomaly event.This element is not available for an anomaly flagged by VM Encryption Detection +Suspicious files | Displays the number of suspicious files created and detected in the last snapshot taken. These files were deemed suspicious using various heuristics, such as file type and extension.This element is not available for an anomaly flagged by VM Encryption Detection. +Event timeline | Displays the series of events associated with the top-level event. +Detection time | Displays the time when the suspect snapshot was detected. +Event category | Displays the category as Anomaly.Critical Anomaly events are only triggered when there is significant evidence of encryption. Anomalies flagged by VM Encryption Detection are also flagged as critical. +Cluster name | Displays the name of the cluster. +Object type | Displays the type of the object. +Object name | Links to the overview and events page of the protected object. + *[ > ]: and then diff --git a/saas_anomaly_report_filters.md b/saas_anomaly_report_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..f17554d211b378c856ec00364662079c06735340 --- /dev/null +++ b/saas_anomaly_report_filters.md @@ -0,0 +1,40 @@ +# Anomaly report filters + +Source: https://docs.rubrik.com/en-us/saas/saas/anomaly_report_filters.html + +--- + +# Turbo threat hunts and advanced threat hunts + +RSC provides two distinct types of threat hunts, turbo threat hunts and advanced threat hunts to enhance security measures against potential threats. + +Turbo threat hunts and advanced threat hunts use specific methods to analyze and detect anomalies within snapshots. + + * During an advanced threat hunt, RSC performs a full scan only on the latest snapshot in the selected range and incremental scans on previous snapshots in the selected range. + * Turbo threat hunting searches the hash table created by Threat Monitoring during the backup process. When a turbo threat hunt is executed, the supplied hashes are compared against those in the hash table, enabling thousands of point-in-time snapshots to be checked in less than one minute. + +Enabling # Turbo threat hunts and advanced threat hunts + +RSC provides two distinct types of threat hunts, turbo threat hunts and advanced threat hunts to enhance security measures against potential threats. + +Turbo threat hunts and advanced threat hunts use specific methods to analyze and detect anomalies within snapshots. + + * During an advanced threat hunt, RSC performs a full scan only on the latest snapshot in the selected range and incremental scans on previous snapshots in the selected range. + * Turbo threat hunting searches the hash table created by Threat Monitoring during the backup process. When a turbo threat hunt is executed, the supplied hashes are compared against those in the hash table, enabling thousands of point-in-time snapshots to be checked in less than one minute. + +Enabling Threat Monitoring is a requirement for initiating a turbo threat hunt. This is because a turbo threat hunt uses hash scans, which are only populated after the Threat Monitoring scans are complete. When enabling Threat Monitoring for the first time, ensure that it completes an initial scan of all your workloads before starting the turbo threat hunt. You can verify the status of the scan from the Event Logs page. + +# Anomaly report filters + +The filters for anomaly reports. + +Filter | Description +---|--- +Time range | Sets one of the following time ranges for the report: + * Past 24 hours + * Past 7 days + * Past 30 days + * Past 12 months + * Custom: A specified number of months before the current time. +Clusters | Displays the Rubrik clusters connected to RSC. Multi-selection is supported. + *[ > ]: and then diff --git a/saas_auth_sso_user_accounts_saml.md b/saas_auth_sso_user_accounts_saml.md new file mode 100644 index 0000000000000000000000000000000000000000..a3323757412c920054868b348cae3515d3b6c69a --- /dev/null +++ b/saas_auth_sso_user_accounts_saml.md @@ -0,0 +1,18 @@ +# Authentication of SSO user accounts using SAML + +Source: https://docs.rubrik.com/en-us/saas/saas/auth_sso_user_accounts_saml.html + +--- + +# Authentication of SSO user accounts using SAML + +RSC uses a third-party identity provider for authentication. The identity provider authenticates the SSO user accounts through the SAML 2.0 protocol. + +RSC users log in using SSO. A third-party identity provider authenticates user accounts through the SAML 2.0 protocol. + +During the SSO login process, the SAML Identity Provider (IdP) shares a signed assertion with RSC. The signed assertion identifies a user account by the email address and by the IdP groups to which the user account belongs. For each IdP group in the assertion, RSC looks up the roles assigned to the groups. RSC assigns these roles to the user account for the duration of the session. RSC does not store user account information or the groups to which the account belongs. + +RSC grants permissions to SSO user accounts based on the roles assigned through the IdP groups to which they belong. This group-to-role mapping ensures that once the SSO user accounts log in as members of an IdP group, RSC assigns the roles assigned to the appropriate groups. RSC restricts the role assignment and deactivation of SSO user accounts. + +According to the SAML 2.0 protocol, RSC cannot synchronize the list of user accounts when you remove SSO user accounts from the IdP group. As a result, an SSO user account removed from an IdP group might continue to appear on the Users page. If the SSO user accounts that were removed from an IdP group have accessed RSC before their access to that group was removed, such accounts continue to appear on the SSO tab of the Users page. The presence of these accounts in the list of user accounts does not guarantee their access to RSC. Instead, the tab lists all the user accounts that have previously accessed RSC. You can hide or delete user accounts from this list in RSC. Deleting a user account is an irreversible action. Users lose all the configured profile options and scheduled reports. Deleting a user account removes directly assigned roles and terminates all active sessions for the users. This, however, does not prevent future logins if the user account is still active in the SSO IdP. When you hide or delete a user account in RSC but do not remove them from the IdP group in your SSO IdP, they can still log in to RSC. The hidden or deleted SSO user accounts are automatically restored to the SSO Users page on the next successful login if they still belong to an authorized IdP group. Removal of user accounts from the IdP group in your SSO application is the only way to prevent SSO user access to RSC. + *[ > ]: and then diff --git a/saas_aws_cc_es_rsc.md b/saas_aws_cc_es_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..129dab8e2c7a3799162c0b866b57c135b621a1a9 --- /dev/null +++ b/saas_aws_cc_es_rsc.md @@ -0,0 +1,24 @@ +# Rubrik Cloud Cluster ES for AWS + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_cc_es_rsc.html + +--- + +# Rubrik Cloud Cluster ES for AWS + +A Rubrik Cloud Cluster Elastic Storage protects applications and data by running Rubrik CDM software on Amazon EC2 instances within a virtual private cloud. + +Rubrik Cloud Cluster Elastic Storage (ES) for AWS or Azure runs on a single node, or it runs on three or more nodes. Rubrik CDM version 9.0.1 and later support single-node configuration. Rubrik does not support a two-node configuration. + +You can deploy a single-node cluster with either standard or extra-dense nodes. + +Multi-node clusters do not support mixing standard and dense nodes. + +Rubrik recommends using a single-node cluster when protecting workloads with 100 or fewer objects. The listed workloads do not support a single-node configuration. These workloads require using dense nodes: + + * NAS systems + * VMware Cloud on AWS + * Azure VMware Solution on Azure + +Nodes are instantiated through the AWS Management Console, using an AMI available from the AWS Marketplace. Data is temporarily stored in block storage until it can be moved to an S3 storage bucket. + *[ > ]: and then diff --git a/saas_aws_cloud_acc_setup.md b/saas_aws_cloud_acc_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..1e23b5c379e806a479a1f8ac3b0ba1d812bec4bb --- /dev/null +++ b/saas_aws_cloud_acc_setup.md @@ -0,0 +1,19 @@ +# AWS cloud account setup + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_cloud_acc_setup.html + +--- + +# AWS cloud account setup + +You can set up an AWS cloud account in RSC and start protecting your AWS workloads. + +Setting up an AWS cloud account in RSC to protect your AWS workloads involves detailed planning. This process includes: + + * Reviewing the recommendations from Rubrik for adding AWS cloud accounts. + * Reviewing the permission categories required to protect the AWS workloads. + * Evaluating various options for adding an AWS cloud account to ensure the choice aligns with your requirements, including direct account integration and advanced methods such as role chaining for multi-account environments. + * Performing the required prerequisites before adding AWS cloud accounts. + +After the planning is complete, you can proceed with adding your AWS cloud accounts to RSC. + *[ > ]: and then diff --git a/saas_aws_common_protection_terms.md b/saas_aws_common_protection_terms.md new file mode 100644 index 0000000000000000000000000000000000000000..e2399290d44127b497736bcc5e93d7e6fc6dec15 --- /dev/null +++ b/saas_aws_common_protection_terms.md @@ -0,0 +1,59 @@ +# Common AWS protection terms + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_common_protection_terms.html + +--- + +# Common AWS protection terms + +It is important to understand some common terms when protecting AWS workloads with RSC. + +By familiarizing yourself with common protection terms, you can better understand and navigate the steps and components involved in protecting AWS workloads. + +Term | Definition +---|--- +AWS account | A logical container for creating and managing AWS resources.The AWS account provides administrative capabilities for access control and billing, to organize and oversee permissions, security credentials, and the use of AWS services. This enables efficient management and governance of your cloud infrastructure. +AWS Management Console | A graphical interface to manage compute, storage, and other AWS cloud resources. +AWS region | A distinct geographical area independent from other regions in terms of location, power, cooling, and water supply, for high availability and fault tolerance. Each region comprises one or more availability zones, for added redundancy and reliability. +AWS Availability Zone (AZ) | A subset of an AWS region, except in the rare case where a region has only one AZ.AZs are discrete data centers in a region, with redundant power, networking, and connectivity. Network performance across AZs is typically high throughput and low latency. AZs are remote from each other, but usually within 60 miles within the region. +Virtual Private Cloud (VPC) | An Amazon service for provisioning a logically isolated section of the AWS cloud, where you can define your own virtual network.You have full control over this virtual network environment, to select IP address ranges, create subnets, and configure route tables and network gateways. +Subnet | A range of IP addresses in your VPC.You launch AWS resources, such as EC2 instances, into your subnets. You can connect a subnet to the internet, other VPCs, and your data centers, and route traffic to and from your subnets using route tables. +Security group | A virtual firewall for your AWS workloads, such as Amazon EC2 instances and Amazon RDS and Aurora databases, to control incoming and outgoing traffic.Inbound rules control the incoming traffic to your workload, and outbound rules control the outgoing traffic from your workload. When you launch a workload, you can specify one or more security groups. +Identity and Access Management (IAM) | An Amazon service that provides fine-grained access control across AWS accounts. You can specify who can access which AWS services and resources and under what conditions.AWS IAM is a fundamental security feature offering simple ways to secure AWS accounts and resources. +IAM policy | An object in AWS that defines permissions for IAM identities such as users, groups, or roles, and AWS resources.AWS users manage access by creating policies and attaching them to these identities or resources. When an IAM principal, such as a user or role, makes a request, AWS evaluates these policies to decide whether the request is allowed. +IAM role | An identity AWS users create in AWS, and to which they grant specific permissions.Trusted entities such as AWS services or accounts can use these roles. IAM policies attached to the roles dictate the actions an entity using the role can take. +Permissions policy | An IAM policy attached to an IAM role specifies the actions of an IAM principal, such as a user or AWS service, and the AWS resources it can access after assuming that role.AWS evaluates these permissions policies to determine whether a requested action is explicitly allowed or denied. +Trust policy | A policy document associated with an IAM role specifies which IAM principals, AWS accounts, or AWS services can assume that role.AWS evaluates trust policies to verify the identities of the entities authorized to assume that IAM role. +AWS Security Token Service (STS) | A web service you use to request temporary, limited-privilege credentials for IAM users or for users you authenticate, such as through your corporate network. These temporary credentials allow access to AWS services and resources.Rubrik uses AWS IAM roles with the minimum permissions needed to protect your AWS workloads. By setting up these roles through CloudFormation or manually, Rubrik can use the STS AssumeRole API call to request temporary credentials for secure interactions with your AWS resources. +Amazon Resource Name (ARN) | A string that uniquely identifies an AWS resource, such as EC2 instances, S3 buckets, or AWS accounts.AWS requires an ARN when you specify a resource unambiguously across the entire AWS environment, such as in IAM policies, Amazon RDS tags, and API calls. +AWS resource | Manageable items available through AWS, such as EC2 instances, EBS volumes, S3 buckets, RDS and Aurora databases, and VPCs. Resource groups, IAM roles, security groups, and tags are also considered resources. +Key Management Service (KMS) | A managed service that enables AWS users to create and control the keys used for cryptographic operations easily.This service is a highly available key generation, storage, management, and auditing solution allowing users to encrypt or digitally sign data in their applications or to control the encryption of data across AWS services. AWS creates and manages KMS keys, typically referred to as Default Keys, while users can create and manage their own keys, known as Customer Managed Keys (CMKs). +Amazon Elastic Cloud Compute (EC2) instance | A virtual server running in AWS.The instance size and type dictate the CPU, RAM, and other performance characteristics of the instance. Instances run in a subnet within virtual networks known as VPCs. Each subnet is associated with one AZ, so each instance runs within a single AZ. +Amazon Machine Image (AMI) | An AWS image file that contains the information necessary to launch an EC2 instance.An AWS user launching an instance through the AWS Management Console or the EC2 API must specify the AMI to be used for the launch. An AMI includes a list of EBS volume snapshots, permissions that control which AWS accounts can use the AMI, and a mapping file that specifies where the volumes corresponding to each EBS volume snapshot should be mounted. +Amazon Elastic Block Storage (EBS) volume | A block storage device that AWS users can connect to EC2 instances.Each EBS volume is automatically replicated within a single AZ to protect against hardware failures, but it is not replicated across different AZs or regions. Most EC2 instances have at least one EBS volume, known as the root volume, attached to them. The EC2 instances might also have additional data volumes attached to them. +Amazon Simple Storage Service (S3) | A public cloud storage resource provided by AWS that offers object-based storage. Data is stored in S3 buckets as distinct units called objects, rather than as traditional files. +Amazon S3 Scale to Billions | The capability of Amazon S3 to scale and accommodate billions of objects seamlessly, while maintaining consistent performance and reliability. It allows AWS users to store, manage, and retrieve any amount of data at any time. +Amazon Relational Database Service (RDS) | A managed relational database service that makes it easy to set up, operate, and scale a relational database in the AWS cloud.It provides cost-efficient, resizable capacity while automating time-consuming administration tasks such as hardware provisioning, database setup, patching, and backups. +Amazon Aurora | A MySQL and PostgreSQL-compatible relational database built for the AWS cloud, combining the performance and availability of high-end commercial databases with the simplicity and cost-effectiveness of open-source databases. +Simple Notification Service (SNS) | An Amazon service for setting up, operating, and sending notifications from the AWS cloud.It provides developers with a highly scalable, flexible, and cost-effective way to publish messages from an application and immediately deliver them to subscribers, such as Amazon SQS queues, AWS Lambda functions, email addresses, or other applications. +CloudFormation | An Amazon service that allows AWS users to model infrastructure and application resources using templates written in formats such as JSON or YAML.Users submit these templates to the CloudFormation service on AWS to create a collection of resources known as a stack. By managing stacks and their life cycles through CloudFormation, users can update a stack by modifying its template, or delete a stack to remove all of its associated resources automatically. +AWS Stack | A collection of AWS resources manageable as a single unit, created and managed using AWS CloudFormation templates.With a stack, you can deploy, update, or delete all the associated resources as a cohesive group within a single AWS account and region. +AWS StackSet | An AWS StackSet extends the capability of stacks by allowing you to create, update, or delete stacks across multiple AWS accounts and regions with a single operation.StackSets enable centralized management and deployment of resources, ensuring consistency and compliance across a broader AWS environment. +AWS workload | An AWS resource for which RSC can take a snapshot for data protection, such as an Amazon EC2 instance, EBS volume, Amazon S3, Amazon RDS and Aurora database, and AmazonDB. +AWS cloud account in RSC | An integration that enables RSC to interact with AWS workloads in an AWS account, allowing RSC to manage data protection, backup, recovery, and archiving services for these workloads deployed in AWS accounts. +Snapshot | Point-in-time copies of protected workloads, used for recovery or replication. +SLA Domain | A Rubrik feature you configure to define policies for data protection, including snapshot frequency, retention duration, and archiving and replication requirements. You can configure and apply these policies to workloads, ensuring consistent and automated data protection. +Exocompute | A Rubrik service that provides scalable and automated compute resources for running data operations, such as indexing, file recovery, application-consistent snapshots, and storage tiering. +AWS Organization | An AWS service that consolidates multiple AWS accounts for unified administration. It provides hierarchical framework to group accounts into Organizational Units (OUs) and apply protection policies to multiple accounts, simplifying governance, security, and compliance at scale. +Management account | An account that is used to create an AWS Organization. There is only one management account with the permissions to create and manage the AWS Organization. It handles the creation and removal of accounts from the organization, and manages policy assignments for OUs and individual accounts. Each management account can create multiple Delegated administrator account. +Delegated administrator account | A member account within an AWS Organization that has been authorized to manage specific AWS services on behalf of the management account. These accounts have the administrator permissions to manage the AWS Organizations. +Administrator account | An AWS account where you create StackSets. For StackSet using service-managed permissions, this account is either the management account associated with the organization or a delegated administrator account. +Target account | A specific AWS account where a StackSet deploys its stacks. It is the destination for the resources defined in the StackSet template. StackSets allow you to deploy the same CloudFormation stack across multiple target accounts simultaneously from a single, centralized administrative account. +StackSet instance | A stack in a target account within an AWS region. The StackSet instance is associated with only one stack set. +Service-managed permission model | A permission model that simplifies deployments by automatically creating the necessary AWS IAM roles for StackSets. These roles enable StackSets to deploy resources across accounts within the same AWS Organization and across different AWS regions. +Amazon DynamoDB | A fully managed NoSQL database service provided by AWS that supports key-value and document data structures. It is known for its scalability and performance, processing millions of requests each second. +Continuous backup | An Amazon DynamoDB feature that provides point-in-time recovery, allowing restoration to any point within a specific retention window. +Global tables | An Amazon DynamoDB feature that provides multi-region, multi-active replication for globally distributed applications. +Point-in-Time Recovery (PITR) | A DynamoDB feature that provides continuous backups and enables restoration to any point within a specified time window, typically up to 35 days. +Role chaining | An AWS IAM method that enables RSC to securely access multiple AWS accounts through an intermediary AWS account, simplifying secure management and rapid access revocation. + *[ > ]: and then diff --git a/saas_aws_dynamodb.md b/saas_aws_dynamodb.md new file mode 100644 index 0000000000000000000000000000000000000000..0a8e85db304ec01266b60e45b35534cc4ffb627b --- /dev/null +++ b/saas_aws_dynamodb.md @@ -0,0 +1,20 @@ +# Amazon DynamoDB + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_dynamodb.html + +--- + +# Amazon DynamoDB + +RSC secures Amazon DynamoDB tables with automated snapshots governed by SLA Domain policies. You can gain insights from detailed snapshot data and optimize resources using on-demand account refresh and AWS custom tags. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +After you have set up protection for Amazon DynamoDB tables, RSC begins taking automated snapshots of those tables based on the data protection policies you configured in the assigned SLA Domains. You can view detailed snapshot information on the Inventory page for AWS - DynamoDB. + +With RSC, you can: + + * Refresh an AWS account on-demand to retrieve the latest metadata. + * Add AWS custom tags to apply specific policies for cost allocation, financial management, and resource creation. + + *[ > ]: and then diff --git a/saas_aws_ec2_ebs_volume.md b/saas_aws_ec2_ebs_volume.md new file mode 100644 index 0000000000000000000000000000000000000000..859d1366858725a28f74e36c729ad935e092e3c6 --- /dev/null +++ b/saas_aws_ec2_ebs_volume.md @@ -0,0 +1,20 @@ +# Amazon EC2 instances and EBS volumes + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_ec2_ebs_volume.html + +--- + +# Amazon EC2 instances and EBS volumes + +After you set up protection for Amazon EC2 instances and EBS volumes, RSC takes automated snapshots of those instances and volumes based on the configured policies in SLA Domains. You can also take on-demand snapshots, refresh AWS accounts, and add AWS custom tags for better resource management. + +After you have completed the protection setup for Amazon EC2 instances and EBS volumes, RSC starts taking automated snapshots of those instances and volumes according to the data protection policies you configured in the assigned SLA Domains. You can view detailed snapshot information on the Inventory page for AWS - EC2 & Applications. Based on your requirements, you can take on-demand snapshots of your workloads and perform snapshot management tasks such as modifying retention policies and deleting snapshots. + +You can use RSC to do the following: + + * Refreshing an AWS account on-demand to retrieve the latest metadata. + * Adding AWS custom tags to implement specific policies for cost allocation, financial management, and resource creation. + * Enabling application-consistent backups to preserve the working state of applications running on a protected EC2 instance. + * Enabling Anomaly Detection for your AWS account to detect ransomware attacks in EC2 instances and EBS volumes. + + *[ > ]: and then diff --git a/saas_aws_key_features_protection.md b/saas_aws_key_features_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..0fca780576591c72ced07ee62de4ff25cc7fdf04 --- /dev/null +++ b/saas_aws_key_features_protection.md @@ -0,0 +1,81 @@ +# Key features for protecting AWS workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_key_features_protection.html + +--- + +# Key features for protecting AWS workloads + +RSC provides unified data management, automated global data protection, various recovery options for AWS workloads, and advanced security features to protect your workloads. + +The cloud-native protection that RSC provides for AWS workloads offers comprehensive features to streamline data management, enable quick recovery, and reduce costs. + +The key features of cloud-native protection for AWS workloads include: + + * Unified data management + * Automated global data protection through SLA Domains + * Storage tiering to reduce cloud storage costs + * Various recovery options for AWS workloads within or across regions + * Advanced security features, such as Data scanning and Anomaly Detection + * Multiple AWS account addition using AWS Organization + * Role chaining for secure, centralized access management across multiple AWS accounts. + +## Unified data management + +Feature | Description +---|--- +Rubrik Security Cloud | Provides a SaaS platform for hybrid and multicloud environments that does not require persistent resources in AWS accounts. +Consolidated monitoring and reporting | Provides unified reporting to track SLA Domain assignment, protection and recovery activities, and SLA Domain policy compliance. + +## Multiple AWS account addition using AWS Organization + +Feature | Description +---|--- +Multiple account discovery and addition | Provides an administrator with delegated administrator privileges the ability to query AWS Organizations to automatically discover all accounts and Organizational Units (OUs) within the organization. This capability facilitates the selection and onboarding of entire organizations, specific OUs, or a set of individual accounts simultaneously. +Permission update for multiple accounts | Enables you to update permissions for multiple accounts in RSC. +Migration for existing accounts | Provides a mechanism to migrate previously onboarded accounts to the AWS Organization model. +Role name customization | Supports the customization of role names and paths during both onboarding and update processes, maintaining customer preferences. + +## Automated global data protection with SLA Domains + +Feature | Description +---|--- +Global SLA Domains | Enforces data protection policies across object types and AWS accounts for simplified data protection management. +Account level protection | Automatically assigns SLA Domains to entire AWS accounts and makes sure that every AWS workload provisioned to the protected regions receives the required level of data protection without the need for individual assignments.You can override account-level SLA Domain assignments by using tag-based assignment or by directly assigning SLA Domains to AWS workloads. +Tag-based protection | Assigns SLA Domains to AWS workloads when specific tag keys or key-value pairs are found on an Amazon EC2 instance, EBS volume, Amazon S3, and Amazon RDS and Aurora databases in an AWS account in the specified scope. +Cross-region snapshot replication | Provides the ability to define target accounts, regions, and retention periods in an SLA Domain for automatic cross-region snapshot replication.RSC replicates snapshots created by that SLA Domain to the target region and expires them after the specified retention period has elapsed. +Storage tiering | Sends the compressed Amazon EC2 instance, EBS volume, or DynamoDB snapshots to a target Amazon S3 bucket and can make sure that their immutability meets the regulatory requirements.You can specify the target AWS account, region, and KMS key for data encryption and select the S3 storage class of the destination bucket, offering the possibility of reducing long-term protection costs. +Primary backup encryption for Amazon DynamoDB | Encrypts the snapshot data associated with Amazon DynamoDB tables based on the specified KMS key. To ensure successful encryption of the backed-up table data, the specified KMS key alias must be present and correctly configured in the target AWS account and the target AWS region. While different accounts and regions have unique underlying KMS keys, these accounts and regions can share a common KMS key alias for this purpose. When creating an SLA Domain for Amazon DynamoDB tables, you can configure primary backup encryption by providing a KMS key alias. You can retrieve this KMS key alias from your AWS account. + +## Recovery options + +Recovery option | Description +---|--- +EC2 instance export | Creates EC2 instances from snapshots, with options to define instance details and security settings. +EBS volume export | Creates encrypted or unencrypted EBS volumes using snapshots, with options to define volume type, size, and more. +EC2 instance restore | Rolls back EC2 instances to a known good state, preserving the InstanceId and private IP address. +File and folder download from a snapshot of EC2 instances and EBS volumes | Searches and downloads specific files or folders from the selected snapshots to an Amazon S3 bucket. +S3 bucket export | Exports a snapshot associated with an entire Amazon S3 bucket or individual objects to an existing S3 bucket. +S3 bucket restore | Restores an entire Amazon S3 bucket or individual objects to their source location. +RDS database export | Exports an on-demand, scheduled, or continuous snapshot of Amazon RDS databases to create a point-in-time copy of that database. +DynamoDB restore | Provides DynamoDB data continuity and resilience with robust recovery features. You can restore an entire DynamoDB table from a primary or an archived snapshot. For enhanced disaster recovery, RSC provides: + + * Cross-region Point-in-Time Recovery (PITR): Restores your table to any supported recovery point in time and provisions the new table in a different AWS region. + * Cross-region and cross-account snapshot recovery: Restores your table from a snapshot to a new destination in a different AWS region and a separate AWS account. + +After the table is recovered, RSC automatically encrypts the data using the specified KMS key. + +## Additional features + +Note: + +These features are not applicable for Amazon DynamoDB. + +Feature | Description +---|--- +Data scanning for AWS | Provides detailed and intelligent insights into your sensitive data. You can use these insights to measure the data security risk and proactively reduce it. You can enable Data scanning for AWS workloads to classify and gain a better understanding of the sensitive data. +Anomaly Detection | Detects ransomware attacks and other anomalous events to protect the data in Amazon EC2 instances, EBS volumes, and Amazon S3. +Application-consistent snapshots for Amazon EC2 instances | Provides the ability to create application-consistent snapshots using Volume Shadow Copy Service (VSS) or pre-snapshot and post-snapshot scripts with RSC. +AWS custom tags | Implements specific policies for cost allocation, financial management, and resource creation. +Role chaining | Provides a dedicated AWS account serving as a centralized gateway to securely manage multiple AWS accounts from a single administrative point. + *[ > ]: and then diff --git a/saas_aws_planning_protection.md b/saas_aws_planning_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..7549f5de6b6930017e920b2655a77b7201f46b20 --- /dev/null +++ b/saas_aws_planning_protection.md @@ -0,0 +1,14 @@ +# Planning for AWS protection + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_planning_protection.html + +--- + +# Planning for AWS protection + +Before setting up an AWS cloud account in RSC, it is necessary to plan the user and access management for designated RSC users. This planning also involves reviewing the permissions that RSC requires in your AWS environment to protect your AWS workloads. + +When planning AWS protection, understanding the Role-based Access Control (RBAC) mechanisms of RSC is important and establishing a clear framework for user and access management is necessary. This ensures secure and efficient operations within your AWS environment. You can start by categorizing your RSC users based on their roles and responsibilities and by assigning appropriate privileges through roles to limit access according to the principle of least privilege. + +Additionally, it is important that you review the specific permissions that RSC requires to protect your AWS workloads. Understanding these permissions helps explain why they are needed. This ensures clarity on the operations that protect your AWS workloads. + *[ > ]: and then diff --git a/saas_aws_protection_high_level_arch.md b/saas_aws_protection_high_level_arch.md new file mode 100644 index 0000000000000000000000000000000000000000..36112aac45b28f6dd93c13a75cb821be71fd44c5 --- /dev/null +++ b/saas_aws_protection_high_level_arch.md @@ -0,0 +1,12 @@ +# High-level architecture for AWS protection + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_protection_high_level_arch.html + +--- + +# High-level architecture for AWS protection + +A high-level architectural overview of how RSC protects AWS workloads and the RSC AssumeRole workflow. + +Rubrik implements various architectural strategies and workflows to protect AWS workloads. This includes detailing how the cloud-native protection for AWS workloads works, how RSC interfaces with your AWS account to establish a secure communication, and the specific protection mechanisms for Amazon RDS, Amazon DynamoDB, and Amazon S3. + *[ > ]: and then diff --git a/saas_aws_rds.md b/saas_aws_rds.md new file mode 100644 index 0000000000000000000000000000000000000000..1c85ed20c6640a991d7d5f2465b8acaba1443dd3 --- /dev/null +++ b/saas_aws_rds.md @@ -0,0 +1,23 @@ +# Amazon RDS and Aurora databases + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_rds.html + +--- + +# Amazon RDS and Aurora databases + +RSC protects the data and resources of Amazon RDS and Amazon Aurora databases. + +You can add an AWS cloud account to provide RSC access to specific Amazon RDS and Amazon Aurora databases. RSC provides protection through the implementation of rules and policies within SLA Domains. + +The onboarding workflow and utilization of RSC features remain consistent across all types of RDS databases, including Aurora databases. The Amazon RDS and Aurora databases documentation calls out any differences. + +The following table describes the features supported for Amazon RDS and Amazon Aurora databases. Feature | Amazon RDS (Non-Aurora) | Amazon Aurora +---|---|--- +Type of snapshots supported | Incremental snapshots | Non-incremental snapshots.RSC takes only a full snapshot of Aurora databases due to the limitation of AWS APIs. +Continuous backup | You can enable the continuous backup for point-in-time recovery feature in an SLA Domain and select a retention period between 0 and 35 days. | You can enable the continuous backup for point-in-time recovery feature in an SLA Domain.The minimum retention period for the continuous backups is 1 day. For example, you select the retention period as zero in the SLA Domain and assign this SLA Domain to Amazon RDS and Aurora databases. RSC retains the continuous backups of Aurora databases for 1 day regardless of the zero day configuration in the SLA Domain. The zero-day retention period will be valid only for RDS databases.If you do not assign an SLA Domain, RSC retains the continuous backups according to the retention period configured for the Aurora databases in the AWS console.After you assign an SLA Domain, the retention period configured in the SLA Domain overrides the retention period configured in the AWS console. +Archiving | RSC offers archiving capabilities for Amazon RDS PostgreSQL and Aurora PostgreSQL databases, supporting both long-term retention and instant archival. RSC ensures cost-efficient archival by storing your backup data in a more economical location. | RSC does not support archiving for Amazon Aurora databases. +Supported deployment types | Amazon RDS Multi-AZ and Amazon RDS Single-AZ | Amazon Aurora DB cluster and Amazon Aurora global databases.For Aurora global databases, in the Databases tab, you can view the primary and replica databases in the DB Instance Type column. +Supported database engines | MySQL, MariaDB, PostgreSQL, Oracle, and SQL Server | MySQL and PostgreSQL +Recovery of snapshots | RSC recovers the RDS database instance from the selected snapshot. | RSC recovers the primary DB (writer) instance and the Amazon Aurora DB cluster but not the Aurora replica (reader) instances. + *[ > ]: and then diff --git a/saas_aws_storage_tiering_setup.md b/saas_aws_storage_tiering_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..a2053d14cab460b2c7f6a3d1354eb475a105dd8f --- /dev/null +++ b/saas_aws_storage_tiering_setup.md @@ -0,0 +1,39 @@ +# AWS storage tiering setup + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_storage_tiering_setup.html + +--- + +# AWS storage tiering setup + +You can use AWS storage tiering to archive Amazon EC2 instance, EBS volume, or DynamoDB table snapshots that exceed a specified threshold to Amazon S3 storage classes. By archiving snapshots to these storage classes, you can optimize costs. + +Backups of certain workloads might need to be retained for an extended period, for example, more than a year. This is common in industries such as financial services, healthcare, and public sectors, where snapshots must be retained for several years to meet regulatory and compliance requirements. You can leverage AWS storage tiering to optimize costs by archiving Amazon EC2 instance, EBS volume, or DynamoDB table snapshots to low-cost Amazon S3 storage classes such as Amazon S3 Standard, S3 Standard-Infrequent Access (S3-IA), and S3 One Zone-Infrequent Access (S3 Z-IA). + +You can use AWS storage tiering to move all weekly, monthly, or annual backups with extended retentions of more than one year to the cooler storage classes to manage costs. + +Important: + +RSC does not support the archival of application-consistent snapshots of EC2 instances when using the centralized Exocompute configuration. + +## Support for EC2 marketplace workloads + +RSC supports archiving snapshots of EC2 marketplace workloads (EC2 instance and EBS volume) and recovering files or folders from the snapshots of these workloads through the direct read APIs. This helps overcome the limitations previously imposed by AWS regulations on regular volume mounting processes for EC2 marketplace workloads. + +## Tiered snapshots immutability + +RSC supports AWS immutability to protect the tiered snapshots against accidental deletion or malicious activity such as ransomware attacks. RSC leverages the AWS S3 Object Lock feature for immutable data, which locks the S3 object data with a Write-Once, Read-Many (WORM) lock for a specified interval. After the AWS S3 Object Lock feature is set, you can read and create objects but cannot modify or delete objects until the retention period expires. The retention period for the snapshots is managed through the SLA Domains. For example, if you specify the retention period as five weeks in the SLA Domain, the snapshot stays in the immutable state for five weeks. + +Note: + + * The AWS immutability works only when S3 Versioning and Object Lock are enabled on the Amazon S3 bucket. RSC enables S3 Versioning and Object Lock when creating the S3 bucket. + * AWS storage tiering leverages the compliance mode of S3 Object Locking, which ensures that data cannot be overwritten or deleted by any user, including administrators. Compliance mode is a configuration for S3 Object Lock that maintains a WORM state, conforming to regulatory and compliance requirements. + +AWS immutability provides the following advantages: + + * Prevents deletion or modification of tiered snapshots from the S3 bucket. + * Provides protection against insider malicious activity, for example, administrators modifying or deleting the snapshots. + +This ensures retrieval of backup data in the archival location for a set period in case of malicious activity, until the lock or the retention configured in the SLA Domain expires. + + *[ > ]: and then diff --git a/saas_aws_tags.md b/saas_aws_tags.md new file mode 100644 index 0000000000000000000000000000000000000000..c62735184b30984641b5227dda85c07e077b43d3 --- /dev/null +++ b/saas_aws_tags.md @@ -0,0 +1,136 @@ +# AWS tags + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_tags.html + +--- + +# AWS tags + +RSC attaches specific tags to the AWS resources you create using RSC. + +The following table lists the tags attached to the EBS Volume snapshot. Tag key | Tag value +---|--- +Name | Rubrik-Snapshot_snapshot-creation-time-mils_ebs-volume-native-id_UUID +rk_aws_native_account_id | UUID assigned by RSC to the source AWS account +rk_component | Cloud Native Protection +rk_object | EBS Backup +rk_snapshot_type | Primary, Replica, Replica Intermediate, or Transient EBS +rk_sla_name | Name of the assigned SLA Domain +rk_source_volume_native_id | AWS native ID for the source EBS Volume +rk_source_volume_native_name | Name of the source EBS Volume in the AWS Management console +rk_taskchain_id | RSC UUID for the source task chain +rk_gc_leaked_resource | True or FalseIndicates whether the resource is required and whether the garbage collection task cleans the resource. +rk_gc_creation_time | Timestamp when the rk_gc_leaked_resource tag was set to true. +rk_on_demand_snapshot_sla_id | SLA ID corresponding to the SLA Domain assigned to the on-demand snapshot +rk_reencryption_active | True or FalseThis tag is attached to the re-encrypted intermediate snapshots taken during the cross-account replication. + +The following table lists the tags attached to AWS S3 buckets corresponding to AWS archival locations. Tag key | Tag value +---|--- +rk_storage_setting | Name of the archival location +rk_aws_native_account_name | Name of the AWS cloud account that corresponds to the archival location +rk_object | Archival Storage +rk_component | Cloud Native Protection +rk_aws_native_account_id | UUID assigned by RSC to the source AWS account +rk_polaris_account | RSC account name of the customer +rk_storage_setting_id | Internal ID corresponding to the archival location + +The following table lists the tags attached to the EC2 instance snapshot. Tag key | Tag value | Attached to +---|---|--- +AMI Name | Rubrik-Snapshot_snapshot-creation-time- mils_ec2-instance-id_UUID | AMI snapshot +rk_source_volume_native_id | AWS native ID for the source EBS Volume | EBS snapshot +rk_source_volume_native_name | Name of the source EBS Volume | EBS snapshot +rk_aws_native_account_id | UUID assigned by RSC to the source AWS account | AMI and EBS snapshots +rk_component | Cloud Native Protection | AMI and EBS snapshots +rk_gc_leaked_resource | True or False | AMI and EBS snapshots +rk_object | EC2 Backup | AMI and EBS snapshots +rk_sla_name | Name of the assigned SLA Domain | AMI and EBS snapshots +rk_snapshot_type | Primary | AMI and EBS snapshots +rk_source_vm_native_id | AWS native ID for the source EC2 instance | AMI and EBS snapshots +rk_source_vm_native_name | Name of the source EC2 instance in the AWS Management console | AMI and EBS snapshots +rk_taskchain_id | RSC UUID of the source task chain | AMI and EBS snapshots +rk_on_demand_snapshot_sla_id | SLA ID corresponding to the SLA Domain assigned to the on-demand snapshot | AMI and EBS snapshots +rk_is_ami_based | True or FalseChecks whether the snapshot is crash consistent. | AMI and EBS snapshots +rk_gc_creation_time | Snapshot Creation Time | AMI and EBS snapshots +rk_image_native_id | Native ID of the image created on AWS for the EC2 instance backup | EBS snapshots + +The following table lists the tags attached to the replica snapshot. Tag key | Tag value | Attached to +---|---|--- +AMI Name | Rubrik-Snapshot_snapshot-creation-time- mils_ec2-instance-id_UUID | AMI snapshot +rk_aws_native_account_id | UUID assigned by RSC to the source AWS account | AMI and EBS snapshots +rk_component | Cloud Native Protection | AMI and EBS snapshots +rk_object | EC2 Backup or EBS Backup | AMI and EBS snapshots +rk_snapshot_type | Primary, Replica, or Replica Intermediate | AMI and EBS snapshots +rk_sla_name | Name of the assigned SLA Domain | AMI and EBS snapshots +rk_gc_creation_time | Snapshot Creation Time | EBS Snapshot +rk_gc_leaked_resource | False | AMI and EBS snapshots +rk_source_vm_native_id | AWS native ID for the source EC2 instance | AMI and EBS snapshots +rk_source_vm_native_name | Name of the source EC2 instance in the AWS Management console | AMI and EBS snapshots +rk_source_volume_native_id | AWS native ID for the source EBS Volume | EBS snapshot +rk_source_volume_native_name | Name of the source EBS Volume | EBS snapshot +rk_taskchain_id | RSC UUID of the source task chain | AMI and EBS snapshots + +The following table lists the restore detached EBS volume tags. Tag key | Tag value +---|--- +rk_detached_by | Name of the task that detached this volume +rk_detached_from | Instance ID and path of the device from which the volume was detached +rk_detached_time | The UTC time when the volume was detached +rk_component | Cloud Native Protection +rk_object | Detached EBS Volume +rk_taskchain_id | RSC UUID of the source task chain +rk_user | RSC user who triggered the restore operation +rk_source_snapshot_native_id | Resource ID of the AMI that you used to trigger the restore operation +rk_restore_source_region | Source region of the snapshot that you used for the restore operation + +The following table lists the restored EC2 instance and EBS volume tags. Tag key | Tag value +---|--- +rk_restore_timestamp | The UTC time when the restore operation was initiated +rk_user | RSC user who triggered the restore operation +rk_source_snapshot_native_id | Resource ID of the AMI that you used to trigger the restore operation +rk_restore_source_region | Source region of the snapshot that you used for the restore operation +rk_taskchain_id | RSC UUID of the source task chain +rk_aws_native_account_id | AWS account ID on RSC +rk_component | Cloud Native Protection +rk_object | Restored EC2 instance or EBS volume +rk_source_vm_native_id | AWS native ID of the restored EC2 instance + +The following table lists the exported EC2 instance and the related EBS volume tags. Tag key | Tag value +---|--- +Name | Assigned name of the exported EC2 instance +rk_aws_native_account_id | AWS account ID on RSC +rk_export_source_region | Source region of the snapshot +rk_export_timestamp | The UTC time when you initiated the export operation +rk_source_snapshot_native_id | AWS native ID of the source snapshot for this EBS volume +rk_source_vm_native_id | AWS native ID of the source EC2 instance +rk_source_vm_native_name | Name of the source EC2 instance in the AWS Management console +rk_user | RSC user who triggered the export operation +rk_taskchain_id | RSC UUID of the source task chain +rk_gc_leaked_resource | True or False +rk_gc_creation_time | Time when the rk_gc_leaked_resource tag was set to true +rk_component | Cloud Native Protection +rk_object | Exported EC2 instance or EBS Volume of the exported EC2 instance + +The following table lists the exported detached EBS volume tags. Tag key | Tag value +---|--- +rk_detached_by | export-volume +rk_detached_from | Instance ID and mount point from which the volume was detached +rk_detached_time | The UTC time when the volume was detached +rk_component | Cloud Native Protection +rk_object | Detached EBS Volume +rk_taskchain_id | RSC UUID of the source task chain +rk_user | RSC user who triggered the export operation +rk_source_snapshot_native_id | Resource ID of the AMI that you used to trigger the export operation +rk_restore_source_region | Source region of the snapshot that you used for the export operation + +The following table lists the exported EBS volume tags. Tag key | Tag value +---|--- +Name | Assigned name of the exported EBS volume +rk_aws_native_account_id | AWS account ID on RSC +rk_export_source_region | Source region of the snapshot +rk_export_timestamp | The UTC time when you initiated the export operation +rk_source_snapshot_native_id | AWS native ID of the source snapshot for this EBS volume +rk_source_volume_native_id | AWS native ID of the source EBS volume +rk_user | Email ID of the RSC user who triggered the export operation +rk_component | Cloud Native Protection +rk_object | Exported EBS Volume +rk_taskchain_id | RSC UUID of the source task chain + *[ > ]: and then diff --git a/saas_aws_workload_recovery.md b/saas_aws_workload_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..eae9d6eb6e25cf56ceb1dc3fcacb67221075a995 --- /dev/null +++ b/saas_aws_workload_recovery.md @@ -0,0 +1,12 @@ +# AWS workloads recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_workload_recovery.html + +--- + +# AWS workloads recovery + +After RSC takes snapshots of your AWS workloads, you can recover the required workloads. + +After you complete the protection setup for your AWS workloads, RSC starts protecting your data by taking snapshots based on the configured policies in the assigned SLA Domains. You can recover the workloads from these snapshots using various recovery options based on your specific requirements. Rubrik recommends that you familiarize yourself with the various recovery options to ensure that your choice aligns with your recovery requirements. + *[ > ]: and then diff --git a/saas_aws_workloads.md b/saas_aws_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..20257826a229e3d6a5447379a34e06e95b089f29 --- /dev/null +++ b/saas_aws_workloads.md @@ -0,0 +1,23 @@ +# Amazon Web Services workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_workloads.html + +--- + +# Amazon Web Services workloads + +RSC protects the following types of Amazon Web Services workloads: EC2 instances, EBS volumes, Amazon S3, Amazon RDS and Aurora databases, and Amazon DynamoDB. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +As organizations expand their use of Amazon Web Services (AWS), they encounter new complexities in protecting, managing, and securing their data. Complex deployments can be at greater risk of threats to data integrity and operational stability, putting businesses at risk of data breaches, accidental data loss, and ransomware attacks. The Shared Responsibility Model established by AWS makes it clear that, while AWS secures the infrastructure, the ultimate responsibility for application and data protection rests with the organization. + +Rubrik provides a streamlined, SaaS-based solution to these challenges with Rubrik Security Cloud (RSC). RSC secures and automates data protection processes for AWS workloads, making sure that data remains protected against accidental deletions, ransomware attacks, and other potential threats. With RSC, organizations can automate backup, recovery, and replication schedules across AWS accounts and regions using global SLA Domain policies that allow organizations to align data protection seamlessly with business requirements. + +Protecting AWS workloads with RSC involves an approach that makes sure that data is comprehensively and consistently protected across the cloud infrastructure of an organization. By breaking down the tasks into three main categories, Authorization, Configuration, and Protection, RSC simplifies the steps required to protect AWS workloads. Each category addresses specific aspects of data security, from granting secure access to applying global policies that enable comprehensive cyber resiliency. + +Task category | Description +---|--- +Authorization | For authorization, you grant RSC secure access to your AWS accounts that need protection. You can achieve this through temporary credentials with an assumed IAM role and the automatic sharing of any required encryption keys, as needed. +Configuration | For configuration, you set up SLA Domains to protect AWS workloads automatically, according to your business objectives.Using SLA Domains, you can define and manage data protection policies uniformly across different regions. +Protection | For protection, you enforce data security by assigning SLA Domains to AWS workloads. If the situation arises, RSC provides quick recovery options for Amazon EC2 instances, EBS volumes, Amazon S3, Amazon RDS and Aurora databases, Amazon DynamoDB, and individual files within or across regions. diff --git a/saas_aws_workloads_protection_setup.md b/saas_aws_workloads_protection_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..b28681ac093278757bd294133b8ffea61a50047a --- /dev/null +++ b/saas_aws_workloads_protection_setup.md @@ -0,0 +1,21 @@ +# AWS workloads protection setup + +Source: https://docs.rubrik.com/en-us/saas/saas/aws_workloads_protection_setup.html + +--- + +# AWS workloads protection setup + +You can set up SLA Domains to apply data protection policies, ensuring automatic and hierarchical protection of AWS accounts and individual AWS workloads, with granular control overriding higher-level assignments. + +In cloud data protection, ensuring that your AWS workloads are secure and recoverable is essential. Rubrik SLA Domains offer a structured way to apply data protection policies across various AWS workloads, ensuring consistent and reliable backup and recovery processes. An SLA Domain is a set of policies that defines the backup and recovery objectives for your data. These policies specify the frequency of snapshots, the retention period for these snapshots, and the archiving and replication requirements. + +By assigning SLA Domains to AWS workloads, you ensure that your data protection strategies align with your organizational requirements and compliance standards. RSC enables hierarchy-based, automatic protection of AWS workloads. This automatic protection mechanism simplifies the protection of large numbers of workloads. + +After you add an AWS account to RSC, you can create one or more customized SLA Domains to begin protecting AWS workloads. Although RSC provides Gold, Silver, and Bronze SLA Domains, these defaults may not fully meet the specific requirements of your organization. Creating customized SLA Domains allows for precise control over snapshot frequency, retention periods, and archival policies, ensuring alignment with your organizational and compliance standards. After creation, you can assign these customized SLA Domains to different AWS entities. RSC then starts creating, archiving, replicating, and expiring snapshots to protect the relevant workloads based on the parameters defined in the assigned SLA Domain. + +The following table summarizes where you can assign an SLA Domain: Entity | Description +---|--- +AWS account | Assigning SLA Domain settings at the account level for managing protection policies for the associated workloads. +Individual AWS workload | Assigning SLA Domain settings to a specific AWS workload, such as EC2 instances, EBS volumes, S3 buckets, RDS and Aurora databases, and Amazon DynamoDB for granular control. + *[ > ]: and then diff --git a/saas_azr_cloud_acc_setup.md b/saas_azr_cloud_acc_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..3ce5e9adcfeae1ccfd11f3131174ad4265145c80 --- /dev/null +++ b/saas_azr_cloud_acc_setup.md @@ -0,0 +1,23 @@ +# Set up Azure cloud accounts + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_cloud_acc_setup.html + +--- + +# Set up Azure cloud accounts + +You can set up an Azure cloud account in RSC to start protecting Azure workloads. + +Setting up an Azure cloud account in RSC to protect Azure workloads involves detailed planning, including: + + 1. Referring to the Rubrik recommendations for adding Azure cloud accounts, as described in [Recommendations for adding Azure cloud accounts](azr_recommendations_add_cloud_acc.html "Rubrik recommends specific actions and best practices for adding Azure cloud accounts to RSC."). + 2. Learning about the permission categories and how to implement the least-permission model for enhanced security, as described in [Permission categories for Azure workloads](azr_permission_categories.html "For tasks that operate on Azure workloads, such as indexing, recovery, and storage tiering, RSC requires specific permissions. RSC groups these permissions into categories for granular management so that you can include or exclude these categories as required."). + 3. Evaluating various options for adding an Azure cloud account to ensure the choice aligns with your requirements, as described in [Evaluate Azure cloud account setup options](azr_evaluate_options_cloud_acc_setup.html "When adding an Azure cloud account to RSC, it is important to evaluate the available options for adding the account, including data scanning capabilities."). + 4. Understanding the Azure policy restrictions that can interface with RSC operations, as described in [Azure policy restrictions](azure_policy_restrictions.html "Azure policies can obstruct RSC operations such as storage account creation. Knowing how to adjust these policies is crucial for maintaining both security and compliance."). + +After the planning is complete, you can proceed with adding your Azure cloud account to RSC. For more information, see [Configure Azure cloud accounts](azr_configuration_cloud_acc.html "Start the configuration of your Azure cloud accounts by adding them to RSC and performing other maintenance operations, such as editing and upgrading accounts."). + +Note: + +After you configure Azure cloud accounts, the next step is to [Set up Exocompute on Azure](azr_exocompute.html "With the Exocompute on Azure feature, RSC launches an Azure Kubernetes Service cluster to perform various operations to protect Azure workloads. RSC uses the Azure Kubernetes Service cluster to serve as a compute resource in your Azure subscription."). + *[ > ]: and then diff --git a/saas_azr_common_protection_terms.md b/saas_azr_common_protection_terms.md new file mode 100644 index 0000000000000000000000000000000000000000..cd229b58bbc018c90548b6ba0202e78667c4d59f --- /dev/null +++ b/saas_azr_common_protection_terms.md @@ -0,0 +1,38 @@ +# Common Azure protection terms + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_common_protection_terms.html + +--- + +# Common Azure protection terms + +It is important to understand some common terms when protecting Azure workloads with RSC. + +By familiarizing yourself with the common terms, you can better understand and navigate the various steps and components involved in protecting Azure workloads. + +Term | Definition +---|--- +Azure tenant | A dedicated instance of Microsoft Entra ID that an organization automatically creates when subscribing to a Microsoft cloud service, such as Azure, Intune, or Office 365. It represents a single isolated environment for an organization, housing subscriptions and resources that can be protected through services such as RSC cloud-native protection for Azure.Tenants can operate in either a single-tenant or a multitenant environment. In the context of RSC, an Enterprise App Registration in a Rubrik-owned Azure tenant, trusted by your Azure tenant, is used to make necessary API calls for protecting Azure workloads. The snapshots remain within the customer-owned subscription and only metadata is stored in RSC. +Microsoft Entra ID | Each Azure tenant includes a dedicated, trusted Microsoft Entra ID that contains users, groups, and applications of the tenant, and is used for identity and access management of tenant resources.When protecting Azure resources, RSC establishes a two-way trust between the Microsoft Entra ID App Registration specific to you in the Rubrik Azure tenant and a Service Principal in your Azure subscription, with a custom role assigned for required permissions. This setup ensures secure and efficient API interactions necessary for protection tasks. +Azure subscription | A logical container for the resources you provision in Azure, holding the details of all resources such as virtual machines and databases. Creating a subscription is the first step in adopting Azure, and each resource is associated with only one subscription. +Enterprise App Registration (Service Principal) | An entity within your Microsoft Entra ID tenant that governs how applications, such as RSC, connect to Microsoft Entra ID. It represents the instance of the application in your directory, with permissions managed through role assignments at the subscription level. This setup ensures secure and controlled access to Azure resources in your environment. +Azure workload | An Azure resource for which RSC can take a snapshot for data protection, such as an Azure virtual machine, managed disk, Azure Blob Storage, Azure SQL Database, or Azure SQL Managed Instance. +Azure resource | A manageable item available through Azure is referred to as a resource, with examples including virtual machines, storage accounts, web apps, databases, and virtual networks. Resource groups, subscriptions, management groups, and tags are also considered resources. +Azure region | A set of datacenters, deployed within a latency-defined perimeter and connected through a dedicated regional low-latency network. +Azure availability zone | Unique physical locations within an Azure region that offer high availability to protect your applications and data from datacenter failures. Each zone consists of one or more datacenters equipped with independent power, cooling, and networking.The physical separation of availability zones within a region protects applications and data from facility-level issues. Zone-redundant services replicate your applications and data across Azure availability zones to safeguard them from single points of failure. +Azure Virtual Network (VNet) | A logically isolated network in Azure that enables secure communication between Azure services, on-premises infrastructure, and the internet. It allows you to segment and manage your network with subnets, route tables, and network security groups. +Subnet | A range of IP addresses within a VNet.You can divide a VNet into multiple subnets for organizational and security purposes, and each NIC in a virtual machine is connected to a single subnet within that virtual network. +Network security group | Security rules that allow or deny inbound and outbound network traffic to various types of Azure resources. For each rule, you can specify the source and destination, port, and protocol. +Azure storage account | A cloud-based storage service that holds all of your Azure storage data objects, including blobs, files, queues, tables, and disks.It provides a unique namespace for your data, accessible worldwide over HTTP or HTTPS, ensuring data durability, high availability, security, and scalability. This allows you to efficiently manage and store large amounts of unstructured data in the cloud. +Shared Access Signature (SAS) URI | A Uniform Resource Identifier (URI) that grants secure delegated access to resources in an Azure storage account without compromising data security. It allows you granular control over client access, specifying which resources can be accessed, the permissions granted, and the duration of access. SAS URIs, known as ad hoc SAS, include specified start and expiry times, as well as permissions directly within the SAS URI. +Azure role (Role definition) | A collection of permissions and is typically called a role.It lists the operations that you can perform, such as read, write, and delete. Roles can be high-level, like the Owner role, or specific, such as the Virtual Machine Reader role. You can use these roles to delegate permissions to users, groups, or service principals within an Azure subscription or resource group. +Resource group | A logical container that holds related resources for an Azure solution, allowing you to manage them as a group. You decide which resources belong in a resource group based on the organizational structure and management requirements. +Azure cloud account in RSC | An integration that enables RSC to interact with Azure workloads in an Azure subscription, allowing RSC to manage data protection, backup, recovery, and archival services for these workloads deployed in Azure subscriptions. +Open Authorization (OAuth) | A standard designed to allow a website or application to access resources hosted by other web applications on behalf of a user. When adding an Azure cloud account to RSC, OAuth enables RSC to authenticate and securely access Azure resources by obtaining an access token. This token permits RSC to perform actions on behalf of the user without directly handling user credentials. +Exocompute | A Rubrik service that provides scalable and automated compute resources for running data operations, such as indexing, file recovery, application-consistent snapshots, storage tiering, and Azure SQL immutable backups. +Snapshot | Point-in-time copies of protected workloads, used for recovery or replication. +Archival location | Customer-defined storage configurations known as archival locations and utilized by RSC. These archival locations specify the subscription and Azure storage accounts used for Azure storage tiering.These configurations include attributes necessary for protecting Azure virtual machines, such as the subscription, region, tier, redundancy level, and encryption. Once created, you can use archival locations to configure an SLA Domain with Azure storage tiering enabled. +Rubrik Cloud Vault (RCV) | A secure and air-gapped vault service provided by Rubrik to enhance the cyber-resilience of your data by creating isolated copies. RCV supports Azure virtual machines, allowing you to leverage this service for your cloud-based data protection needs. +SLA Domain | A Rubrik feature that you configure to define policies for data protection, including snapshot frequency, retention duration, and archiving and replication requirements. It allows you to configure and apply these policies to workloads, ensuring consistent and automated data protection. +Data scanning | A Rubrik feature that you configure for an Azure subscription to scan and classify sensitive data within your Azure workloads. + *[ > ]: and then diff --git a/saas_azr_exocompute.md b/saas_azr_exocompute.md new file mode 100644 index 0000000000000000000000000000000000000000..ec6ca86a9e165f26863810f45243bf3c281bdb6c --- /dev/null +++ b/saas_azr_exocompute.md @@ -0,0 +1,51 @@ +# Set up Exocompute on Azure + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_exocompute.html + +--- + +# Set up Exocompute on Azure + +With the Exocompute on Azure feature, RSC launches an Azure Kubernetes Service cluster to perform various operations to protect Azure workloads. RSC uses the Azure Kubernetes Service cluster to serve as a compute resource in your Azure subscription. + +The Exocompute on Azure feature of RSC uses a container-based framework and is designed to perform various data processing tasks in your Azure environment. By leveraging Azure Kubernetes Service (AKS), Exocompute manages compute resources to perform essential operations, such as file indexing, file recovery, application-consistent backups, and storage tiering. + +## Key operations of Exocompute + +Exocompute uses AKS to perform the following operations: + + * File indexing: When you enable the file search feature for a virtual machine or a managed disk, each new backup of the virtual machine or managed disk initiates a file indexing operation. + * File recovery: When you initiate a recovery operation for the files in the backup of a virtual machine or a managed disk, RSC launches an AKS cluster to read the file data from the backup. + * Application-consistent backups: When you turn on application-consistent backups for virtual machines, RSC launches a temporary Exocompute instance to coordinate backup activity with the Rubrik Backup Service (RBS) agent installed on the Azure virtual machine. + * Azure storage tiering: When a snapshot reaches the archival threshold specified in the SLA Domain, RSC launches an AKS cluster to tier the snapshot to the specified storage. + +## AKS Integration + +Exocompute leverages AKS to launch an AKS cluster to manage Exocompute nodes. The AKS cluster consists of two types of nodes: + + * Master node: Orchestrates the lifecycle of the worker nodes, launches worker nodes, assigns jobs to them, and terminates them, as required. No Rubrik logic is executed within the master node. + * Worker nodes: Executes the core logic for tasks such as file search, file recovery, and application-consistent backups. Worker nodes are launched as a node pool with a minimum of one node. Based on the Azure workload requirements, additional worker nodes may be launched automatically. + +Based on the requirements, Exocompute automatically creates, scales, and destroys these AKS clusters and nodes to minimize costs. + +## Private AKS clusters + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Exocompute deploys the AKS cluster as a private cluster, which ensures that network traffic between the control plane of the cluster or API server and node pools remains within the VNet of the cluster. Additionally, the API server is accessible only from within the VNet and not over the internet. For more information about the configurations you need to perform for a successful AKS cluster deployment, see [Private AKS clusters](azr_pvt_aks_clusters.html "Private AKS clusters enable secure in-VNet communication between the control plane and node pools, restricting API server access to the VNet. They manage a private DNS zone by default but can be configured with a custom DNS zone for specific network needs."). + +## Resource groups in AKS + +When Exocompute launches an AKS cluster in your Azure subscription, Azure automatically creates and configures an AKS control plane. The Azure platform manages the AKS control plane, which handles the Exocompute nodes for running the operations, such as file indexing, file recovery, application-consistent backups, and storage tiering. The AKS architecture utilizes various Azure infrastructure resources, such as Virtual Machine Scale Sets, virtual networks, and managed disks. These integrations enable you to use many of the core capabilities of the Azure platform within the managed Kubernetes environment provided by AKS. + +To set up this architecture, when Exocompute launches an AKS cluster, the following two resource groups are created: + + * Kubernetes service resource group: RSC creates this group, which contains only the Kubernetes service resource. + * Node resource group: AKS automatically creates this group. It contains all the infrastructure resources associated with the AKS cluster, such as the Kubernetes nodes, virtual networking, and storage. By default, the node resource group is named MC___. For example, if your AKS cluster is called myAKSCluster, it resides in the resource group named myResourceGroup, and is located in the eastus region, then the node resource group is named MC_myResourceGroup_myAKSCluster_eastus. When Exocompute deletes the AKS cluster, AKS automatically deletes the node resource group. + +For more information about the resource groups, see [Why are two resource groups created with AKS?](https://learn.microsoft.com/en-us/answers/questions/25725/why-are-two-resource-groups-created-with-aks). + +Note: + +After you configure Exocompute on Azure, the next step is to [Set up Azure storage tiering](azr_storage_tiering_setup.html "You can use Azure storage tiering to archive Azure virtual machine or managed disk snapshots, which are older than a specified threshold, to Azure storage access tiers. By archiving snapshots to these access tiers, you can optimize cost."). + *[ > ]: and then diff --git a/saas_azr_key_features_protection.md b/saas_azr_key_features_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..51bc7164f4c04642a09becc299859f3439d87b6d --- /dev/null +++ b/saas_azr_key_features_protection.md @@ -0,0 +1,69 @@ +# Key features for protecting Azure workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_key_features_protection.html + +--- + +# Key features for protecting Azure workloads + +RSC provides unified data management, automated global data protection, various recovery options for Azure workloads, and additional security features to protect your workloads. + +The cloud-native protection that RSC provides for Azure workloads offers comprehensive features to streamline data management, ensure quick recovery, and reduce costs. RSC integrates with Azure environments, providing automation, enhanced security, and simplified management. + +The key features of cloud-native protection for Azure workloads include: + + * Unified data management + * Automated global data protection through SLA Domains + * Immutable backup copies + * Indexed backups for file or object-level recoveries + * Various recovery options for Azure workloads within or across regions + * Additional features, such as data scanning, Anomaly Detection, application-consistent snapshots, and Azure custom tags + +## Unified data management + +Feature | Description +---|--- +Rubrik Security Cloud | Provides a SaaS platform for hybrid and multicloud environments that does not require persistently running resources in Azure subscriptions. +Consolidated monitoring and reporting | Provides unified reporting to track SLA Domain assignment, protection and recovery activity, and SLA Domain policy compliance. + +## Automated global data protection with SLA Domains + +Feature | Description +---|--- +Global SLA Domains | Enforces data protection policies across object types and accounts for simplified data protection management. +Subscription and resource group protection | Automatically assigns SLA Domains to entire Azure subscriptions and Azure resource groups and ensures that every Azure workload provisioned to the protected regions receives the required level of data protection without the need for individual assignments.You can override subscription- and resource group-level SLA Domain assignments by using tag-based assignment or by directly assigning SLA Domains to Azure workloads. +Tag-based protection | Assigns SLA Domains to Azure workloads when specific tag keys or key-value pairs are found on an Azure virtual machine, managed disk, Blob Storage, or Azure SQL workload in an Azure subscription in the specified scope. +Cross-region snapshot replication | Provides the capability to define target accounts, regions, and retention periods in an SLA Domain for automatic cross-region snapshot replication.RSC replicates any snapshots created by that SLA Domain to the target region and expires them after the specified retention period has elapsed. +Storage tiering | Sends compressed Azure virtual machine snapshots to a target Azure storage account and can ensure their immutability to meet the requirements of any regulatory standards.You can specify the subscription of the target storage account, region, and select the storage tier, redundancy level, and encryption to potentially reduce long-term protection costs. + +## Recovery options + +Recovery option | Description +---|--- +Azure virtual machine export | Creates an Azure virtual machine from the selected snapshot using either the original snapshot in the source region or a replica in another region.You can define the virtual machine details and security settings. Also, you can include or exclude tags that were on the source virtual machine at the time the snapshot was taken from the export operation. +Managed disk export | Creates a managed disk from the selected snapshot using either the original snapshot in the source region or a replica in another region.You can define the managed disk details and security settings. Also, you can include or exclude tags that were on the source managed disk at the time the snapshot was taken from the export operation. +Azure virtual machine restore | Rolls back Azure virtual machines to a known good state, preserving resourceId and private IP address. +Azure virtual disk mount | Mounts the Azure virtual disks to the source virtual machine or a different virtual machine running in another region or subscription. +File and folder download | Searches and downloads specific files or folders from the selected snapshots of an Azure virtual machine or managed disk to an Azure storage account. +In-place file recovery | Recovers Azure files from an indexed snapshot either to a source virtual machine or a different virtual machine or exports the files to a different virtual machine. +Azure Blob restore | Restores an individual Azure Blob from a snapshot to recover an Azure Blob to an alternative storage location or overwrite an Azure Blob with a blob selected from a snapshot. +Azure Blob-Storage account restore | Restores an entire Azure Blob Storage account in disaster situations to ensure data integrity. +Azure SQL recovery from Rubrik backups | + + * Recover to database: Recovers workloads by exporting backup data to the required server. + * Download BACPAC file: Uploads the BACPAC file of an Azure SQL Managed Instance snapshot to a target storage account so that you can download the file from this storage account. + + +Azure SQL restore | Restores an Azure SQL workload to a point in time using the short-term retention backups. +Azure SQL export | Recovers an Azure SQL workload by exporting a long-term retention backup. + +## Additional features + +Feature | Description +---|--- +Data Observability for Azure virtual machines and managed disks | Detects ransomware attacks and other anomalous events and identifies sensitive data in backups to protect the data in your virtual machines and managed disks. +Data scanning | Discovers and classifies sensitive data based on their protection status to help you make better backup decisions. +Anomaly Detection for Azure Blob Storage | Identifies and analyzes anomaly events that can indicate a ransomware attack and provides data recovery services for the protected resources. +Application-consistent snapshot for Azure virtual machines | Provides the capability to create application-consistent snapshots using Volume Shadow Copy Service (VSS) or pre-snapshot and post-snapshot scripts with RSC. +Azure custom tags | Implements specific policies for cost allocation, financial management, and resource creation. + *[ > ]: and then diff --git a/saas_azr_manage_vm_md.md b/saas_azr_manage_vm_md.md new file mode 100644 index 0000000000000000000000000000000000000000..d6a4c21b167d0252a0b483b6229bed98ea979e5f --- /dev/null +++ b/saas_azr_manage_vm_md.md @@ -0,0 +1,20 @@ +# Manage Azure virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_manage_vm_md.html + +--- + +# Manage Azure virtual machines + +After completing the protection setup for Azure virtual machines and managed disks, RSC takes automated snapshots of those virtual machines and disks based on the configured policies in SLA Domains. You can also take on-demand snapshots, refresh Azure subscriptions, and add Azure custom tags for better resource management. + +After you have completed the protection setup for Azure virtual machines and managed disks, RSC starts taking automated snapshots of those virtual machines and disks according to the data protection policies you configured in the assigned SLA Domains. You can view detailed snapshot information on the Inventory page for Azure virtual machines. Based on your requirements, you can take on-demand snapshots of your workloads and perform snapshot management tasks such as modifying retention policies and deleting snapshots. + +RSC also provides you the ability to do the following: + + * Refreshing an Azure subscription as an on-demand task to retrieve the latest metadata. + * Adding Azure custom tags to implement specific policies for cost allocation, financial management, and resource creation. + * Enabling application-consistent backups to preserve the working state of applications running on a protected Azure virtual machine. + * Enabling Anomaly Detection to detect ransomware attacks, and enabling Data Security Posture to identify sensitive data in backups for Azure virtual machines and managed disks. + + *[ > ]: and then diff --git a/saas_azr_protect_implementation.md b/saas_azr_protect_implementation.md new file mode 100644 index 0000000000000000000000000000000000000000..f61ed945a4520c0c4ce2d0ead9d803c86ab70ae1 --- /dev/null +++ b/saas_azr_protect_implementation.md @@ -0,0 +1,20 @@ +# Azure protection implementation workflow + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_protect_implementation.html + +--- + +# Azure protection implementation workflow + +The Azure protection implementation workflow involves a structured approach to secure data management, starting with planning and preparation, followed by cloud account setup, infrastructure configuration, workload protection, continuous management and optimization, and workload recovery. + +You can follow this structured approach to ensure comprehensive and secure data management for your Azure workloads using RSC: + + 1. Planning and preparation: In this foundational phase, you understand the capabilities of RSC for Azure protection, including its key features, common terminology, and high-level architecture. You plan user and access management within RSC for Azure and carefully review all necessary permissions that RSC requires in the Azure environment for data protection. + 2. Azure cloud account setup: In this phase, you focus on securely connecting RSC to the Microsoft Azure subscription. It involves adding the Azure subscription to RSC by configuring the chosen authentication method, such as OAuth or manual setup. + 3. Core infrastructure configuration: In this phase, you set up the underlying Rubrik components within Azure. This includes configuring Exocompute on Azure, which provides scalable compute resources for data operations such as indexing and file recovery. Additionally, you configure Azure Storage Tiering to manage archival locations and optimize long-term storage costs. + 4. Workload protection: In this phase, you define how data will be protected. You create and customize SLA Domains to automatically protect Azure workloads according to business objectives, specifying snapshot frequency and retention. You also configure advanced policies for data archival, replication, and retention lock. This phase also involves enforcing data security by assigning the configured SLA Domains to specific Microsoft Azure workloads. Automated backups are initiated based on these policies. You can also perform on-demand snapshots as needed. + 5. Management of workloads: In this phase, you monitor Azure protection dashboards to track backup job statuses and data changes, generate reports for auditing and data management planning, and review event logs for all protection activities. This stage also includes resolving any issues and continuously optimizing the configuration for efficiency and compliance. + 6. Workload recovery: After any data loss event, you focus on restoring operations with clean data. RSC provides various recovery options, including performing granular or full recoveries for Azure workloads, ensuring business continuity. + + *[ > ]: and then diff --git a/saas_azr_protection_planning.md b/saas_azr_protection_planning.md new file mode 100644 index 0000000000000000000000000000000000000000..d8bdca9b74d1064249fc3cc4cf3dcc939f2d2ffa --- /dev/null +++ b/saas_azr_protection_planning.md @@ -0,0 +1,18 @@ +# Plan your Azure protection + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_protection_planning.html + +--- + +# Plan your Azure protection + +Before setting up an Azure cloud account in RSC, you are required to plan the user and access management for designated RSC users. This planning also involves reviewing the permissions that RSC requires in your Azure environment to protect your Azure workloads. + +When planning Azure protection, it is important that you establish a clear framework for user and access management to ensure secure and efficient operations within your Azure environment. You can start by categorizing your RSC users based on their roles and responsibilities and by assigning appropriate privileges through roles to limit access according to the principle of least privilege. + +Additionally, it is important that you review the specific permissions that RSC requires to protect your Azure workloads. Understanding these permissions helps explain why they are needed. By doing this, you can gain clarity on the operations being implemented to protect your Azure workloads. + +Note: + +After you complete planning for Azure protection, the next step is to [Set up Azure cloud accounts](azr_cloud_acc_setup.html "You can set up an Azure cloud account in RSC to start protecting Azure workloads."). + *[ > ]: and then diff --git a/saas_azr_quick_links.md b/saas_azr_quick_links.md new file mode 100644 index 0000000000000000000000000000000000000000..b6cfedf018274062c028056b5810881c8b66f4e8 --- /dev/null +++ b/saas_azr_quick_links.md @@ -0,0 +1,56 @@ +# Quick links for Azure workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_quick_links.html + +--- + +# Quick links for Azure workloads + +Immediate access to important tasks and information, enabling quick setup, daily operations, and critical recovery. + +## Initial setup and onboarding + + * [Required RSC permissions for Azure cloud accounts](azr_req_rbk_perms_cloud_acc.html "RSC requires specific permissions in your Azure environment to protect the Azure workloads.") + * [Creating Azure cloud accounts with OAuth](azr_creating_cloud_account_oauth.html "Create an Azure cloud account with OAuth configuration in RSC to protect Azure resources using a Microsoft Entra ID application.") + * [Azure cloud account addition without OAuth](azr_cloud_acc_addition_without_oauth.html "You can set up an Azure cloud account on RSC using the Configure without OAuth method and start protecting your Azure workloads.") + * [Managing granular permissions for an Azure cloud account](managing_granular_perm_azr_cloud_acnt.html "Manage the permission categories for an Azure cloud account that you have already added to RSC by including or excluding permission categories, as required.") + * [Creating a VNet](azr_creating_vnet.html "Create a VNet on the Azure portal to configure localized or centralized Exocompute with Rubrik-hosted ACR and Rubrik-managed AKS clusters.") + * [Configuring Exocompute for Rubrik-managed clusters](azr_configuring_exo_host_acct_rmc.html "After creating an Exocompute host account for a Rubrik-managed cluster, configure an Exocompute instance in the host account by adding a region.") + * [Creating archival locations for Azure storage account](azr_creating_arch_loc_storage_acc.html "Create an archival location for the Azure storage account created for archiving the Azure virtual machine or managed disk snapshots and for storing Azure SQL backups.") + * [Creating RCV locations for cloud-native workloads on Azure](rcv_creating_rcv_cn_workloads_azure.html "Create a Rubrik Cloud Vault location on Azure to archive the backups of cloud-native workloads.") + * [Creating a custom SLA Domain](rsc_creating_custom_sla_domain.html "Create a custom SLA Domain to streamline and customize workload protection and management policies.") + * [Assigning protection to Azure virtual machines or managed disks](azr_assigning_protection_vm_md.html "Assign a data protection policy to specific Azure virtual machines or managed disks.") + * [Assigning protection to Azure Blob Storage](../azure_blob/assigning_protection_azr_blob_storage.html "Assign a data protection policy to an Azure Blob Storage account.") + * [Assigning protection to Azure SQL workloads](azr_sql_assigning_protection.html "Assign a data protection policy to individual or multiple Azure SQL workloads.") + * [Assigning protection to Azure subscriptions or resource groups](azr_assigning_protection_sub_rg.html "Assign a data protection policy at the Azure subscription or resource group level.") + * [Creating a tag rule for Azure virtual machines or managed disks](azr_creating_tag_rules.html "Create a tag rule to protect the Azure virtual machines or managed disks and assign a protection setting to that tag rule.") + * [Creating a tag rule for Azure Blob storage](../azure_blob/creating_tag_rule_azr_blob.html "Create a tag rule to group the Azure Blob Storage accounts and assign an SLA Domain to protect the accounts and their objects.") + * [Configure Azure SQL DB Rubrik backups](azr_sql_db_config_rbk_backup.html "Information about the configuration tasks to set up Rubrik backups for Azure SQL Databases.") + * [Configure Azure SQL MI Rubrik backups](azr_sql_mi_config_rbk_backup.html "Information about the configuration tasks to set up Rubrik backups for Azure SQL Managed Instances.") + +## Daily operations and monitoring + + * [Viewing the Azure subscription page](azr_view_azure_subscription.html "View the Azure subscription page from RSC.") + * [Viewing the Azure resource group page](azr_view_resource_grp.html "The Azure resource group list displays protection status, region, and subscription ID of the resource groups.") + * [Refreshing an Azure subscription](azr_refresh_azure_subscription.html "RSC refreshes Azure subscription data as an on-demand task or as a periodic background job that runs every three hours.") + * [Taking an on-demand snapshot for Azure VMs or managed disks](azr_taking_ondemand_snapshot.html "Manually initiate an on-demand snapshot of the Azure VMs and managed disks with or without assignment of an SLA Domain.") + * [Taking on-demand snapshots of Azure Blob Storage](../azure_blob/taking_ods_azr_blob.html "Take an on-demand snapshot of the Azure Blob Storage account.") + * [Taking on-demand snapshots of Azure SQL workloads](azr_sql_taking_ods.html "Manually initiate an on-demand snapshot of an Azure SQL database object.") + * [Viewing the Exocompute on Azure details page](azr_viewing_exocompute_details_page.html "View the details of an Exocompute on Azure instance. Based on the information, you can run a health check, add or delete regions, or deactivate and delete an Exocompute host subscription, if required.") + * [Viewing Exocompute events](viewing_exo_health_check_events.html "View the Events page from the Dashboard to see the Exocompute events.") + +## Recovery and troubleshooting + + * [Recovering files or folders to an Azure storage account](recovering_files_folders_to_azr_storage_account.html "Recover files or folders from Azure virtual machines or managed disks to an Azure storage account if the files that you want to access are deleted, corrupted, or encrypted.") + * [Exporting Azure virtual machine snapshots](azr_exporting_vm_snapshot.html "Export a snapshot of an Azure virtual machine to create a virtual machine from a point-in-time copy of the source virtual machine.") + * [Exporting an Azure managed disk snapshot](export_azure_md_snapshot.html "Export a snapshot of an Azure managed disk to create a new disk from a point-in-time copy of the source managed disk.") + * [Restoring Azure virtual machine using a snapshot](azr_restore_snapshot.html "Use an Azure virtual machine snapshot to replace the original virtual machine with a fully functional point-in-time copy.") + * [Mounting Azure virtual disks for data recovery](mounting_azr_virtual_disks_for_data_recovery.html "To recover critical data in a disaster or outage that can pose a significant business problem, mount the Azure virtual disks to the source virtual machine or a different virtual machine running in another region or subscription.") + * [Azure In-place File Recovery](azr_in_place_file_recovery.html "With the In-place File Recovery feature, you can recover Azure files from an indexed snapshot either to a source virtual machine or a different virtual machine or export the files to a different virtual machine.") + * [Restoring an individual Azure blob from a snapshot](../azure_blob/restoring_indvidual_azr_blob_snapshot.html "When you want to recover an Azure blob to an alternative storage location or overwrite an Azure blob with a blob selected from a snapshot, restore an individual Azure blob from a snapshot.") + * [Restoring an entire Azure Blob Storage](../azure_blob/restoring_entire_azr_blob.html "Restore an entire Azure Blob Storage account in disaster situations to ensure data integrity.") + * [Azure SQL workload recovery](azr_sql_workload_recovery.html "RSC supports recovering Azure SQL workloads at the individual database level.") + * [Resolving common Azure Exocompute issues](azr_resolving_common_exocompute_issues.html "You can troubleshoot and resolve common Azure Exocompute issues that occurs while setting up an Azure Kubernetes Service cluster. The AKS cluster not starting properly is a common issue reported to Rubrik Support. Some reasons for this are described below.") + * [Resolving AKS cluster health-check failure](resolving_aks_cluster_health_check_failure.html "You can often troubleshoot and resolve Exocompute health-check failure issues while setting up an Azure Kubernetes Service cluster.") + + *[ > ]: and then diff --git a/saas_azr_sql_db_manage.md b/saas_azr_sql_db_manage.md new file mode 100644 index 0000000000000000000000000000000000000000..395c8a95f433d1a4944fea16ed769adc23515e33 --- /dev/null +++ b/saas_azr_sql_db_manage.md @@ -0,0 +1,16 @@ +# Manage Azure SQL Database + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_sql_db_manage.html + +--- + +# Manage Azure SQL Database + +RSC enhances Azure native backup capabilities for SQL Databases by offering advanced, Rubrik-managed protection. This solution overcomes native limitations with customizable SLA Domain policies, on-demand snapshots, and flexible cross-subscription recovery, ensuring a consistent and automated approach to data security. + +Azure SQL Database offers built-in Azure native backup capabilities, including Point-in-Time Retention (PITR) and Long-Term Retention (LTR). While these Azure native backups provide a basic level of data protection, they have limitations, such as the inability to perform on-demand backups or recover across subscriptions. + +RSC provides advanced data protection for Azure SQL Databases by offering Rubrik backups that overcome these native limitations. This solution enables customizable backup frequencies, on-demand snapshots, and cross-subscription recovery, giving you more granular control over your data protection policies. By protecting your Azure SQL data with RSC, you can ensure a consistent and automated approach to data security and recovery across your entire environment. + +Protecting Azure SQL Database with RSC requires you to understand Azure native backup features and their limitations before implementing Rubrik backups. You will learn about the components of Rubrik backups, including Exocompute, the Cloud Storage Layer (CSL), and snapshot immutability, along with the necessary prerequisites and configuration steps. + *[ > ]: and then diff --git a/saas_azr_sql_mi_manage.md b/saas_azr_sql_mi_manage.md new file mode 100644 index 0000000000000000000000000000000000000000..b5c6576e476ef43eb96ff1b29109ca56fc68105c --- /dev/null +++ b/saas_azr_sql_mi_manage.md @@ -0,0 +1,16 @@ +# Manage Azure SQL Managed Instance + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_sql_mi_manage.html + +--- + +# Manage Azure SQL Managed Instance + +RSC enhances Azure native backup capabilities for SQL Managed Instances by offering advanced, Rubrik-managed protection. This solution overcomes native limitations with customizable SLA Domain policies, on-demand snapshots, and flexible cross-subscription recovery, ensuring a consistent and automated approach to data security. + +Azure SQL Managed Instance (MI) offers built-in backup capabilities, including Point-in-Time Retention (PITR) and Long-Term Retention (LTR). While these Azure native backups provide a basic level of data protection, they have limitations, such as the inability to perform on-demand backups or recover across subscriptions. + +RSC provides advanced data protection for Azure SQL MI, offering Rubrik backups that overcome these native limitations. This solution enables customizable backup frequencies, on-demand snapshots, and cross-subscription recovery, giving you more granular control over your data protection policies. By protecting your Azure SQL MI data with RSC, you can ensure a consistent and automated approach to data security and recovery across your entire environment. + +Protecting Azure SQL MI with RSC requires you to understand Azure native backup features and their limitations before implementing Rubrik backups. You will learn about the components of Rubrik backups, including Exocompute, Change Data Capture (CDC) and local database user, the Cloud Storage Layer (CSL), and snapshot immutability, along with the necessary prerequisites and configuration steps. + *[ > ]: and then diff --git a/saas_azr_sql_mi_recovery_settings.md b/saas_azr_sql_mi_recovery_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..ed44c5d3189e24612810354dc784ad8ad2197eea --- /dev/null +++ b/saas_azr_sql_mi_recovery_settings.md @@ -0,0 +1,22 @@ +# Azure SQL Managed Instance recovery settings + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_sql_mi_recovery_settings.html + +--- + +# Azure SQL Managed Instance recovery settings + +Recovering Azure SQL Server databases by exporting snapshots requires specific configuration. + +RSC requires the following settings for recovering Azure SQL Server databases from backups. + +Setting | Description +---|--- +Database Name | The name of the exported database.RSC populates this field with a randomly generated database name. +(Rubrik backups) Username and Password | The credentials of the database admin account for authentication during recovery. +(Rubrik backups) Subscription | The target Azure subscription to export the workload. +(Rubrik and long-term retention backups) Region | The geographical region within the subscription. +Managed Instance | The target managed instance. +Resource group | The resource group of the exported database.The resource group is the same as that of the source database and cannot be edited. +(Rubrik backups) Azure Active Directory Domain | The name of the Azure Active Directory Domain for authentication using OAuth during recovery. + *[ > ]: and then diff --git a/saas_azr_storage_tiering_setup.md b/saas_azr_storage_tiering_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..540d407276f60d657cc235fa6db444e77ee67a91 --- /dev/null +++ b/saas_azr_storage_tiering_setup.md @@ -0,0 +1,36 @@ +# Set up Azure storage tiering + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_storage_tiering_setup.html + +--- + +# Set up Azure storage tiering + +You can use Azure storage tiering to archive Azure virtual machine or managed disk snapshots, which are older than a specified threshold, to Azure storage access tiers. By archiving snapshots to these access tiers, you can optimize cost. + +Industries in the public sector, such as financial services and healthcare, require snapshots to be retained for several years to meet regulatory and compliance requirements. Azure storage tiering enables cost optimization by archiving such snapshots to Azure storage access tiers or Rubrik Cloud Vault (RCV). + +## Managed disk tiering and cost considerations + +When preparing to set up Azure storage tiering, it is important to consider the following points: + + * RSC supports tiering of managed disks with storage space of up to 32 TB. + * Azure storage tiering provides lower-cost Azure Blob Storage to store snapshots. + +## Tiered snapshots immutability + +RSC leverages the Azure time-based retention policy for immutable blob data. This policy locks the blob data with a Write-Once, Read-Many (WORM) lock for a specified interval. Once this policy is set, you can read and create blobs but cannot modify or delete them until the retention period expires. The retention period for the snapshots is managed through the SLA Domains. For example, if the retention period is specified as five weeks in the SLA Domain, the snapshot will stay in the immutable state for five weeks. + +Azure immutability works only when the Blob versioning is enabled on the Azure storage account. RSC enables blob versioning when creating the storage account. + +Azure immutability has the following advantages: + + * Prevents deletion or modification of tiered snapshots from the storage account. + * Provides protection against insider malicious activity, for example, administrators modifying or deleting the snapshots. + +These advantages ensure retrieval of backup data in the archival location for a set period in case of malicious activity until the lock or the retention configured in the SLA Domain expires. + +Note: + +After you configure Azure storage tiering, the next step is to [Set up Azure workloads protection](azr_workloads_protection_setup.html "You can set up SLA Domains to apply data protection policies, ensuring automatic and hierarchical protection of Azure subscriptions, resource groups, and individual Azure workloads, with granular control overriding higher-level assignments."). + *[ > ]: and then diff --git a/saas_azr_workload_recovery.md b/saas_azr_workload_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..9bcacdf55471ca2ff3de942dc6a30c1cc40141a7 --- /dev/null +++ b/saas_azr_workload_recovery.md @@ -0,0 +1,18 @@ +# Recover Azure workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_workload_recovery.html + +--- + +# Recover Azure workloads + +After RSC takes snapshots of your Azure workloads, you can recover the required workloads. + +After completing the protection setup for your Azure workloads, RSC starts protecting your data by taking snapshots based on the configured policies in the assigned SLA Domains. You can recover the workloads from these snapshots using various recovery options based on your specific requirements. Rubrik recommends adding an Azure cloud account based on the least privilege model, which involves selecting only the Basic permission category. When a recovery operation becomes necessary, you can then elevate the permissions for recovery purposes. + +Before beginning the recovery operations, it is important to do the following: + + * Evaluating the privilege elevation options and learning how to assign a permission category for recovery. + * Familiarizing yourself with the various recovery options to ensure that your choice aligns with your recovery requirements. + + *[ > ]: and then diff --git a/saas_azr_workloads.md b/saas_azr_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..aa0488c7617d26666280ada7d80a713aacd9dfbc --- /dev/null +++ b/saas_azr_workloads.md @@ -0,0 +1,23 @@ +# Microsoft Azure workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_workloads.html + +--- + +# Microsoft Azure workloads + +RSC protects the data and resources of Azure virtual machines, Azure managed disks, Azure Blob Storage, and Azure SQL workloads in Azure subscriptions. + +As digital organizations expand their use of Azure virtual machines, Azure managed disks, Azure Blob Storage, and Azure SQL workloads to deploy applications, they encounter new complexities in protecting, managing, and securing their data. Complex deployments can be at greater risk of threats to data integrity and operational stability, putting businesses at risk of data breaches, accidental data loss, and ransomware attacks. The Shared Responsibility Model established by Microsoft makes it clear that, while Microsoft Azure secures the infrastructure, the ultimate responsibility for application and data protection rests with the organization. + +As organizations increasingly rely on Azure workloads for their compute needs, maintaining consistent data protection policies becomes paramount. This important task demands solutions that ensure data security and integrity within the Azure environment. Organizations must actively protect their data against accidental deletions, cyber threats, and operational errors in Azure workloads. + +Rubrik provides a streamlined solution to these challenges with Rubrik Security Cloud (RSC), its data protection platform based on SaaS. RSC secures and automates data protection processes for Azure workloads, ensuring that data remains protected against accidental deletions, ransomware attacks, and other potential threats. With RSC, organizations can automate backup, recovery, and replication schedules across Azure regions using a global policy model called an SLA Domain. SLA Domains allow organizations to take advantage of rapid innovation of Azure while reducing management complexity. + +Protecting Azure workloads with RSC involves a structured approach that ensures comprehensive and consistent data protection policies across the cloud infrastructure of an organization. By breaking down the tasks into three main categories, Authorization, Configuration, and Protection, RSC simplifies the steps required to protect your Azure workload. Each task category addresses specific aspects of data security, from granting secure access to applying global policies and enforcing data protection measures. + +The following table provides an overview of these task categories and the associated activities: Task category | Description +---|--- +Authorization | For authorization, you grant RSC secure access to your Azure subscriptions that need protection. You can achieve this through an OAuth-integrated workflow that aligns with Azure security best practices. +Configuration | For configuration, you set up SLA Domains to automatically protect Azure workloads according to your business objectives.Using SLA Domains, you can define and manage data protection policies uniformly across different regions. +Protection | For protection, you enforce data security by assigning SLA Domains to Azure workloads. If the situation arises, RSC provides quick recovery options for Azure virtual machines, managed disks, Azure Blob Storage, Azure SQL workloads, and individual files within or across regions. diff --git a/saas_azr_workloads_protection_setup.md b/saas_azr_workloads_protection_setup.md new file mode 100644 index 0000000000000000000000000000000000000000..8051efd08067e062df36ae34af09e0442717e39b --- /dev/null +++ b/saas_azr_workloads_protection_setup.md @@ -0,0 +1,22 @@ +# Set up Azure workloads protection + +Source: https://docs.rubrik.com/en-us/saas/saas/azr_workloads_protection_setup.html + +--- + +# Set up Azure workloads protection + +You can set up SLA Domains to apply data protection policies, ensuring automatic and hierarchical protection of Azure subscriptions, resource groups, and individual Azure workloads, with granular control overriding higher-level assignments. + +In cloud data protection, ensuring that your Azure workloads are secure and recoverable is essential. The SLA Domain feature of Rubrik offers a structured way to apply data protection policies across various Azure workloads, ensuring consistent and reliable backup and recovery processes. An SLA Domain is a set of policies that define the backup and recovery objectives for your data. These policies specify the frequency of snapshots, the retention period for these snapshots, and the archiving and replication requirements. + +By assigning SLA Domains to Azure workloads, you ensure that your data protection strategies align with your organizational requirements and compliance standards. RSC enables hierarchy-based, automatic protection of Azure workloads. This automatic protection mechanism simplifies the process of assigning protection to large numbers of workloads. + +After you add an Azure subscription to RSC, you need to create one or more SLA Domains to begin protecting Azure workloads. Then, you can assign these SLA Domains to different Azure entities. RSC then starts creating, archiving, replicating, and expiring snapshots to protect the relevant workloads based on the parameters defined in the assigned SLA Domain. + +The following table summarizes where you can assign an SLA Domain: Entity | Description +---|--- +Azure subscription | Assigning SLA Domain settings at the subscription level to ensure all workloads within this subscription adhere to the protection policies. +Resource group | Assigning SLA Domain settings at the resource group level for managing protection policies for grouped resources. +Individual Azure workload | Assigning SLA Domain settings to a specific Azure workload, such as virtual machines or managed disks, for granular control. + *[ > ]: and then diff --git a/saas_azure_cc_es_rsc.md b/saas_azure_cc_es_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..8fbe2d13e0e41ffe65fe8234e1ecf3e87fe3dbec --- /dev/null +++ b/saas_azure_cc_es_rsc.md @@ -0,0 +1,23 @@ +# Rubrik Cloud Cluster ES for Azure + +Source: https://docs.rubrik.com/en-us/saas/saas/azure_cc_es_rsc.html + +--- + +# Rubrik Cloud Cluster ES for Azure + +You can use Rubrik Cloud Cluster Elastic Storage for Azure to protect applications and data within a Microsoft Azure virtual network. + +Rubrik Cloud Cluster Elastic Storage (ES) for AWS or Azure runs on a single node, or it runs on three or more nodes. Rubrik CDM version 9.0.1 and later support single-node configuration. Rubrik does not support a two-node configuration. + +You can deploy a single-node cluster with either standard or extra-dense nodes. + +Multi-node clusters do not support mixing standard and dense nodes. + +Rubrik recommends using a single-node cluster when protecting workloads with 100 or fewer objects. The listed workloads do not support a single-node configuration. These workloads require using dense nodes: + + * NAS systems + * VMware Cloud on AWS + * Azure VMware Solution on Azure + + *[ > ]: and then diff --git a/saas_canceling_a_m365_restore_job.md b/saas_canceling_a_m365_restore_job.md new file mode 100644 index 0000000000000000000000000000000000000000..a3767900a1d7d433fce6b21c9e4f190703efbeb9 --- /dev/null +++ b/saas_canceling_a_m365_restore_job.md @@ -0,0 +1,40 @@ +# Canceling a Microsoft 365 Restore Job + +Source: https://docs.rubrik.com/en-us/saas/saas/canceling_a_m365_restore_job.html + +--- + +# Canceling a Microsoft 365 Restore Job + +Cancel Microsoft 365 restore jobs from the Events tab. + +## Before you begin + +To cancel Microsoft 365 restore jobs, your account must have the following privileges: + + * View Events, for the specified Microsoft 365 instance + * CANCEL_RUNNING_EVENT + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Events. + +The Events page appears. + + 3. **Optional:** Select filters to apply to the Events page. + +RSC fills the Events page with the aggregate values for the selected filter. + + 4. Click an event. + +The Events series page appears. + + 5. Click Cancel job. + +The cancel option appears only for ongoing restore jobs. + +## Results + +RSC cancels the running event. + *[ > ]: and then diff --git a/saas_cascading_archival.md b/saas_cascading_archival.md new file mode 100644 index 0000000000000000000000000000000000000000..0d134e173d58e22caca3e87bbe41451441f3e4e7 --- /dev/null +++ b/saas_cascading_archival.md @@ -0,0 +1,25 @@ +# Cascading archival + +Source: https://docs.rubrik.com/en-us/saas/saas/cascading_archival.html + +--- + +# Cascading archival + +Using cascading archival, you can increase replicated data redundancy and decrease data storage costs by archiving replicated snapshots from a replication target Rubrik cluster to a remote archival location. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Cascading archival is a combination of snapshot replication and archiving. When a source Rubrik cluster is configured to replicate snapshots to a target Rubrik cluster, you can enable cascading archival on the target cluster. + +RSC uses the cascading archival settings to move replicated snapshots from the replication target Rubrik cluster to an archival location. + +Cascading archival can maintain two different off-site copies of snapshots. You can configure archiving from the replication source cluster even when cascading archival is configured to archive replicated snapshots from the replication target cluster. The archiving policies on the two clusters are independent of each other. + +For example, consider a scenario involving a central headquarters office that has multiple branch offices in different locations. The replication feature allows the branch offices to replicate snapshots to the central office, and the cascading archival feature enables the central office to archive the replicated snapshots to a remote archival location for long-term retention compliance and disaster recovery. + +When the replication target cluster supports multiple archival locations, you can enable cascading archival to the different archival locations. + +RSC supports SLA Domains that have both retention lock and cascading archival enabled. + +RSC supports cascading archival only when the workloads to be archived are managed through Rubrik clusters. diff --git a/saas_cascading_archival_config_examples.md b/saas_cascading_archival_config_examples.md new file mode 100644 index 0000000000000000000000000000000000000000..ef857bbc672fa5c8d06d8c5d48825ae983f748d5 --- /dev/null +++ b/saas_cascading_archival_config_examples.md @@ -0,0 +1,48 @@ +# Cascading archival configuration examples + +Source: https://docs.rubrik.com/en-us/saas/saas/cascading_archival_config_examples.html + +--- + +# Cascading archival configuration examples + +Examples explaining how to configure data retention settings to achieve the required retention period when cascading archival is enabled. + +## Configuration to maximize data retention + +Setting | Example value +---|--- +The duration to retain data on the replication source Rubrik cluster | 100 days +Replication Retention | 100 days +(Cascading archival enabled) Retention on Target Cluster | 100 days +(Cascading archival enabled) Cascading Archival Threshold | 0 days + +With the configuration values in this example, RSC archives the data instantly from the replication target cluster while also retaining the data on the replication target cluster for 100 days. As a result, the data is retained on the replication target cluster and the archival location for the maximum retention of 100 days. + +The following formula determines the retention duration on the cascading archival location. + + + Cascading archival retention duration = Replication Retention - Cascading Archival Threshold + Cascading archival retention duration = 100 days - 0 days = 100 days + +## Configuration to customize data retention + +Setting | Example value +---|--- +The duration to retain data on the replication source Rubrik cluster | 100 days +Replication Retention | 75 days +(Cascading archival enabled) Retention on Target Cluster | 50 days +(Cascading archival enabled) Cascading Archival Threshold | 30 days + +The configuration values in this example specify that RSC will retain the data on the replication target cluster for 75 days. + +When cascading archival is enabled, RSC retains the data on the replication target cluster for 50 days but will start archiving the data to the archival location after 30 days on the replication target cluster. With this configuration, the data remains on the replication target cluster for 20 more days after archiving begins. + +RSC determines the retention duration on the cascading archival location as a difference between the total replication retention and the cascading archival threshold to achieve the maximum configured replication retention. As a result, to retain the data for a maximum of 75 days, RSC retains the data on the cascading archival location for 45 days after the first 30 days on the replication target cluster. + +The following formula determines the retention duration on the cascading archival location. + + + Cascading archival retention duration = Replication Retention - Cascading Archival Threshold + Cascading archival retention duration = 75 days - 30 days = 45 days + *[ > ]: and then diff --git a/saas_cces_recoverability.md b/saas_cces_recoverability.md new file mode 100644 index 0000000000000000000000000000000000000000..a1c54d2b0233b8b9413db9beb5b89d2f4cf772c7 --- /dev/null +++ b/saas_cces_recoverability.md @@ -0,0 +1,28 @@ +# Rubrik Cloud Cluster recoverability + +Source: https://docs.rubrik.com/en-us/saas/saas/cces_recoverability.html + +--- + +# Rubrik Cloud Cluster recoverability + +To restore your data, you can recover a Rubrik Cloud Cluster Elastic Storage that has immutability enabled. You can do this only when the cluster nodes cannot be recovered. + +You can recover data from a Rubrik Cloud Cluster Elastic Storage even when the nodes are destroyed. A node is destroyed and cannot be recovered in situations like these: + + * A malicious actor who has cloud administrator credentials launches an attack that destroys the nodes. + * A benign actor with cloud administrator credentials accidentally deletes the nodes. + * A catastrophic failure occurs that impacts the nodes or availability zone. + +Specific conditions must exist before you can recover a cluster with destroyed nodes. Each of the following conditions must exist at the time of recovery: + + * The cluster is registered with RSC. + * Immutability is enabled. + * The nodes cannot be recovered and the cluster is disconnected. + +Note that all of the nodes must be destroyed. Using other methods, you can recover from a partial node failure, but to recover a cluster, each of the nodes must be destroyed. When each of the nodes of a cluster cannot be recovered, the cluster is in the disconnected state. + +When you recover a cluster, RSC creates new nodes by transferring the data and metadata of the old nodes from the immutable storage location to the new nodes. You cannot recover Live Mounts. + +Rubrik CDM version 8.1.3 or later supports recoverability. + *[ > ]: and then diff --git a/saas_changing_snapshot_retention_inv_page.md b/saas_changing_snapshot_retention_inv_page.md new file mode 100644 index 0000000000000000000000000000000000000000..db6547134310fb4b4ecab6e83961659b1a1ccbc0 --- /dev/null +++ b/saas_changing_snapshot_retention_inv_page.md @@ -0,0 +1,58 @@ +# Changing retention of snapshots from the Inventory page + +Source: https://docs.rubrik.com/en-us/saas/saas/changing_snapshot_retention_inv_page.html + +--- + +# Changing retention of snapshots from the Inventory page + +Change the retention period of individual snapshots from the Snapshots card on the Inventory page to implement the required modifications. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the required inventory card. + +The selected inventory page appears. + + 5. Click the name of the instance or a virtual machine, depending on the selected object type. + 6. On the Snapshots card, click a day that has a green dot. + +The green dot indicates that one or more snapshots were taken on that specific day. + +The list of snapshots taken on that date appears. + + 7. Click for a snapshot and select Change retention. + +The Change Retention wizard appears, displaying the list of available SLA Domains. + + 8. Select an appropriate SLA Domain and click Next. + +You can select an SLA Domain that supports the required configuration for the snapshots of the object. + +RSC triggers a Quorum Authorization (QAuth) request in the following scenarios: + * The SLA Domain has governance retention lock enabled, and the new retention period is less than the old retention period. + * An explicit QAuth policy is configured for this SLA Domain. + +For SLA Domains not in the governance mode, the assignment triggers automatically. + + 9. Review the configuration details and click Assign. + +A Request Quorum Authorization page appears. + + 10. Click Submit Request. + +After the QAuth Admin or reviewer approves the QAuth request, the SLA Domain changes become effective. + +## Results + +RSC updates the retention policy for the selected snapshots. Subsequently, RSC submits a request for QAuth. The changes in the SLA Domain become effective only after the request is approved. + *[ > ]: and then diff --git a/saas_changing_the_password.md b/saas_changing_the_password.md new file mode 100644 index 0000000000000000000000000000000000000000..e31f9c7d33e35470d76fb81ba0af78383ee38a94 --- /dev/null +++ b/saas_changing_the_password.md @@ -0,0 +1,35 @@ +# Changing the password + +Source: https://docs.rubrik.com/en-us/saas/saas/changing_the_password.html + +--- + +# Changing the password + +Change the password from the RSC login page. + +## Procedure + + 1. Log in to RSC. + +Use the URL: your_domain.my.rubrik.com, where your_domain is the unique name selected for the RSC account. + + 2. On the Login page, click Forgot Password. + +The Reset Password view appears. + + 3. In Email, enter the address and click Submit. + +RSC sends a password reset email. + + 4. From the password reset email, click Continue. + +The New password page appears. + + 5. In New Password, enter a new password. + 6. In Confirm Password, enter the same password. + 7. Click Continue. + +## Results + +RSC stores the new password. diff --git a/saas_classification_hits.md b/saas_classification_hits.md new file mode 100644 index 0000000000000000000000000000000000000000..6007f4e49da7d6109c514e18957a4e747166f8e4 --- /dev/null +++ b/saas_classification_hits.md @@ -0,0 +1,17 @@ +# Classification hits + +Source: https://docs.rubrik.com/en-us/saas/saas/classification_hits.html + +--- + +# Classification hits + +Data Security Posture analyzes sensitive data and identifies them as hits when a data types detects a specific piece of content in a location that is not allowed by a specified policy. + +The information for a hit includes: + + * A data types that detected the hit + * A policy instance that was violated + * A location where the hit occurred + * A point in time at which the hit occurred + *[ > ]: and then diff --git a/saas_cleaning_source_database_details_ui.md b/saas_cleaning_source_database_details_ui.md new file mode 100644 index 0000000000000000000000000000000000000000..f175d702682af5fa1af944ded00f0a06adc7f31e --- /dev/null +++ b/saas_cleaning_source_database_details_ui.md @@ -0,0 +1,43 @@ +# Cleaning up source database details using RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/cleaning_source_database_details_ui.html + +--- + +# Cleaning up source database details using RSC + +Unconfigure the system copy to clean up the details of the source database using RSC. + +## About this task + +Unconfiguring the system copy runs a script to clean up the details of a source database. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click on the SAP HANA inventory card. + +The SAP HANA page appears. + + 5. Click an SAP HANA system. + +The list of SAP HANA databases appears. + + 6. Open the ellipsis menu for the target database and select Unconfigure System Copy. + +The Unconfigure System Copy dialog box appears. + + 7. Click Unconfigure. + +## Results + +The script runs and cleans up the details of the source database. + *[ > ]: and then diff --git a/saas_clear_network_misconfiguration.md b/saas_clear_network_misconfiguration.md new file mode 100644 index 0000000000000000000000000000000000000000..805c82a46b352738340e40079f9a8cded841bffa --- /dev/null +++ b/saas_clear_network_misconfiguration.md @@ -0,0 +1,43 @@ +# Clearing a network misconfiguration alert + +Source: https://docs.rubrik.com/en-us/saas/saas/clear_network_misconfiguration.html + +--- + +# Clearing a network misconfiguration alert + +Clear a network misconfiguration alert for a Rubrik cluster. + +## About this task + +When a Rubrik cluster cannot connect to a required URL, RSC adds an alert icon next to the cluster name. This task describes how to view a list of URLs that the cluster cannot access, and how to clear the alert after network fixes, such as firewall changes, are made. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Hover over the misconfigured-cluster icon next to the cluster name. + +The Cluster Misconfigured message box appears. + + 5. Click the link in the message box. + +The Cluster Configuration modal appears and provides a list of the required URLs that were found to be unavailable to the Rubrik cluster. + + 6. Make network changes to allow the Rubrik cluster to connect to the URLs in the list. + +Fix any network misconfigurations that are blocking the connections. For example, check that firewall and router settings allow the connections. + + 7. Click Check Connectivity. + +RSC runs a connectivity check on the Rubrik cluster and places a green checkmark next to each working connection in the list. + +## Results + +RSC removes the misconfigured-cluster icon. + +## What to do next + +If the issue cannot be resolved by making changes to the network, contact Rubrik Support. + *[ > ]: and then diff --git a/saas_cloud_accounts.md b/saas_cloud_accounts.md new file mode 100644 index 0000000000000000000000000000000000000000..5064e7c6b8bc0b3ded0dd65c4293e01ccd760f4c --- /dev/null +++ b/saas_cloud_accounts.md @@ -0,0 +1,16 @@ +# Cloud Accounts + +Source: https://docs.rubrik.com/en-us/saas/saas/cloud_accounts.html + +--- + +# Cloud Accounts + +You can add, view, edit, and delete cloud accounts for AWS, Azure, GCP, and Microsoft Entra ID. Additionally, you can manage Exocompute settings for AWS and Azure. + +Protecting your cloud-native workloads requires adding your cloud accounts to RSC. Once added, the workloads in your cloud account are viewable on the Inventory page. RSC provides an array of features for protecting workloads. The most useful of these features is the SLA Domain, where you set the frequency of taking snapshots and use those snapshots to recover workloads. + +Getting started involves navigating to the Cloud Accounts menu and adding cloud accounts for AWS, Azure, GCP, and Microsoft Entra ID to RSC. Additionally, you can view the account details and edit and delete the accounts, as required. + +You can also manage the Exocompute settings for AWS and Azure. With the Exocompute feature, you can launch an Elastic Kubernetes Service (EKS) cluster or Azure Kubernetes Service (AKS) cluster from RSC to perform snapshot indexing, file recovery, storage tiering, and application-consistent protection of AWS EC2 instances or Azure virtual machines. + *[ > ]: and then diff --git a/saas_clusters_page.md b/saas_clusters_page.md new file mode 100644 index 0000000000000000000000000000000000000000..bad062e179cd159dc46cd510f067f870f942726e --- /dev/null +++ b/saas_clusters_page.md @@ -0,0 +1,38 @@ +# Clusters page + +Source: https://docs.rubrik.com/en-us/saas/saas/clusters_page.html + +--- + +# Clusters page + +The Clusters page provides a list of Rubrik clusters connected to RSC. + +The Clusters page displays a list of Rubrik clusters connected to RSC. By default, the list view is displayed, but you can choose to view the clusters in either card view or list view. From this page, you can monitor cluster details, initiate software upgrades, and add clusters, ensuring efficient management of the Rubrik clusters. + +Metric | Description +---|--- +Card view | A visual representation of Rubrik clusters, providing detailed information in a card view. If a Rubrik cluster is marked as isolated, is displayed next to the name of the isolated cluster, indicating the isolation status. Additionally, you can view the last synced timestamp for the isolated clusters and the disconnected clusters only in the card view. The card view provides critical information about the installed Rubrik CDM versions and the cluster software support status. Indicators such as Plan upgrade soon and Unsupported version are displayed next to each version number. When you hover over these indicators, a message is displayed if the cluster version is nearing its end of support or has already ended. Additionally, you can click the Release Table link within the message to access information about Rubrik cluster release status. You can pin or unpin the cluster cards for easy access. Pinned cluster cards are always displayed at the top of the list. If there are more than 50 clusters, RSC automatically displays the list view. +List view | A list of Rubrik cluster details in tabular format, providing information for each cluster in a row. If a Rubrik cluster is marked as isolated, is displayed next to the name of the isolated cluster, indicating the isolation status. The list view provides critical information about the installed Rubrik CDM versions and the cluster software support status, with indicators such as Plan upgrade soon and Unsupported version displayed next to each version. When you hover over these indicators, a message is displayed if the cluster version is nearing its end of support or has already ended. Additionally, you can click the Release Table link within the message to access information about Rubrik cluster release status. +Manage Software Upgrades | You can navigate to the Rubrik CDM Upgrades page to view the total clusters. +\+ icon | You can add a Rubrik cluster. +Search by clusters | You can search for a Rubrik cluster by name. +Rubrik cluster statuses | You can view the following details about the clusters: + + * Total clusters + * Error clusters + * Warning clusters + * Healthy clusters + * Disconnected clusters + + +Banner message | A banner message indicates that a certain number of cluster versions are not supported. This information serves as a reminder to consider upgrading for continued Rubrik Support and access to the latest security fixes. Additionally, you can access the cluster software upgrades link within the banner message, which navigates you to the Upgrades Needed tab within the Rubrik CDM Upgrades page. +Rubrik cluster details in a tabular format | This option appears when you are in the list view. Detailed information about each Rubrik cluster, such as the following, presented in tabular format. + + * Cluster + * Node status + * Version + * Type + * Used/Total capacity + + *[ > ]: and then diff --git a/saas_common_accessing_release_notes.md b/saas_common_accessing_release_notes.md new file mode 100644 index 0000000000000000000000000000000000000000..43410794bafe3fa6575f4fa4f7b48e3419cd29ae --- /dev/null +++ b/saas_common_accessing_release_notes.md @@ -0,0 +1,34 @@ +# Accessing release notes + +Source: https://docs.rubrik.com/en-us/saas/saas/common/accessing_release_notes.html + +--- + +# Accessing release notes + +Access the Release Notes tab from the menu bar to read the RSC release notes. + +## Procedure + + 1. Log in to RSC. + 2. On the menu bar, click . + +The Notifications tab appears. + + 3. Click Release Notes. + +A list of release notes grouped by release date appears. The latest release notes appear at the top. For the release notes, you can view the new features, updates to features, and fixes. + + 4. **Optional:** Click next to a release note to expand the release note and view additional details, such as CDM dependencies and feature limitations, if any. + 5. **Optional:** Use the search box to search for a release note by keyword. + +You can search for fixed issues by Jira reference number. + + 6. **Optional:** Maximize the release notes pane to view the information in full screen and apply filters to narrow down the list. + +You can filter the release notes by label and time range. + +## Results + +You can read the release notes to understand the new features, updates to features, and fixes for a particular release. + *[ > ]: and then diff --git a/saas_common_add_floating_ip_address_rubrik_cluster.md b/saas_common_add_floating_ip_address_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..a4f4d223eb7c5865445eb93eb44238c9f34bf702 --- /dev/null +++ b/saas_common_add_floating_ip_address_rubrik_cluster.md @@ -0,0 +1,41 @@ +# Adding floating IP addresses to a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/add_floating_ip_address_rubrik_cluster.html + +--- + +# Adding floating IP addresses to a Rubrik cluster + +Add floating IPv4 and IPv6 IP addresses to a Rubrik cluster for high availability and load balancing. + +## Before you begin + +Ensure that the Rubrik cluster is running CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click Floating IPs. + 8. In Floating IPv4 addresses, add a comma-separated list of floating IPv4 addresses. + 9. In Floating IPv6 addresses, add a comma-separated list of floating IPv6 addresses. + 10. Click Save. + +## Results + +RSC adds the floating IPv4 and IPv6 addresses to the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_adding_floating_ip_cdm.md b/saas_common_adding_floating_ip_cdm.md new file mode 100644 index 0000000000000000000000000000000000000000..235569b79346684ba41233cb551980c1712131e6 --- /dev/null +++ b/saas_common_adding_floating_ip_cdm.md @@ -0,0 +1,35 @@ +# Adding floating IP addresses in CDM + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_floating_ip_cdm.html + +--- + +# Adding floating IP addresses in CDM + +Adding floating IPv4 and IPv6 IP addresses to a Rubrik cluster running CDM version 9.2.0 or earlier ensures high availability and load balancing. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The Cluster details page appears. + + 5. Click Network Details. + +The Network Details page appears. + + 6. Click for the Network Details page and select Floating IPs. + +The Floating IPs page appears. + + 7. In Floating IPv4 addresses, add a comma-separated list of floating IPv4 addresses. + 8. In Floating IPv6 addresses, add a comma-separated list of floating IPv6 addresses. + 9. Click Confirm. + +## Results + +RSC adds the floating IPv4 and IPv6 addresses to the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_adding_node_rbk_supp_third_party_clus.md b/saas_common_adding_node_rbk_supp_third_party_clus.md new file mode 100644 index 0000000000000000000000000000000000000000..cd98e1299a45658d178c036177572b7e32dfb0d6 --- /dev/null +++ b/saas_common_adding_node_rbk_supp_third_party_clus.md @@ -0,0 +1,64 @@ +# Adding a node to Rubrik or supported third-party clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_node_rbk_supp_third_party_clus.html + +--- + +# Adding a node to Rubrik or supported third-party clusters + +Add a node to physical clusters such as Rubrik appliances and supported third-party hardware appliances. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The Cluster details page appears. + + 5. Click Nodes. + +The Nodes details page appears. + + 6. Click Add Node. + +Node entitlement is automated for Rubrik CDM versions 8.0.1 and later. Performing entitlement is not necessary when you add a node to a Rubrik cluster running these versions. Node entitlement is discussed in the third-party hardware guides. + +When adding new nodes, the maximum number of additional nodes being added at one time should not exceed the number in the Rubrik cluster. For example, if your Rubrik cluster has four nodes, you can add up to an additional four nodes at one time for a revised total of eight nodes in the cluster. Adding more nodes in a single operation than the number in the Rubrik cluster could result in Add Node operation delays or failure. + +Note: + +To ensure Rubrik cluster compatibility, RSC blocks you from adding R7000 nodes if the current version of Rubrik CDM does not support them. The Rubrik cluster must be running CDM version 9.1.3-p10, 9.2.3-p3, or 9.3.1-p1 at least. This measure prevents potential issues with data migration processes and promotes system stability. + +The node discovery process starts. When the node discovery process completes, the Add Node wizard displays a list of nodes available to add to the Rubrik cluster along with their network information. + + 7. **Optional:** Disable the settings for Add to cluster or click X to remove nodes from the list. + 8. In Management (Bond0), enter the management IP address for each node. + 9. When Data Network is enabled, in In Data (Bond1), enter the data IP address. + 10. When IPMI is configured during bootstrap, in IPMI, enter the IPMI IP address. + 11. When VLANs are configured, click Add VLAN IP, enter the VLAN IP address for each VLAN on the node. + 12. Click Save. + 13. Click Next. + +The wizard advances to the Network page. + + 14. In Gateway IP, review the default gateway address. + 15. In Gateway Network, review the default gateway network. + +The available node networks are Management Network, Data Network, and VLAN. + + 16. In Subnet Mask, review the management network subnet mask. + 17. **Optional:** In Management VLAN, enter the management VLAN ID. + 18. When Data Network is enabled, in Subnet Mask, review the data network subnet mask. + 19. **Optional:** In Data VLAN, enter the data VLAN ID. + 20. (IPMI) In Subnet Mask, enter the IPMI subnet mask. + 21. (IPMI) IPMI Gateway, enter the IPMI gateway address. + 22. (IPMI) In Password, enter the new IPMI password for all nodes in the Rubrik cluster. + 23. (IPMI) In Re-enter Password, re-enter the password. + 24. Click Add. + +## Results + +RSC adds the nodes to the Rubrik cluster or supported third-party cluster. + *[ > ]: and then diff --git a/saas_common_adding_ntp_server_cdm.md b/saas_common_adding_ntp_server_cdm.md new file mode 100644 index 0000000000000000000000000000000000000000..bb2b25126f0421de49e90bae58faf1147deac7e8 --- /dev/null +++ b/saas_common_adding_ntp_server_cdm.md @@ -0,0 +1,36 @@ +# Adding NTP servers in CDM + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_ntp_server_cdm.html + +--- + +# Adding NTP servers in CDM + +Add an NTP server to the Rubrik cluster running CDM version 9.2.0 or earlier for a network time synchronization. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The Cluster details page appears. + + 5. Click Network Details. + +The Network Details page appears. + + 6. Click for the Network Details tab and select NTP Servers. + +The NTP Servers page appears. + + 7. In NTP Server Address, enter the IP address of the NTP server. + 8. **Optional:** Make changes to the optional fields for adding an NTP server. + 9. **Optional:** Repeat the steps to add additional NTP servers. + 10. Click Confirm. + +## Results + +RSC adds the NTP server to the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_adding_ntp_server_rubrik_cluster.md b/saas_common_adding_ntp_server_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..905b637676eeb5add38724401b6a836035c55006 --- /dev/null +++ b/saas_common_adding_ntp_server_rubrik_cluster.md @@ -0,0 +1,44 @@ +# Adding NTP servers to a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_ntp_server_rubrik_cluster.html + +--- + +# Adding NTP servers to a Rubrik cluster + +Add an NTP server to the Rubrik cluster for network time synchronization. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click NTP Servers. + 8. Click Add NTP Server. + 9. In NTP Server Address, enter the IP address of the NTP server. + 10. **Optional:** In Key ID, enter the key ID for the NTP server. + 11. In Key, enter the symmetric key. + 12. In Key Type, select the key type from the dropdown list. + 13. Click Save. + +## Results + +RSC adds the NTP server to the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_adding_proxy_settings_cdm.md b/saas_common_adding_proxy_settings_cdm.md new file mode 100644 index 0000000000000000000000000000000000000000..82f3cda1a22460de6d3f524388e3d37a9086e7f3 --- /dev/null +++ b/saas_common_adding_proxy_settings_cdm.md @@ -0,0 +1,43 @@ +# Adding proxy settings in CDM + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_proxy_settings_cdm.html + +--- + +# Adding proxy settings in CDM + +Add settings for a proxy server connected to a Rubrik cluster running CDM version 9.2.0 or earlier to filter and monitor web traffic from the Rubrik cluster, to save bandwidth by caching files or compressing incoming traffic, and to improve security. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The Cluster details page appears. + + 5. Click Network Details. + +The Network Details page appears. + + 6. Click for the network list and select Proxy Settings. + +The Proxy Settings page appears. + + 7. In Protocol, select the network protocol used by the proxy server. + * HTTP + * HTTPS + * SOCKS5 + 8. In Proxy Server, enter the IP address or FQDN for the proxy server. + 9. In Port Number, enter the port number used for the proxy server. + +The default port numbers for HTTP, HTTPS, and SOCKS5 are 80, 443, and 1080, respectively. + + 10. **Optional:** Enter the required credentials in the Username and Password fields. + 11. Click Done. + +## Results + +RSC configures the proxy server with the selected settings. + *[ > ]: and then diff --git a/saas_common_adding_proxy_settings_rubrik_cluster.md b/saas_common_adding_proxy_settings_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..e264a4bec3241b991b19a8b9687e31d580fd405c --- /dev/null +++ b/saas_common_adding_proxy_settings_rubrik_cluster.md @@ -0,0 +1,49 @@ +# Adding proxy settings to a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_proxy_settings_rubrik_cluster.html + +--- + +# Adding proxy settings to a Rubrik cluster + +Add settings for a proxy server connected to a Rubrik cluster to filter and monitor web traffic from the Rubrik cluster, to save bandwidth by caching files or compressing incoming traffic, and to improve security. + +## Before you begin + +Ensure that the Rubrik cluster is running CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click Proxy Settings. + 8. In Protocol, select the network protocol used by the proxy server. + +The supported protocols are HTTP, HTTPS, and SOCKS5. + + 9. In Proxy Server, enter the IP address or FQDN for the proxy server. + 10. In Port Number, enter the port number used for the proxy server. + +The default port numbers for HTTP, HTTPS, and SOCKS5 are 80, 443, and 1080, respectively. + + 11. **Optional:** Enter the required credentials in the Username and Password fields. + 12. Click Save. + +## Results + +RSC configures the proxy server with the settings. + *[ > ]: and then diff --git a/saas_common_adding_routing_table_cluster.md b/saas_common_adding_routing_table_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..61b9d0c9f19f1b690270dff92394460b6de2b036 --- /dev/null +++ b/saas_common_adding_routing_table_cluster.md @@ -0,0 +1,49 @@ +# Adding a static route to a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_routing_table_cluster.html + +--- + +# Adding a static route to a Rubrik cluster + +Add a static route for a Rubrik cluster to a specified network destination with other network details such as netmask, gateway and interface for efficient network routing and better performance. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +You can view, delete, and add an IPv4 or IPv6 static route for a Rubrik cluster in the routing table for network efficiency, reliability, and performance. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click Routing Table. + 8. Click Add Static Route. + 9. In Network Destination, enter the IP address for the destination network or host. + 10. In Netmask, enter the subnet mask of the destination network. + 11. In Interface, select a network interface for the static route from the dropdown list. + 12. In Gateway, enter a gateway for the static route. + +RSC auto-populates the gateway if you select a VLAN interface that has an associated gateway. You can edit the auto-populated gateway. + + 13. Click Add. + +## Results + +RSC adds the static route to the routing table with the static route details you specified. + *[ > ]: and then diff --git a/saas_common_adding_vlan_cdm.md b/saas_common_adding_vlan_cdm.md new file mode 100644 index 0000000000000000000000000000000000000000..4d7d2f5b8428c91b040b3f45e651b138140f081f --- /dev/null +++ b/saas_common_adding_vlan_cdm.md @@ -0,0 +1,38 @@ +# Adding VLANs in CDM + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_vlan_cdm.html + +--- + +# Adding VLANs in CDM + +Add a VLAN to a Rubrik cluster running CDM version 9.2.0 or earlier for a logical segmentation of networks. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The cluster details page appears. + + 5. Click Network Details. + +The Network Details page appears. + + 6. Click Add VLAN. + +The Add VLAN dialog box appears. + + 7. In VLAN ID, enter the ID of the VLAN. + 8. In VLAN Subnet Mask, enter the subnet mask associated with the VLAN. + 9. In VLAN IP Address, enter an IP address associated with the VLAN for each node in the cluster. + 10. Click Add. + +## Results + +RSC adds the VLAN for the selected Rubrik cluster. + +After the VLAN addition completes, you can review the details on the Network Details page. + *[ > ]: and then diff --git a/saas_common_adding_vlan_rubrik_cluster.md b/saas_common_adding_vlan_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..f9c15ad150654d4cb71aaab458c6981320f3d152 --- /dev/null +++ b/saas_common_adding_vlan_rubrik_cluster.md @@ -0,0 +1,55 @@ +# Adding VLANs to a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/adding_vlan_rubrik_cluster.html + +--- + +# Adding VLANs to a Rubrik cluster + +Add a VLAN to a Rubrik cluster to enable a logical segmentation of networks, enhancing network and security management. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click Add VLAN. + +The Add VLAN dialog box appears. + + 8. In VLAN ID, enter the ID of the VLAN. + 9. **Optional:** In VLAN Name, enter a name for the VLAN. + 10. In VLAN Subnet Mask, enter the subnet mask associated with the VLAN. + 11. **Optional:** In Gateway, enter a gateway for the VLAN. + +RSC pre-populates the entered gateway when you add a static route for this VLAN interface. You can edit the pre-populated gateway to change it in the static route table. + + 12. In VLAN IP Address, enter an IP address associated with the VLAN for each node in the cluster. + +You can enter the VLAN IP address for the first node, and then click the Auto-Populate IP Address to auto-populate the IP addresses for the other nodes. Auto-populate increments the IP address of the first node to add the IP addresses for the other nodes. + + 13. Click Add. + +## Results + +RSC adds a VLAN to the Rubrik cluster. + +After the VLAN addition completes, you can review the details on the Network page. + *[ > ]: and then diff --git a/saas_common_assigning_role_based_access_control_on_custom_reports.md b/saas_common_assigning_role_based_access_control_on_custom_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..a562c5ce9037313342ed4bc91d1b541c1fb43520 --- /dev/null +++ b/saas_common_assigning_role_based_access_control_on_custom_reports.md @@ -0,0 +1,53 @@ +# Assigning role-based access control on custom reports + +Source: https://docs.rubrik.com/en-us/saas/saas/common/assigning_role_based_access_control_on_custom_reports.html + +--- + +# Assigning role-based access control on custom reports + +Administrators and owners can assign role-based access control on custom reports, allowing more granular control over reports. + +## About this task + +As an administrator or owner, you can create custom roles on particular reports using the Roles function in RSC settings. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Select Users & Access > Roles. + 4. Click Create Role. + +The Create Role wizard appears. + + 5. Click Custom Role. + 6. In Assign System Configuration Privileges, click Configure to set the system configuration privileges for the role. + +The wizard displays the Assign System Configuration Privileges page. + + 7. In the Reports section, select which permissions to assign to this role. + 8. Click All reports. + +The Select Reports wizard appears. + + 9. Choose Select specific reports to view, then select the reports to which RSC applies these permissions. + 10. Click Done. + +You can clear or edit the permissions on the Select Reports wizard. + + 11. Click Next. + 12. Enter a role name and an optional description. + 13. Click Create. + +## Results + +RSC creates a new role with role-based access control (RBAC) on custom reports. + +Note: + +The content of the report the user can view depends on their object-level role-based access control. + *[ > ]: and then diff --git a/saas_common_audit_log_details_2.md b/saas_common_audit_log_details_2.md new file mode 100644 index 0000000000000000000000000000000000000000..67dbeab2d05de28fefa1f183c572cf758fb98186 --- /dev/null +++ b/saas_common_audit_log_details_2.md @@ -0,0 +1,31 @@ +# Audit log details + +Source: https://docs.rubrik.com/en-us/saas/saas/common/audit_log_details_2.html + +--- + +# Audit log details + +The Audit Log tab provides several filters with detailed information about the audit logs. + +Filter | Description +---|--- +Time range | Displays a sequential view of the events that occurred during the selected period. + * Past 15 minutes + * Past 2 hours + * Past 24 hours + * Past 7 days + * Past 30 days + * Custom +Clusters | Lists all connected Rubrik clusters. Selecting a value changes the display to only show audit log messages for the selected Rubrik cluster. +Severity | Lists events of all severity levels. + * Critical + * Warning + * Informational + * N/A +Selecting a value changes the display to only show audit log messages for the selected severity level. +Status | Displays events with the selected status. + * Failure + * Completed +Clearing the filter selection displays all events. + *[ > ]: and then diff --git a/saas_common_authorization.md b/saas_common_authorization.md new file mode 100644 index 0000000000000000000000000000000000000000..be63defb2946ee16b0efe689a546095f4d115293 --- /dev/null +++ b/saas_common_authorization.md @@ -0,0 +1,16 @@ +# Authorization + +Source: https://docs.rubrik.com/en-us/saas/saas/common/authorization.html + +--- + +# Authorization + +RSC provides role-based access control, and several methods for authenticating a user account. + +RSC offers role-based access control (RBAC) that restricts access based on the roles of individuals within an organization. Depending on the assigned role, access rights are restricted to the relevant associated information and resources. + +RSC isolates individual customer data into logically partitioned databases. This prevents potential data leakage and preserves data privacy among customers. + +RSC creates a special system user with full privileges on Rubrik clusters. RSC makes Rest API calls as this system user. + *[ > ]: and then diff --git a/saas_common_backup_strikes_reports.md b/saas_common_backup_strikes_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..49694a169383428be4e52b8a51280d8afdf839c3 --- /dev/null +++ b/saas_common_backup_strikes_reports.md @@ -0,0 +1,20 @@ +# Backup strikes reports + +Source: https://docs.rubrik.com/en-us/saas/saas/common/backup_strikes_reports.html + +--- + +# Backup strikes reports + +A backup strike is an indication that an object could not successfully complete all backups scheduled on a single day. + +The backup strikes report displays a list of backup strikes data over the course of a compliance range of three or seven days. You can select the compliance range in the Backup Strikes Report menu. + +Strikes are calculated for all objects on the previous day, between 12:00 a.m. and 11:59 p.m. UTC. If updates are made to the SLA Domain or to objects, strikes are calculated and displayed the day the updates are made. + +Strikes are listed from left to right, starting with the most recent day of backups. + +A strike is indicated with a red x, a successful day of backups is indicated with a green dot, and a day without a scheduled snapshot is indicated with a grey dot. + +If an SLA Domain is scheduled to run backups every six hours in one day, there are a total of four backups scheduled in one day. If all four backups fail to complete, then the report indicates a strike with a red x. If at least one backup successfully completes, the report displays a green dot. + *[ > ]: and then diff --git a/saas_common_closing_a_support_tunnel.md b/saas_common_closing_a_support_tunnel.md new file mode 100644 index 0000000000000000000000000000000000000000..6465ca6cc88a02cacf1e8e401d2c84f35213d905 --- /dev/null +++ b/saas_common_closing_a_support_tunnel.md @@ -0,0 +1,32 @@ +# Closing a support tunnel + +Source: https://docs.rubrik.com/en-us/saas/saas/common/closing_a_support_tunnel.html + +--- + +# Closing a support tunnel + +After the Rubrik Support engineer resolves the issue in a Rubrik cluster by using the support tunnel you opened, close the support tunnel. + +## Before you begin + +Ensure that you have the Manage support tunnels system configuration permission. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Customer Support. + 4. Select Support Tunnel. + 5. For the Rubrik cluster that has an open support tunnel, click and select Close Support Tunnel. + 6. From the dropdown list, select a node and click Submit. + +## Results + +RSC closes the support tunnel for the selected node. + +RSC logs a message in the audit log. + *[ > ]: and then diff --git a/saas_common_cluster_details_page.md b/saas_common_cluster_details_page.md new file mode 100644 index 0000000000000000000000000000000000000000..cf0bc1ecc1674c6b429c3af319b107d7ef3577cc --- /dev/null +++ b/saas_common_cluster_details_page.md @@ -0,0 +1,18 @@ +# Cluster details page + +Source: https://docs.rubrik.com/en-us/saas/saas/common/cluster_details_page.html + +--- + +# Cluster details page + +Information about the cluster, configurations, and encryption status for a selected Rubrik cluster. + +The Cluster details page provides detailed information about the cluster, configurations, and encryption status for a selected Rubrik cluster. + +Metric | Description +---|--- +Cluster Overview | Displays information about the cluster, including its name, physical location, time zone, and status of the web server certificate. +System Details | Provides detailed specifications of the system, such as its Universally Unique Identifier (UUID), type, cluster version, appliance ID, memory capacity, number of nodes, CPU cores, and counts and sizes of HDDs and SSDs within the cluster. +Encryption Details | Displays the current status of encryption on the system, the type of encryption used, and the cipher suite used for secure data handling. Additionally, Manage Encryption is an option to rotate keys for a selected cluster on the Encryption Management page. + *[ > ]: and then diff --git a/saas_common_clusters_overview_page.md b/saas_common_clusters_overview_page.md new file mode 100644 index 0000000000000000000000000000000000000000..c95bb92ec958206a272563a83aafd7773662f33e --- /dev/null +++ b/saas_common_clusters_overview_page.md @@ -0,0 +1,55 @@ +# Clusters overview page + +Source: https://docs.rubrik.com/en-us/saas/saas/common/clusters_overview_page.html + +--- + +# Clusters overview page + +Information about specific details for a selected Rubrik cluster. + +Note: + +The Clusters overview page displays a banner with a message indicating that support for this cluster version will end on a specific date. Additionally, you can learn more about the Rubrik cluster release status by using the Open Release Table link. + +The Cluster overview page provides detailed information about a selected Rubrik cluster, including performance metrics, system events, hardware health statuses, capacity trends, compliance details, protection statuses, node health, and data reduction percentages. + +The following table describes the metrics for a selected Rubrik cluster. Metric | Description +---|--- +Cluster name | Displays the name of the cluster. If a Rubrik cluster is marked as isolated, is displayed next to the name of the isolated cluster, indicating the isolation status. Additionally, the cluster indicates whether it is connected or disconnected. +Performance and Tasks | Displays the cluster performance and task details. +Events | Displays the system status and the number of failed events aggregated over the selected time range. + + * Critical system events + * Replication failed + * Backup failed + * Archiving failed + +Clicking within the Events section displays events for the selected cluster. +Hardware Health | Displays various hardware statuses. + + * Power Supply Status + * Network Status + * DIMM Status + * Disk Status + * Chassis Status + * Node Status + +Additionally, Run Status Check initiates a health check for real-time updates. +Capacity | Displays the capacity information of the cluster. You can view capacity historical trends of cluster storage consumption for up to the past 12 months. The used capacity includes: + + * Total storage + * Used storage + * Available storage + * Snapshot storage + * Live Mount storage + * CDP + * System storage + * Pending snapshot storage + +Additionally, the capacity card displays the data archived under Archived Used, the average daily growth of data on the local cluster under Average Daily Growth, and the timestamp of the last update. With Manage Storage, you can modify snapshot retention for the objects or delete snapshots on the Snapshots Retention page, but you cannot modify the snapshot retention of a protected object. +Compliance | Displays the total number of protection details, categorized into objects that are in compliance and out of compliance. +Protection | Displays the total number of objects, categorized into protected, not protected, and objects without an assigned SLA Domain. +Node Status | Displays the health of the nodes within the cluster. +Data Reduction | Displays the percentage of reduction in total data size of the backup on the local cluster and archival location, calculated after deduplication and compression. + *[ > ]: and then diff --git a/saas_common_creating_a_report.md b/saas_common_creating_a_report.md new file mode 100644 index 0000000000000000000000000000000000000000..72f44e6d19f3e716ba982159b7ea4ef751de65a6 --- /dev/null +++ b/saas_common_creating_a_report.md @@ -0,0 +1,48 @@ +# Creating a report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/creating_a_report.html + +--- + +# Creating a report + +Use RSC to create reports using the templates available for each report type. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Reports. + +The Reports page appears, displaying a library of templates grouped by use case categories, such as Users & Org. Management and Capacity Management. Each category contains the related reports. + + 4. Click Create Report. + +The Create a Report wizard appears, showing the template categories and the related reports. + + 5. **Optional:** Use the navigation panel to browse the report templates by category, such as Audit & Compliance and Capacity Management. + +Each report category displays the templates it contains. + + 6. Select a category to view the available templates. + +Alternatively, you can use the Search by template name field to find the report template. A description of each report template is provided. + + 7. Select the report template to create and click Preview & Edit. + +The report template page appears. + + 8. **Optional:** Change the available filters. + 9. Change the report name. + +Each report needs its own unique name. To change the name of the report, click on the report name to show , then type in a new, unique name for the report. + + 10. Click Save to save the customized report. + +## Results + +RSC displays the newly created report. + *[ > ]: and then diff --git a/saas_common_creating_a_report_schedule.md b/saas_common_creating_a_report_schedule.md new file mode 100644 index 0000000000000000000000000000000000000000..30c4f7cf0b51671dec76a69513e26158b616eea5 --- /dev/null +++ b/saas_common_creating_a_report_schedule.md @@ -0,0 +1,49 @@ +# Creating a report schedule + +Source: https://docs.rubrik.com/en-us/saas/saas/common/creating_a_report_schedule.html + +--- + +# Creating a report schedule + +Create and store the schedule information for a report on the Reports page. You can use this stored schedule information when you want to send the report to the selected email addresses at specific intervals. + +## About this task + +You can create and store a schedule for a report when you want RSC to automatically send reports to the selected email addresses at specific intervals. You can create a schedule for all types of reports, except for the Data Security Posture Object Details report. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. From the list displayed on the left-side, select a report type. + +Reports of the selected type appear. + + 4. Select a report. + 5. Open the ellipsis menu and select Add schedule. + +After you create a schedule, the Add schedule option in the dropdown list changes to Schedules (number-of-schedules), where (number-of-schedules) is the number of schedules that already exist. + +The New schedule page appears. + + 6. In Schedule name, enter a name for the schedule. + 7. **Optional:** Specify the time and frequency for emailing the report. + 8. **Optional:** Click Add user or email address to select email addresses from the Email Address dropdown list. + 9. To receive the full report as an attachment in the selected email addresses, select the format of the report that is, CSV or PDF, or both the formats. + +If you do not select the format of the report, the email message displays only the first 100 rows of the report. + + 10. Click Add. + +The new schedule appears in the Schedules page. Hovering over on the created schedule provides you the options to edit or delete the schedule. You can create more report schedules using the Add New link. + + 11. When you have completed creating the required schedules, click Done. + +## Results + +RSC creates a schedule for the selected report. + *[ > ]: and then diff --git a/saas_common_creating_custom_object_capacity_over_time_report.md b/saas_common_creating_custom_object_capacity_over_time_report.md new file mode 100644 index 0000000000000000000000000000000000000000..50cf5f4f35710c62b69a380ce5ad9852cc4bee60 --- /dev/null +++ b/saas_common_creating_custom_object_capacity_over_time_report.md @@ -0,0 +1,49 @@ +# Creating a custom Object Capacity Over Time report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/creating_custom_object_capacity_over_time_report.html + +--- + +# Creating a custom Object Capacity Over Time report + +Create a custom Object Capacity Over Time report to view custom reports for a specific set of objects. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Reports. + +The Reports page appears. + + 4. Click Create Report > Object Capacity Over Time. + +The Object Capacity Over Time Report page appears. + + 5. Modify the report name. + +Each report must have a unique name. To modify the report name, click the report name to display the edit icon and enter the new name. + + 6. In the Object Name filter, select the object names used for the custom report. + +You can select multiple object names. Hovering over an object name displays additional available information about the object, including the object Type, Location, and Cluster. + +When selecting Location, location information is not available for historical data collected before April 1, 2024, for Object Capacity Over Time reports. + + 7. Select additional filters for the custom Object Capacity Over Time report. + +You can choose from Time, Assigned Org, Clusters, Location, and SLA Domain. You can select multiple filters. + +Hovering over a location displays additional available information about that object, including the Name, Type, and Cluster. + +When selecting Location, location information is not available for historical data collected before April 1, 2024 for Object Capacity Over Time reports. + + 8. Click Create. + +## Results + +RSC creates and displays the custom Object Capacity Over Time report for the selected set of objects with the selected filters. To view the created custom report, you can navigate to the Reports page and turn on View My Reports Only. + *[ > ]: and then diff --git a/saas_common_creating_role.md b/saas_common_creating_role.md new file mode 100644 index 0000000000000000000000000000000000000000..c3e0e24c832352d325eb68f3c1fb7fe1d111b366 --- /dev/null +++ b/saas_common_creating_role.md @@ -0,0 +1,61 @@ +# Creating a role + +Source: https://docs.rubrik.com/en-us/saas/saas/common/creating_role.html + +--- + +# Creating a role + +Create a role to grant permissions to user accounts. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users & Access, then select Roles. + +The list of roles appears. + + 4. Click Create Role. + +The Create Role wizard appears. + + 5. Select a method to create a role. + +Option| Description +---|--- +Custom role | Creates a custom role and adds permissions to access resources and to perform administrative tasks. +Pre-defined template | Creates a role using an existing template that contains a pre-selected set of permissions. Use the template as a starting point to add or delete permissions to modify the role. + + 6. In Data Management Privileges, click Configure to set the data management privileges for the role. + 7. In Assign System Configuration Privileges, click Configure to set the system configuration privileges for the role. + 8. In Rubrik application Privileges, click Configure to set the configuration privileges for Rubrik applications. + 9. Click Next. + +The Role Details section of the Create Role wizard appears. + + 10. In Role name, enter the name of the role. + 11. **Optional:** Click Add Description to enter the description of the role. + 12. Turn on Synchronize Role to CDM Clusters to sync the role with Rubrik CDM. + +You can only sync roles to CDM version 9.3.0 and later. + +The Role Details section displays the number of chosen clusters based on the permissions and clusters selected in the Data Management and System Configuration sections. It also displays the number of connected and disconnected clusters. You can click the number to get a list of these clusters. + + 13. Click Create. + +A message appears indicating that the role is created. + + 14. **Optional:** Click Go to Users Page. + +The Users page appears, displaying a list of assigned users. + + 15. Click Done. + +## Results + +RSC creates a new role and refreshes the Roles page. + *[ > ]: and then diff --git a/saas_common_creating_role_2.md b/saas_common_creating_role_2.md new file mode 100644 index 0000000000000000000000000000000000000000..7e3b6a639cff50c52ffb0c9552d6568884c2ec6b --- /dev/null +++ b/saas_common_creating_role_2.md @@ -0,0 +1,61 @@ +# Creating a role + +Source: https://docs.rubrik.com/en-us/saas/saas/common/creating_role_2.html + +--- + +# Creating a role + +Create a role to grant permissions to user accounts. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users & Access, then select Roles. + +The list of roles appears. + + 4. Click Create Role. + +The Create Role wizard appears. + + 5. Select a method to create a role. + +Option| Description +---|--- +Custom role | Creates a custom role and adds permissions to access resources and to perform administrative tasks. +Pre-defined template | Creates a role using an existing template that contains a pre-selected set of permissions. Use the template as a starting point to add or delete permissions to modify the role. + + 6. In Data Management Privileges, click Configure to set the data management privileges for the role. + 7. In Assign System Configuration Privileges, click Configure to set the system configuration privileges for the role. + 8. In Rubrik application Privileges, click Configure to set the configuration privileges for Rubrik applications. + 9. Click Next. + +The Role Details section of the Create Role wizard appears. + + 10. In Role name, enter the name of the role. + 11. **Optional:** Click Add Description to enter the description of the role. + 12. Turn on Synchronize Role to CDM Clusters to sync the role with Rubrik CDM. + +You can only sync roles to CDM version 9.3.0 and later. + +The Role Details section displays the number of chosen clusters based on the permissions and clusters selected in the Data Management and System Configuration sections. It also displays the number of connected and disconnected clusters. You can click the number to get a list of these clusters. + + 13. Click Create. + +A message appears indicating that the role is created. + + 14. **Optional:** Click Go to Users Page. + +The Users page appears, displaying a list of assigned users. + + 15. Click Done. + +## Results + +RSC creates a new role and refreshes the Roles page. + *[ > ]: and then diff --git a/saas_common_data_management_permission_types.md b/saas_common_data_management_permission_types.md new file mode 100644 index 0000000000000000000000000000000000000000..7fca453e748aa5da6b9c1ee74f267f7504dac133 --- /dev/null +++ b/saas_common_data_management_permission_types.md @@ -0,0 +1,18 @@ +# Data management permission types + +Source: https://docs.rubrik.com/en-us/saas/saas/common/data_management_permission_types.html + +--- + +# Data management permission types + +Information on data management permissions for a role based on object types, Rubrik clusters, or data sources. + +The following table describes the various approaches for assigning permissions to a role. + +Permission Type | Description +---|--- +Object type | Sets boundaries for permissions granted to a role based on the selected object types and SLA Domains. For each object type, the protectable objects, recovery targets, and the data management privileges must be specified.Using object types provide the most granular control for assigning data management permissions. +Cluster | Limits permission for a role to the selected Rubrik clusters, selected object types, and SLA Domains on those clusters.RSC applies the data management privileges to all current and future protectable objects and recovery targets on the Rubrik clusters. +Data sources | Configures permissions for a role based on selected data management privileges and SLA Domains.RSC applies the data management privileges to all current and future protectable objects and recovery targets on the Rubrik clusters. + *[ > ]: and then diff --git a/saas_common_data_security.md b/saas_common_data_security.md new file mode 100644 index 0000000000000000000000000000000000000000..747a0bf6f18364ab55e3db135faefc807f1c53f3 --- /dev/null +++ b/saas_common_data_security.md @@ -0,0 +1,16 @@ +# Data security + +Source: https://docs.rubrik.com/en-us/saas/saas/common/data_security.html + +--- + +# Data security + +RSC does not access the data on Rubrik clusters or on objects protected by Rubrik clusters. + +RSC works exclusively with metadata from Rubrik clusters, such as object size, type, or location. + +Data isolation is achieved by isolating individual customer data into logically partitioned databases. This prevents potential data leakage and preserves data privacy among customers. + +RSC ensures data residency by enabling instances based on the geographical location of customer data or the data centers. RSC addresses the strict regulatory and compliance requirements of different geographic locations. + *[ > ]: and then diff --git a/saas_common_deleting_a_report.md b/saas_common_deleting_a_report.md new file mode 100644 index 0000000000000000000000000000000000000000..9fa03fbfa06f358add845d45a446cd11edd9e728 --- /dev/null +++ b/saas_common_deleting_a_report.md @@ -0,0 +1,39 @@ +# Deleting a report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/deleting_a_report.html + +--- + +# Deleting a report + +Delete a report using RSC. + +## About this task + +Reports are based on account-level permissions. Deleted reports are unavailable to other users of the account. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. From the list displayed on the left-side, select a report type. + +Reports of the selected type appear. + + 4. Select a report. + +The selected report appears. + + 5. Click and select Delete. + +A confirmation prompt appears. + + 6. Click Yes, Delete Report. + +## Results + +RSC deletes the report. + *[ > ]: and then diff --git a/saas_common_deleting_a_report_schedule.md b/saas_common_deleting_a_report_schedule.md new file mode 100644 index 0000000000000000000000000000000000000000..9ae3f3848a9482db8de8f07af4178c3ffa48c292 --- /dev/null +++ b/saas_common_deleting_a_report_schedule.md @@ -0,0 +1,35 @@ +# Deleting a report schedule + +Source: https://docs.rubrik.com/en-us/saas/saas/common/deleting_a_report_schedule.html + +--- + +# Deleting a report schedule + +Delete a report schedule to stop sending that report. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. From the list displayed on the left-side, select a report type. + +Reports of the selected type appear. + + 4. Select a report. + +The selected report details page appears. + + 5. Open the ellipsis menu and select Schedules. + +The Schedules dialog box appears. + + 6. Hover over a schedule and click the delete icon. + +## Results + +RSC deletes the report scheduling information, and a confirmation notification appears. + *[ > ]: and then diff --git a/saas_common_deleting_a_role.md b/saas_common_deleting_a_role.md new file mode 100644 index 0000000000000000000000000000000000000000..5c8b9c4cc0320e69bb4efcc96191b9de839200f7 --- /dev/null +++ b/saas_common_deleting_a_role.md @@ -0,0 +1,44 @@ +# Deleting a role + +Source: https://docs.rubrik.com/en-us/saas/saas/common/deleting_a_role.html + +--- + +# Deleting a role + +Delete a role. + +## Before you begin + +To delete a role, first remove the role from all user accounts. + +The Owner role cannot be deleted. It can only be assigned or unassigned by a user with an Owner role. + +The Administrator role cannot be deleted. It can be assigned or unassigned only by a user with an Administrator or Owner role or any user with Manage Access permission. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users and Access. + 4. Click Roles. + +The list of roles appear. + + 5. Click the role name. + +The role details page appears. + + 6. Click Delete. + +Alternatively, open the ellipsis menu for the role and click Delete to delete a role. + + 7. When prompted, click Delete to confirm the role deletion. + +## Results + +RSC deletes the role and refreshes the Roles page. + *[ > ]: and then diff --git a/saas_common_deleting_ntp_server_rubrik_cluster.md b/saas_common_deleting_ntp_server_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..4826944e0e983385aa98207cc40f66e2a9f5d2ec --- /dev/null +++ b/saas_common_deleting_ntp_server_rubrik_cluster.md @@ -0,0 +1,40 @@ +# Deleting NTP servers for a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/deleting_ntp_server_rubrik_cluster.html + +--- + +# Deleting NTP servers for a Rubrik cluster + +Delete an NTP server from a Rubrik cluster if you do not need the NTP server for network time synchronization. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click NTP Servers. + 8. Click for an NTP server and select Delete NTP Server. + 9. Click Delete. + +## Results + +RSC deletes the NTP server from the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_deleting_static_route_cluster.md b/saas_common_deleting_static_route_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..09ab646b1d72b9b69e9aa08020351b6eda347124 --- /dev/null +++ b/saas_common_deleting_static_route_cluster.md @@ -0,0 +1,44 @@ +# Deleting a static route from a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/deleting_static_route_cluster.html + +--- + +# Deleting a static route from a Rubrik cluster + +Delete an unneeded static route from the routing table of a Rubrik cluster. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Note: + +You cannot delete a default static route. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click Routing Table. + 8. Click for a route and select Delete Route. + 9. Click Delete. + +## Results + +RSC deletes the static route from the cluster. + *[ > ]: and then diff --git a/saas_common_deleting_vlans_cdm.md b/saas_common_deleting_vlans_cdm.md new file mode 100644 index 0000000000000000000000000000000000000000..75add4330517e3e80dc0429d439b240e542b2b78 --- /dev/null +++ b/saas_common_deleting_vlans_cdm.md @@ -0,0 +1,45 @@ +# Deleting VLANs in CDM + +Source: https://docs.rubrik.com/en-us/saas/saas/common/deleting_vlans_cdm.html + +--- + +# Deleting VLANs in CDM + +Remove the VLANs you no longer need for the Rubrik cluster network running CDM version 9.2.0 or earlier. + +## About this task + +VLANs are often deleted from a Rubrik cluster when their configurations change. After a configuration change completes, the configurations are added back to the Rubrik cluster. When the Rubrik cluster does not have VLANs configured, the option to delete the VLANs is not available. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The Cluster details page appears. + + 5. Click Network Details. + +The Network Details page appears. + + 6. Click for the Network Details page and select Delete VLANs. + +The Delete VLANs page appears. + + 7. In Select VLANs, select the VLANs to delete. + +You can select the VLAN ID check box to select all the VLANs displayed in the table. + + 8. Click Next. + +The Confirmation page appears. + + 9. Review the summary information and click Delete. + +## Results + +RSC deletes the selected VLANs from the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_deleting_vlans_rubrik_cluster.md b/saas_common_deleting_vlans_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..453dbb3bc894f14e5c0d47887d28b57d2f1bfd31 --- /dev/null +++ b/saas_common_deleting_vlans_rubrik_cluster.md @@ -0,0 +1,53 @@ +# Deleting VLANs from a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/deleting_vlans_rubrik_cluster.html + +--- + +# Deleting VLANs from a Rubrik cluster + +Delete VLANs from a Rubrik cluster to remove unnecessary network segmentation and free up resources. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +VLANs are often deleted from a Rubrik cluster when their configurations changes. After configuration changes complete, the configurations are added back to the Rubrik cluster. When the Rubrik cluster does not have VLANs configured, the option to delete VLANs is not available. + +Note: + +You cannot delete a VLAN if it is used for data or management network. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click for the network list and select Delete VLANs. + +The Delete VLANs wizard appears. + + 8. In Select VLANs, select the VLANs to delete. + +You can select the VLAN ID check box to select all the displayed VLANs in the table. + + 9. Click Next. + 10. Review the details and click Delete. + +## Results + +RSC deletes the selected VLAN from the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_displaying_a_report.md b/saas_common_displaying_a_report.md new file mode 100644 index 0000000000000000000000000000000000000000..70edc7085cda86863cb029af9be8d165cf712718 --- /dev/null +++ b/saas_common_displaying_a_report.md @@ -0,0 +1,37 @@ +# Displaying a report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/displaying_a_report.html + +--- + +# Displaying a report + +View an RSC report. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Reports. + +The Reports page appears, displaying a library of templates grouped by use case categories, such as Users & Org. Management and Capacity Management. Each category contains the related reports. + + 4. Select the report to view. + +Alternatively, in the Search report name field, enter a report name to find a specific report. + +The selected report appears. + + 5. **Optional:** Customize the view of the report. + +Use column sorting, filtering, and search to customize the view. + + 6. Click Save. + +## Results + +The resulting report shows the selected customizations. + *[ > ]: and then diff --git a/saas_common_downloading_a_report.md b/saas_common_downloading_a_report.md new file mode 100644 index 0000000000000000000000000000000000000000..e4208e6ce46279bb5ea8b695504352914fa48288 --- /dev/null +++ b/saas_common_downloading_a_report.md @@ -0,0 +1,52 @@ +# Downloading a report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/downloading_a_report.html + +--- + +# Downloading a report + +Download reports from RSC for monitoring or auditing. + +## About this task + +RSC provides the ability to download the available report types, except for the Data Security Posture Object Details report. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. From the list displayed on the left-side, select a report type. + +Reports of the selected type appear. + + 4. Select a report. + +The selected report appears. + + 5. Click Report Settings. + +The Data Unit Selection wizard appears. + + 6. From the drop-down list, select a data unit for the report. + +Data Unit| Used for +---|--- +Rubrik Default | Automatically selects the optimal data format for you. CSV files will always be in bytes. +MB (Megabytes) | Ideal for smaller data sizes. +GB (Gigabytes) | Ideal for mid-sized data. +TB (Terabytes) | Ideal for larger datasets. +PB (Petabytes) | Ideal for extremely large datasets. + + 7. Click Save. + 8. From the Save drop-down list, select a format. + * Download CSV + * Download PDF + +## Results + +RSC provides the formatted report for download. + *[ > ]: and then diff --git a/saas_common_edit_dns_search_domains_cdm.md b/saas_common_edit_dns_search_domains_cdm.md new file mode 100644 index 0000000000000000000000000000000000000000..d4eec63c60cea497971bb2d907cc14baee820279 --- /dev/null +++ b/saas_common_edit_dns_search_domains_cdm.md @@ -0,0 +1,35 @@ +# Editing DNS and search domains in CDM + +Source: https://docs.rubrik.com/en-us/saas/saas/common/edit_dns_search_domains_cdm.html + +--- + +# Editing DNS and search domains in CDM + +Edit the DNS and search domains for a Rubrik cluster running CDM version 9.2.0 or earlier to maintain network efficiency, security, and reliability. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The Cluster details page appears. + + 5. Click Network Details. + +The Network Details page appears. + + 6. Click for the Network Details page and select DNS & Search Domains. + +The DNS Servers page appears. + + 7. In DNS Servers, review the server list and update the list if necessary. + 8. In Search Domains, review the domains included and update the address if necessary. + 9. Click Confirm. + +## Results + +RSC edits the DNS and search domains for the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_edit_dns_search_domains_rubrik_cluster.md b/saas_common_edit_dns_search_domains_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..5e6b0463aef8f90af7083631f2f0a39912f914e1 --- /dev/null +++ b/saas_common_edit_dns_search_domains_rubrik_cluster.md @@ -0,0 +1,41 @@ +# Editing DNS and search domains for a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/edit_dns_search_domains_rubrik_cluster.html + +--- + +# Editing DNS and search domains for a Rubrik cluster + +Edit the DNS and search domains for a Rubrik cluster to improve the network efficiency, security, and accessibility. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click DNS & Search Domains. + 8. In DNS Servers, review the server list and update the list if necessary. + 9. In Search Domains, review the domains included and update the address if necessary. + 10. Click Save. + +## Results + +RSC edits the DNS and search domains for the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_editing_a_report.md b/saas_common_editing_a_report.md new file mode 100644 index 0000000000000000000000000000000000000000..8bf180813328b6d231d9b6f77f6b6e4945d552c5 --- /dev/null +++ b/saas_common_editing_a_report.md @@ -0,0 +1,35 @@ +# Editing a report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_a_report.html + +--- + +# Editing a report + +Use the available options to edit or customize a report. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. From the list displayed on the left-side, select a report type. + +Reports of the selected type appear. + + 4. Select a report. + +The selected report appears. + + 5. Modify the editable fields. + +Change the name, edit filters, edit the schedule. + + 6. Click Save. + +## Results + +RSC displays the edited report. + *[ > ]: and then diff --git a/saas_common_editing_a_report_schedule.md b/saas_common_editing_a_report_schedule.md new file mode 100644 index 0000000000000000000000000000000000000000..ebd6f8d43bc0302942b1cdeb7b66bc68b576000d --- /dev/null +++ b/saas_common_editing_a_report_schedule.md @@ -0,0 +1,46 @@ +# Editing a report schedule + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_a_report_schedule.html + +--- + +# Editing a report schedule + +Edit an existing report schedule to change and store the name of the report schedule, subscription frequency and time, and the email recipient. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. From the list displayed on the left-side, select a report type. + +Reports of the selected type appear. + + 4. Select a report. + +The selected report page appears. + + 5. Open the ellipsis menu and select Schedules. + +The Schedules pane appears. + + 6. Hover over a schedule and click the edit icon. + +The Editing pane appears. + + 7. Make changes to the fields. + 8. **Optional:** Click Remove user. + +Selecting this option prevents the email account from receiving the scheduled report email. + +The default RSC user account cannot be removed. + + 9. Click Update. + +## Results + +RSC updates the schedule for the selected report. + *[ > ]: and then diff --git a/saas_common_editing_a_role.md b/saas_common_editing_a_role.md new file mode 100644 index 0000000000000000000000000000000000000000..c59679620bf7ac303fa42b6fa3c5edd6015f3085 --- /dev/null +++ b/saas_common_editing_a_role.md @@ -0,0 +1,43 @@ +# Editing a role + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_a_role.html + +--- + +# Editing a role + +Add additional permissions to or remove particular permissions from the role. + +## About this task + +The permissions for the owner and administrator roles cannot be edited. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users and Access. + 4. Select Roles. + +The list of roles appear. + + 5. Select a role. + +The role details page appears. + + 6. Click Edit. + +The Edit an existing role wizard appears. + + 7. In Data management, click Edit to modify the data management privileges for an existing role. + 8. In System configuration, click Edit to modify the cluster configuration privileges for an existing role. + 9. In Rubrik application, click Edit to modify the configuration privileges for an existing role. + 10. Click Save. + +## Results + +RSC makes changes to the role and refreshes the roles detail page. + *[ > ]: and then diff --git a/saas_common_editing_ntp_server_rubrik_cluster.md b/saas_common_editing_ntp_server_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..404ee738727722cd05e870751b42cf078da862db --- /dev/null +++ b/saas_common_editing_ntp_server_rubrik_cluster.md @@ -0,0 +1,47 @@ +# Editing NTP servers for a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_ntp_server_rubrik_cluster.html + +--- + +# Editing NTP servers for a Rubrik cluster + +Edit an NTP server for a Rubrik cluster to update NTP server address, key ID, key, and key type associated with the NTP server. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click NTP Servers. + 8. Click for an NTP server and select Edit NTP Server. + +The Edit NTP Server dialog box appears. + + 9. Update the required fields. + +You can update the values for NTP server address, key ID, key, and key type. + + 10. Click Update. + +## Results + +RSC updates the NTP server based on the edited values. + *[ > ]: and then diff --git a/saas_common_editing_role_asmt_multiple_obj.md b/saas_common_editing_role_asmt_multiple_obj.md new file mode 100644 index 0000000000000000000000000000000000000000..3b0fd923f6f46ef610820eb7695206ce185daabc --- /dev/null +++ b/saas_common_editing_role_asmt_multiple_obj.md @@ -0,0 +1,70 @@ +# Editing role assignments for multiple users, SSO groups, or service accounts + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_role_asmt_multiple_obj.html + +--- + +# Editing role assignments for multiple users, SSO groups, or service accounts + +Change the roles that are assigned to multiple users, SSO groups, or service accounts to modify the privileges associated with the objects. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Select Users and Access. + 4. Select the object-specific option to begin editing role assignments. + * Users + * SSO Groups + * Service Accounts + +The selected object page appears. + + 5. Select multiple objects. + +Use the search field to find objects whose roles need to be edited. + + 6. Click the popover icon in the Roles column for additional information in a tooltip. + +Clicking the role name in the tooltip shows the role details page. Clicking More in the tooltip shows the View Role Assignment dialog box for the object. + + 7. Click Edit Role Assignment. + +The Edit Role Assignment window appears. + + 8. Select an option for editing roles. + +Option| Description +---|--- +Replace the current role assignments | Replaces all existing assigned roles with the new roles. At least one owner is required for an account. This option is not available if you select all owner accounts for replacement. +Assign and unassign individual roles | Adds roles to or removes roles from the existing role assignment without replacing the current roles.The maximum number of owner roles for an account is five. If you select more than five users, the Set owner option is not available. + + 9. Click Next. + +The Select Roles page appears with no roles selected when you choose Replace the current role assignments. The Select Roles page appears with roles that are assigned to all objects selected, by default, when you choose Assign and unassign individual roles. + + 10. (Replace the current role assignments) Select one or more roles. + +Use the search field to find roles. + +Clicking the selected objects link displays information about the selected objects. Clicking the link in the Current Assignment Column displays the objects to which the role is assigned. + + 11. (Assign and unassign individual roles) Select one or more roles to assign or unassign. + +Use the search field to find roles. + +Clicking the selected objects link displays information about the selected objects. Clicking the link in the Current Assignment Column displays the objects the role is assigned to. + + 12. Click Save. + +## Results + +RSC replaces the existing role assignment of the selected objects with the selected roles. RSC assigns the new role to the selected objects and grants access to the protected resources associated with this new role. The change is indicated in the popover icon on the specific page and in the Audit Logs. + *[ > ]: and then diff --git a/saas_common_editing_role_asmt_single_obj.md b/saas_common_editing_role_asmt_single_obj.md new file mode 100644 index 0000000000000000000000000000000000000000..e43621724aa62d337364ae56d5ea0fc5692098a4 --- /dev/null +++ b/saas_common_editing_role_asmt_single_obj.md @@ -0,0 +1,48 @@ +# Editing role assignments for a single user, SSO group, or service account + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_role_asmt_single_obj.html + +--- + +# Editing role assignments for a single user, SSO group, or service account + +Edit the roles that are assigned to a single user, SSO group, or service account to modify the privileges associated with the object. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Select Users and Access. + 4. Select the object-specific option to begin editing role assignments. + * Users + * SSO Groups + * Service Accounts + +The page for the selected object appears. + + 5. Select an object. + +Use the search field to find a specific object. + + 6. **Optional:** Click the popover icon in the Roles column for additional information in a tooltip. + +Clicking the role name in the tooltip shows the role details page. Clicking More in the tooltip shows the View Role Assignment dialog box for the object. + + 7. Click Edit Role Assignment. + +The Edit Role Assignment dialog box appears with the complete list of roles. The Current Assignment column indicates whether they are assigned or unassigned to the object. + + 8. Select or clear the checkboxes to edit the roles for the object. + 9. Click Save. + +## Results + +RSC assigns the new role to the selected objects and grants access to the protected resources associated with this new role. RSC indicates the change in the popover icon on the specific page and in the Audit Logs. + *[ > ]: and then diff --git a/saas_common_editing_support_access.md b/saas_common_editing_support_access.md new file mode 100644 index 0000000000000000000000000000000000000000..9854745605fe0332bba10664263302e3d22b73ea --- /dev/null +++ b/saas_common_editing_support_access.md @@ -0,0 +1,39 @@ +# Editing support access duration + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_support_access.html + +--- + +# Editing support access duration + +An RSC user account with owner or administrator privileges can increase the support access duration for an existing support access grant. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Settings. + +A new tab displaying the settings menu opens on your browser. + + 3. Click Customer Support and select Support Access. + +The Support Access page appears. + + 4. Open the ellipsis menu for a support access instance and select Edit Access. + +You can only edit the access duration for a support access instance that is in open state. + +The Edit Support Access page appears. + + 5. Edit the access duration and click Save. + +You must only open the Edit Access page if you want to increase the access duration. If you attempt to decrease the current access duration, or make no changes to the existing duration, then a message about invalid duration appears and the existing duration remains the same. + +A confirmation message appears. + + 6. Click Done. + +## Results + +The support access duration for the selected RSC user account is modified. RSC increases the duration for the selected support access grant. + *[ > ]: and then diff --git a/saas_common_editing_vlans_rubrik_cluster.md b/saas_common_editing_vlans_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..b92ed485a4ed52b729e76f161fd45c4bbeb96273 --- /dev/null +++ b/saas_common_editing_vlans_rubrik_cluster.md @@ -0,0 +1,54 @@ +# Editing VLANs of a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/editing_vlans_rubrik_cluster.html + +--- + +# Editing VLANs of a Rubrik cluster + +Edit a VLAN to update the network details associated with the VLAN. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +You can update the VLAN name, subnet mask, and gateway of an existing VLAN associated with a Rubrik cluster. You can also update the VLAN IP addresses of the nodes in the cluster. + +Note: + +You cannot edit a VLAN if it is used for the data or management network. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Click Manage Cluster Settings. + +The Cluster Settings page for the Rubrik cluster appears. + + 6. Click Network. + +The Network page appears. + + 7. Click for the network list and select Edit VLAN. + +The Edit VLAN wizard appears. + + 8. Select a VLAN to edit. + 9. Edit the values for the VLAN Name, Subnet Mask, and Gateway fields. + 10. In VLAN IP Address, enter the VLAN IP addresses for each node in the cluster. + +You can enter the VLAN IP address for the first node, and then click the Auto-Populate IP Address to auto-populate the IP addresses for the other nodes. Auto-populate increments the IP address of the first node to add the IP addresses for the other nodes. + + 11. Click Update. + +## Results + +RSC updates the VLAN details of the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_enabling_support_access.md b/saas_common_enabling_support_access.md new file mode 100644 index 0000000000000000000000000000000000000000..9af4df782939dc4166b6ba40159dd35f6a942ee2 --- /dev/null +++ b/saas_common_enabling_support_access.md @@ -0,0 +1,41 @@ +# Enabling support access + +Source: https://docs.rubrik.com/en-us/saas/saas/common/enabling_support_access.html + +--- + +# Enabling support access + +An RSC user account with owner or administrator privileges can enable support access for an RSC user account. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Settings. + +A new tab displaying the settings menu opens on your browser. + + 3. Click Customer Support and select Support Access. + +The Support Access page appears. + + 4. Click Grant Support Access. + +The Grant Support Access page appears. + + 5. Enter the Access duration and select from the drop-down list to choose days or weeks. + +The number of days or weeks entered in the access duration is the duration during which Rubrik Support has access to your RSC user account. + + 6. Enter the Ticket Numberassociated with your submitted Rubrik Support case. + 7. Select Impersonated User that you want Rubrik Support to impersonate. + 8. Click Grant. + +A confirmation message appears. + + 9. Click Done. + +## Results + +Rubrik Support has access to the selected user's RSC account in read-only mode for the specified duration. + *[ > ]: and then diff --git a/saas_common_encryption.md b/saas_common_encryption.md new file mode 100644 index 0000000000000000000000000000000000000000..e15d4dc45a87edb7025450ba828161f7085734cc --- /dev/null +++ b/saas_common_encryption.md @@ -0,0 +1,16 @@ +# Encryption + +Source: https://docs.rubrik.com/en-us/saas/saas/common/encryption.html + +--- + +# Encryption + +Encryption restricts the ability of an unauthorized party to read data. + +RSC requires strong ciphers with forward secrecy for all connections, and uses a strong access key for authentication of Rubrik clusters. Data transmission between RSC and Rubrik clusters is encrypted with the Transport Layer Security (TLS) protocol. RSC accesses and manipulates data on Rubrik clusters exclusively over HTTPS, using TLS v1.2 only. + +RSC uses TLS v1.2 and strong ciphers with forward secrecy for internal and external communication. + +RSC stores and encrypts data at rest with AES-256 encryption using a symmetric key algorithm and keys sized at 256 bits. Data is encrypted before being written to disk and decrypted during read operations. + *[ > ]: and then diff --git a/saas_common_events.md b/saas_common_events.md new file mode 100644 index 0000000000000000000000000000000000000000..532a99e323d989b024e4d27f48eb508097c359e6 --- /dev/null +++ b/saas_common_events.md @@ -0,0 +1,13 @@ +# Events + +Source: https://docs.rubrik.com/en-us/saas/saas/common/events.html + +--- + +# Events + +RSC events identify, isolate, and prioritize events and provide with a unified view of all Rubrik events. + +The Events page displays all connected Rubrik cluster events in the local timezone. The feature also displays an audit log that shows messages for system events on the connected Rubrik clusters and for the RSC domain. + +The Events page provides easy-to-use filters and options to perform a real-time search for point-in-time events. diff --git a/saas_common_events_page.md b/saas_common_events_page.md new file mode 100644 index 0000000000000000000000000000000000000000..73e6987b780424d71aa35fcec7ebd3355b6942af --- /dev/null +++ b/saas_common_events_page.md @@ -0,0 +1,47 @@ +# Events page + +Source: https://docs.rubrik.com/en-us/saas/saas/common/events_page.html + +--- + +# Events page + +The Events page displays the events of all connected Rubrik clusters in the local time zone. + +RSC tracks, monitors, and displays all events of all connected Rubrik clusters when no filter is applied. + +Change filters to change the Events page view dynamically. + +The following table describes the RSC event filters. + +Filter | Description +---|--- +Time range | Displays events aggregated over the specified time. + + * Past 2 hours + * Past 24 hours + * Past 7 days + * Past 30 days + * CustomWith the Custom date range, you can specify a date range to include a specific number of days, including beyond 30 days. + + +Clusters | Displays events on Rubrik clusters connected to RSC or RSC native events. +Severity | Displays the severity of the events. + + * Critical - System event that requires attention, such as failed backup, archiving, or replication. + * Warning - System event finished with a backup, archiving, or recovery warning. + * Informational - System event for information only. + + +Status | Displays events based on the event status. + + * Failure + * Running + * Completed + * Canceled + * Queued + + +Event type | Displays events based on the specified type. This filter supports multi-selection. The Anomaly event type is visible and supported only when you have a valid license for Data Threat Analytics. +Object type | Displays events of the specified object type related to the connected Rubrik clusters on RSC, such as virtual machines, servers, and applications. + *[ > ]: and then diff --git a/saas_common_getting_started_with_rsc.md b/saas_common_getting_started_with_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..4a1e36caaddb619b1d9d8f1084e98259f0d1116f --- /dev/null +++ b/saas_common_getting_started_with_rsc.md @@ -0,0 +1,15 @@ +# Getting started with RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/common/getting_started_with_rsc.html + +--- + +# Getting started with RSC + +To start using Rubrik Security Cloud, add authorized user accounts before adding Rubrik clusters. + +Rubrik sets up the initial user account for the RSC domain and sends an email invitation to the primary owner from this account. After setting up the initial user account, the owner can invite other users to set up accounts on the domain. + +Any user account in the RSC domain with cluster-management permissions can add Rubrik clusters to the domain. + +RSC uses HTTPS to transmit data between RSC and Rubrik clusters. RSC requires that each Rubrik cluster enable outbound port 443 in both firewall and proxy settings. diff --git a/saas_common_groupings.md b/saas_common_groupings.md new file mode 100644 index 0000000000000000000000000000000000000000..a4ae64bbe4197942f8df3fc285585beec2a2027c --- /dev/null +++ b/saas_common_groupings.md @@ -0,0 +1,67 @@ +# Groupings + +Source: https://docs.rubrik.com/en-us/saas/saas/common/groupings.html + +--- + +# Groupings + +Apply groupings to view aggregated values for the selected report. + +Use groupings to combine data for a filter within the report. + +For example, the Compliance report displays the compliance status of the selected data source. Use the Cluster grouping to view the compliance status of each cluster within the source. + +The following table lists the groupings available for reports. + +Grouping | Description | Availability +---|---|--- +Cluster | The data is grouped by the cluster. | + + * Compliance + * Protection + * Capacity + * Event + * Protection Tasks Details + * Recovery Tasks Details + + +Cluster type | The data is grouped by the cluster type. | + + * Infrastructure + * Compliance + * Protection + * Capacity + * Events + * Protection Tasks Details + * Recovery Tasks Details + + +Object type | The data is grouped by the object type. | + + * Compliance + * Protection + * Capacity + * Events + * Protection Tasks Details + * Recovery Tasks Details + * Data Security Posture Object Details + + +Events | The number of events for each event type. This is the default grouping for the Events report. | Events +Time | + + * Number or sum of column values based on time. + * Time granularity for charts is fixed or inferred by RSC based on the selected time range. + +| + + * Infrastructure + * Compliance + * Protection + * Capacity + * Events + * Protection Tasks Details + * Recovery Tasks Details + + *[ > ]: and then diff --git a/saas_common_limitations.md b/saas_common_limitations.md new file mode 100644 index 0000000000000000000000000000000000000000..a4a3d061ced10e2f6515a73492515db0cc8873cd --- /dev/null +++ b/saas_common_limitations.md @@ -0,0 +1,34 @@ +# Limitations + +Source: https://docs.rubrik.com/en-us/saas/saas/common/limitations.html + +--- + +# Limitations + +Review the limitations of RSC reporting. + +RSC reporting has the following limitations: + + * RSC only manages reports for Rubrik clusters with access to RSC. + * RSC synchronizes most data with connected Rubrik clusters in real time. Report synchronization between Rubrik clusters and RSC can take a few hours. + * For reporting purposes, RSC retains metadata from the data synchronization instance with Rubrik clusters. + +## Report customization + +Report customizations are available to allow better reporting experience. + +RSC changes chart data, such as compliance, protection, infrastructure, and event by customizing reports. + +Change filters or groupings to customize default, preconfigured, or previously customized reports. + +RSC provides the following report customizations: + + * Customize charts and tables with pre-defined groups (such as Cluster Type, Cluster, Object Type, and Time). Groupings vary based on the report type. + * Apply and save filters (such as Time range, Clusters, Object Type). + * Convert charts/tables into time-based or PIT-based format, with the exception of the Infrastructure report/chart. + +RSC manages reports based on account-level permissions. + +Creating, deleting, or editing reports in a given account impacts users within the same account. + *[ > ]: and then diff --git a/saas_common_navigation_history.md b/saas_common_navigation_history.md new file mode 100644 index 0000000000000000000000000000000000000000..a6aaf942ea0bd9c63c9bf40abb880aaf19d1cb1c --- /dev/null +++ b/saas_common_navigation_history.md @@ -0,0 +1,43 @@ +# RSC navigation history + +Source: https://docs.rubrik.com/en-us/saas/saas/common/navigation_history.html + +--- + +# Notifications and release notes + +You can access notifications and see information related to pending tasks on the Notifications tab. You can view RSC release information on the Release Notes tab. + +The icon provides options to access the product notifications and release notes associated with RSC. The notifications provide a way for RSC to communicate necessary information and alerts to you. The Notifications tab in RSC notifies you when an event relevant to you occurs. + +The notifications inform you about necessary information, such as the following: errors, failures, downtime, insights, subscription alerts, and any actionable tasks in RSC. The badges for notifications or release notes indicate unread messages in the lists. The most recent notifications or release notes appear at the top of a list. When you open a notification with a link for an actionable task, clicking the link takes you to the RSC page relevant to the notification. + +The Notification tab lists only the notifications that arrived in the last 30 days. RSC removes any notification older than 30 days. + +The Release Notes tab lists all the release notes for RSC# Notifications and release notes + +You can access notifications and see information related to pending tasks on the Notifications tab. You can view RSC release information on the Release Notes tab. + +The icon provides options to access the product notifications and release notes associated with RSC. The notifications provide a way for RSC to communicate necessary information and alerts to you. The Notifications tab in RSC notifies you when an event relevant to you occurs. + +The notifications inform you about necessary information, such as the following: errors, failures, downtime, insights, subscription alerts, and any actionable tasks in RSC. The badges for notifications or release notes indicate unread messages in the lists. The most recent notifications or release notes appear at the top of a list. When you open a notification with a link for an actionable task, clicking the link takes you to the RSC page relevant to the notification. + +The Notification tab lists only the notifications that arrived in the last 30 days. RSC removes any notification older than 30 days. + +The Release Notes tab lists all the release notes for RSC releases. Based on the information, RSC sorts the release notes into the following categories: + + * New features introduced in a release, which are indicated by the New label + * Updates to features, which are indicated by the Updates label + * Issues fixed in a release version, which are indicated by the Issues Fixed label + +You can expand a release note to view additional details, such as CDM dependencies and limitations, if any. + +# RSC navigation history + +You can view the navigation history for the recently visited pages in RSC. + +When you hover over the header icon on any page in RSC, you can view the navigation history of up to 20 recently visited pages during a session. When the number of recently visited pages exceeds 20, the last item in the list is removed. + +The navigation history list is unique to the user, preserves the custom set of filters applied on the recently visited pages, and is also session-specific, that is, the navigation history is not shared among the other RSC tabs. + +The navigation history list is cleared when you log out, log in, and refresh your browser. diff --git a/saas_common_node_replacement_rsc.md b/saas_common_node_replacement_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..7f022686748579d813ea1fc9ad6fda0e3d793657 --- /dev/null +++ b/saas_common_node_replacement_rsc.md @@ -0,0 +1,44 @@ +# Node replacement in RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/common/node_replacement_rsc.html + +--- + +# Node replacement in RSC + +You can use RSC to replace a node in a Rubrik cluster or a supported third-party hardware cluster. You can replace faulty node hardware while keeping the same set of disks intact. + +You can replace a node in a Rubrik cluster or a supported third-party hardware cluster to address one of the following scenarios: + + * Replacing a node with hardware failure that does not include a disk failure. You can contact Rubrik Support if you experience software or disk failure. + * Reconfiguring a node by removing and adding it back logically. + +If you need a new node to replace an old node in a Rubrik cluster, you can contact Rubrik Support to purchase a new node. + +RSC does not support node replacement on a cloud cluster. RSC requires that you do not remove a node physically before RSC logically removes the node from the cluster. + +Before starting the node replacement task, RSC requires that you fulfill the prerequisites for node replacement. + +RSC requires that you set up a quorum authorization policy to request additional approvals for replacing a node. A quorum authorization policy prevents accidental or malicious replacement of a node by a compromised administrator. A global administrator can set up a quorum authorization policy to request additional approvals for replacing a node. + +To replace a node, RSC requires that you assign a user role to a user with the add cluster nodes and remove cluster node permissions. + +After you initiate the node replacement task for a healthy node, RSC drains the selected node to transfer the data from the selected node to other nodes in the cluster, ensuring that the cluster data has proper failure tolerance. RSC cannot drain data from an unhealthy node. You can choose one of the following node data transfer options: + + * Full Node Drain: A Full Node Drain makes replicas of the node data to ensure that the cluster has failure tolerance for your data on the selected node to replace. A Full Node Drain can take several hours or days to complete depending on the amount of data. + * Quick Node Drain: A Quick Node Drain does not make any replicas of your node data and can complete within a few minutes. However, your data on the selected node becomes unavailable if another node or disk failure occurs during the node replacement process. + +For the data transfer, RSC requires you to ensure that sufficient space is available for the data to be transferred to other nodes of the cluster. + +After transferring the data, RSC removes the node metadata from the cluster and resets the node. This task takes about 30 minutes to complete. + +Warning: + +You cannot cancel the node replacement after RSC completes the data transfer. You can cancel the node replacement during the data transfer. However, if you cancel a node replacement during the data transfer, RSC does not transfer back the data already transferred from the node. + +After RSC completes the logical removal of a node, you can physically replace the old node with a new node. + +Important: + +Rubrik recommends that you initiate the node replacement after receiving the new node and then carefully place the old disk into the new node to avoid any data loss. + *[ > ]: and then diff --git a/saas_common_object_backup_task_summary_report.md b/saas_common_object_backup_task_summary_report.md new file mode 100644 index 0000000000000000000000000000000000000000..8d2d44b1cfe785e284780ad9f71a09255b3f7f32 --- /dev/null +++ b/saas_common_object_backup_task_summary_report.md @@ -0,0 +1,37 @@ +# Object Backup Task Summary report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/object_backup_task_summary_report.html + +--- + +# Object Backup Task Summary report + +The Object Backup Task Summary report provides information about scheduled backup tasks that are triggered by the protection policy of the assigned SLA Domain. + +You can view information about the scheduled backup tasks that are triggered by the assigned SLA Domain, total number of daily expected backup tasks for each object along with the number of successful, failed, canceled, and missed tasks. + +Note: + +This report does not include information for the current day. The report does not include information about on-demand backup tasks. + +You can view various Object Capacity graphs based on the Top 10 Missed Tasks by Object Name and Top 10 by SLA Domain filters. + +You can use the Object Backup Task Summary report to perform the following actions: + + * Selecting columns to include in the report + * Editing the name of the report, modifying the filters, and saving the report for future reference + * Downloading the report either in the CSV format or as a PDF document + * Emailing the report to the required email addresses + * Adding, editing, or deleting a report schedule + * Deleting a report + +Based on the Rubrik CDM version you are using, you can view the data for each of your clusters as follows: + + * For all the Rubrik CDM versions, you can view the data for each of your clusters that is running Rubrik CDM version 9.2.0 or later. + * For Rubrik CDM version 9.1.x, you can view the data for each of your clusters that is running Rubrik CDM version 9.1.2 or later. + + * For Rubrik CDM version 9.0.x, you can view the data only for clusters with Rubrik CDM version 9.0.3-p5 or later. + + * For Rubrik CDM version 8.1.x, you can view the data only for clusters with Rubrik CDM version 8.1.3-p11 or later. + + *[ > ]: and then diff --git a/saas_common_opening_a_support_tunnel.md b/saas_common_opening_a_support_tunnel.md new file mode 100644 index 0000000000000000000000000000000000000000..1645d7771fcb4ac8f387cd58f562a6f638bc33ff --- /dev/null +++ b/saas_common_opening_a_support_tunnel.md @@ -0,0 +1,39 @@ +# Opening a support tunnel + +Source: https://docs.rubrik.com/en-us/saas/saas/common/opening_a_support_tunnel.html + +--- + +# Opening a support tunnel + +Open a support tunnel to allow the Rubrik Support engineer to access a Rubrik cluster and resolve hardware or software issues, or both. + +## Before you begin + +Ensure that you have the Manage support tunnels system configuration permission. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Customer Support. + 4. Select Support Tunnel. + 5. For a Rubrik cluster that is in the connected state, click and select Open Support Tunnel. + 6. For the Timeout window, enter a value, in hours. + +Inactivity timeout is the default setting, and the default value is 96 hours. When the value is 0, the support tunnel remains open indefinitely. + +You can switch between inactivity timeout and absolute timeout by logging in to a Rubrik cluster through SSH and using commands. + + 7. In Select the node you want to open, select a cluster node to be accessed through the support tunnel. + 8. Click Submit. + +## Results + +RSC opens the support tunnel for the specified number of hours. + +RSC logs a status message in the audit log. + *[ > ]: and then diff --git a/saas_common_outbound_connection_through_ports.md b/saas_common_outbound_connection_through_ports.md new file mode 100644 index 0000000000000000000000000000000000000000..b51560115785a3c50e2b688efa764b595ad9f6a8 --- /dev/null +++ b/saas_common_outbound_connection_through_ports.md @@ -0,0 +1,54 @@ +# Outbound connection through ports + +Source: https://docs.rubrik.com/en-us/saas/saas/common/outbound_connection_through_ports.html + +--- + +# Outbound connection through ports + +RSC requires you to open an outbound connection through port 443 for a Rubrik cluster to access specific sites. + +A Rubrik cluster requires an outbound connection through port 443 to access specific sites. It is mandatory to ensure that your network firewalls and security devices permit these connections for each node in a Rubrik cluster. You can use a proxy server for communication if required. + +The following table lists the endpoints that a Rubrik cluster accesses through TCP port 443. Use case | Endpoints +---|--- +Connection between RSC and Rubrik clusters running Rubrik CDM version 8.1.1 or later | https://.my.rubrik.com, where is your Rubrik account name, which resolves to a static IP address.Rubrik recommends that you upgrade your Rubrik cluster to CDM version 8.1.1 or later so it can connect to RSC using a single endpoint. +Connection between RSC and Rubrik clusters running Rubrik CDM version earlier than 8.1.1 | + + * https://.my.rubrik.com + * https://accounts.google.com + * https://storage.googleapis.com + * https://www.googleapis.com + * https://oauth2.googleapis.com + + + + * Connection between your web browser and the RSC domain + * Downloading RSC reports + +| + + * https://.my.rubrik.com, where is your Rubrik account name + * https://cdn-rsc.rubrik.com + +These host names resolve to static IP addresses, if needed, for network configurations. The https://.my.rubrik.com endpoint is also required for downloading RSC reports. +Rubrik support tunnel, cluster statistics, and error log uploads | https://proxy.rubrik.com +Support bundle uploads | + + * https://apollo-ingest.s3.amazonaws.com + * https://rubrikstats.s3.amazonaws.com + + +Support bundle uploads (if IPv6 dual-stack is required) | + + * https://apollo-ingest.s3.dualstack.us-east-1.amazonaws.com + * https://rubrikstats.s3.dualstack.us-east-1.amazonaws.com + + +Rubrik CDM software package for upgrades using Rubrik CLI | + + * https://rubrik-support-download.s3.amazonaws.com + * https://rubrik.force.com + +If you download CDM software packages using RSC, you do not require access to these endpoints. +Rubrik Cloud Vault (RCV) | You can find the endpoints that you need to allowlist by clicking the Allowlist RCV locations option on the Rubrik Cloud Vaults page. You can access this page by clicking View All Rubrik Cloud Vaults on the Rubrik Cloud Vault dashboard. diff --git a/saas_common_password_constraints.md b/saas_common_password_constraints.md new file mode 100644 index 0000000000000000000000000000000000000000..ddab3881994456a330536e3b49185d2f8e22e916 --- /dev/null +++ b/saas_common_password_constraints.md @@ -0,0 +1,17 @@ +# RSC password constraints + +Source: https://docs.rubrik.com/en-us/saas/saas/common/password_constraints.html + +--- + +# RSC password constraints + +RSC passwords must comply with the password constraints. + +RSC requires that the password have at least eight characters, with at least three of the following character types: + + * Lower case letters + * Upper case letters + * Integers + * ASCII special characters + diff --git a/saas_common_qauth_roles_report.md b/saas_common_qauth_roles_report.md new file mode 100644 index 0000000000000000000000000000000000000000..3a0d72b317960e0696fa32e38de30c886b0ca85b --- /dev/null +++ b/saas_common_qauth_roles_report.md @@ -0,0 +1,25 @@ +# Quorum Authorization Roles report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/qauth_roles_report.html + +--- + +# Quorum Authorization Roles report + +The Quorum Authorization Roles report displays a list of users who can approve specific policies associated with a Quorum Authorization request. Using this report, you can easily find the users with the QAuth reviewer role and the policies they can approve. + +For performing data-modifying actions such as data management, system configuration, or global configurations within Rubrik, you need approvals based on the Quorum Authorization (QAuth) security feature. The data-modifying actions are protected by a QAuth policy. When you perform a data modifying action, RSCgenerates an authorization request requiring approval from a user with the QAuth reviewer role. + +The Quorum Authorization Roles report lists users who can approve specific QAuth policies associated with Quorum Authorization requests. You can use this report to identify users with the QAuth reviewer role and the policies they can approve. + +You can use the Quorum Authorization Roles report for: + + * Selecting columns to include in the report + * Editing the name of the report and saving the report for future reference + * Downloading the report either as a PDF or in the CSV format + * Emailing the report to the required email addresses + * Searching a user with the QAuth reviewer role with the details of the policies they can approve + * Managing a report schedule + * Deleting a report + + *[ > ]: and then diff --git a/saas_common_rbac_practical_scenarios_role_config.md b/saas_common_rbac_practical_scenarios_role_config.md new file mode 100644 index 0000000000000000000000000000000000000000..b7680ddaeb0cf0cef8caa87da8b536cfc076bdc3 --- /dev/null +++ b/saas_common_rbac_practical_scenarios_role_config.md @@ -0,0 +1,59 @@ +# Practical scenarios for role configuration + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rbac_practical_scenarios_role_config.html + +--- + +# Practical scenarios for role configuration + +Information about the scenarios that map common administrative tasks to their minimum required privileges, offering a blueprint to help create custom roles based on the Principle of Least Privilege (PoLP). + +## VMware vSphere workloads + +The following table describes the privileges required for common administrative tasks related to VMware vSphere workloads. + +Task | Required privileges | Use case +---|---|--- +Exclude a virtual machine disk | + + * View Inventory + * Manage Protection + +| An administrator or automation script programmatically excludes an unused disk from a virtual machine backup to conserve storage. The operation requires the View Inventory privilege to view the virtual machine and the Manage Protection privilege to modify its protection settings. +Configure pre/post-thaw scripts | Manage Protection | An administrator adds scripts to a virtual machine protection policy to ensure application quiescence and consistency during snapshot operations. Manage Protection is the core privilege for modifying these advanced policy settings. +Configure application-consistent snapshots | Manage Protection | You can enable the application-consistent snapshot feature in the virtual machine protection settings to ensure that backups are application-consistent and requires the Manage Protection privilege. Functional VMware Tools must also be present on the guest operating system. + +## Database workloads for SQL Server + +The following table describes the privileges required for common administrative tasks related to SQL Server database workloads. + +Task | Required privileges | Use case +---|---|--- +Restore a SQL Server Database to a different location | + + * View Inventory + * Export Files + +| A Database Administrator (DBA) restores a database to an alternate server for testing or development purposes. This requires the View Inventory privilege to view the source database and the Export Files privilege to perform an out-of-place restore. +Live mount a database for testing | + + * View Inventory + * Mount snapshot + * View clusters + +| A developer requires instant, read-write access to a database backup for testing. Mount snapshot is the specific privilege for this action, and View clusters is also required to select a valid Rubrik cluster to host the mounted copy. + +## General system and data management + +The following table describes the privileges required for general system and data management tasks. + +Task | Required privileges | Use case +---|---|--- +Take an on-demand snapshot | + + * View Inventory + * Take On-demand Snapshot + +| A user initiates an immediate backup of an object, such as a file set or a virtual machine, prior to a significant change. This requires permission to view the object and take an on-demand snapshot. +Add a new Azure subscription | Manage cloud account configuration | An administrator onboards a new Azure subscription to protect its resources. This requires the global Manage cloud account configuration privilege in addition to appropriate permissions for the service principal in the Azure tenant. + *[ > ]: and then diff --git a/saas_common_rbac_roles_dba.md b/saas_common_rbac_roles_dba.md new file mode 100644 index 0000000000000000000000000000000000000000..5b435f6872b0b036d4926fef82c686ec0fa93a4f --- /dev/null +++ b/saas_common_rbac_roles_dba.md @@ -0,0 +1,16 @@ +# Role-based access control roles for database administrators + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rbac_roles_dba.html + +--- + +# Role-based access control roles for database administrators + +Role-based access control roles for database administrators allow you to specify with granularity which objects database administrators have access to and what permissions they have to perform actions on these objects. + +You can use RSC to grant role-based access control (RBAC) roles to database administrators (DBAs) to determine which objects on RSC they do and do not have access to and the actions they can perform on these objects. + +The Create Role wizard in the RSC Roles page provides you the ability to specify the granularity of permissions each DBA has for objects in a workload, ranging from full access to all workload resources to permissions that are restricted at the object level. + +When you assign RBAC roles to DBAs in a replicated environment, it might be advantageous to select a specific host or cluster, group, or database as the source object to which the DBAs have access. You can then select the appropriate targets to which you are recovering. This configuration is helpful for developers who need to refresh their development environment. By selecting specific targets for export or live mount, the DBA can manage specific hosts, clusters, or databases. + *[ > ]: and then diff --git a/saas_common_remove_rubrik_cluster.md b/saas_common_remove_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..d346109158e2156258a211792eea2841f1f92112 --- /dev/null +++ b/saas_common_remove_rubrik_cluster.md @@ -0,0 +1,21 @@ +# Remove a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/remove_rubrik_cluster.html + +--- + +# Remove a Rubrik cluster + +You can remove a Rubrik cluster from RSC when it is no longer needed. + +There are several scenarios in which a Rubrik cluster should be removed from RSC. For example, when an older Rubrik cluster has been decommissioned or when a Rubrik cluster used for testing is no longer needed. + +Before removing a Rubrik cluster, verify that: + + * The Rubrik cluster has no objects protected by SLA Domains. + * The Rubrik cluster is not a replication target for any SLA Domain. + * The Rubrik cluster is not used by any RCV locations. + * The Rubrik cluster is connected to RSC and is running Rubrik CDM version 5.3 or newer, or it is disconnected from RSC. + +If you've enabled quorum authorization, you must create a quorum authorization policy before you can initiate the removal of a Rubrik cluster. After you initiate the removal, a quorum authorization request is automatically submitted. The cluster removal proceeds only after the required approvals are granted. [Quorum authorization](../../reuse/conrefs/../../qauth/quorum_authorization.html "Quorum authorization is a security feature that enforces the requirement of getting additional approvals before a requester can perform data-modifying actions in RSC.") provides more information about quorum authorization. + *[ > ]: and then diff --git a/saas_common_removing_disk_rbk_or_supp_tp_cluster.md b/saas_common_removing_disk_rbk_or_supp_tp_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..bb6a3f24ec4382ec663690758894a3d41864ed55 --- /dev/null +++ b/saas_common_removing_disk_rbk_or_supp_tp_cluster.md @@ -0,0 +1,47 @@ +# Removing a disk from Rubrik or supported third-party clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/removing_disk_rbk_or_supp_tp_cluster.html + +--- + +# Removing a disk from Rubrik or supported third-party clusters + +After you have identified a disk that needs replacement or an upgrade for more space or other reasons, remove the disk from a Rubrik or a supported third-party cluster. + +## Before you begin + +Before removing a disk from a Rubrik or a supported third-party cluster, identify the disk that is in a failed or missing state and requires removal. You can use the Rubrik CDM web UI or the administrator CLI command support find_bad_disk to identify such disks. + +The Identifying the disk to replace section in the Rubrik CDM Hardware Guide provides more information about identifying a disk that requires removal using the CDM web UI. The Support management section in the Rubrik CDM CLI Guide provides more information about how to use the CLI command to locate a failed or missing disk. + +## About this task + +You can remove disks for either replacing them or upgrading them to a format with more space, or for other reasons. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click the name of the cluster containing the failed or missing disk you want to remove. + +The cluster details page appears. + + 5. Click Nodes. + +The Nodes details page appears. + + 6. In Node Name, click the name of the node requiring a disk replacement. + +The details page for this node appears. + +Disks that require replacement have an exclamation mark in the Status column of the HDD Disks table. + +Additionally, under the LED column, RSC illuminates the red LED light for a failed disk. For a missing disk, the red LED light is not lit. + + 7. Click Remove. + +## Results + +RSC removes the disks from the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_report_customization.md b/saas_common_report_customization.md new file mode 100644 index 0000000000000000000000000000000000000000..8e6665abdfdb8d9153df027963a6edcfa1471165 --- /dev/null +++ b/saas_common_report_customization.md @@ -0,0 +1,20 @@ +# Report customization + +Source: https://docs.rubrik.com/en-us/saas/saas/common/report_customization.html + +--- + +# Report customization + +Customize the reports by selecting the data to include. + +Use report templates as the starting point and modify them to create new reports with the available customizations. + +Use the following report customization actions: + + * Use groupings to view aggregated data. + * Apply filters to restrict data that appears in a report. + * Convert charts and tables into time-based or PIT-based format. + +All users of the account can see the customizations made to the reports. + *[ > ]: and then diff --git a/saas_common_report_filters.md b/saas_common_report_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..af55fbc6a7f5d75b5f54397ffdc9cc00b772b15e --- /dev/null +++ b/saas_common_report_filters.md @@ -0,0 +1,171 @@ +# Report filters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/report_filters.html + +--- + +# Report filters + +You can use report filters to select the relevant data for each RSC report. Report filters apply to the entire report, including all tables and charts. + +For all RSC reports, you can utilize the available filters to sort and analyze the relevant data effectively. You can access these filters from the Filters sidebar. The filters allow you to customize your data view based on various criteria. Only filters applicable to the chart type are available for use. + +Filter | Description +---|--- +Time | The time range for the report.Supported ranges are: + + * Past 24 Hours + * Past 7 Days + * Past 30 Days + * Past 12 Months + * Custom Range + + +Compliance range | The time range for the report.Supported ranges are: + + * Past 24 Hours + * Past 7 Days + * Past 30 Days + * Past 90 Days + * Past 365 Days + * Start of protection + +This filter applies only to the Compliance report. +Clusters | The Rubrik clusters connected to RSC. You can select multiple clusters. +Object Name | The name of the object associated with the connected Rubrik cluster in RSC. Hovering over an object name in the Object Name filter displays the Type, Location, and Cluster for that object. You can select multiple object names. +Object Type | The object type associated with the connected Rubrik cluster on RSC. You can select multiple object types. +Location | The IP address or the Fully Qualified Domain Name (FQDN) for an object. You can select multiple locations. The Location filter displays data synced to RSC. Hovering over an object in the Location filter displays the Name, Type, and Cluster for that object. Location information is not available for historical data collected before April 1, 2024, for Object Capacity Over Time reports. +Object Status | The status of the object type to include in the report. You can select multiple object types.Supported values are: + + * Protected + * Unprotected + * Replicated Relic + * Relic + +This filter applies only to the Object Audit report. +Cluster type | The Rubrik cluster types to include in the report.You can select multiple object types.Supported values are: + + * Cloud + * Appliance + * Virtual + * Rubrik Security Cloud + +This filter does not apply to the SLA Audit, Object Audit, and Data Threat Analytics reports.The value Rubrik Security Cloud is also available only for the Infrastructure, Object capacity, Compliance, Protection, and Event reports. +Cluster location | The Rubrik cluster location to include in the report. A Rubrik cluster is either local or remote. This filter applies only to the Protection Tasks Details and Recovery Tasks Details reports. +SLA Domain | The SLA Domains to include in the report.This filter does not apply to the Infrastructure and the Data Threat Analytics reports. +Replication source | The Rubrik cluster that manages the protected objects that are the source of the replicated data.This filter applies only to the Protection Tasks Details report. +Event type | The event to include in the report.This filter applies only to the Event report.The Anomaly filter is only viewable when you have a valid license for Data Threat Analytics.You can select multiple event types. +Status | The status to include in the report: + + * Completed + * Running + * Failure + * Canceled + * Queued + +This filter applies only to the Event report.You can select multiple statuses. +Task status | The specific task status to include in the report: + + * Success + * Canceled + * Failed + +This filter applies only to the Protection Tasks Details and Recovery Tasks Details reports.You can select multiple task statuses. +Task type | The task type to include in the report. This filter applies only to the Protection Tasks Details and Recovery Tasks Details reports.Task types for the following events are available in the Protection Tasks details report: + + * Archival + * Archival Tiering + * Backup + * Conversion + * Index + * Log Archival + * Log Backup + * Log Replication + * Log Shipping + * Replication + +The following task types are available for the Recovery Tasks details report: + + * Export + * File Download + * File Restore + * In-Place Recovery + * Instant Recovery + * Live Mount + * Restore + * Validation + + +Policies | The Data Security Posture policy to include in the report.This filter applies only to the Data Security Posture Object details report. +User Action | The specific user action to include in the report. + + * Create + * Delete + * Update + +You can select multiple User Actions.This filter applies only to the SLA Audit report. +Protection Status | The protection status of the objects in the report.Supported values are: + + * Protected + * Don't Protect + * No SLA + +This filter applies only to the Protection report. +Compliance Status | The compliance status of the objects in the report.Supported values are: + + * In compliance + * Out of compliance + * No SLA + +This filter applies only to the Compliance report. +Indexing | The indexing status for objects in the report.Supported values are: + + * Object Name + * Object Type + * Location + * SLA Domain + * Latest Snapshot Time + * Latest Snapshot Index Status + * Latest Successful indexed Snapshot Time + * Count of Total Snapshots + * Count of Total Indexed Snapshots + +This filter applies only to the Indexing report. +Domain Type | Indicates the type of authentication system used for authorization while logging in to RSC. Supported values are: + + * SSO: Lists the user accounts that use Single Sign-on (SSO) as an authentication method while logging in to RSC, where a user can access multiple applications or services with a single set of login credentials. + * Local: Lists the user accounts that use credentials as an authentication method, where the user accounts use a standalone system where user credentials are stored and managed locally on the device or within the local network. + * LDAP: Lists the user account that use LDAP as an authentication method while logging in to RSC, where user information, credentials, and access rights are managed through an LDAP directory. LDAP is a protocol used to access and manage directory information over IP network. + +This filter applies only to Users report. +Roles | Indicates a defined set of permissions and access rights that can be assigned to users. Roles provide information about the explicit authorization of a user to perform actions on resources specified in the assigned roles. A role can be assigned to more than one user account, and a user account can have more than one role assigned to it. This filter applies only to Users, SSO Groups, Service Account, and Roles report. +SSO Group | A list of groups of users who are managed within a SSO system for easy administration of access controls and permissions.This filter applies only to Users report. +Organizations | A global organization responsible for creating and managing tenant organizations. A tenant organization is a group of resources, workloads, SLA Domains, and permissions defined by the Global organization. Tenant organizations are defined subsets of a global organization. Each tenant organization has an administrator that can define additional roles that are subsets of the tenant organization administrator role. This filter applies only to Users and SSO Groups report. +MFA Status | Indicates whether the multi-factor authentication is enabled for a user account.This filter applies only to Users report. +MFA | Indicates the type of multi-factor authentication enabled for a user account where you are required to enter a single-use numeric code in addition to your login credentials to login to RSC for enhanced security.Supported values are: + + * All: Lists all the user accounts where multi-factor authentication is either enabled with TOTP, TOTP and passkeys, only passkeys, or the multi-factor authentication is not enabled. + * TOTP: Lists the user accounts where multi-factor authentication is enabled with TOTP where Rubrik multi-factor authentication feature uses time-based one-time passwords in addition to the user login credentials to enforce multi-factor authentication on user accounts. + * Passkey: Lists the user accounts where multi-factor authentication is enabled with passkey. + * TOTP and Passkey: Lists the user accounts where multi-factor authentication is enabled with TOTP and passkey. + * None: Lists the user accounts where multi-factor authentication is not enabled. + + +Lockout Status | Indicates the lockout status of a user account.Supported values are: + + * All: Lists all the user accounts that are locked and unlocked. + * Locked: Lists the user accounts that are temporarily locked due to multiple failed login attempts. + * Not Locked: Lists the user accounts that are active and not locked. + +This filter applies only to Users report. +User Activity | Indicates whether the user has logged in or not logged in to RSC. Supported values are: + + * All: Lists all the user accounts that have logged in or not logged in to RSC. + * Invited: Lists all the user accounts that have received an invitation from the administrator to log in to RSC, however, they have not logged in. + * Active: Lists all the user accounts that have logged in to RSC. + +This filter applies only to Users report. +Last Login | The most recent instance when a user successfully authenticated and logged into RSC. This filter applies only to Users report. +Last Locked | Indicates the most recent instance when a user account was locked. This information is tracked to detect unusual login patterns or potential security threats. This filter applies only to Users report. +Last Unlocked | The latest instance when a user account was locked due to security measures such as multiple failed login attempts. This filter applies only to Users report. + *[ > ]: and then diff --git a/saas_common_report_schedules.md b/saas_common_report_schedules.md new file mode 100644 index 0000000000000000000000000000000000000000..31edc05339d584471bf36a545b6d6272833efec3 --- /dev/null +++ b/saas_common_report_schedules.md @@ -0,0 +1,23 @@ +# Report schedules + +Source: https://docs.rubrik.com/en-us/saas/saas/common/report_schedules.html + +--- + +# Report schedules + +Report schedules automatically deliver RSC reporting data, reducing the amount of time spent on generating accurate and timely reports. + +Report schedules provide a customized method to deliver RSC reporting data at a scheduled date and time. RSC delivers report schedules as an email in HTML format. Any email address registered in RSC is eligible to receive a report schedule. + +Each report schedule contains the following: + + * A PDF document with details about the report + * A CSV file with the contents of the report + +RSC automatically compresses report files with attachments larger than 10 MB as a ZIP file. + +To configure a report schedule, an RSC user requires a role with the permissions to configure and modify report schedules. When an RSC user with that role configures an email for a report schedule, RSC applies the user permissions assigned to the user at the time the report schedule was created. This ensures that a report schedule is delivered regardless of whether a user role changes over time. + +Report schedules use different timezones based on when the report schedule is created and delivered. When RSC creates report schedules, it uses the local timezone. The events captured in the report email are displayed in the UTC timezone. + *[ > ]: and then diff --git a/saas_common_reporting.md b/saas_common_reporting.md new file mode 100644 index 0000000000000000000000000000000000000000..550863693fc637feaead4bf31ff433e6dbee105b --- /dev/null +++ b/saas_common_reporting.md @@ -0,0 +1,23 @@ +# Reporting + +Source: https://docs.rubrik.com/en-us/saas/saas/common/reporting.html + +--- + +# Reporting + +You can use the Reporting feature to perform audits and data management planning by creating customizable reports for application data protection and for the underlying infrastructure of Rubrik Security Cloud. + +Reports in Rubrik Security Cloud (RSC) are organized into categories based on use cases, which help users easily find the report templates most relevant to their needs. This approach streamlines report discovery, creation, and overall user experience by providing intuitive guidance within the user interface. + +You can use the reporting feature to create customizable reports using various filters and to create a view of the most commonly used system metrics. Reports containing data for Rubrik clusters can be used for performing audits and data management planning. + +The following report categories are available in the RSC UI to help guide your selection: + + * Audit & Compliance: Includes reports for auditing system activities and verifying compliance with assigned SLA Domains. + * Capacity Management: Offers reports that help monitor storage capacity usage for effective resource planning. + * Health & Performance: Provides reports related to the overall health and performance of your Rubrik clusters and protected objects. + * Users & Org Management: Contains reports that provide insights into user activities, roles, and SSO groups for auditing and daily operations. + * Others: Contains reports that do not fall into the other report categories, such as Indexing reports. + +In addition to viewing reports, you can perform various actions on them, including creating, editing, sending, downloading, and saving them. The customization options allow you to modify filters, groupings, and other settings to create a personalized view of the data. You can also create and manage report schedules to automatically deliver reports at specific intervals to specified email addresses. diff --git a/saas_common_reports_page_nav.md b/saas_common_reports_page_nav.md new file mode 100644 index 0000000000000000000000000000000000000000..d6522a196646566d417cede8d6b3b2ebf0d07636 --- /dev/null +++ b/saas_common_reports_page_nav.md @@ -0,0 +1,20 @@ +# Reports page navigation + +Source: https://docs.rubrik.com/en-us/saas/saas/common/reports_page_nav.html + +--- + +# Reports page navigation + +You can use the navigation panel on the Reports page to find reports by category, search, or pinned status. + +The Reports page in RSC includes a panel for easy navigation. This panel organizes reports into categories of templates based on use cases. It helps users find the right report templates, and makes it easier to create and find reports. + +The following table explains how to find a report on the Reports page: Method | Description +---|--- +Pinned Reports | Lets you quickly access reports you have pinned for frequent use. +Search | Allows you to search for a specific report by name. +All Reports | Shows a complete list of all available reports in one view. +By Category | Groups reports by their use case, like Audit and Compliance or Health & Performance, to help you find relevant reports. Within each category, you can also filter on templates to narrow your search. +View My Reports Only | Lets you quickly access the reports you created. + *[ > ]: and then diff --git a/saas_common_revoking_support_access.md b/saas_common_revoking_support_access.md new file mode 100644 index 0000000000000000000000000000000000000000..cc4c3041699dc2e6e477b8ce8210f34e25a5679d --- /dev/null +++ b/saas_common_revoking_support_access.md @@ -0,0 +1,33 @@ +# Revoking support access + +Source: https://docs.rubrik.com/en-us/saas/saas/common/revoking_support_access.html + +--- + +# Revoking support access + +An RSC user account with owner or administrator privileges can revoke an existing support access grant. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Settings. + +A new tab displaying the settings menu opens on your browser. + + 3. Click Customer Support and select Support Access. + +The Support Access page appears. + + 4. Open the ellipsis menu for a support access instance and select Revoke Access. + +You can only revoke access for a support access instance that is in open state. + +A confirmation message appears. + + 5. Click Revoke. + +## Results + +RSC revokes the selected support access instance and all the support sessions for this support access instance are logged out automatically. + *[ > ]: and then diff --git a/saas_common_roles_and_permissions.md b/saas_common_roles_and_permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..454a5c4e5ee9b9727581d732e01114837b0c83f1 --- /dev/null +++ b/saas_common_roles_and_permissions.md @@ -0,0 +1,33 @@ +# User roles and permissions + +Source: https://docs.rubrik.com/en-us/saas/saas/common/roles_and_permissions.html + +--- + +# User roles and permissions + +Roles are sets of permissions that are assigned to a user account. You can assign multiple roles to a user account. + +Table 1. Correlation between roles and permissions Filter | Description +---|--- +Role | + + * A role is a set of permissions. + * A role can have multiple sets of permissions. + * Users can have more than one role assigned to them. + + +Permission | + + * A permission is the ability to perform a certain operation or task. + * A permission can be assigned to many roles. + * A permission can be assigned to many operations or tasks. + * An operation or task can be assigned to many objects or targets. + + + +RSC provides predefined roles as well as templates to create additional roles in the UI. Owner and Administrator roles are the predefined roles available in RSC. You can create additional roles from RSC user role templates or as custom roles. + +RSC provides a default Owner role that has full access rights to all operations and tasks. RSC creates this role for all existing and new accounts. You can assign this role only to a local user. Authorized users can assign the default role to other users in the system. However, you cannot edit or delete the default role. The owner role retains full access to RSC even when the SSO provider is unavailable. + +To provide easier and customized role creation, RSC supports role templates that contain a pre-selected set of permissions associated with the specific role being created. Role templates are a default selection that you can modify freely when creating a role. diff --git a/saas_common_roles_report.md b/saas_common_roles_report.md new file mode 100644 index 0000000000000000000000000000000000000000..466de2a39c12439c5103de51b0c7f1414f4836aa --- /dev/null +++ b/saas_common_roles_report.md @@ -0,0 +1,31 @@ +# Roles report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/roles_report.html + +--- + +# Roles report + +For daily operations and auditing purposes, you can view the Roles report in RSC, which displays the roles created by the administrator and their descriptions. + +You can view the Roles report that displays the roles created by the administrators and their descriptions. Roles indicate a defined set of permissions and access rights that an administrator can assign to users. A user can then perform actions on resources specified in the assigned roles. + +An administrator can assign a role to more than one user account and a user account can have more than one role assigned to it. This report is crucial for effective access management, security monitoring, and compliance auditing. + +Key aspects of Roles report are: + + * Access management: Ensuring that users have appropriate permissions and access rights based on their assigned roles. + * Security monitoring: Identifying potential security risks associated with role assignments. + * Compliance: Auditing for adherence to internal policies and regulatory requirements. + * Operational efficiency: Streamlining the management and review of access rights by providing a clear overview of roles and associated permissions. + +With RSC, you can: + + * Choose which columns to include in the report + * Edit and save the report name for future use + * Download the report in PDF or CSV format + * Email the report to specified addresses + * Set up and manage a report schedule + * Delete the report + + *[ > ]: and then diff --git a/saas_common_rsc_report_sox_compliance.md b/saas_common_rsc_report_sox_compliance.md new file mode 100644 index 0000000000000000000000000000000000000000..2a139ef6f1d96188f0062f87af104c518baa4833 --- /dev/null +++ b/saas_common_rsc_report_sox_compliance.md @@ -0,0 +1,21 @@ +# SOX compliance for audit reports + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_report_sox_compliance.html + +--- + +# SOX compliance for audit reports + +To meet SOX compliance requirements RSC provides audit reports that contain granular historical details of SLA Domains and workload objects managed by Rubrik clusters. + +Sarbanes-Oxley (SOX) compliance mandates a public company to provide proof of accurate and data-secured reporting. + +RSC creates the SLA Audit report after you create an SLA Domain. After you assign an SLA Domain to a workload object, RSC adds an entry for the related details in the Object Audit report. These reports are available for Rubrik clusters running Rubrik CDM version 7.0.2 or later. + +The following table describes the SLA Audit and Object Audit reports in detail. + +Report Name | Description +---|--- +SLA Audit Report | Displays the historical data for SLA Domains.You can view information for SLA Domains that were modified in a specific time period. The most recent version of the SLA Domain is shown in the SLA audit report table.A new version of an SLA Domain is created each time the SLA Domain is modified. You can click on the SLA Domain name to view the list of all versions. +Object Audit Report | Displays the SLA Domain assigned to each workload managed through a Rubrik cluster.You can expand the row for an object to view historical information about the SLA Domain assignments.This report also contains information about the different versions of an SLA Domain that was assigned to an object.For example, you updated the current version of the SLA Domain. RSC will add an entry in the report stating that a new version is protecting the object. + *[ > ]: and then diff --git a/saas_common_rsc_rmfa_totp.md b/saas_common_rsc_rmfa_totp.md new file mode 100644 index 0000000000000000000000000000000000000000..aabdb2df3282c7ddb2c98aceaf8132d805f4623a --- /dev/null +++ b/saas_common_rsc_rmfa_totp.md @@ -0,0 +1,17 @@ +# Rubrik MFA with TOTP + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_rmfa_totp.html + +--- + +# Rubrik MFA with TOTP + +The Rubrik two-step verification feature uses time-based one-time passwords in addition to the user login credentials to enforce multi-factor authentication on user accounts. + +Rubrik two-step verification is an implementation of 2FA for Rubrik Security Cloud (RSC). You can enable Rubrik two-step verification to use 2FA mediated by time-based one-time password (TOTP), which provides an additional layer of authentication security. By using TOTP, Rubrik enforces multi-factor authentication (MFA) with the help of a single-use numeric code in addition to your login credentials. You can use an application running on your personal device, for example a smart phone, to generate the single-use numeric code. Rubrik two-step verification works with any TOTP application that complies with RFC 6238. + +MFA enforcement is mandatory for all local RSC user accounts. Administrators must enforce Rubrik two-step verification for users at the global level. When enforced, each user must configure Rubrik two-step verification on an individual basis. + +Note: + +MFA enforcement does not impact user accounts authenticated through SAML-based SSO authentication providers. diff --git a/saas_common_rsc_roles.md b/saas_common_rsc_roles.md new file mode 100644 index 0000000000000000000000000000000000000000..515252f90c1a312ca16f7a81254766c58f74950a --- /dev/null +++ b/saas_common_rsc_roles.md @@ -0,0 +1,37 @@ +# Roles + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_roles.html + +--- + +# Roles + +Roles help define privileges for user accounts on a Rubrik cluster. With the admin account, you can assign administrator roles that grant different access permissions to user accounts for specific purposes. + +A role is a collection of workload objects, SLA Domains, and privileges that you can assign to user accounts. You can assign a role to more than one user account, and a user account can have more than one role assigned to it. + +RSC provides role templates that have a predefined set of permissions required to perform a specific function. While creating a role, you can start with a role template or select the Custom role template to customize permissions or combinations of permissions. + +For Rubrik CDM version 9.3.0 and later, you can sync RSC roles that belong to the global organization with CDM while creating or editing the roles. When you enable cluster role sync for a role in RSC, the system creates the same roles in CDM for the selected clusters. The synced roles on the cluster have assigned permissions based on federated login permission translations. When you delete a role in RSC that is synced to a Rubrik cluster, CDM also deletes it for the corresponding cluster. CDM displays the synced roles in the following format: (From RSC) RSC role name. + +The Administrator and Owner role templates are static and cannot be edited. All other role templates, however, are custom, and you can customize any of the other roles according to your requirements. + +The following table lists the static role templates in RSC. + +Role | Description +---|--- +Administrator | Gives full permissions for all actions on RSC. +Owner | Gives permission to add other Owner user accounts. This role is created during initial user account configuration and is the default user account to receive event notifications. + +The following table lists the custom RSC role templates. + +Role | Description +---|--- +Auditor | Gives permission to view all aspects of the Rubrik RSC domain, workload, and SLA Domain configuration for the purpose of validating configuration or operations as part of auditing. +AWS Cloud Account Owner | Enables management of all aspects of AWS cloud accounts. These are the credentials used to integrate with workloads, storage, or archive locations that reside in the AWS Cloud. +Azure Cloud Account Owner | Enables management of all aspects of Azure cloud accounts. These are the credentials used to integrate with workloads, storage, or archive locations that reside in Azure Cloud. +Backup Administrator | Enables management of every aspect of backup and recovery operations on RSC for all supported workloads. +Compliance Auditor | Provides a role for auditors interested in the results of data security posture and classification for the purpose of auditing compliance. A user account with this role has global visibility into the output of the Rubrik Data Security Posture product tool set. +Compliance Officer | Provides a role for auditors interested in managing data security posture and classification. A user account with this role has global visibility and configures the output of the Rubrik Data Security Posture product tool set. +GCP Cloud Account Owner | Enables management of all aspects of Google (GCP) cloud accounts. These are the credentials used to integrate with workloads, storage, or archive locations that reside in Google Cloud. + *[ > ]: and then diff --git a/saas_common_rsc_service_account_report.md b/saas_common_rsc_service_account_report.md new file mode 100644 index 0000000000000000000000000000000000000000..eb03fd622b147f08248fb590b3b67245775c04af --- /dev/null +++ b/saas_common_rsc_service_account_report.md @@ -0,0 +1,31 @@ +# Service Account report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_service_account_report.html + +--- + +# Service Account report + +For daily operations and auditing purposes, you can view the Service Account report in RSC, which displays service accounts and their roles. + +You can view the Service Account report that displays service accounts and their roles. The Service Account report provides insights on service accounts within an organization and the roles assigned to them. Service accounts are non-interactive accounts and requires careful monitoring and management to ensure they do not become security liabilities. You can use this report for auditing purposes. + +This report helps the stakeholders to understand and manage the activities, statuses, and security of service accounts within an organization. With the compiled service account data, you can ensure that the service accounts are used securely and do not pose undue security risk to the organization. + +Key aspects of Service Account report are: + + * Security monitoring: Identifying and monitoring potential security risks associated with service accounts, such as unauthorized usage or credential misuse. + * Compliance auditing: Ensuring that service accounts comply with policies and regulatory requirements by providing an audit trail and detailed analysis. + * Resource management: Optimizing the allocation and usage of service accounts, ensuring they have the appropriate level of access and are being used as intended. + * Risk mitigation: Identifying inactive service accounts and reduce the potential security issues by disabling unnecessary accounts. + +RSCallows you to: + + * Choose which columns to include in the report + * Edit and save the report name for future use + * Download the report in PDF or CSV format + * Email the report to specified addresses + * Set up and manage a report schedule + * Delete the report + + *[ > ]: and then diff --git a/saas_common_rsc_sso_group_report.md b/saas_common_rsc_sso_group_report.md new file mode 100644 index 0000000000000000000000000000000000000000..bfbf7ac26bf024b56e1c1cfaf05e7e5135ddbb88 --- /dev/null +++ b/saas_common_rsc_sso_group_report.md @@ -0,0 +1,31 @@ +# SSO Groups report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_sso_group_report.html + +--- + +# SSO Groups report + +For daily operations and auditing purposes, you can view the SSO Groups report in RSC, which displays SSO groups and their roles. + +You can view the SSO Groups report that displays Single Sign-on (SSO) groups and their roles. The SSO Groups report provides information about groups within a SSO system and the roles assigned to the SSO groups. Any user who is part of the SSO group inherits the permissions associated with the roles of that group. + +You can use this report for daily operations and auditing purposes. + +Key aspects of SSO Groups report are: + + * Access management: Ensuring users have appropriate access levels by helping administrators manage and review SSO group and role details. + * Security monitoring: Identifying potential security risks associated with group memberships and activities, such as unauthorized access or privilege escalation. + * Compliance: Ensuring groups and their memberships comply with organizational policies and regulatory requirements by providing detailed audit trails. + * Efficiency: Streamlining the administration of user access by providing a clear overview of group structures and usage for efficient user and permission management. + +RSCallows you to: + + * Choose which columns to include in the report + * Edit and save the report name for future use + * Download the report in PDF or CSV format + * Email the report to specified addresses + * Set up and manage a report schedule + * Delete the report + + *[ > ]: and then diff --git a/saas_common_rsc_users_reports.md b/saas_common_rsc_users_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..825890ec437541e53b8a2d2200f6a7849a0fef30 --- /dev/null +++ b/saas_common_rsc_users_reports.md @@ -0,0 +1,28 @@ +# Users reports + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rsc_users_reports.html + +--- + +# Users reports + +For daily operations and auditing purposes, you can view the Users report in RSC, which displays users and their roles. + +The Users report provides insights into the activities, status, and attributes of a user within RSC. You can use this report for security monitoring, user management, daily operations, and auditing purposes. With the Users report, the administrators and stakeholders get a clear understanding of user behaviors, access patterns, account statuses, and potential security issues. This comprehensive view also helps in making informed decisions regarding user management and actions to mitigate potential security violations. + +Key aspects of the Users report are: + + * Security monitoring: Identifying unusual and suspicious activities, potential security violations, and unauthorized access attempts. + * User Management: Assisting administrators in managing user accounts, such as identifying inactive accounts. + * Auditing: Providing necessary documentation for regulatory and compliance audits. + +RSCallows you to: + + * Choose which columns to include in the report + * Edit and save the report name for future use + * Download the report in PDF or CSV format + * Email the report to specified addresses + * Set up and manage a report schedule + * Delete the report + + *[ > ]: and then diff --git a/saas_common_rubrik_clusters.md b/saas_common_rubrik_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..80f228e55bcb81d02f5762524602d5bb0a348a7f --- /dev/null +++ b/saas_common_rubrik_clusters.md @@ -0,0 +1,19 @@ +# Rubrik clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rubrik_clusters.html + +--- + +# Rubrik clusters + +A Rubrik cluster is an instance of Rubrik CDM running on any virtual or physical platform. You can add the Rubrik cluster to RSC to enable extended features for the cluster. + +A Rubrik cluster is an instance of Rubrik CDM running on any virtual or physical platform, and is a distributed, scale-out system that serves as the foundation for the Rubrik data security and management platform. The Rubrik platform protects and manages data across various environments, including on-premises data centers, private clouds, and public clouds. + +A Rubrik cluster is made up of multiple nodes that work together to provide a unified platform for backup, recovery, archival, and more. + +You can add Rubrik clusters toRSC to monitor backup events, ensure compliance, and view the protection status for those Rubrik clusters. + +Rubrik clusters use a single-token from RSC to authenticate and secure an ongoing connection. + +Once the token from the Rubrik cluster has been added, RSC synchronizes events, reports, and metadata from the Rubrik cluster. Synchronization can take up to 24 hours from the time the token has been added, depending on the size and performance of the Rubrik cluster. While synchronizing, the Rubrik cluster is in an Initializing state until the synchronization is complete. If the Initializing state persists over 24 hours, contact Rubrik Support. diff --git a/saas_common_rubrik_clusters_2.md b/saas_common_rubrik_clusters_2.md new file mode 100644 index 0000000000000000000000000000000000000000..e905f0eba03b2104564c9cd40b68959991080929 --- /dev/null +++ b/saas_common_rubrik_clusters_2.md @@ -0,0 +1,19 @@ +# Rubrik clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rubrik_clusters_2.html + +--- + +# Rubrik clusters + +A Rubrik cluster is an instance of Rubrik CDM running on any virtual or physical platform. You can add the Rubrik cluster to RSC to enable extended features for the cluster. + +A Rubrik cluster is an instance of Rubrik CDM running on any virtual or physical platform, and is a distributed, scale-out system that serves as the foundation for the Rubrik data security and management platform. The Rubrik platform protects and manages data across various environments, including on-premises data centers, private clouds, and public clouds. + +A Rubrik cluster is made up of multiple nodes that work together to provide a unified platform for backup, recovery, archival, and more. + +You can add Rubrik clusters toRSC to monitor backup events, ensure compliance, and view the protection status for those Rubrik clusters. + +Rubrik clusters use a single-token from RSC to authenticate and secure an ongoing connection. + +Once the token from the Rubrik cluster has been added, RSC synchronizes events, reports, and metadata from the Rubrik cluster. Synchronization can take up to 24 hours from the time the token has been added, depending on the size and performance of the Rubrik cluster. While synchronizing, the Rubrik cluster is in an Initializing state until the synchronization is complete. If the Initializing state persists over 24 hours, contact Rubrik Support. diff --git a/saas_common_rubrik_nas_cd_clusters.md b/saas_common_rubrik_nas_cd_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..15dd1579ecce16f02709be56390d044738044733 --- /dev/null +++ b/saas_common_rubrik_nas_cd_clusters.md @@ -0,0 +1,19 @@ +# Rubrik NAS CD clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/rubrik_nas_cd_clusters.html + +--- + +# Rubrik NAS CD clusters + +Rubrik NAS Cloud Direct clusters are Rubrik clusters that protect large-scale NAS data. + +Rubrik NAS Cloud Direct (NAS CD) clusters provide secure, reliable, and high-performance backup and archiving for enterprise environments. NAS CD clusters offer scalable data protection for unstructured file and object data, including documents, images, and videos. This data can reside on various NAS devices, such as Dell EMC Isilon, NetApp ONTAP, and a wide range of other generic NAS systems. NAS CD clusters efficiently scan NAS data, securely back up the data, and transfer it directly to cloud storage. The Rubrik NAS Cloud Direct User Guide provides more information about NAS CD clusters, the supported NAS devices, and other features. + +NAS CD clusters protect data using virtual machine appliances, which you set up in the data center or cloud environment of your organization. From Rubrik Security Cloud (RSC), you can: + + * Download NAS CD virtual machine images customized for your specific virtualization platform. + * Monitor the health and operational status of NAS CD virtual machines. + * Access the NAS CD UI to configure and manage the selected NAS CD cluster. + + *[ > ]: and then diff --git a/saas_common_saas_authentication.md b/saas_common_saas_authentication.md new file mode 100644 index 0000000000000000000000000000000000000000..a5868219edfc4f773a9fc0e59df02239b8c81f65 --- /dev/null +++ b/saas_common_saas_authentication.md @@ -0,0 +1,14 @@ +# Authentication + +Source: https://docs.rubrik.com/en-us/saas/saas/common/saas_authentication.html + +--- + +# Authentication + +Rubrik Security Cloud authentication restricts access to a specified set of users. + +RSC requires and enforces the use of strong passwords for all user authentication. This helps detect brute-force attacks and to block credentials identified in security breaches. Customer data is protected from common SaaS security issues, such as session hijacking, script insertion, and cross-site request forgery. + +The IP allowlist enables RSC to restrict login access to a specified list of IP addresses, address ranges, or subnets. + *[ > ]: and then diff --git a/saas_common_searching_an_event.md b/saas_common_searching_an_event.md new file mode 100644 index 0000000000000000000000000000000000000000..270050ce2effa696495bf78b8d2ee49f87f7b38f --- /dev/null +++ b/saas_common_searching_an_event.md @@ -0,0 +1,14 @@ +# Searching for an event + +Source: https://docs.rubrik.com/en-us/saas/saas/common/searching_an_event.html + +--- + +# Searching for an event + +RSC searches a specific event by object name. + +Enter a search string in the Search object name field to display a list of objects that match the search string. + +RSC begins a predictive search and updates the results as letters are entered in. The search matches the characters entered in the search field with the same sequence of characters anywhere in an object name. + *[ > ]: and then diff --git a/saas_common_sec_new_device_login_notification.md b/saas_common_sec_new_device_login_notification.md new file mode 100644 index 0000000000000000000000000000000000000000..1d4d8c801881425b3b834acc056eba01716b3d12 --- /dev/null +++ b/saas_common_sec_new_device_login_notification.md @@ -0,0 +1,29 @@ +# New device login notification + +Source: https://docs.rubrik.com/en-us/saas/saas/common/sec_new_device_login_notification.html + +--- + +# New device login notification + +RSC notifies you when a new device is used to log in to your RSC account, providing details such as device name, IP address, and location. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +In the current cybersecurity environment, unauthorized access poses a significant risk to organizations, potentially leading to data breaches and financial losses. To mitigate the risk, RSC sends you notifications through different channels whenever it detects login from a new device. This empowers you to proactively monitor your account security, detect unauthorized access promptly, and take swift action to prevent data breaches. + +## Notification details + +To inform you about new device logins, RSC provides notifications through multiple channels. + + * Email alerts: You receive an email at your registered email ID whenever RSC detects a login from a new device. This email includes important details such as the device name, IP address, location, and a link to reset your password. + * RSC Inbox notifications: In addition to the email, a notification appears in the RSC Inbox, displaying the name of the new device. You can click the notification to view the device details. + +## Device management + +Managing your devices effectively is important to maintaining RSC account security. + + * User Preferences page: You can view all the devices used to log in to your account in the last 60 days or the number of days specified in the MFA member token, whichever is longer. + * Automatic and manual management: RSC automatically removes devices that are not used to log in within the last 60 days or the number of days specified in the MFA member token. You also have the manual option to rename or delete devices from your account, keeping your device list organized and secure. + + *[ > ]: and then diff --git a/saas_common_sec_removing_device.md b/saas_common_sec_removing_device.md new file mode 100644 index 0000000000000000000000000000000000000000..8fde905c0083cac4513f75ee2d23044692c3a63b --- /dev/null +++ b/saas_common_sec_removing_device.md @@ -0,0 +1,41 @@ +# Removing a device + +Source: https://docs.rubrik.com/en-us/saas/saas/common/sec_removing_device.html + +--- + +# Removing a device + +You can remove a device from the My Devices page in RSC to get notified whenever RSC detects a login from that device. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Removing a device does not permanently prevent it from accessing your account. Instead, it only removes the device from the list of recognized devices in the My Devices page. If a removed device is used to log in to your account again, RSC treats it as a new device and notifies you through email and RSC Inbox notifications. By removing a device, you can ensure that RSC flags the future login attempts from that device, enabling you to promptly identify and address unauthorized access by changing your password or further restricting access. + +Note: + +Removing a device does not terminate any active sessions. If you want to terminate any active sessions, you must change the password for your account. + +## Procedure + + 1. Log in to RSC. + 2. Click and select User Preferences. + +The User Preferences page appears. + + 3. Click My Devices. + +The My Devices page appears. + + 4. Click for the device you want to remove. + +The Remove Device dialog box appears. + + 5. Click Remove. + +## Results + +RSC removes the device. + *[ > ]: and then diff --git a/saas_common_security.md b/saas_common_security.md new file mode 100644 index 0000000000000000000000000000000000000000..8f1e7d27e435725aad63db127d67fbf7324c564c --- /dev/null +++ b/saas_common_security.md @@ -0,0 +1,11 @@ +# Security + +Source: https://docs.rubrik.com/en-us/saas/saas/common/security.html + +--- + +# Security + +Rubrik Security Cloud provides end-to-end security for data management information. + +RSC offers a multi-layered security approach that protects the integrity and privacy of applications and data. diff --git a/saas_common_sending_instant_report.md b/saas_common_sending_instant_report.md new file mode 100644 index 0000000000000000000000000000000000000000..4164063da389ea4c1282fde7c8826c6392c05d45 --- /dev/null +++ b/saas_common_sending_instant_report.md @@ -0,0 +1,49 @@ +# Sending an instant report + +Source: https://docs.rubrik.com/en-us/saas/saas/common/sending_instant_report.html + +--- + +# Sending an instant report + +Email instant reports to the RSC domain administrator account or to an email address you configure. + +## About this task + +RSC emails instant reports as a CSV attachment. When the CSV attachments are larger than 10 MB, RSC automatically compresses the attachments as a ZIP file. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. In the report gallery, click one of the listed report types. + +A list of all available reports related to the selected report type appears. + + 4. Click the name of a report. + +The selected report page appears. + + 5. Click and select Send now. + +The Send Now pane appears. + + 6. Confirm the recipient email address. + +By default, the report is sent to the administrator email account for the RSC domain. + + 7. **Optional:** Click Add User or Email Address to deliver the report to additional recipients. + +You can add multiple users or email addresses by following the same process for adding each additional user or email address. + +A field appears with the option to add either a Rubrik user or an email address. + + 8. Click Send. + +## Results + +RSC generates the instant report and sends it to the recipients. + *[ > ]: and then diff --git a/saas_common_setting_data_management_privileges.md b/saas_common_setting_data_management_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..dcd337e810fdf8fdd56bceb06cb57ee93b107abd --- /dev/null +++ b/saas_common_setting_data_management_privileges.md @@ -0,0 +1,56 @@ +# Setting data management privileges by Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/setting_data_management_privileges.html + +--- + +# Setting data management privileges by Rubrik cluster + +Set privileges for a role to permit user accounts with the role to manage backup and recovery operations on a Rubrik cluster. + +## Before you begin + +Create a role to grant privileges to users, as described in [Creating a role](creating_role.html "Create a role to grant permissions to user accounts."). + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users and Access. + 4. Select Roles. + 5. Click Create Role. + +The Create role wizard appears. + + 6. Select a role from the role templates and click Next. + 7. In Data management, click Configure. + 8. Select By cluster and click Next. + +The Data management - Data source selection screen of the Create role appears. + + 9. Select the Rubrik cluster. + +RSC will assign privileges to the user accounts on the selected Rubrik clusters. You can select multiple Rubrik clusters and use locations and search strings to filter the list of Rubrik clusters. + +The Data management - privileges wizard appears. + + 10. Select the required privileges and click Next. + +The SLA Domains wizard appears. + + 11. Select a method for assigning SLA Domains. + +Option| Description +---|--- +Select all existing and future SLA Domains | Assign permissions to this role to manage existing and future SLA Domains. +Select specific SLA Domains | Assign permissions to this role to manage selected SLA Domains.In SLA Domain Name, select SLA Domains to be managed by this role. Select clusters in Managed By to show only SLA Domains from the selected clusters. Enter a search string in the Search by name field to display only SLA Domains with names that match the string. + + 12. Click Done. + +## Results + +RSC assigns the specified privileges to the role. + *[ > ]: and then diff --git a/saas_common_setting_disk_rbk_or_supp_tp_cluster.md b/saas_common_setting_disk_rbk_or_supp_tp_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..1dae7da268f415b28e6f434a42d42536c3122a93 --- /dev/null +++ b/saas_common_setting_disk_rbk_or_supp_tp_cluster.md @@ -0,0 +1,35 @@ +# Setting up disks on Rubrik or supported third-party clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/setting_disk_rbk_or_supp_tp_cluster.html + +--- + +# Setting up disks on Rubrik or supported third-party clusters + +Set up a disk on a Rubrik or supported third-party cluster. + +## Before you begin + +Insert the new disk into the computer chassis or add the disk to the virtual cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click Nodes. + +The Nodes details page appears. + + 5. In Node Name, click the name of the node requiring a disk setup. + +Disks that are unformatted and require setup have an exclamation mark for their Status in the HDD Disks table. + +The details page for this node appears. + + 6. Click Set up to set up the newly added disk. + +## Results + +The disks are set up automatically on the Rubrik or supported third-party cluster. There are no user interactions required. + *[ > ]: and then diff --git a/saas_common_setting_dm_privileges_by_object_type.md b/saas_common_setting_dm_privileges_by_object_type.md new file mode 100644 index 0000000000000000000000000000000000000000..b9f043c5b45ce0b830f5c43a7f3c2e3a152b66a5 --- /dev/null +++ b/saas_common_setting_dm_privileges_by_object_type.md @@ -0,0 +1,93 @@ +# Setting data management privileges by object type + +Source: https://docs.rubrik.com/en-us/saas/saas/common/setting_dm_privileges_by_object_type.html + +--- + +# Setting data management privileges by object type + +Set data protection and recovery permissions for protected data objects. + +## Before you begin + +Create a role to grant privileges to users, as described in [Creating a role](creating_role.html "Create a role to grant permissions to user accounts."). + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users and Access. + 4. Select Roles. + 5. Click Create Role. + +The Create role wizard appears. + + 6. Select a role from the role templates and click Next. + 7. In Data management, click Configure. + 8. Select By object type and click Next. + +The Data management - by type wizard appears. + + 9. Select an object type. + +The default privilege set for the select type appears. + + 10. Click All protectable objects. + +The Protectable object selection wizard appears. + + 11. Select a method for identifying objects of the selected object type. + +Option| Description +---|--- +Select all existing and future objects | Applies data management privileges to all existing and future objects. +Select specific objects | Applies data management privileges to selected objects.Select the objects that require protection. Enter a search string in the Search by name field to display only objects with names that match the string. + +When selecting specific objects, a list of protected objects of the selected type appears. Otherwise, all objects are selected. + + 12. Click Done. + +The Protectable object selection wizard closes and the Data management - by type page regains focus. + + 13. Click All recovery targets. + +The Recovery target selection wizard appears. + + 14. Select a method for selecting recovery targets of the selected object type. + +Option| Description +---|--- +Select all existing and future recovery targets | Uses all existing and future objects as the recovery targets. +Select specific recovery targets | Uses the selected objects as the recovery targets.Select the objects to be used as recovery targets. Enter a search string in the Search by name field to display only objects with names that match the string. + +When selecting specific recovery targets, a list of recovery targets of the selected type appears. + + 15. Click Done. + +The Protectable object selection wizard closes and the Data management - by type page regains focus. + + 16. Click Full privileges. + +The list of privileges for the selected type appears. + + 17. Select boxes that correspond to the privileges that the role grants and click Done. + 18. Click Next. + +The wizard advances to the SLA Domains selection step. + + 19. Select a method for assigning SLA Domains. + +Option| Description +---|--- +Select all existing and future SLA Domains | Assigns all existing and future SLA Domains to the custom role. +Select specific SLA Domains | Assigns the selected SLA Domains to the custom role.For specific SLA Domain, select Rubrik cluster in Managed By to view only SLA Domains from the selected clusters. Enter a search string in the Search by name field to display only SLA Domains with names that match the string. + + 20. Click Done. + +## Results + +RSC assigns the specified privileges to the role. + *[ > ]: and then diff --git a/saas_common_setting_system_configuration_privileges.md b/saas_common_setting_system_configuration_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..9cb0bca879d586af0e9cc3ccd60737e0e05f0513 --- /dev/null +++ b/saas_common_setting_system_configuration_privileges.md @@ -0,0 +1,48 @@ +# Setting system configuration privileges + +Source: https://docs.rubrik.com/en-us/saas/saas/common/setting_system_configuration_privileges.html + +--- + +# Setting system configuration privileges + +System configuration privileges enable users to manage aspects of RSC and the associated Rubrik clusters. + +## About this task + +This task is performed while creating or modifying a user role, as described in [User roles and permissions](roles_and_permissions.html "Roles are sets of permissions that are assigned to a user account. You can assign multiple roles to a user account."). + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users and Access. + 4. Select Roles. + 5. Click Create Role. + +The Create role wizard appears. + + 6. Select a role from the role templates and click Next. + 7. In System configuration, click Configure. + 8. Select boxes that correspond to the privileges that the role grants. + 9. **Optional:** In Cluster configuration, click All clusters. + +The Select clusters wizard appears. + + 10. Select a method for identifying clusters. + +Option| Description +---|--- +Select all existing and future clusters | Applies data management privileges to all existing and future clusters. +Select specific clusters | Applies data management privileges to selected clusters.Select the clusters on which this role grants privileges. + + 11. (Select specific clusters) Select the clusters on which this role grants privileges. + 12. Click Done. + +## Results + +RSC assigns the specified privileges to the role. + *[ > ]: and then diff --git a/saas_common_sla_domain_versions.md b/saas_common_sla_domain_versions.md new file mode 100644 index 0000000000000000000000000000000000000000..2c19759732e62fb4d72ee6fe7c8291e201a0fe88 --- /dev/null +++ b/saas_common_sla_domain_versions.md @@ -0,0 +1,39 @@ +# SLA Domain versions + +Source: https://docs.rubrik.com/en-us/saas/saas/common/sla_domain_versions.html + +--- + +# SLA Domain versions + +View changes made to the data protection policies of an SLA Domain. + +A new version of an SLA Domain is created each time the SLA Domain is modified. All versions of an SLA Domain are listed. + +When an SLA Domain is created, a version number of 1 is assigned to it. This version number is incremented by one each time the SLA Domain is modified. + +The SLA Domain version follows the format SLA Domain name-local version number-remote version number, where version number indicates the version number of the local SLA Domain, version number corresponds to the SLA Domain version on a replication target. + +For example, an SLA Domain SLA3d-2, indicates that local SLA Domain SLA3d was modified once after it was created. + +An SLA Domain SLA3d-2-1 indicates that local SLA Domain SLA3d was modified once after it was created and that the SLA Domain on the replication target has not been modified after it was created. + +The following table describes how to access this information. + +Option | Description +---|--- +SLA Domain page | + + 1. On RSC, click SLA Domain. + 2. Select an SLA Domain. + 3. Click Audit. + 4. Click a specific version to view details of the modifications. + + +Reports page | + + 1. On RSC, click Reports. + 2. Create or view an existing SLA Audit Report. + 3. Click on a specific version to view details of the modifications. + + *[ > ]: and then diff --git a/saas_common_support_access.md b/saas_common_support_access.md new file mode 100644 index 0000000000000000000000000000000000000000..80b77c98f42868f9e208cf7ec965e63dee161c0a --- /dev/null +++ b/saas_common_support_access.md @@ -0,0 +1,15 @@ +# Support access + +Source: https://docs.rubrik.com/en-us/saas/saas/common/support_access.html + +--- + +# Support access + +The support access feature provides Rubrik Support with secure, read-only access to your Rubrik Security Cloud domain on behalf of an existing user account. + +The support access feature enables Rubrik Support to securely access your Rubrik Security Cloud (RSC) domain in read-only mode. If you have an issue with your RSC account, you must create a Rubrik Support case. Rubrik Support uses the support access feature to understand the complete context of the issue with your RSC account and resolve them. + +An RSC user account with owner or administrator privileges can enable Rubrik Support to access your RSC domain on behalf of a specified RSCuser account. The access duration for a support access instance can be set between 1 and 99 days. + +When you edit support access duration, you can only increase the duration for the support access instance to be active. All Rubrik Support sessions in the support access instance are automatically logged out after the support access duration ends. At any given time, RSC allows only one support access grant for a specific support case on behalf of a specific RSC user account. Each support access session initiated by Rubrik Support is valid for a maximum of 4 hours for security reasons. After 4 hours the support session times out, and Rubrik Support can initiate the support session again. All Rubrik Support operations are audited, and you can view or download the audit logs. diff --git a/saas_common_support_tunnel_page_available_info.md b/saas_common_support_tunnel_page_available_info.md new file mode 100644 index 0000000000000000000000000000000000000000..c0b15c6ce7322a48d2f299aee957c419ad4a2456 --- /dev/null +++ b/saas_common_support_tunnel_page_available_info.md @@ -0,0 +1,20 @@ +# Information available on the Support Tunnel page + +Source: https://docs.rubrik.com/en-us/saas/saas/common/support_tunnel_page_available_info.html + +--- + +# Information available on the Support Tunnel page + +Information about the details provided by the Support Tunnel page, including cluster name, UUID, tunnel status, open nodes, open port, time opened, and time left. + +The following table describes the information provided by the Support Tunnel page: Detail | Description +---|--- +Cluster | Name of the Rubrik cluster.Rubrik clusters that are disconnected from RSC have a yellow visual indicator next to the cluster name. +UUID | Universally unique identifier (UUID) assigned to the Rubrik cluster. +Tunnel Status | Status of the support tunnel for each cluster, either Open or Closed. +Open Nodes | Nodes that have an open support tunnel. +Open Port | Port number used by each node. +Time Opened | For open support tunnels, the time the support tunnel was opened. +Timeout Window | For open support tunnels, the amount of time left before the support tunnel closes. + *[ > ]: and then diff --git a/saas_common_support_tunnel_timeout_setting.md b/saas_common_support_tunnel_timeout_setting.md new file mode 100644 index 0000000000000000000000000000000000000000..9523a1c431e7364295b0c62cfa24037513442fa6 --- /dev/null +++ b/saas_common_support_tunnel_timeout_setting.md @@ -0,0 +1,34 @@ +# Timeout setting for support tunnels + +Source: https://docs.rubrik.com/en-us/saas/saas/common/support_tunnel_timeout_setting.html + +--- + +# Timeout setting for support tunnels + +You can specify the duration for which a Rubrik support tunnel remains open by setting either an inactivity timeout or an absolute timeout. Inactivity timeout resets with any activity, and absolute timeout is fixed regardless of activity. + +When you are opening a Rubrik support tunnel, you can specify how long the support tunnel should remain open. By default, this value represents inactivity timeout, not absolute timeout. + +The difference between inactivity timeout and absolute timeout is as follows: + + * Inactivity timeout: Indicates the duration for which the support tunnel stays open but remains inactive. If the authorized Rubrik Support engineer accesses the support tunnel at any point during this time, the countdown timer to close the tunnel resets. If no value is specified, the default inactivity timeout is 96 hours. + +For example, if you set an inactivity timeout value of 2 hours and the support tunnel remains inactive for 1 hour, when a Rubrik Support engineer attempts to connect to the tunnel, the timer will reset to 0 and the support tunnel can remain inactive for another 2 hours. However, if the support tunnel remains inactive for 2 hours, it closes automatically because it has reached its timeout value. + + * Absolute timeout: Indicates the fixed duration for which the support tunnel will be open. This value is not affected by activity or inactivity. + +Note: + +After you open a support tunnel, it will remain open until either the inactivity timeout is reached and triggers an automatic closure or you manually close the tunnel. + +You can view the timeout type currently in use and switch to the other type by logging in to a Rubrik cluster through SSH and using the following commands: Task | Command +---|--- +Viewing the existing timeout type | support tunnel get_timeout_type +Changing to the absolute timeout type | support tunnel use_fixed_interval_timeout +Changing to the inactivity timeout type | support tunnel use_inactivity_timeout + +The Support management section in the Rubrik CDM CLI Guide provides more information about support tunnel commands. + +When you use the commands to switch between timeout types, open support tunnels will be closed automatically. However, the tunnel status might take time to reflect in RSC. To avoid this delay, you can close the support tunnel and then reopen it from RSC to see the updated timeout type. + *[ > ]: and then diff --git a/saas_common_support_tunnels.md b/saas_common_support_tunnels.md new file mode 100644 index 0000000000000000000000000000000000000000..0b4ec007454ca4468661da2684e492b72cdc9f9b --- /dev/null +++ b/saas_common_support_tunnels.md @@ -0,0 +1,24 @@ +# Support tunnel for RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/common/support_tunnels.html + +--- + +# Support tunnel for RSC + +Support tunnel is a functionality that allows authorized Rubrik Support engineers gain secure, logged access to Rubrik clusters for diagnosis and resolution of hardware and software issues. + +Rubrik clusters provide a built-in support tunnel utility. The Rubrik support tunnel facilitates efficient and secure troubleshooting of Rubrik clusters. + +By using a support tunnel, an authorized Rubrik Support engineer can access the Rubrik cluster to address issues related to the service, operating system, database, or configuration. This capability significantly reduces the time and effort required to resolve these issues, eliminating the need for lengthy screen-sharing sessions or phone calls. Rubrik enables access to the support tunnel through RSC and restricts the access using RSC RBAC. + +To ensure highly controlled and monitored access, Rubrik implements the following security measures for the support tunnel: Security measure | Description +---|--- +User control | RSC gives you complete control over the availability of a support tunnel. When you choose, you can open and close a support tunnel to one of your Rubrik clusters. For each support tunnel that you open, you can also define a time-based policy for automatically closing it, using a specified period of inactivity or a specified time limit. +MFA and SSO | Access to the support tunnel requires MFA and SSO, ensuring only verified Rubrik Support engineers can gain access. +Authorization | Only authorized Rubrik Support engineers requiring troubleshooting access can use the support tunnel. +Logged actions | All actions the Rubrik Support engineer performs are logged on the Rubrik cluster and available for your collection and audit. +Internal audits | Rubrik conducts regular internal audits on support tunnel access. These audits ensure effective access controls, appropriate use of the support tunnel, and prompt identification and mitigation of unauthorized access. +Secure entry point and VPN | The support tunnel system uses a secure and access-controlled server as its entry point. Rubrik Support access is only available through Rubrik internal networks, which are restricted by authenticated VPN access. +HTTPS proxy | The support tunnel connection passes through an HTTPS proxy located at proxy.rubrik.com over port 443. When using SNI filtering with Rubrik CDM version 9.1.1 or later, you must allow the hostname rsukg.proxy.rubrik.com along with proxy.rubrik.com. Since the hostname might change in future releases, you can future-proof the exception by using *.proxy.rubrik.com. +Data security | Data stored on the Rubrik cluster is encrypted and not directly accessible over the support tunnel. Rubrik Support engineers can view and modify the configuration and metadata stored in the cluster configuration database. The Rubrik cluster logs all remote console actions performed by the Rubrik Support engineer and makes them available for your collection and audit. diff --git a/saas_common_viewing_clusters_page.md b/saas_common_viewing_clusters_page.md new file mode 100644 index 0000000000000000000000000000000000000000..d802bad4ebfd3354259922b654022b2b9197d184 --- /dev/null +++ b/saas_common_viewing_clusters_page.md @@ -0,0 +1,20 @@ +# Viewing the Clusters page + +Source: https://docs.rubrik.com/en-us/saas/saas/common/viewing_clusters_page.html + +--- + +# Viewing the Clusters page + +RSC displays an aggregate view of all connected Rubrik clusters on the Clusters page. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + +## Results + +RSC displays a list of all connected Rubrik clusters. + *[ > ]: and then diff --git a/saas_common_viewing_events_page_clusters_tab.md b/saas_common_viewing_events_page_clusters_tab.md new file mode 100644 index 0000000000000000000000000000000000000000..75d399bec78fc415678cd8cc556af607a173a9b7 --- /dev/null +++ b/saas_common_viewing_events_page_clusters_tab.md @@ -0,0 +1,42 @@ +# Viewing the Events page from the Clusters tab + +Source: https://docs.rubrik.com/en-us/saas/saas/common/viewing_events_page_clusters_tab.html + +--- + +# Viewing the Events page from the Clusters tab + +View the Events page from the Clusters tab to get a global view of all events of the selected Rubrik cluster connected to RSC. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + +The Cluster Details page appears. + + 5. On a Rubrik cluster, click within the Events section. + +The selected Cluster page appears. + + 6. Click within the Events section. + +Clicking on system, archival, and back up events opens the Events page for the selected Rubrik cluster and type of event. + +The Events page appears. + + 7. **Optional:** Change filters to dynamically change the Events page view. + 8. Click an event. + +The event expands. + +This page displays the series of events associated with the top-level event, such as the Rubrik cluster name, object type, event type, duration of the event, start time of the event, and the details of each event within the event timeline. + + 9. **Optional:** Apply filters to view the Events page with the aggregate values based on the selected filter. + +## Results + +The event details appear. + *[ > ]: and then diff --git a/saas_common_viewing_nas_cd_virtual_machine_details.md b/saas_common_viewing_nas_cd_virtual_machine_details.md new file mode 100644 index 0000000000000000000000000000000000000000..dc7ea803a23a351547aa1193b7bceba11145d90f --- /dev/null +++ b/saas_common_viewing_nas_cd_virtual_machine_details.md @@ -0,0 +1,27 @@ +# Viewing NAS CD virtual machine details + +Source: https://docs.rubrik.com/en-us/saas/saas/common/viewing_nas_cd_virtual_machine_details.html + +--- + +# Viewing NAS CD virtual machine details + +View the details of a NAS CD virtual machine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. In the Clusters column, select a NAS CD cluster. + +The NAS CD Cluster Details page for the cluster appears. + + 5. Click View & Manage Site. + +RSC redirects you to the Systems page of your NAS CD cluster. + +## Results + +RSCdisplays a list of all the connected virtual machines for the cluster. + *[ > ]: and then diff --git a/saas_common_viewing_network_details_cdm_921_later.md b/saas_common_viewing_network_details_cdm_921_later.md new file mode 100644 index 0000000000000000000000000000000000000000..6c0fd9114f9bd98474944b938c9c721d37cae450 --- /dev/null +++ b/saas_common_viewing_network_details_cdm_921_later.md @@ -0,0 +1,35 @@ +# Viewing network details in CDM v9.2.1 or later + +Source: https://docs.rubrik.com/en-us/saas/saas/common/viewing_network_details_cdm_921_later.html + +--- + +# Viewing network details in CDM v9.2.1 or later + +View network details of a Rubrik cluster to manage the network settings of the Rubrik cluster. + +## Before you begin + +Ensure that the Rubrik cluster is running Rubrik CDM version 9.2.1 or later. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +On the Cluster Settings page, you can manage the network details of a cluster, including adding VLAN, floating IP addresses, proxy settings, NTP servers, static routing table, DNS & search domains. You can also edit or delete VLANs and NTP servers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + 3. Click Clusters and select Cluster Settings. + 4. Click a Rubrik cluster. + +The cluster details page appears. + + 5. Click Network. + +## Results + +The Network page appears and displays information about networks associated with the cluster. + *[ > ]: and then diff --git a/saas_common_viewing_network_details_rubrik_clusters.md b/saas_common_viewing_network_details_rubrik_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..3af6cf6cbe68f2821d8e18cf2ecaca21cc7a0dca --- /dev/null +++ b/saas_common_viewing_network_details_rubrik_clusters.md @@ -0,0 +1,33 @@ +# Viewing network details for Rubrik clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/common/viewing_network_details_rubrik_clusters.html + +--- + +# Viewing network details for Rubrik clusters + +From the Network Details page, review and manage networks associated with a Rubrik cluster. This includes viewing network configurations such as node names, networks, IP addresses, floating IPs, and subnet masks. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click a Rubrik cluster. + 5. Select the cluster based on the version. + +Version| Description +---|--- +CDM version 9.2.0 or earlier | Click Network Details.You can filter the information on the Network Details page according to network type, including Data, Management, or VLAN. +CDM version 9.2.1 or later | Click Manage Cluster Settings and then click Network. + +The cluster details page appears. + +## Results + +RSC displays a list of networks associated with the Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_viewing_own_reports.md b/saas_common_viewing_own_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..dc267bb05f60e8fdbeb94fa67e3965b68de7f1ec --- /dev/null +++ b/saas_common_viewing_own_reports.md @@ -0,0 +1,23 @@ +# Viewing your own reports + +Source: https://docs.rubrik.com/en-us/saas/saas/common/viewing_own_reports.html + +--- + +# Viewing your own reports + +To easily view and manage your reports on RSC, view only the reports that you have created in your RSC domain on the Reports page. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears, displaying all the reports created in an RSC domain. + + 3. Turn on View My Reports Only. + +## Results + +RSC displays all the reports that you have created. + *[ > ]: and then diff --git a/saas_common_viewing_support_access_audit_logs.md b/saas_common_viewing_support_access_audit_logs.md new file mode 100644 index 0000000000000000000000000000000000000000..f041f998301f54ac3222fc4ce444cbf625c03b65 --- /dev/null +++ b/saas_common_viewing_support_access_audit_logs.md @@ -0,0 +1,31 @@ +# Viewing support access audit logs + +Source: https://docs.rubrik.com/en-us/saas/saas/common/viewing_support_access_audit_logs.html + +--- + +# Viewing support access audit logs + +An RSC user account with owner or administrator privileges can view and download audit log information of support access instance for an RSC user account. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Settings. + +A new tab displaying the settings menu opens on your browser. + + 3. Click Customer Support and select Support Access. + +The Support Access page appears. + + 4. Open the ellipsis menu for a support access instance and select View Audit Log. + +You can select a time range from the available time range filters to view the events details for a specific period of time. You can also select the filters for clusters, severity, and status to customize the audit log view. + + 5. Click Download CSV to download the audit log details. + +## Results + +RSC allows you to view and download the audit log details for the selected support access instance. + *[ > ]: and then diff --git a/saas_common_visiting_a_rubrik_cluster.md b/saas_common_visiting_a_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..5da83c63035d1a01377fa221b80a60591bae6c2a --- /dev/null +++ b/saas_common_visiting_a_rubrik_cluster.md @@ -0,0 +1,29 @@ +# Visiting a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/common/visiting_a_rubrik_cluster.html + +--- + +# Visiting a Rubrik cluster + +RSC allows easy and direct access to connected Rubrik clusters from the Clusters page. + +## About this task + +RSC displays the configuration details on the Rubrik cluster setup. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Select a Rubrik cluster. + +The Clusters details page appears. + + 5. Click Visit cluster. + +## Results + +RSC opens a secure connection to the connected Rubrik cluster. RSC redirects the connection to the IP address of the connected Rubrik cluster. + *[ > ]: and then diff --git a/saas_common_webhooks.md b/saas_common_webhooks.md new file mode 100644 index 0000000000000000000000000000000000000000..66380242ccac32adb0a785a53c73edb03aac8db8 --- /dev/null +++ b/saas_common_webhooks.md @@ -0,0 +1,14 @@ +# Webhooks + +Source: https://docs.rubrik.com/en-us/saas/saas/common/webhooks.html + +--- + +# Webhooks + +Webhook integration provides the capability to send event details related to a service account from RSC to external systems. This makes it easier to monitor and analyze logs for security incidents while keeping control over data transmission. + +When an event occurs that matches the webhook trigger conditions, RSC sends an HTTP request with the relevant event and audit details (if configured) for the service account to the specified webhook URL. You can specify the format of webhook payloads using a Rubrik-provided default template or by creating your own custom JSON template inRSC. A custom template gives you the ability to select Rubrik-supported variables and structure webhook notifications according to your specific requirements. + +You can use webhooks to store and manage all Rubrik log data at a centralized location and meet compliance requirements. Additionally, you can create roles and then use these roles to view, manage, and assign webhooks to users. + *[ > ]: and then diff --git a/saas_configuring_cascading_archival.md b/saas_configuring_cascading_archival.md new file mode 100644 index 0000000000000000000000000000000000000000..860799d89bedb8cc282e6f4039146663d03f9fff --- /dev/null +++ b/saas_configuring_cascading_archival.md @@ -0,0 +1,140 @@ +# Configuring cascading archival + +Source: https://docs.rubrik.com/en-us/saas/saas/configuring_cascading_archival.html + +--- + +# Configuring cascading archival + +When you create or edit an SLA Domain, configure cascading archival settings for a replication target Rubrik cluster. + +## Before you begin + +Do the following: + + * Configure an archival location on the replication target cluster, as described in [Creating a data center archival location](../archival/arch_dc_creating_an_archival_location.html "Create an archival location and associate it with a Rubrik cluster for archiving data."). + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +You can configure cascading archival only in an SLA Domain that includes a replication policy. With RSC, you can configure cascading archival settings for each replication policy. As part of these settings, specify the cascading archival location for each target cluster within the replication policy. You cannot, however, configure cascading archival if the Rubrik cluster is disconnected from RSC. + +On-demand snapshots do not support cascading archival, meaning snapshots taken through the on-demand snapshot are not archived through cascading archival. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click SLA Domains. + +The SLA Domains page appears. + + 4. Click Create SLA Domain. + +Ensure that you understand the provided information about SLA Domains, including snapshot frequency and retention policies, before proceeding to create an SLA Domain. + +The Create SLA Domain wizard appears. + + 5. Click Create on the Create SLA Domain page that describes SLA Domains. + 6. Select the workload types and click Next. + +You can enable cascading archival only for workload types that are managed through Rubrik clusters. + + 7. **Optional:** Turn on Retention Lock. + +Selecting this option applies retention lock, preventing data deletion outside the retention policy. + + 8. Click Next. + 9. Enter a snapshot frequency and a corresponding retention period. + +The snapshot frequency categories are optional, but at least one category must have a value. + + 10. Click Next. + +The Archival and Replication page appears. + + 11. Select Replication. + +Option| Description +---|--- +Many-to-one | Consolidates data from multiple source clusters into a single target cluster. +One-to-one | Involves direct replication between a single source and a single target.Selecting this option requires choosing the source clusters. You can select multiple source clusters, but each source cluster requires specifying its corresponding target cluster. Each source cluster can have up to two target clusters, with each connection remaining dedicated and separate for each source. + + 12. Click Next. + +The Replication Parameters page appears. + + 13. **Optional:** In Local Storage Retention, adjust the local retention period of snapshots on the source Rubrik cluster. + +This option appears only when you set the replication retention period to be the same as the maximum retention period configured. + + 14. In Replication Policy 1, select the target clusters. + +You can select the target cluster to be a cluster connected to RSC or to an isolated cluster. You cannot configure cascading archival to a cluster that is not connected to RSC. + +You can select target clusters only when they are part of an existing replication pairing, are connected, and you have the necessary permissions to use them as replication targets. + +When no target cluster exists in the Select Target Cluster dropdown, click Replication Pairings to create a replication pair. + +You can add a maximum of two replication policies. + + 15. In Replication Retention, enter the number of days for which you want to retain the replicated snapshots. + +Alternatively, you can use the slider to adjust the retention period within the available range. + +The snapshot replication retention period cannot exceed the maximum retention period configured for the snapshot frequency. + +When cascading archival is enabled, the replication retention period includes the retention period of both the snapshots on the replication target cluster and of those on the archival location. + + 16. Select Enable Cascading Archival to enable the target cluster to transfer replicated data to an archival location. + +When cascading archival is selected, choose the target archival locations for the policy. + + 17. Click Next. + +The Cascading Archival page appears. + + 18. In Target Cluster Retention, specify the snapshot retention period on the replication target. + +Alternatively, you can use the slider to adjust the retention period within the available range. The maximum value of this retention period is limited by the replication retention period. + +The retention period on the target cluster specifies the number of days for which the snapshots are retained on the replication target cluster before they expire. + + 19. In Cascading Archival Policy 1, select an archival location for each replication target cluster. + +You can add a maximum of two cascading archival policies. + +Additional configuration fields appear, depending on the type of selected archival location. + + 20. In Storage Tiering, select the storage tier for either AWS or Azure. + 21. In Snapshot Frequency, select snapshot frequencies. + +Selecting a frequency implies that RSC archives the snapshots taken at that frequency. + + 22. In Cascading Archival Threshold, make a choice between archiving instantly or after a specific period of time. + +Option| Result +---|--- +Select Enable Instant Archive | RSC archives the replicated snapshots instantly. +Clear Enable Instant Archive | RSC displays a slider to specify the cascading archival threshold value.The cascading archival threshold is the number of days after which RSC archives the replicated snapshots. + + 23. Click Next and configure the remaining SLA Domain settings. + +The Confirmation page appears. + + 24. In SLA Domain name, enter a name for the SLA Domain. + 25. **Optional:** In Add Description, enter a descriptive identification for the SLA Domain. + 26. Review the configuration details and click Create. + +## Results + +RSC creates an SLA Domain with cascading archival enabled. + +## What to do next + +Assign the SLA Domain to workloads to archive replicated snapshots of the workload. + *[ > ]: and then diff --git a/saas_connecting_a_cdm_cluster.md b/saas_connecting_a_cdm_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..13d11547b7f34176e8637fc6fa9db9860433c4b9 --- /dev/null +++ b/saas_connecting_a_cdm_cluster.md @@ -0,0 +1,45 @@ +# Connecting a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/connecting_a_cdm_cluster.html + +--- + +# Connecting a Rubrik cluster + +To enhance data protection capabilities, connect a Rubrik cluster to a Rubrik Security Cloud account. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Click and select Import Rubrik cluster. + +The Import Rubrik cluster dialog box appears. + + 5. Copy the single-use token to your clipboard. + 6. Click Done. + +The dialog box closes. + + 7. Log in to the Rubrik cluster using the administrator account or an account with administrator privileges. + 8. Click the on the top bar of the web UI. + +The Settings menu appears. + + 9. Select Cluster Settings. + +The Cluster Settings page appears. + + 10. In Global Cluster Manager Token, paste the token from your clipboard. + +Rubrik clusters use HTTPS when initially connecting to RSC. During this process, the system upgrades the connection protocol to WebSocket Secure (WSS) for secure bidirectional communication. The network administrator should verify that the WSS protocol is allowed across the network between the Rubrik cluster and RSC. + + 11. Click Update. + +## Results + +The Rubrik cluster saves the values and initiates a secure connection with the RSC domain. + +After a secure connection is established, the Rubrik cluster appears on the Clusters page in RSC. + *[ > ]: and then diff --git a/saas_continuous_data_protection_dashboard.md b/saas_continuous_data_protection_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..b928e450508c4160a3669ec8c54220d189014896 --- /dev/null +++ b/saas_continuous_data_protection_dashboard.md @@ -0,0 +1,57 @@ +# Continuous Data Protection dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/continuous_data_protection_dashboard.html + +--- + +# Continuous Data Protection dashboard + +The Continuous Data Protection dashboard provides information on the CDP status of virtual machines. + +Column Heading | Description +---|--- +Virtual Machine Name | Name of the virtual machine. +Location | Location of the virtual machine. +Source Cluster | Name of the source Rubrik cluster specified in the SLA Domain with Continuous Data Protection (CDP) enabled. +SLA Domain | Name of the SLA Domain with CDP enabled. +CDP Local Status | Status of CDP on the local cluster. Status can be: + + * Not Enabled + * Pending + * Taking Snapshot + * Active + * Resyncing + * Failed + + +CDP Replication Status | Status of replication on the target cluster. Status can be: + + * Failed + * Healthy + * Initializing + * Not Enabled + + +CDP Filter Status | Status of the CDP Filter. Status can be: + + * Inconsistent + * Up to date/Installed + * Install Error + * Install in progress + * Out of date + * Unavailable + * Not installed + * Uninstall error + * Uninstall in progress + * Unknown + * Unsupported by Rubrik + * Unsupported by VMware + * Upgrade error + * Upgrade in progress + + +Target Cluster | Name of the target cluster specified in the CDP-enabled SLA Domain. +Local Recovery Point | The most recent point in time to which a virtual machine can be recovered on a source cluster. +Remote Recovery Point | The most recent point in time to which a virtual machine can be recovered on a target cluster. This field is empty if replication is not enabled. +Latest Local Snapshot | The date and time of the latest local snapshot. + *[ > ]: and then diff --git a/saas_creating_cyber_rp_ahv.md b/saas_creating_cyber_rp_ahv.md new file mode 100644 index 0000000000000000000000000000000000000000..2a7e2c75b7bf318c548290a0315c310d923a38f4 --- /dev/null +++ b/saas_creating_cyber_rp_ahv.md @@ -0,0 +1,109 @@ +# Creating a cyber Recovery Plan for AHV virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/creating_cyber_rp_ahv.html + +--- + +# Creating a cyber Recovery Plan for AHV virtual machines + +Create a cyber Recovery Plan to protect a set of AHV virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears, listing all Recovery Plans. + +You can access vSphere virtual machines, AHV virtual machines, Azure virtual machines, and AWS virtual machines in the respective tabs. + + 4. Click AHV. + +The list of all AHV Recovery Plans appears. + + 5. Click Create and then select **Cyber Recovery Plan**. + +The Create Recovery Plan wizard appears. + + 6. Click Start. + +The Recovery Plan Details page appears. + + 7. **Optional:** Review the What is Cyber Recovery page and click Start. + +The informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. Selecting the option to not show the page again prevents this page from appearing in the future. + + 8. In Recovery Plan Name, enter a name for the Recovery Plan. + 9. In Recover from, select a Rubrik cluster. + +All virtual machines in the Recovery Plan must belong to the same Rubrik cluster. The list shows virtual machines and replicas on the selected cluster. + + 10. Click Next. + +The wizard lists the virtual machines on the source Rubrik cluster in the Select Virtual Machines page. + + 11. Select the virtual machines to recover and click Next. + +You can search for a virtual machine by name or use a filter to search for the results. + + 12. Click Next. + +The Assign a Boot Order page appears. + + 13. Assign a boot order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. Rubrik recommends that you first recover the Identity and Access Management and other core infrastructure services. + + 14. **Optional:** Turn on Enable pauses between priority groups. + +RSC displays the specified pauses during recovery in minutes. + + 15. Click Next. + +The Assign Target Compute Resources page appears. + + 16. **Optional:** Select the Assign the same compute resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign compute resources for individual objects. + + 17. Assign compute resources for the objects. + 18. Click Next. + +The Assign Target Storage Resources page appears. + + 19. Select the Assign the same storage resource for all objects check box to use the same storage resource for all objects and then select a single storage resource. + +This option is selected by default. If you do not select this option, you can assign storage resources for individual objects. + + 20. Click Next. + +The Assign Network Resources page appears. + + 21. Select an option for network preservation. + +Option| Description +---|--- +Remove all network devices. | Removes all network devices, allowing you to assign new target networks to each object. +Preserve MAC Address | Preserves the existing MAC address for each object. You can then select a Network from the pull-down options. + |  + + 22. **Optional:** Click Fast Fill to apply the selected values to multiple objects. + +The Fast Fill window opens for applying the network resource values to multiple objects. + + 23. Click Next. + +The Confirmation page appears, displaying the Recovery Plan details. + + 24. Click Confirm. + +## Results + +RSC creates the cyber recovery plan and provides options to Recover Now, Schedule Recovery Plan Tests, or Create Another Plan. + +When you click any of these options, RSC displays the appropriate wizard. + *[ > ]: and then diff --git a/saas_creating_cyber_rp_aws.md b/saas_creating_cyber_rp_aws.md new file mode 100644 index 0000000000000000000000000000000000000000..94e490a745b8f6cbf09756050a62e3c1f2585d7a --- /dev/null +++ b/saas_creating_cyber_rp_aws.md @@ -0,0 +1,95 @@ +# Creating a cyber Recovery Plan for AWS EC2 instances + +Source: https://docs.rubrik.com/en-us/saas/saas/creating_cyber_rp_aws.html + +--- + +# Creating a cyber Recovery Plan for AWS EC2 instances + +Create a cyber Recovery Plan to protect a set of AWS EC2 instances. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click AWS EC2 in the Objects tab. + +The list of all AWS EC2 instances appears. + + 4. Click Recovery Plans. + +The Recovery Plans page appears, listing all Recovery Plans. + +You can access vSphere virtual machines, AHV virtual machines, Azure virtual machines, and AWS virtual machines in the respective tabs. + + 5. Click Create. + +The Create Cyber Recovery Plan wizard appears. + + 6. In Recovery Plan Name, enter a name for the Recovery Plan. + 7. In Recovery Source, select an AWS Account and Region. + +RSC receives this information when you onboard your AWS cloud account. RSC can only recover to and from AWS cloud accounts that are registered with RSC. + + 8. In Recovery Target, select a target AWS Account and Region. + +The target region must be the same as the source region. You can recover AWS EC2 instances to the same or to an alternate account in the same region. + + 9. **Optional:** Under Additional Settings, select an option to export tags for the specific virtual machine snapshot selected for recovery. Then click Next. + 10. **Optional:** Review the What is Cyber Recovery page and click Start. + +The informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. Selecting the option to not show the page again prevents this page from appearing in the future. + + 11. Select the virtual machines to recover and click Next. + +You can search for a virtual machine by name or use a filter to search for the results. + + 12. Click Next. + +The Assign a Boot Order page appears. + + 13. Assign a boot order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple EC2 instances in the same priority group boot simultaneously. Rubrik recommends that you first recover the Identity and Access Management and other core infrastructure services. + +You can recover EC2 instances to the same recovery group or different recovery group. + + 14. **Optional:** Turn on Pause between priority groups. + +RSC displays, in minutes, the specified pauses during recovery. + + 15. Click Next. + +The Encryption and Access page appears. + + 16. Select how you want to set up encryption and access for the selected objects. + +Select| To +---|--- +Skip KMS key, key pair, and IAM instance profile | Choose to use the same encryption settings as the source object. Key Management Service (KMS) key, key pair, and IAM instance profile enable you to encrypt the objects. Unencrypted snapshots create unencrypted EC2 instances and EBS volumes. Encrypted EC2 instances and EBS volumes are encrypted using the source CMK. Use the key pair and password of the original instance to access the exported instance. +Configure encryption and access | Select options to encrypt with a platform-managed key, encrypt with the same customer-managed key, or select keys individually. + + 17. Click Next. + +The Target Networks page appears. + + 18. Configure the target networks. + +You can either configure the target networks individually or configure them in bulk. Select a VPC and Subnet for the EC2 instances. + + 19. **Optional:** Select one or more Security Groups. + 20. Click Next. + +The Confirmation page displays the Recovery Plan details. + + 21. Review your configuration and click Confirm. + +## Results + +RSC creates the cyber recovery plan for the selected AWS EC2 instances and provides options to Recover Now or Create Another Plan. + +When you click any of these options, RSC displays the appropriate wizard. + *[ > ]: and then diff --git a/saas_creating_cyber_rp_azure.md b/saas_creating_cyber_rp_azure.md new file mode 100644 index 0000000000000000000000000000000000000000..de65991281cdac391566f363231f65319d820ddf --- /dev/null +++ b/saas_creating_cyber_rp_azure.md @@ -0,0 +1,102 @@ +# Creating a cyber Recovery Plan for Azure virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/creating_cyber_rp_azure.html + +--- + +# Creating a cyber Recovery Plan for Azure virtual machines + +Create a cyber Recovery Plan to protect a set of Azure virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears, listing all Recovery Plans. + +You can access vSphere virtual machines, AHV virtual machines, Azure virtual machines, and AWS virtual machines in the respective tabs. + + 4. Click Azure VM. + +The list of all Azure Recovery Plans appears. + + 5. Click Create and then select **Cyber Recovery Plan**. + +The Create Recovery Plan wizard appears. + + 6. Click Start. + +The Recovery Plan Details page appears. + + 7. **Optional:** Review the What is Cyber Recovery page and click Start. + +The informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. Selecting the option to not show the page again prevents this page from appearing in the future. + + 8. In Recovery Plan Name, enter a name for the Recovery Plan. + 9. In Recovery Source, select a Subscription and a Region. + +RSC gets this information when you onboard your Azure cloud account. RSC can only recover to and from Azure cloud accounts that are registered with RSC. + + 10. In Recovery Target, select a Subscription. + +RSC supports cyber recovery for Azure virtual machines on the same region as the recovery source subscription only. You can recover Azure virtual machines to the same or to an alternate subscription in the same region. + + 11. In Plan-Level Recovery Settings, select an option to export tags for the specific virtual machine snapshot selected for recovery. Then click Next. + +The wizard lists the virtual machines on the source Rubrik cluster in the Select Virtual Machines page. + + 12. Select the virtual machines to recover and click Next. + +You can search for a virtual machine by name or use a filter to search for the results. + + 13. Click Next. + +The Assign a Boot Order page appears. + + 14. Assign a boot order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. Rubrik recommends that you first recover the Identity and Access Management and other core infrastructure services. + + 15. **Optional:** Turn on Enable pauses between priority groups. + +RSC displays the specified pauses during recovery in minutes. + + 16. Click Next. + +The Target Resource Group page appears. + + 17. Select a target resource group option. + +You can select the same resource group to all objects, or select a different resource group for objects. + + 18. Click Next. + +The Attached Disk Encryption page appears. + + 19. Select an option for Attached Disk Encryption and click Next. + +You can select options to encrypt with a platform-managed key, encrypt with the same customer-managed key, or select keys individually. + + 20. Click Next. + +The Target Networks page appears. + + 21. Select a VNet and Subnet. + 22. **Optional:** Select a Network Security Group. + 23. Click Next. + +The Confirmation page displays the Recovery Plan details. + + 24. Click Confirm. + +## Results + +RSC creates the cyber recovery plan for the selected Azure virtual machines and provides options to Recover Now, Schedule Recovery Plan Tests, or Create Another Plan. + +When you click any of these options, RSC displays the appropriate wizard. + *[ > ]: and then diff --git a/saas_creating_cyber_rp_vsphere.md b/saas_creating_cyber_rp_vsphere.md new file mode 100644 index 0000000000000000000000000000000000000000..d5b5194df2ccc8eb8cb311dd6caf60d066743c25 --- /dev/null +++ b/saas_creating_cyber_rp_vsphere.md @@ -0,0 +1,123 @@ +# Creating a cyber Recovery Plan for vSphere virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/creating_cyber_rp_vsphere.html + +--- + +# Creating a cyber Recovery Plan for vSphere virtual machines + +Create a cyber Recovery Plan to protect a set of virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears, listing all Recovery Plans. + +You can access vSphere virtual machines, AHV virtual machines, Azure virtual machines, and AWS virtual machines in the respective tabs. + + 4. Click vSphere. + +The list of all vSphere Recovery Plans appears. + + 5. Click Create and then select **Cyber Recovery Plan**. + +The Create Recovery Plan wizard appears. + + 6. Click Start. + +The Recovery Plan Details page appears. + + 7. **Optional:** Review the What is Cyber Recovery page and click Start. + +The informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. Selecting the option to not show the page again prevents this page from appearing in the future. + + 8. In Recovery Plan Name, enter a name for the Recovery Plan. + 9. In Recover from, select a Rubrik cluster. + +All virtual machines in the Recovery Plan must be protected by the same Rubrik cluster. The list shows virtual machines and replicas on the selected cluster. + + 10. Click Next. + +The wizard lists the virtual machines on the source Rubrik cluster in the Select Virtual Machines page. + + 11. Select the virtual machines to recover and click Next. + +You can search for a virtual machine by name or use a filter to search for the results. + + 12. Click Next. + +The Assign a Boot Order page appears. + + 13. Assign a boot priority order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. Rubrik recommends that you prioritize recovering Identity and Access Management and other core infrastructure services. + + 14. **Optional:** Turn on Enable pauses between priority groups. + +RSC displays the specified pauses during recovery in minutes. + + 15. Click Next. + +The Assign Target Compute Resources page appears. + + 16. **Optional:** Select the Assign the same compute resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign compute resources for individual objects. + + 17. Assign compute resources for the objects. + 18. Click Next. + +The Assign Target Storage Resources page appears. + + 19. Select an option for your planned recovery. + +Option| Description +---|--- +Assign storage resources | Assigning a datastore or datastore cluster is necessary if you plan to use the Export recovery method. If you do not assign a datastore or datastore cluster, you can only use Live Mount to recover using this plan. +Proceed without target storage resources | Only Live Mount can be used if you proceed without assigning target storage resources. + +Adding storage resources to the Recovery Plan is necessary only for using the Export option. + + 20. Click Next. + +The Assign Target Network Resource page appears. + + 21. Select one of the options for Network Preservation. + +Option| Description +---|--- +Select Entire Network and then select Network for each object. | The current MAC Address and IP configuration are retained. +Select MAC Address Only and then select Network and IP Configuration for each object. | The current MAC address is retained for the source virtual machine. +Select None and then select the Network and IP Configuration for each object. | A new MAC address will be assigned to the virtual machine. + + 22. **Optional:** Select the Recover with network disconnected check box. + 23. Click Fast Fill to apply the selected values to multiple objects. + +The Fast Fill window opens for applying the network resource values to multiple objects. + + 24. Click Next. + +The Specify Post-Recovery Scripts page appears. + + 25. **Optional:** In Post-Recovery Scripts, enter the path to a post-instantiation script for a virtual machine. + +Post-instantiation scripts increase the recovery time for a virtual machine due to the script demand on compute resources. + + 26. Click Next. + +The Confirmation page displays the Recovery Plan details. + + 27. Click Confirm. + +## Results + +RSC creates the cyber recovery plan and provides options to Recover Now, Schedule Recovery Plan Tests, or Create Another Plan. + +When you click any of these options, RSC displays the appropriate wizard. + *[ > ]: and then diff --git a/saas_creating_disaster_rp_ahv.md b/saas_creating_disaster_rp_ahv.md new file mode 100644 index 0000000000000000000000000000000000000000..4d61974bd3615d2783295d997174032dc33378f6 --- /dev/null +++ b/saas_creating_disaster_rp_ahv.md @@ -0,0 +1,114 @@ +# Creating a disaster Recovery Plan for AHV virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/creating_disaster_rp_ahv.html + +--- + +# Creating a disaster Recovery Plan for AHV virtual machines + +Create a disaster Recovery Plan to enable failover testing and production failover orchestration for a set of AHV virtual machines. + +## Before you begin + +Add the Nutanix Prism Central to RSC and enable data protection for the Nutanix disaster recovery workflow. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. On the AHV tab, click **Recovery Plans**. + +The Recovery Plans page appears, listing all Recovery Plans. + + 4. Click Create and then select Disaster Recovery Plan. + +The Create Recovery Plan wizard appears. + + 5. In Name, enter a name for the Recovery Plan. + 6. In Recover From, select a Rubrik cluster from the dropdown list. + +All virtual machines in the Recovery Plan must come from the selected Rubrik cluster. + + 7. In Recover To, select a Rubrik cluster from the dropdown list. + +During a failover operation, RSC creates virtual machines on the selected Rubrik cluster. + + 8. Click Next. + +The Select virtual machines page appears. + + 9. Select the virtual machines to recover and click Next. + +The Assign a Boot order page appears. + + 10. Select a boot priority group for each virtual machine. + 11. **Optional:** Turn on Enable pauses between priority groups. + +You can add pauses during recovery and display them in minutes between the priority groups by turning on the Enable pauses between priority groups option. + + 12. Click Next. + +The Assign Target Compute Resources page appears. + + 13. **Optional:** Select Assign the same compute resource for all objects to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. When you do not select this option, you can assign compute resources for individual objects. + + 14. Assign compute resources for the objects. + 15. Click Next. + +The Assign Target Storage Resources page appears. + + 16. **Optional:** Select Assign the same storage resource for all objects to use the same storage resource for all objects and then select a single storage resource. + +This option is selected by default. When you do not select this option, you can assign storage resources for individual objects. + + 17. Assign storage resources for the objects. + 18. Select Assign the same storage resource for all objects check box to use the same storage resource for all objects and then select a single storage resource. + 19. Click Next. + +The Assign Target Network Resources page appears. + + 20. Select the target networks to use for each object. + +RSC provides the list of available networks based on the compute resources you previously selected. + + 21. For Failover and Test Failover, select network preservation options. + +Option| Description +---|--- +Remove all network devices | Select when networking changes or issues prevent the virtual machine from starting. +Preserve MAC address | Select to use the MAC addresses from the snapshot instead of assigning new MAC addresses. When the snapshot contains manually assigned MAC addresses, those MAC addresses are used even when this option is not selected. + + 22. **Optional:** Click Fast Fill. + +The Fast Fill window appears. You can enter a target network for each virtual machine in the Recovery Plan for failover. + + 23. When using Fast Fill, select an option for choosing NICs and then click Apply. + * Apply to all NICs + * Apply to selected NICs + +The network configurations are applied to the virtual machines during recovery. + + 24. Click Next. + +The Assign post-failover SLA Domains page appears. + + 25. Select an option for assigning SLA Domains. + * Select Use the same post-failover SLA domains for all objects to use the same SLA Domains for all objects and then select a single SLA Domain. + * Specify an SLA Domain for each virtual machine. These SLA Domains protect the virtual machines after a failover operation. To failback to the original site, select SLA Domains that have the current source cluster as their replication target cluster. + 26. Click Next. + +The Confirm Recovery Plan details page appears. + + 27. Review the Recovery Plan details and click Create. + +## Results + +RSC creates the Recovery Plan and provides options to Recover Now, Schedule Recovery Plan Tests, or Create Another Plan. + +When you click any of these options, RSC displays the appropriate wizard. + *[ > ]: and then diff --git a/saas_creating_in_place_rp.md b/saas_creating_in_place_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..8fb8ac86a8d073d05a1bf2cada7b961b334f9d1f --- /dev/null +++ b/saas_creating_in_place_rp.md @@ -0,0 +1,54 @@ +# Creating an in-place Recovery Plan + +Source: https://docs.rubrik.com/en-us/saas/saas/creating_in_place_rp.html + +--- + +Recovery Plan# Creating an in-place Recovery Plan + +Create an in-place Recovery Plan to protect a set of virtual machines and enable recovery on the same Rubrik cluster where the source virtual machine is being protected. + +## About this task + +Orchestrated Recovery supports creating an in-place Recovery Plan for only vSphere virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plan page appears, listing all Recovery Plans. + + 4. Click Create and then select In-place Recovery Plan. + +The Create Recovery Plan wizard appears. + + 5. In Name, enter a name for the Recovery Plan. + 6. In Recover from, select a Rubrik cluster. + +All virtual machines in the Recovery Plan have a snapshot on the selected Rubrik cluster. + + 7. Click Next. + +The wizard lists the virtual machines on the source Rubrik cluster. + + 8. Select the virtual machines to recover and click Next. + 9. Set the boot order for recovery by assigning virtual machines to a priority group. + 10. **Optional:** In Post scripts, specify the path to scripts that run on the virtual machines after instantiation. + +Using post-instantiation scripts affects the Recovery Time Objective (RTO) metric by requiring high-level services to be available as a prerequisite for boot order instantiation. + + 11. Click Next. + +The Review Recovery Plan details step appears. + + 12. Review the Recovery Plan details and click Create. + +## Results + +RSC creates the Recovery Plan and provides the option to Create Another Plan. + *[ > ]: and then diff --git a/saas_creating_ncd_protection_report.md b/saas_creating_ncd_protection_report.md new file mode 100644 index 0000000000000000000000000000000000000000..c128f9637438a331853963ca9d1847625fc9b0ed --- /dev/null +++ b/saas_creating_ncd_protection_report.md @@ -0,0 +1,55 @@ +# Creating a NAS CD protection report + +Source: https://docs.rubrik.com/en-us/saas/saas/creating_ncd_protection_report.html + +--- + +# Creating a NAS CD protection report + +In RSC, create a report using the Protection report template to summarize the details about the protection status of NAS CD objects. + +## Procedure + + 1. Log in to RSC. + 2. On the navigation bar, click Reports. + +The Reports page appears. + + 3. Click Create Report, and select Protection. + +The Protection Report template appears. + + 4. Click Object Type filter, and select NAS Cloud Direct. + +The Protection Report page displays a table with details of all Rubrik NAS Cloud Direct objects. + + 5. In the Protection table, click . + +You can add, remove, pin, or reorder columns in the Protection table. + +A list of column headers appears. + + 6. Select columns to include in the report. + +Select the following columns: + * Object + * Object Type + * Last Updated + * Protection Status + * Latest Local Snapshot + * NCD Policy + * Source Protocol + * Latest Archive Snapshot + * NCD Site + + 7. Click outside the column headers list. + +The list closes. + + 8. Click Protection Report, and edit the name of the report. + 9. Click Create. + +## Results + +RSC displays the new protection report for the NAS CD objects with the details corresponding to the selected columns. + *[ > ]: and then diff --git a/saas_custom_intel_feed.md b/saas_custom_intel_feed.md new file mode 100644 index 0000000000000000000000000000000000000000..9510932a572baf682531492c628423103d00311e --- /dev/null +++ b/saas_custom_intel_feed.md @@ -0,0 +1,20 @@ +# Custom intel feed + +Source: https://docs.rubrik.com/en-us/saas/saas/custom_intel_feed.html + +--- + +# Custom intel feed + +To monitor data for specific threats, you can create a custom feed of indicators of compromise. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +The Rubrik Threat Monitoring feature proactively scans for threats based on vetted threat intelligence from multiple sources. Threat Monitoring can also scan using a custom intel feed that you create. You can create up to seven custom feeds. Each custom feed can contain up to 10 indicators of compromise (IOCs). + +The IOCs in your custom intel feed can be any combination of YARA rules and file hashes.Threat Monitoring checks for file hashes immediately after you add them, and checks for added YARA rules after the next snapshot is taken. + +The Intel Feed page in Data Threat Analytics displays the configured intel feed cards with details including the users who added the intel feeds, the total number of IOCs that the users added to the feeds, and the date the intel feeds were added. + +The Rubrik cluster must be running Rubrik CDM 9.1.3-p2 or later, or if using Rubrik CDM 9.2, the Rubrik cluster must be running Rubrik CDM 9.2.0-p3 or later to enable the Threat Monitoring feature. + *[ > ]: and then diff --git a/saas_customer_support.md b/saas_customer_support.md new file mode 100644 index 0000000000000000000000000000000000000000..ddc7e20797f4b8b919f89841664c0eea167bf143 --- /dev/null +++ b/saas_customer_support.md @@ -0,0 +1,25 @@ +# Customer Support for RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/customer_support.html + +--- + +# Customer Support for RSC + +You can grant support access and open and close a support tunnel in the Customer Support menu. The support access feature enables Rubrik Support to access your RSC domain securely in read-only mode. Rubrik Support uses the support tunnel to examine the health of the Rubrik cluster and to troubleshoot and resolve issues. You can also run network diagnostics from the Customer Support menu. + +From the Customer Support menu, you can: + + * Enable support access for an RSC user account. + +The support access feature enables Rubrik Support to access your Rubrik Security Cloud (RSC) domain securely, in read-only mode. If you have an issue with your RSC account, you can create a Rubrik Support case. Rubrik Support uses the support access feature to understand the complete context of the issue with your RSC account and resolve them. + + * Open or close a support tunnel. + +Each Rubrik cluster provides a built-in support tunnel utility. RSC provides a unified interface to open or close a support tunnel on any Rubrik cluster. + +Rubrik Support uses the support tunnel to access the Rubrik cluster to address many issues effectively, such as service-down, operating system, database, and configuration problems. This capability allows the support team to reduce significantly the time and effort required to resolve these issues, eliminating the need for lengthy screen-sharing sessions or phone calls. + + * Run network diagnostics to check your network status and troubleshoot issues in RSC. + + *[ > ]: and then diff --git a/saas_customizing_date_and_time_settings.md b/saas_customizing_date_and_time_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..5d47f8ce8016ad3283889625c304c8b6789d8386 --- /dev/null +++ b/saas_customizing_date_and_time_settings.md @@ -0,0 +1,27 @@ +# Customizing date and time settings + +Source: https://docs.rubrik.com/en-us/saas/saas/customizing_date_and_time_settings.html + +--- + +# Customizing date and time settings + +Customize date and time settings based on your preferences, location, and specific requirements. + +## Procedure + + 1. Log in to RSC. + 2. Open the user account menu and select User Preferences. + +The User Preferences page appears. + + 3. Click Date and Time. + 4. In Time zone, select Set time zone. + 5. In Time zone for cluster events, select Use the local time zone of the Rubrik cluster location. + 6. In Date format, select Set date format. + 7. In Time format, select Set time format. + +## Results + +RSC modifies the date and time settings based on your preferences. + *[ > ]: and then diff --git a/saas_cyber_event_lockdown.md b/saas_cyber_event_lockdown.md new file mode 100644 index 0000000000000000000000000000000000000000..32e4036fe9d0d5188335dc72c42127b455897a11 --- /dev/null +++ b/saas_cyber_event_lockdown.md @@ -0,0 +1,18 @@ +# Cyber Event Lockdown + +Source: https://docs.rubrik.com/en-us/saas/saas/cyber_event_lockdown.html + +--- + +# Cyber Event Lockdown + +When a suspected cyber attack, ransomware attack, or other event affecting data integrity impacts your environment, you can use Cyber Event Lockdown to protect the data on your Rubrik clusters. + +When you enable the Cyber Event Lockdown mode, you temporarily override SLA Domain retention expiration operations for current and future snapshots to preserve all cluster data. Because the cluster does not delete data in this mode, the Cyber Event Lockdown automatically runs a cluster capacity precheck determining whether lockdown is safe to use at that time. If the cluster capacity is insufficient, the lockdown instructs you to contact Rubrik Support for further assistance. + +The Cyber Event Lockdown generates a message, identifying the user who triggered the lockdown. You can view this activity in the activity log. When the Rubrik cluster is connected to Rubrik Security Cloud, enabling Cyber Event Lockdown automatically creates a support ticket to save all current and future cluster snapshots. + +Note: + +To reinstate a cluster in lockdown mode to normal operations, you will need to contact Rubrik Support. + *[ > ]: and then diff --git a/saas_data_discovery_class.md b/saas_data_discovery_class.md new file mode 100644 index 0000000000000000000000000000000000000000..df44b748002d57ddbbe29909f49bb9d00cb1466f --- /dev/null +++ b/saas_data_discovery_class.md @@ -0,0 +1,57 @@ +# Data Discovery and Classification + +Source: https://docs.rubrik.com/en-us/saas/saas/data_discovery_class.html + +--- + +# Data Discovery and Classification + +The Data Discovery and Classification feature in Data Security Posture discovers sensitive information in structured and unstructured data that is subject to regulation. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +You can use Data Discovery and Classification to find all data from an enterprise that matches a specified data classification rule. You can support current and future data privacy regulations by using preconfigured policies or creating custom policies to stay compliant. Data Discovery and Classification scans snapshots or the live environment without affecting production systems. Access to Data Discovery and Classification tasks depends on the level of permission granted. + +Data Discovery and Classification scans up to 50 MB of every file. + +## Data classification workflow + +The Data Discovery and Classification workflow involves: + + * Assigning data categories to workloads protected by SLA Domains for on-premise and M365 objects. + * Viewing classification results on the dashboards and on the object inventory. + +## Supported workloads for on-premise and Rubrik clusters + +Data Discovery and Classification supports the following workloads protected by SLA Domains on Rubrik clusters running Rubrik CDM version 8.0 or later: + + * VMware, AHV, vSphere, and Hyper-V virtual machines + * NAS filesets (excluding NAS Direct Archive) + * Linux and Windows filesets + * Windows Volumes groups + * Microsoft SQL Server databases + +Enabling Data Discovery and Classification for Microsoft SQL Server databases has specific requirements. + + * Microsoft 365 SharePoint and OneDrive + * Azure virtual machines and managed disks + * NAS CD data sets + * AWS EC2 instances and EBS volumes + * Google Cloud Platform (GCP) virtual machines + +## Supported workloads for auto scanning + +Data Discovery and Classification supports auto scanning of the following workloads: + + * Amazon Simple Storage (Amazon S3) resources, AWS EC2 instances and Elastic Block Store (EBS) volumes, Amazon Relational Database Service (RDS), and Aurora databases + * Microsoft Azure blob storage, Azure SQL Databases and SQL Managed Instances, and Azure virtual machines and managed disks + +## Azure virtual machines and managed disks specifications + +The following specifications apply for customers using Data Discovery and Classification for Azure virtual machines and managed disks: + + * Sensitive Data Discovery and Classification scans are performed on samples of the live production data rather than the entire workload. + * Existing customers who have onboarded one subscription can decide to transition all of their subscriptions to sampled scanning. Alternatively, existing users who have onboarded one subscription can decide to transition a subset of their subscriptions to sampled scanning. In this case, the remaining subscriptions will have the scanning turned off, until those subscriptions are transitioned. + * After transitioning to sampled scanning, the customer cannot opt to go back to RSC scanning the entire workload for Data Discovery and Classification. + + *[ > ]: and then diff --git a/saas_data_discovery_class_microsoft_365.md b/saas_data_discovery_class_microsoft_365.md new file mode 100644 index 0000000000000000000000000000000000000000..fc703fafa271efa08008cc562c16241d0aad9ade --- /dev/null +++ b/saas_data_discovery_class_microsoft_365.md @@ -0,0 +1,24 @@ +# Data Discovery and Classification for Microsoft 365 + +Source: https://docs.rubrik.com/en-us/saas/saas/data_discovery_class_microsoft_365.html + +--- + +# Data Discovery and Classification for Microsoft 365 + +The classification performed by Data Discovery and Classification for Microsoft 365 identifies sensitive data that matches a specified policy within backups. + +Data Discovery and Classification for Microsoft 365 supports these workloads: + + * SharePoint + * OneDrive + * Exchange Online + +Data Discovery and Classification for Microsoft 365 Exchange Online supports emails, attachments, and shared mailboxes. + +To enable Data Security Posture for Microsoft 365 objects, you must assign policies in Data Security Posture to discover sensitive data that matches a specified data policy within snapshots. You can also create custom data categories and data types based on your requirements and assign these to the objects you are interested in reviewing. + +After you enable the data category, Data Security Posture performs a full analysis and the sensitive data classification is available in the object details page in Data Security Posture. + +You can configure Data Security Posture for up to 50,000 Microsoft 365 objects in RSC. + *[ > ]: and then diff --git a/saas_data_discovery_class_oracle_db_req.md b/saas_data_discovery_class_oracle_db_req.md new file mode 100644 index 0000000000000000000000000000000000000000..bd9efa1376637c71080e7b5419e73d7dfc9c0833 --- /dev/null +++ b/saas_data_discovery_class_oracle_db_req.md @@ -0,0 +1,23 @@ +# Oracle database requirements + +Source: https://docs.rubrik.com/en-us/saas/saas/data_discovery_class_oracle_db_req.html + +--- + +# Oracle database requirements + +Enabling Data Discovery and Classification for Oracle databases has specific requirements. + +Requirement | Description +---|--- +Rubrik cluster software | Your Rubrik cluster must be running Rubrik CDM version 9.3.1 or later. +License | You must have the Rubrik Enterprise Edition or Rubrik Enterprise Proactive Edition enabled for your RSC domain. +Feature enablement | You are required to enable Data Discovery and Classification for your RSC domain by contacting Rubrik Support. +User permissions | You must assign specific permissions to a user account. + * Required permissions: You must assign the necessary read and query permissions to a user on the Oracle database. + * User information provision: You must provide the information associated with this user as input when registering a host or updating an existing host. + * Single user for each host: RSC supports the use of only one user for a given host as user details are provided during host registration. + * Privileges for multiple databases: If a host contains multiple databases that require classification, the same user account must have privileges for all these databases. +TCP port 2484 access | You are required to configure TCP internet protocol with SSL/TLS (TCPS) on port 2484 on the listener settings on the Oracle databases that need to be classified.If you want to change the port setting, contact Rubrik Support. +Secure wallet | You are required to configure a secure wallet on the Oracle host. This secure wallet is used for host authentication during the communication with the host. The certificates for the user provided during the host registration must be available in this wallet file. During the classification jobs, Rubrik automatically pulls this wallet file into the Rubrik cluster and deletes these files after the classification is complete. Rubrik takes the wallet path on the Oracle host as input during host registration along with the Data Discovery and Classification credentials. + *[ > ]: and then diff --git a/saas_data_discovery_class_oracle_dbs.md b/saas_data_discovery_class_oracle_dbs.md new file mode 100644 index 0000000000000000000000000000000000000000..c3d370c9f59310b7ac4e934384ce645e190f7095 --- /dev/null +++ b/saas_data_discovery_class_oracle_dbs.md @@ -0,0 +1,19 @@ +# Data Discovery and Classification for Oracle databases + +Source: https://docs.rubrik.com/en-us/saas/saas/data_discovery_class_oracle_dbs.html + +--- + +# Data Discovery and Classification for Oracle databases + +The classification mechanism for Oracle databases has specific processes and requirements compared to file system classification for other supported workloads. + +After enabling Data Discovery and Classification for your RSC RSC domain, you can assign policies to an Oracle database in Data Security Posture. After the database backup job completes,Data Discovery and Classification queries the production database to read a sample list of rows from each table and classifies the data in those rows. Data Discovery and Classification then extrapolates the classification results based on the total number of rows in the table. + +## Limitations for Data Discovery and Classification for Oracle databases + +The following are the limitations for Data Discovery and Classification for Oracle databases: + * Data Discovery and Classification for tables belonging to pluggable databases in a container database is not supported. + * The Data Discovery and Classification user credentials are applicable for all the tables belonging to all the databases running on a given Oracle host as the credentials are at a physical host level. + * Data Discovery and Classification is not supported for Oracle databases deployed on virtual machines running Windows OS. + *[ > ]: and then diff --git a/saas_data_discovery_class_sql_server_dbs.md b/saas_data_discovery_class_sql_server_dbs.md new file mode 100644 index 0000000000000000000000000000000000000000..fa1973df7e5a892d9ebc54787e7b9aaa4f688842 --- /dev/null +++ b/saas_data_discovery_class_sql_server_dbs.md @@ -0,0 +1,15 @@ +# Data Discovery and Classification for MS SQL Server databases + +Source: https://docs.rubrik.com/en-us/saas/saas/data_discovery_class_sql_server_dbs.html + +--- + +# Data Discovery and Classification for MS SQL Server databases + +The classification performed by Data Discovery and Classification for Microsoft SQL Server databases differs from the file system classification for other supported workloads. + +The Rubrik cluster provides data management and protection only for Microsoft SQL Server databases. Data Discovery and Classification for SQL Server databases is different from file system classification in the following aspects: + + * For SQL Server databases, Data Discovery and Classification queries the production database after the database backup job that reads a sample list of rows from each table, classifies the data in those rows, and then extrapolates the classification results based on the total number of rows in the table. In comparison, Data Discovery and Classification for filesets mounts the snapshot and reads all the data from the mounted snapshot to perform the classification. + * For SQL Server databases, Data Discovery and Classification triggers the classification job at the end of every database backup job. Each classification job scans all the tables in the database to perform the classification. You can view the classification jobs in the Events tab for the database. + *[ > ]: and then diff --git a/saas_data_management_permissions.md b/saas_data_management_permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..cd47f1f37fdce5896ae7f471c30acdfa18aa9a92 --- /dev/null +++ b/saas_data_management_permissions.md @@ -0,0 +1,62 @@ +# Data management permissions + +Source: https://docs.rubrik.com/en-us/saas/saas/data_management_permissions.html + +--- + +# Data management permissions + +Details of data management permissions that are available for assignment to different roles in RSC. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Permission category | Description | Impact +---|---|--- +Protectable objects | For selected object types, permissions apply to one of the following: + + * All existing and future protectable objects of the chosen object type + * Specific protectable objects + +| RSC applies the data management privileges to the selected objects. +Recovery targets | For selected object types, permissions apply to one of the following: + + * All existing and future recovery objects of the chosen object type + * Specific recovery objects + +| You can use the selected objects as recovery targets.You can recover to only the target locations (the Microsoft 365 subscriptions) that you have access to, as defined by the RSC role assigned to you by the RSC administrator.If the administrator does not specify a recovery target during role creation, you cannot recover to any target location. +Data management privileges: View | For the selected object types, this allows the following actions: + + * View protectable objects + * Refresh data sources + +| RSC applies the data management privileges to the selected objects. +Data management privileges: Protection | For selected object types, this allows the following privileges: + + * ViewThis includes the privilege to view the selected objects and refresh data sources. + * ProtectionThis includes the privilege to manage protection, take on-demand snapshots, and delete snapshots. + * RecoveryThis includes the privilege to export files, export snapshots, download files, and to restore objects. + * Data source managementThis includes the privilege to add and delete resources that contain protectable objects and recovery targets, such as physical hosts. + +| RSC applies the data management privileges to the selected objects. +Data management privileges: Recovery | For selected object types, this allows the following actions : + + * Download from data center and archival location + * Mount snapshot + * Manage Log Shipping + * Export files + * Export snapshots + * Download files + * Restore over original + * Download from replication target + +| RSC applies the data management privileges to the selected objects. The Manage Log Shipping action is only available for the SQL Server database object type. +Data management privileges: Data source management | For selected object types, this allows adding and deleting resources that contain protectable objects and recovery targets, such as physical hosts. | RSC applies the data management privileges to the selected objects. +Datacenter archival locations | For selected object types, this allows view permissions for archival locations. | RSC applies the data management privileges to the selected objects. +SLA Domains | Applies to one of the following: + + * All existing and future SLA Domains + * Specific SLA Domains + +| You can view, assign, and manage the selected SLA Domains. +SLA Domains: Self-Service | Applies to Self-Service permissions for SLA Domain creation and management. | You can create and manage SLA Domains. + *[ > ]: and then diff --git a/saas_data_observability_sharepoint_onedrive.md b/saas_data_observability_sharepoint_onedrive.md new file mode 100644 index 0000000000000000000000000000000000000000..5ea60f389ec3306a26726497586337b2fc85f5cd --- /dev/null +++ b/saas_data_observability_sharepoint_onedrive.md @@ -0,0 +1,26 @@ +# Data Observability for Microsoft Sharepoint and OneDrive + +Source: https://docs.rubrik.com/en-us/saas/saas/data_observability_sharepoint_onedrive.html + +--- + +# Data Observability for Microsoft Sharepoint and OneDrive + +To provide Data Observability, you can enable Anomaly Detection and Threat Monitoring to detect ransomware attacks and configure Data Security Posture to identify sensitive data in backups of Microsoft OneDrive and Sharepoint objects. + +Data Observability for Microsoft Sharepoint and OneDrive has two components: + + * Configuring Anomaly Detection and Threat Monitoring to detect and investigate ransomware attacks. + +Anomaly Detection monitors for anomalous file system changes to detect and automate recovery from encryption or mass deletion events. Threat Monitoring processes threat intelligence against backup data to identify malware infections. + + * Configuring Data Security Posture to discover types of sensitive data in your OneDrive and SharePoint objects. + +Data Security Posture searches indexed snapshots for specific types of sensitive data that must be secured. + +Enabling Anomaly Detection in RSC requires an initial backup of the OneDrive and SharePoint objects. Confirm that the objects have an assigned SLA Domain and that Anomaly Detection is enabled for the specific Microsoft 365 subscription. You can configure Anomaly Detection for up to a total of 50,000 OneDrive and SharePoint objects in RSC. RSC identifies anomalies for OneDrive and SharePoint objects that have an initial backup with Anomaly Detection enabled at the subscription level. + +You can enable Threat Monitoring for up to 1 TB of Microsoft SharePoint and OneDrive objects. RSC scans up to 50,000 files per minute to provide Threat Monitoring insights. + +You can also configure Data Security Posture for up to a total of 50,000 OneDrive and SharePoint objects in RSC. + *[ > ]: and then diff --git a/saas_data_observability_sharepoint_onedrive_2.md b/saas_data_observability_sharepoint_onedrive_2.md new file mode 100644 index 0000000000000000000000000000000000000000..e5b1aa88d7eec42c149d991eb82102bc6f6a2732 --- /dev/null +++ b/saas_data_observability_sharepoint_onedrive_2.md @@ -0,0 +1,25 @@ +# Data Observability for Microsoft Sharepoint and OneDrive + +Source: https://docs.rubrik.com/en-us/saas/saas/data_observability_sharepoint_onedrive_2.html + +--- + +# Data Observability for Microsoft Sharepoint and OneDrive + +To provide Data Observability, you can enable Anomaly Detection and Threat Monitoring to detect ransomware attacks and configure Data Security Posture to identify sensitive data in backups of Microsoft OneDrive and Sharepoint objects. + +Data Observability for Microsoft Sharepoint and OneDrive has two components: + * Configuring Anomaly Detection and Threat Monitoring to detect and investigate ransomware attacks. + +Anomaly Detection monitors for anomalous file system changes to detect and automate recovery from encryption or mass deletion events. Threat Monitoring processes threat intelligence against backup data to identify malware infections. + + * Configuring Data Security Posture to discover types of sensitive data in your OneDrive and SharePoint objects. + +Data Security Posture searches indexed snapshots for specific types of sensitive data that must be secured. + +Enabling Anomaly Detection in RSC requires an initial backup of the OneDrive and SharePoint objects. Confirm that the objects have an assigned SLA Domain and that Anomaly Detection is enabled for the specific Microsoft 365 subscription. You can configure Anomaly Detection for up to a total of 50,000 OneDrive and SharePoint objects in RSC. RSC identifies anomalies for OneDrive and SharePoint objects that have an initial backup with Anomaly Detection enabled at the subscription level. + +You can enable Threat Monitoring for up to 1 TB of Microsoft SharePoint and OneDrive objects. RSC scans up to 50,000 files per minute to provide Threat Monitoring insights. + +You can also configure Data Security Posture for up to a total of 50,000 OneDrive and SharePoint objects in RSC. + *[ > ]: and then diff --git a/saas_data_protection_dashboard.md b/saas_data_protection_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..525e61ee6d4b89244e9f3e8eec6a5d4a79018ac3 --- /dev/null +++ b/saas_data_protection_dashboard.md @@ -0,0 +1,18 @@ +# Data Protection dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/data_protection_dashboard.html + +--- + +# Data Protection dashboard + +The Data Protection dashboard provides information about the current state of the Rubrik clusters connected to RSC. + +The Dashboard drop-down list helps users navigate to the Data Protection and Microsoft 365 dashboards. The Data Protection dashboard is an aggregated view of all events and compliance across all Rubrik clusters in their respective regions. The Data Protection dashboard provides aggregated Events, Compliance Overview, Protection Overview, and a global map information for all connected Rubrik clusters associated with the authenticated user. The Microsoft 365 dashboard provides a unified view of the backup events and compliance across the data sources within a Microsoft 365 subscription connected to RSC. + +The Data Protection dashboard can use dynamic filters. + +The Data Protection dashboard shows all setup events aggregated during a configurable time range. + +RSC regularly refreshes the information that appears in the Data Protection dashboard. RSC refreshes SLA Domain information every 15 minutes. + *[ > ]: and then diff --git a/saas_data_security_posture_aws.md b/saas_data_security_posture_aws.md new file mode 100644 index 0000000000000000000000000000000000000000..144c79c43ef472efdc574c9acff5dac9bb8fb459 --- /dev/null +++ b/saas_data_security_posture_aws.md @@ -0,0 +1,25 @@ +# Data Security Posture for AWS + +Source: https://docs.rubrik.com/en-us/saas/saas/data_security_posture_aws.html + +--- + +# Data Security Posture for AWS + +Using Data Security Posture, you can scan your AWS environment to classify sensitive data, monitor for threats, and manage your data security risks. + +Using Data Security Posture, you can view information about data in your AWS account. Data Security Posture on your AWS account provides a global, unified view of the data in your environment, access activity, and whether it contains personally identifiable information or financial records. + +Enabling Data Security Posture on your AWS account is fast and easy, with flexible deployment options. Data never leaves your environment, thus ensuring data security. Enabling Data Security Posture for an AWS account requires turning on Data Security Posture and configuring an outpost account by providing the 12-digit outpost account ID. + +The AWS account is the account that contains the AWS workloads with Data Security Posture enabled. The outpost account is the account that accesses the AWS account to perform sensitivity scans and generate metadata for data classification and sensitivity. RSC connects to the outpost account and collects the metadata to generate the insights. This ensures that the data remains within the AWS environment. After you have enabled Data Security Posture, RSC automatically discovers and scans your AWS environment to generate classification and security posture insights. + +Note: + +An outpost account can be the same as the AWS account. You can choose which AWS account to configure as the outpost account. You can, however, configure only one outpost account in RSC. After you configure the outpost account, all future AWS accounts added in RSC for Data Security Posture use the same outpost account. + +You can enable Data Security Posture for the following: + + * A new AWS cloud account you are adding to RSC + * An existing active AWS cloud account you have already added to RSC + *[ > ]: and then diff --git a/saas_data_security_posture_for_azure.md b/saas_data_security_posture_for_azure.md new file mode 100644 index 0000000000000000000000000000000000000000..d10b4590c22128fbef7349efd279c642220d3ac6 --- /dev/null +++ b/saas_data_security_posture_for_azure.md @@ -0,0 +1,20 @@ +# Data Security Posture for Azure + +Source: https://docs.rubrik.com/en-us/saas/saas/data_security_posture_for_azure.html + +--- + +# Data Security Posture for Azure + +Using Data Security Posture, you can scan your Azure environment to classify sensitive data, monitor for threats, and manage your data risks. + +Using Data Security Posture, you can view information about data in your Azure account. Data Security Posture on your Azure account provides a global, unified view of the data in your environment, access activity, and whether it contains personally identifiable information or financial records. Data Security Posture in RSC provides an in-depth view of the protection status of Azure data and identifies any sensitive information in your Azure environment that you might want to safeguard. You can also minimize unnecessary storage cost by backing up only the sensitive data. + +Data Security Posture autonomously and continuously discovers assets and data across your cloud environment. Data Security Posture carries out data discovery seamlessly, without agents or the need for configuration or credentials. Data Security Posture uses Azure APIs to check whether Azure objects are protected by native backup tools. This information is then combined with the existing data in RSC, providing a clear picture of the protection status of your data. RSC then uses an Azure outpost account of the user to discover and perform data classification scans, ensuring that no data leaves your cloud environment. + +You can enable Data Security Posture for the following: + * A new Azure cloud account you are adding to RSC using the Configure with OAuth option + * An existing active Azure cloud account you have already added to RSC + +RSC requires a native snapshot for scanning SQL Server databases and Azure managed instances. + *[ > ]: and then diff --git a/saas_data_sources.md b/saas_data_sources.md new file mode 100644 index 0000000000000000000000000000000000000000..27e278dbf0e41e61892f10f75bb87a30a835c889 --- /dev/null +++ b/saas_data_sources.md @@ -0,0 +1,16 @@ +# Data Sources + +Source: https://docs.rubrik.com/en-us/saas/saas/data_sources.html + +--- + +# Data Sources + +You can add hosts, instances, and servers for various data-center workloads in the Data Sources menu. Additionally, you can configure access credentials by setting up Guest OS settings and SMB security. + +Protecting your data-center workloads requires adding them to RSC. Once added, the workloads are viewable on the Inventory page. RSC provides an array of features for protecting workloads. The most useful of these features is the SLA Domain, where you set the frequency of taking snapshots and use those snapshots to recover workloads. + +Getting started involves navigating to the Data Sources menu and adding hosts, instances, and servers for different data-center workloads, such as vCenter servers, SCVMM servers, Nutanix, Linux and Unix, Windows, NAS systems, and Storage arrays to RSC. + +Configuring Guest OS settings and SMB security makes it possible to set up access credentials. With the SMB security feature, a Rubrik cluster provides security for SMB shares by requiring Active Directory authentication and enforcing SMB security. The Guest OS Settings page enables the administration of guest OS credentials for virtual machines. + *[ > ]: and then diff --git a/saas_date_and_time_customization.md b/saas_date_and_time_customization.md new file mode 100644 index 0000000000000000000000000000000000000000..a4893e779760f3e6b8a0a68fee0ef1f1027a3bcd --- /dev/null +++ b/saas_date_and_time_customization.md @@ -0,0 +1,11 @@ +# Date and time customization + +Source: https://docs.rubrik.com/en-us/saas/saas/date_and_time_customization.html + +--- + +# Date and time customization + +Date and time is a setting under User Preferences that allows you to customize the date and time settings based on your preferences. + +The default time zone is determined by your browser settings, which typically align with the time zone of your current location. You can customize the time zone according to your preferences or location. You can choose to display the date and time in various formats. You can select the time zone, date format, and time format to display the date and time based on the time zone of the specific region, your preferences, and your specific requirements. These settings apply across the entire system, ensuring consistent date and time display throughout. diff --git a/saas_date_and_time_settings.md b/saas_date_and_time_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..61cc338439c7aaed62ae95a29af5b722a41af711 --- /dev/null +++ b/saas_date_and_time_settings.md @@ -0,0 +1,21 @@ +# Date and time settings + +Source: https://docs.rubrik.com/en-us/saas/saas/date_and_time_settings.html + +--- + +# Date and time settings + +You can use the date, time, and time zone settings to select options for time zone, date format, and time format. + +Setting | Option | Description +---|---|--- +Time zone | Use my computer's time zone | Allows you to use the same time zone as your computer for displaying and recording cluster events. +Set time zone | Allows you to manually set the time zone for all timestamps, including cluster events, unless the Time zone for cluster events option is set to Use the local time zone of the Rubrik cluster location. +Time zone for cluster events | Use selected timezone | Allows you to set the time zone for the cluster events and snapshot times based on the time zone selected in the Time zone option. +Use the local time zone of the Rubrik cluster location | Allows you to use the local time zone of the Rubrik cluster location for displaying and recording cluster events. +Date format | Auto | Allows you to automatically set the date format based on the language and regional settings of your computer. +Set date format | Allows you to select the date format for displaying the dates. +Time format | Auto | Allows you to automatically set the time format based on the language and regional settings of your computer. +Set time format | Allows you to select the time format for displaying the times. You can choose between 12-hour or 24-hour time format. + *[ > ]: and then diff --git a/saas_default_sla_domains.md b/saas_default_sla_domains.md new file mode 100644 index 0000000000000000000000000000000000000000..0cd1aeedb0e0894ac208a25c13adcdf9ceb6b483 --- /dev/null +++ b/saas_default_sla_domains.md @@ -0,0 +1,26 @@ +# Default SLA Domains + +Source: https://docs.rubrik.com/en-us/saas/saas/default_sla_domains.html + +--- + +# Default SLA Domains + +RSC provides preconfigured SLA Domains. + +Name | Hourly | Daily | Monthly | Yearly +---|---|---|---|--- +Gold | + + * Create snapshot every 4 hours + * Retain for 3 days + +| Pick the last successful snapshot every day and retain it for 32 days | Pick last successful snapshot every month and retain it for 1 year | Pick last successful snapshot every year and retain it for 2 years +Silver | + + * Create snapshot every 12 hours + * Retain for 3 days + +| Pick the last successful snapshot every day and retain it for 32 days | Pick last successful snapshot every month and retain it for 1 year | Pick last successful snapshot every year and retain it for 2 years +Bronze | None | Create snapshot every day and retain it for 32 days | Pick last successful snapshot every month and retain it for 1 year | Pick last successful snapshot every year and retain it for 2 years + *[ > ]: and then diff --git a/saas_deleting_guest_os_credentials.md b/saas_deleting_guest_os_credentials.md new file mode 100644 index 0000000000000000000000000000000000000000..c581e926af410d2423578bf12000929f379f9d57 --- /dev/null +++ b/saas_deleting_guest_os_credentials.md @@ -0,0 +1,40 @@ +# Deleting guest OS credentials + +Source: https://docs.rubrik.com/en-us/saas/saas/deleting_guest_os_credentials.html + +--- + +# Deleting guest OS credentials + +Delete guest OS credentials from the list of credentials that RSC uses to access virtual machines. + +## Before you begin + +To delete a guest OS credential, use an RSC user account that is assigned the administrator role and the Manage guest OS credentials permission. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC using the administrator account. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Source > Access Credentials. + +The Access Credentials page appears. + + 4. Click Guest OS Settings tab. + 5. Open the ellipsis menu for a Guest OS credential and select Delete. + +A confirmation message appears. + + 6. Click Delete. + +## Results + +RSC deletes the selected guest OS credential. + *[ > ]: and then diff --git a/saas_deleting_rp.md b/saas_deleting_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..e9e1203536d86d2770c0f8496df6c06c75cbfa7a --- /dev/null +++ b/saas_deleting_rp.md @@ -0,0 +1,41 @@ +# Deleting a Recovery Plan + +Source: https://docs.rubrik.com/en-us/saas/saas/deleting_rp.html + +--- + +# Deleting a Recovery Plan + +You can delete an Azure, AHV, or vSphere Recovery Plan from the Recovery Plan details page. + +## About this task + +You cannot delete a Recovery Plan while recovery is in progress. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears, listing all Recovery Plans. + +You can access vSphere virtual machines, AHV virtual machines, Azure virtual machines, and AWS virtual machines in the respective tabs. + + 4. Select a Recovery Plan from the list. + +The Recovery Plan details page appears. + + 5. Click and select Delete Recovery Plan . + +The Delete Recovery Plan confirmation dialog box appears. + + 6. Click Delete. + +## Results + +RSC removes the Azure, AHV, or vSphere Recovery Plan. + *[ > ]: and then diff --git a/saas_deleting_sso_user_account_rsc.md b/saas_deleting_sso_user_account_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..d57c5abb372064ce93fba3dc31fdb2bdff9b0bca --- /dev/null +++ b/saas_deleting_sso_user_account_rsc.md @@ -0,0 +1,36 @@ +# Deleting an SSO user account from RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/deleting_sso_user_account_rsc.html + +--- + +# Deleting an SSO user account from RSC + +Delete SSO user accounts from RSC after deleting them from the SSO identity provider to prevent unauthorized access. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Users & Access and select Users. + +The Users page appears. + + 4. Click SSO. + 5. Select an SSO user account from the list. + +You can select multiple SSO user accounts. + + 6. Click and select Delete User Accounts. + +A confirmation prompt appears. + + 7. Click Delete. + +## Results + +RSC deletes the selected SSO user accounts and creates an entry in the Audit Logs page listing the deleted accounts and the user accounts that deleted them. + *[ > ]: and then diff --git a/saas_disaster_rp_information.md b/saas_disaster_rp_information.md new file mode 100644 index 0000000000000000000000000000000000000000..4c132cd02e026e0428cfbafc76903d53d6652585 --- /dev/null +++ b/saas_disaster_rp_information.md @@ -0,0 +1,269 @@ +# Disaster Recovery Plan information + +Source: https://docs.rubrik.com/en-us/saas/saas/disaster_rp_information.html + +--- + +# Creating a disaster Recovery Plan for vSphere virtual machines + +Create a disaster Recovery Plan to enable failover testing and production failover orchestration for a set of virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. In the vSphere tab, click **Recovery Plans**. + +The Recovery Plans page appears, listing all Recovery Plans + + 4. Click Create and then select Disaster Recovery Plan. + +The Create Recovery Plan wizard appears. + + 5. In Name, enter a name for the Recovery Plan. + 6. In Recover From, select a Rubrik cluster from the dropdown list. + +All virtual machines in the Recovery Plan must have a snapshot on the selected Rubrik cluster. + + 7. In Recover To, select a Rubrik cluster. + +During a failover operation, RSC creates virtual machines on the target hypervisor resources. + + 8. Click Next. + +The Select vSphere virtual machines page appears. + + 9. Select the virtual machines to recover and click Next. + +The Set the boot order of virtual machines page appears. + + 10. Select a priority group for each virtual machine and click Next. + +The Select compute resource page appears. + + 11. Select an option for failover target selection and click Next. + +Choice| Effect +---|--- +Choose a vSphere compute cluster, host, or resource pool for your Recovery Plan(All virtual machines). | Enables selecting a failover target from a list. All virtual machines in the Recovery Plan use the selected target during a failover operation. +Choose a vSphere compute cluster, host, or resource pool for each virtual machine in your Recovery Plan. | Enables selecting a specific failover target for each virtual machine in the Recovery Plan. The Targets column displays a list of target choices. + +Compute clusters that do not have hosts or resource pools are not available for selection. + + 12. In Targets, click a target name to select a failover target for each virtual machine. + +The Select a target for compute resources window appears. + + 13. Select the target and click Save for each virtual machine. + 14. Click Next. + +The RTO optimization page appears. + + 15. Choose a Recovery Time Objective (RTO) optimization option. + +Choice| Effect +---|--- +Minimize recovery time | Keeps a hot standby (prefixed with **RBRK_**) in the selected datastores. Shortens recovery time, but increases production storage requirements. Do not delete the hot standby virtual machine prefixed with **RBRK_**. +Minimize datastore usage | Only uses storage during test or live failover operations. Can affect RTO by increasing the time required to mount the virtual machines. + + 16. Click Next. + +The Assign Storage Resources page appears. + + 17. **Optional:** Select Assign the same storage resource for all objects to use the same storage resource for all objects and then select a single storage resource. + 18. Choose an option for the Recovery Plan failover datastore. + +Choice| Effect +---|--- +Select a datastore or datastore cluster for your Recovery Plan for all virtual machines. | Enables selecting a datastore or datastore cluster from a list. All virtual machines in the # Creating a disaster Recovery Plan for vSphere virtual machines + +Create a disaster Recovery Plan to enable failover testing and production failover orchestration for a set of virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. The Objects page appears. + 3. In the vSphere tab, click **Recovery Plans**. The Recovery Plans page appears, listing all Recovery Plans + 4. Click Create and then select Disaster Recovery Plan. The Create Recovery Plan wizard appears. + 5. In Name, enter a name for the Recovery Plan. + 6. In Recover From, select a Rubrik cluster from the dropdown list. All virtual machines in the Recovery Plan must have a snapshot on the selected Rubrik cluster. + 7. In Recover To, select a Rubrik cluster. During a failover operation, RSC creates virtual machines on the target hypervisor resources. + 8. Click Next. The Select vSphere virtual machines page appears. + 9. Select the virtual machines to recover and click Next. The Set the boot order of virtual machines page appears. + 10. Select a priority group for each virtual machine and click Next. The Select compute resource page appears. + 11. Select an option for failover target selection and click Next. | Choice| Effect +---|--- +Choose a vSphere compute cluster, host, or resource pool for your Recovery Plan(All virtual machines). | Enables selecting a failover target from a list. All virtual machines in the Recovery Plan use the selected target during a failover operation. +Choose a vSphere compute cluster, host, or resource pool for each virtual machine in your Recovery Plan. | Enables selecting a specific failover target for each virtual machine in the Recovery Plan. The Targets column displays a list of target choices. + +Compute clusters that do not have hosts or resource pools are not available for selection. + + 12. In Targets, click a target name to select a failover target for each virtual machine. + +The Select a target for compute resources window appears. + + 13. Select the target and click Save for each virtual machine. + 14. Click Next. + +The RTO optimization page appears. + + 15. Choose a Recovery Time Objective (RTO) optimization option. + +Choice| Effect +---|--- +Minimize recovery time | Keeps a hot standby (prefixed with **RBRK_**) in the selected datastores. Shortens recovery time, but increases production storage requirements. Do not delete the hot standby virtual machine prefixed with **RBRK_**. +Minimize datastore usage | Only uses storage during test or live failover operations. Can affect RTO by increasing the time required to mount the virtual machines. + + 16. Click Next. + +The Assign Storage Resources page appears. + + 17. **Optional:** Select Assign the same storage resource for all objects to use the same storage resource for all objects and then select a single storage resource. + 18. Choose an option for the Recovery Plan failover datastore. + +Choice| Effect +---|--- +Select a datastore or datastore cluster for your Recovery Plan for all virtual machines. | Enables selecting a datastore or datastore cluster from a list. All virtual machines in the Recovery Plan use the selected datastore during a failover operation. +Select a datastore or datastore cluster for each virtual machine in your Recovery Plan. | Enables selecting a specific datastore or datastore cluster for each virtual machine in the Recovery Plan. + + 19. Click Next. + 20. Select a datastore or datastore cluster for all virtual machines in the Recovery Plan. + 21. In Datastore or datastore Cluster, click a name to select the datastore or datastore cluster for storage during failover for each virtual machine. + +The Select a datastore or datastore cluster window appears. + + 22. Select a datastore or datastore cluster and click Save. + 23. Click Next. + +The Post scripts page appears. + + 24. **Optional:** In Post Scripts, enter the path to a post-instantiation script for a virtual machine. + +Post-instantiation scripts increase the recovery time for a virtual machine due to the script demand on compute resources. + + 25. Click Next. + +The Network resources page appears. + + 26. Select a target network and IP configuration for each virtual machine in the Recovery Plan for failover and test failover and click Next. + +Option| Description +---|--- +Select Entire Network and then select the Target Network for each object. | The current MAC Address and IP configuration is retained. +Select MAC Address Only and then select the Target Network and IP Configuration for each object. | The current MAC address is retained for the source virtual machine. +Select None and then select the Target Network and IP Configuration for each object. | A new MAC address is assigned to the virtual machine. + + 27. Enter a target network and IP configuration for each virtual machine in the Recovery Plan for failover. + +When you select Static as the IP configuration, you can also enter the IP Address/Netmask, DNS Servers, and Gateway values. + +The network configurations are applied to the virtual machines during recovery. + + 28. **Optional:** Click Fast Fill. + +When you select Static as the IP configuration, you can also enter the IP Address/Netmask, DNS Servers, and Gateway values. + +The Fast Fill window appears and you can enter a target network and IP configuration for each virtual machine in the Recovery Plan for failover. + + 29. Select an option for applying Fast Fill, when using Fast Fill. + * Apply to all virtual machines + * Apply to selected virtual machines + +You can use the search bar to search for virtual machines. + + 30. When using Fast Fill, click Apply. + +The network configurations are applied to the virtual machines during recovery. + + 31. Click Next. + +The Assign post-failover SLA Domains page appears. + + 32. Select an option for assigning SLA Domains: + * Select Use the same post-failover SLA domains for all objects to use the same SLA Domains for all objects and then select a single SLA Domain. + * Specify an SLA Domain for each virtual machine. These SLA Domains protect the virtual machines after a failover operation. To failback to the original site, select SLA Domains that have the current source cluster as their replication target cluster. + 33. Click Next. + +The Review Recovery Plan details page appears. + + 34. Review Recovery Plan details and click Create. + +## Results + +RSC creates the Recovery Plan and provides options to Recover Now, Schedule Recovery Plan Tests, or Create Another Plan. + +When you click any of these options, RSC displays the appropriate wizard. + +# Disaster Recovery Plan information + +RSC provides important information about disaster Recovery Plan statuses and the actions permitted for each status in the Recovery Plans page. + +Status | Description | Permitted actions +---|---|--- +Configured | RSC has configured the Recovery Plan. | + * Deleting the Recovery Plan. + * Performing a local recovery. + * Performing a failover operation. + * Testing failover. +Inconsistent target location | RSC is not protecting the Recovery Plan with an SLA Domain or the SLA Domain is specifying a replication target that does not match the Recovery Plan target. | + * Editing the Recovery Plan. + * Deleting the Recovery Plan. + * Taking an on-demand snapshot. + * Performing a local recovery. +Missing resource mapping | Disaster Recovery Plans require a resource mapping. This Recovery Plan does not have a resource map and cannot be used in this state. | + * Editing the Recovery Plan. + * Deleting the Recovery Plan. + * Taking an on-demand snapshot. + * Performing a local recovery. + * Mapping resources. +Invalid resource mapping | The current configuration of the resource mapping for the Recovery Planor the Recovery Plan itself is not usable. The Recovery Plan cannot be used in this state. | + * Editing the Recovery Plan. + * Deleting the Recovery Plan. + * Taking an on-demand snapshot. + * Performing a local recovery. + * Mapping resources. + * Performing a failover operation.RSC supports failover operations from a specific snapshot. +Test in progress | A test failover is in progress. | You cannot perform any operations while the test failover is in progress. +Test paused on error | The test failover encountered an error. The status of the virtual machines determines whether the test can resume or be cleaned up. | + * Taking an on-demand snapshot. + * Performing a local recovery. + * Mapping resources. + * Resuming test. + * Cleaning up test. +Test pending cleanup. | The test failover is complete and resources created in the test environment can be cleaned up. | + * Taking an on-demand snapshot. + * Performing a local recovery. + * Cleaning up test. +Cleaning up test | RSC is cleaning up the test failover. | No operations can be performed during a test failover cleanup. +Test failed | The last test failover operation has failed. The test report provides additional information. | + * Editing the Recovery Plan. + * Deleting the Recovery Plan. + * Taking an on-demand snapshot. + * Performing a local recovery. + * Mapping resources. + * Performing a test failover. + * Performing a failover operation.RSC supports failover operations from a specific snapshot. +Test job succeeded | The test failover operation completed successfully and resources created for the test have been cleaned up. | Performing any action. +Failover in progress | Failover is in progress. | No operations can be performed while a failover is in progress. +Failover paused on error | RSC encountered an error during failover. The status of the virtual machines determines whether the failover can resume or be cleaned up. | + * Resuming failover. + * Cleaning up failover. +Failover cleanup in progress | The failover operation has failed. RSC is cleaning up the failover. | No operations can be performed during a failover cleanup. +Failover failed | The last failover attempt failed. The failover report provides additional information. | + * Editing the Recovery Plan. + * Deleting the Recovery Plan. + * Taking an on-demand snapshot. + * Performing a local recovery. + * Mapping resources. + * Testing failover. + * Performing a failover operation.RSC supports failover operations from a specific snapshot. +Failover succeeded | The failover operation succeeded. | After a test failover: + * Cleaning up test. +After a non-test failover: + * Performing a local recovery. + * Deleting the Recovery Plan. + * Mapping resources. + *[ > ]: and then diff --git a/saas_downloading_a_sdd_report.md b/saas_downloading_a_sdd_report.md new file mode 100644 index 0000000000000000000000000000000000000000..a763e0bab86252a0524d3f69c403cdadfe23f32c --- /dev/null +++ b/saas_downloading_a_sdd_report.md @@ -0,0 +1,36 @@ +# Downloading a Data Security Posture report + +Source: https://docs.rubrik.com/en-us/saas/saas/downloading_a_sdd_report.html + +--- + +# Downloading a Data Security Posture report + +Download a Data Security Posture report in one of the available formats. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. Click Reports &Events. + 4. Select a report. + +The selected report opens. + + 5. Click the dropdown next to Save and select a format to download the report. + * Download CSV + * Download PDF + +A message appears that Data Security Posture is preparing the report. A tray also displays the report name. + + 6. Click the located on the tray or in the File Preparation Center tab to download reports. + +Clicking View all files in the tray displays the File Preparation Center. + +## Results + +Data Security Posture downloads the report in the selected format. + *[ > ]: and then diff --git a/saas_downloading_quarantined_files_analysis.md b/saas_downloading_quarantined_files_analysis.md new file mode 100644 index 0000000000000000000000000000000000000000..9893f4fd7a78b93293dcee4cdd689798635b43d6 --- /dev/null +++ b/saas_downloading_quarantined_files_analysis.md @@ -0,0 +1,47 @@ +# Downloading quarantined files for forensic analysis + +Source: https://docs.rubrik.com/en-us/saas/saas/downloading_quarantined_files_analysis.html + +--- + +# Downloading quarantined files for forensic analysis + +Download quarantined files to examine and analyze them for malicious content. + +## Before you begin + +Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click the threat hunt of interest. + +If added to quarantine, the quarantined objects are listed along with details of their location, files matched, and match type. + + 5. Click an object to view the files in that object. + 6. Select the files to download. + 7. Click and select Download For Forensics. + +The Download for Forensics dialog box appears. + + 8. **Optional:** Click the snapshot column to choose any other non-expired snapshot containing the file. + +By default, the Download For Forensics wizard selects the latest non-expired snapshot for each file. + + 9. Click Download. + +Downloading the files can be dangerous if these files are malicious. Exercise caution to keep your systems safe. + +## Results + +RSC downloads the files as specified. + *[ > ]: and then diff --git a/saas_downloading_the_rubrik_cluster_upgrade_report.md b/saas_downloading_the_rubrik_cluster_upgrade_report.md new file mode 100644 index 0000000000000000000000000000000000000000..9fde210d204083f053e5fdf5677cf64c1ea18596 --- /dev/null +++ b/saas_downloading_the_rubrik_cluster_upgrade_report.md @@ -0,0 +1,41 @@ +# Downloading the Rubrik cluster upgrade report + +Source: https://docs.rubrik.com/en-us/saas/saas/downloading_the_rubrik_cluster_upgrade_report.html + +--- + +# Downloading the Rubrik cluster upgrade report + +Download and view the Rubrik cluster upgrade report for monitoring or auditing. + +## About this task + +User access for this task depends on view permissions for the Rubrik clusters. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Clusters and select CDM Software Upgrades. + +The Rubrik CDM Upgrades page appears. + + 4. Open the ellipsis menu and select Download cluster upgrade report. + +RSC prepares the cluster upgrade report for download. The prompt indicates that the download is being prepared. + + 5. Select an option to view the report. + +Option| Description +---|--- +Click the download icon in the message prompt. | The Rubrik cluster upgrade report opens for viewing. +In the navigation menu, click Events > File Preparation Center, and then click the download icon for the file text. | The Rubrik cluster upgrade report opens for viewing. + + +## Results + +The Rubrik cluster upgrade report is available for viewing. + *[ > ]: and then diff --git a/saas_dsp_conf_workloads.md b/saas_dsp_conf_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..0bef45a40ed5d5deac4982d8089051bc95bb36f9 --- /dev/null +++ b/saas_dsp_conf_workloads.md @@ -0,0 +1,19 @@ +# Data Security Posture configuration for workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/dsp_conf_workloads.html + +--- + +# Data Security Posture configuration for workloads + +Enabling Data Security Posture has specific requirements according to the workload. + +You can use Data Security Posture to monitor where your sensitive data is, who has access to it, and how it has been used. You can create access policies based on classifications and quickly remediate violations. + +The following table describes the prerequisites and classification support available for specific workloads. Workload | Prerequisites | Classification support +---|---|--- +AWS | Rubrik Enterprise edition or the Universal Cloud license is required | RSC automatically discovers and classifies sensitive data. +Azure | Rubrik Enterprise edition or the Universal Cloud license is required | RSC automatically discovers and classifies sensitive data. +M365 | Microsoft 365 license is required and data must be backed up | RSC automatically discovers and classifies sensitive data after the first backup is complete and you assign policies in Data Security Posture. +On-Premises | License for the respective workload is required and data must be backed up | RSC automatically discovers and classifies sensitive data after the first backup is complete and you assign policies in Data Security Posture. + *[ > ]: and then diff --git a/saas_dsp_windows_audit_log_configuration.md b/saas_dsp_windows_audit_log_configuration.md new file mode 100644 index 0000000000000000000000000000000000000000..55df7091cff215287c9da3baf814ea36470f140d --- /dev/null +++ b/saas_dsp_windows_audit_log_configuration.md @@ -0,0 +1,63 @@ +# Windows audit log configuration for Active Directory identities + +Source: https://docs.rubrik.com/en-us/saas/saas/dsp_windows_audit_log_configuration.html + +--- + +# # Identity Inventory information + +Security teams can use the Identity Inventory to perform user access reviews, track user activity on sensitive data, and assess associated user risk. This visibility helps security teams detect excessive privileges, unauthorized access, and accelerates incident response through detailed user and access context. + +Security teams can leverage the Identity Inventory to perform user access reviews, track user activity on sensitive data, and evaluate associated user risk. This comprehensive visibility helps security teams in detecting excessive privileges and unauthorized access, while also accelerating incident response through detailed user and access context. + +## Identity information access + +You can access the identity information on the Identity Inventory page for Microsoft and Entra ID identities, and on the AWS Identities page for AWS identities. + +To explore the details of an identity further, you can do the following: + * Clicking an identity on the main inventory page displays a subsequent page. This page shows additional associated identities and the accessible objects for that identity within their respective tabs. + * Clicking an identity on this subsequent page opens the identity details page, which further displays members, associated identities, and accessible objects in their dedicated tabs. + +## Identity types + +The Identity Inventory lists identities that are learned from Entra ID and Active Directory. The following table lists the identity types. + +Identity Types | Description +---|--- +Roles | A role is an identity with specific permissions enabled for whoever is assigned to the role. +Groups | A group of users. Rubrik recommends granting permissions to groups rather than directly to users, aligning with a business need. +Users | An identity defining the set of permissions a specific person or entity has within the environment. This option usually refers to human identities. + +# Windows audit log configuration for Active Directory identities + +Enabling the Identity Inventory successfully requires specific audit log configuration in the Windows security auditing feature to monitor relevant events. + +The Identity Inventory relies on Windows security features to track the activities that users perform on the protected data. For optimal performance, Rubrik recommends specific configurations to monitor only relevant events. + +Performing the audit log configuration requires logging in as a member of the Microsoft Windows Built-in Administrators group. Configuring these specific requirements is essential for enabling the Identity Inventory on your virtual machines. + +Note: + +The Identity Inventory is available as part of the Rubrik Enterprise Proactive Edition. + +Setting | Rubrik recommendation | Description +---|---|--- +Audit Configuration | The Identity Inventory uses the Windows security audit log to track activities users perform on protected data. The Windows security audit is designed to support many use cases. Because the Identity Inventory needs events information only for object access, Rubrik recommends setting the audit configuration to audit only the file system. | The following code configures the Windows security audit to audit only the file system. Executing the following commands in PowerShell enables event generation for Object Access. + + PS C:\Users\Administrator> auditpol /set /Subcategory:"File System" /success:enable /Failure:Enable + The command was successfully executed. + + PS C:\Users\Administrator> auditpol /set /Subcategory:"Handle Manipulation" /Failure:Enable + The command was successfully executed. + +The output of the following command confirms whether the configuration was successful. + + PS C:\Users\Administrator> auditpol /get /category:"Object Access" + +Microsoft documentation provides further details on creating a basic audit policy for an event category. +SACL configuration | Rubrik recommends applying audit policies to individual files and folders on your computer by setting the permission type to record successful access attempts or failed access attempts in the security log. | Selecting and holding or right-clicking the file or folder to audit, and then selecting the following options in the Audit tab of Advanced Security Settings, applies audit policies to individual files and folders: + * All for the Type + * Files Only for the objects which this configuration applies to + * Full Control for the Basic Permissions settings +Audit log configuration | Rubrik recommends a sufficiently large evtx-formatted file to avoid log rotation between two backups. Rubrik extracts this log file from the backup data. | A sufficiently large evtx-formatted file at %SystemRoot%\System32\Winevt\Logs\Security.evtx, where Security audit logs are stored by default, is required to enable the Identity Inventory successfully. The default size of this file is 20 MB. Navigating to the properties section of the Security Log in the Event Viewer opens a dialog box for providing the file size in KB.The same dialog box also offers the choice to Archive the logs when full, and not to overwrite events instead of automatically rotating them, as needed.Enabling audit logs for the Authenticated Users or Everyone principals includes system services that might create large size logs. Rubrik recommends using the Domain Users principal when enabling audit logs. + *[ > ]: and then diff --git a/saas_dta_dashboard.md b/saas_dta_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..b21daff00a486227aa8f0766d85121ac4ff531cb --- /dev/null +++ b/saas_dta_dashboard.md @@ -0,0 +1,24 @@ +# Data Threat Analytics dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/dta_dashboard.html + +--- + +# Data Threat Analytics dashboard + +The Data Threat Analytics dashboard provides a comprehensive analysis of data threats including a summary of anomalies, threat monitoring matches, matched threat hunts for protected objects, and object timeline analysis. + +Widget | Description +---|--- +Threat Summary | Displays the number of backups completed with the percentage of healthy backups and the following Data Threat Analytics summary: + + * Anomaly Detection analysis completed and the number of anomalous objects found + * Threat Monitoring results with the details of the objects scanned for IOCs appear + * Active threat hunts with the number of matched hunts + +You can filter the data for the past 24 hours, 7 days, or 30 days. +Known IOCs | Displays a pie chart of the known IOCs for which Threat Monitoring checks. The chart displays known IOCs divided into file hashes and YARA rules. This widget also displays the time at which the known IOCs were updated. +Anomaly Detection | Displays the total percentage of anomalous and non-anomalous objects for the past 24 hours, 7 days, and 30 days. +Threat Monitoring | Displays the total percentage of objects with and without threats for the past 24 hours, 7 days, and 30 days.This widget is visible when Threat Monitoring is enabled. Threat Monitoring is available as part of the Rubrik Enterprise edition. +Timeline Analysis | The chart shows the number of anomalies and threats found over the past 7 days and 30 days. + *[ > ]: and then diff --git a/saas_editing_cyber_rp.md b/saas_editing_cyber_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..0f5ddd6c78647e8491555a9f727fbc50e60a752e --- /dev/null +++ b/saas_editing_cyber_rp.md @@ -0,0 +1,43 @@ +# Editing a cyber Recovery Plan + +Source: https://docs.rubrik.com/en-us/saas/saas/editing_cyber_rp.html + +--- + +# Editing a cyber Recovery Plan + +Edit a cyber recovery Recovery Plan when deployment requirements change. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click **Recovery Plans**. + +The Recovery Plans page appears, listing all Recovery Plans in the vSphere, AHV, and Azure VM tabs. + + 4. Select the cyber Recovery Plan to edit. + +The Cyber Recovery Plan overview page appears. + + 5. Click Edit. + +The Edit Cyber Recovery Plan wizard appears. + + 6. Choose a component of the cyber Recovery Plan to edit. + +You can edit an element of the plan in the pages of the wizard. You can use the Next button to proceed to the next component or the Back button to revisit previous steps. + + 7. Click Next. + +The Confirmation page appears. + + 8. Click Confirm. + +## Results + +RSC saves the changed configuration and returns to the Recovery Plan details page. + *[ > ]: and then diff --git a/saas_editing_disaster_rp.md b/saas_editing_disaster_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..056f2050996325fa5f8b7fa2a554082167f842ce --- /dev/null +++ b/saas_editing_disaster_rp.md @@ -0,0 +1,43 @@ +# Editing a disaster Recovery Plan + +Source: https://docs.rubrik.com/en-us/saas/saas/editing_disaster_rp.html + +--- + +# Editing a disaster Recovery Plan + +Edit the Recovery Plan when deployment requirements change. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click **Recovery Plans**. + +The Recovery Plans page appears, listing all Recovery Plans in the vSphere and AHV tabs. + + 4. Select the disaster Recovery Plan to edit. + +The Recovery Plan overview page appears. + + 5. Click Edit. + +The Edit DR Recovery Plan wizard appears. + + 6. Choose a component of the Recovery Plan to edit. + +You can edit an element of the plan in the pages of the wizard. You can use the Next button to proceed to the next component or the Back button to revisit previous steps. + + 7. Click Next. + +The Review Recovery Plan details page appears. + + 8. Click Edit. + +## Results + +RSC saves the changed configuration and returns to the Recovery Plan details page. + *[ > ]: and then diff --git a/saas_editing_guest_os_credentials.md b/saas_editing_guest_os_credentials.md new file mode 100644 index 0000000000000000000000000000000000000000..00a71744b672d7969402506b7dcc6912c7cba176 --- /dev/null +++ b/saas_editing_guest_os_credentials.md @@ -0,0 +1,44 @@ +# Editing a guest OS credential + +Source: https://docs.rubrik.com/en-us/saas/saas/editing_guest_os_credentials.html + +--- + +# Editing a guest OS credential + +Edit a guest OS credential to update the Rubrik cluster with changes to the authentication server, username, or password. + +## Before you begin + +To edit a guest OS credential, use an RSC user account that is assigned the administrator role and the Manage guest OS credentials permission. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC using the administrator account. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Source > Access Credentials. + +The Access Credentials page appears. + + 4. Click Guest OS Settings tab. + 5. Open the ellipsis menu for a Guest OS credential and select Edit. + +The Edit Guest OS Credential dialog box appears. + + 6. Edit the domain, description, user name, or password. + +For Linux credentials, ensure that the Domain field is empty. + + 7. Click Update. + +## Results + +RSC saves the updated information. + *[ > ]: and then diff --git a/saas_editing_in_place_rp.md b/saas_editing_in_place_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..5cb9bfd0c82020469ace54effb94c0765e2a8891 --- /dev/null +++ b/saas_editing_in_place_rp.md @@ -0,0 +1,50 @@ +# Editing an in-place Recovery Plan + +Source: https://docs.rubrik.com/en-us/saas/saas/editing_in_place_rp.html + +--- + +# Editing an in-place Recovery Plan + +Edit an in-place Recovery Plan based on your requirements. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click **Recovery Plans**. + +The Recovery Plans page appears, listing all Recovery Plans. + + 4. Select the in-place Recovery Plan to edit. + +The Recovery Plan overview page appears. + + 5. Click Edit and then select Recovery Plan. + +The Edit Recovery Plan wizard appears. + + 6. **Optional:** Edit the name of the Recovery Plan. + 7. Click Next. + +The wizard displays the virtual machines managed by RSC. + + 8. **Optional:** Change the selected virtual machines as required. + 9. Click Next. + +The wizard lists the boot order of the virtual machines in the Recovery Plan. + + 10. **Optional:** Change the boot order assignments as required. + 11. Click Next. + +The Review Recovery Plan details page appears. + + 12. Click Edit. + +## Results + +RSC saves the changed configuration and returns to the Recovery Plan details page. + *[ > ]: and then diff --git a/saas_enable_dsp_sharepoint_and_onedrive.md b/saas_enable_dsp_sharepoint_and_onedrive.md new file mode 100644 index 0000000000000000000000000000000000000000..bb53e24314b709cad644563ea66add2d3ec628bf --- /dev/null +++ b/saas_enable_dsp_sharepoint_and_onedrive.md @@ -0,0 +1,16 @@ +# Enable Data Security Posture for Microsoft SharePoint and OneDrive + +Source: https://docs.rubrik.com/en-us/saas/saas/enable_dsp_sharepoint_and_onedrive.html + +--- + +# Enable Data Security Posture for Microsoft SharePoint and OneDrive + +To find data matching a specified data policy within snapshots, enable Data Security Posture for Microsoft SharePoint and OneDrive. + +Data Security Posture identifies sensitive data matching a specified policy within archived backups. + +To enable Data Security Posture for Microsoft SharePoint and OneDrive, you must assign policies in Data Security Posture to discover sensitive data matching a specified data policy within snapshots. You can also create custom data categories and data types based on your requirements and assign to the desired objects. After the data category is enabled, Data Security Posture performs a full analysis and the sensitive data classification will be available in the object details page in Data Security Posture. + +You can configure Data Security Posture for up to a total of 50,000 OneDrive and Sharepoint objects in RSC. + *[ > ]: and then diff --git a/saas_enabling_anomaly_detection.md b/saas_enabling_anomaly_detection.md new file mode 100644 index 0000000000000000000000000000000000000000..87ee5d8c194f41b8473be993652e4596356cbae7 --- /dev/null +++ b/saas_enabling_anomaly_detection.md @@ -0,0 +1,46 @@ +# Enabling Anomaly Detection + +Source: https://docs.rubrik.com/en-us/saas/saas/enabling_anomaly_detection.html + +--- + +# Enabling Anomaly Detection + +Enable Anomaly Detection to perform behavioral and content analysis on the file system and show details about potentially anomalous incidents. + +## Before you begin + +Enabling Anomaly Detection for Amazon S3 buckets and Azure Blob Storage accounts requires assigning an SLA Domain with an archival location for the Amazon S3 buckets and Azure Blob Storage accounts, respectively. + +Note: + +Enabling Anomaly Detection requires either the Owner or Admin role or a custom role with both Edit system preferences and Manage Anomaly Detection privileges. + +## About this task + +When you enable Anomaly Detection for the data, Large Language Model (LLM) analysis for Anomaly Detection is enabled by default. If you do not wish to use LLM analysis for Anomaly Detection, you can disable it. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Threat Analytics and select one of the following options: + +Option| Description +---|--- +Clusters | Displays the list of Rubrik clusters for which you can enable Anomaly Detection.The option is available only for connected Rubrik clusters. +Cloud Accounts | Displays the list of cloud accounts for which you can enable Anomaly Detection. +Rubrik Cloud Vault | Displays the list of Rubrik Cloud Vault locations for which you can enable Anomaly Detection.Use Rubrik Cloud Vault locations when you enable Anomaly Detection for NAS CD data sets. +Microsoft 365 | Displays the list of Microsoft 365 subscriptions for which you can enable Anomaly Detection. + + 4. Turn on Anomaly Detection for the required option. + +## Results + +You have enabled Anomaly Detection according to your selection. The Anomaly Detection dashboard displays the anomalies in the protected objects. + +When Anomaly Detection detects an anomalous incident, RSC sends an anomaly event email with a severity level of either Warning or Critical to the specified email recipients. Warning indicates low levels of detected encryption, and Critical indicates high levels of detected encryption. + *[ > ]: and then diff --git a/saas_enabling_stringent_policies_organizations.md b/saas_enabling_stringent_policies_organizations.md new file mode 100644 index 0000000000000000000000000000000000000000..b7d48c9237e2dbc4fde9e3270b0958beba82c1e8 --- /dev/null +++ b/saas_enabling_stringent_policies_organizations.md @@ -0,0 +1,33 @@ +# Enabling stringent policies for organizations + +Source: https://docs.rubrik.com/en-us/saas/saas/enabling_stringent_policies_organizations.html + +--- + +# Enabling stringent policies for organizations + +An user with administrator privileges for a global organization can enable global enforcement settings to enforce stricter policies for tenant organizations. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Organizationsand select Management. + +The Organization Management page appears. + + 4. Click Organization Settings. + +The Organization Settings dialog box appears. + + 5. Turn on the Stringent policies for tenant organization toggle and click Save. + +If you turn off the toggle, the stringent policies for tenant organization will not be enabled and it relaxes the global enforcement for your tenant organizations. + +## Results + +You have enforced your tenant organizations to implement policies that are equal to or stricter than the global configurations. + *[ > ]: and then diff --git a/saas_event_details.md b/saas_event_details.md new file mode 100644 index 0000000000000000000000000000000000000000..73ec2a5df3689f1838dd22580cd2912ea58f8316 --- /dev/null +++ b/saas_event_details.md @@ -0,0 +1,30 @@ +# Event details + +Source: https://docs.rubrik.com/en-us/saas/saas/event_details.html + +--- + +# Event details + +Select an event on the Events page to see detailed information for the event. + +Event detail | Description +---|--- +Object | A combination of Object type and Object name. +Status | The status of the event. +Event | The most recent update from the event timeline. +Cluster | The name of the event host, either a Rubrik cluster or RSC. +Object type | The type of the object associated with the event, such as: + + * virtual machine + * server + * application + + +Object name | The name of the object associated with the event. +Event type | The type of the event. +Duration | The time elapsed for an event in progress or the total time taken for the completed events. +Start time | The date and time when the event started. +Event timeline | A list of updates about the event from beginning to end. +Incident ID | A unique identifier for failed events. + *[ > ]: and then diff --git a/saas_events_information.md b/saas_events_information.md new file mode 100644 index 0000000000000000000000000000000000000000..ae60e4127a6bf389354cc0b6789e723083391f67 --- /dev/null +++ b/saas_events_information.md @@ -0,0 +1,10 @@ +# Events information + +Source: https://docs.rubrik.com/en-us/saas/saas/events_information.html + +--- + +# Events information + +RSC displays the Events page from the Dashboard page, the Events tab, and the Clusters page. + *[ > ]: and then diff --git a/saas_exocompute_for_aws.md b/saas_exocompute_for_aws.md new file mode 100644 index 0000000000000000000000000000000000000000..08fb29c89eff7805b41a49c94ce4c928970497c8 --- /dev/null +++ b/saas_exocompute_for_aws.md @@ -0,0 +1,89 @@ +# Exocompute on AWS + +Source: https://docs.rubrik.com/en-us/saas/saas/exocompute_for_aws.html + +--- + +# Exocompute on AWS + +With the Exocompute on AWS feature, RSC launches an Elastic Kubernetes Service cluster to perform various operations to protect AWS workloads. RSC uses the Elastic Kubernetes Service cluster as a compute resource in your AWS account. + +The Exocompute on AWS feature of Rubrik uses a container-based framework and is designed to perform various data processing tasks in your AWS environment. By leveraging Amazon Elastic Kubernetes Service (EKS), Exocompute manages compute resources to perform essential operations, such as file indexing, file recovery, application-consistent backups, and storage tiering. + +## Key operations of Exocompute + +Exocompute uses EKS to perform the following operations: + + * File indexing: When you enable the file search feature for an EC2 instance or an EBS volume, each new backup of the instance or volume initiates a file indexing operation. + * File recovery: When you initiate a recovery operation for the files in the backup of an EC2 instance or an EBS volume, RSC launches an EKS cluster to read the file data from the backup. + * Application-consistent backups: When you turn on application-consistent backups for EC2 instances, RSC launches a temporary Exocompute instance to coordinate backup activity with the Rubrik Backup Service (RBS) agent installed on the EC2 instance. + +Important: + +RSC does not support the archival of application-consistent snapshots of EC2 instances when using the centralized Exocompute configuration. + + * AWS storage tiering: When a snapshot reaches the archival threshold specified in the SLA Domain, RSC launches an EKS cluster to tier the snapshot to the specified storage. + +## EKS integration + +Exocompute uses Amazon EKS to launch an Amazon EKS cluster to manage Exocompute nodes. An EKS cluster consists of two primary components: the EKS control plane and EKS nodes registered with the control plane. The EKS control plane consists of control plane nodes that run the Kubernetes software, such as etcd and the Kubernetes API server. The control plane runs in an account managed by AWS, and the Kubernetes API is exposed through the Amazon EKS endpoint associated with the EKS cluster. Amazon EKS nodes run in your AWS account and connect to the control plane through the API server endpoint and a certificate file created for the EKS cluster. + +The roles and responsibilities of each component are as follows: + + * Control plane node: Orchestrates the life cycle of the EKS nodes, launches EKS nodes, assigns jobs to them, and terminates them, as required. No Rubrik logic is executed within the control plane node. + * EKS nodes: Executes the core logic for tasks such as file search, file recovery, and application-consistent backups. EKS nodes are launched as a node pool with a minimum of one node. Based on the AWS workload requirements, additional EKS nodes may be launched automatically. + +Based on the requirements, Exocompute automatically creates, scales, and destroys these EKS clusters and nodes to minimize costs. + +## Private Exocompute on AWS + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Private Exocompute on AWS deploys an Amazon EKS cluster in private mode, ensuring all network traffic between the control plane of the cluster and its nodes remains within a dedicated Virtual Private Cloud (VPC). This setup makes the Kubernetes API server endpoint inaccessible from the public internet, enabling access only from within the VPC. This approach aligns with strict enterprise security guidelines by containing network traffic and limiting external exposure. The Private clusters section in the AWS documentation provides more information about the private mode. + +To enable RSC to manage the private EKS cluster, a secure, dedicated connection is established. This connection allows only requests originating from your AWS account to reach the RSC domain. This controlled access mechanism ensures that the private nature of the cluster is maintained while allowing for essential management operations. + +Important: + + * RSC supports the private Exocompute on AWS feature only in standard AWS regions, excluding AWS GovCloud (US) and AWS (China) regions. + * RSC does not support private Exocompute for users who use a Private Container Registry (PCR). Even if you configure a PCR for your AWS account, the Exocompute workflow continues to use a public endpoint access. For more information about PCR, see [Private Container Registry for AWS](private_container_registry.html "For security purposes, when you do not want to retrieve Docker images from a registry hosted by Rubrik, you can configure a Private Container Registry to retrieve these Docker images from a registry hosted by you."). + +To facilitate secure, private connectivity, RSC creates a Lambda function in your AWS environment. This function performs a one-time setup to establish a two-way channel between a private EKS cluster and RSC. To accomplish this, RSC assumes a cross-account role with specific, scoped permissions. + +The following table describes the key permissions required for this process: + +Category | Required permissions | Purpose +---|---|--- +Lambda | + + * lambda:CreateFunction + * lambda:GetFunction + * lambda:DeleteFunction + * lambda:UpdateFunctionConfiguration + * lambda:TagResource + +| Enables RSC to create, retrieve, delete, and update the specific Lambda function responsible for communication. These actions are limited to functions prefixed with `Lambda-Rubrik-Exocompute-`. +EKS access entry | + + * eks:CreateAccessEntry + * eks:AssociateAccessPolicy + * eks:DeleteAccessEntry + +| Enables RSC to manage access entries within the EKS cluster. This includes creating an access entry for the Lambda function IAM role, attaching necessary policies, and managing its lifecycle, thereby granting the Lambda function permission to operate within the EKS cluster. +Elastic Container Registry (ECR) image pull | + + * ecr:BatchGetImage + * ecr:GetDownloadUrlForLayer + +| Enables the AWS Lambda service to retrieve container images from Amazon ECR, so that this service can launch the Lambda function. + +RSC performs the following key operations in your AWS environment to establish this private connectivity: + + * Lambda role creation: RSC creates an IAM role named `AWSLambdaExocompute`. This role has a trust policy that allows the `lambda.amazonaws.com` service to assume it. + * Policy attachment: RSC attaches the `arn:aws:iam::aws:policy/service-role/AWSLambdaVPCAccessExecutionRole` policy to the Lambda role. This policy is essential for the Lambda function to create Elastic Network Interfaces (ENIs) and operate within the VPC, and write logs to CloudWatch for debugging purposes. + * EKS cluster access: RSC grants the `AmazonEKSClusterAdminPolicy` access to the Lambda role using the `eks:CreateAccessEntry` permission. This action gives the Lambda function the necessary permissions to create a configuration map and a pod inside the EKS cluster, which are integral to the communication setup. + +## Additional information + +For the AWS Marketplace AMI instances, you can perform file indexing, file recovery, and storage tiering. + *[ > ]: and then diff --git a/saas_extra_dense_migration_cces_clusters.md b/saas_extra_dense_migration_cces_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..41b9c9ef66b181df1b313f7259ca844c1be14be4 --- /dev/null +++ b/saas_extra_dense_migration_cces_clusters.md @@ -0,0 +1,58 @@ +# Extra dense node migration for CCES clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/extra_dense_migration_cces_clusters.html + +--- + +# Extra dense node migration for CCES clusters + +Extra dense nodes offer greater storage and performance, without a loss of storage capacity. Using extra dense nodes, organizations can reduce node counts by half during migration. Customization options are available through the GraphQL API. + +## Prerequisites + +The following tables describe the prerequisites, process, and customization options for migrating Rubrik cloud clusters to use extra dense nodes. Prerequisite | Description +---|--- +Cluster composition | The Rubrik Cloud Cluster Elastic Storage (Rubrik Cloud Cluster ES) must contain at least 3 nodes. +Node specification | All cluster nodes must be 32 TB dense nodes. +CDM version | The cluster must be running Rubrik CDM version 9.2.2 or later. + +## Process + +The migration process involves calculating the new node count by halving the existing node count. For example, a cluster initially comprising n dense nodes will be replaced with n/2 extra dense nodes. The process involves the following steps: + +Step | Description +---|--- +Step 1: Addition of extra dense nodes | Adds n/2 extra dense nodes to the cluster. +Step 2: Removal of original nodes | Removes the original n dense nodes after the extra dense nodes are successfully added. + +## Customization options + +To reduce risks and tailor the process to specific needs, you can override the default settings: + +Default setting | Possible override +---|--- +Custom node count | Specifies the desired number of extra dense nodes, instead of halving the node count. +Batch size adjustment | Adjusts the default batch size of six nodes for each iteration, for example, migrating one node at a time. + +## API syntax example + +The following GraphQL API request customizes the migration process by specifying the desired node count and batch size: + + + mutation MigrateCloudClusterDisks { + migrateCloudClusterDisks( + input: { + cloudAccountId: "" + clusterUuid: "" + newNodeCount: + vendor: + batchSize: + migrateToExtraDense: true + } + ) { + message + success + } + } + + *[ > ]: and then diff --git a/saas_failback_operations.md b/saas_failback_operations.md new file mode 100644 index 0000000000000000000000000000000000000000..261ccb8bd5d8c8266781a7b704f0abe481e36fe4 --- /dev/null +++ b/saas_failback_operations.md @@ -0,0 +1,24 @@ +# Failback operations + +Source: https://docs.rubrik.com/en-us/saas/saas/failback_operations.html + +--- + +# Failback operations + +A failback operation restores production data back to the original site after initial failover to a secondary location. + +After any data losses are resolved or threats mitigated after a ransomware event, the original site can resume operations. The next failover after an initial failover is therefore, often to the same source site. A failback operation executes a return to the primary system. + +To perform a failback operation, you must select the Use the original site's resources for the next failover option in the Initiate failover wizard when performing a failover operation. This option automatically updates the Recovery Plan resource map after failover to use the original source site resource configurations, for example, IP network settings. Selecting this option prepares Orchestrated Recoveryfor an eventual failback without the need to manually update the Recovery Plan. Failback is a best-effort process and relies on the ability to retrieve source object resource details, such as IP network information from snapshot metadata. + +Some examples of this process are: + + * When you configure static IP addresses for original source objects but the source virtual machines are powered down, Rubrik might not be able to determine the original static IP address of the object. Then, Orchestrated Recovery might not be able to automatically reverse the Recovery Plan and configure it with the source IP addresses. You can resolve this issue by editing the Recovery Plan and providing the IP addresses. + * When Rubrik cannot retrieve original source object IP address information from snapshot metadata, recovery will still succeed, but the Recovery Plan will display a Missing Resource Mapping warning. You can resolve this issue by editing the Recovery Plan and updating the missing resources. + +The following actions ensure using the resources of the original site during a failback operation: + + * When creating a Recovery Plan, it is necessary to select post-failover SLA Domains that have the original source cluster as their replication target. If the assigned post-failover SLA Domains do not replicate backups to the original source site, editing the Recovery Plan and Resource Map ensures this change before performing the failover. + * When performing a failover, it is necessary to select the option to use the original site’s resources. When you select this option, the Recovery Plan resource map is automatically updated after failover as a best-effort process. + *[ > ]: and then diff --git a/saas_failover_operations.md b/saas_failover_operations.md new file mode 100644 index 0000000000000000000000000000000000000000..15da1569ac8bd6e083cf6c9e7074836ee1271bca --- /dev/null +++ b/saas_failover_operations.md @@ -0,0 +1,22 @@ +# Failover operations + +Source: https://docs.rubrik.com/en-us/saas/saas/failover_operations.html + +--- + +# Failover operations + +A failover operation moves a workload from a failed site to a recovery site. + +RSC fails over virtual machines and their workloads from an on-premises site to a recovery site during disaster recovery or application migration. During a failover operation, RSC powers down the virtual machines in the Recovery Plan at the source if connectivity is still available and powers on the virtual machines at the recovery site. + +RSC performs failover operations to move VMware workloads between an on-premises site and a VMware recovery site. Recovery Plans store recovery details such as boot order, resources, network mappings, and post scripts. RSC uses these details to manage the recovery flow between sites. + +For RSC to perform a failover operation, it is necessary to enable replication on the Rubrik cluster that protects the virtual machines. When replication is enabled, and then a virtual machine on the replication source cluster fails, you can initiate a failover of the virtual machine using the replication target cluster. + +Orchestrated Recovery supports failover operations for only vSphere virtual machines. + +Note: + +You must assign Change Memory and Create Folder privileges in the vCenter Server for successful failover operations. + *[ > ]: and then diff --git a/saas_false_positive_mgmt_dta.md b/saas_false_positive_mgmt_dta.md new file mode 100644 index 0000000000000000000000000000000000000000..6aa0ccb544dad661dadddd30096194abdd3c4fc3 --- /dev/null +++ b/saas_false_positive_mgmt_dta.md @@ -0,0 +1,21 @@ +# False positives management in Threat Monitoring + +Source: https://docs.rubrik.com/en-us/saas/saas/false_positive_mgmt_dta.html + +--- + +# False positives management in Threat Monitoring + +You can often resolve false positives that occur in Threat Monitoring. + +Threat Monitoring is updated daily with new threat indicators from Google Mandiant. The daily update of threat indicators might trigger detections that were not previously flagged. You can view the threat indicators in the intel feed or in the Known IOCs widget on the Threat Monitoring dashboard. The enhanced detection capabilities may result in higher alert volumes as the advanced rule processing identifies threats more effectively. These alerts do not necessarily indicate new threats but reflect improved monitoring and detection accuracy. + +You can take the following steps to resolve false positives: + + * Verifying the alert by confirming with your security team if it is a legitimate threat. You can use external tools like VirusTotal, Hybrid Analysis, or internal threat intel platforms to validate the matched file. + * Using file hashes to run a manual threat hunt in RSC on the most recent snapshot or a custom range. + * Disabling false positive IOCs in Threat Monitoring. You can navigate to the specific IOC in the Threats page and manually turn off the IOC. If needed, you can also disable the IOC from your custom feed. Rubrik recommends documenting these actions in your incident tracking system for reference. + +Removing the IOC lists the IOC in the Intel Feed tab under the Disabled IOCs tab. You can re-enable the IOC if this was a true positive. + + *[ > ]: and then diff --git a/saas_fast_upgrade_rbk_cdm_software.md b/saas_fast_upgrade_rbk_cdm_software.md new file mode 100644 index 0000000000000000000000000000000000000000..93eb9e7505ddc62ddb681c78f7de1cbbf562cada --- /dev/null +++ b/saas_fast_upgrade_rbk_cdm_software.md @@ -0,0 +1,12 @@ +# Fast upgrade of Rubrik CDM software + +Source: https://docs.rubrik.com/en-us/saas/saas/fast_upgrade_rbk_cdm_software.html + +--- + +# Fast upgrade of Rubrik CDM software + +With the fast upgrade of Rubrik CDM software running on your Rubrik cluster, you can simultaneously upgrade all Rubrik cluster nodes. This option saves time but requires some system downtime. + +Fast upgrades of Rubrik CDM software running on your Rubrik cluster are performed simultaneously on all nodes in a Rubrik cluster. This option may require some system downtime, but the upgrade completes quickly and efficiently. You can upgrade the Rubrik CDM software running on a Rubrik cluster immediately or schedule an upgrade to run later. + *[ > ]: and then diff --git a/saas_federated_access.md b/saas_federated_access.md new file mode 100644 index 0000000000000000000000000000000000000000..bac8dc69acffb6530e615d34c442d080e80cd564 --- /dev/null +++ b/saas_federated_access.md @@ -0,0 +1,32 @@ +# Federated access + +Source: https://docs.rubrik.com/en-us/saas/saas/federated_access.html + +--- + +# Federated access + +Federated access enables RSC user and service accounts to access connected Rubrik clusters, including Rubrik NAS Cloud Direct clusters. This access is provided through the RSC user interface using Single Sign-On, eliminating the need for separate login credentials. + +For federated access, RSC is the identity provider. RSC uses SAML to securely pass the identity and permissions of the logged-in RSC user account to the Rubrik cluster. Rubrik clusters honor the Role-based Access Control (RBAC) rules that you create and assign to user accounts in the RSC user interface. Additionally, RSC users with the administrator role retain administrative privileges on the Rubrik clusters. + +The Activity Log on the Rubrik cluster displays the username and the domain IP address. + +Note: + +Federated access from RSC is available only on Rubrik clusters running Rubrik CDM version 5.3.2 or later. + +## Capabilities and required permissions + +Enabling federated access provides the following capabilities: + + * Seamless cluster access: Authorized RSC users and service accounts can access cluster interfaces from RSC and log in to clusters using their RSC credentials. Users must have the Enable cluster access permission and at least one more cluster configuration permission in RSC. + +Note: + +Existing RSC permissions map to equivalent permissions on each cluster to reduce redundancy. + + * NAS CD interface access: Users must have the Data management permissions on NAS CD, Enable cluster access permission, and at least one more cluster configuration permission to access the NAS CD interface. + * Direct snapshot download: Users and service accounts can download cluster snapshots directly from RSC. + + *[ > ]: and then diff --git a/saas_file_preparation_center.md b/saas_file_preparation_center.md new file mode 100644 index 0000000000000000000000000000000000000000..fe7c913ecb1fd1c779c91ec527bdad6d1ab4935f --- /dev/null +++ b/saas_file_preparation_center.md @@ -0,0 +1,16 @@ +# File preparation center + +Source: https://docs.rubrik.com/en-us/saas/saas/file_preparation_center.html + +--- + +# File preparation center + +The File Preparation Center tab on the Events page provides information about reports downloaded or sent to email recipients. + +The File Preparation Center lists reports downloaded or emailed to users in the past 24 hours. + +When a report is downloaded or sent to email recipients from the Reports page, the name of the report appears in a tray at the bottom of the screen. Clicking the View all items button on the tray opens the File Preparation Center tab. + +You can also use the download button located on the tray or in the File Preparation Center tab to download reports. + *[ > ]: and then diff --git a/saas_file_preparation_center_2.md b/saas_file_preparation_center_2.md new file mode 100644 index 0000000000000000000000000000000000000000..2dacb48dfc9dabd509f2e6a7906a937a32131bc6 --- /dev/null +++ b/saas_file_preparation_center_2.md @@ -0,0 +1,16 @@ +# File preparation center + +Source: https://docs.rubrik.com/en-us/saas/saas/file_preparation_center_2.html + +--- + +# File preparation center + +The File Preparation Center tab on the Events page provides information about reports downloaded or sent to email recipients. + +The File Preparation Center lists reports downloaded or emailed to users in the past 24 hours. + +When a report is downloaded or sent to email recipients from the Reports page, the name of the report appears in a tray at the bottom of the screen. Clicking the View all items button on the tray opens the File Preparation Center tab. + +You can also use the download button located on the tray or in the File Preparation Center tab to download reports. + *[ > ]: and then diff --git a/saas_file_preparation_center_details.md b/saas_file_preparation_center_details.md new file mode 100644 index 0000000000000000000000000000000000000000..416e20c8e442a064e93722eb7128bcf1b532e870 --- /dev/null +++ b/saas_file_preparation_center_details.md @@ -0,0 +1,28 @@ +# File preparation center details + +Source: https://docs.rubrik.com/en-us/saas/saas/file_preparation_center_details.html + +--- + +# File preparation center details + +The File Preparation Center tab contains details about the reports downloaded or sent to email recipients. + +Field | Description +---|--- +Name | The name of the report. +Identifier | The type of the file. + + * Report + * Email + + +Created On | The time when the operation was initiated. +Completed On | The time when the operation was completed. +Status | The status of the report. + + * Processing: The report is still being prepared. + * Ready To Download: The report is ready for download. + * Report Sent: The report has been sent to the specified email recipients. + + *[ > ]: and then diff --git a/saas_finding_ip_address.md b/saas_finding_ip_address.md new file mode 100644 index 0000000000000000000000000000000000000000..122ce9c89ea50d32781a85d4c29a702c5db8ddb6 --- /dev/null +++ b/saas_finding_ip_address.md @@ -0,0 +1,22 @@ +# Finding the RSC IP address + +Source: https://docs.rubrik.com/en-us/saas/saas/finding_ip_address.html + +--- + +# Finding the RSC IP address + +Locate the IP address of your RSC domain for various use cases. + +## Procedure + + 1. Log in to RSC. + 2. From the silhouette menu, select About Rubrik Security Cloud. + +The About Rubrik Security Cloud window appears. + + 3. Hover over the region link. + +## Results + +The list of IP addresses for your RSC domain appears. diff --git a/saas_finding_rsc_region.md b/saas_finding_rsc_region.md new file mode 100644 index 0000000000000000000000000000000000000000..2137d00a69a6eed942b696741ee64bff65787467 --- /dev/null +++ b/saas_finding_rsc_region.md @@ -0,0 +1,55 @@ +# Finding the RSC domain region + +Source: https://docs.rubrik.com/en-us/saas/saas/finding_rsc_region.html + +--- + +# Adding the initial account + +Use the instructions in the email sent by Rubrik to set up the initial account.# Adding the initial account + +Use the instructions in the email sent by Rubrik to set up the initial account. + +## Procedure + + 1. In the RSC set up email, click Continue. + +The Welcome to RSC login page appears. + + 2. In Email, enter the email address of the person who will be an owner for RSC. + +Use the address to which RSC sent the email. + + 3. In Password, enter a password for the new account. + +RSC accepts the password and activates the Login button. + + 4. Click Login. + +The Rubrik Security Cloud end user license agreement (EULA) appears. + + 5. Read the EULA, scrolling through to the end of the document. + 6. Click I accept these terms and conditions. + +## Results + +The account is created, and the RSC Dashboard page appears. + +# Finding the RSC domain region + +Find the region in which your RSC domain is running. + +## Procedure + + 1. Log in to RSC. + 2. From the account menu, select About Rubrik Security Cloud. + +The About Rubrik Security Cloud window appears. + +## Results + +RSC displays the region in which your RSC domain is running. + +## What to do next + +You can access the Rubrik Status page at to check the current status and the uptime history of the RSC domain. diff --git a/saas_fs_data_recovery_from_a_host_fileset.md b/saas_fs_data_recovery_from_a_host_fileset.md new file mode 100644 index 0000000000000000000000000000000000000000..21b763be0063a3b50219a15a5016f7bf5493a357 --- /dev/null +++ b/saas_fs_data_recovery_from_a_host_fileset.md @@ -0,0 +1,14 @@ +# Data recovery from a host fileset + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_data_recovery_from_a_host_fileset.html + +--- + +# Data recovery from a host fileset + +RSC allows recovering data from a host fileset. + +RSC allows recovery of the data that is backed up through a host fileset at any level of the hierarchical file system. You can select from the files and folders or search for a specific file for recovery. + +Data can be recovered from a host fileset by downloading the data, restoring the data to a specific location, overwriting the source data, and exporting the data to another host. + *[ > ]: and then diff --git a/saas_fs_exporting_fileset_snapshot_data.md b/saas_fs_exporting_fileset_snapshot_data.md new file mode 100644 index 0000000000000000000000000000000000000000..33ca058930a76e2515910265ce75b07ae2084307 --- /dev/null +++ b/saas_fs_exporting_fileset_snapshot_data.md @@ -0,0 +1,41 @@ +# Exporting fileset snapshot data + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_exporting_fileset_snapshot_data.html + +--- + +# Exporting fileset snapshot data + +Export files or folders from the fileset snapshot to a host that is different from the source host. + +## Before you begin + + * Confirm that the Rubrik Backup Service is installed and in a connected state on the target host. Then locate a fileset snapshot to recover, as described in [Locating a fileset snapshot for recovery](fs_locating_a_fileset_snapshot_for_recovery.html "Locate a fileset snapshot to recover data from the entire snapshot or from a selection of files and folders within the snapshot."), or search for a file or folder to recover, as described in [Searching for a file or folder for recovery](fs_searching_for_a_file_or_folder_for_recovery.html "Use the search capability to find a specific file or folder from a fileset snapshot for recovery."). + * If you are exporting to a secondary host, all Rubrik clusters connected to the host must be running CDM version 9.4.0 or later. All clusters that the host is connected to must be using the same version. + +## Procedure + + 1. On the Select Recovery Type page of the recovery wizard, select Export to a different host. + 2. In Export host, select a target host. + +The target host can be connected as a primary host or a secondary host. The target host must be different from the source host. + + 3. In Folder Path, enter the full path for a folder on the selected host. + +Note: + +The folder must already exist. The Rubrik cluster writes the exported data into the specified folder. + + 4. **Optional:** Select the required options: + +Option| Description +---|--- +Continue on restore errors | Selecting this option instructs the Rubrik cluster to continue the restore job after encountering a restore error. A restore error occurs when you cannot restore a file, folder, or symlink. Clearing this option instructs the Rubrik cluster to end the restore job when a restore error occurs. Files that were successfully restored before the error occurred remain on the restore target. +Restore on ACLs and extended attributes | Selecting this option enables the Rubrik cluster to restore only the Access Control Lists (ACLs) and extended attributes for all files, directories, and symlinks.ACLs are a set of rules that define permissions for individual users or groups, providing more granular security control beyond traditional file permissions.Extended attributes are metadata components associated with files and directories that can store additional information such as user-defined data, system metadata, or application-specific attributes. + + 5. Click Recover. + +## Results + +RSC initiates a task to write the fileset data to the target host at the location indicated by the export path. The Events tab on the local host page tracks the status of the task. + *[ > ]: and then diff --git a/saas_fs_fileset_protection_for_failover_clusters.md b/saas_fs_fileset_protection_for_failover_clusters.md new file mode 100644 index 0000000000000000000000000000000000000000..793b97122d1665ba4bacd664dea869a27d70737b --- /dev/null +++ b/saas_fs_fileset_protection_for_failover_clusters.md @@ -0,0 +1,28 @@ +# Fileset protection for failover clusters + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_fileset_protection_for_failover_clusters.html + +--- + +# Fileset protection for failover clusters + +RSC supports backup of hosts grouped into failover clusters through filesets. + +To enable data protection on failover clusters, RSC requires the failover cluster to associate with at least one service. The failover cluster service comprises of filesets that determine the file system paths on the failover cluster that need protection. RSC supports multiple services for each failover cluster. Each service can include multiple filesets to protect failover cluster data. + +You can manage fileset protection by assigning an SLA Domain to the failover cluster, by assigning different SLA Domains to each service corresponding to different filesets, or by assigning SLA Domains directly to the filesets. The SLA Domain of the failover cluster will protect the services and filesets that do not have assigned SLA Domains. + +RSC uses a virtual IP address (VIP) to identify each failover cluster service. Each failover cluster can support up to 32 nodes. Backups are taken from the active node. If failover occurs during a backup event, RSC automatically connects to the host on the new active node. All nodes in a protected failover cluster must be running the same OS type. For example, RSC does not support a failover cluster with both Windows and Linux hosts. + +Fileset protection for failover clusters is available only for Rubrik clusters running Rubrik CDM version 5.3 and later. RSC provides fileset cluster support for specific operating systems and services. + +Environment | Support +---|--- +OS | + + * Windows 2012, 2012 R2, 2016, 2019 (all 64-bit) + * RHEL 6 and 7 + + +Services | Veritas File Cluster and Windows Failover File Server as clustered applications + *[ > ]: and then diff --git a/saas_fs_fileset_protection_for_hosts.md b/saas_fs_fileset_protection_for_hosts.md new file mode 100644 index 0000000000000000000000000000000000000000..366c43b6a28a95c5e586549510364799864f4c70 --- /dev/null +++ b/saas_fs_fileset_protection_for_hosts.md @@ -0,0 +1,16 @@ +# Fileset protection for hosts + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_fileset_protection_for_hosts.html + +--- + +# Fileset protection for hosts + +The combination of a fileset with a host creates a protectable object referred to as a host fileset. + +RSC allows policy-based protection of a host fileset through SLA Domain assignment and manual protection through an on-demand backup. + +The ability to pair one host with several different filesets enables the protection of different set of data on a single host. + +The ability to protect each of the host and fileset combinations with a different SLA Domain permits different levels of protection for each set of data. + *[ > ]: and then diff --git a/saas_fs_filesets.md b/saas_fs_filesets.md new file mode 100644 index 0000000000000000000000000000000000000000..a1d4c7c2437c5d0da01538d8b51c1702c4dc5209 --- /dev/null +++ b/saas_fs_filesets.md @@ -0,0 +1,14 @@ +# Filesets + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_filesets.html + +--- + +# Filesets + +RSC manages the protection of folders and files on host computers through filesets. + +A fileset defines a set of files and folders on a host computer. The Rubrik cluster uses the filesets that are assigned to a host to determine the data to manage and protect through an SLA Domain. + +The Rubrik cluster interprets a fileset based on a set of rules that identify the files and folders to be protected on a host. The fileset rules accept full paths, path segments, and file names, which can be represented by regular expressions. + *[ > ]: and then diff --git a/saas_fs_filesystems.md b/saas_fs_filesystems.md new file mode 100644 index 0000000000000000000000000000000000000000..3e3437a2ad76b7b44989cf6c11f739617b35f741 --- /dev/null +++ b/saas_fs_filesystems.md @@ -0,0 +1,44 @@ +# File systems + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_filesystems.html + +--- + +# File systems + +RSC provides management and protection of file system data on supported Linux, Unix, and Windows hosts through filesets. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +A fileset is a template that defines the rules used to identify the files and folders to be protected on a host. + +Protection of file systems in RSC involves the following steps: + + 1. Associating a host with a Rubrik cluster + 2. Creating a fileset + 3. Associating the fileset with a host to create a host fileset + 4. Assigning an SLA Domain to the host fileset + +For Linux and Windows hosts, the supported operating systems can be running on physical hardware or on a supported virtual machine. For Unix, the supported operating systems can be running on physical hardware. + +The following table describes the features of file system protection supported by RSC. + +Feature | Description +---|--- +Fileset | Defines the data to manage and protect by specifying paths, path segments, and file types to include, exclude and exempt from exclusion. Valid fileset path statements must begin with one of the following: + + * Slash (/) + * Backslash (\\) + * A single uppercase or lower case alpha character followed immediately by a colon. For example, C: and e:. + +Wildcard characters represent one or more characters in a path or path segment. +Multiple filesets for each host | Provides granular protection by creating several different filesets for a host and assigning each host fileset to an individually selected SLA Domain. +Filesets stored on Pure Storage volumes on AIX hosts | Supports backup of filesets stored on Pure Storage FlashArray volumes on AIX hosts. +SLA Domains | Supports the same SLA Domain functionality that is provided for other workload types, including SLA rules and policies, for the protection of host filesets as well. +Backup indexing | The backup indexes data from a host fileset during ingest. This enables full file-level search and browsing of the backed up data when it is on the local Rubrik cluster, on the replication target, or at the archival location. +Fileset Cluster Backup | Supports fileset backups from clustered hosts. +Replication | Supports the assignment of an SLA Domain that has a replication policy to a host fileset to enable the replication of the data backed up from that fileset according to that policy. +Archiving | Supports the assignment of an SLA Domain that has an archival policy to a host fileset to enable the archival of the data backed up from that fileset according to that policy. +Restore to original location | Supports searching or browsing of the indexed host fileset backup to find and restore files and folders to the original location on the source host. +Export to a new location | Supports searching or browsing of the indexed host fileset backup to find and export files and folders to a known host running the same operating system variant (Linux, Unix, or Windows). +Download | Supports searching or browsing of the indexed host fileset backup to find and download files and folders from the snapshot. diff --git a/saas_fs_host_management_for_filesets.md b/saas_fs_host_management_for_filesets.md new file mode 100644 index 0000000000000000000000000000000000000000..0ed3ebe9bad2dbb7be0db95740d2cef14aafbea5 --- /dev/null +++ b/saas_fs_host_management_for_filesets.md @@ -0,0 +1,18 @@ +# Host management for filesets + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_host_management_for_filesets.html + +--- + +# Host management for filesets + +RSC supports protection of file system data on Windows, Linux, and Unix hosts. + +In order to protect file systems on a host, the Rubrik Backup Service (RBS) must be installed on the host. Subsequently, adding a host to the Rubrik cluster establishes a secure connection between the Rubrik cluster and the Rubrik Backup Service that is running on the host. After the host has been added, an entry for the host appears in RSC. + +The Rubrik cluster identifies the host by an IPv4 address or a resolvable hostname. When the IP address or the name of the host changes, you can edit the host information on the Rubrik cluster to reflect the new value. + +To stop protecting the data on a host, you can delete the host from the Rubrik cluster. Deleting a host removes that host from RSC. A removed host cannot be paired with a fileset and cannot be a target of an export. RSC moves the existing host filesets of the removed host and all associated backups to the Snapshots tab of the host. + +RSC provides the ability to filter the hosts by Rubrik cluster, fileset names, SLA Domains assigned to the filesets, RBS status, and protection status of the filesets. A search field is also available to find hosts by hostname or IP address. + *[ > ]: and then diff --git a/saas_fs_local_pages_for_fileset_objects.md b/saas_fs_local_pages_for_fileset_objects.md new file mode 100644 index 0000000000000000000000000000000000000000..de9645b188fd30298fae0a70181cb4b6a0afc51d --- /dev/null +++ b/saas_fs_local_pages_for_fileset_objects.md @@ -0,0 +1,12 @@ +# Local pages for fileset objects + +Source: https://docs.rubrik.com/en-us/saas/saas/fs_local_pages_for_fileset_objects.html + +--- + +# Local pages for fileset objects + +The local pages of a fileset host and a failover cluster service provide detailed information about tasks related to protecting filesets and managing available snapshots. + +In an environment with an individual host, filesets must be associated with a host to enable file system data protection on the host. Similarly, in an environment with a failover cluster that groups multiple hosts, filesets must be associated with a failover cluster service to enable file system data protection on the failover cluster hosts. As a result, the local pages for a fileset host and a failover cluster service provide similar information. + *[ > ]: and then diff --git a/saas_global_dashboard_required_permissions.md b/saas_global_dashboard_required_permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..abd17f697cfa9d8e96308e0a9047db23a80516b4 --- /dev/null +++ b/saas_global_dashboard_required_permissions.md @@ -0,0 +1,18 @@ +# Global Dashboard required permissions + +Source: https://docs.rubrik.com/en-us/saas/saas/global_dashboard_required_permissions.html + +--- + +# Global Dashboard required permissions + +User accounts must have specific permissions to view the RSC dashboard. + +Category | Privilege +---|--- +Data management | View privilege for all current and future data sources +System configuration | View privilege for clusters +View privilege for system and non-system events +View and create reports +Rubrik applications | View data classification + *[ > ]: and then diff --git a/saas_healthcare_dashboard.md b/saas_healthcare_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..a9f495a9265eaa348fd0d8fefb055f564212ef1d --- /dev/null +++ b/saas_healthcare_dashboard.md @@ -0,0 +1,24 @@ +# Healthcare dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/healthcare_dashboard.html + +--- + +# Healthcare dashboard + +The Healthcare dashboard provides a unified view of data protection, compliance, and recoverability for the entire Epic ecosystem. + +Epic admins typically manage backups for the IRIS ODB due to their domain expertise and also handle analytics databases such as Clarity and Caboodle and also Web Blob files that are stored on NAS. Their primary focus is to ensure backup performance, seamless code upgrades, and consistent backup success, all while emphasizing cyber resiliency and recovery. + +The Healthcare dashboard provides an overview of healthcare data, displaying backup duration, capacity trends, daily compliance, and recent recoveries for the selected objects in RSC. + +The Dashboard dropdown list helps users navigate to the Healthcare dashboard. The Healthcare dashboard contains three tabs representing the three object types. + + * IRIS ODB: Corresponds to Linux and Unix filesets. + * Clarity and Caboodle DB: Corresponds to Oracle and MySQL filesets. + * Web Blob: Corresponds to NAS shares and Windows filesets. + +You can filter the dashboard view by selecting the object and the time range. You can filter only one object at a time for IRIS ODB and Web Blob, but you can select multiple databases for Clarity and Caboodle DB. You can choose either a predefined time range or set a custom time range. + +The Healthcare dashboard does not support pulling widgets from other dashboards. However, you can add or remove widgets within the dashboard or have multiple copies of the same widgets. + *[ > ]: and then diff --git a/saas_healthcare_dashboard_widgets.md b/saas_healthcare_dashboard_widgets.md new file mode 100644 index 0000000000000000000000000000000000000000..f450e469dc5991e163d7c6597d4d6bf2d538796e --- /dev/null +++ b/saas_healthcare_dashboard_widgets.md @@ -0,0 +1,43 @@ +# Healthcare dashboard widgets + +Source: https://docs.rubrik.com/en-us/saas/saas/healthcare_dashboard_widgets.html + +--- + +# Healthcare dashboard widgets + +The Healthcare dashboard provides information about data backup duration, capacity trends over time, daily compliance patterns, and the recent data recoveries for the selected objects. + +Widget | Description +---|--- +Backup Duration | Displays the average time taken for backups that were either successful or had warnings over the past six months. +Backup Duration Stats | Displays an overview of backup duration statistics for the set time range. This includes the following details: + + * Latest duration + * Change in duration + * Average duration + + +Capacity Over Time | Displays the storage capacity usage over time. Capacity can be evaluated in three contexts: + + * Logical Object Capacity: Displays the volume of storage available. + * Local Storage Used: Displays the volume of storage consumed. + * Protected Objects: Displays the count of the objects protected in the selected databases or objects. + + +Capacity Stats | Displays an overview of storage capacity usage statistics for the set time range. This includes the following details: + + * Current size (logical) + * Current size (local) + * Change in logical size + + +Daily Compliance Trend | Displays the number of data objects in compliance or out of compliance within the past 24 hours over the last seven days. +Latest Successful Recovery Stats | Displays the status of the most recent successful or successful with warning recovery. This includes the following details: + + * Latest Recovery: Displays the duration of the most recent recovery. + * Latest Data Transferred: Displays the data transferred during the most recent recovery. + + +Last 25 Recoveries | Displays a detailed overview of the last 25 recoveries. You can customize the view of this table. + *[ > ]: and then diff --git a/saas_hyper_v_azure_stack_hci_limitations.md b/saas_hyper_v_azure_stack_hci_limitations.md new file mode 100644 index 0000000000000000000000000000000000000000..9a1e8e1d33d3af23f3ef99d00aae895a7a4eab63 --- /dev/null +++ b/saas_hyper_v_azure_stack_hci_limitations.md @@ -0,0 +1,18 @@ +# Azure Local limitations + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/azure_stack_hci_limitations.html + +--- + +# Azure Local limitations + +Recovering virtual machines to an Azure Local (Azure Stack HCI) has certain limitations, but these limitations have workarounds. + +When you restore a virtual machine using Live Mount or export a virtual machine to an Azure Local cluster, you must select a host as the target. And when you attempt to manage that host using cluster management in Windows Admin Center for Azure Local, the restored virtual machine is not a clustered virtual machine and does not appear under Virtual Machines in Cluster Manager. The restored virtual machine only appears under Virtual Machines on the server that you restored it to in the Server Manager view. + +As a workaround, you can enable the clustered role for the recovered virtual machine directly using the following PowerShell command. + +"Get-VM -Name *Rubrik-recovered-vm-name* | Add-ClusterVirtualMachineRole" + +Microsoft documentation provides more information about the PowerShell command. + *[ > ]: and then diff --git a/saas_hyper_v_azure_stack_hci_overview.md b/saas_hyper_v_azure_stack_hci_overview.md new file mode 100644 index 0000000000000000000000000000000000000000..bd20a27a4e65b444ee71aefbe414dd2eeeee3388 --- /dev/null +++ b/saas_hyper_v_azure_stack_hci_overview.md @@ -0,0 +1,26 @@ +# Azure Local overview + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/azure_stack_hci_overview.html + +--- + +# Azure Local overview + +With RSC, you can protect on-premises Microsoft workloads and Azure Local (Azure Stack HCI) resources in a unified control plane and provide insight into critical data. + +Azure Local is a platform for running on-premises or edge workloads using hyper-converged compute nodes. With growing cloud computing needs, each of these nodes expands the cluster, adding CPU, memory, and storage resources with no downtime. You can manage Azure Local using Azure Arc and Windows Admin Center (WAC). + +Rubrik Data Resilience provides essential security features for your Azure Local workloads. With an immutable file system, your data remains safe from any tampering attempts. Moreover, backups are protected with a logical air gap, meaning no one can access them over any network protocol. This extra layer of security ensures that your data is not discoverable over the network. Additionally, the RSC platform enforces multi-factor authentication, temporary one-time passwords, retention lock, and two-person rules, ensuring that critical data remains secure. + +Completing the Azure Local onboarding steps provides the following benefits: + + * Rubrik Data Observability enables you to restore your protected Azure Local data. + * Data Security Posture ensures protection for any sensitive data containing regulated financial or personal health information. + * Data Threat Analytics determines the blast radius of a ransomware event down to the individual file level and correlates it with Data Security Posture to determine if your sensitive data was targeted. + * Rubrik Threat Hunting capabilities enable you to scan historical recovery points to determine the point in time when indicators of compromise (IOCs) first appeared, ensuring that your restored environment is safe from reinfection. + * Rubrik Data Remediation capabilities enable you to recover the protected Azure Local data. + * Rubrik Threat Containment enables you to quarantine a ransomware infection and ensure safe and quick data recovery. + * Rubrik Mass Recovery enables you to restore applications or individual files with surgical precision. + * Rubrik Recovery Time Objective (RTO) is fast and reliable and enables you to Live Mount for near zero RTO. + + *[ > ]: and then diff --git a/saas_hyper_v_excluding_hyperv_vhd_files.md b/saas_hyper_v_excluding_hyperv_vhd_files.md new file mode 100644 index 0000000000000000000000000000000000000000..5d3b1d376bc4e8f940460944068ba448778415b9 --- /dev/null +++ b/saas_hyper_v_excluding_hyperv_vhd_files.md @@ -0,0 +1,37 @@ +# Excluding Hyper-V virtual machine VHD files + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/excluding_hyperv_vhd_files.html + +--- + +# Excluding Hyper-V virtual machine VHD files + +Among the VHD files on a virtual machine, some VHD files might not require a backup. Exclude these VHD files from the backup, thereby reducing the size of the snapshots. + +## About this task + +Virtual machines sometimes include some VHD files that do not need to be protected. RSC can ignore some of the VHD files of a virtual machine while protecting other VHD files on that virtual machine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + 4. Click the Hyper-V VM card. + 5. Select a virtual machine. + +The local host page for the virtual machine appears. + + 6. Open the ellipsis menu and select Exclude VHDs. + +The size column displays the space occupied by the VHD file on the Hyper-V host. For dynamically expanding disks, the occupied space should be less than the maximum disk size. + +The Exclude VHDs from Snapshots dialog box appears. + + 7. Select the disks to exclude from snapshots. + 8. Click Exclude. + +## Results + +RSC excludes the selected VHD files from all future backups of the virtual machine. + *[ > ]: and then diff --git a/saas_hyper_v_hyperv_host_management.md b/saas_hyper_v_hyperv_host_management.md new file mode 100644 index 0000000000000000000000000000000000000000..390b42c4c0c876320cf494f0325a1f559379cc6e --- /dev/null +++ b/saas_hyper_v_hyperv_host_management.md @@ -0,0 +1,16 @@ +# Hyper-V host management + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/hyperv_host_management.html + +--- + +# Hyper-V host management + +After installing the Rubrik Backup Service software on a Hyper-V host, adding a host to the Rubrik cluster establishes a secure connection between the Rubrik cluster and the Rubrik Backup Service that is running on the host. + +Adding a host to the Rubrik cluster establishes a secure connection between the Rubrik cluster and the Rubrik Backup Service running on the host. + +The Rubrik cluster identifies the host by an IPv4 address or a resolvable hostname. When the value that is used to identify a host changes, you can edit the host information on the Rubrik cluster to reflect the new value. + +To stop managing the data on a host, you can delete the host from the Rubrik cluster. A removed host cannot be paired with a fileset and cannot be a target of an export. The Rubrik cluster moves the existing host filesets of the removed host and all associated backups to the Retention Management page. + *[ > ]: and then diff --git a/saas_hyper_v_hyperv_retention.md b/saas_hyper_v_hyperv_retention.md new file mode 100644 index 0000000000000000000000000000000000000000..6ceb7c3fdb3a8371f8cf9149f185c35514c5526d --- /dev/null +++ b/saas_hyper_v_hyperv_retention.md @@ -0,0 +1,12 @@ +# Hyper-V archival snapshot retention + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/hyperv_retention.html + +--- + +# Hyper-V archival snapshot retention + +The retention period assigned to the archival snapshot by the associated SLA Domain determines the expiration of an archival snapshot. + +To ensure existing snapshots are always fully functional, the Rubrik cluster combines any required data from expired incremental snapshots into the chain of existing incremental snapshots. This permits each retained archival snapshot to be mounted as a fully functional virtual machine. After the expiration of the retention period, the Rubrik cluster marks the archival snapshot as expired and moves the snapshot data to garbage collection. + *[ > ]: and then diff --git a/saas_hyper_v_hyperv_sla_domain_assignment.md b/saas_hyper_v_hyperv_sla_domain_assignment.md new file mode 100644 index 0000000000000000000000000000000000000000..fe650b11e094c7a8402c0b74214b2de2a1a6fa89 --- /dev/null +++ b/saas_hyper_v_hyperv_sla_domain_assignment.md @@ -0,0 +1,19 @@ +# Hyper-V SLA Domain assignment + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/hyperv_sla_domain_assignment.html + +--- + +# Hyper-V SLA Domain assignment + +Provide protection for a virtual machine through an SLA Domain. + +You can protect a virtual machine can by assigning an SLA Domain setting individually to the virtual machine. You can also protect a virtual machine can also be protected by deriving an SLA Domain setting through automatic protection. + +Automatic protection occurs in one of the following ways: + + * An administrator assigns an object that contains the virtual machine to an SLA Domain. + * An administrator moves the virtual machine into the hierarchy of an object that is assigned to an SLA Domain. + +Automatic protection uses the automatic protection rules to determine whether a setting applies to an object. + *[ > ]: and then diff --git a/saas_hyper_v_hyperv_virtual_machines.md b/saas_hyper_v_hyperv_virtual_machines.md new file mode 100644 index 0000000000000000000000000000000000000000..54ff3a9ca67e08120b2dab2057a9821a2af412a6 --- /dev/null +++ b/saas_hyper_v_hyperv_virtual_machines.md @@ -0,0 +1,21 @@ +# Hyper-V virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/hyperv_virtual_machines.html + +--- + +# Hyper-V virtual machines + +A Rubrik cluster provides data management and protection for virtual machines that are deployed in a Microsoft Hyper-V environment. The Rubrik cluster can manage and protect virtual machines in an environment with multiple Hyper-V servers and virtual machines. + +Rubrik invokes the Windows Management Instrumentation (WMI) APIs to communicate with the hypervisor directly for a first full and forever incremental set of backups through Resilient Change Tracking (RCT). There is no requirement to have SCVMM installed in your environment. + +SLA policies can be applied anywhere in the hierarchy stack: the SCVMM host, the cluster, host, or virtual machine levels. The Rubrik cluster provides a variety of methods to recover virtual machines and to restore protected data. Recover virtual machines and restore data by using local snapshots, replicas, and archived snapshots. + +Hyper-V environments require Rubrik Backup Service (RBS) installation on the server, but it is optional for virtual machines. + +Virtual machines can be recovered and protected on any operating system. However, the operating system on the virtual machine must support RBS. + +RBS is a connector that self manages after initial deployment. + +Hyper-V host refers to a Windows Server with the Hyper-V role installed. diff --git a/saas_hyper_v_hyperv_vm_protection.md b/saas_hyper_v_hyperv_vm_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..727e592dd4a829027bcad19f6bce65eaf69bb215 --- /dev/null +++ b/saas_hyper_v_hyperv_vm_protection.md @@ -0,0 +1,16 @@ +# Hyper-V virtual machine protection + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/hyperv_vm_protection.html + +--- + +# Hyper-V virtual machine protection + +Rubrik clusters can protect virtual machines based on a direct SLA Domain assignment or based on inheritance of the SLA Domain assigned to the parent object. + +A Rubrik cluster provides protection for virtual machines through either individual assignment of the virtual machine to an SLA Domain or through automatic protection. Automatic protection occurs when the virtual machine derives the SLA Domain assignment of a containing folder, cluster, or host. + +The Rubrik cluster provides flexibility in the protection assignments made for virtual machines. Virtual machines that are protected by individual assignment can be set to Don't protect or can be set to inherit a protection setting. + +An individual virtual machine, which is part of a group of virtual machines being automatically protected, can be set to Don't protect, without moving the virtual machine out of the group. + *[ > ]: and then diff --git a/saas_hyper_v_local_host_page_hyperv.md b/saas_hyper_v_local_host_page_hyperv.md new file mode 100644 index 0000000000000000000000000000000000000000..255587a8825dcc3a6fc886848060b992b284a846 --- /dev/null +++ b/saas_hyper_v_local_host_page_hyperv.md @@ -0,0 +1,12 @@ +# Local Hyper-V host page + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/local_host_page_hyperv.html + +--- + +# Local Hyper-V host page + +The local host page provides detailed information about the protection of a virtual machine, and tasks related to the virtual machine. + +The local host page displays details about virtual machines and gives access to tasks that you can perform for virtual machines. + *[ > ]: and then diff --git a/saas_hyper_v_recovery_and_restore_vm_data.md b/saas_hyper_v_recovery_and_restore_vm_data.md new file mode 100644 index 0000000000000000000000000000000000000000..d71806a6f27959d37fcc857e83b6a7ed1d6a8d3b --- /dev/null +++ b/saas_hyper_v_recovery_and_restore_vm_data.md @@ -0,0 +1,26 @@ +# Hyper-V virtual machine recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/recovery_and_restore_vm_data.html + +--- + +# Hyper-V virtual machine recovery + +You can recover virtual machines and restore data by using any Rubrik data protection object and using an available recovery action. + +You can recover virtual machines and restore data by using snapshots, replicas, and archival snapshots. + +The Rubrik cluster provides the following recovery actions for virtual machines: + + * Instant Recovery + * Live Mount + * Export + * Mount virtual disks + * Download VM-level files + +When snapshot data exists in a snapshot and in an archival snapshot, the cluster uses the local snapshot to recover a virtual machine or to restore data. By using the local snapshot, the cluster reduces network impact and eliminates any archival data recovery charges associated with a recovery operation or with a restore operation. + +Recovery using a replica cannot use the Instant Recovery, Mount Virtual Disks, or Download VM Files actions. + +You can recover a virtual machine by using any of the Rubrik data protection objects: snapshots, replicas, or archival snapshots. + *[ > ]: and then diff --git a/saas_hyper_v_rubrik_backup_service_scvmm.md b/saas_hyper_v_rubrik_backup_service_scvmm.md new file mode 100644 index 0000000000000000000000000000000000000000..f93a585f02d0ba0fb6f8b602abe0f8f756983f04 --- /dev/null +++ b/saas_hyper_v_rubrik_backup_service_scvmm.md @@ -0,0 +1,31 @@ +# Rubrik Backup Service for Hyper-V + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/rubrik_backup_service_scvmm.html + +--- + +# Rubrik Backup Service for Hyper-V + +The Rubrik Backup Service provides enhanced integration with protected resources and host systems. + +The Rubrik cluster that provides the download for the RBS software package installed to the host is the initial primary Rubrik cluster for that host. Primary Rubrik clusters provide the following functionality that is not available for secondary Rubrik clusters: + + * Communication and backup activity is restricted to the primary Rubrik cluster. + * Secondary Rubrik clusters do not receive updates on host information or status. + +Only Rubrik clusters that replicate to or from the primary Rubrik cluster can register as secondary Rubrik clusters. RBS instances that connect through Envoy virtual machines or that are running on SCVMM cannot register with multiple Rubrik clusters. Multi-cluster RBS is not supported for replicated Rubrik clusters configured as Archival Readers. + +Rubrik can protect any Hyper-V virtual machine, regardless of the operating system. For file level recovery of Hyper-V virtual machines, the operating system of the virtual machine needs to support installation of RBS. + +Refer to Compatibility Matrix for information about which operating system supports RBS installation. + +## RBS for Hyper-V without SCVMM + +For Hyper-V without SCVMM, the Rubrik cluster uses the same Rubrik Backup Service software that is used for Windows file system protection. + +For failover Rubrik clusters, the connector should be installed on all hosts and each host should be added to Rubrik individually. + +## RBS for Hyper-V with SCVMM + +Download and install of RBS for Hyper-V hosts with SCVMM requires separate tasks. + *[ > ]: and then diff --git a/saas_hyper_v_scvmm_prerequisites.md b/saas_hyper_v_scvmm_prerequisites.md new file mode 100644 index 0000000000000000000000000000000000000000..9111c7ea1a6b3878877eee2fbdec7efe9bbbb903 --- /dev/null +++ b/saas_hyper_v_scvmm_prerequisites.md @@ -0,0 +1,19 @@ +# Prerequisites for System Center Virtual Machine Manager + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/scvmm_prerequisites.html + +--- + +# Prerequisites for System Center Virtual Machine Manager + +Microsoft provides SCVMM hosts to manage virtual machines across multiple hosts. The Rubrik Backup Service should be installed on all hosts running SCVMM. + +The following prerequisites are required for SCVMM hosts supported by Rubrik: + + * Hyper-V Server 2016 or newer + * Hyper-V host and Rubrik cluster must be part of the same Active Directory domain + * "Run As" account that is a member of the local Administrators group or a member of the Domain Admins group on the Hyper-V Server being managed + * For versions of Hyper-V that are older than Hyper-V 2016, use volume snapshots, or install the Rubrik Backup Service on each virtual machine + +RSC does not support SCVMM deployed in a high availability configuration. + *[ > ]: and then diff --git a/saas_hyper_v_unmanaged_data.md b/saas_hyper_v_unmanaged_data.md new file mode 100644 index 0000000000000000000000000000000000000000..4a0b477be906bafa440352ac7a2f566121169e0a --- /dev/null +++ b/saas_hyper_v_unmanaged_data.md @@ -0,0 +1,12 @@ +# Unmanaged data + +Source: https://docs.rubrik.com/en-us/saas/saas/hyper_v/unmanaged_data.html + +--- + +# Unmanaged data + +RSC supports managing file system and application data that is not subject to a retention policy. + +The Rubrik cluster defines backups and snapshots that do not have a retention policy as unmanaged snapshot objects. Unmanaged snapshot objects can be managed through RSC. + *[ > ]: and then diff --git a/saas_identity_inventory_prereqs_limitations.md b/saas_identity_inventory_prereqs_limitations.md new file mode 100644 index 0000000000000000000000000000000000000000..c13caa0c6c6ae1ca94e1d438c28c28693381ff22 --- /dev/null +++ b/saas_identity_inventory_prereqs_limitations.md @@ -0,0 +1,29 @@ +# Identity Inventory prerequisites and limitations + +Source: https://docs.rubrik.com/en-us/saas/saas/identity_inventory_prereqs_limitations.html + +--- + +# Identity Inventory prerequisites and limitations + +Enabling the Identity Inventory to view user activity and sensitive file activity has specific requirements and limitations. + +The Identity Inventory is available as part of Rubrik Data Security Posture Management. + +Enabling the Identity Inventory has specific prerequisites according to the workload. + +Workload | Prerequisite +---|--- +Active Directory | + * Configuring audit logs on all folders and files across all objects for monitoring. Configuring audit logs for the Authenticated Users or Everyone principals includes system services that might create large size logs. Rubrik recommends using the Domain Users principal when enabling audit logs. The Audit Log section in the Microsoft documentation provides more information on enabling audit logs. You can also contact Rubrik Support for assistance with enabling audit logs. + * Upgrading to Rubrik CDM version 9.0.3, 9.1.1, or later on Rubrik clusters. + * Enabling Active Directory (AD) backup on the Rubrik cluster. + * Enabling LDAP configuration on the Rubrik cluster. +Microsoft 365 OneDrive and SharePoint | Enabling Entra ID backups. + +The Identity Inventory on RSC has the following limitations: + * The Identity Inventory requires a minimum retention period of one day for the AD workloads. + * RSC supports the Identity Inventory for a maximum of 10,000 identities with access to sensitive information. + +RSC supports the Identity Inventory for a maximum of 20,000 Entra ID identities with access to sensitive information. + *[ > ]: and then diff --git a/saas_import_users_roles_rsc.md b/saas_import_users_roles_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..8a43da67c2e4fe7ca2967c465189adb304751db7 --- /dev/null +++ b/saas_import_users_roles_rsc.md @@ -0,0 +1,41 @@ +# Import users and roles to RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/import_users_roles_rsc.html + +--- + +# Import users and roles to RSC + +You can import users and roles created on the Rubrik cluster to manage them on RSC. After import, you can view the CDM RBAC migration summary report for confirmation or for further changes to users and roles. + +Users and roles created on a Rubrik cluster can be imported to RSC on a cluster basis. Importing users and roles creates new RSC roles for each applicable Rubrik cluster. + +You can import users and roles by using the Import Users, Roles, and SSO Configurations wizard in RSC. In the wizard, you can view a list of available Rubrik clusters, users, and SSO groups along with their import status. The wizard imports all available users and roles. + +Rubrik recommends completing the following tasks before starting the import process: + + * Removing users and roles that are not in use from Rubrik clusters + * Ensuring that all users have unique and valid email addresses + +After import, you can view the CDM RBAC migration summary report in the cluster selection step of the Import Users, Roles, and SSO Configurations wizard for confirmation or for further changes to users and roles. The report is also available in the File Preparation Center in the RSC for 24 hours if you opt to download the report in the import wizard. The CDM RBAC migration summary report provides the following information: + + * Imported users with their role assignments + * Imported roles with their RSC permissions + * Users that could not be imported with their role assignments + * SSO groups that could not be imported with their role assignments + * Roles that could not be imported + +The Rubrik cluster must be running CDM version 7.0 or later for importing users and roles to RSC using the wizard. + +Importing SSO groups to RSC is not supported. You must manually create those SSO groups in RSC after the migration has occurred. You can use the migration summary report to view the SSO groups that need to be manually created and the roles that must be assigned to the SSO groups. + +If you are using SSO on the Rubrik cluster, recreating your configuration and groups in RSC involves the following actions: + + * Connecting your SSO (SAML 2.0 IdP) to RSC + * Adding your SSO groups to RSC + * Mapping your SSO groups to the newly created roles in RSC + +Refer to the Rubrik Security Cloud Migration Guide for more information. + +RSC does not directly support LDAP for authentication. If you are using LDAP to authenticate to the Rubrik cluster, a SAML 2.0-based SSO federation solution is required to connect RSC to your LDAP service. + *[ > ]: and then diff --git a/saas_initiating_advanced_threat_hunt.md b/saas_initiating_advanced_threat_hunt.md new file mode 100644 index 0000000000000000000000000000000000000000..33f6ab20e007481f021246056895952c339891a4 --- /dev/null +++ b/saas_initiating_advanced_threat_hunt.md @@ -0,0 +1,90 @@ +# Initiating an advanced threat hunt + +Source: https://docs.rubrik.com/en-us/saas/saas/initiating_advanced_threat_hunt.html + +--- + +# Initiating an advanced threat hunt + +Initiate an advanced threat hunt to scan Rubrik backups for Indicators Of Compromise and identify files at risk. Advanced threat hunt does not support cloud workloads. An advanced threat hunt supports all three IOC types: YARA rule, files hash, and file pattern. + +## Before you begin + +To perform a threat hunt, you must first enable Threat Monitoring for the required clusters and cloud accounts. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click Start Threat Hunt. + +The Start a Threat Hunt wizard appears. + + 5. Select Advanced Threat Hunt and click Next. + +The Advanced Hunt page appears. + + 6. Select the objects to scan for threats and click Next. + +You can use the filters to sort by object type, Rubrik cluster, replication type, SLA Domain, or status. You can also search for objects by using the search bar. + +The scan time depends on the number and type of objects selected. + +The Add IOCs page appears. + + 7. Click \+ Add IOC to add an IOC. + +The Add an IOC page appears. + + 8. Select the type of IOC you want to use for the threat hunt. + 9. **Optional:** Enter the threat family name. + 10. Define the IOC for the threat hunt and click Add. + +You can include up to ten IOCs in a threat hunt. + +RSC adds the IOC for the threat hunt. + + 11. In Threat Hunt Name, enter a name for the threat hunt. + 12. In Time Range, select a time frame for the threat hunt and click Next. + +Time range| Description +---|--- +Most recent snapshot only | Select to scan only the most recent snapshot for the hunt. +Custom time range | Select a time range for the threat hunt. + +You can configure the maximum number of snapshots with the Custom time range option to optimize performance. The limit will be the latest snapshot in the time range. The default value is 10. + +Rubrik recommends limiting the number of snapshots scanned for each object for optimal performance. + +The Configure Filters page appears. + + 13. **Optional:** Click Auto-Populate Fields to use the default values for limits. + 14. In Limits, select limits on the number of IOC matches, file sizes to scan, and the creation and modification times of the file. + +For the IOC match limit, the default value is 1. Increasing the IOC count from the default of 1 IOC slows down the scan. + +For the maximum file size to scan, the default value is 1024 KB. The highest value that you can enter is 15,000 KB, or 15 MB. + + 15. In Inclusions and Exclusions, add file extensions, paths, and patterns to include, exclude, and to not exclude from this hunt. + +The default values are: *.acm, *.ax, *.cpl, *.dll, *.drv, *.efi, *.exe, *.mui, *.ocx, *.scr, *.sys, and *.tsp. You can modify these for best results. + + 16. Click Next. + +The Confirmation page appears. + + 17. Review the parameters of the threat hunt and click Start. + +A confirmation message indicates that RSC has initiated a threat hunt. + +## Results + +RSC initiates the advanced threat hunt with the selected IOCs to identify files at risk. + *[ > ]: and then diff --git a/saas_initiating_turbo_threat_hunt.md b/saas_initiating_turbo_threat_hunt.md new file mode 100644 index 0000000000000000000000000000000000000000..4b1fdfa093df4493c534ed56ab93e50b78bf8970 --- /dev/null +++ b/saas_initiating_turbo_threat_hunt.md @@ -0,0 +1,78 @@ +# Initiating a turbo threat hunt + +Source: https://docs.rubrik.com/en-us/saas/saas/initiating_turbo_threat_hunt.html + +--- + +# Initiating a turbo threat hunt + +A turbo-charged threat hunt scans for hashes of file types most often used by threat agents. You can initiate this scan on both Rubrik clusters and cloud accounts. + +## Before you begin + +Enabling Threat Monitoring is a requirement for initiating a turbo threat hunt. This is because a turbo threat hunt uses hash scans, which are only populated after the Threat Monitoring scans are complete. + +When enabling Threat Monitoring for the first time, ensure that it completes an initial scan of all your workloads before starting the turbo threat hunt. You can verify the status of the scan from the Event Logs page. + +## About this task + +Turbo threat hunt only scans file hashes. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click Start Threat Hunt. + +The Start a Threat Hunt wizard appears. + + 5. Select Turbo Threat Hunt and click Next. + +The Turbo Hunt page appears. + + 6. In Select Clusters and Cloud Accounts, select an option to choose all or specific clusters and cloud accounts: + * Select all existing eligible clusters and cloud accounts + * Select specific eligible clusters and cloud accounts + +When you select the Select specific eligible clusters and cloud accounts option, a list of clusters and cloud accounts appears. You can select the required clusters and cloud accounts from this list. + + 7. Click Next. + +The Enter Hashes page appears. + + 8. Enter comma-separated file hashes and click Next. + +The Threat Hunt Details page appears. + + 9. In Threat Hunt Name, enter a name for the threat hunt. + 10. In Time Range, select a time range for the threat hunt. + +Time range| Description +---|--- +All Snapshots | Select to scan all snapshots of each object in the selected cluster for the hunt. +Most Recent Snapshot only | Select to scan only the most recent snapshot of each object for the hunt. +Custom Time Range | Select to scan all snapshots of each object taken during a specific time range for the threat hunt. + +You can configure the maximum number of snapshots within a custom time range to optimize performance. The limit will be the latest snapshot in the time range. The default value is 10. + +Rubrik recommends limiting the number of snapshots scanned for each object for optimal performance. + + 11. Click Next. + +The Confirmation page appears. + + 12. Review the parameters of the threat hunt and click Start. + +A confirmation message indicates that RSC has initiated a threat hunt. + +## Results + +RSC initiates the turbo threat hunt to identify files at risk for the selected clusters and cloud accounts. + *[ > ]: and then diff --git a/saas_integration_third_party_apps_in_rsc.md b/saas_integration_third_party_apps_in_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..dc7d4fda8c3c442bce15f6c9b6bba933bdd7607b --- /dev/null +++ b/saas_integration_third_party_apps_in_rsc.md @@ -0,0 +1,14 @@ +# Integration of third-party applications in RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/integration_third_party_apps_in_rsc.html + +--- + +# Integration of third-party applications in RSC + +You can access the Integrations page to configure and manage your third-party SaaS integrations in RSC. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Using the Integrations page in RSC, you can streamline and manage your third-party applications in one place, allowing you to configure and manage all your integrations seamlessly. For instance, the Zscaler integration in RSC helps you to identify sensitive data objects and prevent any unauthorized transfer of your most critical data by leveraging the Rubrik Data Security Posture and Zscaler Data Loss Prevention services. + *[ > ]: and then diff --git a/saas_investigating_ri_anomalies.md b/saas_investigating_ri_anomalies.md new file mode 100644 index 0000000000000000000000000000000000000000..a152ab0c95952bb54e70b2ace01ac95589548245 --- /dev/null +++ b/saas_investigating_ri_anomalies.md @@ -0,0 +1,31 @@ +# Investigating Anomalies + +Source: https://docs.rubrik.com/en-us/saas/saas/investigating_ri_anomalies.html + +--- + +# Investigating Anomalies + +Investigate anomalous incidents and recover selected files from the Data Threat Analytics Anomalies page. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. On the navigation bar, click **Anomaly Detection**. + +The Anomaly Detection page appears. + + 4. Click on a file set. + +The page opens on the Browse tab. + + 5. Click within the file set to view the file shares with the anomalous data. + +## Results + +The suspicious, deleted, and added files for the selected file set appears. + *[ > ]: and then diff --git a/saas_legal_hold_snapshot_rtn_3.md b/saas_legal_hold_snapshot_rtn_3.md new file mode 100644 index 0000000000000000000000000000000000000000..40703cf2f6405f89d896c4c432619a9c6de1ac75 --- /dev/null +++ b/saas_legal_hold_snapshot_rtn_3.md @@ -0,0 +1,38 @@ +# Legal hold for snapshot retention + +Source: https://docs.rubrik.com/en-us/saas/saas/legal_hold_snapshot_rtn_3.html + +--- + +# Legal hold for snapshot retention + +Legal hold ensures that snapshots are retained indefinitely until the hold is removed, overriding the scheduled expiry of an SLA Domain policy. This ensures that snapshots are available as long as necessary to meet legal obligations. + +Legal hold is a feature that preserves snapshots indefinitely and is designed to retain specific backups in order to meet legal requirements. When a snapshot is placed on legal hold and assigned an SLA Domain with an archival policy, an additional copy of the snapshot is stored in the archival location. Snapshots under legal hold do not expire regardless of the SLA Domain policy, and the snapshots cannot be removed from the system. Placing a legal hold on a snapshot does not prevent the administrator from recovering files or downloading a CSV file from the snapshot. + +Note: + +Only data center workloads support legal hold. + +Legal hold does not apply to the following workloads and snapshots: + + * Log backups of SQL Server databases + * Log backups of Oracle databases + * Managed Volumes + * Snapshots of direct archive filesets + +During the replication of snapshots, the legal hold status is not automatically propagated to the replicated snapshot. However, you can choose to manually place a legal hold on the replicated snapshots to ensure they are retained to meet the compliance requirements. + +When placing a snapshot on legal hold, a user with Place and remove legal hold privilege can choose to: + + * Place legal hold on snapshots. + * Remove legal hold from snapshots. + * Retain the snapshot at both the local and archival locations. + * Retain the snapshot only at the locations with the longest retention period. + +When you select the option to retain the local snapshot until legal hold is removed, the local cluster will retain the snapshot until the legal hold is removed. If an SLA Domain specifies an archival location, the archived snapshot is placed on legal hold by default. If no archival location is specified, the local snapshot is placed on legal hold. + +Removing the legal hold from a snapshot reverses the hold status. After the hold is removed, the snapshot is retained based on the retention policy defined in the relevant SLA Domain. If no SLA Domain policy exists, the snapshot becomes unmanaged once the hold is removed. If the snapshot expiry date has passed, the snapshot is deleted immediately. To avoid deletion of snapshots, you can extend the snapshot retention before the legal hold is removed. + +Legal hold information does not propagate from the source Rubrik cluster to the target Rubrik cluster or from the target cluster back to the source cluster. For example, when snapshots on the source Rubrik cluster are placed on legal hold, the replicated snapshots on the target Rubrik cluster are not automatically placed on legal hold and expire according to the SLA Domain policy. Similarly, when a replicated snapshot is placed on legal hold, the corresponding snapshot on the source Rubrik cluster is not automatically placed on legal hold and expires according to the SLA Domain policy. + *[ > ]: and then diff --git a/saas_legal_hold_snapshot_rtn_4.md b/saas_legal_hold_snapshot_rtn_4.md new file mode 100644 index 0000000000000000000000000000000000000000..a6ff7cdc2157ed030261b41978029963553a5d7c --- /dev/null +++ b/saas_legal_hold_snapshot_rtn_4.md @@ -0,0 +1,38 @@ +# Legal hold for snapshot retention + +Source: https://docs.rubrik.com/en-us/saas/saas/legal_hold_snapshot_rtn_4.html + +--- + +# Legal hold for snapshot retention + +Legal hold ensures that snapshots are retained indefinitely until the hold is removed, overriding the scheduled expiry of an SLA Domain policy. This ensures that snapshots are available as long as necessary to meet legal obligations. + +Legal hold is a feature that preserves snapshots indefinitely and is designed to retain specific backups in order to meet legal requirements. When a snapshot is placed on legal hold and assigned an SLA Domain with an archival policy, an additional copy of the snapshot is stored in the archival location. Snapshots under legal hold do not expire regardless of the SLA Domain policy, and the snapshots cannot be removed from the system. Placing a legal hold on a snapshot does not prevent the administrator from recovering files or downloading a CSV file from the snapshot. + +Note: + +Only data center workloads support legal hold. + +Legal hold does not apply to the following workloads and snapshots: + + * Log backups of SQL Server databases + * Log backups of Oracle databases + * Managed Volumes + * Snapshots of direct archive filesets + +During the replication of snapshots, the legal hold status is not automatically propagated to the replicated snapshot. However, you can choose to manually place a legal hold on the replicated snapshots to ensure they are retained to meet the compliance requirements. + +When placing a snapshot on legal hold, a user with Place and remove legal hold privilege can choose to: + + * Place legal hold on snapshots. + * Remove legal hold from snapshots. + * Retain the snapshot at both the local and archival locations. + * Retain the snapshot only at the locations with the longest retention period. + +When you select the option to retain the local snapshot until legal hold is removed, the local cluster will retain the snapshot until the legal hold is removed. If an SLA Domain specifies an archival location, the archived snapshot is placed on legal hold by default. If no archival location is specified, the local snapshot is placed on legal hold. + +Removing the legal hold from a snapshot reverses the hold status. After the hold is removed, the snapshot is retained based on the retention policy defined in the relevant SLA Domain. If no SLA Domain policy exists, the snapshot becomes unmanaged once the hold is removed. If the snapshot expiry date has passed, the snapshot is deleted immediately. To avoid deletion of snapshots, you can extend the snapshot retention before the legal hold is removed. + +Legal hold information does not propagate from the source Rubrik cluster to the target Rubrik cluster or from the target cluster back to the source cluster. For example, when snapshots on the source Rubrik cluster are placed on legal hold, the replicated snapshots on the target Rubrik cluster are not automatically placed on legal hold and expire according to the SLA Domain policy. Similarly, when a replicated snapshot is placed on legal hold, the corresponding snapshot on the source Rubrik cluster is not automatically placed on legal hold and expires according to the SLA Domain policy. + *[ > ]: and then diff --git a/saas_licenses_usage.md b/saas_licenses_usage.md new file mode 100644 index 0000000000000000000000000000000000000000..5c5cc96199d7036fc42bcc0d825d1219eff8f360 --- /dev/null +++ b/saas_licenses_usage.md @@ -0,0 +1,23 @@ +# Licenses and usage details + +Source: https://docs.rubrik.com/en-us/saas/saas/licenses_usage.html + +--- + +# Licenses and usage details + +RSC provides a comprehensive view of license and usage details for workloads. The Licenses and Usage page helps you analyze the current data protection usage and make informed decisions about future license requirements, based on various combinations of the number of users, storage capacity, and workload. + +The Licenses and Usage page in RSC effectively tracks consumption of capacity and license renewal dates for planning future license requirements. Depending on the workload and license model, RSC generates various charts to show a detailed breakdown of license capacity consumption. The Licenses and Usage page in RSC has the following features: + + * Provides access to a complete list of purchased licenses and their term periods. + * Uses various indicators to help track and manage licenses, based on the expiration dates. + * Sends email and in-app notification alerts when a license is nearing expiration, surpassing the threshold limit, or exceeding its capacity. + +When a license or usage of a workload requires attention, RSC displays the following information for each workload: + + * Number of licenses expiring in the next six months. + * Percentage of license utilization, when the utilization exceeds threshold capacity. + * Number of accounts exceeding the license capacity, and the amount by which the accounts have exceeded the license capacity. + + *[ > ]: and then diff --git a/saas_limitations_configuring_cascading_archival.md b/saas_limitations_configuring_cascading_archival.md new file mode 100644 index 0000000000000000000000000000000000000000..8ee9d33b258a35307d5b999b83f0abac8499d5c1 --- /dev/null +++ b/saas_limitations_configuring_cascading_archival.md @@ -0,0 +1,17 @@ +# Limitations for configuring cascading archival + +Source: https://docs.rubrik.com/en-us/saas/saas/limitations_configuring_cascading_archival.html + +--- + +# Limitations for configuring cascading archival + +Information about actions and limitations for configuring cascading archival, including restrictions on cross-account targets, shared target clusters, isolated clusters, and on-demand snapshots. + +The following table describes the details on cascading archival options, including available actions, configuration requirements, and descriptions. Cascading archives | Enable or configure | Description +---|---|--- +Cross-account replication target | No | Supports only replication policies without cross-account replication targets, also referred to as external targets. +Shared target cluster in one-to-one replication | Yes | Allows cascading archival for only one replication policy when two policies share the same target cluster. Does not allow cascading archival for a second policy with the same target cluster. +Isolated cluster | Yes | Supports cascading archival for isolated clusters only when the Rubrik cluster is connected to RSC. +Snapshot type | Yes | Applies cascading archival only to scheduled snapshots, not to on-demand snapshots. + *[ > ]: and then diff --git a/saas_limitations_replication_config.md b/saas_limitations_replication_config.md new file mode 100644 index 0000000000000000000000000000000000000000..586f93eec37ddb2aa10a4792b64c48ec0266dc6a --- /dev/null +++ b/saas_limitations_replication_config.md @@ -0,0 +1,47 @@ +# Limitations in replication configuration + +Source: https://docs.rubrik.com/en-us/saas/saas/limitations_replication_config.html + +--- + +# Limitations in replication configuration + +Configuring replication as part of the SLA Domain creation process has specific limitations that require consideration. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +The following table outlines the limitations across different aspects of replication configuration. Policy | Limitation +---|--- +When creating an SLA Domain | When selecting a source cluster for one-to-one replication or archiving: + + * Selecting a source cluster is not allowed if it is not part of a replication pairing or if you do not have permission for the paired target cluster. + * Selecting a source cluster is not allowed if it has no archival location or if you do not have view permission for the archival location. + +When selecting a target cluster for many-to-one replication: + + * Selecting target clusters that have replication pairing with at least one cluster is possible only when archiving is not selected. + * Selecting target clusters that have replication pairing with at least one of the selected source clusters is only possible when both archival and many-to-one replication are selected. + + +When editing an SLA Domain | + + * Switching between one-to-one and many-to-one replication configurations is not allowed. + * Deselecting source clusters is not allowed if any object on the cluster is protected by the assigned SLA Domain. + * For SLA Domains without protected data center objects, when you choose many-to-one replication without selecting archiving, only target clusters that are paired with at least one source cluster are viewable. This follows the SLA Domain creation rule. For many-to-one replication with archiving, only target clusters paired with at least one of the source clusters selected during SLA Domain creation are viewable. + * For an SLA Domain with protected data center objects, when you choose many-to-one replication with archiving, only target clusters that are paired with all protected clusters in the SLA Domain are viewable. When you choose many-to-one replication without selecting archiving, only target clusters that are paired with all protected clusters in the SLA Domain are viewable.A protected cluster indicates that there are objects on the clusters where the SLA Domain has been assigned. + + +When configuring cascading archival | + + * Having multiple replication policies pointing to the same target cluster is not possible in many-to-one replication. Each replication policy must point to a different target cluster, which means that cascading archival cannot be configured when multiple policies are directed to the same target. + * In one-to-one replication, when the same target cluster is used in both replication policies, cascading archival is configurable only for the first replication policy. + * Cascading archival is only available to set up with an isolated cluster when it is connected to RSC. When configuring cascading archival, ensure that the replication target is connected to RSC. + * Cascading archival is not configurable when a replication policy includes an external cluster.An external cluster refers to a cluster that belongs to a different RSC account and is used for replication purposes. In cross-account replication, one RSC account can provide its cluster as a replication target to another RSC account. + + +When changing retention of snapshots | + + * Assigning one-to-one replication to an SLA Domain when the source cluster of the selected snapshots is not part of the replication pairing is not allowed. Similarly, for both one-to-one and many-to-one replication, a replication pairing between the source cluster of the snapshot and the corresponding target clusters in the SLA is required. A message prompts you to create the necessary replication pairing before assigning the SLA Domain. + * Changing the retention of snapshots on source clusters not included in the one-to-one SLA Domain replication policy is not allowed. + + *[ > ]: and then diff --git a/saas_local_user_account_lockout.md b/saas_local_user_account_lockout.md new file mode 100644 index 0000000000000000000000000000000000000000..ad619ebbb600f31a80301c92362da5399fd0756e --- /dev/null +++ b/saas_local_user_account_lockout.md @@ -0,0 +1,20 @@ +# Local user account lockout + +Source: https://docs.rubrik.com/en-us/saas/saas/local_user_account_lockout.html + +--- + +# Local user account lockout + +Local user accounts are automatically locked after a configured number of failed login attempts or due to inactivity, enhancing security against unauthorized access. + +To enhance security, RSC counts the number of failed logins for a local user account since the last successful login. A local user account is automatically locked after a configured number of failed login attempts. Additionally, local user accounts are automatically locked if they have been inactive for a certain amount of time, as configured by an administrator. + +A locked account can be unlocked using one of the following methods: + + * Administrative unlock: An administrator with appropriate privileges can unlock the account. + * Auto-unlock: For accounts locked by the brute-force method, the account can automatically unlock after a fixed duration, if configured. + * Self-unlock: For accounts locked due to inactivity, users may have the option to self-unlock their account through a password reset email if this feature is enabled by an administrator. + * Rubrik Support unlock: If an administrator is unavailable, Rubrik Support can unlock a user account. + * Resetting the password using the Forgot password link on RSC login page. + diff --git a/saas_local_users.md b/saas_local_users.md new file mode 100644 index 0000000000000000000000000000000000000000..ea82cf4e09f11967ddb738d82fc1f2be77980e42 --- /dev/null +++ b/saas_local_users.md @@ -0,0 +1,14 @@ +# Local users + +Source: https://docs.rubrik.com/en-us/saas/saas/local_users.html + +--- + +# Local users + +You can manage local user accounts on RSC. + +You can add and delete local user accounts on RSC. You can also manage role assignments of the local user accounts to determine their access to protected resources. + +RSC displays local users both with and without roles on the Local tab of the Users page. Users with the administrator account and users with the View user access and Manage user access privileges for access management can delete local user accounts. Local users deleted from a tenant organization do not lose access to other tenant organizations where they have access. However, local users from the global organization will also be deleted from the tenant organizations where they have access. + *[ > ]: and then diff --git a/saas_lock_cyber_recoveries.md b/saas_lock_cyber_recoveries.md new file mode 100644 index 0000000000000000000000000000000000000000..e3b260c0d8d73fd32e592cbfce5599439563ec1f --- /dev/null +++ b/saas_lock_cyber_recoveries.md @@ -0,0 +1,22 @@ +# Lock cyber recoveries + +Source: https://docs.rubrik.com/en-us/saas/saas/lock_cyber_recoveries.html + +--- + +# Lock cyber recoveries + +Locking a cyber recovery prevents accidental cleanup and changes to the recovery in future Orchestrated Recovery operations. + +Locking a cyber recovery ensures that the recovered virtual machines are not accidentally deleted in future Orchestrated Recovery operations. You can access and lock cyber recoveries from the Recoveries page in Orchestrated Recovery. RSC supports the Lock Recovery operation only for cyber recoveries. + +After locking a cyber recovery, Orchestrated Recovery no longer manages that cyber recovery. You can retain, move, or delete the recovered virtual machines from your hypervisor or Azure cloud subscription as needed. + +Note: + +Locking a cyber recovery is permanent, and you cannot make changes to a recovery after it is locked. + +You can download a report from the recovery details page and continue to make changes to the recovered objects on their individual pages in RSC. + +You can lock a cyber recovery only if you have the Manage Recovery permission in Orchestrated Recovery. + *[ > ]: and then diff --git a/saas_m365.md b/saas_m365.md new file mode 100644 index 0000000000000000000000000000000000000000..d6c09b97171fc11e27296f0a3146935d4bf1f765 --- /dev/null +++ b/saas_m365.md @@ -0,0 +1,26 @@ +# Microsoft 365 + +Source: https://docs.rubrik.com/en-us/saas/saas/m365.html + +--- + +# Microsoft 365 + +Using the data management and protection services offered by Rubrik Security Cloud, you can protect Microsoft 365 data operations. + +For all Microsoft 365 data management operations, including backup and restore, Rubrik Security Cloud (RSC) uses Azure cloud computing services. All Microsoft 365 data management operations run within an Azure account hosted either by you or by Rubrik. The protected data is always held within the hosting Azure tenant, which ensures data security and privacy. + +RSC backs up the data from Microsoft 365 objects by creating a snapshot of the corresponding data source, such as Exchange (mailboxes, calendars, and contacts), OneDrive, SharePoint, and Teams. This first full snapshot is a complete backup of the Microsoft 365 data. RSC then creates incremental snapshots based on the changed information, such as deleted or modified email messages or files. + +The data in every user account protected by Rubrik requires a license. Each user license automatically protects a shared mailbox at no extra cost. + +Microsoft 365 deployments on RSC require: + + * In customer-hosted mode, firewall rules configured for communication among RSC, Microsoft 365, and Microsoft Azure. + * Administrator access to the Microsoft 365 subscription you want to protect. + * An enterprise AAD app. The enterprise AAD app creates apps required for authorizing RSC to act as a control plane for accessing Microsoft 365 and Azure accounts. + * A working secret for the enterprise AAD app, required for communication with Microsoft 365 data. + +After configuring the enterprise AAD app and the secret, you can contact Rubrik Support to apply the secret to the AAD app and enable Microsoft 365 support for RSC. You can then set up a Microsoft 365 subscription on the RSC deployment. + +Microsoft 365 user accounts derive protection from the SLA Domain assigned to the Microsoft 365 subscription. diff --git a/saas_m365_azure_ent_app_mgmt.md b/saas_m365_azure_ent_app_mgmt.md new file mode 100644 index 0000000000000000000000000000000000000000..e257982891be5436315e3f6f9f14a4bf5f964b12 --- /dev/null +++ b/saas_m365_azure_ent_app_mgmt.md @@ -0,0 +1,16 @@ +# Azure Enterprise applications management + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_azure_ent_app_mgmt.html + +--- + +# Azure Enterprise applications management + +Rubrik Security Cloud supports Azure Enterprise applications deployed on Microsoft 365. + +Developing or deploying an Azure Enterprise application on Microsoft 365 requires permissions to allow Rubrik Security Cloud (RSC) access to specific Microsoft 365 operations and functionality. + +For example, an administrator deploys an Azure Enterprise application authorized to read and write emails for a Microsoft 365 tenant. This authorization is used to back up a user mailbox as part of a daily backup. The Azure Enterprise application gives RSC permission to restore emails back to the Microsoft 365 tenant. Without granting the appropriate permissions to RSC, operations performed against the tenant associated with the Azure Enterprise application would fail. + +With designated permissions applied, RSC supports Azure Enterprise applications for Microsoft Exchange, SharePoint, OneDrive, and Microsoft Teams, each with the required permissions to protect that workload. + *[ > ]: and then diff --git a/saas_m365_backup_recovery_snapshots.md b/saas_m365_backup_recovery_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..2649a4f548e9503d513fbac2c6661fabb4db9ef6 --- /dev/null +++ b/saas_m365_backup_recovery_snapshots.md @@ -0,0 +1,31 @@ +# Backup and recovery with Microsoft 365 snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_backup_recovery_snapshots.html + +--- + +# Backup and recovery with Microsoft 365 snapshots + +RSC protects and manages Microsoft 365 data using snapshots of source Microsoft 365 objects. You can take snapshots of backup data for Microsoft Exchange, OneDrive, SharePoint, and Teams to recover lost or compromised information. + +You can securely back up Microsoft 365 Exchange, OneDrive, SharePoint, and Teams data to recover your data in case of lost or compromised information. You can protect data by defining protection policies in SLA Domains and assigning the SLA Domains to your Microsoft 365 data sources. The SLA Domain policies define when RSC creates a point-in-time snapshot or backup of protectable Microsoft 365 objects, and how long to keep the data. + +RSC provides a variety of ways to recover snapshot data from the following Microsoft 365 objects: + + * Exchange email messages, folders, files, contacts, and both single occurrences and recurring series of calendar events, meetings, and appointments. + * OneDrive files and folders. + * SharePoint site collections, document libraries, lists, files, list items, and apps. + * Teams channels, files, conversations, and conversation attachments. + +Administrators can also configure SSO users to recover their own Exchange and OneDrive data without an administrator. RSC performs an in-place recovery by recovering the objects to the original location. + +RSC recovery locations depend on the objects you are recovering. + +Object | Recovery location +---|--- +Email, OneDrive, SharePoint, or Teams | New folder +Calendar data or contacts | New calendar group or contact folder +Exchange or OneDrive (for SSO users) | Original location + +RSC generates recovery events and displays them on the Events tab of the object details page. Administrators of SSO users or groups can view all events performed by an SSO user. + *[ > ]: and then diff --git a/saas_m365_configure_working_secret.md b/saas_m365_configure_working_secret.md new file mode 100644 index 0000000000000000000000000000000000000000..6e740d47f2d19286c5e0d82606e12285bdc34d41 --- /dev/null +++ b/saas_m365_configure_working_secret.md @@ -0,0 +1,87 @@ +# Configuring a working secret for the enterprise Azure AD app + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_configure_working_secret.html + +--- + +# Configuring a working secret for the enterprise Azure AD app + +Describes the creation of a working secret for the enterprise Azure Active Directory app, required for deploying Microsoft 365 on RSC. + +## Before you begin + +Complete the following in the order listed: + + * Download the latest RSC packages and install them on the cluster. + * Configure the correct API permissions on Azure for the enterprise Azure Active Directory (AAD) app. + * Deploy the enterprise AAD app on RSC. + +## About this task + +This procedure replaces the default dummy secret provided with the enterprise AAD app. A working secret is required for Microsoft 365 communication with RSC. + +## Procedure + + 1. Log in to the Azure portal. + 2. Select Enterprise Applications. + 3. Select or search for the enterprise AAD app. + +The enterprise AAD app overview screen appears. + + 4. Click Certificates & secrets. + 5. Click New client secret. + 6. In the Add a client secret pane, enter the secret information. + 7. In Description, add a secret description. + 8. In Expires, select the expiration properties. + 9. Click Add. + +The client secret is created. + + 10. Copy the secret ID to the clipboard. + 11. Use SSH to access RSC. + 12. Delete the dummy secret by replacing the automatically generated IP address with the cluster IP. + +Enter the following command in a terminal. Use your terminal editor to replace the ip value with the IP address of the cluster. + + % kubectl --pmc-cluster-name-ip -n rubrik-spark delete secret o365-azure-app-creator-creds + +. + + 13. Use the app credentials copied earlier to run the following command to add the correct secret. + + % kubectl --context pmc-cluster-name-ip -n rubrik-spark create secret generic + o365-azure-app-creator-creds + --from-literal=client.id= + --from-literal=client.secret= + --from-literal=tenant.domain= + --from-literal=saas.client.id= + --from-literal=saas.client.secret= + --from-literal=saas.tenant.domain= + --from-literal=gov.client.id= + --from-literal=gov.client.secret= + --from-literal=gov.tenant.domain= + + % kubectl --context pmc-10.0.37.21 -n rubrik-spark create secret generic o365-azure-app-creator-creds + --from-literal=client.id=d37abfc3-77c4-4edb-b5fb-7cdbecf0375e + --from-literal=client.secret=FMlgFoSFAr05lEOUdF6fmKaCbzlD+PsSwEyCeFd2Af0= + --from-literal=tenant.domain=example.example.com + --from-literal=saas.client.id=1e4b45b0-e89f-465b-a720-4956ed55d5f2 + --from-literal=saas.client.secret=a0p~oj3K-F.qSzW1VUbhC3JA.FM2t4zLj0 + --from-literal=saas.tenant.domain=o365rubrik.example.com + --from-literal=gov.client.id=3dfa14ba-e5d0-4d15-b69f-f456e3ffbaba + --from-literal=gov.client.secret=P9G55vyx_7dt5KdBDkG.zA_uz~v.u2sm0R + --from-literal=gov.tenant.domain=azurerubrikgov.example.us + + +## Results + +A working secret is configured and deployed on RSC. + +## What to do next + +Complete the following in the order listed: + + * Contact Rubrik Support to apply the secret to the AAD app and to enable Microsoft 365 on RSC. + * Set up a Microsoft 365 subscription on RSC. + + *[ > ]: and then diff --git a/saas_m365_create_enterprise_aad.md b/saas_m365_create_enterprise_aad.md new file mode 100644 index 0000000000000000000000000000000000000000..186b0d5294cc09d0240d26aeca786f483a4ede32 --- /dev/null +++ b/saas_m365_create_enterprise_aad.md @@ -0,0 +1,106 @@ +# Creating the enterprise AAD app + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_create_enterprise_aad.html + +--- + +# Creating the enterprise AAD app + +Create the enterprise Azure Active Directory app used by RSC Microsoft 365 workloads when you are using advanced setup. + +## Before you begin + +Complete the following: + + * Configure the firewall on the host to allow outbound traffic for Microsoft 365 URLs. + * Download and install the most recent RSC upgrade packages on the cluster. + +## Procedure + + 1. Log in to the Azure portal. + 2. Click Enterprise Applications. + 3. Select New application. + 4. Click Create your own application. + 5. In the Create your own application pane, provide the application information. + + * Enter the application name. + * Select Integrate any other application you don't find in the gallery (Non-gallery). + + 6. Click Create. + +The App overview screen appears. + + 7. Copy the Application ID to the clipboard. + 8. In the search bar, enter **App Registrations**. + +The App Registrations screen appears. + + 9. Click All Applications. + 10. In the search bar, paste the copied Application ID and click the search icon. + +The new application appears in the search results. + + 11. Click API Permissions + +The API Permissions screen appears. + + 12. Search for and select your new application. + +The new application setting screen appears. + + 13. Select API Permissions. + 14. Under Configured permissions, click Add a permission. + 15. Add required Microsoft API permissions. + +You can set the API permissions through the Azure UI or by replacing `requiredResourceAccess` in the Azure manifest with the following: + + "requiredResourceAccess": [ + { + "resourceAppId": "00000002-0000-0000-c000-000000000000", + "resourceAccess": [ + { + "id": "1cda74f2-2616-4834-b122-5cb1b07f8a59", + "type": "Role" + }, + { + "id": "824c81eb-e3f8-4ee6-8f6d-de7f50d565b7", + "type": "Role" + }, + { + "id": "5778995a-e1bf-45b8-affa-663a9f3f4d04", + "type": "Role" + } + ] + }, + { + "resourceAppId": "00000003-0000-0000-c000-000000000000", + "resourceAccess": [ + { + "id": "18a4783c-866b-4cc7-a460-3d5e5662c884", + "type": "Role" + }, + { + "id": "7ab1d382-f21e-4acd-a863-ba3e13f7da61", + "type": "Role" + }, + { + "id": "1bfefb4e-e0b5-418b-a88f-73c46d2cc8e9", + "type": "Role" + }, + { + "id": "9a5d68dd-52b0-4cc2-bd40-abcf44ac3a30", + "type": "Role" + } + ] + } + ] + + +## Results + +The enterprise AAD app is now deployed and configured. + +## What to do next + +Configure a working secret for the enterprise AAD app. + *[ > ]: and then diff --git a/saas_m365_dashboard.md b/saas_m365_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..4b23a716599f85e888a721a73cfc38963dee6717 --- /dev/null +++ b/saas_m365_dashboard.md @@ -0,0 +1,20 @@ +# Microsoft 365 dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_dashboard.html + +--- + +# Microsoft 365 dashboard + +The Microsoft 365 dashboard provides important insights into your protected Microsoft 365 environment. By using the dashboard, you can view and monitor information such as deployment locations and settings, backup and recovery status, events, and compliance information. + +Microsoft 365 dashboard uses visual elements, such as graphs and charts, to display the current state of the backup events and details about the Microsoft 365 environment. You can view and monitor deployment location and settings, backup and recovery status, events, and compliance data. The panes provide interactive elements for further data discoverability related to protected Microsoft 365 applications. + +The Microsoft 365 dashboard also provides options to perform the following tasks: + + * Adding a subscription: Add a Microsoft 365 subscription. + * Managing enterprise apps: Add Microsoft 365 apps to RSC to improve the backup and recovery speeds. + * Assigning an SLA Domain: Choose a data protection policy for the applications in a Microsoft 365 subscription. + * Refreshing or deleting a subscription: Refresh or delete a Microsoft 365 subscription. + + *[ > ]: and then diff --git a/saas_m365_deployment_mode.md b/saas_m365_deployment_mode.md new file mode 100644 index 0000000000000000000000000000000000000000..69128f12a7976122f344ee8835831a4e064d2775 --- /dev/null +++ b/saas_m365_deployment_mode.md @@ -0,0 +1,25 @@ +# Deployment modes + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_deployment_mode.html + +--- + +# Deployment modes + +RSC supports deployment modes for the data plane responsible for the Microsoft 365 data source computing activities. + +RSC supports two deployment modes: + + * In Rubrik-hosted deployment mode, the data plane is deployed in the Azure account hosted by Rubrik. + * In customer-hosted deployment mode, the data plane is deployed in the Azure account hosted by the customer. + +The data plane in both modes is built with the same architecture and functionality. The use of either mode depends on the needs of the customer environment. + +The data plane is managed by a centralized RSC control plane. RSC orchestrates the tasks for the Microsoft 365 subscription, such as refreshing metadata, taking snapshots, indexing, searching, or restoring data. + +The data plane uses an Azure blob storage to store the backup data within the Azure account. The backup data in the Azure blob storage account is encrypted with keys stored in an Azure Key Vault in the Azure account. + +Azure Kubernetes Service (AKS) is used to provision a Kubernetes cluster. For a Microsoft 365 subscription, all tasks such as taking snapshots, indexing, searching, or restoring data are performed on this cluster as data management applications running within a container. + +The Kubernetes cluster is deployed in the subnet of a private virtual network (Azure VNet). This subnet uses a network security group to block incoming traffic from outside the VNet. The storage account is part of this private VNet ensuring secure and private communication between the containers and the storage account. + *[ > ]: and then diff --git a/saas_m365_enterprise_aad_app_permissions_settings.md b/saas_m365_enterprise_aad_app_permissions_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..50eddc0f5f2d1dc8d18bbe8f50764bc478984480 --- /dev/null +++ b/saas_m365_enterprise_aad_app_permissions_settings.md @@ -0,0 +1,27 @@ +# Enterprise AAD app API permissions settings + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_enterprise_aad_app_permissions_settings.html + +--- + +# Enterprise AAD app API permissions settings + +Required Microsoft 365 API permission settings for the enterprise Azure Active Directory app. + +Microsoft API | Permission name +---|--- +Azure Active Directory | Application.ReadWrite.All +Azure Active Directory | Application.ReadWrite.OwnedBy +Azure Active Directory | Directory.Read.All> +Microsoft Graph | Application.Read.All +Microsoft Graph | Application.ReadWrite.All +Microsoft Graph | Application.Read.Write.OwnedBy +Microsoft Graph | Directory.Read.All + +In addition, each Microsoft API entry requires the following configuration: + + * The Type set to Application. + * The Admin consent requiredfield for each permission set to Yes. + * Status set as Not Granted for application-name. + + *[ > ]: and then diff --git a/saas_m365_firewall_rules.md b/saas_m365_firewall_rules.md new file mode 100644 index 0000000000000000000000000000000000000000..d02cd76ae27ef53c287f763e413ea7e2b56411e2 --- /dev/null +++ b/saas_m365_firewall_rules.md @@ -0,0 +1,49 @@ +# Firewall rules + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_firewall_rules.html + +--- + +# Firewall rules + +Lists the firewall rules needed for communication between the RSC, Microsoft 365, and Microsoft Azure when using customer-hosted deployment. + +The firewall rules on the RSC host must allow outbound traffic through TCP port 443 to the following URLs: + +Description | URLs +---|--- +Microsoft Azure Access | + + * login.microsoftonline.com + * graph.microsoft.com + * management.azure.com + * *.azmk8s.io mcr.microsoft.com + * *.data.mcr.microsoft.com + * packages.microsoft.com + * acs-mirror.azureedge.net + + +Managed Kubernetes Service (AKS) access | Azure Firewall supports an Azure Kubernetes Service FQDN (AzureKubernetesService) that you can use to restrict outbound access to just the services required by AKS. +ACR access | + + * usgovcommercialacr.azurecr.us + * mcr.microsoft.com + + +Azure storage access | + + * *.blob.core.windows.net + * *.table.core.windows.net + + +Key vault access | *.vault.azure.net +Microsoft 365 access | + + * outlook.office.com + * outlook.office365.com + * autodiscover-s.outlook.com + * login.microsoftonline.com + * graph.microsoft.com + * *.sharepoint.com + + *[ > ]: and then diff --git a/saas_m365_groups.md b/saas_m365_groups.md new file mode 100644 index 0000000000000000000000000000000000000000..210a229f34f950dfe75ba3ea8f083b0f5e51166a --- /dev/null +++ b/saas_m365_groups.md @@ -0,0 +1,20 @@ +# Groups in M365 + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_groups.html + +--- + +# Groups in M365 + +RSC uses groups to assign data protection and management policies uniformly to Microsoft 365 objects. + +Rubrik Security Cloud (RSC) uses the following group types for managing Microsoft 365 data protection: + + * Entra ID groups for managing Exchange Mailboxes and OneDrive objects + * SharePoint groups for managing SharePoint objects + * Teams groups for managing Teams objects + +Entra ID groups are a collection of objects associated with Entra ID and are managed in Entra ID. In RSC, Entra ID groups add a layer to Microsoft 365 protection hierarchy between the Microsoft 365 organization and users. Creating an Entra ID group requires Entra ID authorization. + +SharePoint and Teams groups use wildcard patterns to associate specific SharePoint or Teams objects to a group. To limit the SharePoint or Teams group to objects that are part of a specific location, you can apply a Preferred Data Location (PDL). + *[ > ]: and then diff --git a/saas_m365_immutability.md b/saas_m365_immutability.md new file mode 100644 index 0000000000000000000000000000000000000000..58010a9ab91f9d548ddce2a281effa9453026d8e --- /dev/null +++ b/saas_m365_immutability.md @@ -0,0 +1,22 @@ +# Microsoft 365 immutability + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_immutability.html + +--- + +# Microsoft 365 immutability + +RSC uses immutable storage for Azure Blob Storage to provide immutability protection for Microsoft 365 when creating an Azure storage account for Microsoft 365 deployments. Immutability protection ensures that your data remains unaltered, which is critical for disaster recovery, protection from ransomware attacks, and data compliance. + +For Microsoft 365 deployments for which RSC creates an Azure storage account, the Azure time-based retention policy for immutable blob data protects Microsoft 365 data against accidental deletion or malicious activity. The retention policy locks the data with a Write-Once, Read-Many (WORM) lock for a specified interval. When the WORM lock is active, you can create and read Microsoft 365 data, but not modify or delete it until the retention period expires. + +You can set and manage retention periods using SLA Domains. When you apply an SLA Domain to a snapshot, it stays effective until the retention period expires. For example, when you apply an SLA Domain to a snapshot that has a retention period of 30 days, it remains in an immutable state for 30 days. After 30 days, you can modify or delete the snapshot. + +When you change the SLA Domain retention period after applying it to a snapshot, the snapshot retains the previous retention period. For example, if you change an SLA Domain retention policy from 30 days to 15 days, snapshots taken when the retention policy was set to 30 days remain immutable for 30 days, while snapshots taken after the retention policy changed to 15 days are immutable for only 15 days. + +RSC supports changing the retention period of all snapshots for the following Microsoft 365 objects: + + * Protected or unprotected relic objects + * Unprotected active objects + + *[ > ]: and then diff --git a/saas_m365_implicit_permissions_rbac.md b/saas_m365_implicit_permissions_rbac.md new file mode 100644 index 0000000000000000000000000000000000000000..312525f9c24b6522ec297c9807466e2611e654e4 --- /dev/null +++ b/saas_m365_implicit_permissions_rbac.md @@ -0,0 +1,20 @@ +# Implicit permissions and Microsoft 365 objects + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_implicit_permissions_rbac.html + +--- + +# Implicit permissions and Microsoft 365 objects + +Rubrik Security Cloud uses implicit permissions to help provide access to specific objects in the Microsoft 365 hierarchy. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +As part of its RBAC rules, Rubrik Security Cloud (RSC) uses implicit permissions so that you can view and manage specific objects. These permissions are logically implied by the permissions that you explicitly received for an object in the Microsoft 365 hierarchy. + +RSC organizes Microsoft 365 objects hierarchically, with the Microsoft 365 application as the root. Beneath the root of this hierarchy, the objects exist in parent and child relationships with each other. Each object on any branch of the hierarchy is the parent of the object immediately below it and the child of the object immediately above it. When you are assigned permissions for a Microsoft 365 object, you also get the implicit permissions for the parents of the object that are required for you to navigate to the object. + +When RSC uses implicit permissions to allow you to view and work with a Microsoft 365 object, the dashboard displays a limited view to facilitate navigation into the M365 Subscription. RSC hides any objects for which you were granted implicit permissions. + +You can recover to only the target locations (the Microsoft 365 subscriptions) that you have access to, as defined by the RSC role assigned to you by the RSC administrator. If the administrator does not specify a recovery target during role creation, you cannot recover to any target location. + *[ > ]: and then diff --git a/saas_m365_protection.md b/saas_m365_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..0c436a578963364b660041bf171658e41fa98e49 --- /dev/null +++ b/saas_m365_protection.md @@ -0,0 +1,12 @@ +# Microsoft 365 protection + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_protection.html + +--- + +# Microsoft 365 protection + +Use SLA Domains to apply the data protection policies and management policies to Microsoft 365 resources. + +Exchange mailboxes derive the assigned SLA Domain from the user account or the subscription. However, an individual assignment to the mailbox overrides the assignment derived from the Microsoft 365 subscription. If the SLA Domain is applied to the subscription, new user accounts are detected and automatically protected. + *[ > ]: and then diff --git a/saas_m365_protection_hierarchy.md b/saas_m365_protection_hierarchy.md new file mode 100644 index 0000000000000000000000000000000000000000..2770abf5a97095583859e108264951201df2262e --- /dev/null +++ b/saas_m365_protection_hierarchy.md @@ -0,0 +1,29 @@ +# Protection hierarchy for Microsoft 365 resources + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_protection_hierarchy.html + +--- + +# Protection hierarchy for Microsoft 365 resources + +RSC provides hierarchy-based, automatic protection of Microsoft 365 resources. + +The automatic protection mechanism simplifies assigning protection to large numbers of Microsoft 365 resources. The SLA Domain assignment provides a method of assigning specific SLA Domains uniformly to all protected objects in a Microsoft 365 subscription. An additional SLA Domain can also be assigned directly to all objects of a Microsoft 365 resource or directly to an individual Microsoft 365 object. + +Level | Description +---|--- +Subscription | Any Microsoft 365 object type (Exchange, Mailbox, OneDrive, Sharepoint, and Team) can be assigned an SLA Domain at the Subscription level. If assigned, all Microsoft 365 objects of that type will then inherit that SLA Domain assignment. +Exchange (mailbox, calendar, contacts) | An SLA Domain or Don't protect setting assigned to Exchange overrides an assignment derived from the Microsoft 365 Subscription. +OneDrive | An SLA Domain or Don't protect setting assigned to a Microsoft 365 OneDrive overrides an assignment derived from the Microsoft 365 Subscription. +Site Collection | An SLA Domain or Don't protect setting assigned to a SharePoint Site Collection overrides an assignment derived from the Microsoft 365 Subscription. +Site | A SharePoint Site derives the SLA Domain assignment from the parent site, which can be a Site Collection (for a top level site) or a Subsite. An SLA Domain or Don't protect setting assigned to a SharePoint Site overrides an assignment derived from the SharePoint Site Collection. +Document Library | A SharePoint Document Library derives the SLA Domain assignment from the site. An SLA Domain or Don't protect setting assigned to a SharePoint document library overrides an assignment derived from the site. +List | A SharePoint List derives the SLA Domain assignment from the Site. An SLA Domain or Don't protect setting assigned to a SharePoint List overrides an assignment derived from the Site. +Team | An SLA Domain or Don't protect setting assigned to a Team overrides an assignment derived from the Microsoft 365 Subscription. + +All Microsoft 365 objects in a Microsoft 365 subscription are assigned the SLA Domain, SD1. + +A separate SLA Domain, SD2, is then assigned to all Exchange objects in the Microsoft 365 subscription, overwriting SD1. + +Finally, a separate SLA Domain, SD3, is assigned to OneDrives in the Microsoft 365 subscription, overwriting SD1. + *[ > ]: and then diff --git a/saas_m365_relic_management.md b/saas_m365_relic_management.md new file mode 100644 index 0000000000000000000000000000000000000000..b3fa8d0241a3fa89e0201d1b96c667f623f3c0ba --- /dev/null +++ b/saas_m365_relic_management.md @@ -0,0 +1,16 @@ +# Relic Microsoft 365 management + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_relic_management.html + +--- + +# Relic Microsoft 365 management + +Microsoft 365 does not support user accounts once the user license is revoked. RSC archives inactive user accounts without snapshots and manages the ones with snapshots as relics. + +There are two types of inactive Microsoft 365 user accounts, one with snapshots and the other without snapshots. + +When a Microsoft 365 user license is revoked, the user is no longer managed and protected by Microsoft. The user account becomes inactive. RSC performs periodic refresh jobs to update subscription data to discover inactive Microsoft 365 user accounts. + +RSC archives inactive user accounts that have no snapshots. For inactive user accounts that contain snapshots, RSC manages them as relics. + *[ > ]: and then diff --git a/saas_m365_subscription_management.md b/saas_m365_subscription_management.md new file mode 100644 index 0000000000000000000000000000000000000000..29278e40b1ccd74ae25e0adc78f29494913c862f --- /dev/null +++ b/saas_m365_subscription_management.md @@ -0,0 +1,16 @@ +# M365 subscription management + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_subscription_management.html + +--- + +# M365 subscription management + +RSC provides management and protection of Microsoft 365 subscriptions. + +A single set of credentials for an Azure Service Principal grants permission for RSC to access resources in the Azure account. The service principal has a contributor role that automatically manages the resource group for an Exocompute instance. + +For the Rubrik-hosted deployment mode, when a Microsoft 365 subscription is deleted, RSC archives all user accounts in the subscription. After 30 days, RSC deletes the snapshots and resources associated with the deleted subscription in the cloud account. + +For the customer-hosted deployment mode, when a Microsoft 365 subscription is deleted, RSC archives all user accounts in the subscription. RSC retains the snapshots and resources associated with the deleted subscription in the cloud account. + *[ > ]: and then diff --git a/saas_m365_updating_app_secrets_and_cert.md b/saas_m365_updating_app_secrets_and_cert.md new file mode 100644 index 0000000000000000000000000000000000000000..f1074f33e06a2bfc9c0377e8c67abccae66f7373 --- /dev/null +++ b/saas_m365_updating_app_secrets_and_cert.md @@ -0,0 +1,46 @@ +# Updating expired app secrets and certificates + +Source: https://docs.rubrik.com/en-us/saas/saas/m365_updating_app_secrets_and_cert.html + +--- + +# Updating expired app secrets and certificates + +You can update expired app secrets and certificates in RSC. + +## Before you begin + +Updating expired secrets and certificates requires the View Inventory permission. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Inventory. + +If an app secret or certificate is expired, RSC displays a message that it could not connect to Microsoft. + + 4. Click View Apps. + +You can alternatively use a Powershell script to update credentials by clicking the script link in the message. + +The Enterprise App Management page appears. + + 5. For the app with the expired secret or certificate, click and select Edit. + +The Edit Enterprise App wizard appears. + + 6. Click Advanced and then click Next. + 7. In App Secret, enter the app secret. + 8. For OneDrive, SharePoint, or Teams, in Certificate, paste the contents of the certificate file. + 9. For OneDrive, SharePoint, or Teams, in Private Key, paste the contents of the private key file. + 10. Click Update. + +RSC validates the app details. + + 11. Confirm your settings and then click Update. + +## Results + +RSCupdates the expired app secret and certificate. + *[ > ]: and then diff --git a/saas_manage_retention_sap_hana_snapshots.md b/saas_manage_retention_sap_hana_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..2b31cff6013782cadb0bafd215ff2ab460375cce --- /dev/null +++ b/saas_manage_retention_sap_hana_snapshots.md @@ -0,0 +1,21 @@ +# Manage retention of SAP HANA snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/manage_retention_sap_hana_snapshots.html + +--- + +# Manage retention of SAP HANA snapshots + +To meet data governance and regulatory compliance, you can increase the retention period of individual SAP HANA snapshots, as required. + +Retaining snapshots is crucial for supporting data governance and regulatory compliance. Snapshot retention ensures that all critical data is preserved, and you can access it in unforeseen situations. + +Based on your specific data governance and compliance needs, you can change the retention period of SAP HANA snapshots to a custom value by assigning a different SLA Domain. However, changing the retention period of SAP HANA snapshots is only available on Rubrik clusters running Rubrik CDM version 9.0.1 or later. + +With the change retention feature, you can: + + * Change the retention period of full snapshots by assigning them a different SLA Domain. You can also choose to retain the snapshots forever. + * Choose to retain the incremental and differential snapshots forever. + +Additionally, you can check the expiration date of your snapshots in the Snapshots tab for local, archival, or replication locations. Once you have this information, you can determine which snapshots require the retention period adjustment, helping you manage their retention period more efficiently. + *[ > ]: and then diff --git a/saas_managing_llm_analysis_anomaly_detection.md b/saas_managing_llm_analysis_anomaly_detection.md new file mode 100644 index 0000000000000000000000000000000000000000..b374732189b93b74143735cdee2de1c9e0862aef --- /dev/null +++ b/saas_managing_llm_analysis_anomaly_detection.md @@ -0,0 +1,32 @@ +# Managing LLM analysis for Anomaly Detection + +Source: https://docs.rubrik.com/en-us/saas/saas/managing_llm_analysis_anomaly_detection.html + +--- + +# Managing LLM analysis for Anomaly Detection + +Manage the use of LLM analysis for Anomaly Detection in RSC by disabling it when it is not required. To enhance the accuracy of Anomaly Detection, enable LLM analysis for Anomaly Detection. + +## About this task + +When you enable Anomaly Detection for your data, LLM analysis for Anomaly Detection is enabled by default. LLM analysis for Anomaly Detection uses a pretrained Large Language Model (LLM) to detect anomalous activities. + +Data sent to the LLM is processed in-memory, and discarded after it has been analyzed. As such, it is never written to disk. Additionally, this data is not used to train the LLM. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Threat Analytics and select General Settings. + 4. Choose a setting for LLM Analysis for Anomaly Detection. + +You can enable or disable LLM analysis for Anomaly Detection at any time. Disabling Anomaly Detection might result in an increased number of false alerts for anomalous activities. + +## Results + +RSC saves the setting chosen for Anomaly Detection. + *[ > ]: and then diff --git a/saas_managing_protection_for_snapmirror_cloud.md b/saas_managing_protection_for_snapmirror_cloud.md new file mode 100644 index 0000000000000000000000000000000000000000..b87f802b80db22cf2e43579cd305bb1f82db1b0e --- /dev/null +++ b/saas_managing_protection_for_snapmirror_cloud.md @@ -0,0 +1,57 @@ +# Managing protection with SnapMirror Cloud + +Source: https://docs.rubrik.com/en-us/saas/saas/managing_protection_for_snapmirror_cloud.html + +--- + +# Managing protection with SnapMirror Cloud + +Assign an SLA Domain configured with a SnapMirror Cloud archival location to a NetApp NAS host. + +## Procedure + + 1. Log in to RSC. + 2. Click Inventory. + +The Inventory page shows cards for each configured type of protectable object. + + 3. Click SnapMirror Cloud. + +A list of configured NetApp hosts appears. + + 4. Click the name of a listed NetApp host. + +A list of volumes on the NetApp host appears. Volumes not supported by SnapMirror cloud might not appear. + + 5. Select a volume and click Manage Protection. + +You can select multiple volumes. + +The Assign SLA Domain wizard appears. + + 6. Select a label and click Next. + +This step only appears when protecting read-only volumes. + + 7. Select an SLA Domain from the list or click the + button to create and assign a new SLA Domain. + 8. Choose a protection option. + +Option| Description +---|--- +SLA Domain | Assigns the selected SLA Domain to the object. You must select either an existing SLA Domain or click the button to create and assign a new SLA Domain. +Clear existing assignment | Removes the current SLA Domain assignment from the object. + + 9. Click Next. + +The Confirmation page appears. + + 10. **Optional:** Apply changes to existing snapshots and existing on-demand and downloaded snapshots. + +The frequency and retention of backups configured on the SLA Domain applies to snapshots in the cloud storage. There are no local copies of snapshots for SnapMirror Cloud. + + 11. Review the parameters of the SLA Domain and click Assign. + +## Results + +RSC protects the selected volumes on the NetApp NAS host according to the SLA Domain settings. + *[ > ]: and then diff --git a/saas_managing_protection_object.md b/saas_managing_protection_object.md new file mode 100644 index 0000000000000000000000000000000000000000..42cc1ced11d895e99ca2ec545c823817b2a1e60f --- /dev/null +++ b/saas_managing_protection_object.md @@ -0,0 +1,77 @@ +# Managing protection for an object + +Source: https://docs.rubrik.com/en-us/saas/saas/managing_protection_object.html + +--- + +# Managing protection for an object + +Manage protection for an object by assigning an SLA Domain to optimize data management and enhance data protection. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the inventory card. + +The selected inventory page appears. + + 5. Select the name of the instance or a virtual machine, depending on the selected object type. + +You can also select multiple items. + + 6. Click Manage Protection. + 7. Select a protection option and click Next. + +Option| Description +---|--- +SLA Domain | Assigns the selected SLA Domain to the object.You can assign a retention-locked SLA Domain only to clusters running CDM version 9.2.0 or later.When you configure replication using an isolated Rubrik cluster with an SLA Domain, ensure that a replication pair exists between the source and the isolated cluster for the assignment to succeed.When assigning many-to-one or one-to-one replication configurations, if the clusters associated with the selected objects do not have a replication pairing with the targets defined in the SLA Domain, create a replication pairing before assigning an SLA Domain. +Don't protect | Excludes the chosen objects from all further SLA Domain assignments.Provides options for existing snapshot retention.Removing protection for an object assigned to a retention-locked SLA Domain is applicable only to the governance mode and requires quorum authorization. +Clear existing assignment | Removes the current SLA Domain assignment from the object. After the assignment is cleared, the object inherits an SLA Domain from the parent object.When the SLA Domain is in governance mode, clearing the existing assignment requires quorum authorization.When the SLA Domain is in compliance mode, clearing the existing assignment is not allowed. + + 8. (Don't protect) In Existing snapshot retention, choose an option to retain the existing snapshots. + +Option| Description +---|--- +Use current SLA Domain for retention | The retention policy of the current SLA Domain determines how long the snapshots are retained.This is the default option. +Keep forever | The snapshots are retained until you manually delete them. +Expire immediately | The Rubrik cluster deletes the snapshots. + + 9. Click Next. + +The confirmation page displays a summary of SLA Domain changes and options to apply changes to existing snapshots. RSC does not display these options when you select the Don't protect option. + +A Confirmation page appears. + + 10. **Optional:** Turn on Apply changes to existing snapshots. + +When you turn off this option, the retention policy of existing snapshots remains unchanged. + + 11. **Optional:** (Apply changes to existing snapshots) For Include on-demand and downloaded snapshots: + * Select the setting to apply changes to the retention policy of on-demand and downloaded snapshots. + * Clear the setting to keep the retention policy of on-demand and downloaded snapshots unchanged. + 12. Click Assign. + +For SLA Domains not in the governance mode, the assignment triggers automatically. + +The Request Quorum Authorization page appears only for governance mode retention-locked SLA Domains. + + 13. Click Submit Request. + +After the QAuth Admin or reviewer approves the quorum authorization request, the SLA Domain changes become effective. + +## Results + +RSC processes the specified SLA Domain assignment options and manages protection for the selected object. + *[ > ]: and then diff --git a/saas_mandatory_mfa.md b/saas_mandatory_mfa.md new file mode 100644 index 0000000000000000000000000000000000000000..9229efea0b099cf21993b9a258e90d832eba7a11 --- /dev/null +++ b/saas_mandatory_mfa.md @@ -0,0 +1,20 @@ +# Mandatory multi-factor authentication + +Source: https://docs.rubrik.com/en-us/saas/saas/mandatory_mfa.html + +--- + +# Mandatory multi-factor authentication + +Multi-factor authentication enforcement is mandatory for all user accounts in your RSC environment. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +RSC requires you to enforce multi-factor authentication (MFA) for all local user accounts. You have a grace period of 90 days to enforce MFA in your RSC account from the time of first RSC access. User accounts provided through SAML-based SSO integration are not subject to this MFA enforcement. The SSO identity provider enforces MFA for SSO accounts. + +If you use automation scripts to invoke Rubrik GraphQL (GQL) APIs, MFA enforcement may require updates to the authentication methods used by your automation scripts. To avoid any interruption in service resulting from mandatory MFA enforcement, Rubrik recommends that you update your scripts to use Service Accounts. + +Administrators can test the environment during the 90-day grace period by enabling time-based one-time password (TOTP) globally for MFA. + +After the grace period elapses, RSC automatically enforces MFA on all user accounts, and the option to disable MFA is not available at the user, global, or organization levels. + *[ > ]: and then diff --git a/saas_migration_organizations_from_rubrik_cdm.md b/saas_migration_organizations_from_rubrik_cdm.md new file mode 100644 index 0000000000000000000000000000000000000000..047fa2462a32f63202c2f429497c8869e8956fc5 --- /dev/null +++ b/saas_migration_organizations_from_rubrik_cdm.md @@ -0,0 +1,18 @@ +# Migration of organizations from Rubrik CDM + +Source: https://docs.rubrik.com/en-us/saas/saas/migration_organizations_from_rubrik_cdm.html + +--- + +# Migration of organizations from Rubrik CDM + +To successfully migrate organizations from Rubrik CDM to RSC, you must complete certain tasks. + +When you are migrating multitenant organizations from Rubrik CDM, you must initially complete the following tasks: + + * Ensuring that the SLA Domains in Rubrik CDM have been upgraded to RSC SLA Domains. + * Ensuring that all the resources are available in RSC. + * Ensuring all the users are available in RSC. + +You must initially create new organizations in RSC and assign resources as appropriate. Besides assigning resources such as SLA Domains and Rubrik clusters, you can also assign workloads and users. + *[ > ]: and then diff --git a/saas_ms_entra_id.md b/saas_ms_entra_id.md new file mode 100644 index 0000000000000000000000000000000000000000..6ef17fe73ad81c366b7e2da9d996d370ed503752 --- /dev/null +++ b/saas_ms_entra_id.md @@ -0,0 +1,17 @@ +# Microsoft Entra ID + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id.html + +--- + +# Microsoft Entra ID + +RSC supports backup and recovery of Microsoft Entra ID. + +When you add Microsoft Entra ID as a protected workload to an SLA Domain, you can use the snapshots from the Microsoft Entra ID directory to recover objects deleted by a user. You can recover objects such as Microsoft Entra ID users, groups, and roles. You can additionally use RSC to search snapshots for specific users and groups. + +You can use Microsoft Entra ID snapshots to update user, or group attributes. The updates you make are reflected in the subsequent snapshot. + +After you recover information for a user on a Microsoft 365 deployment, you can restore the Microsoft 365 application data for the user with the snapshots provided by the Microsoft 365 protected workload on RSC. + +You can optionally configure Microsoft Entra ID for quorum authorization. Microsoft Entra ID supports quorum authorization policies for assigning SLA Domains and for deleting snapshots. After you enable quorum authorization for these policies, RSC requires users to obtain additional approvals to perform these actions on Microsoft Entra ID workloads. diff --git a/saas_ms_entra_id_conditional_access_recovery.md b/saas_ms_entra_id_conditional_access_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..c7f211cfd802a2705522a1a36dbe011f1afbd7c7 --- /dev/null +++ b/saas_ms_entra_id_conditional_access_recovery.md @@ -0,0 +1,33 @@ +# Microsoft Entra ID Conditional Access recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_conditional_access_recovery.html + +--- + +# Microsoft Entra ID Conditional Access recovery + +For Microsoft Entra ID directories that support Conditional Access, RSC can protect Microsoft Entra ID Conditional Access objects and relationships. + +RSC uses SLA Domains to apply data protection policies to the following Microsoft Entra ID Conditional Access objects: + + * Policies + * Named locations + * Authentication contexts + * Authentication strengths + * Terms of use + +Recovering Microsoft Entra ID Conditional Access objects using RSC requires a Microsoft Entra ID license that supports Conditional Access. Additionally, recovering some Conditional Access objects for a Microsoft Entra ID directory protected by RSC, when not using the OAuth protocol, requires specific permissions. + +This table describes the specific permissions required to recover some Conditional Access object types for a Microsoft Entra ID directory not using the OAuth protocol. Object type | Permission +---|--- +Policy | + + * Policy.Read.All + * Policy.ReadWrite.ConditionalAccess + + +Authentication strengths | Policy.ReadWrite.ConditionalAccess +Terms of use | Agreement.ReadWrite.All + +RSC requires that these permissions be applied to the Microsoft Entra ID application before configuring the application to enable recovery. + *[ > ]: and then diff --git a/saas_ms_entra_id_deleting_domains_directories.md b/saas_ms_entra_id_deleting_domains_directories.md new file mode 100644 index 0000000000000000000000000000000000000000..e9baff62fb0cdd31d58b73462b7edf4bf301b5b0 --- /dev/null +++ b/saas_ms_entra_id_deleting_domains_directories.md @@ -0,0 +1,35 @@ +# Deleting a Microsoft Entra ID domain + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_deleting_domains_directories.html + +--- + +# Deleting a Microsoft Entra ID domain + +Delete a Microsoft Entra ID domain from a directory when the domain no longer requires protection. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, select Inventory > Identity > Microsoft Entra ID . + +The inventory list for Microsoft Entra ID appears. + + 4. Click Manage Directories. + +The Settings page appears. + + 5. Click for the Microsoft Entra ID directory, or domain you want to delete and select Delete Domain. + +A confirmation page appears, notifying you that this action is permanent. + + 6. Click Delete. + +## Results + +You have deleted the Microsoft Entra ID domain from the directory and from RSC protection. + *[ > ]: and then diff --git a/saas_ms_entra_id_deleting_snapshot.md b/saas_ms_entra_id_deleting_snapshot.md new file mode 100644 index 0000000000000000000000000000000000000000..b50ef5f7d4630be7ca046b1e7ad9f509288e4bcd --- /dev/null +++ b/saas_ms_entra_id_deleting_snapshot.md @@ -0,0 +1,55 @@ +# Deleting a Microsoft Entra ID snapshot + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_deleting_snapshot.html + +--- + +# Deleting a Microsoft Entra ID snapshot + +Delete a Microsoft Entra ID snapshot that has the Forever retention policy assigned. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, select Inventory > Identity > Microsoft Entra ID . + +The inventory list for Microsoft Entra ID appears. + + 4. In the Domain column, click a Microsoft Entra ID domain. + +Alternatively, enter a name in the search field or use the filters at the top of the list. + +The local page for the domain appears, with the Snapshots card displaying the month view. + + 5. On the Snapshots card, select a day that has a green dot. + +A green dot indicates that RSC successfully took a snapshot on that day. + +The Snapshots card displays the Day view with a list of snapshots. + + 6. Hover over a snapshot and click . + 7. Click Delete Snapshot. + +The confirmation dialog box appears. + + 8. Click Delete. + +If you have created a quorum authorization policy for this operation, you are required to submit a request for quorum authorization. + + 9. (Quorum authorization policy) Select a run type option. + +Option| Description +---|--- +Automatically schedule | Schedules the action to automatically run after approval. +Manually schedule | Schedules the action to run within 24 hours after the approval. Actions not run 24 hours after approval will expire. + + 10. (Quorum authorization policy) Click Submit Request. + +## Results + +RSC deletes the selected snapshot and all the data associated with the snapshot. If you have created a quorum authorization policy, RSC deletes the snapshot according to the specified run type option after the request is approved. + *[ > ]: and then diff --git a/saas_ms_entra_id_devices_protection.md b/saas_ms_entra_id_devices_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..092da73e2f684f2ec54b06901748092e0f003d78 --- /dev/null +++ b/saas_ms_entra_id_devices_protection.md @@ -0,0 +1,24 @@ +# Microsoft Entra ID device protection + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_devices_protection.html + +--- + +# Microsoft Entra ID device protection + +RSC protects Microsoft Entra ID devices by securing critical recovery data against ransomware and accidental loss. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +By protecting Microsoft Entra ID device data, RSC can securely retrieve critical secrets necessary for a full ransomware recovery or forensic investigation. + +RSC delivers recovered data either as a CSV file or as part of the snapshot depending on the device category. For data delivered in CSV files, RSC provides the option to configure a password to prevent unauthorized access. Each CSV file download link expires after 24 hours. + +The following table describes the device protection details for Microsoft Entra ID: Device category | Recovery details | Recovery output +---|---|--- +Device metadata | Configuration and attribute data for the Entra ID device object | CSV file +BitLocker recovery keys | Keys to decrypt volumes encrypted by Microsoft BitLocker | CSV file +Local administrator passwords | Passwords for local administrator accounts on a device | CSV file +Groups | Group device membership details | Snapshot +Administrative units | Administrative unit device membership details | Snapshot + *[ > ]: and then diff --git a/saas_ms_entra_id_downloading_recovery_details.md b/saas_ms_entra_id_downloading_recovery_details.md new file mode 100644 index 0000000000000000000000000000000000000000..902ebba8244e7087542d246bbe9763e948f51771 --- /dev/null +++ b/saas_ms_entra_id_downloading_recovery_details.md @@ -0,0 +1,40 @@ +# Downloading Microsoft Entra ID recovery details + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_downloading_recovery_details.html + +--- + +# Downloading Microsoft Entra ID recovery details + +Download a CSV file containing information about a completed Microsoft Entra ID snapshot recovery. The information includes details about object IDs, object display names, object types, and relationship recovery. + +## Before you begin + +Complete a recovery using any RSC Microsoft Entra ID recovery workflow. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click EventsEvent Logs. + 4. Filter the Event Logs for Microsoft Entra ID recovery events. + +To filter the Event Logs, select Recovery from the Event Type filter and Microsoft Entra ID from the Object Type filter. + +A list of Microsoft Entra ID recovery events appears. + + 5. Select a Microsoft Entra ID recovery event for review. + +The event log entry expands to display the event timeline. + + 6. Click CSV. + +The token for the CSV download expires after 24 hours. + +## Results + +RSC downloads the CSV file that contains the Microsoft Entra ID recovery details. Restore process details, such as relationship creation or deletion, are displayed in JSON format in the CSV file. + *[ > ]: and then diff --git a/saas_ms_entra_id_editing_domain.md b/saas_ms_entra_id_editing_domain.md new file mode 100644 index 0000000000000000000000000000000000000000..edeaaa17e723f8409d0bb07920ae83e89e6ca978 --- /dev/null +++ b/saas_ms_entra_id_editing_domain.md @@ -0,0 +1,61 @@ +# Editing a Microsoft Entra ID domain + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_editing_domain.html + +--- + +# Editing a Microsoft Entra ID domain + +Edit the authentication type and storage method used to recover Microsoft Entra ID domains added to RSC . + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Identity Providers > Microsoft Entra ID. + +The list of Microsoft Entra ID Domains appears. + + 4. Select a domain and click . Then select Edit Domain. + +The Edit Entra ID Domain wizard appears. + + 5. In Domain Details, select an authentication and storage option and click Next. + +Select an access option according to your updated authentication and storage selection. + +Access option| Requirements +---|--- +Configure with OAuth | Select an Access option for the domain. You can choose from the following options: + * Full Access Provides RSC with read and write access to the domain. Additional permissions are not required during a recovery. + * Just-in-time AccessGrant RSC limited read-only access to the domain for ongoing backups. This option requires additional write permissions for recovery.RSC does not support just-in-time (JIT) access for Microsoft 365 workloads. +Configure without OAuth | Add the following information: + * Application ID + * Client secret + +The Add Microsoft Entra ID page appears. + + 6. Click Next. + 7. Click Log in to Microsoft Entra ID. + +The Microsoft Pick an account screen appears. + + 8. Select a Microsoft account. + +For OAuth updates only, the Permissions requested screen appears with a list of permissions requested for RSC. + + 9. Click Accept. + +When the authorization is successful, RSC is granted the updated authentication method for your Microsoft Entra ID domain. + +## Results + +You have updated the authentication type and storage method for the Microsoft Entra ID domain added to RSC. + *[ > ]: and then diff --git a/saas_ms_entra_id_full_domain_recov.md b/saas_ms_entra_id_full_domain_recov.md new file mode 100644 index 0000000000000000000000000000000000000000..b23774ec159d0138d6c54f1b5b0659c6ea4bd38f --- /dev/null +++ b/saas_ms_entra_id_full_domain_recov.md @@ -0,0 +1,20 @@ +# Microsoft Entra ID full domain recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_full_domain_recov.html + +--- + +# Microsoft Entra ID full domain recovery + +Using Microsoft Entra ID full domain recovery, administrators can restore all objects and relationships in a domain from a previous state. You can specify objects to exclude from recovery. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +You may need to restore a full domain, or directory, after a security breach or after major system updates. RSC supports recovering full domains to the source directory. + +During recovery, RSC rolls back all protected items and relationships to their original state at the time of the snapshot. You can opt to exclude objects from this process. + +RSC stores user identities found in the Recycle Bin with the passwords from the time of the snapshot, while those not found receive a new UUID and a unique random password. By default, RSC generates this password and does not share this password with the administrator or user. + +RSC does not support creating a new recovery directory in the Entra ID portal. Additionally, RSC excludes recovering domain settings not covered by the Rubrik backup, such as network settings and domain descriptions. + *[ > ]: and then diff --git a/saas_ms_entra_id_jit_access.md b/saas_ms_entra_id_jit_access.md new file mode 100644 index 0000000000000000000000000000000000000000..6e605ef58b309900f93c51acb5396fddc1203a1b --- /dev/null +++ b/saas_ms_entra_id_jit_access.md @@ -0,0 +1,52 @@ +# Microsoft Entra ID just-in-time access + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_jit_access.html + +--- + +# Microsoft Entra ID just-in-time access + +Just-in-time access for Microsoft Entra ID separates read and write access to align with the principle of least privilege, ensuring that critical write permissions are active only during necessary recovery operations. Just-in-time access is available for Microsoft Entra ID domains using OAuth authentication. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Traditional Microsoft Entra ID protection requires comprehensive read and write permissions to be granted upfront when you add a Microsoft Entra ID domain to RSC. Since these permissions remain active continuously, they create a security exposure and conflict with the principle of least privilege security. + +Just-in-time (JIT) access resolves this exposure by separating the necessary permissions into two categories: + + * Read Permissions + +RSC requests these permissions when you add or modify the Microsoft Entra ID domain in RSC. These permissions remain continuously active and ensure that RSC can successfully complete ongoing backup and retention operations. + + * Write Permissions + +RSC only requests and temporarily assigns these permissions during a granular recovery or full recovery operation. Once the recovery is complete, RSC automatically revokes the temporary write permissions. This limits the Microsoft Entra ID security exposure only to the duration of the recovery. + +## Access options + +When adding or editing a Microsoft Entra ID domain using OAuth to RSC, you must select one of the following access options: + + * Full Access + +This option grants RSC comprehensive read and write permissions to the domain when it is added to RSC. No additional permissions are required during recovery. This is the traditional access option. + + * Just-in-time Access + +This option grants RSC limited read-only access for ongoing backups. Temporary write permissions are requested and assigned only when a recovery is initiated. + +Note: + +Microsoft 365 SharePoint and Teams recovery have a dependency on Microsoft Entra ID for complete metadata restore. As a result, performing a full Teams recovery or a SharePoint relic recovery with JIT access applied to the Microsoft Entra ID domain may result in group metadata loss. To ensure a complete recovery, Rubrik recommends that you apply the Full Access on the Microsoft Entra ID domain before initiating a Microsoft 365 recovery operation. + +You can add or modify a Microsoft Entra ID domain from the Settings menu. + +## Pre-recovery Permission Checks + +Prior to a recovery operation, RSC performs a check for missing permissions on the domain according to the access option. RSC then prompts you for further action to complete the recovery. + +The following table describes the behavior of the RSC pre-recovery permissions check for Microsoft Entra ID recoveries according to the assigned access option: Access option | Description +---|--- +OAuth and JIT access | RSC prompts you to assign the missing permissions. The permissions assignments are temporary and will be removed after the recovery operation is complete. +OAuth and Full Access | If RSC detects missing permissions, you will be given the option to assign them. The permissions assignments persist even after the recovery operation is completed. +Without OAuth | If missing permissions are detected, RSC displays an error message. You must then manually add the required permissions within the Microsoft Entra portal for RSC to proceed with recovery. + *[ > ]: and then diff --git a/saas_ms_entra_id_known_limits_rsc.md b/saas_ms_entra_id_known_limits_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..6db9b43bf7e14657fd211a4c30387da785f32182 --- /dev/null +++ b/saas_ms_entra_id_known_limits_rsc.md @@ -0,0 +1,25 @@ +# Known limitations for Microsoft Entra ID on RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_known_limits_rsc.html + +--- + +# Known limitations for Microsoft Entra ID on RSC + +Microsoft Entra ID on RSC includes some known limitations for recovering groups, users, relationships, and Microsoft Entra ID properties. + +There are some known limitations for Microsoft Entra ID on RSC. + +Limitation | Description +---|--- +Group recovery | You cannot recover: + + * Mail-enabled security groups + * Distribution groups + * Properties of on-premises groups synced from Active Directory (AD) + + +Properties recovery | Recovering some properties requires a supported Microsoft license. +Relationship recovery | RSC limits Microsoft Entra ID relationship recovery to role assignment, group membership, and group ownership for user, group, and role objects. Additionally, RSC recovers only relationships for user, group, or role objects that exist in the directory or that are specified as a part of the recovery. RSC limits relationship recovery to top-level relationships only. Recursive relationship recovery is not supported. +User recovery | RSC can recover up to 1000 users in a single operation. You cannot recover properties from on-premises users synced from AD. + *[ > ]: and then diff --git a/saas_ms_entra_id_non_recov_soft_del_obj_rsc.md b/saas_ms_entra_id_non_recov_soft_del_obj_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..b763c32a86bc011ce7212ba0fe35f9047881400f --- /dev/null +++ b/saas_ms_entra_id_non_recov_soft_del_obj_rsc.md @@ -0,0 +1,31 @@ +# Non-recovery of soft-deleted objects by RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_non_recov_soft_del_obj_rsc.html + +--- + +# Non-recovery of soft-deleted objects by RSC + +RSC does not recover higher-privileged, soft-deleted Microsoft Entra ID user or group objects. Instead, RSC creates new objects, leaving the soft-deleted ones in the Microsoft Recycle Bin. + +RSC does not recover higher-privileged, soft-deleted objects because the enterprise app that performs RSC restore operations does not have sufficient privileges to recover or update these objects. When you restore one of these objects, RSC creates a new object in Microsoft Entra ID for the recovered object, and the higher-privileged, soft-deleted object remains in the Microsoft Recycle Bin. + +## Soft delete and higher-privileged objects + +In Microsoft Entra ID, a soft delete occurs when an object is marked as deleted but is still available on the system. For example, an item is moved to the Recycle Bin but is not permanently deleted. + +Higher-privileged objects are objects that have more privileges than the enterprise app that RSC uses to perform read or write operations, such as backup and restore. + +The Microsoft Entra ID documentation describes privileges for Entra ID user or group objects. + +## Enabling recovery of soft-deleted objects + +To enable the recovery of soft-deleted, higher-privileged objects, you must grant the Privileged Authentication Administrator role to the enterprise application that RSC uses for recovery. You grant this role through the Microsoft Entra admin center. + +The method for granting this role depends on the method used to add the Microsoft Entra ID domain to RSC: + + * OAuth: You grant the Privileged Authentication Administrator role to the enterprise app when adding the domain to RSC. This method requires a valid Microsoft account to complete the configuration. + * Non-OAuth: You grant the Privileged Authentication Administrator role to the enterprise app designated for RSC recovery. In addition, domains not using OAuth require the application ID and client secret when you add the domain to RSC. + +The Microsoft documentation describes the Privileged Authentication Administrator role. + *[ > ]: and then diff --git a/saas_ms_entra_id_obj_recov_across_snapshots.md b/saas_ms_entra_id_obj_recov_across_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..d19312b7e8fe1ddb7b3385ad4be31aebf52c8f1a --- /dev/null +++ b/saas_ms_entra_id_obj_recov_across_snapshots.md @@ -0,0 +1,20 @@ +# Microsoft Entra ID object recovery across snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_obj_recov_across_snapshots.html + +--- + +# Microsoft Entra ID object recovery across snapshots + +With RSC, you can search Microsoft Entra ID user, groups, and roles objects for recovery across different snapshots. This functionality enables recovery of objects and relationships from a specific date and time. + +There might be cases in which you need to recover Microsoft Entra ID objects and relationships for a specific snapshot. For example, you might need to recover a change made to a Microsoft Entra ID user associated with a role at a specific date and time. With RSC, you can search across Microsoft Entra ID snapshots to find the user and role to recover, rather than manually searching through individual snapshots. + +## Searching for Objects and Relationships + +Searching for objects and relationships across snapshots involves selecting the object types and the date range. RSC then displays the filtered results that meet the search criteria. You can then select a snapshot containing those results for recovery. RSC limits recovery to the objects present in the selected snapshot. + +## Snapshot Recovery Date Range or Limitations + +RSC limits the snapshot recovery date range to a maximum of 15 days. While you can filter on-premises user objects and Windows Server AD group objects from the search results, you cannot recover those objects through RSC due to Microsoft Entra ID limitations. + *[ > ]: and then diff --git a/saas_ms_entra_id_obj_relationship_recovery.md b/saas_ms_entra_id_obj_relationship_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..78d43129268e57dd6db4e579309ef2950b2f997b --- /dev/null +++ b/saas_ms_entra_id_obj_relationship_recovery.md @@ -0,0 +1,28 @@ +# Microsoft Entra ID object and relationship recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_obj_relationship_recovery.html + +--- + +# Microsoft Entra ID object and relationship recovery + +RSC recovers various Microsoft Entra ID objects and object relationships, including users, groups, roles, enterprise apps, and app registrations. + +RSC recovers Microsoft Entra ID users, groups, roles, enterprise apps, and app registration objects, along with role assignments, group membership, and group ownership for those object types. Relationship recovery is not recursive. + +You can recover up to 1000 users from a snapshot in a single operation. The recovered user account does not need to be active for the recovery to occur. + +When a user account selected for recovery exists in the current Microsoft Entra ID environment or is recovered from the recycle bin, the user account keeps the existing password. When the user account selected for recovery is present only in the snapshot, or is in the recycle bin at the time of recovery, RSC, by default, generates a one-time login password for that account. If you recover 50 or fewer users in a single operation, you can manually set each password. + +RSC does not store user login passwords. Based on the Microsoft Entra ID directory settings, administrators can prompt users to reset their password when logging in after recovery. + +RSC strongly recommends using two-factor authentication for all user accounts. During Microsoft Entra ID user recovery, RSC re-establishes two-factor authentication for user accounts present only in the snapshot or that are in the recycle bin. For these accounts, RSC prompts each user to set up two-factor authentication when logging in to the Microsoft Entra ID directory after a restore. + +RSC can recover enterprise apps and app registrations independently. Additionally, RSC provides an option to recover app registrations along with the linked enterprise app, provided that both objects are located in the same directory. + +RSC does not recover app registration secrets. After recovery, you can recreate the secret by logging into the Azure portal and searching for the recovered app registration. + +RSC requires the Application.ReadWrite.All permission on the Microsoft Entra ID Domain page in the Azure portal to recover an enterprise app or app registration for a domain added without OAuth. The Microsoft Entra ID documentation provides more details about app permissions. + +Recovering Entra ID objects requires that you are assigned an RSC role that includes the Recover privilege for Microsoft Entra ID objects. + *[ > ]: and then diff --git a/saas_ms_entra_id_protecting.md b/saas_ms_entra_id_protecting.md new file mode 100644 index 0000000000000000000000000000000000000000..697f7fb9b5a9e5d5a4ef62b4bc5713f547efc902 --- /dev/null +++ b/saas_ms_entra_id_protecting.md @@ -0,0 +1,54 @@ +# Protecting Microsoft Entra ID + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_protecting.html + +--- + +# Protecting Microsoft Entra ID + +Choose a data protection policy for a Microsoft Entra ID directory. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, select Inventory > Identity > Microsoft Entra ID . + +The inventory list for Microsoft Entra ID appears. + + 4. Select a domain. + +You can select more than one domain. + + 5. Click Manage protection. + +The Manage Protection window appears. + + 6. Choose a protection option and click Next. + +Option| Description +---|--- +SLA Domain | The SLA Domain is assigned to the object or other databases within the selected object. +Don't protect | An individual SLA Domain assignment is removed from the protected object, and the object will not derive an assignment from any other object. +Clear existing assignment | An individual SLA Domain assignment is removed from the protected object, and the object is protected based on the inheritance rules. + + 7. Click Assign. + +If you have created a quorum authorization policy for this operation, you are required to submit a request for quorum authorization. + + 8. (Quorum authorization policy) Select a run type option. + +Option| Description +---|--- +Automatically schedule | Schedules the action to automatically run after approval. +Manually schedule | Schedules the action to run within 24 hours after the approval. Actions not run 24 hours after approval will expire. + + 9. (Quorum authorization policy) Click Submit Request. + +## Results + +RSC applies the data protection policy to Microsoft Entra ID. If you have created a quorum authorization policy, RSC applies the data protection policy according to the specified run type option after the request is approved. + *[ > ]: and then diff --git a/saas_ms_entra_id_recovery_details.md b/saas_ms_entra_id_recovery_details.md new file mode 100644 index 0000000000000000000000000000000000000000..2d34314e5252ab3d03dc3e53b224732ca8f413a7 --- /dev/null +++ b/saas_ms_entra_id_recovery_details.md @@ -0,0 +1,25 @@ +# Microsoft Entra ID recovery details + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_recovery_details.html + +--- + +# Microsoft Entra ID recovery details + +Information about a Microsoft Entra ID recovery, including details about object IDs, object display names, object types, and relationship recovery. + +You can download Microsoft Entra ID recovery details information as a CSV file from the Events page. + +The following table describes the Microsoft Entra ID recovery parameters. Parameters | Description +---|--- +ID | The object ID at the time of the snapshot. +NEW_ID | The object ID in the Microsoft Entra ID directory created during the recovery process. +DISPLAY_NAME | The object display name in the Microsoft Entra ID directory. +RESULT | The success status of the object during the recovery process. +RESOURCE | The object type recovered or modified during the recovery process. +RESTORED_RELATIONSHIPS | The list of relationships created during the recovery process. +DELETED_RELATIONSHIPS | The list of relationships deleted during the recovery process. +RELATIONSHIP_ERR | The list of errors related to the relationship recovery process. +PROPERTY_ERR | The list of errors related to property recovery. +PASSWORD_SOURCE | The source of the password for restored user objects. + *[ > ]: and then diff --git a/saas_ms_entra_id_recovery_hybrid_env.md b/saas_ms_entra_id_recovery_hybrid_env.md new file mode 100644 index 0000000000000000000000000000000000000000..de1e84418b60eab69e52a9d88f115b54840bedb0 --- /dev/null +++ b/saas_ms_entra_id_recovery_hybrid_env.md @@ -0,0 +1,23 @@ +# Recovery in a hybrid identity environment + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_recovery_hybrid_env.html + +--- + +# Recovery in a hybrid identity environment + +In a hybrid Microsoft Entra ID and Active Directory environment on RSC, you can view Active Directory group and user assignments synced from the Active Directory domain. You can additionally recover relationships for synced Active Directory user and group objects and protect the Active Direct domain. + +In a hybrid Microsoft Entra ID and Active Directory (AD) environment on RSC, you can perform the following operations on user and groups synced to Microsoft Entra ID from the AD domain: + + * Displaying AD group and user assignments + * Recovering AD group and user relationships + +If there is at least one on-premises AD domain that is not protected by Rubrik, RSC optionally directs you to the RSC Active Directory domain page. From this page, you can perform Active Directory domain protection operations, such as SLA Domain assignment. + +To perform property recovery operations on RSC for user and group objects synced from an AD domain, you are required to sync the object to Microsoft Entra ID through Microsoft Entra Connect. The Microsoft documentation describes this operation. After the operation: + + * If the object already exists in Microsoft Entra ID and the sync updates the properties, the object ID remains the same. + * If the object is newly created, the synced user and group objects use a new object ID generated from RSC. + + *[ > ]: and then diff --git a/saas_ms_entra_id_taking_ods.md b/saas_ms_entra_id_taking_ods.md new file mode 100644 index 0000000000000000000000000000000000000000..83ed488939b1667b6a77dc45e4bceafc01137a93 --- /dev/null +++ b/saas_ms_entra_id_taking_ods.md @@ -0,0 +1,37 @@ +# Taking on-demand snapshots of Microsoft Entra ID + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_taking_ods.html + +--- + +# Taking on-demand snapshots of Microsoft Entra ID + +Take on-demand snapshots of Microsoft Entra ID protectable objects in addition to the policy-based snapshots provided by the SLA Domain. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, select Inventory > Identity > Microsoft Entra ID . + +The inventory list for Microsoft Entra ID appears. + + 4. Select a domain. + +Alternatively, enter a name in the search field or use the filters at the top right of the list. + +You can select more than one domain. + + 5. Click Take on demand snapshot. + +The Take on demand snapshot dialog box appears. + + 6. Review the information on the confirmation screen and click Confirm. + +## Results + +RSC adds the specified on-demand snapshot task to the task queue. + *[ > ]: and then diff --git a/saas_ms_entra_id_user_obj_attr_recov.md b/saas_ms_entra_id_user_obj_attr_recov.md new file mode 100644 index 0000000000000000000000000000000000000000..1b0ade8105b72c8d42953d3056912ad55af35077 --- /dev/null +++ b/saas_ms_entra_id_user_obj_attr_recov.md @@ -0,0 +1,29 @@ +# Microsoft Entra ID user object attribute recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_user_obj_attr_recov.html + +--- + +# Microsoft Entra ID user object attribute recovery + +Attribute recovery for a Microsoft Entra ID user object selectively restores specific attributes that were maliciously or accidentally altered without performing a full object restore. You can compare user object attributes from a snapshot against live data and recover only the changed attributes. + +RSC provides two methods to select a snapshot for comparing user attributes against the live environment: + + * Selecting a snapshot from a specific point in time + * Selecting a snapshot from a specific date range + +## Selecting a snapshot from a point in time + +You can use the specific point in time method when you know the exact snapshot containing the correct attribute state, for example, when recovering a snapshot taken just before a configuration error or incident. This method involves navigating directly to the calendar view, selecting a specific snapshot, then the required user object, and choosing the Select Attributes option. RSC then displays a list of attributes that differ from the current state. You can then select one or more of these altered attributes to recover. + +## Selecting a snapshot from a specific date range + +You can use the specific date range method when you are unsure of when a change occurred. You can define a date range of up to 15 days, allowing you to browse a smaller, focused set of snapshots. With this method, you can quickly identify the correct snapshot without reviewing the entire backup history. After you have selected a snapshot within that range, the comparison and recovery steps are the same as the point-in-time method. RSC then displays the altered attributes, and you can choose which ones to restore. + +## User object attribute recovery limitations + +When recovering attributes that support multiple values, such as group memberships, you must choose whether to overwrite or merge the data. Overwriting replaces all current live values with those from the snapshot, while merging keeps existing live values and adds the values from the snapshot. + +RSC displays all user object attributes, including altered attributes, to help you identify changes. However, due to Microsoft Entra ID API restrictions, only some attributes can be recovered. By using the filters provided in RSC, you can identify and recover these attributes. + *[ > ]: and then diff --git a/saas_ms_entra_id_viewing_directories.md b/saas_ms_entra_id_viewing_directories.md new file mode 100644 index 0000000000000000000000000000000000000000..b25411b84ce8cefc0f3a334157dd8654fafae06c --- /dev/null +++ b/saas_ms_entra_id_viewing_directories.md @@ -0,0 +1,27 @@ +# Viewing Microsoft Entra ID directories + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_entra_id_viewing_directories.html + +--- + +# Viewing Microsoft Entra ID directories + +View details for the Microsoft Entra ID directories. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, select Inventory > Identity > Microsoft Entra ID . + +The inventory list for Microsoft Entra ID appears. + + 4. Select a Microsoft Entra ID directory to view its details on the Snapshots page. + +## Results + +RSC displays details about the Microsoft Entra ID directories. + *[ > ]: and then diff --git a/saas_ms_exchange_assigning_sla_domain.md b/saas_ms_exchange_assigning_sla_domain.md new file mode 100644 index 0000000000000000000000000000000000000000..e00728f5ed7e53db308b4bb4a165ee3ef1857c33 --- /dev/null +++ b/saas_ms_exchange_assigning_sla_domain.md @@ -0,0 +1,55 @@ +# Assigning an SLA Domain to a Microsoft Exchange database availability group + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_assigning_sla_domain.html + +--- + +# Assigning an SLA Domain to a Microsoft Exchange database availability group + +Assign an SLA Domain to a Microsoft Exchange database availability group to provide Microsoft database availability group snapshot management based on SLA Domain policies. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Microsoft Exchange Servers inventory card. + +The Microsoft Exchange dashboard appears. + + 5. Select a tab for a supported DAG object. + +Tab| Description +---|--- +Availability Groups | Lists accessible Microsoft Exchange availability groups +Databases | Lists accessible Microsoft Exchange databases + + 6. Click the Microsoft Exchange object name check box. + +Manage Protection is highlighted. + + 7. Click Manage Protection. + +The Manage Protection screen appears. + + 8. Assign an SLA Domain. + +You can assign an existing SLA Domain, create an SLA Domain, or search for a new SLA Domain. You can additionally select options to exclude future SLA Domain assignments or to clear the existing SLA Domain assignment. + + 9. Click Next. + 10. Select an option to either retain the current SLA Domain or inherit a new SLA Domain from the parent SLA Domain. + +Once objects already protected by an SLA Domain are reassigned, existing snapshots conform to the new SLA policy and may expire. + + 11. Confirm the SLA Domain assignment settings and click Assign. + +## Results + +RSC processes the specified assignments and begins protecting the mailbox databases in the selected Microsoft Exchange object as per assignments. + *[ > ]: and then diff --git a/saas_ms_exchange_management.md b/saas_ms_exchange_management.md new file mode 100644 index 0000000000000000000000000000000000000000..634e165b6ddf79e818392efc314f1932047ade94 --- /dev/null +++ b/saas_ms_exchange_management.md @@ -0,0 +1,16 @@ +# Microsoft Exchange management + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_management.html + +--- + +# Microsoft Exchange management + +Rubrik Security Cloud provides backup and recovery for Microsoft Exchange deployments. + +You can add Microsoft Exchange hosts and set Microsoft Exchange backup preferences through the Rubrik Security Cloud (RSC) interface. + +You can assign additional SLA Domains directly to Microsoft Exchange databases that are part of a standalone Microsoft Exchange Server. + +A database backup preference is required for Microsoft Exchange database availability group (DAG) deployments. By default, RSC provides passive backup protection. Passive backup protection permits RSC to back up active database copies if all other passive database copies are offline or unavailable. RSC also offers passive-only backup protection. Passive-only backup protection prevents RSC from backing up active database copies. + *[ > ]: and then diff --git a/saas_ms_exchange_protection.md b/saas_ms_exchange_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..60d09df2e95ba1bec99ff08a14aec0ebbbaf4ab5 --- /dev/null +++ b/saas_ms_exchange_protection.md @@ -0,0 +1,16 @@ +# Microsoft Exchange protection + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_protection.html + +--- + +# Microsoft Exchange protection + +You can use Rubrik Security Cloud data protection features to secure Microsoft Exchange deployments. + +Rubrik Security Cloud (RSC) uses SLA Domains to apply data protection to Microsoft Exchange database availability group (DAG) deployments. Microsoft Exchange deployments using DAG derive the assigned SLA Domain from the Microsoft Exchange DAG. However, an individual assignment to a Microsoft Exchange database overrides the assignment derived from the Microsoft Exchange DAG. + +Microsoft Exchange databases not associated with a DAG require direct SLA Domain assignment. + +RSC supports different database backup preferences. You can set a database backup preference to specify if RSC is authorized to back up an active copy if all passive copies are offline or unavailable. + *[ > ]: and then diff --git a/saas_ms_exchange_protection_hierarchy.md b/saas_ms_exchange_protection_hierarchy.md new file mode 100644 index 0000000000000000000000000000000000000000..95f72ff667489a6ba57dea051816aca17050fae9 --- /dev/null +++ b/saas_ms_exchange_protection_hierarchy.md @@ -0,0 +1,22 @@ +# Protection hierarchy for Microsoft Exchange + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_protection_hierarchy.html + +--- + +# Protection hierarchy for Microsoft Exchange + +RSC provides hierarchy-based, automatic protection for Microsoft Exchange resources. + +The hierarchy-based automatic protection mechanism simplifies assigning protection to each object in a Microsoft Exchange deployment. + +Exchange Servers and databases that are part of a Microsoft database availability group (DAG) follow a hierarchy. Additional SLA Domains can be assigned directly to Microsoft Exchange databases that are part of a standalone Exchange Server. An SLA Domain cannot be assigned to standalone Exchange Servers. + +Level | Description +---|--- +Microsoft Exchange DAG | Any Microsoft Exchange database that is part of a DAG can be assigned an SLA Domain at the Microsoft Exchange DAG level. If assigned, all Microsoft Exchange databases then inherit that SLA Domain assignment. +Exchange Server | Any Exchange Server that is part of a Microsoft Exchange DAG derives its protection from the Microsoft Exchange DAG. +Microsoft Exchange database | An SLA Domain or do not protect setting assigned to an Microsoft Exchange database overrides an assignment derived from the Microsoft Exchange DAG. + +All Microsoft Exchange objects in a DAG are assigned the SLA Domain, SD1. A separate SLA Domain, SD2, is then assigned to a single Microsoft Exchange database, overwriting SD1. + *[ > ]: and then diff --git a/saas_ms_exchange_recovering_snapshot.md b/saas_ms_exchange_recovering_snapshot.md new file mode 100644 index 0000000000000000000000000000000000000000..9d17ce58cdbf8b6ca35290d8e7b8020caa2158f2 --- /dev/null +++ b/saas_ms_exchange_recovering_snapshot.md @@ -0,0 +1,58 @@ +# Recovering a Microsoft Exchange database snapshot + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_recovering_snapshot.html + +--- + +# Recovering a Microsoft Exchange database snapshot + +You can recover on-demand and scheduled snapshots for Microsoft Exchange databases. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Microsoft Exchange Servers inventory card. + +The Microsoft Exchange dashboard appears. + + 5. Select a database. + * Databases + * Availability Groups + 6. (Availability groups) Select an availability group name. + 7. Click on a database name. + +The Database details page appears. + + 8. Select a snapshot from the calendar view and click Recover. + +The Exchange Database Recovery screen appears. + + 9. Click Next. + +The SMB configuration screen appears. + + 10. Confirm the Rubrik cluster name. + 11. Provide the remaining Server Message Block (SMB) configuration details. + +Detail| Description +---|--- +Domain | The fully-qualified Active Directory domain name. +Username | The user name or user names associated with the database. +Client IP addresses | Client IPv4 addresses associated with the database. The client IP is the secure address to access the SMB share where Kroll is installed. + +You can enter multiple user names and Client IP addresses, separated by commas. + + 12. Click Mount. + +## Results + +A new SMB share is created to host the database files, using the Rubrik cluster as the datastore. + *[ > ]: and then diff --git a/saas_ms_exchange_server.md b/saas_ms_exchange_server.md new file mode 100644 index 0000000000000000000000000000000000000000..2921cf659aeed0bf1ddf1b3d66802a4f12115a3c --- /dev/null +++ b/saas_ms_exchange_server.md @@ -0,0 +1,13 @@ +# Microsoft Exchange Server + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_server.html + +--- + +# Microsoft Exchange Server + +Rubrik Security Cloud provides protection for Microsoft Exchange Servers. + +Rubrik Security Cloud (RSC) protects both standalone Microsoft Exchange Servers or Microsoft Exchange Servers that are part of a database availability group (DAG). In Microsoft Exchange, data is protected at the database level. + +The volume group workflow is disabled to prevent conflicts between RSC and Microsoft DAG operations. If the volume workgroup is enabled, a notification message appears on the Microsoft Exchange hosts page indicating that the volume group workflow is active. Contact Rubrik Support to disable or enable the volume group workflow. diff --git a/saas_ms_exchange_snapshots.md b/saas_ms_exchange_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..971b2281b882c6d9700780df413d0b4ea54186ba --- /dev/null +++ b/saas_ms_exchange_snapshots.md @@ -0,0 +1,14 @@ +# Microsoft Exchange snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_snapshots.html + +--- + +# Microsoft Exchange snapshots + +Rubrik Security Cloud protects and manages data by taking snapshots of the source object. + +Rubrik Security Cloud (RSC) provides Microsoft Exchange object protection at the database level. You can recover both Microsoft database availability group (DAG) databases and databases not associated with a DAG. + +Live Mount is supported for Microsoft Exchange database recovery. Mailbox recovery is supported through a third-party data recovery tool, such as Kroll OnTrack. + *[ > ]: and then diff --git a/saas_ms_exchange_workflow.md b/saas_ms_exchange_workflow.md new file mode 100644 index 0000000000000000000000000000000000000000..681e57d79c982eae5eb14f63a0b6fe5e7fe31c2f --- /dev/null +++ b/saas_ms_exchange_workflow.md @@ -0,0 +1,12 @@ +# Microsoft Exchange workflow + +Source: https://docs.rubrik.com/en-us/saas/saas/ms_exchange_workflow.html + +--- + +# Microsoft Exchange workflow + +The Microsoft Exchange workflow provides a summary of the actions involved in protecting Microsoft Exchange data on Rubrik Security Cloud. + +When all the hosts for the Microsoft Exchange database availability group (DAG) are added, Rubrik Security Cloud (RSC) retrieves the details of the Microsoft Exchange hierarchy. RSC performs instance discovery every 30 minutes when the instance is manually refreshed or when the host is added to the Rubrik cluster or to RSC. This information is initially stored in the Rubrik cluster. A periodic metadata sync between the Rubrik cluster and RSC pushes the metadata to RSC. + *[ > ]: and then diff --git a/saas_mssql_restore_recovery_SQLServer_databases.md b/saas_mssql_restore_recovery_SQLServer_databases.md new file mode 100644 index 0000000000000000000000000000000000000000..dc74a087137e6b78a2e2a6a5cb192e6413336fe0 --- /dev/null +++ b/saas_mssql_restore_recovery_SQLServer_databases.md @@ -0,0 +1,24 @@ +# Restore and recovery of Microsoft SQL Server databases + +Source: https://docs.rubrik.com/en-us/saas/saas/mssql_restore_recovery_SQLServer_databases.html + +--- + +# Restore and recovery of Microsoft SQL Server databases + +A Rubrik cluster can be used to manage backup, restore, and recovery of Microsoft SQL Server databases. + +You can recover a database from snapshots of the database using the Rubrik cluster. When transaction logs for the database have been backed up, you can also recover the database to any point in time within the backed up data using the Rubrik cluster. + +For each protected database, the Rubrik cluster provides a Snapshots card. Use the Snapshots card to select a recovery point and to start the recovery process. The following options are available for database recovery: + + * The source database can be replaced with a copy of the database from the selected recovery point. + * A database can be exported as a new database from a recovery point. The export can be to the same Microsoft SQL Server instance or to another Microsoft SQL Server instance on any available Windows Server host. + * A selected database recovery point can be used to create a Live Mount. The recovered database uses the Rubrik cluster as the datastore. + * A selected snapshot and the transaction logs can be downloaded together as a single zip file. + * A selected snapshot and the transaction logs can be downloaded from the archival location to stage them locally. This can decrease the time required to restore the database. + +Note: + +The Rubrik cluster can back up Microsoft SQL Server system databases, such as: ‘master’, ‘model’, and ‘msdb’, but backups of these system databases cannot be directly restored from the Rubrik cluster. However, system database backups can be exported or created as Live Mounts. + *[ > ]: and then diff --git a/saas_mssql_rubrik_backup_service.md b/saas_mssql_rubrik_backup_service.md new file mode 100644 index 0000000000000000000000000000000000000000..8cb228e82e02063cd8e52cb709f51c7910474828 --- /dev/null +++ b/saas_mssql_rubrik_backup_service.md @@ -0,0 +1,14 @@ +# Rubrik Backup Service for SQL Server databases + +Source: https://docs.rubrik.com/en-us/saas/saas/mssql_rubrik_backup_service.html + +--- + +# Rubrik Backup Service for SQL Server databases + +The Rubrik Backup Service backs up and restores SQL Server databases and provides enhanced integration with SQL Server protected resources and host systems. + +You can back up and restore SQL databases by installing Rubrik Backup Service (RBS) on a SQL Server. You can download and install RBS while you add a Windows Server host. You can also download and install RBS on an existing Windows Server host. + +For more information and a description of the permissions required to add RBS to a SQL Server protected by RSC, see Using Service SIDs to grant permissions to services in SQL Server in the Microsoft SQL Server documentation. + *[ > ]: and then diff --git a/saas_mssql_unlinking_multi_datacenter_avail_grp.md b/saas_mssql_unlinking_multi_datacenter_avail_grp.md new file mode 100644 index 0000000000000000000000000000000000000000..4d33aae403b2bab97e801c7611f93c06714f6ea5 --- /dev/null +++ b/saas_mssql_unlinking_multi_datacenter_avail_grp.md @@ -0,0 +1,45 @@ +# Unlinking multi-datacenter availability groups + +Source: https://docs.rubrik.com/en-us/saas/saas/mssql_unlinking_multi_datacenter_avail_grp.html + +--- + +# Unlinking multi-datacenter availability groups + +You can unlink multi-datacenter availability groups from a bidirectional SLA Domain when you no longer need protection for primary and secondary database replicas for both Rubrik clusters. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the SQL Server Databases inventory card. + +The SQL Server Databases page appears. + + 5. Click Availability Groups. + +The Availability Groups tab appears. + + 6. Click Manage Protection. + 7. Click Don't Protect. + 8. Click Next. + 9. Clear the Link the selected availability group databases in the clusters below selection. + 10. Click Next. + 11. Confirm that RSC no longer protects the selected objects. + 12. Click Assign. + +## Results + +RSC triggers an asynchronous job to unlink the objects and remove protection. + +## What to do next + +You can view the job progress on the Events page. Monitor the Availability Groups tab, and the unlinking is complete when the selected objects no longer show a Linked label and an assigned SLA Domain. + *[ > ]: and then diff --git a/saas_mssql_windows_server_failover_clustering.md b/saas_mssql_windows_server_failover_clustering.md new file mode 100644 index 0000000000000000000000000000000000000000..6e1fb62aa5156e922430296bcad5b95bfee8be02 --- /dev/null +++ b/saas_mssql_windows_server_failover_clustering.md @@ -0,0 +1,16 @@ +# Windows Server Failover Clustering + +Source: https://docs.rubrik.com/en-us/saas/saas/mssql_windows_server_failover_clustering.html + +--- + +# Windows Server Failover Clustering + +The Rubrik cluster provides protection for Windows Server Failover Clustering at the failover cluster instance level. + +The Rubrik Backup Service software must be installed on each of the Windows Server Failover Clustering (WSFC) nodes used by an failover cluster instance (FCI). Specific Windows instructions are provided when downloading and installing the Rubrik Backup Service (RBS) software. + +For the account running the Rubrik Backup Service, the View server state permission must be explicitly enabled at the server scope level for each Microsoft SQL Server database in the FCI. + +Adding all WSFC nodes to the Rubrik cluster ensures continuous protection of Microsoft SQL Server databases in the event of a failover. The Rubrik cluster cannot protect the databases of a Microsoft SQL Server database when the active instance is on a WSFC node that has not been added to the Rubrik cluster. + *[ > ]: and then diff --git a/saas_mt_MFA_for_tenant_org.md b/saas_mt_MFA_for_tenant_org.md new file mode 100644 index 0000000000000000000000000000000000000000..96f6fa84c5b7bdcadb91679ffde9b07c7b8bbb7f --- /dev/null +++ b/saas_mt_MFA_for_tenant_org.md @@ -0,0 +1,24 @@ +# Multifactor authentication for a tenant organization + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_MFA_for_tenant_org.html + +--- + +# Multifactor authentication for a tenant organization + +Enabling multifactor authentication adds one or more factors to the basic authentication process and is recommended to protect against ransomware and other vulnerabilities. + +Rubrik recommends using multifactor authentication (MFA) to increase the security of your data. The Multi-Factor Authentication page from the Settings menu in RSC is available to both global organization and tenant organization administrators for configuration. The Organizations must conform to or implement stringent policies toggle is available only to the global organization administrator. If this is enabled, tenant organizations must conform to global MFA settings. + +The Enforce MFA for all users in the organization toggle is turned on by default during the Add organization process. Tenant organization administrators can configure their own MFA settings if global enforcement is disabled. You must provide tenant organizations with access management privileges during the tenant organization creation process to enable them to configure their own MFA settings. + +When a user account is a member of an organization that has MFA enabled, MFA is enforced for that account across all organizations. + +The following considerations apply when configuring MFA for multitenancy: + + * The global administrator can enforce MFA on all user accounts through MFA settings. If enforced, only the global administrator can remove that enforcement through the MFA settings in the global organization. + * The global administrator can enforce and remove enforcement of MFA on a single organization through the organization creating or editing process. The tenant organization administrator can enforce and remove MFA on the organization through organization MFA settings. If enforced at the organization level, then the organization MFA enforcement must be turned off to remove MFA enforced on a user account. + * The global administrator can enforce or remove MFA on a single user account through the Users listing page. The tenant organization administrator can enforce MFA on a single user account, only for users authorized to the specific tenant organization (even if the user is authorized to other tenant organizations) through the organization user listing page. The tenant organization administrator can only remove MFA enforced on a user if the user is only part of that tenant organization. + * A user can enable MFA themselves through User Preferences page. + + *[ > ]: and then diff --git a/saas_mt_SSO_options_for_tenant_organizations.md b/saas_mt_SSO_options_for_tenant_organizations.md new file mode 100644 index 0000000000000000000000000000000000000000..a03be6f0181c64f009fc9d014798ea27c3c6db2f --- /dev/null +++ b/saas_mt_SSO_options_for_tenant_organizations.md @@ -0,0 +1,24 @@ +# SSO options for tenant organizations + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_SSO_options_for_tenant_organizations.html + +--- + +# SSO options for tenant organizations + +The global organization administrator can configure SSO options for user access in the tenant organizations. + +An SSO user account has access and privileges only in the authorized organization and groups. The SSO page from the Settings menu in RSC is available to both global organization and tenant organization admins for configuration to manage SSO settings. The type of SSO options for tenant organizations can be configured by the global organization administrator as part of the organization creation process. There are three options for selection: + + * Enable per tenant access control, which allows the tenant organization to set up a dedicated SSO provider for the organization. The tenant organization has access to SSO settings and can configure the identity provider (IdP). + +A tenant organization cannot have the same IdP as another tenant organization or the global organization with this option. Once the tenant organization has configured the IdP for their organization, you cannot modify this option from the global organization until the IdP is deleted from the tenant organization. + + * Inherit SSO from the global org, which allows the tenant organization to use the same SSO provider as the global organization. Only the global organization can modify or control the IdP and the tenant organization does not have those privileges. + +The tenant organization will not have access to the SSO settings. In this option, the global organization administrator can add SSO groups to the tenant organization as part of the organization creation process and the tenant organizations can then authorize the group to set the level of privileges. The tenant organization cannot authorize a group that it has not been assigned. A group assigned to the tenant organization will not show up in the groups list until it is authorized with a role. + + * Keep all the users local, which allows all user accounts to sign in to the RSC account with RSC credentials. No IdP will be used in the tenant organization. SSO settings will not be available to the tenant and SSO groups cannot be created in the tenant organization if this option is selected. + +Once registered, an SSO user account cannot be deleted from the Users page. To remove an SSO user account, the groups the user belongs to need to be unauthorized or the IdP that the user account belongs to needs to be deleted. If an IdP has been configured, deleting the IdP provider will delete SSO user accounts and groups associated with that IdP. + *[ > ]: and then diff --git a/saas_mt_archival_locations_for_tenant_orgs.md b/saas_mt_archival_locations_for_tenant_orgs.md new file mode 100644 index 0000000000000000000000000000000000000000..ae5a4bd94e31467fa7641cfb2b8d6a04868435a7 --- /dev/null +++ b/saas_mt_archival_locations_for_tenant_orgs.md @@ -0,0 +1,16 @@ +# Archival locations for tenant organizations + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_archival_locations_for_tenant_orgs.html + +--- + +# Archival locations for tenant organizations + +The global administrator can assign archival location options or archival view and manage privileges to the tenant organization during organization creation or editing. + +In RSC, archival location management privileges can be assigned to roles at the global organization level. Roles with archival privileges can manage archival locations. These permissions are assigned by default to the global organization administrator who can view, add, and modify archival locations. + +For a tenant organization, archival locations are configured as part of an SLA Domain which can then be assigned to an organization as part of the organization creation or edit process. Tenant organization archival locations function according to the configuration in the SLA Domain. + +Based on permissions assigned, tenant organizations can view specifically assigned archival data center locations and relevant information, including information about the storage used. The Data Centers page displays all the information for the archival location. + *[ > ]: and then diff --git a/saas_mt_cert_csr_mgmt_orgs.md b/saas_mt_cert_csr_mgmt_orgs.md new file mode 100644 index 0000000000000000000000000000000000000000..a00fe010d389e15a080094dbddbd89dd0c2d9cde --- /dev/null +++ b/saas_mt_cert_csr_mgmt_orgs.md @@ -0,0 +1,14 @@ +# Certificate and Certificate Signing Request management for organizations + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_cert_csr_mgmt_orgs.html + +--- + +# Certificate and Certificate Signing Request management for organizations + +Tenant organizations with the required permissions can view and manage certificates and Certificate Signing Requests for their organizations. + +The global administrator can create and assign certificates to tenant organizations. Tenant organizations with view and manage certificate permissions can then use the certificates and Certificate Signing Requests (CSRs) according to their requirements. + +The global administrator can also assign system configuration permissions to create and manage new certificates to the tenant organization when creating or editing an organization. Tenant organization administrators, by default, can then create and manage certificates for their organizations. Tenant organization administrators can also assign view and manage permissions for certificates and CSRs to tenant organization users who can then manage certificates and CSRs according to their requirements. + *[ > ]: and then diff --git a/saas_mt_creating_tenant_org.md b/saas_mt_creating_tenant_org.md new file mode 100644 index 0000000000000000000000000000000000000000..e11379d3d944765d53fff1e7ad903692a1aabe5f --- /dev/null +++ b/saas_mt_creating_tenant_org.md @@ -0,0 +1,145 @@ +# Creating a tenant organization + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_creating_tenant_org.html + +--- + +# Creating a tenant organization + +Create a tenant organization by adding a name, adding user accounts, and assigning clusters and objects to protect. + +## Before you begin + +You must have the Manage Organization privilege when you log in to enable global organization user accounts to create a tenant organization. The Manage Organization privilege is only available to global administrators. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Organizations > Management. + +The Organization Management page appears. + + 4. Click Add Organization. + +The Create Organization wizard appears, unless DNS is not configured, in which case Add Organization is not visible, and you get a message stating that DNS configuration is required, along with a link to the Network Settings page. + + 5. In Organization Name, enter a name for the organization. + 6. In Unique Organization ID, enter a unique ID for the organization. + +You can accept the generated unique Organization ID or enter your own. The unique Organization ID must be a combination of lowercase letters or numbers, or a mix of both, and must have a total size less than or equal to 20 characters. The Organization ID determines the unique URL for that tenant organization to use to access its RSC organization. + + 7. In Description, enter a description to identify the organization. + 8. Select an SSO option. + +Option| Description +---|--- +Enable per tenant access control | Allows use of a dedicated SSO provider for the organization. +Inherit SSO from the organization | Allows users to inherit the SSO provider of the global organization or Managed Service Provider (MSP). +Keep all the users local | Makes all user accounts authenticate locally to the RSC account. + + 9. Turn on Enforce MFA for all users in the organization. + +This option is enabled by default. Organization administrators can configure their own MFA settings if enforcement is not enabled. + + 10. Turn on Tenant organization inherits IP allowlist and settings from the global organization when the tenant organization should inherit settings and lists from the global organization. + 11. Click Next. + 12. Select user accounts to assign to the organization. + +You can assign the organization administrator role to user accounts, SSO groups, or both. At least one user account should have organization administrator privileges. When you select No in the Organization Administrator option, an organization administrator can assign specific privileges to the user or SSO group. + +You can click the users selected link to open the Assigned Users dialog box, where you can view and make changes to the selected users. + + 13. **Optional:** Invite user accounts to join the organization. + +An email invitation is sent to the user account when the organization is created. + + 14. **Optional:** Authorize SSO groups to the organization by creating an SSO group and assigning permissions for the organization administrator role. + +This option is available only when you select the Inherit SSO from the organization option as the SSO option. + + 15. Click Next. + 16. Select the Rubrik clusters your organization can access. + +Click the clusters selected link to open the Selected Clusters dialog box where you can view and make changes to the selected clusters. + + 17. Click for any selected cluster to set cluster privileges for the organization, including Cluster configuration, SMB Settings, and Replication configuration privileges. + 18. **Optional:** Turn on Use cluster as a replication to choose how the organization uses the target cluster. + +Option| Description +---|--- +Block resource assignment | This organization still has access to replicated objects originating from its own source objects, but does not have access to other objects, SLA Domains, or resources on the target cluster. +Allow resource assignment | Additional workloads and objects are available for selection in the subsequent Data Management step.Using All current and future with Allow resource assignment for a data management workload assignment grants the tenant organization full access to workload data on the replication target cluster. + + 19. Click Done and then click Next. + +The Assign Privileges page appears. + + 20. Click Configure in the Data Management Permissions card to select an option. + +The Assign Data Management Privileges page appears. + + 21. Select an option to assign data management privileges. + +Option| Description +---|--- +To select specific object types, select the workload checkbox . | Configures permissions to the data sources by object type. You can individually select objects to add to the organization, and configure permissions to data sources by object type.You can add a data source only to a single organization. Adding an object assigned to another organization results in an error. +To select all object types, select the checkbox at the top of the list. | Assigns all current and future objects on the selected clusters to the organization that has the permissions. + + 22. **Optional:** Click to assign the following for the workload: + + * Workloads + * Recovery targets + * Privileges +You can select specific objects and recovery targets or all existing and future objects and recovery targets. + + 23. Click Next. + +The Assign Datacenter Archival Locations page appears. + + 24. Select the archival locations to which this tenant organization has view access. + +Option| Description +---|--- +Select all existing and future archival locations | Provides the tenant organization view access to storage locations across all current and later added data center sites. +Select specific archival locations | Provides the tenant organization view access to specific storage locations within the data center infrastructure. + +Tenant organizations can have view permissions only on archival locations. + +Click the items selected link to open the Selected Datacenter Archival Locations dialog box. You can view and make changes to the list there. + + 25. Click Next. + +The Select SLA Domains page appears. + + 26. **Optional:** Turn on Self-Service to allow the organization to create and manage all existing and future SLA Domains that the organization creates. + 27. Select an option for assigning SLA Domains to the organization. + +Option| Description +---|--- +Select specific SLA Domains for the organization | Provides access to the SLA Domains dialog box, where you can view and make changes to the selected SLA domains for the tenant organization. +Select all existing and future SLA Domains created by the Global Org | Provides the tenant organization view-only privileges for SLA Domains created by the global organization. + + 28. Click Done. + 29. Click Edit in the Assign System Configuration Privileges card to select the system configuration permissions to assign to the organization. + +System preferences and Access management privileges are assigned by default. You can also choose Certificate Management, Events, Reports, and Manage legal hold privileges on this page. + + 30. Click Done. + 31. Click Next. + 32. Select optional additional settings for the tenant organization. + +Option| Description +---|--- +Cross-Account Replication | Allows clusters managed in different RSC accounts to establish a connection with this organization for replication. +Block Service Accounts | Stops all operations and management of service accounts in this organization. + + 33. Click Create. + +## Results + +RSC creates the tenant organization and displays it on the Organizations page. + *[ > ]: and then diff --git a/saas_mt_editing_tenant_org_storage_quota.md b/saas_mt_editing_tenant_org_storage_quota.md new file mode 100644 index 0000000000000000000000000000000000000000..297686751797a9442101aa2154be4897740d14fd --- /dev/null +++ b/saas_mt_editing_tenant_org_storage_quota.md @@ -0,0 +1,51 @@ +# Editing the tenant organization storage quota + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_editing_tenant_org_storage_quota.html + +--- + +# Editing the tenant organization storage quota + +Edit the tenant organization storage quota to increase or decrease the storage limits for an organization. + +## About this task + +You require a user account with the administrator role to complete this task. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Organizations > Management. + +The Organizations page appears. + + 4. Click in the row for the organization and click Manage Quotas. + +You can also access the Manage Quotas dialog box from the organization details page. + +The Manage Quotas dialog box appears. + + 5. Click Edit Quota for the Rubrik cluster that you want to edit the storage quota. + +The dialog box lists all the clusters that the organization has access to. + + 6. In the Soft Limit and Hard Limit fields, edit the values for the storage quota limits. + +The soft limit value must be less than or equal to the hard limit value. + + 7. Click Done. + +You can assign storage quotas for multiple organizations. + + 8. Click Save. + +RSC displays a message that the organization quotas have been updated. + +## Results + +RSC assigns the updated storage quota to the organization. + *[ > ]: and then diff --git a/saas_mt_events_reports_tenants.md b/saas_mt_events_reports_tenants.md new file mode 100644 index 0000000000000000000000000000000000000000..21c83b2d675465adc7b1e28e868aa87da14cb5d3 --- /dev/null +++ b/saas_mt_events_reports_tenants.md @@ -0,0 +1,16 @@ +# Events and reports for tenant organizations + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_events_reports_tenants.html + +--- + +, replication configuration privileges can be assigned to roles at the global organization level. User accounts with privileges to view and edit replication and edit network throttling will be able to view the replication targets page and pause, resume, and update network throttling.# Events and reports for tenant organizations + +Events and reports for tenant organizations are limited to the objects and privileges assigned to them. + +The global administrator of the RSC account can create, view, and filter data in reports. + +Tenant organization user accounts can view all report types. Tenant organization reports reflect data according to the organization and tenant organization user accounts can view data that they have privileges on. All tenant organizations with privileges can view a new custom report created by the global organization, though the data in the report only reflects the objects for which the user account has privileges. + +The global organization administrator can also view and filter the data in Events page for all the tenant organizations. The Events page for the tenant organization and for tenant organization user accounts displays data according to the organization and privileges assigned. + *[ > ]: and then diff --git a/saas_mt_global_organization_administrator_privileges.md b/saas_mt_global_organization_administrator_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..4127d656edce45058202dfdd41b598dfb0755c89 --- /dev/null +++ b/saas_mt_global_organization_administrator_privileges.md @@ -0,0 +1,20 @@ +# Global organization administrator privileges + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_global_organization_administrator_privileges.html + +--- + +# Global organization administrator privileges + +The global organization administrator or global organization owner role has privileges in the global organization as well as the tenant organization. + +From the global organization dashboard, the global organization administrator in RSC can: + + * View, create, and manage the tenant organizations and assign privileges to them. They can also edit or delete tenant organizations. + * View and create the global organization user accounts and their roles and permissions. + * Create SLA Domains with replication and archival targets that can be assigned to a tenant organization. + * Add, edit, or delete replication targets, archival locations, and SLA Domains, including those created by the tenant organization. Assign permissions to tenant organizations for viewing and managing replication targets, viewing data center archival locations, and managing the creation and editing of SLA Domains. Also provide permissions to view and use SLA Domains created by the global organization. + * Manage, protect, and recover objects assigned to the tenant organization. + * View reports and events for objects assigned to the organization. + + *[ > ]: and then diff --git a/saas_mt_multitenancy_in_rsc.md b/saas_mt_multitenancy_in_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..89d4a41ea34042b17c29bc7edf7738667b8bb112 --- /dev/null +++ b/saas_mt_multitenancy_in_rsc.md @@ -0,0 +1,21 @@ +# Multitenancy in RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_multitenancy_in_rsc.html + +--- + +# Multitenancy in RSC + +RSC supports multitenancy with some similarities to and some differences from the multitenancy support provided on Rubrik clusters. + +Multitenant organizations created in Rubrik CDM do not appear in the RSC account. However, objects, SLA Domains, archival locations, and replication pairings created in Rubrik CDM are available in RSC after the initial connection and can subsequently be assigned to RSC organizations. Migrating multitenancy from Rubrik CDM requires that you first create organizations in RSC and then assign resources to them. + +The following limitations apply for multitenancy in RSC: + + * A tenant organization cannot create or add subscriptions for cloud-native services such as, AWS EC2 instances and EBS volumes, Azure virtual machines, and GCE instances. Only the global organization can add subscriptions for tenant organizations. + * Tenant organizations in RSC cannot access or build on the existing global allowlist or explicitly grant either host or subnet access or both at an individual organization level. Only the global organization can access or build the existing global allowlist. + * RSC does not support nested multitenancy, where a tenant organization can create sub-organizations to logically isolate shared compute, storage, and network resources. + * RSC does not support creating service accounts for tenant organizations. + * RSC does not support Data Threat Analytics, Data Security Posture, and Orchestrated Application Recovery for multitenant organizations. + + *[ > ]: and then diff --git a/saas_mt_multitenant_organizations.md b/saas_mt_multitenant_organizations.md new file mode 100644 index 0000000000000000000000000000000000000000..74979101e0f44b43107052db6ab7979868121e9a --- /dev/null +++ b/saas_mt_multitenant_organizations.md @@ -0,0 +1,28 @@ +# Multitenant organizations + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_multitenant_organizations.html + +--- + +# Multitenant organizations + +Multitenancy in RSC refers to the logical isolation of shared compute, storage, and network resources in such a way that each organization can only see and access data that belongs to that organization, especially for shared infrastructure platforms. + +Multitenancy in RSC enables a global organization to delegate administrative capabilities to multiple tenant organizations. The global organization is the primary owner and operator of the RSC domain and is responsible for the creation and management of tenant organizations. The global organization defines the resources, workloads, SLA Domains, and permissions for the tenant organization. + +The global organization is administered by a user account assigned the owner or administrator role. The owner or administrator role has access to all resources and grants privileges to other users, including tenant organization administrators. Tenant organizations can only be set up by user accounts assigned the Manage Organization privilege. The owner and administrator roles in the global organization are assigned this privilege by default. + +Each tenant organization in a multitenant RSC account has access to a set of resources and a subset of administrative privileges defined by the global organization. The administrators of the tenant organization can exercise these administrative privileges independently of each other and of the global organization administrators. + +An RSC account can have one global organization and any number of tenant organizations. A tenant organization comprises: + + * Rubrik clusters + * Cloud accounts + * Workload objects + * SLA Domains + * Replication and archival targets + * Users and SSO groups + * Service credentials + * Reports and events + +Organizations created in Rubrik CDM will not appear in the RSC account. However, objects, SLA Domains, archival locations, and replication pairings created in Rubrik CDM are available in RSC after the initial connection. If you are migrating multitenancy from Rubrik CDM, you must initially create organizations in RSC using the Add organization wizard, and assign resources to them. diff --git a/saas_mt_sla_domain_management_multitenancy.md b/saas_mt_sla_domain_management_multitenancy.md new file mode 100644 index 0000000000000000000000000000000000000000..4e0ab42ce626521bc8e664913a87b02e4d43c273 --- /dev/null +++ b/saas_mt_sla_domain_management_multitenancy.md @@ -0,0 +1,14 @@ +# SLA Domain management + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_sla_domain_management_multitenancy.html + +--- + +# SLA Domain management + +In a multitenant environment, SLA Domains can be assigned to tenant organizations by the global organization administrator during the tenant organization creation or editing process. Tenant organizations can also be provided the ability to create and manage their own SLA Domains. + +The SLA Domain page in the global organization in RSC displays the list of SLA Domains, details on archival and replication, and the tenant organizations they are assigned to. The global organization administrator can assign privileges for specific SLA Domains or all and future SLA Domains created on RSC to a tenant organization as part of the creation or editing process. The global organization administrator can view, filter, and manage all SLA Domains for the RSC account from the SLA Domain page. SLA Domains managed by Rubrik CDM cannot be assigned to tenant organizations in RSC. + +The tenant organization user accounts can use the assigned SLA Domains for data protection but cannot edit or delete SLA Domains assigned to them. When tenant organizations are assigned the self-service permission for SLA Domains, they can create, edit, and manage SLA Domains for their organization. They can also use the archival locations and replication targets that they have permissions on when creating SLA Domains. The SLA Domains created by the tenant organization are manageable by the global organization. Tenant organization administrators assigned data management protection permissions by object type or for specific objects are able to manage protection for those objects. The SLA Domains page and the Inventory page in the tenant organization only displays the objects assigned to the organization. + *[ > ]: and then diff --git a/saas_mt_tenant_org_administrator_privileges.md b/saas_mt_tenant_org_administrator_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..7d38c5c7eff4c393f9f7b6b6a877972886370199 --- /dev/null +++ b/saas_mt_tenant_org_administrator_privileges.md @@ -0,0 +1,30 @@ +# Tenant organization administrator privileges + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_tenant_org_administrator_privileges.html + +--- + +# Tenant organization administrator privileges + +The tenant organization administrator role is assigned specific permissions by the global organization administrator. + +The tenant organization administrator role is assigned privileges at the time of tenant organization creation. Based on the privileges assigned, tenant organization administrators can manage data management and system configuration for their organization. While data management privileges can be assigned at the object level or for all object types, system configuration privileges to view system preferences, and view and manage user account access are assigned by default. Assigning events and reports privileges is optional. + +Tenant organization administrator privileges will depend on the privileges assigned to that organization and privileges not assigned to an organization will not be available to a user account within that organization. + +At least one tenant organization user account must have organization administrator privileges to configure access for non-administrators. The tenant organization administrator can create roles for their organization and assign specific permissions to those roles. From the tenant organization dashboard, the tenant organization administrator can: + + * View and create the user accounts and roles in their organization + * Add user accounts and SSO groups + * Edit email preferences + * Authorize and unauthorize users + +In RSC, the tenant organization administrator can: + + * View RSC dashboards that provide an overview of organization data health and security. + * Access cluster information from the Clusters page. + * Add workloads and manage protection for Datacenter, Cloud, and SaaS tenant organization workloads using SLA Domains. + * View and assign replication target clusters in SLA Domains, view their archival location information and use them in SLA Domains, and create and manage SLA Domains for their organization , based on permissions assigned by a global administrator during creation or editing of an organization. When tenant organizations are assigned SLA Domains by the global organization, they can also view and use them. + * Access and view events, reports, and task monitoring for the tenant organization. + + *[ > ]: and then diff --git a/saas_mt_tenant_org_user_privileges.md b/saas_mt_tenant_org_user_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..8c8b8fa55a0c13caa57d7e339f19c74c2d11f4fc --- /dev/null +++ b/saas_mt_tenant_org_user_privileges.md @@ -0,0 +1,47 @@ +# Tenant organization user privileges + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_tenant_org_user_privileges.html + +--- + +# Replication for tenant organizations + +The global organization administrator sets up replication targets, options, and permissions for the tenant organization when creating or editing the organization. + +Note: + +The global organization administrator must set up a replication pairing before a tenant organization can use it. After the global organization administrator sets up the replication pairing, they can decide on the options and permissions for how the tenant organization can use the replication pair. + +In RSC# Replication for tenant organizations + +The global organization administrator sets up replication targets, options, and permissions for the tenant organization when creating or editing the organization. + +Note: + +The global organization administrator must set up a replication pairing before a tenant organization can use it. After the global organization administrator sets up the replication pairing, they can decide on the options and permissions for how the tenant organization can use the replication pair. + +In RSC, replication configuration privileges can be assigned to roles at the global organization level. User accounts with privileges to view and edit replication and edit network throttling will be able to view the replication targets page and pause, resume, and update network throttling. + +For a tenant organization, you can configure replication options as part of an SLA Domain and then assign them to an organization during the organization creation process. If the tenant organization has self-service permission, they can also create their own SLA Domains with replication options. + +When tenant organizations are assigned replication permissions, they can view and assign replication target clusters as part of their SLA Domain creation and management. + +The following considerations apply: + + * Tenant organization user accounts with SLA Domain permissions can then assign the SLA Domain to the replication source clusters to perform replication. + * Pause or resume and update network throttling permissions are not available to tenant organizations. + +# Tenant organization user privileges + +The tenant organization user roles are assigned specific permissions by the tenant organization administrator. + +Tenant user access to RSC depends on the privileges you assign during role creation. The dashboard, Task Monitoring, and other RSC pages reflect the objects and privileges assigned to the user account. The report information displayed for a user account is restricted to the resources assigned to the tenant organization and assigned user privileges. + +In RSC, the tenant organization users have role-based privileges that enable them to: + + * View RSC dashboards that provide an overview of organization data health and security. + * Access cluster information from the Clusters page. + * Add workloads and manage protection for Datacenter, Cloud, and SaaS tenant organization workloads using SLA Domains based on assigned privileges. + * Access and view events, reports, and task monitoring for the tenant organization based on assigned privileges. + + *[ > ]: and then diff --git a/saas_mt_tenant_organizations.md b/saas_mt_tenant_organizations.md new file mode 100644 index 0000000000000000000000000000000000000000..edee5a4aa399f64813d497d81db9584e83805113 --- /dev/null +++ b/saas_mt_tenant_organizations.md @@ -0,0 +1,20 @@ +# Tenant organizations + +Source: https://docs.rubrik.com/en-us/saas/saas/mt_tenant_organizations.html + +--- + +# Tenant organizations + +Tenant organizations in RSC are a defined subset of the global organization with specified resources, workloads, SLA Domains, and permissions. + +A tenant organization is created and assigned a specific subset of resources and privileges by the global administrator. Tenant organization privileges determine the tasks available to the organization. The following rules apply to tenant organizations: + + * A global organization user account with the Manage Organization privilege can create tenant organizations. The administrator and owner roles are assigned this privilege by default. + * An organization administrator can view and manage the privileges of the users or groups in the tenant organization. Each tenant organization must have an organization administrator that can define additional roles that are subsets of the administrator role. You can assign different levels of organizational privileges to tenant organization user accounts. + * A tenant organization administrator can manage roles for existing user accounts in the context of that organization only. When a specific tenant administrator deletes a local user account used by multiple organizations, the user account is only removed from that specific tenant organization, but remains in RSC and other tenant organizations. + * When tenant organizations are assigned replication permissions, they can view and manage the replication target clusters. When tenant organizations are assigned archival permissions, they can view their archival locations and all relevant information, including information about storage used for the specific datacenter archival locations for which they have permissions. When assigned SLA Domain self-service, replication target, and archival location permissions, they can use these archival locations and replication targets as part of their SLA Domain creation and management. + * A tenant organization administrator with the privileges to manage user accounts can create new local user accounts within the tenant organization and manage them. Tenant organization administrators can configure SAML authentication for their organization. + * Tenant organization user accounts can view information about system activity on objects assigned to them. Tenant administrators can view information about system activity that affects all objects in the tenant organization. + + *[ > ]: and then diff --git a/saas_multiple_archival_policies.md b/saas_multiple_archival_policies.md new file mode 100644 index 0000000000000000000000000000000000000000..0b6df31d906cc7803f2a3a1036d260fe47072a2c --- /dev/null +++ b/saas_multiple_archival_policies.md @@ -0,0 +1,62 @@ +# Multiple archival policies + +Source: https://docs.rubrik.com/en-us/saas/saas/multiple_archival_policies.html + +--- + +# Multiple archival policies + +RSC allows you to configure an SLA Domain with up to two archival policies for Rubrik CDM and cloud workloads. + +RSC supports multiple archival locations, allowing you to configure an SLA Domain with up to two archival policies that enable archiving protected data to an archival location. Each policy must specify: + + * A different archival location. + * A different archival threshold. + * A selection of snapshot frequency types to archive to the location for Rubrik CDM workloads. + +However, this option is unavailable for cloud workloads, and all frequencies are selected by default for both archival locations. + +The local retention is specified in the SLA Domain and indicates how long to retain the snapshot locally. The retention period must be greater than the archival threshold specified in archival policies. + +## Benefits + +Multiple archival locations provide granular archival policies for snapshots. You can configure each archival policy in an SLA Domain with different thresholds, retention periods, and snapshot frequencies. As a result, you can organize snapshots based on the criteria of the corresponding archival policy. For example, you can: + + * Archive snapshots taken at a specific frequency to an on-premises storage target with a lower retention period, but you can archive snapshots with other frequencies to a cloud storage target with long-term retention. However, you cannot configure different backup frequencies for different archival locations for cloud workloads. The backup frequencies must be the same for all archival locations. + * Archive all snapshots to two different targets with independent archival thresholds for both Rubrik CDM and cloud workloads. + * Instantly archive daily snapshots retained for 30 days and monthly snapshots retained for 7 years to the first archival location to address disaster recovery requirements for Rubrik CDM workloads. You can archive monthly snapshots to another location to manage long-term retention compliance. However, you cannot archive snapshots with different frequencies to different archival locations for cloud workloads. + +## Snapshot frequency, retention, and rules + +If you do not configure specific snapshot frequencies for an archival policy, RSC archives snapshots from all the frequencies configured in the SLA Domain. A snapshot frequency determines how often RSC takes a snapshot of the workload. For example, when specifying daily and weekly frequencies for snapshots in the SLA Domain, you must select both daily and weekly frequencies for archival; selecting only a daily frequency for archival is not permitted. + +Snapshots with retention periods lower than the threshold expire from the Rubrik cluster and are never archived, irrespective of whether the SLA Domain is configured with multiple archival policies. + +Rubrik imposes specific rules to maintain consistency: + + * The Rubrik clusters or cloud storage selected in the first archival policy must be the same as the Rubrik clusters or cloud storage specified in the second archival policy. + * You cannot select the same archival location for a cluster or cloud workloads in both archival policies. + * The type of archival location configured for both policies must be the same. + * When you set an archival policy for snapshots at a specific frequency, you must also archive snapshots taken at all higher frequencies. This can be done within the same policy or across two different policies. + +For example, if you configure archiving for daily snapshots, you must also configure it for weekly, monthly, and yearly snapshots. If you archive weekly snapshots in one policy, you must also manage monthly and yearly snapshots, either in the same archival policy or the second archival policy. + +## Archival policy modifications + +You can edit the archival policies for the SLA Domain independently. Changes to one archival policy do not impact the other archival policy. However, you must meet any higher frequency archival requirements. You can edit an existing SLA Domain to add or remove an archival policy. Adding a second archival policy does not impact the behavior of the first archival policy. If an SLA Domain has two archival policies and one of the policies is removed, the remaining archival policy continues archiving as specified in the SLA Domain. + +## Supported workloads + +The following table describes the Rubrik CDM versions and cloud environments that supports the multiple archival locations feature. + +Type | Supported workloads +---|--- +Rubrik CDM version 8.0.2 or later | All workloads by default, except Oracle, SQL Server, SAP HANA database, and Db2 database. +Rubrik CDM version 8.0.3 or later | All workloads, except SAP HANA, Db2 database, and MongoDB database. +Rubrik CDM version 9.3.0 or later | All workloads, except Db2 database and MongoDB database. +Cloud | + + * Amazon EC2 instance and EBS volume + * Azure virtual machine and managed disk + + *[ > ]: and then diff --git a/saas_multiple_role_assignment_scenarios.md b/saas_multiple_role_assignment_scenarios.md new file mode 100644 index 0000000000000000000000000000000000000000..6dbb1aa81d9ba881ced5957a926a24d3c63ded09 --- /dev/null +++ b/saas_multiple_role_assignment_scenarios.md @@ -0,0 +1,20 @@ +# Multiple role assignment scenarios + +Source: https://docs.rubrik.com/en-us/saas/saas/multiple_role_assignment_scenarios.html + +--- + +# Multiple role assignment scenarios + +Information about the permissions when multiple roles are assigned to a user or a group. + +Users have a combination of permissions when multiple role-based access control (RBAC) roles are assigned. + +Here are some examples of the multiple RBAC role assignments and resulting permissions. + +Multiple-role assignment scenario | Resolution +---|--- +A group has a global administrator role, and a user is a member of this group. | The user has the permissions of the global administrator because the user has inherited the permissions from its group. +Group 1 has role A and access to object 1 and group 2 has role B and access to object 2, and the user is a member of groups 1 and 2. | The user can access the objects accessed by roles A and B, that is, objects 1 and 2. +Group 1 has role A and access to object 1 and group 2 has an administrator role, and the user is a member of groups 1 and 2. | The user can access the objects accessed by the administrator and role A. + *[ > ]: and then diff --git a/saas_nascd_compliance_report.md b/saas_nascd_compliance_report.md new file mode 100644 index 0000000000000000000000000000000000000000..f88bfcc5c017416757d4542c3c3704a01f631d3d --- /dev/null +++ b/saas_nascd_compliance_report.md @@ -0,0 +1,28 @@ +# NAS Cloud Direct Compliance Report + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_compliance_report.html + +--- + +# NAS Cloud Direct Compliance Report + +The Rubrik NAS Cloud Direct Compliance report provides information about the compliance status of NAS CD objects. By using this report, you can determine whether the snapshots taken for an object are in compliance with the policy schedule associated with the object. + +To adhere to regulatory mandates and to ensure that Rubrik is operating within legal frameworks, RSC provides the compliance status of Rubrik NAS Cloud Direct snapshot objects in the NAS CD Compliance report. + +With the Rubrik NAS Cloud Direct Compliance report, you can view the compliance status and the number of scheduled snapshots or backups that were not taken in a specified time range. Also, you can view the time when the last successful snapshot was completed and the details related to Awaiting First full snapshot, that is, whether the first full backup is completed or yet to be taken. + +RSC captures the compliance data from the date the NAS CD Compliance report feature is shipped to you. If a new policy is applied to NAS Share or the policy applied is modified, the compliance data on NAS Share is reset. + +You can view various NAS CD Compliance graphs based on Time, Cluster Type, Cluster, Object Type, and All filters. + +Besides viewing the NAS CD Compliance report, you can also perform the following actions: + + * Select the columns to include in the report. + * Edit the name of the report, modify the filters, and save the report for future reference. + * Download the NAS CD Compliance report in CSV and PDF formats. + * Email the report to the required email addresses. + * Add, edit, or delete a report schedule. + * Delete a report. + + *[ > ]: and then diff --git a/saas_nascd_direct_object_capacity_over_time_report.md b/saas_nascd_direct_object_capacity_over_time_report.md new file mode 100644 index 0000000000000000000000000000000000000000..b40453b34d8659e046223930774e814b16ebccdd --- /dev/null +++ b/saas_nascd_direct_object_capacity_over_time_report.md @@ -0,0 +1,24 @@ +# NAS CD Object Capacity Over Time report + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_direct_object_capacity_over_time_report.html + +--- + +# NAS CD Object Capacity Over Time report + +The Rubrik NAS Cloud Direct Object Capacity Over Time report provides details about the size of a NAS Share and the storage space used to back up the NAS Share over a period of time. You can use the Rubrik NAS Cloud Direct Object Capacity Over Time report for insights on your storage consumption for effective resource management and future planning. + +The Rubrik NAS Cloud Direct (NAS CD) Object Capacity Over Time report provides details about the size of a NAS share, the storage space used to back up the NAS share, and how it has changed over a period of time. You can view the details associated with the size of a NAS share and storage space for up to one year. You can use theNAS CD Object Capacity Over Time report for insights on your storage consumption for effective resource management and future planning. + +You can view various NAS CD Object Capacity Over Time graphs based on All Source Size, All Target Size, and All Protected Object Count on theRubrik NAS Cloud Direct Object Capacity Over Time report. + +You can use the NAS CDObject Capacity Over Time report to perform the following actions: + + * Viewing specific details by selecting the columns to include in the report + * Editing the name of the report, modifying the filters, and saving the report for future reference + * Downloading the report either in the CSV format or as a PDF document + * Emailing the report to the required email addresses + * Adding, editing, or deleting a report schedule + * Deleting a report + + *[ > ]: and then diff --git a/saas_nascd_inventory_management.md b/saas_nascd_inventory_management.md new file mode 100644 index 0000000000000000000000000000000000000000..475022e8ad8bde9d4b13e377fe0bc3be55372c6e --- /dev/null +++ b/saas_nascd_inventory_management.md @@ -0,0 +1,22 @@ +# NAS CD Inventory Management + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_inventory_management.html + +--- + +# NAS CD Inventory Management + +Inventory management provides options to view NAS CD data sets and perform recoveries of their backups. + +From the NAS CD Inventory page, you can perform tasks such as view the data sets and recover their backups from a specific associated object snapshot page. The NAS CD Inventory page consists of the following tabs: + + * Shares: Lists the available NAS CD shares. + * Namespaces: Lists the available namespaces. You can click each namespace to view its shares. + * Systems: Lists the available systems. You can click a system to see the namespaces associated with it. You can further click the namespaces to view the shares associated with the system. + +The inventory page shows the details associated with each NAS CD object type, depending on the tab clicked. You can search for a NAS CD object using the search bar or filters. + +A NAS CD share marked with a Directory tag indicates that this share is manually created from a subdirectory of its parent directory. When you click a NAS CD share, the Overview tab shows the object details associated with that share, such as the system, system type, namespace, protocol, and policy name. You can also see the snapshot details for the share on the Snapshot tab. You can recover NAS CD backups by choosing a Snapshot from the snapshots available on the Snapshot tab. + +A global administrator user with the required access permission can access the NAS CD UI from the NAS CD Inventory page. The Creating custom roles for NAS Cloud Direct data sets topic provides more information about creating a custom role for accessing NAS CD UI. + *[ > ]: and then diff --git a/saas_nascd_object_capacity_report.md b/saas_nascd_object_capacity_report.md new file mode 100644 index 0000000000000000000000000000000000000000..08dc015a89246e6993ecc2461c3796aeea12c24c --- /dev/null +++ b/saas_nascd_object_capacity_report.md @@ -0,0 +1,24 @@ +# NAS CD Object Capacity report + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_object_capacity_report.html + +--- + +# NAS CD Object Capacity report + +The Rubrik NAS Cloud Direct Object Capacity report provides details about the size of a NAS Share and the storage space used to back up the NAS Share. You can use the Rubrik NAS Cloud Direct Object Capacity report for insights on your storage consumption for effective resource management and future planning. + +You can view information about the size of a NAS Share and the storage space used to back up the NAS Share in the Rubrik NAS Cloud Direct (NAS CD) Object Capacity report. The NAS CD Object Capacity report provides insights into your storage consumptions. Such insights help in effective resource management and future planning. You can also track your Rubrik license usage with the help of the report. + +You can view various NAS CD Object Capacity graphs based on Time, Cluster Type, Cluster, Object Type, Object Type Source Size, and All filters on the NAS CDObject Capacity report. + +You can use the NAS CD Object Capacity report to perform the following actions: + + * Viewing specific details by selecting the columns to include in the report + * Editing the name of the report, modifying the filters, and saving the report for future reference + * Downloading the report either in the CSV format or as a PDF document + * Emailing the report to the required email addresses + * Adding, editing, or deleting a report schedule + * Deleting a report + + *[ > ]: and then diff --git a/saas_nascd_protection_report.md b/saas_nascd_protection_report.md new file mode 100644 index 0000000000000000000000000000000000000000..a0fc8cdc37e17c26f511e4e43b332f3fca605519 --- /dev/null +++ b/saas_nascd_protection_report.md @@ -0,0 +1,24 @@ +# NAS Cloud Direct Protection Report + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_protection_report.html + +--- + +# NAS Cloud Direct Protection Report + +The Rubrik NAS Cloud Direct Protection Report shows the protection status of NAS CD on the Reports page. You can use this report to check the health of a backup for data integrity and safety. + +You can view the protection status of NAS CD using the NAS CD Protection Report. This report helps you check the protection status and health of a NAS CD backup for data integrity and safety. The report provides details such as object, source protocol, NAS CD site name and NAS CD policy, protection status of each object, and the time when the last backup job was completed successfully. With this report, you can find out if the NAS CD protection policy is assigned to an object. + +You can view various NAS CD Protection graphs based on Time, Cluster Type, Cluster, Object Type, and All filters. + +Besides viewing the NAS CD Protection Report, you can also perform the following actions: + + * Select the columns to include in the report. + * Edit the name of the report, change the filters, and save the report for future reference. + * Download the NAS CD Protection Report in CSV and PDF formats. + * Email the report to the required email addresses. + * Add, edit, or delete a report schedule. + * Delete a report. + + *[ > ]: and then diff --git a/saas_nascd_recovery.md b/saas_nascd_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..5557700ea2ff45ec039d2cd1c395bc63cdaf8c29 --- /dev/null +++ b/saas_nascd_recovery.md @@ -0,0 +1,14 @@ +# NAS CD Recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_recovery.html + +--- + +# NAS CD Recovery + +You can recover shares from the snapshots on the Overview tab of a share on the NAS CD Inventory page. + +NAS CD takes snapshots based on the policy configured for a data set. You can browse and recover data from the NAS CD Inventory page for a share. From the Inventory page, you can navigate to the Overview tab of a share to search for a specific snapshot from the snapshot calendar or on the snapshot tab. You can use filters to search for a snapshot based on the date range during which a snapshot was taken. + +The Task Monitoring dashboard in RSC lists the restore tasks related to the NAS CD shares. You can change filters to change the Task Monitoring page view dynamically, and to filter the tasks by cluster, cluster status, task type, object type, organization, and so on. + *[ > ]: and then diff --git a/saas_nascd_report_details.md b/saas_nascd_report_details.md new file mode 100644 index 0000000000000000000000000000000000000000..fbe435c0f26b8e9914b0cd5188d9ea3529327e7e --- /dev/null +++ b/saas_nascd_report_details.md @@ -0,0 +1,56 @@ +# Rubrik NAS Cloud Direct report details + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_report_details.html + +--- + +# Rubrik NAS Cloud Direct report details + +Information about the details you can view in the Rubrik NAS Cloud Direct Protection, Object Capacity, Object Capacity Over Time, and Compliance reports. + +The following report details are available to view in the Rubrik NAS Cloud Direct Protection, Object Capacity, Object Capacity Over Time, and Compliance reports. Detail | Description +---|--- +Object | NAS Server name with the path details as follows: /namespace/ +Object Type | Object type that RSC manages. +Source Protocol | The protocol the NAS source uses to make shares and exports available, such as NFS or SMB. The supported values for the NAS protocol: + + * nfs + * nfsv4 + * s3 + * smb + * nfs, smb + + +NCD Site | The name of the NAS site. +Last Updated | The retrieval time of the report data from the NCD site. The updates take place every four hours. +NCD Policy | The name of the NCD policy. +NCD SnapshotType | The type of snapshot taken for a given object. The supported values are as follows: + + * Backup: Regularly scheduled snapshots capturing the state of an export, with retention based on incremental changes from the source. + * Archive: User-initiated, on-demand snapshots of an export with retention specified by policy and independent of source changes. This snapshot type allows for multiple archives from the same source to the same target. + * Inactive: An export with a backup that has been unassigned. + + +Protection Status | The protection status indicates whether the object has an active protection policy applied. The supported values for the protection status of an object: + + * Protected: A protection policy is assigned to the object. + * No SLA: A protection policy is not assigned to the object. The NCD snapshot type of archive falls under this protection status. + +Protection Status is applicable only for the NAS CD Protection report. +Last Snapshot | The time of the last completed scheduled backup.Last Snapshot is applicable only for the NAS CD Protection report. +Last Archive Snapshot | The time of the last completed archive on NAS Share.Last Archive Snapshot is applicable only for the NAS CD Protection report. +Source Size | The sum of the sizes of all the files backed up on a NAS share based on the last backup.Source Size is applicable for the NAS CD Object Capacity and NAS CD Object Capacity Over Time reports. +Target Size | Cloud storage usage for all the backups of a NAS Share.Target Size is applicable for the NAS CD Object Capacity and NAS CD Object Capacity Over Time reports. +Data Reduction | Ratio of data transferred to data stored in percentage. Data Reduction is applicable only for the NAS CD Object Capacity report. +Compliance Status (applicable only for the NAS CD Compliance report) | The compliance status of Rubrik NAS Cloud Direct snapshot objects. The supported values for the compliance status of NAS CD snapshot objects: + + * In Compliance: The object is in compliance during the selected time frame, which indicates that there is at least one snapshot in each time period equal to the frequency specified in the protection policy associated with the NCD object. If the frequency is Daily, then there is at least one snapshot for every 24 hours. + * Out of Compliance: The object is out of compliance during the selected time frame. The Out of Compliance status indicates that RSCcould not take a successful snapshot in the selected time frame of the policy schedule. + * Unprotected: No protection policy is applied to the object. + * Not Available: RSC cannot determine the compliance status because of an error. + + +Missed Snapshots (applicable only for the NAS CD Compliance report) | Number of missed snapshots in the specified time range. +Last Successful Backup (applicable only for the NAS CD Compliance report) | The time of the last completed backup. +Awaiting First Full (applicable only for the NAS CD Compliance report) | Status update on whether the first full backup is completed or yet to be taken. + *[ > ]: and then diff --git a/saas_nascd_report_filters.md b/saas_nascd_report_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..5bf984c0996852687d1f94bd8e05bc27576b9737 --- /dev/null +++ b/saas_nascd_report_filters.md @@ -0,0 +1,35 @@ +# NAS Cloud Direct report filters + +Source: https://docs.rubrik.com/en-us/saas/saas/nascd_report_filters.html + +--- + +# NAS Cloud Direct report filters + +Information about the filters associated with time range, clusters, object type, cluster type, and a few other filters that you can use to sort the Rubrik NAS Cloud Direct Protection, Object Capacity, and Compliance reports. + +The following report filters are available to sort the Rubrik NAS Cloud Direct Protection, Object Capacity, and Compliance reports. + +Filter | Description +---|--- +Time | The time range for the report. Supported ranges are as follows: + + * Start Of Protection (Applicable only for the Compliance report) + * Past 24 hours + * Past 7 days + * Past 30 days + * Past 12 months + * Custom + + +Clusters | The Rubrik clusters connected to RSC. You can select multiple clusters. +Object Type | The object type associated with the connected Rubrik cluster on RSC. You can select multiple object types. +Cluster Type | The Rubrik cluster types to include in the report. You can select only the Virtual cluster type. This filter does not apply to the SLA Audit, Object Audit, and Data Threat Analytics reports. The value Rubrik Security Cloud is also available only for the Infrastructure, Object capacity, Compliance, Protection, and the Event reports. +Protection Status (Applicable only for the Protection report) | The protection status of the objects in the report. The supported values are as follows: + + * Protected + * Don't Protect + * No SLA + +This filter applies only to the Protection report. + *[ > ]: and then diff --git a/saas_ncd_data_observability.md b/saas_ncd_data_observability.md new file mode 100644 index 0000000000000000000000000000000000000000..5ca5da25da1a7af7b3d06184e88cc824a369465d --- /dev/null +++ b/saas_ncd_data_observability.md @@ -0,0 +1,38 @@ +# Data Observability for NAS CD data sets + +Source: https://docs.rubrik.com/en-us/saas/saas/ncd_data_observability.html + +--- + +# Data Observability for NAS CD data sets + +To provide Data Observability, you can enable Data Threat Analytics and configure Data Security Posture for NAS CD data sets. Data Threat Analytics detects ransomware attacks and Data Security Posture identifies sensitive data in your NAS CD data sets. + +By using the Data Observability feature, you can monitor your data for ransomware and reduce sensitive data exposure by discovering the types of sensitive data you have. Data Observability for NAS CD data sets has the following components: + + * Rubrik Cloud Vault or other storage provider to provide simplified archiving of backups, including archiving backups to locations that provide immutable storage. + * Data Threat Analytics to scan backups for anomalies. + * Data Security Posture to identify sensitive data that must be secured. + +Rubrik Cloud Vault provides a secure storage target. For NAS CD backups and archives, you can use Rubrik Cloud Vault in any newly defined policy. You can also add it to an existing protection policy to maintain a second copy of the data for Data Observability and cyber resiliency. + +Data Security Posture works only with a Rubrik Cloud Vault storage that is allocated to the NAS CD cluster. After NAS CD backups have been uploaded to Rubrik Cloud Vault, you can enable Data Security Posture on backups sent to Rubrik Cloud Vault storage targets. Data Security Posture identifies sensitive data within backups that match a specified data policy. + +Data Threat Analytics works with Rubrik Cloud Vault storage or any custom storage that your NAS CD cluster might be using. To detect anomalous encryption events that might indicate a ransomware attack on your NAS CD backups, you can enable Data Threat Analytics on the Rubrik Cloud Vault storage or the NAS CD cluster depending on the storage you use. In case of an attack, you can use Data Threat Analytics for data recovery. + +To configure Data Observability, you are required to complete the following actions: + + * Creating a Rubrik Cloud Vault or custom storage target allocated to the NAS CD cluster + * Enabling Data Threat Analytics for the appropriate NAS CD cluster + * Creating a NAS CD policy to send backups to the storage target + * Enabling Data Security Posture by assigning required policies to scan NAS data sets + * Assigning the created NAS CD policy to the relevant NAS data sets + +Important: + +Using Rubrik Cloud Vault requires you to enable Data Threat Analytics and Data Security Posture before the first full backup of the NAS CD data set to ensure that the entire data set is subject to analysis. NAS CD is an incremental-forever backup product. If these capabilities are not enabled in advance of the first full backup, then only the incremental changes captured after the first full backup is subject to analysis. + +After RSC takes the first backup, you have a grace period of 14 days to apply the Data Security Posture policy to ensure that the entire data set is subject to analysis. + +When using a custom storage provider, you do not need to enable the Data Threat Analytics feature before the first full backup of the NAS CD data set finishes, but RSC does not scan preexisting backups for Data Threat Analytics. + *[ > ]: and then diff --git a/saas_ncd_data_sets.md b/saas_ncd_data_sets.md new file mode 100644 index 0000000000000000000000000000000000000000..de644329e975a37e89aeb529ca69ac8932ef71ed --- /dev/null +++ b/saas_ncd_data_sets.md @@ -0,0 +1,19 @@ +# NAS CD data sets + +Source: https://docs.rubrik.com/en-us/saas/saas/ncd_data_sets.html + +--- + +# NAS CD data sets + +Rubrik NAS Cloud Direct offers secure data protection with high-performance, scalable enterprise backup, and archive services for unstructured file data. + +Rubrik NAS Cloud Direct (NAS CD) combines all unstructured data management functions into a SaaS solution delivered through RSC. NAS CD secures file data stored on any file system under any NAS protocol and writes data to any NFSv3- or S3-compatible object storage on-premises or in the cloud to AWS S3, Azure blob, Google Cloud Object Storage, and many other S3-compatible cloud object storage solutions. One or more stateless virtual machines deployed near the NAS systems under protection facilitate the high-speed data movement required for data protection. Key benefits of NAS CD include the following: + + * Incremental-forever protection to avoid periodic full backups and consolidation jobs + * Policy-based backup and archival operations for many popular NAS platforms + * Latency-aware throttling to ensure no impact to NAS storage users and applications during backups + * Intuitive identification of aging datasets for reporting and archiving + * API integration with Dell PowerScale, NetApp ONTAP, Qumulo Core, and Pure FlashBlade + +The Rubrik NAS Cloud Direct User Guide provides more information about the benefits of NAS CD. diff --git a/saas_ncd_unstructured_data_dashboard.md b/saas_ncd_unstructured_data_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..1ab59740daf12ae1117ac273b99e180ebd395e76 --- /dev/null +++ b/saas_ncd_unstructured_data_dashboard.md @@ -0,0 +1,23 @@ +# Unstructured Data dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/ncd_unstructured_data_dashboard.html + +--- + +# Unstructured Data dashboard + +The Unstructured Data dashboard in RSC provides a comprehensive data protection summary for all connected clusters, displaying statistics on data collection, archive usage, storage, and the status of protected files and shares. + +NAS CD offers protection for unstructured object data with high-performance, scalable enterprise backup and archive services. The source of the unstructured data can be files or NAS shares. + +When you use NAS CD to protect NAS shares, the Unstructured Data dashboard in RSC displays the data protection and operations status statistics. The data is aggregated from all NAS CD clusters connected to RSC. + +The Unstructured Data dashboard displays the following details: + + * The total data ingested by NAS CD + * The archive data used by NAS CD + * The data stored in the backend in the storage target + * The number of protected and unprotected files and shares + * A list of backup and restore tasks running on all NAS CD clusters + + *[ > ]: and then diff --git a/saas_ncd_unstructured_data_dashboard_2.md b/saas_ncd_unstructured_data_dashboard_2.md new file mode 100644 index 0000000000000000000000000000000000000000..e7c4625bd5dddfcd65631af54261d47c869769e9 --- /dev/null +++ b/saas_ncd_unstructured_data_dashboard_2.md @@ -0,0 +1,46 @@ +# Unstructured Data dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/ncd_unstructured_data_dashboard_2.html + +--- + +# MongoDB source cluster details + +The MongoDB source cluster details page provides an overview of the selected MongoDB source. + +The following table provides information about the MongoDB source. Tab | Description +---|--- +Overview | Provides information about protection, object details, and snapshots. + + * Protection: Displays the SLA Domain associated with the protection policy for this object. + * Object details: Displays the associated cluster, host count, deployment type, integration method, and number of databases. + * Snapshots: Provides a snapshot overview, including total snapshot count, oldest snapshot date, and the latest snapshot date, along with a calendar view of the snapshots. It also provides information about the location and expiry of each snapshot. + + +Events | Displays all the events related to the selected MongoDB source. You can filter the events by selecting a time range, severity, status, and type. +Snapshots | Provides detailed information about all snapshots taken for a specific MongoDB source. + + * Snapshot Date and Time: Displays the date and time at which the snapshot was taken. + * Snapshot Type: Specifies the type of snapshot. + * Archival Location: Displays the archival location of the snapshot. + * Replication Targets: Displays the replication locations of the snapshot. + +You can filter the snapshots by selecting a time range and type. + +# Unstructured Data dashboard + +The Unstructured Data dashboard in RSC provides a comprehensive data protection summary for all connected clusters, displaying statistics on data collection, archive usage, storage, and the status of protected files and shares. + +NAS CD offers protection for unstructured object data with high-performance, scalable enterprise backup and archive services. The source of the unstructured data can be files or NAS shares. + +When you use NAS CD to protect NAS shares, the Unstructured Data dashboard in RSC displays the data protection and operations status statistics. The data is aggregated from all NAS CD clusters connected to RSC. + +The Unstructured Data dashboard displays the following details: + + * The total data ingested by NAS CD + * The archive data used by NAS CD + * The data stored in the backend in the storage target + * The number of protected and unprotected files and shares + * A list of backup and restore tasks running on all NAS CD clusters + + *[ > ]: and then diff --git a/saas_netapp_volume_export.md b/saas_netapp_volume_export.md new file mode 100644 index 0000000000000000000000000000000000000000..c0f965682804a0346442adef66b82f35249c4a99 --- /dev/null +++ b/saas_netapp_volume_export.md @@ -0,0 +1,14 @@ +# NetApp volume export + +Source: https://docs.rubrik.com/en-us/saas/saas/netapp_volume_export.html + +--- + +# NetApp volume export + +To allow backups of read-only NetApp volumes, you must first export the volumes through NFS. + +Read-only volumes do not always have pre-configured NFS access. When NFS access is not configured, you must export read-only volumes through NFS to allow SnapMirror Cloud backups of the read-only volumes. + +You can enable NFS access on the volume configuration page for NetApp. + *[ > ]: and then diff --git a/saas_node_removal_rsc.md b/saas_node_removal_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..cdcbefb24732af7a9ef83557347b8e609dd601a5 --- /dev/null +++ b/saas_node_removal_rsc.md @@ -0,0 +1,58 @@ +# Node removal in RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/node_removal_rsc.html + +--- + +# Node removal in RSC + +If you no longer require a node in a Rubrik cluster, a supported third-party hardware cluster, or a Rubrik Cloud Cluster, you can remove the node by using RSC. To remove a node, you must meet the requirements for node removal. + +You may choose to remove nodes from your cluster in the following use cases: + + * For Rubrik or supported third-party hardware clusters, you can permanently remove a node, repurpose a node, and update cluster configuration during a hardware refresh. + +Important: + +RSC requires that you do not remove a node physically before RSC logically removes the node from the cluster. + + * For Rubrik Cloud Clusters, you can remove a node to scale down the number of nodes in your cluster and change the type of instance used to host the nodes. + +Important: + +RSC requires that you do not clear the cloud resources before RSC logically removes a node from the cluster. + +Note: + +RSC does not support removal of nodes for Rubrik Edge and Rubrik Virtual Cluster. + +## Security and authorization + +To prevent accidental or malicious node removal by a compromised administrator, a global administrator can set up a quorum authorization policy to request additional approvals for removing a node. + +## Selection of nodes for removal + +In the process of node removal, you can select the nodes that you want to remove from a cluster. If you do not select all the nodes in a chassis, RSC provides an option to remove all remaining nodes in the entire chassis. + +You may remove all the nodes in a chassis in the following use cases: + + * When you perform a hardware refresh. For example, when you want to change your Rubrik platform from r6000 to r7000 + * When you repurpose a node to move an entire chassis to another cluster + * When you unrack an entire chassis + * When you remove Rubrik loaned hardware + +You may remove only selected nodes from a chassis in the following use cases: + + * When you do not have enough space in your cluster to move an entire chassis to another cluster + * When you need to move nodes from one chassis to another chassis + +## Node removal process + +After selecting the nodes, when you initiate the process of node removal, RSC performs prechecks to ensure that the following criteria for removing nodes are met: + + * The nodes selected for removal are healthy nodes. RSC cannot remove an unhealthy node. + * The cluster from which you want to remove the nodes is a healthy cluster. RSC cannot remove a node from a cluster that is not healthy. + * The number of nodes selected for removal is not more than half of the current number of nodes in a cluster, with at least three nodes remaining in the cluster after removing the nodes. + +After the prechecks, RSC transfers the data from the selected nodes to other nodes in the cluster. The process of transferring data might take hours or days depending on the amount of data. You cannot cancel the node removal process after the data transfer from the node is complete. You can check the progress of the node removal process in the Cluster details page under the Nodes tab in RSC. + *[ > ]: and then diff --git a/saas_node_removal_rsc_2.md b/saas_node_removal_rsc_2.md new file mode 100644 index 0000000000000000000000000000000000000000..19405297437f9ac8de69979e995c2020e33c5e64 --- /dev/null +++ b/saas_node_removal_rsc_2.md @@ -0,0 +1,58 @@ +# Node removal in RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/node_removal_rsc_2.html + +--- + +# Node removal in RSC + +If you no longer require a node in a Rubrik cluster, a supported third-party hardware cluster, or a Rubrik Cloud Cluster, you can remove the node by using RSC. To remove a node, you must meet the requirements for node removal. + +You may choose to remove nodes from your cluster in the following use cases: + + * For Rubrik or supported third-party hardware clusters, you can permanently remove a node, repurpose a node, and update cluster configuration during a hardware refresh. + +Important: + +RSC requires that you do not remove a node physically before RSC logically removes the node from the cluster. + + * For Rubrik Cloud Clusters, you can remove a node to scale down the number of nodes in your cluster and change the type of instance used to host the nodes. + +Important: + +RSC requires that you do not clear the cloud resources before RSC logically removes a node from the cluster. + +Note: + +RSC does not support removal of nodes for Rubrik Edge and Rubrik Virtual Cluster. + +## Security and authorization + +To prevent accidental or malicious node removal by a compromised administrator, a global administrator can set up a quorum authorization policy to request additional approvals for removing a node. + +## Selection of nodes for removal + +In the process of node removal, you can select the nodes that you want to remove from a cluster. If you do not select all the nodes in a chassis, RSC provides an option to remove all remaining nodes in the entire chassis. + +You may remove all the nodes in a chassis in the following use cases: + + * When you perform a hardware refresh. For example, when you want to change your Rubrik platform from r6000 to r7000 + * When you repurpose a node to move an entire chassis to another cluster + * When you unrack an entire chassis + * When you remove Rubrik loaned hardware + +You may remove only selected nodes from a chassis in the following use cases: + + * When you do not have enough space in your cluster to move an entire chassis to another cluster + * When you need to move nodes from one chassis to another chassis + +## Node removal process + +After selecting the nodes, when you initiate the process of node removal, RSC performs prechecks to ensure that the following criteria for removing nodes are met: + + * The nodes selected for removal are healthy nodes. RSC cannot remove an unhealthy node. + * The cluster from which you want to remove the nodes is a healthy cluster. RSC cannot remove a node from a cluster that is not healthy. + * The number of nodes selected for removal is not more than half of the current number of nodes in a cluster, with at least three nodes remaining in the cluster after removing the nodes. + +After the prechecks, RSC transfers the data from the selected nodes to other nodes in the cluster. The process of transferring data might take hours or days depending on the amount of data. You cannot cancel the node removal process after the data transfer from the node is complete. You can check the progress of the node removal process in the Cluster details page under the Nodes tab in RSC. + *[ > ]: and then diff --git a/saas_notifications.md b/saas_notifications.md new file mode 100644 index 0000000000000000000000000000000000000000..0fe73b77384a03e043716e9a79daeb92b9c9fb7d --- /dev/null +++ b/saas_notifications.md @@ -0,0 +1,18 @@ +# Notifications + +Source: https://docs.rubrik.com/en-us/saas/saas/notifications.html + +--- + +# Notifications + +In the Notifications menu, you can configure event email preferences, add webhooks, set up SNMP for network management and monitoring, and create a syslog export rule to enable the Rubrik cluster to send server messages to an external Syslog server. + +From the Notifications menu, you can: + + * Set up an email notification setting to send information about specific event types and severity to the email addresses of specific users. + * Add a webhook to send alerts to an external service. + * Integrate SNMP for central monitoring of managed devices on IP networks. + * Create a Syslog export rule so that the Rubrik cluster can send server messages to an external Syslog server. + + *[ > ]: and then diff --git a/saas_oar.md b/saas_oar.md new file mode 100644 index 0000000000000000000000000000000000000000..0e6d7c23507bda147c9e31757ee5e14208f147d0 --- /dev/null +++ b/saas_oar.md @@ -0,0 +1,32 @@ +# RSC Orchestrated Application Recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/oar.html + +--- + +# RSC Orchestrated Application Recovery + +The Orchestrated Application Recovery feature automates end-to-end recovery as well as disaster recovery and application migration from an on-premises data center to a secondary recovery site. + +Orchestrated Recovery uses Recovery Plans to group virtual machines for proactive testing and reporting and for production recovery situations. RSC creates Recovery Plans for a group of virtual machines and their associated target resource specifications for recovery. Orchestrated Recovery options to recover objects using a Recovery Plan include the following: + + * Disaster recovery + * Cyber recovery + * In-place recovery + +You can also initiate a cyber recovery as needed without a Recovery Plan by using the Cyber Recovery wizard. + +Orchestrated Recovery supports the following recovery types. You can filter for a recovery point based on Anomaly Detection and Quarantine results. + +You can use Orchestrated Recovery for the following workloads: + + * VMware virtual machines + * AHV virtual machines + * Azure virtual machines + +Only Cyber recovery is available for Azure virtual machines. + + * AWS EC2 instances + +Only Cyber recovery is available for AWS EC2 instances. + diff --git a/saas_oar_audit_log_filters.md b/saas_oar_audit_log_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..76776775d786b6f734b60936cf1f8088d60fe8f9 --- /dev/null +++ b/saas_oar_audit_log_filters.md @@ -0,0 +1,36 @@ +# Orchestrated Recovery Audit Log filters + +Source: https://docs.rubrik.com/en-us/saas/saas/oar_audit_log_filters.html + +--- + +# Orchestrated Recovery Audit Log filters + +The Audit Logs page provides a chronological record of user-initiated actions that occur during Orchestrated Recovery operations, with filtering options to refine the displayed results. + +The following table describes the available Orchestrated Recovery audit log filters. Filter | Description +---|--- +Time Range | Displays a sequential view of the audit logs that occurred during the selected period. + + * Past 15 minutes + * Past 2 hours + * Past 24 hours + * Past 7 days + * Past 30 days + * CustomUsing the Custom date range, you can specify a range to include a specific number of days, including beyond 30 days. + + +Severity | Displays events of all severity levels. + + * Critical + * Warning + * Informational + * N/A + +Selecting a value changes the display to show only audit log messages for the selected severity level or levels. This filter supports multi-selection. +Status | Displays audit log entries with the selected status. Clear the selection to see all entries. + + * Failed + * Completed + + *[ > ]: and then diff --git a/saas_oar_event_log_filters.md b/saas_oar_event_log_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..2ecd467bf6a9c4a2d5f6fad27d8a208bd64de78f --- /dev/null +++ b/saas_oar_event_log_filters.md @@ -0,0 +1,35 @@ +# Orchestrated Recovery Event Log filters + +Source: https://docs.rubrik.com/en-us/saas/saas/oar_event_log_filters.html + +--- + +# Orchestrated Recovery Event Log filters + +The Event Logs page provides a chronological record of operational details that occur during Orchestrated Recovery operations, with filtering options to refine the displayed results. + +The following table describes the available Orchestrated Recovery event log filters. Filter | Description +---|--- +Time Range | Displays events aggregated during the specified period. + * Past 15 minutes + * Past 2 hours + * Past 24 hours + * Past 7 days + * Past 30 days + * CustomUsing the Custom date range, you can specify a range to include a specific number of days, including beyond 30 days. +Status | Displays events based on the event status. + * Failed + * In progress + * Succeeded + * Succeeded with warnings + * Canceled + * Queued +This filter supports multi-selection. +Recovery type | Displays events based on the recovery type. + * In-Place Recovery + * Test Failover + * Cyber Recovery + * Failover + * Schedule Recovery +This filter supports multi-selection. + *[ > ]: and then diff --git a/saas_oar_events.md b/saas_oar_events.md new file mode 100644 index 0000000000000000000000000000000000000000..6855caf909f723c65fffa4fcbf7fdb0cddf05d82 --- /dev/null +++ b/saas_oar_events.md @@ -0,0 +1,43 @@ +# Orchestrated Recovery events + +Source: https://docs.rubrik.com/en-us/saas/saas/oar_events.html + +--- + +# Orchestrated Recovery events + +Event logs and audit logs provide a chronological record of automated operational tasks and user actions performed during orchestrated recovery, allowing activity monitoring and tracking, and maintaining accountability. + +Rubrik Security Cloud provides event logs and audit logs for monitoring and tracking activity in Orchestrated Recovery: + + * Event logs show details about the operations performed within Orchestrated Recovery. This log type records the actions that Orchestrated Recovery performs during a task. For example, this can include cleaning up resources, restoring virtual machines to a specified recovery point, or initiating an automated scheduled recovery. Event logs provide a record of actions resulting from user activities or automated scheduled tasks. + * Audit logs track activities initiated by users. This log type shows who performed an action, the action performed, and when the action occurred. Audit logs help to provide accountability by capturing details about user actions, such as starting recovery plans or initiating clean up operations to delete recovered objects. + +You can find both types of logs on the Events tab. + +## Event Logs + +The Event Logs page provides a chronological record of operational details during recovery events, sorted by event end time. When you click an event, the following details appear: + + * Recovery name, type, status, and completion time of the recovery operation. + * The Event timeline, listing updates in chronological order. + * Additional details, including Rubrik cluster, object type, object name, event type, location, duration, and start time. + +From the Event Logs page, you can: + + * Filter events by time range, status, or recovery type. + * Search for specific objects by name on the Search bar to identify particular event details. + * View the list of Orchestrated Recovery events and detailed information. + +## Audit Logs + +The Audit Logs page provides a chronological record of user-initiated actions during recovery operations, sorted by audit log end time. + +From the Audit Logs page, you can: + + * Filter audit logs by time range, severity, and status. + * Use the Search bar to find audit logs by username or specific actions, such as deletions, edits, or initiated tasks. + * View detailed information about each audit log entry. + * Download all filtered audit logs as a single CSV file. + + *[ > ]: and then diff --git a/saas_oar_features.md b/saas_oar_features.md new file mode 100644 index 0000000000000000000000000000000000000000..ac708c682a30e741a2e3ba3fc86c93ef164dd50a --- /dev/null +++ b/saas_oar_features.md @@ -0,0 +1,21 @@ +# Orchestrated Recovery features + +Source: https://docs.rubrik.com/en-us/saas/saas/oar_features.html + +--- + +# Orchestrated Recovery features + +Orchestrated Recovery features enable data management and protection tasks for Recovery Plans. + +Task | Description +---|--- +Managed hierarchy and authorization | + + * A user account with View privileges on all of the virtual machines in theRecovery Plan can access the Recovery Plan. + * Removing a virtual machine from a Recovery Plan does not alter the permissions assigned to that virtual machine. + + +Backup | Based on the SLA Domain assigned to the virtual machine, the Rubrik cluster initiates backup jobs and takes snapshots of the virtual machines contained in a Recovery Plan. The Rubrik cluster saves metadata and snapshots for each virtual machine in the Recovery Plan. +Agentless reconfiguration | In Orchestrated Recovery, network reconfiguration and post-script execution is agentless and installing RBS for network reconfiguration is not required. You must enable vCenter privileges for this option to be available. + *[ > ]: and then diff --git a/saas_oar_objects.md b/saas_oar_objects.md new file mode 100644 index 0000000000000000000000000000000000000000..3caad6f34cf489ab3d7fdccce4c94164164da96a --- /dev/null +++ b/saas_oar_objects.md @@ -0,0 +1,17 @@ +# Orchestrated Recovery objects + +Source: https://docs.rubrik.com/en-us/saas/saas/oar_objects.html + +--- + +# Orchestrated Recovery objects + +The Objects page provides information about the objects for which Orchestrated Recovery is configured or available for configuration. + +The Objects page provides details about the SLA Domain, Recovery Plan, number of snapshots, and recoveries for objects withOrchestrated Recovery enabled. You can view the objects in the vSphere, AHV, and Azure virtual machines tabs. From the Objects page, you can: + + * Filter vSphere and AHV virtual machines by SLA Domain, Recovery Plan type, or Rubrik cluster. You can filter Azure virtual machines by Recovery Plan type, source subscription, target subscription, or region. + * Search for an object by name in the Search bar. + * Select objects and use the Cyber Recovery wizard to recover them. + + *[ > ]: and then diff --git a/saas_oar_rp.md b/saas_oar_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..59c032f6e0b50b8dae2b5cfe558139b0f5fa75df --- /dev/null +++ b/saas_oar_rp.md @@ -0,0 +1,28 @@ +# Recovery Plans + +Source: https://docs.rubrik.com/en-us/saas/saas/oar_rp.html + +--- + +# Recovery Plans + +RSC uses Recovery Plans as templates to store the virtual machine configurations and resource mappings used during recovery. + +A Recovery Plan stores resource mappings for each virtual machine to enable recovery, failover, failback, and application migration by mapping the required compute, storage, and network resources from a production environment to the environment at the recovery site. + +You can create Recovery Plans to recover virtual machines located on the source cluster and replicas from the target cluster. Only virtual machines can be used to create Recovery Plans. If a virtual machine that was part of a Recovery Plan becomes a relic, it can still be recovered as part of the Recovery Plan. + +Apart from resource specifications, a Recovery Plan specifies a boot order for virtual machines. During a recovery operation, RSC brings up each virtual machine in the first boot group or priority group, then proceeds to the next boot group in the sequence. Pauses can also be configured between priority groups if required. + +You can create Recovery Plans for the different types of recovery: + + * Disaster recovery and application migration + * Cyber recovery to an environment that is not connected to a production environment. + * In-place recovery on the same Rubrik cluster + +You can also save the specifications selected in a cyber recovery as a cyber Recovery Plan. + +Important: + +A Recovery Plan can only contain virtual machines from the same Rubrik cluster. + *[ > ]: and then diff --git a/saas_on-demand_classification.md b/saas_on-demand_classification.md new file mode 100644 index 0000000000000000000000000000000000000000..85ef7a7ed8f9f8da478a6dc329eabea3cc8304dd --- /dev/null +++ b/saas_on-demand_classification.md @@ -0,0 +1,18 @@ +# On-demand classification + +Source: https://docs.rubrik.com/en-us/saas/saas/on-demand_classification.html + +--- + +# On-demand classification + +On-demand classification jobs run against the most recent snapshot of the specified resources to generate classification results and reports. + +Apart from Data Security Posture classification, you can also initiate classification jobs on demand. During classification jobs, Data Security Posture analyzes the most recent indexed snapshots to find all data that matches the selected policies. Either predefined policies or custom analyzers, or a combination of both, can be used to look for specific types of data. Data Security Posture searches the most recent indexed snapshots to find the specified types of data. + +[Supported file types](../dspm/supported_file_types.html "Information about the file types that Data Security Posture analyzes and performs deep inspection for classifying the data discovered.") describes the list of file types RSC supports. + +Data Security Posture provides classification results in a prioritized list that uses the hierarchy of the source file system. From the top-level classification results, you can browse the objects, sub-directories, and individual files that contain hits from each analyzer. + +RSC exports the results of a data classification job to a CSV file. The CSV file contains a list of all classification files that contain hits and their associated metadata. The CSV file can be downloaded from the browser for further analysis. + *[ > ]: and then diff --git a/saas_orchestrated_recovery_guest_operating_systems.md b/saas_orchestrated_recovery_guest_operating_systems.md new file mode 100644 index 0000000000000000000000000000000000000000..fe08143d044e2f29eec13c05a82e90675bd9accf --- /dev/null +++ b/saas_orchestrated_recovery_guest_operating_systems.md @@ -0,0 +1,23 @@ +# Orchestrated Application Recovery guest operating systems + +Source: https://docs.rubrik.com/en-us/saas/saas/orchestrated_recovery_guest_operating_systems.html + +--- + +# Orchestrated Application Recovery guest operating systems + +The Orchestrated Application Recovery feature supports specific guest operating systems and provides network configuration and postscript support for Rubrik Backup Services. + +## Supported guest operating systems + +The following table lists the guest operating systems that support the Orchestrated Application Recovery feature. + +OS version | Network configuration method | Orchestrated Application Recovery support status +---|---|--- +RHEL 6, 7, 8 | network-scripts NetworkManager | Yes TBD +CentOs 6, 7, 8 | network-scripts NetworkManager | Yes TBD +Ubuntu 16.04 LTS | /etc/network/interfaces | Yes +Ubuntu 18.04 and 20.04 LTS | /etc/network/interfaces netplan/cloud-init | Yes TBD +Suse Linux Enterprise 11, 12, 15 | network-script NetworkManager | Yes TBD +Microsoft Windows Server (All CDM-supported releases) | N/A | Yes + *[ > ]: and then diff --git a/saas_organization_branding.md b/saas_organization_branding.md new file mode 100644 index 0000000000000000000000000000000000000000..c002e6cc5c810fb60129fec6f58348a069bce8ac --- /dev/null +++ b/saas_organization_branding.md @@ -0,0 +1,22 @@ +# Organization branding + +Source: https://docs.rubrik.com/en-us/saas/saas/organization_branding.html + +--- + +# Organization branding + +Organization branding personalizes RSC by displaying a selected custom brand logo for all users in the global organization and associated tenant organizations. + +You can add a custom brand logo to personalize RSC for the global organization and all the associated tenant organizations. This custom brand logo appears in the global header in the global organization and all the tenant organizations for all users. + +You are required to log in as an administrator to the global organization to view the Organization Branding page. Users without administrator privileges in the global organization and tenant organization administrators and users cannot view the Organization Branding page. + +The recommended image guidelines for the brand logo are: + + * Dimension of 24 x 24 pixels + * Format of .png, .jpg, .jpeg, or .webp + * Maximum file size of 48 kB + +Optionally, you can also provide a URL that is accessible by clicking the brand logo. This URL can link back to your website and improve awareness about your organization. Once entered, RSC retains your website URL when enabling or disabling the Logo URL. The organization administrator can also revert to the unbranded configuration. + *[ > ]: and then diff --git a/saas_pause_resume_cluster_notifications.md b/saas_pause_resume_cluster_notifications.md new file mode 100644 index 0000000000000000000000000000000000000000..4e54a50a7d96104aae8f65ff4a0d0651740a5849 --- /dev/null +++ b/saas_pause_resume_cluster_notifications.md @@ -0,0 +1,20 @@ +# Pause and resume Rubrik cluster notifications + +Source: https://docs.rubrik.com/en-us/saas/saas/pause_resume_cluster_notifications.html + +--- + +# Pause and resume Rubrik cluster notifications + +To improve operational management while performing maintenance work for a Rubrik cluster, you can temporarily pause webhook, email, and event digest notifications. + +You can use the pause and resume notifications feature to silence expected operational notifications that can occur during Rubrik cluster maintenance. Pausing notifications prevents you from receiving continuous notifications for expected behavior during maintenance. Rubrik Security Cloud (RSC) allows you to pause the following notification types: + + * Webhooks + * Individual emails + * Email digests + +You can pause notifications for only one Rubrik cluster at a time. Paused notifications are not saved or preserved. The Events page displays events that occurred during the time notifications were paused. + +To use this feature, you must have a role with administrator privileges for the Rubrik cluster. The pause and resume notifications feature is available for Rubrik clusters running Rubrik CDM versions 7.0 and later. + *[ > ]: and then diff --git a/saas_pause_resume_protection_activity.md b/saas_pause_resume_protection_activity.md new file mode 100644 index 0000000000000000000000000000000000000000..2c504c236ba9e323f6455f39ac5d2a5bf862e22f --- /dev/null +++ b/saas_pause_resume_protection_activity.md @@ -0,0 +1,32 @@ +# Pause and resume protection activity + +Source: https://docs.rubrik.com/en-us/saas/saas/pause_resume_protection_activity.html + +--- + +# Pause and resume protection activity + +When you are performing maintenance activities on a Rubrik cluster, you can temporarily pause the protection activity and then resume it by using the pause and resume protection activity feature. + +Pausing the protection activity provides a temporary pause from scheduled backups and archiving jobs on a Rubrik cluster. Pausing protection cancels all in-progress backup and archival tasks. + +When you pause protection, you can perform the following actions: + + * Take on-demand snapshots. + * Continue database log backups regardless of pause status. + * Suspend the scheduling of any further tasks by the Rubrik cluster. + * Allow any already running replication tasks to complete. + * Perform maintenance activities on the Rubrik cluster without interference from scheduled backups and archiving. + +When you pause protection, you cannot perform the following actions: + + * Run scheduled backup jobs. + * Start new backup or archiving jobs. + * Resume any stopped backup or archiving jobs. These jobs will start only after protection is resumed. + +The pause protection activity feature prevents scheduled backup and archiving jobs from starting and initiates stopping of backup and archiving jobs that are in progress. You can use this feature to temporarily reduce the impact of Rubrik cluster activity on the associated resources and resume protection when required. + +Pausing and resuming backup jobs and archival data uploads require RSC administrator privileges. + +The pause protection feature is available for Rubrik clusters running Rubrik CDM version 6.0 or later. + *[ > ]: and then diff --git a/saas_performing_cyber_recovery_ahv_vms.md b/saas_performing_cyber_recovery_ahv_vms.md new file mode 100644 index 0000000000000000000000000000000000000000..27ac9d84c6856330cda2c509072779c8bfef4f4b --- /dev/null +++ b/saas_performing_cyber_recovery_ahv_vms.md @@ -0,0 +1,91 @@ +# Performing a cyber recovery for AHV virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_cyber_recovery_ahv_vms.html + +--- + +# Performing a cyber recovery for AHV virtual machines + +Perform a cyber recovery using a Recovery Plan to recover AHV virtual machines into an isolated recovery environment. Recovery can also be conducted to shared infrastructure with IP networks not connected to production environments. + +## Before you begin + +Ensure that you have assigned recovery operations privileges, such as exporting and mounting virtual machines, on the Nutanix cluster. Recovery operations permissions are required to use the Live Mount or Export options for a cyber recovery, + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click **Recovery Plans**. + +You can access Recovery Plans for the virtual machines in the respective tabs. + +The Recovery Plans page appears, listing all Recovery Plans + + 4. Select the filter for the type of Recovery Plan. + +The page displays a list of all Recovery Plans. + + 5. Select a Recovery Plan from the list and click Recover. + +The Start Recovery Plan wizard appears. + + 6. Select a recovery method. + +Option| Description +---|--- +Live Mount | Creates new virtual machines from snapshots and uses the Rubrik cluster as the datastore. If you choose this option, RSC gets your applications up and running faster. +Export | Creates new virtual machines from snapshots and uses the selected target storage resources for the new virtual machines. + + 7. In Snapshot Selection, choose a recovery point in time. + +Option| Description +---|--- +Latest Snapshots | The cyber recovery uses the most recent snapshot for each virtual machine in the Recovery Plan. +Select Snapshots | Specify a snapshot to use for each virtual machine in the Recovery Plan. Open for each virtual machine and click Select Snapshot to choose a snapshot. Then, click Save Selection to save your selected snapshot. + +When you choose to select snapshots for each virtual machine, you can filter them based on the Data Threat Analytics outcome. + + 8. When using the Select snapshots option, in Latest Snapshot Taken Before, select the date and time, and in Anomaly Detection Outcome, select a snapshot type. + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides a filtered list of non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides a filtered list of quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides a filtered list of anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a filtered list of snapshots without considering snapshot status. + + 9. (Select snapshots) Select snapshots for the objects and click Save Selection. + 10. Click Next. + 11. In Error Handling, select an option. + +Option| Description +---|--- +Pause and resume recovery manually after assessing the error | RSC pauses the recovery and resumes after assessing the error.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort recovery and clean up the recovered objects | RSC stops the recovery and cleans the recovery jobs and any resources in use if an error is encountered during the recovery. + + 12. Click Next. + +The Confirm Network Resources page appears. + + 13. Enter a Recovery Name. + +If you do not enter a recovery name, RSC names the recovery named as Recovery_Plan_Name_Recovery_Date_Recovery_Number by default, where Number stands for an assigned number. + +When you provide a name, RSC names the recovery accordingly. + + 14. **Optional:** Select Remove all network devices when networking changes or issues prevent the virtual machine from starting. + 15. Select Preserve MAC address to use MAC addresses from the snapshot instead of assigning new MAC addresses. + +When the snapshot contains manually assigned MAC addresses, those MAC addresses are used even when this option is not selected. + + 16. **Optional:** Click the network name to select a different network. + 17. Click Recover. + +## Results + +RSC starts the cyber recovery and updates the Recoveries tab. You can view Recovery information in the Recoveries and Events pages. + *[ > ]: and then diff --git a/saas_performing_cyber_recovery_azure_vms.md b/saas_performing_cyber_recovery_azure_vms.md new file mode 100644 index 0000000000000000000000000000000000000000..b255c3e13512e883b6b9b70a16180d078f0c36ee --- /dev/null +++ b/saas_performing_cyber_recovery_azure_vms.md @@ -0,0 +1,76 @@ +# Performing a cyber recovery for Azure virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_cyber_recovery_azure_vms.html + +--- + +# Performing a cyber recovery for Azure virtual machines + +Perform a cyber recovery using a Recovery Plan to recover Azure virtual machines into an isolated recovery environment. + +## About this task + +If recovering to an isolated environment, ensure that you include all fundamental infrastructure services required for these virtual machines to function. These infrastructure services might include but are not limited to DNS and authentication services. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Select a cyber Recovery Plan from the list and click Recover. + +The Start a Cyber Recovery wizard appears. + + 4. Enter a Recovery Name. + +If you do not enter a recovery name, RSC names the recovery as "Recovery_Plan_Name_Recovery_Date_Recovery_Number by default, where Number stands for an assigned number. + +When you provide a name, RSC names the recovery accordingly. + + 5. **Optional:** In Boot Settings, select the option to launch in the power off state. + 6. In Error Handling for VM Recovery, choose an option for error handling. + +Option| Description +---|--- +Pause and resume manually after assessing the error | RSC stops the recovery if there is an error during the recovery.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort and clean up the recovered objects | RSC stops the recovery and cleans up the recovery jobs and any resources in use if there is an error during the recovery. + + 7. Click Next. + +The Select Snapshots page appears. + + 8. In Snapshot Selection, choose a recovery point in time. + +Option| Description +---|--- +Latest Snapshots | The cyber recovery uses the most recent snapshot for each virtual machine in the Recovery Plan. +Select Snapshots | Specify a snapshot to use for each virtual machine in the Recovery Plan. Open for each virtual machine and click Select Snapshot to choose a snapshot. Then, click Save Selection to save your selected snapshot. + +When you choose to select snapshots for each virtual machine, you can filter them based on the Data Threat Analytics outcome. + + 9. (Select snapshot) In Latest Snapshot Taken Before, select the date and time, and in Anomaly Detection Outcome, select a snapshot type. + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides a filtered list of non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides a filtered list of quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides a filtered list of anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a filtered list of snapshots without considering snapshot status. + + 10. (Select snapshots) Select snapshots for the objects and click Save Selection. + 11. Click Next. + +The Network Configuration page appears. + + 12. **Optional:** (Editing network configuration) Edit the network configuration settings and click Save. + +You can edit the VNet, Subnet, and Network Security Group for the Recovery Plan. Network Security Groups are optional and are not used by default. + + 13. Click Recover. + +## Results + +RSC starts the cyber recovery and updates the Recoveries tab. You can view Recovery information in the Recoveries and Events pages. + *[ > ]: and then diff --git a/saas_performing_cyber_recovery_export_ahv.md b/saas_performing_cyber_recovery_export_ahv.md new file mode 100644 index 0000000000000000000000000000000000000000..a7900124bd0d335962a12dbeade1160d8a947baf --- /dev/null +++ b/saas_performing_cyber_recovery_export_ahv.md @@ -0,0 +1,128 @@ +# Performing a cyber recovery using Export on AHV virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_cyber_recovery_export_ahv.html + +--- + +# Performing a cyber recovery using Export on AHV virtual machines + +Perform an export to recover selected AHV virtual machines to a local or remote, isolated recovery environment. Recovery can also be conducted to shared infrastructure with IP networks not connected to production environments. + +## About this task + +The Export recovery option creates virtual machines from snapshots and uses the selected target storage resources for the virtual machines. + +If you are recovering to an isolated environment, ensure that you include all fundamental infrastructure services required for these virtual machines to function. These services might include but are not limited to DNS and authentication services. + +When recovering AHV virtual machines, to enable successful recovery operations, privileges to export the virtual machines must be assigned on the Nutanix cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Objects. + +The Objects tab appears with a detailed list of objects, including the assigned SLA Domain and name of the Rubrik cluster. + + 4. Click AHV. + +The list of all AHV objects appears. + + 5. Select the AHV objects to recover and click Start **Cyber Recovery** . + +All objects selected for recovery must have at least one snapshot on the same cluster. Additionally, the Rubrik cluster must be running a minimum of Rubrik CDM version 9.2 to perform a cyber recovery. + +If you are recovering virtual machines and replicas, the objects in the recovery must have a common cluster, either the source cluster or the target cluster. + + 6. **Optional:** Review the What is Cyber Recovery page and click Start. + +The informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. Selecting the option to not show the page again prevents this page from appearing in the future. + + 7. Select Export as the option for recovery. and click Next. + +The Select Snapshots page appears. + + 8. In Cluster, select the cluster you want to use for the recovery. + +If you choose the replication cluster, the replica of the object is recovered. + + 9. In Latest snapshot taken before, select the date and time for the snapshot. + 10. Select a snapshot for recovery for each object. + +You can filter based on the Anomaly Detection outcome. Options include the following: + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a snapshot without considering snapshot status. + +You cannot complete recovery when are no snapshots are available for an object. + + 11. In Error Handling, select an option. + +Option| Description +---|--- +Pause and resume recovery manually after assessing the error | RSC pauses the recovery and resumes after assessing the error.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort recovery and clean the recovered objects | If RSC encounters any errors during the recovery, it stops the recovery and removes any changes to the recovery job and resources. + + 12. Click Next. + 13. Assign a boot priority order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. Rubrik recommends that you prioritize recovering Identity and Access Management and other core infrastructure services. + + 14. **Optional:** Turn on Enable pauses between priority groups. + +RSC displays the specified pauses during recovery in minutes. + + 15. Click Next. + +The Assign Target Compute Resources page appears. + + 16. Select the target compute resources that you want your objects to use. + 17. Select the Assign the same compute resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign compute resources for individual objects. + + 18. Click Next. + +The Assign Target Storage Resources page appears. + + 19. Select the Assign the same storage resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign storage resources for individual objects. + + 20. Click Next. + +The Assign Target Network Resource page appears. + + 21. Select Remove all network devices and Preserve MAC Address. + 22. Click Fast Fill to apply the selected values to multiple objects. + +The Fast Fill window opens for applying the network resource values to multiple objects. + + 23. Select an option for error handling for network configurations. + 24. Click Next. + +The Confirmation page appears. + + 25. **Optional:** Turn on Save as Recovery Plan to save your recovery specifications. + +A Recovery Plan saves information about the selected objects, their recovery order, and the target resources. You can use this plan to perform a cyber recovery in the future. If any of the virtual machines you selected for this recovery are relics, the Recovery Plan cannot be saved for future use. + + 26. For saving as a Recovery Plan, in **Recovery Plan Name** Details, enter a name for the Recovery Plan. + +When a name is provided, the recovery is named a combination of the Recovery Plan name, date, and number. If you do not enter a recovery name, the recovery is named as Recovery Number by default, where Number stands for an assigned number. + + 27. Click Confirm. + +## Results + +RSC starts the cyber recovery and updates the Recoveries page. + +If you select the option to save the Recovery Plan, it appears in the Recovery Plans page. + *[ > ]: and then diff --git a/saas_performing_cyber_recovery_export_azure.md b/saas_performing_cyber_recovery_export_azure.md new file mode 100644 index 0000000000000000000000000000000000000000..f2b46588565fe3501410629d5069964471faf700 --- /dev/null +++ b/saas_performing_cyber_recovery_export_azure.md @@ -0,0 +1,100 @@ +# Performing a cyber recovery using Export on Azure virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_cyber_recovery_export_azure.html + +--- + +# Performing a cyber recovery using Export on Azure virtual machines + +Perform an export to recover selected Azure virtual machines to a local or remote, isolated recovery environment. Recovery can also be conducted to shared infrastructure with IP networks not connected to production environments. + +## About this task + +The Export recovery option creates virtual machines from snapshots and uses the selected target storage resources for the virtual machines. + +If you are recovering to an isolated environment, ensure that you include all fundamental infrastructure services required for these virtual machines to function. These services might include but are not limited to DNS and authentication services. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Objects. + +The Objects tab appears with a detailed list of objects, including the assigned SLA Domain and name of the Rubrik cluster. + + 4. Click Azure VM. + +The list of all Azure objects appears. + + 5. Select the objects to recover and click Start **Cyber Recovery** . + +All objects selected for recovery must have at least one snapshot and must belong to the same subscription and region. + + 6. **Optional:** Review the What is Cyber Recovery page and click Start. + +This informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. Selecting the option to not show the page again prevents this page from appearing in the future. + + 7. In Recovery Name, enter a name for the recovery. + +. If you do not enter a recovery name, the recovery is named a combination of the recovery type, recovery date, and recovery number by default, where number stands for an assigned number. + + 8. In Recovery Target, select a Subscription. + +RSC supports cyber recovery for Azure virtual machines on the same region as the recovery source subscription only. + + 9. Select an option to export tags for all virtual machines and to launch in the power-off state. + 10. In Error Handling, select an option. + +Option| Description +---|--- +Pause and resume recovery manually after assessing the error | RSC pauses the recovery and resumes after assessing the error.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort recovery and clean the recovered objects | If RSC encounters any errors during the recovery, it stops the recovery and removes any changes to the recovery job and resources. + + 11. Click Next. + 12. Select the snapshots you want to recover and click Next. + 13. Assign a boot priority order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. Rubrik recommends that you prioritize recovering Identity and Access Management and other core infrastructure services. + + 14. **Optional:** Turn on Enable pauses between priority groups. + +RSC displays the specified pauses during recovery in minutes. + + 15. Click Next. + +The Assign Target Compute Resources page appears. + + 16. Select a target resource group option and click Next. + +You can select the same resource group to all objects, or select a different resource group for objects. + + 17. Select an encryption option for Attached Disk Encryption and click Next. + +You can select options to encrypt with a platform-managed key, encrypt with the same customer-managed key, or select keys individually. + + 18. Click Next. + +The Target Network page appears. + + 19. Select a VNet and subnet. + 20. **Optional:** Select a Network Security Group. + 21. Click Next. + +The Confirmation page appears. + + 22. **Optional:** Turn on Save as Recovery Plan to save your recovery specifications. + +A Recovery Plan saves information about the selected objects, their recovery order, and the target resources. You can use this plan to perform a cyber recovery in the future. If any of the virtual machines you selected for this recovery are relics, the Recovery Plan cannot be saved for future use. + + 23. For saving as a Recovery Plan, in **Recovery Plan Name** Details, enter a name for the Recovery Plan. + 24. Click Confirm. + +## Results + +RSC starts the cyber recovery and updates the Recoveries page. + +If you select the option to save the Recovery Plan, it appears in the Recovery Plans page. + *[ > ]: and then diff --git a/saas_performing_cyber_recovery_export_vsphere.md b/saas_performing_cyber_recovery_export_vsphere.md new file mode 100644 index 0000000000000000000000000000000000000000..ce31548ab5c0145fd92a075d3c0f91d8a4542381 --- /dev/null +++ b/saas_performing_cyber_recovery_export_vsphere.md @@ -0,0 +1,142 @@ +# Performing a cyber recovery using Export on vSphere virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_cyber_recovery_export_vsphere.html + +--- + +# Performing a cyber recovery using Export on vSphere virtual machines + +Perform an export to recover selected vSphere virtual machines to a local or remote, isolated recovery environment. Recovery can also be conducted to shared infrastructure with IP networks not connected to production environments. + +## About this task + +The Export recovery option creates new virtual machines from snapshots and uses the selected target storage resources for the virtual machines. + +If you are recovering to an isolated environment, ensure that you include all fundamental infrastructure services required for these virtual machines to function. These services might include but are not limited to DNS and authentication services. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Objects. + +The Objects tab appears with a detailed list of objects, including the assigned SLA Domain and name of the Rubrik cluster. + + 4. Click vSphere. + +The list of all vSphere objects appears. + + 5. Select the objects to recover and click Start **Cyber Recovery** . + +All objects selected for recovery must belong to the same cluster. If you are recovering virtual machines and replicas, the objects in the recovery must have a common cluster, either the source cluster or the target cluster. + +The Start Cyber Recovery wizard appears. + + 6. **Optional:** Review the What is Cyber Recovery page and click Start. + +This informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. Selecting the option to not show the page again prevents this page from appearing in the future. + +The Select a Recovery Option page appears. + + 7. Select Export as the option for recovery. + 8. Click Next. + +The Select Snapshots page appears. + + 9. In Cluster, select the cluster you want to use for the recovery. + +If you choose the replication cluster, the replica of the object is recovered. + + 10. In Latest snapshot taken before, select the date and time for the snapshot. + 11. Select a snapshot for recovery for each object. + +You can filter based on the Anomaly Detection outcome. Options include the following: + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a snapshot without considering snapshot status. + +You cannot complete recovery when are no snapshots are available for an object. + + 12. In Error Handling, select an option. + +Option| Description +---|--- +Pause and resume recovery manually after assessing the error | RSC pauses the recovery and resumes after assessing the error.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort recovery and clean the recovered objects | If RSC encounters any errors during the recovery, it stops the recovery and removes any changes to the recovery job and resources. + + 13. Click Next. + 14. Assign a boot priority order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. Rubrik recommends that you prioritize recovering Identity and Access Management and other core infrastructure services. + + 15. **Optional:** Turn on Enable pauses between priority groups. + +RSC displays the specified pauses during recovery in minutes. + + 16. Click Next. + +The Assign Target Compute Resources page appears. + + 17. Select the target compute resources that you want your objects to use. + 18. Select the Assign the same compute resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign compute resources for individual objects. + + 19. Click Next. + +The Assign Target Storage Resources page appears. + + 20. Select the Assign the same storage resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign storage resources for individual objects. + + 21. Click Next. + +The Assign Target Network Resource page appears. + + 22. Select an option for Network Preservation. + +Option| Description +---|--- +Select Entire Network and then select Network for each object. | The current MAC Address and IP configuration are retained. +Select MAC Address Only and then select Network and IP Configuration for each object. | The current MAC address is retained for the source virtual machine. +Select None and then select Network and IP Configuration for each object. | A new MAC address is assigned to the virtual machine. + + 23. Click Fast Fill to apply the selected values to multiple objects. + +The Fast Fill window opens for applying the network resource values to multiple objects. + + 24. Select an option for error handling for network configurations. + 25. Click Next. + 26. **Optional:** For vSphere virtual machine recovery, on the Specify Post-Recovery Scripts page, enter the script or the path to the script that you want to run on each virtual machine after recovery. + +Ensure that the path points to an existing shell script on the associated virtual machine. + + 27. Click Next. + +The Confirmation page appears. + + 28. **Optional:** Turn on Save as Recovery Plan to save your recovery specifications. + +A Recovery Plan saves information about the selected objects, their recovery order, and the target resources. You can use this plan to perform a cyber recovery in the future. If any of the virtual machines you selected for this recovery are relics, the Recovery Plan cannot be saved for future use. + + 29. For saving as a Recovery Plan, in Recovery Plan Name, enter a name for the recovery plan. + 30. For saving as a Recovery Plan, in **Cyber Recovery** Details, enter a name for the Recovery Plan. + +When a name is provided, the recovery is named a combination of the Recovery Plan name, date, and number. If you do not enter a recovery name, the recovery is named as Recovery Number by default, where Number stands for an assigned number. + + 31. Click Recover. + +## Results + +RSC starts the cyber recovery and updates the Recoveries page. + +If you select the option to save the Recovery Plan, it appears in the Recovery Plans page. + *[ > ]: and then diff --git a/saas_performing_cyber_recovery_live_mount.md b/saas_performing_cyber_recovery_live_mount.md new file mode 100644 index 0000000000000000000000000000000000000000..0fdba6d941115a92910d64fbcd188e2293ec0aa8 --- /dev/null +++ b/saas_performing_cyber_recovery_live_mount.md @@ -0,0 +1,136 @@ +# Performing a cyber recovery using Live Mount + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_cyber_recovery_live_mount.html + +--- + +# Performing a cyber recovery using Live Mount + +Perform a Live Mount to recover selected virtual machines to a local or remote recovery environment. Recovery can also be conducted to shared infrastructure with IP networks not connected to production environments. + +## About this task + +The Live Mount recovery option creates new virtual machines from snapshots and uses the Rubrik cluster as the datastore or storage container. This option also gets your applications up and running sooner. + +If you are recovering to an isolated environment, ensure that you include all fundamental infrastructure services required for these virtual machines to function. These infrastructure services might include but are not limited to DNS and authentication services. + +When recovering AHV virtual machines, to enable successful recovery operations, privileges to export the virtual machines must be assigned on the Nutanix cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Objects. + +The Objects tab appears with a detailed list of objects, including the relevant SLA Domain and Rubrik cluster. You can access vSphere virtual machines and AHV virtual machines in the respective tabs. + + 4. Select the objects to recover and click Start **Cyber Recovery**. + +All objects selected for recovery must belong to the same cluster. If you are recovering virtual machines and replicas, the objects in the recovery must have a common cluster, either source cluster or target cluster. + +The Start Cyber Recovery wizard appears. + + 5. In the Select Recovery Option page, select Live Mount as the option for recovery. + 6. Click Next. + +The Select Snapshots page appears. + + 7. In Cluster, select the cluster you want to use for the recovery. + +If you choose the replication cluster, the replica of the object is recovered. + + 8. In Latest snapshot taken before, select the date and time for the snapshot. + 9. Select a snapshot for recovery for each object. You can filter based on the Anomaly Detection outcome. Options include the following: + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides a filtered list of non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides a filtered list of quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. Users must have privileges to recover quarantined snapshots to use this option. +Anomalous | Provides a filtered list of anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a filtered list of snapshots without considering snapshot status. + +If no snapshots are available for an object, recovery cannot be completed. + + 10. In Error Handling for VM Recovery select an option: + +Option| Description +---|--- +Pause and resume manually after assessing the error | RSC pauses the recovery and resumes after assessing the error.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort and clean up the recovered objects | RSC stops the recovery and cleans up the recovery jobs and any resources in use if it encounters an error during the recovery. + +The Assign a Recovery Order page appears. + + 11. Assign a recovery order for the objects that you want to recover and select their priority group. + +First, recover the Identity and Access Management and other core infrastructure services needed for recovery. + + 12. **Optional:** Turn on the Enable pauses between priority groups toggle. + +If you turn on this toggle, you can add pauses between the priority groups and display their duration in minutes. + + 13. Click Next. + +The Assign Target Compute Resources page appears. + + 14. Select the Assign the same compute resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign compute resources for individual objects. + + 15. Select the target compute resources that you want the objects to use . + 16. Click Next. + 17. For vSphere virtual machine recovery, select the Assign the same storage resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. + +This option is selected by default. If you do not select this option, you can assign storage resources for individual objects. + + 18. Click Next. + +The assign Network Resources page appears. + + 19. Specify your network configurations for recovery. + 20. For vSphere virtual machine recovery, select an option for Network Preservation. + +Option| Description +---|--- +Select Entire Network and then select Network for each object. | The current MAC Address and IP configuration are retained. +Select MAC Address Only and then select Network and IP Configuration for each object. | The current MAC address is retained for the source virtual machine. +Select None and then select Network and IP Configuration for each object. | A new MAC address will be assigned to the virtual machine. + + 21. **Optional:** For vSphere virtual machine recovery, select the Ignore network reconfiguration errors and continue check box. + +If you select this option, RSC ignores network configuration and post-script errors, and network configuration or post-script errors will not cause recovery failure. + + 22. For vSphere virtual machine recovery, select Remove all network devices to recover without connecting to a network. + 23. For AHV virtual machine recovery, select Remove all network devices and Preserve MAC Address. + 24. Click Fast Fill to apply the selected values to multiple objects. + +The Fast Fill window opens for applying the network resource values to multiple objects. + + 25. Click Next. + 26. **Optional:** For vSphere virtual machine recovery, on the Specify Post-Recovery Scripts page, enter the script or the path to the script that you want to run on each virtual machine after recovery. + +Ensure that the path points to an existing shell script on the associated virtual machine. + + 27. Click Next. + +The Confirm Cyber Recovery page appears. + + 28. **Optional:** Turn on Save as a Recovery Plan to save your recovery specifications. + +A Recovery Plan saves information about the selected objects, their recovery order, and the target resources. You can use this plan to perform a cyber recovery in the future. If any of the virtual machines you selected for this recovery are relics, the Recovery Plan cannot be saved for future use. + + 29. For saving as a Recovery Plan, in Recovery Plan Name, enter a name for the recovery plan. + 30. For saving as a Recovery Plan, in **Cyber Recovery** Details, enter a name for the Recovery Plan. + +If a name is provided, the recovery is named a combination of the Recovery Plan name, date, and recovery number. If you do not enter a recovery name, the recovery is named a combination of recovery type, date, and recovery number. + + 31. Click Recover. + +## Results + +RSC starts the cyber recovery and updates the Recoveries page. + +If you select the option to save the Recovery Plan, it appears on the Recovery Plans page. + *[ > ]: and then diff --git a/saas_performing_cyber_recovery_vsphere.md b/saas_performing_cyber_recovery_vsphere.md new file mode 100644 index 0000000000000000000000000000000000000000..33979db9859e0ec397aef6a939f33b93b20750b5 --- /dev/null +++ b/saas_performing_cyber_recovery_vsphere.md @@ -0,0 +1,100 @@ +# Performing a cyber recovery for vSphere virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_cyber_recovery_vsphere.html + +--- + +# Performing a cyber recovery for vSphere virtual machines + +Perform a cyber recovery using a Recovery Plan to recover vSphere virtual machines into an isolated recovery environment. Recovery can also be conducted to shared infrastructure with IP networks not connected to production environments. + +## Before you begin + +Assign Change Memory privileges in the vCenter Server. + +To use the Export option for vSphere virtual machines, add the storage resources added to the Recovery Plan. + +## About this task + +If recovering to an isolated environment, ensure that you include all fundamental infrastructure services required for these virtual machines to function. These infrastructure services might include but are not limited to DNS and authentication services. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click **Recovery Plans**. + +You can access Recovery Plans for the virtual machines in the respective tabs. + +The Recovery Plans page appears, listing all Recovery Plans + + 4. Select the filter for the type of Recovery Plan. + +The page displays a list of all Recovery Plans. + + 5. Select a Recovery Plan from the list and click Recover. + +The Start Recovery Plan wizard appears. + + 6. Select a recovery method. + +Option| Description +---|--- +Live Mount | Creates new virtual machines from snapshots and uses the Rubrik cluster as the datastore. If you choose this option, RSC gets your applications up and running faster. +Export | Creates new virtual machines from snapshots and uses the selected target storage resources for the new virtual machines. + + 7. In Snapshot Selection, choose a recovery point in time. + +Option| Description +---|--- +Latest Snapshots | The cyber recovery uses the most recent snapshot for each virtual machine in the Recovery Plan. +Select Snapshots | Specify a snapshot to use for each virtual machine in the Recovery Plan. Open for each virtual machine and click Select Snapshot to choose a snapshot. Then, click Save Selection to save your selected snapshot. + +When you choose to select snapshots for each virtual machine, you can filter them based on the Data Threat Analytics outcome. + + 8. When using the Select snapshots option, in Latest Snapshot Taken Before, select the date and time, and in Anomaly Detection Outcome, select a snapshot type. + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides a filtered list of non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides a filtered list of quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides a filtered list of anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a filtered list of snapshots without considering snapshot status. + + 9. (Select snapshots) Select snapshots for the objects and click Save Selection. + 10. Click Next. + 11. In Error Handling, select an option. + +Option| Description +---|--- +Pause and resume recovery manually after assessing the error | RSC pauses the recovery and resumes after assessing the error.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort recovery and clean up the recovered objects | RSC stops the recovery and cleans the recovery jobs and any resources in use if an error is encountered during the recovery. + + 12. Click Next. + +The Confirm Network Resources page appears. + + 13. Enter a Recovery Name. + +If you do not enter a recovery name, RSC names the recovery named as Recovery_Plan_Name_Recovery_Date_Recovery_Number by default, where Number stands for an assigned number. + +When you provide a name, RSC names the recovery accordingly. + + 14. For vSphere virtual machine recovery, in Network Preservation, choose an option: + +Option| Description +---|--- +Select Entire Network and then select Network for each object. | The current MAC address and IP configuration are retained. +Select MAC Address Only and then select Network and IP Configuration for each object. | The current MAC address is retained for the source virtual machine. +Select None and then select Network and IP Configuration for each object. | A new MAC address will be assigned to the virtual machine. + + 15. Select the Recover with network disconnected option to recover without connecting to a network. + 16. Click Recover. + +## Results + +RSC starts the cyber recovery and updates the Recoveries tab. You can view Recovery information in the Recoveries and Events pages. + *[ > ]: and then diff --git a/saas_performing_disaster_recovery.md b/saas_performing_disaster_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..4f152bb62aeff1f63318d71810aec7d55d99f4e2 --- /dev/null +++ b/saas_performing_disaster_recovery.md @@ -0,0 +1,47 @@ +# Performing a disaster recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_disaster_recovery.html + +--- + +# Performing a disaster recovery + +Use a Recovery Plan to recover virtual machines to a recovery site during disaster recovery or application migration. + +## Before you begin + +Assign Change Memory privileges in the vCenter Server to enable successful recovery operations when recovering vSphere virtual machines. + +You can perform a disaster recovery only for VMware virtual machines and AHV virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears. + + 4. Select the filter for **Disaster Recovery Plan**. + +The page displays the list of all disaster Recovery Plans. + + 5. Select a disaster Recovery Plan from the list. + 6. Click Recover and then select an option for recovery. + +| +---|--- +Start Failover | Starts a failover of the selected virtual machines to the selected recovery site. +Start Test Failover | Starts a test failover of the selected virtual machines on the test network. + +RSC displays a wizard for recovery according to the option selected. + + 7. Confirm the options in the wizard and click Recover. + +## Results + +RSC recovers the virtual machines in the Recovery Plan using the specified recovery points. You can view Recovery information in the Recoveries and Events pages. + *[ > ]: and then diff --git a/saas_performing_failover_operation.md b/saas_performing_failover_operation.md new file mode 100644 index 0000000000000000000000000000000000000000..1cc55160a1320c5b0be3e3e4355eb9e808ee7ffd --- /dev/null +++ b/saas_performing_failover_operation.md @@ -0,0 +1,72 @@ +# Performing a failover operation + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_failover_operation.html + +--- + +You can perform an export to recover selected AWS virtual machines to a local or remote recovery environment. # Performing a failover operation + +Perform a failover for the virtual machines in the selected Recovery Plan using the specified recovery points. + +## Before you begin + +Assign Change Memory and Create Folder privileges in the vCenter Server to enable successful failover operations. + +You can perform failover operations when at least one snapshot is available for each virtual machine in the Recovery Plan. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click **Recovery Plans**. + +The Recovery Plans page appears. + + 4. Select the filter for **Disaster Recovery Plan**. + +The page displays the list of all disaster Recovery Plans. + + 5. Select a disaster Recovery Plan. + 6. Click Recover > Start Failover. + +The Initiate Failover wizard appears. + + 7. Choose a recovery point in time. + +Option| Description +---|--- +Latest recovery point at target | Click View to view the recovery point. The In-place Recovery uses the most recent snapshot for each virtual machine in the Recovery Plan. +Select a point in time | Click Select to choose a snapshot for each virtual machine. You can specify a snapshot to use for each virtual machine in the Recovery Plan. Click Update to confirm the changes. + + 8. Choose a response to any errors during the failover operation. + +Option| Description +---|--- +Ignore and continue | Continue the recovery when errors specific to a virtual machine occur. This is the default option. When RSC detects errors on a virtual machine, RSC proceeds to recover the rest of the virtual machines specified in the Recovery Plan. RSC displays details on the recovery, including details on the missed virtual machines, on the Events page. +Abort and cleanup | Aborts failover when errors related to the failover process occur. These errors can include RSC and Rubrik cluster connection errors, failures to call the CDM API, and database connection errors. The Events page displays further details of the failover operation. +Pause | Pauses failover when errors related to the failover process occur. These errors can include RSC and Rubrik cluster connection errors, failures to call the CDM API, and database connection errors. You can manually resume the failover process when these errors are cleared. The Events page displays further details of the failover operation. + + 9. **Optional:** Select the check box to use the original site resources for the next failover. + +When you select this option, the post-failover resource map in the Confirm failover step confirms the resources assigned. + + 10. Click Continue. + 11. **Optional:** Click See more in the Post-Failover Resource map. + +Selecting this option displays a summary of the Compute Resources, Storage Resources, and Network Resources - Failover applied to the resource map. + + 12. In the confirmation field, enter `RECOVERYPLAN`. + +The Recover button becomes available. + + 13. Click Recover. + +## Results + +RSC performs a failover operation using the specified snapshots of the virtual machines in the Recovery Plan. RSC also deletes the source virtual machines once the recovery process is fully complete. + +When you select the option to use the resources of the original site for the next failover, RSC auto-updates the resource map to fail back to the source site after the failover. + *[ > ]: and then diff --git a/saas_performing_in_place_recovery.md b/saas_performing_in_place_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..ec06dde8d04e63dd94cc66b3703d392c1b908558 --- /dev/null +++ b/saas_performing_in_place_recovery.md @@ -0,0 +1,60 @@ +# Performing an in-place recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/performing_in_place_recovery.html + +--- + +# Performing an in-place recovery + +Perform an in-place recovery to replace the virtual machines specified by a Recovery Plan with point-in-time copies. + +## About this task + +You can perform an in-place recovery only for VMware virtual machines and AHV virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears. + + 4. Select the filter for **In-Place Recovery Plan**. + +The page displays the list of all in-place Recovery Plans. + + 5. Select an in-place Recovery Plan from the list and click Recover. + +The Initiate In-Place Recovery wizard appears. + + 6. **Optional:** Click the Recovery Plan to access the overview page, open the ellipsis menu, and select Start In-Place Recovery. + 7. Choose a recovery point in time. + +Option| Description +---|--- +Latest available snapshot | The in-place recovery uses the most recent snapshot for each virtual machine in the Recovery Plan +Select a point in time | Click Select to choose a snapshot for each virtual machine. You can specify a snapshot to use for each virtual machine in the Recovery Plan. + + 8. The option to ignore In-Place Recovery Error is selected by default. + 9. **Optional:** Select the checkbox to ignore network reconfiguration errors and continue. + +When this option is selected, the post script will not run in case of errors. Therefore, recovery will not fail if network configuration fails. + + 10. Click Next. + +The Confirm recovery page appears. + + 11. In the confirmation field, enter `Recovery Plan`. + +The Recover button becomes available. + + 12. Click Recover. + +## Results + +RSC performs the in-place recovery for the virtual machines in the Recovery Plan using the specified recovery points. You can view Recovery information in the Recoveries and Events pages. + *[ > ]: and then diff --git a/saas_prerequisites_for_sap_hana_protection.md b/saas_prerequisites_for_sap_hana_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..9b7524086c9356c410955176d4c46ed253d63dd4 --- /dev/null +++ b/saas_prerequisites_for_sap_hana_protection.md @@ -0,0 +1,29 @@ +# Prerequisites for SAP HANA protection + +Source: https://docs.rubrik.com/en-us/saas/saas/prerequisites_for_sap_hana_protection.html + +--- + +# Prerequisites for SAP HANA protection + +There are a number of prerequisites that you must complete to protect SAP HANA systems. + +Prerequisite | Description +---|--- +Configuring the on-premises Rubrik cluster | The on-premises Rubrik cluster or the cloud cluster must be configured on AWS, Azure, or GCP. +Configuring specific ports | If SAP HANA hosts are in different Virtual Private Cloud (VPC) or Azure Virtual Network (VNet), outbound traffic for port 9639 must be allowed from the SAP HANA host to the Rubrik cluster. SAP HANA requires port 9638 for internode communications. Also, inbound and outbound traffic for ports 12800 and 12801 must be allowed between the SAP HANA host and the Rubrik cluster. +Installing RBS | RBS must be installed on the Linux host running the SAP HANA databases and added to a Rubrik cluster. The supported operating systems are Red Hat Enterprise Linux (RHEL) and SUSE Linux Enterprise Server (SLES). +Adding the Rubrik cluster to the RSC interface | The Rubrik cluster must be added to RSC. +Adding the Linux host to the Rubrik cluster | The Linux host must be added to the Rubrik cluster. +Adding the SAP HANA system to the RSC environment | The SAP HANA system must be added to RSC. +Assigning an SLA Domain | An SLA Domain must be assigned to the SAP HANA system and databases in the RSC environment to start protecting SAP HANA objects. +Verifying privileges | The Backup administrator must belong to the SYSTEM database and not a tenant database. The Backup administrator must have the BACKUP ADMIN, CATALOG READ, INIFILE ADMIN, and DATABASE BACKUP ADMIN privileges.The DATABASE BACKUP ADMIN privilege was introduced in SAP HANA 2.0 SPS 04. For systems running on earlier versions, the Backup administrator must have DATABASE ADMIN privilege to take tenant database backups.For high availability setup systems, ensure that you fulfill any one of the following requirements: + + * [inifile_checker]/replicate equals true in global.ini + * The Backup administrator has DATABASE ADMIN privilege to configure [inifile_checker]/replicate equals true. + + +Setting log_mode | The value of log_mode on SAP HANA must be set to normal to enable a continuous recovery chain on the SAP HANA workload. Setting the value of log_mode to overwrite prevents SAP HANA from creating log backups and prevents RSC from creating a continuous recovery chain. +Setting [inifile_checker]/replicate | For high availability setup systems, the value of [inifile_checker]/replicate must be set to true at each database level to automatically replicate the backint configuration. +Setting [inifile_checker]/interval | For high availability setup systems, the value of [inifile_checker]/interval must be set to 900 seconds (15 minutes) at each database level. This setting ensures that the backint configuration is automatically replicated every 15 minutes, matching the frequency set on the primary system. + *[ > ]: and then diff --git a/saas_privileged_access_management.md b/saas_privileged_access_management.md new file mode 100644 index 0000000000000000000000000000000000000000..b47f7d494aae8f70c42532f4a71061237f6c33d2 --- /dev/null +++ b/saas_privileged_access_management.md @@ -0,0 +1,12 @@ +# Privileged access management + +Source: https://docs.rubrik.com/en-us/saas/saas/privileged_access_management.html + +--- + +# Privileged access management + +You can create and manage API credentials to use with the Privileged Access Management solution. + +Privileged Access Management (PAM) is a third-party cybersecurity solution that helps control, monitor, and secure access to your most critical systems. PAM software identifies the people, processes, and technology that require privileged access, and specifies the policies that apply to them. When configured to do so, PAM manages RSC local user passwords using APIs. Enabling PAM activates the APIs necessary for its integration, generates the unique credentials for its software, and allows configuring an optional IP access list to limit connections to a specified IP range. + *[ > ]: and then diff --git a/saas_protecting_sap_hana_objects.md b/saas_protecting_sap_hana_objects.md new file mode 100644 index 0000000000000000000000000000000000000000..d4f9fd554bac1b011fd7a8dc98b637b3ac425f3a --- /dev/null +++ b/saas_protecting_sap_hana_objects.md @@ -0,0 +1,52 @@ +# Protecting SAP HANA workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/protecting_sap_hana_objects.html + +--- + +# Protecting SAP HANA workloads + +To protect SAP HANA workloads by applying the data protection policies and management policies, select and assign an SLA Domain to an SAP HANA workload using the Manage protection option. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click on the SAP HANA inventory card. + +The SAP HANA page appears. + + 5. Select the tab for a workload type. + * Systems + * Databases + +Workloads of the selected type appear. + + 6. Select the workloads to protect. + 7. Click Manage protection. + +The Manage Protection page appears. + + 8. Select a protection option. + +Option| Description +---|--- +SLA Domain | The SLA Domain is assigned to the chosen workloads. +Clear existing assignment | The SLA Domain is assigned from the next higher-level workload based on inheritance rules. +Don't protect | The chosen workloads are excluded from all further SLA Domain assignments. + + 9. Click Assign. + +It takes up to 15 minutes for the backups to start running successfully after an SLA Domain is assigned. This waiting period is applicable only for the first time when backups have to be triggered. Subsequent backups use the already configured Rubrik Backint client, and there is no waiting period. + +## Results + +RSC processes the specified assignments and begins protecting the selected workloads according to the assignments. + *[ > ]: and then diff --git a/saas_protection_hierarchy_for_sap_hana.md b/saas_protection_hierarchy_for_sap_hana.md new file mode 100644 index 0000000000000000000000000000000000000000..4fad178e7684a65c188346107ce3d3cfb8ebf595 --- /dev/null +++ b/saas_protection_hierarchy_for_sap_hana.md @@ -0,0 +1,15 @@ +# Protection hierarchy for SAP HANA objects + +Source: https://docs.rubrik.com/en-us/saas/saas/protection_hierarchy_for_sap_hana.html + +--- + +# Protection hierarchy for SAP HANA objects + +RSC provides hierarchy-based, automatic protection of SAP HANA objects. + +Level | Description +---|--- +SAP HANA system | SAP HANA databases derive their SLA Domain assignments or Don't Protect settings from the SAP HANA system. +SAP HANA databases | SAP HANA databases derive their SLA Domains from the SAP HANA system by default. An SLA Domain assignment or a Don't Protect setting made to the SAP HANA database overrides this default assignment. + *[ > ]: and then diff --git a/saas_quarantine.md b/saas_quarantine.md new file mode 100644 index 0000000000000000000000000000000000000000..8af87cfaf23d1d85ed3c3bde3f68d36367674119 --- /dev/null +++ b/saas_quarantine.md @@ -0,0 +1,59 @@ +# Quarantine overview + +Source: https://docs.rubrik.com/en-us/saas/saas/quarantine.html + +--- + +# Quarantine overview + +The Quarantine feature in Data Threat Analytics isolates potentially malicious files or objects to allow seamless data recovery and to avoid reinfection. + +Data recovery risks restoring malware, ransomware, or other unwanted applications. To restore data rapidly without compromising the recovered systems, you must: + + * Restore to a pre-malware infection state. + * Restore only uninfected files. + +By quarantining the snapshots that contain malware, you can quickly isolate potentially malicious files and identify healthy snapshots to use for performing a full system restore. + +## Quarantine operation and file version + +When you quarantine a file from a threat hunt or Threat Monitoring match, the system creates a quarantine operation. A quarantine operation is expressed as the unique combination of the object, file path, and file version. This operation fundamentally blocks the recovery of a specific file version. The file version is defined by its modification time (MTime). The MTime is a unique metadata stamp that records the exact date and time the file was last modified on the source object. This precision ensures you block the recovery of the specific malicious content that existed at that exact point in time. + +The quarantine operation applies to that specific file version across all existing and future snapshots for that object, including any replica and archival copies. This is the recommended behavior, as the operation uses file version metadata to automatically apply the quarantine to all current and future snapshots. If the file is modified and its MTime changes, the new version is not covered by the original operation. + +Note: + +In some cases, if the file version information is unavailable, such as with older Threat Monitoring matches or a threat hunt performed on Rubrik clusters running a version earlier than 9.2.3, the system will fall back to a limited quarantine scope that only affects the specific snapshots where the match was detected. To initiate the recommended full-scope quarantine for such a file, run a new threat hunt on the object to ensure the necessary file version metadata is populated, and then quarantine the file again. + +## Quarantine processing and recovery restrictions + +It is important to understand the following concepts regarding the quarantine mechanism and their impact on recovery: + + * Quarantine scope: Quarantining a file implicitly quarantines the file path and the snapshot. The operation applies to all snapshots, including future snapshots of the object that contain the relevant file path and version. + * Quarantine processing: When an object has active quarantine operations, RSC processes every snapshot to determine if the relevant file version exists. Until this process is complete, the snapshot is marked as Quarantine processing. Recovery is automatically blocked for any snapshot in this state. + +Snapshots are marked as Quarantine processing in two primary cases: + + * When a new snapshot first arrives at RSC, if the associated object has any active quarantine operations. Processing of the new snapshot usually completes in seconds to minutes, but can take up to 30 minutes in certain conditions. + * When a new quarantine operation or a remove from quarantine operation is applied to the object. All snapshots are temporarily reset to the Quarantine processing status and reprocessed. Processing of all affected snapshots usually completes in seconds to minutes, but can take up to 30 minutes in certain conditions. + +Recovery block: Quarantining a file or object blocks all image-level recovery options for the affected snapshot, including Live Mount, Export, and Instant Recovery. The following exceptions apply: + + * Exception for forensics: The quarantined data remains accessible for security operations only by using the password-protected Download for Forensics feature. + * RBAC override: This recovery block is automatically bypassed for users who have the Recover From Quarantine RBAC permission. + +## Supported workloads + +RSC supports quarantining on the following objects: + + * VMware virtual machines + * Linux filesets + * Windows filesets + * Nutanix AHV virtual machines + * Hyper-V virtual machines + * Volume groups + * NAS filesets + * Kubernetes virtual machines + * Kubernetes protection sets + +Using the Quarantine feature requires access to the Data Protection dashboard, the Data Threat Analytics dashboard, and either the threat hunt or Threat Monitoring feature. For detailed instructions on how to configure user permissions, refer to the [RBAC Permissions for Quarantine](rbac_permissions_for_quarantine.html "RBAC privileges are required to remove files or objects from quarantine, bypass quarantine, and download files for forensic analysis.") topic. diff --git a/saas_quarantining_matched_objects_or_files.md b/saas_quarantining_matched_objects_or_files.md new file mode 100644 index 0000000000000000000000000000000000000000..273e85b40fda5ac0a2b1412113fc0fd7bde52334 --- /dev/null +++ b/saas_quarantining_matched_objects_or_files.md @@ -0,0 +1,46 @@ +# Quarantining matched files or objects + +Source: https://docs.rubrik.com/en-us/saas/saas/quarantining_matched_objects_or_files.html + +--- + +# Quarantining matched files or objects + +Quarantine a matched file or object indicated in a threat hunt to separate potentially malicious objects or files before proceeding with recovery. + +## Before you begin + +Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click the threat hunt of interest. + +Quarantined objects are listed with details of their location, files matched, and match type. + + 5. **Optional:** Click an object to view the files in that object. + 6. Select items at the object or file level and click Quarantine. + +Matched files are quarantined only on the snapshots where they were matched in the threat hunt and cannot be recovered. When the file exists in a previous or later snapshot, it might still be recoverable. + +Quarantining a file implicitly quarantines the snapshot. Snapshots with a matched file have limited recovery options unless they are removed from quarantine. + +The Quarantine Objects wizard shows the files selected for quarantine. + + 7. In the Quarantine Objects wizard, click Quarantine. + +When the total request size exceeds the limit, you can make further selections on a subsequent request. + +## Results + +RSC quarantines the file and provides no recovery options in any quarantined snapshot until the file is removed from quarantine. Users with the Recover From Quarantine permission can still download the file for forensics or perform image-level recovery options for the snapshot. + *[ > ]: and then diff --git a/saas_rbac_nascd.md b/saas_rbac_nascd.md new file mode 100644 index 0000000000000000000000000000000000000000..0e35978837699f6cd64efb06355f8383a524076e --- /dev/null +++ b/saas_rbac_nascd.md @@ -0,0 +1,31 @@ +# RBAC for NAS CD + +Source: https://docs.rubrik.com/en-us/saas/saas/rbac_nascd.html + +--- + +# RBAC for NAS CD + +You can use role based access control for users to assign a role containing a set of permissions to aNAS CD user. You can also assign multiple roles to a user. + +RSC provides predefined roles and options to create custom roles for a user. With Role Based Access Control (RBAC) for NAS CD data sets, you can create user roles with appropriate permissions to perform specific actions in RSC. You can then assign the roles to a user. + +Configuring Data Management Privileges by object type or by cluster can restrict user operations. You can provide permissions to operate specific NAS CD objects and perform specific actions in RSC. + +When you create a custom role based on NAS CD object type, you can specify the following permissions: + + * View and recover specific NAS CD objects + * Recover NAS CD objects to specific targets + +When you create a custom role based on NAS CD cluster type, you can specify the clusters and set up data management privileges for the selected clusters. + +Adding and managing organizations makes it possible for NAS CD users to create logical isolation of the shared objects and network resources in such a way that each organization member can see and access only data that belongs to that organization, especially for shared infrastructure platforms. + +A global administrator user can add a tenant organization. When you add a tenant organization for NAS CD data sets, you can assign users to the organization and make at least one user an organization administrator. With the required permissions, the organization administrator can access the NAS CD UI to add and manage systems. Those added systems are shown on the RSC Inventory page after the global administrator edits the NAS CD organization to add the systems for the organization administrator user. A non-administrator user in an organization can only view the systems, but cannot access the NAS CD UI. + +A user can access the NAS CD UI only if one of the following conditions is met: + + * User is an organization administrator with Federated access permission. + * User is assigned a user role with Federated access, View cluster, and Data Source Management permission. + + *[ > ]: and then diff --git a/saas_rbac_orchestrated_recovery.md b/saas_rbac_orchestrated_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..2aac0f8f1d02bc652e78ec08fe31f7f4e0241a29 --- /dev/null +++ b/saas_rbac_orchestrated_recovery.md @@ -0,0 +1,45 @@ +# RBAC for Orchestrated Application Recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/rbac_orchestrated_recovery.html + +--- + +# RBAC for Orchestrated Application Recovery + +Viewing and managing Recovery Plans and recoveries in Orchestrated Recovery require RBAC privileges. + +User-account access in Orchestrated Recovery is limited by the level of RBAC privileges. + +RBAC privileges that affect user-account access in Orchestrated Recovery are of the following types: + + * Object-level view, recovery target, and recovery permissions on the virtual machines, which determine whether a user can view and recover a virtual machine. Recovery permissions on vSphere virtual machines include the Mount snapshot, Export files, Export snapshots, and Restore over origin permissions. + * Application-level permissions for Orchestrated Recovery, which determine whether a user can view and manage recoveries and Recovery Plans. + +You can assign permissions when you create a role. By default, RSC assigns complete permissions to the owner, administrator, and backup administrator roles. The auditor role has the view permission by default. Details about the RBAC permissions in Orchestrated Recovery are as follows: + +Permission | Description +---|--- +View Orchestrated Recovery application | + + * Provides user account permissions to view the Orchestrated Recovery tile from the menu and the Orchestrated Recovery pages, objects with view permissions, Recovery Plans, recoveries, and events.Object-level permissions limit view access to objects, Recovery Plans, the Recovery Plan details page, recoveries, and events for these objects. The user account must have the view permission on all the objects in the Recovery Plan, including the virtual machines and the recovery target, to access the Recovery Plan details page and events.If a user account does not have view access to any object in the Recovery Plan, the user account cannot view the Recovery Plan, the Recovery Plan details page, recoveries, and events. For Azure virtual machines, the user requires view access to the subscription. + * Provides user accounts with access to download reports.The user account must have the view permission on all the objects in the Recovery Plan to download the recovery report.If a user account does not have access to any object in the Recovery Plan, the user account cannot download the Recovery Plan report. + + +Manage Recovery Plans in Orchestrated Recovery | Provides user accounts permissions for the following Recovery Plan actions: + + * Create Recovery Plan + * Edit Recovery Plan + * Delete Recovery Plan + * Schedule Recovery Plans. The Manage Recoveries permission is also required to schedule recoveries. + +The user account must have object-level permissions for all the objects on the Recovery Plan to create, edit, and delete the Recovery Plan.If the user account does not have access to any object in the Recovery Plan, the actions to manage Recovery Plans will not be available.This permission does not enable actions related to recoveries. +Manage Recoveries in Orchestrated Recovery | Provides user accounts permissions for all recovery actions for all recovery types. The user account can perform the following actions: + + * Start a cyber recovery. + * Start a recovery by using a Recovery Plan. + * View recovery details. + * Schedule recoveries. The Manage Recovery Plans permission is also required to schedule recoveries. + * Perform recovery-related operations, such as cleanup or resume recovery.When cleaning up a recovery, Orchestrated Recovery deletes the recovered virtual machines after a test failover or cyber recovery.If you select the Pause and resume manually after assessing the error option for Error Handling for VM Recovery when initiating a recovery ,Orchestrated Recovery pauses the recovery in case of any errors. + * Lock recoveries.Locking a cyber recovery ensures that the recovered virtual machines cannot be deleted by Rubrik in future Orchestrated Recovery operations. This is a permanent operation. + +The user account must have object-level permissions for all objects on the recovery to manage recovery-related actions.If a user account does not have access to any object in the Recovery Plan, the actions to manage the recovery will not be available.This permission does not enable actions related to Recovery Plans. diff --git a/saas_rbac_permissions_for_quarantine.md b/saas_rbac_permissions_for_quarantine.md new file mode 100644 index 0000000000000000000000000000000000000000..554aa44885622c6f2586830cdee5d979f8588e14 --- /dev/null +++ b/saas_rbac_permissions_for_quarantine.md @@ -0,0 +1,29 @@ +# RBAC privileges for quarantine + +Source: https://docs.rubrik.com/en-us/saas/saas/rbac_permissions_for_quarantine.html + +--- + +# RBAC privileges for quarantine + +RBAC privileges are required to remove files or objects from quarantine, bypass quarantine, and download files for forensic analysis. + +All Data Threat Analytics users can view quarantined objects and files. Additional threat containment privileges are required to: + + * Add files to quarantine and remove files from quarantine + * Bypass quarantine and continue with recovery, and download for forensics + +You can assign additional threat containment privileges from the Users and Roles page. The administrator and owner roles are assigned these privileges by default. You can also assign these additional privileges to custom roles. + +Privilege | Description +---|--- +Add files to quarantine and remove files from quarantine | Users with this privilege can add files to quarantine and remove files from quarantine. The administrator and owner roles are assigned this privilege by default and this privilege can also be assigned to custom roles. +Recover quarantined files and snapshots | Users with this privilege can bypass quarantine and perform most recoveries for: + + * Image-level recoveries such as Live Mount, Export, and Instant Recovery + * File-level recoveries from the Hunts page + +Users can only download quarantined files or folders containing quarantined files. Other file recovery options are not available for quarantined files. + +All users with permission to view a workload in the Data Protection room can view the snapshots quarantined for that workload, as well as the files quarantined in a particular snapshot, in the Data Protection object details page. + *[ > ]: and then diff --git a/saas_rbac_privileges_threat_hunt.md b/saas_rbac_privileges_threat_hunt.md new file mode 100644 index 0000000000000000000000000000000000000000..a5ad47edab78565c2d7c25a622fa61055dd9197b --- /dev/null +++ b/saas_rbac_privileges_threat_hunt.md @@ -0,0 +1,18 @@ +# RBAC privileges for threat hunt + +Source: https://docs.rubrik.com/en-us/saas/saas/rbac_privileges_threat_hunt.html + +--- + +# RBAC privileges for threat hunt + +RBAC privileges are required to create a threat hunt and view threat hunt results. + +Threat hunt view privileges enable users to view the Threat Hunt tab in Data Threat Analytics and see threat hunt results. Threat hunt create privileges enable users to create a threat hunt to scan Rubrik backups for indicators of compromise. Users without the appropriate RBAC privileges cannot view the Threat Hunt tab or create a threat hunt. + +The administrator and owner roles are assigned RBAC privileges to create a threat hunt and view threat hunt results by default. These privileges can also be assigned to custom roles from the Users and Roles page in the web UI. + +Note: + +Threat hunt privileges are required to access quarantine capabilities in Data Threat Analytics. + *[ > ]: and then diff --git a/saas_rbac_troubleshooting_permissions.md b/saas_rbac_troubleshooting_permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..5bf45fd7892518da12d90ac4e800fea9efe8b3be --- /dev/null +++ b/saas_rbac_troubleshooting_permissions.md @@ -0,0 +1,20 @@ +# Troubleshooting permissions + +Source: https://docs.rubrik.com/en-us/saas/saas/rbac_troubleshooting_permissions.html + +--- + +# Troubleshooting permissions + +Information about how you can troubleshoot permission issues when a user or service account cannot perform an intended task. + +Failures, such as an API returning a 403 Forbidden error, typically relate to a missing privilege in the assigned role or an incorrect scope for that privilege. In many cases, the API response provides specific details about the missing permissions. + +When troubleshooting, you can investigate the following areas: + + * Verifying role assignment: You can confirm that the user or service account has been assigned one or more roles. If no roles are assigned, the user has no permissions. + * Inspecting role privileges: You can review the assigned roles to determine if they contain the specific privileges required for the failed action, such as the Export Files privilege for an out-of-place restore. You can view the permissions associated with a role from the Roles page in RSC. If the privilege is missing, you can edit the role to add it. + * Checking privilege scope: You can verify that the privilege applies to the correct object. A role may grant Manage Protection, but the scope may be limited to a specific object type or Rubrik cluster. You can adjust the role configuration if the scope is incorrect. + * Examining audit logs: For detailed information, you can view the Audit Logs and filter events by the user or service account that experienced the failure. The log entry for the failed action specifies the missing permission, which provides definitive confirmation of the issue. + + *[ > ]: and then diff --git a/saas_rbk_cdm_soft_upgrade_rsc.md b/saas_rbk_cdm_soft_upgrade_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..453e93bf78dfe92a2a57110782e07525631a3ba6 --- /dev/null +++ b/saas_rbk_cdm_soft_upgrade_rsc.md @@ -0,0 +1,20 @@ +# Rubrik CDM software upgrade using RSC + +Source: https://docs.rubrik.com/en-us/saas/saas/rbk_cdm_soft_upgrade_rsc.html + +--- + +# Rubrik CDM software upgrade using RSC + +To take advantage of the latest features and improvements that Rubrik offers, you can upgrade the Rubrik CDM version running on any connected Rubrik cluster to the latest version using RSC. + +After you have reviewed the most recent versions of Rubrik CDM software and determined that upgrading to the latest version is the best course of action, you can initiate the upgrade procedure through RSC. + +Logging into an RSC account with the corresponding privileges provides view and upgrade options for Rubrik clusters. An upgrade of the Rubrik CDM software version is available only for Rubrik clusters running Rubrik CDM version 5.3 or later. + +Performing Rubrik CDM software upgrade involves: + + * Downloading the Rubrik CDM software upgrade package + * Upgrading the Rubrik cluster + + *[ > ]: and then diff --git a/saas_rbk_cdm_software_upgrade.md b/saas_rbk_cdm_software_upgrade.md new file mode 100644 index 0000000000000000000000000000000000000000..125832bab489e1cc7f1d0c3a4c0f5ce3f5de7631 --- /dev/null +++ b/saas_rbk_cdm_software_upgrade.md @@ -0,0 +1,36 @@ +# Rubrik CDM software upgrade + +Source: https://docs.rubrik.com/en-us/saas/saas/rbk_cdm_software_upgrade.html + +--- + +# Rubrik CDM software upgrade + +To take advantage of the latest features and improvements, you can upgrade your Rubrik CDM software running on your Rubrik clusters to the latest version. + +An upgrade is an operation for updating an older software version to a newer version, representing significant changes or improvements. Rubrik CDM software upgrades offer considerable changes and new functionality over previous versions, effectively superseding them. + +Some key advantages of upgrading your Rubrik CDM software to the latest version are as follows: + + * Maintaining business continuity and preventing unnecessary failures. + * Benefiting from essential security updates, new features, and integration with current technology trends and advancements, giving your business a competitive advantage. + * Safeguarding your systems and applications from viruses, spyware, and other malicious software that can harm or steal data or cause lengthy delays in problem resolution. + * Enhancing the quality of user experiences. + +If you are considering upgrading your Rubrik CDM software, Rubrik recommends that you evaluate the latest version available. Rubrik maintains a comprehensive Compatibility Matrix document that outlines which systems, protocols, and interfaces are supported for each product release. You can also check the Release Notes for the latest CDM software version to learn about new features, enhancements, and resolved issues. This way, you can ensure you are making the best choice for your needs. + +Rubrik follows the N-2 lifecycle policy, which supports the three most recent major releases (N, N-1, and N-2) of Rubrik CDM software. Each major release comes with a minimum support duration of 18 months. The Rubrik CDM Software Support Lifecycle documentation provides more information about the lifecycle policy. + +The Rubrik CDM Upgrades page provides all the information you need to make an informed decision about upgrading the CDM software. Some critical pieces of information you can gather include: + + * Checking the installed CDM software versions for your Rubrik clusters. + * Opening the Rubrik CDM Releases table to view details about the major release, its release notes, release adoption, release dates, latest minor release, Rubrik CDM software support policy, and Compatibility Matrix documentation. + +After you have decided to upgrade the Rubrik CDM software, you need to consider: + + * Choosing between a rolling upgrade and a fast upgrade. + * Reviewing the list of prerequisites and prechecks for your chosen upgrade type and ensuring you fulfill them for a successful upgrade. + * Selecting RSC or Rubrik CLI to perform the upgrade. + +Rubrik does not support using CLI commands to upgrade Rubrik clusters to the Rubrik CDM software version 9.0 or later. + diff --git a/saas_rcv_allowlist_azure.md b/saas_rcv_allowlist_azure.md new file mode 100644 index 0000000000000000000000000000000000000000..3551f267899c83455d03d985bec10a614107835f --- /dev/null +++ b/saas_rcv_allowlist_azure.md @@ -0,0 +1,31 @@ +# Allowlist for RCV on Azure + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_allowlist_azure.html + +--- + +# Allowlist for RCV on Azure + +To optimize network traffic restrictions to trusted Rubrik Cloud Vault location endpoints, you can allowlist a customer-specific endpoint for your Rubrik Cloud Vault locations. + +You can allowlist a customer-specific endpoint for Rubrik Cloud Vault (RCV) locations to restrict network traffic to trusted RCV location endpoints. This feature addresses security requirements for organizations that need to block traffic from untrusted endpoints. This customer-specific endpoint is specific to an RSC account and is available on the Rubrik Cloud Vaults page. + +The syntax for customer-specific endpoint is `<10-char-cust-id>*.blob.core.windows.net`. + +## Benefits + +When you create an RCV location on Azure, RSC automatically creates an Azure storage account. To restrict network traffic to trusted RCV location endpoints, you need to add a customer-specific endpoint to the allowlist for the storage account. By allowlisting this customer-specific endpoint, the rule applies to all storage accounts, eliminating the need to add the endpoint separately for each Azure storage account associated with your RCV location. This approach also removes the need to manually update the allowlist when provisioning new storage accounts. + +## Note on RCV locations created before April 2025 + +For the RCV locations that you created before April 2025, the customer-specific prefix is not available for the RSC account. In such cases, you must allowlist the location specific endpoints, such as `.blob.core.windows.net` in the network. + +## Additional network requirements + +Along with the storage account endpoints, RSC requires you to open an outbound connection through port 443 for the Rubrik clusters to access the following endpoints: + + * management.azure.com + * management.core.windows.net + * login.microsoftonline.com + + *[ > ]: and then diff --git a/saas_rcv_aws_config.md b/saas_rcv_aws_config.md new file mode 100644 index 0000000000000000000000000000000000000000..a807befe6113d2a1a6332b7b4db3a3d4c6070cbc --- /dev/null +++ b/saas_rcv_aws_config.md @@ -0,0 +1,14 @@ +# Configuration of RCV on AWS + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_aws_config.html + +--- + +# Configuration of RCV on AWS + +Information about configuring Rubrik Cloud Vault locations on AWS. + +After evaluating the different configuration options, you can start creating the Rubrik Cloud Vault (RCV) locations. You can create an RCV location in AWS on clusters running Rubrik CDM version 9.3.1 or later. RCV location hosted on AWS leverages the scalable infrastructure of Amazon S3 for secure and resilient data protection. You can configure the RCV location for data center, cloud-native, and NAS CD workloads. + +RCV locations hosted on AWS support single zone and multi-zone redundancy options, providing multiple levels of data protection to ensure your data remains secure and durable. + *[ > ]: and then diff --git a/saas_rcv_azure_config.md b/saas_rcv_azure_config.md new file mode 100644 index 0000000000000000000000000000000000000000..c1bb8c12bf0c4ea03802786b309dcebfd68f1c07 --- /dev/null +++ b/saas_rcv_azure_config.md @@ -0,0 +1,14 @@ +# Configuration of RCV on Azure + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_azure_config.html + +--- + +# Configuration of RCV on Azure + +Information about configuring Rubrik Cloud Vault locations on Azure. + +After evaluating the different configuration options, you can start creating the Rubrik Cloud Vault (RCV) locations. RCV locations hosted on Azure utilizes Microsoft Azure Blob Storage to offer a secure and scalable storage solution. You can configure the RCV location for data center, cloud-native, and NAS CD workloads. + +RCV locations hosted on Azure support various redundancy options, such as Single Zone, Multi Zone, and Multi Region, providing multiple levels of data protection to ensure your data remains secure and durable. + *[ > ]: and then diff --git a/saas_rcv_best_practices.md b/saas_rcv_best_practices.md new file mode 100644 index 0000000000000000000000000000000000000000..82e24f4bc5f6f7d2138f3cec0739a4ed0767752d --- /dev/null +++ b/saas_rcv_best_practices.md @@ -0,0 +1,50 @@ +# Rubrik Cloud Vault best practices + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_best_practices.html + +--- + +# Rubrik Cloud Vault best practices + +Information about the Rubrik Cloud Vault best practices, which aim to optimize data protection and compliance. + +Rubrik Cloud Vault (RCV) offers two distinct storage tiers, the Backup tier and the Archive tier, each designed for specific data retention and recovery scenarios. To optimize the data protection strategy and ensure compliance with organizational requirements, it is important to understand and follow the best practices for using each tier effectively. + +## Backup tier + +The Backup tier in RCV offers a minimum retention period of 30 days, providing instant access to data for immediate recovery needs. + +Rubrik recommends that you adhere to the following guidelines regarding the Backup tier: + + * Use for SLA Domains with shorter backup frequencies, meant for disaster and cyber recovery, to help meet your Recovery Time Objectives (RTOs). + * For RCV on Azure, AWS, and GCP, use with Multi-zone Redundancy for scenarios that require high availability or when restricting data replication to a particular region to meet data governance requirements, as recommended by Microsoft. + * For RCV on Azure, use with Multi-region Redundancy to protect against regional failures and to meet compliance requirements of storing backups in two regions. + * Do not use for SLA Domains with long-term frequencies, such as weekly, monthly, or yearly retention periods. + +## Archive tier + +For RCV locations on Azure and AWS, the Archive tier offers a minimum retention period of 180 days to access data, making it suitable for long-term data retention and compliance purposes. For RCV locations on GCP, the Archive tier offers a minimum retention period of 365 days. + +Rubrik recommends that you adhere to the following guidelines regarding the Archive tier: + + * Use for SLA Domains with longer frequencies, such as weekly, monthly, or yearly. + * When planning for data recovery, factor in that the Archive tier may take several hours up to a few days for the data to become accessible. + * Do not use for SLA Domains with short-term frequencies, such as those requiring a daily retention period, or for backups needed for disaster and cyber recovery. + +This is because instant data access is not available, recovery can take several hours up to a few days, and backups must be retained for a minimum of 180 days. + + * Do not rely solely on the Archive tier as a Business Continuity and Disaster Recovery (BCDR) solution. The Archive tier in RCV may take several hours up to a few days to recover your data. Although the Backup tier provides immediate access to downloaded data, site recovery from the Archive tier in RCV can be prolonged and may exceed the RTO. + +## General recommendations + +To ensure optimal use of RCV and maximize storage efficiency and security, Rubrik recommends that you adhere to the following guidelines: + + * Do not store backups with different backup frequencies in the same archival location. This prevents inefficient storage use and increased costs. Rubrik recommends archiving short-term backups to the RCV Backup tier and long-term backups to the RCV Archive tier to optimize storage consumption. + +Note: + +Recovery from the RCV Archive tier may take several hours up to a few days in Azure and AWS RCV locations. However, for RCV locations on GCP, no additional time is required to restore the data from the Archive tier. + + * Ensure Rubrik clusters are running Rubrik CDM version 9.1 or later to leverage blob-level immutability for the most efficient use of the storage capacity. This makes your SLA Domain design both efficient and secure by taking advantage of the latest features. + + *[ > ]: and then diff --git a/saas_rcv_converting_redundancy.md b/saas_rcv_converting_redundancy.md new file mode 100644 index 0000000000000000000000000000000000000000..12fc2f028959411d82ace40b3eef7c727463cedd --- /dev/null +++ b/saas_rcv_converting_redundancy.md @@ -0,0 +1,65 @@ +# Converting RCV redundancy + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_converting_redundancy.html + +--- + +# Converting RCV redundancy + +Convert the storage redundancy of an existing RCV on Azure location to meet security or compliance requirements. + +## Before you begin + +Ensure that you have the appropriate Rubrik Cloud Vault (RCV) entitlement capacity for the new redundancy option for the data you are converting. If you have insufficient entitlement, contact the Rubrik accounts team. + +## About this task + +You can change the redundancy for RCV locations hosted on Azure. For cloud native RCV locations, you can change the redundancy option at both parent and child level. Changing RCV redundancy is an asynchronous process, and the total time to completion depends on the amount of data and the type of conversion. During conversion, regular backup and recovery operations are not interrupted. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Infrastructure > Rubrik Cloud Vault. + +The Rubrik Cloud Vault dashboard appears. + + 4. Click RCV Locations. + +A list of RCV locations appears. + + 5. Click for the Azure RCV location you want to modify, and select Edit Rubrik Cloud Vault. + +If you are editing a cloud native location, you can choose a specific child location or the parent location for bulk updates. For cloud native locations of type specific region, RSC directly applies the update to the parent location and updates the redundancy only after the child vault is converted to the new redundancy type. + +The Edit Rubrik Cloud Vault wizard appears. + + 6. In the Redundancy dropdown, select the desired redundancy type. + 7. For cloud native RCV locations containing child locations, select how the child objects should inherit redundancy from the parent RCV location. + +Option| Description +---|--- +Future child RCV locations only | Applies the redundancy change to future child RCV locations only. +All existing and future child RCV locations | Applies the redundancy change to all existing and future child RCV locations.To convert the existing child RCV locations, they must have the same redundancy as the parent location. If a child location region is not supported in the target redundancy type, RSC cannot convert that location, but it converts the remaining locations. + + 8. Click Next. + +The Confirmation page appears. + + 9. In the Redundancy Conversion Summary section, review the following information: + + * Estimated required capacity + * Estimated remaining capacity after the conversion + * Estimated time to start the conversion + + 10. Click Save. + +A message appears confirming that the conversion is preparing to start. + +## Results + +The conversion process starts. You can monitor the status of the conversion on the Events page. You can also check the Redundancy column on the Rubrik Cloud Vaults page. The RCV location redundancy is updated after the conversion process successfully completes. + *[ > ]: and then diff --git a/saas_rcv_dashboard.md b/saas_rcv_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..e35c7c81d20be529f3f78ba17df8b4163a9be841 --- /dev/null +++ b/saas_rcv_dashboard.md @@ -0,0 +1,22 @@ +# Rubrik Cloud Vault dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_dashboard.html + +--- + +# Rubrik Cloud Vault dashboard + +The Rubrik Cloud Vault dashboard in RSC displays the data protection and usage summary of all the Rubrik Cloud Vault locations connected to RSC. + +When you use Rubrik Cloud Vault (RCV) to secure your backups, the RCV dashboard in RSC displays detailed information about the data protection tasks and the storage usage for all the RCV locations. + +On the RCV dashboard, you can view the following details, which are gathered from the RCV locations: + + * The status of the RCV for data center workloads only + * The number of objects protected by the RCV locations + * The amount of immutable and non-immutable data available in the Backup and Archive tiers of the RCV locations + * The amount of storage purchased, used, and allocated across redundancy levels based on your RCV entitlements + * The total storage capacity consumed over a period of 90 days + * The number of backup tasks completed and the tasks running on all the RCV locations + + *[ > ]: and then diff --git a/saas_rcv_failover_azure.md b/saas_rcv_failover_azure.md new file mode 100644 index 0000000000000000000000000000000000000000..a19a00453a0f28d6fe6d09f4870d781f64555c7e --- /dev/null +++ b/saas_rcv_failover_azure.md @@ -0,0 +1,49 @@ +# Failover for RCV on Azure + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_failover_azure.html + +--- + +# Failover for RCV on Azure + +The failover process for Rubrik Cloud Vault ensures continuous data availability during regional outages and disasters by switching between primary and secondary regions configured with Multi-region redundancy. + +Failover is the process of transitioning data recovery operations from a primary region to a secondary region when a failure or disaster occurs. For Rubrik Cloud Vault (RCV) locations configured with Multi-region redundancy, failover ensures continued access to data by designating the secondary region as the new recovery point. This process supports only recovery operations. Resuming backup operations requires that you perform a failback after the primary region is back online and available. + +Note: + +Rubrik recommends performing a failover only when the primary region is unavailable, because there might be a risk of data loss if the failover is not performed correctly. Additionally, you must ensure that your users and applications can access the secondary region if a failover is performed. If a regional outage occurs, Microsoft automatically performs the failover to ensure data availability. + +## Important terms + +The following are the important terms related to regions in a failover process: + + * Primary region: The original region where data operations and backups occur before a failover. + * Secondary region: The region that becomes active in a failover scenario. + +## Failover types and quorum authorization + +RCV supports the following failover types in a Multi-region redundancy environment: + + * Microsoft-initiated failover: Azure automatically initiates a failover when it detects a catastrophic failure in the primary region. + * Customer-initiated failover: You can manually initiate a failover to the secondary region as part of disaster recovery. + +Before initiating a failover, you must configure quorum authorization, a security measure that requires multiple approvers to authorize a failover action. This configuration helps prevent unauthorized or potentially malicious users from initiating a failover that may lead to data loss. Quorum authorization is particularly crucial for customer-initiated failovers because the actions such as switching operational control to the secondary region and subsequently back to the primary region are often high-risk. + +## Conditions for safe failover + +You need to initiate failover only when certain conditions are met to prevent data loss or inconsistency. Azure geo-replication between primary and secondary regions occurs asynchronously, that is, data is not always immediately synchronized between regions. A safe failover requires that the following criteria are met: + + * No ongoing data or state changes: Confirming that no data or state change activity is occurring on the RCV location in the primary region is crucial. This prevents the loss of data that has not been copied to the secondary location when the failover process is initiated, as failover is only allowed when the primary region is disabled. + * Last redundancy sync time: Indicating the most recent point at which data is guaranteed to have been replicated, the last sync time helps assess potential data loss during failover. You must verify the last sync time to ensure that all data from the primary region has been replicated to the secondary region. Any new data uploaded to the primary region after the last redundancy sync time is not copied to the secondary region and is lost during failover. + +## Post-failover operations and monitoring + +After a failover is completed, the secondary region becomes the primary region, which operates in single zone. Rubrik automatically re-establishes Multi-region redundancy after the paired region becomes available. Single zone stores multiple copies of data within a single data center in the secondary region. While this provides protection against hardware failures, it does not offer the same level of redundancy as Multi-region redundancy. + +The new failover primary region supports recovery operations. To resume backup operations, Rubrik requires you to perform a failback after the paired region becomes available, Multi-region redundancy has been re-established, and all data has been copied over. + +You can monitor the progress of the failover task on the Rubrik Cloud Vaults page and view the status in the Notifications tab under . The failover operation is considered complete when the RCV status in the Redundancy column changes to Failover complete. During a failover, you can recover backups from the failed-over RCV location, which remains in a disabled or paused status. To resume backup operations and return the RCV location to active status, you must perform a failback. + +Microsoft Azure documentation provides more information about failover. + *[ > ]: and then diff --git a/saas_rcv_gcp_config.md b/saas_rcv_gcp_config.md new file mode 100644 index 0000000000000000000000000000000000000000..064dbd7d671f50d727d3479dc684fb9da80ed4c9 --- /dev/null +++ b/saas_rcv_gcp_config.md @@ -0,0 +1,22 @@ +# Configuration of RCV on GCP + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_gcp_config.html + +--- + +# Configuration of RCV on GCP + +Information about configuring Rubrik Cloud Vault locations on GCP. + +After evaluating the different configuration options, you can start creating the Rubrik Cloud Vault (RCV) locations. This secures your GCP workloads with an air-gapped, immutable copy of your data for enhanced cyber resilience. You can configure the RCV location only for cloud-native workloads. + +RCV locations hosted on GCP support multi-zone redundancy option, providing multiple levels of data protection to ensure your data remains secure and durable. + +Note: + +You cannot configure RCV locations on GCP for the following workloads: + + * Workloads protected using a Rubrik cluster on-premise or in the cloud + * NAS CD workloads + + *[ > ]: and then diff --git a/saas_rcv_location_management.md b/saas_rcv_location_management.md new file mode 100644 index 0000000000000000000000000000000000000000..7a09a4d5ed3d1ad26164b9fdc3e6ce337c8cff7e --- /dev/null +++ b/saas_rcv_location_management.md @@ -0,0 +1,19 @@ +# Rubrik Cloud Vault location management + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_location_management.html + +--- + +# Rubrik Cloud Vault location management + +RSC provides actions to manage the Rubrik Cloud Vault locations. + +You can perform the following actions to manage the Rubrik Cloud Vault (RCV) locations: + + * Edit + * Pause or resume + * Disable or enable + * Delete + +The Delete action works only on locations that are not being used for archiving by any Rubrik cluster and that have archiving disabled. + *[ > ]: and then diff --git a/saas_rcv_notifications.md b/saas_rcv_notifications.md new file mode 100644 index 0000000000000000000000000000000000000000..d32fa66d74239b818b186e5079271ab92c795968 --- /dev/null +++ b/saas_rcv_notifications.md @@ -0,0 +1,32 @@ +# Rubrik Cloud Vault Notifications + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_notifications.html + +--- + +# Rubrik Cloud Vault Notifications + +Rubrik sends notifications to keep you informed about your storage capacity usage and subscription status of your RCV locations. These notifications ensures that you can take timely actions to maintain service availability and data protection. + +Rubrik notifies you about your storage capacity usage and the subscription status of your RCV locations. When you receive these notifications, you must plan to renew your Rubrik Cloud Vault (RCV) licenses or purchase additional storage to avoid backups from pausing. If you have already renewed your license, you can ignore the notifications. + +## Entitlement notifications + +The following table describes the different notifications that Rubrik sends to notify you about entitlement expiry. Entitlement status | Notification +---|--- +You purchase RCV storage | Rubrik sends an email notification with the details of the purchased storage capacity. +From 30 days before the expiry of the RCV subscription till the expiry date | Rubrik sends daily email notifications with a message that the archival locations will be paused on the expiration date if not renewed before then. +From the expiry date of the RCV subscription till 30 days | Rubrik pauses the RCV archival locations and sends daily email notifications to notify that Rubrik will delete the archival locations and the archived data if the subscription remains in the expired state 30 days past the expiration date. +From 31 days after expiry of the RCV subscription till 60 days | Rubrik removes access to the RCV archival locations and sends email notifications every two days to notify that Rubrik will delete the data in your archival locations if the subscription remains in the expired state 60 days past the expiration date. +After 60 days of expiry of the RCV subscription | Rubrik deletes the data in the archival locations and sends email notifications every two days for seven days to notify that the data has been deleted. + +## Storage capacity notifications + +The following table describes the notifications that Rubrik sends to notify you about storage consumption. Usage Status | Notification +---|--- +75% usage | Rubrik sends email notifications every 10 days. +80% usage | Rubrik sends email notifications every 10 days. +85% usage | Rubrik sends email notifications every three days. +90% usage | Rubrik sends daily email notifications with a warning message that the archival location will be paused if usage exceeds 100%. +100% or more usage | Rubrik pauses archiving to the locations in the storage tier that have exceeded the allocated capacity. + *[ > ]: and then diff --git a/saas_rcv_page.md b/saas_rcv_page.md new file mode 100644 index 0000000000000000000000000000000000000000..4fc2ec2a9c392af07bad78021ed00f6d6fa93c0e --- /dev/null +++ b/saas_rcv_page.md @@ -0,0 +1,18 @@ +# Rubrik Cloud Vaults page + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_page.html + +--- + +# Rubrik Cloud Vaults page + +The Rubrik Cloud Vaults page provides a list of all available archival locations and the actions that RSC supports for each location. + +The Rubrik Cloud Vaults page provides detailed information about Rubrik Cloud Vault (RCV) archival locations: + + * Displays RCV for data center environments, including Rubrik NAS Cloud Direct vaults and cloud environments, along with child locations in the same regions as their associated cloud-native workloads + * Provides management actions through the icon for each location + * Displays storage usage for each location classified by storage tier + * Provides filters to view locations by region, tier, status, cloud provider, and redundancy based on specified criteria + + *[ > ]: and then diff --git a/saas_rcv_prep_location_creation.md b/saas_rcv_prep_location_creation.md new file mode 100644 index 0000000000000000000000000000000000000000..643bbc8558dfe43ccc70bce1631a616c4fa2bff0 --- /dev/null +++ b/saas_rcv_prep_location_creation.md @@ -0,0 +1,12 @@ +# Preparation for RCV location creation + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_prep_location_creation.html + +--- + +# Preparation for RCV location creation + +Before utilizing Rubrik Cloud Vault, it is essential to understand the various options available for creating an RCV location, ensuring optimal data protection and recovery. + +RSC provides various options for creating Rubrik Cloud Vault (RCV) locations, each designed to meet different needs and operational scenarios. The preparation involves evaluating and selecting the most suitable configurations for hosting your RCV location. Additionally, it is also important to refer to the best practices from Rubrik for adding RCV locations. + *[ > ]: and then diff --git a/saas_rcv_rubrik_cloud_vault.md b/saas_rcv_rubrik_cloud_vault.md new file mode 100644 index 0000000000000000000000000000000000000000..150c2104650f8687cb9e604ea9ed81c5ad4b485a --- /dev/null +++ b/saas_rcv_rubrik_cloud_vault.md @@ -0,0 +1,43 @@ +# Rubrik Cloud Vault + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_rubrik_cloud_vault.html + +--- + +# Rubrik Cloud Vault + +Rubrik Cloud Vault is a Rubrik managed cloud service that provides isolated and immutable copies of protected data, enhancing cyber resiliency. + +In the current digital landscape, ensuring the security and resilience of data is a paramount concern for organizations. Traditional methods of storing data offsite, such as secondary data centers or public cloud storage, are no longer sufficient. This is mainly because of advanced cybersecurity threats, such as ransomware attacks. + +Rubrik Cloud Vault (RCV) is a fully managed service that offers immutable, air-gapped backups that are isolated from your primary data environment. This ensures that you have a reliable data recovery plan in the event of a cyber attack. RCV secures your data in a logically air-gapped vault without the need to deploy or manage any additional cloud resources. As a fully managed service, Rubrik takes on the responsibility for security, monitoring, and management of the cloud and security functions of RCV. This end-to-end management ensures that you can focus on your core business operations while Rubrik handles your data security needs. + +## RCV location creation + +You can create RCV locations to protect your on-premises, cloud-native, and unstructured data. You can create distinct RCV locations for your data center, NAS CD, and cloud-native workloads. RSC supports hosting of RCV locations in AWS, GCP, and Azure. + +Note: + +You can create RCV locations in GCP only for cloud-native workloads. + +## SLA Domain configuration + +After creating an RCV location, you can create an SLA Domain and configure archival or backup policies to use the RCV location. When you assign the SLA Domain to a workload, RSC starts archiving the snapshots to the RCV location based on the frequency specified in the SLA Domain. You can view detailed information about the data protection tasks and the storage usage for all the RCV locations on the RCV dashboard. + +You can use RCV for simplified recovery from operational, disaster, and cyber events. You can recover your data from the RCV location using different recovery options. The recovery time varies depending on the storage tier of the RCV location. + +## Key considerations for RCV + +Some key points to consider about RCV are as follows: + + * RCV does not support Archive Consolidation. + * RCV requires a Rubrik cluster running Rubrik CDM version 6.0.1 or later to archive data center workloads to an RCV storage location. + +## Egress costs + +The RCV service includes up to 10% of your total data in egress costs during each 12-month subscription period. This allowance ensures that you can manage your data efficiently within the provided limits. The percentage limit, however, does not apply in exceptional situations, such as the following: + + * Cybersecurity incidents, which require immediate response and recovery due to threats to information integrity, confidentiality, or availability + * Disaster recovery events, where the original infrastructure is inaccessible and recovery efforts are necessary + +In such situations, you can access and retrieve your data without restriction to ensure timely response and recovery. diff --git a/saas_rcv_security.md b/saas_rcv_security.md new file mode 100644 index 0000000000000000000000000000000000000000..08d5e87e8d27e5cbab133a6e89b5d0ed467de9fc --- /dev/null +++ b/saas_rcv_security.md @@ -0,0 +1,24 @@ +# Rubrik Cloud Vault security + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_security.html + +--- + +# Rubrik Cloud Vault security + +Rubrik Cloud Vault adheres to security standards for the protection of archived backups. + +Rubrik Cloud Vault (RCV) provides robust security measures to ensure data protection across different environments. + +## Data center workloads + +The Rubrik cluster encrypts the data for your data center workloads with AES-256 GCM before sending it to RCV. You can use an RSA key or a key from a customer-managed Azure Key Vault. If you use an RSA key, you need to store it securely for potential future recovery, as Rubrik does not store this key. + +## Cloud-native workloads + +In cloud-native environments, RCV uses Server Side Encryption (SSE) with platform-managed keys to encrypt your data. This method simplifies the key management as the cloud service provider manages the encryption keys. + +## NAS CD workloads + +NAS CD supports SSE with platform-managed keys to secure your data, ensuring data protection with minimal user intervention in key management. + *[ > ]: and then diff --git a/saas_rcv_storage_tiers.md b/saas_rcv_storage_tiers.md new file mode 100644 index 0000000000000000000000000000000000000000..8bb6105cc0d0dd915764c9271c6ee4caba9e5f63 --- /dev/null +++ b/saas_rcv_storage_tiers.md @@ -0,0 +1,35 @@ +# Rubrik Cloud Vault storage tiers + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_storage_tiers.html + +--- + +# Rubrik Cloud Vault storage tiers + +Information about Rubrik Cloud Vault storage tiers, which include backup and archive options, each with corresponding retention periods, access times, and immutability features to meet various data storage requirements. + +The following table describes the purpose of each storage tier. Attribute | Backup tier | Archive tier | Notes +---|---|---|--- +Required snapshot retention period | At least 30 days | + + * At least 180 days for RCV locations on Azure and AWS + * At least 365 days for RCV locations on GCP + +| Rubrik rejects the assignment of the Rubrik Cloud Vault (RCV) archival location to an SLA Domain if the archival parameters of the SLA Domain do not meet the snapshot retention requirements. Deleting an RCV archival location might result in some snapshots that do not meet retention requirements, leading to an early deletion penalty. Not renewing an RCV subscription might result in an RCV location storing snapshots that cannot meet the retention period, leading to an early deletion penalty. +Time to access archived snapshots | Immediately after snapshots are archived | Several hours up to a few days after snapshots are archived | NA +Blob-level immutability or object-level immutability | Yes (for the retention period of the snapshots) | Yes (for the retention period of the snapshots) | The following objects are protected in RCV with blob-level or object-level immutability enabled by default: + + * Data center objects protected in RCV locations created on Rubrik clusters running Rubrik CDM version 9.1 or later + * Cloud-native objects + * Rubrik NAS Cloud Direct objects + +For data center objects, blob-level immutability is available only for Rubrik clusters running Rubrik CDM version 9.1 or later. For Rubrik clusters running an earlier version, only container-level immutability is available for backup tier locations. +Container-level immutability or bucket-level immutability | Yes (for up to 150 days) | NA | Immutable storage in the RCV is automatically terminated at the end of your subscription period and is limited to a maximum of 150 days. This is applicable only to data center RCV locations on Azure. +Redundancy | For data center and cloud-native RCV locations on Azure, RSC supports the following redundancy options: + + * Single zone + * Multi-zone + * Multi-region + +For NAS CD RCV locations on Azure, RSC supports only Single zone redundancy. For RCV locations hosted on AWS, RSC supports Single zone and Multi-zone redundancy. For RCV locations hosted on GCP, redundancy is always Multi-zone. | Single zone for RCV locations on Azure.Multi-zone for RCV locations on AWS.For RCV locations hosted on GCP, redundancy is always Multi-zone. | NA + *[ > ]: and then diff --git a/saas_rcv_workloads_protection.md b/saas_rcv_workloads_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..087edcc1b52e3fff3fe9560f13473b6aa42d9bba --- /dev/null +++ b/saas_rcv_workloads_protection.md @@ -0,0 +1,14 @@ +# Protection of workloads in RCV + +Source: https://docs.rubrik.com/en-us/saas/saas/rcv_workloads_protection.html + +--- + +# Protection of workloads in RCV + +You can protect your workloads in the Rubrik Cloud Vault locations by assigning SLA Domains to your workloads. + +After creating a Rubrik Cloud Vault (RCV) location, you can assign it to an SLA Domain. When you assign the SLA domain to RSC workloads, RSC starts archiving the snapshots to the RCV location based on the policy in the specified SLA Domain. + +In the event of a cyber incident, this setup ensures that you can always access your data in RCV and recover a clean copy in an environment of your choice. This integration provides a strong strategy for data recovery, making sure your important data stays safe and accessible even during a cyber incident. + *[ > ]: and then diff --git a/saas_reconnecting_disconnected_cluster.md b/saas_reconnecting_disconnected_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..dffa40accfb9443b0405658da46ac3fe5d393295 --- /dev/null +++ b/saas_reconnecting_disconnected_cluster.md @@ -0,0 +1,37 @@ +# Reconnecting to a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/reconnecting_disconnected_cluster.html + +--- + +# Reconnecting to a Rubrik cluster + +Reestablish a secure connection with a Rubrik cluster. + +## About this task + +Network issues can result in the loss of the secure connection between RSC and a Rubrik cluster. When that happens RSC adds an alert icon next to the cluster. Use this task to reestablish the connection by sending a single-use token to the cluster. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Hover over the disconnected-cluster icon next to the cluster name. + +The Cluster Disconnected message box appears. + + 5. Click the link in the message box. + +The Cluster Connectivity modal appears. The modal describes how to reestablish the connection with the Rubrik cluster. + + 6. Perform the steps described in the reconnection instructions. + +## Results + +RSC reestablishes a secure connection with the Rubrik cluster and removes the alert. + +## What to do next + +If the connection cannot be reestablished, contact Rubrik Support. + *[ > ]: and then diff --git a/saas_recovering_files_from_a_snapmirror_cloud_snapshot.md b/saas_recovering_files_from_a_snapmirror_cloud_snapshot.md new file mode 100644 index 0000000000000000000000000000000000000000..2bdc4d3b346145a9a94f23b9dd7e72590c48acca --- /dev/null +++ b/saas_recovering_files_from_a_snapmirror_cloud_snapshot.md @@ -0,0 +1,53 @@ +# Recovering files from a SnapMirror Cloud snapshot + +Source: https://docs.rubrik.com/en-us/saas/saas/recovering_files_from_a_snapmirror_cloud_snapshot.html + +--- + +# Recovering files from a SnapMirror Cloud snapshot + +Recover a selected set of files on a SnapMirror Cloud archival location to a specified destination. + +## Procedure + + 1. Log in to RSC. + 2. Click Inventory. + +The Inventory page shows cards for each configured type of protectable object. + + 3. Click SnapMirror Cloud. + +A list of configured NetApp hosts appears. + + 4. Click the name of a listed NetApp host. + +A list of volumes on the NetApp host appears. + + 5. Click the name of a volume. + +The details page for the volume appears. + + 6. In the Snapshots calendar, click a date. + 7. Hover over the ellipsis menu for a listed snapshot and select Recover. + +The SnapMirror Recovery wizard appears. + + 8. Select Recover files and click Next. + +The wizard displays the file system for the volume. + + 9. Browse the file system, select the files to recover, and then click Next. + 10. Choose a recovery type. + +Choice| Action +---|--- +Overwrite original | Specify whether to continue after a recovery error. +Recover to separate folder | Enter the path to the folder where the files will be recovered and specify whether to continue the recovery after a recovery error. +Export | Select a NetApp host from the drop-down, enter a path where to recover the files, and enterpe a name for the volume where files are restored. + + 11. Click Recover. + +## Results + +RSC recovers the selected files. + *[ > ]: and then diff --git a/saas_recovering_from_smc_to_existing_volume.md b/saas_recovering_from_smc_to_existing_volume.md new file mode 100644 index 0000000000000000000000000000000000000000..e98a6056252569381dd72ceb55a160893e49e0c0 --- /dev/null +++ b/saas_recovering_from_smc_to_existing_volume.md @@ -0,0 +1,54 @@ +# Recovering a volume from a SnapMirror Cloud snapshot to an existing volume + +Source: https://docs.rubrik.com/en-us/saas/saas/recovering_from_smc_to_existing_volume.html + +--- + +# Recovering a volume from a SnapMirror Cloud snapshot to an existing volume + +Recover a volume from a snapshot to an existing empty volume. + +## Procedure + + 1. Log in to RSC. + 2. Click Inventory. + +The Inventory page shows cards for each configured type of protectable object. + + 3. Click SnapMirror Cloud. + +A list of configured NetApp hosts appears. + + 4. Click the name of a listed NetApp host. + +A list of volumes on the NetApp host appears. + + 5. Click the name of a volume. + +The details page for the volume appears. + + 6. In the Snapshots calendar, click a date. + 7. Hover over the ellipsis menu for a listed snapshot and select Recover. + +The SnapMirror Recovery wizard appears. + + 8. Select Recover volume to existing volume and click Next. + +The wizard displays a list of NetApp hosts. + + 9. Click the name of a listed NetApp host. + +The wizard displays a list of all the volumes on the selected NetApp host. + + 10. Select a volume to be the target for the recovery operation and click Next. + +Only empty volumes can be targets for recovery operations. + +The wizard advances to the confirmation step. + + 11. Click Recover. + +## Results + +RSC restores the content of the selected snapshot to the existing volume. The restored volume becomes read-write compatible. + *[ > ]: and then diff --git a/saas_recovering_from_smc_to_new_volume.md b/saas_recovering_from_smc_to_new_volume.md new file mode 100644 index 0000000000000000000000000000000000000000..8aa9677255d3bde298c860ab889b8bcc6f30095d --- /dev/null +++ b/saas_recovering_from_smc_to_new_volume.md @@ -0,0 +1,51 @@ +# Recovering a volume from a SnapMirror Cloud snapshot to a new volume + +Source: https://docs.rubrik.com/en-us/saas/saas/recovering_from_smc_to_new_volume.html + +--- + +# Recovering a volume from a SnapMirror Cloud snapshot to a new volume + +Recover a volume from a snapshot to a newly created volume on a NetApp host. + +## Procedure + + 1. Log in to RSC. + 2. Click Inventory. + +The Inventory page shows cards for each configured type of protectable object. + + 3. Click SnapMirror Cloud. + +A list of configured NetApp hosts appears. + + 4. Click the name of a listed NetApp host. + +A list of volumes on the NetApp host appears. + + 5. Click the name of a volume. + +The details page for the volume appears. + + 6. In the Snapshots calendar, click a date. + 7. Hover over the ellipsis menu for a listed snapshot and select Recover. + +The SnapMirror Recovery wizard appears. + + 8. Select Recover volume to new volume and click Next. + +The wizard displays a list of NetApp hosts. + + 9. Select a NetApp host. + 10. In Storage Virtual Machine, select a virtual machine. + 11. In NetApp Aggregate Name, enter a name. + 12. In NetApp Volume Name, enter a name for the recovered volume and then click Next. + +The wizard advances to the confirmation step. + + 13. Click Recover. + +## Results + +RSC recovers the selected volume to the newly created volume on the selected NetApp storage virtual machine. + *[ > ]: and then diff --git a/saas_recovering_vm_file_guest_os_creds.md b/saas_recovering_vm_file_guest_os_creds.md new file mode 100644 index 0000000000000000000000000000000000000000..ce34292b7a15a2a798edf251a497ed14bbb875ea --- /dev/null +++ b/saas_recovering_vm_file_guest_os_creds.md @@ -0,0 +1,77 @@ +# Recovering a virtual machine file using guest OS credentials + +Source: https://docs.rubrik.com/en-us/saas/saas/recovering_vm_file_guest_os_creds.html + +--- + +# Recovering a virtual machine file using guest OS credentials + +Recover a virtual machine file through VMware Tools using guest OS credentials. You can use guest OS credentials to recover files to guest operating systems that do not have the RBS installed. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC using the administrator account. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the vSphere VMs inventory card. + +The vSphere VMs page appears. + + 5. Click a virtual machine that has snapshots. + +The virtual machine object details page appears. + + 6. Click a date on the calendar to view the list of snapshots taken on that day. + 7. Open the ellipsis menu for the snapshot you want to use for recovery and select Recover. + +The Virtual Machine Recovery wizard appears. + + 8. Select Recover files and click Next. + +The Select folders or files page appears. + + 9. Select the files and click Next. + +The Select Recovery Type page appears. + + 10. Select one of the recovery options. + +Option| Description +---|--- +Overwrite original | Restores the selected file or folder to the original path. This option overwrites the existing file or folder at the original path. +Recover to separate folder | Restores the file or folder to a different location. +Export | Exports the files from the current virtual machine to another virtual machine. + +Note: + +To use guest OS credentials, use the recovery options Overwrite original, Recover to separate folder, and Export. Download is not applicable. + + 11. (Export) In VMs List, select a target virtual machine where you want to recover the selected file. + 12. (Recover to separate folder and Export) In Folder Path, enter the path of the folder where you want to recover the selected file. + 13. Select a VMware Tools restore method. + +Option| Description +---|--- +Use existing guest OS credentials | Uses the existing guest OS credentials to recover the selected files.Note: Using existing guest OS credentials require view guest OS credentials permission to view the existing guest OS credentials. +Add new guest OS credentials | Adds guest OS credentials to access the guest operating system. While adding guest OS credentials, the application prompts you to enter the following: + * Domain: The resolvable hostname or IP address of the authentication server for the credentials. Domain is an optional field. + * Description: The description for guest OS credentials.Note: Description is only available for Rubrik clusters running Rubrik CDM version 9.2 or later. + * Username and password: The login credentials for the account. +To store guest OS credentials for future use for all VMs requires Manage guest OS credentials permission.Selecting Continue on restore errors option continues recovery of other objects even if recovering an object in the recovery fails. + + 14. Click Recover. + +## Results + +RSC recovers the virtual machine files through VMware Tools using the guest OS credentials. + *[ > ]: and then diff --git a/saas_recovery_details.md b/saas_recovery_details.md new file mode 100644 index 0000000000000000000000000000000000000000..4f24a517da4389e3d33932ed0fce19021765a7c0 --- /dev/null +++ b/saas_recovery_details.md @@ -0,0 +1,45 @@ +# Recovery details + +Source: https://docs.rubrik.com/en-us/saas/saas/recovery_details.html + +--- + +# Recovery details + +The recovery details page provides specific details about the selected recovery. + +The recovery details page displays detailed information about the specific recovery. + +Tab | Description +---|--- +Progress | Displays the following under Overview: + + * Recovery Plan name. If this was a cyber recovery, you can use the Save as a plan option to save this Recovery Plan. If any of the virtual machines are relics, this option is not available. + * Recovery outcome + * Number of objects recovered + * Start time + * End time + * Duration of the recovery + +Displays the following for each recovery step under Progress: + + * The number of steps and sub-steps + * Message about the recovery step + * Start time + * End time + * The elapsed time + * Status + + +Details | Displays the following elements used for the recovery: + + * Recovery option-Export or Live Mount + * Compute resources + * Storage resources + * Network Resources + + +Post Scripts (vSphere virtual machines only) | Displays the objects and the post-scripts configured. + +You can also download the recovery report or clean up the recovery from this page. + *[ > ]: and then diff --git a/saas_recovery_information.md b/saas_recovery_information.md new file mode 100644 index 0000000000000000000000000000000000000000..5733757bf2a7c032a263c2ffb59c2c9adf972e21 --- /dev/null +++ b/saas_recovery_information.md @@ -0,0 +1,29 @@ +# Recovery information + +Source: https://docs.rubrik.com/en-us/saas/saas/recovery_information.html + +--- + +# Recovery information + +For recoveries that have been performed, the Recoveries page provides the following information regarding : Recovery Plan recovery outcomes. + +The Recoveries page provides the Recovery Plan name, objects, start and end time, duration, recovery result, and recovery outcome. The following table describes the various recovery outcomes: + +Recovery result | Description +---|--- +Completed | The recovery was completed. +Failed | The recovery failed. The recovery report provides additional information. +Paused | The recovery has been paused because of an error. The status of the virtual machines determines whether the test should resume or be cleaned up. +Completed, Awaiting Cleanup | Orchestrated Recovery is yet to delete the virtual machines recovered after a test failover or cyber recovery. +Completed, Cleanup Failed | Orchestrated Recovery failed to delete the virtual machines recovered after a test failover or cyber recovery. + +The following table describes the actions that you can perform on the Recoveries page: + +Action | Description +---|--- +Filter recoveries | You can filter by Recovery Plan type, time range, Recovery Plan, recovery schedule (for VMware virtual machines and AHV virtual machines), and recovery name. +Download report | You can download the report for a recovery by selecting the Download icon from the ellipsis menu in the corresponding recovery row. +Clean up recovery | You can clean up a recovery by selecting Clean Up Recovery from the ellipsis menu in the corresponding recovery row. +Resume recovery | You can resume a paused recovery by selecting Resume Recovery from the ellipsis menu in the corresponding recovery row.RSC pauses the recovery in case of an error if you select the Pause and resume manually after assessing the error option for Error Handling for VM Recovery when initiating a recovery. + *[ > ]: and then diff --git a/saas_recovery_plan_details.md b/saas_recovery_plan_details.md new file mode 100644 index 0000000000000000000000000000000000000000..21ff90dae6d54973e5bf813422b56384ef0910bd --- /dev/null +++ b/saas_recovery_plan_details.md @@ -0,0 +1,18 @@ +# Recovery Plan details + +Source: https://docs.rubrik.com/en-us/saas/saas/recovery_plan_details.html + +--- + +# Recovery Plan details + +The Recovery Plan details page provides information about the configured Recovery Plan. + +From the Recovery Plan details page, you can: + + * View details of the Recovery Plan. The information depends on the Recovery Plan selected and the virtual machine platform. + * Recover the objects using the specific Recovery Plans. + * Edit the recovery plan or the resource map (for in-place or disaster Recovery Plans). + * Delete the Recovery Plan. + + *[ > ]: and then diff --git a/saas_recovery_plan_page_actions.md b/saas_recovery_plan_page_actions.md new file mode 100644 index 0000000000000000000000000000000000000000..8297e4a1a366249010d6770ba93977eb37dab52e --- /dev/null +++ b/saas_recovery_plan_page_actions.md @@ -0,0 +1,20 @@ +# Actions available for Recovery Plans + +Source: https://docs.rubrik.com/en-us/saas/saas/recovery_plan_page_actions.html + +--- + +# Actions available for Recovery Plans + +The Recovery Plans page provides a detailed overview of the Recovery Plans as well as options to search, create, and recover. + +From the Recovery Plans page, you can: + + * Filter Recovery Plans. For vSphere and AHV virtual machines, you can filter by type or source cluster. For Azure virtual machines, you can filter by source subscription and target subscription. + * Search for a Recovery Plan by name in the Search bar. + * Create a cyber, disaster, or in-place Recovery Plan using the Create Recovery Plan wizard. + * Recover objects using a preconfigured Recovery Plan. + * Select and delete a Recovery Plan from the menu. + * View details of a Recovery Plan. + + *[ > ]: and then diff --git a/saas_recovery_using_rp.md b/saas_recovery_using_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..15a86cc4a8d5c622021d5b3300c56f866fa1d0b3 --- /dev/null +++ b/saas_recovery_using_rp.md @@ -0,0 +1,12 @@ +# Recovery using a Recovery Plan + +Source: https://docs.rubrik.com/en-us/saas/saas/recovery_using_rp.html + +--- + +# Recovery using a Recovery Plan + +Recovery Plans can restore data locally when there is data loss from an on-premises application. + +RSC protects Recovery Plans by backing up virtual machine data, Recovery Plan metadata, network configuration, boot order information, and post scripts. RSC recovers virtual machines according to a Recovery Plan by using snapshots from each virtual machine in the Recovery Plan. By default, RSC uses the most recent snapshots, but you can specify snapshots during the recovery process. + *[ > ]: and then diff --git a/saas_recovery_without_rp.md b/saas_recovery_without_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..cb85806d4aa2610b53221f5bd076b0af199c0084 --- /dev/null +++ b/saas_recovery_without_rp.md @@ -0,0 +1,24 @@ +# Recovery without using a Recovery Plan + +Source: https://docs.rubrik.com/en-us/saas/saas/recovery_without_rp.html + +--- + +# Recovery without using a Recovery Plan + +Using the Cyber Recovery wizard, you can select and recover objects on demand even without a Recovery Plan. + +Cyber recovery helps you prepare for a cyber attack through proactive testing and automates your end-to-end recovery. You can select objects from the Objects page and recover them using the Cyber Recovery wizard. You can select virtual machines based on threat hunt results and the applicable recovery options. + +The Cyber Recovery workflow involves the following: + + * Selecting a snapshot to recover each object. You can use threat hunt results to specify the snapshot. + * Defining the target resources that are available in the recovery environment for recovering the selected virtual machines. This task is only applicable for cyber recoveries. + * Assigning the boot order for the virtual machines. When recovering VMware virtual machines, you can also assign post scripts. The boot order ensures that a virtual machine is running before instantiating other virtual machines that depend on it. The post scripts run on a virtual machine after the boot process to perform setup and configuration tasks specific to an environment. + +You can recover virtual machines and replicas of virtual machines without a Recovery Plan. Performing cyber recovery has the following requirements: + + * The Rubrik cluster must be running Rubrik CDM version 8.1.3 or later. + * The user must have permissions assigned for Live Mount and Export recovery options. + + *[ > ]: and then diff --git a/saas_removing_ioc_from_custom_intel_feed.md b/saas_removing_ioc_from_custom_intel_feed.md new file mode 100644 index 0000000000000000000000000000000000000000..ced7a1c4a8a430aa13d9300eeaea38494fc7f256 --- /dev/null +++ b/saas_removing_ioc_from_custom_intel_feed.md @@ -0,0 +1,41 @@ +# Removing an IOC from a custom intel feed + +Source: https://docs.rubrik.com/en-us/saas/saas/removing_ioc_from_custom_intel_feed.html + +--- + +# Removing an IOC from a custom intel feed + +When you do not agree with the indicators of compromise results or the indicator of compromise is too noisy, remove it from custom intel feed. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. On the navigation bar, click Intel Feed. + +The Intel Feed page appears. + + 4. Click an intel feed card. + +The intel feed card displays the list of indicators of compromise (IOCs), their type, the threat family, the date they were added, and the user who added them. + + 5. Select an IOC from the list and click Remove IOCs. + +If you remove the selected IOC, Threat Monitoring no longer scans for it. You can remove more than one IOC at a time. + +The Remove IOCs dialog box appears. + + 6. Click Remove. + +## Results + +Threat Monitoring removes the selected IOC from the intel feed. + *[ > ]: and then diff --git a/saas_removing_quarantined_file_or_object.md b/saas_removing_quarantined_file_or_object.md new file mode 100644 index 0000000000000000000000000000000000000000..3f875e136406939f3fa49b088325e63c7f93e418 --- /dev/null +++ b/saas_removing_quarantined_file_or_object.md @@ -0,0 +1,45 @@ +# Removing a quarantined file or object + +Source: https://docs.rubrik.com/en-us/saas/saas/removing_quarantined_file_or_object.html + +--- + +# Removing a quarantined file or object + +Remove a quarantined file or object to make it available for recovery. + +## Before you begin + +Ensure that you have a user account with permissions to add files to quarantine and remove files from quarantine. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Click the threat hunt of interest. + +When added to quarantine, the quarantined objects are listed with details of the location, files matched, and match type. + + 5. **Optional:** Click an object to view the files in that object. + 6. Select items for quarantining at the object or file level. + 7. Click select Remove from Quarantine. + +Releasing the selected files from quarantine removes the restrictions placed on those files. All matched snapshots in the threat hunt that contain the selected files then have full recovery options. + +The Remove from Quarantine wizard shows the files you selected for removal from quarantine. + + 8. In the Remove from Quarantine wizard, enter `REMOVE` to confirm and then click Remove. + +When the total request size exceeds the limit, you can make further selections on a subsequent request. + +## Results + +RSC removes the selected objects from quarantine and makes the object available for recovery. + *[ > ]: and then diff --git a/saas_removing_standalone_esxi_host.md b/saas_removing_standalone_esxi_host.md new file mode 100644 index 0000000000000000000000000000000000000000..c7b85ea42c65044fe038f80086f78ab9cc170bb0 --- /dev/null +++ b/saas_removing_standalone_esxi_host.md @@ -0,0 +1,37 @@ +# Removing a standalone ESXi host + +Source: https://docs.rubrik.com/en-us/saas/saas/removing_standalone_esxi_host.html + +--- + +# Removing a standalone ESXi host + +Remove a connected standalone ESXi host to stop managing its virtual machines and backups, ensuring that the host is no longer part of the data protection operations. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the vSphere VMs inventory card. + +The vSphere VMs page appears. + + 5. Click Manage vSphere. + +The vSphere page under Settings appears. + + 6. Click on the host and select Remove Host. + +A message that the host has been removed appears. + +## Results + +RSC removes the connected ESXi host. + *[ > ]: and then diff --git a/saas_replication_and_cascading_arch_settings.md b/saas_replication_and_cascading_arch_settings.md new file mode 100644 index 0000000000000000000000000000000000000000..0a5075aa3ca7d634f782e60a8735edf25b83e7e5 --- /dev/null +++ b/saas_replication_and_cascading_arch_settings.md @@ -0,0 +1,24 @@ +# Replication and cascading archival settings + +Source: https://docs.rubrik.com/en-us/saas/saas/replication_and_cascading_arch_settings.html + +--- + +# Replication and cascading archival settings + +When you enable cascading archival, you can determine the snapshot retention period by managing specific settings. + +To determine the retention period of snapshots on the cascading archival location, RSC uses several snapshot retention settings on the replication source Rubrik cluster and the replication target Rubrik cluster. The following table describes these settings. + +Setting | Description +---|--- +The duration to retain snapshots (configured on the Frequency and Retention page for the replication source Rubrik cluster) | Specifies the maximum duration for which snapshots will be retained.When archiving and replication are enabled, the maximum duration includes the retention period on the archival location and the replication target cluster. +Replication Retention | Specifies the maximum duration for which snapshots are retained by the replication target cluster.The replication retention must be less than or equal to the maximum retention configured for the snapshots. +(Cascading archival enabled) Retention on Target Cluster | Specifies the period for which snapshots are retained locally on the replication target cluster.This retention duration must be less than or equal to the maximum retention on the target cluster specified by the Replication Retention setting.RSC expires the snapshots locally from the target cluster after the specified duration elapses or the retention period based on the snapshot frequency elapses, whichever occurs first. +(Cascading archival enabled) Cascading Archival Threshold | Specifies the number of days after which RSC archives the snapshots from the replication target cluster to the archival location.Archival threshold must be less than or equal to the value of the Retention on Target Cluster setting. + +The snapshot retention period on the cascading archival location is determined by the following formula: + + + Cascading archival retention period = Replication Retention - Cascading Archival Threshold + *[ > ]: and then diff --git a/saas_report_templates.md b/saas_report_templates.md new file mode 100644 index 0000000000000000000000000000000000000000..83c10888be7003fab3d5d9bb9b77437b79c1d86a --- /dev/null +++ b/saas_report_templates.md @@ -0,0 +1,46 @@ +# Report templates + +Source: https://docs.rubrik.com/en-us/saas/saas/report_templates.html + +--- + +# Report templates + +Information about the report templates in RSC to create reports that provide insights into resource usage and related operations. + +Reports offer insights into the usage of resources and associated operations. The following table provides information about the report templates available in RSC. + +Default reports have no filters or groupings. You can use default reports as basic templates and modify them to create new reports. + +The following table describes the available report template types: Template type | Description +---|--- +Infrastructure | Displays attributes related to your Rubrik infrastructure. +Object Capacity | Displays the amount of local data transferred and storage used. +Object Capacity Over Time | Displays the amount of local data transferred and storage used on a monthly, daily, or hourly basis. +Compliance | Displays the compliance status of the selected workload. +Protection | Displays protection information for the selected workload. +Event | Displays the RSC events status.The following colors indicate the severity levels of the notifications in reports. + + * Critical: red + * Warnings: orange + * Information: blue + +Each event in a notification report has a hyperlink and points you to the event series in RSC. You can click the link to view the event series.A column in the report table provides the reason for any failed events.Data for events takes about 10-15 minutes to synchronize. Synchronization between Rubrik clusters and RSC can take up to four hours. +Protection Tasks Details | Displays the protection tasks for each cluster and a summary table with detailed information. The NAS CD object type is supported in this report. +Recovery Tasks Details | Displays the status of the recovery tasks for each cluster and a summary table with detailed information. The NAS CD object type is supported in this report. +Anomaly Detection | Displays anomaly information for the selected workload. +SLA Audit | Displays information for SLA Domains from a Rubrik cluster that was modified during a specific time period. Lists the most recent change made to the SLA Domain.You can click an SLA Domain name in the report to view the changes made during that time period. +Object Audit | Displays the SLA Domain assigned to each Rubrik CDM workload. You can expand an object row to view historical information about the SLA Domain assignments. +Object Backup Task Summary | Provides information about scheduled backup tasks. RSC triggers these backup tasks based on the protection policy of the associated SLA Domain. The report does not include information about on-demand backup tasks.Information includes the total number of daily expected backup tasks for each object along with the number of successful, failed, canceled, and missed tasks.This report does not include information for the current day. +Threat Monitoring | Displays information about the threats detected by Rubrik on all CDM workloads across the selected time range. +Indexing | Displays information about the indexing status for objects. Provides filtering according to SLA Domain, Object Type, and the latest snapshot index status. +QAuth Roles | Displays a list of users who can approve specific policies associated with a Quorum Authorization request. With this report, you can easily find the users with QAuth reviewer role and the associated policies they can approve. +Users | Displays users, their login configurations, and activities that you can use for daily operations and auditing purposes. +Service Account | Displays service accounts and details that you can use for auditing purposes. +SSO Groups | Displays SSO Groups and details that you can use for auditing purposes. +Roles | Displays the roles created by the administrator and the associated descriptions. + +Note: + +Depending on the amount of data involved, synchronization between Rubrik clusters and RSC can take several days. + *[ > ]: and then diff --git a/saas_requirements_for_sla_domain_names.md b/saas_requirements_for_sla_domain_names.md new file mode 100644 index 0000000000000000000000000000000000000000..8fa33fcb35ab42eab6204a48110d4060b0dd41b0 --- /dev/null +++ b/saas_requirements_for_sla_domain_names.md @@ -0,0 +1,18 @@ +# Requirements for SLA Domain names + +Source: https://docs.rubrik.com/en-us/saas/saas/requirements_for_sla_domain_names.html + +--- + +# Requirements for SLA Domain names + +An SLA Domain must meet specific name requirements. + +When creating an SLA Domain, use a domain name that meets the following requirements: + + * Unique within the RSC namespace + * Cannot be null + * Less than 255 characters + * Contains only alphanumeric, space, hyphen, and underscore characters + + *[ > ]: and then diff --git a/saas_resetting_password.md b/saas_resetting_password.md new file mode 100644 index 0000000000000000000000000000000000000000..5d083d9ae94957c59114ff2e15a32f25606315bc --- /dev/null +++ b/saas_resetting_password.md @@ -0,0 +1,36 @@ +# Resetting the password + +Source: https://docs.rubrik.com/en-us/saas/saas/resetting_password.html + +--- + +# Resetting the password + +If you suspect your RSC domain has been compromised or have other security concerns, reset your password from the User Preferences page. + +## Procedure + + 1. Log in to RSC. + 2. Open the silhouette menu and select User Preferences. + +The User Preferences page appears. + + 3. Click Password Settings. + +The Password Settings page appears. + + 4. Click Reset Password. + +RSC sends a password reset email. + + 5. From the password reset email, click Continue. + +The New password page appears. + + 6. In New Password, enter a new password. + 7. In Confirm Password, enter the same password. + 8. Click Continue. + +## Results + +RSC stores the new password. diff --git a/saas_retention_locked_sla_domain.md b/saas_retention_locked_sla_domain.md new file mode 100644 index 0000000000000000000000000000000000000000..ea1073d8003cc61728df289c7aa7a656ca5dcd4c --- /dev/null +++ b/saas_retention_locked_sla_domain.md @@ -0,0 +1,49 @@ +# Retention-locked SLA Domains + +Source: https://docs.rubrik.com/en-us/saas/saas/retention_locked_sla_domain.html + +--- + +# Retention-locked SLA Domains + +The retention lock feature on RSC SLA Domains ensures the security and integrity of your data for a specified duration by preventing the premature deletion of snapshots for various workloads. + +The retention lock feature is available only for Rubrik clusters running Rubrik CDM version 7.0.2 or later. + +With the retention lock feature, you can achieve the following results: + + * Control and secure the retention settings for data. + * Ensure that data remains unaltered and protected against accidental deletion. + * Maintain data integrity and adhere to data retention policies. + +You can enable the retention-locked SLA Domain feature by contacting Rubrik Support. After Rubrik Support enables the retention lock feature on a Rubrik cluster, when you create or edit an SLA Domain, a toggle to apply the retention lock appears, providing you with the option to use the retention lock feature. + +When you are creating or editing an SLA Domain, you can assign settings that affect the level of security for your workloads, including the following parameters: + + * Snapshot frequency: How frequently snapshots are taken + * Data retention: How long data is retained before deletion + +To understand the security levels of SLA Domains, consider the following definitions: + + * Less secure SLA Domain: Retention and frequency settings that provide reduced protection or a shorter data retention period compared to the current SLA Domain settings for the snapshots. This implies weaker data protection. + * More secure SLA Domain: Retention and frequency settings that offer enhanced security and an extended data retention period compared to the current SLA Domain settings for the snapshots. + +When you enable Apply to existing snapshots: + + * If a more secure SLA Domain retains a snapshot, the compliance mode remains unchanged. + * If the current SLA Domain has a lesser retention period or lower snapshot frequency than the new compliance mode SLA Domain, the compliance mode SLA Domain policies are applied to the snapshot. This results in stronger data protection due to more frequent snapshots and longer retention periods. + * If a retention-locked SLA Domain retains existing snapshots, whether in governance mode or a less secure compliance mode, the more secure retention lock of the new SLA Domain protects them. + * If snapshots are in compliance mode, the current SLA Domain continues to retain them. + +When you disable the retention lock, existing snapshots remain retention-locked unless you enable Apply changes to existing snapshots. If you enable the Apply changes to existing snapshots option, the existing snapshots or the new snapshots are not retention locked. + +A retention lock prevents the retention period assigned to an SLA Domain from being decreased. Before you can set a retention lock, you must define a minimum retention period for the SLA Domain. Setting the retention lock enforces this minimum retention period. After the retention lock is enabled for an SLA Domain, the following actions cannot be performed: + + * Removing the retention lock from that SLA Domain + * Deleting the snapshots protected by the SLA Domain during the retention period + * Decreasing the minimum retention period until the snapshot has expired + +Note: + +Rubrik cannot guarantee that no data is lost if an attacker gains access to a non-immutable or cascading archival location. + *[ > ]: and then diff --git a/saas_retention_mgmt_existing_snapshots.md b/saas_retention_mgmt_existing_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..25b95704f64a6522bf3a44a02ceb7e4f61b4776f --- /dev/null +++ b/saas_retention_mgmt_existing_snapshots.md @@ -0,0 +1,52 @@ +# Retention management for existing snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/retention_mgmt_existing_snapshots.html + +--- + +# Retention management for existing snapshots + +You can manage the retention period of existing snapshots to prevent accidental data loss, ensuring the preservation of individual snapshot retention even when modifying SLA Domains. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +Managing the retention of existing snapshots helps prevent accidental data loss that can occur when you modify or reassign an SLA Domain, especially if the new SLA Domain has a shorter retention period. With the static retention feature, you can preserve the retention of individual snapshots, even when you edit their associated SLA Domain. This feature ensures that your critical recovery points are not prematurely deleted and provides granular control over snapshot retention. For example, you can assign an SLA Domain to a specific snapshot that differs from the SLA Domain you assign to the object. This enables you to retain crucial data for longer periods. You can also view the exact expiration date of snapshots in primary, archival, and replicated locations. + +## Retention changes based on workload type + +When modifying SLA Domains, RSC applies the changes to snapshots based on the workload type: + + * For SLA Domains with data center workloads: RSC applies the changes to snapshots in primary and archival locations. You can optionally apply the changes to on-demand and downloaded snapshots. + * For SLA Domains with cloud-native workloads: RSC applies the changes to snapshots in primary, archival, and replicated locations. You can optionally apply these changes to on-demand snapshots. + +## Snapshot retention levels + +RSC provides flexible options for managing retention, enabling you to control how long snapshots are kept at various granular levels to align with your specific data protection and compliance needs. + + * SLA Domain level: When you modify the retention settings in an SLA Domain, you can also apply these changes to existing snapshots. This ensures that your entire data protection strategy aligns with your current protection policy. + + * Object level: For more granular control, you can change the retention period for all snapshots associated with a specific object. Managing retention at the object level enables you to apply a consistent retention policy to all snapshots for a specific workload. + + * Snapshot level: You can modify the retention period of an individual snapshot. This is useful for preserving critical recovery points beyond the standard SLA Domain policy or for quickly releasing storage space for less critical, on-demand snapshots. + +## Re-replication of snapshots + +If you update an existing SLA Domain to change its replication target, all snapshots taken within the last 31 days are re-replicated to the new target if those snapshots are not already present at that location. This re-replication occurs regardless of whether you applied the SLA Domain changes to existing snapshots or not. + +When you update the SLA Domain for an individual snapshot, you must consider the following: + + * If the snapshot is older than 31 days, RSC does not re-replicate the snapshot. + * If the snapshot is within 31 days, not replicated to the new target, and no newer snapshot is already present at the new target, RSC re-replicates the snapshot. + +## Example scenario for re-replication behavior + +Consider a scenario where you updated an SLA Domain to change the replication target from T1 to T2 for a workload with the following snapshots: + +Snapshot | Age (Relative to 31 days) | Original replication target | New replication target (if applicable) | Re-replication status | Reason +---|---|---|---|---|--- +S0 | Older than 31 days | T1 | N/A | Not Re-replicated | Snapshot is older than 31 days. +S1 | Within 31 days | T1 | N/A | Not Re-replicated | A newer snapshot (S2) is already replicated to the new target (T2). +S2 | Within 31 days | T2 | T2 | Not Re-replicated | Snapshot is already replicated to the same target (T2). +S3 | Within 31 days | T1 | T2 | Re-replicated | The original target (T1) differs from the new target (T2), and no newer snapshot exists on T2. +S4 | Within 31 days | T1 | T2 | Re-replicated | The original target (T1) differs from the new target (T2), and no newer snapshot exists on T2. + *[ > ]: and then diff --git a/saas_retention_policy_modification_for_existing_snapshots.md b/saas_retention_policy_modification_for_existing_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..0af223b97bf3efa2a61c2023ae2383a8b4b420f7 --- /dev/null +++ b/saas_retention_policy_modification_for_existing_snapshots.md @@ -0,0 +1,32 @@ +# Retention policy modification for existing snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/retention_policy_modification_for_existing_snapshots.html + +--- + +# Retention policy modification for existing snapshots + +After configuring the SLA Domain settings, you can modify the retention policy for existing snapshots. + +The following table provides information about optional settings for modifying existing snapshots associated with various workloads. Workload | Modify retention of existing snapshots +---|--- +Db2 | NoYou cannot change the retention period for policy based SLA Domain backups or external backups, but you can change the retention period for on-demand backups.You can apply log retention as the retention for externally triggered backups. +Filesets | Yes (Edit SLA Domain) Apply changes to existing snapshots.You can apply the changes made to the SLA Domain to existing snapshots. +vSphere | Yes (Edit SLA Domain) Apply changes to existing snapshots.You can apply the changes made to the SLA Domain to existing snapshots. +Amazon Web Services (AWS) workloads: + + * AWS - EC2 and applications + * AWS S3 + * AWS RDS + +| Yes (Edit SLA Domain) Apply changes to existing snapshots.You can apply the changes made to the SLA Domain to existing snapshots. +Microsoft Azure workloads: + + * Azure - VMs and Applications + * Azure Blob Storage + * Azure SQL Databases + * Azure SQL Managed Instances + +| Yes (Edit SLA Domain) Apply changes to existing snapshots.You can apply the changes made to the SLA Domain to existing snapshots.Note: For Azure SQL Databases and Managed Instances, you cannot change the retention of snapshots that are managed by Azure. +Google Cloud Platform (GCP) | Yes (Edit SLA Domain) Apply changes to existing snapshots.You can apply the changes made to the SLA Domain to existing snapshots. + *[ > ]: and then diff --git a/saas_ri_best_practices_configuring_threat_hunts.md b/saas_ri_best_practices_configuring_threat_hunts.md new file mode 100644 index 0000000000000000000000000000000000000000..74a204dfed1b05b9eaecca5ba181bd5c95b9c841 --- /dev/null +++ b/saas_ri_best_practices_configuring_threat_hunts.md @@ -0,0 +1,67 @@ +# Best practices for configuring threat hunts + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_best_practices_configuring_threat_hunts.html + +--- + +# Best practices for configuring threat hunts + +For optimal results, you can follow a set of best practices when configuring threat hunts. + +When ransomware attacks happen, identifying the point of time the malware was introduced is critical to ensure a safe recovery without reinfection. Scanning backups for indicators of compromise (IOCs) provides a safe point of time and safe data to recover from. Configuring threat hunts selectively provides specific results whereas configuring broadly generic threat hunts causes performance delays and bottlenecks. + +Rubrik recommends the following best practices to achieve the best performance and results when configuring threat hunts: + + * Selecting YARA rule as the IOC provides more in-depth results because this option checks file contents. + * Specifying the Rubrik cluster and the objects in the threat hunt ensures that the snapshot selection is smaller. Choosing a custom date range and the maximum snapshots per object also optimizes the scope of the scan. + * Lowering the number of maximum IOC matches narrows the scope and enables a more efficient threat hunt when the goal is to understand whether the host is affected and to identify a clean point for restoration. If you have multiple file hashes added, you can also lower the IOC matches option to one for optimal scanning. When the threat hunt identifies the IOC on the host, it skips the remaining files to scan, and flags the snapshot for the impacted host as a match. + * Lowering the minimum file size from the default value of 250 KB to a lower value of about 10 KB or to the size of the file that you are hunting for provides a quicker and more optimized scan. + * Using the file exclusions correctly also ensures a more optimized scan for specific issues. + * Updating to Rubrik CDM versions 8.0.3, 8.1, or later ensures a more efficient scan due to optimizations in the codebase. + * Using the 3.7.1 version for YARA rules instead of later versions provides better results. + +The following are some considerations when creating YARA rules for threat hunts: + + * Creating your YARA rule to focus specifically on unique and characteristic strings or patterns unlikely to occur in benign files. + * Considering the context in which the malicious string appears. If the pattern is surrounded by other known malware indicators or characteristics, those indicators can be incorporated in the YARA rule. + * Before deploying the YARA rule, testing it against various samples, including both malicious and benign files, to verify its accuracy and minimize false positives. + * Keeping the rule up to date with the latest threat intelligence. Malware might evolve and change over time, so regularly reviewing and updating your rules is crucial. + * Avoiding the use of generic or common strings because they might lead to false positives due to their prevalence in legitimate files. + +The following sample YARA rule from the open source library of YARA rulesets by Airbnb matches these considerations: + + + rule eicar_av_test { + /* + Per standard, match only if entire file is EICAR string plus optional trailing whitespace. + The raw EICAR string to be matched is: + X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H* + */ + + meta: + description = "This is a standard AV test, intended to verify that BinaryAlert is working correctly." + author = "Austin Byers | Airbnb CSIRT" + + strings: + $eicar_regex = /^X5O!P%@AP\[4\\PZX54\(P\^\)7CC\)7\}\$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!\$H\+H\*\s*$/ + + condition: + all of them + } + + rule eicar_substring_test { + /* + More generic - match just the embedded EICAR string (e.g. in packed executables, PDFs, etc) + */ + + meta: + description = "Standard AV test, checking for an EICAR substring" + author = "Austin Byers | Airbnb CSIRT" + + strings: + $eicar_substring = "$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!" + + condition: + all of them + } + *[ > ]: and then diff --git a/saas_ri_events.md b/saas_ri_events.md new file mode 100644 index 0000000000000000000000000000000000000000..f34a919316108196f10caddaeb659afc119e2ab9 --- /dev/null +++ b/saas_ri_events.md @@ -0,0 +1,16 @@ +# Data Threat Analytics events + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_events.html + +--- + +# Data Threat Analytics events + +Data Threat Analytics provides filters and real-time search capabilities that can be used to find specific events. + +When events are enabled, Data Threat Analytics sends an alert email when an anomaly is detected. The alert email contains a link to RSC. Accessing the link allows you to perform further investigation and, if necessary, recover files. The recovery process allows you to replace only the affected data without requiring that you perform a new analysis of the entire data set. + +Click on a Data Threat Analytics event to view the time line of snapshots taken for a specific time range, examine the file system of a series of snapshots, and determine approximately when the ransomware attack occurred. From this view, select the snapshot with the most recent clean versions of the files that were identified as compromised. Those files can be used as the starting point for file recovery. + +To support RBAC, CSV file downloads are only available from the Anomalies page and the anomaly details page. When you click Download CSV, RSC prepares a secure link for the file and displays a message about the download. You can also visit the File Preparation Center to access the downloaded file. + *[ > ]: and then diff --git a/saas_ri_events_for_protected_objects.md b/saas_ri_events_for_protected_objects.md new file mode 100644 index 0000000000000000000000000000000000000000..84d98ce36c83fe9245170fa002b9839ca3cac578 --- /dev/null +++ b/saas_ri_events_for_protected_objects.md @@ -0,0 +1,18 @@ +# Anomaly Detection events for protected objects + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_events_for_protected_objects.html + +--- + +# Anomaly Detection events for protected objects + +Anomaly Detection events are enabled by default for supported and scanned objects. + +As needed, events can be disabled at the object level. Events can also be enabled if they were previously disabled. This provides more fine-grained control of Anomaly Detection alerts at a protected-object level. + +When Anomaly Detection events are enabled, event data is displayed in the Dashboard page, the Events page, and in Alert emails (if configured). + +When Anomaly Detection Events are disabled on an object, new events will no longer be visible in the Events page and alert emails will not be generated for Anomaly Detection events for that object. Old events will still be visible in the Events page or in previously received emails. + +The disable option only impacts whether the data is visible in the Events page. Snapshots for disabled objects will continue to be processed and the data captured in reports. + *[ > ]: and then diff --git a/saas_ri_ransomware_monitoring.md b/saas_ri_ransomware_monitoring.md new file mode 100644 index 0000000000000000000000000000000000000000..a733dce8dab6057f34e187992ce626289e421428 --- /dev/null +++ b/saas_ri_ransomware_monitoring.md @@ -0,0 +1,17 @@ +# RSC Data Threat Analytics + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_ransomware_monitoring.html + +--- + +# RSC Data Threat Analytics + +RSC Data Threat Analytics provides Anomaly Detection and data recovery services on protected resources. + +Data Threat Analytics comprises Anomaly Detection, Threat Monitoring, Threat Hunting, and data recovery services on protected resources. + +Anomaly Detection identifies and analyzes anomaly events that can indicate a ransomware attack. When an attack is discovered, you can use Anomaly Detection to directly recover the original data. Anomaly Detection works in combination with other data security methods to provide an additional layer of protection. + +For each protected object, Anomaly Detection captures the changes in file system behavior and file content behavior that occur between snapshots. Anomaly Detection analyzes this information and provides a view of the changed behavior and changed content over time, when an incident has occurred. RSC retains the history of the metadata tracked by Data Threat Analytics for 30 days. + +Anomaly Detection does not support deep scanning for encryption for NAS Direct Archive. diff --git a/saas_ri_reports.md b/saas_ri_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..3c4dd1253327d3fdf5c2d3c2dcc93b8665f73f0f --- /dev/null +++ b/saas_ri_reports.md @@ -0,0 +1,14 @@ +# Anomaly Detection reports + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_reports.html + +--- + +# Anomaly Detection reports + +Anomaly Detection reports provide information about the changes in snapshots for anomaly events. You can also download, save, or delete the reports. + +The Anomaly Detection report displays information about anomalies detected in the Scanned Objects and Unscannable Objects tab. You can view details, including snapshot date, resource name, resource type, change in byte size, anomaly indicator, number of files added, number of files removed, and number of files modified. + +You can also download a CSV or PDF file of the report, send the report to an email address, and save or delete the report. + *[ > ]: and then diff --git a/saas_ri_threat_hunts.md b/saas_ri_threat_hunts.md new file mode 100644 index 0000000000000000000000000000000000000000..dd2899354e4c1c1295fa4a6b7b0d0dc612b9f412 --- /dev/null +++ b/saas_ri_threat_hunts.md @@ -0,0 +1,40 @@ +# Threat hunts + +Source: https://docs.rubrik.com/en-us/saas/saas/ri_threat_hunts.html + +--- + +# Threat hunts + +On-demand threat hunts scan Rubrik backups for user-defined indicators of compromise and identify the systems potentially affected by an attack. + +When ransomware attacks happen, it is essential to respond quickly. Identifying which systems were compromised and when indicators of compromise (IOCs) were first present in those systems can be challenging. A threat hunt identifies files that might be at risk by scanning Rubrik backups to find when a compromise related to the attack occurred. + +Threat hunting is not a pattern-based anti-malware scanner, but an analysis tool for identifying specific IOCs. You can use threat hunt results to identify potentially malicious files and the snapshots in which they were present, avoiding malware reinfection during recovery. + +Threat hunting employs a full/incremental scanning method in which the initial scan is a full scan, but all subsequent scans are incremental. This reduces the number of files in subsequent scans and reduces the time to scan, optimizing the threat hunt. + +The presence of IOCs on a system indicates that malware might have compromised the system. You can configure threat hunts with the following key IOCs: + + * Yet Another Recursive Acronym (YARA) rules, which use scripts that look for certain characteristics to identify malware. YARA rules are available only for advanced threat hunts. + * File hashes, which use specific file hash values to search for malware (MD5, SHA1, or SHA256). + * File patterns, which use specific file paths to search for malware. File patterns are available only for advanced threat hunts. + +RSC limits the number of threat hunts it supports. For each 30-day period, the product of the number of threat hunts and the number of snapshots per threat hunt should be fewer than 10,000. + +Threat hunting is supported for the following workloads: + + * VMware, AHV, and Hyper-V virtual machines + * NAS filesets, excluding NAS Direct Archive filesets + * Microsoft Windows filesets + * Linux and Unix filesets + * Microsoft SharePoint and OneDrive + * Azure virtual machines, Blob storage, and managed disks + * AWS EC2 instances, S3 buckets, and EBS volumes + +Only turbo threat hunts are supported for Azure virtual machines, Blob storage, and managed disks, AWS EC2 instances, S3 buckets, and EBS volumes, Microsoft SharePoint, and OneDrive. + + * GCP GCE Instances + * GCP Disks + + *[ > ]: and then diff --git a/saas_rm_performing_cyber_recovery_vm_export.md b/saas_rm_performing_cyber_recovery_vm_export.md new file mode 100644 index 0000000000000000000000000000000000000000..4424eddd364fe9ce29fd3f7a6aaa31b6b56312c1 --- /dev/null +++ b/saas_rm_performing_cyber_recovery_vm_export.md @@ -0,0 +1,126 @@ +# Performing cyber recovery of virtual machines using Export + +Source: https://docs.rubrik.com/en-us/saas/saas/rm_performing_cyber_recovery_vm_export.html + +--- + +# Performing cyber recovery of virtual machines using Export + +Select and recover virtual machines using export, based on threat hunting results, to a local, isolated recovery environment. + +## About this task + +If the recovery environment is completely isolated, ensure that you include all fundamental infrastructure services required for these objects to function. These may include, but are not limited to, DNS and authentication services. This option creates virtual machines from snapshots and uses the selected target storage resources for the new virtual machines. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. On the navigation bar, click **Anomaly Detection**. + +The Anomaly Detection page appears. + + 4. Select the virtual machines to recover and click Start **Cyber Recovery**. + +All objects selected for recovery must belong to the same Rubrik cluster. If you are recovering virtual machines and replicas, the objects in the recovery must have a common cluster, either source cluster or target cluster. + +The Start Cyber Recovery wizard appears. + + 5. In the Select Recovery Option page, select Export as the option for recovery. + +The Select Snapshots page appears. + + 6. In Cluster, select the cluster you want to use for this recovery. + +If you choose the replication cluster, the replica of the object is recovered. + + 7. In the Select Snapshots page, select the date and time. + 8. Select a specific snapshot for recovery for each object based on the Anomaly Detection outcome. + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides non-quarantined and non-anomalous snapshots as options for recovery +Quarantined | Provides quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behaviour. +Do not consider | Provides a snapshot without considering snapshot status. + +When there are no snapshots available for an object, you cannot complete a recovery. + + 9. In Error Handling for VM Recovery select an option: + +Option| Description +---|--- +Pause and resume manually after assessing the error | RSC stops the recovery and resumes after assessing the error. +Abort and cleanup the recovered objects | RSC aborts the recovery and cleans up the recovery jobs and any resources in use when it encounters any error during the recovery. + +The Assign Compute Resources page appears. + + 10. In vCenter Server and Datacenter, select target compute resources. + 11. Select the compute resource from one of the options. + * Select the Use the same compute resource for all objects check box to use the same compute resource for all objects and then select a single compute resource. This option is selected by default. + * Clear the Use the same compute resource for all objects check box and then assign compute resources for individual objects. + 12. Click Next. + +The Assign Target Storage Resources page appears. + + 13. Select the datastore or datastore cluster you want the objects to use for their target storage resources. + +You can also select multiple datastore or datastore clusters for each virtual machine disk within the same virtual machine. + + 14. **Optional:** Select the check box to use the same storage resource for all virtual machines. + 15. Click Next. + 16. In the Assign Network Resources page, select an option for Network Preservation. + +Option| Description +---|--- +Select Entire Network and then select the Network for each object. | The current MAC address and IP configuration are retained. +Select MAC Address Only and then select the Network and IP Configuration for each object. | The current MAC address is retained for the source virtual machine. +Select None and then select the Network and IP Configuration for each object. | A new MAC address will be assigned to the virtual machine. + + 17. Select the Recover with network disconnected option to recover without connecting to a network. + 18. **Optional:** Select the Ignore network reconfiguration errors and continue check box. + +When you select this option, RSC ignores network configuration and post-script errors and network configuration or post-script errors will not cause recovery failure. + + 19. Click Next. + +The Assign a Recovery Order page appears. + + 20. Assign a recovery order for the objects you want to recover and select their priority group. + +The objects are recovered in the order specified. Rubrik recommends that you first recover the Identity and Access Management and other core infrastructure services. + + 21. **Optional:** Select the Enable pauses between priority groups toggle to add pauses during recovery. + +The pauses are displayed in minutes between the priority groups. + + 22. Click Next. + +The Specify Post-Recovery Scripts page appears. + + 23. **Optional:** In Specify Post-Recovery Scripts page, enter the script or path to the script you want to execute on each virtual machine after recovery. + +Ensure that the path points to an existing shell script on the associated virtual machine. + + 24. Click Next. + +The Review and Confirm page appears. + + 25. Click Start. + 26. **Optional:** Turn on the toggle to save your recovery specifications as a Recovery Plan and provide it a name. + +A Recovery Plan saves information about the selected objects, their recovery order, and the target resources. You can use this plan to perform a cyber recovery recovery in the future. If any of the virtual machines you selected for this recovery are relics, you cannot include them in the Recovery Plan. + + 27. (Only when saving as a Recovery Plan) In **Cyber Recovery** Details, enter a name for the Recovery Plan. + +If you do not enter a recovery name, the recovery is named as "Recovery Number" by default, where "Number" stands for an assigned number. When a name is provided, the recovery is named as "Recovery Plan Name_Number". + + 28. Click Confirm. + +## Results + +RSC starts the cyber recovery and updates the Recoveries page. + *[ > ]: and then diff --git a/saas_rolling_upgrade_rbk_cdm_software.md b/saas_rolling_upgrade_rbk_cdm_software.md new file mode 100644 index 0000000000000000000000000000000000000000..d0295a833aa71c662b5f970ccb751f932a9fa14d --- /dev/null +++ b/saas_rolling_upgrade_rbk_cdm_software.md @@ -0,0 +1,20 @@ +# Rolling upgrade of Rubrik CDM software + +Source: https://docs.rubrik.com/en-us/saas/saas/rolling_upgrade_rbk_cdm_software.html + +--- + +# Rolling upgrade of Rubrik CDM software + +To minimize any potential downtime for your Rubrik clusters, you can perform the rolling upgrade of Rubrik CDM software running your Rubrik cluster. + +Note: + +The rolling upgrades feature should only be used when you are upgrading a cluster from Rubrik CDM version 9.0 or later. + +With the rolling upgrade, you can upgrade the Rubrik CDM software running on a Rubrik cluster without interrupting backup, refresh, and restore jobs. Nodes of the Rubrik cluster are upgraded one by one, while the backup and restore jobs running on the node are transferred to other nodes in the Rubrik cluster to continue the job progress. + +During a rolling upgrade, you can still access RSC and resume jobs to varying degrees. For instance, if you have MSSQL or VMware Live Mounts, they can continue to run and be kept live by configuring floating IP addresses in the Rubrik cluster. This feature makes the rolling upgrade an ideal option for mission-critical systems. You can initiate an on-demand rolling upgrade or schedule a rolling upgrade directly from the RSC without taking the system offline. + +Rolling upgrade eliminates the efforts involved in an upgrade, such as planning, working with stakeholders, changing the control board, establishing upgrade requirements, and rolling out upgrade plans. + *[ > ]: and then diff --git a/saas_rp_management.md b/saas_rp_management.md new file mode 100644 index 0000000000000000000000000000000000000000..9f4a4e841c379d10505e052acc161d4d7fa66812 --- /dev/null +++ b/saas_rp_management.md @@ -0,0 +1,27 @@ +# Recovery Plan management + +Source: https://docs.rubrik.com/en-us/saas/saas/rp_management.html + +--- + +# Recovery Plan management + +Recovery Plans manage recovery specifications for the different types of recovery. + +A Recovery Plan can contain any one type of virtual machine only: VMware virtual machines, AHV virtual machines, or Azure virtual machines. + +The virtual machines in a Recovery Plan must meet these conditions: + + * For data center workloads, the same Rubrik cluster must protect all virtual machines in a Recovery Plan. For Azure virtual machines, all virtual machines in a Recovery Plan must belong to the same subscription and region. + * For Recovery Plans with VMware virtual machines, all VMware virtual machines must have VMtools installed. + * You cannot add a vSphere virtual machine that has previously been a part of a vCloud Director vApp to a Recovery Plan. + * You cannot share a virtual machine between multiple disaster Recovery Plans, between multiple in-place Recovery Plans, or between a disaster Recovery Plan and an in-place Recovery Plan. + * You can share a virtual machine between a disaster Recovery Plan and a cyber recovery Recovery Plan or between an in-place Recovery Plan and a cyber Recovery Plan. + * You can share a virtual machine between multiple cyber Recovery Plans . + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. + +When creating or editing a Recovery Plan, you can choose individual datastores or a datastore cluster for vSphere virtual machines or storage containers for AHV virtual machines as storage resources in a Recovery Plan during disaster recovery or cyber recovery. For vSphere virtual machines, RSC supports only datastore clusters that have Storage Distributed Resource Scheduler (SDRS) enabled. For a datastore cluster where SDRS is disabled, RSC displays its child datastores as storage resource options. + +For vSphere virtual machines only, you can optionally configure a post-failover script when you create a Recovery Plan. Post-failover scripts are user-defined scripts meant to be executed at the end of a recovery job to confirm that the protected application is completely on line and ready for users once the job is complete. Post-failover scripts run as commands in the shell environment of the guest operating system. + *[ > ]: and then diff --git a/saas_rsc_api_proxy_nascd_rest_api.md b/saas_rsc_api_proxy_nascd_rest_api.md new file mode 100644 index 0000000000000000000000000000000000000000..27e6a0b5128a5c729e86147c68aee7492f33cdd9 --- /dev/null +++ b/saas_rsc_api_proxy_nascd_rest_api.md @@ -0,0 +1,26 @@ +# RSC API proxy for NAS CD REST API + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_api_proxy_nascd_rest_api.html + +--- + +# RSC API proxy for NAS CD REST API + +Using the RSC API proxy, you can send NAS CD REST API requests directly to an RSC instance instead of a NAS CD instance. This simplifies data management across NAS CD clusters and streamlines API interactions, reduces complexity, and enables efficient management of NAS CD data from a single, secure location. + +With the RSC API proxy, you can send NAS CD REST API requests directly to an RSC instance instead of a NAS CD instance. When you use the RSC API proxy to manage a NAS CD cluster, RSC forwards the REST API request to the NAS CD cluster to retrieve the required response. The RSC API proxy simplifies NAS CD data set management from RSC providing centralized management and flexible control over API requests. + +You can use the RSC API proxy with either a service account or an administrator account. For enhanced session management and robust access control, RSC requires you to use a JSON Web Token (JWT) that expires after a predefined period. + +The key features of RSC API proxy are as follows: + + * RSC IP whitelist applies to the RSC API proxy. + * RSC Role-Based Access Control (RBAC) applies to the RSC API proxy users. + +The key benefits of RSC API proxy are as follows: + + * Eliminates the need to get security tokens from individual NAS CD instances because RSC manages the required authentication and authorization centrally for all the NAS CD clusters. + * Requires the same API endpoint to manage both RSC and NAS CD. + * Acts as a stop-gap API solution until RSC can fully manage NAS CD cluster using GraphQL APIs. + + *[ > ]: and then diff --git a/saas_rsc_creating_custom_sla_domain.md b/saas_rsc_creating_custom_sla_domain.md new file mode 100644 index 0000000000000000000000000000000000000000..8a709ead002229d3daffe27e041a95f15c79fc98 --- /dev/null +++ b/saas_rsc_creating_custom_sla_domain.md @@ -0,0 +1,126 @@ +# Creating a custom SLA Domain + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_creating_custom_sla_domain.html + +--- + +# Creating a custom SLA Domain + +Create a custom SLA Domain to streamline and customize workload protection and management policies. + +## Before you begin + +Do the following: + + * Review the settings for the specific object types listed in [Supported features for RSC workloads](supported_features_for_workloads.html "Supported features for specific RSC workloads when creating or modifying an SLA Domain."). + * Select the workload types that support archival and replication. + * Enable quorum authorization if you plan to use the retention lock feature. + +## About this task + +RSC displays options for custom SLA Domains based on the selected workload type, as each type has unique properties to protect its objects. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click SLA Domains. + +The SLA Domains page appears. + + 4. Click Create SLA Domain. + +Ensure that you understand the provided information about SLA Domains, including snapshot frequency and retention policies, before proceeding to create one. + +The Create SLA Domain wizard appears. + + 5. Click Start on the Create SLA Domain page that describes SLA Domains. + +Selecting Don't show again skips this page the next time you create SLA Domains. + + 6. Select the workload types and click Next. + 7. **Optional:** Turn on Retention Lock. + +Option| Description +---|--- +Governance mode | Requires quorum authorization.Governance mode retention lock appears by default and requires quorum authorization. +Compliance mode | This mode does not support cloud workloads and does not require quorum authorization. Selecting the mandatory acknowledgment allows proceeding to the next step. To enable compliance mode retention lock, contact Rubrik Support. + + 8. Click Next. + 9. Enter a snapshot frequency and a corresponding retention period. + +The snapshot frequency categories are optional, but at least one category must have a value. + + 10. **Optional:** In Snapshot window, enter a time window for the snapshot. + +When you specify a snapshot window, RSC takes the snapshot during the specified time frame. Workloads managed by a Rubrik cluster use the timezone of that Rubrik cluster. Workloads managed by RSC use the UTC timezone. + + 11. In First full snapshot, select a start type. + +Option| Description +---|--- +First opportunity | The first full backup occurs by default when a data source is added. +Custom range | The first full backup occurs within a specified window. + + 12. Click Next. + +The Archival and Replication page appears. + + 13. **Optional:** Select Archival. + +Selecting this option configures archival locations for disaster recovery and long-term retention. + +Click Learn more to explore configuring archival locations for disaster recovery and long-term retention. + + 14. **Optional:** Select Replication. + +Selecting this option configures replication between source and target clusters for data protection and disaster recovery. + +Click Learn more to learn about setting up replication pairings between source and target clusters. + + 15. Click Next. + +The Archival Parameters page appears. + + 16. For archival, configure the source retention, archival location, and the archival threshold. + +For the Archival Threshold, you can select instant archive or specify the number of days from when you want your archival to begin. You can configure multiple archival locations. + +Note: + +For data center workloads, RSC does not tier the log snapshots to cold storage tiers. However, RSC tiers the data snapshots based on the customer-specified policies. + + 17. For instant tiering, select the archival location. + 18. Click Next. + +The Object-Specific Settings page appears. + + 19. Configure object-specific details based on the selected workloads and click Next. + +Amazon DynamoDB tables automatically enable continuous backups. Disabling these backups or changing the retention period in your AWS Management Console can increase your storage and consumption costs. To prevent these higher expenses, keep continuous backups enabled in your AWS Management Console. + +The [Workload-specific settings for SLA Domains](workload_specific_settings_sla_domains.html "Information about workload-specific settings configured when creating or editing SLA Domains for continuous data protection and backups for supported workloads.") topic provides more details about the settings available for a specific workload. + + 20. For Amazon DynamoDB, retrieve the KMS Key alias from your AWS account and enter the details to configure primary backup encryption. + +Important: + +To ensure successful encryption of the backed-up table data, the specified KMS key alias must be present and correctly configured in the target AWS account and the target AWS region. While different accounts and regions have unique underlying KMS keys, these accounts and regions can share a common KMS key alias for this purpose. + + 21. Click Next. + +The Confirmation page appears. + + 22. In SLA Domain name, enter a name to identify the SLA Domain. + 23. **Optional:** In Add Description, enter a description to provide additional context for the SLA Domain. + 24. Review the configuration details and click Create. + +A message that you have created an SLA Domain successfully appears. + +## Results + +RSC creates a custom SLA Domain for the selected workload types. + *[ > ]: and then diff --git a/saas_rsc_dashboards.md b/saas_rsc_dashboards.md new file mode 100644 index 0000000000000000000000000000000000000000..867f2d331718e0da54fcce6eb469512e4814c8f6 --- /dev/null +++ b/saas_rsc_dashboards.md @@ -0,0 +1,13 @@ +# Dashboards + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_dashboards.html + +--- + +releases. Based on the information, # Dashboards + +RSC dashboards provide information about the connected Rubrik clusters and the installed RSC apps. + +The Data Protection dashboard provides information about the current state of the Rubrik clusters connected to RSC. + +The Global dashboard displays summary information for each installed RSC app in a dedicated pane for that app. The panes provide interactive elements for further data discoverability related to the app. diff --git a/saas_rsc_domain_url_change.md b/saas_rsc_domain_url_change.md new file mode 100644 index 0000000000000000000000000000000000000000..8b30dc6d4b3daa666afe87c5f0fc269f799622c0 --- /dev/null +++ b/saas_rsc_domain_url_change.md @@ -0,0 +1,39 @@ +# RSC domain URL change + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_domain_url_change.html + +--- + +# RSC domain URL change + +RSC enables you to change your RSC domain URL without losing any existing metadata or account configurations. This feature ensures continuous workflow continuity, as only the domain URL itself changes, while your data and settings remain unchanged. + +## RSC domain URL change requirements + +You must complete the following actions when changing an RSC domain URL: + + * Allowlisting the new RSC domain URL: You must allowlist the new RSC domain URL to ensure proper connectivity. + * Updating callback URL for SSO: For RSC accounts configured with SSO, you must update the callback URL in your identity provider configuration to match the new RSC domain URL. This ensures successful user authentication after the change. + * Adding reply URLs for Azure integration: For RSC accounts configured with Azure integration, you must add the new RSC domain URL to the reply URLs of your Azure applications. This is important for maintaining secure communication and authentication with Azure services. + +## RSC domain URL change limitations + +Rubrik does not support changing your RSC domain URL under the following conditions: + + * The RSC account requires relocation. + * The RSC account is set up in a multitenant environment. + * The RSC account is configured with cross-account replication. + +## RSC domain URL change process + +To change your RSC domain URL, you must submit a URL change request to Rubrik Support. The Rubrik Support team then completes the following tasks: + + * Creating the new URL: The Rubrik Support team creates the new URL for your RSC domain account. + * Sending email notification to users: After successfully changing the RSC domain URL, an email notification is automatically sent to all users associated with that RSC account, informing them about the change. + +Note: + +If any clusters were previously disconnected from RSC, you must reconnect them using the new RSC domain URL to restore their functionality. + + * Removing old URL: After you confirm that the new RSC domain URL functions correctly, the old URL is removed. + diff --git a/saas_rsc_global_dashboard.md b/saas_rsc_global_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..2bf4b439dee16c8518cde90111d658959a119d19 --- /dev/null +++ b/saas_rsc_global_dashboard.md @@ -0,0 +1,23 @@ +# Global Dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_global_dashboard.html + +--- + +# Global Dashboard + +The Global dashboard displays summary information for each installed RSC app. + +Information type | Description +---|--- +Data Protection | Information on: + + * Protected Objects + * Data Centers + * Tasks (Failed, Completed, and Canceled) + + +Data Threat Analytics | Displays the number of objects and anomaly events. +Data Security Posture | Displays the number of open access sensitive files, stale sensitive files, and sensitive files. +Orchestrated Recovery | Displays the percentage of enabled, Recovery Plans ready, and Recovery Plans that have failed tests in the last 90 days. + *[ > ]: and then diff --git a/saas_rsc_hc.md b/saas_rsc_hc.md new file mode 100644 index 0000000000000000000000000000000000000000..a732219d2f94946a68cde82bd9c51a99b3ccbad9 --- /dev/null +++ b/saas_rsc_hc.md @@ -0,0 +1,16 @@ +# RSC Help Center + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_hc.html + +--- + +# RSC Help Center + +You can use the Help Center in RSC to search product documentation, access the Rubrik knowledge base, and create support cases. + +The Rubrik Security Cloud (RSC) Help Center provides you with self-help support resources within RSC. In the Help Center, you can: + + * Search product documentation and the Rubrik knowledge base. + * Engage Rubrik Support by opening a support ticket. + +Opening a support ticket through the Help Center requires that you be a Rubrik customer. If you are accessing Rubrik products through a partner, you can contact your partner support to file a support ticket. diff --git a/saas_rsc_hc_creating_support_case.md b/saas_rsc_hc_creating_support_case.md new file mode 100644 index 0000000000000000000000000000000000000000..f9cc58cd14a03a1628b1df156b335975c01ab329 --- /dev/null +++ b/saas_rsc_hc_creating_support_case.md @@ -0,0 +1,91 @@ +# Creating a support case through the RSC Help Center + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_hc_creating_support_case.html + +--- + +# Creating a support case through the RSC Help Center + +If you need to engage Rubrik Support, you can create a support case through the RSC Help Center. + +## Before you begin + +You must meet the following conditions to create a support case: + + * Be a Rubrik customer. If you are accessing Rubrik products through a partner, contact your partner support to create a support case. + * Provide a phone number or email address. If you are using an email address, it must match the email address on file with Rubrik Support. + * Have an existing Rubrik Support portal account with the same email as your RSC login. Note that the email is different from the username used to log in to the Support portal. + * Have only one Rubrik Support portal account using the email address. + +## Procedure + + 1. Log in to RSC. + 2. On the menu bar, click ?. + +The Help Center window appears. + + 3. Scroll to the bottom of the window and click Create a support case. + +The New Support Case dialog box appears. + + 4. In Subject, enter a brief summary of the question or issue. + +Links to related Rubrik Support knowledge base articles or product documentation appear in Recommended Help. + + 5. In Type, select the support case type. + +Type| Description +---|--- +Documentation | Requests to update product documentation +Hardware | Requests involving Rubrik hardware +Other | Other support case types not listed +Product enhancement | Requests for enhancement (RFE) of product features or functionality +Product question | Questions about product operations and functions +Software | Requests involving Rubrik software + + 6. In Priority, select the support case priority. + +Priority| Description +---|--- +P1 - Critical | System and operations are not accessible. +P2 - High | System is operational, but is working with reduced functionality. +P3 - Medium | System is operational, but has experienced a minor issue not affecting overall functionality. +P4 - Low | General question. + + 7. In Cluster Name, select a Rubrik cluster. + +Select a Rubrik cluster if you have identified that the issue exists on a specific cluster. + + 8. In Preferred Contact Method, select a contact method. + * Email + * Phone + 9. In Description, enter the support case details. + 10. Click Submit Case. + +Your new support case number appears in the New Support Case window. + + 11. In Provide Additional Information, click Upload File to upload a file attachment. + +You can upload a total of 7 MB for each support case. + +Files larger than 7 MB must be uploaded through the Support portal. The Support portal can support file attachments up to 5 GB. + + 12. In Grant Account Access to Rubrik Support, confirm or open a support tunnel for Rubrik Support access. + +Option| Description +---|--- +A support tunnel is open on the Rubrik cluster | The CDM cluster access option is automatically selected. The cluster name and tunnel access duration appear. The Access Duration field uses the support tunnel values configured in RSC. +A support tunnel is not open on the Rubrik cluster | Select CDM cluster access and configure the time for which the Rubrik Support team will have access to your RSC instance in Access Duration. + +If the Rubrik cluster is disconnected, RSC displays a warning message stating that no actions can occur on the disconnected cluster. + + 13. Click Update Case. + +## Results + +RSC creates a support case with the new information. + +## What to do next + +Log in to the Rubrik Support portal to view the support case status and to provide any further case updates. + *[ > ]: and then diff --git a/saas_rsc_insights.md b/saas_rsc_insights.md new file mode 100644 index 0000000000000000000000000000000000000000..71b618fb279ffd2b332e8a488f5b2cec73591e15 --- /dev/null +++ b/saas_rsc_insights.md @@ -0,0 +1,21 @@ +# RSC Insights + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_insights.html + +--- + +# RSC Insights + +RSC Insights identifies problems in your Rubrik environment, proposes solutions, and provides actionable information to minimize the need for help from Rubrik Support. + +RSC Insights monitors infrastructure health by identifying anomalies, errors, or changes in your Rubrik environment and providing important information and suggested solutions. + +RSC Insights adheres to the rules of RBAC by allowing only those users with explicit access to objects to view the object-related insights. + +RSC Insights has the following default behavior: + + * Insights are updated every hour based on the data. + * Users can dismiss insights. + * Insights disappear automatically when the problem no longer exists. + * Insights are removed after 30 days. If the underlying problem persists, the insight reappears. + diff --git a/saas_rsc_security.md b/saas_rsc_security.md new file mode 100644 index 0000000000000000000000000000000000000000..9b762339ca058f150777385943d1bbc6c6214064 --- /dev/null +++ b/saas_rsc_security.md @@ -0,0 +1,12 @@ +# Security settings + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_security.html + +--- + +# Security settings + +Rubrik Security Cloud provides enhanced security authentication services. + +RSC offers authentication services that provides additional security for applications and data. + *[ > ]: and then diff --git a/saas_rsc_settings_menu.md b/saas_rsc_settings_menu.md new file mode 100644 index 0000000000000000000000000000000000000000..ea81afd8c31b6e3b3a7891abd19a4189f0388c95 --- /dev/null +++ b/saas_rsc_settings_menu.md @@ -0,0 +1,42 @@ +# Settings menu + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_settings_menu.html + +--- + +# Settings menu + +You can use the RSC Settings menu to access and configure the global settings for all your Rubrik applications. + +You can access the Settings menu by clicking in RSC. + +The following table describes available settings and tasks in the Settings menu. Menu item | Description +---|--- +Quorum Authorization | Enforces the requirement to have approvals from a minimum number of users before allowing critical, data-modifying operations to proceed. +Snapshots | + + * Provides access to snapshot and backup information for protected objects and relic objects. + * Enables retention policy management and the ability to place a legal hold on snapshots. + + +Data Sources | Manages data sources connected to RSC for workload protection. +Cloud Accounts | + + * Enables the addition, viewing, editing, and deletion of cloud accounts. + * Manages Exocompute settings. + + +Archival & Storage | Manages archival locations for data centers and for cloud native workloads. +Replication Pairings | Manages replication tasks. +Integrations | Provides an option to configure and manage your third-party SaaS integrations. +Users & Access | Provides RBAC and other methods for authenticating a user account. +Notifications | Manages emails, webhooks, SNMP, and syslogs. +Security | Manages SSO, IP allowlists, multifactor authentication, and account lockout in RSC. +Organizations | Provides logical isolation of shared compute, storage, and network resources in such a way that each organization can view and access only data that belongs to that organization, especially for shared infrastructure platforms. +Clusters | Provides options to upgrade existing Rubrik CDM version and update general settings for a Rubrik cluster. +Customer Support | Opens or closes a support tunnel on any cluster and runs network diagnostics. +Data Threat Analytics | Provides options to enable LLM Analysis for Anomaly Detection and enable anomaly detection and threat monitoring for clusters. +Data Security Posture | Provides an option to enable the data discovery feature for clusters. +License Management | Provides the license information about clusters. +API Playground | Opens the API Playground to browse, explore, and run GraphQL API operations. +Ruby | Provides an option to enable Ruby.Ruby is a generative AI assistant that extends Rubrik Security Cloud capabilities. You can interact with Ruby to use and manage RSC security features. diff --git a/saas_rsc_settings_menu_2.md b/saas_rsc_settings_menu_2.md new file mode 100644 index 0000000000000000000000000000000000000000..54ab505207295165ca4a092cd93297b22dca30b9 --- /dev/null +++ b/saas_rsc_settings_menu_2.md @@ -0,0 +1,42 @@ +# Settings menu + +Source: https://docs.rubrik.com/en-us/saas/saas/rsc_settings_menu_2.html + +--- + +# Settings menu + +You can use the RSC Settings menu to access and configure the global settings for all your Rubrik applications. + +You can access the Settings menu by clicking in RSC. + +The following table describes available settings and tasks in the Settings menu. Menu item | Description +---|--- +Quorum Authorization | Enforces the requirement to have approvals from a minimum number of users before allowing critical, data-modifying operations to proceed. +Snapshots | + + * Provides access to snapshot and backup information for protected objects and relic objects. + * Enables retention policy management and the ability to place a legal hold on snapshots. + + +Data Sources | Manages data sources connected to RSC for workload protection. +Cloud Accounts | + + * Enables the addition, viewing, editing, and deletion of cloud accounts. + * Manages Exocompute settings. + + +Archival & Storage | Manages archival locations for data centers and for cloud native workloads. +Replication Pairings | Manages replication tasks. +Integrations | Provides an option to configure and manage your third-party SaaS integrations. +Users & Access | Provides RBAC and other methods for authenticating a user account. +Notifications | Manages emails, webhooks, SNMP, and syslogs. +Security | Manages SSO, IP allowlists, multifactor authentication, and account lockout in RSC. +Organizations | Provides logical isolation of shared compute, storage, and network resources in such a way that each organization can view and access only data that belongs to that organization, especially for shared infrastructure platforms. +Clusters | Provides options to upgrade existing Rubrik CDM version and update general settings for a Rubrik cluster. +Customer Support | Opens or closes a support tunnel on any cluster and runs network diagnostics. +Data Threat Analytics | Provides options to enable LLM Analysis for Anomaly Detection and enable anomaly detection and threat monitoring for clusters. +Data Security Posture | Provides an option to enable the data discovery feature for clusters. +License Management | Provides the license information about clusters. +API Playground | Opens the API Playground to browse, explore, and run GraphQL API operations. +Ruby | Provides an option to enable Ruby.Ruby is a generative AI assistant that extends Rubrik Security Cloud capabilities. You can interact with Ruby to use and manage RSC security features. diff --git a/saas_rubrik_application_privileges.md b/saas_rubrik_application_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..f5ae529c63d2a221378664166be03b695548a49f --- /dev/null +++ b/saas_rubrik_application_privileges.md @@ -0,0 +1,53 @@ +# Rubrik application privileges + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_application_privileges.html + +--- + +# Rubrik application privileges + +Details of application-specific privileges that are available for assignment to different roles in RSC. + +Application | Available privileges +---|--- +Orchestrated Recovery | + + * ViewOrchestrated Recoveryapplication + * Manage Recovery Plans in Orchestrated Recovery + * Manage recoveries in Orchestrated Recovery + + +Data Security Posture | + + * View Data Security Posture results + * Manage data classification settings + * Download classification results + * View ServiceNow Integrations + * Manage ServiceNow Integrations + + +Anomaly Detection | + + * View Anomaly Detection results + * View file details + * Download suspicious files for forensics + * Manage Anomaly Detection + + +Threat Hunt | + + * View threat hunt results + * Create threat hunt + + +Data Security Command Center | + + * View security scores + + +Threat Containment | + + * Add files to quarantine and remove files from quarantine + * Recover quarantined files and snapshots + + *[ > ]: and then diff --git a/saas_rubrik_backup_service.md b/saas_rubrik_backup_service.md new file mode 100644 index 0000000000000000000000000000000000000000..a49eab5b44e39b6afb9e193035bd8f4f838b63d7 --- /dev/null +++ b/saas_rubrik_backup_service.md @@ -0,0 +1,32 @@ +# Rubrik Backup Service + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_backup_service.html + +--- + +# Rubrik Backup Service + +The Rubrik Backup Service is software installed on a host that coordinates activity between the Rubrik cluster and the host. + +Rubrik Backup Service (RBS) is a component of the Rubrik solution that you install on the operating system of a protected workload. Working in conjunction with Rubrik CDM, RBS interacts with both the operating system and the protected workload to ensure consistent data backups and facilitate recovery operations. + +## Installation prerequisite + +You must install RBS on the host before you can back up data from a protected workload. + +## Key tasks of RBS + +RBS performs a wide variety of tasks, such as: + + * Physical system protection: Backing up and recovering files for Windows, Linux, AIX, and Solaris physical systems. + * Database protection: Backing up and recovering databases for SQL, Oracle, HANA, DB2, and MongoDB. + * Hyper-V protection: Backing up and recovering Hyper-V virtual machines. + * Microsoft Exchange protection: Backing up and recovering Microsoft Exchange (hypervisor or physical volume). + * Virtual machine operations: Quiescing virtual machines for backups. + * Streamlined virtual machine recovery: Recovering files to virtual machines instead of using native hypervisor tools. + * Windows volume protection: Backing up and recovering volumes for Windows. + +## RBS software distribution + +You can download the RBS software directly from the Rubrik cluster. Alternatively, you can download it once and push it to hosts. Accessing software directly from the Rubrik cluster ensures secure authentication between the Rubrik cluster and the hosted RBS deployment. + *[ > ]: and then diff --git a/saas_rubrik_backup_service_2.md b/saas_rubrik_backup_service_2.md new file mode 100644 index 0000000000000000000000000000000000000000..800769071907492ef61990a117ada5f3a6f67005 --- /dev/null +++ b/saas_rubrik_backup_service_2.md @@ -0,0 +1,32 @@ +# Rubrik Backup Service + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_backup_service_2.html + +--- + +# Rubrik Backup Service + +The Rubrik Backup Service is software installed on a host that coordinates activity between the Rubrik cluster and the host. + +Rubrik Backup Service (RBS) is a component of the Rubrik solution that you install on the operating system of a protected workload. Working in conjunction with Rubrik CDM, RBS interacts with both the operating system and the protected workload to ensure consistent data backups and facilitate recovery operations. + +## Installation prerequisite + +You must install RBS on the host before you can back up data from a protected workload. + +## Key tasks of RBS + +RBS performs a wide variety of tasks, such as: + + * Physical system protection: Backing up and recovering files for Windows, Linux, AIX, and Solaris physical systems. + * Database protection: Backing up and recovering databases for SQL, Oracle, HANA, DB2, and MongoDB. + * Hyper-V protection: Backing up and recovering Hyper-V virtual machines. + * Microsoft Exchange protection: Backing up and recovering Microsoft Exchange (hypervisor or physical volume). + * Virtual machine operations: Quiescing virtual machines for backups. + * Streamlined virtual machine recovery: Recovering files to virtual machines instead of using native hypervisor tools. + * Windows volume protection: Backing up and recovering volumes for Windows. + +## RBS software distribution + +You can download the RBS software directly from the Rubrik cluster. Alternatively, you can download it once and push it to hosts. Accessing software directly from the Rubrik cluster ensures secure authentication between the Rubrik cluster and the hosted RBS deployment. + *[ > ]: and then diff --git a/saas_rubrik_backup_service_3.md b/saas_rubrik_backup_service_3.md new file mode 100644 index 0000000000000000000000000000000000000000..863b90fc7154b18e6afedcb4ced89605f96bc3d3 --- /dev/null +++ b/saas_rubrik_backup_service_3.md @@ -0,0 +1,32 @@ +# Rubrik Backup Service + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_backup_service_3.html + +--- + +# Rubrik Backup Service + +The Rubrik Backup Service is software installed on a host that coordinates activity between the Rubrik cluster and the host. + +Rubrik Backup Service (RBS) is a component of the Rubrik solution that you install on the operating system of a protected workload. Working in conjunction with Rubrik CDM, RBS interacts with both the operating system and the protected workload to ensure consistent data backups and facilitate recovery operations. + +## Installation prerequisite + +You must install RBS on the host before you can back up data from a protected workload. + +## Key tasks of RBS + +RBS performs a wide variety of tasks, such as: + + * Physical system protection: Backing up and recovering files for Windows, Linux, AIX, and Solaris physical systems. + * Database protection: Backing up and recovering databases for SQL, Oracle, HANA, DB2, and MongoDB. + * Hyper-V protection: Backing up and recovering Hyper-V virtual machines. + * Microsoft Exchange protection: Backing up and recovering Microsoft Exchange (hypervisor or physical volume). + * Virtual machine operations: Quiescing virtual machines for backups. + * Streamlined virtual machine recovery: Recovering files to virtual machines instead of using native hypervisor tools. + * Windows volume protection: Backing up and recovering volumes for Windows. + +## RBS software distribution + +You can download the RBS software directly from the Rubrik cluster. Alternatively, you can download it once and push it to hosts. Accessing software directly from the Rubrik cluster ensures secure authentication between the Rubrik cluster and the hosted RBS deployment. + *[ > ]: and then diff --git a/saas_rubrik_cc_es_on_saas.md b/saas_rubrik_cc_es_on_saas.md new file mode 100644 index 0000000000000000000000000000000000000000..2ee2c830fd129b46ef2d9e1c71e9522d15c97899 --- /dev/null +++ b/saas_rubrik_cc_es_on_saas.md @@ -0,0 +1,17 @@ +# Rubrik Cloud Cluster Elastic Storage + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_cc_es_on_saas.html + +--- + +# Rubrik Cloud Cluster Elastic Storage + +You can use Rubrik Security Cloud to provision a Rubrik Cloud Cluster Elastic Storage on AWS or a Rubrik Cloud Cluster Elastic Storage on Azure. + +Rubrik Cloud Cluster Elastic Storage (ES) runs on a single node, or it runs on three or more nodes. Rubrik CDM 9.0.1 and later versions support single-node configuration. Rubrik CDM does not support a two-node configuration. Provisioning a Rubrik Cloud Cluster Elastic Storage creates a virtual Rubrik Cloud Cluster running in a virtual private cloud, providing data protection for hosts and applications. + +Because Rubrik Cloud Cluster ES stores data in cloud object storage, Rubrik Cloud Cluster ES achieves fault tolerance for either one node or for three or more nodes. + +Note: + +Rubrik Security Cloud support requires provisioning Rubrik Cloud Cluster ES on Rubrik CDM 8.0.2 or later. diff --git a/saas_rubrik_cdm_release_information.md b/saas_rubrik_cdm_release_information.md new file mode 100644 index 0000000000000000000000000000000000000000..cc99417eeb8e40f7da5150097afc73ef1a58c05f --- /dev/null +++ b/saas_rubrik_cdm_release_information.md @@ -0,0 +1,14 @@ +# Rubrik CDM release information + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_cdm_release_information.html + +--- + +# Rubrik CDM release information + +The Rubrik CDM release information includes details such as release date, end of support date, and current adoption rate. You can use this information to compare the available versions for making a decision about upgrading. + +The decision to upgrade a Rubrik cluster is determined based on factors such as the current Rubrik CDM version, the protected workloads, and the need to upgrade to a specific release. After considering these factors, you can decide whether to upgrade the Rubrik CDM to the latest or a specific release. + +Rubrik does not provide explicit recommendations for CDM releases or specify the exact percentage of customer adoption. + *[ > ]: and then diff --git a/saas_rubrik_cdm_upgrade_using_cli.md b/saas_rubrik_cdm_upgrade_using_cli.md new file mode 100644 index 0000000000000000000000000000000000000000..c30309d8a4cab3ec2218e0b74e5b84573d3d3562 --- /dev/null +++ b/saas_rubrik_cdm_upgrade_using_cli.md @@ -0,0 +1,24 @@ +# Rubrik CDM software upgrade using CLI + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_cdm_upgrade_using_cli.html + +--- + +# Rubrik CDM software upgrade using CLI + +To take advantage of the latest features and improvements that Rubrik offers, you can upgrade the Rubrik CDM version running on any connected Rubrik cluster to the latest version using Rubrik CLI. + +After you have reviewed the most recent versions of Rubrik CDM software and determined that upgrading to the latest version is the best course of action, you can initiate the upgrade procedure through Rubrik CLI. + +You can transfer the upgrade package and the associated signature file to one of the nodes of the Rubrik cluster using one of the following methods: + + * Rubrik CLI session to access the Rubrik Support Portal + * Rubrik CLI session to access a specified URL + * SFTP session to access an SFTP server + +After copying the upgrade package and the associated signature file to a node, you can start upgrading the Rubrik cluster from that node. + +Note: + +Rubrik does not support using CLI commands to upgrade Rubrik clusters to the Rubrik CDM software version 9.0 or later. + *[ > ]: and then diff --git a/saas_rubrik_cluster_direct_access_config.md b/saas_rubrik_cluster_direct_access_config.md new file mode 100644 index 0000000000000000000000000000000000000000..302bfd734ec7d3574988a1b64f8f0b09274299ec --- /dev/null +++ b/saas_rubrik_cluster_direct_access_config.md @@ -0,0 +1,19 @@ +# Rubrik cluster direct access configuration + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_cluster_direct_access_config.html + +--- + +# Rubrik cluster direct access configuration + +You can configure the IP address or the fully qualified domain name of a managing load balancer to enable direct access to a Rubrik cluster. + +Configuring a specific IP address or fully qualified domain name (FQDN) for a Rubrik cluster establishes its primary access point. After you configure the IP address or FQDN of the cluster, you can enable direct access to the cluster to allow the following: + + * Visiting the cluster + * Downloading the Rubrik Backup Service (RBS) software from the cluster + +If you do not explicitly configure an IP address or FQDN, [saas] automatically selects the management IP address of one of the nodes in the cluster for direct cluster access. + +For example, if a load balancer manages incoming traffic to a cluster and a firewall separates them, direct access to individual cluster nodes might be prevented. In these scenarios, configuring the FQDN of the load balancer is required to enable direct cluster access. + *[ > ]: and then diff --git a/saas_rubrik_cluster_upgrade_reports.md b/saas_rubrik_cluster_upgrade_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..ad6a330feecf121f7dd799fe142dfbff8ee47a75 --- /dev/null +++ b/saas_rubrik_cluster_upgrade_reports.md @@ -0,0 +1,34 @@ +# Rubrik cluster upgrade reports + +Source: https://docs.rubrik.com/en-us/saas/saas/rubrik_cluster_upgrade_reports.html + +--- + +# Rubrik cluster upgrade reports + +The Rubrik cluster upgrade report is downloaded as a CSV file and provides a variety of information about the cluster upgrades. + +Metric | Description +---|--- +Cluster name | The name of the Rubrik cluster. +Installed version | The current Rubrik CDM version of the cluster. +Downloaded version | The Rubrik CDM version of the downloaded tarball on the cluster. +Previous version | The previous version of Rubrik CDM on the cluster before the upgrade. +Last upgrade start time* | The time at which the last upgrade was started.The last upgrade refers to the most recent version upgrade. +Last upgrade end time* | The time at which the last upgrade was completed. +Upgrade status | The upgrade status of the Rubrik cluster. For example, if the Rubrik cluster is ready for upgrade, the Upgrade status includes the status of the last upgrade, upgrade scheduled at time*, and so forth. +Last upgrade duration | The time taken by the last upgrade to complete. +Location | The location of the Rubrik cluster. +Cluster type | The type of the Rubrik cluster. +Runway remaining | The estimated number of days for the cluster to reach 100% capacity. +Node count | The number of nodes in the cluster. +Last upgrade attempts | The total number of attempts made to successfully upgrade the cluster from previous version to current version.This includes unsuccessful and successful upgrade attempts. +Average upgrade time | The average duration of all successful upgrades for the cluster for the past 1 year.This does not include the time for failed upgrades. +Average outage time | The average duration of all upgrades for the cluster that had one or more failures during upgrades for the past 1 year. +Last download duration | The time taken for the last successful download from RSC. +Average download time | The average duration of all successful downloads from RSC for the past 1 year. + +Note: + +Time indicated in the Rubrik cluster upgrade report (fields indicated with * in the table above) is in UTC time. + *[ > ]: and then diff --git a/saas_ruby_data_security_posture.md b/saas_ruby_data_security_posture.md new file mode 100644 index 0000000000000000000000000000000000000000..ee24b61ee0c396dd7d8d60e88175c55425fbca02 --- /dev/null +++ b/saas_ruby_data_security_posture.md @@ -0,0 +1,23 @@ +# Ruby for Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/saas/ruby_data_security_posture.html + +--- + +# Ruby for Data Security Posture + +You can use Ruby, a generative AI assistant that extends RSC capabilities, to significantly speed up the investigation process in Data Security Posture. + +Ruby can answer your Data Security Posture questions, find evidence of an issue, and help remediate the problem. Ruby reduces the time and effort involved in identifying the most important problems to solve. This includes investigating each case, finding the evidence, compiling the remediation steps, and finally filing a ticket. All of these steps can be easily and efficiently accomplished by using Ruby, reducing a task that could potentially take days, or even weeks to just a few minutes. + +You can access Ruby from the Overview widget in the Data Security Posture dashboard. Using Ruby can help you understand violations in Data Security Posture. Ruby helps to investigate impacted data, dismiss the violation, or assign an Microsoft Information Protection (MIP) label. Accessing Ruby in the Insights tab provides you with information on objects with hits and user access insights. Ruby provides the following: + + * An ordered list of tasks for the analyst to focus on + * Summarized key details for each case + * Specific details for guiding you through a specific case + * Step-by-step remediation guidance + +Note: + +AI-generated content may contain errors or inaccuracies. Independent verification of such content is strongly recommended. + *[ > ]: and then diff --git a/saas_rules_archiving_replication_policies.md b/saas_rules_archiving_replication_policies.md new file mode 100644 index 0000000000000000000000000000000000000000..6906dc1115b6d6e6afe4180a0b30e3cf6f7251e8 --- /dev/null +++ b/saas_rules_archiving_replication_policies.md @@ -0,0 +1,17 @@ +# Rules for archiving and replication policies + +Source: https://docs.rubrik.com/en-us/saas/saas/rules_archiving_replication_policies.html + +--- + +# Rules for archiving and replication policies + +When configuring an SLA Domain, Rubrik clusters that are selected for archiving in the archival policy do not appear as replication target options in the replication policy. + +RSC enforces specific rules for creating a valid SLA Domain that includes both archival and replication policies for workloads managed through a Rubrik cluster: + + * When the archival policy is configured before the replication policy, the Rubrik clusters selected for archiving serve as the source clusters for replication. As a result, any cluster selected for archiving cannot be selected as the replication target. + * When archiving is not enabled, the replication target selected in the replication policy serves as the global target for all Rubrik clusters. + * When the archival policy is configured after configuring the replication policy, the Rubrik cluster selected as the global replication target cannot be selected for archiving in the archival policy. + + *[ > ]: and then diff --git a/saas_saas_workloads.md b/saas_saas_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..c6e22a4c4d096e1c0554c72efd097cede1943a6c --- /dev/null +++ b/saas_saas_workloads.md @@ -0,0 +1,13 @@ +# SaaS workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/saas_workloads.html + +--- + +# SaaS workloads + +RSC protection for SaaS workloads simplifies protecting and managing backups for SaaS application instances. + +RSC protection for SaaS workloads simplifies managing backups for SaaS workloads to restore data when the data is either compromised or lost. You can back up and restore Jira or Salesforce data while keeping parent-child relationships intact. You can automatically back up data at either 12-hour or 24-hour intervals or back up data on demand. + +You can also monitor your data and analyze data to determine if and when data was lost, which helps streamline investigations and recoveries. diff --git a/saas_sai_diagnostics_resolution.md b/saas_sai_diagnostics_resolution.md new file mode 100644 index 0000000000000000000000000000000000000000..62dd033a3ecf3d0994008a9a2ac22765c57930f1 --- /dev/null +++ b/saas_sai_diagnostics_resolution.md @@ -0,0 +1,15 @@ +# RSC Insights diagnostics and resolution + +Source: https://docs.rubrik.com/en-us/saas/saas/sai_diagnostics_resolution.html + +--- + +# RSC Insights diagnostics and resolution + +RSC Insights helps diagnose and resolve issues found in your Rubrik clusters. + +Besides providing monitoring and status information, RSC Insights can help troubleshoot identified issues. + +Each insight includes a description of an identified issue, steps to resolve it, and in some cases reference documentation or articles on the subject. + +After attempting a solution, verify that the issue is resolved. diff --git a/saas_sai_issue_types_severities.md b/saas_sai_issue_types_severities.md new file mode 100644 index 0000000000000000000000000000000000000000..e68c04e8ca451843a3dfb046bad0a5667a535381 --- /dev/null +++ b/saas_sai_issue_types_severities.md @@ -0,0 +1,24 @@ +# Issue types and severities + +Source: https://docs.rubrik.com/en-us/saas/saas/sai_issue_types_severities.html + +--- + +# Issue types and severities + +Information about the insight types and severities used to describe each insight. + +When viewing insights on the Clusters page, you can filter them by dismissal status, type, and severity. + +The following table describes the insight types for RSC Insights. Insight Type | Description +---|--- +Issue | Notification about an event that might affect your operation. +Info | Notification for information only. + +The following table describes the severity types for RSC Insights. Insight Severity | Description +---|--- +No impact | Event with no impact to your operation. This notification is for information only. +Minor impact | Event that might have a small impact on your operation. +Major impact | Event that might have significant impact on your operation. +Critical impact | Event that might have a very serious impact on your operation. This requires immediate attention. + *[ > ]: and then diff --git a/saas_sai_viewing_insights.md b/saas_sai_viewing_insights.md new file mode 100644 index 0000000000000000000000000000000000000000..edd3df111a1c50a997caaffbb9ec2e1a362295a6 --- /dev/null +++ b/saas_sai_viewing_insights.md @@ -0,0 +1,31 @@ +# Viewing insights + +Source: https://docs.rubrik.com/en-us/saas/saas/sai_viewing_insights.html + +--- + +# Viewing insights + +View anomalies or other issues along with actionable insights for your Rubrik clusters. + +## About this task + +Use RSC Insights to monitor the health of your clusters, understand the impact, and view resolution steps for the issues encountered. + +The insights are available for Rubrik clusters in the grid view. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + 3. On the navigation bar, click Infrastructure > Clusters. + 4. Select the grid view. + +The RSC Insights panel shows detected issues and impacted clusters for each insight. + + 5. **Optional:** Filter the insights by clicking Filter by criteria. + +## Results + +RSC Insights displays any issues found along with relevant resolution information. + *[ > ]: and then diff --git a/saas_sap_hana_architecture.md b/saas_sap_hana_architecture.md new file mode 100644 index 0000000000000000000000000000000000000000..582fcf73a95a54ea19ee15083e28b543227dbd8e --- /dev/null +++ b/saas_sap_hana_architecture.md @@ -0,0 +1,27 @@ +# SAP HANA protection architecture + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_architecture.html + +--- + +# SAP HANA protection architecture + +RSC integrates with SAP HANA through its native Backint client, which is deployed automatically on the SAP HANA host when the RBS or an external tool is deployed. + +The following diagram describes how RSC integrates with SAP HANA to provide backup functions. + + 1. Rubrik Cluster on Public Cloud or On-Premises + 2. Data written directly to Rubrik SDFS deployed on Public Clouds or On-Premises + 3. SAP HANA host in Cloud or On-Premises + 4. Backup process through the Rubrik Backup Service (RBS) software + 5. Backup process through external tools such as SAP HANA Studio, Cockpit, API calls, cron jobs, or direct command-line execution + +The following list describes how each component contributes to backup functionality: + + * The RBS software is deployed on the host or cloud virtual machine running the SAP HANA database. + * The Rubrik native Backint client leverages the native APIs of SAP HANA to provide backup and restore operations. + * RSC uses the control path flow to retrieve the metadata and then uses this metadata to add the SAP HANA host and system and discover the databases. + * RSC uses the data path flow to ingest the data to the Rubrik SDFS and retrieve the backups for restore. + +The same architecture and functionalities are used across on-premises and supported public clouds. + *[ > ]: and then diff --git a/saas_sap_hana_archival.md b/saas_sap_hana_archival.md new file mode 100644 index 0000000000000000000000000000000000000000..68d8499ad7ee6344b5922a4490155d07f0928dc8 --- /dev/null +++ b/saas_sap_hana_archival.md @@ -0,0 +1,21 @@ +# SAP HANA archival + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_archival.html + +--- + +# SAP HANA archival + +RSC allows you to include an archival policy in an SLA Domain for archiving SAP HANA snapshots to an archival location. + +You can configure an SLA Domain with an archival policy. The archival policy includes the archival location, the archival threshold, the local retention, and the Instant Archive settings. After you assign an SLA Domain with an archival policy to an SAP HANA workload, the snapshots will be taken and uploaded to the archival location according to the configured settings. + +You can also use the archived snapshot for recovery of the SAP HANA workload. To recover a database, the snapshot must be available on the local Rubrik cluster. If the snapshot has expired on the local Rubrik cluster, you can download the snapshot from the archival location and perform recovery of the workload. + +RSC provides the options for: + + * Downloading a full, incremental, or differential snapshot + * Downloading full and log snapshots for point-in-time recovery + +The archival feature is available only for Rubrik clusters running Rubrik CDM version 8.0.1 or later. Rubrik supports configuring an SLA Domain with multiple archival locations for SAP HANA workload for Rubrik clusters running Rubrik CDM version 9.3.0 or later. + *[ > ]: and then diff --git a/saas_sap_hana_database_details.md b/saas_sap_hana_database_details.md new file mode 100644 index 0000000000000000000000000000000000000000..1be11a3c077721fa9b2f01c6f70edd69c5e2d958 --- /dev/null +++ b/saas_sap_hana_database_details.md @@ -0,0 +1,35 @@ +# SAP HANA database details + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_database_details.html + +--- + +# SAP HANA database details + +The details page for an SAP HANA database displays the protection status, snapshot calendar, and protection events list. + +Field | Description +---|--- +SLA Domain | The SLA Domain assigned to the SAP HANA database. +Object Details | Displays the following information: + + * Object Type – The region in which the database is located. + * Cluster – The zone within the region where the database is located. + * SID – The ID assigned to the SAP HANA system. + * Instance Number – The instance number assigned to the SAP HANA system. + * Location – The location of the database. + * Log Backup Interval – The log backup frequency specified by the SAP HANA native tool. + * Backup Trigger - The backup trigger type is either RSC or an external tool.Note: You can change the backup trigger method directly from the Backup Trigger column. + + +Snapshots | Displays the following information: + + * Total snapshots taken over time. + * Number of on-demand snapshots taken. + * Oldest snapshot for this database. + * Last snapshot taken. + * Calendar view of the snapshots. + +The day view of the snapshot calendar displays the snapshot type and the time it was taken. +Events tab | Displays the recovery and snapshot events. + *[ > ]: and then diff --git a/saas_sap_hana_protection.md b/saas_sap_hana_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..f32cf6dd88ccac4707801a1ed035cf5176da27df --- /dev/null +++ b/saas_sap_hana_protection.md @@ -0,0 +1,33 @@ +# SAP HANA databases + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_protection.html + +--- + +# SAP HANA databases + +RSC enables administrators to implement backup policies on SAP HANA databases running on public clouds and on-premises. + +With SAP HANA protection, RSC automates the discovery of SAP HANA databases and allows administrators to configure SLA Domain-driven policies for backup. The backup for SAP HANA databases can be triggered in two ways: + + * Rubrik-managed backup trigger: This default and recommended method lets Rubrik initiate and manage backups based on the frequency defined in the SLA Domain. + * External backup trigger: You initiate backups from external tools, such as SAP HANA Studio, Cockpit, API calls, cron jobs, or command-line execution. + +Note: + +You can contact Rubrik Support to enable the external backup trigger feature in your RSC domain. Rubrik supports this feature only on Rubrik clusters running Rubrik CDM version 9.4 or later. + +RSC supports protecting SAP HANA databases running on on-premises and on AWS, Azure, and GCP public clouds. + +RSC provides the following key capabilities for backing up and protecting SAP HANA databases: + + * Automatic discovery of databases + * Rubrik Backup Service (RBS) software deployment on the SAP HANA host manages the backint configuration + * Support for SAP HANA scale-up and scale-out deployments + * SLA Domain-driven backup frequency, retention, and replication + * SAP HANA default log-backup frequency of 15 minutes + * Single pane for managing protection, reporting, and compliance + * SAP HANA administrators can also perform on-demand backup and restore operations using SAP HANA Studio or SAP HANA Cockpit + * Option for external backup triggers, which enables using external tools to initiate scheduled backups + +The Events page displays information about SAP HANA system events by event type and object type. The Reporting feature enables the creation of views of the most commonly used system metrics. You can use the data gathered in the reports to perform audits and data management planning. diff --git a/saas_sap_hana_recovery.md b/saas_sap_hana_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..f68836fe9379696096db71d6159ff69e4f225310 --- /dev/null +++ b/saas_sap_hana_recovery.md @@ -0,0 +1,29 @@ +# SAP HANA recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_recovery.html + +--- + +# SAP HANA recovery + +RSC provides point-in-time, full snapshot, and system copy recovery methods for SAP HANA databases. You can recover SAP HANA databases by using RSC or SAP HANA Studio. + +Note: + +SAP HANA recovery using RSC is available only for Rubrik clusters running Rubrik CDM version 9.4 or later. + +RSC recovery capabilities leverage database snapshots, which are full database copies captured at a specific moment, in conjunction with transaction logs, which are records of continuous database changes. This combination enables efficient and reliable recoveries, including point-in-time recovery, full snapshot recovery, and system copy restores. + +Conversely, recovery using SAP HANA Studio provides GUI-driven database recovery options. This method primarily involves direct interaction with database backups and logs, either through a backup catalog or directly through file systems. + +## Considerations for SAP HANA database recovery + +Before initiating any recovery process, you must consider the following points, irrespective of the selected recovery method: + + * Transaction log backups: You must ensure that transaction log backups are performed regularly. Consistent transaction log backups are important for continuous point-in-time database recoverability. + * Software version compatibility: The SAP HANA database software version on the target system must be equivalent to or newer than that of the source database. + * System Database (SYSTEMDB) impact: Recovering SYSTEMDB halts the entire SAP HANA system, including all tenant databases. While SYSTEMDB automatically restarts post-recovery, tenant databases on the target system require manual restarting. + * Delta backup handling: RSC automatically incorporates delta backups for point-in-time recovery, enhancing recovery performance and reducing Recovery Time Objectives (RTOs). While SAP HANA Studio provides an option to turn off delta backups, RSC does not. + * Snapshot type for recovery: You can only use full database snapshots for recovery operations. Incremental and differential snapshots cannot be used independently for recovery. + + *[ > ]: and then diff --git a/saas_sap_hana_replication.md b/saas_sap_hana_replication.md new file mode 100644 index 0000000000000000000000000000000000000000..850587588a5eb48eaa8a8fe5a3f8ccbf233b492d --- /dev/null +++ b/saas_sap_hana_replication.md @@ -0,0 +1,18 @@ +# SAP HANA replication + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_replication.html + +--- + +# SAP HANA replication + +In RSC, you can use the SLA Domain replication policy to replicate SAP HANA snapshots from one Rubrik cluster to another. + +You can configure an SLA Domain with a replication policy. The replication policy includes the replication target Rubrik cluster and the replication retention period. The replication target Rubrik cluster is the cluster to which the snapshots in the local storage of the source Rubrik cluster are replicated. + +An SLA Domain that has a replication policy can be assigned to an SAP HANA workload. The snapshots of that workload will be replicated to the target Rubrik cluster based on the policy settings. The log retention period remains the same on the source Rubrik cluster and the replication target Rubrik cluster. + +You can use the replicated snapshot for recovery of the SAP HANA workload. To recover a database, the snapshot must be available in the local storage of the source Rubrik cluster. If the snapshot is not available locally, you can download the snapshot from the replication target Rubrik cluster to perform recovery of the workload. + +RSC only allows full SAP HANA snapshots to be downloaded from a replication target. The option to download a replicated snapshot is only available for Rubrik clusters running Rubrik CDM version 8.1.2 or later. + *[ > ]: and then diff --git a/saas_sap_hana_storage_snapshots.md b/saas_sap_hana_storage_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..853ca45a603aea9b215d32c9d1008510ab3e154a --- /dev/null +++ b/saas_sap_hana_storage_snapshots.md @@ -0,0 +1,14 @@ +# SAP HANA storage snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_storage_snapshots.html + +--- + +# SAP HANA storage snapshots + +Using RSC, you can take storage snapshots of SAP HANA systems running on an Azure virtual machine and use those snapshots to recover your SAP HANA databases. Storage snapshots are fast, encrypted, have negligible network load, and capture the entire data area at a particular point in time. + +A storage snapshot captures the data persisted in the data area at a particular point in time. A storage snapshot includes all the data required to recover each SAP HANA database to a consistent state. Storage snapshots are fast, encrypted, and have negligible network load. + +Since the storage snapshot involves taking a snapshot of the data area, you can create these snapshots only at the SAP HANA system level. However, you can perform the restore operation on all databases. You can create storage snapshots with minimal impact on the SAP HANA system as it does not consume database resources. Instead, the snapshot is created in the storage system. RSC stores the storage snapshots in the Azure environment and not in the Rubrik cluster. + *[ > ]: and then diff --git a/saas_sap_hana_system_replication.md b/saas_sap_hana_system_replication.md new file mode 100644 index 0000000000000000000000000000000000000000..9f2f64001bbd303bcdbc0130c1d0ddb71d5e6db9 --- /dev/null +++ b/saas_sap_hana_system_replication.md @@ -0,0 +1,12 @@ +# SAP HANA system replication + +Source: https://docs.rubrik.com/en-us/saas/saas/sap_hana_system_replication.html + +--- + +# SAP HANA system replication + +SAP HANA system replication is a configuration to ensure high availability and disaster recovery of your SAP HANA system by setting up a backup system in the same as well as in a different data center location, respectively. With RSC, you can protect the configuration for high availability or disaster recovery. + +RSC can protect the SAP HANA System Replication (HSR) configuration, which ensures high availability or disaster recovery for your SAP HANA system. To set up the HSR configuration, RSC requires you to create a secondary SAP HANA system in the SAP HANA environment that is an exact copy of the active SAP HANA primary system, with the same number of active hosts in each system. The number of standby hosts can be different. The configuration requires a reliable link between the primary and secondary systems to ensure the HSR configuration works correctly. Once you enable the HSR configuration, each server process on the secondary system establishes a connection with its primary system and requests a snapshot of the data. Thereafter, all logged changes in the primary system are replicated continuously to the secondary system. + *[ > ]: and then diff --git a/saas_saphana_protection.md b/saas_saphana_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..a84417f86b5e2d459a1e5c590f88008b073ddf90 --- /dev/null +++ b/saas_saphana_protection.md @@ -0,0 +1,29 @@ +# SAP HANA protection + +Source: https://docs.rubrik.com/en-us/saas/saas/saphana_protection.html + +--- + +# SAP HANA protection + +With the SAP HANA protection feature, you can use SLA Domains to apply the data protection policies and management policies to SAP HANA workloads. + +SLA Domains in RSC consolidate data protection policies, providing a unified approach to manage data protection across various workloads and environments. SLA Domains provide a configurable set of policies that can be applied to groups of virtual machines, applications, hosts, and other workloads to achieve specific data protection objectives. The data protection policies available through an SLA Domain are related to frequency, retention, replication, archival, and retention lock. + +You can assign SLA Domains to protect your SAP HANA workloads. SAP HANA databases derive the assigned SLA Domain from the SAP HANA system. However, an individual assignment to the SAP HANA database overrides the assignment derived from the SAP HANA system. + +Some of the critical information you must consider while protecting your SAP HANA workloads is as follows: + + * You must set the value of log_mode on SAP HANA to normal to enable a continuous recovery chain on the SAP HANA workload. Setting the value of log_mode to overwrite prevents SAP HANA from creating log backups and prevents RSC from creating a continuous recovery chain. + * You can set the value of include_configuration_backup to true in the global.ini file to back up the SAP HANA configuration files along with the data backup. + * You can assign a retention-locked SLA Domain to your SAP HANA workloads. A retention lock prevents premature deletion of snapshots belonging to SAP HANA workloads managed by Rubrik clusters. The retention lock feature is available only for Rubrik clusters running Rubrik CDM version 8.1.1 or later. + +You must contact Rubrik Support to enable the SLA Domain retention lock feature. After Rubrik Support enables the retention lock feature on a Rubrik cluster, a toggle to apply the retention lock appears on the Create SLA Domain page. + +SAP HANA provides the following options for backing up SAP HANA databases: + + * File backups: The backup is stored locally. + * Backint backups: The backup is sent through the Rubrik Backint client to the Rubrik CDM cluster, where the SAP HANA workloads are running. + +Rubrik uses its native Backint client to take Backint backups, but you can still trigger a file backup from the SAP HANA host. However, if both file- and backint- backups are taken, the SAP HANA database might select a file backup as the base snapshot for taking the backint incremental or differential backup. Because Rubrik does not manage file backups, Rubrik recommends avoiding taking file backups after you have assigned an SLA Domain to an SAP HANA database. + *[ > ]: and then diff --git a/saas_schedule_recoveries_rp.md b/saas_schedule_recoveries_rp.md new file mode 100644 index 0000000000000000000000000000000000000000..b169aa85e895c246cd317824b84117000ff35ee4 --- /dev/null +++ b/saas_schedule_recoveries_rp.md @@ -0,0 +1,31 @@ +# Schedule recoveries for Recovery Plans + +Source: https://docs.rubrik.com/en-us/saas/saas/schedule_recoveries_rp.html + +--- + +# Schedule recoveries for Recovery Plans + +The schedule recovery feature automates periodic testing of disaster Recovery Plans and cyber Recovery Plans in Orchestrated Recovery. + +You can schedule periodic tests of previously created disaster Recovery Plans and cyber Recovery Plans in Orchestrated Recovery. These periodic test recoveries help you identify potential issues in the recovery environment that might impact a recovery during a cyber attack or a disaster situation. By addressing the identified issues, you can help to confirm that your systems are prepared for successful recoveries. + +RSC supports scheduling recoveries in Orchestrated Recovery for the following workloads: + + * vSphere virtual machines + * AHV virtual machines + * Azure virtual machines + * Amazon EC2 instances + +For scheduling and updating recovery schedules, you need permission to manage Recovery Plans and recoveries. RSC indicates whichRecovery Plans have configured test schedules by displaying a schedule icon for each in the Recovery Plans page. Scheduled recoveries are automatically cleaned up. Additionally, you can receive scheduled recovery reports by providing email addresses during schedule creation. + +For a scheduled recovery, the Orchestrated Recovery workflow follows this process: + + * Completing initial prechecks confirming the Recovery Plan status, cluster-level protection, validity of the Recovery Plan, ongoing recoveries, and previous cleanups. When a recovery is already in progress, Orchestrated Recovery does not run the recovery, and sends an email notification. + * Running the scheduled recovery according to the recovery plan. RSC selects the latest non-quarantined snapshot for scheduled recovery. When a snapshot is not available, Orchestrated Recovery does not run the recovery, and sends an email notification, if configured to do so. + * Running the scheduled recovery cleanup after the recovery completes. + * Generating a recovery report with the scheduled recovery status and details. + * Running any postchecks as needed. + * Sending notifications to the email addresses provided. + + *[ > ]: and then diff --git a/saas_scheduling_test_recovery.md b/saas_scheduling_test_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..786cc64596cc6bc753bc2609a7558e023691dea6 --- /dev/null +++ b/saas_scheduling_test_recovery.md @@ -0,0 +1,66 @@ +# Scheduling a test recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/scheduling_test_recovery.html + +--- + +# Scheduling a test recovery + +Configure a schedule for automating test recoveries using a selected Recovery Plan. Recovery testing strengthens preparedness and helps identify potential recovery issues before an event occurs. + +## Before you begin + +You must log in with a user account that has permissions to manage Recovery Plans and recoveries. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears. + + 4. Click a Recovery Plan. + +The Recovery Plan details page appears, displaying the Overview tab. + + 5. Click Create a schedule. + +The **Schedule Recovery Plan Tests** dialog box appears. + + 6. In First Recovery, select the date and time to start the test recovery. + 7. In Test Frequency, select an option for the frequency of the scheduled recovery test. + * Weekly + * Monthly + * Quarterly + * Never + +Selecting Never results in a single automated scheduled recovery. + + 8. When scheduling a cyber Recovery Plan, select a recovery option. + +Option | Description +---|--- +Export | + * Select this option to create a virtual machine from this snapshot and use your vSphere or AHV virtual infrastructure as the datastore.You can select Export for vSphere virtual machines only if you have configured a storage location in the recovery plan.You can select Export for AHV virtual machines as configuring a storage location is required for recovery. + * Export is the only recovery option for Azure virtual machines and Amazon EC2 instances. +Live Mount | Select this option to create a virtual machine from this snapshot and use your Rubrik cluster as the datastore. This helps to onboard and deploy your applications faster. + + 9. **Optional:** Click Delete Schedule to delete any existing schedules for that test recovery. + 10. Click Next. + 11. **Optional:** Turn on Recovery Notification to receive a recovery notification email after each test. + 12. **Optional:** When choosing to receive a recovery notification, select the Attach the recovery report to the email option to receive the report attached to the email. + +The Attach the recovery report to the email option is selected by default. You can turn it off to prevent the report being attached to the email. + +Turning on the Recovery Notification and Attach the recovery report to the email options is required for receiving the report attached to the email. + + 13. **Optional:** When choosing to receive a recovery notification, in Recipients, add the email addresses of the users who must receive the report. + 14. Click Save. + +## Results + +RSC performs the test recoveries according the selected schedule. The Recoveries tab displays the details of the performed recoveries. diff --git a/saas_sdd_events.md b/saas_sdd_events.md new file mode 100644 index 0000000000000000000000000000000000000000..c9fff9f088fed9c2ca4bf2aa3fa8bb56b693ef65 --- /dev/null +++ b/saas_sdd_events.md @@ -0,0 +1,26 @@ +# Data Security Posture events + +Source: https://docs.rubrik.com/en-us/saas/saas/sdd_events.html + +--- + +# Data Security Posture events + +The Data Security Posture Event Logs pageprovides information about the status of classification jobs. + +Data Security Posture tracks, monitors, and displays Data Security Posture event information for the connected Rubrik clusters. You can examine this information using various filters. The Data Security Posture Events page lists the events of all connected Rubrik clusters in the local time zone. Clicking an event will provide detailed information for that event. + +The following table describes the event details shown for an event in Data Security Posture. Event detail | Description +---|--- +Object | A combination of object type and object name. +Status | The status of the event. +Event | The most recent update from the event timeline. +Cluster | The name of the Rubrik cluster where the event occurred. +Object type | The type of the object associated with the event. +Object name | The name of the object associated with the event. +Event type | The type of event. +Duration | The time elapsed for an event in progress or the total time taken for the completed events. +Start time | The date and time when the event started. +Event timeline | A list of updates about the event from beginning to end. +Incident ID | A unique identifier for failed events. + *[ > ]: and then diff --git a/saas_sdd_events_filters.md b/saas_sdd_events_filters.md new file mode 100644 index 0000000000000000000000000000000000000000..397bc1d257235a3acafdad3c14254810e00de9b0 --- /dev/null +++ b/saas_sdd_events_filters.md @@ -0,0 +1,36 @@ +# Data Security Posture events filters + +Source: https://docs.rubrik.com/en-us/saas/saas/sdd_events_filters.html + +--- + +# Data Security Posture events filters + +The Data Security Posture Event Logs page displays the events of all connected Rubrik clusters in the local time zone. + +RSC tracks, monitors, and displays all events of all connected Rubrik clusters when no filter is applied. + +Changing filters will dynamically change the Event Logs page view. + +The following table describes the Data Security Posture Event filters. + +Filter | Description +---|--- +Time range | Displays events aggregated over the specified time. + * Past 2 hours + * Past 24 hours + * Past 7 days + * Past 30 days +Clusters | Displays events on Rubrik clusters connected to RSC or RSC native events. +Severity | Displays events by the selected severity. + * Critical: System event that requires attention, such as failed backup, archival, and replication. + * Warning: System event finished with a warning, such as backup, archival, or recovery. + * Informational: System event for information only. +Status | Displays events based on the status of the event. + * Failure + * Running + * Completed + * Canceled + * Queued +Object Type | Displays events of the specified object types respective to the connected Rubrik clusters on RSC, such as virtual machines, servers, and applications. + *[ > ]: and then diff --git a/saas_sdd_reports.md b/saas_sdd_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..5c4a18fc8d895f1cc04c8a80b6d40eb1bf9decda --- /dev/null +++ b/saas_sdd_reports.md @@ -0,0 +1,17 @@ +# Data Security Posture reports + +Source: https://docs.rubrik.com/en-us/saas/saas/sdd_reports.html + +--- + +# Data Security Posture reports + +Customizable reports are available for Rubrik clusters with access to Data Security Posture. + +You can complete the following actions from the Report details page: + + * Viewing the reports + * Using filters to sort information by the type of object, cluster, or policy + * Scheduling a report + * Downloading reports + *[ > ]: and then diff --git a/saas_service_account.md b/saas_service_account.md new file mode 100644 index 0000000000000000000000000000000000000000..ac4e28666225cccb0cbe6e783cf170749733e297 --- /dev/null +++ b/saas_service_account.md @@ -0,0 +1,22 @@ +# Service accounts + +Source: https://docs.rubrik.com/en-us/saas/saas/service_account.html + +--- + +# Service accounts + +RSC uses service accounts to represent services and client applications that need to invoke RSC APIs. + +A service account represents an application that needs authentication and authorization to invoke RSC APIs. In contrast, a user account represents an individual user. + +Service accounts use a client secret to authenticate to an authorization server and obtain an access token to invoke the RSC APIs. Similar to user accounts, RSC allows you to assign roles to the service accounts to enable RBAC. But contrary to user accounts, service accounts cannot be used to access RSC. + +If a service account is unavailable, client applications and services that need access to the protected resources on the RSC server have to authenticate to RSC using the username and password of a user account. Authenticating with the credentials of a user account has the following drawbacks: + + * Every time there is a change in the account password to comply with the security policies of the organizations, the service that uses the credentials needs an update as well. + * If the organization deactivates the user account, the service can no longer authenticate to RSC to invoke the APIs until the credentials are updated. + * The application code becomes vulnerable to attacks by allowing malicious actors to obtain the credentials and gain unauthorized access to the protected resources and APIs. + +Using service accounts to represent client applications eliminates the need to rely on user accounts to access the RSC APIs. + *[ > ]: and then diff --git a/saas_setting_default_dashboard.md b/saas_setting_default_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..25c81afbf209c0fc5613e26ed76b9e3faa812d2d --- /dev/null +++ b/saas_setting_default_dashboard.md @@ -0,0 +1,26 @@ +# Setting the default dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/setting_default_dashboard.html + +--- + +# Setting the default dashboard + +Information about setting RSC default dashboard. + +## Procedure + + 1. Log in to RSC. + 2. In the upper-right corner, click the user account icon and from the drop-down list, select User Preferences. + +The User Preference page appears. + + 3. Click Landing page. + 4. Select the dashboard that you want to set as the default dashboard. + +Alternatively, RSC also allows you to set other pages, for example, inventory, cluster, or MS365 dashboard as the default dashboard view. + +## Results + +The chosen dashboard is set as the default dashboard. + *[ > ]: and then diff --git a/saas_sla_domain_administration.md b/saas_sla_domain_administration.md new file mode 100644 index 0000000000000000000000000000000000000000..931ebb1a68d2a976a333d01b7f5f5fc22b13d22b --- /dev/null +++ b/saas_sla_domain_administration.md @@ -0,0 +1,26 @@ +# SLA Domain administration + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domain_administration.html + +--- + +# SLA Domain administration + +RSC provides centralized administration of SLA Domains. + +SLA Domains in RSC unify data protection policies, providing a unified approach to manage data protection across various workloads and environments. + +To administer SLA Domains, you can use RSC for: + + * Creating an SLA Domain. + * Assigning a default or custom SLA Domain to different workloads. + * Modifying an SLA Domain to adjust assigned workloads, snapshot frequency, retention, replication, archival, and other data protection policies. + * Viewing the details of an SLA Domain. + * Deleting an SLA Domain. + * Changing retention of snapshots. + * Placing a legal hold on snapshots. + * Switching SLA Domains from a Rubrik cluster to RSC SLA Domains. + * Synchronizing SLA Domains with a Rubrik cluster to RSC to ensure the backup of critical infrastructure. + +By leveraging these capabilities, you can effectively manage data protection policies across different workloads and environments, ensuring reliable and consistent data security. + *[ > ]: and then diff --git a/saas_sla_domain_attributes.md b/saas_sla_domain_attributes.md new file mode 100644 index 0000000000000000000000000000000000000000..11d7a17b1d5ff774c4d0bcef06f5cbdf649db7e2 --- /dev/null +++ b/saas_sla_domain_attributes.md @@ -0,0 +1,33 @@ +# SLA Domain attributes + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domain_attributes.html + +--- + +# SLA Domain attributes + +Information about the details for managing SLA Domains and the available actions and attributes on the SLA Domains dashboard. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +On the SLA Domains dashboard, you can perform the following actions: + + * Switch SLA Domains + * Create SLA Domain + * Search by SLA Domain name + * Filter SLA Domains using Managed by, Organizations, Object types, or Creator Org + +The following table describes the attributes of an SLA Domain. SLA Domain attributes | Description +---|--- +SLA Domain | The name of the SLA Domain. +Base Frequency | The time interval at which backups or snapshots are created. +Objects | The number of data objects or workloads assigned to the SLA Domain. +Assigned Orgs | The tenant organizations with view access to the SLA Domain that can view and use the SLA Domain for data protection.Clicking on reveals additional organizations assigned to the SLA Domain. +Creator Org | The organization that created the SLA Domain. +Archival Policy 1 | The archival destination for long-term storage of backups.Clicking reveals the object types and their associated archival and replication targets. +Archival Policy 2 | The archival destination for additional storage, if applicable.Clicking reveals the object types and their associated archival and replication targets. +Replication Policy 1 | The replication policy that manages data replication to one or more target clusters.Hovering over the policy displays details such as object type, target, and retention. Additionally, the appears only for one-to-one replication. Clicking it reveals the source and target clusters. +Cascading Archival (Replication Policy 1) | The archival location for data replicated using Replication Policy 1.Clicking reveals the target clusters and their corresponding cascading archival policies. +Replication Policy 2 | The replication policy that manages data replication to multiple target clusters.Hovering over the policy displays details such as object type, target, and retention. Additionally, the appears only for one-to-one replication. Clicking it reveals the source and target clusters. +Cascading Archival (Replication Policy 2) | The archival location for data replicated using Replication Policy 2.Clicking reveals the target clusters and their corresponding cascading archival policies. + *[ > ]: and then diff --git a/saas_sla_domain_details.md b/saas_sla_domain_details.md new file mode 100644 index 0000000000000000000000000000000000000000..1330932e772b8af03a7033e4b44735388f18e5d1 --- /dev/null +++ b/saas_sla_domain_details.md @@ -0,0 +1,95 @@ +# SLA Domain details + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domain_details.html + +--- + +# SLA Domain details + +Information about SLA Domain details page that provides a list of tabs, actionable options, and key details summarized through information cards. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +On the SLA Domain details page, you can open the following tabs: + + * Objects + * Audit + * Pause Status + +The following table describes the actions that you can perform on the page. Action | Description +---|--- +| Provides the following options: + + * Clone SLA Domain + * Delete SLA Domain + * Sync with a Cluster + + +Edit | Provides the option to edit the SLA Domain. +Protection status filter | Filters based on the protection state of objects such as Protected, Unprotected, or Relic, along with the object count in parenthesis. +Filter | Provides the following filters: + + * Cluster: Filters based on the selected cluster, displays the objects that belong to the selected cluster. + * Object Type: Filters based on the selected object type, or on all objects. + * Assignment Type: Filters based on the direct assignment or all assignment types. By default, RSC displays objects to which SLA Domains are directly assigned. + + +Search by object name | Enables quick filtering of objects by entering a specific name. + +The following table describes the details on the information card. Information card | Description +---|--- +SLA Domain Details | Displays the details of the SLA Domain. The SLA Domain page presents comprehensive information. + + * Managed By: The entity responsible for managing the SLA Domain, either RSC or the Rubrik cluster. + * Created By: The creator of the SLA Domain, which is global by default. + * Assigned Orgs: The organizations that have access to this SLA Domain. + * Description: A brief description of the SLA Domain. + * Object Types: The types of workloads that the SLA Domain protects. + * Clusters: A list of clusters with workloads that can be assigned to this SLA Domain. The choice of archival locations when creating the SLA Domain determines the content of the list.When you create an SLA Domain with a data center archival location, it can be applied only to objects within the same cluster selected for the archival location. The cluster details appear only for archiving use cases. + + +Frequency and Retention | Displays frequency of snapshots and retention policies for the SLA Domain. + + * Take Every: Specifies the frequency at which the snapshots are taken. + * Retain for: Specifies the retention period for the snapshots taken. + * Snapshot Window: The time window during which the snapshots are taken. + * First full snapshot: The time at which the first full snapshot is taken. + + +Archival | Displays the archival policies and settings. + + * Source Retention: The duration for which snapshots are retained on local storage. + * Maximum Retention: The longest retention period for archived snapshots. + * Archive Snapshots Taken: The frequency of snapshots taken for archiving. + * Object Type: The types of objects archived under this policy. + * Archival Location: The storage location where the snapshots are archived. + + +Many-to-one Replication | Displays the replication of data from multiple source clusters to a single target cluster. + + * Replication: The maximum duration for which the replicated snapshots are retained. + * Object Type: The types of objects replicated under this policy. + * Replication Target: The destination cluster that receives the replicated data. + * Service Provider: The name of the account from which the replication target originates, applicable to clusters with replication configured. For cross-account replication, the name of the provider account is shown, and for replication targets within the same account, it displays as Local. + + +One-to-one Replication | Displays the replication of data from a single source cluster to a single target cluster. + + * Replication: The maximum duration for which the replicated snapshots are retained. + * Object Type: The types of objects replicated under this policy. + * Source Cluster: The cluster that replicates the data. + * Target Cluster: The destination cluster that receives the replicated data. + * Service Provider: The name of the account from which the replication target originates, applicable to clusters with replication configured. For cross-account replication, the name of the provider account is shown, and for replication targets within the same account, it displays as Local. + + +Cascading Archival | Displays the archiving of replicated snapshots from a target Rubrik cluster to a remote archival location. This option is visible only for clusters configured with cascading archival. + + * On Cluster: The duration for which the snapshots are retained on the replication target Rubrik cluster. + * Cascading Archival: The duration for which snapshots are retained on a cascading archival location. + * Archive Snapshots: The frequency of snapshots taken for replication. + * Target Cluster: The Rubrik cluster designated as the replication target destination for replicated data. + * Cascading Archival Location: The location where the replicated snapshots are archived. + + +Object Specific Parameters | Displays the parameters that are specific to the selected object types. + *[ > ]: and then diff --git a/saas_sla_domain_states.md b/saas_sla_domain_states.md new file mode 100644 index 0000000000000000000000000000000000000000..35cfd0c532cf03c3df5bd16a73a240aaf26a5520 --- /dev/null +++ b/saas_sla_domain_states.md @@ -0,0 +1,17 @@ +# SLA Domain states + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domain_states.html + +--- + +# SLA Domain states + +RSC protects objects through an SLA Domain. The SLA Domain state determines an object protection. + +State | Description +---|--- +Unassigned | No SLA Domain is assigned to the workload. +Direct | The workload receives direct protection from its assigned SLA Domain. +Derived | The protected object derives protection from its higher-level object. +Pending SLA | The SLA Domain assignment is in progress. When the assignment completes, RSC replaces this state with the new SLA Domain. + *[ > ]: and then diff --git a/saas_sla_domain_sync_rubrik_cluster.md b/saas_sla_domain_sync_rubrik_cluster.md new file mode 100644 index 0000000000000000000000000000000000000000..5627e95622ae962d452776712aef1e4e969e9047 --- /dev/null +++ b/saas_sla_domain_sync_rubrik_cluster.md @@ -0,0 +1,23 @@ +# SLA Domain synchronization with a Rubrik cluster + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domain_sync_rubrik_cluster.html + +--- + +# SLA Domain synchronization with a Rubrik cluster + +By synchronizing the SLA Domains from Rubrik Security Cloud with a Rubrik cluster, you can take on-demand snapshots from the CDM web UI and the CDM REST APIs without assigning the SLA Domains to any object. + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +During recovery scenarios, such as ransomware attacks, Rubrik clusters are often disconnected from external networks. Even in such scenarios, you can take on-demand snapshots through the CDM web UI and the CDM REST APIs to ensure data protection and integrity. After you complete the recovery actions, you must synchronize the SLA Domains with the Rubrik cluster to ensure the backup of critical infrastructure, such as servers, storage systems, and networks. + +You can synchronize the SLA Domains from RSC with a Rubrik cluster without assigning them to any object on that cluster for taking on-demand snapshots. This synchronization is allowed even for isolated Rubrik clusters. + +To enable SLA Domain synchronization, you must perform the following tasks: + + * Connecting the Rubrik cluster to RSC + * Configuring the Rubrik cluster as an archival source cluster if archiving is configured in the SLA Domain + * Pairing the Rubrik cluster with the existing replication targets if replication is configured in the SLA Domain + + *[ > ]: and then diff --git a/saas_sla_domains.md b/saas_sla_domains.md new file mode 100644 index 0000000000000000000000000000000000000000..1076d00b4098cffb73adfb1cb00de2a7143450d2 --- /dev/null +++ b/saas_sla_domains.md @@ -0,0 +1,27 @@ +# SLA Domains + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domains.html + +--- + +# SLA Domains + +SLA Domains in RSC unify data protection policies, providing a unified approach to manage data protection across various workloads and environments. + +SLA Domains simplify the task of protecting and managing different workloads. RSC provides an SLA policy management service, which also unifies SLA policies from multiple clusters into a single view. Task management for objects protected by Rubrik clusters still takes place on the individual Rubrik clusters. SLA Domains provide a configurable set of policies that can be applied to groups of virtual machines, applications, hosts, and other workloads to achieve specific data protection objectives. + +You can assign an SLA Domain to objects on any Rubrik cluster. On RSC, you can review the SLA Domain details and monitor the assigned objects of the SLA Domain and the current status of the policy-based tasks. + +SLA Domains created on the Rubrik cluster contains data protection policies. RSC provides view-only access to these SLA Domains and allows you to assign SLA Domains to objects on that Rubrik cluster using RSC. + +An SLA Domain in RSC requires the specification of object types, allowing you to customize the behaviors specific to the selected object type. + +The following table lists the data protection policies available through an SLA Domain: + +Policy | Description +---|--- +Frequency | Defines the interval to use when creating snapshots. +Retention | Defines how long to retain each snapshot for each storage type. +Replication | Specifies the replication target and the replication target type. +Archival | Specifies the storage of snapshots at an archival location. +Retention lock | Provides two modes, governance mode and compliance mode, with different approaches for managing data security and compliance requirements within SLA Domains. diff --git a/saas_sla_domains_assignment.md b/saas_sla_domains_assignment.md new file mode 100644 index 0000000000000000000000000000000000000000..fd43fd5ebb7115c23910c28531d8b5bd10de2afd --- /dev/null +++ b/saas_sla_domains_assignment.md @@ -0,0 +1,16 @@ +# SLA Domains assignment + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domains_assignment.html + +--- + +# SLA Domains assignment + +You can protect and manage your data by assigning SLA Domains across various workloads in RSC. + +You can assign an SLA Domain in RSC to achieve data protection. This involves configuring predefined or creating custom SLA Domain policies for various workloads, such as databases, virtual machines, or cloud-native applications. + +By using SLA Domain assignment, you can ensure data protection and management for each individual workload within their environment. This approach simplifies the administration of backup and recovery tasks, automates policy enforcement, and enhances data governance and compliance efforts. You can customize behaviors specific to the selected object type in an SLA Domain by specifying object types. On RSC, you can review the SLA Domain details and monitor the assigned objects of the SLA Domain and the current status of the policy-based tasks. + +SLA Domains created on the Rubrik cluster contain data protection policies. RSC provides view-only access to these SLA Domains and allows you to assign SLA Domains to objects on that Rubrik cluster using RSC. You can assign an SLA Domain to objects on any Rubrik cluster. + *[ > ]: and then diff --git a/saas_sla_domains_features.md b/saas_sla_domains_features.md new file mode 100644 index 0000000000000000000000000000000000000000..ab532c6b64121f4f04790aff9f128608f0eff5c6 --- /dev/null +++ b/saas_sla_domains_features.md @@ -0,0 +1,18 @@ +# SLA Domains features + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domains_features.html + +--- + +# SLA Domains features + +Information about the features available when creating an SLA Domain. + +The following table describes the data protection policies available through an SLA Domain. Policy | Description +---|--- +Frequency | Defines the interval to use when creating snapshots. +Retention | Defines how long to retain each snapshot for each storage type.When you modify the retention period, you have the option to apply the modification to the existing snapshots. This prevents accidental data loss, especially if the new SLA Domain has a shorter retention period. +Archival | Specifies the storage of snapshots at an archival location. +Replication | Specifies the replication target and the replication target type. +Retention lock | Provides two modes, governance mode and compliance mode, with different approaches for managing data security and compliance requirements within SLA Domains. + *[ > ]: and then diff --git a/saas_sla_domains_switching.md b/saas_sla_domains_switching.md new file mode 100644 index 0000000000000000000000000000000000000000..c0d46ae3af2fba41984c344fa54d5cf6a5b5a101 --- /dev/null +++ b/saas_sla_domains_switching.md @@ -0,0 +1,28 @@ +# SLA Domains switching + +Source: https://docs.rubrik.com/en-us/saas/saas/sla_domains_switching.html + +--- + +# SLA Domains switching + +By switching Rubrik cluster SLA Domains toRubrik Security Cloud, you can centrally manage and protect multiple objects across Rubrik clusters. + +You can switch Rubrik cluster SLA Domains to RSC only if you have permission to manage them. + +Switching Rubrik cluster SLA Domains to RSC centralizes management and protection of multiple objects across Rubrik clusters. After switching, you can manage all switched SLA Domains centrally from RSC protecting both cloud objects and Rubrik clusters without the need to navigate to the CDM web UI. + +Additionally, you can edit RSC SLA Domains to apply changes across all Rubrik clusters. If you switch SLA Domains from Rubrik cluster to RSC, the data protection policies, objects that are protected, and the lifecycle of snapshots associated with the SLA Domain remain unchanged. + +You can switch Rubrik cluster SLA Domains to RSC either by switching manually or by switching all SLA Domains at once. + +Before switching all SLA Domains, you are required to complete all tasks in the RSC Management dashboard. If some of the tasks are incomplete, you can continue to switch only the SLA Domains for which the tasks are complete. You are required to visit the RSC Management dashboard to complete the remaining tasks. + +Managing SLA Domains involves a set process and timeline, ensuring a smooth transition to RSC. + + * SLA Domain management switching applies only to SLA Domains that are assigned to an object and eligible for switching. + * You have a maximum of 30 days to complete the switching of SLA Domain management from the Rubrik cluster to RSC. This time starts from the first time you log in and see the switching announcement. + * You can request a single extension period of 15 days for the switching process. Extensions apply globally across the accounts, irrespective of individual user permissions. After the extension period ends, Rubrik automatically switches all SLA Domains that are assigned to an object and eligible for switching. + * At the end of the switching period, SLA Domains created on a Rubrik cluster automatically switch to RSC on a daily basis. This automatic switching operates at the account level, ensuring that all users have the same end date and share a unified timer. + + *[ > ]: and then diff --git a/saas_snapmirror_cloud.md b/saas_snapmirror_cloud.md new file mode 100644 index 0000000000000000000000000000000000000000..2af293889c96de7b7febc51fd8de9a6e9afc6fc5 --- /dev/null +++ b/saas_snapmirror_cloud.md @@ -0,0 +1,46 @@ +# SnapMirror Cloud + +Source: https://docs.rubrik.com/en-us/saas/saas/snapmirror_cloud.html + +--- + +# SnapMirror Cloud + +RSC protects user data replicated by the NetApp SnapMirror Cloud service. + +RSC can protect FlexVol volumes on NetApp NAS hosts running ONTAP version 9.8 or later. The NetApp host can be a primary NAS or a SnapMirror replica copy. SnapMirror Cloud protection is available for Rubrik clusters running Rubrik CDM version 7.0.4 or later (except version 8.0). + +RSC uses object storage from a supported cloud vendor that is properly configured as a SnapMirror Cloud destination. Data protection using SnapMirror Cloud supports the following cloud vendors: + + * AWS + * Microsoft Azure + * GCP + +You must add GCP as a Generic S3 compatible object store. Because service account credentials are not accepted, username and password authentication is required. + + * NetApp StorageGRID + +You must add NetApp StorageGRID as S3 compatible storage. + + * NetApp ONTAP S3 + +RSC uses the following information to protect SnapMirror Cloud content. + + * NetApp API credentials + +Providing root credentials for temporary use is required. Credentials are not stored but are used to create NetApp API credentials used for subsequent operations. + + * NetApp cluster IP address or hostname + * Details of the object storage in use, such as the cloud provider, bucket name, and access key + +Network File System (NFS) version 4 is required. + +Protecting NetApp host FlexVol volumes using SnapMirror Cloud requires using SnapDiff API version 3. NetApp documentation provides more details on enabling this version of the required licenses. + +Installing the SnapMirror Cloud license in the relevant NetApp clusters is also required for RSC support. + +The Rubrik cluster coordinates the transfer of backups of protected volumes on the NetApp host to the SnapMirror Cloud archive. The activity log on the Rubrik cluster maintains details of the transfers. The file contents of the backups are indexed usingSnapDiff API version 3. You can browse the file system of indexed backups and select the entire volume or individual files for recovery. + +NetApp host FlexVol volumes protected on SnapMirror Cloud do not support the use of include, exclude, or do not exclude rules in the manner of Rubrik filesets. SLA Domains can protect any FlexVol volume that is associated with a NFS or SMB share on a NetApp API enabled host. + +Because NetApp does not report physical storage used by cloud snapshots, RSC and reports might display the storage as either 0B or N/A (not available). diff --git a/saas_snapmirrorcloud_delete_snapshots.md b/saas_snapmirrorcloud_delete_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..0f38c290fd4522b27d1c7440c8b42a9915d94bee --- /dev/null +++ b/saas_snapmirrorcloud_delete_snapshots.md @@ -0,0 +1,12 @@ +# Snapshots deletion + +Source: https://docs.rubrik.com/en-us/saas/saas/snapmirrorcloud_delete_snapshots.html + +--- + +# Snapshots deletion + +The latest snapshot that has not been synchronized to the cloud cannot be deleted without removing protection from the volume. + +You cannot delete the latest snapshot that has not been synchronized to the cloud. You must first remove the protection from the volume, which in turn removes the association between the NetApp volume and cloud endpoint. + *[ > ]: and then diff --git a/saas_snapshot_retention_management.md b/saas_snapshot_retention_management.md new file mode 100644 index 0000000000000000000000000000000000000000..b1988853bba252049326f662a13eea3edf1b3e63 --- /dev/null +++ b/saas_snapshot_retention_management.md @@ -0,0 +1,39 @@ +# Snapshot retention management + +Source: https://docs.rubrik.com/en-us/saas/saas/snapshot_retention_management.html + +--- + +# Snapshot retention management + +Rubrik implements a concept of buckets to manage snapshot expiration based on an SLA Domain. + +## How snapshot retention buckets work + +Rubrik uses a concept of buckets to manage snapshot expiration based on an SLA Domain. Each frequency type corresponds to a set of buckets, with the bucket size determined by the frequency and the number of buckets calculated as [(retention/frequency) + 1], rounded up to the nearest larger integer. + +For example, let us consider the following SLA Domain configuration. + + * Daily frequency: 1 (snapshot taken every day) + * Daily retention: 48 days (daily snapshots are retained for 48 days) + * Monthly frequency: 1 (snapshot taken once a month) + * Monthly retention: 2 months (monthly snapshots are retained for 2 months). Monthly snapshots are taken on the last day of each month. + +Let us explore how the bucket system works based on this example SLA Domain. + +For a daily frequency of 4 days and a retention of 48 days: + + * Buckets are formed every 4 days + * Number of buckets is 48/4 + 1 = 13 + +For a monthly frequency of 1 month and retention of 2 months (with snapshots taken on the last day of the month): + + * Buckets are formed every 1 month + * Number of buckets is 2/1 + 1 = 3 + +To ensure coverage of the required snapshots, an additional snapshot is retained. This additional snapshot guarantees the availability of a daily snapshot that is at least 48 days old and a monthly snapshot that is at least 2 months old. For example, on May 15, without the additional snapshot, we might only have 2 monthly snapshots on March 31 and April 30, neither of which would be at least 2 months old. Therefore, the expected expiration dates of some snapshots may extend beyond the maximum SLA retention. + +## On-demand and customized snapshots + +The expiration of on-demand and customized snapshots is determined by the configured retention period from the time of their creation. For example, an on-demand snapshot with the SLA Domain configuration described in the example above will be retained for 2 months because the monthly frequency has the maximum retention. + *[ > ]: and then diff --git a/saas_snapshots.md b/saas_snapshots.md new file mode 100644 index 0000000000000000000000000000000000000000..7db8699d3c6d65c32e12e286a95fb27ba15a5b68 --- /dev/null +++ b/saas_snapshots.md @@ -0,0 +1,14 @@ +# SAP HANA snapshots + +Source: https://docs.rubrik.com/en-us/saas/saas/snapshots.html + +--- + +# SAP HANA snapshots + +RSC protects and manages data through snapshots of the source object and enables you to take full, incremental, and differential snapshots. + +The SLA Domain feature provides a configurable set of policies that can be applied to data sources to achieve specific data protection objectives. The SLA Domain directs the objects when to create point-in-time snapshots or backups of protectable objects and how long to keep the data. + +SAP administrators can handle recovery from snapshots using RSC UI or SAP HANA native tools. + *[ > ]: and then diff --git a/saas_sso_groups.md b/saas_sso_groups.md new file mode 100644 index 0000000000000000000000000000000000000000..ee90af3245f495de887c10b7013f1f597e3d85f2 --- /dev/null +++ b/saas_sso_groups.md @@ -0,0 +1,10 @@ +# SSO groups + +Source: https://docs.rubrik.com/en-us/saas/saas/sso_groups.html + +--- + +# SSO groups + +RSC grants permissions to SSO users based on the role assigned by their IdP groups. + *[ > ]: and then diff --git a/saas_sso_users.md b/saas_sso_users.md new file mode 100644 index 0000000000000000000000000000000000000000..2d7ae398610ece57c0ba8ae4e576fb07ce7a5f46 --- /dev/null +++ b/saas_sso_users.md @@ -0,0 +1,37 @@ +# SSO users + +Source: https://docs.rubrik.com/en-us/saas/saas/sso_users.html + +--- + +# SSO users + +SSO users receive permissions according to the roles assigned to their SSO groups. Additionally, you can assign roles directly to individual SSO users as needed. + +In a Single Sign-On (SSO) authentication service, user permissions are managed through roles. Administrators typically assign these roles to SSO groups, and any user who is part of a group inherits the permissions associated with the roles of that group. In large organizations, this simplifies permissions management for users who require similar access levels. + +However, there might be cases where specific users require additional permissions that their SSO group roles do not cover. In such cases, you can assign roles directly to individual SSO users. This flexibility ensures that all users have the necessary permissions to perform their tasks effectively. Moreover, you can directly assign roles to users who are not part of any SSO group, further enhancing flexibility in permissions management. + +The following are a few examples of when to assign roles directly to individual SSO users: + + * Granting temporary access to financial reports for a special project to a member of the Sales team, John Doe, by assigning a financial reporting role directly to the SSO account of John Doe without changing the permissions of the SSO group for the Sales team. This ensures that John has the necessary access for his project while the standard permissions are maintained for the rest of the team. + * Assigning the QAuth reviewer role to an RSC user to approve or deny requests triggered by user-defined policies. + +RSC provides a unified interface for managing your SSO users. From the SSO tab in the Users page, you can perform the following actions: + + * Viewing the authorized SSO users and the associated details, such as SSO groups, SSO group roles, directly assigned roles, organizations, last login time, and email preference settings. + +The directly assigned roles are the additional roles assigned directly to SSO users. + + * Authorizing SSO users and assigning the required roles to them. + +The effective roles for an SSO user consist of all roles inherited through the SSO group of the user and the roles that you assign. + + * Editing the direct role assignment for an authorized SSO user. + * Locking and unlocking an SSO user account. + * Hiding SSO users to prevent unauthorized access. + * Editing email preferences for RSC to send notifications to the configured email addresses. + * Importing users and roles created on the Rubrik cluster to manage them on RSC. + +These features enable efficient management of SSO users and ensure proper access control. + *[ > ]: and then diff --git a/saas_standalone_esxi_host_protection.md b/saas_standalone_esxi_host_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..016232d4419c845ca00e4e12affa912f1907af6e --- /dev/null +++ b/saas_standalone_esxi_host_protection.md @@ -0,0 +1,16 @@ +# Standalone ESXi host protection + +Source: https://docs.rubrik.com/en-us/saas/saas/standalone_esxi_host_protection.html + +--- + +# Standalone ESXi host protection + +Rubrik supports protecting and restoring virtual machines on standalone ESXi hosts, providing continuous data security in environments that do not include a vCenter server. + +Rubrik supports the management of standalone ESXi hosts, enabling the protection and restoration of virtual machines even in environments where a vCenter server is not available, such as remote offices or emergency situations. This feature is particularly useful for securing workloads on servers that operate independently, ensuring continuous data protection. + +Configuring this feature requires adding the standalone ESXi host as a managed entity with accurate network and storage configuration details. This configuration requires providing the appropriate permissions to interact with the host, and then selecting at least one cluster to manage the backup, restore, replication, and archiving operations for the standalone host. After the configuration is complete, you can initiate backups and perform restores on the standalone host resources. + +Rubrik directly manages virtual machines on standalone ESXi hosts by taking snapshots of the virtual machines to use in performing backups. These snapshots ensure that data can easily be restored whenever you need them, providing continuous protection for the virtual machines. + *[ > ]: and then diff --git a/saas_supported_features_for_workloads.md b/saas_supported_features_for_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..8c7a1f14406212ef4f301c4340bac782d3df9f3b --- /dev/null +++ b/saas_supported_features_for_workloads.md @@ -0,0 +1,39 @@ +# Supported features for RSC workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/supported_features_for_workloads.html + +--- + +# Supported features for RSC workloads + +Supported features for specific RSC workloads when creating or modifying an SLA Domain. + +The following table provides information about supported features for RSC workloads. Workload type | Workload | Supported features +---|---|--- +Data center objects +Virtual Machines | vSphere VMs | Archiving: SupportedReplication: Supported +VCD vApp | Archiving: SupportedReplication: Supported +Hyper-V VM | Archiving: SupportedReplication: Supported +Nutanix VM | Archiving: SupportedReplication: Supported +Databases and Apps | SQL Server Databases | Archiving: SupportedReplication: Supported +Oracle Databases | Archiving: SupportedReplication: Supported +SAP HANA | Archiving: SupportedReplication: Supported +Db2 | Archiving: SupportedReplication: Supported +Cassandra | Archiving: Not supportedReplication: Not supported +MongoDB | Archiving: SupportedReplication: Supported +Managed Volume | Archiving: SupportedReplication: Supported +Physical Hosts | Filesets | Archiving: SupportedReplication: Supported +NAS Systems | Archiving: SupportedReplication: Supported +Windows Volume | Archiving: SupportedReplication: Supported +NetApp Volumes (SnapMirror Cloud) | Archiving: SupportedReplication: Not supported +Kubernetes | Kubernetes | Archiving: Not supportedReplication: Supported +Microsoft Exchange | Exchange | Archiving: SupportedReplication: Not supported +Cloud objects +Microsoft 365 | Microsoft 365 | Archiving: Not supportedReplication: Not supported +Microsoft Azure | Azure VM/Managed Disk | Archiving: SupportedReplication: Supported +Azure SQL Databases | Archiving: SupportedReplication: Not supported +Azure SQL Managed Instances | Archiving: SupportedReplication: Not supported +Amazon Web Services | AWS EC2/EBS | Archiving: SupportedReplication: Supported +AWS RDS | Archiving: Not supportedReplication: Supported +Google Cloud Platform | GCE Instance/Disk | Archiving: Not supportedReplication: Not supported + *[ > ]: and then diff --git a/saas_supported_rep_targets_for_failover.md b/saas_supported_rep_targets_for_failover.md new file mode 100644 index 0000000000000000000000000000000000000000..5a0c0aa425b8de52a7e564cf17fe0a6d07920df2 --- /dev/null +++ b/saas_supported_rep_targets_for_failover.md @@ -0,0 +1,25 @@ +# Supported replication targets for failover operations + +Source: https://docs.rubrik.com/en-us/saas/saas/supported_rep_targets_for_failover.html + +--- + +# Supported replication targets for failover operations + +RSC supports specific types of replication targets for failover operations. + +The following table lists the supported replication source and target combinations for a failover operation to succeed. + +Replication source | Replication target +---|--- +Rubrik Brik | Rubrik Brik +Rubrik Edge | Rubrik Brik +Rubrik E1000 | Rubrik Brik +Rubrik Brik | Rubrik Edge (30 TB) + +The following table lists the replication source and target combination that is not supported for performing a failover operation. + +Replication source | Replication target +---|--- +Rubrik Brik | Rubrik Edge + *[ > ]: and then diff --git a/saas_supported_rubrik_cdm_instance_types.md b/saas_supported_rubrik_cdm_instance_types.md new file mode 100644 index 0000000000000000000000000000000000000000..43e93a7739da2add686bf2cd4d4e22f0883af98f --- /dev/null +++ b/saas_supported_rubrik_cdm_instance_types.md @@ -0,0 +1,19 @@ +# Supported Rubrik CDM instance types + +Source: https://docs.rubrik.com/en-us/saas/saas/supported_rubrik_cdm_instance_types.html + +--- + +# Supported Rubrik CDM instance types + +RSC supports several Rubrik CDM instance types. + +Through RSC you can manage the data protection capabilities of several types of compute instances that are running Rubrik software. RSC supports the following instance types: + + * Rubrik CDM running as a cluster on a Rubrik appliance + * Rubrik Cloud Cluster ES on AWS + * Rubrik Cloud Cluster ES on Azure + * Rubrik Edge running on a supported hypervisor + * Rubrik CDM running as a cluster on third-party hardware + + *[ > ]: and then diff --git a/saas_supported_rubrik_cdm_instance_types_2.md b/saas_supported_rubrik_cdm_instance_types_2.md new file mode 100644 index 0000000000000000000000000000000000000000..860f8ff6c004c475bb830c4dcb256b2ac3e564c0 --- /dev/null +++ b/saas_supported_rubrik_cdm_instance_types_2.md @@ -0,0 +1,19 @@ +# Supported Rubrik CDM instance types + +Source: https://docs.rubrik.com/en-us/saas/saas/supported_rubrik_cdm_instance_types_2.html + +--- + +# Supported Rubrik CDM instance types + +RSC supports several Rubrik CDM instance types. + +Through RSC you can manage the data protection capabilities of several types of compute instances that are running Rubrik software. RSC supports the following instance types: + + * Rubrik CDM running as a cluster on a Rubrik appliance + * Rubrik Cloud Cluster ES on AWS + * Rubrik Cloud Cluster ES on Azure + * Rubrik Edge running on a supported hypervisor + * Rubrik CDM running as a cluster on third-party hardware + + *[ > ]: and then diff --git a/saas_switching_sla_domains.md b/saas_switching_sla_domains.md new file mode 100644 index 0000000000000000000000000000000000000000..f1853db269f633bdd185270cf80f63ee9a2957b8 --- /dev/null +++ b/saas_switching_sla_domains.md @@ -0,0 +1,51 @@ +# Switching SLA Domains + +Source: https://docs.rubrik.com/en-us/saas/saas/switching_sla_domains.html + +--- + +# Switching SLA Domains + +To manage and protect multiple workloads across Rubrik clusters, switch SLA Domains from a Rubrik cluster to RSC SLA Domains. + +## Before you begin + +Ensure the following: + + * Connect the Rubrik cluster and any replication targets on the Rubrik cluster to RSC. + * Create the appropriate users and roles in RSC for managing SLA Domains. + * Review the information in [Changes in SLA Domains after switching](changes_sla_domains_after_switching.html "Information about the functionality changes in SLA Domains after switching to align with the new architecture, enhancing centralized management.") and [Changes in SLA Domains created on a Rubrik cluster](changes_sla_domains_created_on_rubrik_cluster.html "Information about the functionality changes in the SLA Domains created on a Rubrik cluster. These changes align with the new architecture, enhancing centralized management.") about the changes that occur after switching SLA Domains. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click SLA Domains. + +The SLA Domains page appears. + + 4. Click Switch SLA Domains. + +The Switch SLA Domains page appears. + + 5. Click Select SLA Domains. + 6. Click Ready to switch. + 7. Hover over the SLA Domain that you want to switch and click Switch SLA Domains. + +You can select multiple SLA Domains for switching SLA Domains in batches. + +The Switch Selected SLA Domains dialog box appears. + + 8. Click Switch. + +The data protection policies and snapshots for workloads remain unchanged during the switch. + +A message appears indicating that the switch process for an SLA Domain has been initiated. The switch might take a few minutes to complete. To monitor the progress of the switch, click the link to the Events page provided in the message. + +## Results + +The switched SLA Domain is displayed under the Switched to RSC tab on the Switch SLA Domains page. + *[ > ]: and then diff --git a/saas_switching_ui_language_japanese.md b/saas_switching_ui_language_japanese.md new file mode 100644 index 0000000000000000000000000000000000000000..3dcfe29584378198fd67edf351be89904141ad49 --- /dev/null +++ b/saas_switching_ui_language_japanese.md @@ -0,0 +1,26 @@ +# Switching RSC user interface language to Japanese + +Source: https://docs.rubrik.com/en-us/saas/saas/switching_ui_language_japanese.html + +--- + +# Switching RSC user interface language to Japanese + +To view the user interface of RSC in Japanese language, open the User Preferences page and switch the language to Japanese. + +## Procedure + + 1. Log in to RSC. + 2. Open the silhouette menu and select User Preferences. + +The User Preferences page appears. + + 3. Click Language. + +The Language page appears. + + 4. Select Japanese. + +## Results + +RSC switches the language of the user interface to Japanese. diff --git a/saas_system_config_privileges.md b/saas_system_config_privileges.md new file mode 100644 index 0000000000000000000000000000000000000000..17958fdea6febb7da939767fa45fef7b7488c2a2 --- /dev/null +++ b/saas_system_config_privileges.md @@ -0,0 +1,122 @@ +# System configuration privileges + +Source: https://docs.rubrik.com/en-us/saas/saas/system_config_privileges.html + +--- + +# System configuration privileges + +Details of system configuration privileges that are available for assignment to different roles in RSC. + +The following table describes the RSC permissions for the system configuration. Permission type | Permissions +---|--- +Cluster configuration | + + * View clustersEnables users to view the Clusters page. Note: Users who have the View clusters permission, but not the View Events permission, cannot view events on the Clusters page. + * Add clustersEnables users to add a cluster from the Clusters page.Note: When selecting the Add clusters permission, you also need to select the View clusters permission to view the added cluster. + * Upgrade clustersEnables users to upgrade the Rubrik CDM software running on a Rubrik cluster. + * Remove clustersEnables users to remove a cluster from RSC when the cluster is no longer needed, such as when decommissioning the cluster or transferring it to another RSC account. + * Manage cluster settingsEnables users to manage various cluster settings, such as network, general cluster settings, and IPMI. + * Manage support tunnelsEnables users to open and close a support tunnel for a Rubrik cluster. + * Manage cluster disksEnables users to remove disks from a Rubrik cluster and set up new disks on a Rubrik cluster. + * Add cluster nodesEnables users to add a node to physical clusters, such as Rubrik appliances and supported third-party hardware servers. + * Recover cloud clusterEnables users to recover a cloud cluster from RSC. + * Remove cluster nodesEnables users to permanently remove a node from a Rubrik appliance cluster or supported third-party hardware cluster to repurpose the node or to update a cluster configuration during a hardware refresh. + +Note: You can apply these permissions to some or all of the existing clusters, or to any cluster that you have added for future use. +SMB settings | + + * Enables users to view SMB domains + * Enables users to manage SMB domains + + +Replication configuration | + + * Use cluster as a replication targetEnables users to use the Rubrik cluster for which this permission has been assigned as a target cluster in an SLA Domain. + * View replication settingsEnables users to view the replication pairing of the Rubrik clusters on which this is assigned.Note: To view a replication pair, you must have view permissions for both clusters of the pair. + + +System preferences | + + * View system preferencesEnables users to manage permissions related to RSC system preferences menu. + * Edit system preferencesEnables users to edit system preferences settings. + + +Certificate management | + + * View certificates and certificate signing requestsEnables users to view certificates on RSC. + * Manage certificates and certificate signing requestsEnables users to manage certificates on RSC. + + +Events | + + * View non-system eventsEnables users to view events related to configuration, backup, recovery, archival, and replication jobs that are running in the system. + * View system eventsEnables users to view events that are related to hardware, diagnostics, and system. + * Cancel a running activityEnables users to stop a running Rubrik cluster job that can be canceled either from the Rubrik cluster or from the RSC Events tab. + * View audit logsEnables users to view the audit log. + * View webhooksEnables users to view the configured webhooks. + * Manage webhooksEnables users to create, edit, enable, disable, and delete a webhook. + +Note: RSC applies the selected permission to all non-system events for all objects, whether or not the user has access to the object. +Reports | + + * View reportsEnables users to view reports.Note: When users have the View reports permission, but do not have access to the Events, the Events report becomes unavailable to the users. + * Edit reportsEnables users to modify report configurations.Note: When selecting the Edit reports permission, also select the View reports permission. + * Create reports + * Delete reports + * Assign role-based access control (RBAC) on custom reportsEnables administrators and owners to assign user permissions to particular reports or to all reports. + + +Manage legal hold | Enables users to place and remove legal hold +Cloud account management | For the listed cloud accounts: + + * View cloud account configuration + * Manage cloud account configurationEnables users to manage cloud account configurations, such as adding, editing, and deleting storage cloud account configuration settings. + +Note: This set of permissions is available to users with active subscriptions to the specific cloud native protection on RSC. +Archival and replication settings | + + * View archival location + * Add archival location + * Edit archival location (pause/resume, enable/disable, and promote cluster as reader) + * Delete archival location + * View replication settings + * Edit replication settings + * View network throttle settings + * Edit archival network throttle settings + * Edit replication network throttle settings + + +Access management | + + * View user accessEnables users to view Access management settings. + * Manage user accessEnables users to edit Access management settings.Note: Users with this permission can promote themselves to administrator. + + +Integrations | + + * View Zscaler DLP configurationEnables users to view Zscaler DLP configurations. + * Manage Zscaler DLP configurationEnables users to create, update, and delete Zscaler DLP configurations. + + + +The following table describes Rubrik CDM permissions that administrators can assign to RSC roles when the Federated access permission is enabled. Permission type | Permissions +---|--- +System configuration | + + * View system configurationEnables RSC users to view system configuration settings for the connected Rubrik clusters. + * Edit system configurationEnables RSC users to edit system configuration settings for the connected Rubrik clusters. + + +Network configuration | + + * View network settingsEnables RSC users to view network settings for the connected Rubrik clusters. + * Edit network settingsEnables RSC users to edit network settings for the connected Rubrik clusters. + + +Support configuration | + + * View support settingsEnables RSC users to view support settings for the connected Rubrik clusters. + * Edit support settingsEnables RSC users to edit support settings for the connected Rubrik clusters. + + *[ > ]: and then diff --git a/saas_taking_an_on_demand_snapshot_of_snapmirror_cloud.md b/saas_taking_an_on_demand_snapshot_of_snapmirror_cloud.md new file mode 100644 index 0000000000000000000000000000000000000000..7b35159ef249ac72e0834489d3d6627dcf10d304 --- /dev/null +++ b/saas_taking_an_on_demand_snapshot_of_snapmirror_cloud.md @@ -0,0 +1,46 @@ +# Taking an on-demand snapshot of a NetApp volume + +Source: https://docs.rubrik.com/en-us/saas/saas/taking_an_on_demand_snapshot_of_snapmirror_cloud.html + +--- + +# Taking an on-demand snapshot of a NetApp volume + +In addition to policy-based snapshots, you can take snapshots of NetApp volumes by using the ondemand snapshot process. + +## Before you begin + +On-demand snapshots can only be taken for volumes that already have SLA Domain protection configured. + +## Procedure + + 1. Log in to RSC. + 2. Click Inventory. + +The Inventory page appears. + + 3. Click the SnapMirror Cloud inventory card. + +The SnapMirror Cloud page appears. + + 4. Click the name of a NetApp host. + +The details page for the selected host appears. + + 5. Click the name of a volume. + +The object details page for the selected volume appears. + + 6. Click Take On Demand Snapshot. + +Changing the SLA Domain associated with a SnapMirror Cloud archival location or using a different SLA Domain for on-demand snapshots results in a new, full backup. Previous backups are no longer associated with the NetApp volume, and you cannot use them for incremental snapshot backups. + +The Take On Demand Snapshot wizard appears, and the SLA Domain assigned to the NetApp volume is selected. You cannot select another SLA Domain. + + 7. Click Next. + 8. Confirm the summary information and click Confirm. + +## Results + +RSC takes an on-demand snapshot of the selected NetApp volume and protects the snapshot using the SLA Domain that you assigned to the NetApp volume. + *[ > ]: and then diff --git a/saas_test_and_production_failover.md b/saas_test_and_production_failover.md new file mode 100644 index 0000000000000000000000000000000000000000..f4be0019b26931c7f4ab7e77189c107d4457ddc2 --- /dev/null +++ b/saas_test_and_production_failover.md @@ -0,0 +1,126 @@ +# Test and production failover + +Source: https://docs.rubrik.com/en-us/saas/saas/test_and_production_failover.html + +--- + +# Performing cyber recovery using Export on AWS virtual machines# Performing cyber recovery using Export on AWS virtual machines + +You can perform an export to recover selected AWS virtual machines to a local or remote recovery environment. + +## About this task + +The Export recovery option creates virtual machines from snapshots and uses the selected target storage resources for the virtual machines. You can also recover to shared infrastructure with IP networks that are not connected to production environments. You can save your recovery specifications as a Recovery Plan. + +If you are recovering to an isolated environment, ensure that you include all fundamental infrastructure services required for these virtual machines to function. These services might include, but are not limited to, DNS and authentication services. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Objects. + +The Objects tab appears with a detailed list of objects, including the assigned SLA Domain and name of the Rubrik cluster. + + 4. Click AWS EC2. + +The list of all AWS virtual machines appear. + + 5. Select the objects to recover and click Start **Cyber Recovery** . + +All objects selected for recovery must have at least one snapshot and must belong to the same subscription and region. + + 6. **Optional:** Review the What is Cyber Recovery page and click Start. + +This informational page summarizing the Cyber Recovery process appears if you are performing a cyber recovery for the first time. If you do not want this page to appear in future, select the option to not show the page again. + + 7. In Recovery Name, enter a name for the recovery. + +If you do not enter a recovery name, the recovery is named using a combination of the recovery type, recovery date, and recovery number by default, where number stands for an assigned number. + +When there is a Recovery Plan, RSC uses the name of the Recovery Plan in place of the recovery type. + + 8. In Recovery Target, select a target AWS account for the recovery. + +RSC supports cyber recovery for AWS virtual machines from the same region as the recovery source account. + + 9. **Optional:** Select an option to export tags for all virtual machines. + 10. Select an option to launch in the power-off state. + +If you select this option, the target virtual machines are turned off after you recover them and you cannot assign a boot priority. + + 11. In Error Handling, select an option. + +Option| Description +---|--- +Pause and resume recovery manually after assessing the error | RSC pauses the recovery and resumes after assessing the error.You can resume paused recoveries from the Recoveries page or the recovery details page. +Abort recovery and clean the recovered objects | If RSC encounters any errors during the recovery, it stops the recovery and removes any changes to the recovery job and resources. + + 12. Click Next. + 13. Select a snapshot for recovery for each object. + +You can filter based on the Anomaly Detection outcome. Options include the following: + +Option| Description +---|--- +Non-quarantined and non-anomalous | Provides non-quarantined and non-anomalous snapshots as options for recovery. +Quarantined | Provides quarantined snapshots as options for recovery. A quarantined snapshot contains potentially malicious files or objects and has been placed in quarantine. +Anomalous | Provides anomalous snapshots as options for recovery. An anomalous snapshot is a snapshot that has been flagged by Data Threat Analytics as indicative of anomalous behavior. +Do not consider | Provides a snapshot without considering snapshot status. + +You cannot complete recovery when there are no snapshots available for an object. + + 14. Assign a boot priority order for the objects you want to recover and select their priority group. + +The priority group assigned to a virtual machine determines the boot order of the virtual machine on the recovery site. Multiple virtual machines in the same priority group boot simultaneously. Rubrik recommends that you prioritize recovering Identity and Access Management and other core infrastructure services. + + 15. **Optional:** Turn on Enable pauses between priority groups. + +RSC displays the specified pauses during recovery in minutes. + + 16. Click Next. + +The Assign Target Compute Resources page appears. + + 17. Select how you want to set up encryption and access for the selected objects. + +Select| To +---|--- +Skip KMS key, key pair, and IAM instance profile | Choose to use the same encryption settings as the source object. Key Management Service (KMS) key, key pair, and IAM instance profile enable you to encrypt the objects. Unencrypted snapshots create unencrypted virtual machines and EBS volumes. Encrypted virtual machines and Elastic Block Store (EBS) volumes are encrypted using the source Customer Managed Key (CMK). Use the key pair and password of the original instance to access the exported instance. +Configure encryption and access | Select options to encrypt with a platform-managed key, encrypt with the same customer-managed key, or select keys individually. + + 18. Click Next. + +The Target Network page appears. + + 19. Select a VPC and subnet. + 20. **Optional:** Select one or more Security Groups. + 21. Click Next. + +The Confirmation page appears. + + 22. **Optional:** Turn on Save as Recovery Plan to save your recovery specifications. + +A Recovery Plan saves information about the selected objects, their recovery order, and the target resources. You can use this plan to perform a cyber recovery in the future. If any of the virtual machines you selected for this recovery are relics, the Recovery Plan cannot be saved for future use. + + 23. For saving as a Recovery Plan, in **Recovery Plan Name** Details, enter a name for the Recovery Plan. + 24. Click Confirm. + +## Results + +RSC starts the cyber recovery and updates the Recoveries page. + +# Test and production failover + +Test failover operations have several differences from production failover operations. + +Production failover | Test failover +---|--- +Source virtual machines are shut down. | Source virtual machines are unaffected. +Target virtual machines boot on the production network specified in the recovery plan | Target virtual machines boot on the test network specified in the recovery plan. +Target virtual machines can be assigned an SLA Domain for data protection. | Target virtual machines are unprotected. +Target environment not optimized for post-test cleanup. | Test environment optimized for post-test cleanup. + *[ > ]: and then diff --git a/saas_testing_failover.md b/saas_testing_failover.md new file mode 100644 index 0000000000000000000000000000000000000000..5c04e6b3f210003453feea772a6ea4b5eba3fd8d --- /dev/null +++ b/saas_testing_failover.md @@ -0,0 +1,50 @@ +# Testing a failover + +Source: https://docs.rubrik.com/en-us/saas/saas/testing_failover.html + +--- + +# Testing a failover + +Test a failover for a selected Recovery Plan using the most recent snapshots. + +## Before you begin + +You must assign Change Memory and Create Folder privileges in the vCenter Server to enable successful failover operations. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears, listing all Recovery Plans. + + 4. Click a Recovery Plan from the list. + +The Recovery Plan details page appears. + + 5. Click and select Start Test failover. + +The Test failover wizard appears. + + 6. Choose a recovery point in time. + +Option| Description +---|--- +Latest available snapshot | Click Edit to select a different snapshot. The test failover uses the most recent snapshot for each virtual machine in the Recovery Plan. +Select a point in time | Click Select to choose a snapshot for each virtual machine. You can specify a snapshot to use for each virtual machine in the Recovery Plan. Optionally, you can select Only use non-quarantined and non-anomalous snapshots based on the Anomaly Detection outcome. + + 7. **Optional:** Select the Ignore network reconfiguration errors and continue checkbox. + +When you select this option, RSC ignores network configuration and post script errors and recovery will not fail due to network configuration or post script failures. + + 8. Click Recover. + +## Results + +RSC displays a Recovery Plan event in the Events tab of the Recovery Plan details page and RSC Events page. + *[ > ]: and then diff --git a/saas_tests_for_disaster_recovery_failover.md b/saas_tests_for_disaster_recovery_failover.md new file mode 100644 index 0000000000000000000000000000000000000000..d6ef83b689b16d438d4d641387ceba82b41891c4 --- /dev/null +++ b/saas_tests_for_disaster_recovery_failover.md @@ -0,0 +1,16 @@ +# Tests for disaster recovery failover + +Source: https://docs.rubrik.com/en-us/saas/saas/tests_for_disaster_recovery_failover.html + +--- + +# Tests for disaster recovery failover + +Failover configurations are tested by initiating a test failover from the primary site to the secondary site. + +Test failovers use specified test networks configured in the Recovery Plan to prevent IP address conflicts and potential disruption to the primary site. A test failover demonstrates the capability of running applications on the recovery site and the ability to recover applications from the recovery site. + +During the test failover, the production environment keeps running on the primary site and continues to replicate data to the recovery target. After the failover test, RSC cleans up the virtual machines used for the test from the recovery environment. + +During a test failover, RSC instantiates the latest snapshots of each virtual machine in the Recovery Plan, maps the resources as defined in the Recovery Plan, and brings up the virtual machines based on the priority order defined in the Recovery Plan. After the test failover, when you trigger the Cleanup Test Recovery workflow,RSC cleans up the recovered virtual machines at the recovery site. + *[ > ]: and then diff --git a/saas_threat_hunt_details.md b/saas_threat_hunt_details.md new file mode 100644 index 0000000000000000000000000000000000000000..0ec708516ec8b8a0462d4b539d3982370e2ea710 --- /dev/null +++ b/saas_threat_hunt_details.md @@ -0,0 +1,21 @@ +# Threat hunt details + +Source: https://docs.rubrik.com/en-us/saas/saas/threat_hunt_details.html + +--- + +# Threat hunt details + +The Threat Hunts page provides comprehensive information about threat hunts and the matches identified over time. + +Threat hunting is available as part of the Rubrik Enterprise edition. + +You can use threat hunt results to identify potentially malicious files and the snapshots where they were present and thus avoid malware reinfection during recovery. You can filter the information on the Threat Hunts page using the following filters: + * Hunt Status + * IOC Matches + * Time Range + * Cluster/Cloud Provider + * Quarantine Status + +When you change the filter selection, the hunt numbers on the page change to display the relevant information. You can click a hunt to view relevant details. + *[ > ]: and then diff --git a/saas_threat_hunt_object_details.md b/saas_threat_hunt_object_details.md new file mode 100644 index 0000000000000000000000000000000000000000..f43f2a4560c78aad9fc9a8f3f8991e1185da8f84 --- /dev/null +++ b/saas_threat_hunt_object_details.md @@ -0,0 +1,17 @@ +# Threat hunt object details + +Source: https://docs.rubrik.com/en-us/saas/saas/threat_hunt_object_details.html + +--- + +# Threat hunt object details + +Provides information about the threat hunt object details page. When you open a threat hunt object, you can see all the details of the files that matched the hunt. + +The details page provides information about the hunts matched with objects and the actions you can take to protect them. You can quarantine and remove specific objects from quarantine from this page. RSC does not support quarantine for cloud workloads. You can filter the threat hunt details with the following filters: + * Object Scan Status + * Cluster/Cloud Provider + * Match Type + * Object Type + * Quarantine status + *[ > ]: and then diff --git a/saas_threat_monitoring.md b/saas_threat_monitoring.md new file mode 100644 index 0000000000000000000000000000000000000000..ff67fd9f86fb9146e6545df265934a2dba28ad1e --- /dev/null +++ b/saas_threat_monitoring.md @@ -0,0 +1,35 @@ +# Threat Monitoring + +Source: https://docs.rubrik.com/en-us/saas/saas/threat_monitoring.html + +--- + +# Threat Monitoring + +Threat Monitoring automatically and continuously scans snapshots for new and existing indicators of compromise, and provides visibility into potential threats. + +With an initial full scan at feature enablement, followed by incremental scans, Threat Monitoring scans snapshots for threats based on indicators of compromise (IOCs) from multiple threat intelligence sources. Threat Monitoring detects risk early by: + + * Identifying threat indicators within backups. + * Accelerating threat investigation. + * Reducing the threat duration and risk of reinfection during recovery. + +IOCs provide forensic evidence of potential intrusions on a host system or network. When enabled, Threat Monitoring automatically pushes a threat feed of Yet Another Recursive Acronym (YARA) rules and file hashes every 24 hours to all applicable Rubrik deployments. RSC uses a hash database created during backup indexing to perform the file hash scanning. After the threat feed is downloaded to the Rubrik cluster, subsequent Threat Monitoring jobs start YARA rule analysis using the threat feed details. The threat feed updates periodically to import new intelligence, as available, to identify threats. + +Threat Monitoring scans executable files in snapshots that are smaller than 15 MB in size. Threat Monitoring scans Windows files that have the following extensions: .acm, .ax, .bat, .cmd, .com, .cpl, .dll, .drv, .efi, .exe, .js, .jse, .msi, .mui, .ocx, .ps1, .psc1, .scr, .sys, .tsp, .vbe, .vbs, .wsf, and .wsh. Threat Monitoring scans only Linux files that have the executable bit set. + +Threat Monitoring uses two key detection methods: + + * YARA rule-based detection, which applies pattern-based analysis to identify potential threats, but does not rely on exact file-matching. As a result, YARA rules can sometimes generate false positives, detecting both malicious and benign files under the same logic. To maintain accuracy, RSC continuously monitors, reviews, and refines YARA rules, removing those that generate excessive false positives. + * Hash-based detection, which uses exact file-matching, ensuring high confidence in identifying known threats. + +Threat Monitoring uses only file hashes as IOCs to identify threats for Azure virtual machines and managed disks, Microsoft SharePoint and OneDrive objects, AWS EC2 instances and EBS volumes, and GCP GCE instances and persistent disks. For other workloads, Threat Monitoring supports monitoring with both YARA rules and file hashes as IOCs. + +For Rubrik clusters running CDM version 9.1.3-p2 and later, RSC offers the following capabilities: + + * Scanning using a full set of YARA rules and file hashes. + * File hash scanning using a hash database created during backup indexing. + * Incremental and full scanning of existing data. Incremental scans handle new data, while RSC performs full scans of existing data when IOC updates occur. For example, when hash IOCs are processed against the hash database and new YARA rules are applied to the last completed backups. + * Retroactively processing IOC updates, as well as up to 100 custom IOCs. + + *[ > ]: and then diff --git a/saas_threat_monitoring_details.md b/saas_threat_monitoring_details.md new file mode 100644 index 0000000000000000000000000000000000000000..7c23ba2264c2cdcc271f660253f8367ca201bbb2 --- /dev/null +++ b/saas_threat_monitoring_details.md @@ -0,0 +1,23 @@ +# Threat Monitoring details + +Source: https://docs.rubrik.com/en-us/saas/saas/threat_monitoring_details.html + +--- + +# Threat Monitoring details + +The Threat Monitoring page provides complete information about scanned objects and threats identified over a period of time. + +Threat Monitoring is available as part of the Rubrik Enterprise edition. + +The top bar on the Threats page provides information about scanned objects, malicious objects, and objects without threats. The page also provides a list of objects scanned for threats and potential threats found, with details about the matches, the detection time, and the match type. + +You can filter the information by the following options: + + * Detection time range + * Match type + * Object type + * Rubrik cluster + +When you change the filter selection, the object numbers on the page change to display the relevant information. You can also search for a specific object in the search bar and click an object name to view relevant object details. + *[ > ]: and then diff --git a/saas_threat_monitoring_object_details.md b/saas_threat_monitoring_object_details.md new file mode 100644 index 0000000000000000000000000000000000000000..17db264374f45b25377ba1cb98d530f8876f926f --- /dev/null +++ b/saas_threat_monitoring_object_details.md @@ -0,0 +1,45 @@ +# Threat Monitoring object details + +Source: https://docs.rubrik.com/en-us/saas/saas/threat_monitoring_object_details.html + +--- + +# Threat Monitoring object details + +The threat details page provides details of threats detected for a specific object and actions you can take to protect the object. + +Threat Monitoring is available as part of the Rubrik Enterprise edition. + +The threat details page shows file details for a matched object including the following: + + * File name and size + * First matched snapshot + +First snapshot in which Threat Monitoring found this file to be malicious. This might or might not be the first snapshot in which the file became malicious or the malicious file was introduced. + + * Match type + * Date and time the match was detected + +When you click a file name, the object card shows the following details: + + * The path for the specific file. + * Indicators of compromise (IOC) details including the IOC name, the threat intelligence source, the threat family, the author of the IOC, and IOC description. + +The object card also provides the file hashes of the malicious file. You can copy the file hashes for performing a threat hunt. + + * The affected snapshots indicated by Threat Monitoring. + +The first observed snapshot is the snapshot where the file was first observed. There might be older snapshots that contain the file, depending on the amount of data on the object. + +The first matched snapshot is the snapshot that confirmed that the file is infected based on the ingested threat feed. + +Rubrik recommends initiating a threat hunt to determine whether older snapshots contain the file and whether the file is malicious in older snapshots. + +For further investigation of the selected files, you can complete the following actions: + + * Quarantining files + * Removing files from quarantine + * Downloading files for forensics + * Disabling IOCs + + *[ > ]: and then diff --git a/saas_tm_enabling.md b/saas_tm_enabling.md new file mode 100644 index 0000000000000000000000000000000000000000..135aaf99b6a9efcaa898198ef4b47b5a731d4e4a --- /dev/null +++ b/saas_tm_enabling.md @@ -0,0 +1,33 @@ +# Enabling Threat Monitoring + +Source: https://docs.rubrik.com/en-us/saas/saas/tm_enabling.html + +--- + +# Enabling Threat Monitoring + +Enable Threat Monitoring to scan snapshots for threats based on indicators of compromise. + +## About this task + +Enable Threat Monitoring to receive alerts when threats are detected, so that an investigation can begin quickly. For Azure subscriptions and AWS accounts, Threat Monitoring scans only for file hashes. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Threat Analytics and select an option: + +Option| Description +---|--- +Clusters | Opens the Clusters page, displaying the list of Rubrik clusters for which you can enable Threat Monitoring.You can turn on Threat Monitoring only for Rubrik clusters connected to RSC. This option is not available when a cluster is unreachable or is running an unsupported version of CDM. +Cloud Accounts | Opens the Cloud Providers page, displaying the list of AWS accounts, Azure subscriptions, and GCP projects for which you can enable Threat Monitoring. +Microsoft 365 | Opens the Microsoft 365 page, displaying the list of Microsoft 365 subscriptions for which you can enable Threat Monitoring. + + +## Results + +Threat Monitoring is enabled and continuously scans new snapshots for IOCs, providing visibility into potential threats. The Threat Monitoring page appears, displaying the resulting threat matches. Messages about the Threat Monitoring status and results appear on the Event Logs page in RSC. diff --git a/saas_tm_prereqs_and_supported_workloads.md b/saas_tm_prereqs_and_supported_workloads.md new file mode 100644 index 0000000000000000000000000000000000000000..d30fdc78e2426c7e348ce9b8fa5429954f8cc2f9 --- /dev/null +++ b/saas_tm_prereqs_and_supported_workloads.md @@ -0,0 +1,51 @@ +# Prerequisites and supported workloads + +Source: https://docs.rubrik.com/en-us/saas/saas/tm_prereqs_and_supported_workloads.html + +--- + +# Prerequisites and supported workloads + +Threat Monitoring has specific prerequisites for enablement within RSC, as well as separate prerequisites for various workloads. + +Threat Monitoring is available to support the following workloads: + + * VMware, AHV, and Hyper-V virtual machines + * NAS filesets + * Linux and Windows servers + * Azure virtual machines, Blob storage, and managed disks + * Microsoft SharePoint and OneDrive + * Amazon EC2 instances, S3 buckets, and EBS volumes + * Kubernetes virtual machines + +Note: + +Threat Monitoring does not scan snapshots of Kubernetes virtual machines that have filesystem disks. + + * Kubernetes protection sets + +Note: + +Threat Monitoring does not scan snapshots of Kubernetes protection sets that have block volumes. + + * GCP GCE Instances + * GCP Disks + +The following prerequisites enable Threat Monitoring for data center workloads: + + * The cluster must be running CDM version 9.1.3-p2 or later. + * When running CDM version 9.2., the cluster must use CDM version 9.2.0-p3. + * Rubrik clusters running CDM version 9.0.3-p2 support Threat Monitoring, but do not support the custom intel feed, and they have limited features compared to later versions. + * AWS EC2 instances, Azure virtual machines, and GCP GCE instances must have Exocompute configured and indexing enabled for the object. + * For Kubernetes virtual machines, the Rubrik cluster must be running either CDM version 9.3.2 or later, or CDM version 9.4 or later. For Kubernetes protection sets, the Rubrik cluster must be running CDM version 9.3.3 or later, or CDM version 9.4 or later. + +Kubernetes virtual machines and protection sets with Kubernetes backups require enabling Threat Monitoring at the cluster level. + + * The object must be protected by an SLA Domain. + +The following prerequisites enable Threat Monitoring for cloud workloads: + + * AWS EC2 instances, Azure virtual machines, and GCP GCE instances must have Exocompute configured and indexing enabled for the object. + * The object must be protected by an SLA Domain. + + *[ > ]: and then diff --git a/saas_turning_off_ioc.md b/saas_turning_off_ioc.md new file mode 100644 index 0000000000000000000000000000000000000000..6b9a7ce0a14c26e54739a3f64e2f3542c4d6c277 --- /dev/null +++ b/saas_turning_off_ioc.md @@ -0,0 +1,41 @@ +# Turning off an IOC + +Source: https://docs.rubrik.com/en-us/saas/saas/turning_off_ioc.html + +--- + +# Turning off an IOC + +When the indicator of compromise is too noisy and is validated as a false positive by your security team, you can turn off the indicator of compromise in Threat Monitoring. + +## Before you begin + +Owner or administrator permissions are required to complete this task. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. On the navigation bar, click Threats. + +The Threat Monitoring page appears. + + 4. Click a threat. + +The threat page displays the file matches and IOC details. + + 5. Click Disable IOCs. + +If you turn off the selected IOC, Threat Monitoring no longer scans for that IOC. + +The Remove IOCs dialog box appears. + + 6. Click Remove. + +## Results + +Threat Monitoring turns off the selected IOC. + *[ > ]: and then diff --git a/saas_types_of_orchestrated_recovery.md b/saas_types_of_orchestrated_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..93f8713876c86862fee7fd29f3a1a6a854f8ae36 --- /dev/null +++ b/saas_types_of_orchestrated_recovery.md @@ -0,0 +1,37 @@ +# Types of Orchestrated Recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/types_of_orchestrated_recovery.html + +--- + +# Types of Orchestrated Recovery + +You can use the recovery type that is best suited for your virtual machine, environment, and recovery requirements in Orchestrated Recovery. + +## Cyber Recovery + +Cyber recovery helps you prepare for a cyber attack through proactive testing and automates end-to-end recovery during a security incident.Cyber Recovery helps you perform periodic recovery validation, attack simulations, and other security exercises. During an incident, you can use cyber recovery recovery for rapid recovery of applications in parallel to forensics in the production environment using pre-tested plans. Based on a previously created Recovery Plan, you can recover the selected virtual machines using the following options: + + * The Live Mount option allows for faster recovery by making data available directly from the Rubrik cluster through an NFS mount. It is better suited for workloads that are not performance-driven, and you can perform quick verification of recovered virtual machines during a security incident. RSC supports this recovery option for only VMware virtual machines and AHV virtual machines. + * The Export option takes longer to recover virtual machines, since it transfers the data to an external datastore. The Export option is recommended for performance-heavy and production workloads. RSC supports this recovery option for VMware virtual machines, AHV virtual machines, and Azure virtual machines. + +You can also recover virtual machines, relics, and replicas that are located on the target cluster. + +You can initiate a cyber recovery from the Objects page, even without a Recovery Plan, by using the Cyber Recovery wizard. You can select virtual machines based on threat hunt results, and recover the selected virtual machines using the applicable recovery option. + +## Disaster Recovery + +Disaster Recovery recovers virtual machines to a remote site based on a previously created Recovery Plan. For data center workloads, you must enable replication on the source Rubrik cluster of the virtual machines for this recovery. + +Disaster recovery can be of two types: test failover or production failover. While a test failover can be triggered periodically to verify the Recovery Plan configuration, a production failover can be triggered due to a disaster scenario or to migrate an application from one site to another. + +RSC performs a test failover or a production failover operation by exporting files and failing over to the virtual machine on the replication target cluster. In a production failover, RSC stops the virtual machine on the source cluster before starting the replicated virtual machine on the target cluster. For a production failover, the source virtual machines are eventually deleted once recovery is successful at the recovery destination. + +RSC supports this recovery option for only VMware virtual machines and AHV virtual machines. + +## In-place Recovery + +RSC performs an in-place recovery of a virtual machine according to the specifications in the Recovery Plan on the same Rubrik cluster where the source virtual machine is being protected. + +In-place recovery gets applications back on line faster by recovering directly to production using the latest snapshots that aren’t quarantined in a threat hunt or marked anomalous by Data Threat Analytics. Here, the Rubrik cluster overwrites the source virtual machines according to a Recovery Plan. + *[ > ]: and then diff --git a/saas_upgrade_preparation_and_prechecks.md b/saas_upgrade_preparation_and_prechecks.md new file mode 100644 index 0000000000000000000000000000000000000000..2fcd551a9826b0ddebc02b975e79c5b47260da24 --- /dev/null +++ b/saas_upgrade_preparation_and_prechecks.md @@ -0,0 +1,19 @@ +# Upgrade preparation and prechecks + +Source: https://docs.rubrik.com/en-us/saas/saas/upgrade_preparation_and_prechecks.html + +--- + +# Upgrade preparation and prechecks + +You can prepare the Rubrik CDM cluster for an upgrade process that also automatically includes a series of prechecks. + +An administrator can perform the cluster upgrade that includes a series of prechecks based on whether the type of upgrade selected is rolling or fast. The administrator can run the prechecks alone, without doing a complete upgrade and can avoid potential upgrade obstacles by running an optional precheck before upgrading. The administrator can resolve the upgrade obstacles to ensure a smooth and successful upgrade. + +Before upgrading a Rubrik cluster, you are required to confirm the following: + + * All Managed Volumes are in a read-only state. + * All Managed Volume live mounts have been deleted. + * All Live Mounts have been either deleted or powered off. + + *[ > ]: and then diff --git a/saas_user_auth.md b/saas_user_auth.md new file mode 100644 index 0000000000000000000000000000000000000000..0b144e56f45fc3018ca41dafd1bc6eedcc220bb0 --- /dev/null +++ b/saas_user_auth.md @@ -0,0 +1,12 @@ +# User authorization + +Source: https://docs.rubrik.com/en-us/saas/saas/user_auth.html + +--- + +# User authorization + +Information about explicit authorization of the user to perform actions on resources specified in the assigned roles. + +When you assign a role to the user, the user is explicitly authorized to perform actions on specific resources specified in the role. When a resource contains other objects, the user automatically has authorization on all the descendant objects. When you grant permissions to an SSO group, the users within the SSO group automatically have the permissions related to the SSO group. + *[ > ]: and then diff --git a/saas_user_insights.md b/saas_user_insights.md new file mode 100644 index 0000000000000000000000000000000000000000..b312a3df77c09758af178f61a6507071c6743235 --- /dev/null +++ b/saas_user_insights.md @@ -0,0 +1,21 @@ +# User Insights in Data Security Posture + +Source: https://docs.rubrik.com/en-us/saas/saas/user_insights.html + +--- + +# User Insights in Data Security Posture + +You can view changes in user access to sensitive data in the Insights widget in the Data Security Posture dashboard. You can use these insights to monitor and manage potential data security risks more effectively by setting appropriate access limits. + +The Insights widget in the Data Security Posture dashboard highlights changes within Active Directory (AD) group memberships, modifications to Access Control List (ACL) permissions, or the introduction of new sensitive records that result in increased user access to sensitive data. Data Security Posture uses the data from the current day and previous day to calculate user insights. The data is available in the RSC web UI for 30 days. + +The Insights widget is available only to users with the administrator or owner role. This widget provides granular information in these areas: + + * Changes in sensitive data + * Changes in the ACL that give greater access to users + * Changes in active directory memberships that give greater access to users + * Changes in sensitive data that give greater access to users + +Clicking the user or object link in an insight displays the specific page with further details. You can also view insights for the specific object or user by hovering over the Insights icon in the Identity Inventory and Objects pages. + *[ > ]: and then diff --git a/saas_users_access.md b/saas_users_access.md new file mode 100644 index 0000000000000000000000000000000000000000..48b4766bcf77074c05d84b0c4dffd0002b7041b1 --- /dev/null +++ b/saas_users_access.md @@ -0,0 +1,37 @@ +# Users and Access + +Source: https://docs.rubrik.com/en-us/saas/saas/users_access.html + +--- + +# Users and Access + +RSC provides role-based access control, and several methods for authenticating a user account. + +RSC offers role-based access control (RBAC) that restricts access based on the roles of individuals within an organization. Depending on the assigned role, access rights are restricted to the relevant associated information and resources. + +Permissions are assigned to specific roles, and roles are assigned to user accounts. + +RSC provides RBAC that enables administrators to restrict access to authorized users and to facilitate administration of users and permissions. RSC grants subsets of Rubrik function or customer infrastructure to specific roles. Role-based permissions control the ability to configure different Rubrik cluster features on RSC. + +RSC user management also helps to preserve organizational hierarchy and maintain default security by limiting the accessible account functions. Role-based access control management restricts access to features and resources within a Rubrik cluster to authorized users or groups. + +RSC manages different types of users, as described in the following table. + +User type | Description +---|--- +Local users | + + * Are created and managed on RSC. + * Have accounts in the local directory on the Rubrik cluster. + * Log in to RSC with their local account credentials. + * Can have more than one role assigned to their user accounts. + + +SSO users | + + * Are authenticated by a SAML identity provider. + * Are managed as an SSO group. + * Log in to RSC through single sign-on. + + *[ > ]: and then diff --git a/saas_viewing_anomaly_events_events_page.md b/saas_viewing_anomaly_events_events_page.md new file mode 100644 index 0000000000000000000000000000000000000000..23960c55db63454cc6b758774a592de51a560e97 --- /dev/null +++ b/saas_viewing_anomaly_events_events_page.md @@ -0,0 +1,39 @@ +# Viewing anomaly events from the Events page + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_anomaly_events_events_page.html + +--- + +# Viewing anomaly events from the Events page + +RSC provides information about detected anomaly events for a Rubrik cluster in the Events page. You can also investigate the specific snapshot for further details. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Events. + +The Events page appears. + + 4. In the Event type filter, select Anomaly. + +A list of anomaly events appears. + + 5. Click an anomaly event. + +VM Encryption Detection anomalies are indicated as Ransomware-Hypervisor in the details. + +The anomaly event details page appears. + + 6. **Optional:** Click Investigate snapshot to view snapshot details. + +This option is not available for anomalies flagged by VM Encryption Detection. + +## Results + +RSC provides anomaly event details as well as options to investigate the snapshot. + *[ > ]: and then diff --git a/saas_viewing_anomaly_events_from_the_critical_alert_email.md b/saas_viewing_anomaly_events_from_the_critical_alert_email.md new file mode 100644 index 0000000000000000000000000000000000000000..dfe96a9234aa8f7b2f121f54f043cab7f94e0b7a --- /dev/null +++ b/saas_viewing_anomaly_events_from_the_critical_alert_email.md @@ -0,0 +1,27 @@ +# Viewing anomaly events from the Critical Alert email + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_anomaly_events_from_the_critical_alert_email.html + +--- + +# Viewing anomaly events from the Critical Alert email + +View details of an anomaly event from the link provided in the Critical Alert email. + +## About this task + +In the Critical Alert email, Data Threat Analytics provides the event status, start time, event category, cluster name, object type, object name, suggested actions, and event time line. + +## Procedure + + 1. In the Data Threat Analytics Critical Alert email, click View in app to view the anomaly event details page on Data Threat Analytics. + 2. **Optional:** In Suggested actions, click Investigate snapshot. + +The Select files page appears. + + 3. **Optional:** Select the File changes or the Suspicious filter to filter files. + +## Results + +The Rubrik cluster provides an update to RSC when the recovery completes. + *[ > ]: and then diff --git a/saas_viewing_anomaly_events_from_the_dashboard.md b/saas_viewing_anomaly_events_from_the_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..91965578dac15f112700c804721424c6501a2ed8 --- /dev/null +++ b/saas_viewing_anomaly_events_from_the_dashboard.md @@ -0,0 +1,29 @@ +# Viewing anomaly events from the Dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_anomaly_events_from_the_dashboard.html + +--- + +# Viewing anomaly events from the Dashboard + +RSC provides detailed information about detected anomaly events in the Data Threat Analytics dashboard. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click the Anomalies widget. + +The Anomaly Detection page appears. + +VM Encryption Detection anomalies are indicated as Ransomware - Hypervisor. + + 4. Click an object name to view anomaly details. + +## Results + +The Anomaly event details page appears. + *[ > ]: and then diff --git a/saas_viewing_anomaly_reports.md b/saas_viewing_anomaly_reports.md new file mode 100644 index 0000000000000000000000000000000000000000..cf37dae97cdefed065db48152932dc467ea2bda3 --- /dev/null +++ b/saas_viewing_anomaly_reports.md @@ -0,0 +1,35 @@ +# Viewing anomaly reports + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_anomaly_reports.html + +--- + +# Viewing anomaly reports + +Anomaly reports contain information about anomaly snapshots and object anomalies captured by Data Threat Analytics. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Reports. + +The Reports page appears. + + 4. Click **Data Threat Analytics**. + +The list of anomaly reports appears. + + 5. Click an anomaly report. + +The selected anomaly report appears. + + 6. **Optional:** Select filters to apply to the Events page. + +## Results + +RSC fills the Anomaly report page with the aggregate values based on the selected filter. + *[ > ]: and then diff --git a/saas_viewing_classification_job_results.md b/saas_viewing_classification_job_results.md new file mode 100644 index 0000000000000000000000000000000000000000..01da251217fa03cf07b4c9d9e9702c8426f62091 --- /dev/null +++ b/saas_viewing_classification_job_results.md @@ -0,0 +1,44 @@ +# Viewing classification job results on demand + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_classification_job_results.html + +--- + +# Viewing classification job results on demand + +View classification job results on demand. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. On the navigation bar, click On Demand. + +The On Demand job page appears. + + 4. Click a classification job to view details. + +Select an object to browse the file system for that object. + +The classification details page appears. + + 5. **Optional:** In the Hits filter, select at least one predefined policy. + 6. **Optional:** Click Clear. + +Results for the selected policy or policies are removed from the results list. + + 7. **Optional:** Click Files with Hits. + +Selecting this option allows you to view the details of the discovered files. + +While browsing the object file system, type a search string in the Search field to find a discovered file. + +The discovered files page appears. + +## Results + +Data Security Posture displays the classification job results on demand. + *[ > ]: and then diff --git a/saas_viewing_oar_audit_logs.md b/saas_viewing_oar_audit_logs.md new file mode 100644 index 0000000000000000000000000000000000000000..9e60a50eb31733f58ffba7cfa8a400edd6ad8a94 --- /dev/null +++ b/saas_viewing_oar_audit_logs.md @@ -0,0 +1,27 @@ +# Viewing Orchestrated Recovery audit logs + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_oar_audit_logs.html + +--- + +# Viewing Orchestrated Recovery audit logs + +The Orchestrated Recovery Audit Logs page provides a chronological record of user-initiated actions during recovery operations. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. On the navigation bar, hover over Events and then select Audit Logs. + +The Audit Logs page appears. + + 4. **Optional:** Select filters to apply to the information on the Audit Logs page. + +## Results + +Based on the specified filters, Orchestrated Recoverydisplays the relevant audit logs. + *[ > ]: and then diff --git a/saas_viewing_oar_event_logs.md b/saas_viewing_oar_event_logs.md new file mode 100644 index 0000000000000000000000000000000000000000..718e3dd0c4c81b07a6f10e3e5161095c1d90afc0 --- /dev/null +++ b/saas_viewing_oar_event_logs.md @@ -0,0 +1,33 @@ +# Viewing Orchestrated Recovery event logs + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_oar_event_logs.html + +--- + +# Viewing Orchestrated Recovery event logs + +The Orchestrated Recovery Event Logs page provides a chronological record of operational details during recovery events. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. On the navigation bar, hover over Events and then select Event Logs. + +The Event Logs page appears. + + 4. **Optional:** Select filters to apply to the information on the Event Logs page. + +Orchestrated Recovery displays events based on the selected filters. + + 5. Click an event. + +The event timeline and additional event details appear. + +## Results + +Based on the specified filters, Orchestrated Recovery lists relevant events. When you select an event, Orchestrated Recovery provides historical information about that event. + *[ > ]: and then diff --git a/saas_viewing_quarantined_files.md b/saas_viewing_quarantined_files.md new file mode 100644 index 0000000000000000000000000000000000000000..af34b8976be2d5ddfed9961a2da20b20d79ec1c1 --- /dev/null +++ b/saas_viewing_quarantined_files.md @@ -0,0 +1,29 @@ +# Viewing quarantined files or objects in threat hunts + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_quarantined_files.html + +--- + +# Viewing quarantined files or objects in threat hunts + +You can view threat hunts that have quarantined files or objects as well as the number of impacted snapshots. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. Select One or More in the Quarantined Matches filter. + +This allows you to view threat hunts that have multiple quarantined files or objects. + +## Results + +Threat hunts with quarantined matches, the number of quarantined files, and the number of impacted objects and snapshots appear. + *[ > ]: and then diff --git a/saas_viewing_rp_details.md b/saas_viewing_rp_details.md new file mode 100644 index 0000000000000000000000000000000000000000..72dc2fe7d2f4cc27d42cd954406db0a2614280ce --- /dev/null +++ b/saas_viewing_rp_details.md @@ -0,0 +1,45 @@ +# Viewing Recovery Plans and recoveries + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_rp_details.html + +--- + +# Viewing Recovery Plans and recoveries + +View the configured Recovery Plans and their details. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Orchestrated Recovery**. + +The Objects page appears. + + 3. Click Recovery Plans. + +The Recovery Plans page appears, showing the list of all Recovery Plans. + + 4. Click the tab for the specific workload. + +You can choose from vSphere, AHV, or Azure virtual machines. + + 5. **Optional:** Click a Recovery Plan from the list. + +You can use the filter options provided to access a specific Recovery Plan. + +The Recovery Plans details page appears, showing the information in the different tabs. + + 6. Click Recoveries. + +You can filter recoveries by type, time range, Recovery Plan, or recovery name. + +The Recoveries page appears, showing the list of all recoveries. + + 7. **Optional:** Click a recovery name from the list. + +The recovery details page appears, displaying the information in the different tabs. + +## Results + +The Recovery Plans and recovery details display as selected. + *[ > ]: and then diff --git a/saas_viewing_sdd_events.md b/saas_viewing_sdd_events.md new file mode 100644 index 0000000000000000000000000000000000000000..740f6b5d6270020346858ebfc81a88a18caf8b86 --- /dev/null +++ b/saas_viewing_sdd_events.md @@ -0,0 +1,32 @@ +# Viewing Data Security Posture events + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_sdd_events.html + +--- + +# Viewing Data Security Posture events + +The Data Security Posture Events page provides a global view of all Data Security Posture events on the connected Rubrik clusters. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Security Posture**. + +The Data Security Posture dashboard appears. + + 3. Click Reports &Events. + 4. On the navigation bar, click Event Logs. + +Select any of the filters on the Event Logs page to sort the events shown. + +The Event Logs page displays events based on the selected filters. + + 5. Click an event. + +The timeline of the selected event and other details appear. + +## Results + +Based on the specified filters, Data Security Posture lists relevant events. Also, when an event is selected, Data Security Posture provides historical information about that event. + *[ > ]: and then diff --git a/saas_viewing_the_global_dashboard.md b/saas_viewing_the_global_dashboard.md new file mode 100644 index 0000000000000000000000000000000000000000..244de356619870069995ff6c05427b5255f5fc80 --- /dev/null +++ b/saas_viewing_the_global_dashboard.md @@ -0,0 +1,19 @@ +# Viewing the Global dashboard + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_the_global_dashboard.html + +--- + +# Viewing the Global dashboard + +Change views to the Global Dashboard to view summary information for RSC apps. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Global Dashboard. + +## Results + +The Global Dashboard appears. + *[ > ]: and then diff --git a/saas_viewing_threat_hunts.md b/saas_viewing_threat_hunts.md new file mode 100644 index 0000000000000000000000000000000000000000..9332556486dba831b59520c3af2a9bf08eff3cec --- /dev/null +++ b/saas_viewing_threat_hunts.md @@ -0,0 +1,33 @@ +# Viewing threat hunts + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_threat_hunts.html + +--- + +# Viewing threat hunts + +View the completed and in-progress threat hunts with details on matches found, impacted objects, and impacted snapshots. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. Click Hunts. + +The Hunts page displays the completed and in-progress threat hunts with details about the matches found and their impact. + + 4. **Optional:** Click a threat hunt card. + +The threat hunt details page opens. The Scanned Objects tab displays the impacted objects, files, and indicators of compromise (IOCs). + + 5. Click Parameters. + +The Details card on this page displays the parameters, limits, and file restrictions selected for the threat hunt. The IOCs card displays the key IOCs used for the threat hunt. + +## Results + +The Threat Hunts tab provides detailed information about completed and in-progress threat hunts. + *[ > ]: and then diff --git a/saas_viewing_threat_monitoring_info.md b/saas_viewing_threat_monitoring_info.md new file mode 100644 index 0000000000000000000000000000000000000000..9d87f6ed64a6e181f71da7c1e8df78a0c7873882 --- /dev/null +++ b/saas_viewing_threat_monitoring_info.md @@ -0,0 +1,37 @@ +# Viewing Threat Monitoring information + +Source: https://docs.rubrik.com/en-us/saas/saas/viewing_threat_monitoring_info.html + +--- + +# Viewing Threat Monitoring information + +To better understand the indicators of compromise and the affected snapshots, check the Threat Monitoring results for scanned objects. + +## Before you begin + +Ensure that you are using the Rubrik Enterprise edition. + +## About this task + +Threat Monitoring is available as part of the Rubrik Enterprise edition. + +## Procedure + + 1. Log in to RSC. + 2. Click and select **Data Threat Analytics**. + +The Data Threat Analytics dashboard appears. + + 3. On the navigation bar, click Threats. + +The Threat Monitoring page appears. + + 4. **Optional:** Click an object to view the threat and match details for that object. + +The Threat Monitoring details page for the specific object appears. + +## Results + +The Threat Monitoring page displays information about detected threats and matches. + *[ > ]: and then diff --git a/saas_vm_pre_post_backup_script_config.md b/saas_vm_pre_post_backup_script_config.md new file mode 100644 index 0000000000000000000000000000000000000000..a6ebc2113a0773e6930b91d195f6be9e7905e1ad --- /dev/null +++ b/saas_vm_pre_post_backup_script_config.md @@ -0,0 +1,79 @@ +# Configuring virtual machine backup scripts + +Source: https://docs.rubrik.com/en-us/saas/saas/vm_pre_post_backup_script_config.html + +--- + +# Configuring virtual machine backup scripts + +Configure pre- and post-backup scripts for ensuring application-consistent snapshots. + +## About this task + +This topic describes a feature or features that Rubrik is gradually rolling out to customers. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the vSphere VMs inventory card. + +The vSphere VMs page appears. + + 5. Click the name of a virtual machine. + +To help find virtual machines, use the filters, sort the entries by column heading, or use the search field. + + 6. Open the ellipsis menu and select Configure pre/post scripts. + +The Configure Pre/Post Scripts wizard appears. + + 7. **Optional:** In Pre-backup script, enter the full path for the pre-backup script. + +The full path is relative to the root of the guest OS file system. + + 8. **Optional:** Select Cancel backup if pre-backup script fails. + 9. (Required when available) In Timeout, enter an integer value. + +The value represents the number of seconds before the Rubrik cluster terminates the pre-backup script because the script cannot be completed. + + 10. **Optional:** In Post-snap script, enter the full path for the post-snap script. + +The full path is relative to the root of the guest OS file system. + + 11. (Required when available) In Timeout, enter an integer value. + +The value represents the number of seconds before the Rubrik cluster terminates the post-snap script because the script cannot be completed. + + 12. **Optional:** In Post-backup script, enter the full path for the post-backup script. + +The full path is relative to the root of the guest OS file system. + + 13. (Required when available) In Timeout, enter an integer value. + +The value represents the number of seconds before the Rubrik cluster terminates the post-backup script because the script cannot be completed. + + 14. Click Next. + +The wizard advances to Guest OS Credentials of the Configure Pre/Post Scripts. + + 15. Select one of the following. + +Option| Description +---|--- +Use existing guest OS credentials | Attempts all saved credentials on the cluster if no selection is made. +Add new guest OS credentials | Add new guest OS credentials. To add guest OS credentials you must have the Manage guest OS credentials permission. + + 16. Click Save. + +## Results + +RSC successfully configures the pre-backup and post-backup scripts. + *[ > ]: and then diff --git a/saas_vmc_adding_a_vmc_vcenter_server_4.md b/saas_vmc_adding_a_vmc_vcenter_server_4.md new file mode 100644 index 0000000000000000000000000000000000000000..622f9754c20fc5af6167d25d1ae4b12c6ec0b051 --- /dev/null +++ b/saas_vmc_adding_a_vmc_vcenter_server_4.md @@ -0,0 +1,125 @@ +# Adding a VMware Cloud vCenter Server + +Source: https://docs.rubrik.com/en-us/saas/saas/vmc_adding_a_vmc_vcenter_server_4.html + +--- + +# Adding a VMware Cloud vCenter Server + +Protect the virtual machines of a vCenter Server hosted in VMware Cloud by adding the vCenter Server to a Rubrik Cloud Cluster. + +## Before you begin + +The Rubrik cluster uses dedicated ports to access a software-defined data center (SDDC). Review the list of required ports in [HotAdd proxy port requirements](../ports/hotadd_proxy_port_requirements.html "A Rubrik Cloud Cluster requires access to several TCP ports in order to protect virtual machines in a cloud-based environment."). + +## About this task + +Rubrik clusters attempt to initiate a connection with the vCenter Server using vCenter Server 6.0 or later protocols, which require trusted root certificate. + +When a trusted CA root certificate is not provided, the Rubrik cluster relies on Public Key Intrastructure (PKI) or on a Trust On First Use (TOFU) approach to authenticate the vCenter Server. Depending on the network environment, TOFU might not ensure secure operation. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the vSphere VMs inventory card. + +The vSphere VMs page appears. + + 5. Click Manage vSphere. + +The vSphere Servers page appears. + + 6. Click Add Server/Host → Add vCenter Server + +The Add vCenter Server wizard appears. + + 7. Click Next. + +The Select a vCenter page of the wizard appears. + + 8. In VCenter, enter the fractal name that AWS provided for the VMware Cloud (VMC) vCenter server. + +For example, `vcenter.sddc-xxxxxxxx.fractal.vmwarevmc.com`. + + 9. In Username, enter the name of the user account assigned to the Rubrik Cloud Cluster. + +The value of the username must be in the vmcusername@vmcdomainname format. + +The username must be the name of a VMC user account with the requisite privileges. Using an incorrect username format results in failure to deploy HotAdd Proxies. The VMC documentation provides details on enabling and using a VMC user. + + 10. In Password, enter the password associated with the VMC user account. + 11. **Optional:** Select Automatically link discovered virtual machines (Recommended). + +When adding a vCenter Server, RSC begins automatically linking discovered virtual machines when it adds a vCenter Server. + + 12. Do not select Enable HotAdd transport mode for on-premises vCenter (Export). + +Exporting snapshots using the HotAdd transport mode does not apply to vCenter Servers in the cloud. + + 13. **Optional:** Click Advanced Settings to add a Certificate Authority (CA) certificate for TLS validation. + +The page expands to show a field to provide the trusted root certificate. + + 14. When adding the optional trusted CA, paste the text of the trusted CA root certificate for the vCenter in the field. + 15. Click Next. + +The Select Rubrik Clusters page appears. + + 16. Select a Rubrik cluster to handle the backup, recovery, replication, and archiving operations for the vCenter Server. + +You can select multiple clusters. The selected Rubrik clusters must be in connected state. + + 17. Click Add. + +The Validate Connection page appears. The page displays the selected Rubrik clusters and their state of connectivity. + + 18. Click Done. + +The Proxy Virtual Machine Network Selection page appears. + + 19. In Network segment, select a network segment for the HotAdd proxy virtual machines. + 20. In IP address type, select an option. + * DHCP + * Static IP + 21. Configure values for IP address, Subnet mask, Gateway, and DNS server. + 22. **Optional:** Turn on Network Throttling. + +When Network Throttling is enabled, you can specify the maximum network bandwidth, in Mbps, for backup and export between VMC and AWS Virtual Private Cloud. + + 23. Click Done. + +When multiple Rubrik clusters are selected for the vCenter Server, the Set Compute Resources Visibility dialog box appears. + + 24. Locate the Rubrik cluster to configure the resource visibility for that cluster. + +All compute clusters are visible to all Rubrik clusters by default. When you select Customize, you can specify the vCenter Server resources visible to each Rubrik cluster. Resources that are not specified are hidden. + + 25. In the Compute cluster 1 section, in Compute cluster, select a compute cluster to be protected by the Rubrik cluster. + 26. **Optional:** In Host group, select a host group within the selected compute cluster. + 27. Select VMware vSphere Metro Storage Cluster. + +Selecting this option specifies whether the vCenter Server is a Metro Storage Cluster. + + 28. **Optional:** Click Add Another Compute Cluster. + +Selecting this option adds another compute cluster to the same Rubrik cluster. + + 29. **Optional:** Configure the resource visibility for all the Rubrik clusters. + +If additional Rubrik clusters are connected to the vCenter Server, you can configure the additional clusters to protect different compute clusters. + + 30. Click Save. + 31. Click Done. + +## Results + +The Rubrik cluster tests the connection with the VMC vCenter Server and saves the information. + *[ > ]: and then diff --git a/saas_vmc_editing_proxy_vm_for_vmc_vcenter_server_4.md b/saas_vmc_editing_proxy_vm_for_vmc_vcenter_server_4.md new file mode 100644 index 0000000000000000000000000000000000000000..c31bc34f7a39806e23df547b009d33681317142f --- /dev/null +++ b/saas_vmc_editing_proxy_vm_for_vmc_vcenter_server_4.md @@ -0,0 +1,44 @@ +# Editing proxy virtual machine details + +Source: https://docs.rubrik.com/en-us/saas/saas/vmc_editing_proxy_vm_for_vmc_vcenter_server_4.html + +--- + +# Editing proxy virtual machine details + +Update the network settings for the proxy virtual machine configured for a vCenter Server hosted in VMware Cloud. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the vSphere VMs inventory card. + +The vSphere VMs page appears. + + 5. Click Manage vSphere. + +The vSphere Servers page appears. + + 6. Locate the vCenter Server. + +Alternatively, you can use the Search by name field to search for a vCenter Server. + + 7. Open the and select Edit Proxy VM Network. + +The Edit Proxy Virtual Machine Network dialog box appears. + + 8. Edit the network settings as required. + 9. Click Done. + +## Results + +RSC saves the updated network settings for the proxy virtual machine. + *[ > ]: and then diff --git a/saas_vs_app_consistency_indiv_batch.md b/saas_vs_app_consistency_indiv_batch.md new file mode 100644 index 0000000000000000000000000000000000000000..955b2ecff4c1344ec23a273ecf841976c3ec0952 --- /dev/null +++ b/saas_vs_app_consistency_indiv_batch.md @@ -0,0 +1,12 @@ +# Application consistency + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_app_consistency_indiv_batch.html + +--- + +# Application consistency + +You can set application consistency for vSphere virtual machines individually or in batch at different levels in the vSphere hierarchy. + +The inheritance mechanism of RSC enables application consistency for any object and all its child objects. You can configure batch application consistency in vSphere virtual machines only with Rubrik clusters running CDM 9.3.1 or later. + *[ > ]: and then diff --git a/saas_vs_application_consistency.md b/saas_vs_application_consistency.md new file mode 100644 index 0000000000000000000000000000000000000000..0b472284b5a05e9cc467373be26da2930e350164 --- /dev/null +++ b/saas_vs_application_consistency.md @@ -0,0 +1,14 @@ +# Application consistency + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_application_consistency.html + +--- + +# Application consistency + +The Rubrik cluster supports application-consistent snapshots for many guest OS types and application types. + +The Rubrik cluster supports application-consistent snapshots for applications such as Microsoft Exchange Server, Microsoft SQL Server, Microsoft Active Directory, Microsoft SharePoint, and Oracle Database (RDBMS) running on the Windows Server guest OS. To enable application-consistent snapshots for these applications, RBS must be installed on the guest OS. + +The Rubrik cluster does not support the restore of an application-consistent snapshot into an availability group. Cluster consistency for the availability group cannot be ensured in this situation and problems may occur. + *[ > ]: and then diff --git a/saas_vs_ods.md b/saas_vs_ods.md new file mode 100644 index 0000000000000000000000000000000000000000..5a4bce73ba7a4d155428815ad02a9de03a69fc61 --- /dev/null +++ b/saas_vs_ods.md @@ -0,0 +1,14 @@ +# On-demand snapshots of vSphere virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_ods.html + +--- + +# On-demand snapshots of vSphere virtual machines + +In addition to policy-based snapshots, create virtual machine snapshots by using the on-demand snapshot process. + +A Rubrik cluster creates policy-based snapshots of protected vSphere virtual machines automatically according to the SLA rules of the associated SLA Domain. Additional snapshots of protected and unprotected virtual machines can be created by using the on-demand snapshot process. + +You can take an on-demand snapshot of a virtual machine, a vSphere VM template that is managed in a vSphere server, or a vSphere VM template that is managed in a content library. + *[ > ]: and then diff --git a/saas_vs_recovery_vm.md b/saas_vs_recovery_vm.md new file mode 100644 index 0000000000000000000000000000000000000000..b6ae05eae35222a4059d85fb5033ea7267cf7fc9 --- /dev/null +++ b/saas_vs_recovery_vm.md @@ -0,0 +1,33 @@ +# Recovery of vSphere virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_recovery_vm.html + +--- + +# Recovery of vSphere virtual machines + +To recover a vSphere virtual machine, a Rubrik cluster mounts a point-in-time copy of that virtual machine. + +You can recover vSphere virtual machines from snapshots that are locally available on the Rubrik cluster. Local snapshots include snapshots downloaded from archival locations or replication targets to a Rubrik cluster. + +You can recover from snapshots that are available only at the remote archival locations or replication targets, or from local snapshots that have expired. + +The following table describes the recovery action specifications. Action | Name or type of recovered virtual machine | Datastore | Power state | Network | Source virtual machine state +---|---|---|---|---|--- +Recover files | Not applicable | Not applicable | Not applicable | Not applicable | No impact +Live mount | Composite | Local Rubrik cluster | On or Off | Disconnected | No impact +Mount virtual disks | Composite | Local Rubrik cluster | On | Disconnected | No impact +Instant recovery | Name of the source virtual machine | Local Rubrik cluster | On | Connected (Optional) | Powered off and renamed +Export | Composite by default, but can be set manually. | Datastore of hypervisor | Off | Disconnected | No impact +In-place recovery | Same as the name of the source virtual machine | Datastore of hypervisor | On | Same as the source virtual machine | In-place recovery overwrites the virtual disk files of the source virtual machine with the virtual disk data from the snapshot, without changing the properties of the virtual machine. + +You can use the Recover files option to recover a VMware vSphere virtual machine to any one of the following targets: + + * VMware virtual machines + * Linux hosts + * Nutanix virtual machines + * Hyper-V virtual machines + * Windows hosts + +RSC names the recovered virtual machine in the following format: _. For example, the first mount of the snapshot associated with VirtualMachine1 that was created at 08-04 06:48 but recovered on 07-17 10:20 is named VirtualMachine1_07-1710:20. + *[ > ]: and then diff --git a/saas_vs_resource_visibility.md b/saas_vs_resource_visibility.md new file mode 100644 index 0000000000000000000000000000000000000000..83d6240c2a910249fa843c1a869630785d95346c --- /dev/null +++ b/saas_vs_resource_visibility.md @@ -0,0 +1,16 @@ +# vSphere resource visibility + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_resource_visibility.html + +--- + +# vSphere resource visibility + +In RSC, you can allocate vSphere resources to multiple Rubrik clusters for protection, customizing your RSC deployment for data management that fits your requirements. + +When a vCenter Server is connected to multiple Rubrik clusters, by default all the compute clusters of the vCenter Server are available for protection by all the Rubrik clusters. To protect specific compute clusters on each Rubrik cluster, you can set the visibility of the compute clusters for all the connected Rubrik clusters. By setting the resource visibility you allocate specific vSphere compute clusters to each Rubrik cluster. Setting the visibility of vCenter Server resources is an optional step. + +You can set the resource visibility either by assigning multiple compute clusters to the same Rubrik cluster or by assigning a single compute cluster to each Rubrik cluster. + +After you configure resource visibility for a vCenter Server, RSC will not protect compute cluster resources unless they are assigned to a Rubrik cluster. + *[ > ]: and then diff --git a/saas_vs_storage_array_integration.md b/saas_vs_storage_array_integration.md new file mode 100644 index 0000000000000000000000000000000000000000..d5d497fcbc19c833ffe19913c2a6a5f682b65dd6 --- /dev/null +++ b/saas_vs_storage_array_integration.md @@ -0,0 +1,18 @@ +# Storage array integration + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_storage_array_integration.html + +--- + +# Storage array integration + +Rubrik Security Cloud provides a user interface for integrating Rubrik clusters with storage arrays, reducing the time a virtual machine is quiescent during snapshot operations. + +As part of the snapshot process, a Rubrik cluster reads and processes the data in the VMDK files of a virtual machine. During this time, the virtual machine runs while the VMDK files used for acquiring the backup data are in quiescence. The Rubrik cluster reads and processes the VMDK file very quickly, resulting in extremely short periods of quiescence. + +However, in cases where there are large VMDK files or VMDK files with a high data change rate, the time required for acquiring the data in the VMDK files can impact the virtual machine performance for a noticeable or disruptive period. In these cases, using integrated snapshot creation at the storage array level results in much less performance impact on the applications and system of the virtual machine. + +With storage array integration, the Rubrik cluster uses the storage array API to take snapshots of both the virtual machine and the corresponding storage volumes on the array containing the virtual machine VMDK files. The storage volume snapshots appear in vSphere as a proxy storage array virtual machine, from which the data is then read and processed into the Rubrik cluster. The Rubrik cluster then deletes the snapshot on the original virtual machine, returning the virtual machine to normal operation. + +You can customize storage array integration for a specific environment through the use of custom scripts on the guest operating system. Custom scripts can provide application level quiescence or application consistency. For example, a pre-backup script can prepare an application for the brief quiescence for the storage array integration. A post-snapshot script can resume the application immediately after the Rubrik cluster completes snapshot operations. + *[ > ]: and then diff --git a/saas_vs_virtual_machine_protection.md b/saas_vs_virtual_machine_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..9e55cb8d821e7e4b6bc7724593f13f8922dcf57d --- /dev/null +++ b/saas_vs_virtual_machine_protection.md @@ -0,0 +1,12 @@ +# vSphere virtual machine protection + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_virtual_machine_protection.html + +--- + +# vSphere virtual machine protection + +RSC provides protection for virtual machines through individual assignment of the virtual machine to an SLA Domain or through automatic protection. + +RSC provides flexibility in the protection assignments made for virtual machines. Virtual machines that are protected by individual assignment can be set to Don't protect or to derive a protection setting automatically from a higher-level object. + *[ > ]: and then diff --git a/saas_vs_virtual_machine_scripts.md b/saas_vs_virtual_machine_scripts.md new file mode 100644 index 0000000000000000000000000000000000000000..e5ed9cc4fcd2eea6c4c7777741c474d25d402b76 --- /dev/null +++ b/saas_vs_virtual_machine_scripts.md @@ -0,0 +1,45 @@ +# vSphere virtual machine scripts + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_virtual_machine_scripts.html + +--- + +# vSphere virtual machine scripts + +RSC allows you to configure the Rubrik cluster to run scripts on a guest OS before a snapshot, after a snapshot, and after the Rubrik cluster completes the backup process. + +Virtual machine scripts allow you to: + + * Set a guest OS in a specific state before a snapshot + * Change that state immediately after the snapshot is completed on the host system + * Perform other actions after the Rubrik cluster completes the backup process + +To allow the Rubrik cluster to start scripts, RSC requires Guest OS credentials with sufficient privileges. Without adequate credentials, the Rubrik cluster cannot start the scripts. + +The scripts can consist of any sequence of operations that can be run by the command line interpreter of the guest OS. + +Name | Description +---|--- +Pre-Backup Script | + + * You can use a pre-backup script to prepare for a backup by quiescing the applications on the virtual machine. + * Pre-backup scripts require that a timeout value be specified. + + +Post-Snap Script | + + * You can use a post-snap script to minimize stun time and resume all applications on the virtual machine. + * You can use post-snap scripts to perform clean-up tasks if a backup task fails. + * Post-snap scripts must be idempotent, script may be invoked several times during a single backup task. + * Post-snap scripts require that a timeout value be specified. + * Post-snap scripts run immediately after the host snapshot task completes. + + +Post-Backup Script | + + * You can use post-backup scripts to perform custom post-processing at the end of the backup process. + * Post-backup scripts must be idempotent, script may be invoked several times during a single backup task. + * Post-backup scripts require that a timeout value be specified. + * Post-backup scripts run after the snapshot is copied to the Rubrik cluster and released on the virtual machine host, and the Rubrik cluster completes all data and metadata processing tasks. + + *[ > ]: and then diff --git a/saas_vs_virtual_machines.md b/saas_vs_virtual_machines.md new file mode 100644 index 0000000000000000000000000000000000000000..c0fdbba926e7fd7bc4c8cf64f3bcc53e0ce83341 --- /dev/null +++ b/saas_vs_virtual_machines.md @@ -0,0 +1,21 @@ +# vSphere virtual machines + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_virtual_machines.html + +--- + +# vSphere virtual machines + +Rubrik Security Cloud provides data management and SLA Domain protection for vSphere virtual machines, including vSphere VM templates that are managed either through a VMware vSphere environment or a content library. + +Rubrik Security Cloud (RSC) can manage the protection and recovery of vSphere virtual machines and vSphere VM templates managed by multiple Rubrik clusters. RSC provides protection for VM templates that are managed either through a VMware vSphere environment or through a content library. RSC supports content library protection only for vSphere templates of the VM template type. + +The VMware vSphere documentation provides more information about VM template operations in VMware vSphere environments and content libraries. + +## Encrypted and vTPM-enabled virtual machines + +RSC also provides protection and recovery for encrypted virtual machines and virtual Trusted Platform Module (vTPM)-enabled virtual machines. To back up and recover these virtual machines, you must have the minimum cryptographic operations privileges. If you are using BitLocker for encrypting your virtual machines, you are required to enter the encryption key during recovery. + +## Rubrik cluster and vCenter Server connectivity + +The Rubrik cluster accesses virtual machine data through a connection with the VMware vCenter Server. When one vCenter Server is connected to multiple Rubrik clusters, the virtual machines in the vCenter Server are visible to all connected Rubrik clusters. You can additionally set the visibility of a virtual machine to a specific Rubrik cluster. When you set a virtual machine to be visible to a Rubrik cluster, the selected Rubrik cluster can protect that virtual machine. diff --git a/saas_vs_vm_details_page.md b/saas_vs_vm_details_page.md new file mode 100644 index 0000000000000000000000000000000000000000..72ec061fb068d316236077e33344b47797fd1bd2 --- /dev/null +++ b/saas_vs_vm_details_page.md @@ -0,0 +1,19 @@ +# vSphere virtual machine details page + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_vm_details_page.html + +--- + +# vSphere virtual machine details page + +The vSphere virtual machine details page provides detailed information about the virtual machine, protection of the virtual machine, available snapshots, and tasks related to the virtual machine and snapshots. + +When a virtual machine in a vCenter Server is visible to multiple Rubrik clusters, the Virtual Machines tab on the vSphere VMs inventory page in RSC lists the virtual machine once. The Rubrik Cluster column lists all the Rubrik clusters from where this virtual machine is visible. + +You can navigate to the details page of a specific virtual machine from the vSphere VMs inventory page. The vSphere virtual machine details page provides the following tabs: + + * Overview + * Events + * Snapshots + + *[ > ]: and then diff --git a/saas_vs_vm_templates.md b/saas_vs_vm_templates.md new file mode 100644 index 0000000000000000000000000000000000000000..d24826018ceee638ead51bb7eedf6187842e29d5 --- /dev/null +++ b/saas_vs_vm_templates.md @@ -0,0 +1,21 @@ +# vSphere VM templates + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_vm_templates.html + +--- + +# vSphere VM templates + +Rubrik Security Cloud support selected backup and recovery operations for vSphere VM templates and content library items. These operations include file recovery, export, live mount, mounting virtual disks, and recovering virtual machine images as a template. + +Rubrik Security Cloud (RSC) supports the protection of vSphere VM templates that are managed through vCenter folders and content libraries. RSC supports content library protection only for vSphere templates of the VM template type. + +RSC supports direct and inherited SLA Domain assignments and on-demand and scheduled snapshots for VM templates. You can recover a VM template by performing one of the following actions: + + * Exporting a snapshot as a vSphere virtual machine (VM) or VM template + * Recovering a snapshot as a Live Mount + * Mounting a snapshot as a virtual disk + * Downloading files and folders from an indexed snapshot or replica + +InRSC, a VM template appears as a virtual machine that is powered off. When RSC performs a recovery operation, the snapshot can be exported as either a new virtual machine or a VM template. When RSC exports a snapshot as a VM template, it creates a virtual machine on the selected compute, folder, and storage resource and transfers the VM template or content library item file to the datastore. RSC then converts the virtual machine to a VM template. This behavior might temporarily result in transient virtual machine and VM template states in the vSphere inventory. You can view the status of virtual machine and VM template export activity on the Events page. + *[ > ]: and then diff --git a/saas_vs_vmdk_files.md b/saas_vs_vmdk_files.md new file mode 100644 index 0000000000000000000000000000000000000000..76666f78ad6447503a5428a73a6fd7c3384eeefb --- /dev/null +++ b/saas_vs_vmdk_files.md @@ -0,0 +1,12 @@ +# VMDK files + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_vmdk_files.html + +--- + +# VMDK files + +Virtual machines can include VMDK files that do not need to be protected. + +The Rubrik cluster can be configured to ignore specified VMDK files of a virtual machine while protecting the other VMDK files on the virtual machine. + *[ > ]: and then diff --git a/saas_vs_vsphere_diagnostics.md b/saas_vs_vsphere_diagnostics.md new file mode 100644 index 0000000000000000000000000000000000000000..3d6b37e61ed05d9f2362b80376a50f0a734f98cc --- /dev/null +++ b/saas_vs_vsphere_diagnostics.md @@ -0,0 +1,32 @@ +# vSphere diagnostics + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_vsphere_diagnostics.html + +--- + +# vSphere diagnostics + +Rubrik Security Cloud vSphere diagnostics confirm connectivity and access permissions for a vCenter server connected to a Rubrik cluster. You can use vSphere diagnostics to verify and troubleshoot connectivity, backup, and recovery of a vSphere object or component. + +vSphere diagnostics display the status of the vCenter server connection and the status of required vSphere permissions applied to vSphere objects. The following table lists the information captured in vSphere diagnostics. A green check mark in the output indicates that the network connection or vCenter permission is operating as expected. The vCenter Server documentation provides more information on these permissions. + +Diagnostics category | vSphere object or component +---|--- +Connectivity | General connectivity +Permissions | + + * vCenter + * Compute Clusters + * Resource Pools + * ESXI Hosts + * Virtual Machines + * Virtual Machine Folders + * Datastores + * Network + * Session + * Profile Driven Storage + + + +When launching vSphere diagnostics, you have the option either to view the previous diagnostics or to run new ones. Additionally, you can view vSphere diagnostics results through a link on the RSC Events page. + *[ > ]: and then diff --git a/saas_vs_vsphere_management.md b/saas_vs_vsphere_management.md new file mode 100644 index 0000000000000000000000000000000000000000..ebe459025291581544e1931e2d0da6aed86b9820 --- /dev/null +++ b/saas_vs_vsphere_management.md @@ -0,0 +1,16 @@ +# vSphere management + +Source: https://docs.rubrik.com/en-us/saas/saas/vs_vsphere_management.html + +--- + +# vSphere management + +The Rubrik cluster accesses virtual machine data through a connection with the VMware vCenter Server or ESXi host that manages the hypervisor running the virtual machine. + +To successfully connect with vSphere, the Rubrik cluster requires connection information for the vCenter Server or ESXi host. Once received, the Rubrik cluster requests relevant metadata from vSphere. RSC displays vSphere information on the vSphere Management page. This page provides the FQDN or IP address and the connection status for each vCenter Server or ESXi host that has been added to Rubrik clusters connected to RSC. + +The vSphere role assigned to a Rubrik cluster must have specific privileges on the vCenter Server or ESXi host. + +The Rubrik CDM User Guide provides more information about the vCenter Server and ESXi host privileges. + *[ > ]: and then diff --git a/saas_web_browser_support_rsc.md b/saas_web_browser_support_rsc.md new file mode 100644 index 0000000000000000000000000000000000000000..cdf987975b7d73950b103e4a3a2cbc570bf6f1e8 --- /dev/null +++ b/saas_web_browser_support_rsc.md @@ -0,0 +1,13 @@ +# Web browser support + +Source: https://docs.rubrik.com/en-us/saas/saas/web_browser_support_rsc.html + +--- + +# Web browser support + +When using the RSCweb UI, the latest version of Google Chrome or Microsoft Edge provides the best viewing experience. + +The RSC web UI supports the three most recent versions of Chrome and Edge. However, the latest versions of Chrome and Edge provide the most secure experience and are the preferred versions for the web UI. + +Using an older version of Chrome or Edge can result in a loss of functionality and potentially affect the appearance and layout of the RSC web UI. diff --git a/saas_windows_volume_groups.md b/saas_windows_volume_groups.md new file mode 100644 index 0000000000000000000000000000000000000000..8b0298825354191c2b3b4127abec36297641e414 --- /dev/null +++ b/saas_windows_volume_groups.md @@ -0,0 +1,38 @@ +# Windows volume groups + +Source: https://docs.rubrik.com/en-us/saas/saas/windows_volume_groups.html + +--- + +# Windows volume groups + +A volume group is a Rubrik workload comprised of at least one data storage volume on a Windows host. + +Protection for an entire volume or set of volumes preserves the following information in addition to the individual files stored on the volumes: + + * File system type + * Volume size + +Note: + +Indexing is only supported for NTFS volumes. + +A protected volume group workload does not preserve the following attributes: + + * The Master Boot Record (MBR) + * The GUID Partition Table (GPT) + * The IP address of the original host + +Volume group workloads do not support: + + * Dual- or multi-boot systems + * Multiple operating systems on a single computer + * Multiple instances or multiple versions of an operating system on a single computer + * Dynamic simple volumes, which are volumes on a dynamic disk comprising multiple discontiguous disk extents. + * Volumes over 64 TB in size. + +Protecting a volume group on a Windows host requires the installation of the Volume Filter Driver (VFD). + +Note: + +The Rubrik CDM Compatibility Matrix has detailed information on the operating systems that the Volume Protection feature supports. diff --git a/saas_workload_specific_settings_sla_domains.md b/saas_workload_specific_settings_sla_domains.md new file mode 100644 index 0000000000000000000000000000000000000000..aff388bc3d4e9b7f12fa0ee469eab049f20fec24 --- /dev/null +++ b/saas_workload_specific_settings_sla_domains.md @@ -0,0 +1,43 @@ +# Workload-specific settings for SLA Domains + +Source: https://docs.rubrik.com/en-us/saas/saas/workload_specific_settings_sla_domains.html + +--- + +# Workload-specific settings for SLA Domains + +Information about workload-specific settings configured when creating or editing SLA Domains for continuous data protection and backups for supported workloads. + +The following table provides information about workload-specific settings. Workload | Workload-specific settings +---|--- +vSphere VMs | Continuous Data Protection: Requires entry of the retention period for recovery points in hours when Continuous Data Protection is turned on. The Continuous Data Protection option works only with a single replication target. Depending on the CDM version you use in your cluster, you can enter up to a maximum of 24 hours. The SLA Domains with CDP enabled topic provides more information about the Keep Recovery Points For (Hours) settings and the supported CDM versions. +VCD vApp | Continuous Data Protection: Requires the entry of the retention period for recovery points in hours when Continuous Data Protection is turned on. The Continuous Data Protection option works only with a single replication target. Depending on the CDM version you use in your cluster, you can enter up to a maximum of 24 hours. The SLA Domains with CDP enabled topic provides more information about the Keep Recovery Points For (Hours) settings and the supported CDM versions. +SQL Server Databases | Log Backup: Backs up database transaction logs by reading directly from the database. Providing the log backup retention period is mandatory. +Oracle Databases | Log Backup: Backs up database transaction logs by reading directly from the database. This specifies the frequency and retention period. By default, the frequency is set to 15 minutes and the retention period is set to 1 day. You can edit both values with the frequency not being less than 15 minutes and the retention period can be extended as needed. Additionally, turning on Enable archived redo log retention on Oracle Host ensures: + + * Setting the retention period for archived redo logs on the host in hours. + * Selecting to skip the deletion of archived redo logs on the host, ensuring they remain until explicitly deleted. + + +SAP HANA | + + * Log Backup: Backs up database transaction logs by reading directly from the database. Providing the log backup retention period is mandatory. + * Incremental Backup (Optional): Backs up only the differences between the current data and the last full or incremental backup. You can specify the frequency and its retention follows the retention period of log backups. + * Differential Backup (Optional): Backs up only the data that has changed from the time of the last backup. You can specify the frequency and its retention follows the base retention period for log backups. + + +Db2 | + + * Log Backup: Backs up database transaction logs by reading directly from the database. Providing the log backup retention period is mandatory. + * Incremental Backup (Optional): Backs up only the differences between the current data and the last full or incremental backup. You can specify the frequency and its retention follows the retention period of log backups. + * Delta Backup (Optional): Backs up only the data that has changed from the time of the last backup. You can specify the frequency and its retention follows the base retention period for log backups. + + +MongoDB | OpLog Backup: Specifies the frequency and retention period. By default, the frequency is set to 30 minutes, and the retention period is set to 1 day. The frequency cannot be greater than the base frequency, and the retention period can be extended as needed. Entering the value for OpLog Backup enables point-in-time recovery and provides efficient incremental backups. The minimum frequency allowed is 15 minutes. This option cannot be disabled for MongoDB. +PostgreSQL cluster | Log Backup: Backs up database transaction logs by reading directly from the database. The retention period for these logs must be less than or equal to the base retention period. Providing the log retention period is mandatory. +Amazon RDS | Continuous backups for point-in-time recovery: Requires you to enter the backup period, in days, with retention up to a maximum of 35 days for continuous data protection of database instances. +AWS S3 | Backup Location: Requires selecting a backup location to ensure scheduled snapshots. +AWS DynamoDB | Primary Backup Encryption: Encrypts the snapshot data based on the specified KMS key. You can retrieve the KMS Key alias from your AWS account.This setting is optional.To ensure successful encryption of the backed-up table data, the specified KMS key alias must be present and correctly configured in the target AWS account and the target AWS region. While different accounts and regions have unique underlying KMS keys, these accounts and regions can share a common KMS key alias for this purpose.For more information, see [Protecting data with encryption](https://docs.aws.amazon.com/AmazonS3/latest/userguide/UsingEncryption.html), [Create a KMS key](https://docs.aws.amazon.com/kms/latest/developerguide/create-keys.html), and [Aliases in AWS KMS](https://docs.aws.amazon.com/kms/latest/developerguide/kms-alias.html). +Azure Blob Storage | Backup Location: Requires selecting a backup location to ensure scheduled snapshots. +Azure SQL | Log Backup: Backs up database transaction logs by reading directly from the database. Providing the log backup retention period is mandatory. + *[ > ]: and then diff --git a/saas_wvg_adding_a_windows_host.md b/saas_wvg_adding_a_windows_host.md new file mode 100644 index 0000000000000000000000000000000000000000..95568bd5661200e15b85a4bb39937e15337a2dc6 --- /dev/null +++ b/saas_wvg_adding_a_windows_host.md @@ -0,0 +1,41 @@ +# Adding a Windows host + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_adding_a_windows_host.html + +--- + +# Adding a Windows host + +Add a new Windows host to the Rubrik cluster to begin managing and protecting it. + +## About this task + +The Rubrik Backup Service software must be installed on each host that will be added. If not installed prior to adding a host, it can be downloaded and installed during the process of adding a host. + +## Procedure + + 1. Log in to RSC. + 2. Click and select Settings. + +The Settings menu appears. + + 3. Click Data Sources and select Windows. + +The Windows page appears. + + 4. Click Add Hosts. + +The Add Hosts wizard appears. + + 5. In Rubrik cluster, select the cluster to connect to. + 6. Select whether to install Rubrik Backup Service (RBS). + +If required, follow the steps to download RBS. + + 7. In Host IP addresses or FQDNs, enter the IP addresses or hostnames to add hosts. + 8. Click Add. + +## Results + +The Rubrik cluster checks connectivity with the specified hosts and adds the hosts. + *[ > ]: and then diff --git a/saas_wvg_bmr_restore.md b/saas_wvg_bmr_restore.md new file mode 100644 index 0000000000000000000000000000000000000000..8620b282516699dbcf87ec51c34abfddc4335aba --- /dev/null +++ b/saas_wvg_bmr_restore.md @@ -0,0 +1,145 @@ +# Restoring a volume group using BMR + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_bmr_restore.html + +--- + +# Restoring a volume group using BMR + +You can restore a Windows Volume group by using a bootable ISO file created through the Bare Metal Recovery process. You can create a recovery boot ISO file from any Windows OS, such as a laptop or a desktop server. + +## Before you begin + +Complete the following prerequisites: + + * Install RBS on the source host. + * Assign SLA Domains to protect the volumes. + * Document the server disk layout and the volumes protected by Rubrik to ensure that the disk layout matches the restore operation. + * Ensure the IP address assigned to the target server can communicate with the Rubrik cluster. + * Ensure that the target hardware is similar to the source hardware. Recovery to dissimilar hardware is not supported. + +## About this task + +The Windows Assessment and Deployment Kit (ADK) and Windows Preinstallation Environment (PE) add-on provide tools for customizing Windows images for large-scale deployment, and for testing the quality and performance of your system, its added components, and the applications running on it. The Microsoft documentation provides more information about the Windows ADK. + +## Procedure + + 1. Download the Windows ADK from Microsoft. + 2. Complete the steps in the wizard, including specifying the installation path to finish installation. + +In the wizard, you can also specify the features to install, including the Development Tools, Imaging and Configuration Designer (ICD), Configuration Designer, User State Migration Tool (USMT), Windows Performance Toolkit, and the Microsoft User Experience Virtualization (UE-V) Template. + + 3. Download the WinPE Add-On for the Windows ADK from Microsoft. + 4. Complete the steps in the installation wizard, including specifying the location in which to install the WinPE Add-On. + +You can use the WinPE image to restore volume groups from any supported operating system version. You can determine the SMB path of the mounted snapshot of the volume group to restore. + +In the wizard, you can also specify the features to install, such as the Windows PE. + + 5. Log in to the Rubrik Support portal. + 6. Click Docs & Downloads. + +The Documentation and Downloads page appears. + + 7. Click the Misc Documentation and Software (Compatibility Matrix, Kroll, and so on.) link for the WinPE Recovery Tool. + 8. Under Software, click Download next to WinPE Recovery Tool. + +The EULA acceptance window appears. + + 9. Read the service agreement and select the checkbox to confirm that you have read and understood the terms of the agreement. + 10. Click Accept and download. + +The page refreshes and the download immediately begins. + + 11. Extract the Rubrik WinPE Recovery Tool zip file. + +Extracting the zip file creates an official-scripts directory with BMR and WinPEImageCreation subdirectories. + + 12. Copy the BMR and WinPEImageCreation folders from the recovery tools ZIP file to the C:\ drive of the Windows Server computer. + 13. Change to the C:\WinPEImageCreation folder. + 14. Run powershell. + +A PowerShell environment initiates. + + 15. Run the following command to create the image: + + .\CreateWinPEImage.ps1 -version version -isopath C:\WinPEISO -utilitiespath C:\BMR + +The value of the version parameter is the version of the Windows ADK. The version of the ADK installed on a system is the name of the folder in C:\Program Files (x86)\Windows Kits\. + +The WinPE image is created in the C:\WinPEISO directory. + + 16. Copy the WinPE image from the C:\WinPEISO to boot media and store the recovery ISO image file in a secure place. + 17. Load the boot media on the target host by using the bootable USB key or by using the Intelligent Platform Management Interface (IPMI)/Lights out management interface of your server. + 18. Discover the target server IP address by running ipconfig in cmd.exe. + 19. **Optional:** Assign a static IP address on this host by running the following command: + + netsh int ip set address static X.X.X.X Z.Z.Z.Z Y.Y.Y.Y + +Where X is the desired IP address, Z is the subnet mask, and Y is the gateway IP. + + 20. **Optional:** Set the DNS by running the following command: + + netsh interface ip add dns"" X.X.X.X + +Where X is the IP address of the DNS server. + + 21. Confirm the connectivity and response time between your current system and each of the IP addresses corresponding to the nodes in a Rubrik cluster. + 22. In RSC, use Live Mount to recover the Windows Volume Snapshots for the source Windows host, and follow the steps in the wizard. + 23. In the Mount Snapshot wizard, select No Host, enter information in the SMB Configuration window, and then click Finish. + +Selecting No Host indicates a host that is not connected to the Rubrik cluster. Client IP information, domain name, and username are required fields in the SMB Configuration window. + +The notification on the page confirms the recovery. This information is also indicated in the Events page. + + 24. On the Windows volumes page, click Live Mounts and confirm that the Live Mount for the volumes was created properly. + 25. Copy the path in the Restore Script Path column in the Windows Volumes Live Mounts page. + 26. Boot the Windows system from the generated WinPE ISO image file. + 27. Run powershell. + +A PowerShell environment initiates. + + 28. Set the Windows PowerShell Execution Policy to Unrestricted on the target host as indicated in the following example. + + Set-ExecutionPolicy -ExecutionPolicy Unrestricted + + 29. Run one of the following options for the net use command: + * net use z:\\\\xxxxxx /user: + +Where \\\\xxxxxx is part of the Restore Script Path displayed on the Live Mount page and and are the username and password for the volume group. + + * net use z:\\\\xxxxxx + +Where \\\\xxxxxx is part of the Restore Script Path displayed on the Live Mount page. Enter the username and password as required. Username is the domain username entered when setting up the Live Mount on Rubrik CDM and the password is the password of the domain user. + +It is important to use the net use command to establish the credentials needed to connect to the UNC share, as you cannot run the script from a mapped drive letter. + + 30. Run the Rubrik recovery PowerShell script from the Live Mounted share from the Rubrik node and enter the SMB path of the mounted snapshot of the volume group to restore. + * When the target machine has a system-reserved partition, run the following command: \\\\xxxxxx\with_layout\RubrikBMR.ps1 + * When the target machine does not have a system-reserved partition, run the following command: \\\\xxxxxx\with_layout\RubrikBMR.ps1 -BcdbootAll $true + +The restore script runs. + +The system displays a security warning and the following prompt: + + Do you want to run \\\xxxxxx\with_layout\RubrikBMR.ps1? + D] Do not run [R] Run once [S] Suspend [?] Help (default is "D"): + + 31. Enter `R` and press `Enter`. + +The restore script connects to the SMB shares and copies data from the volume group snapshot to the specified volumes on the host, and then displays a reboot prompt. + + 32. Enter `Y` after the system displays the following prompt. + + Enter 'Y' to reboot + +Before rebooting, ensure that the WinPE recovery boot ISO image file is unplugged and not configured to boot up automatically. + +The host reboots. + +## Results + +The host boots with the restored operating system and volumes. You can ensure that all volumes are recovered properly on the target host. + +After recovery completes, when the system boots for the first time, Diskpart automatically runs to bring the newly recovered volumes on line. This behavior is expected and does not require intervention. + *[ > ]: and then diff --git a/saas_wvg_configuring_the_volume_filter_driver_on_a_windows_host.md b/saas_wvg_configuring_the_volume_filter_driver_on_a_windows_host.md new file mode 100644 index 0000000000000000000000000000000000000000..2e1af4779d842a4359ac4efea46ce0bcb02c64f8 --- /dev/null +++ b/saas_wvg_configuring_the_volume_filter_driver_on_a_windows_host.md @@ -0,0 +1,47 @@ +# Configuring the Volume Filter Driver on a Windows host + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_configuring_the_volume_filter_driver_on_a_windows_host.html + +--- + +# Configuring the Volume Filter Driver on a Windows host + +The Rubrik Volume Filter Driver improves the performance of incremental backups of protected volumes. + +## About this task + +The Rubrik Volume Filter Driver (VFD) is a utility that tracks changes in the individual blocks of a Windows Volume. Installing the VFD can improve the performance of incremental backups of protected volumes. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Windows Volumes inventory card. + +The Windows Volumes page opens. + + 5. Click a host name. + +The Windows Volume group details page opens. + + 6. Open the ellipsis menu and select an option: + * Install VFD + * Uninstall VFD + +If VFD has not been installed, the Uninstall VFD option will not be available. If VFD has been installed, the Install VFD option will not be available. + +A prompt appears, confirming the configuration of the selected option. + + 7. Reboot the Windows host. + +## Results + +The VFD runs in the background to monitor changes in the protected volume. + *[ > ]: and then diff --git a/saas_wvg_protecting_a_windows_volume_group.md b/saas_wvg_protecting_a_windows_volume_group.md new file mode 100644 index 0000000000000000000000000000000000000000..cb90f0d774c7fe78ab5d4aa5bf7f973e4395b80b --- /dev/null +++ b/saas_wvg_protecting_a_windows_volume_group.md @@ -0,0 +1,65 @@ +# Protecting a Windows Volume group + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_protecting_a_windows_volume_group.html + +--- + +# Protecting a Windows Volume group + +Protecting Windows volumes uses the Rubrik Backup Service on a Windows host to read data from the protected volumes, and in some cases to create a Virtual Hard Drive file. + +## Before you begin + + * Communication between the Rubrik Backup Service (RBS) and the Rubrik cluster may use the SMB protocol. Hence, Port 445 must be open to permit inbound SMB connections to the Rubrik cluster. + * Join Windows 2016 and 2019 hosts to a domain. + * Join Windows 2012 hosts to a domain, or use the local administrator account for RBS. + * Add the Windows host to the Rubrik cluster. + +Note: + +Volumes can only be restored to an identical or newer OS. For example, Windows Server 2016 volumes cannot be restored to a Windows Server 2012 host. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Windows Volumes inventory card. + +The Windows Volumes page opens. + + 5. Click a host name. + +The Windows Volume group details page opens. + + 6. Click Manage Protection. + +The Manage Protection wizard appears. + + 7. Select the volumes to protect and click Next. + +Volumes cannot exceed be larger than 64 TB. The selected volumes are collectively referred to as a volume group. To search for a specific volume, enter a string in the Search by Name field. + +The wizard displays a list of available SLA Domains and a drop-down to switch between SLA Domains managed by Rubrik-Cloud and the SLA Domains managed by the Rubrik cluster that this host is connected to. + + 8. **Optional:** To create an SLA Domain, click the + icon. + 9. Select an SLA Domain for the volume group from the list and click Next. + +The SLA Domain applies to each volume in the volume group. To search for a specific SLA Domain, enter a string in the Search SLA Domains field. + +The wizard displays the Confirmation page. + + 10. Click Confirm. + +The selected protection is confirmed in a message. + +## Results + +The selected volume group is protected as a Virtual Hard Drive (VHD) file. + *[ > ]: and then diff --git a/saas_wvg_taking_an_on_demand_snapshot_of_a_windows_volumes_group.md b/saas_wvg_taking_an_on_demand_snapshot_of_a_windows_volumes_group.md new file mode 100644 index 0000000000000000000000000000000000000000..135775f9bfaf883826ae73d65f206e64c57d1cc0 --- /dev/null +++ b/saas_wvg_taking_an_on_demand_snapshot_of_a_windows_volumes_group.md @@ -0,0 +1,54 @@ +# Taking an on-demand snapshot of a Windows Volumes group + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_taking_an_on_demand_snapshot_of_a_windows_volumes_group.html + +--- + +# Taking an on-demand snapshot of a Windows Volumes group + +In addition to policy-based snapshots, use the on-demand process to take snapshots of a Windows Volume group. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Windows Volumes inventory card. + +The Windows Volumes page opens. + + 5. Click a host name. + +The Windows Volume group details page opens. + + 6. Click Take On Demand Snapshot. + +The Take On Demand Snapshot wizard appears. + + 7. Select the volumes to protect and click Next. + +Volumes cannot be larger than 64 TB. The selected volumes are collectively referred to as a volume group. To search for a specific volume, enter a string in the Search by Name field. + +The wizard displays a list of available SLA Domains and a drop-down to switch between SLA Domains managed by Rubrik-Cloud and the SLA Domains managed by the cluster that this host is connected to. + + 8. **Optional:** To create an SLA Domain, click the + icon. + 9. Select an SLA Domain for the volume group from the list and click Next. + +The SLA Domain applies to each volume in the Windows Volumes group. To search for a specific SLA Domain, enter a string in the Search SLA Domains field. + +The wizard displays a confirmation dialog box page. + + 10. Click Confirm. + +The UI message confirms the scheduling of the on-demand snapshot. + +## Results + +The selected volume group is protected as a Virtual Hard Drive (VHD) file. The Rubrik cluster adds the specified on-demand backup to the task queue. An event in the Events tab tracks the status of the on-demand backup task. The Rubrik cluster manages the snapshot based on the rules and policies of the selected SLA Domain. + *[ > ]: and then diff --git a/saas_wvg_verifying_connectivity.md b/saas_wvg_verifying_connectivity.md new file mode 100644 index 0000000000000000000000000000000000000000..c6d6ff7774a9c144ee57416ccda77265f7475f3e --- /dev/null +++ b/saas_wvg_verifying_connectivity.md @@ -0,0 +1,36 @@ +# Verifying connectivity + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_verifying_connectivity.html + +--- + +# Verifying connectivity + +Confirm host connectivity details from the Windows Volume group details page. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Windows Volumes inventory card. + +The Windows Volumes page opens. + + 5. Click a host name. + +The Windows Volume group details page opens. + + 6. Open the ellipsis menu and select Check Connectivity. + +The Host Connectivity window appears. + +## Results + +The host connectivity details are available from the Windows Volume group details page. diff --git a/saas_wvg_viewing_windows_volumes_group_details.md b/saas_wvg_viewing_windows_volumes_group_details.md new file mode 100644 index 0000000000000000000000000000000000000000..0a86b19cffe692e0cebd70a6c11ec16bcb73cb7e --- /dev/null +++ b/saas_wvg_viewing_windows_volumes_group_details.md @@ -0,0 +1,33 @@ +# Viewing Windows Volumes group details + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_viewing_windows_volumes_group_details.html + +--- + +# Viewing Windows Volumes group details + +The Windows Volumes group details page provides information about the Windows Volumes group. + +## Procedure + + 1. Log in to RSC. + 2. Open the app tray and select Data Protection. + +The Data Protection dashboard appears. + + 3. On the navigation bar, click Inventory. + +The Inventory page appears. + + 4. Click the Windows Volumes inventory card. + +The Windows Volumes page opens. + + 5. Click a host name. + +The Windows Volume group details page opens. + +## Results + +The Windows Volumes group details page displays information about the volume group. + *[ > ]: and then diff --git a/saas_wvg_volume_group_recovery.md b/saas_wvg_volume_group_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..4874406d3870e92c43e8c7e49c17d0eea691a898 --- /dev/null +++ b/saas_wvg_volume_group_recovery.md @@ -0,0 +1,16 @@ +# Windows volume group recovery + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_volume_group_recovery.html + +--- + +# Windows volume group recovery + +Multiple recovery options are available for Windows Volumes groups protected by a Rubrik cluster. + +Restore operations for a protected volume group can use physical hardware or a virtual machine as a destination. + +When a Windows host has RBS installed, files and folders of a volume group can be recovered at the individual or volume level, or a Live Mount of a volume group also provides direct access to the volumes in the group. + +For hosts without an existing Windows or RBS installation, download the WinPE Recovery Tool from the Rubrik Support website to enable restore operations for volume groups. + *[ > ]: and then diff --git a/saas_wvg_windows_volumes_group_details.md b/saas_wvg_windows_volumes_group_details.md new file mode 100644 index 0000000000000000000000000000000000000000..b889f2733bca74ef9a4ae3d1c37a4f4dfb6a9f89 --- /dev/null +++ b/saas_wvg_windows_volumes_group_details.md @@ -0,0 +1,51 @@ +# Windows Volumes group details + +Source: https://docs.rubrik.com/en-us/saas/saas/wvg_windows_volumes_group_details.html + +--- + +# Windows Volumes group details + +The Windows Volumes group details page displays the details of the object in the Overview, Events, and Snapshots tab. + +Tab | Description +---|--- +Overview | Displays the following information under Protection: + + * SLA Domain assigned to the object, with included and excluded volumes + +Displays the following information under Object Details: + + * The cluster the object belongs to + * The name of the operating system + * RBS connectivity status + +Displays the following information under Live Mounts: + + * The drives + * The source host + * The target host + * The restore script path + +Displays the following information under Snapshots: + + * Total snapshots taken over time + * Number of on-demand snapshots taken + * Oldest snapshot for this object + * Latest snapshot taken + * Calendar view of the snapshots + +The day view of the snapshot calendar displays the snapshot type and the time it was taken. +Events | Displays the list of events for the Windows Volumes group that can be filtered by the time range, severity, status, and event type. +Snapshots | Displays the following information: + + * List of snapshots with the date and time + * Snapshot type, such as, policy-based snapshots or on-demand snapshots + * Name of the assigned SLA Domain + +Provides options to: + + * Delete on-demand snapshots with Forever SLA Domain, policy-based snapshots with SLA Domain removed at the object level, and replicated snapshots with the replication SLA Domain removed + * Change the retention policy for on-demand snapshots + + *[ > ]: and then diff --git a/salesforce_monitoring_salesforce_organizations.md b/salesforce_monitoring_salesforce_organizations.md new file mode 100644 index 0000000000000000000000000000000000000000..1b51cb17e7b74817be3a34a7dd217140016c700b --- /dev/null +++ b/salesforce_monitoring_salesforce_organizations.md @@ -0,0 +1,23 @@ +# Monitoring Salesforce organizations + +Source: https://docs.rubrik.com/en-us/saas/salesforce/monitoring_salesforce_organizations.html + +--- + +# Monitoring Salesforce organizations + +View details about a Salesforce instance to monitor the data changes, backup jobs, status, backup summary, and license usage. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Select a Salesforce organization. + +## Results + +The Monitor page of the Salesforce organization appears where you can view details about the data changes, backup jobs, status, backup summary, and license usage of that Salesforce organization. + *[ > ]: and then diff --git a/salesforce_salesforce_adding_instance.md b/salesforce_salesforce_adding_instance.md new file mode 100644 index 0000000000000000000000000000000000000000..678a05dfe790a5cf78ba8fa68400bacfadd54714 --- /dev/null +++ b/salesforce_salesforce_adding_instance.md @@ -0,0 +1,72 @@ +# Adding a Salesforce organization + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_adding_instance.html + +--- + +# Adding a Salesforce organization + +Add a Salesforce organization to back up the data in your organization. + +## Before you begin + +Make sure that the user account you use to log in to the Salesforce organization has the appropriate permissions, as described in + +[Table of Salesforce protection limitations](Table of Salesforce protection limitationssalesforce_protection_limitations.dita). + +## About this task + +You can add a Salesforce organization in RSC to back up your data in production or sandbox environments. You need to grant access to the Salesforce organization with global administrator credentials for RSC to protect your data. RSC takes snapshots of the data according to the SLA Domain specification. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps Dashboard appears. + + 3. Click Add Instance. + +The Add a SaaS App Instance wizard appears. + + 4. Click Next. + +The Add a Salesforce Organization page appears. + + 5. In Salesforce Org URL, enter the URL of the Salesforce organization to protect. + 6. In Environment Type, select the environment to protect. + 7. Click Log in to Authenticate to give permission for RSC to access the Salesforce organization. + +A browser window appears and takes you to the Salesforce login page. + + 8. Log in to the Salesforce account with the global administrator credentials of the Salesforce organization. + +After a successful login, your Salesforce account is authenticated with RSC, and the Add a Salesforce Organization dialog box appears. + + 9. Click Next. + +The Assign SLA Domain page appears. + + 10. In SLA Domain, select the SLA Domain to assign to your Salesforce organization. + +Option| Description +---|--- +Bronze lite | Performs backups every 24 hours and retains these backups for one year. +Silver lite | Performs backups every 12 hours and retains these backups for one year. +Custom SLA Domain | Uses the custom SLA Domain that you configured. + +RSC takes the first full snapshot after you add the Salesforce organization. + + 11. In Storage Region, select the region where you want to store the backup and subsequent snapshots, and then click Next. + 12. Set the daily usage limits for the REST APIs and bulk APIs that RSC can use, and then click Next. + +RSC shares the overall API limits with any other application using the same Salesforce organization. You can set a percentage of the overall API limit for RSC to use. + +Before starting a scheduled backup job, RSC checks the number of available API calls for the Salesforce organization. If there is no available API call, RSC does not start the backup job. + + 13. Verify the details and click Set Up. + +## Results + +RSC adds the Salesforce organization and it appears in the Saas Apps dashboard. + *[ > ]: and then diff --git a/salesforce_salesforce_apis.md b/salesforce_salesforce_apis.md new file mode 100644 index 0000000000000000000000000000000000000000..eb96d5b9ff341d758d3f17f6cb01ffb412ae5c32 --- /dev/null +++ b/salesforce_salesforce_apis.md @@ -0,0 +1,25 @@ +# Salesforce APIs + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_apis.html + +--- + +# Salesforce APIs + +Rubrik accesses a Salesforce organization using APIs. Before capturing a scheduled backup job, RSC checks how many API calls are available for the Salesforce organization. If the set daily limits for API usage are exceeded, the scheduled backup job does not start. + +RSC uses Salesforce REST and BULK 2.0 APIs to back up and restore data. RSC uses BULK 2.0 APIs during backup and uses REST APIs for all other operations, including to perform backups if BULK 2.0 APIs are not available. + +All API requests are made on behalf of the Salesforce user account used when setting up and authenticating into a Salesforce instance in RSC. + +In Salesforce, there is a daily limit for concurrent API requests, API timeout limits, and total API request allocations for both REST and BULK 2.0 APIs and for all the integrations calling these APIs. It is important to set limits to have enough API availability so that other applications are not adversely affected when using the Salesforce API. + + * A 40% limit is recommended for BULK 2.0 APIs. If the value is set too low, RSC uses REST APIs, and, backup performance might be slow. + * A 30% limit is recommended for REST APIs. + +Even after reaching the assigned API limits for both REST and BULK 2.0 API limits, RSC completes the backup of objects that were in the process of being backed up. After those limits are reached, however, RSC then skips backups for other objects or metadata until API allocations are again available. + +While RSC uses REST APIs when comparing a snapshot to a live environment or during cascading impact analysis and recovery of records, it tries to perform these operations regardless of API availability. + +Each file backup counts as one available REST API call, so if a Salesforce organization has a large number of files and attachments that cannot be backed up in a single day because of API limits, RSC continues backing up the remaining files and attachments into the following days as long as there is API availability. + *[ > ]: and then diff --git a/salesforce_salesforce_backup_recovery.md b/salesforce_salesforce_backup_recovery.md new file mode 100644 index 0000000000000000000000000000000000000000..100d2d78bc3de9884cf431b5364b75eb097fd5ca --- /dev/null +++ b/salesforce_salesforce_backup_recovery.md @@ -0,0 +1,34 @@ +# Salesforce backup and recovery + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_backup_recovery.html + +--- + +# Salesforce backup and recovery + +RSC securely backs up your Salesforce organization with snapshots and recovers your data from those snapshots. + +You can back up your Salesforce data automatically or on demand to recover data when data is compromised by malicious activity. For backups, RSC takes snapshots of the data in your Salesforce organization, and you can recover your data from these snapshots. + +You can: + + * Back up and recover Salesforce fields, records, objects, and metadata. + +Data backup and recovery also keeps relationships between objects intact. + + * Automatically back up data at either 12-hour or 24-hour intervals so that you have daily restore points. + * Compare snapshots to see the differences between snapshot data and metadata to determine which snapshot to recover. + * Take on-demand snapshots to back up data on demand. + +## Salesforce fields, records and objects backup and recovery + +You can recover Salesforce records or certain fields in such records from a snapshot to a Salesforce production or sandbox environment. You can also recover Salesforce objects, including all the files, fields, and records in the objects. + +Before recovery, you can compare the records in a snapshot with those in your live Salesforce environment. Record and object recovery involves keeping relationships between dependent or related objects intact. Because records or objects you want to recover might have dependent or related records, you can analyze your records or objects to find the ones with dependencies. + +During analysis, RSC provides a list of dependent and related records or objects, and you can select the parent and child records to recover. You can also recover records or objects that were deleted before the last snapshot was taken. + +## Salesforce metadata backup and recovery + +You can recover Salesforce organizational metadata, such as from custom objects, layouts, email templates, workflows, and validation rules to a production or sandbox environment. You can recover all metadata or specific metadata for objects, and you can recover specific metadata components for general metadata types, such as user permission configurations. + *[ > ]: and then diff --git a/salesforce_salesforce_dashboard_details_2.md b/salesforce_salesforce_dashboard_details_2.md new file mode 100644 index 0000000000000000000000000000000000000000..14bd7a6bd0f098bef773888537698079e55452d3 --- /dev/null +++ b/salesforce_salesforce_dashboard_details_2.md @@ -0,0 +1,24 @@ +# Salesforce dashboard details + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_dashboard_details_2.html + +--- + +# Salesforce dashboard details + +RSC monitors Salesforce data and displays important details such as API and license usage and the number of failed or successful backups. + +The details page for the Salesforce instance helps you monitor backup information, such as the number of changed snapshots. You can also view details and access features. For example, you can edit API usage and reauthenticate your Salesforce account. + +The following table describes information on the Monitor tab of the details page. + +Field | Description +---|--- +Change Summary | Displays the number of deleted, modified, and added records during the past seven or 30 days.You can view a timeline of changed records from either the past seven days or the past 30 days. You can select the icons to view deleted, modified, or added records. +Backup Jobs | Displays the failed or successful snapshots in the past seven or 30 days.You can view a timeline of when RSC successfully or unsuccessfully backed up snapshots for either the past seven days or past 30 days. You can click an icon to view the successful snapshots, failed snapshots, and failed metadata snapshots. +Connection status | Displays whether Salesforce protection is online and provides access to reauthenticating to Salesforce. +Take a Snapshot | Provides access to taking an on-demand snapshot. +Backup Summary | Displays protection information and provides access to managing protection on the Salesforce instance. +Monitor API usage | Displays information about API usage over the past 24 hours and provides access to editing API usage. +License usage | Displays the license usage count. + *[ > ]: and then diff --git a/salesforce_salesforce_data_analysis.md b/salesforce_salesforce_data_analysis.md new file mode 100644 index 0000000000000000000000000000000000000000..679ddf3f13c3f9d80aaedc01efdb8906e1a6141c --- /dev/null +++ b/salesforce_salesforce_data_analysis.md @@ -0,0 +1,16 @@ +# Salesforce data analysis + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_data_analysis.html + +--- + +# Salesforce data analysis + +RSC generates comprehensive insights about the changes in Salesforce data and metadata, facilitating detailed monitoring and secure restore operations. + +You can view detailed insights about the changes in your Salesforce data and metadata before restoring the data. You can monitor and analyze the additions, deletions, and modifications in the Salesforce environment to identify any potentially malicious activity and unusual spikes or patterns in the modified records, thereby reducing the risk of data breaches and ensuring compliance with data protection regulations. If you notice any issue, you can selectively restore the required records from a snapshot taken before the update to ensure minimal disruption. + +RSC displays a comprehensive graph that represents the changes in Salesforce data within a seven-day period. The graph contains three distinct lines representing added, deleted, and modified records. Clicking a specific date on the graph displays the records that were changed on that day. You can apply additional filters to narrow down the records you are interested in and use the column picker to display additional columns for the records. You can analyze the records and decide to restore the records from a snapshot. + +You can download the records to review and compare all the records in the table. When you download the records, RSC downloads a ZIP file containing two CSV files. One CSV file contains the record values on the selected date and the other CSV file contains the previous version of the record values. You can compare the CSV files to identify changes in the Salesforce data and metadata and take appropriate actions. + *[ > ]: and then diff --git a/salesforce_salesforce_management.md b/salesforce_salesforce_management.md new file mode 100644 index 0000000000000000000000000000000000000000..9d76a6983e20d5e71c93c4f2eb725d576aa6e8d2 --- /dev/null +++ b/salesforce_salesforce_management.md @@ -0,0 +1,23 @@ +# Salesforce Data Protection + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_management.html + +--- + +# Salesforce Data Protection + +Salesforce Data Protection is a Rubrik-hosted SaaS service that extends RSC by securely backing up your critical Salesforce data and metadata for standard and custom objects. + +RSC simplifies managing backups of Salesforce when the data is either compromised or lost. Salesforce Data Protection requires no infrastructure configuration or maintenance; all storage and compute resources are included as part of the service. + +You can perform the following operations: + + * Back up data on demand or at 12-hour or 24-hour intervals. + * Recover data types and metadata. + * Monitor data to quickly view an analysis of your environment. + * Analyze data to determine if and when data was lost, which helps streamline investigations and recoveries. + * Compare snapshots to determine which snapshot to restore. + +Salesforce Data Protection is licensed per user, where the product counts the number of active Salesforce user licenses and Salesforce Platform user licenses for each protected Salesforce organization. + +Use of Rubrik Salesforce Data Protection involves transmitting and processing data outside of the Salesforce system. Your backup data will be securely stored outside of the Salesforce system and protected by Rubrik Security Cloud, rather than subject to protection by Salesforce. diff --git a/salesforce_salesforce_managing_excluded_perms.md b/salesforce_salesforce_managing_excluded_perms.md new file mode 100644 index 0000000000000000000000000000000000000000..c32996bec1650d4d20d565263dce50bb093e596f --- /dev/null +++ b/salesforce_salesforce_managing_excluded_perms.md @@ -0,0 +1,39 @@ +# Managing excluded permissions + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_managing_excluded_perms.html + +--- + +# Managing excluded permissions + +Manage the permissions that you excluded for a Salesforce organization. + +## About this task + +RSC does not capture backup data of permissions that you excluded. You can download these permissions and then upload them to your Salesforce environment to capture this data. + +Selected permissions will be included in future permissions checks. Unselected permissions remain excluded from permissions checks. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click the Salesforce inventory card. + +The details page for the Salesforce instance appears. + + 4. Click and select Manage Excluded Permissions. + 5. On the Object & Field Permissions or App & System Permissions tabs, select some or all of the excluded permissions. + 6. Click Next. + +A confirmation window appears. + + 7. Check the selected permissions and then click Update and Download. + +## Results + +RSC downloads a ZIP file with the updated permissions. + *[ > ]: and then diff --git a/salesforce_salesforce_monitoring_api.md b/salesforce_salesforce_monitoring_api.md new file mode 100644 index 0000000000000000000000000000000000000000..d1577aca3032d600b2fdf9731b2d51233f6f10f8 --- /dev/null +++ b/salesforce_salesforce_monitoring_api.md @@ -0,0 +1,29 @@ +# Monitoring API usage for Salesforce + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_monitoring_api.html + +--- + +# Monitoring API usage for Salesforce + +View and monitor the Bulk 2.0 and REST API usage details over a period of time from the API Usage page. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click a Salesforce instance. + +The details page for the Salesforce instance appears. + + 4. In the API usage section, click Monitor API usage. + +The API Usage page appears. + +## Results + +RSC displays information showing API usage over time. + *[ > ]: and then diff --git a/salesforce_salesforce_permissions.md b/salesforce_salesforce_permissions.md new file mode 100644 index 0000000000000000000000000000000000000000..25931d511b1054fa44a33019cc638931cc5d9986 --- /dev/null +++ b/salesforce_salesforce_permissions.md @@ -0,0 +1,21 @@ +# Salesforce permissions for backup and recovery + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_permissions.html + +--- + +# Salesforce permissions for backup and recovery + +Backing up and restoring data requires that you assign certain Salesforce permissions to the user account that authenticates into Salesforce. + +Rubrik recommends using a separate, dedicated Salesforce user account, such as a service account, when setting up a Salesforce instance. To back up and restore Salesforce data, you must assign the necessary permissions to the user account used for authenticating with the Salesforce instance. + +Rubrik also recommends creating a permissions set and assigning it to the authenticated Salesforce user. To create a permission set, you can clone the System Administrator profile permissions and add the other required permissions listed in the Rubrik documentation. + +You can use a Salesforce user license or a Salesforce Integration license to assign the permission set to the authenticated Salesforce user account. The Salesforce Integration license requires the following profiles: + + * Salesforce API Only System Integration + * Minimum Access - API Only Integration + * Custom profile + + *[ > ]: and then diff --git a/salesforce_salesforce_protection_limitations.md b/salesforce_salesforce_protection_limitations.md new file mode 100644 index 0000000000000000000000000000000000000000..a3f0a0f669c3f14bf2a48196ae1fe56014d64213 --- /dev/null +++ b/salesforce_salesforce_protection_limitations.md @@ -0,0 +1,63 @@ +# Table of Salesforce protection limitations + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_protection_limitations.html + +--- + +# Table of Salesforce protection limitations + +Information about limitations for Salesforce protection. + +## Unsupported objects for backup + +You can back up all searchable objects except for the following. + +Object type | Object names +---|--- +Big objects | *__b +External objects | *__x +Metadata objects | *__mdt +Specific object types | AccountUserTerritory2View, ActivityMetric, ActivityMetricRollup, ActivityUsrConnectionStatus, AdminSetupEvent, AdminSetupEventStream, AnalyticsBotSession, AnlytDataAssetEventStore, ApexLimitEvent, ApexPageInfo, ApexTypeImplementor, ApiEvent, ApiEventStream, AppTabMember, AuraDefinitionInfo, BackgroundOperationResult, BotAnalytics, BotEventLog, BulkApiResultEventStore, CollaborationGroupRecord, ColorDefinition, ContentFolderItem, ContentFolderMember, ContentHubItem, DataStatistics, DataType, DatacloudAddress, DatacloudCompany, DatacloudContact, DatacloudDandBCompany, DatacloudSocialHandle, DcSocialProfile, DcSocialProfileHandle, EmbeddedServiceDetail, EngagementHistory, EnqueueOrderSummary, EntityParticle, FieldChangeSnapshot, FieldDefinition, FieldHistoryArchive, FileEventStore, FlexQueueItem, FlowDefinitionView, FlowVariableView, FlowVersionView, ForecastingUserPreference, FormulaFunction, FormulaFunctionAllowedType, FormulaFunctionCategory, GoalHistory, GoalOwnerSharingRule, IconDefinition, IdeaComment, IdentityProviderEventStore, IdentityVerificationEvent, InterfaceFieldMapping, LightningUriEvent, LightningUriEventStream, ListViewChartInstance, ListViewEvent, ListViewEventStream, LoginAsEvent, LoginAsEventStream, LoginEvent, LoginEventStream, LogoutEvent, LogoutEventStream, Macro, MacroHistory, MacroInstruction, MacroShare, MatchingInformation, Metric, MetricDataLinkHistory, MetricHistory, MetricOwnerSharingRule, NetworkUserHistoryRecent, OauthToken, OmniRoutingEventStore, OutgoingEmail, OutgoingEmailRelation, OwnerChangeOptionInfo, PermissionSetEventStore, PicklistValueInfo, PlatformAction, Publisher, RecentFieldChange, RecordActionHistory, RecordRecommendation, RecordVisibility, RelatedListDefinition, RelationshipDomain, RelationshipInfo, ReportEvent, ReportEventStream, SalesOrder__xe, SalesStore, SalesforceInvoice, SalesforceQuote, SearchLayout, SiteDetail, SubscriberPackage, SubscriberPackageVersion, TabDefinition, TenantUsageEntitlement, UnifiedActivity, UriEvent, UriEventStream, UserAppMenuItem, UserEntityAccess, UserFieldAccess, UserProfileFeed, UserRecordAccess, Vote, WorkAccessOwnerSharingRule, WorkCoachingHistory, WorkCoachingOwnerSharingRule, WorkGoalCollaboratorHistory, WorkGoalHistory, WorkGoalOwnerSharingRule, WorkRewardFundHistory, WorkRewardFundOwnerSharingRule, WorkRewardFundTypeHistory, WorkRewardFundTypeOwnerSharingRule, WorkRewardHistory, WorkRewardOwnerSharingRule + +## Object types excluded from backup by default + +The following table describes the object types that are excluded from backup because they cannot be restored. + +Object type | Object names +---|--- +History objects | *History +Share objects | *Share +Feed objects | *Feed +Tag objects | *Tag +Chatter | *Chatter +View stat objects | *ViewStat +Vote stat objects | *VoteStat +Change event objects | *ChangeEvent +Historical data objects | *__hd +Proxy objects | *__xo + +## Unsupported metadata types for backup + +RSC backs up metadata types by using SOAP APIs. Salesforce documentation includes information about which metadata types RSC cannot back up, because the metadata type cannot be fetched with SOAP APIs. + +## Recovery limitations + +RSC has the following recovery limitations: + + * RSC cannot recover objects that do not support create or update API calls. + * RSC cannot recover any object record field that you cannot create by using REST APIs. + * If there have been schema changes to an object, and you recover an organization using a snapshot that has a different schema than in your live environment, RSC does not restore the schema changes when recovering records. + +If a field has been removed, then when restoring a record with a snapshot taken before the field was removed, RSC restores the snapshot without that field. + +If a field has been added, then when restoring a record with a snapshot before the field was added, RSC restores the snapshot, but leaves the field empty. + +## Unsupported schema changes + +RSC does not support the following schema changes. + +Schema change | Description +---|--- +Rename field | RSC detects the rename field as a new column that is added with the new name, and the old column is deleted. RSC does not map the backup data with the old column name to the new column name. +Data type change | RSC does not support recovering a record that has a field with a data type that is incompatible with a data type in the Salesforce organization, meaning a data type that is incompatible with the data type in the Salesforce organization. + *[ > ]: and then diff --git a/salesforce_salesforce_rbac.md b/salesforce_salesforce_rbac.md new file mode 100644 index 0000000000000000000000000000000000000000..088921aff0010b15b6c7cf72e854bb2f0940b446 --- /dev/null +++ b/salesforce_salesforce_rbac.md @@ -0,0 +1,34 @@ +# Table of RBAC privileges for Salesforce Data Protection + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_rbac.html + +--- + +# Table of RBAC privileges for Salesforce Data Protection + +Accessing Salesforce protection features within RSC requires the appropriate RBAC permissions. You can use the default Salesforce Admin role or a custom role. + +With RBAC permissions, you can access Salesforce Data Protection features within RSC. The default Salesforce Admin role provides all the required permissions described in the following table. You can also create a custom role with the following required permissions. + +Permission type | Permissions +---|--- +View | + + * View protectable objects + * Refresh data sources + + +Protection | + + * Manage protection: Enables access to managing protection for a Salesforce organization by adding, modifying, or deleting a backup policy, and assigning objects to policies. + * On-demand snapshots: Enables access to taking a snapshot to back up data on demand. + + +Recover | + + * Restore over original: Enables access to restoring objects to their original location. + * Download files: Enables access to downloading files from the File Preparation Center. + +If you do not have Recover permissions, you cannot see the Restore tab on the Salesforce instance details page and cannot view backed-up data. +Data source management | Provides access to connect and authenticate to Salesforce organizations. + *[ > ]: and then diff --git a/salesforce_salesforce_regions.md b/salesforce_salesforce_regions.md new file mode 100644 index 0000000000000000000000000000000000000000..4ce472fb27e9425c8c32fb2435917046fda6fd50 --- /dev/null +++ b/salesforce_salesforce_regions.md @@ -0,0 +1,27 @@ +# Supported regions for Salesforce + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_regions.html + +--- + +# Supported regions for Salesforce + +RSC provides support for Salesforce protection in several regions. You select the region when you set up the Salesforce instance in RSC. + +RSC supports the following regions where Salesforce can be hosted: + + * Australia East + * Canada Central + * Central India + * East US 2 + * France Central + * Germany West Central + * Israel Central + * Japan East + * North Europe + * Norway East + * UK South + * West Europe + * West US 2 + + *[ > ]: and then diff --git a/salesforce_salesforce_removing_org.md b/salesforce_salesforce_removing_org.md new file mode 100644 index 0000000000000000000000000000000000000000..8c40e5f841cc3f620daede756f693ccd4db0ef55 --- /dev/null +++ b/salesforce_salesforce_removing_org.md @@ -0,0 +1,49 @@ +# Removing Salesforce organizations + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_removing_org.html + +--- + +# Removing Salesforce organizations + +Remove a Salesforce organization to remove all snapshots and configurations from RSC. + +## About this task + +During removal, RSC removes all the snapshots and configurations of this Salesforce organization. Adding this Salesforce organization back to RSC requires you to go through the process again. + +If you have a quorum policy configured for removing Salesforce organizations, you require approval from a set of approvers before you can remove a Salesforce organization. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click the Salesforce inventory card. + +The details page for the Salesforce instance appears. + + 4. Click and select Remove Salesforce Org. + +The Remove SaaS Instance dialog box appears. + + 5. Click Remove. + +If you have created a quorum authorization policy for this operation, you need to submit a request for quorum authorization. + + 6. For quorum authorization, select a run type action. + +Option| Description +---|--- +Automatically schedule | Schedules the action to automatically run after approval. +Manually schedule | Schedules the action to run within 24 hours after the approval. Actions not run 24 hours after approval will expire. + + 7. **Optional:** For quorum authorization, in Comment, enter a comment to provide additional details about the request. + 8. For quorum authorization, click Submit Request. + +## Results + +RSC initiates removal of the Salesforce organization. If you have created a quorum authorization policy, RSC completes the action according to the specified run type option after the request is approved. + *[ > ]: and then diff --git a/salesforce_salesforce_running_perms_check.md b/salesforce_salesforce_running_perms_check.md new file mode 100644 index 0000000000000000000000000000000000000000..5f5bd3f52c41a6c2722fb9984f43efe1fe103e7a --- /dev/null +++ b/salesforce_salesforce_running_perms_check.md @@ -0,0 +1,64 @@ +# Running permissions checks for Salesforce + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_running_perms_check.html + +--- + +# Running permissions checks for Salesforce + +Rubrik automatically runs a permissions check every four days to determine if the authenticated user has any missing permissions. You can also run an on-demand permissions check. By checking permissions, you can quickly identify if there are any gaps in your backup data and easily update any necessary permissions to ensure that all necessary data is captured. + +## Before you begin + +Before backing up and restoring Salesforce data, make sure to have the right Salesforce permissions. This ensures that all the necessary data is captured. + +## About this task + +If there are missing permissions, RSC sends a notification and displays a message on the Monitor tab. + +## Procedure + + 1. Log in to RSC. + 2. Click and select SaaS App Protection. + +The SaaS Apps dashboard appears. + + 3. Click the Salesforce inventory card. + +The details page for the Salesforce instance appears. + + 4. Click and select Run Permissions Check. + +This starts a background process to check your permissions for the current Salesforce organization. + +You can see the status of the permissions check and view details about the process on the Events tab. + + 5. View the notification in your inbox about the missing permissions report. + +A warning notification also appears on the SaaS App Protection page. + + 6. To view or manage the missing permissions, either click the inbox notification or click View Missing Permissions on the home page. + +The Manage Missing Permissions window opens. + + 7. To download missing permissions or select permissions to include or exclude from backup and recovery, make a selection: + +Option| Description +---|--- +Download all missing permissions | To retrieve all missing permissions, click Download. +Download specific missing permissions | Update permissions to include or exclude permissions from backup. This also downloads missing permissions in a ZIP file. + 1. Click Next. + 2. In the Select Permissions window, select which permissions to include in the backup. If you select field permissions, you must also select the corresponding object permissions. + 3. Click Next. + 4. Click Update and Download. +Note: Permissions that you do not select are excluded and are displayed when you download excluded permissions. This prevents you from receiving notifications for permissions that you did not want to update. You can go to this list and include these permissions at a later time. + + +## Results + +RSC downloads a ZIP file with the missing permissions. + +## What to do next + +Upload the ZIP file to your Salesforce organization to update the necessary permissions for Rubrik to protect the specified data and metadata. + *[ > ]: and then diff --git a/salesforce_salesforce_supported_data_types.md b/salesforce_salesforce_supported_data_types.md new file mode 100644 index 0000000000000000000000000000000000000000..74b1b65fc84ae25602d61a3e387db997212d6445 --- /dev/null +++ b/salesforce_salesforce_supported_data_types.md @@ -0,0 +1,46 @@ +# Salesforce Data Protection support table + +Source: https://docs.rubrik.com/en-us/saas/salesforce/salesforce_supported_data_types.html + +--- + +# Salesforce Data Protection support table + +Information about Salesforce Data Protection support. + +The following table describes RSC support for Salesforce organizations, editions, products, and APIs. + +Item type | Supported feature +---|--- +Organizations | + + * Production + * Sandbox + + +Editions | + + * Developer + * Enterprise + * Performance + * Unlimited + + +Products | + + * Field Service Cloud + * Financial Services Cloud + * Experience Cloud + * Education Cloud + * Sales Cloud + * Service Cloud + * All Salesforce Cloud products on Salesforce Platform that have queryable Salesforce data and metadata APIs + + +Salesforce APIs | RSC uses the following version 59 APIs: + + * REST + * SOAP + * Bulk API v2 + + *[ > ]: and then diff --git a/vcd_metadata_protection.md b/vcd_metadata_protection.md new file mode 100644 index 0000000000000000000000000000000000000000..99073c825ea089690d97eed0a5d795346ce74092 --- /dev/null +++ b/vcd_metadata_protection.md @@ -0,0 +1,16 @@ +# Metadata protection + +Source: https://docs.rubrik.com/en-us/saas/vcd/metadata_protection.html + +--- + +# Metadata protection + +Protection of vApps by Rubrik includes the metadata of the vApp. + +Metadata | Description +---|--- +Networks | Protects both isolated and routed networks. Also, RSC can reconnect restored virtual machines to the virtual datacenter network if the same network is available at restore time. +Boot order | Protects the order that the virtual machines in the vApp are configured to start and stop. +Access list | Protects the access list for the vApp. + *[ > ]: and then diff --git a/vcd_protection_and_management_features.md b/vcd_protection_and_management_features.md new file mode 100644 index 0000000000000000000000000000000000000000..d10606dd22030ec18b6129752e80adc1ddb738ca --- /dev/null +++ b/vcd_protection_and_management_features.md @@ -0,0 +1,38 @@ +# Protection and management features + +Source: https://docs.rubrik.com/en-us/saas/vcd/protection_and_management_features.html + +--- + +# Protection and management features + +In addition to full SLA-Domain-based protection of vApps, other features available for vSphere virtual machines are also provided for vApps. + +Feature | Description +---|--- +Automatic protection | vApps automatically derive the SLA Domain assignment made to VMware Cloud Director objects that are higher in the VMware Cloud Director hierarchy, such as organizations and organization virtual datacenters. +Synchronization | When you enable the synchronization setting, RSC requests that the associated ESXi host initiate snapshots of the vApp virtual machines at the same time.Actual snapshot start time depends on the availability of ESXi host resources and the number of virtual machines in the vApp. +Instant Recovery | Using Instant Recovery, a protected vApp can be fully recovered from a snapshot or the vApp can be partially recovered. A partial recovery recovers one or more of the virtual machines in the protected vApp. In a full or partial Instant Recovery, the recovered virtual machines use the default storage profile of the organization virtual datacenter. Optionally, you can connect the NIC of the recovered virtual machines to any existing network. +Export - Full or partial | Using Export, a vApp snapshot can be used to + + * Fully export a vApp to another location + * Export one or more of the virtual machines from the vApp to another location + * Export one or more of the virtual machines to an existing vApp + +The full export can include the network configuration of the source vApp: + + * Isolated vApp network + * Direct vApp network + * NAT routed network + +To establish a direct vApp network or a NAT routed network, the associated organization network must be available. After setting up the exported vApp network, Export connects the virtual machine network interface cards to the network. +Exclude virtual machines | Optionally, you can exclude individual virtual machines within a vApp from snapshots of the vApp. +Exclude VMDKs | Optionally, you can exclude individual VMDKs within a vApp from snapshots of the vApp. +Script support | You can set up pre-snapshot and post-snapshot scripts individually on each virtual machine in a protected vApp. +File-level download and restore | You can browse or search for files within a vApp snapshot and restore them to the original source location or download them from the Rubrik cluster. +Custom reports | Custom object reports and task reports can be filtered for a specific VMware Cloud Director organization. +On-demand snapshots | On-demand snapshots can be initiated for a vApp or for individual virtual machines within the vApp. +Migration | Virtual machines in a vApp that are protected individually can be migrated to protection through the vApp. Migrating to vApp protection does not require a new full snapshot of a virtual machine that was previously protected individually. +RBAC support | End users can select only organization virtual datacenters that have been assigned to them. +Multitenancy support | Multitenancy rules only permit tenant organization administrators to work with assigned VMware Cloud Director hierarchy components. For example, to assign an SLA Domain to a vApp or to use a organization virtual datacenter as a recovery target those components must first be assigned to the tenant organization administrator. + *[ > ]: and then diff --git a/vcd_recovery_restore_vapp_data.md b/vcd_recovery_restore_vapp_data.md new file mode 100644 index 0000000000000000000000000000000000000000..ebc397255aa8d59dda73cec64648fe9cb717b547 --- /dev/null +++ b/vcd_recovery_restore_vapp_data.md @@ -0,0 +1,21 @@ +# Recovery and restore of vApp data + +Source: https://docs.rubrik.com/en-us/saas/vcd/recovery_restore_vapp_data.html + +--- + +# Recovery and restore of vApp data + +You can use Instant Recovery, Export, or file-level recovery to recover data from a vApp snapshot. + +Recovery operation | Description +---|--- +Instant Recovery | Replaces all of the virtual machines in the source vApp. Optionally, you can install the virtual machine NICs unmapped or mapped, or delete all NICs. +Export | Fully or partially export the vApp as a new vApp or into an existing vApp. +File level recovery | You can recover folders and files from virtual machines in a vApp using one of these options: + + * Downloading files and folders through a web browser + * Overwriting the source files + * Restoring files and folders to a separate folder + + *[ > ]: and then diff --git a/vcd_vapp_export_options.md b/vcd_vapp_export_options.md new file mode 100644 index 0000000000000000000000000000000000000000..de2c61e98f9a9f8e51c025122bbe23f3476fddf1 --- /dev/null +++ b/vcd_vapp_export_options.md @@ -0,0 +1,19 @@ +# vApp export options + +Source: https://docs.rubrik.com/en-us/saas/vcd/vapp_export_options.html + +--- + +# vApp export options + +The Configure Recovery Options section of a vApp export operation includes a number of optional parameters. + +This table describes the optional Configure Recovery Options parameters for exporting a vApp. + +Options | Description +---|--- +New vApp name | You can enter a new name for the vApp. The default name is used if you do not enter a new name +Power on the selected VMs. | You can elect to power on the selected virtual machines. +Preserve MAC Addresses | You can select this to use MAC addresses from the snapshot instead of assigning new MAC addresses. +Customize Storage Profile | Selecting this creates a custom storage profile. + *[ > ]: and then diff --git a/vcd_vapp_management.md b/vcd_vapp_management.md new file mode 100644 index 0000000000000000000000000000000000000000..c63a28270c5a9a48bbe9ee6fc407fcdcb3892169 --- /dev/null +++ b/vcd_vapp_management.md @@ -0,0 +1,29 @@ +# vApp management + +Source: https://docs.rubrik.com/en-us/saas/vcd/vapp_management.html + +--- + +# vApp management + +After a VMware Cloud Director instance is added, the Rubrik cluster provides methods for finding, viewing, and protecting the vApps. + +When the Rubrik cluster finishes querying the VMware Cloud Director instance, the vApps and hierarchical information appear on the VMware Cloud Director vApps page. From the VMware Cloud Director vApps page, or the local page for a vApp, the Rubrik cluster can perform the tasks listed in the following table. + +Task | Description +---|--- +Find a vApp | Displays the listing for a specific vApp. You can the listing to access the local page for the vApp. +View the hierarchy | Displays each part of the VMware Cloud Director hierarchy that leads to any vApp. +Enable synchronization | Enables synchronization for a vApp to request that the Rubrik cluster initiate snapshots of all of the virtual machines in a vApp at the same time. +Exclude a virtual machine | Selects a vApp virtual machine and excludes it from all snapshots of the vApp. +Perform virtual machine tasks | Selects a vApp virtual machine to perform standard Rubrik tasks with it: + + * Configuring the application consistency setting + * Setting up a pre-script and a post-script + * Excluding VMDKs from snapshots of the virtual machine + * Registering the Rubrik Backup Service after it is installed on the virtual machine + + +Protect a vApp | Assigns the data protection policies of an SLA Domain to the vApp. The SLA Domain can be inherited from any of the levels of the hierarchy or directly assigned to the vApp. +Take an on-demand snapshot | Initiates an on-demand snapshot of the selected vApp and assigns the policies of any SLA Domain to that snapshot. + *[ > ]: and then diff --git a/vcd_vapps_limitations.md b/vcd_vapps_limitations.md new file mode 100644 index 0000000000000000000000000000000000000000..b89b73b85a7979876964d87a5817fc3b09a6ec77 --- /dev/null +++ b/vcd_vapps_limitations.md @@ -0,0 +1,17 @@ +# vApps limitations + +Source: https://docs.rubrik.com/en-us/saas/vcd/vapps_limitations.html + +--- + +# vApps limitations + +vApps support for Rubrik works within specific limitations. + +Limit type | Description +---|--- +Virtual machines in a vApp | You can have a maximum of 128 virtual machines in a vApp. To protect a vApp with more than 128 virtual machines, use the exclude function to reduce the number protected. +Mounts | The Rubrik cluster performs all mounts for vApps at the virtual machine level. +Backup exclusion | Protection of vApps does not include VMware Cloud Director Object metadata. +Autodiscovery | Rubrik ignores the VMware Cloud Director auto-discovery feature. + *[ > ]: and then diff --git a/vcd_vmw_cd_protection_hierarchy.md b/vcd_vmw_cd_protection_hierarchy.md new file mode 100644 index 0000000000000000000000000000000000000000..e631b1a758e903a5cbf260a4126263b2e02e2a02 --- /dev/null +++ b/vcd_vmw_cd_protection_hierarchy.md @@ -0,0 +1,24 @@ +# Protection hierarchy for VMware Cloud Director + +Source: https://docs.rubrik.com/en-us/saas/vcd/vmw_cd_protection_hierarchy.html + +--- + +# Protection hierarchy for VMware Cloud Director + +You can protect virtual machines through several levels of the VMware Cloud Director management hierarchy. + +SLA Domain protection can be applied to virtual machines within VMware Cloud Director vApps by assigning the SLA Domain at several different levels in the VMware Cloud Director management hierarchy. Protection can also be applied by assigning an SLA Domain to an individual virtual machine within a vApp. + +The protection hierarchy represents the hierarchical management levels in a VMware Cloud Director deployment at which SLA Domain protection can be specified. + +The following table describes the labeled areas of this graphic. + +Label | Protection level | Description +---|---|--- +1 | VMware Cloud Director instance | RSC applies the policies of the specified SLA Domain to all virtual machines within the organizations controlled by the VMware Cloud Director instance. +2 | Organization | RSC applies the policies of the specified SLA Domain to all virtual machines within the organization. Assigning an SLA Domain at this level overrides an SLA Domain assignment at the VMware Cloud Director instance level. +3 | Organization virtual datacenter | RSC applies the policies of the specified SLA Domain to all virtual machines within the organization virtual datacenter. Assigning an SLA Domain at this level overrides an SLA Domain assignment at the VMware Cloud Director instance level and the organization level. +4 | vApp | RSC applies the policies of the specified SLA Domain to all virtual machines within the vApp. Assigning an SLA Domain at this level overrides an SLA Domain assignment at the VMware Cloud Director instance level, the organization level, and the organization virtual datacenter level. +5 | Virtual machine | RSC applies the policies of the derived or individually assigned SLA Domain assignment to the specified virtual machine. Essentially, RSC ignores that the virtual machine is part of a vApp. To do this, delete the VMware Cloud Director instance from RSC. + *[ > ]: and then diff --git a/vcd_vmware_cloud_director_instances.md b/vcd_vmware_cloud_director_instances.md new file mode 100644 index 0000000000000000000000000000000000000000..56797ecdee1788fa506362ceb97d967718de00b5 --- /dev/null +++ b/vcd_vmware_cloud_director_instances.md @@ -0,0 +1,27 @@ +# VMware Cloud Director instances + +Source: https://docs.rubrik.com/en-us/saas/vcd/vmware_cloud_director_instances.html + +--- + +# VMware Cloud Director instances + +A Rubrik cluster works with vApps through VMware Cloud Director instances. + +You can start working with vApps by providing access to a VMware Cloud Director instance. You can add multiple VMware Cloud Director instances to a Rubrik cluster. + +After gaining access, the Rubrik cluster queries the VMware Cloud Director instance and populates the Rubrik UI with the instance hierarchy, including all vApps. The Rubrik UI provides a view for each of the following levels of the hierarchy: + + * VMware Cloud Director instance + * VMware Cloud Director organization + * Organization virtual datacenter + * vApps + +Instances of VMware Cloud Director support the actions described in the following table. + +Action | Description +---|--- +Refresh | Use refresh to request that the Rubrik cluster query the VMware Cloud Director instance for the most recent vApp information. +Edit | Use Edit to make changes to the account information for the selected VMware Cloud Director instance. +Delete | Use Delete to remove a VMware Cloud Director instance. The Rubrik cluster marks the vApps from that VMware Cloud Director instance as relics. The Rubrik cluster no longer protects the vApps. + *[ > ]: and then diff --git a/vcd_vmware_cloud_director_vapps.md b/vcd_vmware_cloud_director_vapps.md new file mode 100644 index 0000000000000000000000000000000000000000..3a5b4594662523d5873d843f3d7c424c231404ab --- /dev/null +++ b/vcd_vmware_cloud_director_vapps.md @@ -0,0 +1,24 @@ +# VMware Cloud Director vApps + +Source: https://docs.rubrik.com/en-us/saas/vcd/vmware_cloud_director_vapps.html + +--- + +# VMware Cloud Director vApps + +The Rubrik cluster provides SLA Domain protection and data management for VMware Cloud Director vApps. + +When you add a VMware Cloud Director instance to a Rubrik cluster, the Rubrik cluster automatically discovers all of the components of the VMware Cloud Director deployment, including: + + * Organizations + * Organization virtual datacenters + * vApps + * Virtual machines + +The components appear in the web UI and provide the basis for assigning SLA Domain protection to the vApps. RSC manages and protects the data in vApps using the same SLA Domain approach that it provides for vSphere virtual machines. + +You can derive the SLA Domain assignment of a vApp from a higher-level component or you can specify the assignment directly. Assigning an SLA Domain at a higher level in the organizational hierarchy automatically assigns the policies of that SLA Domain to all lower-level vApps and virtual machines. Assigning an SLA Domain at a lower level in the hierarchy overrides an assignment made at a higher level. + +RSC provides full protection of vApps, backing up not just virtual machine data but also vApp data and metadata, including networks, boot order, and access lists. + +RSC offers the option to enable or disable synchronized snapshots for a vApp. When enabled, RSC attempts synchronization across the vApp by initiating snapshots of all virtual machines in a vApp at the same time. diff --git a/vmware_cloud_vmware_cloud.md b/vmware_cloud_vmware_cloud.md new file mode 100644 index 0000000000000000000000000000000000000000..774eb1d85e5facfc10fc1cb5471752f99609e56f --- /dev/null +++ b/vmware_cloud_vmware_cloud.md @@ -0,0 +1,21 @@ +# VMware Cloud + +Source: https://docs.rubrik.com/en-us/saas/vmware_cloud/vmware_cloud.html + +--- + +# VMware Cloud + +A Rubrik Cloud Cluster effectively protects virtual machines deployed on VMware Cloud on AWS, Microsoft Azure VMware Solution, and Google Cloud VMware Engine. + +Rubrik provides comprehensive data protection, backup, and recovery solutions tailored specifically for virtual environments on VMware Cloud (VMC). + +VMware Cloud solutions include: + + * VMware Cloud on AWS + * Azure VMware Solution (AVS) + * Google Cloud VMware Engine (GCVE) + +These solutions offer software-defined data centers (SDDCs) for hosting virtual machines in the cloud. + +Rubrik Cloud Clusters safeguard data in VMC, AVS, and GCVE by ingesting data from the SDDC using HotAdd proxy virtual machines.