The PreserveDBOnExit setting prevents the journal from being deleted when
the journaled file system the setting is specified for (in the journal
daemon configuration file) is taken offline, such as when
the journal daemon is stopped and restarted.
If the journal is empty when the journal daemon starts of course the
backup will be full incremental (and this full incremental must
successfully complete before the journal can be used again).
The only method of forcing a full incremental without taking the journal
offline is to use the NOJOURNAL client option on the backup command.
Using this option also has the advantage of keeping the journal intact
while the non-journal backup is running.
Unfortunately this option may only be specified as a command line argument
(it isn't valid in the client options file) so the only method of forcing
periodic full (non-journal) incrementals
is to define a separate schedule to run the backup with the NOJOURNAL
option.
Hope this is helpful ....
Pete Tanenhaus
IBM Spectrum Protect Client Development
email: tanenhau AT us.ibm DOT com
tie line: 620.7955, external: 607.429.7955
"Those who refuse to challenge authority are condemned to conform to it"
From: "Michaud, Luc [Analyste principal - environnement AIX]"
<Luc.Michaud2 AT STM DOT INFO>
To: ADSM-L AT VM.MARIST DOT EDU
Date: 05/10/2018 08:20 AM
Subject: Re: Can we disable client journaling with Server CLOPT ?
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Hi Steve,
The PreserveDbOnExit flag is already set. Thus we *NEVER* do run FULL
INCREMENTAL BACKUPs. Now we see that we occasionally have newer versions
of files that never actually got detected by the journal.
What I want is to - say once every month, actually *FORCE* a FULL
INCREMENTAL BACKUP of a given node, on such a setup, without changing the
actual COMMAND specified in the client schedule.
Stay tuned, could take a while however...
Regards,
Luc
-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de
Harris, Steven
Envoyé : 9 mai 2018 19:18
À : ADSM-L AT VM.MARIST DOT EDU
Objet : Re: [ADSM-L] Can we disable client journaling with Server CLOPT ?
Luc,
There is a flag you can set that stops the database from being invalidated
by a stop of the Journal service.
I have usually set this because when journaling is required, an arbitrary
full scan is usually not wanted.
Regards
Steve
Steven Harris
TSM Admin/Consultant
Canberra Australia.
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Michaud, Luc [Analyste principal - environnement AIX]
Sent: Thursday, 10 May 2018 1:12 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Can we disable client journaling with Server CLOPT ?
Hi Marc,
Thanks for the feedback.
I forgot to state that the Windows admins have historically put in place a
batch file to take backups.
It's been forked into more that 50 versions since.
None of which forward any of its cmdline arguments to the actual "dsmc i"
command.
I've since been looking at the "Journal-based backup" section of the BA
client install and users guide.
It lists about 7 possible ways to invalidate the journal db.
Most are not applicable to steady state (changed node, fs, server)
However, I see 2 ways that would work in my universe :
1. "A policy changes occurs (new policy set activation)"
2. "The journal service is not running"
3. The journal service is stopped or started for any reason, even if
it is restarted because the system is rebooted.
I think I'll focus on the 2nd way.
Looking into using DSMCAD to run "dsmcutil stop /name:"TSM Journal
Service"" and "dsmcutil start /name:"TSM Journal Service"" as one-shots.
I'll keep you guys posted.
Still open to other approaches.
Regards,
Luc
-----Message d'origine-----
De : ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] De la part de
Marc Lanteigne Envoyé : 9 mai 2018 10:29 À : ADSM-L AT VM.MARIST DOT EDU Objet
:
Re: [ADSM-L] Can we disable client journaling with Server CLOPT ?
Hi Luc,
You should be able to define a client schedule with "option=-nojournal"
So you would have two schedule. The current one, plus one that
periodically does -nojournal.
-
Thanks,
Marc...
________________________________________________________
Marc Lanteigne
Spectrum Protect Specialist AVP / SRT
416.478.0233 | marclanteigne AT ca.ibm DOT com<mailto:marclanteigne AT ca.ibm
DOT com>
Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
Follow me on: Twitter, developerWorks, LinkedIn
-----Original Message-----
From: Michaud, Luc [Analyste principal - environnement AIX] [
mailto:Luc.Michaud2 AT STM DOT INFO]
Sent: Wednesday, May 9, 2018 11:17 AM
To: ADSM-L AT VM.MARIST DOT EDU<mailto:ADSM-L AT VM.MARIST DOT EDU>
Subject: [ADSM-L] Can we disable client journaling with Server CLOPT ?
Greetings everyone,
Our shop is TSM 717000 on AIX, with lots of Win BA clients v7164 with
journaling enabled.
In a restore test of a Windows node, we found that a file that was changed
in 2017 was never backed up.
We thus kept the previous iteration (circa 2016) as active in the actual
node data.
We were led to journaling FAQ at
http://www-01.ibm.com/support/docview.wss?uid=swg21681523
So, now we are looking to implement the recommended "periodic FULL
INCREMENTAL BACKUPS".
We have no actual access to the Windows clients, except for DSMCAD...
Thus I thought of doing a periodic rotation of node clopt on the
server-side, however it seems that the NOJOURNAL option is only valid on
the dsmc command-line.
How have you guys gone about implementing this ?
Luc
This message and any attachment is confidential and may be privileged or
otherwise protected from disclosure. You should immediately delete the
message if you are not the intended recipient. If you have received this
email by mistake please delete it from your system; you should not copy
the message or disclose its content to anyone.
This electronic communication may contain general financial product advice
but should not be relied upon or construed as a recommendation of any
financial product. The information has been prepared without taking into
account your objectives, financial situation or needs. You should consider
the Product Disclosure Statement relating to the financial product and
consult your financial adviser before making a decision about whether to
acquire, hold or dispose of a financial product.
For further details on the financial product please go to
http://www.bt.com.au
Past performance is not a reliable indicator of future performance.
|
