Podcasts about runbook

The latest disaster recovery statistics reveal that modern businesses still face costly interruptions due to a variety of threats, ranging from ransomware attacks to sudden hardware failures. The monetary costs of disasters and outages can be significant. According to results from Uptime Institute's "Annual Outage Analysis 2023" survey, 25% of respondents reported that their latest outage incurred more than $1 million in direct and indirect costs. In addition, 45% reported that the cost of their most recent outage ranged between $100,000 and $1 million. Another research report reveals that just over half of organizations have disaster recover plans and around 7% of organizations never test their disaster recovery plans. It was a real pleasure having Sagi Brody, Co-Founder and CTO at Opti9 on the podcast to shed light on the various aspects of disaster recovery and how to do it well.Time Stamps00:02 -- Introduction00:54 -- Disaster Recovery Statistics and Guest Introduction03:08 -- Guest's Professional Highlights04:40 -- Overview of Disaster Recovery09:12 -- How do you ensure that the disaster recovery infrastructure does not become the next security incident?11:51 -- Disaster Recovery Best Practices15:23 -- Around 7% of organizations never test their disaster recovery plan. Why is that the case? Why wouldn't organizations want to ensure that whatever they have documented whatever they have planned actually works?19:49 -- How effective are tabletop exercises in the context of rehearsing for disaster recovery? Should organizations be doing more than tabletop exercises?22:09 -- Disaster Recovery and Outsourcing25:09 -- Final ThoughtsMemorable Sagi Brody Quotes/Statements"When you think of backups, I like to think of the word RECOVER. When you think of disaster recovery, I like to think of the word RESUME, you're not restoring data, you're resuming your business operations after a disruption.""I think one of the biggest mistakes that people make is they sort of build their entire production infrastructure, or their application, get it all up and running, make it perfect. And then later on, they want to focus on disaster recovery.""Imposing disaster recovery strategy on an already built, let's say, application is much more difficult than having resilience be part of your thought process as you go along building your production environment.""We need Runbooks (or Playbooks) for what we do during a disaster. Not only that, but we need Runbooks for different types of disasters. If we need to fail over one application versus our entire environment, we need a separate Runbook for testing.""Today, a lot of people have their applications highly integrated with third party SaaS platforms. So let's be sure that when we test our disaster recovery infrastructure, we're testing the applications, we're not poisoning our production data sitting somewhere else inadvertently.""You have to be super careful when making decisions on what platforms, what vendors, what software you're using to build your applications and your infrastructure. When you make those decisions, you have to weigh them against your resilience framework and your security framework."Connect with Host Dr. Dave Chatterjee and Subscribe to the PodcastPlease subscribe to the podcast, so you don't miss any new episodes! And please leave the show a rating if you like what you hear. New episodes release every two weeks. Connect with Dr. Chatterjee

Recent IDC findings show only 1 in 4 organizations are ready to adequately prevent and respond to a disruptive event. Whether that's a natural disaster destroying servers and infrastructure, a mouse chewing through the wires or a ransomware attack, companies need to be able to anticipate, protect, withstand and recover quickly. No matter the industry, every company needs a comprehensive, strong cyber resiliency strategy. But where does one start? How do businesses remove the siloes that exist between departments and align its leaders?Listen as experts discuss the history of cyber resilience and share their insight on how companies can best plan for the next ‘cybergeddon.' 

Embracing automation in distributed systems is key for reaching scale and efficiency. This week we talk to Jake Cohen about runbook automation, what it means for teams, and how it creates opportunities for automated diagnostics.

James is back from the SQL Bits conference! We talk SQL Bits, Device management on-prem v cloud and much more including UK fuel prices, and see if you can count the number of times James had to receive some reverse word treatment. James Storr - twitter.com/CarryOnCloud John Lunn - twitter.com/jonnychipz Dan Stradling - twitter.com/stradderss #cloudsecurity #cloudtechnology #microsoftcloud #podcast #techpodcast

Nishant interned at Intel and Sprint, He authored a book that's on kindle or in print. Nishant has worked at Google, Uber, and Nike, Now see what's behind Nishant's psyche! Privacy by Design available on Manning Publications 35% off code: podaizen21

John is back! With the current global events, we talk security and view on what it means to us from the technology sectors we currently work within. James Storr - twitter.com/CarryOnCloud John Lunn - twitter.com/jonnychipz Dan Stradling - twitter.com/stradderss #cloudsecurity #cloudtechnology #microsoftcloud #podcast #techpodcast

While John is away, we take the opportunity to discuss the SQL Bits Data Conference with special guest Emma Dolling. The conference is happening 8-12 March 2022 at the London Excel Centre, you can attend virtually or in-person. SQL Bits Conference Twitter - https://twitter.com/SQLBits SQL Bits Conference - https://sqlbits.com/ James Storr - https://twitter.com/CarryOnCloud Emma Dolling - https://twitter.com/Dolled_up_data Dan Stradling - https://twitter.com/stradderss https://twitter.com/M365Summit

