We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

Attention

Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support until your contract expires, or until May 1st, 2019, whichever occurs first. The license for ArchiveOne is perpetual; therefore the software may continue to be used independently without any updates or support indefinitely.

ArchiveOne Migration Admin Reporting

  • Last updated on

This article applies to Barracuda ArchiveOne version 7.3.1 or higher.

The ArchiveOne Migration Admin stores reports as text files in \\ARCHIVE_SERVER\Add-Ins\AOnePol\MigrationReports. After each repository is processed, a text file is stored containing the metrics and information in the status window at this point. These files are named with the following convention: <date>_<time>_<repositoryname>.txt where the date/time is the date/time the repository completed and the file was generated. It is appended with the name of the repository which completed processing. At the end of each migration run another text file is generated containing the metrics and information in the status window at this point. These files are named with the following convention: <date>_<time>.txt where the date/time is the date/time when the migration task completed and the file was generated. If the migration task only contained one repository, both the summary report and the repository-specific report files will be generated at the same time. If the migration task contains multiple repositories, the reports for each repository will be stored in turn and the final summary file will be generated at the end of the task once all repositories have completed.

Example summary report file: 20170821_154022.txt

Migration has completed successfully.
688 items out of an approximate total of 688 have been processed (100% complete)
The following section provides a detailed breakdown of progress so far:
Processed 1 out of 1 repositories as follows:
1 were completed successfully: 'Year_2015'

All processing to date: 688 items have been uploaded
Summary of counts of items in various states:
 All completed Current repository
 repositories 
Uploaded 688 0
Previously uploaded 0 0
No message file 0 0
Retrieval Failures 0 0
Upload Failures 0 0
Items In Missing Zips 0 0
Items in Corrupt Zips 0 0
General Failures 0 0
---------------------- ----------- -----------
Totals 688 0
The stub action phase has processed 45 stubs out of a possible 55235.
Processed 7 mailboxes out of a total of 8
Started on 21 August 2017 at 15:40:22
Elapsed time 12 minutes 25 seconds
Status last updated on 21 August 2017 at 15:52:46
Last updated on