I did that, in my case I moved the files, not copied them which if the DB resides in mongodb directory we shouldn't have to leave a trail of files all over I would assume. I get mongo dead but subsys locked now when restarting mongo. What gives?
On Wed, Sep 12, 2012 at 7:34 AM, George Niculae <[email protected]> wrote: > All, > > If you have 4.6 installed from RPMs / ISO and yum upgrade please mind > that it will upgrade MongoDB as well (from 2.0.2 within sipxecs repo > to 2.0.7 published in epel-release). While mongo 2.0.2 stores data in > /var/lib/mongod the new one will store it in /var/lib/mongodb. > So if you want to preserve data after yum update, you just have to > copy files from /var/lib/mongod to /var/lib/mongodb and change > permissions to mongodb:mongodb then restart mongo > > George > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- ~~~~~~~~~~~~~~~~~~ Tony Graziano, Manager Telephone: 434.984.8430 sip: [email protected] Fax: 434.465.6833 ~~~~~~~~~~~~~~~~~~ Linked-In Profile: http://www.linkedin.com/pub/tony-graziano/14/4a6/7a4 Ask about our Internet Fax services! ~~~~~~~~~~~~~~~~~~ Using or developing for sipXecs from SIPFoundry? Ask me about sipX-CoLab 2013! <http://sipxcolab2013.eventbrite.com/?discount=tony2013> -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
