backup strategies

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

backup strategies

Nick
Hi,

Looking at the /opt/gemstone/product/seaside/bin/runBackup, the keys lines appear to be:

  (System suspendCheckpointsForMinutes: 5)
    ifTrue: [
      System performOnServer: 'cp $GEMSTONE_DATADIR/extent0.dbf $GEMSTONE_DATADIR/backups'.
    ].
] ensure: [ System resumeCheckpoints].

However page 187 of the GS64 SysAdminGuide shows:
    SystemRepository fullBackupTo: 'backup' MBytes: 0

Are the two methods equivalent? If not is one to be preferred over the other?

Thanks

Nick

Reply | Threaded
Open this post in threaded view
|

Re: backup strategies

Monty Williams-3
Hi Nick,

They perform the same function using different approaches. If your repository is large and highly active you might not want to use the file copy form, but if it's small it's simple, quick, and efficient. You'll note the file copy would not work as coded if your repository has multiple extents. 

-- Monty


From: "Nick Ager" <[hidden email]>
To: "GemStone Seaside beta discussion" <[hidden email]>
Sent: Monday, January 31, 2011 6:35:25 AM
Subject: [GS/SS Beta] backup strategies

Hi,

Looking at the /opt/gemstone/product/seaside/bin/runBackup, the keys lines appear to be:

  (System suspendCheckpointsForMinutes: 5)
    ifTrue: [
      System performOnServer: 'cp $GEMSTONE_DATADIR/extent0.dbf $GEMSTONE_DATADIR/backups'.
    ].
] ensure: [ System resumeCheckpoints].

However page 187 of the GS64 SysAdminGuide shows:
    SystemRepository fullBackupTo: 'backup' MBytes: 0

Are the two methods equivalent? If not is one to be preferred over the other?

Thanks

Nick

Reply | Threaded
Open this post in threaded view
|

Re: backup strategies

Dale Henrichs
In reply to this post by Nick
Nick,

For production I recommend that you use full backups.

Full backups are used by the GemTools for backups. There a number of
options for restoring from full backups so the restore procedure can be
bit complicated (just look at the GemTools restore code for an example)
but for production it is worth reading the documentation and being
familiar with the various restore procedures.

With the "suspend checkpoints" technique you make a copy of the extent
and to restore you shut down the stone, copy in the backup and restart
the stone ... no need to read the manual to figure out how to do the
restore. The disadvantage is that you don't have as many options as you
with with restore from backup...

I'll probably switch the runBackup script to use full backup in the
future...

Dale

On 01/31/2011 06:35 AM, Nick Ager wrote:

> Hi,
>
> Looking at the /opt/gemstone/product/seaside/bin/runBackup, the keys
> lines appear to be:
>
>    (System suspendCheckpointsForMinutes: 5)
>      ifTrue: [
>        System performOnServer: 'cp $GEMSTONE_DATADIR/extent0.dbf
> $GEMSTONE_DATADIR/backups'.
>      ].
> ] ensure: [ System resumeCheckpoints].
>
> However page 187 of the GS64 SysAdminGuide shows:
>      SystemRepository fullBackupTo: 'backup' MBytes: 0
>
> Are the two methods equivalent? If not is one to be preferred over the
> other?
>
> Thanks
>
> Nick
>