Re: 'open' epics backup?

[Tim Mooney <mooney@aps.anl.gov>]

----- Original Message -----
> From: "emmanuel mayssat" <emmanuel_mayssat@lynceantech.com>
> To: "Tim Mooney" <mooney@aps.anl.gov>
> Cc: tech-talk@aps.anl.gov, "Pete Jemian" <jemian@anl.gov>
> Sent: Thursday, August 25, 2011 6:41:09 PM
> Subject: Re: 'open' epics backup?
> > I use BURT for this.
> > http://www.aps.anl.gov/epics/extensions/burt/index.php
> 
> Ok, for BURT without sdds.
> Just out of curiosity,
> 1/ can you restore a subset of your PVs instead of a complete restore?

The snapshot file is ascii, so you can use a text editor.  There's no
tool for this, as far as I know

> 2/ is there a utility to compare BURT snapshot?

I use diff or tkdiff.  I don't know of any more specialized tool

> 3/ How do you generate a req file? dbl + manual edit ?

Manual edit.

> 4/ what does the Notify means in the Read Only Notify (RON), a popup
> in the GUI? In which case would that be used?

I don't use that feature, so I'm probably not the best source for use
cases.  One use would be to handle PV's that need some special user
attention.  For example, you might need to put a system into a certain
state before writing to certain PVs.  RON would allow you to include
those PVs in the request file, and remind whomever uses the snapshot
that special attention is needed.

> 5/ How does BURT compares to CASR in your opinion?

Pretty similar.  In addition to read-only and read-only-notify, casr
implements write-only, which seems valuable.

I don't do very much backing up and restoring.  We used to put a lot
of effort into BURT request files for synApps, but our users sort of
migrated away from manual save/restore.

> Thanks,
> 
> 
> 
> --
> Emmanuel

-- 
Tim Mooney (mooney@aps.anl.gov) (630)252-5417
Software Services Group (www.aps.anl.gov)
Advanced Photon Source, Argonne National Lab