This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 . It is not the current version, and thus it cannot be edited.
[Back to current version]   [Restore this version]

Amazon Glacier#

Amazon Glacier is a cloud-based storage service designed for long-term data archiving and backup. It offers secure, durable, and low-cost storage for infrequently accessed data. For more information, visit: Amazon Glacier Link.

---

⚠️ Important: Dependency jar files must be downloaded and placed in your CrushFTP Install Folder/plugins/ lib. ⚠️ Restart is required to load the new Glacier dependency jar. Download Link

---

⚠️ Proxy Configuration: If your server accesses the internet through a proxy, ensure that the Glacier domains are whitelisted.

---

The URL should look like this (replace the placeholders with your actual values):

glacier://{ACCESS_KEY_ID}:{SECRET_KEY_ID}@glacier.{REGION}.amazonaws.com/

Make sure to insert your Access Key, Secret key, and AWS region to form a valid connection URL for Glacier.



Select the proper region form the Server combobox. The default region is : us-east-1
Give the Vault name at Vault Name field or you can leave it empty and it will list all the Vaults you have on the given region. Upload is only allowed under a Vault folder. We hold a special "glacier" folder on the CrushFTP server which has the folder structure simulated, and "file" items which are XML pointers to the real glacier archive data. Each archive will have the following archive description:

<m><v>4</v><p>[Base64 encoded path]</p><lm>[the current date]</lm></m>

You can turn off the xml reference store by checking the "Delete local representation after upload" flag. It will delete the xml pointer one second after the upload.

Glacier task#

If you already have archives in Glacier that were ⚠️ not uploaded through CrushFTP, you can use this task to rebuild the simulated folder and file structure (XML Pointers) that CrushFTP uses.
This process happens in two steps: first, it creates an Amazon Glacier Inventory retrieval job. Once this job is completed (typically in 3–5 hours), it downloads the inventory and uses it to generate CrushFTP’s simulated folder structure and file references.
For more details, see: Amazon Valult Inventory Link



⚠️ The CrushTask must be run at least twice:

The first run: It creates the Amazon inventory job, and the job ID returned by Amazon will be stored in the glacier_info.XML file located in the Cache folder.
By default, this Cache folder points to the CrushFTP job folder, which can be found or customized in the task settings. This file is used later to track and complete the inventory retrieval process.

<?xml version="1.0" encoding="UTF-8"?>
<GlacierTask type="properties">
        <job_id>Amazon job id</job_id>
</GlacierTask>

The second run: It checks the status of the Amazon job and downloads the inventory once the job is finished. If the glacier_info.XML file exists, the task uses the stored Amazon job ID to check the current status of the job.
You can set up an Email task after the Glacier task to notify the job result, using the Amazon job status variable.
Possible values for the job status are: In progress, Failed, or Succeeded.

{glacier_job_satus}

Once the Amazon job status is Succeeded, it downloads the Glacier Vault Inventory and creates the CrushFTP's glacier folder and file(XML pointers to your archive data) structures based on glacier inventory. The archive description should have the following format:

<m><v>...</v><p>[Base64 encoded path]</p> ....</m>

If your glacier archive descriptions does not have the format like above, it will creates just the XML pointers with archive description as file name.