Check out our companion blog!
Sept. 12, 2022

How to back up Jira

How to back up Jira

Jira is yet another service that could be at the center of your organization, and losing the data stored in there could cost you a lot. Did you know it doesn't even have an audit trail for many things? Not only can you lose data, you might not know what was deleted or who did it! We are joined this week from two representatives from Revyz, a new service to back up Jira. They talk about what to back up and what you can do for free, along with what functionality that misses out on. They then explain how their new service works and what it offers. Great episode where I learned a lot. Even if you don't use Jira, you will find a lot of useful info in this episode.

Mentioned in this episode:

Interview ad

Transcript
W. Curtis Preston:

Hi, and welcome to Backup Central's Restore it All podcast.

W. Curtis Preston:

I'm your host w Curtis Preston, AKA Mr.

W. Curtis Preston:

Backup, and I have with me, my cylinder misfire detection consultant, Prasanna

W. Curtis Preston:

Malaiyandi, how's it going Prasanna?

Prasanna Malaiyandi:

I'm good Curtis.

Prasanna Malaiyandi:

Honestly, I think you should just throw the entire thing out and just start over.

W. Curtis Preston:

I don't think that I don't think that's economically

Prasanna Malaiyandi:

No that don't do that, but this is the ongoing

Prasanna Malaiyandi:

saga for our listeners of Curtis's car that has an on again, off again,

Prasanna Malaiyandi:

cylinder misfire issue, which may or may not be a head gasket issue,

Prasanna Malaiyandi:

which may or may not be other things.

W. Curtis Preston:

Yeah, I either have a blown head gasket or, or a

W. Curtis Preston:

head gasket that is blowing That is in the process of being blown, uh, or an

W. Curtis Preston:

EGR valve stuck in the open position.

W. Curtis Preston:

And.

W. Curtis Preston:

Uh, the usual and the thing is it's, it's an intermittent problem.

W. Curtis Preston:

And so troubleshooting is very, very difficult, you know, for

W. Curtis Preston:

those of you that are, you know, your, your computer geeks, right?

W. Curtis Preston:

Like how do you fix a bug that only happens once every thousand

W. Curtis Preston:

times that you use the software?

Prasanna Malaiyandi:

exactly.

Prasanna Malaiyandi:

That's when you that's, when you basically turn it into cos.

W. Curtis Preston:

to what?

Prasanna Malaiyandi:

Cosmic.

Prasanna Malaiyandi:

I, one of the

W. Curtis Preston:

Oh yeah,

Prasanna Malaiyandi:

right.

Prasanna Malaiyandi:

If a bug was hit and no one's able to reproduce it, figure it out, right.

Prasanna Malaiyandi:

It'd basically be like the stars aligned.

Prasanna Malaiyandi:

There was a solar flare, some cosmic event happened and therefore

Prasanna Malaiyandi:

the bug is no longer there.

W. Curtis Preston:

I'm down to, I'm going to do the repair of one or the other,

W. Curtis Preston:

and both of them are, are significant.

W. Curtis Preston:

And then see if it goes away.

W. Curtis Preston:

Right.

Prasanna Malaiyandi:

I thought the EGR is less work than

W. Curtis Preston:

No, it's a lot.

W. Curtis Preston:

It's actually quite a bit of work.

W. Curtis Preston:

Um, because you,

Prasanna Malaiyandi:

out to get to it.

W. Curtis Preston:

yeah.

W. Curtis Preston:

It's.

W. Curtis Preston:

Yeah.

W. Curtis Preston:

And then, and then, and as long as you're pulling the EGR valve,

W. Curtis Preston:

you should pull out the, um, the intake manifold and clean it out.

W. Curtis Preston:

There's some ports that need to be, I've been watching, I've been watching

W. Curtis Preston:

a lot of YouTube videos Prasanna.

W. Curtis Preston:

You'd be very proud of me.

Prasanna Malaiyandi:

I am now.

Prasanna Malaiyandi:

What?

Prasanna Malaiyandi:

But wait though, Curtis, are you watching at two X?

W. Curtis Preston:

Uh, no, I I'm old school, man.

W. Curtis Preston:

I watch it at one X.

W. Curtis Preston:

I actually like you.

W. Curtis Preston:

like that.

W. Curtis Preston:

Well, I'm not like you, I'm not watching like 19 hours of it.

Prasanna Malaiyandi:

Hey,

W. Curtis Preston:

to get,

Prasanna Malaiyandi:

like four hours.

Prasanna Malaiyandi:

Come on.

W. Curtis Preston:

uh, yeah, but you're watching 19 hours videos in four hours

Prasanna Malaiyandi:

Ah, I wish they would actually go faster than two X that's.

Prasanna Malaiyandi:

Now my feature request for YouTube.

Prasanna Malaiyandi:

Any developers out there at YouTube?

W. Curtis Preston:

I can't imagine what in the world you would do at two X.

W. Curtis Preston:

Anyway.

W. Curtis Preston:

So, um, well we're gonna get onto something much more

W. Curtis Preston:

exciting than car maintenance.

W. Curtis Preston:

We're gonna talk about backup today.

W. Curtis Preston:

You know, my favorite topic, we have two guests today.

W. Curtis Preston:

Our first guest started his career, just like me as a backup admin, I first cross

W. Curtis Preston:

pass with, with him when he was leading the security and compliance team at

W. Curtis Preston:

Druva, uh, he is a co-founder of Revyz.

W. Curtis Preston:

Welcome to the podcast Sanket Parlikar

Sanket Parlikar:

glad to Glad be on the podcast.

W. Curtis Preston:

And we also have your co-founder.

W. Curtis Preston:

He started his career designing chips at SGI and has worked for

W. Curtis Preston:

multiple security firms, including Symantec, Druva, and Agari data.

W. Curtis Preston:

He's also a co-founder at Revyz.

W. Curtis Preston:

Welcome to the podcast Vish Reddy?

Vish Reddy:

Thank you.

Vish Reddy:

Uh, very nice to be here.

W. Curtis Preston:

sort, sort of be here.

W. Curtis Preston:

What, what time is it over there right now

Sanket Parlikar:

It's like 9 45, 9 50

W. Curtis Preston:

in the evening?

Sanket Parlikar:

Yep.

W. Curtis Preston:

Okay, well, thanks very much for, for joining us to talk about

W. Curtis Preston:

backups at basically 10 o'clock at night.

W. Curtis Preston:

I know I do that a lot, but usually I'm just talking to myself at

Prasanna Malaiyandi:

Socks like this is just me getting started for the evening.

W. Curtis Preston:

I remember it's interesting.

W. Curtis Preston:

I remember 10 o'clock for me, like historically in my career, 10 o'clock

W. Curtis Preston:

was when I was doing backups, like for people, like 10 o'clock for

W. Curtis Preston:

some reason was the time that a lot of them seemed to kick off.

W. Curtis Preston:

So this was like the beginning of the night for, you know, for

W. Curtis Preston:

a lot of, for a lot of time.

W. Curtis Preston:

But, uh, so anyway, so thanks for both of you coming on here.

