I am working out a plan to upgrade a heavily-used production environment from 4.1 to 5.0. We don't want to bring a server off line for an extended reindex while the upgrade happens so we are spinning up a temporary server to handle the load while we do this. My question is whether it would be faster to:
1) back up the forests on the existing database (saving across the network to the new server?), and then restore the 4.1 forests into the 5.0 installation, letting it do its reindexing (is that even possible) - or 1b) restore to a new 4.1 install, and then upgrade it, waiting for the reindexing or 2) copy the data across using xqsync; this will avoid the need for reindexing anyone care to hazard a guess? I'm not really sure how to find out without trying it -Mike Sokolov _______________________________________________ General mailing list [email protected] http://developer.marklogic.com/mailman/listinfo/general
