I’ve been working on this topic for several Provider-1 customers over the past few weeks. If you want to move a CMA to another MDS, you normally could just use the ‘cma_migrate’  process.  Well it turns out that does not work if VSX is used within the CMA.

There is an internal document on how to migrate a CMA with VSX being used. I have seen the document,  and the process is very ugly. It looks like the best way is to setup a temporary MDS and use the HA feature to automagically copy over the CMAs to their new home. I am working on a document that will clearly layout this process. Should be up in the next few days.

No cma_migrate if VSX is present

3 thoughts on “No cma_migrate if VSX is present

  • October 23, 2009 at 2:27 pm

    No offense but I think this is over most CP customers heads. 🙂

  • December 30, 2009 at 12:37 am

    Did you ever get around to doing this document? I would be interested to see it . I am soon to need to do this, and in lab testing recently I observed this exact issue. So far the only suggestion I have seen is from Valeri Loukine who says to hack the import scripts to stop the VSX check at import time. Not sure if that will be possible but will be investigating.

  • December 30, 2009 at 10:58 pm


    I have made some interesting progress on this, and there might be a pretty simple solution. I wrote a white paper on this for a Fortune 25 company that I am working with, and am stepping them through this process in early January. I will contact you via the email address you left me with more info.

    fireverse (pat)

Leave a Reply

Your email address will not be published. Required fields are marked *

five × four =