jump to navigation

The log shipping primary database INSNAME\DBNAME has backup threshold of 60 minutes and has not performed a backup log operation for 60459 minutes. Check agent log and logshipping monitor information. July 13, 2010

Posted by juanpablo1manrique in Alto Desempeño, Best Practices, Cluster, SQL SERVER, SQL SERVER 2008.
Tags:
add a comment

Realizando estrategias de Logshipping sobre las bases de datos se registró el siguiente error sobre el log de eventos,

The log shipping primary database INSNAME\DBNAME has backup threshold of 60 minutes and has not performed a backup log operation for 60459 minutes. Check agent log and logshipping monitor information.

La base de datos en cuestión yo la borre a mano, así que se perdió y el Job se siguió ejecutando a una base de datos que no existe. Una manera que encontré para solucionar este problema es acceder a las tablas de sistema y eliminar el registro.

La tabla a borrar es,

select * from msdb.dbo.log_shipping_monitor_primary

Asegúrese de borrar solo los registros correctos o eliminara toda la configuración de logshipping de su servidor.

Lo correcto es que antes de borrar la base de datos se elimine la configuración de logshipping

Saludos

Advertisements

SharePoint can’t replicated the WEB Applications in different servers March 11, 2010

Posted by juanpablo1manrique in Alta Disponibilidad, Alto Desempeño, Best Practices, Cluster, IIS 7.0, Install, NLB.
add a comment

Well, in this days I found that after installing the nodes of SharePoint farm, I see that the WEB Applications are not replicated in different servers. Whereupon I am saying that if SharePoint is installed properly and the NLB is configured correctly, sharepoint administrator enginier can create WebApplications from CentralAdministrator and forget completely if It properly replicated on all servers. This marvel that is achieved through a service called Application Server SharePoint Timer Job Administration Service which may be found in the operations tab and then Timer Job Definitions. This marvel of service runs with administrative permissions, then is mandatory that the Windows SharePoint Services run with a user with administrative permissions on all machines. Having said that an important tip before installing the nodes in each server is that when you install SharePoint the installation is logged with the account you are running SharePoint services “domain \ SHPservice” if this does not happen and is not replicated sites can do the following. Uninstall SharePoint Server, control panel and then go to add and remove programs and uninstall and reinstall in ideal conditions mentioned above, and is supplied again. :: All programs and runs the wizard of SharePoint Products and Technologies Configuration Wizard. It runs all again and verifies that the service Application Server Administration Service Timer Job has run successfully if it does not work you have problems. But letrasandnumeros’ve is the right place to fix it. The first thing you do is update the registry permissions that need to access SharePoint. This is done using the psconfig found in% COMMONPROGRAMFILES% \ Microsoft Shared \ web server extensions \ 12 \ bin “is a very good option because he does everything himself. psconfig-cmd secureresources After this you need to run some commands that allow you to modify permissions sharepoint services, using the stdadm (% CommonProgramFiles% \ Microsoft Shared \ web server extensions \ 12 \ bin) which are: stsadm-o-userlogin updatefarmcredentials-password ****** ***** iisreset% This is necessary before continue stsadm-o-userlogin updateaccountpassword-password ******** ********-noadmin stsadm.exe-o-farmserviceaccount spsearch-farmservicepassword ******** ******** stsadm.exe-o-farmcontentaccessaccount spsearch-farmcontentaccesspassword ******** ******** stsadm.exe-o editssp-title ‘[ShareServiceProviderName]’-ssplogin-ssppassword ******** ******** stsadm.exe-o-farmserviceaccount OSearch-farmservicepassword ******** ******** And again iisreset The previous command lines you can to use to build a. Bat or. Cmd file and maybe use the day that the Enterprise domain administrator change the password to the service user. I hope they will be helpful Greetings

SharePoint no replica los cambios entre los servidores de la granja March 11, 2010

Posted by juanpablo1manrique in Alta Disponibilidad, Alto Desempeño, Best Practices, Cluster, Developer, IIS 7.0, Install, NLB, SharePoint.
1 comment so far

Bueno hace días me encontré con que después de instalar los nodos de mi granja de servidores, veo que al crear los WEBSites aplication estos no son replicados en los diferentes servers. Con lo cual estoy diciendo que si SharePoint está bien instalado y el NLB está correctamente configurado, el administrador de sharepoint puede crear WEBApplications desde el CentralAdministrator y olvidarse completamente si se replican correctamente en todos los servidores.

