Re: [Evolution] Migration of existing evolution to new partition? (LONG)

On Mon, 2005-02-21 at 16:38 +0800, Not Zed wrote:
There's really not much else to it, your best bet is the source, or
ask specific questions on this list.  There are many references in the
archives to "migration" of data and backing up data, its basically the
#1 Frequently-asked & answered-Question.

Sorry but I'd have to disagree for version 2.x, what files did or did
not have to be backed up for version 1.x has indeed been covered many
times on this list.  However the file-structure has changed from 1.x to
2.x which is why I asked this question again a couple of days ago (my
message "backing up evolution 2.x" of Wed, 16 Feb 2005).

Celsun posted a message on 19 January (thread called "Back up and
restore procedures") which included AFAIK some errors (which is why I am
CC'ing you). I've been wanting to post about this earlier but have been
busy... Partly because one question remained unanswered until a couple
of days ago.

I'll include the backup and restore procedure Celsun posted with my
On Wed, 2005-01-19 at 15:59 -0500, Celsun . wrote:
evolution --force-shutdown

gconftool-2 --shutdwon

As Michael replied to this message it is better to use the gconftool-2
--dump /apps/evolution > /path/to/gconfdump.xml

cd ~

find ~/evolution/local/ -name "mbox.*" -exec rm -f {} \;

With evo 2.x data is stored in ~/.evolution, either this is a typo or
you are still backing up your old (version 1.x) data.
Secondly as I noted above the mbox.* files no longer exist. Mail is now
stored in files like:

And subfolders are stored in dirs like:

So in order to remove the indexes something like:
find ~/.evolution/ -name "*.ibex*"
find ~/.evolution/ -name "*.ev-summary*"

would be required

Also I prefer to use these commands to list all files that don't have to
be backed up in a file so the files are excluded from the backup but
aren't deleted...

I would also like to know whether or not ~/.evolution/cache should be
backed up or not.

tar -cvzf /path/to/evolution.tar.gz evolution .gconf/apps/evolution

As noted earlier this is then no longer required (or even recommended).

evolution --force-shutdown

gconftool-2 --shutdown

Again using the --dump option this is not necessary.

Rather you would use:
 gconftool-2 --load /path/to/gconfdump.xml

cd ~

tar -xvzf /path/to/evolution.tar.gz

I hope someone is willing to answer these questions once more, I'll be
happy to put my updated backup script on my website once I'm sure it
works as expected.


# Mertens Bram "M8ram"   <bram-mertens linux be>   Linux User #349737 #
# debian testing            kernel 2.6.8-1-686     i686     512MB RAM #
# 11:32:39 up 13 days, 15:19, 10 users,  load average: 1.33, 0.75, 0.42 #

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]