Moving user's mailstore to a new node

Discuss installation of Scalix software

Moderators: ScalixSupport, admin

svendsen
Posts: 15
Joined: Wed Jan 03, 2007 7:25 am

Moving user's mailstore to a new node

Postby svendsen » Thu Oct 22, 2009 10:50 am

Hi,

We have setup a multi-server environment.
We have mail1 and mail2.
mail1 was the existing Scalix server from our single-server environment, having all users and mailstores etc.
Now we have installed mail2, setup routing and dirsync - and tested, everything seems to work.

Now we want to move some of our user's mailstore to the mailnode on our new server mail2.

How do we do that? Is the only way to do an omcpoutu to a file, copy the file to the new server and do a omcpinu with the new mailnode name written explicitly?

THANKS!

svendsen
Posts: 15
Joined: Wed Jan 03, 2007 7:25 am

Re: Moving user's mailstore to a new node

Postby svendsen » Fri Oct 23, 2009 5:22 am

Here is what I've done until now. Are there any better/easier way?

1) mail1: omcpoutu user
2) mail1: scp mailbox file to mail2
3) mail1: delete user
4) mail2: create user
5) mail2: omcpinu user

One more question regarding this multi-server setup.
What exactly is the difference between:

mail1: omaddds -e -m +DIRSYNC/mail2
mail2: omaddds -i -m +DIRSYNC/mail1 -t "091022 15:30"

and

mail1: omaddds -i -m +DIRSYNC/mail2 -t "091022 15:30"
mail2: omaddds -e -m +DIRSYNC/mail1

To me it looks like the result are the same??

ltward
Posts: 309
Joined: Tue Jan 15, 2008 1:54 pm
Contact:

Re: Moving user's mailstore to a new node

Postby ltward » Fri Oct 23, 2009 10:35 am

Your migration method looks sound to me.

Regarding your dirsync question, it helps to know that dirsync is "pull" driven. In other words, the importing host controls the synchronizations. The importing host will periodically ask the other host(s) "Send me all your new stuff!". The import agreement is therefore a bit more complex, as it contains information about when to start importing and how frequently to request imports. The export agreement is typically quite simple, basically saying "Yes I'll export to that other host". You can get more complex with filters and masks etc. but most people do not.

So let's look at the agreements you posted:

mail1: omaddds -e -m +DIRSYNC/mail2
mail2: omaddds -i -m +DIRSYNC/mail1 -t "091022 15:30"


This says that beginning 0n Oct 22 2009 at 3:30 p.m., mail2 will begin requesting imports from mail1.
It also says that mail1 allows exports to mail2.

mail1: omaddds -i -m +DIRSYNC/mail2 -t "091022 15:30"
mail2: omaddds -e -m +DIRSYNC/mail1


This is the opposite. It says that on Oct 22 2009 at 3:30 p.m. mail1 will begin requesting imports from mail2.
It also says that mail2 will allow exports to mail1.


What you have shown is a reciprocal agreement, whereby both hosts request imports from, and allow exports to, the other host.


Return to “Installation”



Who is online

Users browsing this forum: No registered users and 4 guests

cron