DIAP is a Bash script collection that creates an experimental system by utilizing three backup nodes.
DIAP is a sophisticated toolkit consisting of Bash shell scripts designed to set up an experimental system that uses three backup nodes either between offices and homes, campuses, or over WANs. The primary purpose of the backup nodes is to store data for existing services, or if required, dedicated to storage. With DIAP, users can achieve round-robin synchronization of incremental backup pools, allowing the data source to vary from personal laptops to store files, all over unused bandwidth. Additionally, DIAP enables the dynamic control of data rates through compression, depending on the load and data availability.
DIAP already has some of the features mentioned above. Still, the shell scripts are a toolkit to support users in creating their own project as well as help the writer improve the system. Through the use of a large number of nodes (backup), the system has round-robin synchronization of incremental backup pools. The source of data ranges from various sources and is transmitted through unused bandwidth where the data rate is dynamically controlled, including compression, based on load and availability.
The DIAP download is a partially working prototype that users can build upon to create their own experimental system. The incremental data retention is a feature that can be adjusted to the organization's needs to ensure that some data is always available from any node in the backup pool quickly. If required, tapes storage can be placed in secure locations to retain older data.
DIAP is cost-effective as it avoids using prohibitively expensive packages by reusing resources and building on Open Source technologies. The system has coherent strategies across multiple sites, increasing the redundancy level significantly.
DIAP comprises layers of indexing, accounting, and a central management facility. The tool assumes that individual file encryption is the responsibility of the file owner. This does not rule out hard drive or partition encryption of individual nodes considered to reside in insecure locations. If used for such locations, physical security automatic fail-safe measures to trigger archive deposits useless upon theft can be deployed. Similar fail-safe techniques can be deployed for attempted network security breaches. Virus scanners are set to scan existing archives periodically and on entry to the archive pool.
CCTV surveillance can also be used to improve the security of the system by deterring intruders, and the protocol itself can ensure the integrity of photographic records. The protocol meets the necessary requirements according to the data protection act of 1998. References to Long-term Archive Protocol (LTAP) I-D highlight DIAP's potential to expand or become a new I-D.
The stable release 0.3.0 includes several improvements such as refined pool structure and timing, general bug fixes, and a refined website and documentation. On the other hand, release 0.3.3 alpha development includes structural changes to match the architecture design refinements.
DIAP already has some of the features mentioned above. Still, the shell scripts are a toolkit to support users in creating their own project as well as help the writer improve the system. Through the use of a large number of nodes (backup), the system has round-robin synchronization of incremental backup pools. The source of data ranges from various sources and is transmitted through unused bandwidth where the data rate is dynamically controlled, including compression, based on load and availability.
The DIAP download is a partially working prototype that users can build upon to create their own experimental system. The incremental data retention is a feature that can be adjusted to the organization's needs to ensure that some data is always available from any node in the backup pool quickly. If required, tapes storage can be placed in secure locations to retain older data.
DIAP is cost-effective as it avoids using prohibitively expensive packages by reusing resources and building on Open Source technologies. The system has coherent strategies across multiple sites, increasing the redundancy level significantly.
DIAP comprises layers of indexing, accounting, and a central management facility. The tool assumes that individual file encryption is the responsibility of the file owner. This does not rule out hard drive or partition encryption of individual nodes considered to reside in insecure locations. If used for such locations, physical security automatic fail-safe measures to trigger archive deposits useless upon theft can be deployed. Similar fail-safe techniques can be deployed for attempted network security breaches. Virus scanners are set to scan existing archives periodically and on entry to the archive pool.
CCTV surveillance can also be used to improve the security of the system by deterring intruders, and the protocol itself can ensure the integrity of photographic records. The protocol meets the necessary requirements according to the data protection act of 1998. References to Long-term Archive Protocol (LTAP) I-D highlight DIAP's potential to expand or become a new I-D.
The stable release 0.3.0 includes several improvements such as refined pool structure and timing, general bug fixes, and a refined website and documentation. On the other hand, release 0.3.3 alpha development includes structural changes to match the architecture design refinements.
What's New
Version 0.3.0 / 0.3.3 Alpha: N/A