btayoga.blogg.se - Best practice veeam backup jobs

How to delete Kubernetes namespaces or pods with a specific pattern or name March 16, 2023.Red Hat OpenShift – Sorry, your reply was invalid: IP expected to be in one of the machine networks March 30, 2023.Quick Tip: Supercharge Kubernetes Resource Retrieval with ‘kubectl get -f’ June 14, 2023.For now, I’ll leave you with one of my favourite Dilbert sketches.įollow my 100 Days of Kubernetes challenge here! I hope this helps, if anyone has any suggestions on how to improve the above, or wants to chat about how they document their environment, either online or offline, let me know. So this is pretty simple, a copy and paste of the above, then remove the server icons, and insert the headline job settings that you need to know. It’s quite simple, a container for each job, and the name of each server/service included in the job. As well as showing the architectural components involved. To complete the visualisation, I decided to included the rack diagrams, which I covered in Part 2 of this series. Now onto visualising each backup and replication job, and more importantly, which servers/services are included in each job. But at the same time, when Veeam has issues, they have done a good job of providing meaningful error messages (unlike Backup exec).

I find this diagram is helpful for support engineers to quickly understand the environment when troubleshooting issues. At this level, I do not bother with server names and IP addresses, but there is nothing stopping you from doing that. So here I am essentially re-working Veeam’s own diagrams of how they show their software working. So this is the conceptual overview, for me, its easy, I setup Veeam in supported configurations, taking advantage of its many features, such as direct SAN backups.

Backup and Replication job settings – high level.

Backup and Replication jobs – Servers/services included.

So I re-visualised the way to present the data, I still have the detailed tables, however I also have three Visio diagrams When you have a number of backup jobs, you have a lot of jobs and information to dig through. Your backup schedules become more complex, and its hard to remember, what does what.Īs past of my job, I setup backup solutions for customers, and then have the task of documenting how they are setup. Your backups evolve over time, as does your environment. Note: The Visio file for these examples can be found at the end of the blog post.

Part 1 – The foundation of any IT infrastructure.

Note: I mainly work with Veeam, but hopefully this will give you idea’s of how to present the setup of your other backup software So this post is to show how I have documented some recent backup configurations. I hoped to keep adding to the series, but at the same time, only do it when I felt I had relevant content to share. So it’s just been a little over a year since Part 4 of my how to document series was posted.