1 00:00:34,318 --> 00:00:37,228 W. Curtis Preston: Hi, and welcome to Backup Central's Restore it All podcast. 2 00:00:37,228 --> 00:00:39,688 I'm your host w Curtis Preston, AKA Mr. 3 00:00:39,688 --> 00:00:45,968 Backup, and I have with me, my cylinder misfire detection consultant, Prasanna 4 00:00:45,968 --> 00:00:47,858 Malaiyandi, how's it going Prasanna? 5 00:00:48,058 --> 00:00:49,078 Prasanna Malaiyandi: I'm good Curtis. 6 00:00:49,078 --> 00:00:53,878 Honestly, I think you should just throw the entire thing out and just start over. 7 00:00:54,208 --> 00:00:57,118 W. Curtis Preston: I don't think that I don't think that's economically 8 00:00:57,493 --> 00:01:00,403 Prasanna Malaiyandi: No that don't do that, but this is the ongoing 9 00:01:00,403 --> 00:01:06,013 saga for our listeners of Curtis's car that has an on again, off again, 10 00:01:06,013 --> 00:01:09,403 cylinder misfire issue, which may or may not be a head gasket issue, 11 00:01:09,403 --> 00:01:11,053 which may or may not be other things. 12 00:01:11,638 --> 00:01:16,028 W. Curtis Preston: Yeah, I either have a blown head gasket or, or a 13 00:01:16,028 --> 00:01:22,808 head gasket that is blowing That is in the process of being blown, uh, or an 14 00:01:22,813 --> 00:01:25,838 EGR valve stuck in the open position. 15 00:01:26,318 --> 00:01:26,648 And. 16 00:01:27,258 --> 00:01:31,818 Uh, the usual and the thing is it's, it's an intermittent problem. 17 00:01:32,148 --> 00:01:35,598 And so troubleshooting is very, very difficult, you know, for 18 00:01:35,598 --> 00:01:38,478 those of you that are, you know, your, your computer geeks, right? 19 00:01:38,478 --> 00:01:42,528 Like how do you fix a bug that only happens once every thousand 20 00:01:42,533 --> 00:01:44,068 times that you use the software? 21 00:01:45,008 --> 00:01:45,728 Prasanna Malaiyandi: exactly. 22 00:01:45,728 --> 00:01:49,228 That's when you that's, when you basically turn it into cos. 23 00:01:50,478 --> 00:01:51,138 W. Curtis Preston: to what? 24 00:01:51,308 --> 00:01:51,968 Prasanna Malaiyandi: Cosmic. 25 00:01:51,968 --> 00:01:52,598 I, one of the 26 00:01:52,758 --> 00:01:53,598 W. Curtis Preston: Oh yeah, 27 00:01:54,368 --> 00:01:54,698 Prasanna Malaiyandi: right. 28 00:01:54,698 --> 00:01:58,178 If a bug was hit and no one's able to reproduce it, figure it out, right. 29 00:01:58,178 --> 00:02:00,938 It'd basically be like the stars aligned. 30 00:02:00,938 --> 00:02:04,568 There was a solar flare, some cosmic event happened and therefore 31 00:02:04,568 --> 00:02:07,618 the bug is no longer there. 32 00:02:08,568 --> 00:02:14,528 W. Curtis Preston: I'm down to, I'm going to do the repair of one or the other, 33 00:02:14,658 --> 00:02:16,698 and both of them are, are significant. 34 00:02:16,758 --> 00:02:18,078 And then see if it goes away. 35 00:02:18,083 --> 00:02:18,448 Right. 36 00:02:18,858 --> 00:02:21,198 Prasanna Malaiyandi: I thought the EGR is less work than 37 00:02:21,243 --> 00:02:22,113 W. Curtis Preston: No, it's a lot. 38 00:02:22,113 --> 00:02:23,343 It's actually quite a bit of work. 39 00:02:23,583 --> 00:02:24,873 Um, because you, 40 00:02:24,953 --> 00:02:25,848 Prasanna Malaiyandi: out to get to it. 41 00:02:25,923 --> 00:02:26,253 W. Curtis Preston: yeah. 42 00:02:26,253 --> 00:02:26,673 It's. 43 00:02:26,763 --> 00:02:27,153 Yeah. 44 00:02:27,153 --> 00:02:30,633 And then, and then, and as long as you're pulling the EGR valve, 45 00:02:30,633 --> 00:02:34,143 you should pull out the, um, the intake manifold and clean it out. 46 00:02:34,143 --> 00:02:36,993 There's some ports that need to be, I've been watching, I've been watching 47 00:02:36,998 --> 00:02:38,533 a lot of YouTube videos Prasanna. 48 00:02:38,553 --> 00:02:39,633 You'd be very proud of me. 49 00:02:40,453 --> 00:02:41,143 Prasanna Malaiyandi: I am now. 50 00:02:41,143 --> 00:02:41,383 What? 51 00:02:41,383 --> 00:02:43,303 But wait though, Curtis, are you watching at two X? 52 00:02:44,253 --> 00:02:46,443 W. Curtis Preston: Uh, no, I I'm old school, man. 53 00:02:46,443 --> 00:02:47,523 I watch it at one X. 54 00:02:47,553 --> 00:02:48,763 I actually like you. 55 00:02:49,998 --> 00:02:50,598 like that. 56 00:02:50,718 --> 00:02:54,618 Well, I'm not like you, I'm not watching like 19 hours of it. 57 00:02:55,843 --> 00:02:56,263 Prasanna Malaiyandi: Hey, 58 00:02:56,478 --> 00:02:56,898 W. Curtis Preston: to get, 59 00:02:57,023 --> 00:02:58,023 Prasanna Malaiyandi: like four hours. 60 00:02:58,093 --> 00:02:58,783 Come on. 61 00:02:59,388 --> 00:03:03,558 W. Curtis Preston: uh, yeah, but you're watching 19 hours videos in four hours 62 00:03:03,738 --> 00:03:07,248 Prasanna Malaiyandi: Ah, I wish they would actually go faster than two X that's. 63 00:03:07,248 --> 00:03:09,618 Now my feature request for YouTube. 64 00:03:09,678 --> 00:03:11,058 Any developers out there at YouTube? 65 00:03:11,688 --> 00:03:15,018 W. Curtis Preston: I can't imagine what in the world you would do at two X. 66 00:03:15,068 --> 00:03:15,878 Anyway. 67 00:03:16,448 --> 00:03:20,498 So, um, well we're gonna get onto something much more 68 00:03:20,498 --> 00:03:21,968 exciting than car maintenance. 69 00:03:21,973 --> 00:03:24,188 We're gonna talk about backup today. 70 00:03:24,188 --> 00:03:27,338 You know, my favorite topic, we have two guests today. 71 00:03:27,758 --> 00:03:33,068 Our first guest started his career, just like me as a backup admin, I first cross 72 00:03:33,068 --> 00:03:35,858 pass with, with him when he was leading the security and compliance team at 73 00:03:35,858 --> 00:03:38,928 Druva, uh, he is a co-founder of Revyz. 74 00:03:38,953 --> 00:03:41,108 Welcome to the podcast Sanket Parlikar 75 00:03:41,188 --> 00:03:44,063 Sanket Parlikar: glad to Glad be on the podcast. 76 00:03:45,363 --> 00:03:47,613 W. Curtis Preston: And we also have your co-founder. 77 00:03:47,823 --> 00:03:51,843 He started his career designing chips at SGI and has worked for 78 00:03:51,843 --> 00:03:56,553 multiple security firms, including Symantec, Druva, and Agari data. 79 00:03:56,853 --> 00:03:59,013 He's also a co-founder at Revyz. 80 00:03:59,283 --> 00:04:01,533 Welcome to the podcast Vish Reddy? 81 00:04:02,448 --> 00:04:02,868 Vish Reddy: Thank you. 82 00:04:03,018 --> 00:04:05,578 Uh, very nice to be here. 83 00:04:06,443 --> 00:04:07,603 W. Curtis Preston: sort, sort of be here. 84 00:04:07,653 --> 00:04:09,993 What, what time is it over there right now 85 00:04:11,253 --> 00:04:13,593 Sanket Parlikar: It's like 9 45, 9 50 86 00:04:14,193 --> 00:04:15,003 W. Curtis Preston: in the evening? 87 00:04:15,673 --> 00:04:16,093 Sanket Parlikar: Yep. 88 00:04:16,263 --> 00:04:20,193 W. Curtis Preston: Okay, well, thanks very much for, for joining us to talk about 89 00:04:20,193 --> 00:04:22,473 backups at basically 10 o'clock at night. 90 00:04:22,893 --> 00:04:26,283 I know I do that a lot, but usually I'm just talking to myself at 91 00:04:26,433 --> 00:04:29,043 Prasanna Malaiyandi: Socks like this is just me getting started for the evening. 92 00:04:29,623 --> 00:04:31,573 W. Curtis Preston: I remember it's interesting. 93 00:04:31,573 --> 00:04:35,653 I remember 10 o'clock for me, like historically in my career, 10 o'clock 94 00:04:35,653 --> 00:04:41,323 was when I was doing backups, like for people, like 10 o'clock for 95 00:04:41,328 --> 00:04:44,053 some reason was the time that a lot of them seemed to kick off. 96 00:04:44,143 --> 00:04:47,503 So this was like the beginning of the night for, you know, for 97 00:04:47,503 --> 00:04:48,973 a lot of, for a lot of time. 98 00:04:49,783 --> 00:04:53,293 But, uh, so anyway, so thanks for both of you coming on here. 99 00:04:53,503 --> 00:04:55,093 We're we're here to talk about. 100 00:04:56,598 --> 00:05:00,628 A new company, which you two, uh co-founded, which is called. 101 00:05:00,628 --> 00:05:03,148 I make sure I, I have pronounced it correctly. 102 00:05:03,148 --> 00:05:04,698 I'm assuming it is Revyz. 103 00:05:05,188 --> 00:05:06,508 Did I, did I get that correct? 104 00:05:07,018 --> 00:05:07,768 Sanket Parlikar: Yes, that's right. 105 00:05:08,938 --> 00:05:09,358 W. Curtis Preston: Okay. 106 00:05:09,463 --> 00:05:10,723 Prasanna Malaiyandi: But it's an interesting spelling. 107 00:05:10,723 --> 00:05:11,773 So if you go to look 108 00:05:11,818 --> 00:05:12,358 W. Curtis Preston: Yeah, it is. 109 00:05:12,358 --> 00:05:12,598 Yeah. 110 00:05:12,598 --> 00:05:15,628 It is an interesting spelling, which is, which is, which is why I wasn't 111 00:05:15,628 --> 00:05:17,188 sure if I was pronouncing it correctly. 112 00:05:17,428 --> 00:05:21,678 It's R E V Y z.io as the website. 113 00:05:22,998 --> 00:05:28,843 Um, so why don't we sort of start at the, and, and by the way, I, you 114 00:05:28,843 --> 00:05:32,173 know, I've already brought up Druva, uh, that's where I happen to work. 115 00:05:32,173 --> 00:05:34,003 Uh, I'll throw out our standard disclaimer. 116 00:05:34,618 --> 00:05:37,348 Our standard disclaimer, Prasanna works at zoom. 117 00:05:37,348 --> 00:05:38,278 I work at Druva. 118 00:05:38,548 --> 00:05:40,408 This is not a podcast of either company. 119 00:05:40,408 --> 00:05:45,538 The opinions that you hear are ours and, um, be sure to rate us at your 120 00:05:45,538 --> 00:05:49,648 favorite podcaster, just give us stars, give us, and we really love comments. 121 00:05:49,918 --> 00:05:52,168 And currently there's an offering on the play. 122 00:05:52,738 --> 00:05:56,188 You guys didn't even know this, but apparently if we. 123 00:05:56,893 --> 00:06:00,553 Nine new comments on apple, on iTunes. 124 00:06:00,673 --> 00:06:04,783 Um, you know, in the next week or two, then apparently I have to grow a 125 00:06:04,828 --> 00:06:05,758 Prasanna Malaiyandi: was, it was a month. 126 00:06:05,938 --> 00:06:06,328 We said 127 00:06:06,463 --> 00:06:07,753 W. Curtis Preston: Oh, that, oh, was it a month? 128 00:06:07,903 --> 00:06:10,633 It was a month from the last episode. 129 00:06:10,753 --> 00:06:11,173 Right? 130 00:06:11,793 --> 00:06:11,993 Prasanna Malaiyandi: went 131 00:06:12,223 --> 00:06:12,763 W. Curtis Preston: Right. 132 00:06:13,123 --> 00:06:19,543 So, uh, if we get nine new comments on apple iTunes, then I have 133 00:06:19,543 --> 00:06:21,043 to grow a beard for Christmas. 134 00:06:23,308 --> 00:06:28,048 Which, you know, I mean, it will still not look as full as Prasannas cuz it's 135 00:06:28,048 --> 00:06:30,448 currently a, theard, is it a theard now? 136 00:06:30,823 --> 00:06:32,123 Prasanna Malaiyandi: uh, not quite a theard. 137 00:06:32,143 --> 00:06:33,243 It's still a tweard. 138 00:06:33,513 --> 00:06:34,533 It's like a and a. 139 00:06:37,753 --> 00:06:38,983 W. Curtis Preston: A two and a half year. 140 00:06:39,193 --> 00:06:40,753 That's not, that doesn't make any sense. 141 00:06:40,753 --> 00:06:41,053 Yeah. 142 00:06:41,623 --> 00:06:46,183 Uh, but yeah, cuz I, I, I, you know, I've really never grown a, a real 143 00:06:46,183 --> 00:06:48,463 beard and anyway, so there you go. 144 00:06:48,463 --> 00:06:54,073 So rate, you know, gives some comments and um, also if you wanna join in the 145 00:06:54,073 --> 00:06:55,603 conversation, we'd love to have you. 146 00:06:56,053 --> 00:07:00,823 So, if you like the topics that we talk about, backup security, privacy, uh, you 147 00:07:00,823 --> 00:07:02,713 know, ransomware, all of those things. 148 00:07:02,803 --> 00:07:08,083 And, uh, then please just, uh, reach out to me at Twitter @wcpreston 149 00:07:08,293 --> 00:07:10,813 or w Curtis Preston at Gmail. 150 00:07:12,343 --> 00:07:15,743 So let's go back to the beginning. 151 00:07:16,403 --> 00:07:22,048 What made you wanna do this crazy thing of, of founding a company? 152 00:07:22,048 --> 00:07:24,058 Well, I'll, I'll start with Vish here. 153 00:07:24,448 --> 00:07:29,188 Um, you know what, you know, what, what problem was out there that you said? 154 00:07:29,188 --> 00:07:30,808 I, I think I can solve this problem. 155 00:07:33,193 --> 00:07:39,263 Vish Reddy: Uh, Curtis having met multiple customers at Druva having worked there. 156 00:07:39,843 --> 00:07:40,903 One of the things 157 00:07:44,878 --> 00:07:45,488 W. Curtis Preston: Mm-hmm 158 00:07:47,323 --> 00:07:54,073 Vish Reddy: applications, companies were deployed were reciting the cloud. 159 00:07:55,758 --> 00:07:58,888 You know, the cloud vendor, again, no fault of the cloud 160 00:07:58,888 --> 00:08:02,938 vendor, uh, you know, the cloud vendor would always say, Hey, Mr. 161 00:08:02,938 --> 00:08:09,268 Customer, it is your responsibility to secure your data, which 162 00:08:09,268 --> 00:08:09,988 is, which makes sense. 163 00:08:09,988 --> 00:08:10,168 Right? 164 00:08:10,173 --> 00:08:16,258 I mean, if a user and delete their data accidentally, you, you can't hold the 165 00:08:16,498 --> 00:08:18,088 cloud vendor to be responsible for that. 166 00:08:18,683 --> 00:08:20,453 W. Curtis Preston: Well, can I interject on you there? 167 00:08:20,483 --> 00:08:24,683 Um, I mean, you're telling your backstory, but I, I just have to interject there. 168 00:08:25,613 --> 00:08:26,633 I would love it. 169 00:08:26,638 --> 00:08:28,193 If the cloud vendors would say that. 170 00:08:29,438 --> 00:08:29,888 Right. 171 00:08:29,888 --> 00:08:30,638 I would love it. 172 00:08:30,638 --> 00:08:34,208 If the cloud vendors would make it very clear whose responsibility 173 00:08:34,208 --> 00:08:40,538 it is to protect the data UN unfortunately many of them don't right. 174 00:08:40,718 --> 00:08:43,448 They, they, they either, they either just don't talk about it. 175 00:08:43,958 --> 00:08:49,178 Um, You, you know that that's probably, that's probably the worst to me is it is 176 00:08:49,178 --> 00:08:53,678 if they say nothing, it it's not in their service contract, it's not in their SLAs. 177 00:08:54,548 --> 00:08:58,718 And, and yet they may have legions of fans and, and, and I'm gonna, I'm gonna call 178 00:08:58,723 --> 00:09:03,368 out Microsoft as being the worst offender here, because they have legions of fans 179 00:09:03,518 --> 00:09:06,248 who say, you do not need to back this up. 180 00:09:06,848 --> 00:09:09,128 They have not publicly clarified. 181 00:09:09,128 --> 00:09:13,718 They have a few things hit, you know, hidden here and there, but there is no. 182 00:09:14,183 --> 00:09:17,093 You know, um, public statement. 183 00:09:17,093 --> 00:09:19,253 So, you know, on the, on the reverse of that, I would 184 00:09:19,253 --> 00:09:20,963 give, I would put Salesforce. 185 00:09:21,533 --> 00:09:24,323 They, they, you know, not only have they clarified what your 186 00:09:24,323 --> 00:09:27,923 responsibilities are, they now offer their own service to back up. 187 00:09:28,583 --> 00:09:32,393 Um, and then somewhere in the middle is, is, you know, 4,000 188 00:09:32,423 --> 00:09:33,833 other SaaS vendors out there. 189 00:09:33,893 --> 00:09:34,223 Right. 190 00:09:34,763 --> 00:09:36,623 Um, but yeah, so. 191 00:09:37,943 --> 00:09:39,203 Uh, let's come back to that. 192 00:09:39,263 --> 00:09:40,553 I wanna, I wanna come back to that. 193 00:09:40,553 --> 00:09:44,033 I want you to finish sort of your story, but I wanna come back to this topic. 194 00:09:44,573 --> 00:09:46,253 Uh, anyway, sorry. 195 00:09:46,253 --> 00:09:47,483 I was just, it's a hobby horse. 196 00:09:47,483 --> 00:09:48,383 I just had to jump on. 197 00:09:48,623 --> 00:09:48,983 So. 198 00:09:51,668 --> 00:09:51,998 Vish Reddy: Yeah. 199 00:09:52,088 --> 00:09:54,938 So, you know, that led us to saying, okay, this is a problem. 200 00:09:55,028 --> 00:09:56,378 Lot of, to your point. 201 00:09:56,383 --> 00:10:01,088 Lot of customers don't know that, uh, there is, uh, in fact, 202 00:10:01,178 --> 00:10:02,798 uh, I'll come back to a story. 203 00:10:02,918 --> 00:10:03,788 One of the first. 204 00:10:04,448 --> 00:10:08,798 Uh, you know, prospects or validators who we met had the 205 00:10:08,798 --> 00:10:11,108 exact same point as you, right? 206 00:10:11,108 --> 00:10:12,428 You said, why do we need to back? 207 00:10:12,728 --> 00:10:15,698 You know, the vendor is providing the service. 208 00:10:16,118 --> 00:10:20,918 I'll get into the details in a bit of that, but that was the Genesis of saying, 209 00:10:20,948 --> 00:10:22,508 okay, you know, there is a problem. 210 00:10:23,693 --> 00:10:29,333 When we looked into some of the more popular, um, DevOps focus, 211 00:10:29,333 --> 00:10:31,013 we were more focused on DevOps. 212 00:10:31,013 --> 00:10:34,103 You obviously, you mentioned office 365 Salesforce. 213 00:10:34,763 --> 00:10:37,523 There's a good ecosystem of vendors there. 214 00:10:37,583 --> 00:10:44,053 So we said the things people are looking at, which critical for the functioning 215 00:10:44,058 --> 00:10:48,233 of that business, uh, is important. 216 00:10:48,623 --> 00:10:51,523 Um, Workday servicenow. 217 00:10:51,878 --> 00:10:55,738 And there's a growing list of, uh, applications, which are out there. 218 00:10:56,138 --> 00:10:58,388 And we said, okay, can we build an architecture? 219 00:10:58,388 --> 00:11:03,638 Which is, which can, you know, help protect that data? 220 00:11:04,028 --> 00:11:07,718 Can we have a generic architecture, which can, where we can plug in any of these 221 00:11:07,723 --> 00:11:13,028 different applications and we can help simplify the job of the administrator. 222 00:11:13,478 --> 00:11:15,518 So that's where we got started. 223 00:11:15,938 --> 00:11:18,098 Uh, that was the Genesis when we recognized this, 224 00:11:18,188 --> 00:11:19,128 that there's this problem. 225 00:11:19,733 --> 00:11:24,413 Uh, we said, okay, you know, again, backup as you guys are more familiar, 226 00:11:24,743 --> 00:11:29,753 this is one of the basic functions, which it administrator performs now. 227 00:11:29,843 --> 00:11:30,623 Unfortunately, 228 00:11:30,934 --> 00:11:35,344 Now, there are some people who spent hours together just started to do this. 229 00:11:35,584 --> 00:11:38,404 And he said, that's not, that's not in today's day and age. 230 00:11:38,614 --> 00:11:41,474 You should not be spending a lot of time doing this. 231 00:11:41,479 --> 00:11:42,514 This should be just offloaded. 232 00:11:42,954 --> 00:11:44,689 Should be at the end of the day. 233 00:11:44,869 --> 00:11:46,859 I dunno whether you guys agree with me or not. 234 00:11:47,189 --> 00:11:52,059 Backup is like insurance, you need it some point of time, but you never 235 00:11:52,059 --> 00:11:53,899 know when you need health insurance. 236 00:11:56,869 --> 00:11:57,259 W. Curtis Preston: Yeah. 237 00:11:57,469 --> 00:11:59,719 It's, it's exactly like insurance in that. 238 00:11:59,869 --> 00:12:01,369 You must buy it before you need it. 239 00:12:03,289 --> 00:12:07,309 you, you can't get car insurance after you've had an accident. 240 00:12:07,519 --> 00:12:09,559 It's exactly like insurance in that same way. 241 00:12:10,984 --> 00:12:11,224 Vish Reddy: Yeah. 242 00:12:11,434 --> 00:12:13,354 So just to continue the story. 243 00:12:13,384 --> 00:12:18,334 Oh, um, uh, you know, Sankit and I used to work together. 244 00:12:18,544 --> 00:12:23,404 Um, and, uh, we would exchange every so often we would exchange some ideas 245 00:12:23,409 --> 00:12:24,784 and say, oh, maybe we should do this. 246 00:12:24,784 --> 00:12:25,384 We should do that. 247 00:12:25,774 --> 00:12:29,614 And then I shared with him this idea, oh, why don't we? 248 00:12:29,854 --> 00:12:32,194 Well, you know, there is a problem out here. 249 00:12:32,194 --> 00:12:34,384 I've talked to a couple people and. 250 00:12:35,844 --> 00:12:42,204 know, they're outlined that there's don't solve. 251 00:12:48,739 --> 00:12:50,779 Sanket Parlikar: Oh, yeah, it was a, a really. 252 00:12:51,559 --> 00:12:52,219 Journey, right. 253 00:12:52,249 --> 00:12:58,489 Uh, since beginning like, uh, inception itself, uh, exchanging ideas, talking to 254 00:12:58,549 --> 00:13:02,689 different people, trying to understand what is a real problem, uh, out there. 255 00:13:02,689 --> 00:13:03,019 Right? 256 00:13:03,289 --> 00:13:08,719 Uh, luckily, uh, I had a lot of, uh, admin friends, uh, who were managing 257 00:13:08,724 --> 00:13:12,769 different applications, uh, and then, uh, wish, uh, had different 258 00:13:12,769 --> 00:13:14,839 connections and all the people. 259 00:13:15,229 --> 00:13:19,009 Talk to, uh, basically they said, wow, that's amazing idea. 260 00:13:19,009 --> 00:13:19,279 Right? 261 00:13:19,309 --> 00:13:24,739 Uh, I do have a lot of critical data sitting into, uh, these, uh, DevOps tools. 262 00:13:25,099 --> 00:13:29,659 And specifically, if you talk about Atlassian, it's again, uh, 263 00:13:29,749 --> 00:13:31,249 pretty sensitive data for me. 264 00:13:31,429 --> 00:13:33,339 Why don't you help me, uh, back that up today? 265 00:13:33,339 --> 00:13:35,929 I have a problem, but I cannot predict that. 266 00:13:36,724 --> 00:13:39,994 Uh, there are a lot of challenges, so exchanging a lot of ideas, 267 00:13:39,994 --> 00:13:41,224 talking to a lot of people. 268 00:13:41,494 --> 00:13:46,144 Uh, that's how the journey, uh, started and then slowly validating that idea, 269 00:13:46,144 --> 00:13:50,374 validating that problem out there and then, uh, finding a solution for it. 270 00:13:50,614 --> 00:13:51,874 That's how it all started. 271 00:13:53,014 --> 00:13:56,134 Prasanna Malaiyandi: Yeah, it's great that you actually have like real 272 00:13:56,134 --> 00:13:57,964 world customers who have this problem. 273 00:13:57,964 --> 00:13:58,264 Right. 274 00:13:58,414 --> 00:13:58,804 A lot of times. 275 00:13:59,254 --> 00:14:00,574 You're like, oh, I have this idea. 276 00:14:00,574 --> 00:14:02,794 Let me try to find a good market fit for this. 277 00:14:02,794 --> 00:14:03,094 Right. 278 00:14:03,094 --> 00:14:04,504 And it's like, you're struggling. 279 00:14:04,504 --> 00:14:08,074 But actually having a problem that people are struggling with is like, 280 00:14:08,164 --> 00:14:09,634 gets you so much further ahead. 281 00:14:10,024 --> 00:14:12,694 The one thing, uh, and I don't know, Sanket or Vish who wants to 282 00:14:12,694 --> 00:14:16,294 answer this is maybe Sanket is, I know you mentioned Atlassian. 283 00:14:16,804 --> 00:14:22,474 A lot of our listeners may not know what Atlassian is or who they are. 284 00:14:22,474 --> 00:14:25,054 Could you maybe give sort of a brief background about some of the 285 00:14:25,054 --> 00:14:28,684 products, um, that they might offer that people might be more familiar? 286 00:14:30,304 --> 00:14:30,994 Sanket Parlikar: Absolutely. 287 00:14:31,174 --> 00:14:35,074 So in general, uh, let's talk about software industry, right? 288 00:14:35,104 --> 00:14:38,854 Uh, in software industry, typically, uh, developers need a 289 00:14:38,854 --> 00:14:40,564 system to track their work, right? 290 00:14:40,804 --> 00:14:42,874 Uh, they are developing the software. 291 00:14:42,874 --> 00:14:45,574 They would be logging in, uh, certain tickets to track, uh, 292 00:14:45,574 --> 00:14:50,064 track their tasks and work, uh, and how they, uh, develop a software. 293 00:14:50,069 --> 00:14:50,254 Right. 294 00:14:50,434 --> 00:14:56,984 So typically, uh, what, uh, This software is, uh, is going to do for developers 295 00:14:56,984 --> 00:14:58,934 is, is going to create tickets. 296 00:14:58,934 --> 00:15:02,294 It's going to manage all their work, their work log, and 297 00:15:02,294 --> 00:15:03,614 then build reports out of it. 298 00:15:03,614 --> 00:15:07,604 That's how, uh, the engineering function, uh, tracks their efforts 299 00:15:07,604 --> 00:15:11,624 right now, Atlassian as a company, what they do is they focus on, 300 00:15:11,894 --> 00:15:14,364 uh, uh, creating a software. 301 00:15:14,974 --> 00:15:17,104 Does that job for engineering function. 302 00:15:17,404 --> 00:15:21,544 And one of their application is called S JIRA software, uh, which will, 303 00:15:21,574 --> 00:15:25,984 uh, give that functionality to the engineering, uh, group, uh, wherein 304 00:15:25,984 --> 00:15:30,394 they can create different tickets, uh, log in their daily tasks and track 305 00:15:30,394 --> 00:15:32,554 it as, as they make the progress. 306 00:15:32,734 --> 00:15:34,264 So that's the JIRA software. 307 00:15:34,829 --> 00:15:37,679 There's another application, for example, which is called as 308 00:15:37,679 --> 00:15:42,149 a confluence wherein you can go ahead, create your documentation, 309 00:15:42,359 --> 00:15:44,459 be your internal documentation. 310 00:15:44,459 --> 00:15:46,529 Be it your customer facing documentation. 311 00:15:46,799 --> 00:15:50,459 You create all the documentation and then use it for different purposes. 312 00:15:50,609 --> 00:15:53,489 So that's what Atlassian does at pretty high level. 313 00:15:54,334 --> 00:15:56,674 Prasanna Malaiyandi: So it's basically building all the tools you need rather 314 00:15:56,674 --> 00:16:00,514 than developers having to spend time focused on how do I track what's 315 00:16:00,514 --> 00:16:05,254 going on in spreadsheets or in like documents, writing out things, right. 316 00:16:05,254 --> 00:16:06,814 It's all easily available. 317 00:16:06,814 --> 00:16:07,654 So people have business. 318 00:16:08,269 --> 00:16:08,629 Gotcha. 319 00:16:08,629 --> 00:16:08,989 Across the 320 00:16:09,199 --> 00:16:11,929 W. Curtis Preston: So this was a, this is a tool that you were obviously 321 00:16:11,934 --> 00:16:17,869 familiar with in your various, you know, basically doing your regular job. 322 00:16:18,874 --> 00:16:19,324 Sanket Parlikar: Exactly. 323 00:16:19,324 --> 00:16:22,864 And, and I just gave you one example of software industry, right? 324 00:16:23,074 --> 00:16:27,394 Uh, because all of us come from software background or a product 325 00:16:27,394 --> 00:16:31,144 background, but when we connected with different, uh, people, different 326 00:16:31,144 --> 00:16:35,764 customers, uh, we discovered that it's not only limited to software industry. 327 00:16:36,004 --> 00:16:40,384 Ticketing system in general is applicable to almost every industry. 328 00:16:40,444 --> 00:16:43,864 We went to healthcare people, they're using ticketing system. 329 00:16:44,074 --> 00:16:46,084 We went to automobile industry people. 330 00:16:46,084 --> 00:16:48,664 They're using ticketing system in one way or the other. 331 00:16:49,084 --> 00:16:49,384 Right. 332 00:16:49,564 --> 00:16:53,344 So this is not limited to one specific software industry, 333 00:16:53,349 --> 00:16:55,414 but it's applicable everywhere. 334 00:16:55,414 --> 00:16:55,714 Right. 335 00:16:55,954 --> 00:16:59,434 And yeah, people may use different tools, but the problem 336 00:16:59,434 --> 00:17:00,934 is still, uh, pretty generic. 337 00:17:02,449 --> 00:17:03,319 W. Curtis Preston: Right, right. 338 00:17:03,799 --> 00:17:10,249 A and so you talked about Vish, you talked about, um, wanting to 339 00:17:10,249 --> 00:17:12,229 develop a generic architecture. 340 00:17:12,859 --> 00:17:16,879 And I'd say that's probably the biggest challenge that you, that you have 341 00:17:16,879 --> 00:17:21,079 is that you, when you're developing a backup tool, that's gonna back up 342 00:17:21,079 --> 00:17:23,479 so many different types of things. 343 00:17:24,019 --> 00:17:28,549 Um, you know, how do, how do you develop a, an architecture that you think 344 00:17:28,549 --> 00:17:31,159 will serve multiple tools like that? 345 00:17:32,704 --> 00:17:33,124 Vish Reddy: Right. 346 00:17:33,184 --> 00:17:34,984 I think that's the, you're absolutely right. 347 00:17:34,984 --> 00:17:38,614 That's the, the biggest challenge we have and I think we've made significant 348 00:17:38,614 --> 00:17:41,074 progress in addressing the challenge. 349 00:17:41,074 --> 00:17:44,334 I'm not saying that, you know, we've completely solved that problem. 350 00:17:44,944 --> 00:17:48,964 Uh, at this point of time, uh, you know, we started off with Atlassian 351 00:17:48,984 --> 00:17:55,564 Atlassian, as Kate mentioned, is got JIRA confluence, JIRA service management. 352 00:17:55,564 --> 00:17:57,874 It's got a bunch of tools in itself. 353 00:17:58,474 --> 00:18:04,144 Uh, we're sort of focusing on that, uh, uh, you know, challenge, so to speak. 354 00:18:04,594 --> 00:18:07,684 Uh, and then, you know, we're hoping that the architecture have built out 355 00:18:07,774 --> 00:18:09,394 is gonna help us scale to others. 356 00:18:10,024 --> 00:18:13,864 JIRA while you know, ticketing system, it seems simple. 357 00:18:13,924 --> 00:18:16,774 You have a ticket, you have a user who's submitting a ticket. 358 00:18:17,164 --> 00:18:19,264 How, how complicated could that be? 359 00:18:19,269 --> 00:18:19,414 Right. 360 00:18:19,444 --> 00:18:20,674 That's what would all think? 361 00:18:20,974 --> 00:18:24,754 But then once you look inside, if you look the, the database 362 00:18:25,144 --> 00:18:26,914 scheme for that, oh my God. 363 00:18:26,944 --> 00:18:31,024 That the first time I saw this, it was, it was a spaghetti bowl 364 00:18:31,024 --> 00:18:34,684 of like, you know, multiple tables interconnected with each other. 365 00:18:35,284 --> 00:18:37,564 W. Curtis Preston: I for the record, I would describe that as the 366 00:18:37,564 --> 00:18:43,174 JIRA user experience as well, but that's but that's, that's just me. 367 00:18:44,524 --> 00:18:44,764 Vish Reddy: Right. 368 00:18:45,094 --> 00:18:51,214 So I think, you know, uh, the proof in, uh, using the product and seeing how far 369 00:18:51,214 --> 00:18:56,164 we'll come, uh, come along now, one thing which I wanna also, uh, highlight here. 370 00:18:56,194 --> 00:19:02,314 So we, couple of prospects, we validated that idea. 371 00:19:02,794 --> 00:19:03,994 We actually went and pitched this to at. 372 00:19:04,819 --> 00:19:08,149 They said, Hey, you know, we not seeing anybody building something 373 00:19:08,149 --> 00:19:09,379 like this in your ecosystem. 374 00:19:09,589 --> 00:19:10,819 We think that this is critical. 375 00:19:11,329 --> 00:19:17,209 Uh, is this what you guys and you know that between sun and 376 00:19:20,689 --> 00:19:27,709 ICS would, we had had in 30 minutes, uh, the people who we're talking to. 377 00:19:28,204 --> 00:19:31,414 Recognize that this is a good problem to solve for them. 378 00:19:31,654 --> 00:19:34,834 And they were like, yeah, you know, if you guys are willing to put in your efforts 379 00:19:34,834 --> 00:19:39,544 and solve this problem for us, we'll, uh, you know, back you or we'll fund you 380 00:19:40,084 --> 00:19:41,854 some amount of seed money to get started. 381 00:19:42,424 --> 00:19:45,964 And not only that, they connected us back to their engineering team, 382 00:19:46,264 --> 00:19:49,234 the same team, which is developed that complicated, which is there. 383 00:19:49,714 --> 00:19:53,944 And, uh, we're working very closely with them in, you know, uh, 384 00:19:54,004 --> 00:19:56,434 building more APIs, which will help. 385 00:19:57,319 --> 00:20:03,379 Um, you know, backup and restore data in a, in a much cleaner way. 386 00:20:04,009 --> 00:20:08,209 Uh, they do have good APIs, but those APIs are not built, uh, 387 00:20:08,239 --> 00:20:10,549 keeping backup and restored in mind. 388 00:20:10,999 --> 00:20:15,169 Um, but they are working towards getting those new APIs out, uh, soon. 389 00:20:15,454 --> 00:20:15,694 Prasanna Malaiyandi: Yeah. 390 00:20:15,694 --> 00:20:18,934 And I think that's one of the keys is a lot of the vendors, right. 391 00:20:18,934 --> 00:20:22,204 They try to stay agnostic and they're like, Hey, here are the APIs. 392 00:20:22,204 --> 00:20:25,054 You go try to build your backup app or whatever app on top of it. 393 00:20:25,414 --> 00:20:28,774 I think the fact that you guys are actually getting engagement from the 394 00:20:28,774 --> 00:20:30,274 engineering team to be like, Hey. 395 00:20:30,664 --> 00:20:34,264 This is really what it takes and probably also imparting that wisdom 396 00:20:34,264 --> 00:20:37,774 on, Hey, these are the requirements from a backup or a restore perspective, 397 00:20:38,134 --> 00:20:39,634 cuz that's also the other challenges. 398 00:20:39,664 --> 00:20:47,554 Usually in like SaaS services, your restores aren't very expansive, right? 399 00:20:48,094 --> 00:20:50,114 The options you provide, it's normally like, yeah, I'm just 400 00:20:50,114 --> 00:20:50,974 gonna restore everything. 401 00:20:50,974 --> 00:20:55,444 But very rarely do you have the ability to say restore a smaller object? 402 00:20:56,179 --> 00:20:58,429 Unless they're really focused on thinking about that. 403 00:20:58,669 --> 00:21:01,489 Because typically as an engineer, you build features, you build 404 00:21:01,489 --> 00:21:05,029 product, you don't always think about backup and restore data protection 405 00:21:05,239 --> 00:21:06,439 when you're building these things. 406 00:21:06,649 --> 00:21:09,109 W. Curtis Preston: Well, I do, but, um, 407 00:21:09,349 --> 00:21:12,289 Prasanna Malaiyandi: and I know vision Sune do, but I'm 408 00:21:12,289 --> 00:21:14,029 just saying most people don't 409 00:21:14,059 --> 00:21:15,289 W. Curtis Preston: no, I know what you, yeah. 410 00:21:15,349 --> 00:21:15,739 Yeah. 411 00:21:15,919 --> 00:21:20,179 I, I, and, and by the way, I, you know, I'll, I'll give credit to Atlassian 412 00:21:20,239 --> 00:21:25,684 because again, I'm gonna contrast to my favorite punching bag, uh, Microsoft. 413 00:21:26,314 --> 00:21:26,734 Right? 414 00:21:26,734 --> 00:21:30,424 They don't, they, they didn't have APIs for backup, right? 415 00:21:30,574 --> 00:21:34,954 The only way that you got, um, that we were, you know, that Druva and 416 00:21:34,959 --> 00:21:38,674 other companies were able to back up is basically use outlook web access. 417 00:21:38,694 --> 00:21:39,254 Right. 418 00:21:39,424 --> 00:21:44,764 Um, and, and you use an API that was completely meant for meant for 419 00:21:44,764 --> 00:21:46,084 something completely different. 420 00:21:46,414 --> 00:21:47,794 And you're using it for backup. 421 00:21:47,794 --> 00:21:49,954 I think now. 422 00:21:50,359 --> 00:21:51,739 For various reasons. 423 00:21:51,739 --> 00:21:53,959 My understanding is that Microsoft has come out with 424 00:21:53,959 --> 00:21:57,589 some, some new APIs, uh, but, 425 00:21:57,589 --> 00:21:58,504 Prasanna Malaiyandi: Not for everything though. 426 00:21:59,369 --> 00:21:59,789 W. Curtis Preston: Yeah. 427 00:21:59,819 --> 00:22:00,629 But not for everything. 428 00:22:00,779 --> 00:22:01,049 But yeah. 429 00:22:01,049 --> 00:22:07,139 So, so, so hats off to Atlassian for giving you, you know, first, first 430 00:22:07,139 --> 00:22:10,719 off, acknowledging that this is a problem that needs to be solved. 431 00:22:11,199 --> 00:22:16,149 And, uh, and then giving you access to the APIs and to the, and to the engineers. 432 00:22:16,149 --> 00:22:16,719 That's great. 433 00:22:16,890 --> 00:22:19,970 Prasanna Malaiyandi: I was going to jump back, actually, a couple of questions. 434 00:22:20,300 --> 00:22:24,020 Um, I know sanket, you talked about Atlassian, what they do. 435 00:22:24,485 --> 00:22:28,415 Um, I'm sure a lot of folks are asking though, why is a JIRA 436 00:22:28,415 --> 00:22:30,515 system or a confluence system? 437 00:22:30,785 --> 00:22:32,435 Like, why do I even need to back that up? 438 00:22:32,440 --> 00:22:32,675 Right. 439 00:22:32,675 --> 00:22:34,325 It's just, oh, I created some things. 440 00:22:34,325 --> 00:22:35,645 These are all closed tickets. 441 00:22:36,005 --> 00:22:36,335 Right? 442 00:22:36,395 --> 00:22:38,705 Why do I even need to back up this old data? 443 00:22:40,130 --> 00:22:41,090 Sanket Parlikar: Good question. 444 00:22:41,660 --> 00:22:45,680 So I will just go back to my previous example, software industry right 445 00:22:46,010 --> 00:22:49,730 now, engineering is working on a life project, for example, right. 446 00:22:50,090 --> 00:22:53,630 Uh, typically what they do is, uh, they try to put in, uh, all 447 00:22:53,630 --> 00:22:58,010 the, uh, comments and all the, uh, data, what they're working on. 448 00:22:58,325 --> 00:22:59,795 In in, into that ticket. 449 00:22:59,915 --> 00:23:00,185 Right. 450 00:23:00,425 --> 00:23:04,445 And a lot of the times, even the, uh, version control system, uh, 451 00:23:04,475 --> 00:23:08,645 which is like bit bucket GitHub, it's linked with your, uh, JIRA. 452 00:23:09,335 --> 00:23:12,605 So now all the commits are being tracked in a ticket. 453 00:23:13,430 --> 00:23:18,410 Now, if that data is lost, the tickets, uh, present in JIRA, if those 454 00:23:18,410 --> 00:23:22,490 are lost, for some reason you lose that visibility of what happened. 455 00:23:22,640 --> 00:23:23,060 Yes. 456 00:23:23,090 --> 00:23:27,920 Uh, you have to, uh, go back, dig in, uh, put in more efforts to 457 00:23:27,920 --> 00:23:29,270 understand what happened, right? 458 00:23:29,570 --> 00:23:32,000 But your productivity is impacted. 459 00:23:32,360 --> 00:23:37,160 Your ongoing activity of, uh, whatever, uh, ongoing sprint or 460 00:23:37,165 --> 00:23:39,170 whatever it is it's impacted. 461 00:23:39,320 --> 00:23:41,530 It's a direct business impact. 462 00:23:42,240 --> 00:23:46,515 So that's one of the reasons why you need to protect that data and make sure 463 00:23:46,515 --> 00:23:49,395 you can roll back as soon as possible. 464 00:23:49,485 --> 00:23:49,815 Right? 465 00:23:50,085 --> 00:23:53,385 Another impact is basically the reporting structure. 466 00:23:53,595 --> 00:23:59,105 Lot of big teams, they rely on JIRA to, uh, understand what is 467 00:23:59,105 --> 00:24:01,025 going on within their scrum teams. 468 00:24:01,515 --> 00:24:02,785 So that's very critical. 469 00:24:02,985 --> 00:24:05,080 Right now that's one example. 470 00:24:05,230 --> 00:24:08,770 The other example is lot of, uh, customers, they 471 00:24:08,770 --> 00:24:11,320 leverage, uh, JIRA software. 472 00:24:11,320 --> 00:24:16,810 They leverage JIRA service management tool for their HR function, uh, for different, 473 00:24:16,870 --> 00:24:19,360 uh, uh, functions like HR finance. 474 00:24:19,600 --> 00:24:24,730 They also leverage Atlassian apps wherein they store sensitive information. 475 00:24:24,730 --> 00:24:27,640 For example, what we have seen is HR teams. 476 00:24:27,985 --> 00:24:33,175 They onboard, uh, different, uh, employees, uh, in, in, 477 00:24:33,235 --> 00:24:35,005 uh, Jira itself, right. 478 00:24:35,005 --> 00:24:40,585 Or JSM, they, uh, conduct interviews and they store certain, uh, amount 479 00:24:40,585 --> 00:24:45,665 of data employee data into, uh, the JIRA software and JSM tools. 480 00:24:45,665 --> 00:24:46,185 Right. 481 00:24:46,555 --> 00:24:49,375 So that is even more, uh, sensitive data. 482 00:24:49,435 --> 00:24:54,605 And, um, Very impactful for your business, if it it's lost. 483 00:24:54,935 --> 00:24:57,605 Uh, so there are multiple angles to it. 484 00:24:57,905 --> 00:25:03,035 Not only, uh, the, uh, business continuity part of it, but also 485 00:25:03,095 --> 00:25:08,885 how sensitive data, uh, uh, is, is being stored into these systems. 486 00:25:08,975 --> 00:25:11,315 And what if that data is lost? 487 00:25:11,435 --> 00:25:11,675 Right? 488 00:25:11,825 --> 00:25:14,165 So there are different, uh, angles to it. 489 00:25:14,990 --> 00:25:16,880 W. Curtis Preston: so let me ask this question. 490 00:25:16,880 --> 00:25:21,450 So Atlassian obviously has a big business already. 491 00:25:21,450 --> 00:25:23,090 Um, and they have a lot of customers. 492 00:25:23,090 --> 00:25:26,970 Certainly some customers have said, gee, I, I, I agree with 493 00:25:26,970 --> 00:25:29,490 everything that you just said. 494 00:25:29,490 --> 00:25:32,040 What would an Atlassian customer do today? 495 00:25:32,040 --> 00:25:34,350 If they wanted to get any kind of backup of that? 496 00:25:34,350 --> 00:25:35,370 I'll, I'll give that to, to. 497 00:25:38,165 --> 00:25:38,945 Vish Reddy: Yeah today. 498 00:25:39,035 --> 00:25:45,845 Um, so, uh, let back up a little bit, which is Atlassian offers 499 00:25:45,845 --> 00:25:50,685 their products in two deployment, uh, modes, um, on premises. 500 00:25:50,935 --> 00:25:55,565 And cloud, uh, of course they came out their on premises product, you know, they. 501 00:25:58,500 --> 00:26:06,170 most customers when they, uh, who are very, uh, you know, sensitive about their 502 00:26:06,170 --> 00:26:11,130 data backups and so on for on premises systems, they would back up the database. 503 00:26:11,910 --> 00:26:15,180 Uh, typically it's a, MySQL, or a Postgress database. 504 00:26:15,420 --> 00:26:16,500 I think you have choices. 505 00:26:17,070 --> 00:26:21,360 So on premises systems, you would back up their database itself, but 506 00:26:21,600 --> 00:26:24,960 still the problem remains, I think, as you were pointing out, right. 507 00:26:25,680 --> 00:26:28,440 You typically go mess up with one or two things. 508 00:26:28,440 --> 00:26:31,890 You, you know, you don't typically blow up your entire site most of the time. 509 00:26:32,610 --> 00:26:36,840 Uh, now the problem with that, you know, backing up your databases, you do have 510 00:26:36,840 --> 00:26:38,580 point time snapshots of your database. 511 00:26:39,100 --> 00:26:43,830 So if you don't roll that back then you do all the work, which 512 00:26:43,830 --> 00:26:47,970 you've done from the point of time, you know, you roll back to right. 513 00:26:48,030 --> 00:26:48,150 OK. 514 00:26:48,155 --> 00:26:51,170 So that that's the current state of affairs on the, 515 00:26:51,175 --> 00:26:52,200 on premises side of things. 516 00:26:53,010 --> 00:26:58,695 On the cloud what Atlassian provided was a mechanism to do a database export. 517 00:27:00,015 --> 00:27:07,245 Uh, so in their UI today, most customers try to go and press pressing that button. 518 00:27:07,845 --> 00:27:10,215 Unfortunately, that takes a very long time. 519 00:27:10,215 --> 00:27:13,935 Again, depends on your size of your data, uh, your, your tenant, right? 520 00:27:13,965 --> 00:27:17,895 How much of data which you have, uh, if you have a couple of, um, you 521 00:27:17,895 --> 00:27:19,635 know, let's, let's go with gigabytes. 522 00:27:19,635 --> 00:27:22,155 Let's say you have 10 gigabytes of data. 523 00:27:22,685 --> 00:27:25,770 Uh, tickets, attachments, whatnot. 524 00:27:27,120 --> 00:27:30,810 That's gonna take you some time to, uh, back up. 525 00:27:31,110 --> 00:27:33,720 Now, here's the thing, which is really messed up in my, 526 00:27:34,680 --> 00:27:37,440 uh, there's a cloud product. 527 00:27:37,770 --> 00:27:39,260 You gotta take that backup. 528 00:27:39,260 --> 00:27:44,100 You gotta download that your on premises system, and then 529 00:27:44,100 --> 00:27:45,270 you decide what to do with it. 530 00:27:45,300 --> 00:27:49,920 You can put it back into the cloud and, you know, manage different versions. 531 00:27:50,700 --> 00:27:54,750 Um, or you can put it on a, on premises system and manage that. 532 00:27:54,750 --> 00:27:54,930 Right. 533 00:27:55,320 --> 00:27:58,080 But here again, if you wanna go, 534 00:27:58,665 --> 00:28:01,455 W. Curtis Preston: Is there a way to restore it to the cloud. 535 00:28:02,850 --> 00:28:05,340 Vish Reddy: yes, you can restore it to the cloud again. 536 00:28:05,340 --> 00:28:06,390 It's all or nothing. 537 00:28:06,810 --> 00:28:11,220 So if you wanna go back, let's say a month, that means 538 00:28:11,220 --> 00:28:13,710 you've lost a month's of data. 539 00:28:14,280 --> 00:28:18,120 It's not, you know, , it's not like I want this one ticket 540 00:28:18,120 --> 00:28:19,350 or two tickets or this attach. 541 00:28:20,025 --> 00:28:22,125 Um, and it's a lot of manual work by the way. 542 00:28:22,605 --> 00:28:29,205 Um, in the current state of affairs, if your data size is greater than 543 00:28:29,210 --> 00:28:35,835 five gigs compressed, uh, then you gotta go and, uh, you know, open that 544 00:28:36,105 --> 00:28:40,605 file up, split it up into multiple parts and then try uploading. 545 00:28:41,175 --> 00:28:43,785 Uh, so there is a lot of work which you would have to do, 546 00:28:43,890 --> 00:28:44,400 W. Curtis Preston: Hmm, 547 00:28:45,405 --> 00:28:46,005 Vish Reddy: and this is. 548 00:28:46,425 --> 00:28:49,425 Prasanna Malaiyandi: It reminds me of like Salesforce backup and restores. 549 00:28:49,425 --> 00:28:49,665 I know 550 00:28:49,755 --> 00:28:50,355 W. Curtis Preston: It does. 551 00:28:50,355 --> 00:28:50,845 Yeah. 552 00:28:50,895 --> 00:28:53,505 Prasanna Malaiyandi: on right talking about that and just trying to deal with 553 00:28:53,505 --> 00:28:55,245 that seems like a bit of a nightmare vish 554 00:28:57,330 --> 00:29:01,980 Vish Reddy: Actually, I would say, you know, uh, one of our first, uh, prospects. 555 00:29:01,980 --> 00:29:06,090 They're in the travel industry, uh, very different, they're not software. 556 00:29:06,840 --> 00:29:14,520 Uh, they would, uh, log, uh, customer issues, changes to the travel 557 00:29:14,520 --> 00:29:16,840 schedule and so on and in JIRA. 558 00:29:17,580 --> 00:29:21,330 And, uh, they were doing this manually and they were looking 559 00:29:21,330 --> 00:29:27,660 for a solution like, every two. 560 00:29:36,060 --> 00:29:36,580 Hello. 561 00:29:36,960 --> 00:29:39,360 And so they're like, oh, there's too much manual work. 562 00:29:39,510 --> 00:29:42,720 It takes at least five to six hours to just download the data 563 00:29:42,960 --> 00:29:44,040 and then you gotta manage it. 564 00:29:44,580 --> 00:29:45,480 I don't wanna do this. 565 00:29:45,480 --> 00:29:46,560 Can I just offload this to. 566 00:29:47,430 --> 00:29:49,530 Um, I think that was the inspiration. 567 00:29:49,530 --> 00:29:51,330 I would say that was one of the, you know, stories. 568 00:29:51,330 --> 00:29:55,020 I was gonna tell you as to how we said, okay, maybe there's a good problem to go. 569 00:29:56,340 --> 00:29:59,220 W. Curtis Preston: And so the, the, the worry, like, again, going to 570 00:29:59,220 --> 00:30:04,930 your, your travel example, the, the worry would be that you accidentally 571 00:30:04,935 --> 00:30:06,990 delete like just a customer. 572 00:30:07,680 --> 00:30:12,030 You know, you, you just deleted all history for a customer that you've been 573 00:30:12,030 --> 00:30:16,770 managing travel for five years, and then you just deleted that customer. 574 00:30:16,890 --> 00:30:20,220 Your only choice as you were saying is to restore the entire database. 575 00:30:21,435 --> 00:30:23,925 You can't restore just that customer, right? 576 00:30:24,870 --> 00:30:25,680 Vish Reddy: That's correct. 577 00:30:26,160 --> 00:30:30,090 Uh, there is no, you know, pick and choose you it's all or nothing. 578 00:30:30,540 --> 00:30:37,770 Um, one other thing, which is, uh, you important for, uh, to, and lot of people 579 00:30:37,770 --> 00:30:44,940 don't this, uh, which is when you delete something in, in JIRA or confluence. 580 00:30:45,660 --> 00:30:46,590 It is gone. 581 00:30:47,400 --> 00:30:49,080 You cannot get it back. 582 00:30:49,670 --> 00:30:51,570 There is no audit trail for that. 583 00:30:52,095 --> 00:30:53,055 W. Curtis Preston: Really none. 584 00:30:53,610 --> 00:30:54,960 Vish Reddy: I I'll give you another example. 585 00:30:55,755 --> 00:30:57,015 W. Curtis Preston: a recycled bin or anything. 586 00:30:58,530 --> 00:30:58,770 Vish Reddy: okay. 587 00:30:58,770 --> 00:31:01,020 So there are, there is a recycled bin. 588 00:31:01,020 --> 00:31:05,010 If you delete things at a project level, but if you delete things at the 589 00:31:05,130 --> 00:31:08,140 ticket level, there is no recycle bin. 590 00:31:08,160 --> 00:31:09,990 There is no audit log for it. 591 00:31:10,830 --> 00:31:15,390 Last year, I was working for, again, this was another data point, 592 00:31:15,390 --> 00:31:19,710 which we had, I was working for Agari data, uh, email security. 593 00:31:20,400 --> 00:31:23,190 We got acquired by a company called help systems. 594 00:31:23,940 --> 00:31:31,020 And there were a lot of upset employees at Agari who did not 595 00:31:31,390 --> 00:31:33,660 like, you know, what was going on. 596 00:31:34,500 --> 00:31:34,800 And. 597 00:31:36,315 --> 00:31:42,135 I, we would use JIRA for our, uh, software development, project management and so on. 598 00:31:42,615 --> 00:31:47,805 I started noticing tickets disappearing, and I'm like, I'm pretty sure I saw this. 599 00:31:48,315 --> 00:31:51,735 I can see AGA 129. 600 00:31:52,155 --> 00:31:54,315 I saw it yesterday, but it's not there in the system. 601 00:31:54,320 --> 00:31:55,005 Where did it go? 602 00:31:55,195 --> 00:31:59,565 I go asking around and nobody knows because there is no trace of it anymore. 603 00:32:00,195 --> 00:32:00,675 W. Curtis Preston: Wow. 604 00:32:02,235 --> 00:32:02,865 That's not good. 605 00:32:04,470 --> 00:32:06,240 Vish Reddy: And that is the state of affairs today. 606 00:32:07,180 --> 00:32:07,740 W. Curtis Preston: Right. 607 00:32:08,690 --> 00:32:09,040 Wow. 608 00:32:10,020 --> 00:32:14,220 Sanket Parlikar: So if, if I may add right, uh, Curtis, uh, how, how, 609 00:32:14,340 --> 00:32:17,820 uh, Backup and restore really works. 610 00:32:18,120 --> 00:32:22,620 Uh, 10 years ago or 20 years ago when you started, right? 611 00:32:22,920 --> 00:32:25,920 Uh, the focus used to be on disaster recovery. 612 00:32:26,190 --> 00:32:30,060 Uh, 30 years, about 20 years ago, it was all about disaster recovery. 613 00:32:30,300 --> 00:32:32,940 Meaning my system is up and running OnPrem system. 614 00:32:33,120 --> 00:32:34,650 Something goes, uh, bad. 615 00:32:34,650 --> 00:32:39,750 I just rolled back, uh, probably, uh, five days older, a snapshot things work. 616 00:32:39,750 --> 00:32:40,080 Right. 617 00:32:40,230 --> 00:32:46,440 And I'm okay to give up some of the data now, uh, Uh, with cloud apps, 618 00:32:46,440 --> 00:32:50,970 basically the situation is like, Hey, I'm not ready to give up all of my data. 619 00:32:51,390 --> 00:32:54,840 Uh, I just want to, uh, pick, choose what I want to restore. 620 00:32:54,840 --> 00:32:55,170 Right. 621 00:32:55,410 --> 00:32:58,740 Uh, because, uh, yeah, there are a number of reasons. 622 00:32:58,940 --> 00:33:02,010 I, I, uh, accidentally deleted something, right. 623 00:33:02,220 --> 00:33:05,310 Uh, why do I roll back, uh, entire tenant? 624 00:33:05,550 --> 00:33:08,910 I, uh, I had a malicious incident where in someone. 625 00:33:09,460 --> 00:33:11,530 Deleted only subset of data. 626 00:33:11,590 --> 00:33:13,090 Why do I roll back completely? 627 00:33:13,270 --> 00:33:13,540 Right. 628 00:33:13,660 --> 00:33:16,180 So these are the evolving scenarios. 629 00:33:16,185 --> 00:33:18,910 Now, malicious actors being the biggest one. 630 00:33:19,300 --> 00:33:25,260 As we talk about security, that's the biggest threat evolving for any SaaS app. 631 00:33:25,935 --> 00:33:29,025 W. Curtis Preston: Yeah, I, I, we actually had a discussion on the 632 00:33:29,030 --> 00:33:36,105 previous, uh, podcast that, you know, I, I just sort of had this realization 633 00:33:37,095 --> 00:33:42,285 that, you know, when I started, uh, which for the record was 30 years ago. 634 00:33:43,485 --> 00:33:43,785 when I 635 00:33:43,890 --> 00:33:44,970 Prasanna Malaiyandi: was being kind to you. 636 00:33:45,105 --> 00:33:49,905 W. Curtis Preston: But what I started, the, the, I will agree that the 637 00:33:49,905 --> 00:33:53,355 primary thing that we were trying to solve was hardware failure. 638 00:33:53,940 --> 00:33:54,390 Right. 639 00:33:54,540 --> 00:33:58,800 Whether it was, it failed because of a disaster or failed because we were running 640 00:33:58,800 --> 00:34:00,900 servers on a single hard drive, right? 641 00:34:00,900 --> 00:34:04,350 No raid, no, nothing, just a hard drive. 642 00:34:04,890 --> 00:34:08,850 And, um, I mean, if there were multiple hard drives, we were just using all of 643 00:34:08,850 --> 00:34:15,400 them as individual drives, but, and, and, and between the, the, the, um, the 644 00:34:15,400 --> 00:34:21,610 change in the technology with everybody using, uh, raid and things like that. 645 00:34:21,610 --> 00:34:24,280 And the change in SaaS providers, Dr. 646 00:34:24,280 --> 00:34:26,260 Is not my problem, right. 647 00:34:26,410 --> 00:34:28,990 With Atlassian with, with JIRA, Dr. 648 00:34:28,990 --> 00:34:30,010 Is not my problem. 649 00:34:30,010 --> 00:34:33,580 That's their problem that we all agree that it is their problem to 650 00:34:33,585 --> 00:34:36,190 get the service up and running. 651 00:34:36,190 --> 00:34:37,720 That is what I'm paying them for. 652 00:34:38,200 --> 00:34:38,860 But. 653 00:34:40,180 --> 00:34:44,700 Due to the, to the change in, in the way technology has, has 654 00:34:44,700 --> 00:34:47,580 evolved the number one reason. 655 00:34:47,640 --> 00:34:52,230 In fact, I, I would argue that like it's like 99.9%. 656 00:34:52,710 --> 00:34:59,010 The number one reason for a restore is now humans, not hardware. 657 00:34:59,010 --> 00:35:00,090 And Dr. 658 00:35:00,390 --> 00:35:03,060 Uh, I mean, it's still, there are still disasters, but the 659 00:35:03,060 --> 00:35:04,980 disasters are caused by humans. 660 00:35:04,980 --> 00:35:06,390 They are they're caused by. 661 00:35:07,050 --> 00:35:11,310 Um, you know, ransomware attacks and other malicious attacks, 662 00:35:11,310 --> 00:35:12,780 like what Vish was talking about. 663 00:35:13,260 --> 00:35:17,700 So I would, I don't know if this was the point you were making, but I'll 664 00:35:17,700 --> 00:35:21,030 make it if you weren't making it and I'll agree if you were making it. 665 00:35:21,030 --> 00:35:21,870 And that is that. 666 00:35:22,950 --> 00:35:26,850 You have, if you're designing a backup product for this world, you have to 667 00:35:26,850 --> 00:35:31,080 design it with that, um, in mind, right? 668 00:35:31,130 --> 00:35:36,650 Since the primary reason that we're going to be doing restores is dumb stuff. 669 00:35:38,060 --> 00:35:38,330 right. 670 00:35:39,230 --> 00:35:41,720 We need to make the restore of dumb stuff. 671 00:35:42,230 --> 00:35:45,920 Uh, the, the easiest thing that the product can do. 672 00:35:47,405 --> 00:35:50,615 Did did I say the same thing you said, but in a whole lot more words. 673 00:35:50,960 --> 00:35:51,620 Sanket Parlikar: Exactly. 674 00:35:51,635 --> 00:35:51,875 W. Curtis Preston: Okay. 675 00:35:52,760 --> 00:35:53,840 Prasanna Malaiyandi: Curtis does that a lot 676 00:35:54,230 --> 00:35:56,975 W. Curtis Preston: I've literally made a career of doing just that. 677 00:35:57,425 --> 00:36:02,495 Um, so, so the, the companies knew, in fact, I, my understanding is that, 678 00:36:02,500 --> 00:36:06,525 you know, you're, you're, you're just now launching what, are you 679 00:36:06,525 --> 00:36:09,135 handling all of Atlassian products? 680 00:36:09,135 --> 00:36:10,065 I'll give that to Vish. 681 00:36:12,795 --> 00:36:17,535 Vish Reddy: we got started in April, uh, for five months in roughly 682 00:36:17,805 --> 00:36:23,195 speaking, um, version one or MVP is gonna be covering JIRA Software. 683 00:36:24,395 --> 00:36:34,295 Um, and then we have a robust roadmap, uh, I think next would be Jira SM, Confluence. 684 00:36:36,495 --> 00:36:36,795 SM 685 00:36:38,525 --> 00:36:40,850 Prasanna Malaiyandi: For your MVP or version one? 686 00:36:41,790 --> 00:36:42,960 Could you talk a little bit? 687 00:36:42,990 --> 00:36:44,910 I'm definitely sure you're doing the backups. 688 00:36:44,910 --> 00:36:45,810 What about from the restores? 689 00:36:45,810 --> 00:36:50,130 I know earlier you talked about today with what you get with, uh, JIRA 690 00:36:50,135 --> 00:36:54,030 today or Atlassian today, it's sort of, you get everything as a backup 691 00:36:54,240 --> 00:36:56,100 once every two days at most, right? 692 00:36:56,100 --> 00:36:57,600 And then you have to restore everything back. 693 00:36:58,050 --> 00:37:00,360 What sort of restores do you handle? 694 00:37:01,770 --> 00:37:02,430 Vish Reddy: Great question. 695 00:37:02,430 --> 00:37:05,290 No, you know, what's the point of doing backup without being 696 00:37:05,290 --> 00:37:06,110 able to restore back right? 697 00:37:06,110 --> 00:37:08,760 Prasanna Malaiyandi: Curtis and I were just talking about that yesterday. 698 00:37:10,725 --> 00:37:11,415 W. Curtis Preston: No one cares. 699 00:37:11,415 --> 00:37:12,575 If you can back up Vish 700 00:37:13,920 --> 00:37:14,270 Vish Reddy: So. 701 00:37:17,525 --> 00:37:41,025 Which, and choosing that one thing or two things, or, you know, again, being very 702 00:37:41,025 --> 00:37:42,825 granular about what you can restore by. 703 00:37:43,275 --> 00:37:45,005 So that is part of our MVP. 704 00:37:45,495 --> 00:37:49,830 We back up every day, every 24 hours, automatic backup, 705 00:37:49,950 --> 00:37:51,360 remember this is insurance, right? 706 00:37:51,810 --> 00:37:54,450 You just buy it and you forget about it till you need it. 707 00:37:54,750 --> 00:37:55,140 Of course. 708 00:37:55,590 --> 00:38:00,540 Um, and so when you need it, you can go back in, you can go pick the specific 709 00:38:00,540 --> 00:38:04,950 day from which you want that backup, uh, or that, you know, piece of data, maybe 710 00:38:04,950 --> 00:38:06,450 it's a ticket, maybe it's an attachment. 711 00:38:06,930 --> 00:38:10,980 Um, and then you can go and filter out, uh, and say, okay, I want this 712 00:38:11,380 --> 00:38:12,540 specific thing to be restored back. 713 00:38:13,230 --> 00:38:13,890 That's what we do. 714 00:38:14,490 --> 00:38:18,630 There are lot more use cases, which are there as an example, something which we're 715 00:38:18,630 --> 00:38:25,620 not doing in the MVP, lot of customers have multiple different sites or tenants. 716 00:38:25,920 --> 00:38:29,610 Uh, you know, you control five different tenants. 717 00:38:29,610 --> 00:38:31,140 You may move things around. 718 00:38:31,830 --> 00:38:33,750 It's sort of a data migration use case. 719 00:38:33,750 --> 00:38:36,840 So to speak, you're backed up something in from one place. 720 00:38:36,840 --> 00:38:38,040 You wanna put it into another place. 721 00:38:38,460 --> 00:38:40,620 Um, that's something that you'll be doing in the future. 722 00:38:41,100 --> 00:38:43,335 Uh, uh, that's not part of MVP today. 723 00:38:43,335 --> 00:38:45,825 What we do is whatever you back up from a given tenant, you 724 00:38:45,825 --> 00:38:47,145 can put it back into the same. 725 00:38:48,345 --> 00:38:52,155 Now JIRA to the earlier point, which we were making. 726 00:38:52,160 --> 00:38:53,385 It is a pretty complex. 727 00:38:53,385 --> 00:38:54,765 The data structure is pretty complex. 728 00:38:55,395 --> 00:39:01,605 So there is actual data which consists of, uh, you know, uh, comments, potentially 729 00:39:01,605 --> 00:39:02,925 description of what the ticket is. 730 00:39:02,930 --> 00:39:03,375 And so on. 731 00:39:03,585 --> 00:39:08,085 And attachments, attachments could be drawings, could be code snippets, 732 00:39:08,865 --> 00:39:11,595 you know, various or zoom recordings. 733 00:39:11,865 --> 00:39:14,905 Lot of people add in zoom recordings have seen into the ticket itself. 734 00:39:15,510 --> 00:39:16,890 Uh, that's part of your data. 735 00:39:16,890 --> 00:39:19,590 Then there is a whole bunch of configuration configuration here could 736 00:39:19,590 --> 00:39:24,780 be workflows, could be, you know, um, you know, different screens would show 737 00:39:24,780 --> 00:39:26,820 up, uh, you know, to different users. 738 00:39:27,330 --> 00:39:31,810 Um, and so we back up both and we can restore both those things back. 739 00:39:32,445 --> 00:39:38,325 Uh, uh, we, for the MVP, we are, we are able to restore back 740 00:39:38,535 --> 00:39:40,285 everything on the data side of this. 741 00:39:40,515 --> 00:39:43,845 Uh, anything you do with the issues, you can restore that back, uh, on 742 00:39:43,850 --> 00:39:47,895 the configuration side, uh, we've started off with screens and workflows 743 00:39:47,895 --> 00:39:51,205 because those, those to be the most important things based on ours. 744 00:39:51,675 --> 00:39:55,485 And then, uh, you know, over the course of the next two, three 745 00:39:55,485 --> 00:40:00,125 weeks, uh, we'll be adding in more configuration elements to, uh, to be. 746 00:40:00,645 --> 00:40:02,505 Prasanna Malaiyandi: I'm glad you covered the config elements because 747 00:40:02,505 --> 00:40:05,295 that's actually, one of the things I was gonna ask is, especially with SaaS 748 00:40:05,295 --> 00:40:08,835 services, people sometimes forget about like the settings and configs, right. 749 00:40:08,840 --> 00:40:12,465 That's also critical to capture in terms of backup and restore 750 00:40:12,465 --> 00:40:13,755 because someone makes a change. 751 00:40:13,755 --> 00:40:15,015 Hey, I wanna be able to restore that. 752 00:40:15,315 --> 00:40:18,195 Or like you said, Vish workflows, people don't necessarily think of 753 00:40:18,200 --> 00:40:21,585 that as like a JIRA ticket, but it's still important for the business. 754 00:40:23,025 --> 00:40:26,565 Vish Reddy: One of the learnings which we, uh, had was. 755 00:40:27,000 --> 00:40:32,220 Uh, you know, a lot of companies go through SOC2 compliance audit right now. 756 00:40:33,000 --> 00:40:37,950 So these companies also have JIRA as their change management system, which 757 00:40:37,955 --> 00:40:47,880 tells you, Hey, we, this, this point, this is what's are just about to embark 758 00:40:48,240 --> 00:40:50,190 on getting ourselves SOC2 compliant. 759 00:40:50,730 --> 00:40:56,445 And in talking to the auditor, they were like, I didn't know that, uh, you know, 760 00:40:56,445 --> 00:41:01,065 you, if you delete some tickets, they can, there is no sign of it anymore. 761 00:41:01,365 --> 00:41:04,325 That's a big problem for 762 00:41:13,665 --> 00:41:14,055 W. Curtis Preston: Yeah, 763 00:41:14,295 --> 00:41:16,455 Vish Reddy: this is interesting, this, you know, as we're. 764 00:41:16,725 --> 00:41:20,985 W. Curtis Preston: honestly, that that's a, that's a major hole for JIRA, but 765 00:41:20,985 --> 00:41:22,605 that's a problem for them to solve. 766 00:41:22,785 --> 00:41:24,735 Like they, they need to have that audit log. 767 00:41:24,735 --> 00:41:25,065 Right? 768 00:41:25,485 --> 00:41:29,775 Uh, the, the, the story that you mentioned earlier, um, it, it should, 769 00:41:30,765 --> 00:41:35,535 you should not be able to just go in and delete tickets without record. 770 00:41:35,805 --> 00:41:36,195 Right. 771 00:41:36,255 --> 00:41:39,435 Um, we should be able to go, oh, it was Steve. 772 00:41:39,735 --> 00:41:42,885 Steve is the one who deleted all the tickets that he 773 00:41:42,885 --> 00:41:43,965 didn't want you to know about. 774 00:41:43,965 --> 00:41:44,325 Right. 775 00:41:44,655 --> 00:41:49,605 Um, but so sort of one final question, cuz we're, we're getting short on 776 00:41:49,605 --> 00:41:53,355 time, uh, earlier, I think it was Vish that mentioned that currently 777 00:41:53,595 --> 00:41:57,255 the, the, the built-in product, you can only back up every other day. 778 00:41:57,255 --> 00:41:59,475 How is it that you're able to back up every day? 779 00:41:59,475 --> 00:42:01,425 Is it because of the, the partnership that you. 780 00:42:01,802 --> 00:42:02,342 Vish Reddy: Great question. 781 00:42:02,342 --> 00:42:02,822 So. 782 00:42:03,242 --> 00:42:08,552 Uh, if you use the backup functionality, which Atlasian gives you, which is 783 00:42:08,552 --> 00:42:13,202 your entire database backup, then you can do it only every 48 hours. 784 00:42:13,652 --> 00:42:17,642 Uh, if you're backing up attachments and so on, what we're doing is different. 785 00:42:17,852 --> 00:42:20,312 We are using that APIs. 786 00:42:20,732 --> 00:42:24,932 We are going, and each of their tickets, uh, we're being very granular, right? 787 00:42:24,932 --> 00:42:27,902 And we're not getting the entire data set in one shot. 788 00:42:28,022 --> 00:42:29,942 We're going and picking everything one at a. 789 00:42:30,737 --> 00:42:31,597 And backing it up. 790 00:42:31,867 --> 00:42:34,007 Now, here is where things are. 791 00:42:34,307 --> 00:42:38,907 Um, and I think most people are familiar with this is, your first backup is gonna 792 00:42:38,907 --> 00:42:47,057 take a long because of are much shorter. 793 00:42:47,177 --> 00:42:47,537 Why? 794 00:42:47,597 --> 00:42:49,007 Because it's changes. 795 00:42:49,847 --> 00:42:50,297 Now. 796 00:42:51,257 --> 00:42:55,907 If we were pulling down the entire database, every time it's not cost 797 00:42:55,907 --> 00:42:58,367 effective and, you know, takes. 798 00:42:59,372 --> 00:43:01,922 W. Curtis Preston: Because you're using APIs and you're doing incremental backup. 799 00:43:01,922 --> 00:43:02,612 That makes sense. 800 00:43:02,642 --> 00:43:03,062 Cool. 801 00:43:03,722 --> 00:43:05,712 Well, listen, uh, we might have lost sanket. 802 00:43:05,732 --> 00:43:10,202 It, um, you know, his, his, his bits are flying up in the internet and coming 803 00:43:10,202 --> 00:43:12,032 back down all the way from India to here. 804 00:43:12,272 --> 00:43:14,042 I, I says he just messaged. 805 00:43:14,042 --> 00:43:15,182 He's not able to hear anymore. 806 00:43:15,582 --> 00:43:18,042 I'm gonna, I'm gonna thank you both for doing this. 807 00:43:18,092 --> 00:43:21,672 Sanket can't hear us anymore, but I'll, I'll thank him as well. 808 00:43:21,942 --> 00:43:24,342 And, um, and, uh, thanks a lot. 809 00:43:24,342 --> 00:43:26,982 I, I, I wish you the best of luck on this new company. 810 00:43:28,407 --> 00:43:29,457 Vish Reddy: Uh, thank you very much. 811 00:43:29,457 --> 00:43:35,427 Uh, uh, and for hosting us out here today, uh, it was great, uh, you know, catching 812 00:43:35,427 --> 00:43:37,107 up with you and also sharing what we've. 813 00:43:37,842 --> 00:43:41,052 Uh, you know, uh, we would love for you guys to try out our 814 00:43:41,052 --> 00:43:43,422 product at some point, um, just. 815 00:43:44,217 --> 00:43:53,307 W. Curtis Preston: Well, well, I I do happen to know a certain, 816 00:43:53,367 --> 00:43:56,067 uh, SaaS company that uses JIRA. 817 00:43:56,337 --> 00:43:59,787 I'm just saying, and I know some people there and I think you do too, 818 00:43:59,817 --> 00:44:04,767 but that's, that's a, that's your own problem to solve, uh, and Prasanna again. 819 00:44:04,797 --> 00:44:06,157 Great questions as always. 820 00:44:06,252 --> 00:44:08,482 Prasanna Malaiyandi: I try and thanks Vish and Sanket. 821 00:44:08,502 --> 00:44:08,802 Yeah. 822 00:44:08,802 --> 00:44:09,702 Great catching up. 823 00:44:09,882 --> 00:44:11,532 Uh, V the one question I was gonna ask. 824 00:44:11,537 --> 00:44:15,132 So if people want to try out the product or anything else, I know 825 00:44:15,132 --> 00:44:17,292 that the website is going live soon. 826 00:44:17,292 --> 00:44:22,122 By the time this podcast gets released, do they just go onto the website, um, 827 00:44:22,422 --> 00:44:26,982 to access and they can request a free trial or whatever needs to be done. 828 00:44:26,982 --> 00:44:28,182 Everything's gonna be available on the. 829 00:44:30,187 --> 00:44:31,057 Vish Reddy: Great question. 830 00:44:31,237 --> 00:44:34,537 Uh, our product is gonna be available on the Atlassian marketplace. 831 00:44:36,267 --> 00:44:37,317 Couple of clicks. 832 00:44:37,467 --> 00:44:38,487 You can get started. 833 00:44:38,637 --> 00:44:39,807 There's a free trial there. 834 00:44:40,047 --> 00:44:41,937 Uh, you know, it's all automated. 835 00:44:42,177 --> 00:44:48,207 Uh, literally you can start your trial of the software within five minutes 836 00:44:48,207 --> 00:44:54,717 or maybe less and you get 30 days backup, restore, unlimited, whatever. 837 00:44:54,927 --> 00:44:56,037 Uh, yep. 838 00:44:56,327 --> 00:44:58,377 All provision through Atlassian. 839 00:44:58,377 --> 00:44:58,777 W. Curtis Preston: Nice. 840 00:44:58,777 --> 00:44:59,337 I like it. 841 00:44:59,877 --> 00:45:00,327 All right. 842 00:45:00,332 --> 00:45:05,457 Well, um, again, thanks to our listeners and remember to subscribe 843 00:45:05,667 --> 00:45:07,587 so that you can restore it all.