Tango Archiving

AFAIK there are Python and C++ tools from ALBA and ELETTRA. I let them answer you with the details.

New tools are being developed for HDB++ with an api for Java and C++.

Andy
Thankyou Andy

Thanks and Regards
TCS-GMRT Team
Regards,
TCS_GMRT
Hi Rapheal
Otherwise, the solution is to have 1 archiving system per tango host, and make a custom mambo script to force the tango host you want to use.

(You have to do a custom mambo script only if you want to check your tango hosts/ databases from the same computer)

I have 1 archiving system per tango host and and using custom mambo script to force the tango host i want to use.
But the problem here is:

Lets say
I have to:

PC1 - Archive attributes of Tangohost1:port1 in Databasehost1
PC2 - Archive attributes of Tangohost1:port1, Tangohost2:port2 in Databsehost2



I am using custom mambo script in PC2 in which I am forcing the host to Tangohost1:port1 and opened mambo from here. With this, I can see the device servers of PC1, but the problem here is that
1.) when I start archiving the attributes of PC1 in PC2, its values are stored in databasehost1, not in databasehost2.
2.) I cant stop archiving the attributes of PC1 from PC2 (though message in the mambo console shows archiving successfully stopped), it has to stopped from PC1 (Don't Know Why)
3.) When I start archiving the attributes of PC1 in PC2 , archiving starts in PC1 but it doesn't reflect in PC2 (the bulb is still grey)

Thanks and Regards
TCS-GMRT Team
Regards,
TCS_GMRT
Edited 8 years ago
Your basic problem is that it is not mambo which archives the attributes, but the archivers.
Your archivers know in which database to store the data. So if mambo sees the attributes of PC1, it sees the archivers of PC1, which will store data in database1.
There is no way you can change that.
Your only solution is to use 1 single archiving database (as I proposed you, and this is what I meant when I said you have configure the archivers the same way), not 1 per tango host.
Rg
Hi Rapheal

I know that the archivers archive the attributes. I am just telling the problem i am facing by using mambo.
My requirement is to have 1 archiving system per tango host, not single archiving system across all hosts. Is workaround possible for this type of requirement ?

Thanks and Regards
TCS-GMRT Team
Regards,
TCS_GMRT
If you have 1 archiving database per tango host, you have to use 1 mambo per tango host. I don't see any other solution…
Rg
Hi Rapheal

1.) I am archiving nearly 150 attributes in HDB at 1 second (I have defined the shortPeriodAttributes in HdbArchiverClass Property).
Problem I am facing is, Its not uniformly archiving the attributes at 1 second means sometimes the archiving is at 1 second or 2 second or 4 second.
Similar problem i am facing in TDB.

2.) One more thing I need to clear, till what period TDB keeps the data ( I am not executing TDB-Cleaner script).
Actually the requirement is to keep data for longer period of time, lets say 5 years. So if i prefer to choose to do archiving at TDB, data wont get deleted for how much time ? because advantage of using TDB is, its archiving frequency is higher than hdb and also I dont have to define shortperiodatrributes property.

3.) I am trying to use difference mode in HDB/TDB. I am unable to set it without checking periodic mode. But I dont want to set periodic mode. Any Workaround possible ?

4.) I have around 6000 attributes to archive. How can it be done effectively using HDB/TDB archiver ?

5.) When can i expect the HDB++ release ? It must be having advantage above the present archiving suite.


Thanks and Regards
TCS_GMRT Team
Regards,
TCS_GMRT
TCS_GMRT
5.) When can i expect the HDB++ release ? It must be having advantage above the present archiving suite.

Hi gmrt,
I'll answer just to the fifth point. We're planning some debian packages to be released before ICALEPCS 2015,
e.g. before mid october.

Cheers,
Lorenzo
Hello Rapheal

I have defined exportPeiod in class porperty of TdbArchiver.
I have defined as ExportPeriod=180000

Its exporting in database from .dat file in every 180 second.

I want to export some attribute at 180 second and some at 1 second.
I have changed the .ac xml file also in which i have defined exportPeriod according to my need.
But its still exporting to database at 180 second which i have defined in class property.

How can I have different export period for different attributes ?

Also I have posted some queries in my previous post which is still unsolved.
Waiting for your reply to solve my queries. Thankyou.

Thanks and Regards
TCS-GMRT TEAM
Regards,
TCS_GMRT
Edited 8 years ago
Hello All

1.) I am archiving nearly 150 attributes in HDB at 1 second (I have defined the shortPeriodAttributes in HdbArchiverClass Property).
Problem I am facing is, Its not uniformly archiving the attributes at 1 second means sometimes the archiving is at 1 second or 2 second or 4 second.
Similar problem i am facing in TDB.

2.)I am trying to use difference mode in HDB/TDB. I am unable to set it without checking periodic mode. But I don't want to set periodic mode. Any Workaround possible ?

3.) I have around 6000 attributes to archive. How can it be done effectively using HDB/TDB archiver ?

4.) How can I have different export period for different attributes in TdbArchiver ? I tried to modify exportPeriod property in .ac file but it isn't working.

Any help will be appreciated

Thanks and Regards
TCS-GMRT TEAM

Regards,
TCS_GMRT
 
Register or login to create to post a reply.