1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 | Index | 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 <2021> 2022 2023 2024 2025 |
<== Date ==> | <== Thread ==> |
---|
Subject: | Re: Epics Archiver Appliance Storage Question |
From: | "Wilson, Andy \(DLSLtd, RAL, LSCI\) via Tech-talk" <tech-talk at aps.anl.gov> |
To: | Abdalla Ahmad <Abdalla.Ahmad at sesame.org.jo>, EPICS tech-talk <tech-talk at aps.anl.gov>, "Manoussakis, Adamandios" <manoussakis1 at llnl.gov> |
Date: | Tue, 12 Oct 2021 08:13:17 +0000 |
Hi Adam,
It appears that the storage locations are stored in the PVTypeinfo in the MySQL database, which are set in the policies.py file when you first archive a PV.
In the case of our install, the storage locations have the environment variables in them, like below, but if they are set to the literal locations in policies.py I guess they will need updating.
Snippet from database:
Snippet from policies.py:
Cheers,
Andy
From: Tech-talk <tech-talk-bounces at aps.anl.gov> on behalf of Manoussakis, Adamandios via Tech-talk <tech-talk at aps.anl.gov>
Sent: Tuesday, October 12, 2021 08:21 To: Abdalla Ahmad <Abdalla.Ahmad at sesame.org.jo>; EPICS tech-talk <tech-talk at aps.anl.gov> Subject: RE: Epics Archiver Appliance Storage Question Thanks Abdalla, seems like it shouldn’t be too much trouble. I have tried stopping the tomcat instances, making sure the environment variable is set correctly (I did see in the policies.py file where the paths are set). I tried to restart the archiver appliance and also re-archived the pv (paused/deleted) but it still seems to be going to the old spot. It looks like the file I am using is from Hans site-specific install where it was hardcoded the paths actually for sts/mts/lts. I tried to just change the directory to see if it would work but still no success in getting the archiver to save the files in a different directory for sts.
Adam
From: Abdalla Ahmad <Abdalla.Ahmad at sesame.org.jo>
Hi Adam
I think it should be easy by changing the macro variables, I think we did this before and it was working, just make sure that you have read/write permissions on the new locations otherwise all your PVs will remain in the “Appliance Assigned” state. For your 2nd question, STORAGE_TOP is optional, the three storage locations definitions are independent, it is not mandatory for the locations or mount points to share the same “STORAGE_TOP”, you can specify each store in the appropriate mount point in your setup.
If you have enough RAM on your server, it is best practice to setup the STS using a RAM disk (the tempfs filesystem), this will improve performance on data retrieval for recent periods.
Best Regards,
Abdalla Al-Dalleh Control Engineer, SESAME Phone: +962-788183296 Email: Abdalla.ahmad at sesame.org.jo
From: Manoussakis, Adamandios via Tech-talk
Hey All,
I am planning on changing where our STS MTS and LTS are stored. Most likely will use STS MTS on the local SSD I have but wanted to move our LTS over to a NAS or some external storage. Wanted to know if there are any pitfalls to setting this up or is at as easy as changing up these values in the archappl.conf? Also was wondering about what STORAGE_TOP does if say my LONG_TERM_FOLDER does not share the same STORAGE_TOP directory for example?
ARCHAPPL_STORAGE_TOP="/arch" ARCHAPPL_SHORT_TERM_FOLDER="/arch/sts/ArchiverStore" ARCHAPPL_MEDIUM_TERM_FOLDER="/arch/mts/ArchiverStore" ARCHAPPL_LONG_TERM_FOLDER="/Network/lts/StorageExample "
Thanks, Adam
-- This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail. |