Administration, SharePoint

Deploying Remote BLOB Storage with SQL Server 2012 AlwaysOn Availability Groups

AlwaysOn Availability Groups can provide a high-availability and disaster recovery solution for SQL Server Remote Blob Store (RBS) BLOB objects (blobs).  AlwaysOn Availability Groups protects any RBS metadata and schemas stored in an availability database by replicating them to the secondary replicas.

AlwaysOn Availability Groups Overview

The AlwaysOn Availability Groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level alternative to database mirroring. Introduced in SQL Server 2012, AlwaysOn Availability Groups maximizes the availability of a set of user databases for an enterprise. An availability group supports a failover environment for a discrete set of user databases, known as availability databases, that fail over together. An availability group supports a set of read-write primary databases and one to four sets of corresponding secondary databases. Optionally, secondary databases can be made available for read-only access and/or some backup operations.

An availability group fails over at the level of an availability replica. Failovers are not caused by database issues such as a database becoming suspect due to a loss of a data file, deletion of a database, or corruption of a transaction log.

See also AlwaysOn Availability Groups (SQL Server).

Remote BLOB Store Overview

SQL Server Remote BLOB Store (RBS) is an optional add-on component that lets database administrators store binary large objects in commodity storage solutions instead of directly on the main database server.

Unstructured Data

Unstructured data refers to information that does not adhere to a defined model or does not fit well into relational tables in SharePoint unstructured data can refer to Microsoft Office document file formats, video, audio, and related file types.

Structured Data

Structured data in SharePoint refers to the metadata associated with its corresponding unstructured data or BLOB.  Relational databases are most often cited as examples of structured data.

SQL Server and Unstructured Data Storage

There are three (3) approaches to storing unstructured data with SQL Server, RBS, SQL BLOB, and FILESTREAM:

  • Remote BLOB Storage (RBS) in which SharePoint relies on a new layer in SQL Server to read or update BLOB data stored outside of the database on separate BLOB Stores (file system or dedicated BLOB stores)
  • SQL BLOB which refers to traditional BLOB storage with SharePoint, BLOB data is stored along side the structured metadata in the Content Database
  • FILESTREAM

See also Remote BLOB Store.

FILESTREAM Overview

FILESTREAM is implemented on the varbinary(max) datatype instructing the database engine to store unstructured data on the file system through a FILESTREAM filegroup that contains file system directories instead of the files themselves also known as data containers.  Data containers are the interface between database engine storage and file system storage.  varbinary is the binary data type designation for binary large objects stored in SharePoint 2010 content databases and refers to variable-length binary data. (MAX) refers to a value that max indicates that the maximum storage size is 2^31-1 bytes or otherwise 2GB.  Remote BLOB Storage does not provide a mechanism to exceed to the 2GB file size limit imposed by SharePoint.

In SharePoint 2013 remote BLOB data is referenced by a unique identifier in content databases configured for RBS (see illustration).

Drawing1

FILESTREAM offers several benefits as related to performance 1) FILESTREAM uses the NT system cache for caching file data reducing the effect that FILESTREAM data has on Database Engine performance and 2) the SQL Server buffer pool is not used; therefore, memory is available for query processing.

FILESTREAM provides optimum value in scenarios where SharePoint is used to storage large BLOB data such as video files that will benefit from FILESTREAM or BLOB data that exceeds 1MB.

High Availability Considerations

AlwaysOn Availability Group Protection

The protection for RBS BLOB data depends on the BLOB Store Location:

BLOB Store Location Protected
same database that contains the RBS metadata Yes
Another database in the same instance of SQL Server Yes
Another database in a different instance of SQL Server Yes
third-party BLOB store To protect this BLOB data, use the high-availability mechanisms of the BLOB store provider.

Database Mirroring Protection

Database mirroring does not support FILESTREAM since a FILESTREAM filegroup cannot be created on the principal server and database mirroring cannot be configured for a database that contains FILESTREAM filegroups. If the FILESTREAM provider is used to store BLOB data locally (within the same content database) the database cannot be configured for database mirroring.

If the FILESTREAM provider is configured to store the BLOB data within a separate SQL database or when using a 3rd party BLOB store, the content database can be mirroring; however, database mirroring will apply only to the content database and not the BLOB data. The BLOB data needs to be handled separately and kept in sync with the associated metadata (content database). For FILESTREAM BLOB databases, this can be done through log shipping.

