Dmitry, I mentioned in another reply in this thread that (for a unix based system) you can back up your entire image with "UnixProcess saveImageInBackgroundNicely". You could probably do something very similar to implement Brian's ReferenceStream approach in the background so that you would not need to show 'Sorry, Pier back up in action, please wait ...". The approach would be: - Fork a headless Squeak (exact copy of your running Pier application) using #forkHeadlessSqueakAndDoThenQuit. - In the child Squeak image (the headless copy of your real server), do whatever is necessary to stop serving, so your child Squeak does not try to compete with the real one that is serving your users. - In the child Squeak, do the ReferenceStream save as described by Brian. You can think of the #forkSqueak as producing an instantanious copy of your running image (using the Unix fork() system call). You can use this copy (the headless child Squeak image) to do all of your backup work without impacting the real Pier server image. This should permit you to guarantee that Pier is not being changed while you do backup, and it also should prevent the backup from having any noticeable effect on your users. If you want to try this, I suggest as a starting point to use UnixProcess class >>saveImageInBackground:nice: as an example. Change it to use #forkHeadlessSqueakAndDoThenQuit: instead of #forkHeadlessSqueakAndDo:, and replace the code that does the image save with whatever you need to pause the Pier server and do the save with ReferenceStream. HTH, Dave On Fri, May 26, 2006 at 12:54:45PM +0400, Dmitry Dorofeev wrote: >Nice and easy, thanks. > >The only question left unresolved is to how ensure that nobody >change Pier pages while I do backup. It is not quite necessary for >me personally. But would be nice to have a backup/restore functionality >embedded into Pier. That may show nice message like 'Sorry, Pier back up is >action, >please wait and try to edit this page later.' to the user who updates the >page. > >Just an idea. > >-Dmitry. > >Brian Chapados wrote: > >>This topic has come up before on the Pier (smallwiki) mailing list. Check >>these links: >> >># save/restore all data from a pier instance >>http://www.iam.unibe.ch/pipermail/smallwiki/2006-March/001773.html >>http://www.iam.unibe.ch/pipermail/smallwiki/2004-May/000615.html >>http://minnow.cc.gatech.edu/squeak/2318 >> >>I use ReferenceStreams as follows: >> >>" save Pier kernel instance " >>stream := ReferenceStream fileNamed: 'pier-export.obj'. >>stream nextPut: (PRKernel instanceNamed: 'mykernelname') root. >>stream close. >> >>" load Pier kernel from stored objects " >>stream := ReferenceStream fileNamed: 'pier-export.obj'. >>(PRKernel instanceNamed: 'mykernelname') root: stream next. >>stream close. >> >>Brian >> >> >> >>>Hi all, >>> >>>The only thing which stops me to run personal wiki on Pier is the >> >>chances >> >> >>>that I >>>can have my image corrupted. Is there any way to make a backup of Pier >> >>content >> >> >>>and full restore ? If I can run it daily would be nice. >>> >>>Thanks. >>>-Dmitry. >> >> >> >> >> >> >>_______________________________________________ >>Seaside mailing list >>Seaside(a)lists.squeakfoundation.org >>http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > >_______________________________________________ >Seaside mailing list >Seaside(a)lists.squeakfoundation.org >http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside