Auditor Help: Migration from 3.6.2 to 4.x

Note: Versions 4.x can only migrate data and tasks not older than from Version 3.6.2. For best results, all modules of older versions should be migrated to 3.6.2 first, then all migrated to 4.x. ALL modules should be migrated at the same time

Select one of the following topics:
Migrating a Large Database
Errors Caused by Lack of Memory
Scheduled Task Migration
Manual Migration

Migrating a Large Database

The default value for Auditor DB Transaction Log maximum size is 20,000 MB. If the Auditor 3.6.2 database is large (~ 5-10 GB and more per module), the migration may fail with the error message: "Transaction log is full."

Workaround if no Auditor 4.x modules have been installed:

BEFORE Auditor 4.x installation, make sure that EcoraAuditorDSN4x (for example, EcoraAuditorDSN40, if you're installing Auditor 4.0) System DSN is not presented on the computer.
Using SQL Server Client tools (Query Analyzer, Enterprise Manager, etc.), create a new database named EcoraAuditorDB40 on the same MSSQL Server where the database for 3.6.2 Auditor was created.
Set Unrestricted file growth value for the EcoraAuditorDB40 database Transaction Log.
Set Unrestricted file growth value for the EcoraAuditorDB40 database Data Files.
Warning: Lack of adequate free disk space can cause problems during database migration. Ecora suggests that the system where MS-SQL server is installed have free space equivalent to 4-5 times the size of the Auditor 3.6.2 DB file (.mdf). This space is required during migration; the process requires the database be completely duplicated and that Microsoft's temporary log files be allowed to reach twice the database size. Note that Microsoft builds the transaction log during delete operations even if the log file is disabled.
Install an Auditor 4.x module.
Run migration.
After installation and migration are complete, shrink the EcoraAuditorDB40 database Transaction Log file.
Set 20,000 MB value for Maximum file size.

Workaround if other Auditor 4.x module(s) have already been installed and the database for Auditor 4.x has already been configured:

Run Enterprise Manager
Select the database Properties;
Set Unrestricted file growth value for the database Transaction Log.
Warning: Lack of adequate free disk space can cause problems during database migration. Ecora suggests that the system where MS-SQL server is installed have free space equivalent to 4-5 times the size of the Auditor 3.6.2 DB file (.mdf). This space is required during migration; the process requires the database be completely duplicated and that Microsoft's temporary log files be allowed to reach twice the database size. Note that Microsoft builds the transaction log during delete operations even if the log file is disabled.
Install an Auditor 4.x module.
Run migration.
After migration is complete, shrink the database Transaction Log file.
Set 20,000 MB value for Maximum file size.

Errors Caused by Lack of Memory

Example errors: "cannot allocate LOCK resource" or "insufficient system memory"

To fix errors caused by lack of memory:

make sure that the memory used by the SQL server is not restricted
if the memory used by the SQL server is restricted, increase the maximum value or select the Dynamically configured SQL Server memory option in SQL Server properties
if the memory used by the SQL server is not restricted, increase physical memory on the computer where SQL Server is installed

Scheduled Task Migration

If several modules of Auditor 3.6.2 version are installed, all modules should be migrated to version 4.x simultaneously.

During migration from Auditor 3.6.2 modules to 4.x, all schedule tasks created in 3.6.2 are copied for Auditor 4.x. Only common (for example, Patch Updates, Database Archiving, etc) tasks and tasks specific for modules upgraded to 4.x will be enabled in 4.x and disabled in Auditor 3.6.2.

Problems can occur if all modules are not upgraded:
For example, Windows and Unix modules were installed in 3.6.2 version. Unix data collection task was a parent task for Windows data collection task. Updating only the Windows module to 4.x version would mean the Unix data collection task is disabled in 4.x. So, Windows data collection task would never start unless its schedule is manually updated.

Manual Migration

If you choose NOT to accept automatic migration in the process of Auditor installation, it can be performed manually after the completion of installation process.

At the command prompt, run
%AuditorInstallationPath%\bin\migration.exe with the appropriate options for your environement (see below).

To migrate all:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrConfig+mgrDatabase+mgrReportData+mgrReports+mgrSelectionSets+mgrLicense+mgrTasks

To migrate configuration settings, discovered devices (files like idb.xml, collector.conf), and alerts, triggers:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrConfig

To migrate the database:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrDatabase

To migrate repo files and generated reports:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrReportData

To migrate custom report definitions:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrReports

To migrate selection sets:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrSelectionSets

To migrate the license(s):
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrLicense

To migrate scheduled tasks:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrTasks

To run help:
%AuditorInstallationPath%\bin\migration.exe /?

Note: To perform several migration tasks simultaneously, call them in the order they are listed above.
For example, use:
%AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrConfig+mgrDatabase but not: %AuditorInstallationPath%\bin\migration.exe /m %Module%Name /l mgrDatabase+mgrConfig.