NetPro Computing, Inc. (NetPro) makes no representations or warranties, either expressed or implied, with respect to the adequacy of this documentation or the programs which it describes in regard to fitness for any particular purpose or with respect to its adequacy to produce any particular result. The computer programs and documentation are sold “as is”, and the entire risk as to quality and performance is with the buyer. In no event shall NetPro be liable for special, direct, indirect or consequential damages resulting from any defect in the programs, documentation or software. Some states do not allow the exclusion or limitation of implied warranties or liability for incidental or consequential damages, in which case the above limitations and exclusions may not apply to you.
Proprietary Rights
NetPro has prepared this document for use by NetPro personnel, agents, licensees and customers. The information contained in this document is the property of NetPro. You may not reproduce, translate, or transmit it in any form or by any means, electronically or mechanically, without prior written permission from NetPro.
Disclaimer of Liability
NetPro makes no representation or warranties of any kind, either expressed or implied, with respect to the contents of this manual, including but not limited to typographical errors and technical completeness, NetPro reserves the right to revise this publication and to make changes in its content without obligation to notify any person of such revision or changes.
Trademarks
NetPro Computing and NetPro are registered trademarks and ChangeAuditor and the NetPro logo are trademarks of NetPro Computing, Inc.
Microsoft, Windows NT, Windows 2000, Windows Server 2003, Windows Server 2008 and Active Directory are either registered trademarks or trademarks of Microsoft Corporation.
Other product names mentioned in this manual may be trademarked: they are used for identification purposes only.
Document Revision History
NetPro Computing, Inc.
Corporate Office
4747 N. 22nd Street, Suite 400
Phoenix, Arizona 85016 USA
Telephone
602 346 3600
FAX
602 346 3610
Email [email protected]
Internet http://www.netpro.com
Sales
USA and Canada
800 998 5090
International
+1 602 346 3630
Worldwide Technical Support
USA
1 602 346 3670
USA (Toll Free)
1 866 9 NETPRO
Germany
0800 180 2577
UK
0 0800 047 0197
France
0800 917881
Table of Contents
Chapter 1: Important Notices and FAQs - - - 1
Chapter 2: Migrating a ChangeAuditor 3.x Database - - - 7
ChangeAuditor 3.x Database in Single Repository Environment - - - 7
ChangeAuditor 3.x Database in Multiple Repository Environment - - - 10
Chapter 3: Migrating a ChangeAuditor 2.x Database - - - -15
ChangeAuditor 2.x in a Single Repository Environment - - - 16
ChangeAuditor 2.x Database in Multiple Repository Environment - - - 18
Chapter 4: Database Migration Wizard - - - -21
Database Migration Wizard - - - 21
Chapter 1: Important Notices and FAQs
ChangeAuditor 4.x has changed the database schema in such a manner that ‘upgrading’ an existing database to the new schema is not possible. Because of this, ChangeAuditor 4.x requires a brand new database to be created.
Therefore, ChangeAuditor 4.x provides a migration utility to help you automate the process of moving events, searches, alerts, etc. from your existing 3.x database to your new 4.x database. This migration utility is installed automatically with the ChangeAuditor Client and is called the Database Migration wizard.
This chapter details some important notes and answers frequently asked questions regarding the migration process. It is strongly recommended that you review this chapter before you
start the data migration.
What is the database migration?
Due to the extensive changes made to the database schema in 4.x, you will need to migrate your 3.x database if you want to view/retrieve your existing events, searches, and alerts from the ChangeAuditor 4.x Client. In addition, this utility will copy your 3.x monitoring points, agent configuration, repository configuration and audit event severity assignments to your 4.x database.
NOTE: When migrating data from 2.x or 3.x, Built-In Searches and Alerts are not migrated. If you have enabled built-in alerts that you wish to use in the new 4.x environment, you must edit the alert and change the alert name to a new, unique name. The alert will save as a copy in My Alerts and will be migrated to 4.x.
Do I have to migrate my database?
No, ChangeAuditor 4.x does not require you to migrate your old database to the new one. You can simply create a brand new 4.x database and configure your repository to use the new database and the skip the migration steps of the installation.
2 ChangeAuditor
Important Notices and FAQs
What is lost if I do not migrate my existing database?
If you choose not to migrate your database you will not be able to view/retrieve your existing events in the new 4.x database. In addition you will have to manually re-create any searches, alerts, agent configurations, and repository configurations in the new 4.x database.
If you do not migrate your data, you can keep the 3.x database online and connect to it with a 3.x client only to view historical events. After you have fully deployed 4.x agents, however, all new events will only go into the 4.x database.
What access rights are required to run the Database Migration Wizard?
• The migration utility must be run as a User with Read access to the Global Catalog. • The destination (4.x) database credentials must have either db owner or
ChangeAuditor_Administrators role access. For more information on the ChangeAuditor_Administrators role access, please refer to the ChangeAuditor
Installation Guide.
• The source (3.x) database must have db owner access. Where should I run the Database Migration Wizard?
For the best performance, it is recommended that you run the Database Migration wizard on your SQL Server machine. We recommend that the 4.x Client be installed on that machine using the appropriate NetPro ChangeAuditor Client 4 msi.
Can I run more than one instance of the Database Migration Wizard?
No, to avoid duplicated events the database migration process will NOT allow more than one instance of the migration utility to be run at any given time.
What's the difference between the Copy Configuration (Step 3 in CASetup) and the Database Migration Wizard? Is it necessary to run both of these utilities?
The ‘Copy Configuration’ option in CASetup will ONLY copy monitored objects, agent configurations, repository configuration, and audit event severity assignments. No events, searches, or alerts will be copied.
The ‘Database Migration Wizard’ will copy everything that the Copy Configuration does, as well as searches, alerts, and events. If you skip the “Copy Configuration” step during the installation, all the information will be copied anyway using the Database Migration wizard. How long will the configuration import take?
How long will the database migration take?
The length of time that the database migration (Database Migration wizard) is based on all of the following:
• the number and type of events that are in your 3.x database • the hardware that the SQL Server is running
• the number of other SQL connections that are using that same machine. For example:
Customer A, has 7.8 Million events in a ChangeAuditor 3.4 database. The database
is roughly 15GB in size.
Running the Database Migration wizard on the SQL server with the following hardware configuration will take about two days to complete the migration process:
• Dual AMD Opteron 248 – 2.21GHZ Processors • 15GB of RAM
• Single 80GB HD – Windows Server 2003 • 2 x 160GB HDs Striped – SQL MDF Files • 1 x 300GB HD – SQL LDF Files
Customer B, has 200K events in a ChangeAuditor 3.5 database. The database is
roughly 100MB in size.
Running the Database Migration Wizard on the SQL server with the following hardware configuration will take approximately five hours to complete the migration process:
• P4 3.0GHZ • 2GB of RAM
• Single 80 IDE HD - Windows Server 2003 \ SQL Server 2005 Can I schedule the Database Migration Wizard to run at certain times?
Yes, the Database Migration wizard can be run with the Windows Task Scheduler (or another third-party task scheduler), and be scheduled to run at any time. See Command
Line Options on page 24 for more information on using the /auto command line option for
scheduling purposes.
What if I need to stage my agent deployment over the course of several days or weeks? No problem, this is fully supported. You can maintain both the 3.x and 4.x repositories until all of your agents are fully deployed. After all of your agents are deployed, you can then remove the older repository and clients.
Can my 3.x agents send events to a 4.x repository?
No, 3.x agents can only communicate with a 3.x repository. Similarly, 4.x agents can only communicate with a 4.x repository.
4 ChangeAuditor
Important Notices and FAQs
Can I run two different versions of the client on the same machine?
No, the 4.x client install will upgrade any existing client that is already installed. Only the repository supports parallel installations.
Can I run two different versions of the agent on the same machine?
No, the Agent Deployment Wizard will upgrade the agents on the severs selected in the Agent Configuration screen. Only the repository supports parallel installations.
Can I run the migration utility multiple times to capture the latest data from my 3.x database?
Yes, the Database Migration wizard can be stopped and started at any time. It can be run as many times as needed. When the utility is restarted, it will continue to migrate only the events that are left, and start where it last left off. It will copy the newest events first, from the 3.x database to the 4.x database.
For example:
Customer A has 12 months of data in his 3.x database (January 2006 through
December 2006). The Database Migration wizard will begin copying with December, then November, then October, etc.
If you have new events that get forwarded into the 3.x database by the 3.x agents, while the migration utility is running, those events will be copied the next time the database migration utility is run again.
Make sure to run the Database Migration wizard one final time after all of your agents are upgraded and now using the 4.x repository.
NOTE: Importing your configuration, whether it is done with the Copy Configuration step or the Database Migration wizard will only be done ONCE. Running the Copy
Configuration step subsequent times will NOT import any new configuration data.
Can I migrate my 2.x database?
Yes, see the migration steps described later in this document.
Can I migrate a SQL Server Integration Services (SSIS) consolidated database?
No, this is not supported. Consolidated databases will need to be rebuilt after the individual repository databases are migrated to 4.x. Please contact NetPro Technical Support for more details.
NOTE: A consolidated database refers to the database that is created when you
installed the separate SSIS package to copy data from multiple repositories into a single database.
If errors are encountered, does the migration utility stop or continue?
I received ‘warnings’ about some events, what happened?
In most cases this is not a problem. The database migration utility will attempt to resolve some event data in Active Directory so that additional parameters can be recorded. For example, for some objects, the utility will try to resolve a Distinguished Name into a GUID, using the Active Directory Global Catalog. If the object is deleted, the migration utility will log a warning and move on to the next event. In most cases this is harmless and can be ignored.
Does the database migration utility have any logs in case any errors are encountered? Yes, logs will be generated by both the Copy Configuration (Step 3 of CASetup) as well as the Database Migration wizard.
The Copy Configuration log is placed in the Temp folder in the Windows system root folder.
For example:
C:\Windows\Temp\CADatabaseImport.dll.log OR
C:\WINNT\Temp\CADatabaseImport.dll.log
There are two (2) separate logs that are generated for the Database Migration wizard: • CADatabaseImport.exe.nptlog
• CADatabaseImportUI.exe.nptlog
The Database Migration Wizard logs are placed in the Client installation folder. For example: C:\Program Files\Netpro\Compliance\Client\ChangeAuditor\CADatabaseImport.exe.nptlog C:\Program Files\Netpro\Compliance\Client\ChangeAuditor\CADatabaseImportUI.exe.nptlog OR C:\Program Files\Netpro\ChangeAuditor\Client\CADatabaseImport.exe.nptlog C:\Program Files\Netpro\ChangeAuditor\Client\CADatabaseImportUI.exe.nptlog
Is there any "clean-up" required after I migrate? • Remove the 3.x or 2.x repositories and clients • Detach and archive or delete the old 3.x database How does this affect SecurityManager?
Chapter 2: Migrating a ChangeAuditor 3.x
Database
This chapter discusses the steps required to migrate a 3.x database to the new 4.x database, which is required if you want to view/retrieve your existing events, searches, and alerts from the ChangeAuditor 4.x Client. For a detailed description of the Database Migration wizard, please refer to Chapter 4: Database Migration Wizard on page 21. For detailed instructions on installing/upgrading the different ChangeAuditor components, please refer to the
ChangeAuditor Installation Guide.
ChangeAuditor 3.x Database in Single Repository Environment
To migrate a 3.x database in a single repository environment:
1. Launch CASetup.exe.
2. Select Step 2: Repository Installation to install the new 4.x repository.
NOTE: This can be on the same machine as the existing 3.x repository or a different
8 ChangeAuditor
Migrating a ChangeAuditor 3.x Database
3. Once the new 4.x repository is installed and running, run Step 3: Copy Configuration from ChangeAuditor 3.x.
This step copies the monitoring points, agent configurations, repository configuration and audit event severity assignments from the 3.x database into the 4.x database. Performing this step at this point of the migration ensures that when new agents are deployed, their agent configuration assignments will be retained from the 3.x database. When you select this option, the ChangeAuditor 3.x Configuration Import dialog will be displayed prompting you to enter the SQL server instance and credentials for the source (3.x) database.
4. Back on the ChangeAuditor Installation Options screen, run Step 4: Client and Deployment Wizard Installation to install the 4.x client, Agent Deployment wizard and Database Migration wizard.
NOTE: If you install the new 4.x client on the same machine, it will upgrade the old 3.x
client, and you will no longer have client access to your 3.x data unless you install a new 3.x client on another machine.
5. (Optional) From the Start menu, run the Database Migration wizard (Start | Programs | NetPro | ChangeAuditor | Database Migration Wizard) to migrate your 3.x events, searches and alerts to the new 4.x database.
10 ChangeAuditor
Migrating a ChangeAuditor 3.x Database
If you need to stop the migration process for any reason, select the Abort button. This will stop the migration process, which can then be started again at a later time by launching the Database Migration wizard. When the migration utility is restarted, it will continue to migrate the events where it last left off (newest to oldest).
Please refer to Chapter 4: Database Migration Wizard on page 21 for a detailed description of this wizard.
7. From the Start Menu, launch the NetPro Compliance Agent Deployment wizard (Start | Programs | NetPro | ChangeAuditor | Agent Deployment Wizard) to upgrade your agents to 4.x.
NOTE: This can take several days or weeks in some environments. During the agent
deployment process, 3.x agents will continue to send events to the 3.x repository; and 4.x agents will only send events to the new 4.x repository.
8. Run the Database Migration wizard (Start | Programs | NetPro | ChangeAuditor | Database Migration Wizard) one last time to migrate the remaining 3.x events to the 4.x database.
9. Once all of your agents are upgraded to 4.x, uninstall the 3.x repository and 3.x client.
ChangeAuditor 3.x Database in Multiple Repository Environment
The migration process for a multi-repository environment, is basically the same as that for a single repository environment. However, you want to make sure to leave at least one of your 3.x repositories and clients running until after you have completed the 4.x agent deployment.
To migrate a 3.x database in a multiple repository environment:
1. Launch CASetup.exe.
2. Select Step 2: Repository Installation to install the new 4.x repository on one of your existing repository machines.
NOTE: This can be on the same machine as an existing 3.x repository or a different
3. Once the new 4.x repository is installed and running, run Step 3: Copy Configuration from ChangeAuditor 3.x.
12 ChangeAuditor
Migrating a ChangeAuditor 3.x Database
Once you have entered the requested information, select the Import button to start copying the 3.x configuration into the new 4.x database.
4. Back on the ChangeAuditor Installation Options screen, run Step 4: Client and Deployment Wizard Installation to install the 4.x client, Agent Deployment wizard and Database Migration wizard.
NOTE: If you install the new 4.x client on the same machine, it will upgrade the old 3.x
client, and you will no longer have client access to your 3.x data, unless you install a new 3.x client on another machine.
6. On the Database Migration wizard screen, enter the 3.x database information in the left-hand pane and the 4.x database information in the right-left-hand pane. After entering the requested information, select the Import button to start migrating data.
If you need to stop the migration process for any reason, select the Abort button. This will stop the migration process, which can then be started again at a later time by launching the Database Migration wizard. When the migration utility is restarted, it will continue to migrate the events where it last left off (newest to oldest).
Please refer to Chapter 4: Database Migration Wizard on page 21 for a detailed description of this wizard.
7. From the Start Menu, launch the NetPro Compliance Agent Deployment wizard (Start | Programs | NetPro | ChangeAuditor | Agent Deployment Wizard) to upgrade your agents to 4.x.
NOTE: This can take several days or weeks in some environments. During the agent
deployment process, 3.x agents will continue to send events to the 3.x repository; and 4.x agents will only send events to the new 4.x repository.
8. Run the Database Migration wizard (Start | Programs | NetPro | ChangeAuditor | Database Migration Wizard) one last time to migrate the remaining 3.x events to the 4.x database.
Chapter 3: Migrating a ChangeAuditor 2.x
Database
NOTE: Please contact NetPro Technical Support for assistance during a ChangeAuditor 2.x database migration.
A ChangeAuditor 2.x database schema must first be upgraded to the 3.5 database schema before the 4.x data migration process can occur.
NOTE: Backup your ChangeAuditor 2.x database BEFORE you attempt to migrate this database.
This chapter discusses the steps required to migrate a 2.x database to the new 4.x database. For a detailed description of the Database Migration wizard, please refer to Chapter 4:
Database Migration Wizard on page 21. For detailed instructions on installing the different
ChangeAuditor components, please refer to the ChangeAuditor Installation Guide. Warning
16 ChangeAuditor
Migrating a ChangeAuditor 2.x Database
ChangeAuditor 2.x in a Single Repository Environment
To migrate a 2.x database in a single repository environment:
1. Launch CASetup.exe.
2. Select Step 2: Repository Installation to install the new 4.x repository.
NOTE: This can be on the same machine as the existing 2.x repository or a different
machine.
NOTE: SKIP Step 3: Copy Configuration from ChangeAuditor 3.x. This is not supported
in the 2.x database.
3. Run Step 4: Client and Deployment Wizard Installation to install the 4.x client, Agent Deployment Wizard and Database Migration wizard.
NOTE: If you install the new 4.x client on the same machine, it will upgrade the old 2.x
4. From the Start Menu, launch the NetPro Compliance Agent Deployment wizard (Start | Programs | NetPro | ChangeAuditor | Compliance Agent Deployment Wizard) to upgrade your agents to 4.x.
NOTE: This can take several days or weeks in some environments. During the agent
deployment process, 2.x agents will continue to send events to the 2.x repository; and 4.x agents will only send events to the new 4.x repository.
5. After ALL of the agents are upgraded to 4.x, uninstall the 2.x repository and client. 6. Now you are ready to upgrade the 2.x database schema to the 3.5 schema.
NOTE: Backup your ChangeAuditor 2.x database BEFORE you attempt to migrate this
database.
Use the ‘CADatabaseImportUI.exe /UPGRADE’ command line to enable the schema
upgrade option in the Database Migration wizard.
7. Once you have added the /UPGRADE option to the migration utility executable, run the Database Migration wizard (Start | Programs | NetPro | ChangeAuditor | Database Migration Wizard) to migrate all your events from 3.x to 4.x.
8. On the Database Migration wizard screen, enter the 3.x database information in the left-hand pane and the 4.x database information in the right-left-hand pane.
Select (check) the Upgrade source database to 3.5 schema check box (which was added to this dialog when you launched the executable with the /UPGRADE option.) After entering the requested information, select the Import button to start migrating data.
Warning
18 ChangeAuditor
Migrating a ChangeAuditor 2.x Database
If you need to stop the migration process for any reason, select the Abort button. This will stop the migration process, which can then be started again at a later time by launching the Database Migration wizard. When the migration utility is restarted, it will continue to migrate the events where it last left off (newest to oldest).
Please refer to Chapter 4: Database Migration Wizard on page 21 for a detailed description of this wizard.
ChangeAuditor 2.x Database in Multiple Repository Environment
The migration process for a multi-repository environment, is basically the same as that for a single repository environment. However, you want to make sure to leave at least one of your 2.x repositories and clients running until after you have completed the 4.x agent deployment.
To migrate a 2.x database in a multiple repository environment:
1. Launch CASetup.exe.
2. Select Step 2: Repository Installation to install the new 4.x repository.
NOTE: This can be on the same machine as the existing 2.x repository or a different
machine.
NOTE: SKIP Step 3: Copy Configuration from ChangeAuditor 3.x. This is not supported
in the 2.x database.
3. Run Step 4: Client and Deployment Wizard Installation to install the 4.x client, Agent Deployment Wizard and Database Migration wizard.
NOTE: If you install the new 4.x client on the same machine, it will upgrade the old 2.x
4. From the Start Menu, launch the NetPro Compliance Agent Deployment wizard (Start | Programs | NetPro | ChangeAuditor | Agent Deployment Wizard) to upgrade your agents to 4.x.
NOTE: This can take several days or weeks in some environments. During the agent
deployment process, 2.x agents will continue to send events to the 2.x repository; and 4.x agents will only send events to the new 4.x repository.
5. After ALL of the agents are upgraded to 4.x, uninstall the 2.x repository and client. 6. Now you are ready to upgrade the 2.x database schema to the 3.5 schema.
NOTE: Backup your ChangeAuditor 2.x database BEFORE you attempt to migrate this
database.
Use the ‘CADatabaseImportUI.exe /UPGRADE’ command line to enable the schema
upgrade option in the Database Migration wizard.
***Warning, your 2.x repository will not be able to connect to this database after the
schema has been upgraded. ONLY do this step when ALL of your agents are upgraded to 4.x.
20 ChangeAuditor
Migrating a ChangeAuditor 2.x Database
8. On the Database Migration wizard screen, enter the 3.x database information in the left-hand pane and the 4.x database information in the right-left-hand pane.
Select (check) the Upgrade source database to 3.5 schema check box (which was added to this dialog when you launched the executable with the /UPGRADE option.) After entering the requested information, select the Import button to start migrating data.
If you need to stop the migration process for any reason, select the Abort button. This will stop the migration process, which can then be started again at a later time by launching the Database Migration wizard. When the migration utility is restarted, it will continue to migrate the events where it last left off (newest to oldest).
Chapter 4: Database Migration Wizard
The Database Migration wizard is automatically installed with the ChangeAuditor Client and can be launched from the Start Menu: Start | Programs | NetPro | ChangeAuditor | Database Migration Wizard. This database migration utility automates the process of moving events, searches, and alerts, from your existing database to your new 4.x database.
This chapter provides a detailed description of the Database Migration wizard and the command line options that can be used to upgrade the database source to 3.5 schema (for 2.x migrations) or automatically import the data (for scheduling purposes).
Database Migration Wizard
22 ChangeAuditor
Database Migration Wizard
Enter the requested information as described below: Source (CA 3.x) Database
In the left-hand pane, enter the requested information for the 3.x database to be migrated. Server/Instance
Enter the server name (member server running the SQL instance) and the SQL instance name of the 3.x database (i.e., <FQDN of SQL Server>\<instance name>. Database
Enter the name assigned to your 3.x ChangeAuditor database.
NOTE: If you do not know the name of your 3.x ChangeAuditor database, you can either
call NetPro Technical Support for assistance or you can use the Repository Database Configuration utility on your 3.x repository machine. That is, right-click the Repository SysTray icon and select the Repository Database
Configurator menu command to open the Database Properties dialog. The
Database Catalog field, near the bottom on this dialog will contain the name of your database.
Use Windows Authentication
This option is selected by default and will use Windows Authentication to access the 3.x repository database.
Use SQL Authentication
Select this option to use SQL authentication to access the 3.x repository database. Username
Enter the user name for the account to be used to access the designated SQL server instance.
Password
Enter the password associated with the user account entered above. Domain
Enter the domain for the Windows account to be used to access the designated SQL server instance. (Only valid for Windows Authentication.)
Destination (CA 4.0) Database
In the right-hand pane, enter the requested information for the new 4.x database: Server/Instance
Enter the server name (member server running the SQL instance) and the SQL instance name of the 4.x database (i.e., <FQDN of SQL Server>\<instance name>. Database
Enter the name to be assigned to the ChangeAuditor 4.0 database.
NOTE: This has to be a different name than the one used for the 3.x database.
Use Windows Authentication
Use SQL Authentication
Select this option to use SQL authentication to access the 4.x repository database. Username
Enter the user name for the account to be used to access the designated SQL server instance.
Password
Enter the password associated with the user account entered above. Domain
Enter the domain for the Windows account to be used to access the designated SQL server instance. (Only valid for Windows Authentication.)
Global Catalog
Enter the Global Catalog (GC) server to be used to retrieve Active Directory information. Use an FQDN (e.g., WinDC1.home.netpro.com) or an IP address.
Upgrade source database to 3.5 schema
Select (check) this check box to upgrade your 2.x schema to the 3.5 schema before starting the migration process.
NOTE: Backup your 2.x database BEFORE using this option to upgrade your 2.x
database schema.
NOTE: This check box is only displayed when the /upgrade command line option is
added to the migration utility executable.
Purge events as they’re getting imported
Select (check) this check box to remove the events from the 3.x database after they have been moved to the 4.x database.
NOTE: We do not recommend checking this check box, unless you have available disk
space issues.
View Log File
Select the View Log File link to review the logs and/or errors generated during the migration process. Selecting this link will launch the Log Viewer to display the contents of the CADatabaseImport.dll.nptlog.
Import
After entering the requested information, select the Import button to start migrating the data to the 4.x database.
Warning
24 ChangeAuditor
Database Migration Wizard
Abort
Once the importing starts, the Import button will change to an Abort button, which can be used to stop the migration process. The migration process can then be started again at a later time by launching the Database Migration wizard. When the migration utility is restarted, it will continue to migrate the events where it last left off (newest to oldest). Save Settings
Use the Save Settings button to save the settings entered for use in subsequent
migrations. That is, when you have selected this button before closing the dialog, the next time you launch the Database Migration wizard, all of the fields will be popluated with the settings you previously saved.
Close
Use the Close button to close the Database Migration wizard.
Command Line Options
The Database Migration wizard, CADatabaseImportUI.exe, can be launched using one of the following command line options:
/upgrade
Use the /upgrade option to enable the Upgrade source database to 3.5 schema check box on the Database Migration wizard screen. Use this option when you are migrating data from a 2.x database.
/auto
Use the /auto option to automatically start the import process without user intervention when the requested information on the Database Migration wizard is filled out. Use this option, when you are planning to use Windows Task Scheduler or another third-party task scheduler to schedule the database migration.
NOTE: To save the connection information, you must run the Database Migration