W. Curtis Preston:

We're we're here to talk about.

W. Curtis Preston:

A new company, which you two, uh co-founded, which is called.

W. Curtis Preston:

I make sure I, I have pronounced it correctly.

W. Curtis Preston:

I'm assuming it is Revyz.

W. Curtis Preston:

Did I, did I get that correct?

Sanket Parlikar:

Yes, that's right.

W. Curtis Preston:

Okay.

Prasanna Malaiyandi:

But it's an interesting spelling.

Prasanna Malaiyandi:

So if you go to look

W. Curtis Preston:

Yeah, it is.

W. Curtis Preston:

Yeah.

W. Curtis Preston:

It is an interesting spelling, which is, which is, which is why I wasn't

W. Curtis Preston:

sure if I was pronouncing it correctly.

W. Curtis Preston:

It's R E V Y z.io as the website.

W. Curtis Preston:

Um, so why don't we sort of start at the, and, and by the way, I, you

W. Curtis Preston:

know, I've already brought up Druva, uh, that's where I happen to work.

W. Curtis Preston:

Uh, I'll throw out our standard disclaimer.

W. Curtis Preston:

Our standard disclaimer, Prasanna works at zoom.

W. Curtis Preston:

I work at Druva.

W. Curtis Preston:

This is not a podcast of either company.

W. Curtis Preston:

The opinions that you hear are ours and, um, be sure to rate us at your

W. Curtis Preston:

favorite podcaster, just give us stars, give us, and we really love comments.

W. Curtis Preston:

And currently there's an offering on the play.

W. Curtis Preston:

You guys didn't even know this, but apparently if we.

W. Curtis Preston:

Nine new comments on apple, on iTunes.

W. Curtis Preston:

Um, you know, in the next week or two, then apparently I have to grow a

Prasanna Malaiyandi:

was, it was a month.

Prasanna Malaiyandi:

We said

W. Curtis Preston:

Oh, that, oh, was it a month?

W. Curtis Preston:

It was a month from the last episode.

W. Curtis Preston:

Right?

Prasanna Malaiyandi:

went

W. Curtis Preston:

Right.

W. Curtis Preston:

So, uh, if we get nine new comments on apple iTunes, then I have

W. Curtis Preston:

to grow a beard for Christmas.

W. Curtis Preston:

Which, you know, I mean, it will still not look as full as Prasannas cuz it's

W. Curtis Preston:

currently a, theard, is it a theard now?

Prasanna Malaiyandi:

Speaker:

uh, not quite a theard.

Prasanna Malaiyandi:

Speaker:

It's still a tweard.

Prasanna Malaiyandi:

Speaker:

It's like a and a.

W. Curtis Preston:

A two and a half year.

W. Curtis Preston:

That's not, that doesn't make any sense.

W. Curtis Preston:

Yeah.

W. Curtis Preston:

Uh, but yeah, cuz I, I, I, you know, I've really never grown a, a real

W. Curtis Preston:

beard and anyway, so there you go.

W. Curtis Preston:

So rate, you know, gives some comments and um, also if you wanna join in the

W. Curtis Preston:

conversation, we'd love to have you.

W. Curtis Preston:

So, if you like the topics that we talk about, backup security, privacy, uh, you

W. Curtis Preston:

know, ransomware, all of those things.

W. Curtis Preston:

And, uh, then please just, uh, reach out to me at Twitter @wcpreston

W. Curtis Preston:

or w Curtis Preston at Gmail.

W. Curtis Preston:

So let's go back to the beginning.

W. Curtis Preston:

What made you wanna do this crazy thing of, of founding a company?

W. Curtis Preston:

Well, I'll, I'll start with Vish here.

W. Curtis Preston:

Um, you know what, you know, what, what problem was out there that you said?

W. Curtis Preston:

I, I think I can solve this problem.

Vish Reddy:

Uh, Curtis having met multiple customers at Druva having worked there.

Vish Reddy:

One of the things

W. Curtis Preston:

Mm-hmm

Vish Reddy:

applications, companies were deployed were reciting the cloud.

Vish Reddy:

You know, the cloud vendor, again, no fault of the cloud

Vish Reddy:

vendor, uh, you know, the cloud vendor would always say, Hey, Mr.

Vish Reddy:

Customer, it is your responsibility to secure your data, which

Vish Reddy:

is, which makes sense.

Vish Reddy:

Right?

Vish Reddy:

I mean, if a user and delete their data accidentally, you, you can't hold the

Vish Reddy:

cloud vendor to be responsible for that.

W. Curtis Preston:

Well, can I interject on you there?

W. Curtis Preston:

Um, I mean, you're telling your backstory, but I, I just have to interject there.

W. Curtis Preston:

I would love it.

W. Curtis Preston:

If the cloud vendors would say that.

W. Curtis Preston:

Right.

W. Curtis Preston:

I would love it.

W. Curtis Preston:

If the cloud vendors would make it very clear whose responsibility

W. Curtis Preston:

it is to protect the data UN unfortunately many of them don't right.

W. Curtis Preston:

They, they, they either, they either just don't talk about it.

W. Curtis Preston:

Um, You, you know that that's probably, that's probably the worst to me is it is

W. Curtis Preston:

if they say nothing, it it's not in their service contract, it's not in their SLAs.

W. Curtis Preston:

And, and yet they may have legions of fans and, and, and I'm gonna, I'm gonna call

W. Curtis Preston:

out Microsoft as being the worst offender here, because they have legions of fans

W. Curtis Preston:

who say, you do not need to back this up.

W. Curtis Preston:

They have not publicly clarified.

W. Curtis Preston:

They have a few things hit, you know, hidden here and there, but there is no.

W. Curtis Preston:

You know, um, public statement.

W. Curtis Preston:

So, you know, on the, on the reverse of that, I would

W. Curtis Preston:

give, I would put Salesforce.

W. Curtis Preston:

They, they, you know, not only have they clarified what your

W. Curtis Preston:

responsibilities are, they now offer their own service to back up.

W. Curtis Preston:

Um, and then somewhere in the middle is, is, you know, 4,000

W. Curtis Preston:

other SaaS vendors out there.

W. Curtis Preston:

Right.

W. Curtis Preston:

Um, but yeah, so.

W. Curtis Preston:

Uh, let's come back to that.

W. Curtis Preston:

I wanna, I wanna come back to that.

W. Curtis Preston:

I want you to finish sort of your story, but I wanna come back to this topic.

W. Curtis Preston:

Uh, anyway, sorry.

W. Curtis Preston:

I was just, it's a hobby horse.

W. Curtis Preston:

I just had to jump on.

W. Curtis Preston:

So.

Vish Reddy:

Yeah.

Vish Reddy:

So, you know, that led us to saying, okay, this is a problem.

Vish Reddy:

Lot of, to your point.

Vish Reddy:

Lot of customers don't know that, uh, there is, uh, in fact,

Vish Reddy:

uh, I'll come back to a story.

Vish Reddy:

One of the first.

Vish Reddy:

Uh, you know, prospects or validators who we met had the

