[Kolab-devel] singleinstancestore within Cyrus (Re: Multiple Kolab's php eat all the RAM)

[Alain Spineux]

On Tue, Jan 6, 2009 at 9:45 AM, Bernhard Reiter <bernhard at intevation.de> wrote:
> On Montag, 5. Januar 2009, Alain Spineux wrote:
>> > I do not recomment singleinstancestore on the imap backend,
>> > as it might complicate backups and restores. Usually using group accounts
>> > for account-less folders you can avoid too much double storage in the
>> > common cases.
>>
>> This doesn't "complicate" the backup nor the restore,  except if you
>> want to keep this advantage during the backup and after the restore.
>> This reduce by 3 the space for my hosted domains.
>> This also require to use the good switch when using "du" :-)
>
> So it is done by hardlinks I presume.
> After a backup and restore the advantace is gone,
> which I would call a "complication". :)

It depend the tool you are using for your backup, some manage the hard links,
afio was one

> (To me a backup - restore should lead to the same situation it was started
> from, at least in the main points a 3 times size increase is a main point.)

But this is also a shrinking of 3 !

3 times less time and less space to backup, 3 times less space on disk,
3 times less time when doing a "fsck", 3 times more user on the same disk ...

Best regards.



>
>
> --
> Managing Director - Owner: www.intevation.net      (Free Software Company)
> Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
> Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
> Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
>
> _______________________________________________
> Kolab-devel mailing list
> Kolab-devel at kolab.org
> https://kolab.org/mailman/listinfo/kolab-devel
>



-- 
Alain Spineux
aspineux gmail com
May the sources be with you