sync:prerequisites
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| sync:prerequisites [2021/06/02 01:59] – [Security considerations] Scott Cunliffe | sync:prerequisites [2025/01/21 22:07] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 26: | Line 26: | ||
| Then, if 100 tapes are updated, this would consume (100 x 300 bytes + 100 x 256 bytes) 55KB of uploaded data. This data is usually compressed at a ratio of 2:1, which means that the total upload bandwidth is around 28KB. | Then, if 100 tapes are updated, this would consume (100 x 300 bytes + 100 x 256 bytes) 55KB of uploaded data. This data is usually compressed at a ratio of 2:1, which means that the total upload bandwidth is around 28KB. | ||
| + | |||
| + | ===== Synchronization vectors ===== | ||
| + | |||
| + | The TapeTrack Synchronization Suite is designed in a way that it can be implemented to synchronize data using the following techniques: | ||
| + | - Direct invocation from a source computer, where the data is pushed to a TapeTrack Server. | ||
| + | - Direct invocation from the TapeTrack server where data is pulled from a source computer and then updated locally on the TapeTrack Server. | ||
| + | - Invocation via the inetd(8) service to provide a dedicated synchronization server where data can be send via the netcat(1) command. | ||
| + | - Invocation via procmail(5) to facilitate the automated processing of data via email. | ||
| ===== Security considerations ===== | ===== Security considerations ===== | ||
sync/prerequisites.1622599162.txt.gz · Last modified: 2025/01/21 22:07 (external edit)