Just a reminder; if you are starting Spectrum from commandline on the 
Secondary, make sure to pass --secondary
$SPECROOT/bin/startSS.pl --secondary

If you run startSS without that parameter, it will first start ArchMgr.  Bad 
juju on a secondary SS.

Shunyun


-----Original Message-----
From: Kuta Pavel [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2008 6:43 AM
To: spectrum
Cc: spectrum
Subject: RE: [spectrum] DDM question

 Thanks, u have confirmed my previous guess ;-)
p.

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 25, 2008 10:09 AM
To: Kuta Pavel
Cc: [email protected]
Subject: Re: [spectrum] DDM question



Hi Pavel,

let me try to answer your questions:

1)  What do you mean by "only events"? The Event tabe stores every event with 
all information (including modelhandle) for the configured MAX_EVENT_DAYS.
The statistical table contained data for the attributes  and you could create 
reports on the data using the legacy Report Generator. Currently no statisical 
data is logged by default and I think Report Generator is no longer part of the 
product (definitely not in 9.0). This has been dropped in favor of  SRG (and 
eHealth).
The performance tap data is live polled and only temporarily stored in OC.

2) Decreasing the max event days will purge data beginning with the oldes data. 
It is a slow process. to reduce the database size you need to run additonally 
the maintenance and optimize scripts.

3) No. On the contrary - it will cause problems if Archive Manager
(ArchMgr) is running on both primary and secondary (at least with the same 
precedence). It might be possible with different precedences, but if the 
"primary" ArchMgr comes up again - you have lost the data for the time it was 
down. This data would be stored in the "secondary" and there is now way to 
synch it up. Well you probably could do manually if you are good with SQL.
However - no need to do it. If the ArchMgr is down the active SS stores the 
events in its SSdb ("locally stored events") once ArchMgr is back the events 
are written back.
If you have an problem where both primary SS and your ArchMgr are down - make 
sure you start the ArchMgr first, wait untill the "locally stored Events" are 
zero before starting the primary server again. Otherwise you will loose the 
events wich are stored in the secondary servers SSdb.

Hope that helps!

Cheers,
Joern


Mit freundlichen Gruessen - Best regards

Joern Henrichs
Senior System Engineer
Customer Support Group

Phone: +49 69 97779 342, Fax: +49 69 97779 110, Mobil: +49 173 2946155
Email: [EMAIL PROTECTED]


Voltastr. 1, 60486 Frankfurt am Main, Germany Computacenter AG & Co. oHG, mit 
Sitz in Kerpen (Amtsgericht Köln HRA 18096) Vertretungsberechtigte 
Gesellschafter:
Computacenter Aktiengesellschaft, mit Sitz in Köln (Amtsgericht Köln HRB
28384)
Vorstand: Oliver Tuszik (Vorsitzender), Hans-Georg Freitag, Frank Kottmann
Aufsichtsrat: Michael Norris (Vorsitzender) Computacenter Management GmbH, mit 
Sitz in Köln (Amtsgericht Köln HRB
28284)
Geschäftsführer: Dr. Karsten Freihube, Hans-Georg Freitag, Ulrich Irnich, Frank 
Kottmann, Reiner Louis, Jürgen Stauber, Oliver Tuszik

Visit us on the Internet: http://www.computacenter.de Visit our Online-Shop: 
https://shop.computacenter.de

This email is confidential. If you are not the intended recipient, you must not 
disclose or use the information contained in it. If you have received this mail 
in error, please tell us immediately by return email and delete the document.



             "Kuta Pavel"
             <[EMAIL PROTECTED]>
                                                                        To
             18.09.2008 14:19          "spectrum"
                                       <[email protected]>
                                                                        cc
             Please respond to
               "Kuta Pavel"                                        Subject
             <[EMAIL PROTECTED]>         [spectrum] DDM question










Hello all,

I would like to check if we same understand couple of things with DDM.

1)
Statistcial and Events>

Event Data - All events are stored in database -> OK  this means only events 
with their  HEXA codes and count of them and relations to models?
Statistical - Which statistical data are stored? Just only online "Performance 
Tab Info" ? Or is something more behind? How is it stored if "statistical" data 
should be "online" ?
could u please help with better explaination?

2)
In case of change MAX_xxxx_DAYS to less number than it was -> Will it cause 
after next run of ArchiveManager automaticel purge of older data?
Or it is valid only for new saved events? Would it be better to offline reduce  
(delete) stats data before change values?

3)
LANDSCAPE_PRECEDENCE in .configrc

Regarding documentation I understand that also (not only SS) Archive Manager 
could running in HOT STANDBAY mode.
Have u ever tried (or implemented) this scenarion? Experience/Problems?
How are events handled? Are in both databases the same? Or take over means only 
for new (after 10 precedence down)?


thannks lot for any shared experience..
P.


__________ Informace od ESET NOD32 Antivirus, verze databaze 3451
(20080918) __________

Tuto zpravu proveril ESET NOD32 Antivirus.

http://www.eset.cz


---
To unsubscribe from spectrum, send email to [EMAIL PROTECTED] with the body:
unsubscribe spectrum [EMAIL PROTECTED]



---
To unsubscribe from spectrum, send email to [EMAIL PROTECTED] with the body: 
unsubscribe spectrum [EMAIL PROTECTED]

---
To unsubscribe from spectrum, send email to [EMAIL PROTECTED] with the body: 
unsubscribe spectrum [EMAIL PROTECTED]

Reply via email to