Name | Modified | Size | Downloads / Week |
---|---|---|---|
Parent folder | |||
1.0.0-release-src.zip | 2014-10-23 | 25.2 kB | |
1.0.0-release-bin.zip | 2014-10-23 | 5.7 kB | |
Totals: 2 Items | 30.9 kB | 0 |
______ _ _ _____ | ___ \ | | | / ___| | |_/ / | ___ ___| | _\ `--. _ _ _ __ ___ | ___ \ |/ _ \ / __| |/ /`--. \ | | | '_ \ / __| | |_/ / | (_) | (__| </\__/ / |_| | | | | (__ \____/|_|\___/ \___|_|\_\____/ \__, |_| |_|\___| __/ | |___/ To run BlockSync, assuming that JRE executables are in your path, run: java -jar BlockSync.jar This will provide you with the syntax to use the tool. Example: Let's say you want to push the changes to a virtual disk image from your local computer to a remote server, whose hostname is Zeus. First we'd connect to Zeus through ssh (or similar), and navigate to the directory that BlockSync has been placed in. Assuming that Ubuntu.vdi is a disk image in the same directory we'd run the following command: java -jar BlockSync.jar -s Ubuntu.vdi BlockSync will then sit idle until a connection is received. On our local computer we'd open a terminal, and navigate to the directory that BlockSync has been placed in. Assuming that Ubuntu.vdi is a disk image in the same directory we'd run the following command: java -jar BlockSync.jar -c Ubuntu.vdi Zeus -push BlockSync will then compute the differences in the files, and transfer the non-identical blocks from your local computer to the remote server. While BlockSync is working it will output details on what it's doing on your local computer. When the process has finished, BlockSync will close on your local computer and the remote server. If we wanted to reverse the process and pull the changes to a virtual disk image from the remote server to your local computer, we'd run the following command: java -jar BlockSync.jar -c Ubuntu.vdi Zeus -pull CAUTION: Remember the phrase, measure it twice and cut it once. When working with BlockSync, always be sure that you're specifying the correct file and the correct direction for changes to be applied. If either parameter is incorrect, data *will* be lost.