On almost all of our customers we run a save of the detached journal
receivers (many of them every two hours for a recovery plan) off to tape.
With BRMS it's a snap to do. With native commands it's still not hard,
you'll just have to code up the save.
I suggest you append to the "journals" tape and fill it up.
Now you have all your journals on tape where they can be recovered quite
easily and you've met your retention requirement without using too much
DASD. (Then again several of us on the list sell disk so that would be OK
too, ;-) )
--
Jim Oberholtzer
Agile Technology Architects
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
Justin Taylor
Sent: Monday, February 20, 2017 10:57 AM
To: MIDRANGE-L (midrange-l@xxxxxxxxxxxx)
Subject: Audit log retention & disk space
It's been recommended that we retain our audit log journal receivers on DASD
to 3-12 months. I figured the amount of disk required for that, and it's
not good. I know that DB journals have ways to reduce their size. Is there
anything similar for the audit journals? Other than changing what's logged,
any way to reduce their size?
TIA
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe,
or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a
moment to review the archives at
http://archive.midrange.com/midrange-l.
Please contact support@xxxxxxxxxxxx for any subscription related questions.
Help support midrange.com by shopping at amazon.com with our affiliate link:
http://amzn.to/2dEadiD
As an Amazon Associate we earn from qualifying purchases.