IBM Security SiteProtector System Migration Utility Guide

Transcription

1 IBM Security IBM Security SiteProtector System Migration Utility Guide Version 3.0

2 Note Before using this information and the product it supports, read the information in Notices on page 5. This edition applies to Version 3.0 of the IBM Security SiteProtector System and to all subsequent releases and modifications until otherwise indicated in new editions. Copyright IBM Corporation 1994, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

3 Contents IBM Security SiteProtector System Migration utility Supported and unsupported options Migration tips Running the migration utility Notices Trademarks Privacy policy considerations Statement of good security practices Copyright IBM Corp. 1994, 2013 iii

4 iv SiteProtector System: Migration Utility Guide

5 IBM Security SiteProtector System Migration utility The SiteProtector System Migration utility migrates an established SiteProtector site to a new hardware configuration. You typically migrate an established site when it grows beyond the capacity of its original configuration. You must complete a few manual tasks before and after you run the utility. Migration utility process The Migration Utility performs the following steps: v Detaches the database from the source site and from the destination site. v Backs up the destination site database. v Copies the source site database to the destination site. v Attaches the destination site database to the destination site SQL instance. v Copies schema files from the source site to the destination site. v Distributes the authentication keys from the destination site to all agents from the source site. Restoring the source site If you run the utility but do not complete the final migration steps, you can restore the source site. Not completing the final steps enables you to use the utility in a test environment where you might not want to perform the entire migration. Or, if an unanticipated problem prevents you from completing the migration process, you can restore the source site. To restore the source site, you must manually reattach the source database to the source site. For more information, see the Attach a Database article at ms aspx or contact IBM Support. Important: Even though you can restore the source site, you cannot use the Migration Utility to create a failover system. Event data Your agents continue to send event data to the Event Collector during the migration process, even while the Migration Utility detaches your source site database and copies it to the destination site. The events that are collected during the migration remain in event queues until you finish the migration steps. The System can lose event data if the database remains detached for an extended time period. An agent can potentially accumulate many events, surpassing the agent's storage capacity. Length of time to migrate a site In most circumstances, migrating the database is the most time consuming part of the migration process. For example, it takes approximately two hours to migrate a 50 GB database on a 100-megabit network. The total migration time also depends on how quickly you complete the final configuration tasks, which include reconfiguring each Event Collector computer to use the destination site database. Supported and unsupported options The Migration Utility supports specific platforms and configuration options. Copyright IBM Corp. 1994,

6 Supported platforms and options You can use the Migration Utility with source and destination sites that run supported versions of the operating system. You can also migrate to SQL Server sites that run on either the same or a later version of SQL Server than the source site. For information about supported versions, see the Hardware and software requirements topics under the Planning heading of the SiteProtector System online Help. Database clustering not supported The Migration Utility does not support configurations where either the source or the destination site databases use SQL Server clustering. Cross Domain migration not supported The Migration Utility does not support Cross Domain migration, so you cannot use the utility to migrate a source site in one domain to a destination site in another domain. Cross Domain migration does not apply to agents. Agents might be in different domains. Migration tips To improve the efficiency of your migration, consider the following tips. Scheduling the migration Consider the following when you choose a time to migrate your site: v Migrate your site when you can complete the final migration tasks immediately after you run the Migration Utility. v Migrate your site when network traffic is minimal to avoid losing events. Database maintenance Perform the database maintenance functions in SiteProtector that are designed to reduce the size of the database and optimize its performance. Note: See the IBM Security SiteProtector System Configuration Guide for detailed instructions about performing database maintenance. User permissions All default SiteProtector permissions should migrate from the source site to the destination site cleanly. If the users you have configured are on the same domain as both the source and the destination sites, then the permissions should function properly after the migration. If you have set up permissions using user accounts, however, they may not function properly after the migration. You must create new versions after the migration because the permissions will not function properly in the following situations: v The users on both the source and destination sites are local users. v The users on both the source and destination sites are domain users and belong to different domains. Running the migration utility Complete the steps to successfully run the migration utility. 2 SiteProtector System: Migration Utility Guide