Esta maravilla se logra gracias a que uno de los servicios de SharePoint llamado Application Server Administration Service Timer Job el cual podrán encontrar en el tab operations y luego en Timer Job Definitions. Esta maravilla de servicio corre con permisos de administración, entonces de manera obligatoria es necesario que los servicios de Windows SharePoint se ejecuten con un usuario que tenga permisos de administración sobre todas las máquinas.

Dicho lo anterior un consejo importante antes de instalar los nodos en cada servidor es que en el momento de instalar SharePoint el ingeniero que realiza la instalación se encuentre logeado con la cuenta con la que van a correr los servicios de SharePoint “domain\SHPservice”  si esto no sucede y no se le replican los sitios puede realizar lo siguiente.

Desinstale SharePoint Server, panel de control y luego en agregar y quitar y programas se desinstala y se vuelve a instalar en las condiciones ideales mencionadas anteriormente, y se aprovisiona de nuevo.  :: Todos los programas y se ejecuta el asistente de SharePoint Products And Technologies configuration wizard. Se corre todo de nuevo y se verifica que el servicio de Application Server Administration Service Timer Job  haya corrido correctamente si esto no sucede tenemos problemas. Pero en letrasandnumeros has dado con el lugar correcto para solucionarlo.

Lo primero que se hace es actualizar los permisos del registro de windows que SharePoint necesita acceso. Esto se logra utilizando el psconfig que se encuentra en %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\12\bin y es una nota porque lo hace todo él solo.

psconfig -cmd secureresources

Luego de esto es necesario ejecutar algunos comandos que permiten modificar los permisos de los servicios de sharepoint, utilizando el stdadm  (%commonprogramfiles%\Microsoft Shared\Web server extensions\12\Bin) los cuales son:

stsadm -o updatefarmcredentials -userlogin ****** -password *****
iisreset %Este es necesario antes de continuar
stsadm -o updateaccountpassword -userlogin ******** -password ******** -noadmin
stsadm.exe -o spsearch -farmserviceaccount ********  -farmservicepassword ********
stsadm.exe -o spsearch -farmcontentaccessaccount ******** -farmcontentaccesspassword ********
stsadm.exe -o editssp -title ‘[ShareServiceProviderName]’ -ssplogin ******** -ssppassword ********
stsadm.exe -o osearch -farmserviceaccount ******** -farmservicepassword ********

Y nuevamente nuestro amigo
iisreset

Las líneas de comandos anteriores les puede servir para construir un .bat o .cmd y utilizarlo el día que al señor administrador del dominio le dé porque es necesario cambiarle el password al usuario de servicio.

Espero que les sea de ayuda

Saludos

Versión en Ingles

SharePoint can’t replicated the WEB Applications in different servers  

problems installing SQL 2008 in WINDOWS 2008 in cluster February 24, 2010

Posted by juanpablo1manrique in Alta Disponibilidad, Cluster, IT, SQL SERVER 2008, Windows 2008.
1 comment so far

Hello Friends

I have problems installing SQL 2008 in WINDOWS 2008 in cluster, the installation start but not finish.

I see de log …

Detailed results:
Feature: Database Engine Services
Status: Failed: see logs for details
MSI status: Passed
Configuration status: Failed: see details below
Configuration error code: 0x4BDAF9BA@1306@23
Configuration error description: Could not find the Database Engine startup handle.
Configuration log: C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20100119_121017\Detail.txt
And in detail you can see.

Error: Action “ConfigEvent_SQL_FullText_Adv_sql_fulltext_Cpu64_CompleteFailoverCluster_ConfigRC_postmsi” failed during execution.
2010-01-19 13:42:59 Slp: Action “ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_CompleteFailoverCluster_Startup_postmsi” will return false due to the following conditions:
2010-01-19 13:42:59 Slp: Condition “Feature dependency condition for action: ConfigEvent_SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64_CompleteFailoverCluster_Startup_postmsi The condition tests feature: SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64. There are 10 dependant features. The feature is tested for results: ValidateResult, Result.” did not pass as it returned false and true was expected.
2010-01-19 13:42:59 Slp: Condition is false because the required feature SQL_Engine_Core_Inst_sql_engine_core_inst_Cpu64 failed in result Result

The solution was unable de recicly bin

