ADSM-L

Re: File scan takes ages during backup

2003-03-24 08:48:02
Subject: Re: File scan takes ages during backup
From: Alan Davenport <Alan.Davenport AT SELECTIVE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 24 Mar 2003 08:46:45 -0500
Geoff,

        Did IBM say why the notifyfilter parameter was significant? I'm
curious what that controls.

All others,

        The notfiybuffersize parameter is too small by default I've been
making it NotifyBufferSize=0x00500000 on all new installations of the
journal service and since I have, I have not had any problems. The journal
service has been running flawlessly. Be advised that the notify buffer size
is PER DRIVE JOURNALED. If you have many logical drives on your server you
will use a LOT of RAM for the service.

        Take care,
           Al

Alan Davenport
Senior Storage Administrator
Selective Insurance Co. of America
alan.davenport AT selective DOT com
(973) 948-1306

-----Original Message-----
From: Richard Foster [mailto:Richard.Foster AT HYDRO DOT COM]
Sent: Friday, March 21, 2003 2:22 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: File scan takes ages during backup



Geoff

> I sure wish it were as easy, and great, as some make it sound.

> I have a server with almost 5 million files on it. There aren't that
> many changes that take place daily. I've installed journaling and it
> still takes over 12 hours to run the backup. No magic here.


I didn't say it was easy - in fact, it was damned hard to get it to work.
The problem was that the Journal service kept stopping. I had to open a PMR
with support. In the end I made 2 changes to the tsmjbbd.ini file:
NotifyFilter=0x00000113
NotifyBufferSize=0x00400000

I think it was the buffer size that was the key. You need to give the
journal LOTS of memory for it to keep up with all the messages the disk
handler throws at it.

Another thing we looked at was anti-virus software on the server. There was
(maybe still is) a known issue with this, which is mentioned in the Readme.
I seem to remember that this was the reason for the filter settings. Our
filter settings are not what are in the Readme, after discussions with
support. YMMV - the general idea is to cut down on all unecessary messages.
Plus we set the registry key mentioned in the Readme.

I think this has come up quite a few times already, and you'll probably
find other suggestions in the archives.

Richard Foster
Norsk Hydro asa