Vish Reddy:

exact same point as you, right?

Vish Reddy:

You said, why do we need to back?

Vish Reddy:

You know, the vendor is providing the service.

Vish Reddy:

I'll get into the details in a bit of that, but that was the Genesis of saying,

Vish Reddy:

okay, you know, there is a problem.

Vish Reddy:

When we looked into some of the more popular, um, DevOps focus,

Vish Reddy:

we were more focused on DevOps.

Vish Reddy:

You obviously, you mentioned office 365 Salesforce.

Vish Reddy:

There's a good ecosystem of vendors there.

Vish Reddy:

So we said the things people are looking at, which critical for the functioning

Vish Reddy:

of that business, uh, is important.

Vish Reddy:

Um, Workday servicenow.

Vish Reddy:

And there's a growing list of, uh, applications, which are out there.

Vish Reddy:

And we said, okay, can we build an architecture?

Vish Reddy:

Which is, which can, you know, help protect that data?

Vish Reddy:

Can we have a generic architecture, which can, where we can plug in any of these

Vish Reddy:

different applications and we can help simplify the job of the administrator.

Vish Reddy:

So that's where we got started.

Vish Reddy:

Uh, that was the Genesis when we recognized this,

Vish Reddy:

that there's this problem.

Vish Reddy:

Uh, we said, okay, you know, again, backup as you guys are more familiar,

Vish Reddy:

this is one of the basic functions, which it administrator performs now.

Vish Reddy:

Unfortunately,

Vish Reddy:

Now, there are some people who spent hours together just started to do this.

Vish Reddy:

And he said, that's not, that's not in today's day and age.

Vish Reddy:

You should not be spending a lot of time doing this.

Vish Reddy:

This should be just offloaded.

Vish Reddy:

Should be at the end of the day.

Vish Reddy:

I dunno whether you guys agree with me or not.

Vish Reddy:

Backup is like insurance, you need it some point of time, but you never

Vish Reddy:

know when you need health insurance.

W. Curtis Preston:

Yeah.

W. Curtis Preston:

It's, it's exactly like insurance in that.

W. Curtis Preston:

You must buy it before you need it.

W. Curtis Preston:

you, you can't get car insurance after you've had an accident.

W. Curtis Preston:

It's exactly like insurance in that same way.

Vish Reddy:

Yeah.

Vish Reddy:

So just to continue the story.

Vish Reddy:

Oh, um, uh, you know, Sankit and I used to work together.

Vish Reddy:

Um, and, uh, we would exchange every so often we would exchange some ideas

Vish Reddy:

and say, oh, maybe we should do this.

Vish Reddy:

We should do that.

Vish Reddy:

And then I shared with him this idea, oh, why don't we?

Vish Reddy:

Well, you know, there is a problem out here.

Vish Reddy:

I've talked to a couple people and.

Vish Reddy:

know, they're outlined that there's don't solve.

Sanket Parlikar:

Oh, yeah, it was a, a really.

Sanket Parlikar:

Journey, right.

Sanket Parlikar:

Uh, since beginning like, uh, inception itself, uh, exchanging ideas, talking to

Sanket Parlikar:

different people, trying to understand what is a real problem, uh, out there.

Sanket Parlikar:

Right?

Sanket Parlikar:

Uh, luckily, uh, I had a lot of, uh, admin friends, uh, who were managing

Sanket Parlikar:

different applications, uh, and then, uh, wish, uh, had different

Sanket Parlikar:

connections and all the people.

Sanket Parlikar:

Talk to, uh, basically they said, wow, that's amazing idea.

Sanket Parlikar:

Right?

Sanket Parlikar:

Uh, I do have a lot of critical data sitting into, uh, these, uh, DevOps tools.

Sanket Parlikar:

And specifically, if you talk about Atlassian, it's again, uh,

Sanket Parlikar:

pretty sensitive data for me.

Sanket Parlikar:

Why don't you help me, uh, back that up today?

Sanket Parlikar:

I have a problem, but I cannot predict that.

Sanket Parlikar:

Uh, there are a lot of challenges, so exchanging a lot of ideas,

Sanket Parlikar:

talking to a lot of people.

Sanket Parlikar:

Uh, that's how the journey, uh, started and then slowly validating that idea,

Sanket Parlikar:

validating that problem out there and then, uh, finding a solution for it.

Sanket Parlikar:

That's how it all started.

Prasanna Malaiyandi:

Yeah, it's great that you actually have like real

Prasanna Malaiyandi:

world customers who have this problem.

Prasanna Malaiyandi:

Right.

Prasanna Malaiyandi:

A lot of times.

Prasanna Malaiyandi:

You're like, oh, I have this idea.

Prasanna Malaiyandi:

Let me try to find a good market fit for this.

Prasanna Malaiyandi:

Right.

Prasanna Malaiyandi:

And it's like, you're struggling.

Prasanna Malaiyandi:

But actually having a problem that people are struggling with is like,

Prasanna Malaiyandi:

gets you so much further ahead.

Prasanna Malaiyandi:

The one thing, uh, and I don't know, Sanket or Vish who wants to

Prasanna Malaiyandi:

answer this is maybe Sanket is, I know you mentioned Atlassian.

Prasanna Malaiyandi:

A lot of our listeners may not know what Atlassian is or who they are.

Prasanna Malaiyandi:

Could you maybe give sort of a brief background about some of the

Prasanna Malaiyandi:

products, um, that they might offer that people might be more familiar?

Sanket Parlikar:

Absolutely.

Sanket Parlikar:

So in general, uh, let's talk about software industry, right?

Sanket Parlikar:

Uh, in software industry, typically, uh, developers need a

Sanket Parlikar:

system to track their work, right?

Sanket Parlikar:

Uh, they are developing the software.

Sanket Parlikar:

They would be logging in, uh, certain tickets to track, uh,

Sanket Parlikar:

track their tasks and work, uh, and how they, uh, develop a software.

Sanket Parlikar:

Right.

Sanket Parlikar:

So typically, uh, what, uh, This software is, uh, is going to do for developers

Sanket Parlikar:

is, is going to create tickets.

Sanket Parlikar:

It's going to manage all their work, their work log, and

Sanket Parlikar:

then build reports out of it.

Sanket Parlikar:

That's how, uh, the engineering function, uh, tracks their efforts

Sanket Parlikar:

right now, Atlassian as a company, what they do is they focus on,

Sanket Parlikar:

uh, uh, creating a software.

Sanket Parlikar:

Does that job for engineering function.

Sanket Parlikar:

And one of their application is called S JIRA software, uh, which will,

Sanket Parlikar:

uh, give that functionality to the engineering, uh, group, uh, wherein

Sanket Parlikar:

they can create different tickets, uh, log in their daily tasks and track

Sanket Parlikar:

it as, as they make the progress.

Sanket Parlikar:

So that's the JIRA software.

Sanket Parlikar:

There's another application, for example, which is called as

Sanket Parlikar:

a confluence wherein you can go ahead, create your documentation,

Sanket Parlikar:

be your internal documentation.

Sanket Parlikar:

