Versions Compared

Old Version 53

changes.mady.by.user Tim Donohue

Saved on

compared with

New Version 54

changes.mady.by.user Tim Donohue

Saved on

Key

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

...

  1. Enable Local Storage Plugin: Ensure the Replication suite is setup to use the 'LocalObjectStore' plugin
    Code Block
    # Replica store implementation class (specify one)
plugin.single.org.dspace.ctask.replicate.ObjectStore = \
    org.dspace.ctask.replicate.store.LocalObjectStore
  2. Wiki Markup
    *Configure Local Storage Folder*: Configure the location where you want all AIPs to be stored on your local filestystem. This defaults to the {{\[dspace\]/repstore}} folder. _However, we recommend changing this to at least a separate hard drive from your existing DSpace installation directory!_ This ensures that all your content will not be lost in the case of a hard drive failure.
    Code Block
    # Location of local (e.g. local, mountable, sync) object store
# ignored for non-local stores (e.g. DuraCloud)
store.dir = ${dspace.dir}/repstore
  3. Optionally Configure Subfolder Settings: Optionally, you can configure the sub-folder names (under store.dir) which will be used to store AIPs, checkm manifests (if enabled), etc.
    Code Block
    # The storage group / folder where AIPs are stored/retrieved when AIP based tasks 
# (e.g. "Transmit AIP", "Recover from AIP") are executed.
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.aip.name = aips

# The storage group / folder where Checkm Manifests are stored/retrieved when Checkm Manifest based tasks are executed
# (e.g. "Transmit Manifest", "Fetch Manifest") are executedorg.dspace.ctask.replicate.checkm.*).
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.manifest.name = manifests

# The storage group / folder where AIPs are temporarily stored/retrieved when an object deletion tasks occurs
#(e.g. "Remove AIP") are executed. This and the ReplicationConsumer is enabled (see below). Essentially, this 'delete' group provides a 
# location where deleted AIPs
# can be temporarily kept in case the deletion needs to be reverted and the object restored.
# WARNING: THIS MUST NOT BE SET TO THE SAME VALUE AS 'group.aip.name'. If it is set to the 
# same value, then your AIP backup processes will be UNSTABLE and restoration may be difficult or impossible.
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.delete.name = deletes

...

  1. Enable Local Storage Plugin: Ensure the Replication suite is setup to use the 'MountableObjectStore' plugin
    Code Block
    # Replica store implementation class (specify one)
plugin.single.org.dspace.ctask.replicate.ObjectStore = \
    org.dspace.ctask.replicate.store.MountableObjectStore
  2. Wiki Markup
    *Configure Mounted Folder*: Configure the location where you want all AIPs to be stored. The folder should already be mounted on your local filesystem. This defaults to the {{\[dspace\]/repstore}} folder.
    Code Block
    # Location of local (e.g. local, mountable, sync) object store
# ignored for non-local stores (e.g. DuraCloud)
store.dir = ${dspace.dir}/repstore
  3. Optionally Configure Subfolder Settings: Optionally, you can configure the sub-folder names (under store.dir) which will be used to store AIPs, checkm manifests (if enabled), etc.
    Code Block
    # The storage group / folder where AIPs are stored/retrieved when AIP based tasks 
# (e.g. "Transmit AIP", "Recover from AIP") are executed.
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.aip.name = aips

# The storage group / folder where Checkm Manifests are stored/retrieved when Checkm Manifest based tasks are executed
# (e.g. "Transmit Manifest", "Fetch Manifest") are executedorg.dspace.ctask.replicate.checkm.*).
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.manifest.name = manifests

# The storage group / folder where AIPs are temporarily stored/retrieved when an object deletion tasks occurs
#(e.g. "Remove AIP") are executed. This and the ReplicationConsumer is enabled (see below). Essentially, this 'delete' group provides a 
# location where deleted AIPs
# can be temporarily kept in case the deletion needs to be reverted and the object restored.
# WARNING: THIS MUST NOT BE SET TO THE SAME VALUE AS 'group.aip.name'. If it is set to the 
# same value, then your AIP backup processes will be UNSTABLE and restoration may be difficult or impossible.
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.delete.name = deletes

...

  1. Enable DuraCloud Storage Plugin: Ensure the Replication suite is setup to use the 'DuraCloudObjectStore' plugin
    Code Block
    # Replica store implementation class (specify one)
plugin.single.org.dspace.ctask.replicate.ObjectStore = \
    org.dspace.ctask.replicate.store.DuraCloudObjectStore
  2. Configure DuraCloud Spaces Primary Space to use: Your DuraCloud account allows you to separate content into various "Spaces". You'll need to create a new DuraCloud Space that your AIPs will be stored within, and configure that as your group.aip.name (by default it's set to a DuraCloud Space with ID of "aips"). You should also create a new DuraCloud Space that your AIPs will be moved to if they are ever removed, and configure that as your group.delete.name. Optionally, if you are using Checkm manifests, you can also create and configure a group.manifest.name DuraCloud Space
    Code Block
    # The storage group / folder where AIPs are stored/retrieved when AIP based tasks 
# (e.g. "Transmit AIP", "Recover from AIP") are executed.
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.aip.name = aips
  3. Optionally, Configure Additional DuraCloud Spaces: If you have chosen to utilize Checkm manifest validation, you will need to create and configure a DuraCloud Space corresponding to the group.manifest.name setting below. Additionally, if you have chosen to enable the Automatic Replication, you will need to create and configure a DuraCloud Space corresponding to the group.delete.name setting below.
    Code Block
    
 ID (Space must already exist)
group.aip.name = aips

# The storage group / folder where Checkm Manifests are stored/retrieved when Checkm Manifest based tasks are executed
# (e.g. "Transmit Manifest", "Fetch Manifest") are executedorg.dspace.ctask.replicate.checkm.*).
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.manifest.name = manifests

# The storage group / folder where AIPs are temporarily stored/retrieved when an object deletion tasks occurs
#(e.g. "Remove AIP") are executed. This and the ReplicationConsumer is enabled (see below). Essentially, this 'delete' group provides a 
# location where deleted AIPs
# can be temporarily kept in case the deletion needs to be reverted and the object restored.
# WARNING: THIS MUST NOT BE SET TO THE SAME VALUE AS 'group.aip.name'. If it is set to the 
# same value, then your AIP backup processes will be UNSTABLE and restoration may be difficult or impossible.
# For Local object stores, this group name corresponds to a subfolder in the 'store.dir'
# For DuraCloud object stores, this group name corresponds to a DuraCloud Space ID (Space must already exist)
group.delete.name = deletes

...

http://duraspace.org/duracloud.php

...