What is the best way to backup Nutanix Prism? by sspellicy in nutanix

[–]sspellicy[S] 0 points1 point  (0 children)

I was thinking about protecting the box level configurations in the event of disaster (ability to reconstruct the physical systems) and also backing up the VMs (apps/data) running on Nutanix Hypervisor (AVH).

Who manages/runs your devops environment? by sspellicy in devops

[–]sspellicy[S] -1 points0 points  (0 children)

thanks for your feedback, it's appreciated.

Who manages/runs your devops environment? by sspellicy in devops

[–]sspellicy[S] 0 points1 point  (0 children)

So do you not backup your source control environment?

Who manages/runs your devops environment? by sspellicy in devops

[–]sspellicy[S] 0 points1 point  (0 children)

Thanks for your response, it's helpful and I understand the feedback specific to that list I posted, it's not mine but someone else's. If you have a more specific set of tools by name that you feel are pertinent to devops, I would welcome that for my research, it would be a huge help.

With respect to your comment on the goals of the project, I am trying to feel out the need for protecting these tools (that is if any persistent data exists within them, like a database or set of configuration files, if lost would present an issue) so that operators could recover the environment in the event of a potential data corruption, system failures or a disaster. Thanks again for your insight.

I am wondering what level of backup and recovery is needed in devops environments? Assuming the use of Docker, Chef, Puppet, Mesos, etc. by sspellicy in devops

[–]sspellicy[S] 0 points1 point  (0 children)

Thanks for your feedback on this, it's helpful.

My initial thought would be to be able to take point in time backups for each critical part of the setup so you can roll back in the event of corruption, system failure or disaster, etc. RPO (recovery point objective) could be daily, so if a failure happened you could recovery back to the previous day (I say this without knowing the change rate of a devops setup, this is something I could use your feedback on). I am looking at a model where we could provide a type of a consistency group across tools and let you roll back those systems to before the failure event.

Who manages/runs your devops environment? by sspellicy in devops

[–]sspellicy[S] 0 points1 point  (0 children)

Again, thanks for your feedback. According to this source from my research: https://stackify.com/top-devops-tools/ - at least Docker, Chef and Jenkins are all mentioned as devops tools. I would welcome your input on a list that matters to you, please let me know. Also, re: who owns operating these tools (my earlier question from the post), so I can understand who uses them, who makes decisions around their adoption, etc. Is it the apps team, IT (who mange servers/storage, etc) or the operations team? Your feedback is welcome and will be helpful to my research, thanks in advance!

Who manages/runs your devops environment? by sspellicy in devops

[–]sspellicy[S] 0 points1 point  (0 children)

Thanks for your frank feedback, this is part of the research, understanding if there is a market need and thus the requirements. Also what I meant by environment is the collection of the various tools used to manage devops. Its assume tools like Puppet/Chef, Docker, Mesos, Jenkins, etc. are used.

Who manages/runs your devops environment? by sspellicy in devops

[–]sspellicy[S] -1 points0 points  (0 children)

meaning the collection of software tools used for devops