Thanks, Christian. That helps, but I’d like a bit of clarification. Do I understand correctly that the tbl, txt, and atv files contain the components of the XML data in the db? In other words, those three files are all that is needed to create the other files in the basex/data/fooDb directory; therefore, if I need to restore my db from an NFS backup, I should ensure that the tbl, txt, and atv files are located on an NFS server. (And I do understand that the “raw” directory and its subdirectories will also need to be on NFS.)
Joe On 1/20/17, 11:45 AM, "Christian Grün" <[email protected]> wrote: Hi Joe, I am referring to the files that are listed in our Wiki [1]: * inf and tbli will be recreated with each update * tbl, txt and atv will be updated * the remaining files will be recreated if the index is rebuilt * when using UPDINDEX, only atvl, atvr, txtl and txtr will be updated If you call OPTIMIZE ALL, all files will be recreated. Does this help? Christian [1] http://docs.basex.org/wiki/Storage_Layout On Fri, Jan 20, 2017 at 5:36 PM, Baysdon, Joseph <[email protected]> wrote: > My baseX database is accessed via an NFS mount, and I’d like to improve its > performance by moving its re-creatable files (e.g. indices) to a local disk. > For the sake of NFS backup & restore, I’d like to keep the db files which > cannot be re-created on the NFS servers. > > > > Would someone please identify which db files I can move to a local disk, and > which files cannot be re-created and therefore, must remain on NFS? > > > > > > Thanks, > > > > Joe
