AutoStart v March-2014

AutoStart v5.4.2 27-March-2014

Publication Information 2014 Imagine Communications Corp. Proprietary and Confidential. Imagine Communications considers this document and its contents to be proprietary and confidential. Except for making a reasonable number of copies for your own internal use, you may not reproduce this publication, or any part thereof, in any form, by any method, for any purpose, or in any language other than English without the written consent of Imagine Communications. All others uses are illegal. This publication is designed to assist in the use of the product as it exists on the date of publication of this manual, and may not reflect the product at the current time or an unknown time in the future. This publication does not in any way warrant description accuracy or guarantee the use for the product to which it refers. Imagine Communications reserves the right, without notice to make such changes in equipment, design, specifications, components, or documentation as progress may warrant to improve the performance of the product. Trademarks Product names and other brands (such as ADC, D-Series, Nexio, Nexio Insight, Nexio Motion, PowerSmart, Versio ) are trademarks or trade names of Imagine Communications or its subsidiaries. Microsoft and Windows are registered trademarks of Microsoft Corporation. All other trademarks and trade names are the property of their respective companies. Contact Information Imagine Communications has office locations around the world. For domestic and international location and contact information see: http://www.imaginecommunications.com/contact-us/ Support Contact Information For domestic and international support contact information see: Support Contacts: http://www.imaginecommunications.com/services/technical-support/ ecustomer Portal: http://support.imaginecommunications.com 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 2 of 184

Contents Contents About this Document... 8 Summary... 8 Before You Start... 8 About SQL Server... 8 Node Cluster Support... 8 References... 9 Application Overview... 10 About AutoStart... 10 Features... 10 Required Hardware and Software... 10 Notification Agent Integration... 11 Summary... 11 Constraints... 11 Installation... 11 Known Issues... 12 64553: AC 4.19.17.0A generates an Access Violation during or after an AutoStart failover.... 12 72506: The Database window is unresponsive after an AutoStart failover with MC 4.19.26.0M.... 12 EMC does not currently support SQL Server 2012.... 12 File Server Preparations... 13 Preparing the File Servers... 13 AutoStart File Server Recommendations... 13 Configuring AutoStart Network Connections... 14 To Configure AutoStart Network Connections... 14 Configuring the Dedicated Link NIC... 15 To Configure the Dedicated Link NIC... 15 Prerequisites to using the DNS registration options... 19 Configuring AutoStart Host Tables... 20 To Configure AutoStart Host Tables... 20 Disabling Power Management on File Server NICs... 21 To Disable Power Management on File Server NICs... 21 Configuring File Server Passwords to Not Expire... 22 To Configure File Server Passwords to Not Expire... 22 Disabling Automatic Windows Updates... 23 To Disable Automatic Windows Updates... 23 Renaming FS-1, and SQL Server 2012 Installation... 24 Renaming the First File Server to ASSQL... 24 To Rename the First File Server to ASSQL... 24 Before installing SQL Server 2012... 25 Installing SQL Server 2012... 25 Install SQL Server 2012... 25 Enabling the Named Pipes Communications Protocol... 34 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 3 of 184

Contents To Enable the Named Pipes Communications Protocol... 35 Renaming the First File Server to AUTOSTART1... 36 To Rename the First File Server to AUTOSTART1... 36 Renaming FS-2, and SQL Server 2012 Installation... 37 Renaming the Second File Server to ASSQL... 37 To Rename the Second File Server to ASSQL... 37 Before installing SQL Server 2012 on the Second File Server... 38 Installing SQL Server 2012 on the Second File Server... 38 To Install SQL Server 2012 on the Second File Server... 38 Renaming the Second File Server to AUTOSTART2... 38 To Rename the Second File Server to AUTOSTART2... 38 Installing AutoStart on Node 1... 40 Installing AutoStart on Node 1... 40 To Install AutoStart on Node 1... 40 Establishing Node Trust... 46 To Establish Node Trust - Make Node 1 Trust Node 2... 46 Installing AutoStart on Node 2... 49 Installing AutoStart on Node 2 Part 1... 49 To Install AutoStart on Node 2 Part 1... 49 Confirming that Node 1 Trusts Node 2... 52 To Confirm that Node 1 Trusts Node 2... 52 Installing AutoStart on Node 2 Part 2... 52 To Install AutoStart on Node 2 Part 2... 52 Set User Mode to Advanced... 54 Confirming that Nodes 1 and 2 are both Primary Nodes, and Node Promotion... 55 To Confirm that Nodes 1 and 2 are both Primary Nodes... 55 To Promote a Secondary Node to a Primary Node... 56 Configuring the Domain for Point-to-point Communications and Managed IP Addresses... 57 Configuring Point-to-point Domain Communications... 57 To Configure Point-to-point Domain Communications... 57 Configuring the Domain for Managed IP addresses... 59 To Configure the Domain for Managed IP Addresses... 60 Configuring Domain Failure Detection Settings... 60 To Configure Domain Failure Detection Settings... 61 Configuring the Local Isolation Network... 61 To Configure the Local Isolation Network... 61 Configuring and Assigning Managed IP Addresses... 63 Configuring Managed AutoStart IP addresses... 63 To Configure a Managed Automation IP address... 63 Configuring a Managed House IP address... 64 To Configure a Managed House IP address... 64 Assigning Managed IP Addresses... 65 To Assign a Managed IP Address for Automation... 66 To Assign a Managed IP Address for House... 66 Configuring and Assigning Node Aliases... 67 Creating Node Aliases... 67 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 4 of 184

Contents To Create an ASSQL Node Alias... 67 To Create a HOUSEDB Node Alias... 68 Assigning Node Aliases... 69 To Assign the ASSQL Node Alias... 69 To Assign the House Node Alias... 70 Configuring Mirroring and Attaching the Mirror as a Data Source... 71 Configuring Source and Mirror Nodes... 71 To configure Mirroring for Windows Servers... 71 Configuring EMC Mirroring... 72 To Configure EMC Mirroring... 72 Attaching the Mirror as a Data Source... 73 To Attach the Mirror as a Data Source... 73 Configuring ADCDB Domain Settings... 75 Configuring ADCDB Domain Failure Detection Settings... 75 To Configure ADCDB Domain Failure Detection Settings... 75 Configuring Notification Utility Processes... 77 Configuring Startup and Shutdown Notification Utility Processes... 77 To Configure the Startup Notification Utility Processes... 77 To Configure the Shutdown Notification Utility Processes... 78 Configuring Startup and Shutdown Notification Scripts... 79 To Configure the Startup Notification Script on AutoStart1... 79 To Configure the Shutdown Notification Script on AutoStart1... 79 To Configure the Startup Notification Script on AutoStart2... 80 To Configure the Shutdown Notification Script on AutoStart2... 80 The SQL Server Module... 81 Enabling the SQL Server Module... 81 To Enable the SQL Server Module by entering a License Key... 81 Creating a New SQL Server Module Instance... 82 To Create a New SQL Server Module Instance on Node 1... 82 Creating the SQL Server Browser Service... 88 To Create the SQL Server Browser Service... 89 Completing the Resource Group... 90 Adding the SQL Server Browser Service to the Resource Group... 90 To Add the SQL Server 2012 Browser Service to the Resource Group... 90 Adding the HOUSE IP to the Resource Group... 91 To Add the HOUSE IP to the Resource Group... 91 Adding the HOUSEDB Node Alias to the Resource Group... 93 To Add the HOUSEDB Node Alias to the Resource Group... 93 Adding the Notification Utility Processes to the Resource Group... 94 To Add the Startup Notification Utility Process to the Resource Group... 94 To Add the Shutdown Notification Utility Process to the Resource Group... 95 Creating the ASDB Database and Configuring it for AutoStart... 97 Running the CreateDB_All_ADC_SQL_2012_V1_3.sql Script... 97 To Run the CreateDB_All_ADC_SQL_2012_V1_3.sql script:... 97 Creating the SQL Server 2012 Database Backup... 99 To Create the Database Backup... 100 Installing Notification Agent... 101 To Install Notification Agent on Node 1... 101 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 5 of 184

Contents To Install Notification Agent on Node 2... 102 Running the Create_Node2_WA_Login_SQL_2012_V1_3.sql script... 104 To Run the Create_Node2_WA_Login_SQL_2012_V1_3.sql script... 104 Running the CreatePermissions_NA_SQL_2012_V1_3.sql Script... 108 To Run the CreatePermissions_NA_SQL_2012_V1_3.sql Script... 108 Configuring the Notification Agent Process and Adding it to the Resource Group... 110 Configuring the Notification Agent Process... 110 To Configure the Notification Agent Process... 110 Adding the Notification Agent Process to the Resource Group... 113 To Add the Notification Agent Process to the Resource Group... 113 Logging Off, and back In to the AutoStart Computers... 115 To Log Off and back In to the AutoStart Computers... 115 Making ASDB a Selected AutoStart Database... 115 Stop all running SQL Server Services... 115 Detach the mirror from autostart2... 116 Bring the Resource Group Online... 117 To Make ASDB a Selected AutoStart Database... 118 Configuring ODBC Data Sources for Notification Agent... 119 To Configure the ODBC Data Source on Node 1... 119 To Configure the ODBC Data Source on Node 2... 123 ADC Automation Configurations... 125 Adjusting Client Net Bios Name Cache Timing... 125 To Adjust Client Net Bios Name Cache Timing... 125 Sharing Folders on the D: Drive; MIRROR... 126 To Share Folders on the D: Drive; MIRROR... 126 Creating Permissions for Shared Folders... 126 To Create Permissions for Shared Folders... 127 Mapping Network Drives... 128 To Map Network Drives... 128 Operational AutoStart Procedures... 130 Re-locating the AutoStart Resource Group... 130 To Re-locate the AutoStart Resource Group... 130 Changing AutoStart File Server Passwords... 131 To Change AutoStart File Server Passwords... 131 Backing up and Restoring AutoStart Database... 133 To Backup the AutoStart Database... 133 To Restore the AutoStart Database... 134 AutoStart Disaster Recovery and Repairs... 136 Gaining Access to the MIRROR Drives... 136 To Gain Access to the Data on the MIRROR Drives... 136 Rebuilding an AutoStart System... 140 To Rebuild the AutoStart System... 140 To configure Mirroring for Windows Servers... 143 To Configure EMC Mirroring... 144 To Attach the Mirror as a Data Source... 145 To Add the MIRROR to the Resource Group... 146 Bring the Resource Group Online... 148 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 6 of 184

Contents Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & Service Packs... 149 Installing EMC AutoStart Version 5.4.2 Hot Fixes and/or Cumulative Hot Fixes... 149 To Install EMC AutoStart Version 5.4.2 Hot fixes and/or Cumulative Hot Fixes... 149 Installing Windows Updates and/or Service Pack(s) on an Active AutoStart System... 150 To Install Windows Updates on an Active AutoStart System... 151 Installing Future SQL Server 2012 Service Packs... 152 To Install Future SQL Server 2012 Service Packs... 152 Backup and Restoration of an SQL Server ASDB Database... 156 Creating an SQL Server 2005 Express Database Backup... 156 To Create an SQL Server 2005 Express Database Backup file... 156 Creating an SQL Server 2008 ASDB Database Backup... 160 To Create an SQL Server 2008 ASDB Database Backup file to a Configured Destination... 161 To Create an SQL Server 2008 ASDB Database Backup file to the Default Destination... 164 Restoring an SQL Server Database Backup into SQL Server 2012... 167 To Restore a Database Backup file into SQL Server 2012... 167 Upgrade Database Users and Permissions... 172 About Notification Agent... 173 Upgrade Notification Agent Database Permissions... 173 Restoring the ASDB Database into an Active AutoStart System... 175 To Restore the ASDB Database into an Active AutoStart System... 175 Registering an AutoStart license with EMC... 178 Activating / Registering Your Software... 178 Enabling.NET v3.5... 179 To Enable.NET v3.5... 179 Editing the SQL Server 2012 Database Backup Schedule... 182 To Edit the Database Backup Schedule... 182 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 7 of 184

About this Document About this Document Summary This document presents a brief overview of AutoStart and - in the order they must be performed the procedures and processes necessary to install and configure AutoStart. Before You Start This Install Guide was created when installing AutoStart and SQL Server on new computers. It can be used to build an AutoStart pair from existing File Servers that meet the minimum specifications for AutoStart and Windows Server 2008 R2 64-bit. This guide was written for AutoStart 5.4.2 Windows (x64) This document is based on the AutoStart version 5.4 Windows (x64) About SQL Server Uninstall SQL Server before you proceed with an AutoStart installation. If you have an existing SQL Server database, back it up using SQL Server resources. Back it up to a safe location before proceeding with the AutoStart/SQL Server installation. Please use the Creating an SQL Server 2005 Express Database Backup or Creating an SQL Server 2008 ASDB Database Backup section for reference. WARNING: Failure to back up the database may result in loss of data. You should have your SQL database administrator present when backing up the database. Node Cluster Support AutoStart supports more than two nodes in a cluster, but it is assumed that there will be two nodes in one AutoStart domain in this document. ADCDB is used for the AutoStart Domain. HARRISNET is used for the Workgroup name, and AUTOSTART1 and AUTOSTART2 are given to the two File Servers. ASSQL is used for the Automation node alias. 172.16.10.40 is used for its managed IP address, which acts as a virtual IP. HOUSEDB is used for the House node alias. 172.16.20.40 is used for its managed IP address, which acts as a virtual IP. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 8 of 184

About this Document For node 1, Autostart1, 172.16.10.46 is given for the Automation NIC, 172.16.20.38 for the House NIC, and 172.16.30.10 for the Dedicated Link NIC. For node 2, Autostart2, 172.16.10.47 is given for the Automation NIC, 172.16.20.39 for the House NIC, and 172.16.30.11 for the Dedicated Link NIC. Note: In each installation, after carefully choosing the values, replace all of the items bolded above with the proper values. References EMC AutoStart Version 5.3 CONCEPTS GUIDE (300-005-714 REV A02) EMC AutoStart Version 5.3 SP4 INSTALLATION GUIDE (300-005-712 REV A05) EMC AutoStart Version 5.3 SP4 ADMINISTRATOR S GUIDE (300-005-713 REV A06) EMC AutoStart Module for SQL Server 2000 Version 2.0 ADMINISTRATOR S GUIDE (300-003- 530 REV A01) 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 9 of 184

Application Overview Application Overview About AutoStart EMC AutoStart keeps a company s applications up and running smoothly during both planned and unplanned events. AutoStart works within an existing environment to: Relocate affected resources and restart a protected application should an application or environment fail. Monitor and automate responses to events. This means that system maintenance, load fluctuations, business work flow cycles, and even human error, and other factors that can impact availability and effectiveness can be monitored and maintained. Features AutoStart enables system administrators to control, manage, and predict resource behavior during any event. Supported features include: System Changes AutoStart allows you to relocate resources with minimum downtime during application and environment upgrades. AutoStart provides a maintenance mode that allows managed resources in and out of the monitored state in order to avoid triggering erroneous migration during maintenance. Failure AutoStart provides complete and flexible failover capabilities at the application and node level. AutoStart minimizes downtime by detecting failures quickly when they occur, and allows you to have complete control over AutoStart migration by configuring shutdown and startup sequences. Disaster Recovery AutoStart safeguards data by providing all of the components required to protect applications and data through mirror restore. Required Hardware and Software The systems should meet the minimum specifications for AutoStart as well as Windows Server 2008 R2 64-bit. Please check with EMC and MS. 2 PC servers with MS Windows Server 2008 R2 64-bit Standard Edition, and the latest update patches installed The two systems do not have to have an identical H/W spec, but it is desired. They should be as similar as possible in RAM, processor speed, and disk technology The PC Servers should have two or more NICs, and Gigabit Ethernet is preferable. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 10 of 184

