MSDN describes that FileMaxSize allows to set 2GB.
But it looks like that it works with range from 1 to 1023 only, at least it tries to work :)
For any values >= 1024 the export uses default cmp size = 24MB
Also is interesting that stsadm has 1024 as a maximum cabsize value.
FileMaxSize works, at least I can get 10MB package. But the export fails on my lab with FileMaxSize > 100: "FatalError: Export ran out of memory while compressing a very large file. To successfully export, turn compression off by specifying the -nofilecompression parameter."
I have tried to export 6GB site and export works only with FileMaxSize <= 100. I think "100" can depend from real site data size.
There is interesting point that error can be raised due the manifest.xml size. I think that true is somewhere near, because compression works with default size. Probably the compression can not split some long description of object from manifest.xml between several files.
Looks like a bug.
No comments:
Post a Comment
Note: Only a member of this blog may post a comment.