HP StorageWorks HP PolyServe Migration Utility for SQL Server 4.
Legal and notice information © Copyright 2007, 2010 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Contents 1 Introduction ...................................................................... 4 Overview ........................................................................................................... How MxMigrate works .................................................................................. Migrated data .............................................................................................. Prerequisites ........................................................................
1 Introduction Overview The HP PolyServe Migration Utility for SQL Server (MxMigrate) is a wizard-based utility designed to move SQL Server databases into HP PolyServe Software for Microsoft SQL Server. At the end of the process, the migrated SQL databases will be highly available and manageable via HP PolyServe Software for Microsoft SQL Server. How MxMigrate works MxMigrate is a WinForm application built on .NET 3.5 and SQL Server Management Object (SMO). It consists of a single executable, MxMigrate.
Migrated data MxMigrate migrates the following: • User data • SQL logins • Linked/remote servers • SQL jobs • SSIS packages MxMigrate does not migrate or handle the following: • • • • • • • • • System databases (for example, master, msdb, tempdb) SSIS settings Replications Log shipping Database mirroring External dependencies Reporting Services Notification Services Service Broker MxMigrate does not handle auto-close or offline databases. The databases to be migrated must be online.
• Matrix Server must be installed and running on all nodes in the cluster. • HP PolyServe Software for Microsoft SQL Server must be installed on all cluster nodes that might host the SQL Server instance. • The Microsoft SQL Server instance must be installed as described in the HP PolyServe Software for Microsoft SQL Server Administration Guide.
2. Validate and connect to the source SQL Server instance (Source Login window.) 3. Validate and connect to the target (physical) SQL Server instance (Target Login window). 4. Select the databases to be migrated (Select Databases for Transfer window). 5. Specify the location for the backup files (Options window). 6. Validate your entries (Validation window). 7. Create any missing databases on the target server (Validation > New Database window). 8.
Migrate to a new matrix, using the same hostnames/IPs In this scenario, Matrix Server, HP PolyServe Software for Microsoft SQL Server, and the SQL Server instance are installed on the target node. The SQL Server instance has not yet been virtualized with HP PolyServe Software for Microsoft SQL Server. After the target SQL Server instance is virtualized during the procedure, the Virtual SQL Server will use the same host name and IP as the source SQL Server instance.
17. Restore the transaction logs to the target server (Backup and Restore Logs window). 18. Migrate SSIS/DTS packages to the target server. 19. Re-sync SQL securities and logins on the target server (Post-Switch Steps window) 20. Shut down the source server. 21. Virtualize the SQL Server instance on the target server. (Using HP PolyServe Software for Microsoft SQL Server, create a Virtual SQL Server with the same IP and hostname as that of the source server and add the SQL Server instance to it.) 22.
11. Apply any third-party applications, tools, and libraries to the target server so that it will match the configuration of the source server. 12. Test applications against the target server in stand-alone mode. 13. Back up the source databases (Backup and Restore Databases window) 14. Restore databases to the target server using NonRecovery (Backup and Restore Databases window). 15. Put the source database in ReadOnly mode.
2 Using MxMigrate Install MxMigrate MxMigrate should be installed on either a node in the Matrix Server cluster or another system that has network connectivity to both the source and target SQL Server instance. To install MxMigrate, complete these steps: 1. Locate the MxMigrate.msi file in the directory where you downloaded the product. 2. Double-click the MxMigrate.msi file and run the Installation Wizard. The installation creates an MxMigrate shortcut that can be used to run the utility.
Source Login window The Source Login window asks for the SQL login information needed to connect to the source SQL Server instance.
SQL Server Instance. Enter a valid SQL 2000, 2005, or 2008 instance such as MySQLSource or MySQLSource\Instance1. NOTE: If you are unsure of the instance name, click the (…) button to open the Select SQL Server Instance window, which lists the SQL Server instances available on the network. Highlight the desired instance and click Select to return to the main application. If you cannot find the correct instance, enter the instance name manually in the textbox field.
Then complete the Source Login window: Authentication Method. Select the desired authentication method to connect to the SQL Server instance. See SQL Server Books Online for additional details regarding Windows versus SQL authentication. User Name. Enter the appropriate user name. (This value is needed only if SQL Server Integrated Security is selected as the Authentication Method.) Password. Enter the user's password, and then re-enter it in the next field.
SQL Server Instance. Enter a valid SQL instance such as MySQLTarget or MySQLTarget\Instance1. This SQL Server instance must not be the same as the source SQL Server instance. If you are unsure of the instance name, click the (…) button to browse for a list of instances available on the network. Authentication Method. Select the desired authentication method to connect to the SQL Server instance. See SQL Server Books Online for additional details regarding Windows versus SQL authentication. User Name.
Select Databases for Transfer window Select the database(s) that you want to transfer to the target server. The window lists only user databases and “model” system databases. NOTE: It is best practice is to migrate the model database with the RECOVERY option before migrating the user databases. If this order is not followed, the restore of some user databases may fail. Click Select All to select all of the listed databases. Click Deselect All to deselect the databases.
NOTE: Migration of a model database is supported only from SQL Server 2005 to SQL Server 2005, provided that the Service Pack level on the source is equal to or lesser than Service Pack level on the target. Options window The Options window allows you to set options that affect how the database backup should be carried out. NOTE: The following requirements apply to both the source and target server: • Specify a UNC path for the backup and restore locations.
Number of Parallel backups. Enter the number of threads that the system should spawn to perform the backup in parallel. This option is useful when there is more than one database to be backed up. The default value is 1. Use file-based backup. This is the default method for backing up the database(s). Backup to. Enter the path to the directory where the source SQL Server instance will place the backup files. Use the (…) button to browse for a directory.
NOTE: The Validation step verifies only that the database exists; it does not check the status of the database. If the database is not online and accessible, the create/backup/restore operations will fail. Access check To check for access to the backup directory, MxMigrate executes the following from the source and target server: Exec master..xp_cmdshell N'dir This step requires that xp_cmdshell execution be allowed during the migration.
Click Save Info to save the results of the validation to a file. Click Start Validation to start the validation process. This process can be run as many times as desired.
If a database is missing on the target server, use the Create DB option to create the database shell on that server using the same database size and ANSI options as the source server. (No data is transferred.) Scroll down the validation report, select the missing database, and then click Create DB. You can specify the location for each of the database files on the New Database window. Name. The logical file name for the database. File Group. The file group to which the database file belongs. File Path.
Click Start Backup to start backing up the source SQL Server database to a shared folder. When the backup is complete, click Start Restore to begin restoring the database to the target server. Restore with RECOVERY on Target server. When this box is checked, the databases will be restored with the Recovery option on the target server. This option allows immediate access to the databases. The default is NonRecovery, or unchecked.
Pre-Switch Steps window The pre-switch steps include creating linked servers on the target server, transferring SQL logins and SQL jobs from the source server to the target server, and setting the source database to read-only. Check the steps that you want to perform and then click Start to begin the operation. Create remote/linked server on Target server. This box is checked by default. Create SQL logins/securities on Target server.
Create SQL jobs on Target server. This option transfers SQL jobs from the source server to the target server. This box is checked by default. Set Source DBs to read_only mode and terminate all user connections.This option sets the source database to read-only. Use this option only if you no longer want users to write to the source database. This option is valid for production migration. This box is unchecked by default.
SSIS (SQL2005/2008 only) window This window can be used to transfer SSIS packages. Check the individual packages that you want to transfer, or click Select All to select all packages. Then click Start to begin the operation. NOTE: The SSIS package transfer operation does not validate or transfer any external objects used by the SSIS packages. You will need to transfer all external object dependencies manually.
Finished window This window appears when the migration is complete. It shows the migration status log, which you can save to a file for future reference. Click Save Info to save the status log.
The MxMigrate utility also maintains a debug log called MxMigrate.log that can be used for debugging purposes. The log is in the same directory as the MxMigrate.exe file. HP PolyServe Migration Utility for SQL Server 4.