Application Overview It is recommended using a Gigabit Switching Hub due to heavy traffic among nodes in addition to traffic to/from clients The Dedicated Link between the two nodes can be a direct connection, without a Hub, by using a Gigabit Crossover Cable. If there is no Switching Hub, this is strongly recommended. A client PC is also recommended, for performing quick tests to verify each installation step. Notification Agent Integration Summary For environments where one or more device server lists need to be updated with database updates from 3 rd party systems such as Automatic Ingest or IMM, Notification Agent can be installed. Notification agent monitors the tables of a SQL database for any changes (add/remove/edit) and then updates the lists of any configured device servers with the appropriate changes. Normally only one instance of Notification Agent is needed in a broadcast environment, but because it needs to be installed with the SQL engine, an instance is required for each AutoStart node. The instance on the active AutoStart node will detect database changes and update the device server lists because the SQL engine will only be running on that one node. Constraints Using Notification Agent with an AutoStart system requires: All nodes of the AutoStart system need to be fully installed and operational before installing Notification Agent. Installing the same version of Notification Agent on all AutoStart nodes using the exact same configuration. Replicating all future Notification Agent configuration changes to all instances on the AutoStart nodes. Installing Notification Agent to a drive (C:) that is not managed by AutoStart Configuring the File-Based Communication Log to write to a directory other than the MIRROR, (:\D), drive of the AutoStart File Server Pair. All Notification Agent configurations must be done while the AutoStart system is Offline. Installation Follow the instructions given in the Notification Agent and AutoStart installation guides to install Notification Agent on each node. After installation, the updates will be processed from only the active AutoStart node. The AutoStart console can be used to change the active node and verify each Notification Agent instance. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 11 of 184

Application Overview Known Issues 64553: AC 4.19.17.0A generates an Access Violation during or after an AutoStart failover. Workaround Click Ignore to the Access Violation, close the Air Client, and re-launch the Air Client. 72506: The Database window is unresponsive after an AutoStart failover with MC 4.19.26.0M. Workaround Close and re-open the Database window. EMC does not currently support SQL Server 2012. Workaround All SQL 2012 functionality needed by ADC has been tested by Imagine Communications in the ADC Lab. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 12 of 184

File Server Preparations File Server Preparations This chapter includes the recommended requirements and network preparations for an AutoStart installation. Preparing the File Servers Here are the recommended requirements for an AutoStart installation. AutoStart File Server Recommendations 1. The File Server should have either two or more HDD or two or more partitions when it has only one HDD. 2. The disks or the partitions which are to be mirrored should be the same size on both nodes, but the target disk can have slightly more disk space than the source disk. 3. The O/S should be installed to a different HDD or partition from the one that the mirrored disk will use. 4. Make sure that MS Windows Server 2008 R2 64-bit Standard Edition OS gets the latest update patches, as well as any service packs. 5. Ensure the Windows Firewalls are disabled. 6. Granted that there are two HDD or partitions with drive letter C for O/S and D for mirrored disk, C drive should always be available to the system and D drive is available only when the system is playing the role of active node. So, care should be taken when installing application programs like SQL Server, and when planning to have something shared by a Windows client. 7. Administrator should have a non-blank password. 8. The two File Servers should be given fixed IP addresses, which should be in the same subnet mask Domain as the Automation network. 9. Make sure that the two File Servers and one client have no problem with belonging to the same workgroup, and that folder/file sharing is shown in My Network Places. 10. Make sure that systems can ping each other using either the IP address or system name. 11. The NIC for Dedicated Link should only have TCP/IPv4 enabled and configured. 12. The Speed and Duplex setting for all NICs should be configured for 1.0 GB Full Duplex. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 13 of 184

File Server Preparations Configuring AutoStart Network Connections The following procedure specifies how to configure general AutoStart network connections and unique configurations for the Dedicated Link NIC. To Configure AutoStart Network Connections 1. On the first File Server computer, click on Start, Control Panel, and select Network and Sharing Center. 2. Click on Change adapter settings. 3. Highlight the top NIC, right click, select Rename, and name it AUTOMATION. 4. Highlight the second NIC, right click, select Rename, and name it DEDICATED LINK. 5. Highlight the third NIC, right click, select Rename, and name it HOUSE: 6. Press Alt + N on the keyboard and select Advanced Settings : 7. Use the arrows in the Advanced Settings window to set the order of the NICs so that the top one is AUTOMATION, the next one is DEDICATED LINK, the third one is HOUSE, and the unused *one is at the bottom: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 14 of 184

File Server Preparations 8. Click OK. 9. Repeat steps 1-9 on the second File Server computer. Configuring the Dedicated Link NIC The AutoStart Dedicated Link NIC requires unique configurations for optimum system performance. This section describes how to configure the Dedicated Link NIC for AutoStart. To Configure the Dedicated Link NIC 1. On the first File Server computer, click on Start, Control Panel, and select Network and Sharing Center. 2. Click on Change adapter settings. 3. Select Dedicated Link, right click, and select Properties. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 15 of 184

File Server Preparations 4. Disable, (uncheck), everything on the Networking tab except Internet Protocol Version 4 (TCP/IPv4): 5. Select Internet Protocol Version 4 (TCP/IPv4), select Properties, and then Advanced. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 16 of 184

File Server Preparations 6. Select the DNS tab and disable, (uncheck), everything except Append primary and connection specific DNS suffix: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 17 of 184

File Server Preparations 7. Select the WINS tab, disable, (uncheck), everything except Disable NetBIOS over TCP/IP, and click OK: 8. Click OK in the Internet Protocol Version 4 (TCP\IPv4) Properties window. 9. Click Close in the DEDICATED LINK Properties window. 10. Select Dedicated Link, right click, and select Properties. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 18 of 184

File Server Preparations 11. Select Configure, select the Link Speed tab, using the Speed and Duplex drop down arrow select 1.0 Gbps Full Duplex, and click OK: 12. Repeat Steps 1-12 on the second File Server computer. Prerequisites to using the DNS registration options IMPORTANT: You may not need to perform all of the procedures listed in this section. What needs to be done will depend on the Network Architecture of the facility you are at. Some operations will only need to add the name of the Node Aliases to their DNS Server. Operations that do not have a DNS Server will need to add Host Tables to their File Servers. Discuss this section with the facility s Network Administrator to determine what procedures will need to be done. Before you can register a C Name or an A Record for a node alias, you must complete the following prerequisites for the node: Add the computer s name in the AutoStart domain to the DNS Admins Security Group of the DNS server. Verify that the DNS admins group has full control of lookup zones in the DNS server. Verify on the DNS server that the TCP/IP properties grant access to DNS administrators for the lookup zone. Create a new registry key: Open the Registry Editor. (From the Start menu, select Run. In the dialog that opens, type regedit.) 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 19 of 184

File Server Preparations In the Registry Editor, navigate to: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters In this folder, create a new key called DnsServerToUpdate and give it the following values: Make sure the Type is REG_SZ. In its Data field, specify the IP address of the DNS server. If there s more than one DNS server, separate the IP addresses with commas (,). Configuring AutoStart Host Tables Host Tables will need to be configured on the File Servers and Client computers if you will not be using a DNS Server. To Configure AutoStart Host Tables 1. Open Explorer, go to C:\Windows\system32\drivers\etc, and open the hosts file with Notepad: 2. Enter the IP Addresses and Computer Names of the File Servers and Node Aliases into it and Save the file: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 20 of 184

File Server Preparations Disabling Power Management on File Server NICs Reduce link speed during standby is enabled by default in Windows Server 2008 R2 64-bit. AutoStart requires uninterrupted communication between the two File Servers for monitoring system status and operations. Disabling power management on the File Server NICs assures that AutoStart and File Server\Client communications will not be interrupted by this. Use the following procedure to disable power management of the File Server NICs. To Disable Power Management on File Server NICs 1. Select Start\Server Manager\View Network Connections. 2. Select the first NIC, right click, and select Properties. 3. Select Configure on the Networking tab of the NIC Properties window. 4. Click on the Power Management tab, disable (uncheck) Allow the computer to turn off this device to save power, and click OK: 5. Repeat Steps 1-4 for the next two Nics. 6. Close the Network Connections window, and then close the Server Manager. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 21 of 184

File Server Preparations 7. Repeat steps 1-6 on the second File Server computer. Configuring File Server Passwords to Not Expire A File Server password is used when configuring AutoStart. Because AutoStart would need to be reconfigured if the password were changed, it is desirable that it be configured to not expire. Use this procedure to configure the File Server passwords to not expire. IMPORTANT: Imagine Communications File Server computers are pre-configured with the password of harris. If any other password will be used with this AutoStart File Server pair it should be changed prior to starting the AutoStart installation. Please see the Changing AutoStart File Server Passwords section if the password must be changed after the initial AutoStart installation. To Configure File Server Passwords to Not Expire 1. Select Start\Administrative Tools\Local Security Policy. 2. Open Account Policies, and then Password Policy. 3. Double click on Maximum password age, set the Password will not expire field to Zero (0) on the Local Security Setting tab of the Maximum password age Properties window: 4. Click Apply, and then click OK. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 22 of 184

File Server Preparations 5. Close the Local Security Policy window. 6. Repeat steps 1-5 on the second File Server computer. Disabling Automatic Windows Updates Install updates automatically is enabled by default in Windows Server 2008 R2 64-bit. Many Windows Updates require restarting the computer to complete their installation. Unplanned File Server reboots may interrupt Automation operations. Manually managing the installation of Windows Updates can avoid these possible interruptions. This procedure describes how to disable automatic Windows Updates. To install Windows Updates please use the Installing Windows Updates on an Active AutoStart System section. To Disable Automatic Windows Updates 1. Select Start\Windows Update. 2. Select Change settings. 3. Using the drop down arrow in the Important updates area, select Check for updates but let me choose whether to download and install them: 4. Click OK. 5. Close the Windows Update window. 6. Repeat steps 1-5 on the second File Server computer. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 23 of 184

Renaming FS-1, and SQL Server 2012 Installation Renaming FS-1, and SQL Server 2012 Installation This chapter includes sections for renaming File Server 1, installing SQL Server 2012, and enabling the Named Pipes protocol. Renaming the First File Server to ASSQL ASSQL is the SQL Server virtual server name that will be used for SQL services. When the SQL Server module instance is defined to AutoStart the virtual name is used as the node alias. Installing SQL Server 2012 and any available Service Packs and/or Updates on the File Servers, when named as the node alias assures that all services and functionality will be available on either node when it is active. Future SQL Server 2012 Service Pack installations after AutoStart has been installed do not require this procedure. Please see the Installing Future SQL Server 2012 Service Packs section for how to install later SQL Server 2012 Service Packs that become available after AutoStart has been installed. Use these steps to rename File Server 1 to ASSQL. To Rename the First File Server to ASSQL 1. Click Start, right click on the Computer s Name, and select Properties. 2. Click Change settings. 3. Click Change on the Computer Name tab of the System Properties window. 4. Enter ASSQL for Computer Name and click OK. 5. Click OK in the pop up Computer Name/Domain Changes window: 6. Close the System Properties window and click Restart Now in the Microsoft Windows window. 7. After the computer restarts it is time to install SQL Server 2012 on it. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 24 of 184

Renaming FS-1, and SQL Server 2012 Installation Before installing SQL Server 2012 Windows Server 2008 R2 64-bit should be updated to the most recent Service Pack and updated with the most recent Updates Before installing SQL Server 2012 Standard. These are available through Windows Updates. For details on the installation of Windows Server 2008 R2 64-bit, refer to Windows Server 2008 R2 64-bit Install Guide. Installing SQL Server 2012 IMPORTANT: SQL Server 2012 will NOT install without having the.net v3.5 installed in the computer. Ensure.NET v3.5 is installed prior to installing to SQL Server 2012. See Enabling.NET v3.5 for how to do this. Install SQL Server 2012 1. Load the Microsoft SQL Server 2012 DVD, browse to its directory, and double click on Setup.exe. 2. Wait while Microsoft SQL Server 2012 Setup processes the current operation: 3. When the SQL Server Installation Center opens click on Installation. 4. Click on New SQL Server stand-alone installation or add features to an existing installation. 5. Wait while Microsoft SQL Server 2012 Setup processes the current operation. 6. Verify that all of the Setup Support Rules passed and click OK: 7. Wait while Microsoft SQL Server 2012 Setup processes the current operation. 8. Enter the product key and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 25 of 184

Renaming FS-1, and SQL Server 2012 Installation 9. Accept the license terms and click Next: 10. SQL Server 2012 will search for Product Updates and then reports its status. Click Next: 11. The Setup Support Files screen appears and its Status goes to In Progress: 12. Verify that all of the Setup Support Rules passed and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 26 of 184

Renaming FS-1, and SQL Server 2012 Installation 13. On the Setup Role screen select SQL Server Feature Installation and click Next. 14. On the Feature Selection screen Enable, (check), Database Engine Services, Client Tools Connectivity, Client Tools Backwards Compatibility, Management Tools Basic, and Management Tools - Complete, and then click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 27 of 184

Renaming FS-1, and SQL Server 2012 Installation 15. On the Installation Rules screen, if desired, view the result of the rules processing. When ready press Next. 16. Verify that Default Instance is selected on the Instance Configuration screen and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 28 of 184

Renaming FS-1, and SQL Server 2012 Installation 17. Click Next on the Disk Space Requirements screen: 18. On the Service Accounts tab of the Server Configuration screen set the: SQL Server Agent to NT Service\SQLSERVERAGENT SQL Server Database Engine to NT Service\MSSQLSERVER SQL Server Browser to NT AUTHORITY\LOCAL SERVICE SQL Server Agent, SQL Server Database Engine, and SQL Server Browser Startup Types to Manual 19. On the Collation tab of the Server Configuration screen, click Customize in the Database Engine area, select SQL collation, used for backwards compatibility, choose SQL_Latin1_General_CP1_CS_AS, and click OK: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 29 of 184

Renaming FS-1, and SQL Server 2012 Installation 20. The Collation tab of the Server Configuration screen should now look like this: 21. Click Next on the Server Configuration screen: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 30 of 184

Renaming FS-1, and SQL Server 2012 Installation 22. On the Server Configuration tab of the Database Engine Configuration screen: Select Mixed Mode. Enter HarrisDB1 (case sensitive) in the Enter password area. Enter HarrisDB1 (case sensitive) in the Confirm password area. Click on Add Current User in Specify SQL Server administrator s area. 23. On the Data Directories tab of the Database Engine Configuration screen: Change the Data root directory to D:\Program Files\Microsoft SQL Server\ Set the User database directory to D:\DATABASE Set the User databaselog directory to D:\DATABASE Reset the Temp DB directory and Temp DB log directories back to C:\Program Files\Microsoft SQL Server\... Set the Backup directory to D:\BACKUP Note: Database Servers can have single or multiple partitions. Imagine Communications ships Database Servers with two partitions (\C: and \D:). If required, change the location to C:\DATABASE, D:\DATABASE, or whatever is needed. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 31 of 184

Renaming FS-1, and SQL Server 2012 Installation 24. Click Next. 25. Verify that the Error Reporting checkbox is not enabled and click Next. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 32 of 184

Renaming FS-1, and SQL Server 2012 Installation 26. Verify that all of the Installation Configuration Rules passed and click Next: 27. Click Install on the Ready to Install screen: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 33 of 184

