SLM ver 1.2.1

df -hT>
> /dev/cciss/c0d0p6 ext3 227G 144G 83G 64%
> /var/opt/novell/sentinel_log_mgr/data
> /dev/mpath-slm-network ext3 1.1T 114G 930G 11% /slm_archive
> /dev/loop0 squashfs 384K 384K 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121014_6E1CCA35-4BD4-102D-91D3-000C2907C76D/index
> /dev/loop1 squashfs 128K 128K 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121011_6E1CCA35-4BD4-102D-91D3-000C2907C76D/index
> /dev/loop2 squashfs 128K 128K 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121011_6E1CCA35-4BD4-102D-91CD-000C2907C76D/index
> /dev/loop3 squashfs 128K 128K 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121010_6E1CCA35-4BD4-102D-91D3-000C2907C76D/index
> /dev/loop4 squashfs 384K 384K 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121009_6E1CCA35-4BD4-102D-91CD-000C2907C76D/index
> /dev/loop5 squashfs 128K 128K 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121012_6E1CCA35-4BD4-102D-91CD-000C2907C76D/index
> /dev/loop6 squashfs 1.2M 1.2M 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121012_408E7E50-C02E-4325-B7C5-2B9FE4853476/index
> /dev/loop7 squashfs 1.3M 1.3M 0 100%
> /slm_archive/9D120730-7B2D-102F-8E4E-002481E92648/eventdata_archive/20121011_408E7E50-C02E-4325-B7C5-2B9FE4853476/index
>

once this situation happens, i.e when SLM starts indexing and
compressing the events on secondary/network storage, SLM webui response
becomes slow, esp time to complete a report become too high
comparitively.

is it some how possible to configure slm to only perform inedexing on
secondary/network storage after hours ? is it possible to schedule it ?


--
sharfuddin
------------------------------------------------------------------------
sharfuddin's Profile: https://forums.netiq.com/member.php?userid=1016
View this thread: https://forums.netiq.com/showthread.php?t=50118