Академический Документы
Профессиональный Документы
Культура Документы
Overview
Introduction The SiteProtector Migration Utility migrates an established SiteProtector Site to a new hardware configuration. You typically migrate an established Site when it has grown beyond the capacity of its original configuration.
Important: You must perform a few manual tasks before and after you run the utility. Read this entire document before you start so that you understand the process.
Terminology
In this document
Utility to create a failover system. Event data Your agents continue to send event data to the Event Collector during the migration processeven while the Migration Utility detaches your source Site database and copies it to the destination Site. The events collected during the migration remain in event queues until you finish the migration steps.
Caution: The System can lose event data if the database remains detached for an extended
time period. An agent could potentially accumulate a large number of events, surpassing the agents storage capacity.
Recommendations
Introduction Timing Considerations To improve the efficiency of your migration, perform the tasks described below. Consider the following when you chose a time to migrate your Site:
Migrate your Site when you can complete the final migration tasks immediately after you run the Migration Utility. 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 SiteProtector 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. The permissions will not function properly in the following situations, and you must create new versions after the migration:
The users on both the source and destination Sites are local users. The users on both the source and destination Sites are domain users and belong to different domains.
Prerequisites
Prerequisites
Introduction Prerequisites You must perform the tasks listed in the table below before you run the Migration Utility. The following table describes the prerequisites for running the Migration Utility:
Prerequisites Install SiteProtector and all its components on the destination Site. Important: The software versions of each component must be the same on both Sites. Shut down the following services on the destination Site: SiteProtector Sensor Controller Service on the SP Core (Application Server) computer SiteProtector Application Server Service on the SP Core (Application Server) computer SQL Server Agent (MSSQLSERVER) service on the database server
If the source Site is a Recommended installation, you must stop the SQL Server Agent (MSSQLSERVER) service on the source database server.
Procedure
2. Double-click Migration.exe.
To modify a DSN for the secondary Site Database: 1. On the Event Collector computer, click Start on the task bar, and then select Control Panel Administrative Tools Data Sources (ODBC). 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. 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 appears: TEST COMPLETED SUCCESSFULLY! 9. Click OK. Task 2: Set up permissions 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. See User permissions on page 4.
Troubleshooting
Deployment Manager on source Site is stopped After you migrate a Site, the status of the Deployment Manager from the source Site may appear as Stopped. To change the status of the Deployment Manager: 1. Reboot the Deployment Manager computer, and then check the status of the Deployment Manager. 2. If rebooting does not change the status of the Deployment Manager, then uninstall, and reinstall, the Deployment Manager, and all updates
Copyright IBM Corporation 1994, 2007. All Rights Reserved. IBM and the IBM logo are trademarks or registered trademarks of International Business Machines Corporation in the United States, other countries, or both. ADDME, Ahead of the threat, BlackICE, Internet Scanner, Proventia, RealSecure, SecurePartner, SecurityFusion, SiteProtector, System Scanner, Virtual Patch, X-Force and X-Press Update are trademarks or registered trademarks of Internet Security Systems, Inc. in the United States, other countries, or both. Internet Security Systems, Inc. is a wholly-owned subsidiary of International Business Machines Corporation. Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product and service names may be trademarks or service marks of others. References in this publication to IBM products or services do not imply that IBM intends to make them available in all countries in which IBM operates.