Renaming FS-1, and SQL Server 2012 Installation 28. Wait while Microsoft SQL Server 2012 Setup processes the current operation. 29. Click Close on the Complete screen: 30. The SQL Server 2012 installation is now complete. NOTE: If this installation of SQL Server 2012 was on the Node 2 (AUTOSTART2) computer then this is a reminder to continue on; using the Enabling the Named Pipes Communications Protocol section below. Enabling the Named Pipes Communications Protocol The Named Pipes Communications Protocol is not enabled when installing SQL Server 2012. This Communications Protocol must be enabled before client computers can connect to the SQL Server 2012 Database via Named Pipes. Use the following procedure to enable the Named Pipes Communications Protocol. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 34 of 184

Renaming FS-1, and SQL Server 2012 Installation To Enable the Named Pipes Communications Protocol 1. Select Start\All Programs\Microsoft SQL Server 2012\Configuration Tools\SQL Server Configuration Manager: 2. Expand SQL Server Network Configuration, select Protocols for MSSQLSERVER, select Named Pipes, right click, and select Enable: 3. Click Apply, and OK the Warning: 4. Verify that Named Pipes is now Enabled: 5. Close the SQL Server Configuration Manager. 6. Install any Service Packs that are currently available for SQL Server 2012 on this computer now. 7. If Named Pipes was just enabled on the Node 2 (AUTOSTART2) computer go to the Renaming the Second File Server to AUTOSTART2 section now. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 35 of 184

Renaming FS-1, and SQL Server 2012 Installation Renaming the First File Server to AUTOSTART1 Now that SQL Server 2012 and any available Service Packs have been installed on this File Server it is time to rename it to the Primary Node name of AUTOSTART1. Use the following procedure to rename the first File Server to AutoStart1. To Rename the First File Server to AUTOSTART1 1. Click Start, right click on the Computer s Name, and select Properties. 2. Click Change settings. 3. Click Change on the Computer Name tab of the System Properties window. 4. Enter AUTOSTART1 for Computer Name and click OK. 5. Click OK in the pop up Computer Name/Domain Changes window: 6. Close the System Properties window, close the System window, and click Restart Now in the Microsoft Windows window. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 36 of 184

Renaming FS-2, and SQL Server 2012 Installation Renaming FS-2, and SQL Server 2012 Installation This chapter includes sections for renaming File Server 2, installing SQL Server 2012, and enabling the Named Pipes protocol. Renaming the Second File Server to ASSQL Now that the first File Server has been renamed to AUTOSTART1 it is time to rename the second File Server to ASSQL for installing SQL Server 2012 and any available Service Packs. Follow these steps to rename the second File Server to ASSQL. To Rename the Second File Server to ASSQL 1. Click Start, right click on the Computer s Name, and select Properties. 2. Click Change settings. 3. Click Change on the Computer Name tab of the System Properties window. 4. Enter ASSQL for Computer Name and click OK. 5. Click OK in the pop up Computer Name/Domain Changes window: 6. Close the System Properties window, close the System window, and click Restart Now in the Microsoft Windows window. 7. After the computer restarts it is time to install SQL Server 2012 on it. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 37 of 184

Renaming FS-2, and SQL Server 2012 Installation Before installing SQL Server 2012 on the Second File Server Windows Server 2008 R2 64-bit should be updated to the most recent Service Pack and updated with the most recent Updates Before installing SQL Server 2012. These are available through Windows Updates. Installing SQL Server 2012 on the Second File Server IMPORTANT: SQL Server 2012 will NOT install without having the.net v3.5 installed in the computer. Ensure.NET v3.5 is installed prior to proceeding to Install SQL Server 2012. See Enabling.NET v3.5 for how to do this. Installing SQL Server 2012 on the second File Server uses the same procedure that was used when installing it on the first File Server. To Install SQL Server 2012 on the Second File Server Please use the Installing SQL Server 2012 section for this installation procedure. Renaming the Second File Server to AUTOSTART2 Now that SQL Server 2012 and any available Service Packs have been installed on this File Server it is time to rename it to the Primary Node name of AUTOSTART2. The following procedure explains how to rename the second File Server to AUTOSTART2. To Rename the Second File Server to AUTOSTART2 1. Click Start, right click on the Computer s Name, and select Properties. 2. Click Change settings. 3. Click Change on the Computer Name tab of the System Properties window. 4. Enter AUTOSTART2 for Computer Name and click OK. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 38 of 184

Renaming FS-2, and SQL Server 2012 Installation 5. Click OK in the pop up Computer Name/Domain Changes window: 6. Close the System Properties window and click Restart Now in the Microsoft Windows window. 7. Now that both File Servers have had SQL Server 2012 and any SQL Server 2012 Service Packs that may be available at the time of this AutoStart installation installed on them; and they have been renamed to their Primary Node names, it is time to install AutoStart on Node 1. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 39 of 184

Installing AutoStart on Node 1 Installing AutoStart on Node 1 This chapter describes how to install AutoStart on Node 1 and establish Node trust. The procedures for installing AutoStart on Node 1 and on Node 2 are different, and both are included in this guide. Installing AutoStart on Node 1 Use the following procedure to install AutoStart on Node 1. To Install AutoStart on Node 1 1. Browse to the location of the AutoStart software 2. Double click on the AutoStart executable file EAS542_WIN_x64.exe. 3. Click Run in the Open File - Security Warning window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 40 of 184

Installing AutoStart on Node 1 4. Click Next in the AutoStart 5.4.2 window: 5. Accept the License Agreement and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 41 of 184

Installing AutoStart on Node 1 6. Click Next in the Custom Setup window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 42 of 184

Installing AutoStart on Node 1 7. Select Yes, this is the first node in the domain, enter ADCDB for Domain Name, leave the Initial Port Number as 8042, and click Next: 8. Select the AutoStart1Dedicated Link IP Address for Mirroring IP Address, enter the AutoStart license key, (or if the license key is not yet available use AMEVAL), click Add, and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 43 of 184

Installing AutoStart on Node 1 9. Click Install in the Confirm Settings window: 10. Click Finish: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 44 of 184

Installing AutoStart on Node 1 11. Click Yes to restart the computer: 12. After AutoStart is successfully installed on Node 1, from the desktop select: Start\All Programs\EMC AutoStart\EMC AutoStart Console 5.4.2. The EMC AutoStart Console launches 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 45 of 184

Installing AutoStart on Node 1 and should look similar to this: 13. Leave this EMC AutoStart Console open. Establishing Node Trust To Establish Node Trust - Make Node 1 Trust Node 2 1. On the EMC AutoStart Console, highlight the domain ADCDB. 2. On the Settings tab change the User Mode: from User to Advanced. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 46 of 184

Installing AutoStart on Node 1 3. Click Apply: 4. On the Licensing/Security tab enter administrator for User Name, autostart2 for Domain/Node, AutoStart2 Node 2 for Description, set Access Rights to Administrator, and click Add: 5. Leave this EMC AutoStart Console open. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 47 of 184

Installing AutoStart on Node 1 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 48 of 184

Installing AutoStart on Node 2 Installing AutoStart on Node 2 This chapter describes how to install AutoStart on Node 2; including instructions for confirming that Node 1 trusts Node 2. The procedures for installing AutoStart on Node 1 and on Node 2 are not the same. Installing AutoStart on Node 2 Part 1 Follow these steps for part 1 of installing AutoStart on Node 2. To Install AutoStart on Node 2 Part 1 1. Browse to the location of the AutoStart software 2. Double click on the AutoStart executable file EAS542_WIN_x64.exe. 3. Click Run in the Open File - Security Warning window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 49 of 184

Installing AutoStart on Node 2 4. Click Next in the AutoStart 5.4.2 window: 5. Accept the License Agreement and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 50 of 184

Installing AutoStart on Node 2 6. Click Next in the Custom Setup window: 7. Select No, (as this is the second node), enter AUTOSTART1 for Primary Node Name, enter ADCDB for Domain Name, leave the Initial Port Number as 8042, and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 51 of 184

Installing AutoStart on Node 2 Confirming that Node 1 Trusts Node 2 To Confirm that Node 1 Trusts Node 2 Follow these steps to Confirm that Node 1 Trusts Node 2. 1. Go to the EMC AutoStart Console on the node 1, (AUTOSTART1), computer. 2. Highlight the Domain ADCDB and click on the Event Log tab. 3. Confirm that AUTOSTART2 has connected to, and disconnected from, the domain via ftcli: Installing AutoStart on Node 2 Part 2 Use the following procedure to complete the installation of AutoStart on Node 2. To Install AutoStart on Node 2 Part 2 1. Return to the AUTOSTART2 computer to continue installing AutoStart on Node 2. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 52 of 184

Installing AutoStart on Node 2 2. Select the AutoStart2 Dedicated Link IP Address for Mirroring IP Address, and click Next: 3. Review the displayed settings, and if they are correct, click Install: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 53 of 184

Installing AutoStart on Node 2 4. Click Finish: 5. Restart the computer by clicking Yes: Set User Mode to Advanced 1. After the computer has restarted, open the EMC AutoStart Console. 2. Highlight the domain ADCDB. 3. On the Settings tab change the User Mode: from User to Advanced. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 54 of 184

Installing AutoStart on Node 2 4. Click Apply. Confirming that Nodes 1 and 2 are both Primary Nodes, and Node Promotion Both Nodes in the AutoStart pair are installed as, and intended to be, Primary Nodes. This allows for one of them to still work correctly if the other Node is unavailable. This section contains instructions for both confirming the status of the configured Nodes, and how to promote either of them if needed. To Confirm that Nodes 1 and 2 are both Primary Nodes Follow these steps to Confirm that Nodes 1 and 2 are both Primary Nodes. 1. Expand the Domain ADCDB, select Nodes, and look in the Agent Type column. Both the autostart1 and autostart2 Nodes should both display as Primary: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 55 of 184

Installing AutoStart on Node 2 2. If both Nodes are displayed as Primary, then go to the Configuring Point-to-point Domain Communications section now. To Promote a Secondary Node to a Primary Node If a Node was identified as a Secondary Node in the steps above then it will need to be promoted. Perform these steps to Promote a Secondary Node to a Primary Node. 1. Expand the Domain ADCDB, select Nodes, and look in the Agent Type column. (In this example Node 2, autostart2, is the Node that needs promoting): 2. Expand the Domain ADCDB, expand Nodes, and select the Secondary Node that needs to be promoted. (Node 2, autostart2, is the Node that needs promoting in this example): 3. Click Yes in the Confirm Promote of Node dialog: 4. In about 30 seconds both Nodes should then be displayed as Primary: 5. Continue on to the Configuring Point-to-point Domain Communications section now. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 56 of 184

Configuring the Domain for Point-to-point Communications and Managed IP Add Configuring the Domain for Pointto-point Communications and Managed IP Addresses This chapter explains how to configure Point-to-point Domain communications. AutoStart configures Multicast Domain Communications by default. Changing them to Point-to-point ensures that the Nodes communicate in the most direct way possible. This can also reduce overall network traffic. This chapter also includes a section on how to configure the Domain for Managed IP Addresses. Configuring Point-to-point Domain Communications Use the following procedure for Configuring Point-to-point Domain Communications. To Configure Point-to-point Domain Communications 1. Expand the ADCDB domain, expand Nodes, select autostart1, and click on the Failure Detection and Mirroring tab. 2. In the "Paths Defined for Node" area highlight the Network Usage Domain that contains the Local IP Address of the AUTOMATION NIC and displays the Destination IP Address of <Multicast>. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 57 of 184

Configuring the Domain for Point-to-point Communications and Managed IP Add 3. Select Point-to-point, enter the IP Address of the autostart2 AUTOMATION NIC, and click Edit Path: 4. In the "Paths Defined for Node" area highlight the Network Usage Domain that contains the Local IP Address of the HOUSE NIC and displays the Destination IP Address of <Multicast>. 5. Select Point-to-point, enter the IP Address of the autostart2 HOUSE NIC, and click Edit Path: 6. Click Apply. 7. Go back to Nodes, select autostart2, and click on the Failure Detection and Mirroring Tab. 8. In the "Paths Defined for Node" area highlight the Network Usage Domain that contains the Local IP Address of the AUTOMATION NIC and displays the Destination IP Address of <Multicast>. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 58 of 184

Configuring the Domain for Point-to-point Communications and Managed IP Add 9. Select Point-to-point, enter the IP Address of the autostart1 AUTOMATION NIC, and click Edit Path: 10. In the "Paths Defined for Node" area highlight the Network Usage Domain that contains the Local IP Address of the HOUSE NIC and displays the Destination IP Address of <Multicast>. 11. Select Point-to-point, enter the IP Address of the autostart1 HOUSE NIC, and click Edit Path: 12. Click Apply. Configuring the Domain for Managed IP addresses The FT_ASSIGN_IP_PING_TIMEOUT AutoStart domain attribute specifies the length of time to wait for the ping that ensures that the IP address specified is not currently in use before assigning the IP address. CAUTION: Setting the time-out value to 0 (zero) may cause IP conflicts and other operating system failures because AutoStart will not have time to verify the lack of existence of the IP before it assigns the IP. Use the following procedure for Configuring the Domain for Managed IP addresses. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 59 of 184

Configuring the Domain for Point-to-point Communications and Managed IP Add To Configure the Domain for Managed IP Addresses 1. In the tree view of the EMC AutoStart console, select the ADCDB domain. 2. Click the Settings tab. 3. In the Attribute field, type: FT_ASSIGN_IP_PING_TIMEOUT 4. In the Value field type 5, (the number of seconds you want AutoStart to wait for a ping). 5. Click Set: 6. Click Apply: Configuring Domain Failure Detection Settings The AutoStart domain network is used for normal heartbeat communication within the AutoStart domain. In most cases, this network is used for both AutoStart domain communication as well as communication with and between managed processes. The AutoStart domain network is the primary method used to determine if agents are online. Select the IP of a computer on the Automation network that will always be on, or the IP of the Router or Managed Switch that the Automation NIC is connected to, to ping. CAUTION: Do not set this IP to 127.0.0.1 because an external IP Address is required. Using 127.0.0.1 will cause the system to not work correctly. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 60 of 184

Configuring the Domain for Point-to-point Communications and Managed IP Add Use the following procedure to set the global isolation addresses for the entire AutoStart domain. To Configure Domain Failure Detection Settings 1. In the tree view of the EMC AutoStart console, select the ADCDB domain. 2. In the right panel, select the Isolation Settings tab. 3. In IP Address, enter the selected IP address that the AUTOMATION NIC is connected to, to ping: 4. Click Add IP Address. 5. Click Apply. Configuring the Local Isolation Network Perform the following steps to configure the Local Isolation Network. To Configure the Local Isolation Network 1. Expand Nodes on the EMC Console. 2. Highlight autostart1 on the EMC Console and select the Failure Detection and Mirroring tab. 3. Select Isolation in the Usage: window: 4. Enter the IP address that was selected in the section above: 5. Click Add Path. 6. Click Apply. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 61 of 184

Configuring the Domain for Point-to-point Communications and Managed IP Add 7. Highlight autostart2 on the EMC Console and select the Failure Detection and Mirroring tab. 8. Select Isolation in the Usage: window. 9. Enter the IP address that was selected in the section above. 10. Click Add Path. 11. Click Apply. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 62 of 184