7 Before you begin 1. Install SiteProtector and all its components on the destination site. Important: The software versions of each component must be the same on both sites. 2. Shut down all SiteProtector services on the destination site: v issdaemon v SiteProtector Application Server Service on the SP Core (Application Server) computer v SiteProtector Event Archiver Service v SiteProtector Event Viewer Service v SiteProtector Sensor Controller Service on the SP Core (Application Server) computer v SiteProtector Web Server Service v SQL Server Agent (MSSQLSERVER) service on the destination database server 3. You must stop the SQL Server Agent (MSSQLSERVER) service on the source database server. 4. If it is a SiteProtector appliance, you must also shut down the SiteProtector Master Service. About this task After you reviewed the migration tips and performed the prerequisites, you are ready to run the Migration Utility. Procedure 1. On the Application Server computer of the source site, locate the path of the Migration Utility. For example, your_drive:\program Files\ISS\SiteProtector\Application Server\bin Note: If you migrated from an earlier version of SiteProtector on your source site, the path might be: your_drive:\program Files\ISS\RealSecure SiteProtector\Application Server\bin 2. Double-click Migration.exe. This launches the Migration wizard. 3. Follow the Migration wizard steps to completion. When the Migration wizard completes, it indicates that the automated portion is complete and that some final manual steps are necessary for completion. These additional steps are covered in the "What to do next" section. What to do next You must configure the Data Source Name (DSN) that each Event Collector computer uses to communicate with the destination site database. Important: If you use more than one Event Collector, then you must update the DSN on each Event Collector computer. To modify a DSN for the secondary site database: 1. On the Event Collector computer, run one of the following programs from the Start menu search or run dialog: v For 32-bit systems, run %systemroot%\system32\odbcad32.exe v For 64-bit systems, run %systemroot%\syswow64\odbcad32.exe 2. In the ODBC Data Source Administrator window, select the System DSN tab. 3. Select RSNTEventCollector, and then click Configure. 4. Type the server name of the destination site Database in the Server box, and then click Next. 5. Select With SQL Server authentication using a login ID and password entered by the user. 6. Select Connect to SQL Server to obtain default settings for the additional configuration options, and then type the user name and password that you use for the Event Collector computers. Migration utility 3

8 7. Click Next. 8. In the ODBC Microsoft SQL Server Setup window, click Test Data Source. If the connection is configured properly, the following message displays: "TEST COMPLETED SUCCESSFULLY!" 9. Click OK. Note: If your user accounts did not transfer automatically from the source site, you must set up the permissions with user accounts on the destination site. 4 SiteProtector System: Migration Utility Guide

9 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing IBM Corporation North Castle Drive Armonk, NY U.S.A. For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to: Intellectual Property Licensing Legal and Intellectual Property Law IBM Japan Ltd , Nihonbashi-Hakozakicho, Chuo-ku Tokyo , Japan The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Copyright IBM Corp. 1994,

10 Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact: IBM Corporation Project Management C55A/74KB 6303 Barfield Rd., Atlanta, GA U.S.A Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee. The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us. All statements regarding IBM's future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only. Trademarks IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at Copyright and trademark information at Copyright and trademark information at legal/copytrade.shtml. Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. UNIX is a registered trademark of The Open Group in the United States and other countries. Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both. Privacy policy considerations IBM Software products, including software as a service solutions, ( Software Offerings ) may use cookies or other technologies to collect product usage information, to help improve the end user experience, to tailor interactions with the end user or for other purposes. In many cases no personally identifiable information is collected by the Software Offerings. Some of our Software Offerings can help enable you to collect personally identifiable information. If this Software Offering uses cookies to collect personally identifiable information, specific information about this offering s use of cookies is set forth below. This Software Offering does not use cookies or other technologies to collect personally identifiable information. If the configurations deployed for this Software Offering provide you as customer the ability to collect personally identifiable information from end users via cookies and other technologies, you should seek your own legal advice about any laws applicable to such data collection, including any requirements for notice and consent. For more information about the use of various technologies, including cookies, for these purposes, See IBM s Privacy Policy at and IBM s Online Privacy Statement at 6 SiteProtector System: Migration Utility Guide

11 sections entitled Cookies, Web Beacons and Other Technologies and Software Products and Software-as-a Service. Statement of good security practices IT system security involves protecting systems and information through prevention, detection, and response to improper access from within and outside your enterprise. Improper access can result in information being altered, destroyed, misappropriated or misused or can result in damage to or misuse of your systems, including for use in attacks on others. No IT system or product should be considered completely secure and no single product, service or security measure can be completely effective in preventing improper use or access. IBM systems, products and services are designed to be part of a comprehensive security approach, which will necessarily involve additional operational procedures, and may require other systems, products or services to be most effective. IBM DOES NOT WARRANT THAT ANY SYSTEMS, PRODUCTS OR SERVICES ARE IMMUNE FROM, OR WILL MAKE YOUR ENTERPRISE IMMUNE FROM, THE MALICIOUS OR ILLEGAL CONDUCT OF ANY PARTY. Notices 7

12 8 SiteProtector System: Migration Utility Guide

13

14 Printed in USA