Rapid Restore: Data Rescue for Dynamics CRM and Power Apps
Best practices for Microsoft Dynamics CRM and Power Apps Backup and Recovery
Hi everyone, I'm Kelly O'Connor and I lead product marketing for our Microsoft
portfolio
at OWN and I'm joined by my colleague, Alagarsia, partner channel director and
business applications
Microsoft MVP.
Together, we're going to talk through rapid restore data rescue for dynamic CRM
and Power
Apps.
Throughout this session, we'll talk about own company, who we are and why we
exist, and
then we'll go through some real, dataverse data loss stories.
Alan is going to take us through the typical lifecycle of SAP disaster recovery
and then
share a demo of our solution.
And to close us out today, I will share a little bit more on our solution, a
recover
for Microsoft Dynamics, CRM and Power Apps.
OWN has been around for about 10 years and we launched right around the time
when SAP
was the shiny new toy and one of the more exciting novel inventions in the tech
industry.
A little background on us and who we are, we protect and activate SaaS data for
Microsoft
Dataverse, primarily dynamic CRM and Power Apps, ServiceNow and Salesforce.
We have almost 7,000 customers across all industries and we're a Microsoft ISV
that
can be found on the Azure marketplace.
The cornerstone of our product suite starts with recovery, a backup and
recovery solution
that protects SaaS data across all of these enterprise ecosystems.
Our platform has grown in the last 9 years to encompass a sandbox-eating
solution, data
security, data archiving and data analytics.
Like all startups, we were born out of a problem that required a solution.
When someone posed the question, but how do I recover my SaaS data in the cloud
What happens if there's a data event, which in this case means data loss,
corruption,
human error or integration has gone wrong?
You name it, you've heard of it and we've all probably experienced it in one
way or another.
The question is, this question is something that all MSA's and standard
enterprise software
agreements address in their contracts and it's called the shared responsibility
model,
which is the notion that the SaaS provider is responsible for the applications,
the operating
system, the physical network and data centers.
However, the data as well as the protection of that data is actually the SaaS
customer's
responsibility.
It's your responsibility.
Failing to protect that data against risks of data breaches, data corruption
events or
being out of compliance has significant financial consequences.
Whether you're looking at loss productivity or a loss of revenue, impact from
downtime
or the cost from the aftermath of a data breach caused by security failures or
the
cost of failing to comply with any number of growing regulations, the
requirement to provide
safeguards to ensure this business critical data is protected is of utmost
importance to
you, your company and your stakeholders.
So before I pass it off to Alan, I just want to highlight a few of the common
scenarios
that we see from our customers.
Starting with rogue integrations, one customer lost 40,000 quotes in dynamic CR
M and dynamics
was actually put into read-only mode for 96 hours until remediation could begin
There's a common scenario that we see a lot of which is data corruption due to
human
error.
With that finger, it happens.
At this biotech manufacturing company, 5,000 serial numbers were overwritten
and were unable
to be recovered.
And then there's dataverse storage capacity.
We see this quite a bit with our enterprise customers that are rapidly scaling
and doubling
their license counts.
This causes them to hit their storage capacity and blow out their dataverse
storage budget.
Our product, own recover, can help mitigate all of these scenarios.
Alan, are you?
Thanks, Kelly.
So what we want to talk about here today is this model of disaster recovery.
In this diagram really depicts what that disruption looks like for a business.
You'll see on the left-hand side of this green arrow is normal operations and
the right-hand
side is normal operations.
But there's this big breach in the middle with the disruption event in the blue
star
and then the big white arrow.
Well, what this really represents is that when a data event occurs, whether it
's a loss
or a corruption event, whatever it might be, the business has to stop operating
normally.
The business has to go into an audible mode.
And so this is a real challenge because of the time that it takes.
So consider to yourself how long it would take if you were to restore your
production
dataverse database into a sandbox and wait for that to complete and then take
it out
of the admin mode and then run your advanced find or your SQL TDS endpoint
queries to
find what was wrong.
Just that effort alone is ours if not days.
And then once you do find that information, you have to find out what the size
and the
severity, the magnitude of that data event was.
And then you have to get very precise around what it is you're going to be
recovering in
that process.
So it's a very complex time-intensive process before you even get to the point
where you
can start to write that information back in, which also is questionable.
Because when you start to write that information back in, you're not always
certain that you're
getting all of the related records and the hierarchy, anything that was orphan
ed in the
process of the deletion.
And there are so many complexities, especially with moving targets with your
metadata.
As you're enhancing your systems, all of that information is changing too.
So this white bar really represents in the real world days and weeks of
business interruption
that here at own what we're trying to do and what we want to illustrate to you
in the
next, oh, we'll say six or seven minutes in a demo is that we can do this in
minutes.
It doesn't take hours or days or weeks for your business to be waiting for the
data for
their data to come back to normal.
So with that, let me just jump in and I'll show you the demo of the product.
And I'll show you the real life cycle end to end, what happens when a data loss
or corruption
event occurs and how we can handle that with own.
Okay, so here we are in the own backup interface.
And again, we really strive hard to make difficult things easy.
So I'm going to go into one of these tiles, which represents one of the
environments in
my tenant that I'm currently backing up.
Somebody has told me that there was a data loss or a corruption event.
And they said a certain number of accounts and opportunities were lost.
So without doing any restore of a backup in Power Platform Admin Center,
without needing
the tenant storage in order to do that restore, I can immediately go in and I
can look at
multiple days of backups here in a single glance in an interactive chart.
And I can see this very quickly.
Okay, here's all of the removals for my account object.
Now if I want to see the opportunities, I could do that quickly too.
So just this quickly, I can see at a glance what my removals looked like in the
date
ranges for accounts and opportunities.
And if there's something a particular area or date that I want to inspect even
further,
again, I'm not doing any restore of a database.
This is real time and I can see this ad hoc.
And so now I see that there was 1100 thereabouts of these opportunities that
were removed.
So I want to see more about this April 26 date because that's a red flag for me
So while my business stakeholder is waiting on the telephone with me, I can say
, yeah,
let's take a look at that date of the 26 when we think this occurred.
And yeah, there was 1100 opportunities deleted.
But you know what, there was also 236 accounts that were deleted too.
So we know that when these accounts are getting deleted, there's a lot of casc
ading stuff that's
happening.
And so if I click on this 236, it's pre-quarantined and it's going to give me
that CSV file so
that I can send that to my business stakeholder while we're on the phone and
say, hey, does
this look like what you're looking for?
And when the business user says, yeah, that's absolutely what I needed to have
restored.
So the single click I can go in and I'm already starting to execute those pre-
quarantined
records into a preview for me.
So as an admin, I've done all of that stuff that that white bar on the previous
graph
takes days and weeks.
I've literally done this in just a few seconds with my business customer on the
phone.
And it builds a lot of faith for these business customers knowing that their
data is going
to be available and that's easily restored without having to wait for days and
weeks
in order to resume their business process.
Okay, so now it looks like this job is done and it has prepared all of that
data that
was lost, including, as you can see, the child records that were deleted along
the way with
the cascading delete.
So I can now choose some or any or all of these hierarchy of records and I can
then initiate
my restore as I need to.
You'll see here that it does not automatically bypass your business logic that
you've built
with third-party applications and plugins.
So when we hit this Restore option or Restore button, it's going to be the same
as if you
hired on a whole bunch of data entry clerks and put them into the empty cub
icles and had
them start manually entering the data in.
So all of your business processes and logic is going to continue to run just as
used as
you have designed it.
So while that's running, now let's take another look at a scenario when it
might be a corruption
event and how you can quickly isolate that information and work with it and
restore down
to the field level on the data.
So I'll go back into my backup.
I'm going to go back and I'm going to look at that same date range of the 26th
they're
abouts.
So here is the 26th.
I'm going to go back into that backup and I want to run a comparison because I
see a
big red flag here with these incidents or the chases.
So when I do this comparison job, it's actually going to do a comparison
between the two different
backups with again without restoring those into a sandbox environment first.
So you'll see how quickly this runs.
We have custom indexes that we build proprietary indexes that makes this run
very quickly.
And when I go into this, you'll see in our ability to look at this from a
precision
layer restore perspective, we can look at this and really work with the data
quickly
and just the data we need to.
So I want to look at the changes.
I don't want to look at the deletions and the additions so I can quickly toggle
those
off.
And what it's going to leave me with was only those changed records.
So okay, now I've got just the changed records and we're all very used to in
Excel where
we right click hide column, right click hide column for all of these extra
columns just
so that we can see what was changed.
We've simplified that for you.
You can do that with a single click and now it's going to show you only those
fields
were changed.
And instead of having to have two spreadsheets upside by side and looking left
and right,
trying to compare row for row, we've actually layered that right on top of it
for you.
So when you hover on top of a field, you'll be able to see what the old and the
new values
were.
So it's very easy for you to find what you're looking for and you can choose
these and add
them into your restore bucket one or all however you want to do this.
And now it's at the row level.
And then when you go into your restore bucket, you can further filter that down
to just your
column level.
So imagine you're doing a integration and you're not real certain if a
calculated field is working
or something to that effect.
Everything else runs fine.
So you want to exclude those because they worked well or they worked as
designed.
But some of these you need to restore.
So now you can just pick those columns that you want to restore and you can go
ahead
and initiate that restore where it will be at the column level and the row
level.
This will function exactly the same as the previous restore we just looked at.
And then it'll pause and it'll continue to write that back in as if you have
data entry
clerks doing the hard heavy lifting for you.
And that's our end to end.
So you saw just in a few minutes here, we've had a data loss as well as a data
corruption
event.
We found it, we've initiated the recovery and we've executed that all within
minutes,
not within days and weeks and God forbid months.
So with that back to you, Kelly.
Thank you, Alan.
So you just saw a recover from Microsoft Dynamics CRM and Power Apps in action.
This is our powerful business continuity solution for Dataverse.
Alan took you through some of the most compelling features and use cases with
cover offers.
But if I had to boil it down to the top three most valuable things that
recovery can help
you with, it's one ensuring your business is operating with accurate data by
leveraging
visualization tools that ensure the health and accuracy of your data.
Two restore your data granularly without compromising data relationships or
permissions.
This is where rapid restore comes in.
This is your data rescue tool.
Three retain backups for as long as you need.
Design the retention policy that's tailored to your business and your needs.
It's also extremely important to meet and ensure compliance.
The Dynamics and Power Platform compliance utilities do not address all
regulatory compliance
use cases, which can be costly and require manual labor for your teams.
Own has a dedicated staff ensuring all current compliance requirements and
regulations are
being met, which helps streamline the effort to meet and ensure regulatory
compliance for
your company.
Thank you for your time.
To get a deeper dive on recover from Microsoft Dynamics CRM and Power Apps, go
to our web page
to request the demo or meet with one of our account executives to learn more.
[BLANK_AUDIO]