Kelly O'Connor 15 min

Rapid Restore: Data Rescue for Dynamics CRM and Power Apps


0:00

Hi everyone, I'm Kelly O'Connor and I lead product marketing for our Microsoft

0:04

portfolio

0:05

at OWN and I'm joined by my colleague, Alagarsia, partner channel director and

0:10

business applications

0:11

Microsoft MVP.

0:12

Together, we're going to talk through rapid restore data rescue for dynamic CRM

0:17

and Power

0:18

Apps.

0:19

Throughout this session, we'll talk about own company, who we are and why we

0:25

exist, and

0:25

then we'll go through some real, dataverse data loss stories.

0:29

Alan is going to take us through the typical lifecycle of SAP disaster recovery

0:34

and then

0:35

share a demo of our solution.

0:37

And to close us out today, I will share a little bit more on our solution, a

0:41

recover

0:41

for Microsoft Dynamics, CRM and Power Apps.

0:46

OWN has been around for about 10 years and we launched right around the time

0:51

when SAP

0:52

was the shiny new toy and one of the more exciting novel inventions in the tech

0:56

industry.

0:57

A little background on us and who we are, we protect and activate SaaS data for

1:03

Microsoft

1:04

Dataverse, primarily dynamic CRM and Power Apps, ServiceNow and Salesforce.

1:10

We have almost 7,000 customers across all industries and we're a Microsoft ISV

1:15

that

1:16

can be found on the Azure marketplace.

1:18

The cornerstone of our product suite starts with recovery, a backup and

1:23

recovery solution

1:25

that protects SaaS data across all of these enterprise ecosystems.

1:30

Our platform has grown in the last 9 years to encompass a sandbox-eating

1:34

solution, data

1:35

security, data archiving and data analytics.

1:43

Like all startups, we were born out of a problem that required a solution.

1:47

When someone posed the question, but how do I recover my SaaS data in the cloud

1:53

What happens if there's a data event, which in this case means data loss,

1:57

corruption,

1:58

human error or integration has gone wrong?

2:01

You name it, you've heard of it and we've all probably experienced it in one

2:05

way or another.

2:07

The question is, this question is something that all MSA's and standard

2:11

enterprise software

2:12

agreements address in their contracts and it's called the shared responsibility

2:18

model,

2:18

which is the notion that the SaaS provider is responsible for the applications,

2:23

the operating

2:24

system, the physical network and data centers.

2:27

However, the data as well as the protection of that data is actually the SaaS

2:32

customer's

2:33

responsibility.

2:34

It's your responsibility.

2:39

Failing to protect that data against risks of data breaches, data corruption

2:44

events or

2:45

being out of compliance has significant financial consequences.

2:51

Whether you're looking at loss productivity or a loss of revenue, impact from

2:55

downtime

2:56

or the cost from the aftermath of a data breach caused by security failures or

3:01

the

3:01

cost of failing to comply with any number of growing regulations, the

3:06

requirement to provide

3:08

safeguards to ensure this business critical data is protected is of utmost

3:13

importance to

3:14

you, your company and your stakeholders.

3:19

So before I pass it off to Alan, I just want to highlight a few of the common

3:23

scenarios

3:24

that we see from our customers.

3:27

Starting with rogue integrations, one customer lost 40,000 quotes in dynamic CR

3:33

M and dynamics

3:34

was actually put into read-only mode for 96 hours until remediation could begin

3:40

There's a common scenario that we see a lot of which is data corruption due to

3:44

human

3:45

error.

3:46

With that finger, it happens.

3:48

At this biotech manufacturing company, 5,000 serial numbers were overwritten

3:52

and were unable

3:53

to be recovered.

3:56

And then there's dataverse storage capacity.

3:58

We see this quite a bit with our enterprise customers that are rapidly scaling

4:02

and doubling

4:03

their license counts.

4:05

This causes them to hit their storage capacity and blow out their dataverse

4:10

storage budget.

4:12

Our product, own recover, can help mitigate all of these scenarios.

4:17

Alan, are you?

4:21

Thanks, Kelly.

4:23

So what we want to talk about here today is this model of disaster recovery.

4:29

In this diagram really depicts what that disruption looks like for a business.

4:34

You'll see on the left-hand side of this green arrow is normal operations and

4:39

the right-hand

4:39

side is normal operations.

4:42

But there's this big breach in the middle with the disruption event in the blue

4:45

star

4:45

and then the big white arrow.

4:48

Well, what this really represents is that when a data event occurs, whether it

4:53

's a loss

4:53

or a corruption event, whatever it might be, the business has to stop operating

4:58

normally.

4:59

The business has to go into an audible mode.

5:02

And so this is a real challenge because of the time that it takes.

5:07

So consider to yourself how long it would take if you were to restore your

5:11