In this episode we discuss the rise in enterprise scale landing zones, the importance of keeping your cloud platform in check, using policy guide rails to ensure your business is kept accountable for its cloud resources, and to avoid needlessly burning money all whilst ensuring any security and compliance requirements can be adhered to. ------------------- Silver Linings Runbook - twitter.com/slrpodcast James Storr - twitter.com/CarryOnCloud Dan Stradling - twitter.com/stradderss John Lunn - twitter.com/jonnychipz

In this episode we discuss cloud data, migrating SQL and other database platforms, combining completely different data sources, and how big data is going to be shaping the future of business. ------------------- Twitter Links Silver Linings Runbook - twitter.com/slrpodcast James Storr - twitter.com/CarryOnCloud Dan Stradling - twitter.com/stradderss John Lunn - twitter.com/jonnychipz

In this weeks episode we talk about the why's and why nots about migrating to the cloud, with many compelling reasons both for and against for small and large technology scenarios, and everything in-between.

In this episode we take on the subject of how relevant training, qualifications and certifications are in the past and present times. ------------------- Twitter Links Silver Linings Runbook - twitter.com/slrpodcast James Storr - twitter.com/CarryOnCloud Dan Stradling - twitter.com/stradderss John Lunn - twitter.com/jonnychipz ------------------- A handful of training providers to get you started Microsoft Learn - learn.microsoft.com Pluralsight - pluralsight.com QA - qa.com Udemy - udemy.com LinkedIn Learning - linkedin.com/learning

Our very first episode introducing you to the team, technology careers and the sort of topics you can expect from future episodes.

This week, Rob Reynolds, the founder and CEO of Chocolatey Software, is joining the podcast!   Rob is a developer-turned-founder who has been involved with several highly successful open source projects related to automation in the Windows ecosystem. He has over 10 years of experience in infrastructure automation, modern automation approaches, and agile methodologies. Most of all, Rob strives for simplicity and automation with low-maintenance solutions that solve customer needs.   In this episode, Rob is speaking all about Chocolatey Software, his solution for a universal package manager for Windows. Chocolatey makes complex tasks simple by easily handling all aspects of package management within the Windows software management ecosystem and works with all existing software installation technologies like MSI, NSIS, InnoSetup, etc. Chocolatey also integrates with all existing infrastructure management and RMM tools and is trusted by hundreds of organizations to manage software across their servers and desktops.   Rob shares about the current benefits of using Chocolatey, the origin story of Chocolatey, the next version of the software, his experience moving from Chief Architect to CEO, tips and advice for leadership growth and development, and much more!   Topics of Discussion: [:14] About The Azure DevOps Podcast, Clear Measure, and Jeffrey's offer to speak at virtual user groups. [1:22] Jeffrey is looking to hire an apprentice! If you, or anyone you know, loves to code and wants to pursue software engineering, apply today! [2:09] Be sure to check out the new video podcast, Architect Tips. [2:17] About today's episode with  Rob Reynolds. [2:27] Jeffrey welcomes Rob to the podcast. [4:09] An overview of Chocolatey: what it does, its origin story, and why you may want to give it a try! [8:02] How many community packages are in the Chocolatey catalog? [10:25] Rob shares some examples of how people are using Chocolatey packages and offshoot projects that have branched off of Chocolatey. [13:53] All about the system admin side of Chocolatey and why system admins might want to check it out! [21:45] A word from The Azure DevOps Podcast's sponsor: Clear Measure. [22:15] How Chocolatey makes everything easier. [24:27] Why was the old-style Runbook process originally put into place? How and why have things become automated since? [27:45] About RoundhousE, the professional database chance and versioning management tool that Rob authored. [31:45] What led Rob to make the shift from Chief Architect to CEO? What was the experience like? [39:40] The current open job positions that are available at Chocolatey. [40:48] Rob reflects on his career journey and growth from Chief Architect to CEO. [41:09] About one of Chocolatey's core values (growth) and Rob's recommendations for personal and professional growth. [43:02] What's coming in the next version of Chocolatey! [48:40] Jeffrey thanks Rob for joining the podcast.   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo's Youtube Jeffrey Palermo's Twitter — Follow to stay informed about future events! Chocolatey Software Boxstarter Windows Remix Azure Pipelines Puppet RoundhousE Redgate DbUp The Chuck Norris Framework (Uppercut, Dropkick, etc.) Ruby | Puppet EntreLeadership The Craig Groeschel Leadership Podcast The Andy Stanley Leadership Podcast   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

In this Episode, a follow up to Episode 71. The teams walks through the process of running Microsoft 365 DSC in Azure Automation. What is MicrosoftDSC? Microsoft365DSC is an Open-Source initiative hosted on GitHub, lead by Microsoft engineers and maintained by the community. It allows you to write a definition for how your Microsoft 365 tenant ...continue reading "Episode #74 – Using Microsoft DSC as a runbook in Azure Automation"

