Reprocessing Copied Files

This process is optional.

The Archive Migration Tool will allow you to again copy files that have already been processed for migration. To identify files that have already been processed, note the ~ symbol and Done status. Files that have not been processed have an Available status. For example:

[] 2022 Jul 26 (Available: 1Gb)
[ ~ ] 2022 Jul 26 (Done: 1Gb)

Note that the system performs the re-copy process only when all selected files already have been processed for migration. If you select a mix of already-processed files and unprocessed files, only the unprocessed files will be copied when the command is executed. That is, the system perform a normal Copy procedure instead of reprocessing any already-processed files.

To reprocess a previously copied file:

  1. Perform Steps 1–3 of the Running the Archive Migration Tool procedure.

  2. Select Archives Available from the initial menu.

  3. Select the files that you want to reprocess, and then Copy.

    When you select a file marked with ~, the tool will prompt you to confirm that want to reprocess them. For example:

    The selection has already been processed. Do you want to copy again the archives?
    [ ] Yes
    [ ] No

Once the copy process is completed, an Archive Catalog file is generated. This file contains metadata information about the archives that have been copied so far, plus additional information about Logger, such as its storage groups and their retention.

The Archive Catalog file is copied to the Amazon S3 bucket in a folder named:

Bucket_Name/event-sync/logger-archives/Tenant_ID/Logger_IP_Without_Dots/

The copied Logger archives' files will be available in folders such as:

Bucket_Name/event-sync/logger-archives/Tenant_ID/Logger_IP_Without_Dots/Storage_Group_ID/YearMonthDay/