If you are upgrading to Teamstudio Adviser from a recent version of Teamstudio Usage Auditor, you may be able to import the usage collected in Usage Auditor into Adviser.
Usage data can only be imported if the Usage Auditor application's server configurations were set to "Save Supporting Data" during data collection. Adviser relies on the full detail of the supporting data files to enable advanced filtering options. See Requirements below for more information.
Adviser imports usage collected in previous versions of Usage Auditor using the source files which Usage Auditor collected during scans to create usage reports.
Usage Auditor only saves these source files for servers where the server configuration was configured to Save Supporting Data. This setting appears on the server documents and can be viewed by going to Admin > Server Configuration in the Usage Auditor database:
In order to import usage, the following conditions must be met:
- Usage Auditor was configured to Save Supporting Data during scans.
- A copy of the Usage Auditor database is available on the Adviser workstation (the Notes client workstation configured to process jobs for the desired instance of Adviser).
- All servers defined in Usage Auditor have also been defined in Adviser.
- The most recent Adviser scan successfully cataloged all enabled servers.
Adviser supports importing the file formats from Usage Auditor versions 4 and 5.
Verifying Saved Supporting Data
Usage Auditor contains a view Supporting Data that can be accessed from the View > go to menu:
This view contains the raw files that Adviser will import. The view is categorized on the date on which the data was collected, and the attachment names listed in the view include the name of the server from which the data was collected.
Adviser will import data for the date ranges available in this view. To limit the amount of data imported to Adviser, make a copy of Usage Auditor and delete older entries as desired.
Gaps in the dates of these files indicate that either Save Supporting Data was disabled during the time of the gap, or Usage collection failed to run (e.g. due to the Usage workstation being shut off). In Usage Auditor 5.x, data is collected for all available activity on the server since the last successful scan; gaps smaller than 10 days should not represent missing data (in 4.x, data was collected nightly for the prior day only). If there are significant gaps (more than 10 days in 5.x), limiting the import to the data available after the gaps will improve accuracy, but shorten the reporting period.
Adviser requires all servers in the import data to be defined in Adviser and successfully scanned prior to import.
If the Usage Auditor data to be imported contains data for servers that are no longer available, or that otherwise should not be imported, create server definitions for those servers in Adviser, and disable them.
Importing Usage Auditor Data
Use the following steps to import Usage Auditor data into Adviser:
- Copy the Usage Auditor database to the Adviser workstation client.
- Review the Supporting Data view in Usage Auditor (as described above).
- Create server definitions in Adviser to match Usage Auditor, if needed (disable any servers that should not be imported).
- Run an Adviser scan (from the Settings > Servers page of the Adviser browser UI), and verify that it completes successfully.
- Open the Adviser server application in the Notes client on the Adviser Workstation, and start the import by choosing the Usage Auditor database via Actions > Upgrade / Reimport Usage.
The import operation will run as an Adviser job (similar to scans triggered in the UI), and can be monitored in the browser UI by reloading the browser app.
Importing both 4.x and 5.x Usage Auditor usage
Notes and Domino timestamps are stored with 100th of a second precision, and Usage Auditor 5.x records server activity with that same precision.
Adviser uses the timestamp of activity, precise to the 100th of a second, to guarantee the uniqueness the activity it records and imports. It is therefore safe to import overlapping usage data from 5.x as the timestamp constraint prevents duplication.
Usage Auditor version 4.x collected activity from the Domino server with a timestamp granularity of whole seconds. Importing Usage Auditor 4.x data that overlaps in time range with imported Usage Auditor 5.x data will result in some usage being recorded multiple times.