If your backup script using HSI often fails

Important:

Files containing PHI must be encrypted when they are stored (at rest) and when they are transferred between networked systems (in transit). To ensure that files containing PHI are encrypted when they are stored, encrypt them before transferring them to storage. To ensure that files containing PHI remain encrypted during transit, use SFTP/SCP or the IU Globus Web App. For more, see Recommended tools for encrypting data containing HIPAA-regulated PHI.

If your backup script using HSI sometimes works but often fails, make sure you are using the correct class of service (COS) while putting files into Indiana University's Scholarly Data Archive (SDA).

This is especially important if you are doing backups using a command-line pipe into HSI. Because the amount of data is unknown to SDA beforehand, the service cannot choose the correct COS automatically, so you must specify it depending on the file size. For backups larger than 64 MB, specify COS 3, using cos=3 in HSI. In HSI, you can use the lscos command to show the available classes of service.

For help with HSI commands and options, see the HSI Reference Manual. If you have questions or need help with classes of service on the SDA, email the UITS Research Storage team (store-admin@iu.edu).

This is document auht in the Knowledge Base.
Last modified on 2023-10-03 09:54:28.