Configuring and Assigning Managed IP Addresses Configuring and Assigning Managed IP Addresses This chapter has sections on how to create and assign managed AutoStart and House IP addresses. Note: You must select IP Addresses before you create the IP address. If you don't, you risk changing the IP address of the object that is currently selected. For example, if a module instance is selected in the tree view and the instance's Resources tab displays, your creating the IP address can possibly change the IP address of the module instance. For that reason, be sure to always select IP Addresses before working with IP addresses. This IP address must be one that is not currently being used on, or reserved for, this network. Configuring Managed AutoStart IP addresses Use this procedure for configuring the managed Automation IP address. To Configure a Managed Automation IP address 1. In the tree view of the EMC AutoStart console, select IP Addresses, right-click and select Create New IP Address. 2. Disable, (uncheck), Get IP from Name Service. 3. Enter the IP Address that was selected above. 4. Enter AUTOMATION for the Description. 5. Enter the subnet mask for this IP address. 6. Verify that autostart1 is selected for Node. 7. Verify that autostart1:automation is selected for Interface. 8. Click Set Interface to save the changes. 9. Select autostart2 for Node. 10. Verify that autostart2:automation is selected for Interface. 11. Click Set Interface to save the changes: 12. Click Apply: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 63 of 184

Configuring and Assigning Managed IP Addresses Configuring a Managed House IP address Use this procedure for configuring the managed House IP address. To Configure a Managed House IP address 1. In the tree view of the EMC AutoStart console, select IP Addresses, right-click and select Create New IP Address. 2. Disable, (uncheck), Get IP from Name Service. 3. Enter the IP Address that was selected above. 4. Enter HOUSE for the Description. 5. Enter the subnet mask for this IP address. 6. Verify that autostart1 is selected for Node. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 64 of 184

Configuring and Assigning Managed IP Addresses 7. Select autostart1:house for Interface. 8. Click Set Interface to save the changes. 9. Select autostart2 for Node. 10. Select autostart2:house for Interface. 11. Click Set Interface to save the changes. 12. Click Apply: Assigning Managed IP Addresses Use this procedure for assigning the managed Automation and House IP addresses. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 65 of 184

Configuring and Assigning Managed IP Addresses To Assign a Managed IP Address for Automation 1. In the tree view of the EMC AutoStart console, expand IP Addresses, select the top IP Address, right click on it, and select Assign IP. 2. Select autostart1: To Assign a Managed IP Address for House 1. In the tree view of the EMC AutoStart console, expand IP Addresses, select the bottom IP Address, right click on it, and select Assign IP. 2. Select autostart1: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 66 of 184

Configuring and Assigning Node Aliases Configuring and Assigning Node Aliases This chapter has sections that describe how to create and assign the ASSQL and HOUSEDB Node Aliases. Creating Node Aliases Use the following procedures for creating ASSQL and HOUSEDB Node Aliases. To Create an ASSQL Node Alias 1. In the tree view of the EMC AutoStart console, select Node Aliases, right click, and select Create New Node Alias. 2. In Name, type ASSQL. (Alias names must be less than 16 characters and may contain only alphanumeric characters and the hyphen, (-). AutoStart forces the node name to uppercase.) 3. Enable, (check), the Associate Node Alias with a Virtual IP checkbox. 4. From the Virtual IP Address drop-down list, select the Automation virtual IP Address configured above. IMPORTANT: Do not enable Register A Record, as described in the next Step, if you will be using Host Tables instead of a DNS Server. 5. Associate the node alias to an A Record by enabling, (checking), the Register A Record checkbox in the DNS Registration Options box, and click Apply: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 67 of 184

Configuring and Assigning Node Aliases To Create a HOUSEDB Node Alias 1. In the tree view of the EMC AutoStart console, select Node Aliases, right click, and select Create New Node Alias. 2. In Name, type HOUSEDB. (Alias names must be less than 16 characters and may contain only alphanumeric characters and the hyphen, (-). AutoStart forces the node name to uppercase.) 3. Enable, (check), the Associate Node Alias with a Virtual IP checkbox. 4. From the Virtual IP Address drop-down list, select the House virtual IP Address configured above. IMPORTANT: Do not enable Register A Record, as described in the next Step, if you will be using Host Tables instead of a DNS Server. 5. Associate the node alias to an A Record by enabling, (checking), the Register A Record checkbox in the DNS Registration Options box, and click Apply: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 68 of 184

Configuring and Assigning Node Aliases Assigning Node Aliases Use the following procedures for assigning the ASSQL and HOUSEDB Node Aliases. To Assign the ASSQL Node Alias 1. Expand Node Aliases on the EMC AutoStart console. 2. Select the ASSQL node alias and right click on it. 3. Select Assign Node Alias. 4. Select autostart1: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 69 of 184

Configuring and Assigning Node Aliases To Assign the House Node Alias 1. Select the HOUSE node alias and right click on it. 2. Select Assign Node Alias. 3. Select autostart1: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 70 of 184

Configuring Mirroring and Attaching the Mirror as a Data Source Configuring Mirroring and Attaching the Mirror as a Data Source This chapter has describes how to configure Mirroring for Windows Servers and EMC mirroring. It also explains how to attach the mirror as a Data Source. IMPORTANT: Before configuring the mirror, be sure to close any application that relies on the disk that is going to be mirrored. If the application is not closed properly before removing the drive upon which it relies, data corruption may occur. Configuring Source and Mirror Nodes Follow these steps for configuring Mirroring for Windows Servers. To configure Mirroring for Windows Servers 1. Open the EMC AutoStart console. In the tree view, expand the ADCDB domain. 2. In the tree view, expand Nodes and select autostart1; which will be the Source Node: 3. Click the Failure Detection and Mirroring tab. 4. From the Local Mirror Address drop-down list, select the AUTOSTART1 DEDICATED LINK IP Address, if it was not selected during installation. 5. From the Remote Mirror Host drop-down list, select autostart2; this will be the Remote Mirror Host. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 71 of 184

Configuring Mirroring and Attaching the Mirror as a Data Source 6. Click Apply: Configuring EMC Mirroring Follow this procedure for Configuring EMC Mirroring. To Configure EMC Mirroring 1. In the tree view of the EMC AutoStart console, select Data Sources, right click on it, select Create New Data Source, and then EMC Mirroring for Windows: 2. On the Settings tab, enter MIRROR for Data Source Name. 3. In the Drive Selection area, select the source node autostart1 from the Source Node list. From the Source Drive list, select D, the drive to be mirrored. 4. In the Drive Selection area, select the target node autostart2 from the Target Node list. From the Target Drive list, select the target drive D. 5. Select the following attach options: 6. Run CHKDSK on ATTACH DIRTYBIT 7. CHKDSK Parameters /F 8. Publish Default Share (e.g. C$) TRUE 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 72 of 184

Configuring Mirroring and Attaching the Mirror as a Data Source 9. Click Apply to create the data source: 10. Click Yes when asked to confirm Save of Mirror Datasource: Attaching the Mirror as a Data Source Use the following steps for Attaching the Mirror as a Data Source. To Attach the Mirror as a Data Source 1. Expand Data Sources. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 73 of 184

Configuring Mirroring and Attaching the Mirror as a Data Source 2. Highlight the Data Source MIRROR and right click on it. 3. Select Attach Data Source, and then autostart1: Note: The status for MIRROR will first display as Attached to autostart1 and then change to Warning: This is the normal behavior until the mirror is fully synchronized. The status will change back to Attached after the mirror is fully synchronized. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 74 of 184

Configuring ADCDB Domain Settings Configuring ADCDB Domain Settings This chapter explains how to configure Domain Failure Detection. Configuring ADCDB Domain Failure Detection Settings Follow these steps to configure the ADCDB domain s Failure Detection settings. To Configure ADCDB Domain Failure Detection Settings 1. In the tree view of the EMC AutoStart console select the ADCDB domain. 2. In the right panel, click the Statistics/Domain Failure Detection tab. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 75 of 184

Configuring ADCDB Domain Settings 3. Set the Min Detection Time/Heartbeat Interval to 5 sec / 500 millsec and click Apply: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 76 of 184

Configuring Notification Utility Processes Configuring Notification Utility Processes This chapter describes how to configure Notification Utility Processes that send messaging about the AutoStart system status to any configured computers. Configuring Startup and Shutdown Notification Utility Processes Follow these steps to configure the Startup and Shutdown Notification Utility Processes. To Configure the Startup Notification Utility Processes 1. Locate and open the AutoStart_Notification_Scripts_V1.0 folder. Open the AS1 folder and copy the Harris_Scripts folder. 2. On the AutoStart1 computer, browse to C:\Program Files (x86)\emc\autostart\adcdb and paste the Harris_Scripts folder there. 3. Open the AS2 folder and copy the Harris_Scripts folder. 4. On the AutoStart2 computer, browse to C:\Program Files (x86)\emc\autostart\adcdb and paste the Harris_Scripts folder there. 5. In the tree view of the EMC AutoStart console select Utility Processes. 6. Right click and select Create New Utility Process: 7. Enter StartupNotification for Name, using the selection arrow select Batch Command for Operation Type, enter. for Domain, Administrator for Userid, and harris (case sensitive) for Password and Confirm Password. Click on the Directory button and browse to C:\Program Files 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 77 of 184

Configuring Notification Utility Processes (x86)\emc\autostart\adcdb\harris_scripts, click on Choose Directory, and then click Apply: 8. Select the Options tab and enable, (check), Allow Access to the Windows Desktop: 9. Select the Script tab, click on Import, browse to C:\Program Files (x86)\emc\autostart\adcdb\harris_scripts, highlight Start.bat, click on Import, and then click Apply: To Configure the Shutdown Notification Utility Processes 1. In the tree view of the EMC AutoStart console select Utility Processes. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 78 of 184

Configuring Notification Utility Processes 2. Right click and select Create New Utility Process: 3. Enter SthutdownNotification for Name, using the selection arrow select Batch Command for Operation Type, enter. for Domain, Administrator for Userid, and harris (case sensitive) for Password and Confirm Password. Click on the Directory button and browse to C:\Program Files (x86)\emc\autostart\adcdb\harris_scripts, click on Choose Directory, and then click Apply. 4. Select the Options tab and enable, (check), Allow Access to the Windows Desktop. 5. Select the Script tab, click on Import, browse to C:\Program Files (x86)\emc\autostart\adcdb\harris_scripts, highlight Stop.bat, click on Import, and then click Apply: Configuring Startup and Shutdown Notification Scripts Follow these steps to configure the Startup and Shutdown Notification Scripts for the AutoStart1 and AutoStart2 computers. To Configure the Startup Notification Script on AutoStart1 1. On the AutoStart1 computer, browse to C:\Program Files (x86)\emc\autostart\adcdb\harris_scripts, highlight Startup.bat, right click, and select Edit. 2. Enter the Computer Names of all computers that should receive File Server status notifications. Use the existing script format of one Computer Name per line, and save the file when finished: To Configure the Shutdown Notification Script on AutoStart1 1. On the AutoStart1 computer, browse to C:\Program Files (x86)\emc\autostart\adcdb\harris_scripts, highlight Shutdown.bat, right click, and select Edit. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 79 of 184

Configuring Notification Utility Processes 2. Enter the Computer Names of all computers that should receive File Server status notifications. Use the existing script format of one Computer Name per line, and save the file when finished: To Configure the Startup Notification Script on AutoStart2 1. On the AutoStart2 computer, browse to C:\Program Files (x86)\emc\autostart\adcdb\harris_scripts, highlight Startup.bat, right click, and select Edit. 2. Enter the Computer Names of all computers that should receive File Server status notifications. Use the existing script format of one Computer Name per line, and save the file when finished: To Configure the Shutdown Notification Script on AutoStart2 1. On the AutoStart2 computer, browse to C:\Program Files (x86)\emc\autostart\adcdb\harris_scripts, highlight Shutdown.bat, right click, and select Edit. 2. Enter the Computer Names of all computers that should receive File Server status notifications. Use the existing script format of one Computer Name per line, and save the file when finished: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 80 of 184

The SQL Server Module The SQL Server Module This chapter covers how to enable the SQL Server Module and create a new instance of it, as well as creating the SQL Server Browser Service. Enabling the SQL Server Module A valid license key must be entered on the SQL Server module configuration tab to enable the SQL Server module. A 90 day temporary license key can be used if the SQL Server module license key is not currently available. Follow these steps to enter the SQL Server license key and enable the SQL Server module. To Enable the SQL Server Module by entering a License Key 1. Expand the ADCDB Domain on the tree view of the EMC AutoStart console, expand Modules, and select the SQL Server module. 2. On the Configuration tab in the New License Key field, enter the SQL module license key, (or if the license key is not yet available enter S5EVAL), and click Add. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 81 of 184

The SQL Server Module 3. The License Key field is populated and the License Type and Expires areas are updated: Creating a New SQL Server Module Instance This section has instructions for creating the SQL Server Module that AutoStart will manage. The Mirror must be attached to Node 1 before creating a new SQL Server instance on Node 1. Use these steps to create a New SQL Server Module Instance on Node 1. To Create a New SQL Server Module Instance on Node 1 1. Expand Data Sources, select Mirror, and on the Status tab confirm that the Mirror is attached to Node 1: IMPORTANT: If the Mirror is not yet fully synchronized the Node status for autostart1 is Warning. Do not proceed forward with the installation until Attached status is displayed. To see the current progress of Mirror synchronization; expand Data Sources: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 82 of 184

The SQL Server Module Note: Full synchronization of the MIRROR on the File Servers in the Imagine Communications Lab took approximately 50 minutes, (for 204GB). 2. From the Start menu of the AUTOSTART1, (Node 1), computer; select All Programs\Microsoft SQL Server 2012\Configuration Tools\SQL Server Configuration Manager. 3. Select SQL Server Services, select SQL Server (MSSQLSERVER), right click, and select Start: 4. In the same SQL Server Configuration Manager area select SQL Server Browser, right click, and select Start. 5. Also in the SQL Server Configuration Manager area select SQL Server Agent (MSSQLSERVER), right click, and select Start. 6. Select the SQL Server module in the directory tree of the EMC AutoStart console, right-click on it, and select Create Instance for SQL Server. 7. On the New Monitored SQL Server Instance screen enter SQL in the Instance Name field, and click Next to continue: 8. On the next New Monitored SQL Server Instance screen, in the Login Info area, enter: 9. In the Domain field, enter. 10. In the Userid field, enter Administrator 11. In the Password field, enter harris, (case sensitive), or the custom configured File Server password 12. In the Confirm field, enter harris, (case sensitive), or the custom configured File Server password 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 83 of 184

The SQL Server Module 13. Click Next to continue. 14. On the next New Monitored SQL Server Instance screen enter: 15. sa in the Login name field 16. HarrisDB1 (case sensitive) in the Password field 17. Click Next: 18. In the Available Nodes section of the next New Monitored SQL Server Instance screen, first double-click autostart1 to add it to the Selected Nodes list, and then do the same for autostart2. Confirm that autostart1 appears at the top of the Selected Nodes list. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 84 of 184

The SQL Server Module 19. Click Next to continue: 20. On the next New Monitored SQL Server Instance screen confirm that the Selected Node is set to autostart1 and that SQL Site Name is set to AUTOSTART1\(local): 21. Click Next. 22. On the next New Monitored SQL Server Instance screen, highlight and move, (by using the left arrow), the master, model, and msdb databases in Available Databases to Selected Databases, and click Next. (Note: At this point in the installation ASDB will not appear and cannot be selected as it will be created later in the process.) 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 85 of 184

The SQL Server Module 23. On the next New Monitored SQL Server Instance screen, using the drop down arrow in the IP Address field, select the Automation IP address that is managed by AutoStart, and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 86 of 184

The SQL Server Module 24. On the next New Monitored SQL Server Instance screen, select ASSQL from the drop down menu in the Node Aliases field, and click Next: 25. On the next New Monitored SQL Server Instance screen, enter ASSQL for SQL Server Virtual Name and click Next: 26. Select MIRROR in the Available Data Sources list of the next New Monitored SQL Server Instance screen, and click the left arrow button to move your selection to the Selected Data 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 87 of 184

