The end location of the data should be the tape drive, so some software is needed to move it from Echo S3 to the tape drives.
Currently, all data goes through the file aggregator, storageD.
This means that, if we were to transfer the data to tape without using storageD, The IDS wouldn’t know about the newly uploaded files and wouldn’t be able to download them.
A separate piece of software, in addition to the upload api, is needed to make the transfer.
The following 2 designs have been considered:
Architectural Design A
Here, the data will need to be downloaded to local storage so the StorageD client can pick it up. This has a high network overhead.
Architectural Design B
If the StorageD client can get the data directly from ECHO, then it won’t have to be downloaded again. However, it will mean a change to the storageD code which may be problematic.
0 Comments