TapeTrack Documentation

Because there is more to tape management than you ever realized

User Tools

Site Tools

Trace: • addtranslation2 • installing • repository • allow_deletes • delete_volumes • sources • user • warnings_and_oversight • introduction
sync:prerequisites

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
sync:prerequisites [2021/06/02 01:52] – [CPU And Bandwidth Considerations] Scott Cunliffesync:prerequisites [2025/01/21 22:07] (current) – external edit 127.0.0.1
Line 16: Line 16:
 ===== CPU And Bandwidth Considerations ===== ===== CPU And Bandwidth Considerations =====
  
-The TapeTrack Synchronization Suite programs are written in C and are optimized to use minimal bandwidth and CPU.+The TapeTrack Synchronization Suite programs are written in C and are optimized to use minimal CPU and bandwidth.
  
 To calculate the potential bandwidth used during a synchronization, the program will download a cache of volume information with each volume record consisting of approximately 300 bytes. If the volume also has a description, an additional 256 bytes may be downloaded. To calculate the potential bandwidth used during a synchronization, the program will download a cache of volume information with each volume record consisting of approximately 300 bytes. If the volume also has a description, an additional 256 bytes may be downloaded.
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 =====
Line 33: Line 41:
 In addition, all password values are also hashed using the MD5 algorithm before them being encrypted, this ensures that any memory dump of the server address space will never show the unencrypted password. In addition, all password values are also hashed using the MD5 algorithm before them being encrypted, this ensures that any memory dump of the server address space will never show the unencrypted password.
  
-<- sync:installing|Sync Installation ^ sync:introduction|introduction ^  ->+<- sync:installing|Sync Installation ^ sync:introduction|introduction ^ sync:sources|Sync Sources ->
  
sync/prerequisites.1622598739.txt.gz · Last modified: 2025/01/21 22:07 (external edit)