production

5:11

dataverse database into a sandbox and wait for that to complete and then take

5:17

it out

5:18

of the admin mode and then run your advanced find or your SQL TDS endpoint

5:22

queries to

5:23

find what was wrong.

5:26

Just that effort alone is ours if not days.

5:32

And then once you do find that information, you have to find out what the size

5:35

and the

5:36

severity, the magnitude of that data event was.

5:40

And then you have to get very precise around what it is you're going to be

5:44

recovering in

5:45

that process.

5:46

So it's a very complex time-intensive process before you even get to the point

5:52

where you

5:53

can start to write that information back in, which also is questionable.

5:58

Because when you start to write that information back in, you're not always

6:02

certain that you're

6:03

getting all of the related records and the hierarchy, anything that was orphan

6:09

ed in the

6:10

process of the deletion.

6:12

And there are so many complexities, especially with moving targets with your

6:16

metadata.

6:17

As you're enhancing your systems, all of that information is changing too.

6:21

So this white bar really represents in the real world days and weeks of

6:26

business interruption

6:28

that here at own what we're trying to do and what we want to illustrate to you

6:32

in the

6:32

next, oh, we'll say six or seven minutes in a demo is that we can do this in

6:37

minutes.

6:38

It doesn't take hours or days or weeks for your business to be waiting for the

6:42

data for

6:42

their data to come back to normal.

6:48

So with that, let me just jump in and I'll show you the demo of the product.

6:51

And I'll show you the real life cycle end to end, what happens when a data loss

6:55

or corruption

6:56

event occurs and how we can handle that with own.

7:00

Okay, so here we are in the own backup interface.

7:03

And again, we really strive hard to make difficult things easy.

7:09

So I'm going to go into one of these tiles, which represents one of the

7:12

environments in

7:13

my tenant that I'm currently backing up.

7:17

Somebody has told me that there was a data loss or a corruption event.

7:20

And they said a certain number of accounts and opportunities were lost.

7:25

So without doing any restore of a backup in Power Platform Admin Center,

7:30

without needing

7:31

the tenant storage in order to do that restore, I can immediately go in and I

7:36

can look at

7:37

multiple days of backups here in a single glance in an interactive chart.

7:42

And I can see this very quickly.

7:45

Okay, here's all of the removals for my account object.

7:49

Now if I want to see the opportunities, I could do that quickly too.

7:53

So just this quickly, I can see at a glance what my removals looked like in the

7:59

date

7:59

ranges for accounts and opportunities.

8:02

And if there's something a particular area or date that I want to inspect even

8:07

further,

8:08

again, I'm not doing any restore of a database.

8:11

This is real time and I can see this ad hoc.

8:15

And so now I see that there was 1100 thereabouts of these opportunities that

8:19

were removed.

8:20

So I want to see more about this April 26 date because that's a red flag for me

8:27

So while my business stakeholder is waiting on the telephone with me, I can say

8:33

, yeah,

8:34

let's take a look at that date of the 26 when we think this occurred.

8:39

And yeah, there was 1100 opportunities deleted.

8:42

But you know what, there was also 236 accounts that were deleted too.

8:47

So we know that when these accounts are getting deleted, there's a lot of casc

8:51

ading stuff that's

8:52

happening.

8:53

And so if I click on this 236, it's pre-quarantined and it's going to give me

8:59

that CSV file so

9:00

that I can send that to my business stakeholder while we're on the phone and

9:04

say, hey, does

9:05

this look like what you're looking for?

9:08

And when the business user says, yeah, that's absolutely what I needed to have

9:13

restored.

9:13

So the single click I can go in and I'm already starting to execute those pre-

9:18

quarantined

9:19

records into a preview for me.

9:22

So as an admin, I've done all of that stuff that that white bar on the previous

9:27

graph

9:28

takes days and weeks.

9:30

I've literally done this in just a few seconds with my business customer on the

9:36

phone.

9:36

And it builds a lot of faith for these business customers knowing that their

9:40

data is going

9:41

to be available and that's easily restored without having to wait for days and

9:48

weeks

9:48

in order to resume their business process.

9:52

Okay, so now it looks like this job is done and it has prepared all of that

10:00

data that

10:01

was lost, including, as you can see, the child records that were deleted along

10:06

the way with

10:07

the cascading delete.

10:09

So I can now choose some or any or all of these hierarchy of records and I can

10:15

then initiate

10:16

my restore as I need to.

10:20

You'll see here that it does not automatically bypass your business logic that

10:24

you've built

10:25

with third-party applications and plugins.

10:28

So when we hit this Restore option or Restore button, it's going to be the same

10:33

as if you

10:34

hired on a whole bunch of data entry clerks and put them into the empty cub

10:39

icles and had

10:40

them start manually entering the data in.

10:43

