Instiki users - Aug 2005 - [Instiki] Madeleine corruption - How big a concern

I have been successful in getting several projects of mine to use 
Instiki as our collaboration tool.

After reading the posts from May about the storage corruption, I am a 
little concerned.  Has this problem been resolved?  Was it ever a big 
problem?

I am backing up the storage directory, but I wonder if I am being silly 
backing up all the snapshot files (which are really a series of backups 
in their on right, correct?)

Any guidance appreciated.

Steve

Although the snapshot and command log files do provide backup, you 
should always have an off-site backup if you want true recovery 
protection.  The corruption people have discussed generally affects the 
last snapshot or command log, so you could roll back to the snapshot 
before then. I view it as an inconvenience more than a big problem 
given how rarely it happens and that version 10.2 protects the Wiki as 
a whole from malformed pages causing markup errors.  However, I and a 
couple of others have seen a problem where snapshots do not get taken 
regularly, although I do not know to what degree if at all this happens 
to others.

Bottom line: If you have Wikis you really want to protect, you should 
verify that snapshots get created regularly, backup the command log and 
a few of the most recent snapshots regulary, then keep that backup 
off-site.

Oh, and do a full recovery test to make sure you actually have the 
backup you think you have.

Tam?s



On Aug 4, 2005, at 6:47 PM, Steve Downey wrote:

I have been successful in getting several projects of mine to use 
Instiki as our collaboration tool.

After reading the posts from May about the storage corruption, I am a 
little concerned.  Has this problem been resolved?  Was it ever a big 
problem?

I am backing up the storage directory, but I wonder if I am being silly 
backing up all the snapshot files (which are really a series of backups 
in their on right, correct?)

Any guidance appreciated.
_______________________________________________
Instiki-users mailing list
Instiki-users@rubyforge.org
http://rubyforge.org/mailman/listinfo/instiki-users

> Bottom line: If you have Wikis you really want to protect, you should
> verify that snapshots get created regularly, backup the command log and
> a few of the most recent snapshots regulary, then keep that backup
> off-site.
I''ve noticed that the problem may actually be in ZLib itself.
I''ve got
a corrupted snapshot that can''t be unpacked in ruby or python using
zlib bindings or cygwin (g)unzip. I then opened the file in 7-Zip,
unpacked the (annonymous) contents and re-zipped them in GZip format.
I could then use that as the snapshot for Instiki. I haven''t been able
to isolate what causes the rare corruption though.

So backing backup like mad is always a good idea, but there may be a
work-around if a corruption occurs.

Cheers,
Assaph

Assaph Mehr wrote:
>>Bottom line: If you have Wikis you really want to protect, you should
>>verify that snapshots get created regularly, backup the command log and
>>    
>>
Adding two more commands to the Web creator''s page would take care of 
the back up issue, it seems.

1) Delete the current wiki.

2) rebuild the current wiki from a Textile dump of the wiki