– Right click on the “Recycle Bin” icon. A window will open
– Click on the “Do not move files to the Recycle Bin. Remove files immediately when deleted” copy from (http://www.sqlservercentral.com/articles/Clustering/68967/)

Manual Install of sharePoint with NLB Windows 2008 February 21, 2010

Posted by juanpablo1manrique in Best Practices, Cluster, Developer, Install, IT, Manual, NLB, SharePoint, Windows 2008.
1 comment so far

For my followers, I publish this excelent manual to Install Microsoft SharePoint Server 2007, the subject than you can find here.

1. Install Share Point Process
2. Configuration Process of Share Point
3. Install NLB Windows server 2008
4. Install Second Node of SharePoint
5. Administration of MOSS 

Happy coding

Best reguards

Version en Español

Installing a SQL Server 2008 Failover Cluster Using Advanced/Enterprise Installation February 21, 2010

Posted by juanpablo1manrique in Alta Disponibilidad, Alto Desempeño, Cluster, SQL SERVER.
add a comment

Advanced/Enterprise Failover Cluster Install Step 1: Prepare

If you want see this post whit images of the instalatión you can do, download the manual of enterprise cluster here.

  1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, browse to the root folder on the share, and then double-click Setup.exe. For more information about how to install prerequisites, see Before Installing Failover Clustering (http://msdn.microsoft.com/en-us/library/ms189910.aspx). You may be asked to install the prerequisites, if they are not previously installed.

 

Install Windows Installer 4.5. Windows Installer 4.5 is required, and it can be installed by the Installation Wizard. If you are prompted to restart your computer, restart it, and then start SQL Server 2008 Setup again.

  1. After the prerequisites are installed, the Installation Wizard starts the SQL Server Installation Center. To prepare the node for clustering, move to the Advanced page and then click Advanced cluster preparation.

 

  1. The System Configuration Checker runs a discovery operation on your computer. To continue, click OK. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. On the Setup Support Files page, click Install to install the setup support files.

 

  1. The System Configuration Checker verifies the system state of your computer before Setup continues. After the check is complete, click Next to continue. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. On the Product Key page, indicate whether you are installing a free edition of SQL Server or you have a PID key for a production version of the product.

Note: The Product Key and License Terms pages show up after the Setup Support Files page if you already installed the setup support files during a previous installation.

Note: You must specify the same product key on all the nodes that you are preparing for the same failover cluster. 

  1. On the License Terms page, read the license agreement, and then select the check box to accept the license terms and conditions.

 

Click Next to continue. To end Setup, click Cancel.

  1. On the Feature Selection page, select the components for your installation.

 

A description for each component group appears in the right pane after you select the feature name. You can select any combination of check boxes, but only the Database Engine and Analysis Services support failover clustering. Other components will run on a single failover cluster node as a stand-alone feature without failover capability.

You can specify a custom directory for shared components by using the field at the bottom of this page. To change the installation path for shared components, either update the path in the field provided at the bottom of the dialog box, or click the ellipsis button to browse to an installation directory. The default installation path is C:\Program Files\Microsoft SQL Server\.

Note: When you select the Database Engine Services feature, both replication and full-text search are selected automatically. Unselecting any of these subfeatures also unselects the Database Engine Services feature.

  1. On the Instance Configuration page, specify whether to install a default or a named instance.

 

Instance ID — By default, the instance name is used as the Instance ID. This is used to identify installation directories and registry keys for your instance of SQL Server. This is the case for default instances and named instances. For a default instance, the instance name and instance ID would be MSSQLSERVER. To use a non-default instance ID, select the Instance ID text box and provide a value.

Note: Typical stand-alone instances of SQL Server 2008, whether default or named instances, do not use a non-default value for the Instance ID text box.

Important: Use the same InstanceID for all the nodes that are prepared for the failover cluster.

Instance root directory — By default, the instance root directory is C:\Program Files\Microsoft SQL Server\. To specify a nondefault root directory, use the field provided, or click the ellipsis button to locate an installation folder.

Installed instances – The box shows instances of SQL Server that are on the computer where setup is running. If a default instance is already installed on the computer, you must install a named instance of SQL Server 2008. Click Next to continue.

  1. The Disk Space Requirements page calculates the required disk space for the features that you specify, and it compares requirements to the available disk space on the computer where Setup is running.

 

  1. Specify the security policy for the cluster.

The following screenshot displays the cluster security policies for Windows Server 2003. In Windows Server 2003, you cannot leverage service SIDs. Specify domain groups for SQL Server services. All resource permissions are controlled by domain-level groups that include SQL Server service accounts as group members. This is displayed in the following screen shot.

The following screenshot displays the cluster security policies available for Windows Server 2008. In Windows Server 2008 and later versions, service SIDs (server security IDs) are the recommended and default setting. The option to specify domain groups is available but not recommended. For information about service SIDs functionality on Windows Server 2008, see Setting Up Windows Service Accounts (http://msdn.microsoft.com/en-us/library/ms143504.aspx). This is displayed in the following screen shot.

Click Next to continue.

Note: If you are installing a SQL Server 2008 failover cluster instance in a Windows 2000 Server mixed-mode domain, you must use domain global groups for SQL Server Clustered Services.

Note: Windows 2000 Server domain controllers can operate in mixed mode and native mode. Mixed mode enables down-level domain controllers in the same domain.

Work flow for the rest of this procedure depends on the features that you have specified for your installation. You might not see all the pages, depending on your selections.

  1. On the Server Configuration page, on the Service Accounts tab, specify login accounts for SQL Server services. The actual services that are configured on this page depend on the features that you selected to install.

 

You can assign the same login account to all SQL Server services, or you can configure each service account individually. The startup type is set to manual for all cluster-aware services, including full-text search and SQL Server Agent, and cannot be changed during installation. Microsoft recommends that you configure service accounts individually to provide least privileges for each service, where SQL Server services are granted the minimum permissions they have to have complete their tasks. For more information, see SQL Server Configuration – Service Accounts (http://technet.microsoft.com/en-us/library/cc281723.aspx) and Setting Up Windows Service Accounts (http://technet.microsoft.com/en-us/library/ms143504.aspx).

To specify the same login account for all service accounts in this instance of SQL Server, provide credentials in the fields at the bottom of the page.

Security note: Do not use a blank password. Use a strong password.

When you are finished specifying login information for SQL Server services, click Next.

  1. Use the Collation tab to specify nondefault collations for the Database Engine and Analysis Services.

 

  1. Use the FILESTREAM tab to enable FILESTREAM for your instance of SQL Server. Click Next to continue.

 

  1. Use the Reporting Services Configuration page to specify the kind of Reporting Services installation to create. For failover cluster installation, the option is set to “Install, but do not configure the report server.” You must configure Reporting Services after you complete the installation.

 

  1. On the Error and Usage Reporting page, specify the information that you want to send to Microsoft that will help improve SQL Server. By default, options for error reporting and feature usage are enabled.

 

  1. The System Configuration Checker runs one more set of rules to validate your configuration with the SQL Server features that you have specified.

 

  1. The Ready to Install page displays a tree view of installation options that you specified during setup. To continue, click Install.

 

  1. During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.

 

  1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes.

 

  1. To complete the SQL Server installation process, click Close.
  2. If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you have finished with setup. For information about setup log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).
  3. Repeat the previous steps to prepare the other nodes for the failover cluster. You can also use the autogenerated configuration file to run prepare on the other nodes. For more information, see How to: Install SQL Server 2008 Using a Configuration File (http://msdn.microsoft.com/en-us/library/dd239405.aspx).
  4. After preparing all the nodes as described in step 1, run Setup on one of the prepared nodes, preferably the one that owns the shared disk. On the Advanced page of the SQL Server Installation Center, click Advanced cluster completion.

Advanced/Enterprise Failover Cluster Installation Step 2: Complete

 

  1. The System Configuration Checker runs a discovery operation on your computer. To continue, click OK. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. On the Setup Support Files page, click Install to install the setup support files.

 

  1. The System Configuration Checker verifies the system state of your computer before setup continues. After the check is complete, click Next to continue. You can view the details on the screen by clicking Show Details, or as an HTML report by clicking View detailed report.

 

  1. Use the Cluster Node Configuration page to select the instance name prepared for clustering, and specify the network name for the new SQL Server failover cluster. This is the name that is used to identify your failover cluster on the network.

 

Note: This is known as the virtual SQL Server name in earlier versions of SQL Server failover clusters. 

  1. Use the Cluster Resource Group page to specify the cluster resource group name where SQL Server virtual server resources will be located. To specify the SQL Server cluster resource group name. You have two options:
  • Use the list to specify an existing group to use.
  • Type the name of a new group to create.

 

  1. On the Cluster Disk Selection page, select the shared cluster disk resource for your SQL Server failover cluster. The cluster disk is where the SQL Server data will be put. More than one disk can be specified. Available shared disks displays a list of available disks, whether each is qualified as a shared disk, and a description of each disk resource. Click Next to continue.

 

Note: The first drive is used as the default drive for all databases, but can be changed on the Database Engine or Analysis Services configuration pages. 

  1. On the Cluster Network Selection page, specify the network resources for your failover cluster instance:
  • Network settings — Specify the IP type and IP address for your failover cluster instance. On Windows Server 2008 failover clusters, SQL Server supports the use of DHCP addresses. Before choosing this option, make sure that any network security such as firewalls and IPsec in use between this SQL Server and its clients can accommodate server-side DHCP. For example, some firewalls will require a static port for proper configuration of the firewall.

 

Click Next to continue.

Work flow for the rest of this procedure depends on the features that you have specified for your installation. You might not see all the pages, depending on your selections.

  1. On the Database Engine Configuration page, use the Account Provisioning tab to specify the following:
  1.  
  1.  
    • SQL Server administrators – you must specify at least one system administrator for the instance of SQL Server. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for the instance of SQL Server. For more information, see Database Engine Configuration – Account Provisioning (http://technet.microsoft.com/en-us/library/cc281849.aspx).

 

When you are finished editing the list, click OK. Verify the list of administrators in the configuration dialog box. When the list is complete, click Next.

  1. Use the Data Directories tab to specify nondefault installation directories. To install to default directories, click Next.

 

Important: If you specify nondefault installation directories, make sure that the installation folders are unique to this instance of SQL Server. None of the directories in this tab should be shared with directories from other instances of SQL Server. The data directories should be located on the shared cluster disk for the failover cluster. 

  1. Use the Account Provisioning tab to specify users or accounts that will have administrator permissions for Analysis Services. You must specify at least one system administrator for Analysis Services. To add the account under which SQL Server Setup is running, click Add Current User. To add or remove accounts from the list of system administrators, click Add or Remove, and then edit the list of users, groups, or computers that will have administrator privileges for Analysis Services. For more information, see Analysis Services Configuration – Account Provisioning (http://technet.microsoft.com/en-us/library/cc281723.aspx).

 

When you are finished editing the list, click OK. Verify the list of administrators in the configuration dialog box. When the list is complete, click Next.

  1. Use the Data Directories tab to specify nondefault installation directories. To install to default directories, click Next.

 

Important: If you specify nondefault installation directories, make sure that the installation folders are unique to this instance of SQL Server. None of the directories in this tab should be shared with directories from other instances of SQL Server. The data directories should be located on the shared cluster disk for the failover cluster.

  1. The System Configuration Checker runs one more set of rules to validate your configuration with the SQL Server features that you have specified.

 

  1. The Ready to Install page displays a tree view of installation options that you specified during setup. To continue, click Install.

 

  1. During installation, the Installation Progress page provides status so that you can monitor installation progress as Setup continues.

 

  1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.

 

With this step, all the prepared nodes for the same failover cluster are now part of the completed SQL Server failover cluster.

Appendix C: Add Node

Use this procedure to manage nodes for an existing SQL Server failover cluster instance.

Important: To update or remove a SQL Server failover cluster, you must be a local administrator with permission to log in as a service on all nodes of the failover cluster. For local installations, you must run Setup as an administrator. If you install SQL Server from a remote share, you must use a domain account that has read and execute permissions on the remote share.

Setup does not install .NET Framework 3.5 SP1 on a clustered operating system. You must install .NET Framework 3.5 SP1 before you run Setup.

You may need to apply cumulative updates to the original media before you install SQL Server 2008, if you are affected by a known issue in the Setup program. For more information about known issues and detailed instructions, see How to update or slipstream an installation SQL Server 2008 (http://support.microsoft.com/kb/955392).

Note that setup operations for SQL Server failover clustering have changed in this release. To install or upgrade a SQL Server failover cluster, you must run the Setup program on each node of the failover cluster.

To add a node to an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be added to the SQL Server failover cluster instance. Do not run Setup on the active node.

To remove a node from an existing SQL Server failover cluster, you must run SQL Server Setup on the node that is to be removed from the SQL Server failover cluster instance.

To Add a Node to an Existing SQL Server 2008 Failover Cluster

  1. Insert the SQL Server installation media, and from the root folder, double-click Setup.exe. To install from a network share, navigate to the root folder on the share, and then double-click Setup.exe. You may be asked to install the prerequisites if they are not previously installed.

 

Install Windows Installer 4.5. Windows Installer 4.5 is required, and it can be installed by the Installation Wizard. If you are prompted to restart your computer, restart, and then start SQL Server 2008 Setup.exe again.

  1. When prerequisites are installed, the Installation Wizard will launch the SQL Server Installation Center. To add a node to an existing failover cluster instance, click Installation in the left-hand pane. Then, click Add node to a SQL Server failover cluster.

 

The System Configuration Checker will run a discovery operation on your computer. To continue, click OK. Setup log files have been created for your installation. For more information about log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

  1. On the Product Key page, specify the PID key for a production version of the product. Note that the product key you enter for this installation must be for the same SQL Server 2008 edition as that which is installed on the active node.

Note: The Product Key and License Terms pages show up after the setup support files page if you already installed the setup support files during a previous installation.

  1. On the License Terms page, read the license agreement, and then select the check box to accept the licensing terms and conditions. To continue, click Next. To end Setup, click Cancel.

 

  1. On the Setup Support Files page, click Install to install the setup support files. To install prerequisites, click Install.

 

  1. The System Configuration Checker will verify the system state of your computer before Setup continues. After the check is complete, click Next to continue.

 

  1. On the Cluster Node Configuration page, use the SQL Server instance name box to specify the name of the SQL Server 2008 failover cluster instance that will be modified during this setup operation.

 

  1. On the Service Accounts page, specify login accounts for SQL Server services. The actual services that are configured on this page depend on the features you selected to install. For failover cluster installations, account name and startup type information will be prepopulated on this page based on settings provided for the active node. You must provide passwords for each account.

 

Security note: Do not use a blank password. Use a strong password.

When you are finished specifying login information for SQL Server services, click Next.

  1. On the Error and Usage Reporting page, specify the information to send to Microsoft that will help to improve SQL Server. By default, options for error reporting and feature usage are enabled.

 

  1. The System Configuration Checker will run one more set of rules to validate your computer configuration with the SQL Server features you have specified.

 

  1. The Ready to Add Node page displays a tree view of installation options that you specified during setup.

 

  1. The Add Node Progress page provides status so you can monitor add node progress as Setup proceeds.

 

  1. After installation, the Complete page provides a link to the summary log file for the installation and other important notes. To complete the SQL Server installation process, click Close.

 

  1. If you are instructed to restart the computer, do so now. It is important to read the message from the Installation Wizard when you are done with setup. For more information about setup log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

 

Appendix D: Removing a Node

Removing a node makes that node unavailable to the specific instance of SQL Server the RemoveNode action was run against. If you must remove a node that is currently hosting your instance of SQL Server, note that your SQL instance will fail over to another node of the cluster. As a best practice, you should remove nodes that are not running the active SQL Server instance, to avoid this failover scenario. If the node to be removed is currently running the SQL Server failover cluster instance that RemoveNode is executed on, consider moving the group to a node that will not be removed from the cluster during a maintenance window. This can help maintain the maximum uptime and avoid unplanned failovers.

Note: Instances that did not have the RemoveNode part of setup run against them will not be affected by the operation.

To Remove a Node from an Existing SQL Server 2008 Failover Cluster

  1. Insert the SQL Server installation media. From the root folder, double-click Setup.exe. To install from a network share, navigate to the root folder on the share, and then double-click Setup.exe. The Installation Wizard will launch the SQL Server Installation Center. To remove a node from an existing failover cluster instance, click Maintenance in the left-hand pane, and then click Remove node from a SQL Server failover cluster.

 

  1. The System Configuration Checker will run a discovery operation on your computer. To continue, click OK. Setup log files have been created for your installation. For more information about log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).

 

  1. The System Configuration Checker will verify the system state of your computer before setup continues. After the check is complete, click Next to continue.

 

  1. On the Cluster Node Configuration page, use the drop-down box to specify the name of the SQL Server 2008 failover cluster instance that will be modified during this setup operation. The node that will be removed will be listed in Name of this node.

 

  1. The Ready to Remove page displays a tree view of options that will be removed during setup. To continue, click Remove.

 

  1. During the remove operation, the Remove Node Progress page provides status.

 

  1. The Complete page provides a link to the summary log file for remove node and other important notes. To complete the SQL Server remove node, click Close. For more information about setup log files, see How To: View SQL Server Setup Log Files (http://msdn.microsoft.com/en-us/library/ms143702.aspx).