At line 13 changed one line |
It will list all the vaults. 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:\\ |
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:\\ |
At line 17 changed one line |
You can turn off xml reference store by checking the "Delete local representation after upload" flag. It will delete the xml pointer 1 second after the upload.\\ |
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 21 changed 2 lines |
If you have archives on glacier not managed by CrusFTP, you can create crush simulated folder and file(XML pointers to your archive data) structure by this task.\\ |
It requires two step as it first creates an Amazone job, and it will download the result, once the job is finished (usually it requires 3-5 hour to finish the job), then based on the result will create the folder structure and XML pointers.(for more info : [https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html])\\ |
If you already have archives on glacier not managed by CrusFTP, you can create CrushFTP simulated folder and file(XML pointers to your archive data) structure by this task.\\ |
It requires two step as it first creates an Amazon job, and it will download the glacier inventory result, once the Amazon job is finished (usually it requires 3-5 hour to be finished), then based on the downloaded inventory will create the CrushFTP's simulated structures.(for more info : [https://docs.aws.amazon.com/amazonglacier/latest/dev/vault-inventory.html])\\ |
At line 26 changed one line |
The Crush job needs to run at least twice:\\ |
The Crush job needs to be run at least twice:\\ |
At line 35 changed one line |
2. It check job status, and download the inventory if the job is finished.\\ |
2. It checks the Amazon job status, and download the inventory when the Amazon job is finished.\\ |
If the [glacier_info.XML] exist, based on the Amazon job's id checks the result of the job, you can notify the job result using an email task after the glacier task with Amazon job status variable(values : In progress, Failed, 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. |