On 09/14/2015 03:12 PM, Mariano Martinez Peck wrote:
>
>
> On Mon, Sep 14, 2015 at 6:01 PM, Dale Henrichs
> <dale.henrichs at gemtalksystems.com
> <mailto:dale.henrichs at gemtalksystems.com>> wrote:
>
> Okay, here's the skinny on the description (you may already have
> figured it out:
>
> TDSessionDescription{
> #name:'gs_3281',
> #stoneHost:'foos.gemtalksystems.com
> <http://foos.gemtalksystems.com>',
> #stoneName:'gs_3281',
> #gemHost:'foos.gemtalksystems.com <http://foos.gemtalksystems.com>',
> #netLDI:'gs_3281_ldi',
> #gemTask:'gemnetobject',
> #userId:'DataCurator',
> #password:'swordfish',
> #backupDirectory:'/export/foos1/users/dhenrich/gsDevKitHome/gemstone/stones/gs_3281/backups/',
> #snapshotDirectory:'/export/foos1/users/dhenrich/gsDevKitHome/gemstone/stones/gs_3281/snapshots/',
> #gemstoneVersion:'3.2.8.1',
> #serverGitRoot:'/export/foos1/users/dhenrich/gsDevKitHome/gemstone/stones/gs_3281/git',
> #serverTodeRoot:'/export/foos1/users/dhenrich/gsDevKitHome/tode'}
>
>
> Yes, that was clear.
>
> You'll want to consider what you put into the name:, stoneHost:,
> stoneName:, gemHost:, netLDI:, backupDirectory:,
> snapshotDirectory:, serverGitRoot: and serverTodeRoot: fields (my
> $GS_HOME is /export/foos1/users/dhenrich/gsDevKitHome).
>
> You will want a separate copy of the description for each stone
> where the file name should match the description name which should
> match the stone name. Keep all of the copies in
> $GS_HOME/tode/sys/local/client/descriptions and the tODEClient
> will find new ones and make them available on the tODE system menu.
>
>
> Yep, I did that, and I could connect :) Even to a remote stone!
>
> The stoneHost:, stoneName:, gemHost:, and netLDI: fields should
> match the stone info you are connecting to.
>
> The serverTodeRoot: field is most likely fine ($GS_HOME/tode).
>
>
> Yes, I let that one.
>
> You can clear serverGitRoot: (empty string) since you don't use git.
>
>
>
> Done.
>
>
> You'll want to change the backupDirectory: and snapshotDirectory:
> fields to point to a pair of directories that is unique to each
> stone ... this is where the tODE backups and snapshots are stored
> ... I assume you will want to keep these separate from your
> production backup directories ...
>
>
> *mmmm I would use the same folder I guess. Is there any risk of having
> the same directory for both (my own daily backups) than those
> performed by tODE? *
>
the only risk is that you would want to avoid the possibility of
overwriting a production backup from tODE .. by accident ... there are
some tests in the image that create backups also there are some standard
scripts that use home.dbf and tode.dbf backup names (I describe those
scipts in my follow-on mail) ... there is a command `bu remove` for
removing backups as well:) so at the end of the day, it is up to you ...
it isn't hard to change where you want the tODE backups to go, so if you
are comfortable with sharing the directory then it won't be a problem
... I tend to be conservative when it comes to interacting with
production, especially when making "recommendations":)
Dale
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.gemtalksystems.com/mailman/private/glass/attachments/20150914/dea09f93/attachment-0001.html>