6 Responses

  1. Newsletter: December 28 | Notes from MWhite

    […] experience, and fortunately figured it out before it was a crisis that customers saw.  Here is the info you need to move the SQL Agent jobs which is what you would be missing if you moved the db.  I do […]

  2. Traze
    Traze at |

    Thanks a lot Chris ! 🙂 🙂

    Reply
  3. Adam T. Courtney
    Adam T. Courtney at |

    Also, be sure to check the following settings in vCenter for the Event Task Cleanup VCDB job:
    Tasks retained for
    Events retained for
    If these are unchecked Event Task Cleanup will do nothing.

    Reply
  4. Bram F.
    Bram F. at |

    When I upgraded my vCenter 5.1 to 5.5 I got an error saying that these jobs were owned by a different user. So I should either install vcenter with that same user or delete the jobs.

    I figured that I added the jobs as a different user and went along with the deletion part (as it’s easy to add the jobs again).

    When I logged into my MSSQL server after the update was finished to re add the jobs I was pleasantly surprised that all the jobs were already present (and this time under the same user as the user that vcenter uses to connect to the DB). So it seems the vCenter 5.5 installer adds these jobs to external MSSQL databases automatically.

    I guess to many people forgot to add these jobs manually.

    Reply
  5. Tom
    Tom at |

    Hi, You forgot to mention that in some situations scripts from local disk will not work – especially in the case of vCenter upgrade like to 5.1 or 5.5. In such case you get the error message continuously and you need to get the new scripts from installation media. Link – http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2038633. Besides it’s a good article.

    Reply

Share your point of view!