| At line 2 changed one line |
| !!Amazon Glacier |
| !!Amazon Glacier Integration\\ |
| At line 8 changed one line |
| __⚠️ Proxy Configuration__: If your server accesses the internet through a proxy, ensure that the __Glacier__ domains are whitelisted.\\ |
| __⚠️ Proxy Configuration__: If your server accesses the internet through a proxy, make sure that the required Glacier domains are whitelisted.\\ |
| At line 19 changed 2 lines |
| 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:\\ |
| Select the appropriate region from the Server dropdown menu. The default region is __us-east-1__.\\ |
| Enter the Vault Name in the corresponding field. If you leave it empty, the system will automatically list all available Vaults in the selected region. Note that uploads are only allowed inside a Vault folder.\\ |
| CrushFTP uses a special __glacier__ folder to simulate the folder structure. Files uploaded here are represented as XML pointers referencing the actual archive in Glacier. Each archive includes a description in this format:\\ |
| At line 23 changed 2 lines |
| }}} |
| 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.\\ |
| }}}\\ |
| At line 26 added 3 lines |
| You can turn off the XML reference storage by enabling the __Delete local representation after upload__ option.\\\ |
| When this is checked, the XML pointer file will be automatically deleted one second after the upload, leaving only the archived data in Glacier.\\\ |
| \\ |
| At line 34 changed one line |
| ⚠️ The CrushTask must be run at __least twice__:\\ |
| __⚠️ Important__: The CrushTask must be run at __least twice__:\\ |
| At line 46 changed 3 lines |
| 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.\\ |
| \\ |
| 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__.\\ |
| \\__ |
| At line 53 changed 2 lines |
| 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: |
| Once the Amazon job status is Succeeded, the task will download the Glacier Vault Inventory and use it to create CrushFTP’s simulated glacier folder and file structure. These files act as XML pointers referencing your archived data in Glacier.\\ |
| Each archive entry will include a description in the following format:\\ |
| At line 57 changed 2 lines |
| }}} |
| 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. |
| }}}\\ |
| This structure allows CrushFTP to represent your Glacier archives in a way that mimics a traditional folder and file system.\\ |
| \\ |
| __⚠️ Note__: If your Glacier archive descriptions do not follow the required format, CrushFTP will still create the XML pointers, but it will use the archive description as the file name instead of placing the file in a simulated folder structure.\\ |
| This means the files will appear flat (without folders), named directly after the description stored with each archive.\\\ |
| \\ |
