Several Enquiries For The More Seasoned Scalix Admin

[propagandhi]

Ok, I am loving the scalix server, we've deployed three nodes under our enterprise license already but I have several questions:

1.) What is the best way of moving a user from one scalix node to another. Lets say one of our employees was previously working in Sydney, but we wanted to move that user to melbourne. Obviously we're connected via WAN. Is there a way to trickle a user aacross so to speak, or replicate that user across the WAN, or do I need to use the omcpoutu and omcpinu functions to completely dump the user, create the user again on the new node and then re-import? Is there a cleaner way?

2.) What archival features does scalix have. For example, we want it to archive every single message that comes in, but how is this implemented?? I see the archive server in the admin/management services, but how do I implement this?

3.) With regard to backing up users, is it vital that users be completely offline, or is there another angle of approach? Also, what inbuilt mechanisms exist for automatic backups, or do we need to rely on say a shell script such as can be found in the wiki.

I'm getting the impression that a lot of the wiki content needs revision, updating or just a complete rewrite. Of course I could be wrong, but I have a multitude of other little questions that I will be wanting to post to get the absolute most out of our scalix experience.

Thanks in advance!

[Valerion]

1.) What is the best way of moving a user from one scalix node to another. Lets say one of our employees was previously working in Sydney, but we wanted to move that user to melbourne. Obviously we're connected via WAN. Is there a way to trickle a user aacross so to speak, or replicate that user across the WAN, or do I need to use the omcpoutu and omcpinu functions to completely dump the user, create the user again on the new node and then re-import? Is there a cleaner way?

sxmboximp/sxmboxexp are better than omcpinu/omcpoutu as they achieve better control, but in essence this is the best way. Unless you use a tool like imapsync to migrate the mail, of course. SAC in its current incarnation doesn't support automated migrations. There are several bugs on the issue, but they need some deep work to get it working properly.

2.) What archival features does scalix have. For example, we want it to archive every single message that comes in, but how is this implemented?? I see the archive server in the admin/management services, but how do I implement this?

This is easy to implement. Put the neccesary line in /var/opt/scalix/??/s/sys/general.cfg and restart the Service Router (or the whole server, if you wish), and off you go. Info on the various options and how archiving can be done are on p.153 of the Administration Guide.

3.) With regard to backing up users, is it vital that users be completely offline, or is there another angle of approach? Also, what inbuilt mechanisms exist for automatic backups, or do we need to rely on say a shell script such as can be found in the wiki.

Shell scripts are the standard UNIX way of doing such things. If you plan your server right (properly set up LVM) you can have backups taken while the users are actively working on the server. They may get frozen connections for a few seconds, but that should be the only issue.

I'm getting the impression that a lot of the wiki content needs revision, updating or just a complete rewrite. Of course I could be wrong, but I have a multitude of other little questions that I will be wanting to post to get the absolute most out of our scalix experience.

Questions are the best way to learn If you feel the wiki is not up to scratch, it can easily be edited, Scalix will gladly accept any fixes or new articles.