Page History

...

• When the Retrieval Tool starts up, it connects to DuraCloud using the connection parameters you provide and gets a list of content items in the spaces you indicate. It will then proceed to download the files from those spaces, each into a local directory named for the space, which is placed within the content directory.
• For each content item, the Retrieval Tool checks to see if there is already a local file with the same name. If so, the checksums of the two files are compared to determine if the local file is the same as the file in DuraCloud. If they match, nothing is done, and the Retrieval Tool moves on to the next file. If they do not match, the file from DuraCloud is retrieved.
• By default, when a local file exists and differs from the DuraCloud copy, the local file is renamed prior to the DuraCloud file being retrieved. If you would prefer that the local file simply be overwritten, you will need to include the overwrite command-line flag when starting the Retrieval Tool.
• As each content file is downloaded, a checksum comparison is made to ensure that the downloaded file matches the file in DuraCloud. If the checksums do not match, the file is downloaded again. This re-download will occur up to 5 times. If the checksums still do not match after the fifth attempt, a failure is indicated in the output file.
• As each file download completes, a new line is added to the retrieval tool output file in the work directory, indicating whether the download was successful or not. Files which did not change are not included in the output file.
• As the Retrieval Tool runs, it will print its status approximately every 10 minutes to indicate how many files have been checked and downloaded.
• Once all files are retrieved, the Retrieval Tool will print its final status to the command line and exit.
• As files are updated in DuraCloud, you can re-run the Retrieval Tool using the same content directory, and only the files which have been added or updated since the last run of the tool will be downloaded.

• Highlight
  color green
  New in 2.4

  A file containing the list of content files within a space can be created using the "list-only" option (-l) instead of retrieving the actual content files themselves.  The format of this text file is one content file name per line.  This can be useful for many things.

• Highlight
  color green
  New in 2.4

   Specific Specific content files can be retrieved from a space using the "list-file" option (-f) instead of retrieving all content files from a space.  This can be useful by saving lots of time and bandwidth usage.  One way to do this would be to first run a retrieval-tool command to create a file containing all content file names in a space using the "list-only" option. Then editing the text file containing the list of content names so it only contains a list of the desired content names and then use this file with the "list-file" option.

...

• To run the Retrieval Tool, open a terminal or command prompt and navigate to the directory where the Retrieval Tool jar file is located

• To display the help for the Retrieval Tool, run

  Code Block
  java -jar retrievaltool-{version}-driver.jar

• When running the Retrieval Tool, you will need to use these options:

  NoNew in 2.4

  Short Option	Long Option	Argument Expected	Required	Description	Default Value (if optional)
  -h	--host	Yes	Yes	The host address of the DuraCloud DuraStore application
  -r	--port	Yes	No	The port of the DuraCloud DuraStore application	443
  -u	--username	Yes	Yes	The username necessary to perform writes to DuraStore
  -p	--password	Yes	No	The password necessary to perform writes to DuraStore. If not specified the retrieval tool will first check to see if an environment variable named "DURACLOUD_PASSWORD" exists, if it does exist the retrieval tool will use its value as the password, otherwise you will be prompted to enter the password.	Not set
  -i	--store-id	Yes	No	The Store ID for the DuraCloud storage provider	The default store is used
  -s	--spaces	Yes	No	The space or spaces from which content will be retrieved. Either this option or -a must be included
  -a	--all-spaces	No	No	Indicates that all spaces should be retrieved; if this option is included the -s option is ignored	Not set
  -c	--content-dir	Yes	Yes	Retrieved content is stored in this local directory
  -w	--work-dir	Yes	Yes	Logs and output files will be stored in the work directory
  -o	--overwrite	No	No	Indicates that existing local files which differ from files in DuraCloud under the same path and name sould be overwritten rather than copied	Not set
  -t	--threads	Yes	No	The number of threads in the pool used to manage file transfers	3
  -d	--disable-timestamps	No	No	Indicates that timestamp information found as content item properties in DuraCloud should not be applied to local files as they are retrieved.	Not set
  -l	--list-only highlight
  color green
  New in 2.4
  No	Indicates that the retrieval tool should create a file listing the contents of the specified space rather than downloading the actual content files. The list file will be placed in the specified content directory. One list file will be created for each specified space.	Not set
  -f	--list-file
  Highlight
  color green
  Yes	No	Retrieve specific contents using content IDs in the specified file. The specified file should contain one content ID per line. This option can only operate on one space at a time.	Not set

  
  

  Examples of running the retrieval tool:

  
  

...