Indeed goes without saying messing with the DB without a GSS ticket is not advised

Already having internal discussions about this yes.  Nothing in the near term but use GSS for now.  We are tracking this in a couple places though.  I will be doing some of my own lab testing to see if there is any other ways out of it.

For the record disabling HA does not do the damage of disabling DRS.  That would not really affect vCloud as much other than the admission control part.  This is definately something we are looking at to help assit in fixing, but right now it is what it is.

Thanks.  It seems the inventory snapshot does not help.  Still changes the MoREF ID's.  This is just one use case in a list of many I am tracking for recovery modeling.

So what would happen if you just restored vcenter from backup?  I mistakenly did exactly what I shouldn't have (disabled DRS) and killed all my resource pools.  Our environment is relatively small and no changes were made since the last full backup of the vcenter server.    What would happen to vcloud director if I just restored the entire vcenter server?

So I was able to restore the Resource Pools by restoring the SQL database to the backup before I disabled DRS.  Luckily we have a small environment right now, so no damage done.   Good lesson though.