Special guest Chris Mellor joins us on the podcast, and he asks some very good questions about the future of backup for Kubernetes, including a discussion about Portworx.
You shouldn’t need an annual day to remind you to treat your sweetheart well. Every day should be Valentine’s Day, right? Reaching out and telling your sweetheart that you love them (or remember them if they are no longer with us) is something that you should do on a very regular basis.
Just like backups.
You shouldn’t have to remind yourself to do backups. In fact, backups should require no action on your part; they should just happen. Like love expressions for your sweetheart, they should happen at least on a daily basis – and possibly more often than that. Making sure backups “just happen” requires you to do a few things.
Your backup system should allow you to define a schedule for backups. The default setting for most people is once a night during a time when most people are not using the computing environment. For example, Time Machine defaults to once an hour.
Whatever the frequency, your backup system should be set up so that backups occur on a very regular basis without anyone having to make them happen. We’ll discuss how often that should be a little bit later in this blog post.
Storage available for backups
Backups are not going to happen if they have nowhere to store the data. Historically this meant you had a tape library full of tapes that were ready to be swapped in when necessary. Backup technology has evolved and most of us are using disk or cloud as the primary target. So the main challenge here is to ensure that the disk is available, online, and has sufficient capacity to hold your backups. (This is one of the great things about using the cloud as your backup target; it’s never out of space.)
This is one of the reasons why I do not like Time Machine for your regular laptop backups. It requires you to plug in a portable hard drive in order for the backups to work, then you have to unplug it in order to get your backups away from the thing that you’re backing up. (The 321 rule is always waiting.) So just make sure that whatever backup storage you have, it is always available and always has available capacity for your backups.
How often should you backup?
The more often you backup, the less data you will lose. In more technical terms, the more often you backup, the shorter recovery point objective (RPO) you can support. Let’s consider a few extremes.
If you only backup once a night and your off-site storage system requires swapping tapes, the best RPO you can support is 96 hours. Why is that, you say? Let’s say something bad happens on Monday before the iron Mountain truck comes. If you are sending backups offsite every day, what night was the most recent off-site backup taken? The answer is Thursday night.
Think about it. The last truck to leave your facility left Friday morning, which means it has Thursday night’s backups. That means you’re going to lose all of Friday’s work, any work done over the weekend, and any work that was done on Monday prior to the disaster. That’s 96 hours of lost work. This is why backup frequency and off-site frequency matters. However, backing up more often and sending backups offsite more often can be a costly endeavor, so this must be a decision based on business requirements.
This means this is a business discussion, not a technical one. Stakeholders in your company should decide what the RPO is for their environment because it should be based on the cost of lost data for that particular stakeholder. Business units with very high data loss costs will seek a much tighter RPO, perhaps an hour or even a few minutes. Such an RPO requires backing up more often. And that is the answer to the question, “How often should I back up?”
Give your backup admin some flowers
I’ll bring this back to Valentine’s Day by saying that your backup admin has a very tough job. No one remembers the hundreds of thousands of backups they got right; they only remember the one restore they got wrong. Get them some flowers, chocolate, or whatever it is that gives them a smile. Say thank you, have a nice Valentine’s Day – and then don’t wait another year before you do that again.
Our special guest this week is Preethi Srinivasan, Technical Product Architect at Druva. We talk about Machine Learning, analytics, and how they relate to Data Protection.
We discuss how Salesforce.com has reversed their position on their “recovery service” that costs $10,000 and takes 6-8 weeks. This is a really important thing to know if you’re using SFDC.
Due to the popularity of last week’s podcast (An investor’s perspective on Veem’s Acquisiton), Prasanna and I decided to discuss this topic further. We used the article “The 6 things a private equity firm will do after they buy your business” from inc.com as a reference: https://www.inc.com/jim-schleckser/the-6-things-a-private-equity-firm-will-do-after-they-buy-your-business.html
We have a special guest this week! None other than the author of “Knative in Action,” Jacques Chester is joining Prasanna and Curtis to help us understand the interesting world of Kubernetes, Docker, Knative, and how it all relates to backup and storage.
Backup Central readers and podcast listeners get a special discount code. Just enter PodRestore20 and you’ll get 40% off!
AND the first five people to give me feedback on our podcast will get a this e-book free! Just email me at wcurtispreston – at – gmail dot com.
One of the most successful investors in technology stocks is our special guest this first podcast of the new year! Matt Feshbach has managed billions in tech stocks, and he lends his brain to answer questions such as:
– What does it mean that a private equity company just bought Veeam?
– Why would they do that?
– What’s next?
It’s a great podcast where I learned a lot. Hope you like it!
W. Curtis Preston (Mr. Backup) and Prasanna Malaiyandi discuss the various ways to back up IaaS, PaaS and SaaS data.
W. Curtis Preston & Prasanna Malaiyandi discuss the announcements of re:Invent 2019, and how Curtis fought zombies and lost.
W. Curtis Preston (Mr. Backup) and Jon Owings (Principal Solutions Architect for Cloud Solutions at Pure Storage) discuss what container backup is, why it’s so difficult, and what you need to do to back them up.