So all of your business processes and logic is going to continue to run just as

10:46

used as

10:47

you have designed it.

10:51

So while that's running, now let's take another look at a scenario when it

10:56

might be a corruption

10:57

event and how you can quickly isolate that information and work with it and

11:02

restore down

11:03

to the field level on the data.

11:07

So I'll go back into my backup.

11:09

I'm going to go back and I'm going to look at that same date range of the 26th

11:13

they're

11:14

abouts.

11:15

So here is the 26th.

11:17

I'm going to go back into that backup and I want to run a comparison because I

11:24

see a

11:25

big red flag here with these incidents or the chases.

11:29

So when I do this comparison job, it's actually going to do a comparison

11:34

between the two different

11:35

backups with again without restoring those into a sandbox environment first.

11:41

So you'll see how quickly this runs.

11:43

We have custom indexes that we build proprietary indexes that makes this run

11:49

very quickly.

11:51

And when I go into this, you'll see in our ability to look at this from a

11:55

precision

11:56

layer restore perspective, we can look at this and really work with the data

12:01

quickly

12:02

and just the data we need to.

12:05

So I want to look at the changes.

12:07

I don't want to look at the deletions and the additions so I can quickly toggle

12:10

those

12:11

off.

12:12

And what it's going to leave me with was only those changed records.

12:17

So okay, now I've got just the changed records and we're all very used to in

12:22

Excel where

12:23

we right click hide column, right click hide column for all of these extra

12:28

columns just

12:29

so that we can see what was changed.

12:31

We've simplified that for you.

12:33

You can do that with a single click and now it's going to show you only those

12:37

fields

12:37

were changed.

12:39

And instead of having to have two spreadsheets upside by side and looking left

12:43

and right,

12:44

trying to compare row for row, we've actually layered that right on top of it

12:49

for you.

12:50

So when you hover on top of a field, you'll be able to see what the old and the

12:54

new values

12:55

were.

12:58

So it's very easy for you to find what you're looking for and you can choose

13:01

these and add

13:02

them into your restore bucket one or all however you want to do this.

13:07

And now it's at the row level.

13:10

And then when you go into your restore bucket, you can further filter that down

13:14

to just your

13:15

column level.

13:17

So imagine you're doing a integration and you're not real certain if a

13:21

calculated field is working

13:22

or something to that effect.

13:25

Everything else runs fine.

13:27

So you want to exclude those because they worked well or they worked as

13:32

designed.

13:33

But some of these you need to restore.

13:35

So now you can just pick those columns that you want to restore and you can go

13:39

ahead

13:39

and initiate that restore where it will be at the column level and the row

13:46

level.

13:46

This will function exactly the same as the previous restore we just looked at.

13:50

And then it'll pause and it'll continue to write that back in as if you have

13:54

data entry

13:55

clerks doing the hard heavy lifting for you.

13:59

And that's our end to end.

14:00

So you saw just in a few minutes here, we've had a data loss as well as a data

14:04

corruption

14:04

event.

14:05

We found it, we've initiated the recovery and we've executed that all within

14:11

minutes,

14:12

not within days and weeks and God forbid months.

14:16

So with that back to you, Kelly.

14:18

Thank you, Alan.

14:20

So you just saw a recover from Microsoft Dynamics CRM and Power Apps in action.

14:25

This is our powerful business continuity solution for Dataverse.

14:28

Alan took you through some of the most compelling features and use cases with

14:33

cover offers.

14:34

But if I had to boil it down to the top three most valuable things that

14:37

recovery can help

14:38

you with, it's one ensuring your business is operating with accurate data by

14:43

leveraging

14:44

visualization tools that ensure the health and accuracy of your data.

14:49

Two restore your data granularly without compromising data relationships or

14:54

permissions.

14:56

This is where rapid restore comes in.

14:58

This is your data rescue tool.

15:00

Three retain backups for as long as you need.

15:04

Design the retention policy that's tailored to your business and your needs.

15:08

It's also extremely important to meet and ensure compliance.

15:11

The Dynamics and Power Platform compliance utilities do not address all

15:15

regulatory compliance

15:16

use cases, which can be costly and require manual labor for your teams.

15:22

Own has a dedicated staff ensuring all current compliance requirements and

15:26

regulations are

15:27

being met, which helps streamline the effort to meet and ensure regulatory

15:31

compliance for

15:32

your company.

15:33

Thank you for your time.

15:35

To get a deeper dive on recover from Microsoft Dynamics CRM and Power Apps, go

15:40

to our web page

15:40

to request the demo or meet with one of our account executives to learn more.

15:44

[BLANK_AUDIO]

X

This is a test comment.

X

This is a longer test comment to see how this looks if the person decides to ramble a bit. So they're rambling and rambling and then they even lorem ipsum.


author