Scalix Forums

Initial setup had users sync'd with AD., Now migrating to OpenLDAP.
To do this, I've used omcpoutu to save a users mail,
ommodent "name" -n "ADMINISTERED-BY=scalix" to break the AD sync, then delete the user.
Finally recreate in openldap and resync followed by omcpinu.

All works great - until I come to a user with larger than 2gb mail dir.

[root@scalix archive]# omcpoutu -n "bob user" -f bob.out
File size limit exceeded

I've verified that it isn't the OS. I can use dd and create a 3gb file no problems. The bob.out file stops cold at 2gb.

How can I accomplish what I need to do as described above?

John

There's a fix for this pending, but for the moment try this:

Move some of the user's larger folders into a public folder somewhere and then do an omcpoutu. Then delete the user's remaining folders, put the folders in the public folder area back and do another omcpoutu. Do two omcpoutu's to get the user back.

I must admit I haven't tried this so I'd try it out on a smaller user before you do the big user to make sure you've got the process right -- it would be annoying if you lost some mail :-)

jch

A Scalix mailbox is made up of a number of components that you can use omcpoutu to copy individually.

Intray is obvious, Pending is the server term for the Sent Items folder and Filing Cabinet is any other folder other than Intray, Outtray and Pending tray.

So, use the -S switch for the ompoutu command followed by i, p or f.

The man page explains this in more detail and gives examples.

This may allow you to break down the size of the omcpoutu file.

Cheers

Dave

Actually, depending on the version of Scalix you're using, you might already have the fix....

If this is Scalix 9.4 or later, you can redirect omcpoutu to write to standard output, i.e.

omcpoutu -n "Bob User" -f - >bob.user.cpoutu

The purpose of this is that you can redirect the output of omcpoutu to a pipe, so that you can compress the data or so, as in

omcpoutu -n "Bob User" -f - | gzip -c -9 >bob.user.cpoutu.gz

Naturally, omcpinu can use the same syntax.

This and at least one more new option to the omcpoutu command will be fully documented in an uncoming release of Scalix.

Hope this helps,
Florian.

[root@host archive]# omcpinu -f - < file.out
File size limit exceeded

The backup via stdout worked beautifully. Unfortunately, now my CTO's email is offline because the import isn't working. Is there an updated omcpinu utility that does work?

Try

DIdn't know that was in the curent release. You learn something new every day :)

jch

I've tried it with the syntax you suggest. The original file was also gzipped, and I tried with:

zcat file.gz | omcpinu -f -

as well - still no joy

What error message do you get with the pipeline (as opposed to the straightfoward redirection)?

jch

Same exact error message as before File size limit exceeded. This is the same error that I got with omcpoutu before using the redirection that Florian mentioned.

Im having the same problem with a 7gb cpoutu file. I *really* need to get this in right away as its an executives mail as well.

I have a complete backup of the message store as well, but due to some of the changes we had to made, simply backing up and restoring the store was not an option.

Cheers.

Christian,

- are you getting this error message right at the beginning of the "restore" operation or does it run for a while (i.e. import the first 2 GB or so?).
- which shell are you using? is this bash or anything else? What OS is this?

-- Florian.

FC4, running Scalix 10 ontop of Xen 3.0.1. Using both bash and zsh.

When running `cat person.dat | omcpinu -f - ` it errors decently quick.
When running `omcpinu -f - < person.dat` it seems to go for a while, then error.

Hi,
Did this get resolved?
Best Regards
Jason

i have the same problems importing a File larger than 2 GB

Running SuSE 10 OSS, Scalix 10


Did this get resolved?
Best Regards


Stefan

I haven't seen this as a problem. My >2GB imports have worked fine.

SLES9 SP2/3 Scalix 10

Kev.