ByteSync Reference Manual

Data comparison

Once the Data Inventory is complete, ByteSync compares the Local Inventories and displays the results in a list.

Interface overview

  1. Filter. Use it to filter the displayed results.
  2. Page. Use this area to select the results page to be displayed.
  3. [ADD MANUAL ACTION] and [DELETE MANUAL ACTION] buttons. Use them to add or delete actions manually.
  4. Automatic actions panel. Use it to define automatic actions.
  5. Moved.
  6. List showing the results of the data comparison.

The List

The List (6) contains one line per file identity. The file identity can be seen as a path to a directory inventory part or a file inventory part. You can find more information about this below at File Identity.

The list has the following columns:

  • The first column, “ITEM”, displays the path to the file identity.
  • Then there is one column per Session Member. They are named “INVENTORY LETTER (MACHINE_NAME)” where LETTER is the letter of the Session Member and MACHINE_NAME is the name of their machine.
  • The “STATUS” column displays the status of the item.
  • The “ACTIONS” column displays the manual and automatic actions that apply to this item.

Filter and pagination

You can filter the results by entering text in the Filter (1) text box. This field is not case sensitive.

You can search for items by:

  • Part of their file name
  • Their signature, starting from the beginning

The results are divided into pages of 20 items. You can use the pagination buttons (2) to navigate between pages.

File identity

The file identity is defined by :

  • The type of the inventory part to which the file belongs.
    The type of the inventory part is Directory if the file was identified in a directory selected by a Session Member.
    The type of the inventory part is File if the file is a file selected by a Session Member.
  • The relative path to the file.
    If the inventory part is a directory, the relative path will be of the form ‘\dir1\dir2…\dirN\file1.txt’, where each directory is a subdirectory of the root directory.
    If the inventory part is a file, the path will be formed only by the file name.

The file identity is shown in the “ITEM” column of the List (6).

“INVENTORY” columns

There is an “INVENTORY” column for each inventory, i.e. per Session Member.
For example, if the session has 3 members, there will be an INVENTORY A column, an INVENTORY B column and an INVENTORY C column.
For ease of identification, the column name also contains the machine name.

The data in each cell can be :

  • Blank. This occurs when the file identity is not present in the inventory.
  • One or more content description blocks. There will be as many content description blocks as there are different contents for a file identity.

The content is defined by the signature and by the file size. If both properties are the same, the content will be common. Otherwise there will be several blocks.

If a file identity exists on different inventories with the same content but different last write times, only one content description block will be used. The last write times will be grouped on the left side, with the corresponding inventory parts grouped on the right side.

Example of a content description block

In this example :

  • The short signature is C8E709D8…6953FEA0.919.
  • The size is 2.1 MB
  • The last write time is 14/05/2021 14:31:49 on data source A1.

You can have more details by hovering over the control. A tooltip is displayed showing the full signature fingerprint and size in bytes.

Status column

The “STATUS” column displays a summary of the contents of the file identity.

If all contents and dates are identical, this pictogram is used:

Otherwise a 2 row pictogram is used. The first line shows information about signatures. The last line shows information about the last hours of writing.

Actions column

The “ACTIONS” column shows the actions that have been defined.

By default, there are no actions defined. You can add manual actions and/or automatic actions (see below).

How to manage synchronization actions


More information can be found at Defining Actions.

Running the synchronization actions

When all actions are defined, the Cloud Session creator can click [RUN SYNCHRONIZATION] to start synchronization.

More information can be found at Running synchronization.