Guys,
Could someone explain what is going here ? I downloaded the latest ML on
last Tuesday from here :
ftp://service.boulder.ibm.com/storage/tivoli-storage-management/maintena
nce/client/v5r3/AIX/v533/
While openeing the archive, there is a tivoli.tsm.client.jbb fileset,
and the readme says :
************************************************************************
*********************************************
Journal-based backup
Journal-based backup is supported on on the non-HSM AIX B/A client, on
JFS, JFS2, and VxFs filesystems. A backup for a particular file system
will be journal-based when the Tivoli Storage Manager journal daemon has
been installed and configured to journal the particular file system, and
a valid journal has been established for the file system.
If you install the journal daemon and it is running, then by default the
incremental command will automatically perform a journal-based backup on
selected file systems which are being monitored by the journal daemon.
In order to successfully perform a journal-based backup, several
conditions must be met. These include:
The journal daemon must be set up to monitor the file system that
contains the files and directories being backed up.
A full incremental backup has to have been run successfully at least
once on the file system being backed up.
The file space image of the file system at the server cannot have been
modified by an administrative command since the last full incremental
The storage management policy for the files being backed up cannot have
been updated since the last full incremental.
The journal daemon records changes to an object or its attributes in a
journal database. During a journal-based backup, the client obtains a
list of files that are eligible for backup from the journal database.
Journal-based backup can increase backup performance because the client
does not scan the local file system or contact the server to determine
which files to process. Journal-based backup also reduces network
traffic between the client and server.
The client filters the list based on the current include-exclude list
and processes, expires, and updates the resulting files according to
policy constraints, such as serialization. However, the client ignores
the server frequency attribute during a journal-based backup. The reason
for this is because a journal-based backup eliminates the backup version
query to the server; therefore the client does not know how many days
have transpired since the last backup of the file. Thus it is not
possible for the journal-based backup to use the frequency attribute, so
the frequency attribute is ignored.
The journal daemon does not record changes in UNIX special files.
Notes:
Journal-based backup is supported on a Version 5.2 or higher Tivoli
Storage Manager server.
When using anti-virus software, there are limitations to journal-based
backup.
A journal-based backup might not fall back to the traditional
incremental backup if the policy domain of your node is changed on the
server. This depends on when the policy set within the domain was last
updated and the date of the last incremental backup. In this case, you
must force a full traditional incremental backup to rebind the files to
the new domain. Use the nojournal option with the incremental command to
specify that you want to perform a traditional full incremental backup,
instead of the default journal-based backup.
NOJournal
Use the nojournal option with the incremental command to specify that
you want to perform a traditional full incremental backup, instead of
the default journal-based backup.
Journal-based incremental backup differs from the traditional full
incremental backup in the following ways:
Tivoli Storage Manager does not enforce non-default copy frequencies
(other than 0).
UNIX special file changes are not detected by the Journal daemon and are
not, therefore, backed up.
For these reasons, you might want to use the nojournal option
periodically to perform a traditional full incremental backup.
Supported Clients
This option is valid for the non-HSM AIX Backup/Archive client.
Options File
Place this option in the client system options file.
Syntax
<<-NOJournal-------------------------------------><-
Parameters
There are no parameters for this option.
Examples
Command line
dsmc incr "<.file space>." -nojournal
************************************************************************
**************************************
I didn't tried it so far, but at least it's here !!!
Arnaud
************************************************************************
******
Panalpina Management Ltd., Basle, Switzerland,
CIT Department Viadukstrasse 42, P.O. Box 4002 Basel/CH
Phone: +41 (61) 226 11 11, FAX: +41 (61) 226 17 01
Direct: +41 (61) 226 19 78
e-mail: arnaud.brion AT panalpina DOT com
************************************************************************
******
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Allen S. Rout
Sent: Monday, 27 March, 2006 18:38
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: TSM Journal Based Backup for AIX
>> On Sun, 26 Mar 2006 19:10:31 -0700, Andrew Raibeck
<storman AT US.IBM DOT COM> said:
> Allen, can you point me to the specific README file (link) and the
> specific line of text to which you refer?
Ahh, I've found whence cometh the egg on my face.
The version that had advertised, but did not deliver, AIX JBB was 5.3.2;
I had an informational PMR open on that, and even nattered about it here
in November. So I'll complete the self-abasement.
- Allen S. Rout
|
