On Wed, Jan 15, 2014 at 1:49 PM, helix84 <heli...@centrum.sk> wrote: > On Tue, Jan 14, 2014 at 10:16 PM, Mark H. Wood <mw...@iupui.edu> wrote: >> The documentation is correct but incomplete. You do not have to shut >> down Tomcat; you have to shut down the instance of DSpace that you are >> restoring. If DSpace is the only application running on that Tomcat >> instance, then it's easiest to shut down Tomcat; if not, there's no >> need to bounce other applications along with DSpace. > > That's true - in theory, you don't to restart Tomcat. However, as long > as DSpace is the only application under your Tomcat, I (and all DSpace > admins I know) still recommend to restart Tomcat. > > By not restating Tomcat you won't gain much in terms of speed, but you > might lose in terms of memory leaks and loss of stability. It's all > just anecdotal experience.
Sorry, I did not read this in context of running update-sequences.sql. In that case, you just need to ensure that DSpace doesn't create new objects in the database, so it is enough to stop the DSpace webapps. Regards, ~~helix84 Compulsory reading: DSpace Mailing List Etiquette https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech List Etiquette: https://wiki.duraspace.org/display/DSPACE/Mailing+List+Etiquette