Be it your customer facing documentation.

Sanket Parlikar:

You create all the documentation and then use it for different purposes.

Sanket Parlikar:

So that's what Atlassian does at pretty high level.

Prasanna Malaiyandi:

So it's basically building all the tools you need rather

Prasanna Malaiyandi:

than developers having to spend time focused on how do I track what's

Prasanna Malaiyandi:

going on in spreadsheets or in like documents, writing out things, right.

Prasanna Malaiyandi:

It's all easily available.

Prasanna Malaiyandi:

So people have business.

Prasanna Malaiyandi:

Gotcha.

Prasanna Malaiyandi:

Across the

W. Curtis Preston:

So this was a, this is a tool that you were obviously

W. Curtis Preston:

familiar with in your various, you know, basically doing your regular job.

Sanket Parlikar:

Exactly.

Sanket Parlikar:

And, and I just gave you one example of software industry, right?

Sanket Parlikar:

Uh, because all of us come from software background or a product

Sanket Parlikar:

background, but when we connected with different, uh, people, different

Sanket Parlikar:

customers, uh, we discovered that it's not only limited to software industry.

Sanket Parlikar:

Ticketing system in general is applicable to almost every industry.

Sanket Parlikar:

We went to healthcare people, they're using ticketing system.

Sanket Parlikar:

We went to automobile industry people.

Sanket Parlikar:

They're using ticketing system in one way or the other.

Sanket Parlikar:

Right.

Sanket Parlikar:

So this is not limited to one specific software industry,

Sanket Parlikar:

but it's applicable everywhere.

Sanket Parlikar:

Right.

Sanket Parlikar:

And yeah, people may use different tools, but the problem

Sanket Parlikar:

is still, uh, pretty generic.

W. Curtis Preston:

Right, right.

W. Curtis Preston:

A and so you talked about Vish, you talked about, um, wanting to

W. Curtis Preston:

develop a generic architecture.

W. Curtis Preston:

And I'd say that's probably the biggest challenge that you, that you have

W. Curtis Preston:

is that you, when you're developing a backup tool, that's gonna back up

W. Curtis Preston:

so many different types of things.

W. Curtis Preston:

Um, you know, how do, how do you develop a, an architecture that you think

W. Curtis Preston:

will serve multiple tools like that?

Vish Reddy:

Right.

Vish Reddy:

I think that's the, you're absolutely right.

Vish Reddy:

That's the, the biggest challenge we have and I think we've made significant

Vish Reddy:

progress in addressing the challenge.

Vish Reddy:

I'm not saying that, you know, we've completely solved that problem.

Vish Reddy:

Uh, at this point of time, uh, you know, we started off with Atlassian

Vish Reddy:

Atlassian, as Kate mentioned, is got JIRA confluence, JIRA service management.

Vish Reddy:

It's got a bunch of tools in itself.

Vish Reddy:

Uh, we're sort of focusing on that, uh, uh, you know, challenge, so to speak.

Vish Reddy:

Uh, and then, you know, we're hoping that the architecture have built out

Vish Reddy:

is gonna help us scale to others.

Vish Reddy:

JIRA while you know, ticketing system, it seems simple.

Vish Reddy:

You have a ticket, you have a user who's submitting a ticket.

Vish Reddy:

How, how complicated could that be?

Vish Reddy:

Right.

Vish Reddy:

That's what would all think?

Vish Reddy:

But then once you look inside, if you look the, the database

Vish Reddy:

scheme for that, oh my God.

Vish Reddy:

That the first time I saw this, it was, it was a spaghetti bowl

Vish Reddy:

of like, you know, multiple tables interconnected with each other.

W. Curtis Preston:

I for the record, I would describe that as the

W. Curtis Preston:

JIRA user experience as well, but that's but that's, that's just me.

Vish Reddy:

Right.

Vish Reddy:

So I think, you know, uh, the proof in, uh, using the product and seeing how far

Vish Reddy:

we'll come, uh, come along now, one thing which I wanna also, uh, highlight here.

Vish Reddy:

So we, couple of prospects, we validated that idea.

Vish Reddy:

We actually went and pitched this to at.

Vish Reddy:

They said, Hey, you know, we not seeing anybody building something

Vish Reddy:

like this in your ecosystem.

Vish Reddy:

We think that this is critical.

Vish Reddy:

Uh, is this what you guys and you know that between sun and

Vish Reddy:

ICS would, we had had in 30 minutes, uh, the people who we're talking to.

Vish Reddy:

Recognize that this is a good problem to solve for them.

Vish Reddy:

And they were like, yeah, you know, if you guys are willing to put in your efforts

Vish Reddy:

and solve this problem for us, we'll, uh, you know, back you or we'll fund you

Vish Reddy:

some amount of seed money to get started.

Vish Reddy:

And not only that, they connected us back to their engineering team,

Vish Reddy:

the same team, which is developed that complicated, which is there.

Vish Reddy:

And, uh, we're working very closely with them in, you know, uh,

Vish Reddy:

building more APIs, which will help.

Vish Reddy:

Um, you know, backup and restore data in a, in a much cleaner way.

Vish Reddy:

Uh, they do have good APIs, but those APIs are not built, uh,

Vish Reddy:

keeping backup and restored in mind.

Vish Reddy:

Um, but they are working towards getting those new APIs out, uh, soon.

Prasanna Malaiyandi:

Yeah.

Prasanna Malaiyandi:

And I think that's one of the keys is a lot of the vendors, right.

Prasanna Malaiyandi:

They try to stay agnostic and they're like, Hey, here are the APIs.

Prasanna Malaiyandi:

You go try to build your backup app or whatever app on top of it.

Prasanna Malaiyandi:

I think the fact that you guys are actually getting engagement from the

Prasanna Malaiyandi:

engineering team to be like, Hey.

Prasanna Malaiyandi:

This is really what it takes and probably also imparting that wisdom

Prasanna Malaiyandi:

on, Hey, these are the requirements from a backup or a restore perspective,

Prasanna Malaiyandi:

cuz that's also the other challenges.

Prasanna Malaiyandi:

Usually in like SaaS services, your restores aren't very expansive, right?

Prasanna Malaiyandi:

The options you provide, it's normally like, yeah, I'm just

Prasanna Malaiyandi:

gonna restore everything.

Prasanna Malaiyandi:

But very rarely do you have the ability to say restore a smaller object?

Prasanna Malaiyandi:

Unless they're really focused on thinking about that.

Prasanna Malaiyandi:

Because typically as an engineer, you build features, you build

Prasanna Malaiyandi:

product, you don't always think about backup and restore data protection

Prasanna Malaiyandi:

when you're building these things.

W. Curtis Preston:

Well, I do, but, um,

Prasanna Malaiyandi:

and I know vision Sune do, but I'm

Prasanna Malaiyandi:

just saying most people don't

W. Curtis Preston:

no, I know what you, yeah.

W. Curtis Preston:

Yeah.

W. Curtis Preston:

I, I, and, and by the way, I, you know, I'll, I'll give credit to Atlassian

