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
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
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