backing up data with gemstone/s
Locked
 
|
is there any way to backup a current data set? further, is it possible to backup that current dataset and install it into another image?
thanks! ---- peace, sergio photographer, journalist, visionary http://www.ThoseOptimizeGuys.com http://www.CodingForHire.com http://www.coffee-black.com http://www.painlessfrugality.com http://www.twitter.com/sergio_101 http://www.facebook.com/sergio101 _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: backing up data with gemstone/s
|
|
Sergio,
On 26 Jun 2013, at 14:51, sergio_101 <[hidden email]> wrote: > quick question on gemstone/s.. > > is there any way to backup a current data set? yes > further, is it possible to backup that current dataset and install it into another image? yes See chapter 9 of the Gemstone System Administration guide: http://community.gemstone.com/display/GSS64/GemStoneS+64+bit+3.0.x+Documentation For specific questions on Gemstone, you can use the gemstone beta mailinglist: http://seaside.gemtalksystems.com/mailman/listinfo/beta (site down right now... Dale is busy moving servers :-) cheers Johan_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: backing up data with gemstone/s
|
|
In reply to this post by sergio_101
Ciao,
You can reference it to ConfigurationOfSIXX from : 'http://www.squeaksource.com/MetacelloRepository' Dario P.S. If i right remember i found some small SIXX problem ( ScaledDecimal read / write ) ... and .......
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: backing up data with gemstone/s
|
|
For clarity,
i work with SIXX support for port some specific data. ( Although data relating to one environment with some classes datas ) It does not interact with the gemstone management backup - restore linked by Johan. Dario
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
In reply to this post by sergio_101
As mentioned by Johan and Dario there are a few ways to do this. GemStone/S has a couple ways of making a full backup of the entire repository (image) and restoring the full backup. It is also possible to export a subset (using a native method called "passivate" or something like SIXX) and import that subset into an existing repository.
James On Jun 26, 2013, at 5:51 AM, sergio_101 <[hidden email]> wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
You should also take a look at Fuel (http://rmod.lille.inria.fr/web/pier/software/Fuel). We haven't tested it on Gemstone though.
Cheers, Max On 26.06.2013, at 16:38, James Foster <[hidden email]> wrote:
_______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: backing up data with gemstone/s
|
|
On Wed, Jun 26, 2013 at 11:46 AM, Max Leske <[hidden email]> wrote:
We discussed that a couple of times. It should not be difficult. The streams usage from Fuel has been significantly reduced. So the APi used from Stream is small.
The number of mandatory special clusters has also been reduced. There are some optional but that can be ignored. Fuel itself does not depend in any weird dependency and it's pure smalltalk.
The amount of tests of Fuel is huge so it makes the port way easier because you can validate if it works. So I think the only part that is necessary to do is to adapt Fuel serialization/materialization of basic types like Floats, decimals, strings, integers, date..
Of course, the whole Fuel team would help anyone trying to do the port. I don't have time for the port myself :( Cheers,
Mariano http://marianopeck.wordpress.com _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: backing up data with gemstone/s
|
|
In reply to this post by jgfoster
Hi James,
Can you maybe elaborate a bit on this 'passivate' method? Sounds interesting. thx Johan On 26 Jun 2013, at 16:38, James Foster <[hidden email]> wrote: > It is also possible to export a subset (using a native method called "passivate" or something like SIXX) and import that subset into an existing repository. _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
|
|
See section 11.4, "Passive Object" on pages 238-39 of http://community.gemstone.com/download/attachments/6816862/GS64-ProgGuide-3.1.pdf?version=1 (available from http://community.gemstone.com/display/GSS64/GemStoneS+64+Documentation). The introduction describes the following:
"To archive your data, you can passivate objects themselves to a file. Objects representing your data are stored into a serialized, text-based form by the GemStone class PassiveObject. PassiveObject starts with a root object and traces through its instance variables, and their instance variables, recursively until it reaches special objects (instances of SmallInteger, Character, Boolean, SmallDouble, or UndefinedObject), or classes that can be reduced to special objects (strings and numbers that are not integers), creating a representation of the object that preserves all of the values required to re-create it. The resulting network of object descriptions can be written to a file, stream, or string." James On Jun 26, 2013, at 10:16 AM, Johan Brichau <[hidden email]> wrote: > Hi James, > > Can you maybe elaborate a bit on this 'passivate' method? > Sounds interesting. > > thx > Johan > > On 26 Jun 2013, at 16:38, James Foster <[hidden email]> wrote: > >> It is also possible to export a subset (using a native method called "passivate" or something like SIXX) and import that subset into an existing repository. > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside > _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: backing up data with gemstone/s
|
|
thanks James!
Never really noticed this possibility in the manual. Good to know and interesting to use. On 26 Jun 2013, at 20:23, James Foster <[hidden email]> wrote: > See section 11.4, "Passive Object" on pages 238-39 of http://community.gemstone.com/download/attachments/6816862/GS64-ProgGuide-3.1.pdf?version=1 (available from http://community.gemstone.com/display/GSS64/GemStoneS+64+Documentation). The introduction describes the following: > > "To archive your data, you can passivate objects themselves to a file. Objects representing your data are stored into a serialized, text-based form by the GemStone class PassiveObject. PassiveObject starts with a root object and traces through its instance variables, and their instance variables, recursively until it reaches special objects (instances of SmallInteger, Character, Boolean, SmallDouble, or UndefinedObject), or classes that can be reduced to special objects (strings and numbers that are not integers), creating a representation of the object that preserves all of the values required to re-create it. The resulting network of object descriptions can be written to a file, stream, or string." > > James > > On Jun 26, 2013, at 10:16 AM, Johan Brichau <[hidden email]> wrote: > >> Hi James, >> >> Can you maybe elaborate a bit on this 'passivate' method? >> Sounds interesting. >> >> thx >> Johan >> >> On 26 Jun 2013, at 16:38, James Foster <[hidden email]> wrote: >> >>> It is also possible to export a subset (using a native method called "passivate" or something like SIXX) and import that subset into an existing repository. >> >> _______________________________________________ >> seaside mailing list >> [hidden email] >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside >> > > _______________________________________________ > seaside mailing list > [hidden email] > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
Re: backing up data with gemstone/s
|
|
Be aware that passivation recurses while traversing data structures so you may need to monkey with your stack size to passivate large data structures ...
The SIXX code avoids recursion so it doesn't take as much pampering to dump large data structures ... Dale ----- Original Message ----- | From: "Johan Brichau" <[hidden email]> | To: "Seaside - general discussion" <[hidden email]> | Sent: Wednesday, June 26, 2013 11:40:41 AM | Subject: Re: [Seaside] backing up data with gemstone/s | | thanks James! | | Never really noticed this possibility in the manual. Good to know and | interesting to use. | | On 26 Jun 2013, at 20:23, James Foster <[hidden email]> | wrote: | | > See section 11.4, "Passive Object" on pages 238-39 of | > http://community.gemstone.com/download/attachments/6816862/GS64-ProgGuide-3.1.pdf?version=1 | > (available from | > http://community.gemstone.com/display/GSS64/GemStoneS+64+Documentation). | > The introduction describes the following: | > | > "To archive your data, you can passivate objects themselves to a | > file. Objects representing your data are stored into a serialized, | > text-based form by the GemStone class PassiveObject. PassiveObject | > starts with a root object and traces through its instance | > variables, and their instance variables, recursively until it | > reaches special objects (instances of SmallInteger, Character, | > Boolean, SmallDouble, or UndefinedObject), or classes that can be | > reduced to special objects (strings and numbers that are not | > integers), creating a representation of the object that preserves | > all of the values required to re-create it. The resulting network | > of object descriptions can be written to a file, stream, or | > string." | > | > James | > | > On Jun 26, 2013, at 10:16 AM, Johan Brichau <[hidden email]> | > wrote: | > | >> Hi James, | >> | >> Can you maybe elaborate a bit on this 'passivate' method? | >> Sounds interesting. | >> | >> thx | >> Johan | >> | >> On 26 Jun 2013, at 16:38, James Foster <[hidden email]> | >> wrote: | >> | >>> It is also possible to export a subset (using a native method | >>> called "passivate" or something like SIXX) and import that | >>> subset into an existing repository. | >> | >> _______________________________________________ | >> seaside mailing list | >> [hidden email] | >> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside | >> | > | > _______________________________________________ | > seaside mailing list | > [hidden email] | > http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside | | _______________________________________________ | seaside mailing list | [hidden email] | http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside | _______________________________________________ seaside mailing list [hidden email] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside |
«
Return to Seaside General
|
1 view|%1 views
| Free forum by Nabble | Edit this page |