At http://www.handle.net/faq.html#4.9 describing your situation, however The instructions are not complete, what I did was:
Assuming the dspace.cfg handle entries did not change, was 1 run SimpleSetup 2 Edited the config.dct file as in http://www.dspace.org/index.php?option=com_content&task=view&id=152 3 Copied over the existing 'handles.jdb' and 'cache.jdb' files to the new $DSPACE/handle-service directory 4 started the handle server 5/ sent the generated file sitebndl.zip to cnri, who updated the site details 6/ updated our proxy server to reference the new server instead of the old one 7/ sorted out at my end firewall issues with the default ports 2641 and 8000 and UDP That was it Regards Graeme Massey University Message: 4 Date: Thu, 13 Mar 2008 10:57:02 -0700 From: Mark Diggory <[EMAIL PROTECTED]> Subject: Re: [Dspace-tech] Moving DSpace & handle server to new server To: [EMAIL PROTECTED] Cc: dspace-tech@lists.sourceforge.net Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed It really depends on if your changing the hostname/domain as well. Are you going to carry the hostname along to the new server as a virtualhost? -Mark On Mar 13, 2008, at 2:30 AM, Robin Taylor wrote: > Unfortunately I believe that moving to a new hostname/IP does > require you to > notify CNRI. Although when we did it they were very helpful and > made the > change exactly when requested. There are also some references in at > least > one of the files in the handle-server directory to the IP addess > (config.dct). I suspect I just edited this manually. > > One other wee thing, do you need to move the source files ? They > are not > used by the running web application so you could just stick them > somewhere > else for reference eg CVS or SVN. > > Cheers, Robin. > > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of > Mathias > Hjelt > Sent: 13 March 2008 08:55 > To: dspace-tech@lists.sourceforge.net > Subject: [Dspace-tech] Moving DSpace & handle server to new server > > We're planning to move our DSpace production environment to a new > server. > (This may or may not involve upgrading from 1.4.2 to 1.5 at the > same time, > but that's a different story altogether.) > > As far as I can see, the easiest way to migrate DSpace from one > server to > another is simply copying the dspace source and install directories > from the > old server to matching locations on the new server, and populate > Postgres on > the new server with the contents of a pg_dump from the old server. > Right? > > Now, my main concern is the Handle server, mainly because setting > it up was > a bit hairy (docs didn't really align well with the real-world > process) and my personal installation notes are quite vague (stupid > of me -- > everything else is documented down to the last bit.) > > So, will the Handle server migrate just as easily as the rest of > DSpace? > What if the host name and/or IP address of the instance changes -- > will I > need to reconfigure the Handle server somehow, and/or send > configuration > updates to CNRI? (After two years of DSpace administration, I must > admit I > still have no clue about how the Handle server communicates with > DSpace and > CNRI... missing the big picture > *and* the hairy details.) > > Any suggestions are welcome! > > best regards > > Mathias Hjelt > DHANKEN > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft Defy all challenges. > Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------ Message: 5 Date: Thu, 13 Mar 2008 10:59:57 -0700 From: Mark Diggory <[EMAIL PROTECTED]> Subject: Re: [Dspace-tech] Automatic system alert when tomcat is down. To: DSpace Tech <dspace-tech@lists.sourceforge.net> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Yes, there are also enterprise grade monitoring tools out there you can use to make sure that services are correctly functioning on your systems. We currently use an open source tool called Nagios. http:// www.nagios.org/ -Mark On Mar 13, 2008, at 5:49 AM, Mark H. Wood wrote: > Um, in general it is not possible for a failed system to report that > it has failed, because it has already failed. :-/ > > What I do is to run a periodic check on a different host. My script > is far from complete, but it often catches problems that I need to > know about. I have cron run it every five minutes. By running the > check on a different host, I avoid the chicken/egg problem of trying > to get a failing machine to monitor itself. > > I've attached a copy of my script. You'll need to configure it for > your services and your notification requirements, and I have no doubt > that it can be improved. > > -- > Mark H. Wood, Lead System Programmer [EMAIL PROTECTED] > Typically when a software vendor says that a product is "intuitive" he > means the exact opposite. > > <ping- > servers.pl>----------------------------------------------------------- > -------------- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------ Message: 6 Date: Thu, 13 Mar 2008 11:07:10 -0700 From: Mark Diggory <[EMAIL PROTECTED]> Subject: Re: [Dspace-tech] out of memory error - statistics and community pages To: Ene Rammer Nielsen <[EMAIL PROTECTED]> Cc: dspace-tech@lists.sourceforge.net, Kyle Kaliebe <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed I tend to agree, If your encountering issues with Communities that contain many collection/subcommunities, then you are more than likely hitting a limit on the number of these object in memory at the same time. I would first try boosting your memory usage... You can safely push it to 2048m (2gig). Everything I've read after that suggests that the JVM can't deal with anything greater... We currently run our JVM for [EMAIL PROTECTED] at 2048m. -Mark On Mar 13, 2008, at 5:42 AM, Ene Rammer Nielsen wrote: > Hi Kyle, > We experienced a similar problem. We resolved it by increasing the > Xmx- > and Xms-value in /usr/local/tomcat/bin/catalina.sh to 512m. I don't > know > if it is the best way to do it, but it solved the problem. > Sincerly > Ene Rammer Nielsen, Roskilde University Library > > Kyle Kaliebe skrev: >> >> Dspace Tech List, >> >> >> >> Our Dspace installation has been generating an increased number of >> out >> of memory errors. My assumption is that there is a memory leak >> somewhere in the installation and that as our traffic increases, this >> problem will only worsen. >> >> >> >> Has anyone encountered memory leaks or out of memory errors in the >> Dspace installation before? To help begin my search, I am >> wondering if >> someone could point me in the right direction of where such memory >> leaks might exist. >> >> >> >> The errors we are encountering are most often occurring when users >> access administrator statistics and communities that have complex >> community pages with a high number of collections and sub- >> communities. >> >> >> >> Thanks. >> >> >> >> Kyle Kaliebe >> Systems Developer/Engineer >> Knowledge Bank >> University Libraries >> Ohio State University >> [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> >> >> >> >> --------------------------------------------------------------------- >> --- >> >> --------------------------------------------------------------------- >> ---- >> This SF.net email is sponsored by: Microsoft >> Defy all challenges. Microsoft(R) Visual Studio 2008. >> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ >> --------------------------------------------------------------------- >> --- >> >> _______________________________________________ >> DSpace-tech mailing list >> DSpace-tech@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> > > ---------------------------------------------------------------------- > --- > This SF.net email is sponsored by: Microsoft > Defy all challenges. Microsoft(R) Visual Studio 2008. > http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ > _______________________________________________ > DSpace-tech mailing list > DSpace-tech@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------ ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ ------------------------------ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech End of DSpace-tech Digest, Vol 23, Issue 28 ******************************************* ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
