Backing RP Error<\/figcaption><\/figure>\nSo How The Heck Do I Fix This!?<\/h3>\n
Well it is not easy, but it is also not impossible, and it is not really something you should do without GSS help. \u00a0First thing is you need to re-enable DRS, and from there a lot of re-work will need to happen to re-create the Resource Pools and re-map them to the vCloud Director Database. \u00a0This may not be as easy as it sounds, as you can see from the initial snapshot, the resource pool name also has a UID associated with it. \u00a0You need to re-create them exactly as they were before the mistake was made. \u00a0Again this is not for people to do on their own. \u00a0I may try to play with this in my now broken lab to see if I can fix it, but I will NOT be posting the Database tables and other information should I get it to work. \u00a0I’m not taking that responsibility should someone break something. \u00a0The real issue is not for two pools, but what if you had 10, 50, or 100 to recreate? \u00a0The whole time your users will not be able to do anything on the organizations and that is not good. \u00a0You also have to know exactly where every Virtual Machine was associated with the right resource pool. \u00a0Some of this may be in the vCloud Director Database as indicated by the error above. \u00a0Obviously it is important to get each organizations Virtual Machines back to the right resource control. \u00a0I have no idea how the ChargeBack data collectors will be affected by this either and what may happen to the billing reports. \u00a0One other thing to consider is you have to also replace the “System vDC” as well but that gets created when you create a Provider vDC, but must also be re-created.<\/p>\n
The Moral of The Story<\/h3>\n
Lock users out of changing this setting, with RBAC, or a completely separate locked down vCenter. \u00a0Sometimes protecting people from themselves is the best option. \u00a0If you do get into trouble call support, you are going to need them, and that is what they are there for. \u00a0Just don’t do it, and think twice before you do. \u00a0You can always set it to manual to prevent DRS migrations, but you need to maintain those Resource Pools. \u00a0The thing to remember is that one way update from vCloud Director to vCenter, and it is not currently the other way around. \u00a0I am currently working on investigating ways this, and other use cases where MoREF ID’s have changed in vCenter can be recovered, but it will take some time and possibly tools like vCenter Orchestrator for example. \u00a0There is also a VMware Labs Fling for Inventory Snapshot<\/a>, which I have yet to test to see if it recreates with the original MoREF ID’s, but I plan on seeing the results this coming week.<\/p>\n","protected":false},"excerpt":{"rendered":"In the past week there have been a rash of reports about people disabling VMware DRS, while vCloud Director was in place. \u00a0I have tweeted multiple times about this and also brought it up on the Community PodCast yesterday. \u00a0The more I bring it up the more people are asking why someone would do such …<\/p>\n","protected":false},"author":2,"featured_media":710,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"jetpack_post_was_ever_published":false,"_jetpack_newsletter_access":"","_jetpack_dont_email_post_to_subs":false,"_jetpack_newsletter_tier_id":0,"_jetpack_memberships_contains_paywalled_content":false,"_jetpack_memberships_contains_paid_content":false,"footnotes":"","jetpack_publicize_message":"","jetpack_publicize_feature_enabled":true,"jetpack_social_post_already_shared":false,"jetpack_social_options":{"image_generator_settings":{"template":"highway","enabled":false}}},"categories":[19,9,11,12],"tags":[61,163,181,182,226],"jetpack_publicize_connections":[],"yoast_head":"\n
Gotcha: Disabling VMware DRS with vCloud Director \u2022 Chris Colotti's Blog<\/title>\n\n\n\n\n\n\n\n\n\n\n\n\n\t\n\t\n\t\n\n\n\n\n\n\t\n\t\n\t\n