BES Logs Causing Space Problems?
Chris Whisonant
|
|
Tags: 
blackberry
infrastructure
admin
storage
maintenance
|
Comments (3)
|
Visits (1,370)
By default, BES debug logs are enabled at installation. They are not only enabled, but they have no roll-off time specified. I have seen this cause drive space issues (not to mention performance issues associated with so many heavily fragmented small files...)
![]() ![]() |
Comments (3)
This is a great tip, we've actually had our BES server stop before because the C: drive was full from the BES server logs. Actually, this has happened more than once.
Incidentally, how does an administrator turn on the SMS and PIN
messaging logging? I couldn't find it anywhere.
I looked in our log directories and the .CSV files are there for
SMS and PIN, but they are both empty.
I set this about 3 months ago and it has not yet started purging the older log folders. I even rebooted the entire server. I haven't had time to pursue this issue. I have moved the default location of the log files, so I wonder if this has anything to do with it.
So my question to you is have you gotten to the 30 day mark yet to
confirm that this actually works?
@1 - It's in the IT Policy under the PIM Sync Policy group. It'sreally vague how it's defined. This is where you can also
disable the Phone Log sync. It's not touted as SMS/PIN
logging but it does the same thing. In that PIM Sync Policy
group, there are options to "Disable PIN Messages Wireless Sync".
By default this is = true. Setting this to false will enable it.
The same goes for the "Disable SMS Messages Wireless Sync".
However, the default for "Disable Phone Call Log Wireless Sync" is
false.
@2 - When I did this the other day, the server had entries going
back to 12/2007. After enabling this log purging and restarting the
BB Services in Windows I could see the logs getting purged from the
daily folders. I'm assuming that 30 days from now the purging will
be taking place daily as expected. In your logging settings on the
BB Config screen above, is the location correct there? That should
work ok outside of the default location.