Sometimes it's not enough to just back up the database itself; but we also need to back up the structure of the data, and having an up-to-date export and backup, says Daniel Hudsky
Does it seem to you that your Atrium installations may be taking too long? Do you understand the importance of hardware, not only in the production environment but also in your testing setup? Do you have a handle on how thorough your backup process really needs to be? Are you puzzled by some aspects of Atrium in a UNIX environment? Do you want some insights on navigating customer support? Join us for a lively conversation with Daniel Hudsky, Senior Technical Support Analyst at BMC Software, to get answers to these questions an more, as we explore the nitty gritty of Atrium Core CMDB Installation.
To get started, let's talk about what is in Atrium Core so we have a basic understanding for everyone that is listening at the moment.
That's a good summary of the components of Atrium. I've always wondered, do I need all of them, can I just use part of them, what's the story with that?
What are the important aspects of a successful Atrium Core CMDB Installation from the hardware point of view?
Why is it important to optimize threading of the Action Request (AR) server?
What's something you see in the field right now that's creating tickets for you?
I understand you get the following kind of question, "I'm trying to to get this product catalog updated, but I'm using Unix, and your product does not seem to be working with Display Redirection.
I've been reading the documentation for Atrium Core and it just doesn't cover everything. What are my options?
How will my case be treated, and how can I impact customer support on the proper severity of my issues for a quick turnaround?