The SQL Server Module Sources field, enable, (check), Parallel Attach, and click Next: 27. Currently we do not use this screen, click Finish to complete this section: Creating the SQL Server Browser Service Use the following procedure for creating the SQL Server Browser Service. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 88 of 184

The SQL Server Module To Create the SQL Server Browser Service 1. Expand the ADCDB Domain. 2. Select Services, right click, and select Create New Service: 3. Enter SQL_Server_Browser for Service Name, SQL Server Browser for Description, using the Service to run drop down menu select SQL Server Browser, and click Apply: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 89 of 184

Completing the Resource Group Completing the Resource Group Portions of the Resource Group were created earlier in this installation. This chapter includes procedures for adding the SQL Browser Service, the HOUSE IP, and the HOUSEDB Node Alias to the Resource Group. Adding the SQL Server Browser Service to the Resource Group Follow these steps to add the SQL Server Browser Service to the Resource Group. To Add the SQL Server 2012 Browser Service to the Resource Group 1. Expand the ADCDB Domain. 2. Expand Resource Group, select S5_SQL, click on the Settings tab, and select Service from the drop down menu in the Startup and Shutdown Sequences area: 3. Click Add 4. In the Service Properties window set the Service Failure Action to No Action, in the Wait Settings area disable, (uncheck), both Wait until service is running and Wait until service is stopped, and 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 90 of 184

Completing the Resource Group click Apply: 5. In the Startup Sequence area of Startup and Shutdown Sequences select SQL_Server_Browser, and using the up arrow, move it underneath S5_SQL_SQLAgent: 6. In the Shutdown Sequence area of Startup and Shutdown Sequences select SQL_Server_Browser, and using the down arrow, move it above S5_SQL_SQLAgent: 7. Click Apply. Adding the HOUSE IP to the Resource Group Use the following procedure to add the HOUSE IP to the Resource Group. To Add the HOUSE IP to the Resource Group 1. Expand the ADCDB Domain. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 91 of 184

Completing the Resource Group 2. Expand Resource Group, select S5_SQL, click on the Settings tab, and select IP from the drop down menu in the Startup and Shutdown Sequences area: 3. Click Add 4. In the IP Address Properties window disable, (uncheck), both Relocate Resource Group on Path Failed State and Relocate Resource Group on Unassigned State, and click Apply: 5. In the Startup Sequence area of Startup and Shutdown Sequences select the House IP, and using the up arrow, move it underneath the AUTOMATION IP: 6. In the Shutdown Sequence area of Startup and Shutdown Sequences select the House IP, and using the down arrow, move it above the AUTOMATION IP: 7. Click Apply. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 92 of 184

Completing the Resource Group Adding the HOUSEDB Node Alias to the Resource Group Use the following instructions to add the HOUSEDB Node Alias to the Resource Group. To Add the HOUSEDB Node Alias to the Resource Group 1. Expand the ADCDB Domain. 2. Expand Resource Group, select S5_SQL, click on the Settings tab, and select Node Alias from the drop down menu in the Startup and Shutdown Sequences area: 3. Click Add 4. In the Node Alias Properties window disable, (uncheck), both Relocate Resource Group on Path Failed State and Relocate Resource Group on Unassigned State, and click Apply: 5. In the Startup Sequence area of Startup and Shutdown Sequences select HOUSEDB, and using the up arrow, move it underneath the ASSQL: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 93 of 184

Completing the Resource Group 6. In the Shutdown Sequence area of Startup and Shutdown Sequences select HOUSEDB, and using the down arrow, move it above the ASSQL: 7. Click Apply. Adding the Notification Utility Processes to the Resource Group Use the following instructions to add the Notification Utility Processes to the Resource Group. To Add the Startup Notification Utility Process to the Resource Group 1. Expand the ADCDB Domain. 2. Expand Resource Group, select S5_SQL, click on the Settings tab, and select Utility Process from the drop down menu in the Startup and Shutdown Sequences area: 3. Click Add 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 94 of 184

Completing the Resource Group 4. Using the selection arrow in the Name area of the Utility Process Properties dialog, select StartupNotification, confirm that Add To Startup Sequence is enabled (checked) and click Apply: 5. Using the Startup Sequence up arrow, select Startup Notification and move it above StartupRescan, and click Apply: To Add the Shutdown Notification Utility Process to the Resource Group 1. Expand the ADCDB Domain. 2. Expand Resource Group, select S5_SQL, click on the Settings tab, and select Utility Process from the drop down menu in the Startup and Shutdown Sequences area: 3. Click Add 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 95 of 184

Completing the Resource Group 4. Using the selection arrow in the Name area of the Utility Process Properties dialog, select ShutdownNotification, disable (un-check) Add To Startup Sequence, enable (check) Add To Shutdown Sequence, and click Apply: 5. Using the Shutdown Sequence down arrow, select Startup Notification and move it below StartupRescan, and click Apply: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 96 of 184

Creating the ASDB Database and Configuring it for AutoStart Creating the ASDB Database and Configuring it for AutoStart This chapter covers creating the ASDB Database, its users and permissions, and making it a selected database in AutoStart. It also includes Notification Agent installation procedures and considerations. Running the CreateDB_All_ADC_SQL_2012_V1_3.sql Script If this is an upgrade from SQL Server 2005, SQL Server 2008, SQL Server 2005 Express, or SQL Server 2008 Express, please go to the section: Restoring an SQL Server Database Backup into SQL Server 2012. The SQL script CreateDB_All_ADC_SQL_2012_V1_3.sql is provided by Imagine Communications to create an SQL Server ODBC-compliant database. Use the CreateDB_All_ADC_SQL_2012_V1_3.sql script to create the SQL Database. IMPORTANT: If Notification Agent will be used with this ADC System then an additional script, CreatePermissions_NA_SQL_2012_V1_3.sql, will need to be executed to create NA Permissions after Notification Agent has been installed. Use the following procedure to create the ASDB Database, its users, and permissions. To Run the CreateDB_All_ADC_SQL_2012_V1_3.sql script: 1. On the Node 1 (AUTOSTART1) computer, select Start\All Programs\Microsoft SQL Server 2012\SQL Server Management Studio. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 97 of 184

Creating the ASDB Database and Configuring it for AutoStart 2. Enter AUTOSTART1 (or the configured computer name) for Server name and click Connect: 3. In the Microsoft SQL Server Management Studio select File\Open\File : 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 98 of 184

Creating the ASDB Database and Configuring it for AutoStart 4. Browse to the folder containing the SQL Scripts, select CreateDB_All_ADC_SQL_2012_V1_3.sql, and click Open: 5. Click Execute: 6. Verify in the Messages area that the Command(s) completed successfully: Creating the SQL Server 2012 Database Backup The SQL script DB_Full_Bkp_SQL_2012_V1_3.sql is provided by Imagine Communications to create Backups of all SQL Server Databases. It is set to do the Backups at 9:30 PM and will keep 30 days of them at any given time. The time and frequency of the Database Backups are configurable. Use the 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 99 of 184

Creating the ASDB Database and Configuring it for AutoStart Editing the SQL Server 2012 Database Backup Schedule section to change the Database Backup configurations. Use the DB_Full_Bkp_SQL_2012_V1_3.sql script to create the SQL Database. Note: To Change backup destination change code on lines: 69 and 97 Example: Line 69: SELECT @location = ''DriveLetter:\Foldername'' or SELECT @location = ''\\ComputerName\sharename'' Example: Line 97: SET @path = ''DriveLetter:\Foldername\'' or SET @path = ''\\ComputerName\sharename\'' To Create the Database Backup 1. Select File\Open File : 2. Browse to the directory containing the SQL Scripts, highlight DB_Full_Bkp_SQL_2012_V1_3.sql, and click Open: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 100 of 184

Creating the ASDB Database and Configuring it for AutoStart 3. Click Execute: 4. Verify in the Messages area that the Command (s) completed successfully: 5. Close the SQL Server Management Studio. 6. If Notification Agent is not part of this installation please go to the Running the AutoStart_Create_Node2_WA_Login.sql script section now. Installing Notification Agent Note: If Notification Agent will be not used with this ADC System then you may skip the Installing Notification Agent and Running the CreatePermissions_NA_SQL_2012_V1_3.sql Script sections and proceed to the Running the AutoStart_Create_Node2_WA_Login.sql script section. IMPORTANT: If Notification Agent was used with the original ADC System, then NA should be installed now on both File Servers. Notification Agent must be installed prior to Creating Notification Agent Database Permissions. For instructions on installing Notification Agent, please see the Notification Agent Installation and Operations Guide. If additional assistance is required, please contact Automation Support. Use the To Install Notification Agent on Node 1 and To Install Notification Agent on Node 2 sections and the Notification Agent Installation and Operations Guide for installing Notification Agent on an AutoStart File Server Pair. IMPORTANT: All Notification Agent configurations must be done before the AutoStart system is brought Online. The Data Source MIRROR needs to be attached to, and SQL Server Services must be running on, the Node that Notification Agent is being installed on. The following procedures are for installing Notification Agent on Nodes 1 and 2. To Install Notification Agent on Node 1 1. Open the EMC AutoStart console; expand the ADCDB Domain, and then Data Sources. 2. Select MIRROR, select the Status tab, and confirm that the status for it displays as Attached to Node 1: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 101 of 184

Creating the ASDB Database and Configuring it for AutoStart 3. Install Notification Agent on the AUTOSTART1 (Node 1) computer. 4. Launch and configure Notification Agent now. Note: ODBC connectivity for Notification Agent cannot be established on Node 1 until the entire AutoStart Resource Group has been brought Online. The AutoStart Resource Group will be brought Online later in this install. 5. From the Start menu of the AUTOSTART1, (Node 1), computer; select Start\All Programs\Microsoft SQL Server 2012\Configuration Tools\SQL Server Configuration Manager. 6. Select SQL Server Services, select SQL Server (MSSQLSERVER), right click, and select Stop: 7. Click Yes in the Stop Service confirmation window to allow the SQL Server Agent to also be stopped: Note: If the Stop Service confirmation window did not pop up when stopping the SQL Server (MSSQLSERVER) Service it will need to be stopped manually; select SQL Server Agent, right click, and select Stop 8. In the same SQL Server Configuration Manager area select SQL Server Browser, right click, and select Stop. 9. Close the SQL Server Configuration Manager. To Install Notification Agent on Node 2 1. Expand Data Sources, select MIRROR, right click, and select Detach Data Source: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 102 of 184

Creating the ASDB Database and Configuring it for AutoStart 2. Click Yes in the Confirm Detach of Datasource window: 3. Select MIRROR, right click, select Attach Data Source, then autostart2: 4. From the Start menu of the AUTOSTART2, (Node 2), computer; select Start\All Programs\Microsoft SQL Server 2012\Configuration Tools\SQL Server Configuration Manager. 5. Select SQL Server Services, select SQL Server (MSSQLSERVER), right click, and select Start: 6. In the same SQL Server Configuration Manager area select SQL Server Browser, right click, and select Start. 7. Also in the SQL Server Configuration Manager area select SQL Server Agent (MSSQLSERVER), right click, and select Start. 8. Install Notification Agent on the AUTOSTART2 (Node 2) computer. 9. If Test connection to the SQL Server using the defined login ID and password was selected during the NA install on Node 2 an error will be generated. Click OK: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 103 of 184

Creating the ASDB Database and Configuring it for AutoStart 10. Continue the NA installation by clicking OK: 11. Launch and configure Notification Agent now. Note: ODBC connectivity for Notification Agent cannot be established on Node 2 until the entire AutoStart Resource Group has been brought Online. The AutoStart Resource Group will be brought Online later in this install. Running the Create_Node2_WA_Login_SQL_2012_V1_3.sql script The SQL Server Management Studio on Node 2 is currently accessible by using SQL Server Authentication, the sa login, and the sa password. Imagine Communications provides the Create_Node2_WA_Login_SQL_2012_V1_3.sql script to create a Windows Authentication Login on the Node 2 computer so that the SQL Server Management Studio can be accessed via Windows Authentication without having to enter a login name or password. Follow these steps to create a Windows Authentication Login for Node 2. To Run the Create_Node2_WA_Login_SQL_2012_V1_3.sql script Note: If Notification Agent was just installed on the AUTOSTART2 (Node 2) computer, please start with Step 13 of the following procedure. 1. From the Start menu of the AUTOSTART1, (Node 1), computer; select All Programs\Microsoft SQL Server 2012\Configuration Tools\SQL Server Configuration Manager. 2. Select SQL Server Services, select SQL Server (MSSQLSERVER), right click, and select Stop: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 104 of 184

Creating the ASDB Database and Configuring it for AutoStart 3. Click Yes in the Stop Service confirmation window to allow the SQL Server Agent to also be stopped: Note: If the Stop Service confirmation window did not pop up when stopping the SQL Server (MSSQLSERVER) Service it will need to be stopped manually; select SQL Server Agent, right click, and select Stop 4. In the same SQL Server Configuration Manager area select SQL Server Browser, right click, and select Stop. 5. Close the SQL Server Configuration Manager. 6. Expand Data Sources, select MIRROR, right click, and select Detach Data Source: 7. Click Yes in the Confirm Detach of Datasource window: 8. Select MIRROR, right click, select Attach Data Source, then autostart2: 9. From the Start menu of the AUTOSTART2, (Node 2), computer; select All Programs\Microsoft SQL Server 2012\Configuration Tools\SQL Server Configuration Manager. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 105 of 184

Creating the ASDB Database and Configuring it for AutoStart 10. Select SQL Server Services, select SQL Server (MSSQLSERVER), right click, and select Start: 11. In the same SQL Server Configuration Manager area select SQL Server Browser, right click, and select Start. 12. Also in the SQL Server Configuration Manager area select SQL Server Agent (MSSQLSERVER), right click, and select Start. 13. On the AUTOSTART2 (Node 2) computer select Start\All Programs\Microsoft SQL Server 2012\ SQL Server Management Studio. 14. In the Connect to Server window: Confirm that Database Engine is entered for Server type Enter AUTOSTART2 for Server name Select SQL Server Authentication by using the drop down arrow in the Authentication field Enter sa for Login Enter HarrisDB1 for Password Click Connect: 15. In the Microsoft SQL Server Management Studio select File\Open\File : 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 106 of 184

Creating the ASDB Database and Configuring it for AutoStart 16. Browse to the folder containing the SQL Scripts or SQL Upgrade Scripts, select Create_Node2_WA_Login_SQL_2012_V1_3.sql, and click Open: 17. Click Execute: 18. Verify in the Messages area that the Command(s) completed successfully: 19. If Notification Agent is not part of this installation close the SQL Server Management Studio and go to the Making ASDB a Selected AutoStart Database section now. 20. If Notification Agent was just installed as part of an upgrade please go to the Upgrade Notification Agent Database Permissions section now. 21. If Notification Agent was just installed for a new installation, continue on to the next section below; Running the CreatePermissions_NA_SQL_2012_V1_3.sql Script now. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 107 of 184

Creating the ASDB Database and Configuring it for AutoStart Running the CreatePermissions_NA_SQL_2012_V1_3.sql Script Note: If Notification Agent was just installed on both File Servers as part of a system upgrade then please go to the Upgrade Notification Agent Database Permissions section for information on how to run the UpgradePermissions_NA_SQL_2012_V1_3.sql script. Notification Agent permissions need to be created now that Notification Agent has been installed on both File Server Nodes. Use the following procedure to run the CreatePermissions_NA_SQL_2012_V1_3.sql Script To Run the CreatePermissions_NA_SQL_2012_V1_3.sql Script 1. On the AUTOSTART2 (Node 2) computer select File\Open\File : 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 108 of 184

