What was the reason to loose DNS records when instance type changed ? 😯

@krish

21 күн бұрын

everything can go wrong.. will go wrong. (murphy's law)

@rukshannet

21 күн бұрын

@@krish at the wrong time too... 🙃

Quote Of The Day ~ "There is no rule saying all problems you have to solve"! ~ this quote reduces my problem-solving ego Thanks for sharing. anyway Krish I wouldn't say I like black background colour.

Thank you Krish for sharing ! appreciate if you could share what went wrong with the DNS.

Thanks a lot for sharing ♥

Got a mini heart attack my self, while listening to you explaining that database file missing part.. 😅

Thanks for sharing that experience. We need more videos like this ayye. More real world scenarios, situation handling.

Bro, this content is straight fire! Honestly, it's the kind of stuff we crave. You've got mad experience and insights that are pure gold. Keep it coming, man!

Love these contents. There's a lot to learn from you. Please do more experience-based videos like these; they will be really helpful in enhancing our understanding, practical skills,best practises and ability to face real situations in different manners

Thank you for your valuable time and your advices ❤

Thanks krish ! I'm an undergraduate I learned lot of things from you. keep this stuffs coming!!

Superb content.

what a experience

Good one sir

I picture the whole seen.. literally 😂😂😂... with the faces..

@krish

22 күн бұрын

😂

Bro better things is, when system run time , similar backup run . but it will be costly . ex : when prod environment down time, if we can easily replace with UAT or Pre-prod env🎉 actually we need plan for that. if we already prepared some Good documentation for the how do we faced like that environment or how do we immediately do solution 🎉

@krish

22 күн бұрын

Love this. but having UAT to replace prod is not a good option. though I cannot disclose customer architectures we do have multiple replica servers with real time sync and DR in place. incase we hit no return wall we had multiple recovery options.

@savindupasintha

22 күн бұрын

@@krish thats good point. so better thing is pre ready the snapshots and good user guide a to ready for like that critical situation. also if we can run different region vs our servers in aws, so time easily we can remap the system loads.

Lol. Where are the processes of so-called legendary IT companies? Does this mean, from the outside have various so-called certifications (ISO, ITIL bla bla) but in practice, nothing is applied? where is change management where is CAB approval before doing production change? where is the backup and recovery plan? for you are all these just theories? disciplinary actions should be taken against you if you are working in a right company.

@krish

22 күн бұрын

Thank you for the comment / question / concern. if you watched the video carefully you find all the answers inside the video. but since you pointed let me to summarize. I explained 2.5 hours process in 15 minutes. :) 1. This has nothing to do with a legendary IT company you assume :) 2. I did not explained every discussion / approval / calls happen during the process because those are not relevant and wanted to explain technical side of it as processes are different company to company. so its not relevant to wider audience. here if you felt I just jump and restart a prod server on my own will then I am sorry, it my bad of explaining. it was not like that. it was collective approved decision to proceed with formal in advance notices. also I mentioned some of approvals I had to made the change for 48 hours. we always have documentation followed by every verbal agreement to make sure we have record. 3. I explained the recovery options I had and backup strategies I took. probably you missed that part in the video :) anyway thank you raising your opinion.