Trenerka biegania, promotorka aktywnego stylu życia Ada Palka właśnie wydała Runbook. W podcaście opowiada o swojej sportowej drodze, o tym, że jest trzecim pokoleniem w rodzinie po krakowskiej AWF oraz o swoich ulubionych ćwiczeniach. Jak zacząć trenować i wytrwać? 

SysOps 4 Life What is SysOps? SysOps vs DevOps SysOps Mantra   - Document   - Repeatable process   - Runbook   - Smooth operator Systems Operations   - Clusters   - Operating System patching   - Operating System hardening   - Ports, firewalls, and permissions   - Resillience and redundancies Chaos Engineering   - Netflix   - Break your systems     -- Safe ways to practice     -- Remove server from load balancers     -- Setup test/performance environment     -- Plan for regular business day     -- Notify your clients Backup Plan   - Have a backup   - Restore from backup   - Automate backups (and restoring)   - Gameplan for failure Know Your Systems   - What is behind the stack   - Start/Stopping/Managing services   - Monitoring more than disk and CPU Certs   - AWS Certified SysOps Administrator   - Microsoft Certified Solutions Expert   - RedHat Certified Engineer

With the explosive growth of people using, and contributing to, open source projects over the last decade, more and more of us are spending their time reading, writing, and understanding documentation. Heroku's Dev Center is the central hub of documentation for Heroku, covering everything from getting started, to how Heroku works, to extending the platform. It acts as a manual for the entire platform, spanning an enormous number of topics and tools. Stephen Barlow, lead strategist for Dev Center, joins Heroku designer / developer Charlie Gleason to discuss why good documentation is so important—from some of the common challenges you and your team might face while writing them, to advice for rationalising and improving your documentation workflow. Tune in to learn why good docs aren't just good—they're great. Links from this episode Heroku Dev Center Heroku Buildpacks Rust Create React App Write The Docs Conference Prettier Typescript Git hooks and Husky Runbooks Heroku Changelog Stack Overflow

How thorough is your Disaster Recovery (DR) strategy and equally important, how comprehensive is your DR Runbook? While possibly the least favored task among IT departments, a well written and up to date Runbook is crucial to restoring mission-critical IT functions without major losses in revenue or business operations during a failure. The post Developing a Comprehensive Disaster Recovery Runbook appeared first on InterVision.

Have you ever been on-call duty as an IT person or otherwise? Woken up at 3 a.m. to solve a problem? Did you have to go through log files or look at a dashboard to figure out what was going on? Did you think there has got to be a better way to troubleshoot and solve problems? Today, we’re talking to Sam Bashton, who previously ran a premiere consulting partner with Amazon Web Services (AWS). Recently, he started runbook.cloud, which is a tool built on top of serverless technology that helps people find and troubleshoot problems within their AWS environment. Some of the highlights of the show include: Runbook.cloud looks at metrics to generate machine learning (ML) intelligence to pinpoint issues and present users with a pre-written set of solutions Runbook.cloud looks at all potential problems that can be detected in context with how the infrastructure is being used without being annoying and useless ML is used to do trend analysis and understand how a specific customer is using a service for a specific auto scaling group or Lambda functions Runbook.cloud takes all aggregate data to influence alerts; if there’s a problem in a specific region with a specific service, the tool is careful to caveat it Various monitoring solutions are on the market; runbook.cloud is designed for a mass market environment; it takes metrics that AWS provides for free and makes it so you don’t need to worry about them Will runbook.cloud compete with or sell out to AWS? Amazon wants to build underlying infrastructure, other people to use its APIs to build interfaces for users Runbook.cloud is sold through AWS Marketplace; it’s a subscription service where you pay by the hour and the charges are added to your AWS bill Amazon vs. Other Cloud Providers: Work is involved to detect problems that address multiple Clouds; it doesn’t make sense to branch out to other Clouds Runbook.cloud was built on top of serverless technology for business financial reasons; way to align outlay and costs because you pay for exactly what you use Analysis paralysis is real; it comes down to getting the emotional toil of making decisions down to as few decision points as possible Save money on Lambda; instead of using several Lambda functions concurrently, put everything into a single function using Go AWS responds to customers to discover how they use its services; it comes down to what customers need Links: Sam Bashton on Twitter runbook.cloud How We Massively Reduced Our AWS Lambda Bill with Go AWS AWS Lambda Microsoft Clippy Honeycomb AWS X-Ray Kubernetes Simon Wardley Go Secrets Manager DynamoDB EFS Digital Ocean

Perhaps you have heard about a runbook--the documented instructions you should follow in the event of a disaster or some situation where an outage occurs.  Instructions are great for IT folks as they give a reference to follow--and they don't freak out even if we might. They don't, however, include instructions for everyone--what about the folks that aren't tapping away on the keyboard?  In this episode, we chat with Greg Moore about his experience in emergency situations outside of IT and how we might apply these principles in our environment. Whether you are directly in the line of fire or support those that do, we think you will find this conversation interesting. The show notes from today's episode can be found at http://sqldatapartners.com/2018/02/13/episode-124-beyond-the-runbook-dr-organization. Have fun on the SQL Trail!