Creating the ASDB Database and Configuring it for AutoStart 2. Browse to the directory containing the SQL Scripts, highlight CreatePermissions_NA_SQL_2012_V1_3.sql, and click Open: 3. Click Execute: 4. Verify in the Messages area that the Command (s) completed successfully: 5. Close the SQL Server Management Studio. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 109 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group Configuring the Notification Agent Process and Adding it to the Resource Group This chapter explains how to create the Notification Agent Process. This process, (when added to the Resource Group), will control Notification Agent. It will start it on the Active Node, stop it during Node Relocation, and start it again on the newly Active Node. This chapter also includes sections on how to add this process into the Resource Group once it has been created, and for Logging off and back in to the AutoStart computers. Configuring the Notification Agent Process Use the following procedure to create the Notification Agent Process. To Configure the Notification Agent Process 1. Expand the ADCDB domain, select Processes, right click, and select Create New Process: 2. On the Settings tab of the New Process window: Enter NotificationAgent for Process Name Enter NotificationAgent for Description 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 110 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 3. click Apply: 4. In the Settings area of the New Process Configuration window: Enter NotificationAgent for Configuration Name Enter NotificationAgent for Description 5. In the Start Operation area of the New Process Configuration window: Verify that Operation Type is set to Executable Select Operation Browse to the Notification Agent install directory, (usually located at: C:\Program Files (x86)\harris Corporation\Notification Agent) Highlight NACore.exe Click on Choose File 6. In the Logon Info area of the New Process Configuration window: Enter. for Domain 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 111 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group Enter Administrator for Userid Enter harris, (case sensitive), or the custom configured File Server password for Password and Confirm 7. Select Directory 8. Browse to Notification Agent install directory, (usually located at: C:\Program Files\Harris Corporation\Notification Agent) 9. Click on Choose Directory: 10. Click on the Options tab. 11. In the I/O Redirection area enable, (check), Allow Access to the Windows Desktop 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 112 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 12. Click Apply: Adding the Notification Agent Process to the Resource Group Use the following procedure to add the Notification Agent Process to the Resource Group. To Add the Notification Agent Process to the Resource Group 1. Expand Resource Groups, select S5_SQL, and click on the Settings tab. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 113 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 2. Select Process by using the dropdown arrow in the Startup and Shutdown Sequences area and click on Add : 3. In the Process Failure Action area of the Process Properties window select Restart, enable, (check), Ignore No Response State in the Process No Response Action area, and click Apply: 4. Select NotificationAgent in the Startup Sequence area of Startup and Shutdown Sequences and by the needed arrow, move it below SQL_Server_Browser: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 114 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 5. Select NotificationAgent in the Shutdown Sequence area of Startup and Shutdown Sequences and by using the needed arrow, move it above SQL_Server_Browser: 6. Click Apply. Logging Off, and back In to the AutoStart Computers If the interactive process that was just configured were brought online now, this process would not start. The user must log off and log back in to the nodes before the Notification Agent Process will start correctly. Use the following procedure to Log off and back in to the AutoStart Computers. To Log Off and back In to the AutoStart Computers 1. On the AutoStart1 computer select Start, and then Log off: 2. Press Control + Alt + Delete on the keyboard. 3. Enter harris for the password and click Enter on the keyboard. 4. Repeat steps 1 3 on the other AutoStart computer. Making ASDB a Selected AutoStart Database After the ASDB Database has been created, (along with its users and permissions); it needs to become a selected database. Use the following procedures to make ASDB a Selected AutoStart Database. Stop all running SQL Server Services To make ASDB a Selected Database the Resource Group must first be brought Online. Stopping all running SQL Server Services before bringing the Resource Group Online allows AutoStart to start them without any SQL conflicts. 1. From the Start menu of the AUTOSTART2, (Node 2), computer select Start\All Programs\Microsoft SQL Server 2012\Configuration Tools\SQL Server Configuration Manager. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 115 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 2. Select SQL Server Services, select SQL Server (MSSQLSERVER), right click, and select Stop: 3. Click Yes in the Stop Service confirmation window to allow the SQL Server Agent to also be stopped: Note: If the Stop Service confirmation window did not pop up when stopping the SQL Server (MSSQLSERVER) Service it will need to be stopped manually; select SQL Server Agent, right click, and select Stop 4. In the same SQL Server Configuration Manager area select SQL Server Browser, right click, and select Stop. 5. Close the SQL Configuration Manager. Detach the mirror from autostart2 AutoStart will attach the mirror to the selected Node when the Resource Group is brought Online. Errors will be generated if the mirror is already attached when it tries to do this. Detaching the mirror now, helps AutoStart bring the Resource Group Online without conflict. 1. Expand the ADCDB Domain, expand Data Sources, select MIRROR, right click, and select Detach Data Source: 2. Click Yes in the Confirm Detach of Datasource window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 116 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 3. Install any EMC Hot Fixes and/or Cumulative Hot Fixes that may be available for AutoStart 5.4.2 on both Nodes. There were no Hot Fixes and/or Cumulative Hot Fixes available for AutoStart 5.4.2 when this guide was created. Check EMC s website for the availability of any AutoStart 5.4.2 Hot Fixes and/or Cumulative Hot Fixes. If any Hot Fixes and/or Cumulative Hot Fixes are available for this version then go to the Installing EMC AutoStart Version 5.4.2 Hot fixes and/or Cumulative Hot Fixes section and start with Step 8 of that procedure before continuing on to the next section below; Bring the Resource Group Online. Bring the Resource Group Online Expand the ADCDB Domain, expand Resource Groups, select S5_SQL, right click, select Bring Online, and then autostart1: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 117 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group To Make ASDB a Selected AutoStart Database 1. Open the EMC AutoStart Console, expand Modules, expand SQL Server, Highlight SQL, click on the Settings tab, and select ASDB in the Available Databases area: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 118 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 2. Use the left arrow to move ASDB to the Selected Databases window, and click Apply: 3. If Notification Agent was not part of this installation then you have completed this AutoStart installation. Configuring ODBC Data Sources for Notification Agent Notification Agent communicates via ODBC. An ODBC data source needs to be configured on each of the AutoStart computers so that NA can monitor database updates and update Transmission Lists when either computer is the active node. Follow these steps to configure an ODBC data source on both nodes. To Configure the ODBC Data Source on Node 1 1. Select Start\All Programs\Administrative Tools\Data Sources (ODBC). 2. Select the System DSN tab and click Add. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 119 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 3. Select SQL Server and click Finish: 4. Enter ASDB for Name, ASSQL for Server, and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 120 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 5. Select With SQL Server authentication using a login ID and password entered by the user, enter HarrisDB (case sensitive) for Login ID and Password and click Next: 6. Enable (check) Change the default database to:, and click Next: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 121 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 7. Click Finish: 8. Click Test Data Source: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 122 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 9. Confirm that TESTS COMPLETED SUCCESSFULLY! is displayed: 10. Click OK in all open windows to exit. To Configure the ODBC Data Source on Node 2 1. Re-locate the Resource Group to the AUTOSTART2 computer using the Re-locating the AutoStart Resource Group section. 2. Select Start\All Programs\Administrative Tools\Data Sources (ODBC). 3. Select the System DSN tab and click Add. 4. Select SQL Server and click Finish. 5. Enter ASDB for Name, ASSQL for Server, and click Next. 6. Select With SQL Server authentication using a login ID and password entered by the user, enter HarrisDB (case sensitive) for Login ID and Password and click Next. 7. Enable (check) Change the default database to:, and click Next: 8. Click Finish. 9. Click Test Data Source. 10. Confirm that TESTS COMPLETED SUCCESSFULLY! is displayed. 11. Click OK to exit all open windows. 12. Relocate the Resource Group back to the AUTOSTART1 computer if desired, or leave it running on the AUTOSTART2 computer. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 123 of 184

Configuring the Notification Agent Process and Adding it to the Resource Group 13. This AutoStart installation including Notification Agent is now complete. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 124 of 184

ADC Automation Configurations ADC Automation Configurations This chapter contains a section on Adjusting Client Net Bios Name Cache Timing for optimizing the ODBC re-connection time after the AutoStart Resource Group has been re-located. It also includes sections on Sharing Folders, and Mapping Network Drives. Adjusting Client Net Bios Name Cache Timing The Net Bios Name Cache Timing of Client computers in the system may need to be adjusted to optimize the ODBC re-connection time after the AutoStart Resource Group has been re-located. The configured timing value is dependent on the time it takes for the AutoStart Resource Group to relocate, the network design, and the performance of the system network. It takes approximately one minute and ten seconds, (1:10), to relocate the AutoStart Resource Group in the Imagine Communications Lab. The Client Net Bios Name Cache value used in the Imagine Communications Lab is one minute and fifteen seconds, (1:15). The Imagine Communications Lab is not using a DNS Server. Follow these steps to adjust Client Net Bios Name Cache Timing. To Adjust Client Net Bios Name Cache Timing 1. Click Start, select Run, enter regedit, and click OK. 2. Browse to HKEY_Local_Machine\SYSTEM\CurrentControlSet\Services\NetBT\Parameters. 3. Select CacheTimeout, right click, and select Modify. 4. In the Edit DWORD Value window select Decimal, enter 75 in the Value data field, and click OK: 5. Close the Registry Editor. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 125 of 184

ADC Automation Configurations Sharing Folders on the D: Drive; MIRROR In addition to containing the ADC Database, the Mirror drive of the AutoStart File Server pair is also available for safeguarding data directories. Folders on this drive need to be shared and granted the correct permissions before other computers in the network can write to them. This section describes how to share the folders, and grant them the correct permissions. Use Note: The D: Drive, MIRROR, is only accessible on the active AutoStart Node computer. An error is displayed when trying to open it on the inactive AutoStart Node. You will encounter this error if you are trying to access the Mirror drive on the inactive AutoStart Node: Click OK to accept the error and move to the active AutoStart Node to continue configurations. Use the following procedure to share folders on the D: Drive. To Share Folders on the D: Drive; MIRROR 1. Determine which File Server is currently the active Node, (the active Node is the one that has the Resource Group located on it). You can reference the Re-locating the AutoStart Resource Group section for determining which Node is currently active. 2. Open the D: Drive, (MIRROR), on the active Node. 3. Create or browse to the folder to be shared. 4. Highlight the folder, right click, and select Share : 5. Click Share in the File Sharing window. 6. Click Done in the File Sharing window. 7. This folder is now shared but it still needs permissions to be created for it. Creating Permissions for Shared Folders Now that the folders that will be shared have been created on the Mirror Drive, permissions for Client Computers to access and write to them need to be created. Use the following procedure for this. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 126 of 184

ADC Automation Configurations To Create Permissions for Shared Folders 1. Right click on the shared folder and select Properties. 2. Select the Security tab, and click Edit : 3. Select Users in the Group or user names area, and in the Permissions for Users area enable, (check), Allow for Full control: 4. Click Apply, and then OK. 5. Click OK in the Folder s Properties window. 6. This folder now has the correct permissions. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 127 of 184

ADC Automation Configurations Mapping Network Drives ADC Client, Traffic, and other computers that will access data directories that are located on the Mirror drive of the AutoStart File Server pair will need to be mapped to those folders. Use the following procedure to Map AutoStart File Server Network Drives. The example below was configured on a computer running Windows XP Pro. The Mapping procedure for other operating systems may be different. IMPORTANT: You will map to the configured AutoStart Node Aliases, and not to either of AutoStart File Server computers. ASSQL is the Automation Node Alias; and HOUSEDB is the House Node Alias. Note: The folders that will be mapped to need the correct permissions to allow access to other computers. Please see the Creating Permissions for Shared Folders section for more information on this. Follow these steps to map the Network Drives. To Map Network Drives 1. Select Start, Control Panel, Network Connections, right click, and select Open. 2. Right click on My Network Places and select Map Network Drive : Note: If My Network Places is not displayed as an option on the left side of the Network Connections window, then click on the Folders icon at the top of the Network Connections window to change the display of the Network Connections window: 3. Select the desired drive letter with the Drive: drop down arrow, and then click Browse. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 128 of 184

ADC Automation Configurations 4. In the Browse For Folder window select Harrisnet, the Automation or House Node Alias name (ASSQL or HOUSEDB), and then the directory you want to map to: Note: If the Shared Folders are not displayed when Assql or Housedb are expanded in the Browse For Folder window; select Start, Run, enter \\ASSQL or \\HOUSEDB in the Open field of the Run window, and then press OK: 5. Click OK in the Browse For Folder window. 6. Click Finish in the Map Network Drive window and the newly Mapped Drive will then open: 7. Repeat Steps 1-6 for Mapping other Network Drives. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 129 of 184

Operational AutoStart Procedures Operational AutoStart Procedures This chapter includes sections on how to re-locate the AutoStart Resource Group, re-configure AutoStart when File Server passwords are changed, and backup and restore the AutoStart Database. Re-locating the AutoStart Resource Group The AutoStart Resource Group may be run on either Node. The AutoStart Resource Group can be manually re-located to allow for computer maintenance. Computer maintenance should only be performed on a Node that is not currently hosting the AutoStart Resource Group. Manual relocation of the AutoStart Resource Group in the Imagine Communications Lab takes approximately one minute and ten seconds, (1:10). Use the following procedure for AutoStart Resource Group relocation. To Re-locate the AutoStart Resource Group 1. Select Start\All Programs\EMC AutoStart\EMC AutoStart Console 5.4.2. 2. Expand ADCDB, expand Resource Groups, and select S5_SQL: 3. Right click, select Relocate Resource Group, and select autostart2, (or the Node displayed as available with a green dot): 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 130 of 184

Operational AutoStart Procedures 4. Click Yes in the Confirm Relocate of Resource Group window: 5. The Resource Group has completely relocated when the Group State returns to Online and all of the resources branched under S5_SQL go green again and now show as assigned to the other Node: Changing AutoStart File Server Passwords Imagine Communications recommends that AutoStart File Server passwords be configured to never expire. If your operation requires that the AutoStart File Server passwords must be changed; the following procedure explains how to change them. This procedure assumes that the AutoStart Resource Group is running on the Node 1 (AUTOSTART1) computer, and that you have Administrator Logon permissions. IMPORTANT: All File Server functionality will not be available while the AutoStart File Server passwords are being changed. Client computers will not have connectivity to the ADC Database or be able to write to mapped drives on the File Server. Please schedule an appropriate maintenance window for this. To Change AutoStart File Server Passwords 1. Close any Client applications that communicate with the ADC Database, or that write Logs to mapped drives on the File Servers. 2. Select Start\All Programs\EMC AutoStart\EMC AutoStart Console 5.4.2 3. Expand the ADCDB Domain, expand Resource Groups, and select S5_SQL: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 131 of 184

Operational AutoStart Procedures 4. Right click on S5_SQL and select Take Offline: 5. Click Yes in the Confirm Take Resource Group Offline window: 6. When the entire Resource Group is Offline it should look like this: 7. On the Node 1 (AUTOSTART1) computer, select Start\Windows Security\Change a password. 8. Enter the old password into the Old password field, enter the new password into the New password and Confirm password fields, and then click on the right arrow. 9. OK the Your password has been changed message. 10. Repeat Steps 7-9 on the Node 2 (AUTOSTART2) computer 11. Expand Modules, expand SQL Server, select SQL, and click on the Settings tab. 12. Enter the new password into the Password and Confirm fields of the Logon Info area: 13. Click Apply. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 132 of 184

