Quest ChangeAuditor 4.8

Transcription

1 Quest ChangeAuditor 4.8 Migration Guide

2 Copyright Quest Software, Inc All rights reserved. This guide contains proprietary information protected by copyright. The software described in this guide is furnished under a software license or nondisclosure agreement. This software may be used or copied only in accordance with the terms of the applicable agreement. No part of this guide may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying and recording for any purpose other than the purchaser's personal use without the written permission of Quest Software, Inc. If you have any questions regarding your potential use of this material, contact: Quest Software World Headquarters LEGAL Dept 5 Polaris Way Aliso Viejo, CA USA legal@quest.com Refer to our Web site for regional and international office information. TRADEMARKS Quest, Quest Software, the Quest Software logo, and ChangeAuditor are trademarks and registered trademarks of Quest Software, Inc in the United States of America and other countries. Other trademarks and registered trademarks used in this guide are property of their respective owners. Disclaimer The information in this document is provided in connection with Quest products. No license, express or implied, by estoppel or otherwise, to any intellectual property right is granted by this document or in connection with the sale of Quest products. EXCEPT AS SET FORTH IN QUEST'S TERMS AND CONDITIONS AS SPECIFIED IN THE LICENSE AGREEMENT FOR THIS PRODUCT, QUEST ASSUMES NO LIABILITY WHATSOEVER AND DISCLAIMS ANY EXPRESS, IMPLIED OR STATUTORY WARRANTY RELATING TO ITS PRODUCTS INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT. IN NO EVENT SHALL QUEST BE LIABLE FOR ANY DIRECT, INDIRECT, CONSEQUENTIAL, PUNITIVE, SPECIAL OR INCIDENTAL DAMAGES (INCLUDING, WITHOUT LIMITATION, DAMAGES FOR LOSS OF PROFITS, BUSINESS INTERRUPTION OR LOSS OF INFORMATION) ARISING OUT OF THE USE OR INABILITY TO USE THIS DOCUMENT, EVEN IF QUEST HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Quest makes no representations or warranties with respect to the accuracy or completeness of the contents of this document and reserves the right to make changes to specifications and product descriptions at any time without notice. Quest does not make any commitment to update the information contained in this document. ChangeAuditor Migration Guide Updated - February 2009 Software Version - 4.8

3 Table of Contents TABLE OF CONTENTS ABOUT THIS GUIDE OVERVIEW ABOUT QUEST SOFTWARE CHAPTER 1 IMPORTANT NOTICES AND FAQS CHAPTER 2 MIGRATING A CHANGEAUDITOR 3.X DATABASE INTRODUCTION CHANGEAUDITOR 3.X DATABASE IN SINGLE REPOSITORY ENVIRONMENT CHANGEAUDITOR 3.X DATABASE IN MULTIPLE REPOSITORY ENVIRONMENT CHAPTER 3 MIGRATING A CHANGEAUDITOR 2.X DATABASE INTRODUCTION CHANGEAUDITOR 2.X IN A SINGLE REPOSITORY ENVIRONMENT...29 CHANGEAUDITOR 2.X DATABASE IN MULTIPLE REPOSITORY ENVIRONMENT CHAPTER 4 DATABASE MIGRATION WIZARD INTRODUCTION DATABASE MIGRATION WIZARD

4

5 About This Guide Overview Conventions About Quest Software Contacting Quest Software Contacting Quest Support

6 Quest ChangeAuditor Overview This document has been prepared to assist you in using the Database Migration Wizard, a utility that is installed automatically with the ChangeAudior Client to automate the process of moving events, searches, alerts, etc. from an existing 3.x database. The Migration Guide contains the information required to use the Database Migration utility. It is intended for network administrators, consultants, analysts, and any other IT professionals wanting to move events, searches, alerts, etc. from an existing 3.x database to a new 4.x database. Conventions In order to help you get the most out of this guide, we have used specific formatting conventions. These conventions apply to procedures, icons, keystrokes and cross-references. ELEMENT Select Bolded text Italic text Bold Italic text CONVENTION This word refers to actions such as choosing or highlighting various interface elements, such as files and radio buttons. Interface elements that appear in Quest products, such as menus and commands. Used for comments. Used for emphasis. Blue text Indicates a cross-reference. When viewed in Adobe Reader, this format can be used as a hyperlink. Used to highlight additional information pertinent to the process being described. Used to provide Best Practice information. A best practice details the recommended course of action for the best result. Used to highlight processes that should be performed with care. Used to highlight a troubleshooting tip pertaining to the topic being described. 6