W. Curtis Preston:

because again, I'm gonna contrast to my favorite punching bag, uh, Microsoft.

W. Curtis Preston:

Right?

W. Curtis Preston:

They don't, they, they didn't have APIs for backup, right?

W. Curtis Preston:

The only way that you got, um, that we were, you know, that Druva and

W. Curtis Preston:

other companies were able to back up is basically use outlook web access.

W. Curtis Preston:

Right.

W. Curtis Preston:

Um, and, and you use an API that was completely meant for meant for

W. Curtis Preston:

something completely different.

W. Curtis Preston:

And you're using it for backup.

W. Curtis Preston:

I think now.

W. Curtis Preston:

For various reasons.

W. Curtis Preston:

My understanding is that Microsoft has come out with

W. Curtis Preston:

some, some new APIs, uh, but,

Prasanna Malaiyandi:

Not for everything though.

W. Curtis Preston:

Yeah.

W. Curtis Preston:

But not for everything.

W. Curtis Preston:

But yeah.

W. Curtis Preston:

So, so, so hats off to Atlassian for giving you, you know, first, first

W. Curtis Preston:

off, acknowledging that this is a problem that needs to be solved.

W. Curtis Preston:

And, uh, and then giving you access to the APIs and to the, and to the engineers.

W. Curtis Preston:

That's great.

Prasanna Malaiyandi:

I was going to jump back, actually, a couple of questions.

Prasanna Malaiyandi:

Um, I know sanket, you talked about Atlassian, what they do.

Prasanna Malaiyandi:

Um, I'm sure a lot of folks are asking though, why is a JIRA

Prasanna Malaiyandi:

system or a confluence system?

Prasanna Malaiyandi:

Like, why do I even need to back that up?

Prasanna Malaiyandi:

Right.

Prasanna Malaiyandi:

It's just, oh, I created some things.

Prasanna Malaiyandi:

These are all closed tickets.

Prasanna Malaiyandi:

Right?

Prasanna Malaiyandi:

Why do I even need to back up this old data?

Sanket Parlikar:

Good question.

Sanket Parlikar:

So I will just go back to my previous example, software industry right

Sanket Parlikar:

now, engineering is working on a life project, for example, right.

Sanket Parlikar:

Uh, typically what they do is, uh, they try to put in, uh, all

Sanket Parlikar:

the, uh, comments and all the, uh, data, what they're working on.

Sanket Parlikar:

In in, into that ticket.

Sanket Parlikar:

Right.

Sanket Parlikar:

And a lot of the times, even the, uh, version control system, uh,

Sanket Parlikar:

which is like bit bucket GitHub, it's linked with your, uh, JIRA.

Sanket Parlikar:

So now all the commits are being tracked in a ticket.

Sanket Parlikar:

Now, if that data is lost, the tickets, uh, present in JIRA, if those

Sanket Parlikar:

are lost, for some reason you lose that visibility of what happened.

Sanket Parlikar:

Yes.

Sanket Parlikar:

Uh, you have to, uh, go back, dig in, uh, put in more efforts to

Sanket Parlikar:

understand what happened, right?

Sanket Parlikar:

But your productivity is impacted.

Sanket Parlikar:

Your ongoing activity of, uh, whatever, uh, ongoing sprint or

Sanket Parlikar:

whatever it is it's impacted.

Sanket Parlikar:

It's a direct business impact.

Sanket Parlikar:

So that's one of the reasons why you need to protect that data and make sure

Sanket Parlikar:

you can roll back as soon as possible.

Sanket Parlikar:

Right?

Sanket Parlikar:

Another impact is basically the reporting structure.

Sanket Parlikar:

Lot of big teams, they rely on JIRA to, uh, understand what is

Sanket Parlikar:

going on within their scrum teams.

Sanket Parlikar:

So that's very critical.

Sanket Parlikar:

Right now that's one example.

Sanket Parlikar:

The other example is lot of, uh, customers, they

Sanket Parlikar:

leverage, uh, JIRA software.

Sanket Parlikar:

They leverage JIRA service management tool for their HR function, uh, for different,

Sanket Parlikar:

uh, uh, functions like HR finance.

Sanket Parlikar:

They also leverage Atlassian apps wherein they store sensitive information.

Sanket Parlikar:

For example, what we have seen is HR teams.

Sanket Parlikar:

They onboard, uh, different, uh, employees, uh, in, in,

Sanket Parlikar:

uh, Jira itself, right.

Sanket Parlikar:

Or JSM, they, uh, conduct interviews and they store certain, uh, amount

Sanket Parlikar:

of data employee data into, uh, the JIRA software and JSM tools.

Sanket Parlikar:

Right.

Sanket Parlikar:

So that is even more, uh, sensitive data.

Sanket Parlikar:

And, um, Very impactful for your business, if it it's lost.

Sanket Parlikar:

Uh, so there are multiple angles to it.

Sanket Parlikar:

Not only, uh, the, uh, business continuity part of it, but also

Sanket Parlikar:

how sensitive data, uh, uh, is, is being stored into these systems.

Sanket Parlikar:

And what if that data is lost?

Sanket Parlikar:

Right?

Sanket Parlikar:

So there are different, uh, angles to it.

W. Curtis Preston:

so let me ask this question.

W. Curtis Preston:

So Atlassian obviously has a big business already.

W. Curtis Preston:

Um, and they have a lot of customers.

W. Curtis Preston:

Certainly some customers have said, gee, I, I, I agree with

W. Curtis Preston:

everything that you just said.

W. Curtis Preston:

What would an Atlassian customer do today?

W. Curtis Preston:

If they wanted to get any kind of backup of that?

W. Curtis Preston:

I'll, I'll give that to, to.

Vish Reddy:

Yeah today.

Vish Reddy:

Um, so, uh, let back up a little bit, which is Atlassian offers

Vish Reddy:

their products in two deployment, uh, modes, um, on premises.

Vish Reddy:

And cloud, uh, of course they came out their on premises product, you know, they.

Vish Reddy:

most customers when they, uh, who are very, uh, you know, sensitive about their

Vish Reddy:

data backups and so on for on premises systems, they would back up the database.

Vish Reddy:

Uh, typically it's a, MySQL, or a Postgress database.

Vish Reddy:

I think you have choices.

Vish Reddy:

So on premises systems, you would back up their database itself, but

Vish Reddy:

still the problem remains, I think, as you were pointing out, right.

Vish Reddy:

You typically go mess up with one or two things.

Vish Reddy:

You, you know, you don't typically blow up your entire site most of the time.

Vish Reddy:

Uh, now the problem with that, you know, backing up your databases, you do have

Vish Reddy:

point time snapshots of your database.

Vish Reddy:

So if you don't roll that back then you do all the work, which

Vish Reddy:

you've done from the point of time, you know, you roll back to right.

Vish Reddy:

OK.

Vish Reddy:

So that that's the current state of affairs on the,

Vish Reddy:

on premises side of things.

Vish Reddy:

On the cloud what Atlassian provided was a mechanism to do a database export.

Vish Reddy:

