Reply to Message

View discussion in a popup

Replying to:
mariodez
Contributor
Contributor

Here is a little more background on the issues we are facing.  I have limited visibility into the vCenter as it is hosted by another vender and they have only given us limited walk-throughs to calm concerns, which only ended up raising additional concerns.   Due to the limited visibility at this time I don't have any of the specific configuration information.  The information that I can give you is that our company is split into three IT departments for three major but seprate business functions.  In the vCenter cluster all application servers across the enterprise are lumped into one cluster.  So with this said we do not have information on the other departments VMs and what functions/environments they serve.  We do know our departments VMs inside and out along with the importance and resources they require.  I have been tasked by our executives for my side of the business to make sure that our environment is protected and need to see what the best practice is to do that.  My initial thought was to recommend that the vendor have a container created at the top level called "My Department" within that pool we would create resource pools for Prod, Test, and Dev and assign the appropriate controls, priorites to each pool.   I saw in one reply that this may not be the best as resouce pools can hurt just as much as help, can you give me some of the pros/cons of this?   I am sorry things are kind of vague but I have limited information to go on myself.  As far as I know DRS and SIOC are not enabled.  With our limited visibilty and the vendors lack of transparency we were unable to tell what server caused the outage and why.  All we can do is look to protect our VMs as best as we can.  Any best practices documentation that can be directed my way for this type of scenario would be much appreciated.

Reply
0 Kudos