7 About This Guide ELEMENT CONVENTION Used to highlight permissions required to perform the action being described. + A plus sign between two keystrokes means that you must press them at the same time. A pipe sign between elements means that you must select the elements in that particular sequence. About Quest Software Quest Software, Inc. delivers innovative products that help organizations get more performance and productivity from their applications, databases, and Windows infrastructure. Through a deep expertise in IT operations and a continued focus on what works best, Quest helps more than 18,000 customers worldwide meet higher expectations for enterprise IT. Quest's Windows Management solutions simplify, automate, and secure Active Directory, Exchange and Windows, as well as integrate Unix and Linux into the managed environment. Quest Software can be found in offices around the globe and at Contacting Quest Software Phone Mail Web site (United States and Canada) info@quest.com Quest Software, Inc. World Headquarters 5 Polaris Way Aliso Viejo, CA USA Please refer to our Web site for regional and international office information. 7

8 Quest ChangeAuditor Contacting Quest Support Quest Support is available to customers who have a trial version of a Quest product or who have purchased a commercial version and have a valid maintenance contract. Quest Support provides around the clock coverage with SupportLink, our web self-service. Visit SupportLink at From SupportLink, you can do the following: Quickly find thousands of solutions (Knowledgebase articles/documents). Download patches and upgrades. Seek help from a Support engineer. Log and update your case, and check its status. View the Global Support Guide for a detailed explanation of support programs, online services, contact information, and policy and procedures. The guide is available at: Support Guide.pdf. 8

9 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. 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.

10 Quest ChangeAuditor 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. Please note, however, that you will not be able to view/retrieve your existing events in the 4.x database and you will also have to manually re-create any searches, alerts, agent configurations, and repository configurations in the new 4.x database if you elect not to run the database migration. 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 Quest 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. 10

11 Important Notices and FAQs 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? The configuration import (Step 3 in CASetup) in most environments will take only a few minutes. In environments that have a lot of servers joined to the Active Directory forest, the configuration import can take considerably longer. For example, an environment that has 30,000 servers (member servers or domain controllers) will take about 1.5 hours to complete. 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 GHZ Processors 15GB of RAM Single 80GB HD Windows Server x 160GB HDs Striped SQL MDF Files 1 x 300GB HD SQL LDF Files 11

12 Quest ChangeAuditor 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 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. Can I run two different versions (e.g, 3.x and 4.x) of the repository on the same machine? Yes, see the migration instructions described later in this document. 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. 12

13 Important Notices and FAQs 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. 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 Quest Support for more details. 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? The migration utility will continue if it encounters any warnings, and it will stop if there are any critical errors. 13

14 Quest ChangeAuditor 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\Quest Software\Compliance\Client\ ChangeAuditor\CADatabaseImport.exe.nptlog C:\Program Files\Quest Software\Compliance\Client\ ChangeAuditor\CADatabaseImportUI.exe.nptlog OR C:\Program Files\Quest Software\ChangeAuditor\Client\ CADatabaseImport.exe.nptlog C:\Program Files\Quest Software\ChangeAuditor\Client\ CADatabaseImportUI.exe.nptlog 14

15 Important Notices and FAQs 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? The 4.x Inspector does not communicate with 3.x agents, and the 4.x agents do not communicate with the 3.x Inspector. The SecurityManager Inspector should be upgraded when all of the agents have been upgraded to 4.x. However, in a long lasting, staged migration, the Inspector should be upgraded at a time such that maximum agent coverage is maintained. How do the changes made to Service Auditing in version 4.8 impact me? Beginning with ChangeAuditor version 4.8, Service Auditing is limited to services identified using Service Auditing templates instead of all services as it was in previous versions. Service Auditing is NOT migrated from your 3.x environment; therefore, you must create and apply a new Service Auditing template to enable Service Auditing. For more information on Service Auditing, please refer to the ChangeAuditor Administrator s Guide. 15

16

17 2 Migrating a ChangeAuditor 3.x Database Introduction ChangeAuditor 3.x Database in Single Repository Environment ChangeAuditor 3.x Database in Multiple Repository Environment

18 Quest ChangeAuditor Introduction 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 Database Migration Wizard. 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. This can be on the same machine as the existing 3.x repository or a different machine. 18

19 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. 19

20 Quest ChangeAuditor 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. 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 Quest Software ChangeAuditor Database Migration Wizard) to migrate your 3.x events, searches and alerts to the new 4.x database. 20

