Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Loading...
Rubrik Data Protection is the core Rubrik application to protect your enterprise data with air-gapped, immutable, access-controlled backups. As we dive into the dashboard, you will notice that each tile surfaces key information to the administrator with metrics that are collected across enterprise, cloud, and SaaS workloads.
Once you are logged into RSC, you will be presented with the Data Protection dashboard:
Let's take a closer look at the key information presented in the Data Protection UI. From the dashboard:
In the upper-right, notice that you can monitor cluster health, capacities, and archival statistics at a glance:
In the lower-right, you'll notice you can view all in-progress, failed, completed, and canceled tasks across your Rubrik deployment:
In the lower left, you can quickly identify your compliance status over the last 24 hours, or in intervals reaching back to the start date of the protection, for any type of workload (Data Center, SaaS, or Cloud) - saving you the troubles of jumping through multiple interfaces to gauge your compliance status over time:
The Protected Objects tile in the upper left gives you more granular protection statistics for each category of protected data.
If you hover over the Data Center category, you can quickly identify objects and data that are currently protected, set to do not protect, and No SLA. Instead of running multiple reports across different applications to answer basic questions, you can often find the answer using the Data Protection Dashboard:
Let's dive into getting some SQL and Oracle workloads protected by SLA policies!
Many organizations use Microsoft SQL Server for their critical applications. Throughout the years, SQL Server has steadily improved to become a critical component of modern data centers. Despite these improvements, SQL Server backups have often been a question of trade-offs between cost, efficiency, and simplicity.
Rubrik’s SQL Server backup functionality builds on top of Rubrik’s policy-driven architecture extending it to SQL backups. Although SQL Server environments can be complex, Rubrik’s support for SQL Server backups aligns with the core architectural and operational simplicity of the Rubrik Security Cloud.
The RBS provides enhanced integration with protected resources and host systems. The RBS software can be downloaded directly from RSC each time the software is needed, or the software can be downloaded once and pushed to hosts as needed. Providing software directly from the RSC enables the Rubrik cluster and a hosted deployment of the RBS to authenticate reliably with each other.
To get started on the migration task, you first need to install the Rubrik Backup Service (RBS) on the MS SQL host and then add the host to RSC.
Navigate to Inventory > All > SQL Server Databases.
Click ADD HOSTS.
Select the default Rubrik Cluster from the drop-down menu. Select "I want to install and register the RBS software now". Click copy button. Close the window by clicking on X on top..
Double-click the RDP session shortcut named as "SQL2.rdp" on the Desktop.
On the RDP session, open the google chrome browser.
Right-click the address bar and click "paste and go to the ...connector.zip" and press Enter.
For the "Your connection is not private' msg, click Advanced. This will start the download of RBS.
From the taskbar, click on the folder sign and navigate to the Downloads folder.
Right-click the RubrikBackupService.zip file and Select Extract All at the default destination folder.
Double-click the RubrikBackupService installer package. Click on More Info in the pop-up box and then click on Run anyway.
Follow the instructions on the screen to install the package with Typical installation.
NOTE: Accept/Allow any pop-ups for unknown apps to allow you to make changes to your device.
Click on Finish to complete the installation.
Click on the search icon from the taskbar and type Services. Double-click Services to start it.
Verify that the Rubrik Backup Service is up and running.
You have now successfully installed the RBS agent on the SQL host.
RBS installation follows a similar process for Linux/Debian-based hosts. You can download the package using wget and use your typical installation method, e.g., yum install, to install the packages.
The core functionality across the supported host OS remains the same.
Rubrik’s SQL Server backup functionality builds on top of Rubrik’s policy-driven architecture extending it to SQL backups. Although SQL Server environments can be complex, Rubrik’s support for SQL Server backups aligns with the core architectural and operational simplicity of the Rubrik platform.
Armed with that information, first, you will first focus on protecting the SQL database which hosts your critical applications.
Rubrik Security Cloud operationalizes all the data situated in your distributed environment into a robust metadata framework. It organizes all the business information to make it discoverable and usable, no matter where it is. By consolidating all the metadata from several data sources into a unified system of record, Rubrik enables customers to enhance the business value hidden in their data assets.
Rubrik Data Protection (RDP) delivers centralized management for your global, distributed Rubrik environment. Designed for a seamless user experience, RDP provides a comprehensive view of customers' physical, virtual, and cloud topologies while making management tasks elegantly simple and intuitive. Search for a point-in-time activity by application or location. Determine SLA-compliant applications at a glance. Powered by an automated visualization engine, RDP enables filtering as you go to generate rich custom dashboards in minutes.
Rubrik allows administrators to abstract away much of the low-end fuss required to build and maintain data protection to focus on adding value at a more strategic level across the organization. Rubrik's policy engine is simple as all of the imperative details are abstracted away and handled by an ingenious scale-out system. The customer input fields are reduced to RPO, retention period, archive target, and replication target for specifying SLAs for protected objects.
In this lab, you will be playing the part of a new System Administrator at Zaffre. This is week two for you at Zaffre, and your initial task is to finish the migration of the MS SQL and Oracle workloads to Rubrik.
So without any delay, let's get started.
WARNING: This is a virtualized lab environment. All systems are running with nested virtualization. This being the case, no expectation for performance should be assumed while using this lab, nor should you consider this lab reflective of the performance expected in a production deployment. This lab is for demo and educational purposes only.
The Rubrik lab environment consists of multiple cloud-hosted virtual machines used to emulate the web application and protection of the Zaffre fashion group.
AD1 = Windows VM for Active Directory, DHCP, and DNS services covering both virtual sites in the rubrik.lab domain.
ESX1 = This is an unmanaged (no vCenter) virtual ESXi Host used to host the Rubrik Edge CDM instances supporting this lab. You should not need to interact with this host through the consoles.
VC1 = These are the ESXi Hosts that contain the test Linux VMs and the vCenter instances supporting each virtual data center.
Jump = This is the VM where you will interact via browser with the lab's various components.
Startup = This VM hosts all of the automation used to provision this lab. You may ignore this VM and should not need to interact with it at all. It should remain powered off.
These serve as the infrastructure for the Zaffre Fashion Group and Haverford websites.
To connect to the Rubrik Security Cloud, start the Google Chrome browser from the jump host. Click on the Lab Credentials bookmark. This bookmark contains the Rubrik Security Cloud URL, username & password for all required hosts.
Rubrik Security Cloud is referred to as Rubrik in the credentials bookmark.
Please use the copy button for username and password.
Note that the lab guide name will reflect this lab, not necessarily the name in the image below.
From here, right-click and open the Rubrik hyperlink.
Enter the specified username and password by copying both from the Lab Credentials page.
Enter Demo as the username, first name, last name, title, and company. For email, enter demo@xyz.com.
Click on I AGREE.
On the next screen for Enable Multi-Factor Authentication, click on SKIP FOR NOW.
On the next screen for Multi-Factor Authentication Required, click on GOT IT.
Reduce the zoom to 75% in your Chrome environment for the lab to be most easily accessible
Now that you have added the host to RSC, you must start protecting your workload. For that, first, you will create a Global SLA policy for the SQL2 host and then assign the SLA policy to the host.
Navigate to SLA DOMAINS > CREATE SLA DOMAIN.
Click Create. Expand Databases and Apps under Datacenter Objects.
Select SQL Server Databases and select Next.
Add 4 hours as the snapshot frequency and 7 days as Retain snapshot duration. Leave everything as default. Then, click Next.
Click Next till you reach Log backup.
Toggle Log backup.
Add 15 mins as the log backup frequency and 7 days as Retention.
Click Next. Add Demo-sql-host2 as the SLA Domain name.
Click CREATE.
Close all the pop-ups.
Ensure the new SLA is listed in the SLA Domains inventory.
Rubrik’s robust SLA policy engine ensures that data is where it needs to be when it needs to be there, enabling Rubrik to deliver rapid recovery combined with the security provided by encryption and an immutable filesystem.
The robust SLA policy creation process is similar across all the different workloads, e.g., across on-prem, cloud, and SaaS.
Let's move on to the next step of assigning the newly created SLA Domain to MS SQL objects.
Now that you have created the SLA Domain, it's time for you to assign it to unprotected SQL databases and ensure it's protected.
To get started, head back to Inventory > All > SQL Server Databases.
Select sql2 and click MANAGE PROTECTION.
Select Demo-sql-host2 SLA domain from the list, click NEXT, and lastly, click ASSIGN.
NOTE: You have protected the host. Notice how all the databases under the host are automatically protected by the same SLA policy. You can assign different SLA policies for each of the databases if the SLA requirements are different.
All databases on this SQL2 host will now be protected using this SLA (even new ones created after this point).
As an administrator, you need to ensure that you schedule an on-demand backup.
Navigate to SQL2 > MSSQLSERVER > msdb from the inventory list.
From the top right, click TAKE ON DEMAND SNAPSHOT and leave the rest of the details as defaults.
NOTE: To fast-track, we have already installed the RBS on the SQL host sql1, applied an SLA to some of the databases, and have some snapshots ready to go. You will use the two SQL hosts to explore the recovery options.
Navigate to sql1.rubrik.lab > MSSQLSERVER.
Select WideWorldImporters and click MANAGE PROTECTION.
Select Global_DB_Silver as the SLA.
Click NEXT.
Click ASSIGN.
Take an on-demand snapshot of the WideWorldImporters database.
Excellent job for completing the migration and protection of SQL workloads! Let's make sure you can recover the applications quickly when needed.
Your SQL Databases often support critical workloads, which can require a lot of testing or development efforts on the production data. Let's discuss how Zaffre can take advantage of the export option creates a standalone copy of one or many databases and can be used without affecting the live production data.c
To get started on the restore operation, first navigate to Inventory > All > SQL Server Databases.
Navigate to sql1.rubrik.lab > MSSQLSERVER > WideWorldImporters.
Select the most recent day with green checks in the calendar.
Move the slider close to the last log time.
Click (...) ellipse and select Recover. Select Export and then click NEXT.
Choose sql2 as the compatible host.
Select MSSQLSERVER as compatible instances.
Add WideWorldImporters_exported as the name, select Advanced Method and choose the default restore path.
Click Export.
Click EVENTS from the left middle panel. Verify on the Events page that the export operation has been completed.
NOTE: It takes about a minute for the Events page to show the export operation
Now, you can verify the exported copy of the database on sql2 host.
From the desktop taskbar at the bottom, double-click the Microsoft SQL Management studio. Select SQL2 as the Server name.
Click Connect.
Expand Databases and verify WideWorldImporters_exported is listed as one of the databases.
Your SQL Databases often support critical workloads, which can require a lot of testing or development efforts on the production data. The export option is a common use case for using a production database snapshot as the source to spin up dev/test clones.
Great job, on successfully exporting your MS SQL database. On to the Live Mount option now!
Let's discuss how Zaffre can take advantage of the Restore option, which replaces an existing database (nuclear option) from a point in time selected during the restore process back to the original SQL Server.
To get started on the restore operation, first navigate to Inventory > All > SQL Server Databases.
Navigate to sql1.rubrik.lab > MSSQLSERVER > StandAlone_AdvWorks.
Select the most recent day with green checks in the calendar.
Move the slider close to the last log time.
Scroll down and select the first snapshot.
Click (...) ellipse and select Recover.
Select Restore and then click NEXT.
Click RESTORE.
Click EVENTS from the left middle panel.
NOTE: It takes about a minute for the Events page to show the restore operation
Verify on the Events page that the restore operation has been completed.
Your SQL Databases often support critical workloads which require an RPO in minutes. Rubrik supports this by backing up the transaction logs in addition to the databases. You can select the desired restore time simply by choosing a day and dragging a slider to the desired time and recover the database without losing critical data.
Great job, on successfully restoring your MS SQL database. On to the Export option now!
You will now focus on Item-level recovery from the live-mounted DB on the same host. However, you can perform live mounts of any databases on any host for other use cases.
To get started, delete an item, such as a table, from the StandAlone_AdvWorks database using the scripts provided in the next steps.
From the Jump host's desktop taskbar at the bottom, double-click the Microsoft SQL Management studio.
Select SQL1 as the Server name.
Click Connect.
Expand Databases and verify StandAlone_AdvWorks-LM is listed as one of the databases.
Select the Show_File_Location SQL query file from C:\Users\demo.RUBRIK\Desktop\SQL Demo Scripts.
Select Show File Location.sql script and click Open.
Execute the query by clicking on Execute from the ribbon functional area.
This script shows the live-mounted database location. Observe the output. The output shows the file is actually located on Rubrik and not in your storage.
Next, open the Delete Table SQL query file from C:\Users\demo.RUBRIK\Desktop\SQL Demo Scripts and execute it.
This script will delete the contents of Person.EmailAddress table from AdventureWorks database.
Next, open the Recover From LM SQL query file from C:\Users\demo.RUBRIK\Desktop\SQL Demo Scripts and execute it.
This script displays the output of the deleted table and then recovers the Person.EmailAddress table from StandAlone_AdvWorks-LM database to StandAlone_AdvWorks. The script also displays the output of the recovered Person.EmailAddress table in AdventureWorks database.
Go back to Google Chrome, and on RSC, navigate to Live Mounts from the top menu.
Select MSSQL Database.
Select (...) ellipse at the right end and select unmount.
From the pop-up, select UNMOUNT to start the unmount process.
Navigate to Events from the top menu. Verify that the unmount is successful.
Rubrik’s Live Mount extends beyond recovery use cases. The feature also enables easy, accelerated test/dev without impacting production.
Exceptional job, on successfully recovering the contents of one of the tables.
Oracle databases are the driving force behind your organization’s most critical applications - providing a performance-driven, relational storage for key transactions. Rubrik’s Oracle database backup functionality builds on top of Rubrik’s policy-driven architecture and optimizes Oracle RMAN database backup with integrated, automated backup and recovery system enhancements.
Armed with that information and after successfully protecting your SQL workloads, you will now focus on protecting the Oracle database, which hosts your critical CRM applications.
So far, you have looked at different recovery options and identified which of the recovery options can be used for various scenarios. Now, you will look at one last option for disaster recovery by creating a synchronous copy of a DB for Disaster Recovery as part of the Microsoft SQL Server Availability Group.
Microsoft SQL Server Availability Group databases are actively involved in database mirroring sessions and cannot be automatically replaced by a backup based on Microsoft SQL Server requirements.
As a result, Rubrik does not allow users to directly export, restore, or Live Mount any database into an Always On Availability Group (AAG) until databases are removed from the Availability Group.
Let's Talk about SQL Availability Groups!
Now that you have successfully installed the RBS, you can add the host to RSC.
Navigate back to RSC and click the radio button for "I have already installed and registered the RBS software." Add "sql2" as the Host FQDN. Click ADD.
After a minute, refresh the browser, and you can verify the host is added to RSC.
Great job with adding the host! Let's move on to the next step.
As a system or database administrator, It is always a good idea to be prepared for any recovery situation and understand the recovery options to recover rapidly from cyber-attacks, operational failures, or natural disasters.
Many recovery plans are based on restoring the entire host. Every data loss event and recovery can not be treated in the same manner. Normal day-to-day business functions routinely change data. These changes are coordinated across multiple files, databases, or even VMs.
Let's discuss how Zaffre can take advantage of this and have multiple options ready to go when it is needed for recovery.
Navigate to sql1.rubrik.lab > MSSQLSERVER > StandAlone_AdvWorks.
Select the latest date with the green checkbox.
Click (...) ellipse and select Recover.
Look at all the options available.
For now, close the recovery options page. You will explore each of the options shortly in the next upcoming sections.
Let's discuss how Zaffre can take advantage of the Live Mount option, which creates a new database from a point-in-time copy of the source database, running on Rubrik storage. RSC provides a Samba share of the new database directly from the Rubrik cluster storage layer to the SQL server selected during the restore procedure. Live Mount significantly reduces the recovery time for the database.
To get started on the Live Mount operation, first navigate to Inventory > All > SQL Server Databases.
Navigate to sql1.rubrik.lab > MSSQLSERVER > StandAlone_AdvWorks.
Select the most recent day with green checks in the calendar.
Click (...) ellipse and select Recover.
Select Mount and then click NEXT.
Choose sql1.rubirk.lab as the compatible host.
Choose MSSQLSERVER as the compatible instance.
Type StandAlone_AdvWorks-LM as the Live Mount database name.
Click Mount.
Click EVENTS from the left middle panel. Verify on the Events page that the Live Mount operation has been completed.
NOTE: It takes about a minute for the Events page to show the Live Mount operation
From the desktop taskbar at the bottom, double-click the Microsoft SQL Management studio.
Select SQL1 as the Server name.
Click Connect.
Expand Databases and verify StandAlone_AdvWorks-LM is listed as one of the databases.
Using Rubrik Live Mount, you can significantly reduce the recovery time for the database, and it provides the ability to quickly perform item-level recovery or patching testing for rolling updates to the production environment!
Great job, on successfully Live Mounting your MS SQL database. You will now recover a table using the live mount!
A secondary SQL Server database, also known as a log shipping target, is regularly updated from a primary database copy. SQL Log Shipping is a commonly used technique to keep a secondary database up-to-date. However, native tools can often require manual configuration steps. Rubrik automates all the config steps, which creates a synchronous copy of a DB for Disaster Recovery.
You can now configure SQL Server Log shipping to create a synchronous copy of StandAlone_AdvWorks and explore how you can prepare for DR.
To get started, first navigate to Inventory > All > SQL Server Databases.
Navigate to sql1.rubrik.lab > MSSQLSERVER > StandAlone_AdvWorks.
Click (...) ellipse and select Add Log Shipping Secondary.
Select sql2 as the compatible host.
Click NEXT.
Select MSSQLSERVER as compatible instances.
Add StandAlone_AdvWorks as the secondary database name, select Advanced Export and choose the default export path.
Click ADD.
From the desktop taskbar at the bottom, double-click the Microsoft SQL Management studio.
Select SQL1 as the Server name.
Click Connect. Expand Databases and verify that StandAlone_AdvWorks is listed as one of the databases.
Under Object Explorer, click Connect Object Explorer next to Connect. Select SQL2 as the server name and click Connect.
Expand Databases for SQL2, and you will find the StandAlone_AdvWorks is now in a (Restoring...) State.
Rubrik automates the configuration tasks on the primary and secondary SQL Servers.
You now have all the recovery options in your armor to ensure your critical data is always available!
Congratulations on completing the migration of your MS SQL database to RSC!
Now that you have successfully installed the RBS, you can add the host to RSC.
Navigate back to RSC and click the radio button for "I have already installed and registered the RBS software." Type ora12c-dev as the Host FQDN. Type oracle as SYSDBA user. Click ADD.
After a couple of minutes refresh the browser, and you can verify the host is added to RSC.
To get started on the migration task, you first need to install the Rubrik Backup Service (RBS) on the Oracle host and then add the host to RSC.
To get started, head to Inventory > All> Oracle Databases.
Click Add Hosts.
Select the default Rubrik Cluster from the drop-down menu. Select "I want to install and register the RBS software now". Select Linux as the platform and Linux rpm agent as the version. Click copy button. Close the window by clicking on X on top.
Double-click the Putty shortcut on the Desktop. Select orac12c-dev.rubrik.lab as the host and click Open.
Enter the credentials as listed below:
Username: root
Password: Welcome10!
NOTE: The credentials are also available on the credentials page on Chrome.
On the command prompt, enter the following commands to download and install the RBS package.
NOTE: Right-click will paste the link to download the rpm.
Install the package. Ensure that the demon status is up post the installation.
Great job with the RBS install! Let's move on to the next step.
As discussed before, RBS installation follows a similar process for Windows-based SQL hosts.
The core functionality across the supported host OS remains the same.
Now that you have added the host to RSC, you must start protecting your workload. For that, first, you will create a Global SLA policy for the orac12c-dev host and then assign the SLA policy to the host.
Navigate to SLA DOMAINS > CREATE SLA DOMAIN.
Click CREATE. Expand Databases and Apps under Datacenter Objects. Select Oracle Databases and select Next.
Add 4 hours as the snapshot frequency and 7 days as Retain snapshot duration. Leave everything as default. Then, click Next.
Click Next and leave everything as default until the Confirmation section. Add Demo-Oracle-Host2 as the SLA Domain name. Click CREATE. Close all the pop-ups.
Ensure the new SLA is listed in the SLA Domains inventory.
Rubrik’s robust SLA policy engine ensures that data is where it needs to be when it needs to be there, enabling Rubrik to deliver rapid recovery combined with the security provided by encryption and an immutable filesystem.
The robust SLA policy creation process is similar across all the different workloads, e.g., across on-prem, cloud, and SaaS.
After Live Mount, let's discuss how Zaffre can take advantage of the Clone option, which creates a secondary Oracle environment for running other jobs, such as reporting jobs, without affecting your production environment.
To get started on the restore operation, first, navigate to Inventory > All > Oracle Databases.
Navigate to ora12c-prod > orcl. Select the most recent day with green checks in the calendar. Move the slider close to the last log time. Go to the latest backup for the day, click (...) ellipse and select Recover. On the pop-up, select Clone and then click NEXT. Choose ora12c-dev as the compatible host and click NEXT. Leave everything as default and click Clone.
Click EVENTS from the left middle panel. Verify on the Events page that the Clone operation has been completed.
NOTES:
It takes about a minute for the Events page to show the clone operation.
It takes about five minutes for the clone operation to finish.
Double-click the Putty shortcut on the Desktop. Select ora12c-prod.rubrik.lab as the host and click Open.
On the SSH Window, log in with the following credentials:
Username: oracle
Password: oracle
Launch SQLPLUS by entering:
On the SQL> Prompt, run the following SQL command:
Repeat the same steps for ora12c-dev.rubrik.com.
The output on the secondary host ora12c-dev indicates data files are identical to the production database.
Rubrik’s Clone feature extends beyond recovery use cases. The feature enables easy, accelerated secondary environments for running different queries without impacting production.
Let's discuss how Zaffre can take advantage of the Instant Recovery option, which takes the snapshot of the latest backup image with the latest transaction log and restores it to your production oracle database server. The database runs off the Rubrik storage. This makes the recovery operation instantaneous, and the services to your customers can be restored with minimum downtime.
To get started on the Instant Recover operation, first, you need to simulate database instances down by shutting down the database.
Double-click the Putty shortcut on the Desktop. Select ora12c-prod.rubrik.lab as the host and click Open.
On the SSH Window, log in with the following credentials:
Username: oracle
Password: oracle
Launch SQLPLUS by entering:
On the SQL> Prompt, run the following SQL command:
Head back to RSC. Click (...) ellipse, and select Refresh. The database should disappear from the page.
NOTE: It can take a couple of minutes for the database to completely shut down and be available for recovery.
Now you will initiate the instant recovery of your oracle production database. First, navigate to Inventory > All > Oracle Databases.
Navigate to ora12c-prod. From the side panel, select the Relic filter for Status. orcl db will now be available under the ora12c-prod host. Select the most recent day with green checks in the calendar. Move the slider close to the last log time. Click (...) ellipse and select Recover. On the pop-up, select Instantly Recover and then click NEXT. Click RECOVER.
NOTE: If you see the error message like in the image below, then wait for a minute before retrying instant recovery
Click EVENTS from the left middle panel. Verify on the Events page that the Clone operation has been completed.
NOTES:
It takes about a minute for the Events page to show the instant recovery operation.
It takes about five minutes for the instant recovery operation to finish.
Navigate to Live Mounts from the top menu. Select Oracle Database. Ensure that orcl is listed as a live mount.
Navigate back to the SSH terminal for ora12c-prod.
Launch SQLPLUS by entering:
On the SQL> Prompt, run the following SQL command:
Recover the local database by running the move_datafiles.sql file.
You can now verify the location of the copied data is back to your storage.
Rubrik’s Instant Recovery feature extends beyond recovery use cases. The feature enables easy, accelerated secondary environments for running different queries without impacting production.
You now have all the recovery options in your armor to ensure your critical data is always available!
Congratulations on completing the migration of your Oracle database along with MS SQL database to RSC!
Let's discuss how Zaffre can take advantage of the Live Mount option, which creates a new database from a point-in-time copy of the source database running on Rubrik storage, enabling DBAs and developers to provision test and development in just a few clicks without impacting production environments.
To get started on the restore operation, first, navigate to Inventory > All > Oracle Databases.
Navigate to ora12c-prod > orcl. Select the most recent day with green checks in the calendar. Move the slider close to the last log time. Click (...) ellipse and select Recover. On the pop-up, select Live Mount and then click NEXT. Choose ora12c-dev as the compatible host. Leave everything as default and click Live Mount.
Click EVENTS from the left middle panel. Verify on the Events page that the Live Mount operation has been completed.
NOTE: It takes about a minute for the Events page to show the Live Mount operation.
Navigate to Live Mounts from the top menu. Select Oracle Database. Ensure that orcl is listed as a live mount.
Double-click the Putty shortcut on the Desktop. Select ora12c-dev.rubrik.lab as the host and click Open.
On the SSH Window, log in with the following credentials:
Username: oracle
Password: oracle
Launch SQLPLUS by entering:
On the SQL> Prompt, run the following SQL command:
The output indicates data files hosted on the Rubrik Cluster.
Go back to Google Chrome, and on RSC, you should be on the Live Mounts page. If not, navigate to Live Mounts from the top menu. Select Oracle Database. Select (...) ellipse at the right end and select unmount. From the pop-up, check the Force unmount and select UNMOUNT to start the unmount process.
Navigate to Events from the top menu. Verify that the unmount is successful.
Rubrik’s Live Mount extends beyond recovery use cases. The feature also enables easy, accelerated test/dev without impacting production.
Post the workload protection, it's really important to be prepared for any recovery situation. So now you will explore what the recovery options for Oracle databases are and how Zaffre can take advantage of these options.
To get started on the restore operation, first, navigate to Inventory > All > Oracle Databases.
Navigate to ora12c-prod > orcl. Select the latest date with the green checkbox. Click (...) ellipse and select Recover. Look at all the options available.
For now, close the recovery options page. You will explore each of the options shortly in the next upcoming sections.
Zaffre Fashion Group has finished migrating its Microsoft SQL and Oracle database workloads to RSC with your initiative. With cyber-attacks on the rise, it's important for ZFG to secure hundreds or even thousands of databases from cyber-attacks and operational errors without compromising the performance you need to operate at scale. By leveraging the applications available to you as a Rubrik Enterprise edition customer, you were able to:
We hope you've enjoyed this lab and learned how Rubrik’s solutions keep your MS SQL and Oracle data safe and easy to recover in the face of cyber-attacks and operational failures.
You can complement your use of the Data Protection dashboard with a diverse set of reports that can help you improve operations, plan for growth, and inspect compliance details. Reports can be modified, saved, and automatically distributed for team visibility. The same reports can also be utilized by the legal and compliance departments.
To get started, you can navigate to REPORTS from the top menu. As you can see, there are a lot of options to choose from.
Navigate to Compliance > Month Compliance Status. You can utilize this to centralize and keep track of the compliance status of all your ZFGs workloads. You can download the report (pdf/csv) by clicking the (...) ellipses. You can send reports on scheduled dates.
You can download the report and look at the other types of available reports.
Week 2 at ZFG for you has been very productive! You could not only migrate two workloads but also learn about recovery options to keep your critical data always available. Centralized compliance and reporting are the icings on the cake! Congratulations!
RSC 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!
Now that you have created the SLA Domain, it's time to assign it to the unprotected Oracle host and ensure it's protected.
To get started, head back to Inventory > All> Oracle Databases.
Select ora12c-dev and click MANAGE PROTECTION. Select Demo-Oracle-Host2 SLA domain from the list, click NEXT, and lastly, click ASSIGN.
NOTE: You have protected the host. All the databases (once created) under the host will be automatically protected by the same SLA policy. You can assign different SLA policies for each of the databases if the SLA requirements are different.
All databases (once created) on this ora12c-dev host will be protected using this SLA..
