Versions Compared

Old Version 1

changes.mady.by.user Andrew Woods

Saved on

compared with

New Version 2

changes.mady.by.user Unknown User (escowles@ucsd.edu)

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Excerpt
The Fedora 4 Backup capability allows a user, such as the repository manager, make a REST call to have the repository binaries and metadata exported to the local file system. Inversely, the Restore capability allows a user to make a REST call to have the repository restored from the contents of a previous Backup operation. In addition, with the default configuration, files are stored on disk named according to their SHA1 digest, so a filesystem backup approach can also be used.

Usage

Backup

Warning

If a POST body specifying a writeable directory (local to Fedora 4 server) is not included in the request, the backup will be written to the system temp directory.

...

  • 'binaries' directory that contains the repository "content" binaries stored in a pair-tree like structure. The filename of the binary is the SHA-1 of the content with the extension '.bin'. The directory structure in which each binary is found is three levels deep based on the SHA-1.

    • For example, binary content in the repository with a SHA-1 of "5613537644c4d081c1dc3530fdb1a2fe843e570170d3d054", would look like 

      No Format
      ├── binaries
    └── 44
        └── c4
            └── d0
                └── 44c4d081c1dc3530fdb1a2fe843e570170d3d054.bin
  • One or more "documents_00000n.bin.gz" files which contains a concatenated listing of the metadata for each of the repository objects in JSON format

    • For example 

      No Format
      { "metadata" : 
  { "id" : "87a0a8c317f1e7/jcr:system/jcr:nodeTypes/nt:unstructured//undefined/1" , 
    "contentType" : "application/json" } ,
  "content" : 
  { "key" : "87a0a8c317f1e7/jcr:system/jcr:nodeTypes/nt:unstructured//undefined/1" ,
    "parent" : "87a0a8c317f1e7/jcr:system/jcr:nodeTypes/nt:unstructured" , 
    "properties" : 
    { "http://www.jcp.org/jcr/1.0" : 
      { "primaryType" : 
        { "$name" : "nt:propertyDefinition" } , 
        "onParentVersion" : "COPY" , 
        "multiple" : false , 
        "protected" : false , 
        "availableQueryOperators" : 
          [ "jcr.operator.equal.to" , 
            "jcr.operator.greater.than" , 
            "jcr.operator.greater.than.or.equal.to" , 
            "jcr.operator.less.than" , 
            "jcr.operator.less.than.or.equal.to" , 
            "jcr.operator.like" , 
            "jcr.operator.not.equal.to" ] , 
        "requiredType" : "UNDEFINED" , 
        "mandatory" : false , 
        "autoCreated" : false } 
    } 
  } 
}

Filesystem Backup

By default, files larger than 4KB are stored on disk named after their SHA1 digest, in the directory fcrepo.binary.directory.  That is, a file with the SHA1 "a1b2c369563c0465ab82cdb2789d45ce1c3585b1" would be stored on disk in /path/to/fcrepo4-data/fcrepo.binary.directory/a1/b2/c3/a1b2c369563c0465ab82cdb2789d45ce1c3585b1.  So files in the repository can be backed up backing up the directory fcrepo.binary.directory.