How to import with postRestURL and status=413 upload too large

No Solution Yet! :/
Anyone can help us?
Administrators?

Its a bug version?

Regards,

Rafael

If someone find the solution for this problem in some other place please post here.

I don't know exactly if Zimbra is interested in their users.
Anyway. I contacted the support (as a FOSS user) and (for what I am very thankful) they answered me.
So the only solution from Zimbra here is to NOT do what we want to do.
It seems Zimbra is absolutely unable to import via postRestURL.
As what I could find out this may be not a problem regarding the MaxUploadFileSize or whatever, more it could be that in the exported tgz mailbox file there are just to many files. Maybe 8700 or 8800 files are somewhat a limit for the FileUploadServlet.java which maybe has to do something with the import.

The greatest thing of all is that exporting a users mailbox works great.
The import doesn't work for larger mailboxes.

Another great thing is that this procedure is shown in an "official" blog post on Zimbra servers.
So it's very ridiculous that the import of bigger files doesn't work at all.

Nevermind. FOSS users don't get support. As you can see in this topic.
I don't even think if we were NE users there would be a solution...

The only thing Zimbra can advise is to upgrade the old server.

But this is what we absolutely don't want.
Our old server is a Ubuntu 10.04 x64 virtual machine which was upgraded from 8.04.
And from Zimbra 5 to 6 to 7 and now to 8 ??? No way, what we want is a fresh and clean install in a newly setup virtual machine with v8 of zimbra.

Maybe this works better in NE with the cool zmbackup and zmrestore commands.
Great tip from support. But FOSS users don't have these commands and so can f*** off.

But: This is impossible. Sorry to say, but this is really really bad.

We will stay at v7, return to the old mail server after struggling around for 2 days and nearly 2 nights now.

What we keep in mind? Never ever try to update to a clean server again.
This is not supported and not wanted by zimbra.

We will stay at v7 and will never update anything again.
This software sucks.

In the past years Mr. "phoenix" saved me a lot of trouble. This is what I really have to remark. His statements always were a good help and I got him to know as a very good supporter who is keen on zimbra and has a great knowledge.
In this topic I missed him very much.

I don't know if this has something to do with my yelling "urgent urgent urgent" on and on. Maybe. Okay.

But you see - at this point there is no "real" solution. Just do an upgrade and you're done - is not what we wanted...

I really hope that there might be a solution for other folks out there....
Maybe someone could show off here how it's working...

Just my 2 cents... :-/

After further reading exactly this problem exists since 2009 or 2010. And it really seems Zimbra does not even notice this situation as something to fix.
This is sooo ridiculous... OMG...

I've seen reports regarding this issue, i've also have seen workarunds reducing the resulting file or splitting in many files as necesary.

Again, don't wanna blame Zimbra for this issue, but at least, we can just take the workaround.

ccelis

Quote:

---

Originally Posted by ccelis5215

I've seen reports regarding this issue, i've also have seen workarunds reducing the resulting file or splitting in many files as necesary.

Again, don't wanna blame Zimbra for this issue, but at least, we can just take the workaround.

ccelis

---

Where do you find this workaround ?

Quote:

---

Originally Posted by bepi

Where do you find this workaround ?

---

An example:

http://www.zimbra.com/forums/general-questions/57051-moving-local-folders-one-machine-another-xp-osx.html

of course, in this case ZD. Don't have time to dig in the forums, but i remember have seen this issue.

ccelis.

ccelis, I tried it with this workaround. This won't work either. Even if you only have 400-500 mails per subfolder (from inbox with over 10,000 mails) this is not going to work.
SOME subfolders can be exported, some can't.
So to be honest, this whole export thing is a piece of crap in FOSS edition.

As I said I contacted the support and a different way which can be tried is to bring up the old server to v8 on the old os. Then upgrade to NE with a trial key.
Take the NE backup and restore tools like zmbackup and zmrestore.
Take the backup on the old server, move the backup files to the new server.
On the new server there has to be NE v8 of course, too. That's for sure.
Then on the new server you can (maybe!?) import with zmrestore. This should work.
It should - like in FOSS edition with getRestURL and postRestURL. It should work.

So I will try this at the weekend (maybe). I don't have other cool things to do... *gg* LOL... ;-)

Quote:

---

Originally Posted by mludwig

I don't know exactly if Zimbra is interested in their users.
Anyway. I contacted the support (as a FOSS user) and (for what I am very thankful) they answered me.
So the only solution from Zimbra here is to NOT do what we want to do.
It seems Zimbra is absolutely unable to import via postRestURL.
As what I could find out this may be not a problem regarding the MaxUploadFileSize or whatever, more it could be that in the exported tgz mailbox file there are just to many files. Maybe 8700 or 8800 files are somewhat a limit for the FileUploadServlet.java which maybe has to do something with the import.

The greatest thing of all is that exporting a users mailbox works great.
The import doesn't work for larger mailboxes.

Another great thing is that this procedure is shown in an "official" blog post on Zimbra servers.
So it's very ridiculous that the import of bigger files doesn't work at all.

Nevermind. FOSS users don't get support. As you can see in this topic.
I don't even think if we were NE users there would be a solution...

The only thing Zimbra can advise is to upgrade the old server.

But this is what we absolutely don't want.
Our old server is a Ubuntu 10.04 x64 virtual machine which was upgraded from 8.04.
And from Zimbra 5 to 6 to 7 and now to 8 ??? No way, what we want is a fresh and clean install in a newly setup virtual machine with v8 of zimbra.

Maybe this works better in NE with the cool zmbackup and zmrestore commands.
Great tip from support. But FOSS users don't have these commands and so can f*** off.

But: This is impossible. Sorry to say, but this is really really bad.

We will stay at v7, return to the old mail server after struggling around for 2 days and nearly 2 nights now.

What we keep in mind? Never ever try to update to a clean server again.
This is not supported and not wanted by zimbra.

We will stay at v7 and will never update anything again.
This software sucks.

In the past years Mr. "phoenix" saved me a lot of trouble. This is what I really have to remark. His statements always were a good help and I got him to know as a very good supporter who is keen on zimbra and has a great knowledge.
In this topic I missed him very much.

I don't know if this has something to do with my yelling "urgent urgent urgent" on and on. Maybe. Okay.

But you see - at this point there is no "real" solution. Just do an upgrade and you're done - is not what we wanted...

I really hope that there might be a solution for other folks out there....
Maybe someone could show off here how it's working...

Just my 2 cents... :-/

---

Hello,

I'm importing a 9.9GB account Zimbra. The solution is to change this parameter rest_request_max_upload_size.
(Excuse me for my horrible english).

From root account lunch this (up to 20GB file .tgz):
/opt/zimbra/bin/zmlocalconfig -e rest_request_max_upload_size=21474836480
su zimbra
zmmailboxdctl restart
exit

Then run the import backup account like this:
/opt/zimbra/bin/zmmailbox -z -m email postRestURL "//?fmt=tgz&resolve=reset" file.tgz

You can log the work in this file:
/opt/zimbra/log/mailbox.log

Andrea Balboni.

Hi Andrea, this sounds really interesting.
Did anyone else try this already?
I hope that I can try it again this weekend.
I will inform you here if I succeeded...