Error 41106: Failed to Join the Availability Group for SQL Always On

If you encountered the following error when add replica to Availability Group

Error 41106

Try to turn off Windows firewall on both nodes. Open "Windows Firewall with Advanced Security".
Turn off Domain Profile
Turn off Private Profile
Turn off Public Profile

Retry to add again. Now you should be successful.

To open windows firewall traffic, create a new inbound rule | Add Port | 5022 | TCP | Apply to specific local ports: 5022

That should do the trick! 

Hope this work

Setup SQL Always On

Let build a SQL Always On...

Just follow the following steps to configure a high availability SQL Always On.

• Node running Windows Server 2016
• SQL Server 2012

Steps

1. Create a Windows Failover Cluster. Example 2 nodes

• Node1
• Node2

2. Install default standalone SQL instance on both nodes
3. Open SQL Server Configuration Manager, edit the Properties of SQL Server (MSSQLServer). On AlwaysOn High Availability tab, tick "Enable AlwaysOn Availability Groups and restart sql services

4. Open SQL Server Management Studio and Connect to SQL Server Instance
5. Create a new database first. Make sure that have performed a full database backup
5. Create a new availability group. Go to AlwaysOn High Availability | Availability Group | New Availability Group Wizard.

To create an availability group, you will need to:

• specify an availability group name

• select one or more user database

• specify one or more instance of SQL Server to host secondary availability replicas

-Add Replica ->Select Node2
-Configure automatic failover
-set the synchronous commit
-set readable secondary

• specify your availability group listener preference

• select your initial data synchronization preference

-shared a folder.Make sure both nodes has Write permission Example:-
\\Node1\Shared

• check the validation result of availability group creation

This will create and configure the SQL Always On Availability Group and join the database.

End result:-

Force Cluster Node from Quarantine to Normal State

By default, cluster node running on Windows Server 2016 enter to quarantine state when the node connectivity has an issue. The lock period is 7200 sec. (that will be 120 minutes).

To force the node to normal state, on quarantine node open Windows powershell to execute cmd
Start-ClusterNode - ClearQuarantine

Quarantine node will back to normal ("UP") status

If problem persist, please check on event viewer to identify the potential issue.

Uninstall Veeam Agent for Linux

The following is the command to remove Veeam Agent for Linux that install on Centos/RHEL/Oracle Linux/Fedora workload

Type:-
yum remove veeam veeamsnap

Sneak Peak Project Honolulu-Web Based Management Solution

Project Honolulu is a new web-based management solution from Microsoft, build to modernize and simplify administration of your Windows datacenter. Currently under technical preview, to download click here:- https://www.microsoft.com/en-us/evalcenter/evaluate-windows-server-honolulu

After installation, you can start to Add Server that you would like to manage.

Added 3 servers: two running Windows Server 2016 and one running Windows Server 2016 Build 1709.

Based on our testing, we can manage the server, monitor performance utilization & basic administration.
Example:- Join to domain, restart server, shutdown, etc

Example:- Initialize new disk

 Example:- Format a volume

 Example:- Install Roles & Features

During our testing, the product is missing on the configuration of roles. Probably the product is still under "technical preview" & we may able to do it when the product is GA.

Give it a try if you're interested about this Project Honolulu.

Backup Windows Server 2016 Hyper-V Over SMB

In this post, we are going to look on how to perform backup Windows Server 2016 Hyper-V Over SMB by using Veeam product. VM is residing on smb path.

My scenario:-

• Host running Windows Server 2016 Hyper-V
• VM on SMB 3.1.1 Files Shares
• Veeam Backup & Replication v9.5 Update 2

To cut it short, we have documented the step by step on how to "Configure Hyper-V Over SMB" on this link:- http://www.ms4u.info/2012/11/configure-hyper-v-over-smb.html

In below video, you able to see how Veeam use Resilient Change Tracking (RCT), natively on Windows Server 2016 to perform backup.

Checklist:-
VM  run on SMB Path..........Passed
Full backup ..........................Passed
Incremental backup .............Passed

Restore On-Premise Exchange Server and Office365

In Previous post, we have look on how to backup on-premise exchange server & office365. Next, we are going to use Veeam Backup for Office365 v1.5 to recover

a) Mail item (email)
b) Task
c) Perform ediscovery to locate user mailbox items

Feel free to check this video:-

My lab scenario:-
a) delete an email subject "Love letter from Lai"
b) delete 2 tasks
c) recover my email subject "Love letter from Lai"
d) recover 2 tasks
e) perform ediscovery by specify criteria to look for subject "love"

Backup On-Premise Exchange Server and Office365

In this post, we are looking on how to backup on-premise exchange server & office365 using Veeam backup for office365 v1.5 (VBO)

v1.5 is latest release which support hybrid environment. In below video, you can see how to configure
a) backup office365 mailbox
b) backup on-premise exchange server
c) Configure policy to backup entire mailbox or selected mailbox
d) exclude user mailbox that you do not want to backup
e) exclude mailbox folder from backup (example:-draft, deleted items, junk email, outbox, sync issue. in-place hold items & litidation hold items

the best part v1.5 able to support multi tenancy to backup different email domain.You can add new backup proxy and add multiple backup repository. The concept is sound familar like using Veeam Backup & replication. Service provider can now use this product as new service besides than BaaS or DraaS.

v1.5 also included with powershell and Restful API.

Public folder is now supported.

Lastly VBO v1.5, extended support include Office 365 U.S. Government (DoD and non-DoD), Office 365 Germany and Office 365 China.

Feel free to check below video:-


My lab scenario:-
a) On-premise exchange server running Exchange 2013
b) Office365 - domain:- ms4ucloud.info

Slide:- 1 Availability, Any App, Any Data, Any Cloud

During Microsoft Hybrid Cloud Launching event @Malaysia, i have session on Cloud Infrastructure Track. During 45 minutes, i've talked about different scenario on

a) To the cloud

Scenario on move backup data to MS Azure & Migrate on-premise workload to MS Azure

b) From the cloud

Protecting Office365 using Veeam Backup for Office365 & sharing on latest version 1.5 which support multi-tenancy & hybrid environment:- Office365 & Exchange on-premise.

c) Within the cloud

Monitoring environment using System Center Operation Manager & MS OMS

Backup & Recovery Azure Virtual Machine

Centralize Monitoring

Backup & Recover MS Azure Stack

Pictures

#1 Availability, Any app, Any data, Any cloud from Lai Yoong Seng

Booth Demo - Backup Solution on Microsoft Azure Stack

During Microsoft Hybrid Cloud Launching event @Malaysia, together with HPE team, we have presented about backup solution on MS Azure Stack.

Backup Solution on Microsoft Azure Stack from Lai Yoong Seng