Operational AutoStart Procedures 14. Expand Resource Groups, and select S5_SQL: 15. Right click on S5_SQL and select Bring Online, and then autostart1: Backing up and Restoring AutoStart Database AutoStart needs a.def backup file to recover from an unexpected corruption or domain failure. It is highly recommended that a recent usable copy of the AutoStart domain be created; with backups kept in a safe location. Use the following procedures to Backup and Restore the AutoStart Database. IMPORTANT: The.def backup file generated by this process is editable. If an error is made when editing this file before using it to restore the AutoStart domain, database corruption of your AutoStart installation may occur. Please exercise extreme caution when working with any backup file you intend to use for restoration of an AutoStart domain. Any modifications done to the AutoStart configurations after the.def backup file has been created will be retained when the saved.def backup file is restored. Note: This is not the ADC Automation ASDB Database. The AutoStart Database contains resource definitions (including IP addresses, processes and services), sensor, trigger, and actuator definitions; scripts (including isolation scripts if configured), and rule text specific to AutoStart operations. Please see the Creating an SQL Server 2008 Database Backup section for how to backup the ADC Automation ASDB Database. To Backup the AutoStart Database 1. Expand the EMC AutoStart console and select the ADCDB Domain. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 133 of 184

Operational AutoStart Procedures 2. Select Action, and then Export Domain Information: 3. Browse to the location where the file will be saved, enter a name for it including the.def extension, and click Export: 4. The.def AutoStart Backup file has been generated and now is in the configured directory. To Restore the AutoStart Database 1. Open the EMC AutoStart console and expand Resource Groups. 2. Select S5_SQL, right click, and select Take Offline: 3. Click Yes in the Confirm Take Resource Group Offline window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 134 of 184

Operational AutoStart Procedures 4. When the entire Resource Group is Offline it should look like this: 5. Select the ADCDB Domain. 6. Select Action, and then Import Domain Information: 7. Browse to the location of the.def AutoStart Backup file, select it, and click Import: 8. The Restore is complete when the hourglass disappears and new entries are displayed on the Event Log tab: 9. Select S5_SQL, right click, select Bring Online, and then autostart1: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 135 of 184

AutoStart Disaster Recovery and Repairs AutoStart Disaster Recovery and Repairs In the event that AutoStart is not functional on either Node, the MIRROR Drive, (D:), on both computers will not be accessible. This chapter includes procedures for gaining access to the Data on the MIRROR Drives and how to rebuild the MIRROR Drive into the AutoStart system. Note: Make sure that you have exhausted all other options to get AutoStart functional on either node before performing the following procedure. Rebuilding the AutoStart system is fairly complex, and the system will be offline for a minimum of 1 ½ to 2 hours. Gaining Access to the MIRROR Drives Use this procedure to gain access to the Data on the MIRROR Drives in case of an AutoStart system failure. To Gain Access to the Data on the MIRROR Drives 1. Launch the EMC AutoStart Console on either AutoStart computer. Select Start\All Programs\EMC AutoStart\EMC AutoStart Console 5.3 SP4 2. Expand the Domain ADCDB, expand Resource Groups, and select S5_SQL: 3. Most likely the Resource Group will be Offline and look like this: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 136 of 184

AutoStart Disaster Recovery and Repairs 4. If either node has any resources assigned to it then you will need to take the Resource Group Offline. Right click on S5_SQL and select Take Offline: 5. Expand Data Sources, select MIRROR, right click, and choose Delete Current Data Source: 6. Expand Node Aliases, highlight ASSQL, (or the name of the Automation Node Alias in your system), and write down the IP Address of this Virtual IP: 7. Go to Program Files\EMC\AutoStart\ADCDB\bin folder and double click on VMVTEST.exe: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 137 of 184

AutoStart Disaster Recovery and Repairs 8. Enter 5 for Enter request, and then hit Enter on the keyboard twice: 9. Make note of the MSET name of the mirror you need to remove. For most AutoStart systems the MSET name will be MIRROR, (the names are case sensitive): 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 138 of 184

AutoStart Disaster Recovery and Repairs 10. Select option 2 and hit enter. Enter the mset name at the prompt and hit enter again to release the disk from the mirroring driver: 11. Verify that the drive is now available via Windows Explorer. 12. Repeat steps 1 through 11 on the other node. 13. Determine which D: Drive has the most up to date data. It is possible that the data on both Drives will be good, in which case, either can be used for the Emergency File Server. 14. On the computer determined to have the best data, (that will become the Emergency File Server), click on Start, Control Panel, and select Network and Sharing Center. 15. Right click on Network and Sharing Center and select Open. 16. Click on Manage network connections. 17. Select the AUTOMATION NIC, right click, and select Properties. 18. Select Internet Protocol Version 4 (TCP/IPv4), select Properties, and then in the IP Address area of the IP Settings tab click on Add... 19. Enter the IP and Subnet Mask of the Automation Virtual IP determined in Step 6 and hit Add: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 139 of 184

AutoStart Disaster Recovery and Repairs 20. The Virtual IP will now be on the Automation NIC: 21. OK out of all of the Automation NIC configuration windows and close the Network and Sharing Center. 22. Select Start\Administrative Toos\Services. 23. Locate the four EMC Services, and one at a time, right click on each of them and select Start: 24. Locate the three SQL Server Services, and one at a time, right click on each of them and select Start: 25. You should now be able to connect all client computers to the Emergency File Server. Rebuilding an AutoStart System After the failure in the AutoStart system has been identified and corrected, the system needs to be rebuilt into a File Server pair. Use the following section to rebuild the AutoStart system. Note: While this procedure is very comprehensive, it is recommended that you work with Automation Technical Support when rebuilding an AutoStart system. WARNING: Choosing the wrong computer as the Source Node may result in a total loss of data. To Rebuild the AutoStart System 1. On the computer that became the Emergency File Server, click on Start, Control Panel, and select Network and Sharing Center. 2. Right click on Network and Sharing Center and select Open. 3. Click on Manage network connections. 4. Select the AUTOMATION NIC, right click, and select Properties. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 140 of 184

AutoStart Disaster Recovery and Repairs 5. Highlight the Virtual IP that was added to this NIC and select Remove: 6. OK out of all of the Automation NIC configuration windows and close the Network and Sharing Center. 7. Launch the EMC AutoStart Console on either AutoStart computer. Select Start\All Programs\EMC AutoStart\EMC AutoStart Console 5.3 SP4 8. Expand the ADCDB Domain. 9. Expand Resource Group and select S5_SQL. 10. Most likely the Resource Group will be Offline and look like this: 11. If either node has any resources assigned to it then you will need to take the Resource Group Offline. Right click on S5_SQL and select Take Offline: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 141 of 184

AutoStart Disaster Recovery and Repairs 12. Select S5_SQL, click on the Settings tab, highlight MIRROR, and click Delete: 13. Click Apply: 14. Expand Data Sources, select MIRROR, right click, and choose Delete Current Data Source: 15. On the problem node select Start\Control Panel\Programs and Features, select AutoStart 5.3 SP4, and click on Uninstall: 16. Re-install AutoStart 5.3 SP4 on the problem node. Refer to the Installing AutoStart on Node 2 section of the AutoStart Installation Guide for this. 17. Launch the EMC AutoStart Console on either AutoStart computer. Expand the Domain ADCDB, expand Nodes, and confirm that both node status indicators are displayed in green: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 142 of 184

AutoStart Disaster Recovery and Repairs 18. Click on the first node under the Nodes section, go to the Failure Detection and Mirroring tab and unset the mirroring configuration for the Remote Mirror Host and Local Mirroring IP fields: 19. Click on Apply and let the Agent re-start: 20. Click on the second node under the Nodes section, go to the Failure Detection and Mirroring tab and verify if the mirroring configuration for the Remote Mirror Host and Local Mirroring IP fields are configured. 21. If the mirroring configuration is not set and looks like the picture above in Step 12, then go on to the next section. 22. If the mirroring configuration is still set and looks like the picture below, then repeat Steps 12 and 13 before going on to the next section: Note: It is now time to rebuild the MIRROR. The node with the best data will be the Source Node and the repaired problem computer will be the Remote Mirror Host. If Autostart1 was the failed computer in your system, then Autostart2 will be the Source Node and Autostart1 will be the Remote Mirror Host in the following procedure. WARNING: Choosing the wrong computer as the Source Node may result in a total loss of data. In the example below, Autostart1 is the Source Node and Autostart2 is the Remote Mirror Host. To configure Mirroring for Windows Servers 1. In the tree view, expand Nodes and select autostart1; which will be the Source Node: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 143 of 184

AutoStart Disaster Recovery and Repairs 2. Click the Failure Detection and Mirroring tab. 3. From the Local Mirror Address drop-down list, select the AUTOSTART1 DEDICATED LINK IP Address, if it was not selected during installation. 4. From the Remote Mirror Host drop-down list, select autostart2; this will be the Remote Mirror Host. 5. Click Apply: To Configure EMC Mirroring 1. In the tree view of the EMC AutoStart console, select Data Sources, right click on it, select Create New Data Source, and then EMC Mirroring for Windows: 2. On the Settings tab, enter MIRROR for Data Source Name. 3. In the Drive Selection area, select the source node autostart1 from the Source Node list. From the Source Drive list, select D, the drive to be mirrored. 4. In the Drive Selection area, select the target node autostart2 from the Target Node list. From the Target Drive list, select the target drive D. 5. Select the following attach options: Run CHKDSK on ATTACH DIRTYBIT CHKDSK Parameters /F Publish Default Share (e.g. C$) TRUE 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 144 of 184

AutoStart Disaster Recovery and Repairs 6. Click Apply to create the data source: 7. Click Yes when asked to confirm Save of Mirror Datasource: To Attach the Mirror as a Data Source 1. Expand Data Sources. 2. Highlight the Data Source MIRROR and right click on it. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 145 of 184

AutoStart Disaster Recovery and Repairs 3. Select Attach Data Source, and then autostart1: Note: The status for MIRROR will first display as Attached to autostart1 and then change to Warning: This is the normal behavior until the mirror is fully synchronized. The status will change back to Attached after the mirror is fully synchronized. To Add the MIRROR to the Resource Group 1. Expand the ADCDB Domain. 2. Expand Resource Group, select S5_SQL, click on the Settings tab, and select Data Source from the drop down menu in the Startup and Shutdown Sequences area: 3. Click Add 4. In the Data Source Properties window enable, (check), Relocate Resource Group on Path Failed State, Relocate Resource Group on Unassigned State, and Parallel Attach, and then click Apply: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 146 of 184

AutoStart Disaster Recovery and Repairs 5. In the Startup Sequence area of Startup and Shutdown Sequences select MIRROR, and using the up arrow, move it underneath the HOUSEDB: 6. In the Shutdown Sequence area of Startup and Shutdown Sequences select MIRROR, and using the down arrow, move it above the HOUSEDB: 7. Click Apply. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 147 of 184

AutoStart Disaster Recovery and Repairs Bring the Resource Group Online 1. Expand Resource Groups, and select S5_SQL: 2. Right click on S5_SQL and select Bring Online, and then autostart1: 3. When the entire Resource Group is Online again it should look like this: 4. If your AutoStart System now looks like the picture above, then it is fully functional and ready to go back Online. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 148 of 184

Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & Service Packs This chapter describes how to install EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & Service Packs on installed and running AutoStart systems. Installing EMC AutoStart Version 5.4.2 Hot Fixes and/or Cumulative Hot Fixes This section describes how to install any EMC AutoStart Hot Fixes and/or Cumulative hot Fixes after AutoStart has been installed. IMPORTANT: All File Server functionality will not be available while the AutoStart Version 5.4.2 hot fixes and/or Cumulative Hot Fixes are being installed. Client computers will not have connectivity to the ADC Database or be able to write to mapped drives on the File Server. Please schedule an appropriate maintenance window for this. Note: If you are installing any hot fixes during the initial AutoStart installation, please start with Step 8 of this procedure. To Install EMC AutoStart Version 5.4.2 Hot fixes and/or Cumulative Hot Fixes 1. Close any Client applications that communicate with the ADC Database, or that write Logs to mapped drives on the File Servers. 2. Open the EMC AutoStart Console on the Node 1 (AUTOSTART1) computer. 3. Expand the domain ADCDB. 4. Expand Resource Groups. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 149 of 184

Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & 5. Select S5_SQL, right click, and select Take Offline: 6. Click Yes in the Confirm Take Resource Group Offline window: 7. When the entire Resource Group is Offline it should look like this: 8. Browse to the directory that contains the EMC Hot fix and double click on its.exe. 9. Unzip the self-extracting.exe to the desired location. 10. Double click on Setup.exe. 11. Follow the prompts to install the Hot Fix. A re-start will be required. 12. Repeat Steps 7-11 on the Node 2 (AUTOSTART2) computer. Note: If the Hot fixes were installed during an initial AutoStart installation or an upgrade, please go to the Bring the Resource Group Online section now. Installing Windows Updates and/or Service Pack(s) on an Active AutoStart System Install updates automatically was disabled during the initial AutoStart installation to avoid unplanned File Server reboots that may interrupt ADC Automation operations. This section describes how to manually install Windows Updates and Service Packs on an Active AutoStart System. This procedure assumes that the AutoStart Resource Group is running on the Node 1 (AUTOSTART1) computer. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 150 of 184

Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & To Install Windows Updates on an Active AutoStart System 1. Open the EMC AutoStart Console, expand the ADCDB Domain, and expand Resource Groups. 2. Select S5_SQL, click on the Status tab, look in the Node column of the Status of Resource Group Elements area, and determine which Node is active, (autostart1 is the Active Node in this example): 3. Select S5_SQL, right click, and select Stop Monitoring: 4. The Monitoring State will go to Disabled when Monitoring is off: 5. Go the Node that is not active, (determined in Step 2), and install the Windows Updates and/or Service Pack(s). 6. Select S5_SQL, right click, select Relocate Resource Group, and select the available Node: 7. Click Yes in the Confirm Relocate of Resource Group window: 8. Install the Windows Updates and/or Service Pack(s) on the inactive Node, (after the Resource Group has completely relocated). Note: The next steps are optional; and only needed if you want to return the original Active Node to being the Active Node again. You may proceed to Step 11 if running on the current Node is OK. 9. Select S5_SQL, right click, select Relocate Resource Group, and select the available Node: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 151 of 184

Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & 10. Click Yes in the Confirm Relocate of Resource Group window: 11. Select S5_SQL, right click, and select Monitor Resource Group: 12. The Monitoring State will go to Enabled when Monitoring is on: 13. Close the EMC AutoStart Console. Installing Future SQL Server 2012 Service Packs This section describes how to install Service Packs for SQL Server 2012 that may become available after the initial AutoStart installation. The AutoStart Resource Group will need to be Offline while any Service Packs are installed. The Mirror will need to be attached to the Node the Service Pack will be installed on while the AutoStart Resource Group is Offline. This procedure assumes that the AutoStart Resource Group is running on the Node 1 (AUTOSTART1) computer. IMPORTANT: All File Server functionality will not be available while the AutoStart Resource Group is Offline. Client computers will not have connectivity to the ADC Database or be able to write to mapped drives on the File Server. Please schedule an appropriate maintenance window for this. To Install Future SQL Server 2012 Service Packs 1. Close any Client applications that communicate with the ADC Database, or that write Logs to mapped drives on the File Servers. 2. Select Start\All Programs\EMC AutoStart\EMC AutoStart Console 5.4.2 3. Expand the ADCDB Domain, expand Resource Groups, and select S5_SQL: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 152 of 184

Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & 4. Right click on S5_SQL and select Take Offline: 5. Click Yes in the Confirm Take Resource Group Offline window: 6. When the entire Resource Group is Offline it should look like this: 7. Expand Data Sources. 8. Highlight the Data Source MIRROR and right click on it. 9. Select Attach Data Source, and then autostart1: 10. Install the SQL Server 2012 Service Pack(s) on the Node 1 (AUTOSTART1) computer. 11. Highlight the Data Source MIRROR and right click on it. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 153 of 184

Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & 12. Select Detach Data Source: 13. Click Yes in the Confirm Detach of Datasource window: 14. Highlight the Data Source MIRROR and right click on it. 15. Select Attach Data Source, and then autostart2: 16. Install the SQL Server 2012 Service Pack(s) on the Node 2 (AUTOSTART2) computer. 17. Highlight the Data Source MIRROR and right click on it. 18. Select Detach Data Source: 19. Click Yes in the Confirm Detach of Datasource window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 154 of 184