Uh, so in their UI today, most customers try to go and press pressing that button.

Vish Reddy:

Unfortunately, that takes a very long time.

Vish Reddy:

Again, depends on your size of your data, uh, your, your tenant, right?

Vish Reddy:

How much of data which you have, uh, if you have a couple of, um, you

Vish Reddy:

know, let's, let's go with gigabytes.

Vish Reddy:

Let's say you have 10 gigabytes of data.

Vish Reddy:

Uh, tickets, attachments, whatnot.

Vish Reddy:

That's gonna take you some time to, uh, back up.

Vish Reddy:

Now, here's the thing, which is really messed up in my,

Vish Reddy:

uh, there's a cloud product.

Vish Reddy:

You gotta take that backup.

Vish Reddy:

You gotta download that your on premises system, and then

Vish Reddy:

you decide what to do with it.

Vish Reddy:

You can put it back into the cloud and, you know, manage different versions.

Vish Reddy:

Um, or you can put it on a, on premises system and manage that.

Vish Reddy:

Right.

Vish Reddy:

But here again, if you wanna go,

W. Curtis Preston:

Is there a way to restore it to the cloud.

Vish Reddy:

yes, you can restore it to the cloud again.

Vish Reddy:

It's all or nothing.

Vish Reddy:

So if you wanna go back, let's say a month, that means

Vish Reddy:

you've lost a month's of data.

Vish Reddy:

It's not, you know, , it's not like I want this one ticket

Vish Reddy:

or two tickets or this attach.

Vish Reddy:

Um, and it's a lot of manual work by the way.

Vish Reddy:

Um, in the current state of affairs, if your data size is greater than

Vish Reddy:

five gigs compressed, uh, then you gotta go and, uh, you know, open that

Vish Reddy:

file up, split it up into multiple parts and then try uploading.

Vish Reddy:

Uh, so there is a lot of work which you would have to do,

W. Curtis Preston:

Hmm,

Vish Reddy:

and this is.

Prasanna Malaiyandi:

It reminds me of like Salesforce backup and restores.

Prasanna Malaiyandi:

I know

W. Curtis Preston:

It does.

W. Curtis Preston:

Yeah.

Prasanna Malaiyandi:

on right talking about that and just trying to deal with

Prasanna Malaiyandi:

that seems like a bit of a nightmare vish

Vish Reddy:

Actually, I would say, you know, uh, one of our first, uh, prospects.

Vish Reddy:

They're in the travel industry, uh, very different, they're not software.

Vish Reddy:

Uh, they would, uh, log, uh, customer issues, changes to the travel

Vish Reddy:

schedule and so on and in JIRA.

Vish Reddy:

And, uh, they were doing this manually and they were looking

Vish Reddy:

for a solution like, every two.

Vish Reddy:

Hello.

Vish Reddy:

And so they're like, oh, there's too much manual work.

Vish Reddy:

It takes at least five to six hours to just download the data

Vish Reddy:

and then you gotta manage it.

Vish Reddy:

I don't wanna do this.

Vish Reddy:

Can I just offload this to.

Vish Reddy:

Um, I think that was the inspiration.

Vish Reddy:

I would say that was one of the, you know, stories.

Vish Reddy:

I was gonna tell you as to how we said, okay, maybe there's a good problem to go.

W. Curtis Preston:

And so the, the, the worry, like, again, going to

W. Curtis Preston:

your, your travel example, the, the worry would be that you accidentally

W. Curtis Preston:

delete like just a customer.

W. Curtis Preston:

You know, you, you just deleted all history for a customer that you've been

W. Curtis Preston:

managing travel for five years, and then you just deleted that customer.

W. Curtis Preston:

Your only choice as you were saying is to restore the entire database.

W. Curtis Preston:

You can't restore just that customer, right?

Vish Reddy:

That's correct.

Vish Reddy:

Uh, there is no, you know, pick and choose you it's all or nothing.

Vish Reddy:

Um, one other thing, which is, uh, you important for, uh, to, and lot of people

Vish Reddy:

don't this, uh, which is when you delete something in, in JIRA or confluence.

Vish Reddy:

It is gone.

Vish Reddy:

You cannot get it back.

Vish Reddy:

There is no audit trail for that.

W. Curtis Preston:

Really none.

Vish Reddy:

I I'll give you another example.

W. Curtis Preston:

a recycled bin or anything.

Vish Reddy:

okay.

Vish Reddy:

So there are, there is a recycled bin.

Vish Reddy:

If you delete things at a project level, but if you delete things at the

Vish Reddy:

ticket level, there is no recycle bin.

Vish Reddy:

There is no audit log for it.

Vish Reddy:

Last year, I was working for, again, this was another data point,

Vish Reddy:

which we had, I was working for Agari data, uh, email security.

Vish Reddy:

We got acquired by a company called help systems.

Vish Reddy:

And there were a lot of upset employees at Agari who did not

Vish Reddy:

like, you know, what was going on.

Vish Reddy:

And.

Vish Reddy:

I, we would use JIRA for our, uh, software development, project management and so on.

Vish Reddy:

I started noticing tickets disappearing, and I'm like, I'm pretty sure I saw this.

Vish Reddy:

I can see AGA 129.

Vish Reddy:

I saw it yesterday, but it's not there in the system.

Vish Reddy:

Where did it go?

Vish Reddy:

I go asking around and nobody knows because there is no trace of it anymore.

W. Curtis Preston:

Wow.

W. Curtis Preston:

That's not good.

Vish Reddy:

And that is the state of affairs today.

W. Curtis Preston:

Right.

W. Curtis Preston:

Wow.

Sanket Parlikar:

So if, if I may add right, uh, Curtis, uh, how, how,

Sanket Parlikar:

uh, Backup and restore really works.

Sanket Parlikar:

Uh, 10 years ago or 20 years ago when you started, right?

Sanket Parlikar:

Uh, the focus used to be on disaster recovery.

Sanket Parlikar:

Uh, 30 years, about 20 years ago, it was all about disaster recovery.

Sanket Parlikar:

Meaning my system is up and running OnPrem system.

Sanket Parlikar:

Something goes, uh, bad.

Sanket Parlikar:

I just rolled back, uh, probably, uh, five days older, a snapshot things work.

Sanket Parlikar:

Right.

Sanket Parlikar:

And I'm okay to give up some of the data now, uh, Uh, with cloud apps,

Sanket Parlikar:

basically the situation is like, Hey, I'm not ready to give up all of my data.

Sanket Parlikar:

Uh, I just want to, uh, pick, choose what I want to restore.

Sanket Parlikar:

Right.

Sanket Parlikar:

Uh, because, uh, yeah, there are a number of reasons.

Sanket Parlikar:

I, I, uh, accidentally deleted something, right.

Sanket Parlikar:

Uh, why do I roll back, uh, entire tenant?

Sanket Parlikar:

I, uh, I had a malicious incident where in someone.

Sanket Parlikar:

Deleted only subset of data.

Sanket Parlikar:

Why do I roll back completely?

Sanket Parlikar:

Right.

Sanket Parlikar:

