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