Hi Mike,
Copying the 3TB of data from one SAN to another across an intercontinental WAN takes several days and requires us to suspend feeds (make read-only), but it is possible! I'll keep this option open. So thanks for that. One of the reasons for assessing XQSync, is because we hope to use this opportunity to extract only the data we now require. There is a lot of duplication of documents in our Forests, which we plan to remove. I have been able to use backup and restore on our old v4 UAT environment for all other (much) smaller, static databases, leaving the one very large database to work with on the new DEV. The stage I'm now at is playing around with XQSync, however, our internal sites block the downloading of the necessary jars. While I wait for an exception to be put in place, do you know if the source code is available for XQSync? I'd like to extend it to do in memory data transfer. Sinclair Cram | Client Technology | J.P. Morgan | Alhambra House, 45 Waterloo Street, Glasgow | J.P. Morgan<http://www.jpmorgan.com/> | T: +44 141 228 0421 -----Original Message----- From: general-boun...@developer.marklogic.com [mailto:general-boun...@developer.marklogic.com] On Behalf Of Michael Blakeley Sent: 19 February 2014 17:52 To: MarkLogic Developer Discussion Subject: Re: [MarkLogic Dev General] Migration from version 4 to 7 So you're migrating from old hardware running ML4 to new hardware running ML7? Couldn't you set up the new hardware with a copy of the old ML4 config and forests, simply by copying the /var/opt/MarkLogic and data directories? For clustering you'd have to fix up the host names to match the new ones, but that isn't too difficult. Then you could turn off reindexing and upgrade in series: first to ML5, then to ML6, then to ML7, each time visiting the admin page to ensure that config and security database updates are successful. Finally enable reindexing. To me that seems simpler than exporting and importing, but I might be missing something. If you have to worry about clustering then fixing up the hostnames could be a bit troublesome, but not too bad. For the smaller dev environment, I would wait until the new UAT hardware is running ML7. It will probably need to reindex, but you can ignore that. Export a config package from UAT and use that to set up dev. Then use mlcp or another import-export tool to copy a subset of the data. -- Mike On 19 Feb 2014, at 02:15 , Cram, Sinclair <sinclair.c...@jpmorgan.com<mailto:sinclair.c...@jpmorgan.com>> wrote: > Hi All, > > Over the next few months, we are migrating our test (UAT) and Production > MarkLogic environments from version 4.2-6 running on older hardware, to > 7.0-2.1 on new kit. Installing the software is straightforward enough, but > the challenge we have is copying both configuration details and > metadata/documents from the Forests. After consulting MarkLogic Support, we > have been advised to upgrade from version 4 to 5, in order to use the MLCP > tool. This would be extremely difficult as we only have a single UAT > environment, which is heavily relied on and we would like to avoid disruption > to that service if possible. > > The alternative suggested is manual configuration via the Admin console and > to use backup/restore for the data. The latter would be particularly > difficult as our new development server (an additional environment we didn't > previously have) has significantly less disk space available (200MB in new > Dev vs 3TB in old UAT), therefore we would be looking to extract a subset of > the data. > > Has anyone overcome a similar problem or aware of other solutions? > > Sinclair Cram | Client Technology | J.P. Morgan | Alhambra House, 45 Waterloo > Street, Glasgow | J.P. Morgan | T: +44 141 228 0421 > > This email is confidential and subject to important disclaimers and > conditions including on offers for the purchase or sale of securities, > accuracy and completeness of information, viruses, confidentiality, legal > privilege, and legal entity disclaimers, available > athttp://www.jpmorgan.com/pages/disclosures/email. > > _______________________________________________ > General mailing list > General@developer.marklogic.com<mailto:General@developer.marklogic.com> > http://developer.marklogic.com/mailman/listinfo/general _______________________________________________ General mailing list General@developer.marklogic.com<mailto:General@developer.marklogic.com> http://developer.marklogic.com/mailman/listinfo/general This email is confidential and subject to important disclaimers and conditions including on offers for the purchase or sale of securities, accuracy and completeness of information, viruses, confidentiality, legal privilege, and legal entity disclaimers, available at http://www.jpmorgan.com/pages/disclosures/email.
_______________________________________________ General mailing list General@developer.marklogic.com http://developer.marklogic.com/mailman/listinfo/general
