Path: csiph.com!usenet.pasdenom.info!weretis.net!feeder1.news.weretis.net!news.szaf.org!news.gnuher.de!news.enyo.de!.POSTED!not-for-mail From: Florian Weimer Newsgroups: comp.databases.berkeley-db Subject: Re: I have a quick question about exporting or dumping a database. Date: Fri, 10 Aug 2012 20:34:06 +0200 Lines: 23 Message-ID: <87mx22sijl.fsf@mid.deneb.enyo.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: news.enyo.de 1344623645 6007 172.17.135.6 (10 Aug 2012 18:34:05 GMT) X-Complaints-To: news@enyo.de Cancel-Lock: sha1:MueFsxJZAX+x3nRYuvWgk+uEulc= Xref: csiph.com comp.databases.berkeley-db:13 * jeff: > I have a server running Citadel which uses Berkeley DB on the back end > and I am trying to transfer the VM that is running it to a different > server and when I just copy the virtual hard drive and load it the > database is corrupt and cannot be fixed. This is odd. Are you copying a volume which is being written to? If you copy a read-only snapshot, it should work. > 1. How long should it take to dump a database? Mine is about 7.4 GB > with about 200 MB of log files right now. That mostly depends on fragmentation. About an hour would not be entirely unheard of. > 2. What is the best way to transfer the database to a different > system? I would prefer a method that does not involve downtime as this > is a production email system. You need to make the database read-only at one point, otherwise some writes will be lost. And if you change versions of Berkeley DB, you have to perform environment recovery, which also requires downtime.