METHOD TO ACHIEVE DISTRIBUTION OF VERY LARGE DIRECTORY STRUCTURE (> 2GB) WITH TIVOLI SWD 3.6
Original Publication Date: 2002-Sep-19
Included in the Prior Art Database: 2003-Jun-21
METHOD TO ACHIEVE DISTRIBUTION OF VERY LARGE DIRECTORY STRUCTURE 2GB) WITH TIVOLI SWD 3.6
METHOD TO ACHIEVE DISTRIBUTION OF VERY LARGE DIRECTORY
STRUCTURE (> 2GB) WITH TIVOLI SWD 3.6
The present publication relates to the transfer of a data file between a source server and a set of target servers. A method is disclosed to transfer files across a Tivoli Sofware Distribution infrastructure, focusing on file integrity and server synchronization across time. This method has been designed to work on a Tivoli Sofware Distribution 3.6 infrastructure, but it can also work on Tivoli Sofware Distribution 4.1. The object of the method is to :
1. allow the distribution of very large directory structure. (> 2 GB)
2. allow to delay the data publication.
3. distribute only changed Files/directory between 2 versions of a repository. The method can be split in two phases:
1. Packaging with 3 intermediate steps.
2. Distribution with 2 intermediate steps.
Phase 1: Packaging
Step 1: Delta build
The two repositories are browsed to calculate the delta between both directory trees. Starting from repositories structure/differences, the process generates 4 files (although several files could be empty):
Contains list of all new files (present in REPOS N+1 but not in REPOS N) Contains also list of changed files (same name but different checksum) - Remove_files.lst:
Contains list of all removed files.(Present in REPOS N but not in N+1) Contains also list of removed directories.
Contains list of all empty directories. - Checksum:
Contains the checksum of all files listed in Add_files.lst
Step 2: Package Calculation
In this step the content of each package is calculated. The Add_files.lst list is sliced in several sub-lists. These sub-lists contain a list of files which overall size is comprised between MIN_SIZE and MAX_SIZE. The user must choose two parameters to complete the process:
- MAX_SIZE: must always be inferior to 2 GB, but can be set to any prefered value (Choice can be driven by network consideration). The highest this value is, the less number of package is built (obvious). - TOLERANCE: difference allowed in the package size in percentage around the given MAX_SIZE. Increasing the tolerance speeds up the package content calculation but can lead to the creation of a higher number of File Package Blocks. From both values, packages MIN_SIZE can be calculated. This value is equal to MAX_SIZE*(1-TOLERANCE/100)
When the original list file is totally...