So these are the evolving scenarios.

Sanket Parlikar:

Now, malicious actors being the biggest one.

Sanket Parlikar:

As we talk about security, that's the biggest threat evolving for any SaaS app.

W. Curtis Preston:

Yeah, I, I, we actually had a discussion on the

W. Curtis Preston:

previous, uh, podcast that, you know, I, I just sort of had this realization

W. Curtis Preston:

that, you know, when I started, uh, which for the record was 30 years ago.

W. Curtis Preston:

when I

Prasanna Malaiyandi:

Speaker:

was being kind to you.

W. Curtis Preston:

But what I started, the, the, I will agree that the

W. Curtis Preston:

primary thing that we were trying to solve was hardware failure.

W. Curtis Preston:

Right.

W. Curtis Preston:

Whether it was, it failed because of a disaster or failed because we were running

W. Curtis Preston:

servers on a single hard drive, right?

W. Curtis Preston:

No raid, no, nothing, just a hard drive.

W. Curtis Preston:

And, um, I mean, if there were multiple hard drives, we were just using all of

W. Curtis Preston:

them as individual drives, but, and, and, and between the, the, the, um, the

W. Curtis Preston:

change in the technology with everybody using, uh, raid and things like that.

W. Curtis Preston:

And the change in SaaS providers, Dr.

W. Curtis Preston:

Is not my problem, right.

W. Curtis Preston:

With Atlassian with, with JIRA, Dr.

W. Curtis Preston:

Is not my problem.

W. Curtis Preston:

That's their problem that we all agree that it is their problem to

W. Curtis Preston:

get the service up and running.

W. Curtis Preston:

That is what I'm paying them for.

W. Curtis Preston:

But.

W. Curtis Preston:

Due to the, to the change in, in the way technology has, has

W. Curtis Preston:

evolved the number one reason.

W. Curtis Preston:

In fact, I, I would argue that like it's like 99.9%.

W. Curtis Preston:

The number one reason for a restore is now humans, not hardware.

W. Curtis Preston:

And Dr.

W. Curtis Preston:

Uh, I mean, it's still, there are still disasters, but the

W. Curtis Preston:

disasters are caused by humans.

W. Curtis Preston:

They are they're caused by.

W. Curtis Preston:

Um, you know, ransomware attacks and other malicious attacks,

W. Curtis Preston:

like what Vish was talking about.

W. Curtis Preston:

So I would, I don't know if this was the point you were making, but I'll

W. Curtis Preston:

make it if you weren't making it and I'll agree if you were making it.

W. Curtis Preston:

And that is that.

W. Curtis Preston:

You have, if you're designing a backup product for this world, you have to

W. Curtis Preston:

design it with that, um, in mind, right?

W. Curtis Preston:

Since the primary reason that we're going to be doing restores is dumb stuff.

W. Curtis Preston:

right.

W. Curtis Preston:

We need to make the restore of dumb stuff.

W. Curtis Preston:

Uh, the, the easiest thing that the product can do.

W. Curtis Preston:

Did did I say the same thing you said, but in a whole lot more words.

Sanket Parlikar:

Exactly.

W. Curtis Preston:

Okay.

Prasanna Malaiyandi:

Speaker:

Curtis does that a lot

W. Curtis Preston:

I've literally made a career of doing just that.

W. Curtis Preston:

Um, so, so the, the companies knew, in fact, I, my understanding is that,

W. Curtis Preston:

you know, you're, you're, you're just now launching what, are you

W. Curtis Preston:

handling all of Atlassian products?

W. Curtis Preston:

I'll give that to Vish.

Vish Reddy:

we got started in April, uh, for five months in roughly

Vish Reddy:

speaking, um, version one or MVP is gonna be covering JIRA Software.

Vish Reddy:

Um, and then we have a robust roadmap, uh, I think next would be Jira SM, Confluence.

Vish Reddy:

SM

Prasanna Malaiyandi:

For your MVP or version one?

Prasanna Malaiyandi:

Could you talk a little bit?

Prasanna Malaiyandi:

I'm definitely sure you're doing the backups.

Prasanna Malaiyandi:

What about from the restores?

Prasanna Malaiyandi:

I know earlier you talked about today with what you get with, uh, JIRA

Prasanna Malaiyandi:

today or Atlassian today, it's sort of, you get everything as a backup

Prasanna Malaiyandi:

once every two days at most, right?

Prasanna Malaiyandi:

And then you have to restore everything back.

Prasanna Malaiyandi:

What sort of restores do you handle?

Vish Reddy:

Great question.

Vish Reddy:

No, you know, what's the point of doing backup without being

Vish Reddy:

able to restore back right?

Prasanna Malaiyandi:

Curtis and I were just talking about that yesterday.

W. Curtis Preston:

No one cares.

W. Curtis Preston:

If you can back up Vish

Vish Reddy:

So.

Vish Reddy:

Which, and choosing that one thing or two things, or, you know, again, being very

Vish Reddy:

granular about what you can restore by.

Vish Reddy:

So that is part of our MVP.

Vish Reddy:

We back up every day, every 24 hours, automatic backup,

Vish Reddy:

remember this is insurance, right?

Vish Reddy:

You just buy it and you forget about it till you need it.

Vish Reddy:

Of course.

Vish Reddy:

Um, and so when you need it, you can go back in, you can go pick the specific

Vish Reddy:

day from which you want that backup, uh, or that, you know, piece of data, maybe

Vish Reddy:

it's a ticket, maybe it's an attachment.

Vish Reddy:

Um, and then you can go and filter out, uh, and say, okay, I want this

Vish Reddy:

specific thing to be restored back.

Vish Reddy:

That's what we do.

Vish Reddy:

There are lot more use cases, which are there as an example, something which we're

Vish Reddy:

not doing in the MVP, lot of customers have multiple different sites or tenants.

Vish Reddy:

Uh, you know, you control five different tenants.

Vish Reddy:

You may move things around.

Vish Reddy:

It's sort of a data migration use case.

Vish Reddy:

So to speak, you're backed up something in from one place.

Vish Reddy:

You wanna put it into another place.

Vish Reddy:

Um, that's something that you'll be doing in the future.

Vish Reddy:

Uh, uh, that's not part of MVP today.

Vish Reddy:

What we do is whatever you back up from a given tenant, you

Vish Reddy:

can put it back into the same.

Vish Reddy:

Now JIRA to the earlier point, which we were making.

Vish Reddy:

It is a pretty complex.

Vish Reddy:

The data structure is pretty complex.

Vish Reddy:

So there is actual data which consists of, uh, you know, uh, comments, potentially

Vish Reddy:

description of what the ticket is.

Vish Reddy:

And so on.

Vish Reddy:

And attachments, attachments could be drawings, could be code snippets,

Vish Reddy:

you know, various or zoom recordings.

Vish Reddy:

Lot of people add in zoom recordings have seen into the ticket itself.

Vish Reddy:

Uh, that's part of your data.

Vish Reddy:

Then there is a whole bunch of configuration configuration here could

Vish Reddy:

be workflows, could be, you know, um, you know, different screens would show

