RE: Epics Archiver Appliance Storage Question

["Shankar, Murali via Tech-talk" <tech-talk at aps.anl.gov>]

>> I have tried to stop the archiver and then rerun it but it doesn’t seem to pull in the new policies.py file when it is being run?

The policy is applied when you first add the PV to the archiver; so this will not have any effect.

>> but I would think when I delete the PV from the archiver and then place it back into the archiver that it would have the new path set for STS

Yes; this should be the effect; so I would look at your policies file and see if there is a issue there. When an archiver instance starts up and start processing new PV's; the location of the policies file is printed to the log like so 

config.org.epics.archiverappliance.config.DefaultConfigService  - Using policies file ....

Policies are cached and refreshed every minute or so; you don't need to restart the instance to have changes in your policy file take effect.

>> ${ ARCHAPPL_SHORT_TERM_FOLDER}

It may just be copy and paste but the space here will probably prevent the MACRO expansion.

Finally, to change the locations of stores, have you considered using softlinks? This is what we do; the PVTypeInfo's point to /arch/sts, /arch/mts, /arch/lts etc but these are in turn softlinks to where the data is actually stored. This may not satisfy your use case; but for us, this gives us an ability to move the stores around to different NFS mount points etc easily without having to change all the PVTypeInfos. To move storage locations, we just rsync and then flip the softlink.

Hope that helps.

Regards,

Murali