Basic GTM Journaling - Revision history

Bhaskar at 12:23, 16 April 2011

2011-04-16T12:23:02Z

← Older revision		Revision as of 12:23, 16 April 2011
Line 29:		Line 29:
	You should periodically review journal file usage and archive/delete previous generation journal files.		You should periodically review journal file usage and archive/delete previous generation journal files.

	If you need anything more sophisticated, please ~~study~~ the Acculturation CD.		If you need anything more sophisticated, please go through the self-paced exercises in the [http://sourceforge.net/projects/fis-gtm/files/GT.M%20Acculturation%20Workshop/ GT.M Acculturation Workshop].

	~~Regards,~~

	~~-- Bhaskar~~

Shabiel at 13:36, 20 November 2010

2010-11-20T13:36:57Z

← Older revision		Revision as of 13:36, 20 November 2010
Line 2:		Line 2:

	-- Turn on before image journaling:		-- Turn on before image journaling:

	<code>		<code>
	$gtm_dist/mupip set -journal="enable,on,before" -file mumps.dat		$gtm_dist/mupip set -journal="enable,on,before" -file mumps.dat
	</code>		</code>

	* Recover a database file using the journal:		-- Recover a database file using the journal:

	<code>		<code>
	$gtm_dist/mupip journal -recover -backward mumps.mjl		$gtm_dist/mupip journal -recover -backward mumps.mjl
	</code>		</code>

	* Create a new journal file (the old journal file has a name of the form mumps.mjl_yyyydddhhmmss where ddd is the day of the year, e.g., today, June 24, 2009, is day 175):		-- Create a new journal file (the old journal file has a name of the form mumps.mjl_yyyydddhhmmss where ddd is the day of the year, e.g., today, June 24, 2009, is day 175):

	<code>		<code>
	$gtm_dist/mupip set -journal="on,before" -file mumps.dat		$gtm_dist/mupip set -journal="on,before" -file mumps.dat
Line 18:		Line 21:
	This assumes that the database file is mumps.dat and the journal file is mumps.mjl. GT.M doesn't restrict the name, and databases can be multiple regions. But these three commands are the most basic. Please use them so that you don't need a rundown to recover your database after a system crash.		This assumes that the database file is mumps.dat and the journal file is mumps.mjl. GT.M doesn't restrict the name, and databases can be multiple regions. But these three commands are the most basic. Please use them so that you don't need a rundown to recover your database after a system crash.

	* Backup database (creates a new journal file; substitute backup directory for /tmp/ in the following):		-- Backup database (creates a new journal file; substitute backup directory for /tmp/ in the following):

	<code>		<code>
	$gtm_dist/mupip backup "*" /tmp/		$gtm_dist/mupip backup "*" /tmp/

Shabiel at 13:35, 20 November 2010

2010-11-20T13:35:57Z

New page

Here are the most basic instructions to turn on and use journaling. I suggest you do this for any database files that are not throw-away.

-- Turn on before image journaling:
<code>
$gtm_dist/mupip set -journal="enable,on,before" -file mumps.dat
</code>

* Recover a database file using the journal:
<code>
$gtm_dist/mupip journal -recover -backward mumps.mjl
</code>

* Create a new journal file (the old journal file has a name of the form mumps.mjl_yyyydddhhmmss where ddd is the day of the year, e.g., today, June 24, 2009, is day 175):
<code>
$gtm_dist/mupip set -journal="on,before" -file mumps.dat
</code>

This assumes that the database file is mumps.dat and the journal file is mumps.mjl. GT.M doesn't restrict the name, and databases can be multiple regions. But these three commands are the most basic. Please use them so that you don't need a rundown to recover your database after a system crash.

* Backup database (creates a new journal file; substitute backup directory for /tmp/ in the following):
<code>
$gtm_dist/mupip backup "*" /tmp/
</code>

You should periodically review journal file usage and archive/delete previous generation journal files.

If you need anything more sophisticated, please study the Acculturation CD.

Regards,

-- Bhaskar