Vish Reddy:

up, uh, you know, to different users.

Vish Reddy:

Um, and so we back up both and we can restore both those things back.

Vish Reddy:

Uh, uh, we, for the MVP, we are, we are able to restore back

Vish Reddy:

everything on the data side of this.

Vish Reddy:

Uh, anything you do with the issues, you can restore that back, uh, on

Vish Reddy:

the configuration side, uh, we've started off with screens and workflows

Vish Reddy:

because those, those to be the most important things based on ours.

Vish Reddy:

And then, uh, you know, over the course of the next two, three

Vish Reddy:

weeks, uh, we'll be adding in more configuration elements to, uh, to be.

Prasanna Malaiyandi:

I'm glad you covered the config elements because

Prasanna Malaiyandi:

that's actually, one of the things I was gonna ask is, especially with SaaS

Prasanna Malaiyandi:

services, people sometimes forget about like the settings and configs, right.

Prasanna Malaiyandi:

That's also critical to capture in terms of backup and restore

Prasanna Malaiyandi:

because someone makes a change.

Prasanna Malaiyandi:

Hey, I wanna be able to restore that.

Prasanna Malaiyandi:

Or like you said, Vish workflows, people don't necessarily think of

Prasanna Malaiyandi:

that as like a JIRA ticket, but it's still important for the business.

Vish Reddy:

One of the learnings which we, uh, had was.

Vish Reddy:

Uh, you know, a lot of companies go through SOC2 compliance audit right now.

Vish Reddy:

So these companies also have JIRA as their change management system, which

Vish Reddy:

tells you, Hey, we, this, this point, this is what's are just about to embark

Vish Reddy:

on getting ourselves SOC2 compliant.

Vish Reddy:

And in talking to the auditor, they were like, I didn't know that, uh, you know,

Vish Reddy:

you, if you delete some tickets, they can, there is no sign of it anymore.

Vish Reddy:

That's a big problem for

W. Curtis Preston:

Yeah,

Vish Reddy:

this is interesting, this, you know, as we're.

W. Curtis Preston:

honestly, that that's a, that's a major hole for JIRA, but

W. Curtis Preston:

that's a problem for them to solve.

W. Curtis Preston:

Like they, they need to have that audit log.

W. Curtis Preston:

Right?

W. Curtis Preston:

Uh, the, the, the story that you mentioned earlier, um, it, it should,

W. Curtis Preston:

you should not be able to just go in and delete tickets without record.

W. Curtis Preston:

Right.

W. Curtis Preston:

Um, we should be able to go, oh, it was Steve.

W. Curtis Preston:

Steve is the one who deleted all the tickets that he

W. Curtis Preston:

didn't want you to know about.

W. Curtis Preston:

Right.

W. Curtis Preston:

Um, but so sort of one final question, cuz we're, we're getting short on

W. Curtis Preston:

time, uh, earlier, I think it was Vish that mentioned that currently

W. Curtis Preston:

the, the, the built-in product, you can only back up every other day.

W. Curtis Preston:

How is it that you're able to back up every day?

W. Curtis Preston:

Is it because of the, the partnership that you.

Vish Reddy:

Great question.

Vish Reddy:

So.

Vish Reddy:

Uh, if you use the backup functionality, which Atlasian gives you, which is

Vish Reddy:

your entire database backup, then you can do it only every 48 hours.

Vish Reddy:

Uh, if you're backing up attachments and so on, what we're doing is different.

Vish Reddy:

We are using that APIs.

Vish Reddy:

We are going, and each of their tickets, uh, we're being very granular, right?

Vish Reddy:

And we're not getting the entire data set in one shot.

Vish Reddy:

We're going and picking everything one at a.

Vish Reddy:

And backing it up.

Vish Reddy:

Now, here is where things are.

Vish Reddy:

Um, and I think most people are familiar with this is, your first backup is gonna

Vish Reddy:

take a long because of are much shorter.

Vish Reddy:

Why?

Vish Reddy:

Because it's changes.

Vish Reddy:

Now.

Vish Reddy:

If we were pulling down the entire database, every time it's not cost

Vish Reddy:

effective and, you know, takes.

W. Curtis Preston:

Because you're using APIs and you're doing incremental backup.

W. Curtis Preston:

That makes sense.

W. Curtis Preston:

Cool.

W. Curtis Preston:

Well, listen, uh, we might have lost sanket.

W. Curtis Preston:

It, um, you know, his, his, his bits are flying up in the internet and coming

W. Curtis Preston:

back down all the way from India to here.

W. Curtis Preston:

I, I says he just messaged.

W. Curtis Preston:

He's not able to hear anymore.

W. Curtis Preston:

I'm gonna, I'm gonna thank you both for doing this.

W. Curtis Preston:

Sanket can't hear us anymore, but I'll, I'll thank him as well.

W. Curtis Preston:

And, um, and, uh, thanks a lot.

W. Curtis Preston:

I, I, I wish you the best of luck on this new company.

Vish Reddy:

Uh, thank you very much.

Vish Reddy:

Uh, uh, and for hosting us out here today, uh, it was great, uh, you know, catching

Vish Reddy:

up with you and also sharing what we've.

Vish Reddy:

Uh, you know, uh, we would love for you guys to try out our

Vish Reddy:

product at some point, um, just.

W. Curtis Preston:

Well, well, I I do happen to know a certain,

W. Curtis Preston:

uh, SaaS company that uses JIRA.

W. Curtis Preston:

I'm just saying, and I know some people there and I think you do too,

W. Curtis Preston:

but that's, that's a, that's your own problem to solve, uh, and Prasanna again.

W. Curtis Preston:

Great questions as always.

Prasanna Malaiyandi:

I try and thanks Vish and Sanket.

Prasanna Malaiyandi:

Yeah.

Prasanna Malaiyandi:

Great catching up.

Prasanna Malaiyandi:

Uh, V the one question I was gonna ask.

Prasanna Malaiyandi:

So if people want to try out the product or anything else, I know

Prasanna Malaiyandi:

that the website is going live soon.

Prasanna Malaiyandi:

By the time this podcast gets released, do they just go onto the website, um,

Prasanna Malaiyandi:

to access and they can request a free trial or whatever needs to be done.

Prasanna Malaiyandi:

Everything's gonna be available on the.

Vish Reddy:

Great question.

Vish Reddy:

Uh, our product is gonna be available on the Atlassian marketplace.

Vish Reddy:

Couple of clicks.

Vish Reddy:

You can get started.

Vish Reddy:

There's a free trial there.

Vish Reddy:

Uh, you know, it's all automated.

Vish Reddy:

Uh, literally you can start your trial of the software within five minutes

Vish Reddy:

or maybe less and you get 30 days backup, restore, unlimited, whatever.

Vish Reddy:

Uh, yep.

Vish Reddy:

All provision through Atlassian.

W. Curtis Preston:

Nice.

W. Curtis Preston:

I like it.

W. Curtis Preston:

All right.

W. Curtis Preston:

Well, um, again, thanks to our listeners and remember to subscribe