Installing EMC Hot Fixes, SQL Server 2012 Service Packs, and Windows Updates & 20. Expand Resource Groups, and select S5_SQL: 21. Right click on S5_SQL and select Bring Online, and then autostart1: 22. When the entire Resource Group is Online again it should look like this: 23. Open any Client applications that were closed in Step 1 of this procedure. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 155 of 184

Backup and Restoration of an SQL Server ASDB Database Backup and Restoration of an SQL Server ASDB Database This chapter includes instructions for creating SQL Server 2005 Express and SQL Server 2008 ASDB Database Backups. It also describes how to restore an ASDB Database Backup into SQL Server 2012, including Notification Agent considerations. Creating an SQL Server 2005 Express Database Backup A backup of the current SQL Server 2005 Express Database must be created for migration into the new SQL Server 2012 Database. This section describes how to create an ASDB.bak Database backup file. Note: It is also recommended that a backup be created and saved for the AutoStart Database. Please see the Backing up and Restoring the AutoStart Database section for how to do this. Important: Only one Backup Destination directory should be configured in the Destination area of the Back Up Database - ASDB window when backing up the ASDB Database. Having multiple Destination directories configured when backing up the ASDB Database will result in partial backup files being written to each of those directories. All of those partial backup files will be needed when restoring the ASDB Database. To Create an SQL Server 2005 Express Database Backup file 1. Select Start\Programs\Microsoft SQL Server 2005\SQL Server Management Studio Express: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 156 of 184

Backup and Restoration of an SQL Server ASDB Database 2. Enter the Server name and then click Connect: 3. Expand SQL Server, expand Databases, highlight ASDB, right click, select Tasks, select Back Up : 4. In the Source area of the Back Up Database - ASDB window verify that ASDB is entered for Database, Full is entered for Backup type, and that Database is selected for the Backup component: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 157 of 184

Backup and Restoration of an SQL Server ASDB Database 5. In the Backup set area of the Back Up Database - ASDB window verify that ASDB-Full Database Backup is entered for Name, After is selected for Backup set will expire, and that 0 is entered for After: 6. In the Destination area of the Back Up Database - ASDB window click on Add, in the Select Backup Destination window click on the ellipsis, ( ), browse to and select the Destination directory for the Backup, enter ASDB.bak as the File name, and click OK: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 158 of 184

Backup and Restoration of an SQL Server ASDB Database 7. Click OK in the Select Backup Destination window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 159 of 184

Backup and Restoration of an SQL Server ASDB Database 8. Click OK in the Back Up Database - ASDB window: 9. Click OK in the Backup confirmation window: 10. Close SQL Server Management Studio Express. Creating an SQL Server 2008 ASDB Database Backup It is highly recommended that a recent usable copy of the SQL Server 2008 Database be created; with backups kept in a safe location. Note: It is also recommended that a backup be created and saved for the AutoStart Database. Please see the Backing up and Restoring the AutoStart Database section for how to do this. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 160 of 184

Backup and Restoration of an SQL Server ASDB Database Important: Only one Backup Destination directory should be configured in the Destination area of the Back Up Database - ASDB window when backing up the ASDB Database. Having multiple Destination directories configured when backing up the ASDB Database will result in partial backup files being written to each of those directories. All of those partial backup files will be needed when restoring the ASDB Database. Use the first of the two following procedures to create an SQL Server 2008 ASDB Database Backup to a custom configured destination when using the SQL Server Management Studio on the Active AutoStart Node. The second of following procedures is to be used for creating an SQL Server 2008 ASDB Database Backup to the default destination in the SQL Server Management Studio on the Active AutoStart Node. To Create an SQL Server 2008 ASDB Database Backup file to a Configured Destination 1. Select Start\All Programs\Microsoft SQL Server 2008\SQL Server Management Studio: 2. On the Connect to Server screen, click Connect: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 161 of 184

Backup and Restoration of an SQL Server ASDB Database 3. Expand SQL Server, expand Databases, highlight ASDB, select Tasks, and then select Backup: 4. In the Source area of the Back Up Database - ASDB window verify that ASDB is entered for Database, Full is entered for Backup type, and that Database is selected for the Backup component: 5. In the Backup set area of the Back Up Database - ASDB window verify that ASDB-Full Database Backup is entered for Name, After is selected for Backup set will expire, and that 0 is entered for After: 6. In the Destination area of the Back Up Database - ASDB window click on Add, in the Select Backup Destination window click on the ellipsis, ( ), browse to and select the Destination 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 162 of 184

Backup and Restoration of an SQL Server ASDB Database directory for the Backup, enter ASDB.bak as the File name, and click OK: 7. Click OK in the Select Backup Destination window: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 163 of 184

Backup and Restoration of an SQL Server ASDB Database 8. Click OK in the Back Up Database - ASDB window: 9. Click OK in the Backup confirmation window: 10. Close SQL Server Management Studio. To Create an SQL Server 2008 ASDB Database Backup file to the Default Destination 1. Select Start\All Programs\Microsoft SQL Server 2008\SQL Server Management Studio: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 164 of 184

Backup and Restoration of an SQL Server ASDB Database 2. On the Connect to Server screen, click Connect: 3. Expand SQL Server, expand Databases, highlight ASDB, select Tasks, and then select Backup: 4. In the Source area of the Back Up Database - ASDB window verify that ASDB is entered for Database, Full is entered for Backup type, and that Database is selected for the Backup component: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 165 of 184

Backup and Restoration of an SQL Server ASDB Database 5. In the Backup set area of the Back Up Database - ASDB window verify that ASDB-Full Database Backup is entered for Name, After is selected for Backup set will expire, and that 0 is entered for After: 6. Click OK in the Back Up Database - ASDB window: 7. Click OK in the Backup confirmation window: 8. The ASDB.bak backup file is located in the default location: D:\Program Files\Microsoft SQL Server\MSSQL10.MSSQLSERVER\MSSQL\Backup. 9. Close SQL Server Management Studio. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 166 of 184

Backup and Restoration of an SQL Server ASDB Database Restoring an SQL Server Database Backup into SQL Server 2012 A backup of the current SQL Server 2005, SQL Server 2008, SQL Server 2005 Express, or SQL Server 2008 Express Database is needed for migration into SQL Server 2012. See the Creating an SQL Server 2005 Express Database Backup or Creating an SQL Server 2008 Database Backup section if you do not have a current Database backup file. This section describes how to restore an ASDB.bak Database backup file into SQL Server 2012 by using the SQL Server Management Studio on the AUTOSTART1 (Node 1) computer. Note: Make sure that all Client Computers are disconnected from the File Server before performing a Database restore. To Restore a Database Backup file into SQL Server 2012 1. On the AUTOSTART1 (Node 1) computer, create a Folder on the D: Drive named DATABASE. 2. Select Start\All Programs\Microsoft SQL Server 2012\SQL Server Management Studio: 3. 4. On the Connect to Server screen, click Connect: 5. Expand the SQL Server, highlight Databases, right click, and select Restore Database : 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 167 of 184

Backup and Restoration of an SQL Server ASDB Database 6. In the Source area of the Restore Database - ASDB window select From device, and click on the ellipsis, ( ): 7. In the Select backup devices window click Add, browse to the location of the ASDB.bak Database backup file, highlight it, and click OK: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 168 of 184

Backup and Restoration of an SQL Server ASDB Database 8. Click OK in the Select backup devices window: 9. All needed fields are auto-populated: 10. Click on Files, and verify that in the Restore As area that the ASDB_dat and ASDB_log files are configured to the D:\DATABASE directory. If they are not set there by default, manually configure 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 169 of 184

Backup and Restoration of an SQL Server ASDB Database the files to this directory: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 170 of 184

Backup and Restoration of an SQL Server ASDB Database 11. Click on Options, enable (check) Overwrite the existing database (WITH REPLACE) and click OK: 12. Click OK in the confirmation window: 13. The Next Steps If this restore was done for an initial Autostart installation, continue to the next section: Upgrade Database Users and Permissions. If this restore was done on a previously installed and active Autostart system, continue with step 10 of procedure: Restoring the ASDB Database into an Active AutoStart System. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 171 of 184

Backup and Restoration of an SQL Server ASDB Database Upgrade Database Users and Permissions The SQL script Upgrade_All_ADC_SQL_2012_V1_2.sql is provided by Imagine Communications to update Users and Permissions for an SQL Server ODBC-compliant database. Use the Upgrade_All_ADC_SQL_2012_V1_2.sql script to update Users and Permissions, and modify the Database for new functionality. IMPORTANT: If Notification Agent was installed and used with this ADC System then an additional script, UpgradePermissions_NA_SQL_2012_V1_2.sql, will also need to be executed to update Notification Agent Permissions. The procedure for this is covered later in this guide, and cannot be performed before Notification Agent has been installed on both File Servers. 1. Select File\Open\File : 2. Browse to the directory containing the SQL Scripts, highlight UpgradePermissions_All_ADC_SQL_2012_V1_2.sql, and click Open: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 172 of 184

Backup and Restoration of an SQL Server ASDB Database 3. Click Execute: 4. Verify in the Messages area that the Command (s) completed successfully: 5. Close the SQL Server Management Studio. 6. Whether Notification Agent is or is not part of this upgrade go to the Creating the SQL Server 2012 Database Backup section now. About Notification Agent Note: If Notification Agent was not installed and used in the prior ADC System then you do not need to perform the operations described in the Upgrade Notification Agent Database Permissions section and can now proceed on to the Creating the SQL Server 2012 Database Backup section. IMPORTANT: If Notification Agent was used with the original ADC System, then NA should be installed now on both File Servers. Notification Agent must be installed prior to Creating Notification Agent Database Permissions. For instructions on installing Notification Agent, please the Notification Agent Installation and Operations Guide. If additional assistance is required, please contact Automation Support. Note: Use the To Install Notification Agent on Node 1 and To Install Notification Agent on Node 2 sections and the Notification Agent Installation and Operations Guide for installing Notification Agent on an AutoStart File Server Pair, and the Create the SQL Server 2012 Database Backup on Node 2 section to create a Windows Authentication Login for Node 2 before proceeding on to the Upgrade Notification Agent Database Permissions section below. Upgrade Notification Agent Database Permissions 1. The SQL script UpgradePermissions_NA_SQL_2012_V1_2.sql is provided by Imagine Communications to upgrade Notification Agent Permissions for an SQL Server ODBC-compliant database. Use the UpgradePermissions_NA_SQL_2012_V1_2.sql script to upgrade Notification Agent Permissions. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 173 of 184

Backup and Restoration of an SQL Server ASDB Database 2. On the AUTOSTART2 (Node 2) computer select File\Open\File : 3. Browse to the directory containing the SQL Scripts, highlight UpgradePermissions_NA_SQL_2012_V1_2.sql, and click Open: 4. Click Execute: 5. Verify in the Messages area that the Command (s) completed successfully: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 174 of 184

Backup and Restoration of an SQL Server ASDB Database 6. Close the SQL Server Management Studio. 7. Now that the ADC Database has been restored into SQL Server 2012, and the permissions for it and Notification Agent have been upgraded, please go to the Configuring the Notification Agent Process section. Restoring the ASDB Database into an Active AutoStart System This section describes how to restore the ASDB Database into an Active AutoStart System. This procedure assumes that the AutoStart Resource Group is running on the Node 1 (AUTOSTART1) computer. To Restore the ASDB Database into an Active AutoStart System 1. Close Notification Agent on the AUTOSTART1 computer 2. Open the EMC AutoStart Console, expand the ADCDB Domain, and expand Resource Groups. 3. Select S5_SQL, click on the Status tab, look in the Node column of the Status of Resource Group Elements area, and determine which Node is active, (autostart1 is the Active Node in this example): 4. Select S5_SQL, right click, and select Stop Monitoring: 5. The Monitoring State will go to Disabled when Monitoring is off: 6. Shut down the AUTOSTART2 computer 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 175 of 184

Backup and Restoration of an SQL Server ASDB Database 7. Expand IP Addresses and Un-assign the Automation IP: 8. Disable the Automation NIC Go to Start > Settings> Control Panel>Network and Sharing Center> Manage Network Connections Select the Automation NIC. Right click and select Disable Exit the networking dialogs. 9. Restore the ASDB Database. For details see: Restoring an SQL Server Database Backup into SQL Server 2012. 10. Enable the Automation NIC Go to Start > Settings> Control Panel>Network and Sharing Center> Manage Network Connections Select the Automation NIC. Right click and select Enable. Exit the networking dialogs. 11. Assign the Automation IP to autostart1: 12. Restart the AUTOSTART2 computer 13. Wait until the status of the Mirror and Data Sources change from Yellow back to Green. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 176 of 184

Backup and Restoration of an SQL Server ASDB Database 14. Enable Monitoring: 15. Restart Notification Agent. 16. Close each Air Client and Media Client application and launch them again. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 177 of 184

Registering an AutoStart license with EMC Registering an AutoStart license with EMC Activating / Registering Your Software Once AutoStart is fully installed new users must register their license with EMC in order to be eligible for software support for this product. 1. Log into Powerlink at http://powerlink.emc.com (New users follow the new member registration steps) 2. Navigate to Support > Software Downloads and Licensing > License Management and click on the product you wish to activate. 3. Enter your assigned License Authorization Code (LAC) via the Quick Keys Menu or Activation menu. 4. Click the Activate button and follow the steps to obtain your license key(s). 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 178 of 184

Enabling.NET v3.5 Enabling.NET v3.5.net v3.5 must be enabled before installing SQL Server 2012 Express. Follow this procedure to enable.net v3.5. To Enable.NET v3.5 1. Select Start\Administrative Tools\Server Manager: 2. Click on Features: 3. Click on Add Features in the Features Summary area of the Server Manager: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 179 of 184

Enabling.NET v3.5 4. Expand.NET Framework 3.5.1 Features, Enable, (check),.net Framework 3.5.1, and click Next: 5. Click Install in the Confirm Installation Selections screen: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 180 of 184

Enabling.NET v3.5 6. Click Close in the Installation Results screen: 7. Close the Server Manager. 8. Click on this link to return to the Installing SQL Server 2012 section. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 181 of 184

Editing the SQL Server 2012 Database Backup Schedule Editing the SQL Server 2012 Database Backup Schedule Now that the Database Backup has been created, it can be edited to change the time and frequency of the Database Backups. The following steps describe hot to edit the Backup Schedule. To Edit the Database Backup Schedule 1. Select Start\Programs\Microsoft SQL Server 2012\SQL Server Management Studio: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 182 of 184

Editing the SQL Server 2012 Database Backup Schedule 2. Expand SQL Server Agent, expand Jobs, highlight BACKUP Full, right click, and select Properties: 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 183 of 184

Editing the SQL Server 2012 Database Backup Schedule 3. Select Schedules, and click Edit: 4. Changes to the time and frequency of the Database Backups can be made in these areas: 5. After any changes, click OK in the Job Schedule Properties dialog, and then click OK in the Job Properties dialog. 6. Close the SQL Server Management Studio. 2014 Imagine Communications Corp. Proprietary and Confidential 27-March-2014 Page 184 of 184