To learn about the differences between FILESTREAM and SQL Server Remote BLOB Store see also http://blogs.msdn.com/b/sqlrbs/archive/2009/11/18/sql-server-remote-blob-store-and-filestream-feature-comparison.aspx.

Step 1 Failover Availability Group(s) to the Secondary Replica

  1. On the Start menu, point to All Programs, point to Microsoft SQL Server 2012, and then click SQL Server Management Studio.
  2. On the Connect to Server dialog, enter the name of the Availability Group Listener and click Connect.
  3. In SQL Server Management Studio, expand AlwaysOn High Availability, and then expand Availability Groups.
  4. Right-click the desired Availability Group and select Failover… from the list of available options.
  5. On the Failover Availability Group: <Availability Group> dialog click Next >.
  6. On the Failover Availability Group: <Availability Group> dialog select or accept the Secondary Replica and click Next >.
  7. On the Failover Availability Group: <Availability Group> dialog click Connect… to connect to the Secondary Replica and click Next >.
  8. On the Failover Availability Group: <Availability Group> dialog click Finish to initiate manual failover of the Availability Group.

See also Planned Manual Failover (Without Data Loss) [http://msdn.microsoft.com/en-us/library/hh213151.aspx#ManualFailover] under Failover and Failover Modes (AlwaysOn Availability Groups).

Step 1.1 Enable FILESTREAM on the Primary Replica

  1. On the Start menu, point to All Programs, point to Microsoft SQL Server 2012, point to Configuration Tools, and then click SQL Server Configuration Manager.
  2. In the list of services, right-click SQL Server Services, and then click Open.
  3. In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
  4. Right-click the instance and then click Properties.
  5. In the SQL Server Properties dialog box, click the FILESTREAM tab.
  6. Select the Enable FILESTREAM for Transact-SQL access check box.
  7. If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
  8. If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.
  9. Click Apply.
  10. In SQL Server Management Studio, click New Query to display the Query Editor.
  11. In Query Editor, enter the following Transact-SQL code:

EXEC sp_configure filestream_access_level, 2

In Query Editor, enter the following Transact-SQL code:

RECONFIGURE

Step 2 Failover the Availability Group(s) to the Primary Replica

  1. On the Start menu, point to All Programs, point to Microsoft SQL Server 2012, and then click SQL Server Management Studio.
  2. On the Connect to Server dialog, enter the name of the Availability Group Listener and click Connect.
  3. In SQL Server Management Studio, expand AlwaysOn High Availability, and then expand Availability Groups.
  4. Right-click the desired Availability Group and select Failover… from the list of available options.
  5. On the Failover Availability Group: <Availability Group> dialog click Next >.
  6. On the Failover Availability Group: <Availability Group> dialog select or accept the Secondary Replica and click Next >.
  7. On the Failover Availability Group: <Availability Group> dialog click Connect… to connect to the Secondary Replica and click Next >.
  8. On the Failover Availability Group: <Availability Group> dialog click Finish to initiate manual failover of the Availability Group.

See also Planned Manual Failover (Without Data Loss) [http://msdn.microsoft.com/en-us/library/hh213151.aspx#ManualFailover] under Failover and Failover Modes (AlwaysOn Availability Groups).

Step 2.1 Enable FILESTREAM on the Secondary Replica

  1. On the Start menu, point to All Programs, point to Microsoft SQL Server 2012, point to Configuration Tools, and then click SQL Server Configuration Manager.
  2. In the list of services, right-click SQL Server Services, and then click Open.
  3. In the SQL Server Configuration Manager snap-in, locate the instance of SQL Server on which you want to enable FILESTREAM.
  4. Right-click the instance and then click Properties.
  5. In the SQL Server Properties dialog box, click the FILESTREAM tab.
  6. Select the Enable FILESTREAM for Transact-SQL access check box.
  7. If you want to read and write FILESTREAM data from Windows, click Enable FILESTREAM for file I/O streaming access. Enter the name of the Windows share in the Windows Share Name box.
  8. If remote clients must access the FILESTREAM data that is stored on this share, select Allow remote clients to have streaming access to FILESTREAM data.
  9. Click Apply.
  10. In SQL Server Management Studio, click New Query to display the Query Editor.
  11. In Query Editor, enter the following Transact-SQL code:

EXEC sp_configure filestream_access_level, 2

In Query Editor, enter the following Transact-SQL code:

RECONFIGURE

Step 3 Provision the RBS Data Store

      

  1. Click Start, click All Programs, click Microsoft SQL Server 2012, and then click SQL Server Management Studio.
  2. On the Connect to Server dialog, enter the name of the Availability Group Listener and click Connect.
  3. Expand Databases.
  4. Select the content database for which you want to create a BLOB store, and then click New Query.
  5. In SQL Server Management Studio, click New Query to display the Query Editor.
  6. In Query Editor, enter the following Transact-SQL code:

USE [Database Name]

IF not exists (SELECT * FROM sys.symmetric_keys WHERE name = N’##MS_DatabaseMasterKey##’)create master key encryption by password = N’Admin Key Password !2#4′

In Query Editor, enter the following Transact-SQL code:

USE [Database Name]

IF not exists (SELECT groupname FROM sysfilegroups WHERE groupname=N’RBSFilestreamProvider’)alter database [Database Name] add filegroup RBSFilestreamProvider contains filestream

In Query Editor, enter the following Transact-SQL code:

USE [Database Name]

alter database [Database Name] add file (name = RBSFilestreamFile, filename = ‘c:BlobStore’) to filegroup RBSFilestreamProvider

NOTE

The Blob Store directory will be provisioned on both the Primary and Secondary Replicas.

Step 4 Install the Microsoft SQL Server 2008 R2 Remote Blob Store

Download the x64 package for the Microsoft SQL Server 2012 Remote Blob Store from http://www.microsoft.com/downloads/en/details.aspx?FamilyID=ceb4346f-657f-4d28-83f5-aae0c5c83d52&displaylang=en.

Open a Command Prompt with Administrator permissions and execute the following command to install RBS.MSI downloaded in the previous step:

msiexec /qn /lvx* rbs_install_log.txt /i RBS.msi TRUSTSERVERCERTIFICATE=true FILEGROUP=PRIMARY DBNAME="<Database Name>" DBINSTANCE="<Instance Name>" FILESTREAMFILEGROUP=RBSFilestreamProvider FILESTREAMSTORENAME=FilestreamProvider_1

NOTE

Specify the full path to RBS.MSI in the above state, i.e. C:UsersAdministratorDesktopRBS.MSI. Replace the values for DBNAME and DBINSTANCE to match your environment.

On additional Web/Application servers open a Command Prompt with Administrator permissions and execute the following command to install RBS.MSI downloaded in the previous step:

Step 5 Enable Remote BLOB Storage

  1. On the Start menu, click All Programs.
  2. Click Microsoft SharePoint 2013 Products.
  3. Click SharePoint 2013 Management Shell.
  4. In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to set the content database to be configured:

$database=Get-SPContentDatabase –Identity “Database Name”

In the SharePoint 2013 Management Shell, enter the following Windows PowerShell statement to gets the object that holds settings that determine how the content database uses Microsoft SQL Server Remote Blob Storage:

$rbs=$database.RemoteBlobStorageSettings

In the SharePoint 2013 Management Shell, enter the following Windows PowerShell statement to determine if RBS has been installed for the selected content database:

$rbs.Installed()

NOTE

The result of $rbs.Installed() should be True, if the result is False, verify RBS.MSI has been installed successfully by reviewing rbs_install_log.txt. Ensure the install statement was running In the SharePoint 2010 Management Shell, enter the following Windows PowerShell statement to enable RBS for the selected content database:

$rbs.Enable()

In the SharePoint 2013 Management Shell, enter the following Windows PowerShell statements to set the RBSprovider for the selected content database:

$rbs.SetActiveProviderName($rbs.GetProviderNames()[0])

$rbs

NOTE

The result of $rbs should be:

Enabled

ActiveProviderName

MinimumBlobStorageSize

UpgradePersistedProperties

True

FileStreamProvider

0

()

Appendix for Table 1

Enabled specifies whether or not RBS has been enabled for the selected content database.

ActiveProviderName is name of the SQL Remote Blob Storage provider new files will be stored in. This will be null if new files will not be stored using SQL Remote Blob storage.

MinimumBlobStorageSize refers to the minimum size a BLOB may be to be considered RBS storage worthy, BLOB data exceeding the specified MinimumBlobStorageSize will be stored in the RBS data store.

Step 5.1 Configure the MinimumBlobStorageSize

  1. On the Start menu, click All Programs.
  2. Click Microsoft SharePoint 2013 Products.
  3. Click SharePoint 2013 Management Shell.
  4. In the SharePoint 2013 Management Shell, enter the following Windows PowerShell statements to configure the MinimumBlobStorageSize at 1MB:

$database = Get-SPContentDatabase “Database Name”

$database.RemoteBlobStorageSettings.MinimumBlobStorageSize=1048576

$database.Update()

UpgradePersistedProperties specifies the collection of field names and values for fields that were deleted or changed.

Step 6 Validate Installation

To validate the FILESTREAM configuration and RBS installation:

  1. Click Start, click All Programs, click Microsoft SQL Server 2012, and then click SQL Server Management Studio.
  2. Expand Databases.
  3. Select the content database for which you want to create a BLOB store, and then click New Query.
  4. In SQL Server Management Studio, click New Query to display the Query Editor.
  5. In Query Editor, enter the following Transact-SQL code:

USE [Database Name]

SELECT * FROM dbo.DatabaseInformation

Confirm that both the RBSCollectionId and RBSProvider rows are available.

Step 7 Test the RBS Data Store

  1. Select a desired Document Library on a site in the configured content database.
  2. Upload a file that is greater than 1 MB.
  3. On the computer that contains the RBS data store, click Start, and then click Computer.
  4. Browse to the RBS data store directory.
  5. Browse to the file list and open the folder that has the most recent modified date (other than $FSLOG). In that folder, open the file that has the most recent modified date. Verify that this file has the same size and contents as the file that you uploaded. If it does not, ensure that RBS is installed and enabled correctly.

The data store directory structure will appear similar to that in the following diagram.

Drawing1

    Resources

    FILESTREAM Overview

    How to: Enable FILESTREAM

    AlwaysOn Availability Groups (SQL Server)

    Remote BLOB Storage (SQL Server Whitepaper)

    Microsoft SQL Server AlwaysOn Solutions Guide for High Availability and Disaster Recovery

    SQL Server 2012 High Availability

    Standard
    Administration, SharePoint

    Implementing SQL Server Code Name “Denali” CTP3 AlwaysOn Availability Groups with SharePoint Server 2010

    If you attended my SharePoint Conference Session on SharePoint 2010 on SQL Server Denali you’re probably ready to get started with some of the features and capabilities we discussed and demonstrated today, particularly AlwaysOn Availability Groups which provide a robust, ready to use solution supporting both local redundancy and remote disaster recovery.

    NOTE

    SharePoint 2010 is not currently supported on SQL Server Code Name “Denali”.

    There are several prerequisites to using AlwaysOn which are documented further at http://msdn.microsoft.com/en-us/library/ff878487(v=SQL.110).

    Windows Server Failover Clustering

    While SQL Server Denali does not need to be clustered from a SQL Server perspective, the nodes on which SQL Server Denali is installed should be members of the same WSFC if configuring an AlwaysOn scenario.

    NOTE

    The steps in this post make several assumptions about the SQL Server environment where SQL Server Codename “Denali” will be installed. The steps to install and configure SQL Server Codename “Denali” may differ as a result.

    These steps will help you configure AlwaysOn in a SQL Server Code Name “Denali” environment.

    Download SQL Server Code Name “Denali” CTP3

    Download SQL Server Code Name “Denali” CTP 3.

    Download SQL Server Code Name “Denali” CTP3 at the TechNet Evaluations Center.

    Create or Select a Windows Server Failover Cluster

    Choose and existing or create a new Failover Cluster on which each node SQL Server Code Name “Denali” will be installed.

    Install .NET Framework 3.5.1

    On each Windows Server where SQL Server Code Name “Denali” will be installed install the .NET 3.5.1 Features.

    1. Open Server Manager and select the Features node.
    2. In the Feature pane select Add Features.
    3. Expand .NET Framework 3.5.1 Features and select .NET Framework 3.5.1.
    4. Click Next > to install the select Features.

    Install SQL Server Code Name “Denali” CTP3

    Install SQL Server Code Name “Denali” CTP3.  For installation instructions see also Installation for SQL Server ‘Denali’.

    Enable Named Pipes and AlwaysOn High Availability Groups

    Enable Named Pipes and AlwaysOn High Availability Groups.

    Enable Named Pipes

    1. Click Start | All Programs | Microsoft SQL Server Denali CTP3 | Configuration Tools | SQL Server Configuration Manager.
    2. Expand SQL Server Network Configuration and then select Protocols for MSSQLSERVER.
    3. Right-click Named Pipes and select Enable from the list of available options.

    NOTE

    MSSQLSERVER will need to be restarted to commit the changes.

    In SQL Server Code Name “Denali” you will need to include the startup option 9532 (TraceFlag 9532) to enable enabling AlwaysOn High Availability Groups.  To configure the required startup option on each Windows Server where SQL Server Code Name “Denali” is installed:

    1. Click Start | All Programs | Accessories | Command Prompt.
    2. Enter NET STOP MSSQLSERVER.
    3. Enter NET START MSSQLSERVER /T9532.

    Enable AlwaysOn High Availability Groups

    1. Click Start | All Programs | Microsoft SQL Server Denali CTP3 | Configuration Tools | SQL Server Configuration Manager.
    2. Select SQL Server Services.
    3. In the details pane right-click SQL Server (MSSQLSERVER) and select Properties from the list of the available options.
    4. Select AlwaysOn High Availability, select the checkbox labeled Enable AlwaysOn Availability Groups and click OK.

    NOTE

    The Windows Failover Cluster Name should appear on the AlwaysOn High Availability dialog.  MSSQLSERVER will need to be restarted to commit the changes.

    Create a Seed or select an existing Database

    Create a seed database.

    NOTE

    At least one database must exist to create a new Availability Group in Step 9 below.  This step is not required when installing SharePoint Server 2010 using DBA created databases.  For information on installing SharePoint Server 2010 using DBA created databases see Deploy by using DBA-created databases (SharePoint Server 2010).

    1. Click Start | All Programs | Microsoft SQL Server Denali CTP3 | SQL Server Management Studio.
    2. Right-click the Databases node and select New Database…
    3. Enter Seed in Database name: and click OK.

    Backup the Seed or an existing Database

    Backup the Seed Database

    1. Click Start | All Programs | Microsoft SQL Server Denali CTP3 | SQL Server Management Studio.
    2. Expand Databases.
    3. Right-click Seed and select Tasks, and then select Back Up…
    4. On the Back Up Database – Seed dialog click OK.

    NOTE

    Prior to adding a database to an Availability Group a FULL backup of the database must exist.

    Create a Network Share

    Create a Network Share

    A network share must exist and must be accessible by all nodes in the AlwaysOn configuration in order to perform initial data synchronization.

    Create an Availability Group

    Create a new Availability Group

    1. In Object Explorer, connect to the server instance that hosts the primary availability replica, and expand the server tree.
    2. To launch the New Availability Group Wizard, expand the Management node, right-click the Availability Groups node, and click New Availability Group.
    3. On the Specify Availability Group Name page, enter the name of the new availability group in the Availability group name field. This name must be a valid SQL Server identifier that is unique on the WSFC failover cluster and in your domain as a whole.
    4. On the Select Databases page, the User databases meeting high-availability requirements grid lists local user databases that are eligible to become the availability databases for the new availability group. Select one or more of the listed databases to participate as availability databases in the availability group. These local availability databases will initially be the primary databases of the new availability group. 
    5. On the Replicas tab, the Selected instances grid initially displays only the instance of SQL Server to which you are connected. This server instance will host the initial primary replica. To specify the server instance that will host the secondary replica, click Add. Note that in CTP3, you must add a single secondary replica now.
    6. Select the desired configuration for each instance in the Selected instances grid.
    7. Click Next.
    8. Click Finish to create the Availability Group.
    9. Click Start Data Synchronization to initiate initial data synchronization.

    NOTE

    The following restrictions exist for using the New Availability Group wizard to start data synchronization:

    • If the file paths on the secondary replica location from the file paths on the primary location, click Close to exit the New Availability Group wizard now and then start data synchronization manually.
    • If any secondary database already exists, using the New Availability Group wizard to start data synchronization requires manually deleting these secondary databases before you click Start Data Synchronization. If want to use your existing secondary databases, click Close to exit the New Availability Group wizard now and then start data synchronization manually.
    • If you have clicked Start Data Synchronization the Start Data Synchronization page opens. This page requires a network share (backup share). Either browse for your backup share, or enter its fully qualified universal naming convention (UNC) path name, \SystemnameShareNamePath, in the Specify a shared network location for backups field. Optionally, click Test to verify the path.

    For each database in the availability group, the Start Data Synchronization page displays the progress of the following operations:

    1. Creating a full database backup of the primary database on the network share.
    2. b. Creating a log backup (which will be part of the backup log chain) on the network share.
    3. c. Restoring these backups onto the secondary replica location. These restore operations both use RESTORE WITH NORECOVERY, leaving the new secondary database in the RESTORING state.
    4. d. Joining the secondary database to the availability group. This step puts the secondary database in to the ONLINE state, and starts data synchronization for this database.

    Column

    Description

    Replica Location

    Displays the name of the server instance that will host the availability replica.

    Read Mode in Secondary Role

    Specifies whether the availability databases on this replica location will be readable when the availability replica is serving as a secondary replica (performing the secondary role).

    Select one of the following values from the drop-down list:

    Value Description

    Disallow ConnectionsNo direct connections are allowed to secondary databases of this replica. They are not available for read access.

    Allow Only Read Intent ConnectionsOnly direct read-only connections are allowed to secondary databases of this replica. The secondary database(s) are all available for read access.

    Allow All ConnectionsAll connections are allowed to secondary databases of this replica, but only for read access. The secondary database(s) are all available for read access.

    Initial Role

    Indicates the role that the new replica will initially perform: Primary or Secondary.

    Create a Client Access Point

    An access point is a name and associated IP address information.  For additional information on Client Access Points in a Failover Cluster see also Understanding Access Points (Names and IP Addresses) in a Failover.  The Client Access Point will be used when configuring SharePoint 2010.

    1. Click Start | Administrative Tools, and then click Failover Cluster Manager.
    2. Expand the cluster.
    3. Expand Services and Applications, and select the name of the Availability Group created in the previous steps.
    4. Note that the resource group, AG1, has the same name as the availability group.
    5. In the Actions pane click Add a resource and select 1 – Client Access Point.
    6. In the Client Access Point dialog specify a name for the network name, and then click Next.
    7. In the Confirmation dialog box, click Next.
    8. In the Summary dialog box, click Finish.
    9. In the Summary of AG1 navigation pane, right-click AG1 under Other Resources, and then click Take this resource offline.
    10. In the Please confirm action dialog box, click Take AG1 offline.
    11. Right-click AG1 and then click Properties.
    12. In the AG1 Properties dialog box, click the Dependencies tab.
    13. Click Insert, and then click the drop-down box under the Resource column.
    14. In the drop-down list, select the network name, and then click OK.
    15. In the Summary of AG1 navigation pane, right-click AG1, and then click Bring this resource online.

    Configure SharePoint Server 2010

    Start the SharePoint 2010 Products Configuration Wizard.

    Create a new server farm specifying the name of the Client Access Point as the name of the database sever.

    Add Databases to the Availability Group

    1. In Object Explorer, connect to the server instance that hosts the primary replica of the availability group, and expand the server tree.
    2. Expand the Management node, the AlwaysOn High Availability node, and the Availability Groups node.
    3. Right-click the availability group to which you are adding a database, and select the Add Database command. This command launches the Add Database to Availability Group Wizard.
    4. On the Select Databases page, select one or more databases.
    5. On the Select Initial Data Synchronization page, choose how you want your new secondary databases to be created and joined to the availability group. Choose one of the following options:
    6. · Full
    7. In the Specify a shared network location accessible by all replicas: field, specify a backup share to which all of the server instance that host replicas have read-write access.
    8. On the Connect to Existing Secondary Replicas page, Information_still_to_come.
    9. The Validation page verifies whether the values you specified in this Wizard meet the requirements of the New Availability Group Wizard. If the validation changes, you can click Previous to return to an earlier wizard page to change one or more values. The click Next to return to the Validation page, and click Re-run Validation.
    10. On the Summary page, review your choices for the new availability group. To make a change, click Previous to return to the relevant page. After making the change, click Next to return to the Summary page.
    11. If you are satisfied with your selections, optionally click Script to create a script of the steps the wizard will execute. Then, to create and configure the new availability group, click Finish.
    12. The Progress page displays the progress of the steps for creating the availability group (configuring endpoints, creating the availability group, and joining the secondary replica to the group).
    13. When these steps complete, the Results page displays the result of each step. If all these steps succeed, the new availability group is completely configured. If any of the steps result in an error, you might need to manually complete the configuration. For information about the cause of a given error, click the associated “Error” link in the Result column.
    14. When the wizard completes, click Close to exit.

    Once all databases have been added to one or more Availability Groups the configuration is complete.

    NOTE

    SharePoint 2010 is not currently supported on SQL Server Code Name “Denali”.

    Standard