TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------
The engine has a 1 gig limit. I do not know that the console does. You are
very right about backing up though. The storing of data is another matter:
Decisions is an unacceptable solution for a large enterprise. At a best,
good for a small company, it does not allow for the "rolling" up of data. I
have been through this with many companies but they were mostly small
organizations creating tools for small companies. If you are going to sell
to global corporations, you need a tool that will allow for the transfer of
data to a central site from location worldwide while still allowing the
local entities to see the data as their own.
Yes the data base can be ported to SQL but ISS does not condon this as they
will not support it and reiterating that Decisions is the solution. Does
this mean there is a problem with the ODBC port in Decisions if they will
not support it?
The data handling needs to be much more malleable so that larger
organizations can centralize the data from hundreds of engines worldwide but
still allow the data to be access locally from each site. (Included in that
is the integrity of the data transfer)
-----Original Message-----
From: Engle [SecEng], Michael T [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 23, 2000 12:04 PM
To: 'Walker Andrew'; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: Real Secure: Console dB problem
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------
An MDB file is not supposed to grow larger than 1 gigabyte.. You need to
replace that bad boy from time to time. Archive it (if you're not using
safesuite decisions, it is the only repository for your data) and replace it
with a "shell" .mdb file.. The same one that gets installed when you install
the console. The original .MDB size is 235520 bytes.
Mike
..Michael Engle
...Lehman Brothers
....Security Engineering
-----Original Message-----
From: Walker Andrew [mailto:[EMAIL PROTECTED]]
Sent: Friday, June 23, 2000 8:34 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Real Secure: Console dB problem
TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------
I have a RS management console to manage 2 network engines and a system
agent.
On the console the file rsntclientlog.mdb has grown to 1048592Kb ! and I am
now experiencing dB synchronization errors with all detectors. When I try to
synchronize with the maintain detector log I get the message "dB synch
error: The dB synchronization operation was cancelled" and a hex id
To cut a long story short, I have run the maintain console log program on 2
or 3 occasions with the aim of reducing the size of the rsclientlog.mdb. It
appears to have no effect and the size of the file has continued to
increase.
In addition I have backed up the file and archived it using ZIP as mentioned
in the documentation (I read the documentation !)
I suspect that the console .mdb has reached it's maximum size and this is
the cause of the synchronization problem with the detectors.
I'm tempted to delete the file rsntclientlog.mdb but am not sure if this is
advisable. I suspect that instead I should use the RS ODBC data source
administrator to reduce or purge the contents of the rsntclientlog.mdb file.
The detectors continue to function but eventually I get high priority errors
that indicate that the dB high watermark threshold has been reached. As
this is a client site I only visit once a week but did notice today that CPU
utilization on both network engines had reached 100 %
Has anyone come across this ?
Andrew Walker
e-mail mailto:[EMAIL PROTECTED]
web http://www.capco.com/
************************************************************************
The information in this email is confidential and is intended solely
for the addressee(s).
Access to this email by anyone else is unauthorised. If you are not
an intended recipient, you must not read, use or disseminate the
information contained in the email.
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of
The Capital Markets Company.
http://www.capco.com
***********************************************************************
