[BlueOnyx:03009] Re: cmuExport/cmuImport

enid vx enidv11 at gmail.com
Thu Dec 3 10:46:53 -05 2009


Thank you Michael for responding ,

so if I want to cmuImport all the sites how do I delete them without
entirely erasing the system and installing from scratch.

Rgds,

Enid


On Thu, Dec 3, 2009 at 4:23 PM, Michael Stauber <mstauber at blueonyx.it>wrote:

> Hi Enid,
>
> > After some time when the BQ server was updated by different site
> > admins, I decided to do another cmuExport/cmuImport to the new BO
> > server,
> > but in this case I had all the sites existing in the BO and there were
> > some problems with
> > 1- the virtual users and
> > 2- system users
> >
> > and the script cmuImport asking me for every users (to resolve
> > dependecies) to modify it/delete it/drop/quit. I've responded to all
> > of them letting them as they were.
> >
> > So the question: is this a problem, and how can I make another
> > cmuImport with the new exported sites in the existing BO?
> >
> > This is somehow an update process that I want to make , to leave the
> > two servers in the same state with the same data.
> > Is it possible to restore (with cmuImport) all the sites data in the
> > existing BO or should I cmuImport only in a clean installation.
>
> It has always been the case that with CMU you should only import sites and
> users that don't already exist on the system.
>
> When CMU tries to import a site or user that already exists on the target
> system, then you sure get the dialogue to merge, drop or modify. That
> allows
> some limited form of conflict resolution. But generally you'd be better off
> to
> delete the conflicting site or user first and then use CMU to import the
> one
> from the CMU dump.
>
> --
> With best regards
>
> Michael Stauber
>
> _______________________________________________
> Blueonyx mailing list
> Blueonyx at blueonyx.it
> http://www.blueonyx.it/mailman/listinfo/blueonyx
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.blueonyx.it/pipermail/blueonyx/attachments/20091203/e8e83568/attachment.html>


More information about the Blueonyx mailing list