21 Migrating a ChangeAuditor 3.x Database 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-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 Database Migration Wizard for a detailed description of this wizard. 7. From the Start Menu, launch the Quest Compliance Agent Deployment wizard (Start Programs Quest Software ChangeAuditor Agent Deployment Wizard) to upgrade your agents to 4.x. 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 Quest Software 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. 21

22 Quest ChangeAuditor 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. This can be on the same machine as an existing 3.x repository or a different machine. 22

23 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. 23

24 Quest ChangeAuditor 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. 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 Quest Software ChangeAuditor Database Migration Wizard) to migrate your 3.x events, searches and alerts to the new 4.x database. 24

25 Migrating a ChangeAuditor 3.x Database 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-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 Database Migration Wizard for a detailed description of this wizard. 7. From the Start Menu, launch the Quest Compliance Agent Deployment wizard (Start Programs Quest Software ChangeAuditor Agent Deployment Wizard) to upgrade your agents to 4.x. 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 Quest Software 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 all of the 3.x repositories and 3.x clients. 25

26

27 3 Migrating a ChangeAuditor 2.x Database Introduction ChangeAuditor 2.x in a Single Repository Environment ChangeAuditor 2.x Database in Multiple Repository Environment

28 Quest ChangeAuditor Introduction Please contact Quest 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. Backup your ChangeAuditor 2.x database BEFORE you attempt to migrate this database. Your 2.x repository will NOT be able to connect to this database once the schema has been upgraded. ONLY use the Database Migration wizard AFTER ALL of your agents have been upgraded to 4.x. 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 Database Migration Wizard. For detailed instructions on installing the different ChangeAuditor components, please refer to the ChangeAuditor Installation Guide. 28

29 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. This can be on the same machine as the existing 2.x repository or a different machine. 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. If you install the new 4.x client on the same machine, it will upgrade the old 2.x client, and you will no longer have client access to your 2.x data, unless you install a 2.x client on another machine. 29

30 Quest ChangeAuditor 4. From the Start Menu, launch the Quest Compliance Agent Deployment wizard (Start Programs Quest Software ChangeAuditor Compliance Agent Deployment Wizard) to upgrade your agents to 4.x. 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. 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. 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. 30

31 Migrating a ChangeAuditor 2.x Database 7. Once you have added the /UPGRADE option to the migration utility executable, run the Database Migration wizard (Start Programs Quest Software 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-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). Please refer to Database Migration Wizard for a detailed description of this wizard. 31

32 Quest ChangeAuditor 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. This can be on the same machine as the existing 2.x repository or a different machine. SKIP Step 3: Copy Configuration from ChangeAuditor 3.x. This is not supported in the 2.x database. 32

33 Migrating a ChangeAuditor 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. If you install the new 4.x client on the same machine, it will upgrade the old 2.x client, and you will no longer have client access to your 2.x data, unless you install a 2.x client on another machine. 4. From the Start Menu, launch the Quest Compliance Agent Deployment wizard (Start Programs Quest Software ChangeAuditor Agent Deployment Wizard) to upgrade your agents to 4.x. 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. Backup your ChangeAuditor 2.x database BEFORE you attempt to migrate this database. 33

34 Quest ChangeAuditor 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. 7. Once you have added the /UPGRADE option to the migration utility executable, run the Database Migration wizard (Start Programs Quest Software 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-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). Please refer to Database Migration Wizard for a detailed description of this wizard. 34

35 4 Database Migration Wizard Introduction Database Migration Wizard

36 Quest ChangeAuditor Introduction The Database Migration wizard is automatically installed with the ChangeAuditor Client and can be launched from the Start Menu: Start Programs Quest Software 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 The following screen is displayed when the Database Migration wizard option is selected from the Start menu. Enter the requested information as described below: 36 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>.

37 Database Migration Wizard Database Enter the name assigned to your 3.x ChangeAuditor database. If you do not know the name of your 3.x ChangeAuditor database, you can either call Quest 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. This has to be a different name than the one used for the 3.x database. 37

38 Quest ChangeAuditor Use Windows Authentication This option is selected by default and will use Windows Authentication to access the 4.x repository database. 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.quest.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. Backup your 2.x database BEFORE using this option to upgrade your 2.x database schema. Your 2.x repository will NOT be able to connect to this database once the schema has been upgraded. ONLY use the Database Migration wizard AFTER ALL of your agents have been upgraded to 4.x This check box is only displayed when the /upgrade command line option is added to the migration utility executable. 38

39 Database Migration Wizard 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. 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. 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. 39

40 Quest ChangeAuditor 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. To save the connection information, you must run the Database Migration wizard once manually before running it in no user intervention mode. That is, your connection information is saved when you (manually) select the Import button. 40