3 Responses

  1. Matt Liebowitz
    Matt Liebowitz at |

    Great post, thanks Chris. One thing I will add is that I find it’s really helpful to organize VMs into folders under the VMs and Templates view. Not only does that make assigning permissions to the application owners easier but also lets you have easier control over backups with products like Veeam.

    One more point – don’t go too crazy with permissions if you can avoid it. To the best of my knowledge there is no easy way to export/import permissions if you have to move to a new vCenter database. I know some folks who had this issue when doing migrations to new vCenter 4.1 servers (because of the 64-bit requirement) who wanted to start with a clean database. I think there are some PowerCLI scripts to help with that now but nothing I have tried personally.

    Reply
  2. hemp
    hemp at |

    All of the information about your vCenter environment is stored in that database – so if you build a new vCenter server all you will need to do is have the ODBC connector to point to the existing database and when you install vCenter 4.1 the databse will get upgraded.Check out Section 5 of this document If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful …………………. If your SQL Database is located on a separate server you could just rebuild the vCenter on the 64 bit OS and point to the existing DB. A DCSE MCP MCSA MCSE MCTS MCITP MCDBA NCDA VCP4If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful.

    Reply

Share your point of view!